From owner-freebsd-current Sun Mar 8 00:22:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA27535 for freebsd-current-outgoing; Sun, 8 Mar 1998 00:22:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mn26hp6.honeywell.com (mn26hp6.honeywell.com [129.30.4.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA27497 for ; Sun, 8 Mar 1998 00:22:02 -0800 (PST) (envelope-from sleas@mn26hp6.honeywell.com) Received: from localhost by mn26hp6.honeywell.com with SMTP (1.40.112.4/16.2) id AA235955232; Sun, 8 Mar 1998 02:20:32 -0600 Date: Sun, 8 Mar 1998 02:20:32 -0600 (CST) From: Shawn Leas To: Mike Smith Cc: quiksilver , current@FreeBSD.ORG, Jamie Novak Subject: Re: ATAPI Zip Drive In-Reply-To: <199803080805.AAA09170@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 Sun, 8 Mar 1998, Mike Smith wrote: > > How do you mount an ATAPI Zip drive? > > 4 screws, two down either side, or from underneath. If you want to get > it into a 5.25" drive bay, you'll need a bracket set to suit a floppy > drive (it has the same mounting requirements as a 3.5" floppy). 1) Will this work with -current, and -stable?? 2) I heard that your "mounting brackets" break NFS, that means server AND client! 3) Why don't you just commit these "screws" and "brackets". Is this just a kludge fix? Shouldn't they be in the distribution? 4) Why didn't you didn't post the URL of where to download these things. 5) I think by "mounting", he really meant that he was sexually attracted to his ZIP drive. Pfah HA, hoh, stop it, you're killing me!!! Please mail this to misc-mounting-hardware@freebsd.org. > -- > \\ 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 <=========== America Held Hostage ===========> Day 1873 for the poor and the middle class. Day 1892 for the rich and the dead. 1049 days remaining in the Raw Deal. <============================================> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 00:29:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28720 for freebsd-current-outgoing; Sun, 8 Mar 1998 00:29:29 -0800 (PST) (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 AAA28712 for ; Sun, 8 Mar 1998 00:29:23 -0800 (PST) (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 JAA10805; Sun, 8 Mar 1998 09:28:47 +0100 (CET) To: Nate Williams cc: Dmitrij Tejblum , Terry Lambert , current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-reply-to: Your message of "Sat, 07 Mar 1998 17:02:48 MST." <199803080002.RAA05223@mt.sri.com> Date: Sun, 08 Mar 1998 09:28:47 +0100 Message-ID: <10803.889345727@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Tell me what I'm missing, if anything? You're absolutely right. Terry is obfuscating the argument because he is trying to cover up for the fact that he didn't realize what the default operations vectors were there for. -- 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 Mar 8 01:52:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06366 for freebsd-current-outgoing; Sun, 8 Mar 1998 01:52:51 -0800 (PST) (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 BAA06359 for ; Sun, 8 Mar 1998 01:52:48 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id EAA02939 for current@freebsd.org; Sun, 8 Mar 1998 04:52:47 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803080952.EAA02939@dyson.iquest.net> Subject: Performance problem in -current To: current@FreeBSD.ORG Date: Sun, 8 Mar 1998 04:52:47 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have noticed a paging performance problem in -current. Will address first thing in the morning. The problem is fairly minor, and is manifest by overly aggressive pagedaemon activity. Hopefully, the system will be much more stable. -- 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 Mar 8 03:18:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14193 for freebsd-current-outgoing; Sun, 8 Mar 1998 03:18:16 -0800 (PST) (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 DAA14176 for ; Sun, 8 Mar 1998 03:18:08 -0800 (PST) (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 NAA27113 for ; Sun, 8 Mar 1998 13:17:53 +0200 (EET) 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 NAA09284 for ; Sun, 8 Mar 1998 13:17:52 +0200 (EET) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.8.8/8.8.8/8.Who.Cares) with UUCP id NAA08513 for current@freebsd.org; Sun, 8 Mar 1998 13:15:43 +0200 (EET) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id MAA00495; Sun, 8 Mar 1998 12:53:18 +0200 (EET) (envelope-from archer) Message-ID: <19980308125317.47202@carrier.kiev.ua> Date: Sun, 8 Mar 1998 12:53:17 +0200 From: Alexander Litvin To: current@FreeBSD.ORG Subject: Bad string table index Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I experience the following problem. When I build kernel with -g, then "strip -d" it, it doesn't boot -- I just see "Bad string table index ()" running on the screen. When kernel is built without debugging info, it boots just ok. I assume it has someting to do with kernel symbol table, right? Kernel sources cvsupped at Sun Mar 8 09:47:49 GMT 1998, userland about some eight hour older. --- Hurewitz's Memory Principle: The chance of forgetting something is directly proportional to... to... uh..... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 03:20:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14445 for freebsd-current-outgoing; Sun, 8 Mar 1998 03:20:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14399 for ; Sun, 8 Mar 1998 03:20:01 -0800 (PST) (envelope-from pantzer@sister.ludd.luth.se) Received: from sister.ludd.luth.se (pantzer@sister.ludd.luth.se [130.240.16.77]) by zed.ludd.luth.se (8.8.5/8.8.5) with SMTP id MAA13128; Sun, 8 Mar 1998 12:19:57 +0100 Message-Id: <199803081119.MAA13128@zed.ludd.luth.se> X-Mailer: exmh version 2.0.1 12/23/97 To: Mikael Karpberg cc: current@FreeBSD.ORG Subject: Re: Okay, -current should be conditionally safe to use In-reply-to: Your message of "Sun, 08 Mar 1998 01:28:51 +0100." <199803080028.BAA03950@ocean.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 12:19:56 +0100 From: Mattias Pantzare Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > another interesting thing to try is: > > > > sysctl -w vfs.nfs.async=1 > > > > on the server. This is better (safer) than softupdates, but you *can* > > have data lossage, due to writes not being committed to disk. It is > > a good idea to have a UPS when using the above option. > > We certainly don't have a UPS. > What exactly does turning on that sysctl mean? That we can get an > inconsistant state on the disk, like with mount option async, or that > writes are ACKed (or whatever you call it) directly, and then queued for > a normal write to the disk according to the disks mount options? > The latter would mean nothing except data loss at a crash, I guess, and > that doesn't seem so bad, since data written the second a crash or > power outage happens is still pretty much doomed. If vfs.nfs.async is on and the NFS server crashes and has data not written to the disk, then the client won't know that the data never got to the disk and will continue as nothing hapend. Not very good... If nfs.async was not on then the client would have repeated the write when the server was up again. UPS and a stable OS and vfs.nfs.async => presto. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 06:36:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29546 for freebsd-current-outgoing; Sun, 8 Mar 1998 06:36:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ultracom.net (mail.ultracom.net [207.86.154.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29541 for ; Sun, 8 Mar 1998 06:36:07 -0800 (PST) (envelope-from quik@ultracom.net) Received: from uart ([207.86.154.210]) by mail.ultracom.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-40194U2500L250S0) with SMTP id AAA130 for ; Sun, 8 Mar 1998 09:50:39 -0500 Date: Sun, 8 Mar 1998 09:31:22 -0500 (EST) From: quiksilver X-Sender: quik@uart To: current@FreeBSD.ORG Subject: Re: ATAPI Zip Drive 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 Funny.. I was really refering to what device I'm supposed to use. On Sun, 8 Mar 1998, Shawn Leas wrote: > > On Sun, 8 Mar 1998, Mike Smith wrote: > > > > How do you mount an ATAPI Zip drive? > > > > 4 screws, two down either side, or from underneath. If you want to get > > it into a 5.25" drive bay, you'll need a bracket set to suit a floppy > > drive (it has the same mounting requirements as a 3.5" floppy). > > 1) Will this work with -current, and -stable?? > > 2) I heard that your "mounting brackets" break NFS, that > means server AND client! > > 3) Why don't you just commit these "screws" and "brackets". Is > this just a kludge fix? Shouldn't they be in the distribution? > > 4) Why didn't you didn't post the URL of where to download these > things. > > 5) I think by "mounting", he really meant that he was sexually > attracted to his ZIP drive. > > Pfah HA, hoh, stop it, you're killing me!!! Please mail this > to misc-mounting-hardware@freebsd.org. > > > -- > > \\ 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 > > <=========== America Held Hostage ===========> > Day 1873 for the poor and the middle class. > Day 1892 for the rich and the dead. > 1049 days remaining in the Raw Deal. > <============================================> > > > 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 Mar 8 06:41:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00221 for freebsd-current-outgoing; Sun, 8 Mar 1998 06:41:55 -0800 (PST) (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 GAA00216 for ; Sun, 8 Mar 1998 06:41:53 -0800 (PST) (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 GAA10490; Sun, 8 Mar 1998 06:40:36 -0800 (PST) Message-Id: <199803081440.GAA10490@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: quiksilver cc: current@FreeBSD.ORG Subject: Re: ATAPI Zip Drive In-reply-to: Your message of "Sun, 08 Mar 1998 09:31:22 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 06:40:35 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Funny.. > I was really refering to what device I'm supposed to use. Well, why didn't you say so? You asked how to mount one, I told you. If what you mean is "I have installed an ATAPI Zip drive and I am at a loss as to how to go about using it" then that's probably a good thing to start by saying. There is a succint description of the process at http://www.mui.net/hilo/syscon/atapi.html, recently posted by a happy new Zip user. The process is the same for -current as it is for -stable. Enjoy! -- \\ 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 Mar 8 06:52:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01734 for freebsd-current-outgoing; Sun, 8 Mar 1998 06:52:47 -0800 (PST) (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 GAA01721 for ; Sun, 8 Mar 1998 06:52:27 -0800 (PST) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id PAA05384 for freebsd-current@freebsd.org; Sun, 8 Mar 1998 15:51:57 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.8.8/8.8.5/pb-19970302) id PAA06463; Sun, 8 Mar 1998 15:51:42 +0100 (CET) Message-ID: <19980308155141.YE46219@@> Date: Sun, 8 Mar 1998 15:51:42 +0100 From: pb@fasterix.freenix.org (Pierre Beyssac) To: freebsd-current@FreeBSD.ORG Subject: something weird about CTM patch 3278 X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it just me, or is there something weird with CTM patch 3278 ? It seems to delete a great deal of important stuff ? Just to name a few: ctm_rmail: ctm: > DR gnu/usr.bin/pr ctm_rmail: ctm: > DR gnu/usr.bin/yppush ctm_rmail: ctm: > DR lib/librpc ctm_rmail: ctm: > DR sbin/comcontrol ctm_rmail: ctm: > DR sbin/fdisk ctm_rmail: ctm: > DR sbin/mount_devfs ctm_rmail: ctm: > DR sbin/mount_fdesc ctm_rmail: ctm: > DR sbin/mount_kernfs ctm_rmail: ctm: > DR sbin/mount_lfs ctm_rmail: ctm: > DR sbin/mount_msdos ctm_rmail: ctm: > DR sbin/mount_procfs ctm_rmail: ctm: > DR usr.bin/diff ctm_rmail: ctm: > DR usr.bin/grep ctm_rmail: ctm: > DR usr.bin/ld ctm_rmail: ctm: > DR usr.bin/man ctm_rmail: ctm: > DR usr.bin/patch ctm_rmail: ctm: > DR usr.bin/uucp ctm_rmail: ctm: > DR usr.bin/whatis ctm_rmail: ctm: > DR usr.sbin/bind ctm_rmail: ctm: > DR usr.sbin/bootpd ctm_rmail: ctm: > DR usr.sbin/routed ctm_rmail: ctm: > DR usr.sbin/sup ctm_rmail: ctm: > DR usr.sbin/swapinfo ctm_rmail: ctm: > DR usr.sbin/update -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 07:00:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02634 for freebsd-current-outgoing; Sun, 8 Mar 1998 07:00:53 -0800 (PST) (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 GAA02515 for ; Sun, 8 Mar 1998 06:59:30 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id PAA05799 for current@FreeBSD.ORG; Sun, 8 Mar 1998 15:59:12 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id PAA06254; Sun, 8 Mar 1998 15:06:39 +0100 (CET) (envelope-from roberto) Message-ID: <19980308150639.A6195@keltia.freenix.fr> Date: Sun, 8 Mar 1998 15:06:39 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Okay, -current should be conditionally safe to use Mail-Followup-To: current@FreeBSD.ORG References: <199803080059.TAA00326@dyson.iquest.net> <2649.889329889@gjp.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <2649.889329889@gjp.erols.com>; from Gary Palmer on Sat, Mar 07, 1998 at 11:04:49PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4103 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Gary Palmer: > Apart from the problems with using Async & SoftUpdates together, what > other `known' problems are there? The panic Amancio and I have seen is not related to async + softupdates, just softupdates themselves. It always panic in softdep_setup_allocindir_page while doing a bcopy. #10 0xf019e5d2 in generic_bcopy () #11 0xf0172637 in softdep_setup_allocindir_page (ip=0xf09e0c00, lbn=203, bp=0xf1ca394c, ptrno=191, newblkno=303640, oldblkno=0, nbp=0xf1cc4cd4) at ../../ufs/ffs/ffs_softdep.c:1416 #12 0xf016fbbd in ffs_balloc (ap=0xf4048e94) at ../../ufs/ffs/ffs_balloc.c:302 #13 0xf017936c in ffs_write (ap=0xf4048ee8) at vnode_if.h:995 #14 0xf013ac27 in vn_write (fp=0xf0a2adc0, uio=0xf4048f30, cred=0xf0aca800) at vnode_if.h:331 #15 0xf011b9cb in write (p=0xf3f42f00, uap=0xf4048f84) softdep_setup_allocindir_page() has no bcopy but calls softdep_setup_allocindir_page2 which has one at the end: -=-=-=-=- MALLOC(newindirdep, struct indirdep *, sizeof(struct indirdep), M_INDIRDEP, M_WAITOK); newindirdep->ir_list.wk_type = D_INDIRDEP; newindirdep->ir_state = ATTACHED; LIST_INIT(&newindirdep->ir_deplisthd); LIST_INIT(&newindirdep->ir_donehd); newindirdep->ir_saveddata = (ufs_daddr_t *)bp->b_data; newindirdep->ir_savebp = getblk(ip->i_devvp, bp->b_blkno, bp->b_bcount, 0, 0); bcopy((caddr_t)newindirdep->ir_saveddata, newindirdep->ir_savebp->b_data, bp->b_bcount); } } -=-=-=-=- -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 07:04:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03241 for freebsd-current-outgoing; Sun, 8 Mar 1998 07:04:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03231; Sun, 8 Mar 1998 07:04:29 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id PAA17374; Sun, 8 Mar 1998 15:45:08 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.7) id PAA01013; Sun, 8 Mar 1998 15:35:08 +0100 (CET) (envelope-from andreas) Message-ID: <19980308153508.12630@klemm.gtn.com> Date: Sun, 8 Mar 1998 15:35:08 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Cc: dyson@FreeBSD.ORG Subject: page fault while in kernel mode (-current from this morning && softupdates) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! I grabbed the newest -current and enabled Softtupdates. I don't know, if this problem is more related to softupdates, SMP or to -current's vm system. I already noticed, that some people seemed to have trouble with enabling noatime. This is the first panic, but I'll keep you informed. It happened when I left X11 session with CTRL-ALT-BS Here what DDB told me: Fatal trap 12: page fault while in kernel mode mp_lock=00000002 cpuip=0 lapic.id=01000000 fault virtual address = 0xf1349ff8 Supervisor read page not present ... Current process = 306 (XF86_SVGA) kernel: type 12 trap, code=0 .... Stopped at _pmap_remove_all+0x10d: movel 0x8(%esi), %ebr _pmap_remove_all _pmap_page_protect _vmobject_terminate _vmobject_deallocate _vm_map_entry_delete _vm_map_delete _vm_map_remove _exit1 _exit _syscall _xsyscall ---syscall 0x1, I use SMP, BISDN and Softupdates /dev/sd0a on / (local, writes: sync 7 async 152) /dev/sd0s2f on /usr (local, soft-updates, writes: sync 2 async 207) /dev/sd0s2e on /var (local, soft-updates, writes: sync 103 async 312) /dev/ccd0c on /obj (asynchronous, local, noatime, soft-updates, writes: sync 2 async 0) /dev/ccd1c on /news (local, noatime, soft-updates, writes: sync 2 async 0) /dev/ccd2c on /proxy (local, noatime, soft-updates, writes: sync 2 async 31) /dev/ccd3c on /home (local, writes: sync 133 async 68) procfs on /proc (local, writes: sync 0 async 0) /dev/sd0s1 on /dos (local, read-only, writes: sync 0 async 0) mfs:33 on /tmp (asynchronous, local, noatime, writes: sync 49 async 120) # # BISDN kernel # machine "i386" cpu "I686_CPU" ident BISDNSMP maxusers 64 # SMP Stuff options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O #options USER_LDT # for Wine #Debugging options DDB options KTRACE #kernel tracing options SHOW_BUSYBUFS # busy buffers on shutdown ? options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor # Networking options INET #InterNETworking options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about dropped packets options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets # filesystems options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Kirk McKusick's code options DSI_SOFT_MODEM #code for DSI Softmodems options QUOTA #enable disk quotas options NFS #Network File System options MFS #Memory File System options PROCFS #Process filesystem options MSDOSFS #MS DOS File System options "CD9660" #ISO 9660 filesystem options NSWAPDEV=3 #Allow this many swap-devices. options FDESC #File descriptor filesystem # misc options options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options SYSVSHM,SYSVSEM,SYSVMSG #shared memory (X11) options "MD5" options COMPAT_LINUX # Linux Binary compatibility #options "VM86" config kernel root on sd1 # ISA and PCI BUS support controller isa0 controller pci0 # PnP Support controller pnp0 # Floppy Disk Controller controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # SCSI Devices # AHA 2940U controller ahc0 controller scbus0 at ahc0 disk sd0 at scbus0 target 0 unit 0 disk sd3 at scbus0 target 1 unit 0 tape st0 at scbus0 target 4 device worm0 at scbus0 target 5 device cd0 at scbus0 target 6 # AHA 2940 controller ahc1 controller scbus1 at ahc1 disk sd1 at scbus1 target 1 unit 0 disk sd2 at scbus1 target 2 unit 0 options AHC_TAGENABLE # tagged command queueing options AHC_ALLOW_MEMIO options AHC_SCBPAGING_ENABLE options SCSI_REPORT_GEOMETRY # SCO compatible system console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=4 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines # floating point unit device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr # serial devices on mainboard # `flags' for serial drivers that support consoles (only for sio now): # 0x10 enable console support for this unit. The other console flags # are ignored unless this is set. Enabling console support does # not make the unit the preferred console - boot with -h or set # the 0x20 flag for that. Currently, at most one unit can have # console support; the first one (in config file order) with # this flag set is preferred. Setting this flag for sio0 gives # the old behaviour. # 0x20 force this unit to be the console (unless there is another # higher priority console). This replaces the COMCONSOLE option. # 0x40 reserve this unit for low level console operations. Do not # device sio0 at isa? port "IO_COM1" tty irq 4 flags 0x20 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to DDB, #if available. options CONSPEED=38400 #default speed for serial console #(default 9600) # parallel device on mainboard device lpt0 at isa? port? tty irq 7 vector lptintr # PS/2 mouse on mainboard device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr options "PSM_ACCEL=1" # PS/2 mouse acceleration # Joystick device joy0 at isa? port "IO_GAME" # Network 3COM PCI device vx0 device ed0 at isa? port 0x280 net irq 10 iomem 0xd0000 vector edintr # Soundblaster 16 # SoundBlaster DSP driver - for SB, SB Pro, SB16, PAS(emulating SB) # SoundBlaster 16 DSP driver - for SB16 - requires sb0 device # SoundBlaster 16 MIDI - for SB16 - requires sb0 device # Yamaha OPL-2/OPL-3 FM - for SB, SB Pro, SB16, PAS # controller snd0 # device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr # device sbxvi0 at isa? port? irq? drq 5 conflicts # device sbmidi0 at isa? port 0x330 irq? conflicts # device opl0 at isa? port 0x388 conflicts # pcm: PCM audio through various sound cards. device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x15 vector pcmintr # Pseudo devices pseudo-device loop pseudo-device ether pseudo-device vn 1 #Vnode driver (turns a file into a dev.) pseudo-device tun 1 #user mode ppp pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device ccd 4 #Concatenated disk driver pseudo-device ppp 1 #Point-to-point protocol pseudo-device su #scsi user pseudo-device ssc #super scsi options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) # BISDN options IPI_VJ # Van Jacobsen header compression support #options "IPI_DIPA=3" # send ip accounting packets every 3 seconds options TELES_HAS_MEMCPYB # bisdn 0.97 # Teles S0/16.3 ###################################################### IRQ 9 ## controller tel0 at isa? port 0xd80 net irq 9 vector telintr pseudo-device disdn pseudo-device isdn pseudo-device ipi 4 pseudo-device ispy 4 pseudo-device itel 2 -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 07:04:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03304 for freebsd-current-outgoing; Sun, 8 Mar 1998 07:04:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03237; Sun, 8 Mar 1998 07:04:34 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id QAA18759; Sun, 8 Mar 1998 16:00:08 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.7) id PAA01013; Sun, 8 Mar 1998 15:35:08 +0100 (CET) (envelope-from andreas) Message-ID: <19980308153508.12630@klemm.gtn.com> Date: Sun, 8 Mar 1998 15:35:08 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Cc: dyson@FreeBSD.ORG Subject: page fault while in kernel mode (-current from this morning && softupdates) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! I grabbed the newest -current and enabled Softtupdates. I don't know, if this problem is more related to softupdates, SMP or to -current's vm system. I already noticed, that some people seemed to have trouble with enabling noatime. This is the first panic, but I'll keep you informed. It happened when I left X11 session with CTRL-ALT-BS Here what DDB told me: Fatal trap 12: page fault while in kernel mode mp_lock=00000002 cpuip=0 lapic.id=01000000 fault virtual address = 0xf1349ff8 Supervisor read page not present ... Current process = 306 (XF86_SVGA) kernel: type 12 trap, code=0 .... Stopped at _pmap_remove_all+0x10d: movel 0x8(%esi), %ebr _pmap_remove_all _pmap_page_protect _vmobject_terminate _vmobject_deallocate _vm_map_entry_delete _vm_map_delete _vm_map_remove _exit1 _exit _syscall _xsyscall ---syscall 0x1, I use SMP, BISDN and Softupdates /dev/sd0a on / (local, writes: sync 7 async 152) /dev/sd0s2f on /usr (local, soft-updates, writes: sync 2 async 207) /dev/sd0s2e on /var (local, soft-updates, writes: sync 103 async 312) /dev/ccd0c on /obj (asynchronous, local, noatime, soft-updates, writes: sync 2 async 0) /dev/ccd1c on /news (local, noatime, soft-updates, writes: sync 2 async 0) /dev/ccd2c on /proxy (local, noatime, soft-updates, writes: sync 2 async 31) /dev/ccd3c on /home (local, writes: sync 133 async 68) procfs on /proc (local, writes: sync 0 async 0) /dev/sd0s1 on /dos (local, read-only, writes: sync 0 async 0) mfs:33 on /tmp (asynchronous, local, noatime, writes: sync 49 async 120) # # BISDN kernel # machine "i386" cpu "I686_CPU" ident BISDNSMP maxusers 64 # SMP Stuff options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O #options USER_LDT # for Wine #Debugging options DDB options KTRACE #kernel tracing options SHOW_BUSYBUFS # busy buffers on shutdown ? options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor # Networking options INET #InterNETworking options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about dropped packets options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets # filesystems options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Kirk McKusick's code options DSI_SOFT_MODEM #code for DSI Softmodems options QUOTA #enable disk quotas options NFS #Network File System options MFS #Memory File System options PROCFS #Process filesystem options MSDOSFS #MS DOS File System options "CD9660" #ISO 9660 filesystem options NSWAPDEV=3 #Allow this many swap-devices. options FDESC #File descriptor filesystem # misc options options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options SYSVSHM,SYSVSEM,SYSVMSG #shared memory (X11) options "MD5" options COMPAT_LINUX # Linux Binary compatibility #options "VM86" config kernel root on sd1 # ISA and PCI BUS support controller isa0 controller pci0 # PnP Support controller pnp0 # Floppy Disk Controller controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # SCSI Devices # AHA 2940U controller ahc0 controller scbus0 at ahc0 disk sd0 at scbus0 target 0 unit 0 disk sd3 at scbus0 target 1 unit 0 tape st0 at scbus0 target 4 device worm0 at scbus0 target 5 device cd0 at scbus0 target 6 # AHA 2940 controller ahc1 controller scbus1 at ahc1 disk sd1 at scbus1 target 1 unit 0 disk sd2 at scbus1 target 2 unit 0 options AHC_TAGENABLE # tagged command queueing options AHC_ALLOW_MEMIO options AHC_SCBPAGING_ENABLE options SCSI_REPORT_GEOMETRY # SCO compatible system console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=4 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines # floating point unit device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr # serial devices on mainboard # `flags' for serial drivers that support consoles (only for sio now): # 0x10 enable console support for this unit. The other console flags # are ignored unless this is set. Enabling console support does # not make the unit the preferred console - boot with -h or set # the 0x20 flag for that. Currently, at most one unit can have # console support; the first one (in config file order) with # this flag set is preferred. Setting this flag for sio0 gives # the old behaviour. # 0x20 force this unit to be the console (unless there is another # higher priority console). This replaces the COMCONSOLE option. # 0x40 reserve this unit for low level console operations. Do not # device sio0 at isa? port "IO_COM1" tty irq 4 flags 0x20 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to DDB, #if available. options CONSPEED=38400 #default speed for serial console #(default 9600) # parallel device on mainboard device lpt0 at isa? port? tty irq 7 vector lptintr # PS/2 mouse on mainboard device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr options "PSM_ACCEL=1" # PS/2 mouse acceleration # Joystick device joy0 at isa? port "IO_GAME" # Network 3COM PCI device vx0 device ed0 at isa? port 0x280 net irq 10 iomem 0xd0000 vector edintr # Soundblaster 16 # SoundBlaster DSP driver - for SB, SB Pro, SB16, PAS(emulating SB) # SoundBlaster 16 DSP driver - for SB16 - requires sb0 device # SoundBlaster 16 MIDI - for SB16 - requires sb0 device # Yamaha OPL-2/OPL-3 FM - for SB, SB Pro, SB16, PAS # controller snd0 # device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr # device sbxvi0 at isa? port? irq? drq 5 conflicts # device sbmidi0 at isa? port 0x330 irq? conflicts # device opl0 at isa? port 0x388 conflicts # pcm: PCM audio through various sound cards. device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x15 vector pcmintr # Pseudo devices pseudo-device loop pseudo-device ether pseudo-device vn 1 #Vnode driver (turns a file into a dev.) pseudo-device tun 1 #user mode ppp pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device ccd 4 #Concatenated disk driver pseudo-device ppp 1 #Point-to-point protocol pseudo-device su #scsi user pseudo-device ssc #super scsi options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) # BISDN options IPI_VJ # Van Jacobsen header compression support #options "IPI_DIPA=3" # send ip accounting packets every 3 seconds options TELES_HAS_MEMCPYB # bisdn 0.97 # Teles S0/16.3 ###################################################### IRQ 9 ## controller tel0 at isa? port 0xd80 net irq 9 vector telintr pseudo-device disdn pseudo-device isdn pseudo-device ipi 4 pseudo-device ispy 4 pseudo-device itel 2 -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 07:20:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04712 for freebsd-current-outgoing; Sun, 8 Mar 1998 07:20:12 -0800 (PST) (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 HAA04706; Sun, 8 Mar 1998 07:20:06 -0800 (PST) (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 HAA10644; Sun, 8 Mar 1998 07:18:50 -0800 (PST) Message-Id: <199803081518.HAA10644@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Michael Smith cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c In-reply-to: Your message of "Sun, 08 Mar 1998 07:06:58 PST." <199803081506.HAA06931@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 07:18:50 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Modified files: > sys/i386/i386 autoconf.c > Log: > Construct the minor number for the root device taking into account the > slice number passed in by the bootblocks. This means the kernel will > not use the compatability slice to obtain the root filesystem when > booting from a sliced disk. *WARNING* If your boot disk is sliced (has a partition table), and you have not upgraded /sbin/mount to the most recent version preceeding this change, you will have problems booting. This change means that if your current /etc/fstab looks like this: /dev/xd0a / ufs ... /dev/xd0s2e /usr ufs ... you need to update it to look like: /dev/xd0s2a / ufs ... /dev/xd0s2e /usr ufs ... Note that the root filesystem is now consistent with the others. If you are using a 'dedicated' disk, you will have entries like /dev/xd0a / ufs ... /dev/xd0e /usr ufs ... and you should *not* change. The recent update to /sbin/mount includes compatability support which will ease this transition. -- \\ 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 Mar 8 07:20:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04724 for freebsd-current-outgoing; Sun, 8 Mar 1998 07:20:15 -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 HAA04705 for ; Sun, 8 Mar 1998 07:20:06 -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 SAA07146; Sun, 8 Mar 1998 18:15:39 +0300 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 SAA01730; Sun, 8 Mar 1998 18:24:43 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199803081524.SAA01730@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: pb@fasterix.freenix.org (Pierre Beyssac) cc: freebsd-current@FreeBSD.ORG Subject: Re: something weird about CTM patch 3278 In-reply-to: Your message of "Sun, 08 Mar 1998 15:51:42 +0100." <19980308155141.YE46219@@> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 18:24:43 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pierre Beyssac wrote: > Is it just me, or is there something weird with CTM patch 3278 ? > It seems to delete a great deal of important stuff ? > > [...] This stuff obsoleted long time ago. I suspect, somebody started use -P with cvs update on the CTM generator. CTM is not very happy with it here, since I don't have most of these directories. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 07:36:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06393 for freebsd-current-outgoing; Sun, 8 Mar 1998 07:36:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06385 for ; Sun, 8 Mar 1998 07:36:36 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id QAA06008; Sun, 8 Mar 1998 16:32:10 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199803081532.QAA06008@ocean.campus.luth.se> Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c In-Reply-To: <199803081518.HAA10644@dingo.cdrom.com> from Mike Smith at "Mar 8, 98 07:18:50 am" To: mike@smith.net.au (Mike Smith) Date: Sun, 8 Mar 1998 16:32:10 +0100 (CET) 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 According to Mike Smith: > If your boot disk is sliced (has a partition table), and you have not > upgraded /sbin/mount to the most recent version preceeding this change, > you will have problems booting. > > This change means that if your current /etc/fstab looks like this: > > /dev/xd0a / ufs ... > /dev/xd0s2e /usr ufs ... > > you need to update it to look like: > > /dev/xd0s2a / ufs ... > /dev/xd0s2e /usr ufs ... Er... Excuse me for the maybe silly question, but WHY is this done? I mean... I run my disk split up between FreeBSD and Win95, and so there's really no ambigiousness. There's just one UFS slice. So not having to deal with the cumbersomeness of the "sX" part is nicer, and I went the other way, for shorter names: /dev/xd0a / ufs ... /dev/xd0e /usr ufs ... Also, on my other machine I have a SCSI disk for freebsd, and a IDE disk for Win95. Computer boots from the ide, and then I use booteasy there to boot from the SCSI disk. The SCSI disk is not "dangerously dedicated", but it's just one big BSD slice. So... will I need "sd0s1a" on that, or just "sd0a"? /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 08:23:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11371 for freebsd-current-outgoing; Sun, 8 Mar 1998 08:23:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11366 for ; Sun, 8 Mar 1998 08:23:01 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id KAA22623; Sun, 8 Mar 1998 10:21:30 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <19980308155141.YE46219@@> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 8 Mar 1998 10:14:34 -0600 To: pb@fasterix.freenix.org (Pierre Beyssac) From: Richard Wackerbarth Subject: Re: something weird about CTM patch 3278 Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:51 AM -0600 3/8/98, Pierre Beyssac wrote: >Is it just me, or is there something weird with CTM patch 3278 ? >It seems to delete a great deal of important stuff ? > >Just to name a few: > >ctm_rmail: ctm: > DR gnu/usr.bin/pr >ctm_rmail: ctm: > DR gnu/usr.bin/yppush >ctm_rmail: ctm: > DR lib/librpc >ctm_rmail: ctm: > DR sbin/comcontrol >ctm_rmail: ctm: > DR sbin/fdisk >ctm_rmail: ctm: > DR sbin/mount_devfs >ctm_rmail: ctm: > DR sbin/mount_fdesc >ctm_rmail: ctm: > DR sbin/mount_kernfs >ctm_rmail: ctm: > DR sbin/mount_lfs >ctm_rmail: ctm: > DR sbin/mount_msdos >ctm_rmail: ctm: > DR sbin/mount_procfs >ctm_rmail: ctm: > DR usr.bin/diff >ctm_rmail: ctm: > DR usr.bin/grep >ctm_rmail: ctm: > DR usr.bin/ld >ctm_rmail: ctm: > DR usr.bin/man >ctm_rmail: ctm: > DR usr.bin/patch >ctm_rmail: ctm: > DR usr.bin/uucp >ctm_rmail: ctm: > DR usr.bin/whatis >ctm_rmail: ctm: > DR usr.sbin/bind >ctm_rmail: ctm: > DR usr.sbin/bootpd >ctm_rmail: ctm: > DR usr.sbin/routed >ctm_rmail: ctm: > DR usr.sbin/sup >ctm_rmail: ctm: > DR usr.sbin/swapinfo >ctm_rmail: ctm: > DR usr.sbin/update You will find that those are empty directories. The "important part" of them was moved some time ago. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 08:23:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11422 for freebsd-current-outgoing; Sun, 8 Mar 1998 08:23:07 -0800 (PST) (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 IAA11350 for ; Sun, 8 Mar 1998 08:22:31 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id RAA10074 for current@FreeBSD.ORG; Sun, 8 Mar 1998 17:22:13 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id RAA06959; Sun, 8 Mar 1998 17:00:03 +0100 (CET) (envelope-from roberto) Message-ID: <19980308170003.A6941@keltia.freenix.fr> Date: Sun, 8 Mar 1998 17:00:03 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: page fault while in kernel mode (-current from this morning && softupdates) Mail-Followup-To: current@FreeBSD.ORG References: <19980308153508.12630@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <19980308153508.12630@klemm.gtn.com>; from Andreas Klemm on Sun, Mar 08, 1998 at 03:35:08PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4103 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Andreas Klemm: > -current's vm system. I already noticed, that some people seemed > to have trouble with enabling noatime. Please don't use async with softupdates, it serves no purpose than probably confusing softupdates... Using noatime is probably not necessary anymore with softupdates either. > /dev/ccd0c on /obj (asynchronous, local, noatime, soft-updates, writes: sync 2 async 0) > /dev/ccd1c on /news (local, noatime, soft-updates, writes: sync 2 async 0) > /dev/ccd2c on /proxy (local, noatime, soft-updates, writes: sync 2 async 31) > /dev/ccd3c on /home (local, writes: sync 133 async 68) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 09:05:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15075 for freebsd-current-outgoing; Sun, 8 Mar 1998 09:05:32 -0800 (PST) (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 JAA15062 for ; Sun, 8 Mar 1998 09:05:29 -0800 (PST) (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 RAA02825; Sun, 8 Mar 1998 17:05:23 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id SAA14455; Sun, 8 Mar 1998 18:05:22 +0100 (MET) Message-ID: <19980308180522.35587@follo.net> Date: Sun, 8 Mar 1998 18:05:22 +0100 From: Eivind Eklund To: Mikael Karpberg , Mike Smith Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c References: <199803081518.HAA10644@dingo.cdrom.com> <199803081532.QAA06008@ocean.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803081532.QAA06008@ocean.campus.luth.se>; from Mikael Karpberg on Sun, Mar 08, 1998 at 04:32:10PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 08, 1998 at 04:32:10PM +0100, Mikael Karpberg wrote: > According to Mike Smith: > > If your boot disk is sliced (has a partition table), and you have not > > upgraded /sbin/mount to the most recent version preceeding this change, > > you will have problems booting. > > > > This change means that if your current /etc/fstab looks like this: > > > > /dev/xd0a / ufs ... > > /dev/xd0s2e /usr ufs ... > > > > you need to update it to look like: > > > > /dev/xd0s2a / ufs ... > > /dev/xd0s2e /usr ufs ... > > Er... Excuse me for the maybe silly question, but WHY is this done? Consistency. Magic should _not_ happen underneath the partitioning scheme - partitioning is too important to make it more obscure than it have to be. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 09:05:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15133 for freebsd-current-outgoing; Sun, 8 Mar 1998 09:05:37 -0800 (PST) (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 JAA15104 for ; Sun, 8 Mar 1998 09:05:34 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id JAA01191 for ; Sun, 8 Mar 1998 09:05:28 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Sun, 8 Mar 1998 09:05:28 -0800 (PST) From: Manfred Antar To: current@FreeBSD.ORG Subject: new mount won't compile 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 cc -O2 -pipe -m486 -fno-strength-reduce -DROOTSLICE_HUNT -c /usr/src/sbin/mount/mount_ufs.c /usr/src/sbin/mount/mount_ufs.c: In function `mount_ufs': /usr/src/sbin/mount/mount_ufs.c:141: `unit' undeclared (first use this function) /usr/src/sbin/mount/mount_ufs.c:141: (Each undeclared identifier is reported only once /usr/src/sbin/mount/mount_ufs.c:141: for each function it appears in.) /usr/src/sbin/mount/mount_ufs.c:157: parse error before `{' /usr/src/sbin/mount/mount_ufs.c: At top level: /usr/src/sbin/mount/mount_ufs.c:180: parse error before `return' This is from this morning. 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 Mar 8 10:12:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20639 for freebsd-current-outgoing; Sun, 8 Mar 1998 10:12:26 -0800 (PST) (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 KAA20631; Sun, 8 Mar 1998 10:12:22 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id NAA00198; Sun, 8 Mar 1998 13:12:05 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803081812.NAA00198@dyson.iquest.net> Subject: Re: page fault while in kernel mode (-current from this morning && softupdates) In-Reply-To: <19980308153508.12630@klemm.gtn.com> from Andreas Klemm at "Mar 8, 98 03:35:08 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Sun, 8 Mar 1998 13:12:04 -0500 (EST) Cc: current@FreeBSD.ORG, dyson@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 Andreas Klemm said: > Hi ! > > I grabbed the newest -current and enabled Softtupdates. I don't > know, if this problem is more related to softupdates, SMP or to > -current's vm system. I already noticed, that some people seemed > to have trouble with enabling noatime. > I just committed a fix. -- 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 Mar 8 10:35:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22768 for freebsd-current-outgoing; Sun, 8 Mar 1998 10:35:11 -0800 (PST) (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 KAA22762 for ; Sun, 8 Mar 1998 10:35:08 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id MAA25873 for ; Sun, 8 Mar 1998 12:35:08 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id MAA17354; Sun, 8 Mar 1998 12:35:08 -0600 (CST) Message-ID: <19980308123508.00742@mcs.net> Date: Sun, 8 Mar 1998 12:35:08 -0600 From: Karl Denninger To: current@FreeBSD.ORG Subject: Softupdates? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Was this merged into the CVS tree or? I tried enabling it in a kernel config file and config bitched about not knowing what the option was. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 10:39:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23398 for freebsd-current-outgoing; Sun, 8 Mar 1998 10:39:56 -0800 (PST) (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 KAA23388 for ; Sun, 8 Mar 1998 10:39:48 -0800 (PST) (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 TAA00803 for ; Sun, 8 Mar 1998 19:44:03 +0100 (MET) Message-ID: <3502E68B.67684781@giovannelli.it> Date: Sun, 08 Mar 1998 19:42:19 +0100 From: Gianmarco Giovannelli X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: make world fails 980308 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> sbin/mount cc -nostdinc -O -pipe -DROOTSLICE_HUNT -I/usr/obj/usr/src/tmp/usr/include -c / usr/src/sbin/mount/mount.c cc -nostdinc -O -pipe -DROOTSLICE_HUNT -I/usr/obj/usr/src/tmp/usr/include -c / usr/src/sbin/mount/mount_ufs.c /usr/src/sbin/mount/mount_ufs.c: In function `mount_ufs': /usr/src/sbin/mount/mount_ufs.c:141: `unit' undeclared (first use this function) /usr/src/sbin/mount/mount_ufs.c:141: (Each undeclared identifier is reported onl y once /usr/src/sbin/mount/mount_ufs.c:141: for each function it appears in.) /usr/src/sbin/mount/mount_ufs.c:157: parse error before `{' /usr/src/sbin/mount/mount_ufs.c: At top level: /usr/src/sbin/mount/mount_ufs.c:180: parse error before `return' *** Error code 1 Stop. *** Error code 1 -- 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 Sun Mar 8 10:46:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24184 for freebsd-current-outgoing; Sun, 8 Mar 1998 10:46:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa4-17.ix.netcom.com [207.93.136.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24169 for ; Sun, 8 Mar 1998 10:46:00 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id KAA02194; Sun, 8 Mar 1998 10:45:47 -0800 (PST) (envelope-from tomdean) Date: Sun, 8 Mar 1998 10:45:47 -0800 (PST) Message-Id: <199803081845.KAA02194@ix.netcom.com> From: Thomas Dean To: current@FreeBSD.ORG In-reply-to: <199803081518.HAA10644@dingo.cdrom.com> (message from Mike Smith on Sun, 08 Mar 1998 07:18:50 -0800) Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does this mean that /dev will be cleaned in the future to remove the offending device names? Everything that I have tried, like disklabel accept /dev/sd1 and /dev/sd1s1c. disklabel gives (proper?) different information for different arguments. I have: /dev/sd1 /dev/sd1e /dev/sd1s1a /dev/sd1s1f /dev/sd1s4 /dev/sd1a /dev/sd1f /dev/sd1s1b /dev/sd1s1g /dev/sd1b /dev/sd1g /dev/sd1s1c /dev/sd1s1h /dev/sd1c /dev/sd1h /dev/sd1s1d /dev/sd1s2 /dev/sd1d /dev/sd1s1 /dev/sd1s1e /dev/sd1s3 If I only had sd1s[a-h] then it would be less confusing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 11:10:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25881 for freebsd-current-outgoing; Sun, 8 Mar 1998 11:10:28 -0800 (PST) (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 LAA25876 for ; Sun, 8 Mar 1998 11:10:27 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id NAA26934 for ; Sun, 8 Mar 1998 13:10:24 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id NAA17750; Sun, 8 Mar 1998 13:10:24 -0600 (CST) Message-ID: <19980308131024.00085@mcs.net> Date: Sun, 8 Mar 1998 13:10:24 -0600 From: Karl Denninger To: current@FreeBSD.ORG Subject: HJmmm... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm... OK, so I re-supped, and "cvs update"d the /usr/src/sys tree... Now Softupdates configs, but won't build (it fails during make depend with a missing file). Without it, I fail here: Codebase# make cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h ../../kern/kern_exit.c In file included from ../../kern/kern_exit.c:61: ../../sys/aio.h:84: field `aio_sigevent' has incomplete type *** Error code 1 Is this one of those "everything's a mess, wait a bit and try again" things? -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 11:45:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00227 for freebsd-current-outgoing; Sun, 8 Mar 1998 11:45:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00220; Sun, 8 Mar 1998 11:45:45 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id SAA08156; Sun, 8 Mar 1998 18:45:10 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.7) id SAA00696; Sun, 8 Mar 1998 18:31:27 +0100 (CET) (envelope-from andreas) Message-ID: <19980308183127.63646@klemm.gtn.com> Date: Sun, 8 Mar 1998 18:31:27 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Cc: dyson@FreeBSD.ORG Subject: Re: page fault while in kernel mode (-current from this morning && softupdates) References: <19980308153508.12630@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980308153508.12630@klemm.gtn.com>; from Andreas Klemm on Sun, Mar 08, 1998 at 03:35:08PM +0100 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here what DDB told me: > > Fatal trap 12: page fault while in kernel mode > mp_lock=00000002 cpuip=0 lapic.id=01000000 > fault virtual address = 0xf1349ff8 > Supervisor read page not present > ... > Current process = 306 (XF86_SVGA) > kernel: type 12 trap, code=0 > .... > Stopped at _pmap_remove_all+0x10d: movel 0x8(%esi), %ebr > _pmap_remove_all > _pmap_page_protect > _vmobject_terminate This bite me again when leaving X11 with CTRL+ALT+BS And I got another one: panic vm_fault: fault on nofault entry, addr: f2d93000 mp_lock = 01000002 cpuid=1 lapic.id = 00000000 Debugger("panic") Stopped at _Debugger+0x35: movb $0, _in_Debugger.94 _Debugger _panic _vm_fault _trap_pfault _trap calltrap() ---trap0xc... _generic_bcopy _softdep_setup_allocindir_page _ffs_balloc _ffs_write _vn_write _write _syscall _xsyscall ---syscall -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 13:25:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14485 for freebsd-current-outgoing; Sun, 8 Mar 1998 13:25:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14440 for ; Sun, 8 Mar 1998 13:25:19 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id WAA02709 for current@FreeBSD.ORG; Sun, 8 Mar 1998 22:15:15 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.7) id WAA27131; Sun, 8 Mar 1998 22:01:17 +0100 (CET) (envelope-from andreas) Message-ID: <19980308220117.19484@klemm.gtn.com> Date: Sun, 8 Mar 1998 22:01:17 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: make world fails (mount) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> sbin/mount cc -nostdinc -pipe -O2 -DROOTSLICE_HUNT -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/mount/mount_ufs.c /usr/src/sbin/mount/mount_ufs.c: In function `mount_ufs': /usr/src/sbin/mount/mount_ufs.c:141: `unit' undeclared (first use this function) /usr/src/sbin/mount/mount_ufs.c:141: (Each undeclared identifier is reported only once /usr/src/sbin/mount/mount_ufs.c:141: for each function it appears in.) /usr/src/sbin/mount/mount_ufs.c:157: parse error before `{' /usr/src/sbin/mount/mount_ufs.c: At top level: /usr/src/sbin/mount/mount_ufs.c:180: parse error before `return' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 13:49:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16726 for freebsd-current-outgoing; Sun, 8 Mar 1998 13:49:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16719 for ; Sun, 8 Mar 1998 13:49:36 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id WAA06837; Sun, 8 Mar 1998 22:45:11 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.7) id WAA27487; Sun, 8 Mar 1998 22:15:15 +0100 (CET) (envelope-from andreas) Message-ID: <19980308221515.38170@klemm.gtn.com> Date: Sun, 8 Mar 1998 22:15:15 +0100 From: Andreas Klemm To: Karl Denninger , current@FreeBSD.ORG Subject: Re: HJmmm... References: <19980308131024.00085@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980308131024.00085@mcs.net>; from Karl Denninger on Sun, Mar 08, 1998 at 01:10:24PM -0600 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 08, 1998 at 01:10:24PM -0600, Karl Denninger wrote: > > Hmmm... OK, so I re-supped, and "cvs update"d the /usr/src/sys tree... > > Now Softupdates configs, but won't build (it fails during make depend with a > missing file). > > Without it, I fail here: > Codebase# make > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wuninitialized -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include > opt_global.h > ../../kern/kern_exit.c > In file included from ../../kern/kern_exit.c:61: > ../../sys/aio.h:84: field `aio_sigevent' has incomplete type > *** Error code 1 > > Is this one of those "everything's a mess, wait a bit and try again" things? Read Julians Home Page http://www.freebsd.org/~julian It's because of Kirk's copyright, you have to fetch the two missing files by hand ... And be careful ... ;-) Andreas /// -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 14:36:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20919 for freebsd-current-outgoing; Sun, 8 Mar 1998 14:36:07 -0800 (PST) (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 OAA20883 for ; Sun, 8 Mar 1998 14:35:45 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id XAA28417 for current@FreeBSD.ORG; Sun, 8 Mar 1998 23:35:28 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id XAA09485; Sun, 8 Mar 1998 23:02:23 +0100 (CET) (envelope-from roberto) Message-ID: <19980308230222.A9458@keltia.freenix.fr> Date: Sun, 8 Mar 1998 23:02:22 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: page fault while in kernel mode (-current from this morning && softupdates) Mail-Followup-To: current@FreeBSD.ORG References: <19980308153508.12630@klemm.gtn.com> <19980308183127.63646@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <19980308183127.63646@klemm.gtn.com>; from Andreas Klemm on Sun, Mar 08, 1998 at 06:31:27PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4121 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Andreas Klemm: > And I got another one: > > panic vm_fault: fault on nofault entry, addr: f2d93000 [...] > _generic_bcopy > _softdep_setup_allocindir_page Welcome to the club :-) This is the same panic as Amancia and I (and now you) are seeing. I can't find a pattern in this :-( It happens for me in two cases: - rnews batch processing, - procmail delivering mail into mailboxes. The funny part is that I can "make world", "cvs update" and "ctm" without problem and these stress the filesystems quite a bit compared to procmail... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 14:36:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21020 for freebsd-current-outgoing; Sun, 8 Mar 1998 14:36:48 -0800 (PST) (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 OAA20986 for ; Sun, 8 Mar 1998 14:36:27 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id XAA28431 for current@FreeBSD.ORG; Sun, 8 Mar 1998 23:36:11 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id XAA09496; Sun, 8 Mar 1998 23:03:17 +0100 (CET) (envelope-from roberto) Message-ID: <19980308230317.B9458@keltia.freenix.fr> Date: Sun, 8 Mar 1998 23:03:17 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Softupdates? Mail-Followup-To: current@FreeBSD.ORG References: <19980308123508.00742@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <19980308123508.00742@mcs.net>; from Karl Denninger on Sun, Mar 08, 1998 at 12:35:08PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4121 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Karl Denninger: > Was this merged into the CVS tree or? Yes. > I tried enabling it in a kernel config file and config bitched about not > knowing what the option was. Check /sys/conf/files. You should find two entries in there: ufs/ffs/ffs_softdep_stub.c optional ffs ufs/ffs/ffs_softdep.c optional softupdates -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 14:58:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24715 for freebsd-current-outgoing; Sun, 8 Mar 1998 14:58:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mhub3.tc.umn.edu (0@mhub3.tc.umn.edu [128.101.131.53]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA24681 for ; Sun, 8 Mar 1998 14:57:56 -0800 (PST) (envelope-from adkin003@tc.umn.edu) Received: from pub-19-c-219.dialup.umn.edu by mhub3.tc.umn.edu; Sun, 8 Mar 98 16:57:46 -0600 Date: Sun, 8 Mar 1998 16:54:45 -0600 (CST) From: dave adkins X-Sender: adkin003@samthedog To: current@FreeBSD.ORG Subject: ext2fs broken from latest file system changes 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 It seems that the latest changes that incorporated the softupdates stuff has broken ext2fs. There were a few places where SI_MOUNTEDON remained. Removing them and replacing them with (p)->v_specmountpoint = mp or NULL depending on whether we're mounting or unmounting. With this change the mount seems to work OK, but when ext2_sync runs it faults when VTOI() returns a NULL inode ptr. dave adkins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 15:04:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25620 for freebsd-current-outgoing; Sun, 8 Mar 1998 15:04:51 -0800 (PST) (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 PAA25611 for ; Sun, 8 Mar 1998 15:04:47 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id RAA24781; Sun, 8 Mar 1998 17:54:13 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Sun, 8 Mar 1998 17:54:12 -0500 (EST) From: "Alok K. Dhir" To: julian@whistle.com cc: current@FreeBSD.ORG Subject: Soft updates 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 Question: Can softupdates be used on a ccd striped partition? Thanks! -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ R7-003, ITSMC 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 Mar 8 15:13:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27259 for freebsd-current-outgoing; Sun, 8 Mar 1998 15:13:39 -0800 (PST) (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 PAA27254 for ; Sun, 8 Mar 1998 15:13:37 -0800 (PST) (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.6.9) with ESMTP id PAA23724; Sun, 8 Mar 1998 15:12:19 -0800 (PST) To: Mikael Karpberg cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c In-reply-to: Your message of "Sun, 08 Mar 1998 16:32:10 +0100." <199803081532.QAA06008@ocean.campus.luth.se> Date: Sun, 08 Mar 1998 15:12:19 -0800 Message-ID: <23720.889398739@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Er... Excuse me for the maybe silly question, but WHY is this done? It's inconsistent to have every partition *other* than the root partition use the compatability slice, that's why, and there's nasty code in sysinstall to deliberately do the non-obvious thing for root partitions specifically because you can't boot off a correctly specified root partition. It's a win and there's nothing "cumbersome" about using the proper name for a slice, the use of the compatability naming was always a hack to work around limitations elsewhere. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 15:19:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27987 for freebsd-current-outgoing; Sun, 8 Mar 1998 15:19:50 -0800 (PST) (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 PAA27973 for ; Sun, 8 Mar 1998 15:19:46 -0800 (PST) (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 AAA13411; Mon, 9 Mar 1998 00:19:10 +0100 (CET) To: Ollivier Robert cc: current@FreeBSD.ORG Subject: Re: page fault while in kernel mode (-current from this morning && softupdates) In-reply-to: Your message of "Sun, 08 Mar 1998 23:02:22 +0100." <19980308230222.A9458@keltia.freenix.fr> Date: Mon, 09 Mar 1998 00:19:08 +0100 Message-ID: <13409.889399148@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Considering that it mentions "allocindir" it would be obvious that it involves files bigger than what we have in our source-tree. That should also be the avenue to reproduction I think... In message <19980308230222.A9458@keltia.freenix.fr>, Ollivier Robert writes: >According to Andreas Klemm: >> And I got another one: >> >> panic vm_fault: fault on nofault entry, addr: f2d93000 >[...] >> _generic_bcopy >> _softdep_setup_allocindir_page > >Welcome to the club :-) > >This is the same panic as Amancia and I (and now you) are seeing. I can't >find a pattern in this :-( > >It happens for me in two cases: >- rnews batch processing, >- procmail delivering mail into mailboxes. > >The funny part is that I can "make world", "cvs update" and "ctm" without >problem and these stress the filesystems quite a bit compared to >procmail... >-- >Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.f >r >FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "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 Mar 8 15:25:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28835 for freebsd-current-outgoing; Sun, 8 Mar 1998 15:25:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28830 for ; Sun, 8 Mar 1998 15:25:49 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.8) with ESMTP id RAA04184; Sun, 8 Mar 1998 17:25:37 -0600 (CST) (envelope-from ccsanady@friley585.res.iastate.edu) Message-Id: <199803082325.RAA04184@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: "Alok K. Dhir" cc: julian@whistle.com, current@FreeBSD.ORG Subject: Re: Soft updates In-reply-to: Your message of "Sun, 08 Mar 1998 17:54:12 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 17:25:36 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Question: Can softupdates be used on a ccd striped partition? > Yes, there should no longer be any problems with them. Although this doesn't effect things, it seems that the b_dep list is still not being initialized in the ccdbuf. Was this going to be added? Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 15:31:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29842 for freebsd-current-outgoing; Sun, 8 Mar 1998 15:31:50 -0800 (PST) (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 PAA29836 for ; Sun, 8 Mar 1998 15:31:48 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id QAA23781; Sun, 8 Mar 1998 16:31:45 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd023772; Sun Mar 8 16:31:40 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id QAA08328; Sun, 8 Mar 1998 16:31:19 -0700 (MST) From: Terry Lambert Message-Id: <199803082331.QAA08328@usr08.primenet.com> Subject: Re: vnode_pager: *** WARNING *** stale FS code in system To: dima@tejblum.dnttm.rssi.ru (Dmitrij Tejblum) Date: Sun, 8 Mar 1998 23:31:19 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199803072354.CAA02807@tejblum.dnttm.rssi.ru> from "Dmitrij Tejblum" at Mar 8, 98 02:54:05 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 > > The reason I went the way I did was that putting the vnode_pager.c > > code in the defaultops vector does nothing toward making the code > > in vnode_pager.c _go away_, which is the eventual goal. > > Your changes do same nothing toward this goal. Everyone can insert a > function into a vnops table. It is trivial. Almost nobody can write a > real getpages or putpages routine. For example, you failed even to > write a readonly cd9660_putpages, while it would be, apparently, > trivial. (I suspect, simple 'return (VM_PAGER_BAD);' would do a right > thing.) You also failed to mention this problem in your standard comment. > So, when real implementation for getpages and putpages for all these > filesystem will written? Most assuredly, at some time *after* a skeleton versions of FS specific getpages/putpages have been written. Organizationally, the patches I gave *do* move toward that goal. If you insist, I can duplicate the generic code into the FS's themselves immediately, and remove it from the generic location. I don't see this action as being useful. What I *do* see as the next logical progression is to move the code into *one* FS, and make it work. The reason this is more logical is that it provides a staged reference to the generic routines, so that we can tell the difference between an FS which has been migrated, and one that still needs work. It also gives other people the chance to work on FS specific code: it broadens the potential for participation, even though I suspect I know the one or two people who might help already -- at least the potential is there. > Filesystem-specific getpages/putpages possible since end of 1995. You > saved a filesystem writer from writing 7 obvious lines of each > implementations (even these lines contain style bugs, so actual number > is slightly less). Is this the big win? Codewise, no. That's why I would have preferred to leave the other FS's issuing the warning until such time as I could fix the code; after all, I am a purist. But pragmatically, it makes the desired organization obvious (instead of clouding it unnecessarily), and the patches were necessary, given the stabilization requirements now in force. I would cetrainly welcome your assitance in unstubbing the local media getpages/putpages, if you were willing to give it. This would resolve your implementation issues, without stepping on my organizational issues. > > FS's which > > can act as backing store need to have FS specific backing store > > management, > > A problem is that every leaf filesystem with 'regular' files may be > asked to act as backing store. For example, try > cmp /proc/1/map /proc/curproc/map Which calls mmap, and invokes a vnode pager, because it things these are normal files. mmap() vm_mmap() vm_pager_allocate() pagertab[ OBJT_VNODE]->pgo_alloc > After you 'fix' getpages on procfs with your usual method, you will > notice that procfs does not implement VOP_STRATEGY. (and that pfs_type > is not a string, like procfs_print thinks). But why something ever > try to call STRATEGY on procfs? Because procfs implement BMAP in some > 'specific' way. This serves as a little example of usefulness of some > filesystem-specific code. Clearly you misjudge how I would fix this problem. This code is, obviously, in error. The vm_mmap() should probably dereference vp->v_mount->mnt_kern_flag looking for MNT_PSEUDO, and if present, use a seperate pseduo-local-media pager that's not the same thing (ie: the pages in procfs are backed by kernel memory, not physical storage -- the vnode_pager is anppropriate for them). The quick hack in this case is to either treat the procfs vnodes as something other than normal vnodes (avoiding the cmp code triggering the mmap()) or simply to fail the mmap (since the data represents derived data, in any case). One problem here is that cmp (stupidly) does not fall back to c_special() in c_regular() in the case that the mmap() fails. This is a bug in cmp. > > for a large variety of reasons (I can enumerate these > > reasons again, if you need me to). > > Well, actually I don't know any reasons for it, other than reference to > John Dyson's authority and complexity of the generic code. So it would > be interesting. But it is outside of scope of this discussion. Then casting aspersions on my reasoning by implying that my only validation is lodged in "appeal to authority" is probably *also* outside the scope of this discussion, don't you think? > > A secondary reason is that it means I have to make special code in > > stacking FS's in order to be able to access the bypass (which I think > > should be placed in the defaultops vector instead). > > I am not sure if I can parse this. Anyway, I claim that my way has > exactly same results as your in this aspect. In terms of eventual results, yes. > From point of view of a > stacking layer, the filesystem below provide a getpages/putpages > implementation, and this is all that you want. Actually, I want to use the local media FS's pager. The difference here is that if I have a crypto FS stacked on top of a transaction FS stacked on top of a ACL FS stacked on top of a quota FS on top of an FFS FS, when I try to getpages on the crypto FS, it should try to getpages on the underlying FFS. In your suggested implementation, I can't collapse the call graph because in the stacking FS's will each have a getpages/putpages to access the bypass explicitly, instead of accessing it implicitly. > Also you want that you > will get a warning if your stacking layer does not bypass or implement > the getpages/putpages correctly. Then make vop_nogetpages and > vop_noputpages, which will print the warning and the bad vnode and > return VM_PAGER_BAD (which is at least a correct getpages/putpages return > value, unlike EOPNOTSUPP), and put vop_stdgetpages and vop_stdputpages > to vnops table of affected local medial file systems. Here's my preferred soloution, since it will pacify you as well: make the warning non-fatal *for now*; ie: ========================================================================= Index: vnode_pager.c =================================================================== RCS file: /b/cvstree/ncvs/src/sys/vm/vnode_pager.c,v retrieving revision 1.87 diff -c -r1.87 vnode_pager.c *** 1.87 1998/02/26 06:39:58 --- vnode_pager.c 1998/03/08 23:22:24 *************** *** 531,545 **** { int rtval; struct vnode *vp; vp = object->handle; /* * XXX temporary diagnostic message to help track stale FS code, * Returning EOPNOTSUPP from here may make things unhappy. */ ! rtval = VOP_GETPAGES(vp, m, count*PAGE_SIZE, reqpage, 0); ! if (rtval == EOPNOTSUPP) ! printf("vnode_pager: *** WARNING *** stale FS code in system.\n"); return rtval; } --- 531,548 ---- { int rtval; struct vnode *vp; + int bytes = count * PAGE_SIZE; vp = object->handle; /* * XXX temporary diagnostic message to help track stale FS code, * Returning EOPNOTSUPP from here may make things unhappy. */ ! rtval = VOP_GETPAGES(vp, m, bytes, reqpage, 0); ! if (rtval == EOPNOTSUPP) { ! printf("vnode_pager: *** WARNING *** stale FS getpages\n"); ! rtval = vnode_pager_generic_getpages( vp, m, bytes, reqpage); ! } return rtval; } *************** *** 803,811 **** { int rtval; struct vnode *vp; vp = object->handle; ! return VOP_PUTPAGES(vp, m, count*PAGE_SIZE, sync, rtvals, 0); } --- 806,820 ---- { int rtval; struct vnode *vp; + int bytes = count * PAGE_SIZE; vp = object->handle; ! rtval = VOP_PUTPAGES(vp, m, bytes, sync, rtvals, 0); ! if (rtval == EOPNOTSUPP) { ! printf("vnode_pager: *** WARNING *** stale FS putpages\n"); ! rtval = vnode_pager_generic_putpages( vp, m, bytes, sync, rtvals); ! } ! return rtval; } ========================================================================= > > A tertiary reason is that if the code is in the defaultops vector, > > I can't know when it becomes safe to remove from vnode_pager.c > > and the defaultops vector. There's no way to measure usage of > > the defaultops code (that's kind of the point, really). > > OK, don't put it to defaultops vector, put vop_stdgetpages and > vop_stdputpages to vnops table of every affected filesystem. I suggest > it in every mail on this topic :-). Now you are basically griping only about naming. The problem with calling it standard is that *it's not supposed to be the standard, correct way of doing things*. The blunt fact is that the way it was being done is screwed up, and *something* needs to be done to unscrew it, and done in such a way as it doesn't screw the FS stacking at the same time. > One may say that my complains are more about decorative issues that > about real programming issues. Sorry. It is because all discussing > changes actually more decorative than real code. And as decorative, > they are IMHO bad. Also, unfortunately, most points in this discussion > were repeated several times... I don't know how many times I should have to repeat this, but the code *should not be in vnode_pager.c* and was, in fact *designed to not be in vnode_pager.c*. There is a discrepancy between design and implementation that we need to reconcile. If this counts as "decorative" in your book, so be it. I think our disagreement hinges more on order and granularity of implementation of this change than it does on whether or not the goal is reasonable. I think the goal is reasonable. If you agree, and don't like the granularity of implementation, then start implementing. I could use the help. Regards, 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 Mar 8 15:35:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00490 for freebsd-current-outgoing; Sun, 8 Mar 1998 15:35:42 -0800 (PST) (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 PAA00485 for ; Sun, 8 Mar 1998 15:35:40 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id PAA26490 for ; Sun, 8 Mar 1998 15:35:38 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Sun, 8 Mar 1998 15:35:37 -0800 (PST) From: Manfred Antar To: current@FreeBSD.ORG Subject: current kernel won't build 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 cc -c -O2 -pipe -m486 -fno-strength-reduce -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h ../../kern/kern_exit.c In file included from ../../kern/kern_exit.c:61: ../../sys/aio.h:84: field `aio_sigevent' has incomplete type *** Error code 1 This is the same with or without Softupdates ============================== || 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 Mar 8 15:44:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02172 for freebsd-current-outgoing; Sun, 8 Mar 1998 15:44:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf27.cruzers.com [205.215.232.27]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA02163 for ; Sun, 8 Mar 1998 15:44:25 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 610 invoked by uid 100); 8 Mar 1998 23:45:41 -0000 Message-ID: <19980308154538.A594@top.worldcontrol.com> Date: Sun, 8 Mar 1998 15:45:38 -0800 To: freebsd-current@FreeBSD.ORG Subject: ../../sys/aio.h:84: field `aio_sigevent' has incomplete type Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.7i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In a kernel build from sources cvsup'ed a few minutes ago (Sun 8 Mar 15:43:49 PST 1998). cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h ../../kern/kern_subr.c --- kern_exit.o --- In file included from ../../kern/kern_exit.c:61: ../../sys/aio.h:84: field `aio_sigevent' has incomplete type *** Error code 1 -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 16:03:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05217 for freebsd-current-outgoing; Sun, 8 Mar 1998 16:03:54 -0800 (PST) (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 QAA05207 for ; Sun, 8 Mar 1998 16:03:51 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id PAA24491; Sun, 8 Mar 1998 15:06:21 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803082306.PAA24491@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ollivier Robert cc: current@FreeBSD.ORG Subject: Re: page fault while in kernel mode (-current from this morning && softupdates) In-reply-to: Your message of "Sun, 08 Mar 1998 23:02:22 +0100." <19980308230222.A9458@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 15:06:21 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The funny part is that I can "make world", "cvs update" and "ctm" without > problem and these stress the filesystems quite a bit compared to > procmail... Well, try removing a big directory while doing a make world . I usually just do make world and routinely just untar and remove a large directory -- a few thousand files like X. Usually, I can crash the system in the first hour or so. There are other problems which Julian and Dyson are well aware of and they are working on it. About the posted panic, we need to evaluate why the system is generating a panic when the buffer allocation scheme used in soft update is supposed to return a valid buffer: In /sys/ufs/ffs/ffs_softdep.c: static void setup_allocindir_phase2(bp, ip, aip) .... MALLOC(newindirdep, struct indirdep *, sizeof(struct indirdep), M_INDIRDEP, M_WAITOK); newindirdep->ir_list.wk_type = D_INDIRDEP; newindirdep->ir_state = ATTACHED; LIST_INIT(&newindirdep->ir_deplisthd); LIST_INIT(&newindirdep->ir_donehd); newindirdep->ir_saveddata = (ufs_daddr_t *)bp->b_data; newindirdep->ir_savebp = getblk(ip->i_devvp, bp->b_blkno, bp->b_bcount, 0, 0); bcopy((caddr_t)newindirdep->ir_saveddata, newindirdep->ir_savebp->b_data, bp->b_bcount); Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 16:28:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07895 for freebsd-current-outgoing; Sun, 8 Mar 1998 16:28:40 -0800 (PST) (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 QAA07889 for ; Sun, 8 Mar 1998 16:28:38 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id SAA03778; Sun, 8 Mar 1998 18:28:37 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id SAA21915; Sun, 8 Mar 1998 18:28:36 -0600 (CST) Message-ID: <19980308182836.24418@mcs.net> Date: Sun, 8 Mar 1998 18:28:36 -0600 From: Karl Denninger To: Ollivier Robert Cc: current@FreeBSD.ORG Subject: Re: Softupdates? References: <19980308123508.00742@mcs.net> <19980308230317.B9458@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980308230317.B9458@keltia.freenix.fr>; from Ollivier Robert on Sun, Mar 08, 1998 at 11:03:17PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 08, 1998 at 11:03:17PM +0100, Ollivier Robert wrote: > According to Karl Denninger: > > Was this merged into the CVS tree or? > > Yes. > > > I tried enabling it in a kernel config file and config bitched about not > > knowing what the option was. > > Check /sys/conf/files. You should find two entries in there: > > ufs/ffs/ffs_softdep_stub.c optional ffs > ufs/ffs/ffs_softdep.c optional softupdates Those are present. The file "ffs_softdep.c" is missing. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 16:30:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08395 for freebsd-current-outgoing; Sun, 8 Mar 1998 16:30:50 -0800 (PST) (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 QAA08389 for ; Sun, 8 Mar 1998 16:30:48 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id SAA03872; Sun, 8 Mar 1998 18:30:48 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id SAA21952; Sun, 8 Mar 1998 18:30:48 -0600 (CST) Message-ID: <19980308183048.54636@mcs.net> Date: Sun, 8 Mar 1998 18:30:48 -0600 From: Karl Denninger To: Manfred Antar Cc: current@FreeBSD.ORG Subject: Re: current kernel won't build References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Manfred Antar on Sun, Mar 08, 1998 at 03:35:37PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Same problem I am seeing here. -- Karl On Sun, Mar 08, 1998 at 03:35:37PM -0800, Manfred Antar wrote: > cc -c -O2 -pipe -m486 -fno-strength-reduce -Wreturn-type -Wcomment > -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc > -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h > ../../kern/kern_exit.c > In file included from ../../kern/kern_exit.c:61: > ../../sys/aio.h:84: field `aio_sigevent' has incomplete type > *** Error code 1 > > This is the same with or without Softupdates > > > ============================== > || 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 16:51:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10382 for freebsd-current-outgoing; Sun, 8 Mar 1998 16:51:49 -0800 (PST) (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 QAA10377 for ; Sun, 8 Mar 1998 16:51:45 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 3046 invoked from network); 9 Mar 1998 00:51:27 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 9 Mar 1998 00:51:27 -0000 Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id QAA00635 for freebsd-current@freebsd.org; Sun, 8 Mar 1998 16:51:43 -0800 (PST) (envelope-from scottm) Date: Sun, 8 Mar 1998 16:51:43 -0800 (PST) From: Scott Michel Message-Id: <199803090051.QAA00635@mordred.cs.ucla.edu> To: freebsd-current@FreeBSD.ORG Subject: libg++ changed? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is really cool: ld.so failed: Undefined symbol "__vt$8stdiobuf" in vat:/usr/lib/libstdc++.so.2.0 I haven't been following all of the commit messages, but when did this break? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 17:04:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11897 for freebsd-current-outgoing; Sun, 8 Mar 1998 17:04:45 -0800 (PST) (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 RAA11891 for ; Sun, 8 Mar 1998 17:04:43 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id TAA04925 for ; Sun, 8 Mar 1998 19:04:44 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id TAA22452; Sun, 8 Mar 1998 19:04:43 -0600 (CST) Message-ID: <19980308190443.54008@mcs.net> Date: Sun, 8 Mar 1998 19:04:43 -0600 From: Karl Denninger To: current@FreeBSD.ORG Subject: One traded for another Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Someone committed a fix to aio.h.... Well, kinda a fix :-) I get this now: -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitializ ed -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h ../../kern/kern_exit.c In file included from ../../kern/kern_exit.c:61: ../../sys/aio.h:47: parse error before `SIGEV_NONE' ../../sys/aio.h:100: parse error before `}' ../../sys/aio.h:113: field `_aiocb_private' has incomplete type *** Error code 1 Uh, guys, in line 47 the "#" is missing before the "define" :-) You might want to commit another fix :-) -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 17:11:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12902 for freebsd-current-outgoing; Sun, 8 Mar 1998 17:11:16 -0800 (PST) (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 RAA12891 for ; Sun, 8 Mar 1998 17:11:13 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id TAA05091 for ; Sun, 8 Mar 1998 19:11:11 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id TAA22604; Sun, 8 Mar 1998 19:11:11 -0600 (CST) Message-ID: <19980308191111.08309@mcs.net> Date: Sun, 8 Mar 1998 19:11:11 -0600 From: Karl Denninger To: current@FreeBSD.ORG Subject: Someone needs to re-develop "Softupdates" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just read Julian's page. What is in the Copyright file, and how Kirk "interprets" it, are two completely different things. According to the copyright, using the code as long as it is not resold as part of a packaged product is perfectly fine. According to Kirk, if someone wants to use it in a "Production ISP System" (to cite one of his examples) they need to negotiate a license from him. To use a single word Kirk: NO. Your copyright is clear about resale of the code (ie: as part of an embedded system used for something). However, it says NOTHING about someone wanting to use the code internally for their own use being restricted based on what they intend to do *INTERNALLY* with it. That's nothing short of incredible, if you ask me. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 17:20:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14147 for freebsd-current-outgoing; Sun, 8 Mar 1998 17:20:34 -0800 (PST) (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 RAA14140 for ; Sun, 8 Mar 1998 17:20:32 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA15588; Sun, 8 Mar 1998 17:12:13 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd015583; Sun Mar 8 17:12:06 1998 Date: Sun, 8 Mar 1998 17:07:49 -0800 (PST) From: Julian Elischer To: Chris Csanady cc: "Alok K. Dhir" , current@FreeBSD.ORG Subject: Re: Soft updates In-Reply-To: <199803082325.RAA04184@friley585.res.iastate.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 I will add that patch. julian On Sun, 8 Mar 1998, Chris Csanady wrote: > > > > >Question: Can softupdates be used on a ccd striped partition? > > > > Yes, there should no longer be any problems with them. Although this doesn't > effect things, it seems that the b_dep list is still not being initialized > in the ccdbuf. Was this going to be added? > > Chris > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 17:33:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15494 for freebsd-current-outgoing; Sun, 8 Mar 1998 17:33:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15477 for ; Sun, 8 Mar 1998 17:33:15 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id SAA04697 for ; Sun, 8 Mar 1998 18:33:14 -0700 (MST) Message-Id: <199803090133.SAA04697@pluto.plutotech.com> Date: Sun, 08 Mar 1998 18:30:05 -0700 From: "Justin T. Gibbs" Subject: New CAM snapshot available. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: undisclosed-recipients:; ------- Blind-Carbon-Copy X-Mailer: exmh version 2.0.1 12/23/97 To: scsi@FreeBSD.org Subject: New CAM snapshot available. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 18:30:05 -0700 From: "Justin T. Gibbs" The 980308 CAM snapshot is now available at the following locations: ftp.FreeBSD.org:/pub/FreeBSD/cam ftp.kdm.org:/pub/FreeBSD/cam The README available at these sites is reproduced below. As always, your comments about CAM are greatly appreciated. Thanks, Justin Common Access Method SCSI Layer "What is CAM? and why would I want it?" CAM is an ANSI ratified spec that defines a software interface for talking to SCSI and ATAPI devices. This new SCSI layer for FreeBSD is not strictly CAM compliant, but follows many of the precepts of CAM. More importantly, this work addresses many of the short comings of the previous SCSI layer and should provide better performance, reliability, and ease the task of adding support for new controllers. "Who is working on CAM?" Justin T. Gibbs Kenneth D. Merry General discussion about CAM usually occurs on the FreeBSD-scsi@FreeBSD.org list. "What hardware is supported?" Controller Drivers: Aic7xxx driver (ahc): This driver supports all of the devices the original FreeBSD driver supports but with the following new features: Support for aic7890/91/95 based controllers. ULTRA2 speeds have not yet been tested. I'd be happy to do so if someone wants to send me a drive. 8-) The driver now uses the secondary DMA FIFO to DMA SCBs and SG lists on controllers that support it. Although some prefetching is performed now, there is still much room for improvement. Autotermination support for all cards that support it. SCB paging that allows up to 255 SCBs to be active on aic7770, aic7850, and aic7860 cards. Bug fixes to the multi-lun support. The beginnings of a target mode implementation. AdvanSys Driver (adv): This driver supports the entire line of AdvanSys narrow channel devices. Tagged queuing is also supported. NCR Driver (ncr): This driver supports all of the devices the original driver supports, but does not yet have truely robust error recovery features implemented. Supported Peripherals: Direct Access driver (da): 512 byte sectored disk drivers. Support for other sector sizes is planned, but further investigation on the "right" approach for this is needed. It probably belongs in the disk-slice code. CDROM driver (cd): This driver should support everything the old driver did. Sequential Access driver (sa): This driver should support most "newer" tape drives. It does not have the ability to change either the density or compression settings yet. This is the "greenest" component in CAM currently, having only been tested on an Archive Python. Look for additional enhancements to this driver in the near term. "What versions of FreeBSD can I use CAM with?" CAM is developed under FreeBSD-current so most patch sets apply to a "current" of the day the snapshot was released. The patches will likely apply to source trees synched near that date, but there are no guarantees. As soon as the merging activity for 2.2.6 into -stable dies down, we plan on releasing a version of CAM for 2.2. CAM greatly increases the stability of the SCSI system and is currently being run on Wcarchive (a 2.2 environment). If your environment does not require device support that CAM has yet to offer and you are encountering SCSI related instabilities, you may want to give it a try when the next 2.2 patch set becomes available. "How reliable is it?" Although "work in progress", this code has been through over six months of testing here at Pluto in a RAID application. We feel pretty good about the stability of the code. If you do have the facilities to experiment (you must be running current), please do. We welcome your feedback especially about the performance and reliability of the new system. "How do I install it?" BACKUP YOUR OLD SRC TREE AND KERNEL!!!! cp /kernel /kernel.works Get the code: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/cam-980308.diffs.gz On a FreeBSD-current system from ~980308 cd /usr/src zcat cam-980308.diffs.gz | patch -p1 cd usr.sbin/config make clean all install cd ../../sys/i386/conf vi MYKERNEL Comment out all unsupported SCSI devices, and substitute "da" for "sd" and "sa" for "st". Look in LINT or GENERIC for examples. config MYKERNEL cd ../../MYKERNEL make all make install "What are the features of CAM?" - Round-robin, per priority level scheduling of devices and their resources. - I/O Completion, error recovery, and processing queued I/O is performed in a separate software interrupt handler. The old system had the potential of blocking out hardware interrupts for lengthy periods as much of this processing occurred as the result of a call from the controller's interrupt handler. - The generic SCSI layer now understands tagged I/O and exports this functionality to the peripheral drivers. This allows drivers like the "direct access" driver to perform ordered tagged transactions for meta-data writes. Async, ordered, meta-data writes are now enabled in vfs_bio.c - The "direct access" driver prevents "tag starvation" from occurring by guaranteeing that at least one write in every 5 second period to a tagged queuing device has an ordered tag. This removes the need for individual controller drivers to worry about this problem. - Complete and controller independent handling of the "QUEUE FULL" and "BUSY" status codes. The number of tags that are queued to a device are dynamically adjusted by the generic layer. - Interrupt driven sub-device probing. At boot time, all buses are probed in parallel yielding a much faster boot. As probing occurs after all interrupt and timer services are available, no additional (and often error prone) "polling" code is needed in each controller driver. - Better error recovery. When an error occurs, the queue of transactions to the erring device is "frozen", full status is reported back to the peripheral driver, and the peripheral driver can recover the device without perturbing queued up I/O. As all transactions have an associated priority and generation count, after recovery is complete, transactions that are retried are automatically re-queued in their original order. - All error handling is performed based on a detected failure. The old code would often perform actions "just in case" before accessing a device as the error recovery mechanism was inadequate. Now, for example, if your disk spins down, the system will properly recover even if the device is already open. - Support for "high power" commands. Peripheral drivers can mark actions that may tax a power supply as "high powered". Only a certain number (default of 4, but configurable with the CAM_MAX_HIGHPOWER kernel option) of these commands are allowed to be active at a time. This allows a user to, for example, disable spin-up on the drives in an enclosure and let the system spin them up in a controlled fashion. - By default, all luns are scanned on devices during probe. In the old SCSI layer, this was often problematic as it performed a Test Unit Ready prior to performing an Identify. Many devices that properly handle the Identify will hang the bus if you attempt a different command to a high lun. - Transfer negotiations only occurs to devices that actually support negotiations (based on their inquiry information). This is performed in a controller independent fashion. - There is now a generic quirk mechanism that allows controllers, peripheral drivers, or the CAM transport layer to define their own quirks entries. Currently the CAM transport layer has quirk entries that allow for modulation of tags and disabling multi-lun probing. The AdvanSys driver uses quirk entries to control some of the "hardware bug fixes" in the driver that only apply to certain types of devices. - Hard-wiring of devices to specific unit numbers is supported as it was in the old system. - Userland "pass-through" commands are supported. The interface is different than from the old SCSI code, but sample code is provided (including patches to XMCD), and we also provide the beginnings of a "scsi.8" utility in the form of "camcontrol". Features added in the 971211 Snapshot: - Preliminary tape support. This has only been tested on a DDS2 drive and the driver is fairly green. - New device statistic code. A whole slew of information is now recorded on a per-device basis. The interface is generic and once we have systat converted to using this code, all other drivers using the old "dk" stat interface will be converted. The Iostat utility has already been converted to use the new stats. - Bus DMA based bounce buffer support. ISA AdvanSys support now works in all memory configurations. - aic7xxx driver improvements. The aic7895 is now supported. The command queing algorithm is now more efficient. Bug fixes include some problems with error recovery and target initiated sync/wide negotiation. - AdvanSys driver improvements. The driver has now been tested on almost every narrow SCSI card AdvanSys has produced. Many bugs in the device probe code have been fixed. - Table driven error handling. This greatly simplifies the task of enhancing or modifying how errors are handled. - Enhanced PCI conf support. Although this isn't really CAM related, you get it for free. Check out the pciconf utilty for details. - Numerous other bug fixes I've forgotten about. Features added in the 980103 Snapshot: - Preliminary NCR/Symbios adapter support. Regular operations should be fine, but the error recovery portions of this driver need work. - iostat is now fully functional. - Fixed an infinite retry bug in the Adaptec driver's error recovery code. - Fixed a bug that prevented disconnections and ultra speeds for target ids above 7 in the Adaptec driver. - Expanded the use of bowrite to other locations where synchronous writes were used only to maintain write ordering. - The disk drivers now perform the buffer elelevator sort even if the device supports tags. - The da driver will now only invalidate the media if it believes the media or device has changed. This means that errors like unrecoverable media errors will not prevent future reads and writes (e.g. to remap a sector). - Userconfig.c now compiles. - Correct ccd to initialize b_resid to 0 as all other buffer allocators in the kernel do so that low level driver code only needs to touch b_resid in the error case. - Transfer negotiation now occurs earlier in the probe sequence so that the messages output at boot time have the final and proper negotiation info in them. - When performing the mode sense during probe to retrieve the control page, we nolonger attempt to use the DBD bit. Some devices don't like that. Changes for the 980308 Snapshot: - Aic7xxx driver now supports the 7890/91 (AKA 2940U2W). This includes support for the new "bmov" instruction, and some utilization of the secondary DMA FIFO for S/G list prefetch on aic7890/91/95 chips. ULTRA2 speeds have not been tested as I do not have any ULTRA2 peripherals to test with. - CAM now differentiates between "user" transfer settings and "current" transfer settings. When a controller starts up, it's current settings should be async/narrow and it's user settings should reflect any configured settings for the card (e.g. SCSI-Select settings) or the defaults if configuration is not supported. During device probe, the XPT layer will querry for the user settings, filter them based on the capabilities of the device and use the result to set the current settings. The aic7xxx driver has been updated to deal with these changes including a new scheme for storing and handling negotiation settings in that driver. Updating the other drivers will follow shortly and is trivial to do. - Full kernel hot swap support. The kernel and all peripheral drivers can handle devices arriving and going away after boot up. - To determine whether any new devices have arrived, you must rescan a SCSI bus, or rescan a particular device by completely specifying it's bus/target/lun. This can be done with the new "camcontrol" utility. Although it would be possible to have the kernel "auto-detect" some new devices using Asynchronous Even Notifications (AEN), no controller driver currently supports AENs and device support for AENs is rare, so AEN support is low on the wish list. - The kernel can figure out that a device has gone away if it gets a selection timeout while talking to the device. In that case, the kernel will automatically invalidate the device and all attached peripheral drivers. You can also issue a rescan of a bus or a bus/target/lun and the kernel will notice if any devices have gone away. - Device removal goes in two stages: - The kernel notices (either through a rescan or a selection timeout) that a device has gone away. It marks the device as invalid, and prints out something like this: (cd5:ahc1:0:1:3): lost device At this point, the peripheral driver will still exists if it is open, although in a state where all new opens, ioctls and I/O requests are refused. This ensures that the system can gracefully handle final close of the device. - Once final close of the device occurs (all userland processes that have the device open issue a close), the kernel finishes removing that peripheral driver instance. The kernel then prints out something like this: (cd5:ahc1:0:1:3): removing device entry Then, and only then, can another peripheral driver with the same unit number take its place. The system enforces this behavior to ensure that all clients release the device, thereby acknowledging the error condition, before any new or old clients can access the new device instance. Be aware when removing a device that even though the "regular" peripheral driver (cd, sd, sa) for a device has gone away, the passthrough peripheral driver, if still open, will still be around. For instance, if you're playing a CD with xmcd, xmcd will only have the passthrough device open, not the cd device. If you unplug the CDROM drive from the SCSI bus, the cd device will go away on the next rescan or selection timeout since you don't have a CD filesystem mounted. The passthrough device will not release, though, until you exit XMCD. The passthrough device is normally "silent" about it's presense, and by default will not print any messages when it arrives or goes away. If you boot with -v, the passthrough driver will print out probe messages and arrival/departure messages. - Better CD changer support. The CAM CDROM driver now automatically detects lun-based CD changers and schedules run time for each lun. This greatly reduces the changer thrashing caused by multiple users or applications accessing multiple CDs on a changer at the same time. - Changer detection is rather simplistic -- if the CD driver sees a CDROM device with a LUN greater than 0, it assumes that that device is part of a changer. All luns of that target will be included in a changer meta-driver, and scheduled to run on a mutually exclusive basis. - Each lun on a changer gets a minimum and a maximum amount of run time. The compiled in defaults are 2 seconds and 10 seconds, respectively, but they can be changed easily by the end user. The maximum run time is only enforced if there is another lun on the changer with I/O waiting. The default minimum and maximum run time can be changed in the kernel config file. See LINT for details. They can also be changed on the fly via two new sysctl variables: kern.cam.cd.changer.min_busy_seconds kern.cam.cd.changer.max_busy_seconds So you can interactively tune your changer's performance to suit your changer and usage patterns. - If anyone actually has a CD tower or other peripheral with independant devices reported on each LUN (not target!), please send probe (i.e. boot) output to ken@plutotech.com. I'll put a quirk entry in the CD driver so that your device doesn't get recognized as a changer. Many thanks go to Lars Fredriksen for letting us borrow his changer to perform this work. - New camcontrol utility. There is no man page for it yet, but eventually this should be at least as useful as scsi(8). For now, it can: - list CAM peripherals attached to a given device - send a test unit ready to a given device - send a SCSI inquiry to a device (and yes, Satoshi, you can print out a drive serial number all by itself. :) ) - send a start/stop unit command to a device (and optionally load or eject media) - rescan a given bus for new/removed devices, or rescan a given bus/target/lun to see if it is present or has gone away - read the defect list (permanant or grown) for a given drive. - Tape driver enhancements. - The CAM tape driver now supports the retension, offline/rewoffl and erase mt(1) commands. - The tape driver also will reserve and release a tape drive on open and close, respectively. This insures mutually exclusive access to the tape drive in multiple initiator environments. - mt(1) has been updated with a number of new densities, and now prints out the bits per inch for each density. - Improved statistics support. Almost every SCSI command sent to a device is now recorded in the devstat facility. Before, some commands, especially non block I/O commands, fell through the cracks. - New transport layer device driver. This drive accepts CCB types that don't apply to a single device (e.g. bus rescanning CCBs). It also accepts the getpassthrough ioctl, and thus performs matching between peripheral drivers and their corresponding passthrough drivers. This change allows users to perform diagnostics on a device using the passthrough driver, even if the normal peripheral driver for the device can't be opened. For instance, you can issue a test unit ready to a CDROM device even when there is no media in the drive. - Updated userland CAM library. - The CAM library interface has been changed to take advantage of the new transport layer device. So, there is now a cam_open_spec_device() function. This allows you to individually specify the device name (e.g. "da", "cd", "sa") and unit number for the peripheral driver you want to open. cam_open_device() now just tries to derive the peripheral name and unit number from the passed in device path. It then passes those in to the real open function. - The CAM library now includes a number of tape-related CCB building functions. - -- Justin T. Gibbs Kenneth D. Merry ------- End of Blind-Carbon-Copy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 17:36:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15833 for freebsd-current-outgoing; Sun, 8 Mar 1998 17:36:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15828 for ; Sun, 8 Mar 1998 17:36:30 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id SAA27378; Sun, 8 Mar 1998 18:36:30 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd027335; Sun Mar 8 18:36:22 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id SAA12054; Sun, 8 Mar 1998 18:36:17 -0700 (MST) From: Terry Lambert Message-Id: <199803090136.SAA12054@usr08.primenet.com> Subject: Re: vnode_pager: *** WARNING *** stale FS code in system To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Mon, 9 Mar 1998 01:36:17 +0000 (GMT) Cc: nate@mt.sri.com, dima@tejblum.dnttm.rssi.ru, tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <10803.889345727@critter.freebsd.dk> from "Poul-Henning Kamp" at Mar 8, 98 09:28:47 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 > >Tell me what I'm missing, if anything? > > You're absolutely right. Terry is obfuscating the argument because > he is trying to cover up for the fact that he didn't realize what > the default operations vectors were there for. Nice of you to chime in with an assumption about what is in my head, Poul. The reason for the default ops vectors is to implement the operations that an FS doesn't want to implement itself. You will notice that this is a violation of the stacking architecture noted in Figure 6.14 on page 234 of "The Design and Implementation of the 4.4BSD Operating System", which levels that avenue for "appeal to authority". You can achieve the same functionality ad the default vops by placing the vop_* functions in the apropriate vnodeopv_entry_desc's, or in the case where you want FS specific implementations, and the use of the functions are a temporary bandaid (as in a generic {get|put}pages), you can provide stub functions (which I did). I note that the use of the default vops breaks FS stack bypass compression at vfs_init time for a given stack instance. Rather than calling to the immediately inferior node, the highest level node in a stack's VOP vector for an uniplemented vector should be passed upwards. If an FS "doesn't want" to implement a VOP, then either the VOP should fail, or the FS should only be used in a context where it is stacked on top of another FS whic *does* implement the VOP. In fact, we see by looking at Kirk McKusick's Suft Updates implementation that a number of the "optimizations" wrought by the default vops in fact *break* existing functionality, where UFS/FFS are not considered as a monolithic object. Returning to first principles, we see that Heidemann specifically cautions against this type of "optimization": Reuse of layers is enhanced whe each layer encompasses few abstractions. If layer crossing overhead is at all significant, modular filing environments will either suffer serious performance penalties (relative to non- layered environments), or layers will be combined, making layer reuse more difficult. Go read John Heidemann's Thesis: ftp://ftp.cs.ucla.edu/pub/ficus/heidemann_thesis.ps.gz Since he invented the thing, why don't we just find out what the inventor intended instead of speculating about "what Terry does or doesn't know about his intent"? Pay attention to 1.2.1, where he makes the case for symmetric interfaces. Pay attention also to the content of chapters 2 & 3, in which he makes the case that the default should be to facilitate stacking, his comments on efficiency, opacity, and limits. Technically, local media FS's, as they are implemented in BSD, do not meet the definition of stacking layers: The key characteristic of a stackable layer is that it possess the same interface above and below. If you need clarification of any issues raised by his paper, let me know, and I can send you his email address (if you won't accept my clarifications), since I have probably asked many of the same questions since first corresponding with him on the subject of rolling the code into BSD 4.3 derived 386BSD, back in 1994. While you are at it, why don't you send Kirk McKusick some mail; don't reference anyone by name so you don't bias him one way or the other (after all, I've probably had dinner with him more recently than you). Ask him how he feels, in general, about whether or not there should be FS specific VOP_{GET|PUT|}PAGES code. Regards, 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 Mar 8 17:41:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17318 for freebsd-current-outgoing; Sun, 8 Mar 1998 17:41:03 -0800 (PST) (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 RAA17292 for ; Sun, 8 Mar 1998 17:40:56 -0800 (PST) (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 MAA19054 for ; Mon, 9 Mar 1998 12:10:53 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id MAA10073 for FreeBSD-current@FreeBSD.ORG; Mon, 9 Mar 1998 12:10:53 +1030 (CST) (envelope-from grog) Message-ID: <19980309100806.34950@freebie.lemis.com> Date: Mon, 9 Mar 1998 10:08:07 +1030 From: Greg Lehey To: Mike Smith Subject: HEADS UP! (was: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c) References: <199803081506.HAA06931@freefall.freebsd.org> <199803081518.HAA10644@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803081518.HAA10644@dingo.cdrom.com>; from Mike Smith on Sun, Mar 08, 1998 at 07:18:50AM -0800 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 Sun, 8 March 1998 at 7:18:50 -0800, Mike Smith wrote: >> Modified files: >> sys/i386/i386 autoconf.c >> Log: >> Construct the minor number for the root device taking into account the >> slice number passed in by the bootblocks. This means the kernel will >> not use the compatability slice to obtain the root filesystem when >> booting from a sliced disk. > > *WARNING* > > If your boot disk is sliced (has a partition table), and you have not > upgraded /sbin/mount to the most recent version preceeding this change, > you will have problems booting. > > This change means that if your current /etc/fstab looks like this: > > /dev/xd0a / ufs ... > /dev/xd0s2e /usr ufs ... > > you need to update it to look like: > > /dev/xd0s2a / ufs ... > /dev/xd0s2e /usr ufs ... > > Note that the root filesystem is now consistent with the others. If > you are using a 'dedicated' disk, you will have entries like > > /dev/xd0a / ufs ... > /dev/xd0e /usr ufs ... > > and you should *not* change. > > The recent update to /sbin/mount includes compatability support which > will ease this transition. I nearly missed this. Wouldn't a "heads up" have been a good idea? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 17:58:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20260 for freebsd-current-outgoing; Sun, 8 Mar 1998 17:58:46 -0800 (PST) (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 RAA20255 for ; Sun, 8 Mar 1998 17:58:43 -0800 (PST) (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 RAA12307; Sun, 8 Mar 1998 17:57:21 -0800 (PST) Message-Id: <199803090157.RAA12307@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Thomas Dean cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c In-reply-to: Your message of "Sun, 08 Mar 1998 10:45:47 PST." <199803081845.KAA02194@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 17:57:20 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does this mean that /dev will be cleaned in the future to remove the > offending device names? Everything that I have tried, like disklabel > accept /dev/sd1 and /dev/sd1s1c. disklabel gives (proper?) different > information for different arguments. No, as the device names aren't "offending" xdN[a-h] refers to partitions on a dedicated disk. xdNsM[a-h] refers to partitions within a slice. This is the way it was always meant to be. There was a problem initially that made it difficult to determine at the appropriate level *which* slice was the right one, so the assumption was made that it should be the first one. Because of the way this misfeature was implemented, the convention was established that xdNa would always be the first partition (in the first slice) on the disk. This is bogus, and makes life very difficult for software which has to attempt to establish the equality between xdNa and xdNsMa. In the short term (2.2, 3.0 prior to the DEVFS/SLICE changeover), the compatability slice cruft will probably remain, in order to avoid violating POLA. All that has been changed here is that the kernel will now explicitly mount the partition in the booted slice. With a little extra work, this would allow you to boot correctly from *any* slice, not just the first, BIOS restrictions notwithstanding. > I have: > > /dev/sd1 /dev/sd1e /dev/sd1s1a /dev/sd1s1f /dev/sd1s4 > /dev/sd1a /dev/sd1f /dev/sd1s1b /dev/sd1s1g > /dev/sd1b /dev/sd1g /dev/sd1s1c /dev/sd1s1h > /dev/sd1c /dev/sd1h /dev/sd1s1d /dev/sd1s2 > /dev/sd1d /dev/sd1s1 /dev/sd1s1e /dev/sd1s3 > > If I only had sd1s[a-h] then it would be less confusing. DEVFS is your friend. Device entries for partitions come and go as they are created/deleted. Have a little patience, and all will make sense. -- \\ 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 Mar 8 18:03:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21130 for freebsd-current-outgoing; Sun, 8 Mar 1998 18:03:55 -0800 (PST) (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 SAA21105 for ; Sun, 8 Mar 1998 18:03:51 -0800 (PST) (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 SAA12336; Sun, 8 Mar 1998 18:01:13 -0800 (PST) Message-Id: <199803090201.SAA12336@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mikael Karpberg cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c In-reply-to: Your message of "Sun, 08 Mar 1998 16:32:10 +0100." <199803081532.QAA06008@ocean.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 18:01:12 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to Mike Smith: > > If your boot disk is sliced (has a partition table), and you have not > > upgraded /sbin/mount to the most recent version preceeding this change, > > you will have problems booting. > > > > This change means that if your current /etc/fstab looks like this: > > > > /dev/xd0a / ufs ... > > /dev/xd0s2e /usr ufs ... > > > > you need to update it to look like: > > > > /dev/xd0s2a / ufs ... > > /dev/xd0s2e /usr ufs ... > > Er... Excuse me for the maybe silly question, but WHY is this done? It's the next step in the very slow process of divesting some of the old design decisions from the 386BSD days. > I mean... I run my disk split up between FreeBSD and Win95, and so there's > really no ambigiousness. There's just one UFS slice. So not having to deal > with the cumbersomeness of the "sX" part is nicer, and I went the other > way, for shorter names: Then you lose. I'm sorry - you're currently taking advantage of a misfeature that is going to disappear very soon. The DEVFS/SLICE code explicitly disavows any knowledge of the "compatability" slice. > /dev/xd0a / ufs ... > /dev/xd0e /usr ufs ... > > Also, on my other machine I have a SCSI disk for freebsd, and a IDE disk > for Win95. Computer boots from the ide, and then I use booteasy there to > boot from the SCSI disk. The SCSI disk is not "dangerously dedicated", > but it's just one big BSD slice. So... will I need "sd0s1a" on that, > or just "sd0a"? The changes I have made *only* affect the boot device. The remainder of the "compatability slice" implementation remains. Note, however, that when you move to DEVFS, there will not be any sd0[a-h] nodes *in* /dev/, so you wouldn't be able to mount them even if you wanted to. -- \\ 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 Mar 8 18:13:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22499 for freebsd-current-outgoing; Sun, 8 Mar 1998 18:13:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22492 for ; Sun, 8 Mar 1998 18:12:57 -0800 (PST) (envelope-from jak@cetlink.net) Received: from exit1.i485.net (i485-gw.cetlink.net [209.198.15.1]) by ns2.cetlink.net (8.8.5/8.8.5) with SMTP id VAA10168; Sun, 8 Mar 1998 21:12:52 -0500 (EST) From: jak@cetlink.net (John Kelly) To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: Someone needs to re-develop "Softupdates" Date: Mon, 09 Mar 1998 02:14:48 GMT Message-ID: <35034f2e.134015736@mail.cetlink.net> References: <19980308191111.08309@mcs.net> In-Reply-To: <19980308191111.08309@mcs.net> X-Mailer: Forte Agent 1.01/16.397 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 SAA22495 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Mar 1998 19:11:11 -0600, Karl Denninger wrote: >According to Kirk, if someone wants to use it in a "Production ISP System" >(to cite one of his examples) they need to negotiate a license from him. > >To use a single word Kirk: NO. >That's nothing short of incredible, if you ask me. It's amazing how some of the same people who decry commercializing FreeBSD with donor control of funding have no objection to Kirk's commercial hooks. Score 1 for the GPL. -- Browser war over, Mozilla now free. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 18:18:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23237 for freebsd-current-outgoing; Sun, 8 Mar 1998 18:18:13 -0800 (PST) (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 SAA23203 for ; Sun, 8 Mar 1998 18:18:05 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id VAA19519; Sun, 8 Mar 1998 21:15:48 -0500 (EST) Date: Sun, 8 Mar 1998 21:15:47 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Mike Smith cc: Thomas Dean , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c In-Reply-To: <199803090157.RAA12307@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 Sun, 8 Mar 1998, Mike Smith wrote: Mike, regarding the disk, I can't remember if I made the disk I'm using right now "dangerously dedicated" or not, and there isn't, obviously (else I wouldn't be confused) any msdos partition. Seeing as I don't dare make a mistake on this, and don't do all that much installation, would you kindly tell me exactly what I should do to find out if I have to change my fstab or not? I'm purposely omitting my fstab so that your answer will be general enough so that everyone will have no excuse for not reading your answer, and won't end up screwed if they make some messy mistake. I am not sure what to look for in doing disklabel, to show me if the disk is dangerously dedicated or not. ----------------------------+----------------------------------------------- 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 Sun Mar 8 18:28:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26248 for freebsd-current-outgoing; Sun, 8 Mar 1998 18:28:31 -0800 (PST) (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 SAA26184; Sun, 8 Mar 1998 18:28:25 -0800 (PST) (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.6.9) with ESMTP id SAA24668; Sun, 8 Mar 1998 18:27:28 -0800 (PST) To: "Jordan K. Hubbard" cc: Mikael Karpberg , mike@smith.net.au (Mike Smith), current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c In-reply-to: Your message of "Sun, 08 Mar 1998 15:12:19 PST." <23720.889398739@time.cdrom.com> Date: Sun, 08 Mar 1998 18:27:28 -0800 Message-ID: <24664.889410448@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Erm.. Just to follow up to correct a confusing typo: > > Er... Excuse me for the maybe silly question, but WHY is this done? > > It's inconsistent to have every partition *other* than the root > partition use the compatability slice, that's why, and there's nasty ^ not To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 18:30:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26613 for freebsd-current-outgoing; Sun, 8 Mar 1998 18:30:44 -0800 (PST) (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 SAA26608 for ; Sun, 8 Mar 1998 18:30:40 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id SAA17159; Sun, 8 Mar 1998 18:24:15 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd017156; Sun Mar 8 18:24:11 1998 Date: Sun, 8 Mar 1998 18:19:53 -0800 (PST) From: Julian Elischer To: Chuck Robey cc: Mike Smith , Thomas Dean , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c 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 the easiest way is to see the output of fdisk /dev/rwd0 if the BSD partition starts at 0 then it's dangerously dedicated. if it starts above 0 then it's not On Sun, 8 Mar 1998, Chuck Robey wrote: > On Sun, 8 Mar 1998, Mike Smith wrote: > > Mike, regarding the disk, I can't remember if I made the disk I'm using > right now "dangerously dedicated" or not, and there isn't, obviously > (else I wouldn't be confused) any msdos partition. Seeing as I don't > dare make a mistake on this, and don't do all that much installation, > would you kindly tell me exactly what I should do to find out if I have > to change my fstab or not? > > I'm purposely omitting my fstab so that your answer will be general > enough so that everyone will have no excuse for not reading your answer, > and won't end up screwed if they make some messy mistake. > > I am not sure what to look for in doing disklabel, to show me if the > disk is dangerously dedicated or not. > > ----------------------------+----------------------------------------------- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 18:45:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29426 for freebsd-current-outgoing; Sun, 8 Mar 1998 18:45:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from forbidden-donut.anet-stl.com (doogie@forbidden-donut.anet-stl.com [209.83.128.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29398 for ; Sun, 8 Mar 1998 18:45:30 -0800 (PST) (envelope-from doogie@forbidden-donut.anet-stl.com) Received: from localhost (doogie@localhost) by forbidden-donut.anet-stl.com (8.8.8/8.8.7) with SMTP id UAA15097; Sun, 8 Mar 1998 20:38:12 -0600 (CST) (envelope-from doogie@forbidden-donut.anet-stl.com) Date: Sun, 8 Mar 1998 20:38:09 -0600 (CST) From: Jason Young To: John Kelly cc: Karl Denninger , current@FreeBSD.ORG Subject: Re: Someone needs to re-develop "Softupdates" In-Reply-To: <35034f2e.134015736@mail.cetlink.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 -----BEGIN PGP SIGNED MESSAGE----- On Mon, 9 Mar 1998, John Kelly wrote: > It's amazing how some of the same people who decry commercializing > FreeBSD with donor control of funding have no objection to Kirk's > commercial hooks. What are you talking about? There's a difference between commercializing FreeBSD, Inc. and a third party developing proprietary code and redistributing it for profit. Do you object to anyone and everyone developing commercial code for FreeBSD? This aside, I don't see anything in the license for Softupdates about the commercial stuff either even though I have read the references on Julian's webpage about it. I would like to use this in my commercial ISP environment and have mailed Kirk asking for clarification. > Score 1 for the GPL. Is this a troll or your actual opinion? If Kirk has in any way used FreeBSD or any BSD licensed code in this, then he can still develop and market Softupdates as he wishes, and I would fight for his ability to do it. If FreeBSD was under the GPL and Kirk used one line of FreeBSD code, he would not have the option to sell his code. Since Kirk, according to the explanations I read, would like to get paid for this code when used commercially (read: eat, sleep indoors, have net access, etc) he would probably develop for an operating system that allowed him to do so. I should probably know better than to get involved in a BSD - GPL licensing debate but that above statement "Score 1 for the GPL" was just too dumb to leave unanswered, I'm sorry. The fact that there's some obvious mixups and misunderstandings in licensing for this which I'm trying to resolve for myself (and will post if anyone's interested) does not reflect in any way on either the BSD or GPL licensing scheme. Jason Young ANET Chief Network Engineer "Bother," said Pooh, "Eeyore, ready two photon torpedoes and lock phasers on the Heffalump, Piglet, meet me in transporter room three." -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNQNWE6InE6ybC66VAQFkkgL+MmJkvLcfS+b76DhPp5JCxysxkyjPha5+ rENNJ8VqaPA1zvSacmvruHTMGjlLEFUNmhYtyfKAl0Fo1176T/+vzp184x9yEW1I 4P0c4M1rgDllN7E3notXIH1VyqyI/mGJ =96+8 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 18:46:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29648 for freebsd-current-outgoing; Sun, 8 Mar 1998 18:46:09 -0800 (PST) (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 SAA29632 for ; Sun, 8 Mar 1998 18:46:04 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id TAA21271; Sun, 8 Mar 1998 19:46:04 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd021258; Sun Mar 8 19:46:01 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id TAA15424; Sun, 8 Mar 1998 19:45:58 -0700 (MST) From: Terry Lambert Message-Id: <199803090245.TAA15424@usr08.primenet.com> Subject: Re: vnode_pager: *** WARNING *** stale FS code in system To: nate@mt.sri.com (Nate Williams) Date: Mon, 9 Mar 1998 02:45:58 +0000 (GMT) Cc: dima@tejblum.dnttm.rssi.ru, tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199803080002.RAA05223@mt.sri.com> from "Nate Williams" at Mar 7, 98 05:02:48 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Tell me what I'm missing, if anything? > Terry wants FS implementors (therefore all FS's) to explicitly write > code for vnode_pagers, rather than having the (potentially buggy) code > used by FS writers. Terry wants local media FS implementors (therefore all non-stackable FS's) to explicitly write code for vnode_pagers as payment for their direct consumption of OS-specific kernel internals. FFS consumes 151 kernel functions; about 120 more than it should. > Dima wants people to not have write potentially trivial code into their > FS, but give them a default that will work in most cases. By use of the default vops vector, which violates the design principles of the stacking FS code according to both "The Design and Implementation of the 4.4BSD Operating System" and "Stackable Layers: An architecture for File System Development", both of which FreeBSD purports to pay lip-service to. > Terry claims that if they rely on the trivial code, it could cause bugs. Terry claims that use of the default vops vector breaks automatic bypass in vfs_init. > Dima claims that for most existing FS's, the trivial stuff is good > enough for their purposes, and that any FS developer that isn't writing > a trivial FS already is smart enough to write a non-default vnode_pager > implementation. Dima wants it to work the way it used to, and doesn't see any reason to change the existing code path in a way which is visible to Dima. > Terry claims that this vnode_pager stuff should go away, and it'll be > easier to remove it by making sure that all FS's have this code, but > then he loses me from that point on. Terry claims to have read the comment in /sys/vm/vnode_pager.c: /* * TODO: * Implement VOP_GETPAGES/PUTPAGES interface for filesystems. Will * greatly re-simplify the vnode_pager. */ > Anyone silly enough to write [ local media ] > FS's should know what they're doing, and forcing them to write more > boilerplate code that could be done by default is simply silliness. The point is, of course, that the code *can't* be done by default, and we have as evidence the death of LFS and the non-function of NFS. In addition, we have the implied comments about VOP_GETPAGES being necessary through its existance in various working FS implementations. > If you're smart enough to write FS, you should also be smart enough to > figure out when the defaults won't cut it. > > This is the intent of stacking FS's as I understand. The VFS stuff is > intended to make FS design more OOP, so that you can pick what things > you need to implement, and not have to implement others, just like > object inheritence. For stackable FS's (which means *NOT* local media FS's) the underlying FS below the stack will implement the VOP_{GET|PUT}PAGES by means of the bypass. Because of this, yoy are mixing the idea of writing a non-stackable local media FS (it can only be stacked *on top of* because it does not properly implement a bottom end that is identical to its top end; it's bottom end is the kernel interfaces to subsystems like VM) and a stackable FS (for which your second paragraph is true). People, *PLEASE* read Heidemann's paper before making comments on FS architecture! It is *the* architectural refrence for the BSD 4.4 stacking vnode interface! 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 Mar 8 18:49:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00340 for freebsd-current-outgoing; Sun, 8 Mar 1998 18:49:03 -0800 (PST) (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 SAA00327 for ; Sun, 8 Mar 1998 18:49:00 -0800 (PST) (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 TAA24841; Sun, 8 Mar 1998 19:48:58 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id TAA13804; Sun, 8 Mar 1998 19:48:56 -0700 Date: Sun, 8 Mar 1998 19:48:56 -0700 Message-Id: <199803090248.TAA13804@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: jak@cetlink.net (John Kelly) Cc: Karl Denninger , current@FreeBSD.ORG Subject: Re: Someone needs to re-develop "Softupdates" In-Reply-To: <35034f2e.134015736@mail.cetlink.net> References: <19980308191111.08309@mcs.net> <35034f2e.134015736@mail.cetlink.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >According to Kirk, if someone wants to use it in a "Production ISP System" > >(to cite one of his examples) they need to negotiate a license from him. > > > >To use a single word Kirk: NO. > > >That's nothing short of incredible, if you ask me. > > It's amazing how some of the same people who decry commercializing > FreeBSD with donor control of funding have no objection to Kirk's > commercial hooks. Sad isn't it.... > Score 1 for the GPL. The GPL has nothing to do with this. This is simply a commercial entity that has paid Kirk that would like to not having to re-integrate this into FreeBSD as changes are made. Basically, this commercial entity is giving some of it's work to FreeBSD, and making it 'easier' for Kirk to get money since other 'commercial' entities who want to use Kirk's work have everything but the legal license. Sort of a 'big carrot' dangling out in front that they can't legally obtain. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 18:56:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02614 for freebsd-current-outgoing; Sun, 8 Mar 1998 18:56:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02490; Sun, 8 Mar 1998 18:55:51 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id NAA15322; Mon, 9 Mar 1998 13:56:08 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803090256.NAA15322@cimlogic.com.au> Subject: gcc, just what you need to here right now To: peter@FreeBSD.ORG Date: Mon, 9 Mar 1998 13:56:08 +1100 (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 Peter, Your recent set of changes to gcc broke it for alpha. Yeah, I know how much you care about that... 8-) I backed out the deltas in my local cvs and it works again, so I'll keep it that way until later. Just thought I'd give you the good news. Welcome to multiple architectures. 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 Mar 8 18:58:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03392 for freebsd-current-outgoing; Sun, 8 Mar 1998 18:58:32 -0800 (PST) (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 SAA03365 for ; Sun, 8 Mar 1998 18:58:18 -0800 (PST) (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 SAA12563; Sun, 8 Mar 1998 18:55:02 -0800 (PST) Message-Id: <199803090255.SAA12563@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Chuck Robey cc: Mike Smith , Thomas Dean , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c In-reply-to: Your message of "Sun, 08 Mar 1998 21:15:47 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 18:55:01 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 8 Mar 1998, Mike Smith wrote: > > Mike, regarding the disk, I can't remember if I made the disk I'm using > right now "dangerously dedicated" or not, and there isn't, obviously > (else I wouldn't be confused) any msdos partition. Seeing as I don't > dare make a mistake on this, and don't do all that much installation, > would you kindly tell me exactly what I should do to find out if I have > to change my fstab or not? Update /sbin/mount at the same time as you build a new kernel this one time. If it emits a diagnostic when you reboot telling you that you need to update /etc/fstab, then you should. > I'm purposely omitting my fstab so that your answer will be general > enough so that everyone will have no excuse for not reading your answer, > and won't end up screwed if they make some messy mistake. 8) > I am not sure what to look for in doing disklabel, to show me if the > disk is dangerously dedicated or not. You don't need to. The problem is that there are pathalogical cases where it becomes impossible to give an accurate answer without lots of work on the part of the questioner. The diagnostic from mount is an unequivocal and absolute indicator. -- \\ 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 Mar 8 19:01:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03982 for freebsd-current-outgoing; Sun, 8 Mar 1998 19:01:13 -0800 (PST) (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 TAA03954 for ; Sun, 8 Mar 1998 19:01:02 -0800 (PST) (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 UAA24932; Sun, 8 Mar 1998 20:00:53 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id UAA13920; Sun, 8 Mar 1998 20:00:47 -0700 Date: Sun, 8 Mar 1998 20:00:47 -0700 Message-Id: <199803090300.UAA13920@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: nate@mt.sri.com (Nate Williams), dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: <199803090245.TAA15424@usr08.primenet.com> References: <199803080002.RAA05223@mt.sri.com> <199803090245.TAA15424@usr08.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Terry wants FS implementors (therefore all FS's) to explicitly write > > code for vnode_pagers, rather than having the (potentially buggy) code > > used by FS writers. > > Terry wants local media FS implementors (therefore all non-stackable > FS's) to explicitly write code for vnode_pagers as payment for their > direct consumption of OS-specific kernel internals. Same thing, different way of putting it. > > Dima wants people to not have write potentially trivial code into their > > FS, but give them a default that will work in most cases. > > By use of the default vops vector, which violates the design principles > of the stacking FS code according to both "The Design and Implementation > of the 4.4BSD Operating System" and "Stackable Layers: An architecture > for File System Development", both of which FreeBSD purports to pay > lip-service to. Screw the design when it comes to having buggy/non-working FS's. That's one of the rules of getting your code committed. If your solution isn't complete, then it shouldn't be committed. So, if you didn't provide patches to *all* existing code then you should be taken out and beat about the head and shoulders with a large noodle. If you want all the FS's to *require* the code, then write code for all of the existing FS in FreeBSD. Finally, I disagree with the claim that *all* FS must implement *every* vops operation. If so, then the 'stackable' design is broken, since in any good design you should have the ability to use a default for common operations. > > Terry claims that if they rely on the trivial code, it could cause bugs. > > Terry claims that use of the default vops vector breaks automatic > bypass in vfs_init. Pray tell which existing FS break if you add the code to the default vops? > > Dima claims that for most existing FS's, the trivial stuff is good > > enough for their purposes, and that any FS developer that isn't writing > > a trivial FS already is smart enough to write a non-default vnode_pager > > implementation. > > Dima wants it to work the way it used to, and doesn't see any reason > to change the existing code path in a way which is visible to Dima. Dima (and I) are fans of POLA. Terry wants to punish people for not doing things his way. I think reading 20 page emails is punishment enought w/out have the FS's break (or whine alot) is overkill. > > Terry claims that this vnode_pager stuff should go away, and it'll be > > easier to remove it by making sure that all FS's have this code, but > > then he loses me from that point on. > > Terry claims to have read the comment in /sys/vm/vnode_pager.c: > > /* > * TODO: > * Implement VOP_GETPAGES/PUTPAGES interface for filesystems. Will > * greatly re-simplify the vnode_pager. > */ I don't see anywhere it states that a 'default' VOP_GETPAGES can't be added in here, vs. a VOP_GETPAGES in every [ local media ] FS. > > Anyone silly enough to write > > [ local media ] > > > FS's should know what they're doing, and forcing them to write more > > boilerplate code that could be done by default is simply silliness. > > The point is, of course, that the code *can't* be done by default, and we > have as evidence the death of LFS and the non-function of NFS. That's a total non-sequiter. LFS and NFS have brokeness way beyond the VOP_GETPAGES stuff. Getting them working require that as well as much other stuff. The reason they don't work is that their bits have rotted due to inattention. > > If you're smart enough to write FS, you should also be smart enough to > > figure out when the defaults won't cut it. > > > > This is the intent of stacking FS's as I understand. The VFS stuff is > > intended to make FS design more OOP, so that you can pick what things > > you need to implement, and not have to implement others, just like > > object inheritence. > > For stackable FS's (which means *NOT* local media FS's) the underlying > FS below the stack will implement the VOP_{GET|PUT}PAGES by means of > the bypass. So, stacking only applies to non 'local media' FS? Seems like a bad design if it can't take care of both cases. (BTW, can you describe succintly what a 'local media' FS is in your terms, so that I'm not making any wrong assumptions?) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 19:02:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04107 for freebsd-current-outgoing; Sun, 8 Mar 1998 19:02:01 -0800 (PST) (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 TAA04089; Sun, 8 Mar 1998 19:01:47 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id UAA24263; Sun, 8 Mar 1998 20:01:44 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd024212; Sun Mar 8 20:01:36 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id UAA15987; Sun, 8 Mar 1998 20:01:34 -0700 (MST) From: Terry Lambert Message-Id: <199803090301.UAA15987@usr08.primenet.com> Subject: Re: Okay, -current should be conditionally safe to use To: dyson@FreeBSD.ORG Date: Mon, 9 Mar 1998 03:01:33 +0000 (GMT) Cc: karpen@ocean.campus.luth.se, current@FreeBSD.ORG In-Reply-To: <199803080012.TAA00282@dyson.iquest.net> from "John S. Dyson" at Mar 7, 98 07:12:31 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 > > Would tuning the NFS exported disk SoftUpdates do a significant difference? > > > Yes. > > > For the moment I don't think we're ready to use the SoftUpdates code, since > > we're using the machine for more then just play, but it might be an > > interesting thing to try once it's more robust. > > It probably isn't a good idea to use softupdates in production yet. However, > another interesting thing to try is: > > sysctl -w vfs.nfs.async=1 > > on the server. This is better (safer) than softupdates, but you *can* > have data lossage, due to writes not being committed to disk. It is > a good idea to have a UPS when using the above option. Note: it is a technical violation of the NFS protocol specification for an NFS server to ACK a write which has not been commited to stable storage. The "Prestoserve" stuff commits the writes to stable storage (battery backed RAM). The Auspex and NetWork Appliance stuff works similarly. The vfs.nfs.async sysctl, Soft Updates, and the SunOS/Solaris/SVR4 write gathering, as well as the SVR4 Delayed Ordered Writes (DOW) are all, in a sense, technical violations. For more information, see: X/Open CAE Specification C218 Protocols for X/Open PC Interworking: XNFS, Issue 4 ISBN: 1-872630-66-9 If you are concerned about fault tolerance, then you should look into a UPS (#define NFS_SERVER STABLE_STORAGE). 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 Mar 8 19:03:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04400 for freebsd-current-outgoing; Sun, 8 Mar 1998 19:03:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA04335; Sun, 8 Mar 1998 19:02:45 -0800 (PST) (envelope-from jak@cetlink.net) Received: from exit1.i485.net (i485-gw.cetlink.net [209.198.15.1]) by ns2.cetlink.net (8.8.5/8.8.5) with SMTP id WAA14626; Sun, 8 Mar 1998 22:02:40 -0500 (EST) From: jak@cetlink.net (John Kelly) To: "Jordan K. Hubbard" Cc: Karl Denninger , current@FreeBSD.ORG Subject: Re: Someone needs to re-develop "Softupdates" Date: Mon, 09 Mar 1998 03:04:36 GMT Message-ID: <35045a62.136823612@mail.cetlink.net> References: <24802.889411323@time.cdrom.com> In-Reply-To: <24802.889411323@time.cdrom.com> X-Mailer: Forte Agent 1.01/16.397 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 TAA04345 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 08 Mar 1998 18:42:03 -0800, "Jordan K. Hubbard" wrote: >> It's amazing how some of the same people who decry commercializing >> FreeBSD with donor control of funding have no objection to Kirk's >> commercial hooks. >> >> Score 1 for the GPL. > >If either of you start this shit up again I'll have you both off the >mailing lists and banned from posting faster than you can say "cheese". > >First and only warning. > > Jordan I'm posting on a topic which has an interrelationship to another topic which I agreed to let die -- and I did. But this is a new topic. Apparently you don't condone the idea of freedom of speech. Or perhaps you just don't like me personally. But if you boot me out, who will be next? Where will it stop? -- Browser war over, Mozilla now free. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 19:07:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05829 for freebsd-current-outgoing; Sun, 8 Mar 1998 19:07:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05786 for ; Sun, 8 Mar 1998 19:07:27 -0800 (PST) (envelope-from jak@cetlink.net) Received: from exit1.i485.net (i485-gw.cetlink.net [209.198.15.1]) by ns2.cetlink.net (8.8.5/8.8.5) with SMTP id WAA15046; Sun, 8 Mar 1998 22:07:22 -0500 (EST) From: jak@cetlink.net (John Kelly) To: Nate Williams Cc: current@FreeBSD.ORG Subject: Re: Someone needs to re-develop "Softupdates" Date: Mon, 09 Mar 1998 03:09:18 GMT Message-ID: <35055ca1.137398237@mail.cetlink.net> References: <19980308191111.08309@mcs.net> <35034f2e.134015736@mail.cetlink.net> <199803090248.TAA13804@mt.sri.com> In-Reply-To: <199803090248.TAA13804@mt.sri.com> X-Mailer: Forte Agent 1.01/16.397 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 TAA05807 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Mar 1998 19:48:56 -0700, Nate Williams wrote: >> It's amazing how some of the same people who decry commercializing >> FreeBSD with donor control of funding have no objection to Kirk's >> commercial hooks. > >Sad isn't it.... > >> Score 1 for the GPL. > >The GPL has nothing to do with this. So you say ... >This is simply a commercial entity that has paid Kirk that would like >to not having to re-integrate this into FreeBSD as changes are made. But then you say that? If all FreeBSD was GPLed Kirk could not demand that anyone license softupdates. So why do you say GPL has nothing to do with it? -- Browser war over, Mozilla now free. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 19:13:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07353 for freebsd-current-outgoing; Sun, 8 Mar 1998 19:13:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA07288 for ; Sun, 8 Mar 1998 19:12:58 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id LAA14528; Mon, 9 Mar 1998 11:12:38 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199803090312.LAA14528@spinner.netplex.com.au> X-Mailer: exmh version 2.0.1 12/23/97 To: John Birrell cc: current@FreeBSD.ORG Subject: Re: gcc, just what you need to here right now In-reply-to: Your message of "Mon, 09 Mar 1998 13:56:08 +1100." <199803090256.NAA15322@cimlogic.com.au> Date: Mon, 09 Mar 1998 11:12:36 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Birrell wrote: > Peter, > > Your recent set of changes to gcc broke it for alpha. Yeah, I know > how much you care about that... 8-) I backed out the deltas in my > local cvs and it works again, so I'll keep it that way until later. > Just thought I'd give you the good news. Welcome to multiple > architectures. 8-) Hmm, most likely there are some missing #ifdef __i386__ or something near the FREEBSD_NATIVE stuff... The wierdo elf/aout switching stuff should be i386 specific. There are some other changes outside the gcc.c area, but I thought I'd done them in such a way that it wouldn't break anything.. Well, that was the plan anyway... Believe it or not, I was actually trying not to break the other arch's much, hence the gymnastics with the #ifdefs rather than just bashing it as needed for i386. What's wrong anyway? Compile or runtime failure? Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 19:16:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08192 for freebsd-current-outgoing; Sun, 8 Mar 1998 19:16:03 -0800 (PST) (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 TAA08144 for ; Sun, 8 Mar 1998 19:15:56 -0800 (PST) (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 UAA25061; Sun, 8 Mar 1998 20:15:54 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id UAA14157; Sun, 8 Mar 1998 20:15:52 -0700 Date: Sun, 8 Mar 1998 20:15:52 -0700 Message-Id: <199803090315.UAA14157@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: jak@cetlink.net (John Kelly) Cc: Nate Williams , current@FreeBSD.ORG Subject: Re: Someone needs to re-develop "Softupdates" In-Reply-To: <35055ca1.137398237@mail.cetlink.net> References: <19980308191111.08309@mcs.net> <35034f2e.134015736@mail.cetlink.net> <199803090248.TAA13804@mt.sri.com> <35055ca1.137398237@mail.cetlink.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> It's amazing how some of the same people who decry commercializing > >> FreeBSD with donor control of funding have no objection to Kirk's > >> commercial hooks. > > > >Sad isn't it.... > > > >> Score 1 for the GPL. > > > >The GPL has nothing to do with this. > > So you say ... > > >This is simply a commercial entity that has paid Kirk that would like > >to not having to re-integrate this into FreeBSD as changes are made. > > But then you say that? If all FreeBSD was GPLed Kirk could not demand > that anyone license softupdates. So why do you say GPL has nothing to > do with it? Because of two reasons: 1) If it was GPL, he wouldn't have written the code since he did it to make money. 2) Kernel enhancements that use 'standard' kernel API in GPL kernels such as Linux don't have to be distributed under the GPL. People seem to make the *very* mistaken assumption that people will do the same sort of things with code if the code is GPL as they would with other copyrights, and fail to realize that the part of the reason they choose to write code for BSD copyrighted code is because the GPL wouldn't allow them the freedom to it the way they want. The GPL isn't about personal freedom, it's about doing things 'for the good of all mankind'. We've already seen what happens when you developer government/commerce on the latter, since it doesn't motivate most people. Further debate on this issue will be ignored. If you want to debate the issue, we can sit over a coke and I can bring in a number of GPL proponents who no longer work on GPL'd code because it wasn't financially beneficial to them. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 19:23:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09882 for freebsd-current-outgoing; Sun, 8 Mar 1998 19:23:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09855 for ; Sun, 8 Mar 1998 19:23:16 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id OAA15438; Mon, 9 Mar 1998 14:23:27 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803090323.OAA15438@cimlogic.com.au> Subject: Re: gcc, just what you need to here right now In-Reply-To: <199803090312.LAA14528@spinner.netplex.com.au> from Peter Wemm at "Mar 9, 98 11:12:36 am" To: peter@netplex.com.au (Peter Wemm) Date: Mon, 9 Mar 1998 14:23:27 +1100 (EST) Cc: jb@cimlogic.com.au, 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 Peter Wemm wrote: > There are some other changes outside the gcc.c area, but I thought I'd > done them in such a way that it wouldn't break anything.. Well, that was > the plan anyway... Believe it or not, I was actually trying not to break > the other arch's much, hence the gymnastics with the #ifdefs rather than > just bashing it as needed for i386. > > What's wrong anyway? Compile or runtime failure? It generates an rdata pseudo-op that gas doesn't recognise. gcc thinks it's doing a wonderful job. gas disagrees. From the glance I took at gas, if I'd configured it for ecoff, it would have known about rdata. But the gas config (I committed the alpha-elf stuff cause it wasn't in the diff I sent jdp, and it doesn't affect i386), declares obj-elf and appears to behave like the NetBSD version of gas (which is what I think I want). I'm happy to leave this until you've completed your aout/elf changes. -- 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 Mar 8 19:24:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10330 for freebsd-current-outgoing; Sun, 8 Mar 1998 19:24:38 -0800 (PST) (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 TAA10279 for ; Sun, 8 Mar 1998 19:24:20 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id WAA19619; Sun, 8 Mar 1998 22:04:42 -0500 (EST) Date: Sun, 8 Mar 1998 22:04:42 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Julian Elischer cc: Mike Smith , Thomas Dean , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c 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 Sun, 8 Mar 1998, Julian Elischer wrote: > the easiest way is to see the output of > fdisk /dev/rwd0 > > if the BSD partition starts at 0 > then it's dangerously dedicated. > if it starts above 0 then it's not > Ahh, yes! That was precisely what I wanted, yup, it was dangerously dedicated. OK, I know (because I saved Mike's earlier posting) what to do. > > On Sun, 8 Mar 1998, Chuck Robey wrote: > > > On Sun, 8 Mar 1998, Mike Smith wrote: > > > > Mike, regarding the disk, I can't remember if I made the disk I'm using > > right now "dangerously dedicated" or not, and there isn't, obviously > > (else I wouldn't be confused) any msdos partition. Seeing as I don't > > dare make a mistake on this, and don't do all that much installation, > > would you kindly tell me exactly what I should do to find out if I have > > to change my fstab or not? > > > > I'm purposely omitting my fstab so that your answer will be general > > enough so that everyone will have no excuse for not reading your answer, > > and won't end up screwed if they make some messy mistake. > > > > I am not sure what to look for in doing disklabel, to show me if the > > disk is dangerously dedicated or not. > > > > ----------------------------+----------------------------------------------- > > 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 > > > > > ----------------------------+----------------------------------------------- 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 Sun Mar 8 19:44:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14020 for freebsd-current-outgoing; Sun, 8 Mar 1998 19:44:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13977 for ; Sun, 8 Mar 1998 19:44:30 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id UAA26279; Sun, 8 Mar 1998 20:44:27 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd026155; Sun Mar 8 20:44:15 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id UAA17601; Sun, 8 Mar 1998 20:44:12 -0700 (MST) From: Terry Lambert Message-Id: <199803090344.UAA17601@usr08.primenet.com> Subject: Re: vnode_pager: *** WARNING *** stale FS code in system To: nate@mt.sri.com (Nate Williams) Date: Mon, 9 Mar 1998 03:44:12 +0000 (GMT) Cc: tlambert@primenet.com, nate@mt.sri.com, dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG In-Reply-To: <199803090300.UAA13920@mt.sri.com> from "Nate Williams" at Mar 8, 98 08:00:47 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 > > > Terry wants FS implementors (therefore all FS's) to explicitly write > > > code for vnode_pagers, rather than having the (potentially buggy) code > > > used by FS writers. > > > > Terry wants local media FS implementors (therefore all non-stackable > > FS's) to explicitly write code for vnode_pagers as payment for their > > direct consumption of OS-specific kernel internals. > > Same thing, different way of putting it. ??? Can't you diff "all FS's" and "all non-stackable FS's"? > Screw the design when it comes to having buggy/non-working FS's. That's > one of the rules of getting your code committed. If your solution isn't > complete, then it shouldn't be committed. That's BS. I've tried that road before, and the code has been consistently refused commit. I've bowed to (IMO, unreasonable) pressure to get there incrementally, and now you are bitching that the code's not getting there all at once. It would be nice if you would make up your mind. > So, if you didn't provide > patches to *all* existing code then you should be taken out and beat > about the head and shoulders with a large noodle. I will be *happy* to wield the noodle over the death of LFS, X.25, and the ISO networking code. Where do I sign up for a noodle? > If you want all the FS's to *require* the code, then write code for all > of the existing FS in FreeBSD. I want them to *eventually* require the code. This is very different from your characterization of my statements. > Finally, I disagree with the claim that *all* FS must implement *every* > vops operation. If so, then the 'stackable' design is broken, since in > any good design you should have the ability to use a default for common > operations. All FS's do *NOT* have to implement every VOP. All FS's do not even have to implement VOP_{GET|PUT}PAGES, if they don't want to. They can stack on an FS that implements them (your argeeement with Dima about which FS that should be is an agreement with me about that), or they can not offer the services that require the use of the vnode_pager. > > Terry claims that use of the default vops vector breaks automatic > > bypass in vfs_init. > > Pray tell which existing FS break if you add the code to the default vops? None. Which existing FS's break if you add stub functions? None. Which existing FS's break if you make a modification to make the warning not fatal, the patch for which was included in my last post? None. Which future FS work breaks by adding the code to the default vops? All stacking FS's. Which future FS work breaks if you add stub functions? None. Which future FS work breaks if you make a modification to make the warning not fatal, the patch for which was included in my last post? Those stacking FS's stacked on top of FS's which are known to be broken by virtue of the warning. > > Dima wants it to work the way it used to, and doesn't see any reason > > to change the existing code path in a way which is visible to Dima. > > Dima (and I) are fans of POLA. So am I. We are just astonished by different things. I'm astonished that after 2 full years of effort, FS stacking still doesn't work. > Terry wants to punish people for not doing things his way. It's not "Terry's way". I didn't put that comment into vnode_pager.c; I didn't invent the framework which FreeBSD fails to correspond to. And the only "punishment" is a perfectly valid warning. Maybe it should be changed to say "..stale FS code: you will not be able to stack FS's on this FS!". > I think reading 20 page emails is punishment enought w/out have the > FS's break (or whine alot) is overkill. Sure, demand rationale, and then whine when you get it... > > Terry claims to have read the comment in /sys/vm/vnode_pager.c: > > > > /* > > * TODO: > > * Implement VOP_GETPAGES/PUTPAGES interface for filesystems. Will > > * greatly re-simplify the vnode_pager. > > */ > > I don't see anywhere it states that a 'default' VOP_GETPAGES can't be > added in here, vs. a VOP_GETPAGES in every [ local media ] FS. It doesn't say I can't include a uuencoded copy of the human genome database in the damn thing, either, but it would be just as stupid to do that. > That's a total non-sequiter. LFS and NFS have brokeness way beyond the > VOP_GETPAGES stuff. Getting them working require that as well as much > other stuff. The reason they don't work is that their bits have rotted > due to inattention. Software. Does. Not. Mutate. You as much as agree with me when you suggest "So, if you didn't provide patches to *all* existing code then you should be taken out and beat about the head and shoulders with a large noodle." Point to the brokenness. Apply my patches when I provide them in response to your pointing. Agree on a definition of "timely", and make it public. If I do not respond in a timely fashion, back my code out. Pretty damned simple. > > For stackable FS's (which means *NOT* local media FS's) the underlying > > FS below the stack will implement the VOP_{GET|PUT}PAGES by means of > > the bypass. > > So, stacking only applies to non 'local media' FS? Seems like a bad > design if it can't take care of both cases. Feel free to enlighten me as to how I may stack an FFS implementation on top of an EXT2FS implementation. > (BTW, can you describe succintly what a 'local media' FS is in your > terms, so that I'm not making any wrong assumptions?) A file system is stackable if it both provides and consumes the VFS interface. NULLFS is an example of a stackable FS. A file system is not stackable if it provides the VFS interface, but consumes another interface (such as the local OS's VM system). FFS is an example of a non-stackable FS which consumes another interface. A file system is not stackable if it does not provide the VFS interface, even if it consumes the VFS interface. The NFS server is an example of a non-stackable VFS consumer. The FreeBSD system call interface is another example of a non-stackable VFS consumer. Please see section 2.2 of John Heidemann's Master's Thesis for a more in-depth description of "stackable": ftp://ftp.cs.ucla.edu/pub/ficus/heidemann_thesis.ps.gz 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 Mar 8 19:46:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14239 for freebsd-current-outgoing; Sun, 8 Mar 1998 19:46:00 -0800 (PST) (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 TAA14229; Sun, 8 Mar 1998 19:45:52 -0800 (PST) (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 UAA25127; Sun, 8 Mar 1998 20:21:24 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id UAA14280; Sun, 8 Mar 1998 20:21:22 -0700 Date: Sun, 8 Mar 1998 20:21:22 -0700 Message-Id: <199803090321.UAA14280@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: dyson@FreeBSD.ORG, karpen@ocean.campus.luth.se, current@FreeBSD.ORG Subject: Re: Okay, -current should be conditionally safe to use In-Reply-To: <199803090301.UAA15987@usr08.primenet.com> References: <199803080012.TAA00282@dyson.iquest.net> <199803090301.UAA15987@usr08.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ NFS performance ] > > It probably isn't a good idea to use softupdates in production yet. However, > > another interesting thing to try is: > > > > sysctl -w vfs.nfs.async=1 > > > > on the server. This is better (safer) than softupdates, but you *can* > > have data lossage, due to writes not being committed to disk. It is > > a good idea to have a UPS when using the above option. > > Note: it is a technical violation of the NFS protocol specification > for an NFS server to ACK a write which has not been commited to > stable storage. Note: Many commercial OS's have this turned on by default, including SUN at one point. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 20:16:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18220 for freebsd-current-outgoing; Sun, 8 Mar 1998 20:16:23 -0800 (PST) (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 UAA18114 for ; Sun, 8 Mar 1998 20:15:54 -0800 (PST) (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 UAA25399; Sun, 8 Mar 1998 20:56:28 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id UAA14668; Sun, 8 Mar 1998 20:56:26 -0700 Date: Sun, 8 Mar 1998 20:56:26 -0700 Message-Id: <199803090356.UAA14668@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: nate@mt.sri.com (Nate Williams), dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: <199803090344.UAA17601@usr08.primenet.com> References: <199803090300.UAA13920@mt.sri.com> <199803090344.UAA17601@usr08.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Terry wants FS implementors (therefore all FS's) to explicitly write > > > > code for vnode_pagers, rather than having the (potentially buggy) code > > > > used by FS writers. > > > > > > Terry wants local media FS implementors (therefore all non-stackable > > > FS's) to explicitly write code for vnode_pagers as payment for their > > > direct consumption of OS-specific kernel internals. > > > > Same thing, different way of putting it. > > ??? > > Can't you diff "all FS's" and "all non-stackable FS's"? What's the difference? Aren't all FS's stackable? > > Screw the design when it comes to having buggy/non-working FS's. That's > > one of the rules of getting your code committed. If your solution isn't > > complete, then it shouldn't be committed. > > That's BS. I've tried that road before, and the code has been > consistently refused commit. > > I've bowed to (IMO, unreasonable) pressure to get there incrementally, and > now you are bitching that the code's not getting there all at once. Make your increments complete. Incomplete increments don't do anyone any good. > > So, if you didn't provide > > patches to *all* existing code then you should be taken out and beat > > about the head and shoulders with a large noodle. > > I will be *happy* to wield the noodle over the death of LFS, X.25, > and the ISO networking code. Where do I sign up for a noodle? Touche. OK, how about your patches should be for all currently working/used code. > > If you want all the FS's to *require* the code, then write code for all > > of the existing FS in FreeBSD. > > I want them to *eventually* require the code. This is very different > from your characterization of my statements. Right now they *require* the code. If they don't have it, they whine and sometimes misbehave. > > Finally, I disagree with the claim that *all* FS must implement *every* > > vops operation. If so, then the 'stackable' design is broken, since in > > any good design you should have the ability to use a default for common > > operations. > > All FS's do *NOT* have to implement every VOP. All FS's do not even have > to implement VOP_{GET|PUT}PAGES, if they don't want to. If they don't have to, then why do they whine if they don't have it? > > > Terry claims that use of the default vops vector breaks automatic > > > bypass in vfs_init. > > > > Pray tell which existing FS break if you add the code to the default vops? > > None. Which existing FS's break if you add stub functions? None. Which > existing FS's break if you make a modification to make the warning not > fatal, the patch for which was included in my last post? None. So what's the point in the warning then? > > > Dima wants it to work the way it used to, and doesn't see any reason > > > to change the existing code path in a way which is visible to Dima. > > > > Dima (and I) are fans of POLA. > > So am I. We are just astonished by different things. I'm astonished > that after 2 full years of effort, FS stacking still doesn't work. What effort? Yours? I dont see anyone working on the FS stacking effort. > And the only "punishment" is a perfectly valid warning. Maybe it should > be changed to say "..stale FS code: you will not be able to stack FS's > on this FS!". It's violates POLA. A normal user of FreeBSD doesn't have any stacking FS, and he's seeing irrelevant/whiney messages that imply something bad about his system, when in fact there are no problems with his system. (There are potential problems, but if he's writing stackable FS's, then he should be smart enough to figure this out, shouldn't he?) > > > Terry claims to have read the comment in /sys/vm/vnode_pager.c: > > > > > > /* > > > * TODO: > > > * Implement VOP_GETPAGES/PUTPAGES interface for filesystems. Will > > > * greatly re-simplify the vnode_pager. > > > */ > > > > I don't see anywhere it states that a 'default' VOP_GETPAGES can't be > > added in here, vs. a VOP_GETPAGES in every [ local media ] FS. > > It doesn't say I can't include a uuencoded copy of the human genome > database in the damn thing, either, but it would be just as stupid to > do that. In your mind yes. To my mind, no. > > That's a total non-sequiter. LFS and NFS have brokeness way beyond the > > VOP_GETPAGES stuff. Getting them working require that as well as much > > other stuff. The reason they don't work is that their bits have rotted > > due to inattention. > > Software. Does. Not. Mutate. Bits. Rot. Due. To. Changes. Around. Them. > You as much as agree with me when you suggest "So, if you didn't provide > patches to *all* existing code then you should be taken out and beat > about the head and shoulders with a large noodle." They were broken when we got them. Their brokeness continued and was at times made worse due to changes made around them. If they had been used by someone, then they would have been maintained. > > (BTW, can you describe succintly what a 'local media' FS is in your > > terms, so that I'm not making any wrong assumptions?) > > A file system is stackable if it both provides and consumes the VFS > interface. NULLFS is an example of a stackable FS. > > A file system is not stackable if it provides the VFS interface, but > consumes another interface (such as the local OS's VM system). FFS is > an example of a non-stackable FS which consumes another interface. > > A file system is not stackable if it does not provide the VFS interface, > even if it consumes the VFS interface. The NFS server is an example of > a non-stackable VFS consumer. The FreeBSD system call interface is another > example of a non-stackable VFS consumer. Thank you. Nate ps. Even though I am often-times the devil's advocate here, I do appreciate you taking the time to answer my questions. I'm attempting to learn wherever I can, and since FS-101 died I'm learning wherever I can. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 20:38:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22610 for freebsd-current-outgoing; Sun, 8 Mar 1998 20:38:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22578; Sun, 8 Mar 1998 20:38:15 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id UAA29379; Sun, 8 Mar 1998 20:53:01 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd029347; Sun Mar 8 20:53:00 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id UAA17990; Sun, 8 Mar 1998 20:52:39 -0700 (MST) From: Terry Lambert Message-Id: <199803090352.UAA17990@usr08.primenet.com> Subject: Re: Okay, -current should be conditionally safe to use To: nate@mt.sri.com (Nate Williams) Date: Mon, 9 Mar 1998 03:52:39 +0000 (GMT) Cc: tlambert@primenet.com, dyson@FreeBSD.ORG, karpen@ocean.campus.luth.se, current@FreeBSD.ORG In-Reply-To: <199803090321.UAA14280@mt.sri.com> from "Nate Williams" at Mar 8, 98 08:21:22 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 > [ NFS performance ] > > Note: it is a technical violation of the NFS protocol specification > > for an NFS server to ACK a write which has not been commited to > > stable storage. > > Note: Many commercial OS's have this turned on by default, including SUN > at one point. Note: I had already noted that in the part of my note you deannotated. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 20:41:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23122 for freebsd-current-outgoing; Sun, 8 Mar 1998 20:41:44 -0800 (PST) (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 UAA23098 for ; Sun, 8 Mar 1998 20:41:27 -0800 (PST) (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 VAA16658; Sun, 8 Mar 1998 21:49:12 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id VAA18601; Sun, 8 Mar 1998 21:48:41 -0600 Message-ID: <19980308214840.62378@right.PCS> Date: Sun, 8 Mar 1998 21:48:40 -0600 From: Jonathan Lemon To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: Someone needs to re-develop "Softupdates" References: <19980308191111.08309@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <19980308191111.08309@mcs.net>; from Karl Denninger on Mar 03, 1998 at 07:11:11PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mar 03, 1998 at 07:11:11PM -0600, Karl Denninger wrote: > I just read Julian's page. > > What is in the Copyright file, and how Kirk "interprets" it, are two > completely different things. Uh. I just read the copyrights, as well as the email on Julian's web site. Remember that what is binding is the copyright attached to the code, not what some email message says. That out of the way, it seems fairly clear (to me, at least) that the only difference from a standard BSD license is point #4. This only states that any _redistributions_ must include both the source for softupdates, and the source for "the software that uses this software". (read: the kernel itself). So, if either 1) you don't redistribute the software, or 2) you include your entire kernel sources, the clause doesn't affect you. This would affect Sun/BSDI/Whistle (binary licensees only), but not Karl, unless he's selling turnkey systems with custom kernel code that he doesn't want to provide source for. > According to Kirk, if someone wants to use it in a "Production ISP System" > (to cite one of his examples) they need to negotiate a license from him. The copyright does not say that. The copyright is what carries the legal weight, not Kirk's email message, (which I think you are misinterpreting, I believe he was referring to something like BSDI). Can we move on now? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 20:59:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26769 for freebsd-current-outgoing; Sun, 8 Mar 1998 20:59:51 -0800 (PST) (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 UAA26762 for ; Sun, 8 Mar 1998 20:59:49 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id VAA28986; Sun, 8 Mar 1998 21:59:49 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpd028968; Sun Mar 8 21:59:46 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id VAA29017; Sun, 8 Mar 1998 21:59:42 -0700 (MST) From: Terry Lambert Message-Id: <199803090459.VAA29017@usr09.primenet.com> Subject: Re: vnode_pager: *** WARNING *** stale FS code in system To: nate@mt.sri.com (Nate Williams) Date: Mon, 9 Mar 1998 04:59:42 +0000 (GMT) Cc: tlambert@primenet.com, nate@mt.sri.com, dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG In-Reply-To: <199803090356.UAA14668@mt.sri.com> from "Nate Williams" at Mar 8, 98 08:56:26 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 > > Can't you diff "all FS's" and "all non-stackable FS's"? > > What's the difference? Aren't all FS's stackable? No. I addressed this later in the posting to which you are replying. > > > If you want all the FS's to *require* the code, then write code for all > > > of the existing FS in FreeBSD. > > > > I want them to *eventually* require the code. This is very different > > from your characterization of my statements. > > Right now they *require* the code. If they don't have it, they whine > and sometimes misbehave. See the patch in the posting that you initially responded to. I can send it to you directly, by itself, if you want. I have sent it to Mike Smith, but he might be getting gun-shy about now. I wouldn't blame him. > > All FS's do *NOT* have to implement every VOP. All FS's do not even have > > to implement VOP_{GET|PUT}PAGES, if they don't want to. > > If they don't have to, then why do they whine if they don't have it? Because you have not applied the patch? The reason they whine is because you won't be able to stack an FS on top of them that required page management services. For example, a quotafs, which must access a hidden file in the FS it is mounted over. > So what's the point in the warning then? See above. [ ... ] > > And the only "punishment" is a perfectly valid warning. Maybe it should > > be changed to say "..stale FS code: you will not be able to stack FS's > > on this FS!". > > It's violates POLA. A normal user of FreeBSD doesn't have any stacking > FS, and he's seeing irrelevant/whiney messages that imply something bad > about his system, when in fact there are no problems with his system. > (There are potential problems, but if he's writing stackable FS's, then > he should be smart enough to figure this out, shouldn't he?) What if he's downloading binary modules and installing them, expecting them to "just work"? This is not an FS devloper issue. How can I tell from above an FS whether or not the FS below me is a stackable FS, or not? If it is, I can look for the VOP's; if it isn't, how can I know if needed services are provided or not? The short answer is that I need a "kernel mount flag" to tell me, but that's not a complete answer. I also have to fill in VOPs in my vector from the FS's below me, and propagate them up, the more I mount. That still isn't a whole answer, but it's maybe 80% of the way there, and a useful starting point. I'm willing to bow to pressure to get some silence. I've discussed this with Mike Smith, and the console warnings should be going away. They're not useful unless you are stacking FS's, and I haven't provided stacking FS's (yet; I depend on things like veto interfaces and nameifree), so they should be hidden by an #ifdef. > > > That's a total non-sequiter. LFS and NFS have brokeness way beyond the > > > VOP_GETPAGES stuff. Getting them working require that as well as much > > > other stuff. The reason they don't work is that their bits have rotted > > > due to inattention. > > > > Software. Does. Not. Mutate. > > Bits. Rot. Due. To. Changes. Around. Them. Annie. Get. Your. Noodle. Incomplete changes around them should be backed out if they are not addressed in a timely fashion (the standard to which I am being held, and to which I agree, I *should* be held). Part of this came from having nothing after the USL cease-and-desist, and having to get *anything* that would work, and damn the torpedoes, and I respect that part of it. > They were broken when we got them. Their brokeness continued and was at > times made worse due to changes made around them. If they had been used > by someone, then they would have been maintained. You *may* be able to make this argument about LFS, if you are arguing with someone who doesn't understand Margo's papers, or the degree to which the code *was* complete *and* functional. Lack of a full-featured "cleaner" is not broken, in my opinion, it's just active research that has yet to be completed. With the Soft Updates not exporting a "dependency resolver registration interface" (there are reasons for this; I've discussed them with Kirk, and neither one of us has been able to convinve the other), an LFS is about the only way you could build a stacking layer that implemented a VOP_TRANSACT. I would *really* like to play with a VOP_TRANSACT. ;-). You *can't* make that claim about Rick Macklem's NFS code. The original breakage there was the addition of cookies to VOP_READDIR instead of some other implementation. The code *was* functional, as provided. It looks as if it's about to be again, thank god^H^H^HJohn Dyson. [ ... why not all FS's are "stackable" ... ] > Thank you. It was nothing. I cribbed it from Heidemann. He's got broad shoulders. 8-). > ps. Even though I am often-times the devil's advocate here, I do > appreciate you taking the time to answer my questions. I'm attempting > to learn wherever I can, and since FS-101 died I'm learning wherever I > can. :) I understand. The still-birth of the FS-101 was a result of impatience on my part. In a lot of cases, I simply don't have the context in common that I would need to boil things down. That's why I'm always referencing papers. I've taught some University classes, but I'm willing to admit that I wouldn't be good at starting from ground zero and building a reasonable justification. I tend to point at papers that I think would do a much better job of it than the hash I would make of things. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 21:06:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27668 for freebsd-current-outgoing; Sun, 8 Mar 1998 21:06:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA27610 for ; Sun, 8 Mar 1998 21:06:02 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yBulC-0001lo-00; Sun, 8 Mar 1998 21:05:58 -0800 Date: Sun, 8 Mar 1998 21:05:54 -0800 (PST) From: Tom To: Karl Denninger cc: current@FreeBSD.ORG Subject: Re: Someone needs to re-develop "Softupdates" In-Reply-To: <19980308191111.08309@mcs.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 Sun, 8 Mar 1998, Karl Denninger wrote: > I just read Julian's page. > > What is in the Copyright file, and how Kirk "interprets" it, are two > completely different things. > > According to the copyright, using the code as long as it is not resold as > part of a packaged product is perfectly fine. > > According to Kirk, if someone wants to use it in a "Production ISP System" > (to cite one of his examples) they need to negotiate a license from him. > > To use a single word Kirk: NO. > > Your copyright is clear about resale of the code (ie: as part of an embedded > system used for something). However, it says NOTHING about someone wanting > to use the code internally for their own use being restricted based on what > they intend to do *INTERNALLY* with it. > > That's nothing short of incredible, if you ask me. I'm not sure I understand your comments. As I understand it, commercial use of softupdates requires a license which you need to buy from Kirk. Are you concerned about the fogginess of the license document, or paying for a commerical license? > -- > -- > Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin > http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service > | NEW! K56Flex support on ALL modems > Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS > Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 21:06:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27762 for freebsd-current-outgoing; Sun, 8 Mar 1998 21:06:21 -0800 (PST) (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 VAA27757 for ; Sun, 8 Mar 1998 21:06:18 -0800 (PST) (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 VAA13176; Sun, 8 Mar 1998 21:03:55 -0800 (PST) Message-Id: <199803090503.VAA13176@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: nate@mt.sri.com (Nate Williams), dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-reply-to: Your message of "Mon, 09 Mar 1998 04:59:42 GMT." <199803090459.VAA29017@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 21:03:55 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > See the patch in the posting that you initially responded to. I can > send it to you directly, by itself, if you want. I have sent it to > Mike Smith, but he might be getting gun-shy about now. I wouldn't > blame him. Just to clarify on this; I fully intend to commit the patch, but I'm currently behind time on sysinstall-related issues for 2.2.6. -- \\ 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 Mar 8 21:17:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29880 for freebsd-current-outgoing; Sun, 8 Mar 1998 21:17:50 -0800 (PST) (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 VAA29875 for ; Sun, 8 Mar 1998 21:17:48 -0800 (PST) (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 WAA25999; Sun, 8 Mar 1998 22:17:41 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA15531; Sun, 8 Mar 1998 22:17:40 -0700 Date: Sun, 8 Mar 1998 22:17:40 -0700 Message-Id: <199803090517.WAA15531@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: nate@mt.sri.com (Nate Williams), dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: <199803090459.VAA29017@usr09.primenet.com> References: <199803090356.UAA14668@mt.sri.com> <199803090459.VAA29017@usr09.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I want them to *eventually* require the code. This is very different > > > from your characterization of my statements. > > > > Right now they *require* the code. If they don't have it, they whine > > and sometimes misbehave. > > See the patch in the posting that you initially responded to. I responded to a posting by Dima, not by you, so there was no such patch. I was just trying to understand the argument from both sides. > > > All FS's do *NOT* have to implement every VOP. All FS's do not even have > > > to implement VOP_{GET|PUT}PAGES, if they don't want to. > > > > If they don't have to, then why do they whine if they don't have it? > > Because you have not applied the patch? And that patch adds the GET|PUT{PAGES} code into all existing local media FS's, right? Then my argument is now moot. > > It's violates POLA. A normal user of FreeBSD doesn't have any stacking > > FS, and he's seeing irrelevant/whiney messages that imply something bad > > about his system, when in fact there are no problems with his system. > > (There are potential problems, but if he's writing stackable FS's, then > > he should be smart enough to figure this out, shouldn't he?) > > What if he's downloading binary modules and installing them, expecting > them to "just work"? If the binary modules were compiled against FreeBSD, then they wouldn't 'ever' work since FreeBSD is broken in this respect per your arguments. Anyone providing said 'binary' modules would be stilly for providing broken code to users. > How can I tell from above an FS whether or not the FS below me is a > stackable FS, or not? Actually, I was wondering this very question myself? How can I tell if the FS below is stackable? > If it is, I can look for the VOP's; if it isn't, how can I know if > needed services are provided or not? You tell me. > I'm willing to bow to pressure to get some silence. I've discussed > this with Mike Smith, and the console warnings should be going away. Sean Fagan explained to me the crux of your argument off line, and once it was put so plainly and simply to me I agree that what you are doing is *a good thing*. But, trying to wade through the noise has been difficult. In short, you are attempting to make local media FS's the 'base class' for all FS (using C++ vernacular). As Base Classes, they must implement/define *everything* for all classes, and that all other 'stackable' FS's can inherit from the base class. [ NFS and LFS were broken ] > > They were broken when we got them. Their brokeness continued and was at > > times made worse due to changes made around them. If they had been used > > by someone, then they would have been maintained. > > You *may* be able to make this argument about LFS ... > You *can't* make that claim about Rick Macklem's NFS code. Sure I can. Rick has posted some patches to the NFS code that we've integrated, and there are obvious bugs in the way the code originally did things in the 4.4BSD that caused problems. In any case, I'm in agreement with you now. I only wish it were possible to distill the description of what you are saying with a lot less volume. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 21:33:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04125 for freebsd-current-outgoing; Sun, 8 Mar 1998 21:33:27 -0800 (PST) (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 VAA04083 for ; Sun, 8 Mar 1998 21:33:21 -0800 (PST) (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 QAA19293 for ; Mon, 9 Mar 1998 16:03:16 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id QAA00508; Mon, 9 Mar 1998 16:03:16 +1030 (CST) (envelope-from grog) Message-ID: <19980309160316.00609@freebie.lemis.com> Date: Mon, 9 Mar 1998 16:03:16 +1030 From: Greg Lehey To: FreeBSD current users Subject: Latest -current kernel panics on boot 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've just (finally been able to) build and boot a new kernel, but I don't get as far as mounting the root file system. I get a fatal page fault in ufs_ihashget when the swapper tries to mount /dev/wds02a (yup, that's right, and I don't know where it gets it from). It's before the swap partition gets mounted, so I don't have a dump. I wrote down a trace, but I'm assuming that we don't need that level of detail, so I won't type it in unless somebody wants it. Since Mike Smith sent some information about changing /etc/fstab round this morning, I changed my fstab entry from /dev/wd0a / ufs rw 1 1 to /dev/wd0s1a / ufs rw 1 1 My disk is (it turns out) not dedicated (can we get rid of that word "dangerously", please?), so it should require the new version. Here's the fdisk output: === root@freebie (/dev/ttyp1) /home/grog 4 -> fdisk wd0 ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=2485 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2485 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 2504817 (1223 Meg), flag 80 beg: cyl 0/ sector 1/ head 1; end: cyl 1023/ sector 63/ head 15 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: This doesn't seem to be problem, though: it doesn't work either way. The old kernel only works with wd0a, and the new kernel doesn't work with either fstab entry. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 21:44:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06412 for freebsd-current-outgoing; Sun, 8 Mar 1998 21:44:05 -0800 (PST) (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 VAA06353 for ; Sun, 8 Mar 1998 21:43:57 -0800 (PST) (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 VAA13322; Sun, 8 Mar 1998 21:41:57 -0800 (PST) Message-Id: <199803090541.VAA13322@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: FreeBSD current users Subject: Re: Latest -current kernel panics on boot In-reply-to: Your message of "Mon, 09 Mar 1998 16:03:16 +1030." <19980309160316.00609@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 21:41:57 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've just (finally been able to) build and boot a new kernel, but I > don't get as far as mounting the root file system. I get a fatal page > fault in ufs_ihashget when the swapper tries to mount /dev/wds02a > (yup, that's right, and I don't know where it gets it from). It's > before the swap partition gets mounted, so I don't have a dump. I > wrote down a trace, but I'm assuming that we don't need that level of > detail, so I won't type it in unless somebody wants it. What does the 'config' line in your kernel look like? It's possible that some of the static configuration code can't deal with the slice number in the minor. > Since Mike Smith sent some information about changing /etc/fstab round > this morning, I changed my fstab entry from Have you rebuilt/reinstalled /sbin/mount? > This doesn't seem to be problem, though: it doesn't work either way. > The old kernel only works with wd0a, and the new kernel doesn't work > with either fstab entry. You should receive a "changing root device to ..." message after your device probes with the new kernel. -- \\ 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 Mar 8 22:22:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11085 for freebsd-current-outgoing; Sun, 8 Mar 1998 22:11:11 -0800 (PST) (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 WAA10990 for ; Sun, 8 Mar 1998 22:09:45 -0800 (PST) (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 QAA19324; Mon, 9 Mar 1998 16:39:16 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id QAA00704; Mon, 9 Mar 1998 16:39:16 +1030 (CST) (envelope-from grog) Message-ID: <19980309163916.42581@freebie.lemis.com> Date: Mon, 9 Mar 1998 16:39:16 +1030 From: Greg Lehey To: Mike Smith Cc: FreeBSD current users Subject: Re: Latest -current kernel panics on boot References: <19980309160316.00609@freebie.lemis.com> <199803090541.VAA13322@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803090541.VAA13322@dingo.cdrom.com>; from Mike Smith on Sun, Mar 08, 1998 at 09:41:57PM -0800 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 Sun, 8 March 1998 at 21:41:57 -0800, Mike Smith wrote: >> I've just (finally been able to) build and boot a new kernel, but I >> don't get as far as mounting the root file system. I get a fatal page >> fault in ufs_ihashget when the swapper tries to mount /dev/wds02a >> (yup, that's right, and I don't know where it gets it from). It's >> before the swap partition gets mounted, so I don't have a dump. I >> wrote down a trace, but I'm assuming that we don't need that level of >> detail, so I won't type it in unless somebody wants it. > > What does the 'config' line in your kernel look like? It's possible > that some of the static configuration code can't deal with the slice > number in the minor. Yes, I thought of that too. Nothing spectacular: config kernel root on wd0 >> Since Mike Smith sent some information about changing /etc/fstab round >> this morning, I changed my fstab entry from > > Have you rebuilt/reinstalled /sbin/mount? Yup. Complete make world cvsupped this morning (Monday). >> This doesn't seem to be problem, though: it doesn't work either way. >> The old kernel only works with wd0a, and the new kernel doesn't work >> with either fstab entry. > > You should receive a "changing root device to ..." message after your > device probes with the new kernel. That's where it dies. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 22:24:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13091 for freebsd-current-outgoing; Sun, 8 Mar 1998 22:24:36 -0800 (PST) (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 WAA13081 for ; Sun, 8 Mar 1998 22:24:32 -0800 (PST) (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 BAA01046; Mon, 9 Mar 1998 01:42:36 GMT Message-ID: <000301bd4b1d$71d59740$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: "Ollivier Robert" , Subject: Re: page fault while in kernel mode (-current from this morning && softupdates) Date: Sun, 8 Mar 1998 18:28:04 -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 it could be a big help if you could recompile and profile the code in the two cases and seeing what calls are made to the system. -Alfred -----Original Message----- From: Ollivier Robert To: current@FreeBSD.ORG Date: Sunday, March 08, 1998 1:45 PM Subject: Re: page fault while in kernel mode (-current from this morning && softupdates) >According to Andreas Klemm: >> And I got another one: >> >> panic vm_fault: fault on nofault entry, addr: f2d93000 >[...] >> _generic_bcopy >> _softdep_setup_allocindir_page > >Welcome to the club :-) > >This is the same panic as Amancia and I (and now you) are seeing. I can't >find a pattern in this :-( > >It happens for me in two cases: >- rnews batch processing, >- procmail delivering mail into mailboxes. > >The funny part is that I can "make world", "cvs update" and "ctm" without >problem and these stress the filesystems quite a bit compared to >procmail... >-- >Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr >FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 > >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 Mar 8 22:29:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14255 for freebsd-current-outgoing; Sun, 8 Mar 1998 22:29:44 -0800 (PST) (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 WAA14224 for ; Sun, 8 Mar 1998 22:29:42 -0800 (PST) (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 WAA13511; Sun, 8 Mar 1998 22:27:06 -0800 (PST) Message-Id: <199803090627.WAA13511@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: Mike Smith , FreeBSD current users Subject: Re: Latest -current kernel panics on boot In-reply-to: Your message of "Mon, 09 Mar 1998 16:39:16 +1030." <19980309163916.42581@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 22:27:05 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 8 March 1998 at 21:41:57 -0800, Mike Smith wrote: > >> before the swap partition gets mounted, so I don't have a dump. I > >> wrote down a trace, but I'm assuming that we don't need that level of > >> detail, so I won't type it in unless somebody wants it. > > > > What does the 'config' line in your kernel look like? It's possible > > that some of the static configuration code can't deal with the slice > > number in the minor. > > Yes, I thought of that too. Nothing spectacular: > > config kernel root on wd0 *mumble* Where does the trace go back through? Is it still in configure()? > >> This doesn't seem to be problem, though: it doesn't work either way. > >> The old kernel only works with wd0a, and the new kernel doesn't work > >> with either fstab entry. > > > > You should receive a "changing root device to ..." message after your > > device probes with the new kernel. > > That's where it dies. Before or after the message? The message won't get emitted until setroot() is called. (This part of the system is a pile of rubble.) What is the root device that it's nominating? -- \\ 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 Mar 8 22:46:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16583 for freebsd-current-outgoing; Sun, 8 Mar 1998 22:46:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA16567 for ; Sun, 8 Mar 1998 22:46:40 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id HAA08109; Mon, 9 Mar 1998 07:41:54 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199803090641.HAA08109@ocean.campus.luth.se> Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c In-Reply-To: <199803090201.SAA12336@dingo.cdrom.com> from Mike Smith at "Mar 8, 98 06:01:12 pm" To: mike@smith.net.au (Mike Smith) Date: Mon, 9 Mar 1998 07:41:54 +0100 (CET) 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 According to Mike Smith: > > Also, on my other machine I have a SCSI disk for freebsd, and a IDE disk > > for Win95. Computer boots from the ide, and then I use booteasy there to > > boot from the SCSI disk. The SCSI disk is not "dangerously dedicated", > > but it's just one big BSD slice. So... will I need "sd0s1a" on that, > > or just "sd0a"? > > The changes I have made *only* affect the boot device. The remainder > of the "compatability slice" implementation remains. > > Note, however, that when you move to DEVFS, there will not be any sd0[a-h] > nodes *in* /dev/, so you wouldn't be able to mount them even if you > wanted to. Ok, let's see if I got this right. :-) * Only the boot device is affected. ( even when boot != FreeBSD root ) * Above point is only effective until you start using DEVFS. * Dedicated disks ARE affected by this change. * "Dangerously dedicated" disks are NOT affected by this change. How many right? :-) /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 23:16:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA20597 for freebsd-current-outgoing; Sun, 8 Mar 1998 23:16:18 -0800 (PST) (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 XAA20573 for ; Sun, 8 Mar 1998 23:16:15 -0800 (PST) (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 XAA13648; Sun, 8 Mar 1998 23:04:24 -0800 (PST) Message-Id: <199803090704.XAA13648@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mikael Karpberg cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c In-reply-to: Your message of "Mon, 09 Mar 1998 07:41:54 +0100." <199803090641.HAA08109@ocean.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 23:04:23 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to Mike Smith: > > > Also, on my other machine I have a SCSI disk for freebsd, and a IDE disk > > > for Win95. Computer boots from the ide, and then I use booteasy there to > > > boot from the SCSI disk. The SCSI disk is not "dangerously dedicated", > > > but it's just one big BSD slice. So... will I need "sd0s1a" on that, > > > or just "sd0a"? > > > > The changes I have made *only* affect the boot device. The remainder > > of the "compatability slice" implementation remains. > > > > Note, however, that when you move to DEVFS, there will not be any sd0[a-h] > > nodes *in* /dev/, so you wouldn't be able to mount them even if you > > wanted to. > > Ok, let's see if I got this right. :-) > > * Only the boot device is affected. ( even when boot != FreeBSD root ) The device which is passed to the kernel by the bootblocks, ie. the device from which the kernel is loaded, and from which the root filesystem will be loaded. If you are booting with the 'ask for root filesystem' flag, then you are expected to know what is involved. > * Above point is only effective until you start using DEVFS. The current situation more closely models what DEVFS will look like. > * Dedicated disks ARE affected by this change. > * "Dangerously dedicated" disks are NOT affected by this change. I don't use the "dangerously" term. A dedicated disk is one which is not sliced. Dedicated disks are not affected by this change. -- \\ 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 Mar 8 23:21:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA22194 for freebsd-current-outgoing; Sun, 8 Mar 1998 23:21:35 -0800 (PST) (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 XAA22187 for ; Sun, 8 Mar 1998 23:21:33 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id AAA13368; Mon, 9 Mar 1998 00:21:33 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd013346; Mon Mar 9 00:21:29 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id AAA04670; Mon, 9 Mar 1998 00:21:25 -0700 (MST) From: Terry Lambert Message-Id: <199803090721.AAA04670@usr09.primenet.com> Subject: Re: vnode_pager: *** WARNING *** stale FS code in system To: nate@mt.sri.com (Nate Williams) Date: Mon, 9 Mar 1998 07:21:25 +0000 (GMT) Cc: tlambert@primenet.com, nate@mt.sri.com, dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG In-Reply-To: <199803090517.WAA15531@mt.sri.com> from "Nate Williams" at Mar 8, 98 10:17:40 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 > > See the patch in the posting that you initially responded to. > > I responded to a posting by Dima, not by you, so there was no such > patch. I was just trying to understand the argument from both sides. OK. The point is that Dima's argument is based on an assumption that I hadn't meant to imply (but did, in all fairness). > If the binary modules were compiled against FreeBSD, then they wouldn't > 'ever' work since FreeBSD is broken in this respect per your arguments. > Anyone providing said 'binary' modules would be stilly for providing > broken code to users. The actual intent of the Heidemann code is that it would still work. There is a problem here in that linker sets are agregated statically instead of dynamically. Some of this requires both ELF and a change to the way we handle linker sets to fix. Specifically, if you look at Heidemann's requirements, then the decriptor structure ought to be built up using linker sets. I haven't committed this change yet. The issue here is whether you can dynamically extend the contents of linker sets or not, in order to meet Heidemann's design goal of dynamic VOP extension. Pretty much, when the linker set is extended, you need to make a callback that causes the allocated vector for the mount instance to add the VOP. > > If it is, I can look for the VOP's; if it isn't, how can I know if > > needed services are provided or not? > > You tell me. I need to look at the kernel mount flags. This is essentially what I told Poul. THe work needs to be domne in vm_mmap. > > I'm willing to bow to pressure to get some silence. I've discussed > > this with Mike Smith, and the console warnings should be going away. > > Sean Fagan explained to me the crux of your argument off line, and once > it was put so plainly and simply to me I agree that what you are doing > is *a good thing*. But, trying to wade through the noise has been > difficult. Sorry about that. Sean has his head screwed on straight with regard to making the obvious obvious. He's a good translator for this type of thing. Like I said before, I'm no Ronald Reagan (great communicator). As John Dyson put it, I'm a better researcher than contributor. 8-(. > In short, you are attempting to make local media FS's the 'base class' > for all FS (using C++ vernacular). As Base Classes, they must > implement/define *everything* for all classes, and that all other > 'stackable' FS's can inherit from the base class. Yes. This is different from interfaces. which are allowed to be "pure virtual" base classes. I wasn't sure about using OO terminology. 8-(. > > You *can't* make that claim about Rick Macklem's NFS code. > > Sure I can. Rick has posted some patches to the NFS code that we've > integrated, and there are obvious bugs in the way the code originally > did things in the 4.4BSD that caused problems. OK. I agree that there were some endemic problems that Rick solved. The distinction here is beteen code from a "trusted" source and not. Rick was trusted, so the code was assumed OK (may or may not be a "bad" thing, but the difference is between OEM'ed code and trusted code: if it came from 4.4, it's assumed to be "OK" kind of by definition). > In any case, I'm in agreement with you now. I only wish it were > possible to distill the description of what you are saying with a lot > less volume. Sean's a better communicator than I am. I wish I were better, but if I had to make a choice between being a better communicator or what I am, I'd have to (sheepishly) choose what I am. Like the scorpion, and the crossing of the river, it's my nature. Anyway, thanks to Sean... 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 23:27:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23600 for freebsd-current-outgoing; Sun, 8 Mar 1998 23:27:28 -0800 (PST) (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 XAA23594 for ; Sun, 8 Mar 1998 23:27:25 -0800 (PST) (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 AAA26852; Mon, 9 Mar 1998 00:27:16 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id AAA16521; Mon, 9 Mar 1998 00:27:14 -0700 Date: Mon, 9 Mar 1998 00:27:14 -0700 Message-Id: <199803090727.AAA16521@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: nate@mt.sri.com (Nate Williams), dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: <199803090721.AAA04670@usr09.primenet.com> References: <199803090517.WAA15531@mt.sri.com> <199803090721.AAA04670@usr09.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In short, you are attempting to make local media FS's the 'base class' > > for all FS (using C++ vernacular). As Base Classes, they must > > implement/define *everything* for all classes, and that all other > > 'stackable' FS's can inherit from the base class. > > Yes. This is different from interfaces. which are allowed to be "pure > virtual" base classes. I wasn't sure about using OO terminology. 8-(. Bingo. I didn't want to say that for fear of complicating the simple definition. As I understand it, the whole VFS framework is an attempt to OOPify (is that a word) the FS interface. I also think using OO teminology is pretty safe, since most anyone here has done their share of programming in an OOP language. (Now, whether or not they enjoyed it is another story. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 23:33:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26194 for freebsd-current-outgoing; Sun, 8 Mar 1998 23:33:53 -0800 (PST) (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 XAA26160 for ; Sun, 8 Mar 1998 23:33:46 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id XAA00351 for ; Sun, 8 Mar 1998 23:33:43 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Sun, 8 Mar 1998 23:33:43 -0800 (PST) From: Manfred Antar To: current@FreeBSD.ORG Subject: netscape 4.0 fails after make world 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 get this message when trying to start netscape after a just completed make world and new kernel. I rebooted and tried again, same thing : ld.so failed: Undefined symbol "__vt$8stdiobuf" in netscape:/usr/lib/libstdc++.so.2.0 src is current as of 6 p.m. pacific time.The netscape is the FreeBSD version 4.0 not linux 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 Mar 8 23:36:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26600 for freebsd-current-outgoing; Sun, 8 Mar 1998 23:36:02 -0800 (PST) (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 XAA26554 for ; Sun, 8 Mar 1998 23:35:48 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id IAA24591 for current@FreeBSD.ORG; Mon, 9 Mar 1998 08:35:39 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id IAA13788; Mon, 9 Mar 1998 08:20:56 +0100 (CET) (envelope-from roberto) Message-ID: <19980309082056.A13758@keltia.freenix.fr> Date: Mon, 9 Mar 1998 08:20:56 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system Mail-Followup-To: current@FreeBSD.ORG References: <199803090300.UAA13920@mt.sri.com> <199803090344.UAA17601@usr08.primenet.com> <199803090356.UAA14668@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <199803090356.UAA14668@mt.sri.com>; from Nate Williams on Sun, Mar 08, 1998 at 08:56:26PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4121 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Nate Williams: > What's the difference? Aren't all FS's stackable? No. If you stack B on top of A but B calls direct VM functions (like FFS does), than A will not see them and it will screw something up. The purpose of stacking is that every function not implemented in B will be bypassed and executed inside A. > What effort? Yours? I dont see anyone working on the FS stacking > effort. Terry does. I would if I could understand all this. > They were broken when we got them. Their brokeness continued and was at > times made worse due to changes made around them. If they had been used > by someone, then they would have been maintained. Uh ? Using something can be done without knowing anything about it. Nullfs has very interesting uses but you should not have to be able to write the code in order to use it. > appreciate you taking the time to answer my questions. I'm attempting > to learn wherever I can, and since FS-101 died I'm learning wherever I > can. :) Ditto. Terry makes sense here. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 8 23:56:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03120 for freebsd-current-outgoing; Sun, 8 Mar 1998 23:56:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03032 for ; Sun, 8 Mar 1998 23:55:57 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id SAA17901 for current@freebsd.org; Mon, 9 Mar 1998 18:56:20 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803090756.SAA17901@cimlogic.com.au> Subject: HEADS UP: Changes to libc. To: current@FreeBSD.ORG Date: Mon, 9 Mar 1998 18:56:20 +1100 (EST) 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 G'day, I've just committed a bunch of changes to libc that allow it to be built on FreeBSD/Alpha using NetBSD syscalls. This is a non-invasive change with respect to the source for i386, but the makefiles are very different, so a HEADS UP warning is needed. 8-) I've built and re-built this many times so you should assume that it has been tested. Let me know if I've messed up! -- 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 Mar 8 23:57:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03570 for freebsd-current-outgoing; Sun, 8 Mar 1998 23:57:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA03496 for ; Sun, 8 Mar 1998 23:56:55 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yBxQS-0004t7-00; Sun, 8 Mar 1998 23:56:44 -0800 Date: Sun, 8 Mar 1998 23:56:40 -0800 (PST) From: Tom To: Nate Williams cc: John Kelly , Karl Denninger , current@FreeBSD.ORG Subject: Re: Someone needs to re-develop "Softupdates" In-Reply-To: <199803090248.TAA13804@mt.sri.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 Sun, 8 Mar 1998, Nate Williams wrote: > > >According to Kirk, if someone wants to use it in a "Production ISP System" > > >(to cite one of his examples) they need to negotiate a license from him. > > > > > >To use a single word Kirk: NO. > > > > >That's nothing short of incredible, if you ask me. > > > > It's amazing how some of the same people who decry commercializing > > FreeBSD with donor control of funding have no objection to Kirk's > > commercial hooks. > > Sad isn't it.... > > > Score 1 for the GPL. > > The GPL has nothing to do with this. This is simply a commercial entity > that has paid Kirk that would like to not having to re-integrate this > into FreeBSD as changes are made. What commercial entity? I'm guessing that you are refering to Whistle. > Basically, this commercial entity is giving some of it's work to > FreeBSD, and making it 'easier' for Kirk to get money since other > 'commercial' entities who want to use Kirk's work have everything but > the legal license. More are benefiting that just Kirk (money) and Whistle (not having to re-integrate changes). > Sort of a 'big carrot' dangling out in front that they can't legally > obtain. According to my understanding of Kirk's message(s), all commercial entities have to do is step up and buy a license, and they can use SoftUpdates too. > Nate Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 00:44:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18079 for freebsd-current-outgoing; Mon, 9 Mar 1998 00:44:36 -0800 (PST) (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 AAA18029 for ; Mon, 9 Mar 1998 00:44:22 -0800 (PST) (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 IAA21744; Mon, 9 Mar 1998 08:12:24 GMT Date: Mon, 9 Mar 1998 17:12:24 +0900 (JST) From: Michael Hancock To: Nate Williams cc: Terry Lambert , dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: <199803090805.BAA16882@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Mar 1998, Nate Williams wrote: > > I think this is good enough to go forward, but you need to understand that > > with the Heidemann FS stacking framework you can extend the set of VOP's > > in interesting ways. For example, suppose you wanted to implement > > VOP_NEWFEATURE. You could do the following: > > > > Layer1 - Supports it and maps results from one below. > > Layer2 - Doesn't support so does a bypass. > > Layer3 - Supports it and maps results from one below. > > Layer4 - Doesn't support so does a bypass. > > Layer5 - Terminal layer, some support some don't. > > > > I'm not sure traditional OOP can do this and this makes finding good > > analogies difficult. > > Traditional OOP does this right, since you inherit from the class below > you, and not from the base class. If you want to inherit from the base > class, you inherit from it and not a subclass. But do you get the mappings from layer1 and layer3? They both touch the results that finally get to the top. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 00:44:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18092 for freebsd-current-outgoing; Mon, 9 Mar 1998 00:44:38 -0800 (PST) (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 AAA18050 for ; Mon, 9 Mar 1998 00:44:25 -0800 (PST) (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 IAA21631; Mon, 9 Mar 1998 08:01:06 GMT Date: Mon, 9 Mar 1998 17:01:06 +0900 (JST) From: Michael Hancock To: Nate Williams cc: Terry Lambert , dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: <199803090727.AAA16521@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Mar 1998, Nate Williams wrote: > > > In short, you are attempting to make local media FS's the 'base class' > > > for all FS (using C++ vernacular). As Base Classes, they must > > > implement/define *everything* for all classes, and that all other > > > 'stackable' FS's can inherit from the base class. > > > > Yes. This is different from interfaces. which are allowed to be "pure > > virtual" base classes. I wasn't sure about using OO terminology. 8-(. > > Bingo. I didn't want to say that for fear of complicating the simple > definition. As I understand it, the whole VFS framework is an attempt > to OOPify (is that a word) the FS interface. I think this is good enough to go forward, but you need to understand that with the Heidemann FS stacking framework you can extend the set of VOP's in interesting ways. For example, suppose you wanted to implement VOP_NEWFEATURE. You could do the following: Layer1 - Supports it and maps results from one below. Layer2 - Doesn't support so does a bypass. Layer3 - Supports it and maps results from one below. Layer4 - Doesn't support so does a bypass. Layer5 - Terminal layer, some support some don't. I'm not sure traditional OOP can do this and this makes finding good analogies difficult. You probably need to explain things seven different ways before things get clearer, before things click, before things feel right, ... to a wider audience because different people have different ways of perceiving the world. VOP_PUT|GET are pretty important to support given the symbiotic relationship of the FS and the VM system. So it should definitely be supported to full capability of the given local media FS. There are some VOP's that are fundamental to the system and some that aren't. Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 00:45:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18652 for freebsd-current-outgoing; Mon, 9 Mar 1998 00:45:58 -0800 (PST) (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 AAA18603 for ; Mon, 9 Mar 1998 00:45:51 -0800 (PST) (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 BAA27145; Mon, 9 Mar 1998 01:05:58 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id BAA16882; Mon, 9 Mar 1998 01:05:56 -0700 Date: Mon, 9 Mar 1998 01:05:56 -0700 Message-Id: <199803090805.BAA16882@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Michael Hancock Cc: Nate Williams , Terry Lambert , dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: References: <199803090727.AAA16521@mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > In short, you are attempting to make local media FS's the 'base class' > > > > for all FS (using C++ vernacular). As Base Classes, they must > > > > implement/define *everything* for all classes, and that all other > > > > 'stackable' FS's can inherit from the base class. > > > > > > Yes. This is different from interfaces. which are allowed to be "pure > > > virtual" base classes. I wasn't sure about using OO terminology. 8-(. > > > > Bingo. I didn't want to say that for fear of complicating the simple > > definition. As I understand it, the whole VFS framework is an attempt > > to OOPify (is that a word) the FS interface. > > I think this is good enough to go forward, but you need to understand that > with the Heidemann FS stacking framework you can extend the set of VOP's > in interesting ways. For example, suppose you wanted to implement > VOP_NEWFEATURE. You could do the following: > > Layer1 - Supports it and maps results from one below. > Layer2 - Doesn't support so does a bypass. > Layer3 - Supports it and maps results from one below. > Layer4 - Doesn't support so does a bypass. > Layer5 - Terminal layer, some support some don't. > > I'm not sure traditional OOP can do this and this makes finding good > analogies difficult. Traditional OOP does this right, since you inherit from the class below you, and not from the base class. If you want to inherit from the base class, you inherit from it and not a subclass. > VOP_PUT|GET are pretty important to support given the symbiotic > relationship of the FS and the VM system. So it should definitely be > supported to full capability of the given local media FS. There are > some VOP's that are fundamental to the system and some that aren't. I understand that now. (I can't do anything about it at this point in time, but understanding is a step in the right direction. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 01:32:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01955 for freebsd-current-outgoing; Mon, 9 Mar 1998 01:22:52 -0800 (PST) (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 BAA01801 for ; Mon, 9 Mar 1998 01:22:35 -0800 (PST) (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 TAA19455; Mon, 9 Mar 1998 19:34:40 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id TAA01248; Mon, 9 Mar 1998 19:34:40 +1030 (CST) (envelope-from grog) Message-ID: <19980309193440.42123@freebie.lemis.com> Date: Mon, 9 Mar 1998 19:34:40 +1030 From: Greg Lehey To: Mike Smith Cc: FreeBSD current users Subject: Re: Latest -current kernel panics on boot References: <19980309163916.42581@freebie.lemis.com> <199803090627.WAA13511@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803090627.WAA13511@dingo.cdrom.com>; from Mike Smith on Sun, Mar 08, 1998 at 10:27:05PM -0800 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 Sun, 8 March 1998 at 22:27:05 -0800, Mike Smith wrote: >> On Sun, 8 March 1998 at 21:41:57 -0800, Mike Smith wrote: >>>> before the swap partition gets mounted, so I don't have a dump. I >>>> wrote down a trace, but I'm assuming that we don't need that level of >>>> detail, so I won't type it in unless somebody wants it. >>> >>> What does the 'config' line in your kernel look like? It's possible >>> that some of the static configuration code can't deal with the slice >>> number in the minor. >> >> Yes, I thought of that too. Nothing spectacular: >> >> config kernel root on wd0 > > *mumble* Where does the trace go back through? Is it still in > configure()? No, the kernel is running. It's process 0 (swapper). ffs_vget+0x27 ufs_root+0x1c xxx_vfs_root_fdtab+0x1f (yup, that's the name) main+0x9a begin+0x4a >>>> This doesn't seem to be problem, though: it doesn't work either way. >>>> The old kernel only works with wd0a, and the new kernel doesn't work >>>> with either fstab entry. >>> >>> You should receive a "changing root device to ..." message after your >>> device probes with the new kernel. >> >> That's where it dies. > > Before or after the message? The message won't get emitted until > setroot() is called. (This part of the system is a pile of rubble.) Damn. I'm pretty sure one message appeared. I'm no longer so sure that it's the one you're looking for. When I rebooted with the old kernel, ISTR that it was different. > What is the root device that it's nominating? As I said, /dev/wd0s2a. My notes say "changing to /dev/wd0s2a", but those were things which made sense to me at the time. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 01:34:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05828 for freebsd-current-outgoing; Mon, 9 Mar 1998 01:34:48 -0800 (PST) (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 BAA05772; Mon, 9 Mar 1998 01:34:36 -0800 (PST) (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 KAA14965; Mon, 9 Mar 1998 10:34:17 +0100 (CET) To: jak@cetlink.net (John Kelly) cc: "Jordan K. Hubbard" , Karl Denninger , current@FreeBSD.ORG Subject: Re: Someone needs to re-develop "Softupdates" In-reply-to: Your message of "Mon, 09 Mar 1998 03:04:36 GMT." <35045a62.136823612@mail.cetlink.net> Date: Mon, 09 Mar 1998 10:34:17 +0100 Message-ID: <14963.889436057@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <35045a62.136823612@mail.cetlink.net>, John Kelly writes: >> >>If either of you start this shit up again I'll have you both off the >>mailing lists and banned from posting faster than you can say "cheese". >> >>First and only warning. >> >> Jordan > >I'm posting on a topic which has an interrelationship to another topic >which I agreed to let die -- and I did. But this is a new topic. > >Apparently you don't condone the idea of freedom of speech. Or >perhaps you just don't like me personally. But if you boot me out, >who will be next? Where will it stop? You have freedom of speech, but not freedom of obnoxiation. Get lost. -- 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 Mon Mar 9 01:46:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07681 for freebsd-current-outgoing; Mon, 9 Mar 1998 01:46:22 -0800 (PST) (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 BAA07660; Mon, 9 Mar 1998 01:46:16 -0800 (PST) (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 AAA14131; Mon, 9 Mar 1998 00:52:39 -0800 (PST) Message-Id: <199803090852.AAA14131@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: stable@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: *HEADS UP* Correction to previous postings. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Mar 1998 00:52:38 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please note that in the recent postings regarding the changes to the fashion in which the root filesystem is located and mounted there has been a fundamental factual error on my part. This error *will* cause users with dedicated disks serious problems, unless they adopt the same procedure require by non-dedicated disk users. The error in this case was the assumption that partitions on a dedicated disk were handled as though they were truly equivalent to the compatability slice entries. This is not correct; rather they appear as though they were in the first slice on the disk. In short, then: - /sbin/mount must be updated on all systems. - /etc/fstab for all systems should be updated to reflect the change as indicated by mount at boot time. This change can occur when convenient, as mount will search for the correct filesystem in the compatability case. Changes to correct the earlier mistakes have been committed. Please accept my apologies for the previous misinformation, and the inconvenience that this has caused by being rushed. -- \\ 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 Mar 9 02:21:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14069 for freebsd-current-outgoing; Mon, 9 Mar 1998 02:21:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14003; Mon, 9 Mar 1998 02:21:01 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA22972; Mon, 9 Mar 1998 21:20:15 +1100 Date: Mon, 9 Mar 1998 21:20:15 +1100 From: Bruce Evans Message-Id: <199803091020.VAA22972@godzilla.zeta.org.au> To: mike@smith.net.au, stable@FreeBSD.ORG Subject: Re: *HEADS UP* Correction to previous postings. Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Please note that in the recent postings regarding the changes to the >fashion in which the root filesystem is located and mounted there has >been a fundamental factual error on my part. > >This error *will* cause users with dedicated disks serious problems, >unless they adopt the same procedure require by non-dedicated disk >users. > >The error in this case was the assumption that partitions on a dedicated >disk were handled as though they were truly equivalent to the >compatability slice entries. A correct assumption. >This is not correct; rather they appear >as though they were in the first slice on the disk. Not with normal slice naming. The first slice (s1) doesn't exist on dangerously dedicated disks. Rev.1.88 of autoconf.c just breaks support for dangerously dedicated disks. Rev.1.87 was correct in this areas, except it spells COMPATIBILITY_SLICE as 0. I think the recent bug reports were for non-dangerously dedicated disks. Disks that have a valid partition table, with one big DOS partition covering the MBR, are not dedicated, just dangerous. Does sysinstall create these? Anyway, the update procedure for non-dangerously-dedicated disks applies to these disks. Dangerously dedicated disks are ones with no DOS partition table. These are created using normal BSD tools (start with a blank disk and run disklabel -B on it). The boot blocks contain a special invalid DOS partition table that is recognized as invalid. Alternatively, an all-zero DOS partition table is recognized as invalid. Someone broke the bugfeature of disklabel -B of overwriting the DOS partition table, so dangerously dedicated disks are not as easy to create as they used to be. Mine have an all-zero DOS partition table. The update procedure for dangerously-dedicated disks is to back out rev.1.88 of autoconf.c. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 02:55:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA19159 for freebsd-current-outgoing; Mon, 9 Mar 1998 02:55:25 -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 CAA19154 for ; Mon, 9 Mar 1998 02:55:21 -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 NAA19844; Mon, 9 Mar 1998 13:38:29 +0300 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 NAA03211; Mon, 9 Mar 1998 13:47:13 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199803091047.NAA03211@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Nate Williams cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-reply-to: Your message of "Sun, 08 Mar 1998 22:17:40 MST." <199803090517.WAA15531@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Mar 1998 13:47:12 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: > In short, you are attempting to make local media FS's the 'base class' > for all FS (using C++ vernacular). As Base Classes, they must > implement/define *everything* for all classes, and that all other > 'stackable' FS's can inherit from the base class. Stacking layers *is not* an analogy of inheritance. Stacking layers is analogy of event-passing in GUI, or "filters" in Unix pipes, or some such. Every widget, of course, must handle every possible event. But some widget are designed especially to dispatch events to other widgets. This dispatching is a way of handling. Both widgets are finished stuff, unlike a derived class without a base class. Or, as example of a layer, consider a program that read a text file, handle lines started with '#', and print other lines in slightly modified form to output. It is a finished program too. You cannot say that it inherit from the program which read and handle its output. But there is real inheritance in filesystems. For example, FIFOs in FFS, FIFOs in NFS, FIFOs in CD9660, etc. is all derived from a generic FIFO. Terry wants that all filesystems handle GETPAGES/PUTPAGES. This is fine. I simple don't like that he put his 'default' junk in zillion filesystems, instead of put it in an appropriate base class. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 03:05:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20684 for freebsd-current-outgoing; Mon, 9 Mar 1998 03:05:52 -0800 (PST) (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 DAA20655 for ; Mon, 9 Mar 1998 03:05:43 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id MAA19332 for ; Mon, 9 Mar 1998 12:08:26 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 9 Mar 1998 12:08:25 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: Wrong root device 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! I believe there's something wrong here: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Mon Mar 9 11:32:43 MET 1998 root@abial.warman.com.pl:/usr/src/sys/compile/TUNE ..... BIOS Geometries: 0:026a7f3f 0..618=619 cylinders, 0..127=128 heads, 1..63=63 sectors 1:03371f3f 0..823=824 cylinders, 0..31=32 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: tun0 attached bpf: lo0 attached Considering FFS root f/s. changing root device to wd0s3a ^^^^^^ wd0s1: type 0x6, start 63, end = 1024127, size 1024065 : OK wd0s2: type 0xa5, start 1024128, end = 3064319, size 2040192 : OK ^^^^^ (this is my root partition) wd0s3: type 0x63, start 3064320, end = 4080383, size 1016064 : OK wd0s4: type 0x5, start 4080384, end = 4991615, size 911232 : OK wd0s5: type 0x6, start 4080447, end = 4991615, size 911169 : OK wd1s1: type 0x81, start 63, end = 133055, size 132993 : OK wd1s2: type 0xa5, start 133056, end = 1663199, size 1530144 : OK wd1s1: type 0x81, start 63, end = 133055, size 132993 : OK wd1s2: type 0xa5, start 133056, end = 1663199, size 1530144 : OK 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 Mon Mar 9 03:18:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA22569 for freebsd-current-outgoing; Mon, 9 Mar 1998 03:18:17 -0800 (PST) (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 DAA22564 for ; Mon, 9 Mar 1998 03:18:15 -0800 (PST) (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 JAA22565 for ; Mon, 9 Mar 1998 09:59:17 GMT Date: Mon, 9 Mar 1998 18:59:17 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: <19980309082056.A13758@keltia.freenix.fr> 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, 9 Mar 1998, Ollivier Robert wrote: > > What effort? Yours? I dont see anyone working on the FS stacking > > effort. I started recently. Mike Smith committed some glue recently. The next round of patches will give some immediate gratification. People have been working on stacking in our tree since April 97 as far as I can tell and have made some progress. I think BSDI has spent quite a bit of time with FS stacking too. What I found surprising is that no one put a higher priority on some fundamental stuff like releasing memory and lock state at the same layer as they were acquired. Imagine trying to map a returning vpp that was vrele'd, or worse vgone'd, before it reached your layer. Kirk says that this is one of the first things that should be done. Regularizing wasn't done when the VFS layer was inserted in the middle because the pre-VFS code was written that way and I guess the various people working on it found it expedient to just leave it the way it was. It wasn't as much of an issue in pre-VFS days. I'm working on this now for the most visible offenders. My next round of patches will fix the dvp argument rele behavior of VOP_CREATE, VOP_MKNOD, VOP_MKDIR, and VOP_SYMLINK. My initial target was just VOP_CREATE, but my list has grown as I discovered dependencies. So far lock state doesn't look like a problem to fix either, but I'll tackle it later after all the rele behavior has been fixed for all offending VOPs. I'm looking for special cases while working on this sweep. This divide and conquer grunt work has paid off in other ways, I've found a missing vput in DEVFS's symlink implementation and let Julian know. Terry's argument for making nameidata "reflexive" is the same issue. Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 04:00:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26575 for freebsd-current-outgoing; Mon, 9 Mar 1998 04:00:23 -0800 (PST) (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 EAA26567 for ; Mon, 9 Mar 1998 04:00:16 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id FAA24909; Mon, 9 Mar 1998 05:39:43 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id FAA00245; Mon, 9 Mar 1998 05:39:42 -0600 (CST) Message-ID: <19980309053942.36537@mcs.net> Date: Mon, 9 Mar 1998 05:39:42 -0600 From: Karl Denninger To: John Kelly Cc: current@FreeBSD.ORG Subject: Re: Someone needs to re-develop "Softupdates" References: <19980308191111.08309@mcs.net> <35034f2e.134015736@mail.cetlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <35034f2e.134015736@mail.cetlink.net>; from John Kelly on Mon, Mar 09, 1998 at 02:14:48AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 09, 1998 at 02:14:48AM +0000, John Kelly wrote: > On Sun, 8 Mar 1998 19:11:11 -0600, Karl Denninger > wrote: > > >According to Kirk, if someone wants to use it in a "Production ISP System" > >(to cite one of his examples) they need to negotiate a license from him. > > > >To use a single word Kirk: NO. > > >That's nothing short of incredible, if you ask me. > > It's amazing how some of the same people who decry commercializing > FreeBSD with donor control of funding have no objection to Kirk's > commercial hooks. > > Score 1 for the GPL. > > -- > Browser war over, Mozilla now free. I have no problem with HONEST representation of a license or copyright. I have a SERIOUS problem with a copyright which says "Use this all you want, but if you embed it in something, you have to give away source to that something", when that is NOT what the author means. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 04:00:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26581 for freebsd-current-outgoing; Mon, 9 Mar 1998 04:00:26 -0800 (PST) (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 EAA26569 for ; Mon, 9 Mar 1998 04:00:18 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id FAA25114; Mon, 9 Mar 1998 05:47:57 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id FAA00324; Mon, 9 Mar 1998 05:47:57 -0600 (CST) Message-ID: <19980309054757.46674@mcs.net> Date: Mon, 9 Mar 1998 05:47:57 -0600 From: Karl Denninger To: Jonathan Lemon Cc: current@FreeBSD.ORG Subject: Re: Someone needs to re-develop "Softupdates" References: <19980308191111.08309@mcs.net> <19980308214840.62378@right.PCS> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980308214840.62378@right.PCS>; from Jonathan Lemon on Sun, Mar 08, 1998 at 09:48:40PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 08, 1998 at 09:48:40PM -0600, Jonathan Lemon wrote: > On Mar 03, 1998 at 07:11:11PM -0600, Karl Denninger wrote: > > I just read Julian's page. > > > > What is in the Copyright file, and how Kirk "interprets" it, are two > > completely different things. > > Uh. I just read the copyrights, as well as the email on Julian's web > site. Remember that what is binding is the copyright attached to the > code, not what some email message says. > > That out of the way, it seems fairly clear (to me, at least) that the > only difference from a standard BSD license is point #4. This only > states that any _redistributions_ must include both the source for > softupdates, and the source for "the software that uses this software". > (read: the kernel itself). > > So, if either 1) you don't redistribute the software, or 2) you include > your entire kernel sources, the clause doesn't affect you. > > This would affect Sun/BSDI/Whistle (binary licensees only), but not > Karl, unless he's selling turnkey systems with custom kernel code > that he doesn't want to provide source for. > > > > According to Kirk, if someone wants to use it in a "Production ISP System" > > (to cite one of his examples) they need to negotiate a license from him. > > The copyright does not say that. The copyright is what carries the > legal weight, not Kirk's email message, (which I think you are > misinterpreting, I believe he was referring to something like BSDI). > > Can we move on now? Sure. But I find it disingenuous at best to claim one thing in a legal document and then another somewhere else. Jordan has made his views known on myself and our organization here. That's fine. I won't bother any of the fine "Core" people any longer, nor post here any longer, nor will the donation which was sitting on my desk and due to go out (quite seriously) go anywhere but the paper shredder. And no, Jordan, it didn't have strings attached. Mr. Dyson, please contact me. Assuming that your latest NFS fixes actually do fix the problems we've had with NFS, you're entitled to *ALL* of what was going to go to the FreeBSD effort - as a *PERSONAL* donation. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 04:15:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29885 for freebsd-current-outgoing; Mon, 9 Mar 1998 04:15:09 -0800 (PST) (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 EAA29880 for ; Mon, 9 Mar 1998 04:15:03 -0800 (PST) (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 NAA15732; Mon, 9 Mar 1998 13:13:18 +0100 (CET) To: Karl Denninger cc: John Kelly , current@FreeBSD.ORG Subject: Re: Someone needs to re-develop "Softupdates" In-reply-to: Your message of "Mon, 09 Mar 1998 05:39:42 CST." <19980309053942.36537@mcs.net> Date: Mon, 09 Mar 1998 13:13:18 +0100 Message-ID: <15730.889445598@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl, and everybody else. Kirk is for all I know not on this mailing-list, if you want to discuss >HIS< copyright & conditions, please send him email. We're currently doing some major things to -current, please stop abusing the current@ mailing list for this kind of irrelevant noise, we need it for more important matters. And before you start replying: Kirks code is NOT in -current, you have the choice to use it WITH current, but just as we don't entertain XFree86 discussions here, any discussion about the licensing on kirks files is NOT WELCOME HERE! I have already long time ago had to drop out of hackers@ because it took too much of my time to read it. Do not force me to be the first -core member to leave -current, OK ??? Poul-Henning In message <19980309053942.36537@mcs.net>, Karl Denninger writes: > >I have no problem with HONEST representation of a license or copyright. > >I have a SERIOUS problem with a copyright which says "Use this all you want, >but if you embed it in something, you have to give away source to that >something", when that is NOT what the author means. > >-- >-- >Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin -- 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 Mon Mar 9 04:16:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA00378 for freebsd-current-outgoing; Mon, 9 Mar 1998 04:16:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA00373 for ; Mon, 9 Mar 1998 04:16:49 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA27209; Mon, 9 Mar 1998 23:12:46 +1100 Date: Mon, 9 Mar 1998 23:12:46 +1100 From: Bruce Evans Message-Id: <199803091212.XAA27209@godzilla.zeta.org.au> To: abial@nask.pl, freebsd-current@FreeBSD.ORG Subject: Re: Wrong root device Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I believe there's something wrong here: >... >changing root device to wd0s3a > ^^^^^^ >wd0s1: type 0x6, start 63, end = 1024127, size 1024065 : OK >wd0s2: type 0xa5, start 1024128, end = 3064319, size 2040192 : OK >^^^^^ (this is my root partition) The printf() at the end of setroot() in autoconf.c is broken. dsname() should be used to format the device name correctly in all cases. This error is harmless except for the confusion it causes. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 05:04:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA06738 for freebsd-current-outgoing; Mon, 9 Mar 1998 05:04:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA06733 for ; Mon, 9 Mar 1998 05:04:36 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-5-15.camtech.net.au [203.28.0.175]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id XAA07490 for ; Mon, 9 Mar 1998 23:31:52 +1030 (CST) Message-ID: <3503E87D.E639921D@camtech.net.au> Date: Mon, 09 Mar 1998 23:32:53 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: CTM src-cur.3278 fails to apply Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This has happened on two machines now (the only two I've tried!) Working on Expecting Global MD5 <48d1ed0699103fde8ff1c945b1055e76> Reference Global MD5 <48d1ed0699103fde8ff1c945b1055e76> DR: TODO-2.1 doesn't exist. DR: gnu/lib/libgmp/mpf/tests doesn't exist. DR: gnu/lib/libgmp/mpf doesn't exist. DR: gnu/lib/libgmp/mpq/tests doesn't exist. DR: gnu/lib/libgmp/mpq doesn't exist. DR: gnu/lib/libgmp/mpz/tests doesn't exist. DR: gnu/lib/libgmp/mpz doesn't exist. ctm: exit(80) matte: {45} -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 05:11:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08353 for freebsd-current-outgoing; Mon, 9 Mar 1998 05:11:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from techunix.technion.ac.il (mellon@techunix.technion.ac.il [132.68.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08343 for ; Mon, 9 Mar 1998 05:11:41 -0800 (PST) (envelope-from mellon@techunix.technion.ac.il) Received: (from mellon@localhost) by techunix.technion.ac.il (8.8.7/8.8.5) id PAA24145; Mon, 9 Mar 1998 15:11:31 +0200 (IST) Message-ID: <19980309151131.44045@techunix.technion.ac.il> Date: Mon, 9 Mar 1998 15:11:31 +0200 From: Anatoly Vorobey To: current@FreeBSD.ORG Subject: Re: CTM src-cur.3278 fails to apply References: <3503E87D.E639921D@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <3503E87D.E639921D@camtech.net.au>; from Matthew Thyer on Mon, Mar 09, 1998 at 11:32:53PM +1030 X-Disclaimer: I was young, I needed the money! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You, Matthew Thyer, were spotted writing this on Mon, Mar 09, 1998 at 11:32:53PM +1030: > This has happened on two machines now (the only two I've tried!) > > Working on > Expecting Global MD5 <48d1ed0699103fde8ff1c945b1055e76> > Reference Global MD5 <48d1ed0699103fde8ff1c945b1055e76> > DR: TODO-2.1 doesn't exist. > DR: gnu/lib/libgmp/mpf/tests doesn't exist. > DR: gnu/lib/libgmp/mpf doesn't exist. > DR: gnu/lib/libgmp/mpq/tests doesn't exist. > DR: gnu/lib/libgmp/mpq doesn't exist. > DR: gnu/lib/libgmp/mpz/tests doesn't exist. > DR: gnu/lib/libgmp/mpz doesn't exist. > ctm: exit(80) The same here. Those directories are supposed to be obsolete; probably your base delta didn't bring them in for some reason. Just create them to keep ctm happy and let it delete them. Have a nice day, Anatoly. P.S. I _did_ have TODO-2.1 though. -- Anatoly Vorobey, mellon@pobox.com http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 05:11:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08363 for freebsd-current-outgoing; Mon, 9 Mar 1998 05:11:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08347 for ; Mon, 9 Mar 1998 05:11:44 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.8/8.8.8) with ESMTP id OAA15998 for ; Mon, 9 Mar 1998 14:11:27 +0100 (MET) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.8/8.8.5) with ESMTP id OAA25465 for ; Mon, 9 Mar 1998 14:11:26 +0100 (CET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id OAA06717 for ; Mon, 9 Mar 1998 14:11:24 +0100 (CET) From: Andre Albsmeier Message-Id: <199803091311.OAA00918@intern> Subject: Re: CTM src-cur.3278 fails to apply In-Reply-To: <3503E87D.E639921D@camtech.net.au> from Matthew Thyer at "Mar 9, 98 11:32:53 pm" To: thyerm@camtech.net.au (Matthew Thyer) Date: Mon, 9 Mar 1998 14:11:17 +0100 (CET) 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 > This has happened on two machines now (the only two I've tried!) > > Working on > Expecting Global MD5 <48d1ed0699103fde8ff1c945b1055e76> > Reference Global MD5 <48d1ed0699103fde8ff1c945b1055e76> > DR: TODO-2.1 doesn't exist. > DR: gnu/lib/libgmp/mpf/tests doesn't exist. > DR: gnu/lib/libgmp/mpf doesn't exist. > DR: gnu/lib/libgmp/mpq/tests doesn't exist. > DR: gnu/lib/libgmp/mpq doesn't exist. > DR: gnu/lib/libgmp/mpz/tests doesn't exist. > DR: gnu/lib/libgmp/mpz doesn't exist. > ctm: exit(80) > matte: {45} Glad to see that someone else got this also. However, I built the whole /usr/src from scratch starting with src-cur.2700A.gz and src-cur.3278.gz could be applied without problems ... -Andre -- HP-UGs: The Microsoft Windows(tm) of the Unix(tm) world. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 05:20:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09722 for freebsd-current-outgoing; Mon, 9 Mar 1998 05:20:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09709 for ; Mon, 9 Mar 1998 05:20:34 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-5-15.camtech.net.au [203.28.0.175]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id XAA08629; Mon, 9 Mar 1998 23:44:19 +1030 (CST) Message-ID: <3503EB6B.A5F1696@camtech.net.au> Date: Mon, 09 Mar 1998 23:45:23 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Andre Albsmeier , current@FreeBSD.ORG Subject: Re: CTM src-cur.3278 fails to apply References: <199803091311.OAA00918@intern> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just did: mkdir -p gnu/lib/libgmp/mpf/tests mkdir -p gnu/lib/libgmp/mpq/tests mkdir -p gnu/lib/libgmp/mpz/tests from /usr/src Andre Albsmeier wrote: > > > This has happened on two machines now (the only two I've tried!) > > > > Working on > > Expecting Global MD5 <48d1ed0699103fde8ff1c945b1055e76> > > Reference Global MD5 <48d1ed0699103fde8ff1c945b1055e76> > > DR: TODO-2.1 doesn't exist. > > DR: gnu/lib/libgmp/mpf/tests doesn't exist. > > DR: gnu/lib/libgmp/mpf doesn't exist. > > DR: gnu/lib/libgmp/mpq/tests doesn't exist. > > DR: gnu/lib/libgmp/mpq doesn't exist. > > DR: gnu/lib/libgmp/mpz/tests doesn't exist. > > DR: gnu/lib/libgmp/mpz doesn't exist. > > ctm: exit(80) > > matte: {45} > > Glad to see that someone else got this also. However, I built > the whole /usr/src from scratch starting with src-cur.2700A.gz > and src-cur.3278.gz could be applied without problems ... > > -Andre > > -- > HP-UGs: The Microsoft Windows(tm) of the Unix(tm) world. -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 05:21:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10011 for freebsd-current-outgoing; Mon, 9 Mar 1998 05:21:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from techunix.technion.ac.il (mellon@techunix.technion.ac.il [132.68.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09993 for ; Mon, 9 Mar 1998 05:21:33 -0800 (PST) (envelope-from mellon@techunix.technion.ac.il) Received: (from mellon@localhost) by techunix.technion.ac.il (8.8.7/8.8.5) id PAA26092; Mon, 9 Mar 1998 15:21:27 +0200 (IST) Message-ID: <19980309152125.08053@techunix.technion.ac.il> Date: Mon, 9 Mar 1998 15:21:25 +0200 From: Anatoly Vorobey To: current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system References: <199803090300.UAA13920@mt.sri.com> <199803090344.UAA17601@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199803090344.UAA17601@usr08.primenet.com>; from Terry Lambert on Mon, Mar 09, 1998 at 03:44:12AM +0000 X-Disclaimer: I was young, I needed the money! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Probably a silly question, but still: You, Terry Lambert, were spotted writing this on Mon, Mar 09, 1998 at 03:44:12AM +0000: > > (BTW, can you describe succintly what a 'local media' FS is in your > > terms, so that I'm not making any wrong assumptions?) > > A file system is stackable if it both provides and consumes the VFS > interface. NULLFS is an example of a stackable FS. > > A file system is not stackable if it provides the VFS interface, but > consumes another interface (such as the local OS's VM system). FFS is > an example of a non-stackable FS which consumes another interface. > > A file system is not stackable if it does not provide the VFS interface, > even if it consumes the VFS interface. The NFS server is an example of > a non-stackable VFS consumer. The FreeBSD system call interface is another > example of a non-stackable VFS consumer. What about the NFS as a whole? It's both a provider and a consumer of VFS. Does it mean it's a stackable FS? (forgetting for a moment the networking details; e.g. export and mount a local filesystem for proof of concept). And if it does, how does it manage to exist if you're saying a lot of work has to be done to make stackable FSs possible? Another question: which OSes _today_ provide for stackable file systems? Not FreeBSD, apparently not Linux or Solaris. NT has got "filesystem filters" kind of drivers which stack above the FS (and on each other if needed) - this is neat and often useful - but hasn't got stackable filesystems IIRC. A third question: can you give a (few?) example(s?) of hypothetical useful stackable file systems, besides NULLFS? Thanks in advance for your patience. -- Anatoly Vorobey, mellon@pobox.com http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 05:29:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10849 for freebsd-current-outgoing; Mon, 9 Mar 1998 05:29:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10844 for ; Mon, 9 Mar 1998 05:29:49 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-5-15.camtech.net.au [203.28.0.175]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id XAA09621; Mon, 9 Mar 1998 23:57:12 +1030 (CST) Message-ID: <3503EE6B.D8B9A29B@camtech.net.au> Date: Mon, 09 Mar 1998 23:58:11 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Anatoly Vorobey CC: current@FreeBSD.ORG Subject: Re: CTM src-cur.3278 fails to apply References: <3503E87D.E639921D@camtech.net.au> <19980309151131.44045@techunix.technion.ac.il> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I thought someone would spot my missing TODO-2.1 directory. That was my mistake. I acidentally/absentmindedly removed it the other day on seeing it was empty. Anatoly Vorobey wrote: > > You, Matthew Thyer, were spotted writing this on Mon, Mar 09, 1998 at 11:32:53PM +1030: > > This has happened on two machines now (the only two I've tried!) > > > > Working on > > Expecting Global MD5 <48d1ed0699103fde8ff1c945b1055e76> > > Reference Global MD5 <48d1ed0699103fde8ff1c945b1055e76> > > DR: TODO-2.1 doesn't exist. > > DR: gnu/lib/libgmp/mpf/tests doesn't exist. > > DR: gnu/lib/libgmp/mpf doesn't exist. > > DR: gnu/lib/libgmp/mpq/tests doesn't exist. > > DR: gnu/lib/libgmp/mpq doesn't exist. > > DR: gnu/lib/libgmp/mpz/tests doesn't exist. > > DR: gnu/lib/libgmp/mpz doesn't exist. > > ctm: exit(80) > > The same here. Those directories are supposed to be obsolete; > probably your base delta didn't bring them in for some reason. > Just create them to keep ctm happy and let it delete them. > > Have a nice day, > Anatoly. > > P.S. I _did_ have TODO-2.1 though. > > -- > Anatoly Vorobey, > mellon@pobox.com http://pobox.com/~mellon/ > "Angels can fly because they take themselves lightly" - G.K.Chesterton > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 05:40:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA12207 for freebsd-current-outgoing; Mon, 9 Mar 1998 05:40:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12200 for ; Mon, 9 Mar 1998 05:40:22 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id HAA28908; Mon, 9 Mar 1998 07:40:01 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <3503EE6B.D8B9A29B@camtech.net.au> References: <3503E87D.E639921D@camtech.net.au> <19980309151131.44045@techunix.technion.ac.il> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 9 Mar 1998 07:39:52 -0600 To: Matthew Thyer From: Richard Wackerbarth Subject: Re: CTM src-cur.3278 fails to apply Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:28 AM -0600 3/9/98, Matthew Thyer wrote: >I thought someone would spot my missing TODO-2.1 directory. >That was my mistake. I acidentally/absentmindedly removed it the >other day on seeing it was empty. WARNING: If you are using CTM to maintain a tree, you MUST NOT remove ANYTHING unless you take responsibility for fixing it at some later time. CTM "owns" the tree and you should treat it as if it were read-only. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 05:50:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13543 for freebsd-current-outgoing; Mon, 9 Mar 1998 05:50:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13520 for ; Mon, 9 Mar 1998 05:50:20 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-5-15.camtech.net.au [203.28.0.175]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id AAA11203; Tue, 10 Mar 1998 00:17:49 +1030 (CST) Message-ID: <3503F351.B1A13393@camtech.net.au> Date: Tue, 10 Mar 1998 00:19:05 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Richard Wackerbarth CC: current@FreeBSD.ORG Subject: Re: CTM src-cur.3278 fails to apply References: <3503E87D.E639921D@camtech.net.au> <19980309151131.44045@techunix.technion.ac.il> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I know. I cant believe I was so stupid. I was thinking that CTM might have failed in some way when I removed the obviously obsolete directory but now CTM has proved itself by complaining about my tampering. The other errors requiring: mkdir -p gnu/lib/libgmp/mpf/tests mkdir -p gnu/lib/libgmp/mpq/tests mkdir -p gnu/lib/libgmp/mpz/tests from /usr/src were not as a result of my tampering. So CTM is not infallible! Any explanation as to what went wrong ? Richard Wackerbarth wrote: > > At 7:28 AM -0600 3/9/98, Matthew Thyer wrote: > >I thought someone would spot my missing TODO-2.1 directory. > >That was my mistake. I acidentally/absentmindedly removed it the > >other day on seeing it was empty. > > WARNING: If you are using CTM to maintain a tree, you MUST NOT > remove ANYTHING unless you take responsibility for fixing > it at some later time. > CTM "owns" the tree and you should treat it as if it were > read-only. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 06:12:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16700 for freebsd-current-outgoing; Mon, 9 Mar 1998 06:12:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16695 for ; Mon, 9 Mar 1998 06:12:16 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id IAA29039; Mon, 9 Mar 1998 08:05:27 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <3503F351.B1A13393@camtech.net.au> References: <3503E87D.E639921D@camtech.net.au> <19980309151131.44045@techunix.technion.ac.il> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 9 Mar 1998 08:05:29 -0600 To: Matthew Thyer From: Richard Wackerbarth Subject: Re: CTM src-cur.3278 fails to apply Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:49 AM -0600 3/9/98, Matthew Thyer wrote: >Yes, I know. > >I cant believe I was so stupid. > >I was thinking that CTM might have failed in some way when >I removed the obviously obsolete directory but now CTM has >proved itself by complaining about my tampering. > >The other errors requiring: > >mkdir -p gnu/lib/libgmp/mpf/tests >mkdir -p gnu/lib/libgmp/mpq/tests >mkdir -p gnu/lib/libgmp/mpz/tests >from /usr/src > >were not as a result of my tampering. > >So CTM is not infallible! OBJECTION! You have admitted that you deleted one directory. Are you sure that you did not do something that caused other empty directories to disappear? > >Any explanation as to what went wrong ? Chi: {3} zgrep "CTM" * | grep "gnu/lib/libgmp/mpf/tests" src-cur.3200xEmpty.gz:CTMDM gnu/lib/libgmp/mpf/tests 900 900 775 src-cur.3278.gz:CTMDR gnu/lib/libgmp/mpf/tests Chi: {4} Well, I can only say that CTM did not delete these directories. As others have noted, just applying the deltas in sequence works. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 06:32:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20390 for freebsd-current-outgoing; Mon, 9 Mar 1998 06:32:45 -0800 (PST) (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 GAA20383 for ; Mon, 9 Mar 1998 06:32:37 -0800 (PST) (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 QAA13526 for ; Mon, 9 Mar 1998 16:32:22 +0200 (EET) 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 QAA16429 for ; Mon, 9 Mar 1998 16:32:20 +0200 (EET) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.8.8/8.8.8/8.Who.Cares) with UUCP id QAA14685 for current@freebsd.org; Mon, 9 Mar 1998 16:15:51 +0200 (EET) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id PAA19494; Mon, 9 Mar 1998 15:54:17 +0200 (EET) (envelope-from archer) Message-ID: <19980309155416.46524@carrier.kiev.ua> Date: Mon, 9 Mar 1998 15:54:16 +0200 From: Alexander Litvin To: current@FreeBSD.ORG Subject: What does that mean? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for bothering you... I just tried 'tail ' and got "Segmentation fault". On the console: spec_getpages: I/O read failure: (error code=0) size: 4096, resid: 0, a_count: 3586, valid: 0x0 nread: 4096, reqpage: 1, pindex: 21, pcount: 1 vm_fault: pager input (probably hardware) error, PID 18023 failure Mar 9 15:48:51 grape /kernel: pid 18023 (tail), uid 0: exited on signal 11 The second attempt to issue the same command succeded. Is it really hardware-related, or... CURRENT of yesterday. --- "Truth is stranger than fiction, because fiction has to make sense." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 07:37:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29965 for freebsd-current-outgoing; Mon, 9 Mar 1998 07:37:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from itesec.hsc.fr (root@itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29959 for ; Mon, 9 Mar 1998 07:36:55 -0800 (PST) (envelope-from pb@hsc.fr) Received: from mars.hsc.fr (pb@mars.hsc.fr [192.70.106.44]) by itesec.hsc.fr (8.8.8/8.8.5/itesec-1.10-nospam) with ESMTP id PAA01185; Mon, 9 Mar 1998 15:50:37 +0100 (MET) Received: (from pb@localhost) by mars.hsc.fr (8.8.5/8.8.5/pb-19970301) id PAA19565; Mon, 9 Mar 1998 15:49:36 +0100 (MET) Message-ID: <19980309154936.XU19721@mars.hsc.fr> Date: Mon, 9 Mar 1998 15:49:36 +0100 From: Pierre.Beyssac@hsc.fr (Pierre Beyssac) To: rkw@dataplex.net (Richard Wackerbarth) Cc: thyerm@camtech.net.au (Matthew Thyer), current@FreeBSD.ORG Subject: Re: CTM src-cur.3278 fails to apply References: <3503E87D.E639921D@camtech.net.au> <19980309151131.44045@techunix.technion.ac.il> X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 In-Reply-To: ; from Richard Wackerbarth on Mar 9, 1998 08:05:29 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Richard Wackerbarth: > At 7:49 AM -0600 3/9/98, Matthew Thyer wrote: > >The other errors requiring: > > > >mkdir -p gnu/lib/libgmp/mpf/tests > >mkdir -p gnu/lib/libgmp/mpq/tests > >mkdir -p gnu/lib/libgmp/mpz/tests > >from /usr/src > > OBJECTION! You have admitted that you deleted one directory. > Are you sure that you did not do something that caused other > empty directories to disappear? Just one more data point: the exact same thing happened to me. I started CTM around September 1997, and I'm absolutely sure I didn't mess up with anything in libgmp ever since. Like Matthew I had to do the above "mkdir -p" to get the patch to apply (then I got my surprise with the whole bunch of stuff it was deleting, that's the combination of all this which prompted me to ask the list if everything was ok with the deletions). It's possible there was a minor sync problem between the complete CTM archive I started from (I believe it was 3000 or 3100) and the source tree. I'll have a look at home if I still have it lying around (I doubt it). I'm not sure it's worth the bother to have a closer look at where the problem might come from, unless it happens again in the future. Again, I'm mentioning this as just one more data point in case it can help, I'm not complaining. On the whole, CTM is a very reliable way to receive updates. -- Pierre.Beyssac@hsc.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 08:23:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06337 for freebsd-current-outgoing; Mon, 9 Mar 1998 08:23:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06306; Mon, 9 Mar 1998 08:23:11 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id IAA07384; Mon, 9 Mar 1998 08:23:01 -0800 (PST) (envelope-from jdp) Message-Id: <199803091623.IAA07384@austin.polstra.com> To: root@mantar.slip.netcom.com, peter@FreeBSD.ORG Subject: Re: netscape 4.0 fails after make world In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Mon, 09 Mar 1998 08:23:00 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Manfred Antar wrote: > I get this message when trying to start netscape after a just completed > make world and new kernel. I rebooted and tried again, same thing : > > ld.so failed: Undefined symbol "__vt$8stdiobuf" in > netscape:/usr/lib/libstdc++.so.2.0 Peter, this looks like it's probably related to the recent multi-gcc changes: kerouac$ nm /usr/lib/libstdc++.so.2.0 | grep stdiobuf 00000c50 T __._8stdiobuf 00000c08 T ___8stdiobufP7__sFILE 00001124 T ___8stdiobufRC8stdiobuf 000010f4 T ___as__8stdiobufRC8stdiobuf 0002f7a0 D __vt.8stdiobuf ^ | GCC must change its name mangling between ELF and a.out after all. :-( John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 08:50:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10331 for freebsd-current-outgoing; Mon, 9 Mar 1998 08:50:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from techunix.technion.ac.il (mellon@techunix.technion.ac.il [132.68.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10173 for ; Mon, 9 Mar 1998 08:49:36 -0800 (PST) (envelope-from mellon@techunix.technion.ac.il) Received: (from mellon@localhost) by techunix.technion.ac.il (8.8.7/8.8.5) id SAA01941; Mon, 9 Mar 1998 18:48:46 +0200 (IST) Message-ID: <19980309184844.22239@techunix.technion.ac.il> Date: Mon, 9 Mar 1998 18:48:44 +0200 From: Anatoly Vorobey To: Richard Wackerbarth Cc: current@FreeBSD.ORG Subject: Re: CTM src-cur.3278 fails to apply References: <3503E87D.E639921D@camtech.net.au> <19980309151131.44045@techunix.technion.ac.il> <3503F351.B1A13393@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Richard Wackerbarth on Mon, Mar 09, 1998 at 08:05:29AM -0600 X-Disclaimer: I was young, I needed the money! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard, You, Richard Wackerbarth, were spotted writing this on Mon, Mar 09, 1998 at 08:05:29AM -0600: > OBJECTION! You have admitted that you deleted one directory. > Are you sure that you did not do something that caused other > empty directories to disappear? Well, I'm sure I didn't, and I got the same mistakes. I built my tree anew a few weeks ago by starting from 3200xEmpty and applying all deltas since then. I've never even entered libgmp before ;) > >Any explanation as to what went wrong ? > > Chi: {3} zgrep "CTM" * | grep "gnu/lib/libgmp/mpf/tests" > src-cur.3200xEmpty.gz:CTMDM gnu/lib/libgmp/mpf/tests 900 900 775 > src-cur.3278.gz:CTMDR gnu/lib/libgmp/mpf/tests > Chi: {4} > > Well, I can only say that CTM did not delete these directories. Can you check the same about mpq and mpz? I don't have the deltas anymore. > As others have noted, just applying the deltas in sequence works. Well, you can't apply them not in sequence (unless perhaps with -F which I didn't use), and still several people got the same mistake. Note that I'm by no means accusing you; in fact I appreciate your work in producing CTM deltas a lot. Thanks! ;) -- Anatoly Vorobey, mellon@pobox.com http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 08:55:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11523 for freebsd-current-outgoing; Mon, 9 Mar 1998 08:55:47 -0800 (PST) (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 IAA11514 for ; Mon, 9 Mar 1998 08:55:41 -0800 (PST) (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 JAA00493; Mon, 9 Mar 1998 09:48:49 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA19175; Mon, 9 Mar 1998 09:48:47 -0700 Date: Mon, 9 Mar 1998 09:48:47 -0700 Message-Id: <199803091648.JAA19175@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Michael Hancock Cc: Nate Williams , Terry Lambert , dima@tejblum.dnttm.rssi.ru, current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: References: <199803090805.BAA16882@mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I think this is good enough to go forward, but you need to understand that > > > with the Heidemann FS stacking framework you can extend the set of VOP's > > > in interesting ways. For example, suppose you wanted to implement > > > VOP_NEWFEATURE. You could do the following: > > > > > > Layer1 - Supports it and maps results from one below. > > > Layer2 - Doesn't support so does a bypass. > > > Layer3 - Supports it and maps results from one below. > > > Layer4 - Doesn't support so does a bypass. > > > Layer5 - Terminal layer, some support some don't. > > > > > > I'm not sure traditional OOP can do this and this makes finding good > > > analogies difficult. > > > > Traditional OOP does this right, since you inherit from the class below > > you, and not from the base class. If you want to inherit from the base > > class, you inherit from it and not a subclass. > > But do you get the mappings from layer1 and layer3? They both touch the > results that finally get to the top. If you want them to, then yes. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 09:46:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18990 for freebsd-current-outgoing; Mon, 9 Mar 1998 09:46:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from techunix.technion.ac.il (mellon@techunix.technion.ac.il [132.68.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18972 for ; Mon, 9 Mar 1998 09:46:41 -0800 (PST) (envelope-from mellon@techunix.technion.ac.il) Received: (from mellon@localhost) by techunix.technion.ac.il (8.8.7/8.8.5) id TAA12507; Mon, 9 Mar 1998 19:46:02 +0200 (IST) Message-ID: <19980309194602.38788@techunix.technion.ac.il> Date: Mon, 9 Mar 1998 19:46:02 +0200 From: Anatoly Vorobey To: Nate Williams Cc: current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system References: <199803090805.BAA16882@mt.sri.com> <199803091648.JAA19175@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199803091648.JAA19175@mt.sri.com>; from Nate Williams on Mon, Mar 09, 1998 at 09:48:47AM -0700 X-Disclaimer: I was young, I needed the money! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You, Nate Williams, were spotted writing this on Mon, Mar 09, 1998 at 09:48:47AM -0700: > > > Traditional OOP does this right, since you inherit from the class below > > > you, and not from the base class. If you want to inherit from the base > > > class, you inherit from it and not a subclass. > > > > But do you get the mappings from layer1 and layer3? They both touch the > > results that finally get to the top. > > If you want them to, then yes. So, does the stacking layer support multiple inheritance? :) Have a good one, Anatoly. P.S. In fact, the VFS framework (more precisely, one of its predecessors, Sun's vnode system) is mentioned in at least one book on Java as an example to what pains these poor C programmers must go in order to create OOP-like FS interface, and how easily you would do that in Java ;) -- Anatoly Vorobey, mellon@pobox.com http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 09:49:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19400 for freebsd-current-outgoing; Mon, 9 Mar 1998 09:49:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley63.res.iastate.edu (friley63.res.iastate.edu [129.186.189.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19390 for ; Mon, 9 Mar 1998 09:48:55 -0800 (PST) (envelope-from ccsanady@friley63.res.iastate.edu) Received: from friley63.res.iastate.edu (loopback [127.0.0.1]) by friley63.res.iastate.edu (8.8.8/8.8.5) with ESMTP id LAA00499 for ; Mon, 9 Mar 1998 11:48:46 -0600 (CST) Message-Id: <199803091748.LAA00499@friley63.res.iastate.edu> To: freebsd-current@FreeBSD.ORG Reply-To: ccsanady@iastate.edu Subject: Filesystem recovery procedures (please help..) Date: Mon, 09 Mar 1998 11:48:46 -0600 From: Patrick Hartling Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After recent recently trying to install the cam patches, I seemed to have been left with a system that simply would not boot. It would get to the place where it mounts root, and then ti would hang. I have tried new kernels, cam kernels, recent kernels, old generic kernels, all without luck. Anyways, I finally just went to reinstall(upgrade) to fix the problems. Unfortunately, somehow, the install disk seems to have toasted the disklabels on both of my disks with very little effort. :( It did leave the bios partitions intact though. Can anyone please tell me how to go about recovering? Will I need to manually grovel the disk for this information? I also have ccds that contain my home dir, so I would like these back as well. I unfortunately do not have real recent backups, or a way of making them. Thanks, Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 09:51:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19922 for freebsd-current-outgoing; Mon, 9 Mar 1998 09:51:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19857 for ; Mon, 9 Mar 1998 09:51:06 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id LAA00876; Mon, 9 Mar 1998 11:50:46 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <19980309184844.22239@techunix.technion.ac.il> References: ; from Richard Wackerbarth on Mon, Mar 09, 1998 at 08:05:29AM -0600 <3503E87D.E639921D@camtech.net.au> <19980309151131.44045@techunix.technion.ac.il> <3503F351.B1A13393@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 9 Mar 1998 11:48:24 -0600 To: Anatoly Vorobey From: Richard Wackerbarth Subject: Culprit Found -- (Re: CTM src-cur.3278 fails to apply) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:48 AM -0600 3/9/98, Anatoly Vorobey wrote: >Richard, > >You, Richard Wackerbarth, were spotted writing this on Mon, Mar 09, 1998 >at 08:05:29AM -0600: > >> OBJECTION! You have admitted that you deleted one directory. >> Are you sure that you did not do something that caused other >> empty directories to disappear? > >Well, I'm sure I didn't, and I got the same mistakes. I built my >tree anew a few weeks ago by starting from 3200xEmpty and applying >all deltas since then. I've never even entered libgmp before ;) >> As others have noted, just applying the deltas in sequence works. > >Well, you can't apply them not in sequence (unless perhaps with -F >which I didn't use), and still several people got the same mistake. You are applying the wrong meaning to my statement. My intent is that if you do nothing other than apply the deltas, it works. >Note that I'm by no means accusing you; in fact I appreciate your >work in producing CTM deltas a lot. Thanks! ;) I have found the culprit. "make cleandir" , when executed in gnu/libs does the following (among other things) rm -f libmp.so.*.* libmp_pic.a rm -rf /pub/FreeBSD/FreeBSD-current/src/gnu/lib/libmp/mpz /pub/FreeBSD/FreeBSD-current/src/gnu/lib/libmp/mpz rm -f .depend rm -f /pub/FreeBSD/FreeBSD-current/src/gnu/lib/libmp/GRTAGS /pub/FreeBSD/FreeBSD-current/src/gnu/lib/libmp/GTAGS I assure you that the CTM generator didn't execute that command. However, I suspect that you may have caused it, or something similar, to get executed. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 09:54:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20660 for freebsd-current-outgoing; Mon, 9 Mar 1998 09:54:53 -0800 (PST) (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 JAA20641 for ; Mon, 9 Mar 1998 09:54:43 -0800 (PST) (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 SAA16791; Mon, 9 Mar 1998 18:54:18 +0100 (CET) To: Anatoly Vorobey cc: Nate Williams , current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-reply-to: Your message of "Mon, 09 Mar 1998 19:46:02 +0200." <19980309194602.38788@techunix.technion.ac.il> Date: Mon, 09 Mar 1998 18:54:18 +0100 Message-ID: <16789.889466058@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980309194602.38788@techunix.technion.ac.il>, Anatoly Vorobey writ >P.S. In fact, the VFS framework (more precisely, one of its >predecessors, Sun's vnode system) is mentioned in at least one >book on Java as an example to what pains these poor C programmers >must go in order to create OOP-like FS interface, and how easily >you would do that in Java ;) booting kernel.jav... -- 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 Mon Mar 9 10:42:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00628 for freebsd-current-outgoing; Mon, 9 Mar 1998 10:42:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00573; Mon, 9 Mar 1998 10:42:25 -0800 (PST) (envelope-from bartol@salk.edu) Received: from dale.salk.edu (dale [198.202.70.112]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id KAA27353; Mon, 9 Mar 1998 10:42:24 -0800 (PST) Date: Mon, 9 Mar 1998 10:42:24 -0800 (PST) From: Tom Bartol To: dyson@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Feedback on NFS in -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 Thank you, thank you, thank you, John!!! Your recent changes to NFS have corrected the problems we had with compiling linux binaries on NFS mounted filesystems!!! The performance seems to have improved as well (just my first impression, I haven't run our benchmarks yet). One million thanks!!! Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 10:50:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02490 for freebsd-current-outgoing; Mon, 9 Mar 1998 10:50:35 -0800 (PST) (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 KAA02423 for ; Mon, 9 Mar 1998 10:50:18 -0800 (PST) (envelope-from dyson@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id NAA04002; Mon, 9 Mar 1998 13:43:21 -0500 (EST) (envelope-from dyson) Message-Id: <199803091843.NAA04002@dyson.iquest.net> Subject: Re: What does that mean? In-Reply-To: <19980309155416.46524@carrier.kiev.ua> from Alexander Litvin at "Mar 9, 98 03:54:16 pm" To: archer@lucky.net (Alexander Litvin) Date: Mon, 9 Mar 1998 13:43:21 -0500 (EST) Cc: current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Alexander Litvin said: > Sorry for bothering you... > > I just tried 'tail ' and got "Segmentation fault". On the > console: > > spec_getpages: I/O read failure: (error code=0) > size: 4096, resid: 0, a_count: 3586, valid: 0x0 > nread: 4096, reqpage: 1, pindex: 21, pcount: 1 > vm_fault: pager input (probably hardware) error, PID 18023 failure > Mar 9 15:48:51 grape /kernel: pid 18023 (tail), uid 0: exited on signal 11 > > The second attempt to issue the same command succeded. > > Is it really hardware-related, or... > It is likely a bug that I have created. I work on it 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 Mon Mar 9 10:53:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03161 for freebsd-current-outgoing; Mon, 9 Mar 1998 10:53:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03051; Mon, 9 Mar 1998 10:52:50 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id LAA22790; Mon, 9 Mar 1998 11:51:00 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id LAA10150; Mon, 9 Mar 1998 11:50:56 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199803091850.LAA10150@panzer.plutotech.com> Subject: Re: Feedback on NFS in -current In-Reply-To: from Tom Bartol at "Mar 9, 98 10:42:24 am" To: bartol@salk.edu (Tom Bartol) Date: Mon, 9 Mar 1998 11:50:56 -0700 (MST) Cc: dyson@FreeBSD.ORG, freebsd-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 Tom Bartol wrote... > > Thank you, thank you, thank you, John!!! > > Your recent changes to NFS have corrected the problems we had with > compiling linux binaries on NFS mounted filesystems!!! The performance > seems to have improved as well (just my first impression, I haven't run > our benchmarks yet). > > One million thanks!!! I agree. I was having trouble with doing compiles over NFS as well, and that seems to be fixed. (objects were being generated with no symbol names, so the linker couldn't resolve functions...) Thanks John! Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 11:02:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05428 for freebsd-current-outgoing; Mon, 9 Mar 1998 11:02:44 -0800 (PST) (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 LAA05375; Mon, 9 Mar 1998 11:02:27 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id LAA01454; Mon, 9 Mar 1998 11:02:05 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803091902.LAA01454@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" cc: bartol@salk.edu (Tom Bartol), dyson@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Feedback on NFS in -current In-reply-to: Your message of "Mon, 09 Mar 1998 11:50:56 MST." <199803091850.LAA10150@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Mar 1998 11:02:04 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did a simple xemacs compile which used to freeze my Pentium 133 and the system survived the compile!! Tnks! Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 11:07:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06516 for freebsd-current-outgoing; Mon, 9 Mar 1998 11:07:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06498 for ; Mon, 9 Mar 1998 11:07:35 -0800 (PST) (envelope-from gallatin@grasshopper.cs.duke.edu) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.8.8/8.8.8) id NAA00363; Mon, 9 Mar 1998 13:56:37 -0500 (EST) (envelope-from gallatin) Date: Mon, 9 Mar 1998 13:56:37 -0500 (EST) Message-Id: <199803091856.NAA00363@grasshopper.cs.duke.edu> From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: current@FreeBSD.ORG Subject: panic: bremfree: removing a buffer when not on a queue X-Mailer: VM 6.31 under 20.2 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a recent kernel (cvsup at about 9PM EST 3/8/98), I'm getting the above panic when untarring a file located in a filesystem NFSv3 mounted from a Digital UNIX 4.0b fileserver into a directory on the same filesystem. The stack trace is: (kgdb) where #0 boot (howto=256) at ../../kern/kern_shutdown.c:296 #1 0xf0118d37 in panic ( fmt=0xf013054a "bremfree: removing a buffer when not on a queue") at ../../kern/kern_shutdown.c:436 #2 0xf01305de in bremfree (bp=0xf3503e44) at ../../kern/vfs_bio.c:265 #3 0xf01313a6 in vfs_bio_awrite (bp=0xf3503e44) at ../../kern/vfs_bio.c:955 #4 0xf0136c46 in vinvalbuf (vp=0xf5ef4360, flags=1, cred=0xf0dbd300, p=0xf5e8dac0, slpflag=0, slptimeo=0) at ../../kern/vfs_subr.c:621 #5 0xf01597dc in nfs_vinvalbuf (vp=0xf5ef4360, flags=1, cred=0xf0dbd300, p=0xf5e8dac0, intrflg=1) at ../../nfs/nfs_bio.c:920 #6 0xf0158dee in nfs_write (ap=0xf5ea8ee8) at ../../nfs/nfs_bio.c:644 #7 0xf013d577 in vn_write (fp=0xf0f99a00, uio=0xf5ea8f30, cred=0xf0dbd300) at vnode_if.h:331 #8 0xf012090b in write (p=0xf5e8dac0, uap=0xf5ea8f84) at ../../kern/sys_generic.c:268 #9 0xf01cfc0f in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 294912, tf_esi = 10240, tf_ebp = -272640504, tf_isp = -169177132, tf_ebx = 8192, tf_edx = 518406, tf_ecx = 10240, tf_eax = 4, tf_trapno = 7, tf_err = 7, tf_eip = 226373, tf_cs = 31, tf_eflags = 518, tf_esp = -272640848, tf_ss = 39}) at ../../i386/i386/trap.c:994 #10 0x37445 in ?? () #11 0xb4cd in ?? () #12 0xdeaf in ?? () #13 0x107e in ?? () The FreeBSD client is a 300Mhz PII, and is connected to the fileserver via a 100Mb full-duplx switched network. The only unusual thing about my configuration is that soft-updates are enabled; but I've been seeing panics with nfs_vinvalbuf() on the stack for quite a while -- usually when compiling hello_world.c, removing it, and building it again. ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 11:11:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07791 for freebsd-current-outgoing; Mon, 9 Mar 1998 11:11:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (archer@burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07701; Mon, 9 Mar 1998 11:11:10 -0800 (PST) (envelope-from archer@burka.carrier.kiev.ua) Received: (from archer@localhost) by burka.carrier.kiev.ua (8.8.8/8.Who.Cares) id VAA26615 for ; Mon, 9 Mar 1998 21:10:54 +0200 (EET) Message-ID: <19980309211054.40322@burka.carrier.kiev.ua> Date: Mon, 9 Mar 1998 21:10:54 +0200 From: Alexander Litvin To: dyson@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: What does that mean? References: <19980309155416.46524@carrier.kiev.ua> <199803091843.NAA04002@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199803091843.NAA04002@dyson.iquest.net>; from John S. Dyson on Mon, Mar 09, 1998 at 01:43:21PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 09, 1998 at 01:43:21PM -0500, John S. Dyson wrote: > Alexander Litvin said: > > Sorry for bothering you... > > > > I just tried 'tail ' and got "Segmentation fault". On the > > console: > > > > spec_getpages: I/O read failure: (error code=0) > > size: 4096, resid: 0, a_count: 3586, valid: 0x0 > > nread: 4096, reqpage: 1, pindex: 21, pcount: 1 > > vm_fault: pager input (probably hardware) error, PID 18023 failure > > Mar 9 15:48:51 grape /kernel: pid 18023 (tail), uid 0: exited on signal 11 > > > > The second attempt to issue the same command succeded. > > > > Is it really hardware-related, or... > > > It is likely a bug that I have created. I work on it NOW. Just to add a bit more (don't know, may be it helps): I've played with that wierd thing a bit. Actually, the same thing happened a few times -- irregularly, but each time with the tail (though it should be just coincidense). The machine was makeworlding at the same time. Then, after a few such seg.faults tail once again reported "Segmentation fault", but didn't return to shell. And machine gradually frose (e.g., I was able to login at one console, but when I typed 'ps' -- it didn't work, then 'make world' stopped to compile, then...), I was able to switch consoles, and to drop to DDB, but that's all. > -- > 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. --- Don't get mad, get interest. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 11:46:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17041 for freebsd-current-outgoing; Mon, 9 Mar 1998 11:46:03 -0800 (PST) (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 LAA16983 for ; Mon, 9 Mar 1998 11:45:51 -0800 (PST) (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 MAA01506; Mon, 9 Mar 1998 12:19:01 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA19904; Mon, 9 Mar 1998 12:18:59 -0700 Date: Mon, 9 Mar 1998 12:18:59 -0700 Message-Id: <199803091918.MAA19904@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: Anatoly Vorobey , Nate Williams , current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: <16789.889466058@critter.freebsd.dk> References: <19980309194602.38788@techunix.technion.ac.il> <16789.889466058@critter.freebsd.dk> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >P.S. In fact, the VFS framework (more precisely, one of its > >predecessors, Sun's vnode system) is mentioned in at least one > >book on Java as an example to what pains these poor C programmers > >must go in order to create OOP-like FS interface, and how easily > >you would do that in Java ;) > > booting kernel.jav... Be still my computer. (Literally. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 11:49:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18110 for freebsd-current-outgoing; Mon, 9 Mar 1998 11:49:22 -0800 (PST) (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 LAA18027; Mon, 9 Mar 1998 11:48:58 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id LAA13226; Mon, 9 Mar 1998 11:48:37 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Mon, 9 Mar 1998 11:48:37 -0800 (PST) From: Manfred Antar To: John Polstra cc: peter@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: netscape 4.0 fails after make world In-Reply-To: <199803091623.IAA07384@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Mar 1998, John Polstra wrote: > In article , > Manfred Antar wrote: > > I get this message when trying to start netscape after a just completed > > make world and new kernel. I rebooted and tried again, same thing : > > > > ld.so failed: Undefined symbol "__vt$8stdiobuf" in > > netscape:/usr/lib/libstdc++.so.2.0 > > Peter, this looks like it's probably related to the recent multi-gcc > changes: > > kerouac$ nm /usr/lib/libstdc++.so.2.0 | grep stdiobuf > 00000c50 T __._8stdiobuf > 00000c08 T ___8stdiobufP7__sFILE > 00001124 T ___8stdiobufRC8stdiobuf > 000010f4 T ___as__8stdiobufRC8stdiobuf > 0002f7a0 D __vt.8stdiobuf > ^ > | > > GCC must change its name mangling between ELF and a.out after all. :-( > After a new make world last night it works now. Manfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 11:59:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20977 for freebsd-current-outgoing; Mon, 9 Mar 1998 11:59:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20933 for ; Mon, 9 Mar 1998 11:59:24 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA20501; Mon, 9 Mar 1998 12:59:09 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd020427; Mon Mar 9 12:59:01 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id MAA23552; Mon, 9 Mar 1998 12:58:57 -0700 (MST) From: Terry Lambert Message-Id: <199803091958.MAA23552@usr05.primenet.com> Subject: Re: vnode_pager: *** WARNING *** stale FS code in system To: dima@tejblum.dnttm.rssi.ru (Dmitrij Tejblum) Date: Mon, 9 Mar 1998 19:58:56 +0000 (GMT) Cc: nate@mt.sri.com, tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199803091047.NAA03211@tejblum.dnttm.rssi.ru> from "Dmitrij Tejblum" at Mar 9, 98 01:47:12 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 > Stacking layers *is not* an analogy of inheritance. Stacking layers is > analogy of event-passing in GUI, or "filters" in Unix pipes, or some > such. Every widget, of course, must handle every possible event. Or know how to pass it to a lower layer, VOP's being the event type and argument decriptors being the events. > But some > widget are designed especially to dispatch events to other widgets. > This dispatching is a way of handling. Both widgets are finished stuff, > unlike a derived class without a base class. Or, as example of a layer, > consider a program that read a text file, handle lines started with '#', > and print other lines in slightly modified form to output. It is a finished > program too. You cannot say that it inherit from the program which > read and handle its output. > > But there is real inheritance in filesystems. For example, FIFOs in > FFS, FIFOs in NFS, FIFOs in CD9660, etc. is all derived from a generic > FIFO. This is true. fifofs and specfs are special cases because they are named in the common namespace. This is brain damage we will have to live with for a while (Julian has fixed the specfs damage using devfs; you don't need the namespace incursion to get devices any more; the fifo incursions are harder to deal with). The FFS/UFS inheritance is both more and less problematic. More, because it is so fundamental to the system. Less, because it's *almost* sufficiently abstract. Kirk's stated intent in the seperation was to provide a flat inode namespace. Some of this has been recently broken (via default vops and other changes), and some of it never worked (specifically, the mechanism whereby UFS gets it's naming relies on an FS specific directory node acquisition). The real reason for UFS/FFS explicit inheritance is so that you don't have to use "mount" to assemble an FFS from pieces. > Terry wants that all filesystems handle GETPAGES/PUTPAGES. This is > fine. I simple don't like that he put his 'default' junk in zillion > filesystems, instead of put it in an appropriate base class. It's not "an apropriate base class". A base class consisting of anything other than EOPNOTSUPP is pretty much broken. Read the BSD4.4 Stacking Architecture design document, I keep posting its URL. 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 Mar 9 12:22:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25845 for freebsd-current-outgoing; Mon, 9 Mar 1998 12:22:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from slave3.aa.net ([204.157.220.249]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25838 for ; Mon, 9 Mar 1998 12:22:56 -0800 (PST) (envelope-from reggie@aa.net) Received: from trane (cust83.max5.seattle-k56.aa.net [206.125.79.83]) by slave3.aa.net (8.8.8/8.8.5) with SMTP id MAA18401; Mon, 9 Mar 1998 12:21:56 -0800 X-Intended-For: current@FreeBSD.ORG Received: by localhost with Microsoft MAPI; Mon, 9 Mar 1998 12:21:54 -0800 Message-ID: <01BD4B55.F28C0D50.reggie@aa.net> From: "Reginald S. Perry" Reply-To: "reggie@aa.net" To: "'Anatoly Vorobey'" , Nate Williams Cc: "current@FreeBSD.ORG" Subject: RE: vnode_pager: *** WARNING *** stale FS code in system Date: Mon, 9 Mar 1998 12:21:53 -0800 Organization: ImaginationWerks Consulting X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 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 Monday, March 09, 1998 9:46 AM, Anatoly Vorobey [SMTP:mellon@pobox.com] wrote: > > P.S. In fact, the VFS framework (more precisely, one of its > predecessors, Sun's vnode system) is mentioned in at least one > book on Java as an example to what pains these poor C programmers > must go in order to create OOP-like FS interface, and how easily > you would do that in Java ;) > Actually, wouldn't it be a pain in the butt to do unionFS in Java because of the lack of multiple inheritance? -Reggie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 13:52:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08396 for freebsd-current-outgoing; Mon, 9 Mar 1998 13:52:01 -0800 (PST) (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 NAA08339 for ; Mon, 9 Mar 1998 13:51:39 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id WAA07054 for current@FreeBSD.ORG; Mon, 9 Mar 1998 22:51:27 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id VAA17274; Mon, 9 Mar 1998 21:54:51 +0100 (CET) (envelope-from roberto) Message-ID: <19980309215450.A17205@keltia.freenix.fr> Date: Mon, 9 Mar 1998 21:54:50 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system Mail-Followup-To: current@FreeBSD.ORG References: <199803090300.UAA13920@mt.sri.com> <199803090344.UAA17601@usr08.primenet.com> <19980309152125.08053@techunix.technion.ac.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <19980309152125.08053@techunix.technion.ac.il>; from Anatoly Vorobey on Mon, Mar 09, 1998 at 03:21:25PM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4121 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Anatoly Vorobey: > Another question: which OSes _today_ provide for stackable file systems? > Not FreeBSD, apparently not Linux or Solaris. NT has got "filesystem Well, the *BSD certainly do but the code is not perfect and has some inconsistancies with respect to the Heideman framework. > A third question: can you give a (few?) example(s?) of hypothetical > useful stackable file systems, besides NULLFS? Compression layer, quota layer, ACL layer, cryptographic layer for instance. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 14:13:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12707 for freebsd-current-outgoing; Mon, 9 Mar 1998 14:13:04 -0800 (PST) (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 OAA12688; Mon, 9 Mar 1998 14:12:50 -0800 (PST) (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 OAA16255; Mon, 9 Mar 1998 14:10:25 -0800 (PST) Message-Id: <199803092210.OAA16255@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bruce Evans cc: mike@smith.net.au, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: *HEADS UP* Correction to previous postings. In-reply-to: Your message of "Mon, 09 Mar 1998 21:20:15 +1100." <199803091020.VAA22972@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Mar 1998 14:10:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Please note that in the recent postings regarding the changes to the > >fashion in which the root filesystem is located and mounted there has > >been a fundamental factual error on my part. > > > >This error *will* cause users with dedicated disks serious problems, > >unless they adopt the same procedure require by non-dedicated disk > >users. > > > >The error in this case was the assumption that partitions on a dedicated > >disk were handled as though they were truly equivalent to the > >compatability slice entries. > > A correct assumption. This doesn't appear to be borne out in any consistent fashion. > >This is not correct; rather they appear > >as though they were in the first slice on the disk. > > Not with normal slice naming. The first slice (s1) doesn't exist on > dangerously dedicated disks. Rev.1.88 of autoconf.c just breaks > support for dangerously dedicated disks. Rev.1.87 was correct in > this areas, except it spells COMPATIBILITY_SLICE as 0. That's odd then; libdisk calls them 'xdNs1', and you appear to be able to mount them like that. More significantly, the bootstrap passes the invalid slice number 1 in; using this is guaranteed to result in failure, as there aren't any devices with a '1' in the slice field. I believed that I had, actually, tested on a dedicated-disk system, however it appears otherwise. 8( > disks are not as easy to create as they used to be. Mine have > an all-zero DOS partition table. The update procedure for > dangerously-dedicated disks is to back out rev.1.88 of autoconf.c. *sigh* I thought that I had established this correctly twice now, based on code study and our earlier discussions. Can I please confirm, so that this isn't screwed for good? - If the slice number from the bootstrap is in the range BASE_SLICE to MAX_SLICES, it is OK to insert this as-is into the root device minor number. - If the slice number is < BASE_SLICE, the correct minor for the root device will have a 0 in the slice field. ie. I should be using COMPATABILITY_SLICE not BASE_SLICE in the test in setroot()? Thanks. -- \\ 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 Mar 9 14:48:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19600 for freebsd-current-outgoing; Mon, 9 Mar 1998 14:48:15 -0800 (PST) (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 OAA19527; Mon, 9 Mar 1998 14:48:05 -0800 (PST) (envelope-from dyson@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA00572; Mon, 9 Mar 1998 17:47:41 -0500 (EST) (envelope-from dyson) Message-Id: <199803092247.RAA00572@dyson.iquest.net> Subject: Re: What does that mean? In-Reply-To: <19980309211054.40322@burka.carrier.kiev.ua> from Alexander Litvin at "Mar 9, 98 09:10:54 pm" To: archer@lucky.net (Alexander Litvin) Date: Mon, 9 Mar 1998 17:47:40 -0500 (EST) Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Alexander Litvin said: > On Mon, Mar 09, 1998 at 01:43:21PM -0500, John S. Dyson wrote: > > Alexander Litvin said: > > > Sorry for bothering you... > > > > > > I just tried 'tail ' and got "Segmentation fault". On the > > > console: > > > > > > spec_getpages: I/O read failure: (error code=0) > > > size: 4096, resid: 0, a_count: 3586, valid: 0x0 > > > nread: 4096, reqpage: 1, pindex: 21, pcount: 1 > > > vm_fault: pager input (probably hardware) error, PID 18023 failure > > > Mar 9 15:48:51 grape /kernel: pid 18023 (tail), uid 0: exited on signal 11 > > > > > > The second attempt to issue the same command succeded. > > > > > > Is it really hardware-related, or... > > > > > It is likely a bug that I have created. I work on it NOW. > Tor Egge created a fix, and I just committed it. Give it a try again!!! -- 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 Mon Mar 9 14:48:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19651 for freebsd-current-outgoing; Mon, 9 Mar 1998 14:48:21 -0800 (PST) (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 OAA19444 for ; Mon, 9 Mar 1998 14:48:01 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id XAA09688 for current@FreeBSD.ORG; Mon, 9 Mar 1998 23:47:31 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id XAA00358; Mon, 9 Mar 1998 23:38:34 +0100 (CET) (envelope-from roberto) Message-ID: <19980309233834.A297@keltia.freenix.fr> Date: Mon, 9 Mar 1998 23:38:34 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: page fault while in kernel mode (-current from this morning && softupdates) Mail-Followup-To: current@FreeBSD.ORG References: <19980308230222.A9458@keltia.freenix.fr> <13409.889399148@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <13409.889399148@critter.freebsd.dk>; from Poul-Henning Kamp on Mon, Mar 09, 1998 at 12:19:08AM +0100 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4121 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Poul-Henning Kamp: > Considering that it mentions "allocindir" it would be obvious that it > involves files bigger than what we have in our source-tree. That > should also be the avenue to reproduction I think... Reproducting it is very easy :-) Finding the cause is not. One of the problem I have is that I can work only a kernel core dump, being unable to do remote debugging. The trace I get shows it stopped in _softdep_setup_allocindir_page when the real point of failure is the bcopy at the end of setup_allocindir_phase2. I don't have access to the latter's variables since it is a private function (I guess). I'll make it a public one and see if I can dig something out of this. Either one of the two pointers (newindirdep->ir_saveddata, newindirdep->ir_savebp->b_data) is bad or bp->b_bcount is too big (8192 which seems right for an indirect block on a 8k/1k FS). Just extending an existing file doen't seem to trigger it (just tried it). Using DDB and putting a break point in setup_allocindir_phrase2 shows that the function is called many times but I can't get the bug to manifest inside DDB . I'd appreciate if someone with more internal knowledge than I have could help :-) > >It happens for me in two cases: > >- rnews batch processing, > >- procmail delivering mail into mailboxes. I can see why for the latter case (procmail tries to append a message in one mailbox). The former could be .overview or history append... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 15:05:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23262 for freebsd-current-outgoing; Mon, 9 Mar 1998 15:05:04 -0800 (PST) (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 PAA23254; Mon, 9 Mar 1998 15:05:01 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id QAA26773; Mon, 9 Mar 1998 16:43:20 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id QAA11086; Mon, 9 Mar 1998 16:43:20 -0600 (CST) Message-ID: <19980309164320.63724@mcs.net> Date: Mon, 9 Mar 1998 16:43:20 -0600 From: Karl Denninger To: current@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Oh, how I hate it when I find leaks in mbuf clusters :-) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Heh, dig this nice problem...... This morning I took down our 100BaseTX hub to replace it with an Intel 510T switch. It helped a lot :-) As a consequence, the servers sat unterminated on that interface for some 5-10 minutes. When I got done with the switch install I plugged it all in and turned the switch on, thinking nothing of it. BIG MISTAKE! It turns out that for some reason the NFS server code was queueing mbufs - and never getting them off the stack. Almost a dozen hours later, under the heaviest load of the day, down goes Mr. Server with a "out of mbuf clusters - increase MAXUSERS" error. Say what? (There's no way it legitimately ran out). It comes back up, and is running happily with 400-500 mbufs in use. When it panic'd it had to have over 15,000 of 'em on the stack. So I go check its sister machine (which hasn't died - yet) and find: $ netstat -m 20228/20544 mbufs in use: 20185 mbufs allocated to data 43 mbufs allocated to packet headers 2419/2686 mbuf clusters in use 7940 Kbytes allocated to network (92% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Yikes! Obviously, I'm going to have to shut it down before it shuts down for me :-) Anyone have ideas on this one? "dmesg" for the kernel is: Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sat Nov 22 13:41:31 CST 1997 karl@Codebase.mcs.net:/usr/src/sys/compile/MCS_NEWS CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping=7 Features=0xfbff real memory = 100663296 (98304K bytes) avail memory = 94986240 (92760K bytes) Probing for devices on PCI bus 0: Correcting Natoma config for non-SMP chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 de0: rev 0x12 int a irq 9 on pci0.11.0 de0: SMC 9332DST 21140 [10-100Mb/s] pass 1.2 de0: address 00:00:c0:2d:57:ed de0: enabling 10baseT port de1: rev 0x12 int a irq 10 on pci0.12.0 de1: SMC 9332DST 21140 [10-100Mb/s] pass 1.2 de1: address 00:00:c0:35:57:ed de1: enabling 100baseTX port ahc0: rev 0x00 int a irq 11 on pci0.13.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 ahc0: target 0 Tagged Queuing Device sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 34729MB (71124992 512 byte sectors) sd0: with 4341 cyls, 128 heads, and an average 128 sectors/track Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 ed1 not found at 0x300 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x3bc-0x3c3 irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdreset: error1: 0x0 wdreset: error1: 0x0 wdc0 not found at 0x1f0 aha0 not found at 0x330 aic0 not found at 0x340 npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers CC'd to hackers and -current; I've no idea where the "right" place for this one is, as this kernel isn't really "that" current. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 15:25:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27769 for freebsd-current-outgoing; Mon, 9 Mar 1998 15:25:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feldman.dyn.ml.org (root@1Cust6.max6.washington.dc.ms.uu.net [153.34.51.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27717 for ; Mon, 9 Mar 1998 15:24:58 -0800 (PST) (envelope-from green@feldman.dyn.ml.org) Received: from localhost (green@localhost) by feldman.dyn.ml.org (8.8.8/8.8.8) with SMTP id SAA05476 for ; Mon, 9 Mar 1998 18:21:35 -0500 (EST) (envelope-from green@feldman.dyn.ml.org) Date: Mon, 9 Mar 1998 18:21:35 -0500 (EST) From: Brian Feldman To: freebsd-current@FreeBSD.ORG Subject: C++ libs are broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You know, I'm surprised I've only seen this twice (cut out the damn stackable FS talk, so we can talk about what's happening NOW!), and have noticed it quite a bit myself, that the newest C++ libraries ARE BROKEN! I wish someone might pay a tiny bit of attention to this, because it's really annoying (2.2.5-RELEASE's C++ libs are less than fully functional to use). Might someone want to see what commit changes have been made and fix these libraries? -Brian Feldman brianfeldman@hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 15:28:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28634 for freebsd-current-outgoing; Mon, 9 Mar 1998 15:28:50 -0800 (PST) (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 PAA28135; Mon, 9 Mar 1998 15:27:03 -0800 (PST) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id PAA02345; Mon, 9 Mar 1998 15:27:48 -0800 (PST) Date: Mon, 9 Mar 1998 15:27:48 -0800 (PST) From: Jim Shankland Message-Id: <199803092327.PAA02345@biggusdiskus.flyingfox.com> To: current@FreeBSD.ORG, karl@mcs.net Subject: Re: Oh, how I hate it when I find leaks in mbuf clusters :-) Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm. Notice that even with this horrendous mbuf leak, there is less than 8 MB of memory allocated to the network. Given that memory keeps getting cheaper and cheaper, and that finding and eliminating memory leaks is time-consuming and error-prone, perhaps we should forget about freeing memory at all, and simply buy more. At today's prices, for example, it's probably not unreasonable for a server machine like Karl's to be equipped with 128 MB of memory dedicated to network buffers. By the time that runs out, it's likely to be even cheaper to add another 256 MB. Disposable diapers and contact lenses have worked out well; why not disposable memory? (Discarded DIMMs don't fill up the landfills as quickly as used diapers, either, and they also smell better.) 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 Mon Mar 9 15:42:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01835 for freebsd-current-outgoing; Mon, 9 Mar 1998 15:42:07 -0800 (PST) (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 PAA01755 for ; Mon, 9 Mar 1998 15:41:41 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 666 invoked from network); 9 Mar 1998 23:41:10 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 9 Mar 1998 23:41:10 -0000 Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id PAA26131; Mon, 9 Mar 1998 15:41:24 -0800 (PST) (envelope-from scottm) Date: Mon, 9 Mar 1998 15:41:24 -0800 (PST) From: Scott Michel Message-Id: <199803092341.PAA26131@mordred.cs.ucla.edu> To: freebsd-current@FreeBSD.ORG, green@feldman.dyn.ml.org Subject: Re: C++ libs are broken In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The changes have apparently been committed. CVSup, make world, stir. Repeat. -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 15:58:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06159 for freebsd-current-outgoing; Mon, 9 Mar 1998 15:58:33 -0800 (PST) (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 PAA05805 for ; Mon, 9 Mar 1998 15:57:27 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id SAA25936; Mon, 9 Mar 1998 18:55:22 -0500 (EST) Date: Mon, 9 Mar 1998 18:55:21 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Brian Feldman cc: freebsd-current@FreeBSD.ORG Subject: Re: C++ libs are broken 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, 9 Mar 1998, Brian Feldman wrote: > > You know, I'm surprised I've only seen this twice (cut out the damn > stackable FS talk, so we can talk about what's happening NOW!), and have > noticed it quite a bit myself, that the newest C++ libraries ARE BROKEN! I > wish someone might pay a tiny bit of attention to this, because it's > really annoying (2.2.5-RELEASE's C++ libs are less than fully functional > to use). Might someone want to see what commit changes have been made and > fix these libraries? Keep some perspective ... current's been the target of some folks who abused the privilege, but the stuff about the filesystems IS a good, and really interesting "current" topic. You can ask about the C++ libs, but not at the expense of what others are doing ... that's selfish. Besides, if you're reading the commit mail, you know that the C++ libs are currently the topic of a lot of work, they haven't been badly busted all that long, give them some time. They already know things are unstable (the reason is because the ELF stuff *and* the Alpha stuff are both hitting the C++ libs at the same time) so this just calls for a little patience. A heads up ("this is broken") is a good thing, but not calling off debate of important topics in design. > > -Brian Feldman > brianfeldman@hotmail.com > > > 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 Mon Mar 9 16:01:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06709 for freebsd-current-outgoing; Mon, 9 Mar 1998 16:01:14 -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 QAA06548 for ; Mon, 9 Mar 1998 16:00:11 -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 CAA09900; Tue, 10 Mar 1998 02:49:47 +0300 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 CAA03508; Tue, 10 Mar 1998 02:59:01 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199803092359.CAA03508@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-reply-to: Your message of "Sun, 08 Mar 1998 23:31:19 GMT." <199803082331.QAA08328@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain Date: Tue, 10 Mar 1998 02:59:01 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > The reason I went the way I did was that putting the vnode_pager.c > > > code in the defaultops vector does nothing toward making the code > > > in vnode_pager.c _go away_, which is the eventual goal. > > > > Your changes do same nothing toward this goal. Everyone can insert a > > function into a vnops table. It is trivial. Almost nobody can write a > > real getpages or putpages routine. For example, you failed even to > > write a readonly cd9660_putpages, while it would be, apparently, > > trivial. (I suspect, simple 'return (VM_PAGER_BAD);' would do a right > > thing.) You also failed to mention this problem in your standard comment. > > So, when real implementation for getpages and putpages for all these > > filesystem will written? > > Most assuredly, at some time *after* a skeleton versions of FS specific > getpages/putpages have been written. Organizationally, the patches I > gave *do* move toward that goal. Before these changes, simple grep for getpages_desc gave the list of real getpages implementations. The tool in src/tools/tools/vop_table also could be used to find such list. Now you succefully created illusion that all filesystems already have own specific getpages implementation. The "organizational" side of these changes, as I already stated, is trivial. > If you insist, I can duplicate the generic code into the FS's themselves > immediately, and remove it from the generic location. I don't see this > action as being useful. Me too. Please don't duplicate it. > [...] > > Filesystem-specific getpages/putpages possible since end of 1995. You > > saved a filesystem writer from writing 7 obvious lines of each > > implementations (even these lines contain style bugs, so actual number > > is slightly less). Is this the big win? > > Codewise, no. That's why I would have preferred to leave the other FS's > issuing the warning until such time as I could fix the code; after all, > I am a purist. But pragmatically, it makes the desired organization > obvious (instead of clouding it unnecessarily), and the patches were > necessary, given the stabilization requirements now in force. Desired organization was obvious. You made the organization more complex without a real advantage. > I would cetrainly welcome your assitance in unstubbing the local media > getpages/putpages, if you were willing to give it. This would resolve > your implementation issues, without stepping on my organizational issues. Thanks. It is hardly possible since I know almost nothing about VM. > > > for a large variety of reasons (I can enumerate these > > > reasons again, if you need me to). > > > > Well, actually I don't know any reasons for it, other than reference to > > John Dyson's authority and complexity of the generic code. So it would > > be interesting. But it is outside of scope of this discussion. > > Then casting aspersions on my reasoning by implying that my only > validation is lodged in "appeal to authority" is probably *also* > outside the scope of this discussion, don't you think? Uh. Yes. But the list of reasons would be interesting :). And I didn't want "aspersions", but referred only to my, quite limited, knowledges... > > > From point of view of a > > stacking layer, the filesystem below provide a getpages/putpages > > implementation, and this is all that you want. > > Actually, I want to use the local media FS's pager. The difference here > is that if I have a crypto FS stacked on top of a transaction FS stacked > on top of a ACL FS stacked on top of a quota FS on top of an FFS FS, > when I try to getpages on the crypto FS, it should try to getpages on the > underlying FFS. > > In your suggested implementation, I can't collapse the call graph > because in the stacking FS's will each have a getpages/putpages to > access the bypass explicitly, instead of accessing it implicitly. I don't see what force stacking layers to access bypass explicitly. Look: int vop_defaultop(struct vop_generic_args *ap) { return (VOCALL(default_vnodeop_p, ap->a_desc->vdesc_offset, ap)); } Does your stacking layer modify ap->a_desc->vdesc_offset? If yes, how and why? If no, everything is OK: vop_defaultop will do the right thing. In other words, the call to vop_defaultop is absolutely equivalent to the operation in the default vector itself. Anyway, this doesn't matter much, since I don't insist on the defaultop way. > > Here's my preferred soloution, since it will pacify you as well: make > the warning non-fatal *for now*; ie: > [...] This looks even worse. And no, it will not pacify me :) To pacify me, either remove msdosfs_getpages and msdosfs_putpages, or make them real msdosfs-specific implementation. These two dumb functions without any purpose irritates me. Actually, all functions without a purpose irritates me. (Well, actually I am already almost pacified :) > > > A tertiary reason is that if the code is in the defaultops vector, > > > I can't know when it becomes safe to remove from vnode_pager.c > > > and the defaultops vector. There's no way to measure usage of > > > the defaultops code (that's kind of the point, really). > > > > OK, don't put it to defaultops vector, put vop_stdgetpages and > > vop_stdputpages to vnops table of every affected filesystem. I suggest > > it in every mail on this topic :-). > > Now you are basically griping only about naming. About functions which do nothing themselves. > The problem with calling it standard is that *it's not supposed to be > the standard, correct way of doing things*. Well, call it as you like :) > The blunt fact is that the way it was being done is screwed up, and > *something* needs to be done to unscrew it, and done in such a way > as it doesn't screw the FS stacking at the same time. I would not call it 'unscrew'. Your action keep vnode_pager.c screwed, and also abused lot of virgin filesystems. > > One may say that my complains are more about decorative issues that > > about real programming issues. Sorry. It is because all discussing > > changes actually more decorative than real code. And as decorative, > > they are IMHO bad. Also, unfortunately, most points in this discussion > > were repeated several times... > > I don't know how many times I should have to repeat this, but the code > *should not be in vnode_pager.c* and was, in fact *designed to not be > in vnode_pager.c*. And here is my usual answer: you did *nothing* to remove the code. > [...] Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 16:14:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10256 for freebsd-current-outgoing; Mon, 9 Mar 1998 16:14:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10164 for ; Mon, 9 Mar 1998 16:14:08 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id KAA03814; Tue, 10 Mar 1998 10:42:17 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id G2GZRY0S; Tue, 10 Mar 1998 10:42:44 +0930 Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id KAA07138; Tue, 10 Mar 1998 10:43:22 +1030 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id KAA13493; Tue, 10 Mar 1998 10:43:15 +1030 (CST) Message-ID: <35048598.92269996@dsto.defence.gov.au> Date: Tue, 10 Mar 1998 10:43:12 +1030 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Richard Wackerbarth CC: Anatoly Vorobey , current@FreeBSD.ORG Subject: Re: Culprit Found -- (Re: CTM src-cur.3278 fails to apply) References: ; from Richard Wackerbarth on Mon, Mar 09, 1998 at 08:05:29AM -0600 <3503E87D.E639921D@camtech.net.au> <19980309151131.44045@techunix.technion.ac.il> <3503F351.B1A13393@camtech.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I gather "make world" does a "make cleandir" at some stage. So if you are asking whether I have done a make world recently then my answer is "Yes, guilty as charged". If thats the cause of the problem then libmp's Makefile needs some work. On the whole I dont mess with my source tree. You may not believe me now that my mistake with the TODO-2.1 directory is known but you'll have to take my word for it. I do the following occasionally: - cd /usr/src/usr.sbin/config ; make (with and empty /usr/obj) - cd /usr/src/usr.sbin/config ; make clean - make world And a while ago I was doing "make distribution" from /usr/src/etc with the destination tree set to somewhere in /tmp. Richard Wackerbarth wrote: > > At 10:48 AM -0600 3/9/98, Anatoly Vorobey wrote: > >Richard, > > > >You, Richard Wackerbarth, were spotted writing this on Mon, Mar 09, 1998 > >at 08:05:29AM -0600: > > > >> OBJECTION! You have admitted that you deleted one directory. > >> Are you sure that you did not do something that caused other > >> empty directories to disappear? > > > >Well, I'm sure I didn't, and I got the same mistakes. I built my > >tree anew a few weeks ago by starting from 3200xEmpty and applying > >all deltas since then. I've never even entered libgmp before ;) > > >> As others have noted, just applying the deltas in sequence works. > > > >Well, you can't apply them not in sequence (unless perhaps with -F > >which I didn't use), and still several people got the same mistake. > > You are applying the wrong meaning to my statement. > My intent is that if you do nothing other than apply the deltas, it works. > > >Note that I'm by no means accusing you; in fact I appreciate your > >work in producing CTM deltas a lot. Thanks! ;) > > I have found the culprit. > > "make cleandir" , when executed in gnu/libs does the following (among > other things) > > rm -f libmp.so.*.* libmp_pic.a > rm -rf /pub/FreeBSD/FreeBSD-current/src/gnu/lib/libmp/mpz > /pub/FreeBSD/FreeBSD-current/src/gnu/lib/libmp/mpz > rm -f .depend > rm -f /pub/FreeBSD/FreeBSD-current/src/gnu/lib/libmp/GRTAGS > /pub/FreeBSD/FreeBSD-current/src/gnu/lib/libmp/GTAGS > > I assure you that the CTM generator didn't execute that command. > However, I suspect that you may have caused it, or something similar, to > get executed. > > Richard Wackerbarth > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 16:18:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11104 for freebsd-current-outgoing; Mon, 9 Mar 1998 16:18:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf52.cruzers.com [205.215.232.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA11016 for ; Mon, 9 Mar 1998 16:17:54 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 429 invoked by uid 100); 10 Mar 1998 00:19:09 -0000 Message-ID: <19980309161906.A372@top.worldcontrol.com> Date: Mon, 9 Mar 1998 16:19:06 -0800 To: freebsd-current@FreeBSD.ORG Subject: machine no longer appears via its primary ethernet interface Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.7i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a P5-90 running -current from Mar 8th. Every other day or so its stops responding to its .161 address, but will respond to others. It's been acting this way for a month or so. Its de0 interface is setup as: de0: flags=8843 mtu 1500 inet xxx.yyy.zzz.161 netmask 0xffffffc0 broadcast xxx.yyy.zzz.191 inet xxx.yyy.zzz.162 netmask 0xffffffff broadcast xxx.yyy.zzz.162 inet xxx.yyy.zzz.163 netmask 0xffffffff broadcast xxx.yyy.zzz.163 inet xxx.yyy.zzz.164 netmask 0xffffffff broadcast xxx.yyy.zzz.164 inet xxx.yyy.zzz.165 netmask 0xffffffff broadcast xxx.yyy.zzz.165 inet xxx.yyy.zzz.166 netmask 0xffffffff broadcast xxx.yyy.zzz.166 ether 00:80:c8:2b:db:08 media: 10baseT/UTP status: active supported media: autoselect 10base5/AUI manual 10baseT/UTP 10baseT/UTP It is setup that way via ifconfig_de0="inet xxx.yyy.zzz.161 netmask 255.255.255.192 media 10baseT/UTP" in /etc/sysconfig and /sbin/ifconfig de0 alias xxx.yyy.zzz.162 netmask 255.255.255.255 /sbin/ifconfig de0 alias xxx.yyy.zzz.163 netmask 255.255.255.255 /sbin/ifconfig de0 alias xxx.yyy.zzz.164 netmask 255.255.255.255 /sbin/ifconfig de0 alias xxx.yyy.zzz.165 netmask 255.255.255.255 /sbin/ifconfig de0 alias xxx.yyy.zzz.166 netmask 255.255.255.255 in /etc/rc.local It is primarily used by via its .161 address. Sometimes it disappears (no longer responds to its .161 address). For example: (I am out on the general internet) brian@top> ping xxx.yyy.zzz.161 [ping just sits there, and will do so for as long as I have waited] In another window issue the command: brian@top>ping -c 1 xxx.yyy.zzz.163 PING xxx.yyy.zzz.163 (xxx.yyy.zzz.163): 56 data bytes 64 bytes from xxx.yyy.zzz.163: icmp_seq=0 ttl=242 time=3888.267 ms --- xxx.yyy.zzz.163 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 3888.267/3888.267/3888.267/0.000 ms Then immediately the first ping begins to respond: (note that 65 packet have previously been lost) brian@top>ping xxx.yyy.zzz.161 PING xxx.yyy.zzz.161 (xxx.yyy.zzz.161): 56 data bytes 64 bytes from xxx.yyy.zzz.161: icmp_seq=66 ttl=242 time=4573.434 ms 64 bytes from xxx.yyy.zzz.161: icmp_seq=67 ttl=242 time=3602.600 ms 64 bytes from xxx.yyy.zzz.161: icmp_seq=68 ttl=242 time=4383.136 ms 64 bytes from xxx.yyy.zzz.161: icmp_seq=69 ttl=242 time=4273.397 ms 64 bytes from xxx.yyy.zzz.161: icmp_seq=70 ttl=242 time=3293.190 ms 64 bytes from xxx.yyy.zzz.161: icmp_seq=71 ttl=242 time=2333.278 ms 64 bytes from xxx.yyy.zzz.161: icmp_seq=72 ttl=242 time=1344.112 ms 64 bytes from xxx.yyy.zzz.161: icmp_seq=73 ttl=242 time=343.187 ms ... When it is in this "odd" state it does not respond via .161 to machines on the same LAN either. It has fallen into this behavior at least once every two days for the past few weeks. The machine is connected to a Cisco switch of some sort. I think it said Cisco 2000. It is the only machine connected into the providers network via the Cisco 2000, so I worry the problem may be related to the switch. Any ideas? I'm going to ask the provider to connect me before the switch to eliminate that as a possible cause. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 16:41:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17115 for freebsd-current-outgoing; Mon, 9 Mar 1998 16:41:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from webfarm1.whistle.com (webfarm1.whistle.com [207.76.204.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17106 for ; Mon, 9 Mar 1998 16:41:28 -0800 (PST) (envelope-from julian@whistle.com) Received: (from smap@localhost) by webfarm1.whistle.com (8.8.5/8.8.5) id QAA13730 for ; Mon, 9 Mar 1998 16:40:38 -0800 (PST) X-Authentication-Warning: webfarm1.whistle.com: smap set sender to using -f Received: from alpo.whistle.com(alpo.isp.whistle.com 207.76.204.38) by webfarm1.whistle.com via smap (V2.0) id xma013728; Mon, 9 Mar 98 16:40:11 -0800 Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA22716; Mon, 9 Mar 1998 16:23:45 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd022711; Mon Mar 9 16:23:38 1998 Message-ID: <35048708.6201DD56@whistle.com> Date: Mon, 09 Mar 1998 16:19:20 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Ollivier Robert CC: current@FreeBSD.ORG, mckusick@mcKusick.com Subject: Re: page fault (-current && softupdates) References: <19980308230222.A9458@keltia.freenix.fr> <13409.889399148@critter.freebsd.dk> <19980309233834.A297@keltia.freenix.fr> Content-Type: multipart/mixed; boundary="------------63DECDAD62319AC452BFA1D7" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------63DECDAD62319AC452BFA1D7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Here's a bit more info on teh Soft Update problem.. Ollivier Robert wrote: > > According to Poul-Henning Kamp: > > Considering that it mentions "allocindir" it would be obvious that it > > involves files bigger than what we have in our source-tree. That > > should also be the avenue to reproduction I think... > > Reproducting it is very easy :-) > > Finding the cause is not. One of the problem I have is that I can work only > a kernel core dump, being unable to do remote debugging. The trace I get > shows it stopped in _softdep_setup_allocindir_page when the real point of > failure is the bcopy at the end of setup_allocindir_phase2. > > I don't have access to the latter's variables since it is a private > function (I guess). I'll make it a public one and see if I can dig > something out of this. > > Either one of the two pointers (newindirdep->ir_saveddata, > newindirdep->ir_savebp->b_data) is bad or bp->b_bcount is too big (8192 > which seems right for an indirect block on a 8k/1k FS). I have this expanded out here.. I replaced bcopy with BC() which in turn calls teh assembler bcopy() this gave me the stack trace needed here is a transcript of the debugging session.. from this it looks as if BOTH newindirdep->ir_saveddata AND newindirdep->ir_savebp are NULL (!??) looking at the code I can't see how this is possible. > > Just extending an existing file doen't seem to trigger it (just tried it). > Using DDB and putting a break point in setup_allocindir_phrase2 shows that > the function is called many times but I can't get the bug to manifest > inside DDB . > > I'd appreciate if someone with more internal knowledge than I have could > help :-) > > > >It happens for me in two cases: > > >- rnews batch processing, > > >- procmail delivering mail into mailboxes. yes it seems to happen in rathe rspecific cases, but just plain HEAVY LOAD is not enough. > > I can see why for the latter case (procmail tries to append a message in > one mailbox). The former could be .overview or history append... > -- --------------63DECDAD62319AC452BFA1D7 Content-Type: text/plain; charset=iso-8859-1; name="gdb2" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="gdb2" NOTE: BC() is an indirect bcopy that saves a stack frame... Script started on Mon Mar 9 23:09:10 1998 phaser2# gdb GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc. Debugger (msg=0xf011953c "panic") at ../../i386/i386/db_interface.c:317 317 in_Debugger = 0; (gdb) where #0 Debugger (msg=0xf011953c "panic") at ../../i386/i386/db_interface.c:317 #1 0xf011959e in panic ( fmt=0xf01cbab0 "vm_fault: fault on nofault entry, addr: %lx") at ../../kern/kern_shutdown.c:434 #2 0xf01cbbe4 in vm_fault (map=0xf026482c, vaddr=4049862656, fault_type=3 '\003', fault_flags=0) at ../../vm/vm_fault.c:227 #3 0xf01eca48 in trap_pfault (frame=0xf2d0fc80, usermode=0) at ../../i386/i386/trap.c:724 #4 0xf01ec6c7 in trap (frame={tf_es = -222429168, tf_ds = 16, tf_edi = -245104640, tf_esi = -246204416, tf_ebp = -221184812, tf_isp = -221184856, tf_ebx = -248986476, tf_edx = 8192, tf_ecx = 512, tf_eax = 1099776, tf_trapno = 12, tf_err = 2, tf_eip = -266422854, tf_cs = 8, tf_eflags = 66054, tf_esp = -258680576, tf_ss = -260642304}) at ../../i386/i386/trap.c:363 #5 0xf01e3401 in calltrap () [***POW***] #6 0xf01bbd06 in setup_allocindir_phase2 (bp=0xf128c494, ip=0xf08f9c00, aip=0xf094d900) at ../../ufs/ffs/ffs_softdep.c:1537 #7 0xf01bb9cb in softdep_setup_allocindir_page (ip=0xf08f9c00, lbn=13, bp=0xf128c494, ptrno=1, newblkno=918504, oldblkno=0, nbp=0xf12a7970) at ../../ufs/ffs/ffs_softdep.c:1419 #8 0xf01b8f3d in ffs_balloc (ap=0xf2d0fea4) at ../../ufs/ffs/ffs_balloc.c:302 #9 0xf01c270c in ffs_write (ap=0xf2d0fef8) at vnode_if.h:995 #10 0xf013dc77 in vn_write (fp=0xf0905480, uio=0xf2d0ff40, cred=0xf070c800) at vnode_if.h:331 #11 0xf012116b in write (p=0xf2bf1f40, uap=0xf2d0ff94) at ../../kern/sys_generic.c:268 #12 0xf01ed2af in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 237568, tf_esi = 103916, tf_ebp = -272640152, tf_isp = -221184028, tf_ebx = 537440352, tf_edx = 103916, tf_ecx = -272640112, tf_eax = 4, tf_trapno = 7, tf_err = 7, tf_eip = 537384545, tf_cs = 31, tf_eflags = 646, tf_esp = -272640176, tf_ss = 39}) at ../../i386/i386/trap.c:994 #13 0xf01e3455 in Xsyscall () #14 0x2007b1d1 in ?? () #15 0x2006bb50 in ?? () #16 0x3bf7 in ?? () #17 0x1099 in ?? () (gdb) up 6 #6 0xf01bbd06 in setup_allocindir_phase2 (bp=0xf128c494, ip=0xf08f9c00, aip=0xf094d900) at ../../ufs/ffs/ffs_softdep.c:1537 1537 BC((caddr_t)newindirdep->ir_saveddata, (gdb) list 1532 LIST_INIT(&newindirdep->ir_deplisthd); 1533 LIST_INIT(&newindirdep->ir_donehd); 1534 newindirdep->ir_saveddata = (ufs_daddr_t *)bp->b_data; 1535 newindirdep->ir_savebp = 1536 getblk(ip->i_devvp, bp->b_blkno, bp->b_bcount, 0, 0); 1537 BC((caddr_t)newindirdep->ir_saveddata, 1538 newindirdep->ir_savebp->b_data, bp->b_bcount); 1539 } 1540 } 1541 (gdb) print newindirdep $1 = (struct indirdep *) 0xf1533800 (gdb) p *$1 $2 = {ir_list = {wk_list = {le_next = 0x0, le_prev = 0x0}, wk_type = 0, wk_state = 0}, ir_saveddata = 0x0, ir_savebp = 0x0, ir_donehd = { lh_first = 0x0}, ir_deplisthd = {lh_first = 0x0}} [*** EH? it's all NULLS??? ***] (gdb) p $1->ir_savebp $3 = (struct buf *) 0x0 [*** this could be a problem.. ***] (gdb) p bp->b_bcount $4 = 8192 (gdb) info local aip = (struct allocindir *) 0xf1640000 wk = (struct worklist *) 0x12 indirdep = (struct indirdep *) 0x0 newindirdep = (struct indirdep *) 0xf1533800 bmsafemap = (struct bmsafemap *) 0xf0250240 oldaip = (struct allocindir *) 0x0 freefrag = (struct freefrag *) 0xf01e23f5 newblk = (struct newblk *) 0xf01ba325 (gdb) list setup_allocindir_phase2 1447 static void 1448 setup_allocindir_phase2(bp, ip, aip) 1449 struct buf *bp; /* in-memory copy of the indirect block */ 1450 struct inode *ip; /* inode for file being extended */ 1451 struct allocindir *aip; /* allocindir allocated by the above routines */ 1452 { 1453 struct worklist *wk; 1454 struct indirdep *indirdep, *newindirdep; 1455 struct bmsafemap *bmsafemap; 1456 struct allocindir *oldaip; 1457 struct freefrag *freefrag; 1458 struct newblk *newblk; 1459 1460 if (bp->b_lblkno >= 0) 1461 panic("setup_allocindir_phase2: not indir blk"); 1462 for (indirdep = NULL, newindirdep = NULL; ; ) { 1463 ACQUIRE_LOCK(&lk); 1464 for (wk = LIST_FIRST(&bp->b_dep); wk; 1465 wk = LIST_NEXT(wk, wk_list)) { 1466 if (wk->wk_type != D_INDIRDEP) 1467 continue; 1468 indirdep = WK_INDIRDEP(wk); 1469 break; 1470 } 1471 if (indirdep == NULL && newindirdep) { 1472 indirdep = newindirdep; 1473 WORKLIST_INSERT(&bp->b_dep, &indirdep->ir_list); 1474 newindirdep = NULL; 1475 } 1476 FREE_LOCK(&lk); 1477 if (indirdep) { 1478 if (newblk_lookup(ip->i_fs, aip->ai_newblkno, 0, 1479 &newblk) == 0) 1480 panic("setup_allocindir: lost block"); 1481 ACQUIRE_LOCK(&lk); 1482 if (newblk->nb_state == DEPCOMPLETE) { 1483 aip->ai_state |= DEPCOMPLETE; 1484 aip->ai_buf = NULL; 1485 } else { 1486 bmsafemap = newblk->nb_bmsafemap; 1487 aip->ai_buf = bmsafemap->sm_buf; 1488 LIST_REMOVE(newblk, nb_deps); 1489 LIST_INSERT_HEAD(&bmsafemap->sm_allocindirhd, 1490 aip, ai_deps); 1491 } 1492 LIST_REMOVE(newblk, nb_hash); 1493 FREE(newblk, M_NEWBLK); 1494 aip->ai_indirdep = indirdep; 1495 /* 1496 * Check to see if there is an existing dependency 1497 * for this block. If there is, merge the old 1498 * dependency into the new one. 1499 */ 1500 if (aip->ai_oldblkno == 0) 1501 oldaip = NULL; 1502 else 1503 for (oldaip=LIST_FIRST(&indirdep->ir_deplisthd); 1504 oldaip; oldaip = LIST_NEXT(oldaip, ai_next)) 1505 if (oldaip->ai_offset == aip->ai_offset) 1506 break; 1507 if (oldaip != NULL) { 1508 if (oldaip->ai_newblkno != aip->ai_oldblkno) 1509 panic("setup_allocindir_phase2: blkno"); 1510 aip->ai_oldblkno = oldaip->ai_oldblkno; 1511 freefrag = oldaip->ai_freefrag; 1512 oldaip->ai_freefrag = aip->ai_freefrag; 1513 aip->ai_freefrag = freefrag; 1514 free_allocindir(oldaip, NULL); 1515 } 1516 LIST_INSERT_HEAD(&indirdep->ir_deplisthd, aip, ai_next); 1517 ((ufs_daddr_t *)indirdep->ir_savebp->b_data) 1518 [aip->ai_offset] = aip->ai_oldblkno; 1519 FREE_LOCK(&lk); 1520 } 1521 if (newindirdep) { 1522 if (indirdep->ir_savebp != NULL) 1523 brelse(newindirdep->ir_savebp); 1524 WORKITEM_FREE((caddr_t)newindirdep, D_INDIRDEP); 1525 } 1526 if (indirdep) 1527 break; 1528 MALLOC(newindirdep, struct indirdep *, sizeof(struct indirdep), 1529 M_INDIRDEP, M_WAITOK); 1530 newindirdep->ir_list.wk_type = D_INDIRDEP; 1531 newindirdep->ir_state = ATTACHED; 1532 LIST_INIT(&newindirdep->ir_deplisthd); 1533 LIST_INIT(&newindirdep->ir_donehd); 1534 newindirdep->ir_saveddata = (ufs_daddr_t *)bp->b_data; 1535 newindirdep->ir_savebp = 1536 getblk(ip->i_devvp, bp->b_blkno, bp->b_bcount, 0, 0); 1537 BC((caddr_t)newindirdep->ir_saveddata, 1538 newindirdep->ir_savebp->b_data, bp->b_bcount); 1539 } 1540 } 1541 1542 /* 1543 * Block de-allocation dependencies. 1544 * 1545 * When blocks are de-allocated, the on-disk pointers must be nullified before 1546 * the blocks are made available for use by other files. (The true [*** and the caller ***] (gdb) list softdep_setup_allocindir_page 1398 struct buf *bp; /* buffer with indirect blk referencing page */ 1399 int ptrno; /* offset of pointer in indirect block */ 1400 ufs_daddr_t newblkno; /* disk block number being added */ 1401 ufs_daddr_t oldblkno; /* previous block number, 0 if none */ 1402 struct buf *nbp; /* buffer holding allocated page */ 1403 { 1404 struct allocindir *aip; 1405 struct pagedep *pagedep; 1406 1407 aip = newallocindir(ip, ptrno, newblkno, oldblkno); 1408 ACQUIRE_LOCK(&lk); 1409 /* 1410 * If we are allocating a directory page, then we must 1411 * allocate an associated pagedep to track additions and 1412 * deletions. 1413 */ 1414 if ((ip->i_mode & IFMT) == IFDIR && 1415 pagedep_lookup(ip, lbn, DEPALLOC, &pagedep) == 0) 1416 WORKLIST_INSERT(&nbp->b_dep, &pagedep->pd_list); 1417 WORKLIST_INSERT(&nbp->b_dep, &aip->ai_list); 1418 FREE_LOCK(&lk); 1419 setup_allocindir_phase2(bp, ip, aip); 1420 } 1421 1422 /* 1423 * Called just before setting an indirect block pointer to a 1424 * newly allocated indirect block. 1425 */ 1426 void 1427 softdep_setup_allocindir_meta(nbp, ip, bp, ptrno, newblkno) (gdb) up #7 0xf01bb9cb in softdep_setup_allocindir_page (ip=0xf08f9c00, lbn=13, bp=0xf128c494, ptrno=1, newblkno=918504, oldblkno=0, nbp=0xf12a7970) at ../../ufs/ffs/ffs_softdep.c:1419 1419 setup_allocindir_phase2(bp, ip, aip); (gdb) p aip $5 = (struct allocindir *) 0xf094d900 (gdb) info local ip = (struct inode *) 0xf08f9c00 inbp = (struct buf *) 0xf12a7970 aip = (struct allocindir *) 0xf094d900 pagedep = (struct pagedep *) 0xf12a7970 (gdb) info frame Stack level 7, frame at 0xf2d0fd44: eip = 0xf01bb9cb in softdep_setup_allocindir_page (../../ufs/ffs/ffs_softdep.c:1419); saved eip 0xf01b8f3d called by frame at 0xf2d0fe34, caller of frame at 0xf2d0fd14 source language c. Arglist at 0xf2d0fd44, args: ip=0xf08f9c00, lbn=13, bp=0xf128c494, ptrno=1, newblkno=918504, oldblkno=0, nbp=0xf12a7970 Locals at 0xf2d0fd44, Previous frame's sp is 0x0 Saved registers: ebx at 0xf2d0fd34, ebp at 0xf2d0fd44, esi at 0xf2d0fd38, edi at 0xf2d0fd3c, eip at 0xf2d0fd48 (gdb) down #6 0xf01bbd06 in setup_allocindir_phase2 (bp=0xf128c494, ip=0xf08f9c00, aip=0xf094d900) at ../../ufs/ffs/ffs_softdep.c:1537 1537 BC((caddr_t)newindirdep->ir_saveddata, (gdb) p bp $6 = (struct buf *) 0xf128c494 (gdb) p *bp $7 = {b_hash = {le_next = 0x0, le_prev = 0xf025e340}, b_vnbufs = { le_next = 0x0, le_prev = 0xf12a7978}, b_freelist = {tqe_next = 0xf12c0f80, tqe_prev = 0xf12c1af8}, b_act = {tqe_next = 0xf1291100, tqe_prev = 0xf0681dd4}, b_proc = 0x0, b_flags = 536870960, b_qindex = 0, b_usecount = 6 '\006', b_error = 0, b_bufsize = 8192, b_bcount = 8192, b_resid = 0, b_dev = 4294967295, b_data = 0xf1532000 "à\003\016", b_kvabase = 0xf1532000 "à\003\016", b_kvasize = 8192, b_lblkno = -12, b_blkno = -12, b_iodone = 0, b_iodone_chain = 0x0, b_vp = 0xf2c7d7c0, b_dirtyoff = 0, b_dirtyend = 0, b_generation = 37739, b_rcred = 0x0, b_wcred = 0x0, b_validoff = 0, b_validend = 0, b_pblkno = 2949231, b_saveaddr = 0x0, b_savekva = 0x0, b_driver1 = 0x0, b_driver2 = 0x0, b_spc = 0x0, b_cluster = {cluster_head = {tqh_first = 0xf1298d54, tqh_last = 0xf12bf4b4}, cluster_entry = {tqe_next = 0xf1298d54, tqe_prev = 0xf12bf4b4}}, b_pages = {0xf047a5b4, 0xf047b2e8, 0x0 }, b_npages = 2, b_dep = {lh_first = 0x0}} (gdb) p wk $8 = (struct worklist *) 0x12 (gdb) info local aip = (struct allocindir *) 0xf1640000 wk = (struct worklist *) 0x12 indirdep = (struct indirdep *) 0x0 newindirdep = (struct indirdep *) 0xf1533800 bmsafemap = (struct bmsafemap *) 0xf0250240 oldaip = (struct allocindir *) 0x0 freefrag = (struct freefrag *) 0xf01e23f5 newblk = (struct newblk *) 0xf01ba325 (gdb) p ip $11 = (struct inode *) 0xf08f9c00 (gdb) p *ip $12 = {i_lock = {lk_interlock = {lock_data = 0}, lk_flags = 1024, lk_sharecount = 0, lk_waitcount = 0, lk_exclusivecount = 1, lk_prio = 8, lk_wmesg = 0xf01c187b "inode", lk_timo = 0, lk_lockholder = 7712}, i_hash = {le_next = 0x0, le_prev = 0xf07e7c20}, i_vnode = 0xf2c7d7c0, i_devvp = 0xf2bef060, i_flag = 142, i_dev = 132102, i_number = 215166, i_effnlink = 1, inode_u = {fs = 0xf06ba000, e2fs = 0xf06ba000}, i_dquot = { 0x0, 0x0}, i_modrev = 0x3500d1f98f53e53d, i_lockf = 0x0, i_count = 0, i_endoff = 0, i_diroff = 0, i_offset = 0, i_ino = 0, i_reclen = 0, i_spare = {0, 0, 0, 0, 0}, i_din = {di_mode = 33188, di_nlink = 1, di_u = { oldids = {0, 0}, inumber = 0}, di_size = 106496, di_atime = 889246204, di_atimensec = 0, di_mtime = 889246315, di_mtimensec = 0, di_ctime = 889246315, di_ctimensec = 0, di_db = {919968, 919976, 919984, 919992, 920000, 920160, 920168, 920176, 920184, 920192, 920200, 920208}, di_ib = {917512, 0, 0}, di_flags = 0, di_blocks = 240, di_gen = 329868342, di_uid = 0, di_gid = 0, di_spare = {0, 0}}} (gdb) list 1527 break; 1528 MALLOC(newindirdep, struct indirdep *, sizeof(struct indirdep), 1529 M_INDIRDEP, M_WAITOK); 1530 newindirdep->ir_list.wk_type = D_INDIRDEP; 1531 newindirdep->ir_state = ATTACHED; 1532 LIST_INIT(&newindirdep->ir_deplisthd); 1533 LIST_INIT(&newindirdep->ir_donehd); 1534 newindirdep->ir_saveddata = (ufs_daddr_t *)bp->b_data; 1535 newindirdep->ir_savebp = 1536 getblk(ip->i_devvp, bp->b_blkno, bp->b_bcount, 0, 0); 1537 BC((caddr_t)newindirdep->ir_saveddata, 1538 newindirdep->ir_savebp->b_data, bp->b_bcount); 1539 } 1540 } 1541 1542 /* 1543 * Block de-allocation dependencies. 1544 * 1545 * When blocks are de-allocated, the on-disk pointers must be nullified before 1546 * the blocks are made available for use by other files. (The true (gdb) quit Script done on Mon Mar 9 23:29:59 1998 --------------63DECDAD62319AC452BFA1D7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 16:45:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17790 for freebsd-current-outgoing; Mon, 9 Mar 1998 16:45:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17770 for ; Mon, 9 Mar 1998 16:45:13 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id SAA06885; Mon, 9 Mar 1998 18:30:38 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <35048598.92269996@dsto.defence.gov.au> References: ; from Richard Wackerbarth on Mon, Mar 09, 1998 at 08:05:29AM -0600 <3503E87D.E639921D@camtech.net.au> <19980309151131.44045@techunix.technion.ac.il> <3503F351.B1A13393@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 9 Mar 1998 18:30:06 -0600 To: Matthew Thyer From: Richard Wackerbarth Subject: Re: Culprit Found -- (Re: CTM src-cur.3278 fails to apply) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:13 PM -0600 3/9/98, Matthew Thyer wrote: >I gather "make world" does a "make cleandir" at some stage. > >So if you are asking whether I have done a make world recently >then my answer is "Yes, guilty as charged". > >If thats the cause of the problem then libmp's Makefile needs >some work. >On the whole I dont mess with my source tree. You may not believe >me now that my mistake with the TODO-2.1 directory is known but >you'll have to take my word for it. I do not doubt that you did not intentionally do anything to cause the tree to get broken. I, too, feel that there is an error in the Makefile that caused the problem. However, I will point out that, contrary to prior claims, CTM was not the program which failed ..... We now return you to your more-difficult-to-fix problems. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 17:25:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25276 for freebsd-current-outgoing; Mon, 9 Mar 1998 17:25:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25212; Mon, 9 Mar 1998 17:25:28 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id MAA27613; Tue, 10 Mar 1998 12:26:01 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803100126.MAA27613@cimlogic.com.au> Subject: gcc alpha-elf works again To: peter@FreeBSD.ORG Date: Tue, 10 Mar 1998 12:26:01 +1100 (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 Peter, Your latest commit/s did the trick, thanks. -- 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 Mon Mar 9 17:46:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29592 for freebsd-current-outgoing; Mon, 9 Mar 1998 17:46:58 -0800 (PST) (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 RAA29583 for ; Mon, 9 Mar 1998 17:46:55 -0800 (PST) (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 BAA28312; Tue, 10 Mar 1998 01:46:01 GMT Date: Tue, 10 Mar 1998 10:46:00 +0900 (JST) From: Michael Hancock To: Anatoly Vorobey cc: Nate Williams , current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: <19980309194602.38788@techunix.technion.ac.il> 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, 9 Mar 1998, Anatoly Vorobey wrote: > > > > Traditional OOP does this right, since you inherit from the class below > > > > you, and not from the base class. If you want to inherit from the base > > > > class, you inherit from it and not a subclass. > > > > > > But do you get the mappings from layer1 and layer3? They both touch the > > > results that finally get to the top. > > > > If you want them to, then yes. > > So, does the stacking layer support multiple inheritance? :) Sort of. It's called fan-out, where you have a single layer stacked across multiple lower layers. e.g. a vfs-based mirroring implementation or unionfs. Unionfs is pretty cool, your lower layer could be your cd and the upper layer could be a directory in an ffs system. You can compile over your cdrom as if it were writable. There's also fan-in where multiple layers are stacked horizontally across a single lower layer. Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 17:58:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03488 for freebsd-current-outgoing; Mon, 9 Mar 1998 17:58:13 -0800 (PST) (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 RAA03385 for ; Mon, 9 Mar 1998 17:57:59 -0800 (PST) (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 BAA28398; Tue, 10 Mar 1998 01:56:55 GMT Date: Tue, 10 Mar 1998 10:56:55 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: Dmitrij Tejblum , nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: <199803091958.MAA23552@usr05.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Mar 1998, Terry Lambert wrote: > The FFS/UFS inheritance is both more and less problematic. More, > because it is so fundamental to the system. Less, because it's > *almost* sufficiently abstract. Kirk's stated intent in the > seperation was to provide a flat inode namespace. Some of this has > been recently broken (via default vops and other changes), and some The flat-namespace filestore vop's were just taken out. They didn't really fit earlier since they didn't have vnodes associated with them. They were hand coded and bypass mechanisms were special cased to ignore them. This policy has changed recently so there's no reason not to bring them back, but a little work will need to be done to update them to include a vnode arg. Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 18:07:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06329 for freebsd-current-outgoing; Mon, 9 Mar 1998 18:07:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06083; Mon, 9 Mar 1998 18:06:45 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA26202; Tue, 10 Mar 1998 13:01:54 +1100 Date: Tue, 10 Mar 1998 13:01:54 +1100 From: Bruce Evans Message-Id: <199803100201.NAA26202@godzilla.zeta.org.au> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: *HEADS UP* Correction to previous postings. Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >The error in this case was the assumption that partitions on a dedicated >> >disk were handled as though they were truly equivalent to the >> >compatability slice entries. >> >> A correct assumption. > >This doesn't appear to be borne out in any consistent fashion. It is nevertheless correct. >> >This is not correct; rather they appear >> >as though they were in the first slice on the disk. >> >> Not with normal slice naming. The first slice (s1) doesn't exist on >> dangerously dedicated disks. Rev.1.88 of autoconf.c just breaks >> support for dangerously dedicated disks. Rev.1.87 was correct in >> this areas, except it spells COMPATIBILITY_SLICE as 0. > >That's odd then; libdisk calls them 'xdNs1', and you appear to be able >to mount them like that. Slice s1 has slice number 2. It is easy to confuse this with slice number 2. setroot() now suffers from this confusion. >More significantly, the bootstrap passes the invalid slice number 1 in; >using this is guaranteed to result in failure, as there aren't any >devices with a '1' in the slice field. Correct. >I believed that I had, actually, tested on a dedicated-disk system, >however it appears otherwise. 8( It broke immediately here. I lied about having a DOS partition table with all-zeros. I actually have one with the historical invalid partition table. This breaks in a different way. There are _three_ signifantly different configurations that give the whole disk to FreeBSD. See below. >I thought that I had established this correctly twice now, based on >code study and our earlier discussions. Can I please confirm, so that >this isn't screwed for good? > - If the slice number from the bootstrap is in the range BASE_SLICE to > MAX_SLICES, it is OK to insert this as-is into the root device minor > number. No. This breaks in my configuration with a historical invalid partition table (see biosboot/boot2.S). The boot blocks search this table and find slice 4 in it. They don't notice that it is invalid, so they pass slice 4 to the kernel. The kernel notices that it is invalid and gives only the compatibility slice, so the boot fails. Slice 4 must be mapped to slice COMPATIBILITY_SLICE (= 0) in this case. > - If the slice number is < BASE_SLICE, the correct minor for the root > device will have a 0 in the slice field. Correct, but it is better to write this rule as: - If the slice number is == WHOLE_DISK_SLICE, the correct minor for the root device will have COMPATIBILITY_SLICE in the slice field. >ie. I should be using COMPATABILITY_SLICE not BASE_SLICE in the test in >setroot()? Yes. Summary of the 3 cases where the whole disk is used for FreeBSD: Partition table config Slice# passed by bootblocks Slice# to use for "/" ---------------------- --------------------------- ------------------------- Signature != 0xAA55 WHOLE_DISK_SLICE (= 1) COMPATIBILITY_SLICE (= 0) Historical invalid BASE_SLICE + 3 (= 5) COMPATIBILITY_SLICE (= 0) "Valid" (1 big part.) BASE_SLICE + N (0 <= N < 4) BASE_SLICE + N User actions in the 3 cases: 1. Hope this doesn't happen. It is very unlikely to happen for boot disks. 2. Wait for fixes. 3. Same as for cases where the whole disk is not used for FreeBSD - edit /etc/fstab. There isn't really an all-zeros case. If the MBR signature is 0xAA55, then all-zeros in the partition table gives 4 slices of size 0. All-zeros in the MBR gives a signature of 0 so it reduces to the signature != 0xAA55 case. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 18:16:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08953 for freebsd-current-outgoing; Mon, 9 Mar 1998 18:16:17 -0800 (PST) (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 SAA08943 for ; Mon, 9 Mar 1998 18:16:11 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id UAA06146 for ; Mon, 9 Mar 1998 20:16:07 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id UAA15944; Mon, 9 Mar 1998 20:16:07 -0600 (CST) Message-ID: <19980309201607.46795@mcs.net> Date: Mon, 9 Mar 1998 20:16:07 -0600 From: Karl Denninger To: current@FreeBSD.ORG Subject: Attempting "make world" with /usr/obj mounted via NFS Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In process now with my last CVS update at about 6:30 PM (which found no changes). Will advise on the results. If this works then we're likely doing pretty well NFS-wise. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 18:36:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11808 for freebsd-current-outgoing; Mon, 9 Mar 1998 18:36:27 -0800 (PST) (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 SAA11798 for ; Mon, 9 Mar 1998 18:36:24 -0800 (PST) (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 CAA28704; Tue, 10 Mar 1998 02:35:19 GMT Date: Tue, 10 Mar 1998 11:35:19 +0900 (JST) From: Michael Hancock To: Dmitrij Tejblum cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: <199803092359.CAA03508@tejblum.dnttm.rssi.ru> 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 think vnode_pager_generic_(put|get)pages should be moved to vfs_default.c and renamed vop_std(put|get)pages. It would need to be modified to accept ap instead of 4 components of ap. Terry is trying to make it more visible to fs implementors so that they take the time to understand how to make VM friendly implementations. The "XXX - wimp out ..." comment is also added for extra emphasis. This comment should be taken out and replaced by a comment explaining what a VM friendly (get|put)pages should do. I think vfs_default.c is visible enough. This is a form discussion, the substance is the same. My personal opinion is that it doesn't belong vnode_pager.c because it will tend to be ignored by fs implementors. Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 18:59:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15721 for freebsd-current-outgoing; Mon, 9 Mar 1998 18:59:09 -0800 (PST) (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 SAA15602; Mon, 9 Mar 1998 18:58:01 -0800 (PST) (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 SAA17092; Mon, 9 Mar 1998 18:55:55 -0800 (PST) Message-Id: <199803100255.SAA17092@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bruce Evans cc: mike@smith.net.au, current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: *HEADS UP* Correction to previous postings. In-reply-to: Your message of "Tue, 10 Mar 1998 13:01:54 +1100." <199803100201.NAA26202@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Mar 1998 18:55:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I believed that I had, actually, tested on a dedicated-disk system, > >however it appears otherwise. 8( > > It broke immediately here. I lied about having a DOS partition table > with all-zeros. I actually have one with the historical invalid > partition table. This breaks in a different way. There are _three_ > signifantly different configurations that give the whole disk to > FreeBSD. See below. This is the problem; I had the understanding that there was only one. > >I thought that I had established this correctly twice now, based on > >code study and our earlier discussions. Can I please confirm, so that > >this isn't screwed for good? > > > - If the slice number from the bootstrap is in the range BASE_SLICE to > > MAX_SLICES, it is OK to insert this as-is into the root device minor > > number. > > No. This breaks in my configuration with a historical invalid partition > table (see biosboot/boot2.S). The boot blocks search this table and > find slice 4 in it. They don't notice that it is invalid, so they pass > slice 4 to the kernel. The kernel notices that it is invalid and gives > only the compatibility slice, so the boot fails. Slice 4 must be mapped > to slice COMPATIBILITY_SLICE (= 0) in this case. This is the case where the disk has been initialised with 'disklabel auto', it seems. > > - If the slice number is < BASE_SLICE, the correct minor for the root > > device will have a 0 in the slice field. > > Correct, but it is better to write this rule as: > > - If the slice number is == WHOLE_DISK_SLICE, the correct minor for the > root device will have COMPATIBILITY_SLICE in the slice field. OK. > >ie. I should be using COMPATABILITY_SLICE not BASE_SLICE in the test in > >setroot()? > > Yes. > > Summary of the 3 cases where the whole disk is used for FreeBSD: > > Partition table config Slice# passed by bootblocks Slice# to use for "/" > ---------------------- --------------------------- ------------------------- > Signature != 0xAA55 WHOLE_DISK_SLICE (= 1) COMPATIBILITY_SLICE (= 0) > Historical invalid BASE_SLICE + 3 (= 5) COMPATIBILITY_SLICE (= 0) > "Valid" (1 big part.) BASE_SLICE + N (0 <= N < 4) BASE_SLICE + N There appears to be no means for differentiating the "historical invalid" case from the "valid" case where the first FreeBSD slice has N == 3, given the constraints under which setroot() is operating. (Note that "valid" above is a subset of any FreeBSD slice being anywhere on the disk. It is this subset that the sysinstall "all disk/no" option generates.) Do you have any suggestions for making this differentiation? Altering the bootstrap is not practical at this point in time, as it hamstrings upgraders. > User actions in the 3 cases: > 1. Hope this doesn't happen. It is very unlikely to happen for boot disks. > 2. Wait for fixes. > 3. Same as for cases where the whole disk is not used for FreeBSD - edit > /etc/fstab. I would like to find a fix for 2. that doesn't involve going backwards to the 'bad old days', but this seems difficult just now. -- \\ 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 Mar 9 19:00:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16396 for freebsd-current-outgoing; Mon, 9 Mar 1998 19:00:57 -0800 (PST) (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 TAA16365 for ; Mon, 9 Mar 1998 19:00:46 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id SAA28146; Mon, 9 Mar 1998 18:55:31 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd028144; Mon Mar 9 18:55:25 1998 Message-ID: <3504AA9A.7566F4CF@whistle.com> Date: Mon, 09 Mar 1998 18:51:06 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Ollivier Robert , current@FreeBSD.ORG, mckusick@mcKusick.com Subject: Re: page fault (-current && softupdates) References: <19980308230222.A9458@keltia.freenix.fr> <13409.889399148@critter.freebsd.dk> <19980309233834.A297@keltia.freenix.fr> <35048708.6201DD56@whistle.com> Content-Type: multipart/mixed; boundary="------------4DAA423A3359056542877E5C" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------4DAA423A3359056542877E5C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Julian Elischer wrote: > > Here's a bit more info on teh Soft Update problem.. > > And here's another dump: --------------4DAA423A3359056542877E5C Content-Type: text/plain; charset=iso-8859-1; name="gdb3" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="gdb3" Once again.. note that: BC == bcopy that makes a stack frame. Script started on Tue Mar 10 02:06:49 1998 phaser2# gdb GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc. Debugger (msg=0xf01195ec "panic") at ../../i386/i386/db_interface.c:319 319 } (gdb) wg here #0 Debugger (msg=0xf01195ec "panic") at ../../i386/i386/db_interface.c:319 #1 0xf011964e in panic ( fmt=0xf01cc297 "vm_fault: fault on nofault entry, addr: %lx") at ../../kern/kern_shutdown.c:434 #2 0xf01cc42e in vm_fault (map=0xf0265adc, vaddr=4052631552, fault_type=3 '\003', fault_flags=0) at ../../vm/vm_fault.c:233 #3 0xf01ecf48 in trap_pfault (frame=0xf2c66c80, usermode=0) at ../../i386/i386/trap.c:724 #4 0xf01ecbc7 in trap (frame={tf_es = 16, tf_ds = -222429168, tf_edi = -242335744, tf_esi = -242575360, tf_ebp = -221877036, tf_isp = -221877080, tf_ebx = -248785580, tf_edx = 0, tf_ecx = 512, tf_eax = 239616, tf_trapno = 12, tf_err = 2, tf_eip = -266421574, tf_cs = 8, tf_eflags = 66054, tf_esp = -259861696, tf_ss = -260514784}) at ../../i386/i386/trap.c:363 #5 0xf01e3901 in calltrap () #6 0xf01bc2b6 in setup_allocindir_phase2 (bp=0xf12bd554, ip=0xf0866400, aip=0xf082d340) at ../../ufs/ffs/ffs_softdep.c:1537 #7 0xf01bbf7b in softdep_setup_allocindir_page (ip=0xf0866400, lbn=45, bp=0xf12bd554, ptrno=33, newblkno=230792, oldblkno=0, nbp=0xf12c3094) at ../../ufs/ffs/ffs_softdep.c:1419 #8 0xf01b94ed in ffs_balloc (ap=0xf2c66ea4) at ../../ufs/ffs/ffs_balloc.c:302 #9 0xf01c2d0c in ffs_write (ap=0xf2c66ef8) at vnode_if.h:995 #10 0xf013de97 in vn_write (fp=0xf08c6e40, uio=0xf2c66f40, cred=0xf0706800) at vnode_if.h:331 ---Type to continue, or q to quit---up 6     #11 0xf012122b in write (p=0xf2bf2f80, uap=0xf2c66f94) at ../../kern/sys_generic.c:268 #12 0xf01ed7af in syscall (frame={tf_es = -272695257, tf_ds = -221904857, tf_edi = 123588, tf_esi = 888832, tf_ebp = -272649576, tf_isp = -221876252, tf_ebx = 123588, tf_edx = 0, tf_ecx = 0, tf_eax = 4, tf_trapno = 12, tf_err = 7, tf_eip = 116357, tf_cs = 31, tf_eflags = 518, tf_esp = -272649596, tf_ss = 39}) at ../../i386/i386/trap.c:994 #13 0xf01e3955 in Xsyscall () #14 0x1a5b6 in ?? () #15 0x1a566 in ?? () #16 0x17720 in ?? () #17 0xf729 in ?? () #18 0x71e2 in ?? () #19 0xb5d2 in ?? () #20 0xbc55 in ?? () #21 0x5183 in ?? () #22 0x1459 in ?? () #23 0x107e in ?? () (gdb) up 6 #6 0xf01bc2b6 in setup_allocindir_phase2 (bp=0xf12bd554, ip=0xf0866400, aip=0xf082d340) at ../../ufs/ffs/ffs_softdep.c:1537 1537 BC((caddr_t)newindirdep->ir_saveddata, (gdb) list setup_allocindir_phase2 1447 static void 1448 setup_allocindir_phase2(bp, ip, aip) 1449 struct buf *bp; /* in-memory copy of the indirect block */ 1450 struct inode *ip; /* inode for file being extended */ 1451 struct allocindir *aip; /* allocindir allocated by the above routines */ 1452 { 1453 struct worklist *wk; 1454 struct indirdep *indirdep, *newindirdep; 1455 struct bmsafemap *bmsafemap; 1456 struct allocindir *oldaip; (gdb) 1457 struct freefrag *freefrag; 1458 struct newblk *newblk; 1459 1460 if (bp->b_lblkno >= 0) 1461 panic("setup_allocindir_phase2: not indir blk"); 1462 for (indirdep = NULL, newindirdep = NULL; ; ) { 1463 ACQUIRE_LOCK(&lk); 1464 for (wk = LIST_FIRST(&bp->b_dep); wk; 1465 wk = LIST_NEXT(wk, wk_list)) { 1466 if (wk->wk_type != D_INDIRDEP) (gdb) 1467 continue; 1468 indirdep = WK_INDIRDEP(wk); 1469 break; 1470 } 1471 if (indirdep == NULL && newindirdep) { 1472 indirdep = newindirdep; 1473 WORKLIST_INSERT(&bp->b_dep, &indirdep->ir_list); 1474 newindirdep = NULL; 1475 } 1476 FREE_LOCK(&lk); (gdb) 1477 if (indirdep) { 1478 if (newblk_lookup(ip->i_fs, aip->ai_newblkno, 0, 1479 &newblk) == 0) 1480 panic("setup_allocindir: lost block"); 1481 ACQUIRE_LOCK(&lk); 1482 if (newblk->nb_state == DEPCOMPLETE) { 1483 aip->ai_state |= DEPCOMPLETE; 1484 aip->ai_buf = NULL; 1485 } else { 1486 bmsafemap = newblk->nb_bmsafemap; (gdb) 1487 aip->ai_buf = bmsafemap->sm_buf; 1488 LIST_REMOVE(newblk, nb_deps); 1489 LIST_INSERT_HEAD(&bmsafemap->sm_allocindirhd, 1490 aip, ai_deps); 1491 } 1492 LIST_REMOVE(newblk, nb_hash); 1493 FREE(newblk, M_NEWBLK); 1494 aip->ai_indirdep = indirdep; 1495 /* 1496 * Check to see if there is an existing dependency (gdb) 1497 * for this block. If there is, merge the old 1498 * dependency into the new one. 1499 */ 1500 if (aip->ai_oldblkno == 0) 1501 oldaip = NULL; 1502 else 1503 for (oldaip=LIST_FIRST(&indirdep->ir_deplisthd); 1504 oldaip; oldaip = LIST_NEXT(oldaip, ai_next)) 1505 if (oldaip->ai_offset == aip->ai_offset) 1506 break; (gdb) 1507 if (oldaip != NULL) { 1508 if (oldaip->ai_newblkno != aip->ai_oldblkno) 1509 panic("setup_allocindir_phase2: blkno"); 1510 aip->ai_oldblkno = oldaip->ai_oldblkno; 1511 freefrag = oldaip->ai_freefrag; 1512 oldaip->ai_freefrag = aip->ai_freefrag; 1513 aip->ai_freefrag = freefrag; 1514 free_allocindir(oldaip, NULL); 1515 } 1516 LIST_INSERT_HEAD(&indirdep->ir_deplisthd, aip, ai_next); (gdb) 1517 ((ufs_daddr_t *)indirdep->ir_savebp->b_data) 1518 [aip->ai_offset] = aip->ai_oldblkno; 1519 FREE_LOCK(&lk); 1520 } 1521 if (newindirdep) { 1522 if (indirdep->ir_savebp != NULL) 1523 brelse(newindirdep->ir_savebp); 1524 WORKITEM_FREE((caddr_t)newindirdep, D_INDIRDEP); 1525 } 1526 if (indirdep) (gdb) 1527 break; 1528 MALLOC(newindirdep, struct indirdep *, sizeof(struct indirdep), 1529 M_INDIRDEP, M_WAITOK); 1530 newindirdep->ir_list.wk_type = D_INDIRDEP; 1531 newindirdep->ir_state = ATTACHED; 1532 LIST_INIT(&newindirdep->ir_deplisthd); 1533 LIST_INIT(&newindirdep->ir_donehd); 1534 newindirdep->ir_saveddata = (ufs_daddr_t *)bp->b_data; 1535 newindirdep->ir_savebp = 1536 getblk(ip->i_devvp, bp->b_blkno, bp->b_bcount, 0, 0); (gdb) 1537 BC((caddr_t)newindirdep->ir_saveddata, 1538 newindirdep->ir_savebp->b_data, bp->b_bcount); 1539 } 1540 } 1541 1542 /* 1543 * Block de-allocation dependencies. 1544 * 1545 * When blocks are de-allocated, the on-disk pointers must be nullified before 1546 * the blocks are made available for use by other files. (The true (gdb) up #7 0xf01bbf7b in softdep_setup_allocindir_page (ip=0xf0866400, lbn=45, bp=0xf12bd554, ptrno=33, newblkno=230792, oldblkno=0, nbp=0xf12c3094) at ../../ufs/ffs/ffs_softdep.c:1419 1419 setup_allocindir_phase2(bp, ip, aip); (gdb) p *bp $1 = {b_hash = {le_next = 0x0, le_prev = 0xf025f4dc}, b_vnbufs = { le_next = 0x0, le_prev = 0xf128fda4}, b_freelist = {tqe_next = 0xf12a7604, tqe_prev = 0xf128fdac}, b_act = {tqe_next = 0xf128eb5c, tqe_prev = 0xf0681dd4}, b_proc = 0x0, b_flags = 536870960, b_qindex = 0, b_usecount = 12 '\f', b_error = 0, b_bufsize = 8192, b_bcount = 8192, b_resid = 0, b_dev = 4294967295, b_data = 0xf18a8000 "ð\203\003", b_kvabase = 0xf18a8000 "ð\203\003", b_kvasize = 8192, b_lblkno = -12, b_blkno = -12, b_iodone = 0, b_iodone_chain = 0x0, b_vp = 0xf2c4d360, b_dirtyoff = 0, b_dirtyend = 0, b_generation = 967, b_rcred = 0x0, b_wcred = 0x0, b_validoff = 0, b_validend = 0, b_pblkno = 2430313, b_saveaddr = 0x0, b_savekva = 0x0, b_driver1 = 0x0, b_driver2 = 0x0, b_spc = 0x0, b_cluster = {cluster_head = {tqh_first = 0xf12b17fc, tqh_last = 0xf1287674}, cluster_entry = {tqe_next = 0xf12b17fc, tqe_prev = 0xf1287674}}, b_pages = {0xf0439ed8, 0xf046d20c, 0x0 }, b_npages = 2, b_dep = {lh_first = 0x0}} (gdb) p *ip $2 = {i_lock = {lk_interlock = {lock_data = 0}, lk_flags = 1024, lk_sharecount = 0, lk_waitcount = 0, lk_exclusivecount = 1, lk_prio = 8, lk_wmesg = 0xf01c1e2b "inode", lk_timo = 0, lk_lockholder = 2867}, i_hash = {le_next = 0x0, le_prev = 0xf06a4d7c}, i_vnode = 0xf2c4d360, i_devvp = 0xf2bef060, i_flag = 142, i_dev = 132102, i_number = 46937, i_effnlink = 1, inode_u = {fs = 0xf06b5000, e2fs = 0xf06b5000}, i_dquot = { 0x0, 0x0}, i_modrev = 0x35049bb806112e8c, i_lockf = 0x0, i_count = 0, i_endoff = 0, i_diroff = 0, i_offset = 0, i_ino = 0, i_reclen = 0, i_spare = {0, 0, 0, 0, 0}, i_din = {di_mode = 33188, di_nlink = 1, di_u = { oldids = {0, 0}, inumber = 0}, di_size = 458279, di_atime = 889494456, di_atimensec = 0, di_mtime = 889494493, di_mtimensec = 0, di_ctime = 889494493, di_ctimensec = 0, di_db = {200392, 200456, 200488, 200496, 200504, 200512, 200520, 200528, 200536, 200544, 200552, 200560}, di_ib = {230376, 0, 0}, di_flags = 0, di_blocks = 832, di_gen = 836009892, di_uid = 0, di_gid = 0, di_spare = {0, 0}}} (gdb) p aip $3 = (struct allocindir *) 0xf082d340 (gdb) p *aip $4 = {ai_list = {wk_list = {le_next = 0x0, le_prev = 0xf12c31b4}, wk_type = 6, wk_state = 32769}, ai_next = {le_next = 0x0, le_prev = 0x0}, ai_offset = 33, ai_newblkno = 230792, ai_oldblkno = 0, ai_freefrag = 0x0, ai_indirdep = 0x0, ai_deps = {le_next = 0x0, le_prev = 0x0}, ai_buf = 0x0} (gdb) list 1414 if ((ip->i_mode & IFMT) == IFDIR && 1415 pagedep_lookup(ip, lbn, DEPALLOC, &pagedep) == 0) 1416 WORKLIST_INSERT(&nbp->b_dep, &pagedep->pd_list); 1417 WORKLIST_INSERT(&nbp->b_dep, &aip->ai_list); 1418 FREE_LOCK(&lk); 1419 setup_allocindir_phase2(bp, ip, aip); 1420 } 1421 1422 /* 1423 * Called just before setting an indirect block pointer to a (gdb) p *nbp $5 = {b_hash = {le_next = 0xf129d89c, le_prev = 0xf025f5c0}, b_vnbufs = { le_next = 0xf12969f8, le_prev = 0xf2c4d390}, b_freelist = { tqe_next = 0xf129d2e8, tqe_prev = 0xf024be40}, b_act = {tqe_next = 0x0, tqe_prev = 0xf0681dd4}, b_proc = 0x0, b_flags = 536870928, b_qindex = 0, b_usecount = 5 '\005', b_error = 0, b_bufsize = 8192, b_bcount = 8192, b_resid = 0, b_dev = 4294967295, b_data = 0xf1948000 "", b_kvabase = 0xf1948000 "", b_kvasize = 8192, b_lblkno = 45, b_blkno = 461584, b_iodone = 0, b_iodone_chain = 0x0, b_vp = 0xf2c4d360, b_dirtyoff = 0, b_dirtyend = 0, b_generation = 961, b_rcred = 0x0, b_wcred = 0x0, b_validoff = 0, b_validend = 0, b_pblkno = 2067583, b_saveaddr = 0x0, b_savekva = 0x0, b_driver1 = 0x0, b_driver2 = 0x0, b_spc = 0x0, b_cluster = {cluster_head = {tqh_first = 0xf12c2c04, tqh_last = 0xf12b1524}, cluster_entry = {tqe_next = 0xf12c2c04, tqe_prev = 0xf12b1524}}, b_pages = {0xf043dd00, 0xf0438234, 0x0 }, b_npages = 2, b_dep = {lh_first = 0xf082d340}} (gdb) p lbn $6 = 45 (gdb) list 1424 * newly allocated indirect block. 1425 */ 1426 void 1427 softdep_setup_allocindir_meta(nbp, ip, bp, ptrno, newblkno) 1428 struct buf *nbp; /* newly allocated indirect block */ 1429 struct inode *ip; /* inode for file being extended */ 1430 struct buf *bp; /* indirect block referencing allocated block */ 1431 int ptrno; /* offset of pointer in indirect block */ 1432 ufs_daddr_t newblkno; /* disk block number being added */ 1433 { (gdb) down #6 0xf01bc2b6 in setup_allocindir_phase2 (bp=0xf12bd554, ip=0xf0866400, aip=0xf082d340) at ../../ufs/ffs/ffs_softdep.c:1537 1537 BC((caddr_t)newindirdep->ir_saveddata, (gdb) list 1532 LIST_INIT(&newindirdep->ir_deplisthd); 1533 LIST_INIT(&newindirdep->ir_donehd); 1534 newindirdep->ir_saveddata = (ufs_daddr_t *)bp->b_data; 1535 newindirdep->ir_savebp = 1536 getblk(ip->i_devvp, bp->b_blkno, bp->b_bcount, 0, 0); 1537 BC((caddr_t)newindirdep->ir_saveddata, 1538 newindirdep->ir_savebp->b_data, bp->b_bcount); 1539 } 1540 } 1541 (gdb) p newindirdep $7 = (struct indirdep *) 0xf18a9800 (gdb) p *$7 $8 = {ir_list = {wk_list = {le_next = 0x0, le_prev = 0x0}, wk_type = 0, wk_state = 0}, ir_saveddata = 0x0, ir_savebp = 0x0, ir_donehd = { lh_first = 0x0}, ir_deplisthd = {lh_first = 0x0}} (gdb) list      quit The program is running. Quit anyway (and kill it)? (y or n) y phaser2# exit Script done on Tue Mar 10 02:09:50 1998 --------------4DAA423A3359056542877E5C-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 19:20:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20786 for freebsd-current-outgoing; Mon, 9 Mar 1998 19:20:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20776 for ; Mon, 9 Mar 1998 19:20:53 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id UAA07675; Mon, 9 Mar 1998 20:20:50 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd007608; Mon Mar 9 20:20:44 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id UAA23886; Mon, 9 Mar 1998 20:20:38 -0700 (MST) From: Terry Lambert Message-Id: <199803100320.UAA23886@usr09.primenet.com> Subject: Re: vnode_pager: *** WARNING *** stale FS code in system To: michaelh@cet.co.jp (Michael Hancock) Date: Tue, 10 Mar 1998 03:20:38 +0000 (GMT) Cc: tlambert@primenet.com, dima@tejblum.dnttm.rssi.ru, nate@mt.sri.com, current@FreeBSD.ORG In-Reply-To: from "Michael Hancock" at Mar 10, 98 10:56:55 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The flat-namespace filestore vop's were just taken out. They didn't > really fit earlier since they didn't have vnodes associated with them. > They were hand coded and bypass mechanisms were special cased to ignore > them. > > This policy has changed recently so there's no reason not to bring them > back, but a little work will need to be done to update them to include a > vnode arg. Yes. The flat namespace needs to be accessed via a naming (ie: vnode) mechanism. There are a lot of nice little hurdles in doing that, starting with the soft updates code (which wants to depend on them being there). 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 Mar 9 19:22:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21264 for freebsd-current-outgoing; Mon, 9 Mar 1998 19:22:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sphinx.lovett.com (root@sphinx.lovett.com [38.155.241.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA21196 for ; Mon, 9 Mar 1998 19:22:31 -0800 (PST) (envelope-from ade@lovett.com) Received: from sphinx.lovett.com [38.155.241.2] (ade) by sphinx.lovett.com with esmtp (Exim 1.82 #1) id 0yCFcW-0001LZ-00; Mon, 9 Mar 1998 21:22:24 -0600 To: current@FreeBSD.ORG Subject: Minor root device oddity Date: Mon, 09 Mar 1998 21:22:23 -0600 From: Ade Lovett Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a power failure (long story, don't ask :), I ended up having to rebuild my -current box this evening - last cvsup was at 0300 CST 03/09 On bootup, I see: ... changing root device to wd0s2a ... Which is kinda odd, since I don't actually have a slice 2 :) gorgon # fdisk wd0 ... The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) ... The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: /etc/fstab references (correctly) wd0s1[ab] for mondo-large partition and swap respectively, and the system appears to be working fine.. gorgon # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1a 6376860 331579 5535133 6% / procfs 4 4 0 100% /proc ... So why is there this boot message reference to slice 2? Confused. -aDe -- Ade Lovett. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 19:32:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23256 for freebsd-current-outgoing; Mon, 9 Mar 1998 19:32:34 -0800 (PST) (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 TAA23248 for ; Mon, 9 Mar 1998 19:32:33 -0800 (PST) (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 TAA17231; Mon, 9 Mar 1998 19:30:12 -0800 (PST) Message-Id: <199803100330.TAA17231@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ade Lovett cc: current@FreeBSD.ORG Subject: Re: Minor root device oddity In-reply-to: Your message of "Mon, 09 Mar 1998 21:22:23 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Mar 1998 19:30:11 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > After a power failure (long story, don't ask :), I ended up having to > rebuild my -current box this evening - last cvsup was at 0300 CST 03/09 > > On bootup, I see: > > ... > changing root device to wd0s2a Typo on my part. Ignore it for now; it'll go away when I fix what I half-fixed last time. -- \\ 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 Mar 9 19:51:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25867 for freebsd-current-outgoing; Mon, 9 Mar 1998 19:51:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25791; Mon, 9 Mar 1998 19:50:31 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA30899; Tue, 10 Mar 1998 14:42:34 +1100 Date: Tue, 10 Mar 1998 14:42:34 +1100 From: Bruce Evans Message-Id: <199803100342.OAA30899@godzilla.zeta.org.au> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: *HEADS UP* Correction to previous postings. Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> No. This breaks in my configuration with a historical invalid partition >> table (see biosboot/boot2.S). The boot blocks search this table and >> find slice 4 in it. They don't notice that it is invalid, so they pass >> slice 4 to the kernel. The kernel notices that it is invalid and gives >> only the compatibility slice, so the boot fails. Slice 4 must be mapped >> to slice COMPATIBILITY_SLICE (= 0) in this case. > >This is the case where the disk has been initialised with 'disklabel >auto', it seems. It depends whether the disk has a suitable existing DOS partition table (and perhaps a suitable BSD label). `disklabel' preserves the table if and only if the table (4 partition entries, not the signature) is not all-zero. `disklabel auto' only works if disk size (as guessed for the auto label) is the same as (or perhaps larger than) the size of the slice being labeled. The sizes will usually be the same if either a) the disk doesn't have any DOS partitions or labels - then `disklabel auto' will initialize the partition table. b) the disk has a DOS partition table with one partition covering the whole disk - then `disklabel auto' won't change the partition table. >> Partition table config Slice# passed by bootblocks Slice# to use for "/" >> ---------------------- --------------------------- ------------------------- >> Signature != 0xAA55 WHOLE_DISK_SLICE (= 1) COMPATIBILITY_SLICE (= 0) >> Historical invalid BASE_SLICE + 3 (= 5) COMPATIBILITY_SLICE (= 0) >> "Valid" (1 big part.) BASE_SLICE + N (0 <= N < 4) BASE_SLICE + N > >There appears to be no means for differentiating the "historical >invalid" case from the "valid" case where the first FreeBSD slice has >N == 3, given the constraints under which setroot() is operating. setroot() doesn't have many constraints. I think it can just attempt to open the device passed by the boot blocks, except in case 1. If this succeeds, then the disk must have real slices. If not, the error is probably caused by the boot blocks passing us the wrong device or unit, and we have worse problems than mistranslating the slice. >(Note that "valid" above is a subset of any FreeBSD slice being anywhere > on the disk. It is this subset that the sysinstall "all disk/no" > option generates.) Except "(1 big part.)" is supposed to restrict to the case where the partition covers the whole disk. It can still be an primary partition (slice 1-4). I don't know exactly what sysinstall does. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 20:18:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02141 for freebsd-current-outgoing; Mon, 9 Mar 1998 20:18:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sphinx.lovett.com (root@sphinx.lovett.com [38.155.241.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA02135 for ; Mon, 9 Mar 1998 20:18:56 -0800 (PST) (envelope-from ade@lovett.com) Received: from sphinx.lovett.com [38.155.241.2] (ade) by sphinx.lovett.com with esmtp (Exim 1.82 #1) id 0yCGV5-0001QT-00; Mon, 9 Mar 1998 22:18:47 -0600 To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: Minor root device oddity In-reply-to: Your message of "Mon, 09 Mar 1998 19:30:11 PST." <199803100330.TAA17231@dingo.cdrom.com> Date: Mon, 09 Mar 1998 22:18:47 -0600 From: Ade Lovett Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > >Typo on my part. Ignore it for now; it'll go away when I fix what I >half-fixed last time. Right-ho. I'd pretty much convinced myself that it was a +1 typo somewhere, but I just wanted to make sure I hadn't hosed something in the rebuild, or got a weird source tree (at least, no weirder than normal :) from cvs update etc.. etc.. it's been one of those days :) -aDe -- Ade Lovett. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 20:37:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04862 for freebsd-current-outgoing; Mon, 9 Mar 1998 20:37:31 -0800 (PST) (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 UAA04849 for ; Mon, 9 Mar 1998 20:37:23 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id WAA02107; Mon, 9 Mar 1998 22:49:30 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Mon, 9 Mar 1998 22:49:30 -0500 (EST) From: "Alok K. Dhir" To: ade@lovett.com cc: current@FreeBSD.ORG Subject: Re: Minor root device oddity In-Reply-To: <286DB07EE20512FD852565C300134F72.00122E78852565C3@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 Similarly, my machine, whose root file system is on sd0s2a, claims "changing root device to sd0s3a" during boot. I suspect someone's code is simply off by 1... Machine works fine, and "mount" correctly reflects the mounted partition. My machine was also built today... Al On Mon, 9 Mar 1998 ade@lovett.com wrote: > > > > After a power failure (long story, don't ask :), I ended up having to > rebuild my -current box this evening - last cvsup was at 0300 CST 03/09 > > On bootup, I see: > > ... > changing root device to wd0s2a > ... > > Which is kinda odd, since I don't actually have a slice 2 :) > > gorgon # fdisk wd0 > ... > The data for partition 1 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > ... > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > > > /etc/fstab references (correctly) wd0s1[ab] for mondo-large partition > and swap respectively, and the system appears to be working fine.. > > gorgon # df > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/wd0s1a 6376860 331579 5535133 6% / > procfs 4 4 0 100% /proc > ... > > So why is there this boot message reference to slice 2? > > Confused. > -aDe > > -- > Ade Lovett. > > 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 \ R7-003, ITSMC 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 Mon Mar 9 20:38:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05565 for freebsd-current-outgoing; Mon, 9 Mar 1998 20:38:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05264; Mon, 9 Mar 1998 20:38:13 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id BAA04547; Tue, 10 Mar 1998 01:37:28 -0300 (EST) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199803100437.BAA04547@gaia.coppe.ufrj.br> Subject: Re: *HEADS UP* Correction to previous postings. In-Reply-To: <199803100201.NAA26202@godzilla.zeta.org.au> from Bruce Evans at "Mar 10, 98 01:01:54 pm" To: bde@zeta.org.au (Bruce Evans) Date: Tue, 10 Mar 1998 01:37:28 -0300 (EST) Cc: bde@zeta.org.au, mike@smith.net.au, current@FreeBSD.ORG, stable@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 #define quoting(Bruce Evans) // Summary of the 3 cases where the whole disk is used for FreeBSD: // // Partition table config Slice# passed by bootblocks Slice# to use for "/" // ---------------------- --------------------------- ------------------------- // Signature != 0xAA55 WHOLE_DISK_SLICE (= 1) COMPATIBILITY_SLICE (= 0) // Historical invalid BASE_SLICE + 3 (= 5) COMPATIBILITY_SLICE (= 0) // "Valid" (1 big part.) BASE_SLICE + N (0 <= N < 4) BASE_SLICE + N // // User actions in the 3 cases: // 1. Hope this doesn't happen. It is very unlikely to happen for boot disks. Most PC BIOSes (if not all) will not boot from a disk if the first block does not have the 0xAA55 signature. Indeed, they will not boot without a valid MBR. Have you ever seen such a case ? Or does this discussion apply to PC98 (from which I have no info, and don't know if the above is still true) and Alpha ports ? // 2. Wait for fixes. // 3. Same as for cases where the whole disk is not used for FreeBSD - edit // /etc/fstab. Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 20:50:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08264 for freebsd-current-outgoing; Mon, 9 Mar 1998 20:50: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 UAA08253 for ; Mon, 9 Mar 1998 20:50:21 -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 OAA22738; Mon, 9 Mar 1998 14:24:13 -0600 (CST) Message-ID: <19980309142412.10242@urh.uiuc.edu> Date: Mon, 9 Mar 1998 14:24:13 -0600 From: dannyman To: freebsd-current@FreeBSD.ORG Subject: funny logs messages - calcru/adjkerntz Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i 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 Hey folks, is there anything "bad" indicated by this rather strnge message? :) thanks! danny ----- Forwarded message from Charlie Root ----- arh0300 kernel log messages: > calcru: negative time of -3384 usec for pid 26 (adjkerntz) > calcru: negative time of -3384 usec for pid 26 (adjkerntz) > calcru: negative time of -3384 usec for pid 26 (adjkerntz) > calcru: negative time of -3384 usec for pid 26 (adjkerntz) > pid 28527 (conftest), uid 0: exited on signal 6 (core dumped) > stray irq 7 > too many stray irq 7's; not logging any more ----- End forwarded message ----- -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 20:54:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08903 for freebsd-current-outgoing; Mon, 9 Mar 1998 20:54:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hotmail.com (f15.hotmail.com [207.82.250.26]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA08894 for ; Mon, 9 Mar 1998 20:54:44 -0800 (PST) (envelope-from brianfeldman@hotmail.com) Received: (qmail 3986 invoked by uid 0); 10 Mar 1998 04:54:13 -0000 Message-ID: <19980310045413.3985.qmail@hotmail.com> Received: from 153.34.49.181 by www.hotmail.com with HTTP; Mon, 09 Mar 1998 20:54:12 PST X-Originating-IP: [153.34.49.181] From: "Brian Feldman" To: freebsd-current@FreeBSD.ORG Subject: de0 problems Content-Type: text/plain Date: Mon, 09 Mar 1998 20:54:12 PST Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to notice something strange in this ifconfig: the 4th quad of that cards IP's seems to be the same for its broadcast each, but the first one has a different netmask and references another IP. Are you certain this is correct? Brian Feldman brianfeldman@hotmail.com >de0: flags=8843 mtu 1500 > inet xxx.yyy.zzz.161 netmask 0xffffffc0 broadcast >xxx.yyy.zzz.191 > inet xxx.yyy.zzz.162 netmask 0xffffffff broadcast >xxx.yyy.zzz.162 > inet xxx.yyy.zzz.163 netmask 0xffffffff broadcast >xxx.yyy.zzz.163 > inet xxx.yyy.zzz.164 netmask 0xffffffff broadcast >xxx.yyy.zzz.164 > inet xxx.yyy.zzz.165 netmask 0xffffffff broadcast >xxx.yyy.zzz.165 > inet xxx.yyy.zzz.166 netmask 0xffffffff broadcast >xxx.yyy.zzz.166 > ether 00:80:c8:2b:db:08 > media: 10baseT/UTP status: active > supported media: autoselect 10base5/AUI manual 10baseT/UTP > 10baseT/UTP ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 21:00:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09938 for freebsd-current-outgoing; Mon, 9 Mar 1998 21:00:00 -0800 (PST) (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 UAA09908 for ; Mon, 9 Mar 1998 20:59:50 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 827 invoked from network); 10 Mar 1998 04:59:30 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 10 Mar 1998 04:59:30 -0000 Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id UAA19095; Mon, 9 Mar 1998 20:59:47 -0800 (PST) (envelope-from scottm) Date: Mon, 9 Mar 1998 20:59:47 -0800 (PST) From: Scott Michel Message-Id: <199803100459.UAA19095@mordred.cs.ucla.edu> To: ade@lovett.com, adhir@worldbank.org Subject: Re: Minor root device oddity Cc: current@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I saw this as well. Here's a temporary workaround until the patch makes it into the suppository: 1. Boot off kernel, single user 2. Mount everything: mount -a -t ufs (ignore the spooge about the root disk and fsck.) 3. TMPDIR=/var/tmp TEMPDIR=/var/tmp export TMPDIR TEMPDIR 4. Edit your configuration, change 'sd0a' to 'sd0s2a', and recompile your kernel. 5. mount /dev/sd0s2a /mnt 6. chflags noschg /mnt/kernel 7. install -c -m 555 -o root -g wheel -fschg kernel /mnt 8. reboot You should be right as rain afterwards, insulated from the current madness. Righteous burr under the saddle. Someone should have put out a bright neon sign e-mail two weeks before they checked this in. Possibly the low SNR in the current "Let's beat on Terry's stackable FS idea" caused me to miss it. >Similarly, my machine, whose root file system is on sd0s2a, claims >"changing root device to sd0s3a" during boot. I suspect someone's code is >simply off by 1... >Machine works fine, and "mount" correctly reflects the mounted partition. >My machine was also built today... >Al >On Mon, 9 Mar 1998 ade@lovett.com wrote: >> >> >> >> After a power failure (long story, don't ask :), I ended up having to >> rebuild my -current box this evening - last cvsup was at 0300 CST 03/09 >> >> On bootup, I see: >> >> ... >> changing root device to wd0s2a >> ... >> >> Which is kinda odd, since I don't actually have a slice 2 :) >> >> gorgon # fdisk wd0 >> ... >> The data for partition 1 is: >> sysid 165,(FreeBSD/NetBSD/386BSD) >> ... >> The data for partition 2 is: >> >> The data for partition 3 is: >> >> The data for partition 4 is: >> >> >> /etc/fstab references (correctly) wd0s1[ab] for mondo-large partition >> and swap respectively, and the system appears to be working fine.. >> >> gorgon # df >> Filesystem 1K-blocks Used Avail Capacity Mounted on >> /dev/wd0s1a 6376860 331579 5535133 6% / >> procfs 4 4 0 100% /proc >> ... >> >> So why is there this boot message reference to slice 2? >> >> Confused. >> -aDe >> >> -- >> Ade Lovett. -- Scott Michel | In life, there are sheep and there are UCLA Computer Science | wolves. PhD Graduate Student | ... One flogged vole later ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 21:01:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10513 for freebsd-current-outgoing; Mon, 9 Mar 1998 21:01:57 -0800 (PST) (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 VAA10484 for ; Mon, 9 Mar 1998 21:01:49 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id XAA15436 for ; Mon, 9 Mar 1998 23:01:45 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id XAA20715; Mon, 9 Mar 1998 23:01:44 -0600 (CST) Message-ID: <19980309230144.54743@mcs.net> Date: Mon, 9 Mar 1998 23:01:44 -0600 From: Karl Denninger To: current@FreeBSD.ORG Subject: Well, NFS is not QUITE there Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, its not quite there. I got a "premature EOF" in the libf77 library during the make world (with /usr/obj mounted over NFS). "make clean; make" in that directory ran to completion. Its probably safe to assume that one of the .o files got trashed. Kernel is: FreeBSD 3.0-CURRENT #0: Sun Mar 8 19:09:40 CST 1998 karl@Codebase.mcs.net:/usr/src/sys/compile/MCS_NFS I SUPped just before building this. John, can you confirm that this should have had all your fixes in it? The NFS "megacommit" *IS* in this build. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 21:09:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12782 for freebsd-current-outgoing; Mon, 9 Mar 1998 21:09:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12730 for ; Mon, 9 Mar 1998 21:09:46 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.8) with ESMTP id WAA06117; Mon, 9 Mar 1998 22:45:08 -0600 (CST) (envelope-from ccsanady@friley585.res.iastate.edu) Message-Id: <199803100445.WAA06117@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: ccsanady@iastate.edu cc: freebsd-current@FreeBSD.ORG Subject: (fixed) Was: Filesystem recovery procedures (please help..) In-reply-to: Your message of "Mon, 09 Mar 1998 11:48:46 CST." <199803091748.LAA00499@friley63.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Mar 1998 22:45:08 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >After recent recently trying to install the cam patches, >I seemed to have been left with a system that simply >would not boot. It would get to the place where it mounts >root, and then ti would hang. I have tried new kernels, >cam kernels, recent kernels, old generic kernels, all without >luck. Anyways, I finally just went to reinstall(upgrade) to >fix the problems. I must have screwed up the device nodes here, I'm not really sure what happened though. :\ Seems to work now after removing them all and recreating them. This is annoying to do from a fixit floppy, because too many paths are hardcoded into MAKEDEV. :( Anyways I can now boot as well.. >Unfortunately, somehow, the install disk seems to have toasted >the disklabels on both of my disks with very little effort. :( >It did leave the bios partitions intact though. > >Can anyone please tell me how to go about recovering? Will I >need to manually grovel the disk for this information? I also >have ccds that contain my home dir, so I would like these back >as well. I unfortunately do not have real recent backups, or >a way of making them. I seemed to have fixed the damage (after many painful hours...) For anyone interested, this is how I went about it. First, I set a disklabel partition to include all the space in the bios partition. After you do this, you can use dumpfs on the partition to figure out its length. I've found that fsck is a simple way to determine if the partition is/is not part of a ccd, as it majorly complians. :) After I have found one, try the remaining space, etc, until there is none left. This seems fairly simple, if your partitions are actually back to back. Takes a while though.. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 21:20:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14805 for freebsd-current-outgoing; Mon, 9 Mar 1998 21:20:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14776; Mon, 9 Mar 1998 21:20:45 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA02316; Tue, 10 Mar 1998 16:17:41 +1100 Date: Tue, 10 Mar 1998 16:17:41 +1100 From: Bruce Evans Message-Id: <199803100517.QAA02316@godzilla.zeta.org.au> To: bde@zeta.org.au, jonny@coppe.ufrj.br Subject: Re: *HEADS UP* Correction to previous postings. Cc: current@FreeBSD.ORG, mike@smith.net.au, stable@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >// User actions in the 3 cases: >// 1. Hope this doesn't happen. It is very unlikely to happen for boot disks. > >Most PC BIOSes (if not all) will not boot from a disk if the first block >does not have the 0xAA55 signature. Indeed, they will not boot without >a valid MBR. The FreeBSD boot blocks can boot from any fd, wd, sd or wfd disk supported by the BIOS. >Have you ever seen such a case ? Or does this discussion apply to I probably have, but don't remember. One of my systems loads the boot blocks from wd0 and the boot blocks the kernel from sd0. sd0 is all-FreeBSD and would work with all-zeros in the MBR. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 9 22:06:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20634 for freebsd-current-outgoing; Mon, 9 Mar 1998 22:06:07 -0800 (PST) (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 WAA20552 for ; Mon, 9 Mar 1998 22:05:44 -0800 (PST) (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 CAA17722; Tue, 10 Mar 1998 02:06:25 GMT Message-ID: <000201bd4be9$f102d600$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: "Alexander Litvin" , Subject: Re: What does that mean? (THANK GOD) Date: Mon, 9 Mar 1998 13:02:39 -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 i've been getting the same error since a makeworld yesterday... i'm breathing a sigh of relief cause i thought maybe my swap partition had gone bad ;) -Alfred -----Original Message----- From: Alexander Litvin To: current@FreeBSD.ORG Date: Monday, March 09, 1998 5:40 AM Subject: What does that mean? >Sorry for bothering you... > >I just tried 'tail ' and got "Segmentation fault". On the >console: > >spec_getpages: I/O read failure: (error code=0) > size: 4096, resid: 0, a_count: 3586, valid: 0x0 > nread: 4096, reqpage: 1, pindex: 21, pcount: 1 >vm_fault: pager input (probably hardware) error, PID 18023 failure >Mar 9 15:48:51 grape /kernel: pid 18023 (tail), uid 0: exited on signal 11 > >The second attempt to issue the same command succeded. > >Is it really hardware-related, or... > >CURRENT of yesterday. > >--- >"Truth is stranger than fiction, because fiction has to make sense." > >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 Mar 9 22:43:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24557 for freebsd-current-outgoing; Mon, 9 Mar 1998 22:43:06 -0800 (PST) (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 WAA24551 for ; Mon, 9 Mar 1998 22:43:04 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id BAA02333 for ; Tue, 10 Mar 1998 01:42:33 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Tue, 10 Mar 1998 01:42:33 -0500 (EST) From: "Alok K. Dhir" To: current@FreeBSD.ORG Subject: Re: sound in -current (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any ideas? Thanks... ---------- Forwarded message ---------- Date: Tue, 10 Mar 1998 01:00:17 -0500 From: luigi@labinfo.iet.unipi.it To: Alok_K._Dhir/Person/World_Bank@worldbank.org Cc: multimedia@FreeBSD.ORG Subject: Re: sound in -current > Sound has been broken in -current (for me, anyway) since roughly March 2. > I supped and rebuilt a kernel today, and the machine still completely > locks up, requiring a hard reboot, as soon as I try to play any sounds. not the first time i hear such a complaint, just i am not sure what the problem can be, since i don't follow -current. the only thing which comes to mind could be something related to dma activity ? 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 Mon Mar 9 22:54:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26969 for freebsd-current-outgoing; Mon, 9 Mar 1998 22:54:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from luoqi.watermarkgroup.com (luoqi.watermarkgroup.com [207.202.73.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26946 for ; Mon, 9 Mar 1998 22:54:25 -0800 (PST) (envelope-from src@luoqi.watermarkgroup.com) Received: (from src@localhost) by luoqi.watermarkgroup.com (8.8.8/8.8.8) id BAA00289 for current@freebsd.org; Tue, 10 Mar 1998 01:54:20 -0500 (EST) (envelope-from src) Date: Tue, 10 Mar 1998 01:54:20 -0500 (EST) From: Source Code Message-Id: <199803100654.BAA00289@luoqi.watermarkgroup.com> To: current@FreeBSD.ORG Subject: Enabling softupdates for root filesystem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With the lastest softupdates code cvsupped, there's no way to enable softupdates for the root partition, no matter what I tried (single user, fixit floppy, boot off another disk). It turned out that when upgrading the root mount from r/o to r/w, no attempt was made to enable the softupdate code. The following patch would do the trick, Index: ffs_vfsops.c =================================================================== RCS file: /fun/cvs/src/sys/ufs/ffs/ffs_vfsops.c,v retrieving revision 1.76 diff -u -r1.76 ffs_vfsops.c --- ffs_vfsops.c 1998/03/08 09:59:06 1.76 +++ ffs_vfsops.c 1998/03/10 06:38:39 @@ -241,6 +241,12 @@ VOP_UNLOCK(devvp, 0, p); } + if ((fs->fs_flags & FS_DOSOFTDEP) && + (error = softdep_mount(ump->um_devvp, mp, + fs, p->p_ucred)) != 0) { + return (error); + } + fs->fs_ronly = 0; } if (fs->fs_ronly == 0) { ----------- -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 00:05:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06278 for freebsd-current-outgoing; Tue, 10 Mar 1998 00:05:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from techunix.technion.ac.il (mellon@techunix.technion.ac.il [132.68.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06269 for ; Tue, 10 Mar 1998 00:05:35 -0800 (PST) (envelope-from mellon@techunix.technion.ac.il) Received: (from mellon@localhost) by techunix.technion.ac.il (8.8.7/8.8.5) id KAA21316; Tue, 10 Mar 1998 10:05:10 +0200 (IST) Message-ID: <19980310100509.15018@techunix.technion.ac.il> Date: Tue, 10 Mar 1998 10:05:09 +0200 From: Anatoly Vorobey To: "reggie@aa.net" Cc: "'Anatoly Vorobey'" , Nate Williams , "current@FreeBSD.ORG" Subject: Re: RE: vnode_pager: *** WARNING *** stale FS code in system References: <01BD4B55.F28C0D50.reggie@aa.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <01BD4B55.F28C0D50.reggie@aa.net>; from Reginald S. Perry on Mon, Mar 09, 1998 at 12:21:53PM -0800 X-Disclaimer: I was young, I needed the money! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You, Reginald S. Perry, were spotted writing this on Mon, Mar 09, 1998 at 12:21:53PM -0800: > On Monday, March 09, 1998 9:46 AM, Anatoly Vorobey > [SMTP:mellon@pobox.com] wrote: > > > > P.S. In fact, the VFS framework (more precisely, one of its > > predecessors, Sun's vnode system) is mentioned in at least one > > book on Java as an example to what pains these poor C programmers > > must go in order to create OOP-like FS interface, and how easily > > you would do that in Java ;) > > > > Actually, wouldn't it be a pain in the butt to do unionFS in Java > because of the lack of multiple inheritance? Not necessarily, since you actually have one "interface" (i.e. VFS); you don't really need multiple inheritance, you need to control several objects of the same class in your implementation. So you lose inheritance and use containment: you have private members which are handles to the FSes you overlay upon. I won't comment, on the other hand, on wisdom of doing _any_ FS in Java... :) -- Anatoly Vorobey, mellon@pobox.com http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 00:28:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09458 for freebsd-current-outgoing; Tue, 10 Mar 1998 00:28:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA09441; Tue, 10 Mar 1998 00:28:41 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: by watermarkgroup.com (4.1/SMI-4.1) id AA26647; Tue, 10 Mar 98 03:27:32 EST Date: Tue, 10 Mar 98 03:27:32 EST From: luoqi@watermarkgroup.com (Luoqi Chen) Message-Id: <9803100827.AA26647@watermarkgroup.com> To: bde@zeta.org.au, mike@smith.net.au Subject: Re: *HEADS UP* Correction to previous postings. Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Summary of the 3 cases where the whole disk is used for FreeBSD: > > > > Partition table config Slice# passed by bootblocks Slice# to use for "/" > > ---------------------- --------------------------- ------------------------- > > Signature != 0xAA55 WHOLE_DISK_SLICE (= 1) COMPATIBILITY_SLICE (= 0) > > Historical invalid BASE_SLICE + 3 (= 5) COMPATIBILITY_SLICE (= 0) > > "Valid" (1 big part.) BASE_SLICE + N (0 <= N < 4) BASE_SLICE + N > > There appears to be no means for differentiating the "historical > invalid" case from the "valid" case where the first FreeBSD slice has > N == 3, given the constraints under which setroot() is operating. > > (Note that "valid" above is a subset of any FreeBSD slice being anywhere > on the disk. It is this subset that the sysinstall "all disk/no" > option generates.) > > Do you have any suggestions for making this differentiation? Altering > the bootstrap is not practical at this point in time, as it hamstrings > upgraders. > > > User actions in the 3 cases: > > 1. Hope this doesn't happen. It is very unlikely to happen for boot disks. > > 2. Wait for fixes. > > 3. Same as for cases where the whole disk is not used for FreeBSD - edit > > /etc/fstab. > > I would like to find a fix for 2. that doesn't involve going backwards > to the 'bad old days', but this seems difficult just now. > I managed to modify boot2 so I was able to boot with -r1.87 autoconf.c from my dedicated disk (historical invalid). My solution was to leave slice to be WHOLE_DISK_SLICE for a BSD partition starts at sector 0 (this would bloat boot2 by two bytes: a je rel8). > -- > \\ 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 > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 00:51:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12978 for freebsd-current-outgoing; Tue, 10 Mar 1998 00:51:19 -0800 (PST) (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 AAA12972 for ; Tue, 10 Mar 1998 00:51:17 -0800 (PST) (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 AAA18205; Tue, 10 Mar 1998 00:49:03 -0800 (PST) Message-Id: <199803100849.AAA18205@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: luoqi@watermarkgroup.com (Luoqi Chen) cc: bde@zeta.org.au, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: *HEADS UP* Correction to previous postings. In-reply-to: Your message of "Tue, 10 Mar 1998 03:27:32 EST." <9803100827.AA26647@watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Mar 1998 00:49:02 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > User actions in the 3 cases: > > > 1. Hope this doesn't happen. It is very unlikely to happen for boot disks. > > > 2. Wait for fixes. > > > 3. Same as for cases where the whole disk is not used for FreeBSD - edit > > > /etc/fstab. > > > > I would like to find a fix for 2. that doesn't involve going backwards > > to the 'bad old days', but this seems difficult just now. > > > I managed to modify boot2 so I was able to boot with -r1.87 autoconf.c > from my dedicated disk (historical invalid). My solution was to leave slice > to be WHOLE_DISK_SLICE for a BSD partition starts at sector 0 (this would > bloat boot2 by two bytes: a je rel8). I'd love to do this, but it means a mandatory bootblock upgrade. Right now, that would be Very Bad, especially for 2.2. I think I have another solution, but I'm waiting on some feeback from Bruce before I get too carried away. He didn't like my first suggestion too much. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 00:57:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14270 for freebsd-current-outgoing; Tue, 10 Mar 1998 00:57:50 -0800 (PST) (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 AAA14262 for ; Tue, 10 Mar 1998 00:57:48 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id BAA17396; Tue, 10 Mar 1998 01:57:48 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpd017375; Tue Mar 10 01:57:38 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id BAA12940; Tue, 10 Mar 1998 01:57:35 -0700 (MST) From: Terry Lambert Message-Id: <199803100857.BAA12940@usr09.primenet.com> Subject: Re: vnode_pager: *** WARNING *** stale FS code in system To: mellon@pobox.com (Anatoly Vorobey) Date: Tue, 10 Mar 1998 08:57:35 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <19980309152125.08053@techunix.technion.ac.il> from "Anatoly Vorobey" at Mar 9, 98 03:21:25 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NOTE: This post has "some of the fun stuff" in it. I love this type of thing. 8-). This probably goes a tiny way towards Nate's "FS 101". > Probably a silly question, but still: > > What about the NFS as a whole? It's both a provider and a consumer > of VFS. Does it mean it's a stackable FS? (forgetting for a moment > the networking details; e.g. export and mount a local filesystem for > proof of concept). No. It's two seperate pieces, the client and the server. John Heidemann's net proxy layer (which allows you to stack two arbitrary layers across a network by proxying the argument descriptor contents and the VOP descriptor contents) isn't either (though it's a lot more useful than NFS. 8-)). > And if it does, how does it manage to exist if you're saying a lot > of work has to be done to make stackable FSs possible? It isn't a stackable FS. > Another question: which OSes _today_ provide for stackable file systems? > Not FreeBSD, apparently not Linux or Solaris. NT has got "filesystem > filters" kind of drivers which stack above the FS (and on each other > if needed) - this is neat and often useful - but hasn't got stackable > filesystems IIRC. Well, Windows 95 has them. I and two other guys ported the Heidemann framework to it for a commercial product. If FreeBSD had all the patches I did, and undid a couple of other changes (or they were redone in the Windows 95 code), *and* FreeBSD ran ELF -- then the same loadable modules could be used by both systems. 8-). SunOS has them (if you get the DES key from John and download the code off the UCLS CS Department FTP server). You can do something similar with the IFSMGR.VXD code in Windows95; it's called a "Miniport Driver". You can't do it to the VFAT.VXD or VFAT32.VXD, unfortunately, because MicroSoft implemented the TSD in the VFAT*.VXD. A TSD is a "Type Specific Driver"; it's what recognizes the partition ID and exports the "cooked device" to the rest of Windows95. You can do the same thing under NT. The documentation will run you $75,000. > A third question: can you give a (few?) example(s?) of hypothetical > useful stackable file systems, besides NULLFS? Sure. Let me make a definition, first: Namespace Escapes A namespace escape is used by a stacking layer to implement stacking layer specific storage. Namespace escapes can be implemented one of several ways: 1) A file on the root of the FS. The file is read and/or written by the stacking layer. The file may or may not be hidden. The stacking layer may or may not protect the file against modification by users. It uses the schg and sunlnk flags to protect against modification; it uses a new flag, shide to hide the file from directory lookups. It uses the sappnd if it wants to keep an immutable log. This implementation is called a "Namespace Incursion", because it puts a special file name in the namespace, and (potentially) obstructs the user from using the name. The user can tell it's there because it denies the user the use of the same name. This is the best way to implement a namespace escape, if you plan on mounting the FS both with and without the stacking layer (example: an FS which will be accessed by more than one OS), and you only need to store data that applies to the FS as a whole. 2) A file in each directory of the FS. This is the same as #1, but each directory has a file, instead of just the root. This is the best way to implement a namespace escape, if you plan on mounting the FS both with and without the stacking layer (example: an FS which will be accessed by more than one OS), and you only need to store data that applies to individual directories or files. 3) A "root-level redirection". A stacking layer that implements a root-level redirection makes it look like all user accesses to the root of the FS do not actually occur on the root of the FS. It does this by making a subdirectory, and pretending that the subdirectory is the root, every time it gets a request for the root (for instance, "./root"). It then keeps its own files and directories in the real root. This is the best way to implement a namespace escape, if you will *always* be mounting the FS with the stacking layer stacked over top of the underlying FS, and you only need to store data that applies to the FS as a whole. 4) A "directory-level redirection". A stacking layer that implements a directory-level redirection makes it look like all user accesses to each directory in the FS, including the root, are actually occuring on subdirectories. This is the classic "files are directories" type of implementation that you see Mac and OS/2 people lamenting for all of the time. When a file is created, you create a directory instead, create a file called "data" (or "default", or any other implementation defined name), and when the user goes to access the file by name, you act as if he had asked for the "data" file in the directory with the name of the file he asked for. You can then create other "streams" (or "forks" or "extended attributes") within the file. This is the best way to implement a namespace escape, if you will *always* be mounting the FS with the stacking layer stacked over top of the underlying FS, and you need to store data that applies to individual directories or files. 5) A "partial directory-level redirection". A stacking layer that implements a partial directory- -level redirection is actually implementing a sort of combination of #4 and #2. The stacking layer creates a hidden directory, and stores its own files in the directory, usually in a subdirectory with the same name as the file the data applies to, or just a file with the same name if it only needs one extra data stream per file. The actual files are still in the same place. This is the best way to implement a namespace escape, if you plan on mounting the FS both with and without the stacking layer (example: an FS which will be accessed by more than one OS), and you only need to store a lot of different types of data that apply to individual directories or files. OK, now onto the fun stuff. 8-). What kind of stacking FS layers can you build? Well, you are pretty much limited by your imagination. Here are 10 of them that I've thought up off the top of my head (I admit, I've been thinking about this for a while now, so several of them aren't original; you may have seen them before): QUOTFS This layer implements quotas using a file on the FS root. The file is hidden from normal users of the FS using either namespace escape technique #3, or it uses technique #1 so that you can put quotas on MSDOS FS's (which need to also be mounted by DOS/Windows). UMSDOSFS This layer implements compatibility with the Linux UMSDOSFS. It works using namespace escape technique #2, because it has to be compatible with Linux. In each directory, it looks for (and creates, if not present) a hidden file named "--LINUX-.---". This file stores things about the the files in the directory it's in, like UNIX UID, UNIX GID, UNIX permissions, etc.; everything that MSDOSFS is too stupid to save for you. Even long filenames, if you didn't mount it as a VFAT/VFAT32 mount because it was a DOS 2.11 or Windows 3.11 drive. ;-). With minor modifications, this FS would allow FreeBSD to boot using a subdirectory of an MSDOSFS as its root filesystem (so that people could "try it out" without needing to repartition their DOS drives). ATALKFS This layer implements resource forks for Macintosh client machines. It works using namespace escape technique #5. The directories it creates are named ".AppleDesktop" and ".AppleDouble". It uses this technique because it makes the code "plug compatible" with netatalk. 8-). If FreeBSD's namei is patched to correctly inherit flags down, and to pass them as part of an opaque cn_pnbuf (needs the "nameifree" fixes to make it opaque), then you can use "the POSIX namespace escape" to access the forks from UNIX. Example: Open the data fork for the file bob in the current directory: bob Open the data fork for the file bob in the current directory: //ATALKFS/data/bob Open the resource fork for the file "bob" in the current directory: //ATALKFS/rsrc/bob Open the resource fork for the file "tom" in the "/tmp" directory: //ATALKFS/rsrc//tmp/bob CRYPTFS This layer implements cryptography for the underlying FS. It uses namespace escape technique #3 to maintain state, and because the FS is useless without the cryptographic layer. If the encrypted and decrypted data are not the same size, it uses namespace escape technique #4. VOP_READ/VOP_WRITE are trapped by this layer. So are file creates, deletions, and so on (events for which the cryptographic state needs to be synchronized). A good implementation will log transactions like this before performing them, in case it crashes halfway through an operation. COMPFS This layer implements file level compression for the underlying FS. It uses namespace escape technique #4 to maintain any uncompressed copies of file for file currently in use. When the COMPFS "fsck" is run, it removes non-compressed files ("forks"). This is done after a crash. A cleaner process follows closes. If the file isn't reopened after a short period of time, the uncompressed image is removed. EAFS This layer implements OS/2 extended attributesA (these are like Mac resource forks, only you can have more than one of them). It is like ATALKFS, but uses namespace escape technique #4 so that it can store multiple streams. Like ATALKFS, it would benefit from POSIX "//" based namespace selection. ACLFS This layer implements Access Control Lists (ACL's). It uses namespace escape technique #4 so it can store as many file attributes as it wants. This layer extends the VOP's with a "VOP_ACL". UNRMFS This layer implements "unrm". It uses namespace escape technique #4 so it can store as many file forks as it wants. This lets you delete the same file twice, and get back either copy because both are saved. It has a companion kernel process that can be told to go around the FS looking for deleted file older older than a set age (ie: over one month old), and "purge" (that is, *really* delete) them. This layer depends on the POSIX namespace selection to allow (1) the deleted files to be listed by a VOP_READDIR (this requires that the FS namage it's own vnodes so it can "know" if a given directory was opened via the POSIX namespace selection or not, since VOP_READDIR doesn't know the directory path), (2) to allow a user "purge" command to be built, so purges can happen under user control, and (3) to allow a user "unrm" command to be built (which simply renames from the deleted to the default namespace). FLSFS This layer implements File Level Security. It is like ATALKFS, but uses namespace escape technique 4 so that it can store multiple streams. This layer requires a session manager process. When a user attempts to access a file for which file level security is active, a message is sent to the user's session manager requesting credential information from the user for the file. The session manager can be a "pre-authentication" mechanism, where credentials are entered in using a command line tool, after login. Or it can be a "password cache" mechanism, like Windows 95 uses (this kind of defeats the purpose, but is useful for other uses of session management credentials, like an SMBFS or NCPFS). Or the session manager can be "active". An "active" session manager is the most interesting. Using it's knowledge of the console, or being built into the "screen" program, or being built into the xdm, the session manager can actually interact with the user on behalf of the FLSFS (or SMBFS, or NCPFS, etc.) to interactively ask the user for credentials. This would let you have password protection per file, even going so far as to have different passwords for different user for a file (an entire passwd file could be supported, including password aging, etc.). NSEFS This layer implements a shared namespace escape for other layers to share between them. At this point you might be wondering about a stack consisting of multiple FS's that use techniques #3, #4, or #5. You might be worried that these would tend to add up rather quickly. 8-). The answer is to implement a stacking layer that *only* does namespace escaping, and implements a new VOP called VOP_NSE. FS's which need a namespace escape can use this VOP (one of the arguments is "technique". Alternately, you can leave it up to the NSEFS stacking layer to decide by looking at the FS, and specify "I need one file" or "I need a file per directory" or "I need a file per file" or "I need multiple files per file". The possibilities are practically endless. 8-). Regards, 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 Tue Mar 10 01:06:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15376 for freebsd-current-outgoing; Tue, 10 Mar 1998 01:06:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15322; Tue, 10 Mar 1998 01:06:09 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id CAA09772; Tue, 10 Mar 1998 02:06:09 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd009702; Tue Mar 10 02:05:58 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id CAA13348; Tue, 10 Mar 1998 02:05:54 -0700 (MST) From: Terry Lambert Message-Id: <199803100905.CAA13348@usr09.primenet.com> Subject: Re: netscape 4.0 fails after make world To: jdp@polstra.com (John Polstra) Date: Tue, 10 Mar 1998 09:05:54 +0000 (GMT) Cc: root@mantar.slip.netcom.com, peter@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199803091623.IAA07384@austin.polstra.com> from "John Polstra" at Mar 9, 98 08:23:00 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 > Peter, this looks like it's probably related to the recent multi-gcc > changes: > > kerouac$ nm /usr/lib/libstdc++.so.2.0 | grep stdiobuf > 00000c50 T __._8stdiobuf > 00000c08 T ___8stdiobufP7__sFILE > 00001124 T ___8stdiobufRC8stdiobuf > 000010f4 T ___as__8stdiobufRC8stdiobuf > 0002f7a0 D __vt.8stdiobuf > ^ > | > > GCC must change its name mangling between ELF and a.out after all. :-( Implementation namespace. This has to do with the "_" prefix. The semantics dictated by ELF are different than those dictated by a.out. 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 Tue Mar 10 01:25:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18917 for freebsd-current-outgoing; Tue, 10 Mar 1998 01:25:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18905; Tue, 10 Mar 1998 01:25:29 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id CAA12518; Tue, 10 Mar 1998 02:25:29 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd012506; Tue Mar 10 02:25:26 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id CAA13727; Tue, 10 Mar 1998 02:25:21 -0700 (MST) From: Terry Lambert Message-Id: <199803100925.CAA13727@usr09.primenet.com> Subject: Re: Oh, how I hate it when I find leaks in mbuf clusters :-) To: jas@flyingfox.com (Jim Shankland) Date: Tue, 10 Mar 1998 09:25:21 +0000 (GMT) Cc: current@FreeBSD.ORG, karl@mcs.net, hackers@FreeBSD.ORG In-Reply-To: <199803092327.PAA02345@biggusdiskus.flyingfox.com> from "Jim Shankland" at Mar 9, 98 03:27:48 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm. Notice that even with this horrendous mbuf leak, there is less > than 8 MB of memory allocated to the network. > > Given that memory keeps getting cheaper and cheaper, and that finding > and eliminating memory leaks is time-consuming and error-prone, > perhaps we should forget about freeing memory at all, and simply > buy more. At today's prices, for example, it's probably not > unreasonable for a server machine like Karl's to be equipped with > 128 MB of memory dedicated to network buffers. By the time that > runs out, it's likely to be even cheaper to add another 256 MB. Sun had a memory leak on the platforms for the "a day on the Internet" or something similarly named, last year. Between all of the machines and all of the streaming video from all over the world, they were leaking 20,000 Commodore 64's an hour. 8^). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 01:32:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA20762 for freebsd-current-outgoing; Tue, 10 Mar 1998 01:32:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20711 for ; Tue, 10 Mar 1998 01:32:29 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id RAA03913; Tue, 10 Mar 1998 17:30:35 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199803100930.RAA03913@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: jdp@polstra.com (John Polstra), root@mantar.slip.netcom.com, current@FreeBSD.ORG Subject: Re: netscape 4.0 fails after make world In-reply-to: Your message of "Tue, 10 Mar 1998 09:05:54 GMT." <199803100905.CAA13348@usr09.primenet.com> Date: Tue, 10 Mar 1998 17:30:34 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > Peter, this looks like it's probably related to the recent multi-gcc > > changes: > > > > kerouac$ nm /usr/lib/libstdc++.so.2.0 | grep stdiobuf > > 00000c50 T __._8stdiobuf > > 00000c08 T ___8stdiobufP7__sFILE > > 00001124 T ___8stdiobufRC8stdiobuf > > 000010f4 T ___as__8stdiobufRC8stdiobuf > > 0002f7a0 D __vt.8stdiobuf > > ^ > > | > > > > GCC must change its name mangling between ELF and a.out after all. :-( > > Implementation namespace. > > This has to do with the "_" prefix. The semantics dictated by ELF > are different than those dictated by a.out. Actually, no, it's because gcc was accidently compiled with NO_DOLLAR_IN_LABEL, which came in via svr4.h. So, __vt$8stdiobuf got remapped to __vt.8stdiobuf - the gas that we use doesn't need this hand-holding (unlike the svr4 assembler), so it was fixed 2(?) days ago. Just recompile cc*, and libstdc++ and libg++ and this will be the way it was. Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 01:33:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21120 for freebsd-current-outgoing; Tue, 10 Mar 1998 01:33:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21096 for ; Tue, 10 Mar 1998 01:33:46 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id CAA11932; Tue, 10 Mar 1998 02:17:49 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd011920; Tue Mar 10 02:17:42 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id CAA13575; Tue, 10 Mar 1998 02:17:40 -0700 (MST) From: Terry Lambert Message-Id: <199803100917.CAA13575@usr09.primenet.com> Subject: Re: vnode_pager: *** WARNING *** stale FS code in system To: mellon@pobox.com (Anatoly Vorobey) Date: Tue, 10 Mar 1998 09:17:40 +0000 (GMT) Cc: nate@mt.sri.com, current@FreeBSD.ORG In-Reply-To: <19980309194602.38788@techunix.technion.ac.il> from "Anatoly Vorobey" at Mar 9, 98 07:46:02 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 > So, does the stacking layer support multiple inheritance? :) Yes. > P.S. In fact, the VFS framework (more precisely, one of its > predecessors, Sun's vnode system) is mentioned in at least one > book on Java as an example to what pains these poor C programmers > must go in order to create OOP-like FS interface, and how easily > you would do that in Java ;) The Sun VFS framework is a bit more primitive than the BSD 4.4 implementation, even with all its current faults. That said, I saw an OO based OS demonstration by some people from the University of Kentucky on the "Choices" OS. I was impressed when they implemented ACL's in about ten minutes, using inheritance. Of course, they had done it before (Any sufficiently advanced technology is indistiguishable from a rigged demo ;-)). 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 Tue Mar 10 01:45:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22866 for freebsd-current-outgoing; Tue, 10 Mar 1998 01:45:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk ([195.78.64.243]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22857 for ; Tue, 10 Mar 1998 01:45:05 -0800 (PST) (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 JAA00348; Tue, 10 Mar 1998 09:07:31 +0100 (CET) To: dannyman cc: freebsd-current@FreeBSD.ORG Subject: Re: funny logs messages - calcru/adjkerntz In-reply-to: Your message of "Mon, 09 Mar 1998 14:24:13 CST." <19980309142412.10242@urh.uiuc.edu> Date: Tue, 10 Mar 1998 09:07:31 +0100 Message-ID: <346.889517251@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes and no. I means that the Xtals in your machine are not all good. Try to enable the CLK_USE_*_CALIBRATION options and look carefully over what it tells you in dmesg when you "boot -v" Consider running xntpd. Otherwise it is mostly harmless. Poul-Henning In message <19980309142412.10242@urh.uiuc.edu>, dannyman writes: >Hey folks, is there anything "bad" indicated by this rather strnge message? : >) > >thanks! > >danny > >----- Forwarded message from Charlie Root ----- > >arh0300 kernel log messages: >> calcru: negative time of -3384 usec for pid 26 (adjkerntz) >> calcru: negative time of -3384 usec for pid 26 (adjkerntz) >> calcru: negative time of -3384 usec for pid 26 (adjkerntz) >> calcru: negative time of -3384 usec for pid 26 (adjkerntz) >> pid 28527 (conftest), uid 0: exited on signal 6 (core dumped) >> stray irq 7 >> too many stray irq 7's; not logging any more >----- End forwarded message ----- > >-- > //Dan -=- This message brought to you by djhoward@uiuc.edu -=- >\\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- >aiokomete -=- Our Honored Symbol deserves an Honorable Retirement > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "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 Mar 10 01:45:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22924 for freebsd-current-outgoing; Tue, 10 Mar 1998 01:45:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk ([195.78.64.243]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22881 for ; Tue, 10 Mar 1998 01:45:11 -0800 (PST) (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 JAA00434; Tue, 10 Mar 1998 09:12:32 +0100 (CET) To: Michael Hancock cc: Dmitrij Tejblum , Terry Lambert , current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-reply-to: Your message of "Tue, 10 Mar 1998 11:35:19 +0900." Date: Tue, 10 Mar 1998 09:12:32 +0100 Message-ID: <432.889517552@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Mich ael Hancock writes: >I think vnode_pager_generic_(put|get)pages should be moved to >vfs_default.c and renamed vop_std(put|get)pages. It would need to be >modified to accept ap instead of 4 components of ap. I agree. >Terry is trying to make it more visible to fs implementors so that they >take the time to understand how to make VM friendly implementations. The >"XXX - wimp out ..." comment is also added for extra emphasis. This >comment should be taken out and replaced by a comment explaining what a VM >friendly (get|put)pages should do. I agree. >I think vfs_default.c is visible enough. If you don't know it is there, you will never get though any kind of VFS work anyway. >This is a form discussion, the substance is the same. My personal opinion >is that it doesn't belong vnode_pager.c because it will tend to be ignored >by fs implementors. It most certainly doesn't belong there. -- 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 Mar 10 01:45:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23038 for freebsd-current-outgoing; Tue, 10 Mar 1998 01:45:24 -0800 (PST) (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 BAA23015 for ; Tue, 10 Mar 1998 01:45:20 -0800 (PST) (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 JAA20627; Tue, 10 Mar 1998 09:22:11 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id KAA08354; Tue, 10 Mar 1998 10:22:11 +0100 (MET) Message-ID: <19980310102210.18093@follo.net> Date: Tue, 10 Mar 1998 10:22:10 +0100 From: Eivind Eklund To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: *HEADS UP* Correction to previous postings. References: <9803100827.AA26647@watermarkgroup.com> <199803100849.AAA18205@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803100849.AAA18205@dingo.cdrom.com>; from Mike Smith on Tue, Mar 10, 1998 at 12:49:02AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 10, 1998 at 12:49:02AM -0800, Mike Smith wrote: > > I managed to modify boot2 so I was able to boot with -r1.87 autoconf.c > > from my dedicated disk (historical invalid). My solution was to leave slice > > to be WHOLE_DISK_SLICE for a BSD partition starts at sector 0 (this would > > bloat boot2 by two bytes: a je rel8). > > I'd love to do this, but it means a mandatory bootblock upgrade. Would the new bootblocks work with the previous kernels? (Otherwise, it sounds really terrifying.) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 01:48:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24243 for freebsd-current-outgoing; Tue, 10 Mar 1998 01:48:49 -0800 (PST) (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 BAA24196 for ; Tue, 10 Mar 1998 01:48:38 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id CAA21778; Tue, 10 Mar 1998 02:48:37 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpd021768; Tue Mar 10 02:48:34 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id CAA14218; Tue, 10 Mar 1998 02:48:30 -0700 (MST) From: Terry Lambert Message-Id: <199803100948.CAA14218@usr09.primenet.com> Subject: Re: vnode_pager: *** WARNING *** stale FS code in system To: dima@tejblum.dnttm.rssi.ru (Dmitrij Tejblum) Date: Tue, 10 Mar 1998 09:48:29 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199803092359.CAA03508@tejblum.dnttm.rssi.ru> from "Dmitrij Tejblum" at Mar 10, 98 02:59:01 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 > > Most assuredly, at some time *after* a skeleton versions of FS specific > > getpages/putpages have been written. Organizationally, the patches I > > gave *do* move toward that goal. > > Before these changes, simple grep for getpages_desc gave the list of > real getpages implementations. The tool in src/tools/tools/vop_table > also could be used to find such list. Now you succefully created > illusion that all filesystems already have own specific getpages > implementation. The "organizational" side of these changes, as I > already stated, is trivial. If it's trivial, why wasn't it already done? You have to start somewhere. You touch the world in a tiny way, and then you touch each of the FS's individually, and then you remove the bogus code that is no longer depended upon. Hopefully, some people will pitch in on doing the per FS code. I could do the NFS and FFS code pretty trivially. I've held off so far, both because John has been (thankfully!) touching NFS code, and because I don't want to compound a possible political problem by adding more wood to the fire. I've spent more time defending the incremental implementation than it would take to do something about it (I could do a hell of a lot all at once if a megacommit was feasible, which it isn't because of the complexity of the code review that would be needed; I'd have to pay Kirk or someone else that was trusted by core, and sufficiently knowledgable about everything that got touched, to vet the code for me). > > If you insist, I can duplicate the generic code into the FS's themselves > > immediately, and remove it from the generic location. I don't see this > > action as being useful. > > Me too. Please don't duplicate it. The NFS/non-NFS split is pretty easy. The other splits, less so. > Desired organization was obvious. You made the organization more > complex without a real advantage. Without immediate advantage. The difference from previous treks down this same track is that at least the light at the end of the tunnel can be seen without binoculars. I fully intend to get to the end of the tunnel if I can avoid being sidetracked into dicussing whether the correct way to build a railroad is to manufacture the ties, the locamotive, or the rails first, before anything gets shipped to where it's going to be used. > > I would cetrainly welcome your assitance in unstubbing the local media > > getpages/putpages, if you were willing to give it. This would resolve > > your implementation issues, without stepping on my organizational issues. > > Thanks. It is hardly possible since I know almost nothing about VM. Well, then *anybody's* assistance. Like I said, I can do it myself if I can free up some cycles from places like this thread. > I don't see what force stacking layers to access bypass explicitly. > Look: > > int > vop_defaultop(struct vop_generic_args *ap) > { > return (VOCALL(default_vnodeop_p, ap->a_desc->vdesc_offset, ap)); > } > > Does your stacking layer modify ap->a_desc->vdesc_offset? Maybe. It depends on what it does. > If yes, how and why? It may add a new VOP. Initially, adding VOP's can be made more dynamic by turning vfs_op_descs into a linker set. This will at least handle the "new FS, new VOP" case. Then you would want to sort it, and eliminate duplicates. > > > > Here's my preferred soloution, since it will pacify you as well: make > > the warning non-fatal *for now*; ie: > > [...] > > This looks even worse. And no, it will not pacify me :) To pacify me, > either remove msdosfs_getpages and msdosfs_putpages, or make them real > msdosfs-specific implementation. These two dumb functions without any > purpose irritates me. Actually, all functions without a purpose irritates > me. (Well, actually I am already almost pacified :) I'll see what I can do about them. 8-). > > I don't know how many times I should have to repeat this, but the code > > *should not be in vnode_pager.c* and was, in fact *designed to not be > > in vnode_pager.c*. > > And here is my usual answer: you did *nothing* to remove the code. My usual answer: "yet". 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 Tue Mar 10 01:50:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24773 for freebsd-current-outgoing; Tue, 10 Mar 1998 01:50:22 -0800 (PST) (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 BAA24766 for ; Tue, 10 Mar 1998 01:50:17 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id BAA06902; Tue, 10 Mar 1998 01:46:51 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd006900; Tue Mar 10 01:46:41 1998 Date: Tue, 10 Mar 1998 01:42:22 -0800 (PST) From: Julian Elischer To: Source Code cc: current@FreeBSD.ORG Subject: Re: Enabling softupdates for root filesystem In-Reply-To: <199803100654.BAA00289@luoqi.watermarkgroup.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG thanks I noticed this myself, and so did phk, who sent me a similar patch. I haven't done it for time reasons.. I'll check his and yours and see which is nicer, and apply it. maybe tomorrow night. julian On Tue, 10 Mar 1998, Source Code wrote: > With the lastest softupdates code cvsupped, there's no way to enable > softupdates for the root partition, no matter what I tried (single user, > fixit floppy, boot off another disk). It turned out that when upgrading > the root mount from r/o to r/w, no attempt was made to enable the > softupdate code. The following patch would do the trick, > > Index: ffs_vfsops.c > =================================================================== > RCS file: /fun/cvs/src/sys/ufs/ffs/ffs_vfsops.c,v > retrieving revision 1.76 > diff -u -r1.76 ffs_vfsops.c > --- ffs_vfsops.c 1998/03/08 09:59:06 1.76 > +++ ffs_vfsops.c 1998/03/10 06:38:39 > @@ -241,6 +241,12 @@ > VOP_UNLOCK(devvp, 0, p); > } > > + if ((fs->fs_flags & FS_DOSOFTDEP) && > + (error = softdep_mount(ump->um_devvp, mp, > + fs, p->p_ucred)) != 0) { > + return (error); > + } > + > fs->fs_ronly = 0; > } > if (fs->fs_ronly == 0) { > ----------- > -lq > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 02:11:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA28718 for freebsd-current-outgoing; Tue, 10 Mar 1998 02:11:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA28698; Tue, 10 Mar 1998 02:10:51 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA13596; Tue, 10 Mar 1998 21:00:28 +1100 Date: Tue, 10 Mar 1998 21:00:28 +1100 From: Bruce Evans Message-Id: <199803101000.VAA13596@godzilla.zeta.org.au> To: bde@zeta.org.au, luoqi@watermarkgroup.com, mike@smith.net.au Subject: Re: *HEADS UP* Correction to previous postings. Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > Summary of the 3 cases where the whole disk is used for FreeBSD: >> > >> > Partition table config Slice# passed by bootblocks Slice# to use for "/" >> > ---------------------- --------------------------- ------------------------- >> > Signature != 0xAA55 WHOLE_DISK_SLICE (= 1) COMPATIBILITY_SLICE (= 0) >> > Historical invalid BASE_SLICE + 3 (= 5) COMPATIBILITY_SLICE (= 0) >> > "Valid" (1 big part.) BASE_SLICE + N (0 <= N < 4) BASE_SLICE + N >> ... >I managed to modify boot2 so I was able to boot with -r1.87 autoconf.c >from my dedicated disk (historical invalid). My solution was to leave slice >to be WHOLE_DISK_SLICE for a BSD partition starts at sector 0 (this would >bloat boot2 by two bytes: a je rel8). This test would misdetect case 3 as dedicated (which may be best :-) and would also misdetect cases where there are multiple nonempty partitions with the first BSD one starting at sector 0. For complete compatility with the kernel, the boot blocks would have to do a bcmp() of the historical table with the actual table. This takes 0x40 bytes for the table and about 0x20 bytes for the test. I don't think this can be compressed much. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 02:12:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29146 for freebsd-current-outgoing; Tue, 10 Mar 1998 02:12:32 -0800 (PST) (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 CAA29126 for ; Tue, 10 Mar 1998 02:12:28 -0800 (PST) (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 CAA18541; Tue, 10 Mar 1998 02:09:49 -0800 (PST) Message-Id: <199803101009.CAA18541@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Eivind Eklund cc: Mike Smith , current@FreeBSD.ORG Subject: Re: *HEADS UP* Correction to previous postings. In-reply-to: Your message of "Tue, 10 Mar 1998 10:22:10 +0100." <19980310102210.18093@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Mar 1998 02:09:48 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, Mar 10, 1998 at 12:49:02AM -0800, Mike Smith wrote: > > > I managed to modify boot2 so I was able to boot with -r1.87 autoconf.c > > > from my dedicated disk (historical invalid). My solution was to leave slice > > > to be WHOLE_DISK_SLICE for a BSD partition starts at sector 0 (this would > > > bloat boot2 by two bytes: a je rel8). > > > > I'd love to do this, but it means a mandatory bootblock upgrade. > > Would the new bootblocks work with the previous kernels? (Otherwise, > it sounds really terrifying.) Yeah, old kernels ignore the slice number completely. But what we need is something that works universally, without requiring a bootblock upgrade. Yes, upgrading the bootblock is the "right" thing to do, but it would make for a really scary change, sort of like I was trying hard to avoid. We're going to be looking at a bootblock upgrade for 3.0 anyway. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 03:06:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA06381 for freebsd-current-outgoing; Tue, 10 Mar 1998 03:06:02 -0800 (PST) (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 DAA06310 for ; Tue, 10 Mar 1998 03:05:59 -0800 (PST) (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 LAA22174; Tue, 10 Mar 1998 11:05:57 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id MAA08749; Tue, 10 Mar 1998 12:05:57 +0100 (MET) Message-ID: <19980310120557.45721@follo.net> Date: Tue, 10 Mar 1998 12:05:57 +0100 From: Eivind Eklund To: Chris Csanady , ccsanady@iastate.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: (fixed) Was: Filesystem recovery procedures (please help..) References: <199803091748.LAA00499@friley63.res.iastate.edu> <199803100445.WAA06117@friley585.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803100445.WAA06117@friley585.res.iastate.edu>; from Chris Csanady on Mon, Mar 09, 1998 at 10:45:08PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 09, 1998 at 10:45:08PM -0600, Chris Csanady wrote: > > >After recent recently trying to install the cam patches, > >I seemed to have been left with a system that simply > >would not boot. It would get to the place where it mounts > >root, and then ti would hang. I have tried new kernels, > >cam kernels, recent kernels, old generic kernels, all without > >luck. Anyways, I finally just went to reinstall(upgrade) to > >fix the problems. > > I must have screwed up the device nodes here, I'm not really > sure what happened though. :\ Seems to work now after removing > them all and recreating them. This is annoying to do from a > fixit floppy, because too many paths are hardcoded into > MAKEDEV. :( Anyways I can now boot as well.. I usually chroot from the fixit floppy to my normal setup as soon as it is 'up enough' to make that possible. It solves a host of problems. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 03:46:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA10228 for freebsd-current-outgoing; Tue, 10 Mar 1998 03:46:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA10217 for ; Tue, 10 Mar 1998 03:46:23 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-12-03.camtech.net.au [203.55.242.3]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id WAA19756; Tue, 10 Mar 1998 22:13:31 +1030 (CST) Message-ID: <350527AA.3139AD63@camtech.net.au> Date: Tue, 10 Mar 1998 22:14:42 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: shimon@simon-shapiro.org CC: Nate Williams , current@FreeBSD.ORG, Mike Smith Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My silo overflows seem to have disappeared. Unfortunately I've just changed 4 things at once! - I recompiled XFree86 3.3.1 (NOT 3.3.2) recently (whilst running a system built from CTM src-cur.3261 [Feb 23] sources) - I've just made the world at CTM src-cur.3281 [8 Mar 1998 23:07:21 -0800 (PST)] - I've turned on SoftUpdates on all but the root fs. - And I've taken Option "pci_retry" out of my /etc/XF86Config file. ** Did anyone change anything that could stop silo overflows between CTM src-cur.3261 and CTM src-cur.3281 ? ** Personally I think this is the key but have not the time to try it now (ie I am downloading XF86 3.3.2 in an xterm and thus cant restart X for a while). Simon Shapiro wrote: > > On 05-Mar-98 Nate Williams wrote: > >> > However the driver has no say in the matter when _someone_else_ > >> > disables interrupts for a long period of time, or when the hardware > >> > fails to deliver them in the first place. > >> > >> Unless I misunderstand something, the driver should get interrupts > >> delivered, unless another part of the kernel is in spltty(), or another > >> spl > >> which masks spltty. There should not be all that many of those, and > >> they > >> should be considered carefully. > > > > I can tell you that uniquivocally XFree86 causes this to happen. Why, I > > don't know, but it's definitely X related. If I don't use X and the > > machine gets the same traffic, I get the messages. If I switch from > > XFree8 to XIG, the messages go away. > > > > What is causing the interrupts to go away, I don't know, but it might be > > syscons or something. I'm not switching vty's, and neither am I hitting > > the caps-lock or causing the LED's to switch. > > > > But, it occurs none-the-less. > > I am guessing it is something to do with the S3 chip. The Mach64 I finally > pulled out was much worse. It would die/kill serial ports. I think the > problem is there and in the FAST_INTR stuff. Now I am going to get myself > in trouble all over again :-) > > Simon > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 05:43:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22796 for freebsd-current-outgoing; Tue, 10 Mar 1998 05:43:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mhub3.tc.umn.edu (0@mhub3.tc.umn.edu [128.101.131.53]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA22782 for ; Tue, 10 Mar 1998 05:42:56 -0800 (PST) (envelope-from adkin003@tc.umn.edu) Received: from pub-22-b-149.dialup.umn.edu by mhub3.tc.umn.edu; Tue, 10 Mar 98 07:42:50 -0600 Date: Tue, 10 Mar 1998 07:39:49 -0600 (CST) From: dave adkins X-Sender: adkin003@samthedog To: current@FreeBSD.ORG Subject: ext2_sync and NULL inode and VNON v_type 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 In current as of 980310, a r/w mounted ext2 filesystem panics on the first sync. This happens when a vnode of type VNON with ip == NULL is processed. I have added a test for a v_type of VNON in ext2_sync(). if (VOP_ISLOCKED(vp)) continue; + if ( vp->v_type == VNON ) + continue; ip = VTOI(vp); if (ip == NULL) { I haven't yet tried writing to the mounted file system with this patch. dave adkins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 07:00:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04769 for freebsd-current-outgoing; Tue, 10 Mar 1998 07:00:35 -0800 (PST) (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 HAA04754 for ; Tue, 10 Mar 1998 07:00:32 -0800 (PST) (envelope-from root@shadow.worldbank.org) Received: from localhost (root@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id KAA00264 for ; Tue, 10 Mar 1998 10:00:01 -0500 (EST) (envelope-from root@shadow.worldbank.org) Date: Tue, 10 Mar 1998 10:00:01 -0500 (EST) From: Charlie ROOT To: current@FreeBSD.ORG Subject: old msdosfs? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What does this message mean: Old mount_msdosfs, flags=0 ? This happens when my -current system mounts my VFAT Windows 95 partition on sd0s1. Thanks... Al To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 09:23:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01472 for freebsd-current-outgoing; Tue, 10 Mar 1998 09:23:29 -0800 (PST) (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 JAA01435 for ; Tue, 10 Mar 1998 09:23:19 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 14382 invoked by uid 1000); 10 Mar 1998 17:30:45 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [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: <350527AA.3139AD63@camtech.net.au> Date: Tue, 10 Mar 1998 09:30:45 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Matthew Thyer Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) Cc: Mike Smith , current@FreeBSD.ORG, Nate Williams Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Mar-98 Matthew Thyer wrote: > My silo overflows seem to have disappeared. > > Unfortunately I've just changed 4 things at once! > > - I recompiled XFree86 3.3.1 (NOT 3.3.2) recently (whilst running a > system built from CTM src-cur.3261 [Feb 23] sources) That's not it here, No X at all and still silo overflows... > - I've just made the world at CTM src-cur.3281 [8 Mar 1998 23:07:21 -0800 > (PST)] That could be it > - I've turned on SoftUpdates on all but the root fs. ?? > - And I've taken Option "pci_retry" out of my /etc/XF86Config file. ** Again, sounds like X11 related. The problem may be agravated, or even manifested, by X11, but I have it regardless of X11. > > Did anyone change anything that could stop silo overflows between > CTM src-cur.3261 and CTM src-cur.3281 ? > > ** Personally I think this is the key but have not the time to try > it now (ie I am downloading XF86 3.3.2 in an xterm and thus cant > restart X for a while). I built XF86--3.3.2, XFSetup does not link, has lots of tk/tcl undefined stuff. When it is installed, it does funny things with interrupts; mouse events seem to be generated out of thin air. Because I get the silo overflows consistently, without any X11 on the machine, I doubt X11 is key to this. From Mike's excellent overview of interrupts, it is pretty clear that an interrupt is leaking someplace. I ALWAYS see this silo overflow associated wit ha DPT lost interrupt; Some time ago (several months) I noticed that the DPT driver is not getting certain interrupts. I simply did not get them. It was not a case where I receive them and not proces them. At first I suspected the hardware. It happens, under SMP, on two drastically different motherboards. I added a simple timer to the DPT driver that occasionally wakes up and checks the hardware for posted interrupt. If I find one, I process it and complain. I always get a silo overflow when using PPP. It always happens with a DPT lost interrupt recovery. Not every DPT lost interrupt recovery has an sio.c silo overflow, but every silo overflow has a DPT lost interrupt associated with it. Probably a race condition in interrupt handling. If X11 causes the video card to generate interrupts, this is our clue; A video card can generate interrupts very quickly. So can a DPT; Less than 2us between interrupts is not unusual. For all it's worth; Fast Interrupts remind me of Linux interrupts; You shutdown all interrupts, etc. Linux chronically loses interrupts. If you block all interrupts, there simply is no way to guarantee you will not lose one. This is how I understand it. I am probably wrong. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 10:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10388 for freebsd-current-outgoing; Tue, 10 Mar 1998 10:01:42 -0800 (PST) (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 KAA10378 for ; Tue, 10 Mar 1998 10:01:39 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id MAA15626 for ; Tue, 10 Mar 1998 12:01:38 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id MAA03499; Tue, 10 Mar 1998 12:01:38 -0600 (CST) Message-ID: <19980310120138.02423@mcs.net> Date: Tue, 10 Mar 1998 12:01:38 -0600 From: Karl Denninger To: current@FreeBSD.ORG Subject: Hmmmm.. odd stuff from the "de" driver Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just loaded a kernel built last night on a system which gets fairly heavy use, and am seeing some odd things on the "de" driver... (this is just after a reboot) $ netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll de0 1500 00.00.c0.0a.a9.c8 6258 0 10183 0 1634 de0 1500 192.160.127 Nntp1 6258 0 10183 0 1634 de1 1500 00.00.c0.b4.49.cf 36083 229 17782 5 0 de1 1500 199.3.39 News-nfs 36083 229 17782 5 0 lp0* 1500 0 0 0 0 0 lo0 16384 0 0 0 0 0 lo0 16384 127 localhost 0 0 0 0 0 de0: rev 0x11 int a irq 12 on pci0.12.0 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:0a:a9:c8 de1: rev 0x12 int a irq 9 on pci0.13.0 de1: SMC 9332DST 21140 [10-100Mb/s] pass 1.2 de1: address 00:00:c0:b4:49:cf de1: enabling 100baseTX port What's odd about this is the "Ierrs" field. The Oerrs field is from me pulling the cord to switch it to another port on our 100BaseTX switch (thinking that perhaps the port was defective). The *switch* (an Intel 510T) to which it is connected reports no errors. The cable has been swapped twice, and they're all pre-builts. Before the upgrade, I wasn't seeing these Ierrs. Is the driver misreporting, is the driver possibly broken, or does anyone have any ideas as to what is going on here? I'm hesitant to update any of our other machines with the new kernel until I understand this, because of the obvious risk if we do so and there's a serious bug in the driver for the "de" cards (which we have a *lot* of). I'm going to swap the board next, on the off chance that perhaps that the card got strange at this particular moment, but I have trouble believing that to be the case. Thanks in advance. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 10:01:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10445 for freebsd-current-outgoing; Tue, 10 Mar 1998 10:01:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10370; Tue, 10 Mar 1998 10:01:36 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id LAA24133; Tue, 10 Mar 1998 11:01:28 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id LAA15498; Tue, 10 Mar 1998 11:01:23 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199803101801.LAA15498@panzer.plutotech.com> Subject: problems stripping kernels To: current@FreeBSD.ORG Date: Tue, 10 Mar 1998 11:01:23 -0700 (MST) Cc: dyson@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 Howdy, I've noticed a problem stripping kernels since John's changes on Saturday went in. (and it wasn't fixed by version 1.46 of ufs_readwrite.c yesterday) Basically, I config my kernels with -g, and then use strip -d to strip off the debugging symbols (after saving a copy of the kernel with debugging symbols, of course). The problem is that kernels I strip on a machine using a kernel built after Saturday's changes don't boot. They just hang forever with the little spinning cursor. Kernels stripped on the same machine running a kernel from before Saturday's changes work just fine. From what I can tell, there are three bytes different between the two kernels: $ ls -la kernel* -rwxr-xr-x 1 ken wheel 1409956 Mar 10 09:50 kernel* -rwx------ 1 ken wheel 1409956 Mar 10 09:53 kernel.debug* $ cmp -l kernel kernel.debug 17 140 20 18 266 133 19 67 1 I have reproduced this behavior on another machine, so it isn't a hardware glitch. I am running CAM, but neither Justin nor I think this could be an Adaptec/CAM bug. If it were, it would manifest itself in other ways besides this. Has anyone else seen this? It could be that for other folks, the corruption happens in a less critical place in the kernel binary. So, here's how to reproduce: - running a kernel from after John's changes on Saturday, build a kernel on your machine with debugging symbols (config -g) - copy the debugging kernel to another file - strip one of the copies of the kernel - boot another kernel from before John's changes on Saturday, and strip the other copy of the kernel - cmp -l kernel1 kernel2 For me, the difference occurs in a place that makes it impossible for the kernel to boot. If anyone wants the config file, more details, etc., just let me know. I'm not absolutely positive that John's changes on Saturday caused this, but it does seem like that may be the case. (And lest anyone think I'm not grateful for the progress, see my NFS success story from yesterday...:) Thanks, 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 Tue Mar 10 10:36:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19944 for freebsd-current-outgoing; Tue, 10 Mar 1998 10:36:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhost (user-38lcb0v.dialup.mindspring.com [209.86.44.31]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA19883 for ; Tue, 10 Mar 1998 10:36:10 -0800 (PST) (envelope-from rlb@mindspring.com) Received: from mindspring.com by mailhost with smtp (Smail3.1.29.1 #1) id m0yCTsh-000FzdC; Tue, 10 Mar 98 13:36 EST Message-ID: <35058823.EE12CABD@mindspring.com> Date: Tue, 10 Mar 1998 13:36:19 -0500 From: Ron Bolin X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.6 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current -- ------------------------------------------------------------------------------- Ron Bolin, Sr. Software Eng, NetChannel Web: http://www.netchannel.net E-mail: rbolin@netchannel.net Web: http://www.gsu.edu/~gs01rlb Ph: 770-729-2929 Ext 249 Hm: 770-992-8877 Web: http://www.mindspring.com/~rlb ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 11:00:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26318 for freebsd-current-outgoing; Tue, 10 Mar 1998 11:00:31 -0800 (PST) (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 LAA26286 for ; Tue, 10 Mar 1998 11:00:21 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 24644 invoked by uid 1000); 10 Mar 1998 19:07:47 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 10 Mar 1998 11:07:47 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: freebsd-current@FreeBSD.ORG Subject: DPT in GENERIC Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any objection for the DPT driver being added to the GENERIC kernel configuration and thus being available on the standard boot floppy? ``I do not know what/do not have a DPT controller'' is not a valid objection. The DPT driver allows FreeBSD users the use of a family of SCSI RAID controllers which are typically used in high end servers. For details on the DPT hardware, see http://www.dpt.com. For information about the driver, see http://simon-shapiro.org. If no one voices a valid objection, I am goingto ask for the change to be comitted. The driver itself is in the 2.0-current source tree for over a month now. the 2.2 equivalent is in final testing after vaving been comitted last week. ---------- 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 Mar 10 11:07:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28069 for freebsd-current-outgoing; Tue, 10 Mar 1998 11:07:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28014 for ; Tue, 10 Mar 1998 11:07:08 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA19557; Tue, 10 Mar 1998 12:06:55 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd019489; Tue Mar 10 12:06:48 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id MAA06001; Tue, 10 Mar 1998 12:06:21 -0700 (MST) From: Terry Lambert Message-Id: <199803101906.MAA06001@usr01.primenet.com> Subject: Re: netscape 4.0 fails after make world To: peter@netplex.com.au (Peter Wemm) Date: Tue, 10 Mar 1998 19:06:21 +0000 (GMT) Cc: tlambert@primenet.com, jdp@polstra.com, root@mantar.slip.netcom.com, current@FreeBSD.ORG In-Reply-To: <199803100930.RAA03913@spinner.netplex.com.au> from "Peter Wemm" at Mar 10, 98 05:30:34 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 > > > GCC must change its name mangling between ELF and a.out after all. :-( > > > > Implementation namespace. > > > > This has to do with the "_" prefix. The semantics dictated by ELF > > are different than those dictated by a.out. > > Actually, no, it's because gcc was accidently compiled with > NO_DOLLAR_IN_LABEL, which came in via svr4.h. So, __vt$8stdiobuf got > remapped to __vt.8stdiobuf - the gas that we use doesn't need this > hand-holding (unlike the svr4 assembler), so it was fixed 2(?) days ago. > Just recompile cc*, and libstdc++ and libg++ and this will be the way it > was. Ah. I thought you were trying to Link an a.out binary dynamically against an ELF shared library. My mistake... 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 Tue Mar 10 11:20:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02187 for freebsd-current-outgoing; Tue, 10 Mar 1998 11:20:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from dyson@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02129 for current@freebsd.org; Tue, 10 Mar 1998 11:20:40 -0800 (PST) (envelope-from dyson) From: John Dyson Message-Id: <199803101920.LAA02129@hub.freebsd.org> Subject: Sorry, will be offline for a few days To: current@FreeBSD.ORG Date: Tue, 10 Mar 1998 11:20:35 -0800 (PST) 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 Gang, I have been trying to be more responsive lately. However, my machine is down, and I am out of town. This makes email, etc. much more difficult (e.g. it isn't sorted, volume is very high, etc.) So, until Fri, I won't be able to generally act on bugs (often that I have created) in -current. The only email mechanism that works (and is unpleasant for me to use) is my 'dyson@iquest.net' address. (Not that it is my ISP's fault, but I have a more sophisticated email environment at home that helps me handle the volume.) I'll try to look at my email daily, but might miss important things until the mail gets properly sorted out when I get home. Sorry for any troubles that I might have caused that I cannot deal with right now. All of my backup plans (except one) has failed :-(. I'll probably be able to be back at 100% on Sat. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 11:42:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07324 for freebsd-current-outgoing; Tue, 10 Mar 1998 11:42:30 -0800 (PST) (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 LAA07310 for ; Tue, 10 Mar 1998 11:42:24 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id MAA03349; Tue, 10 Mar 1998 12:42:12 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd003314; Tue Mar 10 12:42:08 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id MAA07682; Tue, 10 Mar 1998 12:42:03 -0700 (MST) From: Terry Lambert Message-Id: <199803101942.MAA07682@usr01.primenet.com> Subject: Re: Someone needs to re-develop "Softupdates" To: tom@uniserve.com (Tom) Date: Tue, 10 Mar 1998 19:42:03 +0000 (GMT) Cc: nate@mt.sri.com, jak@cetlink.net, karl@mcs.net, current@FreeBSD.ORG In-Reply-To: from "Tom" at Mar 8, 98 11:56:40 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > It's amazing how some of the same people who decry commercializing > > > FreeBSD with donor control of funding have no objection to Kirk's > > > commercial hooks. > > > > Sad isn't it.... > > > > > Score 1 for the GPL. [ ... ] > > Basically, this commercial entity is giving some of it's work to > > FreeBSD, and making it 'easier' for Kirk to get money since other > > 'commercial' entities who want to use Kirk's work have everything but > > the legal license. > > More are benefiting that just Kirk (money) and Whistle (not having to > re-integrate changes). Score 1 for the UCBL. I think the ongoing maintenance issues are as big an incentive to donate to free software projects, and keep the code free, as any draconian licensing restrictions about how you can utilize (as opposed to use) the software. Free by choice, in other words. "Those who sacrifice liberty for security, deserve neither" -- Benjamin Franklin > > Sort of a 'big carrot' dangling out in front that they can't legally > > obtain. > > According to my understanding of Kirk's message(s), all commercial > entities have to do is step up and buy a license, and they can use > SoftUpdates too. And don't forget that Jordan's work is funded, as is Mike Smith's, as is John Dyson's, etc.. 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 Tue Mar 10 11:59:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10054 for freebsd-current-outgoing; Tue, 10 Mar 1998 11:59:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10026 for ; Tue, 10 Mar 1998 11:59:27 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id MAA06291; Tue, 10 Mar 1998 12:59:26 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd006260; Tue Mar 10 12:59:23 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id MAA08570; Tue, 10 Mar 1998 12:59:22 -0700 (MST) From: Terry Lambert Message-Id: <199803101959.MAA08570@usr01.primenet.com> Subject: Re: DPT in GENERIC To: shimon@simon-shapiro.org Date: Tue, 10 Mar 1998 19:59:21 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from "Simon Shapiro" at Mar 10, 98 11:07:47 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 > Is there any objection for the DPT driver being added to the GENERIC kernel > configuration and thus being available on the standard boot floppy? > > ``I do not know what/do not have a DPT controller'' is not a valid > objection. Did you build a boot floppy, and verify that it doesn't make the kernel too large to fit or interfere with using the floppy to install a FreeBSD system? 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 Tue Mar 10 12:09:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12946 for freebsd-current-outgoing; Tue, 10 Mar 1998 12:09:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12892 for ; Tue, 10 Mar 1998 12:09:33 -0800 (PST) (envelope-from bartol@salk.edu) Received: from dale.salk.edu (dale [198.202.70.112]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id MAA09324; Tue, 10 Mar 1998 12:09:19 -0800 (PST) Date: Tue, 10 Mar 1998 12:09:17 -0800 (PST) From: Tom Bartol To: Simon Shapiro cc: freebsd-current@FreeBSD.ORG Subject: Re: DPT in GENERIC 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 If a vote would help, I would vote in favor of this as I am getting ready to purchase a large server machine and I plan to use the DPT controller for RAID. It would be nice to be able to have a GENERIC kernel that I can count on reliably booting the machine during installation and in case of emergency. Tom On Tue, 10 Mar 1998, Simon Shapiro wrote: > Is there any objection for the DPT driver being added to the GENERIC kernel > configuration and thus being available on the standard boot floppy? > > ``I do not know what/do not have a DPT controller'' is not a valid > objection. > > The DPT driver allows FreeBSD users the use of a family of SCSI RAID > controllers which are typically used in high end servers. For details > on the DPT hardware, see http://www.dpt.com. For information about the > driver, see http://simon-shapiro.org. > > If no one voices a valid objection, I am goingto ask for the change to be > comitted. The driver itself is in the 2.0-current source tree for over a > month now. the 2.2 equivalent is in final testing after vaving been > comitted last week. > > ---------- > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 12:17:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14896 for freebsd-current-outgoing; Tue, 10 Mar 1998 12:17:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14859 for ; Tue, 10 Mar 1998 12:17:33 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id PAA29165 for ; Tue, 10 Mar 1998 15:17:21 -0500 (EST) Date: Tue, 10 Mar 1998 15:17:21 -0500 (EST) From: Snob Art Genre To: freebsd-current@FreeBSD.ORG Subject: Re: DPT in GENERIC 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 Me too! On Tue, 10 Mar 1998, Tom Bartol wrote: > > If a vote would help, I would vote in favor of this as I am getting ready > to purchase a large server machine and I plan to use the DPT controller > for RAID. It would be nice to be able to have a GENERIC kernel that I can > count on reliably booting the machine during installation and in case of > emergency. > > Tom > Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 12:19:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15322 for freebsd-current-outgoing; Tue, 10 Mar 1998 12:19:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15284 for ; Tue, 10 Mar 1998 12:18:54 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id NAA24278; Tue, 10 Mar 1998 13:18:34 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id NAA16119; Tue, 10 Mar 1998 13:18:32 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199803102018.NAA16119@panzer.plutotech.com> Subject: problems stripping kernels To: freebsd-current@FreeBSD.ORG Date: Tue, 10 Mar 1998 13:18:32 -0700 (MST) Cc: dyson@iquest.net 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 [ I sent this to -current, but it doesn't seem to have gone through. So, I'm resending it. Sorry if this is a duplicate. ] Howdy, I've noticed a problem stripping kernels since John's changes on Saturday went in. (and it wasn't fixed by version 1.46 of ufs_readwrite.c yesterday) Basically, I config my kernels with -g, and then use strip -d to strip off the debugging symbols (after saving a copy of the kernel with debugging symbols, of course). The problem is that kernels I strip on a machine using a kernel built after Saturday's changes don't boot. They just hang forever with the little spinning cursor. Kernels stripped on the same machine running a kernel from before Saturday's changes work just fine. From what I can tell, there are three bytes different between the two kernels: $ ls -la kernel* -rwxr-xr-x 1 ken wheel 1409956 Mar 10 09:50 kernel* -rwx------ 1 ken wheel 1409956 Mar 10 09:53 kernel.debug* $ cmp -l kernel kernel.debug 17 140 20 18 266 133 19 67 1 I have reproduced this behavior on another machine, so it isn't a hardware glitch. I am running CAM, but neither Justin nor I think this could be an Adaptec/CAM bug. If it were, it would manifest itself in other ways besides this. Has anyone else seen this? It could be that for other folks, the corruption happens in a less critical place in the kernel binary. So, here's how to reproduce: - running a kernel from after John's changes on Saturday, build a kernel on your machine with debugging symbols (config -g) - copy the debugging kernel to another file - strip one of the copies of the kernel - boot another kernel from before John's changes on Saturday, and strip the other copy of the kernel - cmp -l kernel1 kernel2 For me, the difference occurs in a place that makes it impossible for the kernel to boot. If anyone wants the config file, more details, etc., just let me know. I'm not absolutely positive that John's changes on Saturday caused this, but it does seem like that may be the case. (And lest anyone think I'm not grateful for the progress, see my NFS success story from yesterday...:) Thanks, 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 Tue Mar 10 12:34:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19237 for freebsd-current-outgoing; Tue, 10 Mar 1998 12:34:30 -0800 (PST) (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 MAA19218 for ; Tue, 10 Mar 1998 12:34:27 -0800 (PST) (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 MAA20022; Tue, 10 Mar 1998 12:32:07 -0800 (PST) Message-Id: <199803102032.MAA20022@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: shimon@simon-shapiro.org cc: freebsd-current@FreeBSD.ORG Subject: Re: DPT in GENERIC In-reply-to: Your message of "Tue, 10 Mar 1998 11:07:47 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Mar 1998 12:32:05 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there any objection for the DPT driver being added to the GENERIC kernel > configuration and thus being available on the standard boot floppy? > > ``I do not know what/do not have a DPT controller'' is not a valid > objection. Ah, from *this* seat, not having one is somewhat of an objection. I guess we're going to have to see if we can't lay our hands on one shortly. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 12:35:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19537 for freebsd-current-outgoing; Tue, 10 Mar 1998 12:35:31 -0800 (PST) (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 MAA19483 for ; Tue, 10 Mar 1998 12:35:17 -0800 (PST) (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 0yCWFm-0000KT-00; Tue, 10 Mar 1998 15:08:02 -0600 X-Mailer: exmh version 2.0zeta 7/24/97 To: shimon@simon-shapiro.org cc: freebsd-current@FreeBSD.ORG Subject: Re: DPT in GENERIC In-reply-to: Your message of "Tue, 10 Mar 1998 11:07:47 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Mar 1998 15:08:02 -0600 From: Ted Spradley Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there any objection for the DPT driver being added to the GENERIC kernel > configuration and thus being available on the standard boot floppy? I don't have any objection to the DPT driver in GENERIC if it doesn't break anything else, but I do object to this: > > ``I do not know what/do not have a DPT controller'' is not a valid > objection. The reason I object is this: > > The DPT driver allows FreeBSD users the use of a family of SCSI RAID > controllers which are typically used in high end servers. For details ^^^^^^^^^^^^^^^^ I'd bet that folks who've got these DPT things don't often run GENERIC kernels on their high-end servers, and probably don't have too much trouble getting FreeBSD installed on those high-end servers even though the GENERIC kernel lacks a driver they need. The GENERIC kernel has to fit on the boot floppy that's used to do an initial installation on a machine that's the only computer in the building, and not connected to any network. As long as adding the DPT driver doesn't adversely effect that, then fine, add it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 12:58:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24489 for freebsd-current-outgoing; Tue, 10 Mar 1998 12:58:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA24479 for ; Tue, 10 Mar 1998 12:58:44 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yCW5X-0003Lc-00; Tue, 10 Mar 1998 12:57:27 -0800 Date: Tue, 10 Mar 1998 12:57:25 -0800 (PST) From: Tom To: Ted Spradley cc: shimon@simon-shapiro.org, freebsd-current@FreeBSD.ORG Subject: Re: DPT in GENERIC 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, 10 Mar 1998, Ted Spradley wrote: > > The DPT driver allows FreeBSD users the use of a family of SCSI RAID > > controllers which are typically used in high end servers. For details > ^^^^^^^^^^^^^^^^ > I'd bet that folks who've got these DPT things don't often run GENERIC kernels > on their high-end servers, and probably don't have too much trouble getting > FreeBSD installed on those high-end servers even though the GENERIC kernel > lacks a driver they need. The GENERIC kernel has to fit on the boot floppy Since DPT is a disk controller, it is pretty hard to make a system boot from a DPT connected disk unless dpt is in the GENERIC kernel to begin with. The dpt driver must be on the boot floppy to even install. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 13:00:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24858 for freebsd-current-outgoing; Tue, 10 Mar 1998 13:00:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA24753 for ; Tue, 10 Mar 1998 13:00:02 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yCW7s-0003bK-00; Tue, 10 Mar 1998 12:59:52 -0800 Date: Tue, 10 Mar 1998 12:59:49 -0800 (PST) From: Tom To: Terry Lambert cc: shimon@simon-shapiro.org, freebsd-current@FreeBSD.ORG Subject: Re: DPT in GENERIC In-Reply-To: <199803101959.MAA08570@usr01.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Mar 1998, Terry Lambert wrote: > > Is there any objection for the DPT driver being added to the GENERIC kernel > > configuration and thus being available on the standard boot floppy? > > > > ``I do not know what/do not have a DPT controller'' is not a valid > > objection. > > Did you build a boot floppy, and verify that it doesn't make the > kernel too large to fit or interfere with using the floppy to > install a FreeBSD system? I doubt it, unless something else has bloated GENERIC lately. Simon has been making boot floppies with GENERIC and the dpt driver on them for some time. The DPT card handles almost all SCSI processing on the card, so the driver seems pretty simple. > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 13:57:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09200 for freebsd-current-outgoing; Tue, 10 Mar 1998 13:57:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from symbion.srrc.usda.gov ([199.78.118.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08948 for ; Tue, 10 Mar 1998 13:54:53 -0800 (PST) (envelope-from glenn@nola.srrc.usda.gov) Received: from symbion.srrc.usda.gov (localhost [127.0.0.1]) by symbion.srrc.usda.gov (8.8.8/8.8.8) with ESMTP id PAA21916 for ; Tue, 10 Mar 1998 15:47:06 -0600 (CST) (envelope-from glenn@symbion.srrc.usda.gov) Message-Id: <199803102147.PAA21916@symbion.srrc.usda.gov> X-Mailer: exmh version 2.0.1 12/23/97 To: freebsd-current@FreeBSD.ORG From: Glenn Johnson Subject: panics with SMP and NFS Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Mar 1998 15:47:06 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know if this is an NFS or SMP problem but I get the following when I try to use NFS on an SMP system. "panic: bremfree: removing a buffer when not on a queue mp_lock = 00000001; cpuid = 0; 1apic.id = 01000000 boot() called on cpu #0 syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up Automatic reboot in 15 seconds.." Sometimes I will get the following instead: "I'm on cpu #1, I need to be on cpu #0, sleeping {repeated many times} timeout waiting for cpu #0" This was from sources cvsupped and built at about 3:45 CST. -- Glenn Johnson Technician USDA-ARS-SRRC Phone: (504) 286-4252 1100 Robert E. Lee Boulevard FAX: (504) 286-4217 New Orleans, LA 70124 e-mail: gjohnson@nola.srrc.usda.gov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 13:57:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09226 for freebsd-current-outgoing; Tue, 10 Mar 1998 13:57:16 -0800 (PST) (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 NAA09211 for ; Tue, 10 Mar 1998 13:57:10 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 20063 invoked by uid 1000); 10 Mar 1998 22:04:14 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [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: <199803101959.MAA08570@usr01.primenet.com> Date: Tue, 10 Mar 1998 14:04:14 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Terry Lambert Subject: Re: DPT in GENERIC Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Mar-98 Terry Lambert wrote: >> Is there any objection for the DPT driver being added to the GENERIC >> kernel >> configuration and thus being available on the standard boot floppy? >> >> ``I do not know what/do not have a DPT controller'' is not a valid >> objection. > > Did you build a boot floppy, and verify that it doesn't make the > kernel too large to fit or interfere with using the floppy to > install a FreeBSD system? Yup. Been doing so since 2.2beta, on a weekly basis. Still fits. I am testing the EISA additions from Matthew Dodd, to make sure these fit too. ---------- 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 Mar 10 14:02:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10495 for freebsd-current-outgoing; Tue, 10 Mar 1998 14:02:55 -0800 (PST) (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 OAA10457 for ; Tue, 10 Mar 1998 14:02:43 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 26694 invoked by uid 1000); 10 Mar 1998 22:09:28 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 10 Mar 1998 14:09:28 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Ted Spradley Subject: Re: DPT in GENERIC Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Mar-98 Ted Spradley wrote: >> Is there any objection for the DPT driver being added to the GENERIC >> kernel >> configuration and thus being available on the standard boot floppy? > > I don't have any objection to the DPT driver in GENERIC if it doesn't > break > anything else, but I do object to this: >> >> ``I do not know what/do not have a DPT controller'' is not a valid >> objection. > > The reason I object is this: >> >> The DPT driver allows FreeBSD users the use of a family of SCSI RAID >> controllers which are typically used in high end servers. For details > ^^^^^^^^^^^^^^^^ > I'd bet that folks who've got these DPT things don't often run GENERIC > kernels > on their high-end servers, and probably don't have too much trouble > getting > FreeBSD installed on those high-end servers even though the GENERIC > kernel > lacks a driver they need. The GENERIC kernel has to fit on the boot > floppy > that's used to do an initial installation on a machine that's the only > computer in the building, and not connected to any network. As long as > adding > the DPT driver doesn't adversely effect that, then fine, add it. Even very high-end servers have to install from something. In FreeBSD, this something is the boot floppy made with the GENERIC kenrel. So, it is needed for them rich people too :-) Yes, the driver fits on a boot floppy. I know that. Adding it is not breaking anything else I know of. there is well over a year behind this driver. BTW, there are inexpensive DPT controleers. I think you can get a PCI one for about $275.00 or less. Yes, same exact driver code for all of them. ISA, EISA, PCI. No ISA probing support yet... ---------- 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 Mar 10 14:03:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10718 for freebsd-current-outgoing; Tue, 10 Mar 1998 14:03:44 -0800 (PST) (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 OAA10673 for ; Tue, 10 Mar 1998 14:03:31 -0800 (PST) (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 AAA23188 for ; Wed, 11 Mar 1998 00:03:13 +0200 (EET) 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 AAA20780 for ; Wed, 11 Mar 1998 00:03:12 +0200 (EET) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.8.8/8.8.8/8.Who.Cares) with UUCP id AAA22298 for current@FreeBSD.ORG; Wed, 11 Mar 1998 00:01:26 +0200 (EET) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id XAA07443; Tue, 10 Mar 1998 23:51:48 +0200 (EET) (envelope-from archer) Date: Tue, 10 Mar 1998 23:51:48 +0200 (EET) From: Alexander Litvin Message-Id: <199803102151.XAA07443@grape.carrier.kiev.ua> To: current@FreeBSD.ORG Subject: Re: What does that mean? X-Newsgroups: grape.freebsd.current In-Reply-To: <199803092247.RAA00572@dyson.iquest.net> 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 <199803092247.RAA00572@dyson.iquest.net> you wrote: >> > > spec_getpages: I/O read failure: (error code=0) >> > > size: 4096, resid: 0, a_count: 3586, valid: 0x0 >> > > nread: 4096, reqpage: 1, pindex: 21, pcount: 1 >> > > vm_fault: pager input (probably hardware) error, PID 18023 failure >> > > Mar 9 15:48:51 grape /kernel: pid 18023 (tail), uid 0: exited on signal 11 >> > > >> > > The second attempt to issue the same command succeded. >> > > >> > > Is it really hardware-related, or... >> > > >> > It is likely a bug that I have created. I work on it NOW. >> > Tor Egge created a fix, and I just committed it. Give it a try again!!! Thank you, it seems to resolve that problem. > -- > 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. -- 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 Tue Mar 10 14:09:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12080 for freebsd-current-outgoing; Tue, 10 Mar 1998 14:09:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from poboxes.com (rhrz-isdn3-p13.rhrz.uni-bonn.de [131.220.225.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12070 for ; Tue, 10 Mar 1998 14:09:13 -0800 (PST) (envelope-from gorski@poboxes.com) From: gorski@poboxes.com Received: (from gorski@localhost) by poboxes.com (8.8.8/8.8.8) id XAA01205 for current@FreeBSD.ORG; Tue, 10 Mar 1998 23:07:26 +0100 (CET) (envelope-from gorski) Date: Tue, 10 Mar 1998 23:07:26 +0100 (CET) Message-Id: <199803102207.XAA01205@poboxes.com> To: current@FreeBSD.ORG Subject: Hylafax faxgetty eats 100% CPU on 3.0-980304-SNAP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On my 3.0-980304-SNAP the Hylafax faxgetty prg eats the whole CPU time, but works. Does anybody has the same problem and is there a solution? Thanks for information & advice. - Achim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 14:20:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14539 for freebsd-current-outgoing; Tue, 10 Mar 1998 14:20:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mpdr0.detroit.mi.ameritech.net (mpdr0.detroit.mi.ameritech.net [206.141.239.206]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14397 for ; Tue, 10 Mar 1998 14:19:56 -0800 (PST) (envelope-from mcdougall@ameritech.net) Received: from ameritech.net ([206.141.225.134]) by mpdr0.detroit.mi.ameritech.net (InterMail v03.02.01 118 111) with ESMTP id <19980310231841.FHXN7456@ameritech.net>; Tue, 10 Mar 1998 17:18:41 -0600 Message-ID: <3505E622.E4629487@ameritech.net> Date: Tue, 10 Mar 1998 17:17:24 -0800 From: Adam McDougall X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: Snob Art Genre CC: freebsd-current@FreeBSD.ORG Subject: Re: DPT in GENERIC References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Me three :) Can anyone recommend a good place (or several) where I could get a 2044UW? Thanks. Snob Art Genre wrote: > Me too! > > On Tue, 10 Mar 1998, Tom Bartol wrote: > > > > > If a vote would help, I would vote in favor of this as I am getting ready > > to purchase a large server machine and I plan to use the DPT controller > > for RAID. It would be nice to be able to have a GENERIC kernel that I can > > count on reliably booting the machine during installation and in case of > > emergency. > > > > Tom > > > > Ben > > "You have your mind on computers, it seems." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 14:40:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18597 for freebsd-current-outgoing; Tue, 10 Mar 1998 14:40:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gorgon.lovett.com (root@gorgon.lovett.com [38.155.241.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA18592 for ; Tue, 10 Mar 1998 14:40:46 -0800 (PST) (envelope-from ade@demon.net) Received: from gorgon.lovett.com [38.155.241.3] (ade) by gorgon.lovett.com with esmtp (Exim 1.82 #1) id 0yCXgh-0000rq-00; Tue, 10 Mar 1998 16:39:55 -0600 To: Glenn Johnson Cc: current@FreeBSD.ORG Subject: Re: panics with SMP and NFS Organization: Demon Internet Reply-To: ade@demon.net In-reply-to: Your message of "Tue, 10 Mar 1998 15:47:06 CST." <199803102147.PAA21916@symbion.srrc.usda.gov> Date: Tue, 10 Mar 1998 16:39:54 -0600 From: Ade Lovett Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Glenn Johnson writes: > >I don't know if this is an NFS or SMP problem but I get the following when I >try to use NFS on an SMP system. > > "panic: bremfree: removing a buffer when not on a queue Looks like a {V,N}FS problem rather than SMP -- at least I've just seen this happen a few times on a single-cpu box - there doesn't seem to be any repeatability to the problem, just effectively random NFS hangs, then a panic and reboot. Peeking at the code, it seems that this panic (and a bunch of other stuff) is only called if MAX_PERF is undefined -- sadly, no mention of MAX_PERF is made in any of the kernel config files (even LINT). Unfortunately, I'm not able to produce a crash trace of the panic, since the -current I'm using (cvsup @ 0300 CST, 03/10) appears to be incapable of producing sensible debug kernels - viz: config -g BLAH (make depend, make) cp kernel kernel.debug strip -d kernel make install Leads to thousands (literally) of: "Bad string table index (...)" message being sent to the console before any other output from the kernel, and then practically everything that uses kvm falls over. Mar 10 08:47:31 icebat /kernel: pid 25 (dmesg), uid 0: exited on signal 11 Mar 10 08:47:31 icebat /kernel: pid 80 (dset), uid 0: exited on signal 11 Mar 10 08:47:32 icebat /kernel: pid 87 (tickadj), uid 0: exited on signal 11 Mar 10 08:47:32 icebat /kernel: pid 94 (xntpd), uid 0: exited on signal 11 Mar 10 08:47:32 icebat /kernel: pid 118 (kvm_mkdb), uid 0: exited on signal 11 "Normal" config's (without the -g) work just fine. -aDe -- Ade Lovett, Demon Internet, Austin, Texas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 14:55:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21100 for freebsd-current-outgoing; Tue, 10 Mar 1998 14:55:23 -0800 (PST) (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 OAA21075 for ; Tue, 10 Mar 1998 14:55:15 -0800 (PST) (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 WAA04430; Tue, 10 Mar 1998 22:55:07 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id XAA11207; Tue, 10 Mar 1998 23:55:06 +0100 (MET) Message-ID: <19980310235506.04127@follo.net> Date: Tue, 10 Mar 1998 23:55:06 +0100 From: Eivind Eklund To: ade@demon.net, Glenn Johnson Cc: current@FreeBSD.ORG Subject: Re: panics with SMP and NFS References: <199803102147.PAA21916@symbion.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Ade Lovett on Tue, Mar 10, 1998 at 04:39:54PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 10, 1998 at 04:39:54PM -0600, Ade Lovett wrote: > Glenn Johnson writes: > > > >I don't know if this is an NFS or SMP problem but I get the following when I > >try to use NFS on an SMP system. > > > > "panic: bremfree: removing a buffer when not on a queue > > Looks like a {V,N}FS problem rather than SMP -- at least I've just > seen this happen a few times on a single-cpu box - there doesn't > seem to be any repeatability to the problem, just effectively > random NFS hangs, then a panic and reboot. > > Peeking at the code, it seems that this panic (and a bunch of other > stuff) is only called if MAX_PERF is undefined -- sadly, no mention > of MAX_PERF is made in any of the kernel config files (even LINT). I'll check with John and possibly add this as a commented out option in LINT. However, the only thing adding MAX_PERF will do is remove a bunch of cheap sanity checking - when something panic() when that is not defined, it just mean you'd be getting incorrect results if MAX_PERF had been defined. That wouldn't really be of help. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 15:04:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22941 for freebsd-current-outgoing; Tue, 10 Mar 1998 15:04:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22931; Tue, 10 Mar 1998 15:04:22 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id PAA21639; Tue, 10 Mar 1998 15:04:08 -0800 (PST) (envelope-from jdp) Message-Id: <199803102304.PAA21639@austin.polstra.com> To: ken@plutotech.com Subject: Re: problems stripping kernels In-Reply-To: <199803102018.NAA16119@panzer.plutotech.com> References: <199803102018.NAA16119@panzer.plutotech.com> Organization: Polstra & Co., Seattle, WA Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Date: Tue, 10 Mar 1998 15:04:08 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199803102018.NAA16119@panzer.plutotech.com>, Kenneth D. Merry wrote: > I've noticed a problem stripping kernels since John's changes on > Saturday went in. (and it wasn't fixed by version 1.46 of ufs_readwrite.c > yesterday) > > Basically, I config my kernels with -g, and then use strip -d to > strip off the debugging symbols (after saving a copy of the kernel with > debugging symbols, of course). The problem is that kernels I strip on a > machine using a kernel built after Saturday's changes don't boot. They > just hang forever with the little spinning cursor. Kernels stripped on the > same machine running a kernel from before Saturday's changes work just > fine. I can confirm this. > From what I can tell, there are three bytes different between the > two kernels: > > $ ls -la kernel* > -rwxr-xr-x 1 ken wheel 1409956 Mar 10 09:50 kernel* > -rwx------ 1 ken wheel 1409956 Mar 10 09:53 kernel.debug* > $ cmp -l kernel kernel.debug > 17 140 20 > 18 266 133 > 19 67 1 Those are in the a.out header in the field that says how many bytes of symbol table are present. I noticed that in the failing case, the header of the stripped kernel still says it has the same number of bytes of symbols as the header of the unstripped kernel it was made from. In other words, this statement at strip.c:241 isn't taking effect: /* Fill in new symbol table size. */ ep->a_syms = (nsym - symbase) * sizeof(NLIST); Here, ep points to an image of the file that was mmapped at line 189: /* Map the file. */ if ((ep = (EXEC *)mmap(NULL, (size_t)sb.st_size, PROT_READ | PROT_WRITE, MAP_SHARED, fd, (off_t)0)) == (EXEC *)MAP_FAILED) { -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 15:13:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24434 for freebsd-current-outgoing; Tue, 10 Mar 1998 15:13:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24407; Tue, 10 Mar 1998 15:13:35 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id PAA21771; Tue, 10 Mar 1998 15:13:35 -0800 (PST) (envelope-from jdp) Message-Id: <199803102313.PAA21771@austin.polstra.com> To: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: problems stripping kernels In-Reply-To: <199803102304.PAA21639@austin.polstra.com> References: <199803102018.NAA16119@panzer.plutotech.com> <199803102304.PAA21639@austin.polstra.com> Organization: Polstra & Co., Seattle, WA Cc: ken@plutotech.com Date: Tue, 10 Mar 1998 15:13:34 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > made from. In other words, this statement at strip.c:241 isn't > taking effect: > > /* Fill in new symbol table size. */ > ep->a_syms = (nsym - symbase) * sizeof(NLIST); > > Here, ep points to an image of the file that was mmapped at line 189: > > /* Map the file. */ > if ((ep = (EXEC *)mmap(NULL, (size_t)sb.st_size, > PROT_READ | PROT_WRITE, MAP_SHARED, fd, (off_t)0)) == (EXEC *)MAP_FAILED) { For what it's worth (probably not much), I tried adding a call to msync right before the munmap call in strip.c. It didn't make any difference. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 15:25:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26495 for freebsd-current-outgoing; Tue, 10 Mar 1998 15:25:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26462; Tue, 10 Mar 1998 15:25:30 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id KAA00884; Wed, 11 Mar 1998 10:24:38 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803102324.KAA00884@cimlogic.com.au> Subject: Re: problems stripping kernels In-Reply-To: <199803102313.PAA21771@austin.polstra.com> from John Polstra at "Mar 10, 98 03:13:34 pm" To: jdp@polstra.com (John Polstra) Date: Wed, 11 Mar 1998 10:24:38 +1100 (EST) Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG, ken@plutotech.com 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 Polstra wrote: > > /* Map the file. */ > > if ((ep = (EXEC *)mmap(NULL, (size_t)sb.st_size, > > PROT_READ | PROT_WRITE, MAP_SHARED, fd, (off_t)0)) == (EXEC *)MAP_FAILED) { > > For what it's worth (probably not much), I tried adding a call to > msync right before the munmap call in strip.c. It didn't make any > difference. I don't know if this is related (because I'm not seeing the problem), but I committed a 64-bit fix to mmap.c in libc 1998/03/09 07:27:58. If you've built libc from cvsuped sources since then, it might be worth backing out that change to see if it is biting. cvs diff -r1.2 -r1.3 mmap.c Index: mmap.c =================================================================== RCS file: /home/ncvs/src/lib/libc/sys/mmap.c,v retrieving revision 1.2 retrieving revision 1.3 diff -r1.2 -r1.3 40a41 > #include 56c57 < return((void *)__syscall((quad_t)SYS_mmap, addr, len, prot, flags, --- > return((void *)(long)__syscall((quad_t)SYS_mmap, addr, len, prot, flags, -- 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 Mar 10 15:29:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27230 for freebsd-current-outgoing; Tue, 10 Mar 1998 15:29:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.31.78.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27184 for ; Tue, 10 Mar 1998 15:28:46 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id SAA21001; Tue, 10 Mar 1998 18:36:22 -0500 (EST) Date: Tue, 10 Mar 1998 18:36:22 -0500 (EST) From: "Matthew N. Dodd" Reply-To: "Matthew N. Dodd" To: Simon Shapiro cc: Ted Spradley , freebsd-current@FreeBSD.ORG Subject: Re: DPT in GENERIC 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, 10 Mar 1998, Simon Shapiro wrote: > BTW, there are inexpensive DPT controleers. I think you can get a PCI one > for about $275.00 or less. Yes, same exact driver code for all of them. > ISA, EISA, PCI. No ISA probing support yet... ^^^^^^^^^^^^^^^^^^^^^^^^^^ But once I get an ISA card here I'll fix that... Daniel Berlin has a spare PM2021 that he has agreed to ship me so ISA support should be available a week or so after I receive the card. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 15:29:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27408 for freebsd-current-outgoing; Tue, 10 Mar 1998 15:29:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27302; Tue, 10 Mar 1998 15:29:26 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id PAA21956; Tue, 10 Mar 1998 15:29:04 -0800 (PST) (envelope-from jdp) Message-Id: <199803102329.PAA21956@austin.polstra.com> To: John Birrell cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG, ken@plutotech.com Subject: Re: problems stripping kernels In-reply-to: Your message of "Wed, 11 Mar 1998 10:24:38 +1100." <199803102324.KAA00884@cimlogic.com.au> Date: Tue, 10 Mar 1998 15:29:04 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't know if this is related (because I'm not seeing the problem), but > I committed a 64-bit fix to mmap.c in libc 1998/03/09 07:27:58. > > If you've built libc from cvsuped sources since then, it might be worth > backing out that change to see if it is biting. I haven't tried backing it out. But it really doesn't look like the culprit to me. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 15:33:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28282 for freebsd-current-outgoing; Tue, 10 Mar 1998 15:33:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gorgon.lovett.com (root@gorgon.lovett.com [38.155.241.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA28230 for ; Tue, 10 Mar 1998 15:33:06 -0800 (PST) (envelope-from ade@demon.net) Received: from gorgon.lovett.com [38.155.241.3] (ade) by gorgon.lovett.com with esmtp (Exim 1.82 #1) id 0yCYVv-0000tx-00; Tue, 10 Mar 1998 17:32:51 -0600 To: Eivind Eklund cc: current@FreeBSD.ORG Subject: Re: panics with SMP and NFS Organization: Demon Internet Reply-To: ade@demon.net In-reply-to: Your message of "Tue, 10 Mar 1998 23:55:06 +0100." <19980310235506.04127@follo.net> Date: Tue, 10 Mar 1998 17:32:47 -0600 From: Ade Lovett Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund writes: > >> Peeking at the code, it seems that this panic (and a bunch of other >> stuff) is only called if MAX_PERF is undefined -- sadly, no mention >> of MAX_PERF is made in any of the kernel config files (even LINT). > >I'll check with John and possibly add this as a commented out option >in LINT. I'm just wondering how many other undocumented (at least, not mentioned in LINT) #ifdef's there are in the sys/ tree... Would it be useful if I did a scan over the current tree and produced a list of such "missing" options? -aDe -- Ade Lovett, Demon Internet, Austin, Texas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 15:42:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00829 for freebsd-current-outgoing; Tue, 10 Mar 1998 15:42:22 -0800 (PST) (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 PAA00808 for ; Tue, 10 Mar 1998 15:42:09 -0800 (PST) (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 XAA05026; Tue, 10 Mar 1998 23:42:03 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id AAA13794; Wed, 11 Mar 1998 00:42:03 +0100 (MET) Message-ID: <19980311004202.49594@follo.net> Date: Wed, 11 Mar 1998 00:42:02 +0100 From: Eivind Eklund To: ade@demon.net, Eivind Eklund Cc: current@FreeBSD.ORG Subject: Re: panics with SMP and NFS References: <19980310235506.04127@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Ade Lovett on Tue, Mar 10, 1998 at 05:32:47PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 10, 1998 at 05:32:47PM -0600, Ade Lovett wrote: > Eivind Eklund writes: > > > >> Peeking at the code, it seems that this panic (and a bunch of other > >> stuff) is only called if MAX_PERF is undefined -- sadly, no mention > >> of MAX_PERF is made in any of the kernel config files (even LINT). > > > >I'll check with John and possibly add this as a commented out option > >in LINT. > > I'm just wondering how many other undocumented (at least, not > mentioned in LINT) #ifdef's there are in the sys/ tree... There are somewhere between 500 and 600 unmentioned symbols that are checked by #if defined/#if !defined/ifdef/ifndef statements. > Would it be useful if I did a scan over the current tree and produced > a list of such "missing" options? There isn't too much point in you going over them, as I've already got a list, produced by the following little script and a little pipe with awk, sort and uniq. #!/usr/local/bin/perl use strict; my %symbols; my $key; while (<>) { if (/^[ \t]*\#[ \t]*ifn?def[ \t]+([A-Za-z_][A-Za-z_0-9]*)/) { $symbols{$1} = 1; } elsif (/[ \t]*\#[ \t]*if[ \t]/) { while (/defined[ \t]*\([ \t]*([A-Za-z_][A-Za-z_0-9]*)/g) { $symbols{$1} = 1; } } } foreach $key (sort keys %symbols) { print "$key\n"; } However, if you want to help me _remove_ the ifdefs, you're more than welcome. I committed a lengthy comment describing the preferred state of affairs to conf/options earlier today; a non-mentioned point is that options should generally go away, and be replaced with sysctls or smarter code. I'll accept patches to this effect, and make sure they're reviewed and either committed or rejected (with the reasons why) fairly quickly. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 15:44:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01381 for freebsd-current-outgoing; Tue, 10 Mar 1998 15:44:13 -0800 (PST) (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 PAA01268; Tue, 10 Mar 1998 15:43:58 -0800 (PST) (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 AAA09003; Wed, 11 Mar 1998 00:43:25 +0100 (MET) Message-Id: <199803102343.AAA09003@pat.idi.ntnu.no> To: ken@plutotech.com Cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: problems stripping kernels In-Reply-To: Your message of "Tue, 10 Mar 1998 11:01:23 -0700 (MST)" References: <199803101801.LAA15498@panzer.plutotech.com> 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: Wed, 11 Mar 1998 00:43:25 +0100 From: Tor Egge Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Howdy, > > I've noticed a problem stripping kernels since John's changes on > Saturday went in. (and it wasn't fixed by version 1.46 of ufs_readwrite.c > yesterday) > The following patch worked for me as a workaround. As long as msync()/munmap() is performed before ftruncate(), there is no problems with regard to what is 'legal' values for the size fields. Index: strip.c =================================================================== RCS file: /home/ncvs/src/usr.bin/strip/strip.c,v retrieving revision 1.11 diff -u -r1.11 strip.c --- strip.c 1997/08/12 06:44:57 1.11 +++ strip.c 1998/03/09 22:35:26 @@ -250,12 +250,13 @@ */ bcopy(nstrbase, (void *)nsym, len); + msync((caddr_t) ep, (size_t)sb.st_size, MS_SYNC); + munmap((caddr_t)ep, (size_t)sb.st_size); /* Truncate to the current length. */ if (ftruncate(fd, (char *)nsym + len - (char *)ep)) { warn("%s", fn); err_val = 1; } - munmap((caddr_t)ep, (size_t)sb.st_size); } static void - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 15:48:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02353 for freebsd-current-outgoing; Tue, 10 Mar 1998 15:48:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02234 for ; Tue, 10 Mar 1998 15:47:52 -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 CAA08107; Wed, 11 Mar 1998 02:40:25 +0300 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 CAA02253; Wed, 11 Mar 1998 02:49:45 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199803102349.CAA02253@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Charlie ROOT cc: current@FreeBSD.ORG Subject: Re: old msdosfs? In-reply-to: Your message of "Tue, 10 Mar 1998 10:00:01 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Mar 1998 02:49:45 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charlie ROOT wrote: > > What does this message mean: > > Old mount_msdosfs, flags=0 > > ? This is a debugging printf that I forgot to remove. This should mean that your mount_msdos is much older than your kernel. I suspect that this is not the case. If you have NFS server, this message actually mean that I am stupid. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 15:50:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02934 for freebsd-current-outgoing; Tue, 10 Mar 1998 15:50:48 -0800 (PST) (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 PAA02909 for ; Tue, 10 Mar 1998 15:50:40 -0800 (PST) (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 XAA05158; Tue, 10 Mar 1998 23:50:38 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id AAA13846; Wed, 11 Mar 1998 00:50:37 +0100 (MET) Message-ID: <19980311005037.12733@follo.net> Date: Wed, 11 Mar 1998 00:50:37 +0100 From: Eivind Eklund To: ade@demon.net Cc: current@FreeBSD.ORG Subject: Re: panics with SMP and NFS References: <19980310235506.04127@follo.net> <19980311004202.49594@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980311004202.49594@follo.net>; from Eivind Eklund on Wed, Mar 11, 1998 at 12:42:03AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 11, 1998 at 12:42:03AM +0100, Eivind Eklund wrote: > However, if you want to help me _remove_ the ifdefs, you're more than > welcome. Just so this isn't misunderstood: Of course, documentation/LINT entries for options is good too. It's just finding them that doesn't really help. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 15:57:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04245 for freebsd-current-outgoing; Tue, 10 Mar 1998 15:57:14 -0800 (PST) (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 PAA04232 for ; Tue, 10 Mar 1998 15:57:08 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 7283 invoked by uid 1000); 11 Mar 1998 00:04:11 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 10 Mar 1998 16:04:11 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: "Matthew N. Dodd" Subject: Re: DPT in GENERIC Cc: Ted Spradley , freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Mar-98 Matthew N. Dodd wrote: > On Tue, 10 Mar 1998, Simon Shapiro wrote: >> BTW, there are inexpensive DPT controleers. I think you can get a PCI >> one >> for about $275.00 or less. Yes, same exact driver code for all of them. >> ISA, EISA, PCI. No ISA probing support yet... > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > But once I get an ISA card here I'll fix that... > > Daniel Berlin has a spare PM2021 > that he has agreed to ship me so ISA support should be available a week > or > so after I receive the card. Yes, folks, Matthew is to be thanked for the EISA/ISA/S-100 support. I just discarded a DPT 1011 :-) Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 16:03:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05425 for freebsd-current-outgoing; Tue, 10 Mar 1998 16:03:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.31.78.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05412 for ; Tue, 10 Mar 1998 16:03:55 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id TAA21532; Tue, 10 Mar 1998 19:11:57 -0500 (EST) Date: Tue, 10 Mar 1998 19:11:57 -0500 (EST) From: "Matthew N. Dodd" To: Simon Shapiro cc: Ted Spradley , freebsd-current@FreeBSD.ORG Subject: Re: DPT in GENERIC 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, 10 Mar 1998, Simon Shapiro wrote: > Yes, folks, Matthew is to be thanked for the EISA/ISA/S-100 support. What about MCA and QBus? > I just discarded a DPT 1011 :-) How could you! :) /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 16:52:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13580 for freebsd-current-outgoing; Tue, 10 Mar 1998 16:52:06 -0800 (PST) (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 QAA13573 for ; Tue, 10 Mar 1998 16:52:03 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id TAA01579; Tue, 10 Mar 1998 19:51:03 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Tue, 10 Mar 1998 19:51:03 -0500 (EST) From: "Alok K. Dhir" To: dima@tejblum.dnttm.rssi.ru cc: current@FreeBSD.ORG Subject: Re: old msdosfs? In-Reply-To: <9D24EB2D00F692ED852565C300834DE6.0082B682852565C3@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 Aaah - OK, thx. BTW - my mount_msdos is brand new - built with "world" along with everything else. Incidentally, I'm certain you're not stupid. :-) > This is a debugging printf that I forgot to remove. This should mean > that your mount_msdos is much older than your kernel. I suspect that > this is not the case. If you have NFS server, this message actually > mean that I am stupid. > > Dima > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 17:09:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17267 for freebsd-current-outgoing; Tue, 10 Mar 1998 17:09:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA17260 for ; Tue, 10 Mar 1998 17:09:36 -0800 (PST) (envelope-from dyson@iquest.net) From: dyson@iquest.net Received: (qmail 7651 invoked from network); 11 Mar 1998 01:09:33 -0000 Received: from iquest7.iquest.net (206.53.230.110) by iquest3.iquest.net with SMTP; 11 Mar 1998 01:09:33 -0000 Received: (qmail 1368 invoked by uid 4420); 11 Mar 1998 01:09:32 -0000 Message-ID: <19980311010932.1366.qmail@iquest7.iquest.net> Subject: Re: panics with SMP and NFS To: ade@demon.net Date: Tue, 10 Mar 1998 20:09:31 -0500 (EST) Cc: gjohnson@nola.srrc.usda.gov, current@FreeBSD.ORG In-Reply-To: from "Ade Lovett" at Mar 10, 98 04:39: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 > > Peeking at the code, it seems that this panic (and a bunch of other > stuff) is only called if MAX_PERF is undefined -- sadly, no mention > of MAX_PERF is made in any of the kernel config files (even LINT). > Just a suggestion: Be careful using options that are not defined. That option is used by me to evaluate the overhead of certain types consistancy checking. It will probably be a part of the code, but when such options are used, and when the code is still being developed, the valuable internal system consistancy checks are disabled, and the side effects of such can be disasterous. It is bad enough to remove 'options DIAGNOSTIC' on a -current kernel. You are taking even bigger risks using performance options. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 17:19:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18993 for freebsd-current-outgoing; Tue, 10 Mar 1998 17:19:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from forbidden-donut.anet-stl.com (doogie@forbidden-donut.anet-stl.com [209.83.128.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18963 for ; Tue, 10 Mar 1998 17:19:37 -0800 (PST) (envelope-from doogie@forbidden-donut.anet-stl.com) Received: from localhost (doogie@localhost) by forbidden-donut.anet-stl.com (8.8.8/8.8.7) with SMTP id TAA17175 for ; Tue, 10 Mar 1998 19:14:33 -0600 (CST) (envelope-from doogie@forbidden-donut.anet-stl.com) Date: Tue, 10 Mar 1998 19:14:31 -0600 (CST) From: Jason Young To: current@FreeBSD.ORG Subject: Softupdates - Kirk's response In-Reply-To: <34EE3060.4487EB71@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- I'm sending this official response to the current list as it is germane to its inclusion or exclusion from -CURRENT, and apparently many people here are interested. If someone wants to forward it to -chat that would be nice but I'm not on that list. - ----- My "official" response, which you are welcome to post to the mailing list is this: Companies that wish to incorporate the soft update code into systems that will be resold for profit are required to get a license. Generally, the license will require the payment of a one-time fee that covers use of the code by that company in all their products. It does not allow them to sell the soft update code by itself, only to incorporate it into their own products. The one-time fee is negotiated based on the importance of the code to the functioning of the product and the expected size of the market for the product. For-profit companies that wish to use the soft update code in their day-to-day commercial operations but are not distributing it to their customers (for example, ISP's using it in their web servers, ftp archives, etc.) are requested but not required to pay a one-time fee. The fee revenue will be used to support the continued development and support of the soft update code (for example fsck-less rebooting and live dumps). Those companies that pay the one-time fee will receive notification of any offical bug fixes and enhancements as they are made. Requests for information about licensing should be sent to: mckusick@mckusick.com or Marshall Kirk McKusick 1614 Oxford Street Berkeley, CA 94709-1608 - ----- Jason Young ANET Chief Network Engineer "Bother," said Pooh, "Eeyore, ready two photon torpedoes and lock phasers on the Heffalump, Piglet, meet me in transporter room three." -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNQXleaInE6ybC66VAQH0VgL/S68BAaOTQFTcA19KW/9sJSxdpXjX1Avv EvytNz/wa75KrAw9DZ34fX6JaKlfMSoJAKO6CWbDum9wv/6v5fFme20zxp5zlfpR tMuYZbdi7cVQnUZ2NTwmcDQYuDrrObIb =Afmb -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 18:49:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00249 for freebsd-current-outgoing; Tue, 10 Mar 1998 18:49:40 -0800 (PST) (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 SAA00234 for ; Tue, 10 Mar 1998 18:49:38 -0800 (PST) (envelope-from jmz@cabri.obs-besancon.fr) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA11488; Wed, 11 Mar 98 03:53:38 +0100 Date: Wed, 11 Mar 98 03:53:38 +0100 Message-Id: <9803110253.AA11488@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: current@FreeBSD.ORG Subject: Panic with the new slice stuff X-Mailer: Emacs Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wanted to know if my boot disk is dedicated ot not :-) I got: 'error 6: panic: cannot mount root (2)', just after the message: changing root device to sd0s5a What can I do? 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 Mar 10 19:10:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02580 for freebsd-current-outgoing; Tue, 10 Mar 1998 19:10:15 -0800 (PST) (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 TAA02575 for ; Tue, 10 Mar 1998 19:10:10 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA06520 for ; Tue, 10 Mar 1998 19:03:40 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd006516; Tue Mar 10 19:03:33 1998 Message-ID: <3505FE01.695678E2@whistle.com> Date: Tue, 10 Mar 1998 18:59:13 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Softupdates code not Prime Time yet. 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 to let those of you who are looking a the soft-updates code, know that there are still several known problems with the code. We have 2 (possibly but not neccesarily related) crash scenarios, and also a dependency tracking failure. The latter means that there are cases (hey let's be real, USUALLY) where a crash with softupdates running on an active filesystem, will have similar corrupting actions as running async (or at least sync) at the time of a crash. This is a BUG (unlike in async where it is a feature :-) and we are trying to find the missing dependency. So while it's good to play with and really fast, it should still be only used on replaceable data (e.g. /usr/obj) Thanks for all the testing and support! julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 19:12:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02959 for freebsd-current-outgoing; Tue, 10 Mar 1998 19:12:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from luoqi.watermarkgroup.com (luoqi.watermarkgroup.com [207.202.73.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02941 for ; Tue, 10 Mar 1998 19:12:43 -0800 (PST) (envelope-from luoqi@luoqi.watermarkgroup.com) Received: (from luoqi@localhost) by luoqi.watermarkgroup.com (8.8.8/8.8.8) id WAA03744 for current@freebsd.org; Tue, 10 Mar 1998 22:12:42 -0500 (EST) (envelope-from luoqi) Date: Tue, 10 Mar 1998 22:12:42 -0500 (EST) From: Luoqi Chen Message-Id: <199803110312.WAA03744@luoqi.watermarkgroup.com> To: current@FreeBSD.ORG Subject: typo in vop_stdlock() ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Found this when I was browsing throught the code (vfs_default.c), int vop_stdlock(ap) struct vop_lock_args /* { struct vnode *a_vp; int a_flags; struct proc *a_p; } */ *ap; { struct lock *l; if ((l = (struct lock *)ap->a_vp->v_data) == NULL) { if (ap->a_flags & LK_INTERLOCK) simple_unlock(&ap->a_vp->v_interlock); ^^^^^^^^^^^^^ return 0; } return (lockmgr(l, ap->a_flags, &ap->a_vp->v_interlock, ap->a_p)); } Shouldn't simple_unlock be simple_lock instead? -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 19:22:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04955 for freebsd-current-outgoing; Tue, 10 Mar 1998 19:22:26 -0800 (PST) (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 TAA04949 for ; Tue, 10 Mar 1998 19:22:23 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id WAA28896; Tue, 10 Mar 1998 22:19:53 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Tue, 10 Mar 1998 22:19:49 -0500 (EST) From: "Alok K. Dhir" To: current@FreeBSD.ORG cc: Daniel Ingber Subject: Amazing :-) 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 enabled softupdates on all filesystems except root on my SMP -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB RAM). The "make world" time just went from ~6 hours to 2 hours 20 mins. That is one hell of a performance increase! Al To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 19:40:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06559 for freebsd-current-outgoing; Tue, 10 Mar 1998 19:40:41 -0800 (PST) (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 TAA06554 for ; Tue, 10 Mar 1998 19:40:39 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA07248; Tue, 10 Mar 1998 19:35:05 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd007240; Tue Mar 10 19:35:00 1998 Message-ID: <35060560.13728473@whistle.com> Date: Tue, 10 Mar 1998 19:30:40 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: "Alok K. Dhir" CC: current@FreeBSD.ORG, Daniel Ingber Subject: Re: Amazing :-) References: 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: > > I just enabled softupdates on all filesystems except root on my SMP > -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB RAM). > The "make world" time just went from ~6 hours to 2 hours 20 mins. > > That is one hell of a performance increase! > > Al > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message you must have /usr/obj, /var/tmp and /usr/src all on the same physical disk?? (i.e. your setup greatly benefitted from making those accesses async from the compilation process.) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 19:49:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07654 for freebsd-current-outgoing; Tue, 10 Mar 1998 19:49:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley63.res.iastate.edu (friley63.res.iastate.edu [129.186.189.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA07639 for ; Tue, 10 Mar 1998 19:49:21 -0800 (PST) (envelope-from mystify@friley63.res.iastate.edu) Received: from friley63.res.iastate.edu (loopback [127.0.0.1]) by friley63.res.iastate.edu (8.8.8/8.8.5) with ESMTP id VAA24326; Tue, 10 Mar 1998 21:48:48 -0600 (CST) Message-Id: <199803110348.VAA24326@friley63.res.iastate.edu> Reply-to: mystify@iastate.edu To: "Alok K. Dhir" cc: current@FreeBSD.ORG Subject: Re: Amazing :-) In-reply-to: Message from "Alok K. Dhir" of "Tue, 10 Mar 1998 22:19:49 EST." Date: Tue, 10 Mar 1998 21:48:48 -0600 From: Patrick Hartling Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Alok K. Dhir" wrote: } I just enabled softupdates on all filesystems except root on my SMP } -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB RAM). } The "make world" time just went from ~6 hours to 2 hours 20 mins. It is, but you certainly started off with a *slow* build. On my old P5/166 with 64 MB of RAM, I could do it in about four hours. With my dual P6/200 with 128 MB of RAM (same disk partitions and such) and parallel build and soft updates, I'm down to about 1 hour and 20 minutes. Kernels build in just over two minutes. :) I think you may need to optimize your system a bit. ;) -Patrick Patrick L. Hartling | Research Assistant, ICEMT mystify@friley63.res.iastate.edu | SE Lab - 1117 Black Engineering http://www.public.iastate.edu/~oz | http://www.icemt.iastate.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 20:10:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09682 for freebsd-current-outgoing; Tue, 10 Mar 1998 20:10:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09666 for ; Tue, 10 Mar 1998 20:10:45 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA24737; Wed, 11 Mar 1998 15:09:58 +1100 Date: Wed, 11 Mar 1998 15:09:58 +1100 From: Bruce Evans Message-Id: <199803110409.PAA24737@godzilla.zeta.org.au> To: current@FreeBSD.ORG, luoqi@luoqi.watermarkgroup.com Subject: Re: typo in vop_stdlock() ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >int >vop_stdlock(ap) > struct vop_lock_args /* { > struct vnode *a_vp; > int a_flags; > struct proc *a_p; > } */ *ap; >{ > struct lock *l; > > if ((l = (struct lock *)ap->a_vp->v_data) == NULL) { > if (ap->a_flags & LK_INTERLOCK) > simple_unlock(&ap->a_vp->v_interlock); > ^^^^^^^^^^^^^ > return 0; > } > > return (lockmgr(l, ap->a_flags, &ap->a_vp->v_interlock, ap->a_p)); >} > >Shouldn't simple_unlock be simple_lock instead? No. LK_INTERLOCK means that the vnode is already simple-interlocked and that the simple-interlock shall be released when the function returns. The lock is normally relased in lockmgr() as part of upgrading to a non-simple lock, but non-simple locking is impossible in the NULL v_data case (v_data points to an inode whose first element is the non-simple lock, except of course when the pointer is NULL). Perhaps this case shouldn't happen. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 20:20:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10656 for freebsd-current-outgoing; Tue, 10 Mar 1998 20:20:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA10648 for ; Tue, 10 Mar 1998 20:20:10 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yCczt-0005sU-00; Tue, 10 Mar 1998 20:20:05 -0800 Date: Tue, 10 Mar 1998 20:20:02 -0800 (PST) From: Tom To: "Alok K. Dhir" cc: current@FreeBSD.ORG, Daniel Ingber Subject: Re: Amazing :-) 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, 10 Mar 1998, Alok K. Dhir wrote: > I just enabled softupdates on all filesystems except root on my SMP > -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB RAM). > The "make world" time just went from ~6 hours to 2 hours 20 mins. What's amazing, is that it should be faster, much faster. You should get about 90 to 100 minutes for a PPro200 with fast disks and lots of RAM. And that is before Softupdates. I suspect that you hard drive(s) are extremely slow. Softupdates just speed that up. > Al Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 20:24:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11212 for freebsd-current-outgoing; Tue, 10 Mar 1998 20:24:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11205 for ; Tue, 10 Mar 1998 20:24:12 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id VAA24708; Tue, 10 Mar 1998 21:23:59 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id VAA18105; Tue, 10 Mar 1998 21:23:57 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199803110423.VAA18105@panzer.plutotech.com> Subject: Re: Panic with the new slice stuff In-Reply-To: <9803110253.AA11488@cabri.obs-besancon.fr> from Jean-Marc Zucconi at "Mar 11, 98 03:53:38 am" To: jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi) Date: Tue, 10 Mar 1998 21:23:56 -0700 (MST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jean-Marc Zucconi wrote... > I wanted to know if my boot disk is dedicated ot not :-) > > I got: 'error 6: panic: cannot mount root (2)', just after the message: > changing root device to sd0s5a > > What can I do? I had the same problem on a dedicated disk, and version 1.22 of vfs_conf.c (Mike Smith just checked it in today) fixed it for me. 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 Tue Mar 10 20:26:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11696 for freebsd-current-outgoing; Tue, 10 Mar 1998 20:26:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11691 for ; Tue, 10 Mar 1998 20:26:41 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA25533; Wed, 11 Mar 1998 15:24:23 +1100 Date: Wed, 11 Mar 1998 15:24:23 +1100 From: Bruce Evans Message-Id: <199803110424.PAA25533@godzilla.zeta.org.au> To: current@FreeBSD.ORG, jmz@cabri.obs-besancon.fr Subject: Re: Panic with the new slice stuff Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I wanted to know if my boot disk is dedicated ot not :-) > >I got: 'error 6: panic: cannot mount root (2)', just after the message: >changing root device to sd0s5a This is normal for fully dedicated disks :-). >What can I do? It should be fixed in the current vfs_conf.c, except for the bogus device name in the "changing" message. This is not easy to fix, since it is not known until later that slice == 5 (sd0s4, not sd0s5) passed by the boot blocks really means slice == 0, (sd0, not sd0s-1). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 21:01:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14478 for freebsd-current-outgoing; Tue, 10 Mar 1998 21:01:28 -0800 (PST) (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 VAA14471 for ; Tue, 10 Mar 1998 21:01:26 -0800 (PST) (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 UAA21625; Tue, 10 Mar 1998 20:59:45 -0800 (PST) Message-Id: <199803110459.UAA21625@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bruce Evans cc: current@FreeBSD.ORG, jmz@cabri.obs-besancon.fr Subject: Re: Panic with the new slice stuff In-reply-to: Your message of "Wed, 11 Mar 1998 15:24:23 +1100." <199803110424.PAA25533@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Mar 1998 20:59:43 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It should be fixed in the current vfs_conf.c, except for the bogus device > name in the "changing" message. This is not easy to fix, since it is > not known until later that slice == 5 (sd0s4, not sd0s5) passed by the > boot blocks really means slice == 0, (sd0, not sd0s-1). Yeah. Any suggestions on this would be gratefully appreciated. I'm leaning towards masking the slice number in the device comparison when it decides whether to emit the message. Test results today showed up a number of interesting things: - disklabel -rwB ... auto on a virgin disk will not set the disk type correctly. This confuses the bootstrap if the disk in question is a SCSI disk, as it defaults to IDE, causing the root mount to fail. - if you supply 'sd' instead of 'wd' at the prompt, the bootstrap will ignore you and go with what it gets from the disklabel. (bootstrap from -stable in both cases) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 21:15:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16908 for freebsd-current-outgoing; Tue, 10 Mar 1998 21:15:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c243.moon.jic.com [206.156.18.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16901 for ; Tue, 10 Mar 1998 21:15:55 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id AAA14684; Wed, 11 Mar 1998 00:15:44 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: "Alok K. Dhir" cc: current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Amazing :-) In-reply-to: Your message of "Tue, 10 Mar 1998 22:19:49 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Mar 1998 00:15:44 -0500 Message-ID: <14680.889593344@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Alok K. Dhir" wrote in message ID : > > I just enabled softupdates on all filesystems except root on my SMP > -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB RAM). > The "make world" time just went from ~6 hours to 2 hours 20 mins. Are you sure thats not a 486 DX2 66 in disguise? A dual 300 MHz PII should do a make world (even with no filesystem optimization options enabled) in under 2 hours EASILY (unless your /usr/obj is a magneto- optical drive). 6 hours is about the par for a 486, from what I remember of the good old days of my doing test builds of pre-2.0 on thud.cdrom.com :) Gary ( who is more than slightly glad that we now have computers more powerful than thud to play with :-) ) -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 21:22:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17698 for freebsd-current-outgoing; Tue, 10 Mar 1998 21:22:25 -0800 (PST) (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 VAA17691 for ; Tue, 10 Mar 1998 21:22:21 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id VAA04099; Tue, 10 Mar 1998 21:22:13 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803110522.VAA04099@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Alok K. Dhir" cc: current@FreeBSD.ORG, Daniel Ingber Subject: Re: Amazing :-) In-reply-to: Your message of "Tue, 10 Mar 1998 22:19:49 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Mar 1998 21:22:13 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you can post the output of your dmesg . Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 21:22:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17724 for freebsd-current-outgoing; Tue, 10 Mar 1998 21:22:29 -0800 (PST) (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 VAA17689 for ; Tue, 10 Mar 1998 21:22:21 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id AAA17139; Wed, 11 Mar 1998 00:21:49 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 11 Mar 1998 00:21:48 -0500 (EST) From: "Alok K. Dhir" To: julian@whistle.com cc: current@FreeBSD.ORG Subject: Re: Amazing :-) 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, 10 Mar 1998 julian@whistle.com wrote: > you must have /usr/obj, /var/tmp and /usr/src all on the same physical > disk?? Yes, I do. /var/tmp, however is part of the root filesystem and does not currently have softupdates enabled (primarily because its a pain to get to a state where my / is unmounted...). Thanks for the terrific work. Al (I realize its not prime time yet, but mine is a development box, so its OK to play with non-production code). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 21:40:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19718 for freebsd-current-outgoing; Tue, 10 Mar 1998 21:40:38 -0800 (PST) (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 VAA19674 for ; Tue, 10 Mar 1998 21:40:08 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id AAA17177; Wed, 11 Mar 1998 00:38:45 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 11 Mar 1998 00:38:44 -0500 (EST) From: "Alok K. Dhir" To: tom@uniserve.com cc: current@FreeBSD.ORG, Daniel Ingber Subject: Re: Amazing :-) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-361759001-889594724=:17172" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-361759001-889594724=:17172 Content-Type: TEXT/PLAIN; charset=US-ASCII My six hour figure was completely off the wall, and could easily have been 4 hours. Probably not much less than that, though. The disks are ultrawide, 7200RPM Western Digitals. Far from slow. I don't know why the system isn't faster according to what you (and others) are saying. I've attached my kernel config. Any ideas? On Tue, 10 Mar 1998 tom@uniserve.com wrote: > > > > On Tue, 10 Mar 1998, Alok K. Dhir wrote: > > > I just enabled softupdates on all filesystems except root on my SMP > > -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB > RAM). > > The "make world" time just went from ~6 hours to 2 hours 20 mins. > > What's amazing, is that it should be faster, much faster. You should > get about 90 to 100 minutes for a PPro200 with fast disks and lots of RAM. > And that is before Softupdates. > > I suspect that you hard drive(s) are extremely slow. Softupdates just > speed that up. > > > Al > > Tom > > > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ R7-003, ITSMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." --0-361759001-889594724=:17172 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=SHADOW-SMP Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Iw0KIyBMSU5UIC0tIGNvbmZpZyBmaWxlIGZvciBjaGVja2luZyBhbGwgdGhl IHNvdXJjZXMsIHRyaWVzIHRvIHB1bGwgaW4NCiMJYXMgbXVjaCBvZiB0aGUg c291cmNlIHRyZWUgYXMgaXQgY2FuLg0KIw0KIwkkSWQ6IExJTlQsdiAxLjM5 NiAxOTk4LzAxLzI2IDA2OjMzOjQ4IGp1bGlhbiBFeHAgJA0KIw0KIyBOQjog WW91IHByb2JhYmx5IGRvbid0IHdhbnQgdG8gdHJ5IHJ1bm5pbmcgYSBrZXJu ZWwgYnVpbHQgZnJvbSB0aGlzDQojIGZpbGUuICBJbnN0ZWFkLCB5b3Ugc2hv dWxkIHN0YXJ0IGZyb20gR0VORVJJQywgYW5kIGFkZCBvcHRpb25zIGZyb20N CiMgdGhpcyBmaWxlIGFzIHJlcXVpcmVkLg0KIw0KDQojDQojIFRoaXMgZGly ZWN0aXZlIGlzIG1hbmRhdG9yeTsgaXQgZGVmaW5lcyB0aGUgYXJjaGl0ZWN0 dXJlIHRvIGJlDQojIGNvbmZpZ3VyZWQgZm9yOyBpbiB0aGlzIGNhc2UsIHRo ZSAzODYgZmFtaWx5IGJhc2VkIElCTS1QQyBhbmQNCiMgY29tcGF0aWJsZXMu DQojDQptYWNoaW5lCQkiaTM4NiINCg0KIyANCiMgVGhpcyBpcyB0aGUgYGBp ZGVudGlmaWNhdGlvbicnIG9mIHRoZSBrZXJuZWwuICBVc3VhbGx5IHRoaXMg c2hvdWxkDQojIGJlIHRoZSBzYW1lIGFzIHRoZSBuYW1lIG9mIHlvdXIga2Vy bmVsLg0KIw0KaWRlbnQJCVNIQURPVw0KDQojDQojIFRoZSBgbWF4dXNlcnMn IHBhcmFtZXRlciBjb250cm9scyB0aGUgc3RhdGljIHNpemluZyBvZiBhIG51 bWJlciBvZg0KIyBpbnRlcm5hbCBzeXN0ZW0gdGFibGVzIGJ5IGEgY29tcGxp Y2F0ZWQgZm9ybXVsYSBkZWZpbmVkIGluIHBhcmFtLmMuDQojDQptYXh1c2Vy cwk2NA0KDQojDQojIENlcnRhaW4gYXBwbGljYXRpb25zIGNhbiBncm93IHRv IGJlIGxhcmdlciB0aGFuIHRoZSAxMjhNIGxpbWl0DQojIHRoYXQgRnJlZUJT RCBpbml0aWFsbHkgaW1wb3Nlcy4gIEJlbG93IGFyZSBzb21lIG9wdGlvbnMg dG8NCiMgYWxsb3cgdGhhdCBsaW1pdCB0byBncm93IHRvIDI1Nk1CLCBhbmQg Y2FuIGJlIGluY3JlYXNlZCBmdXJ0aGVyDQojIHdpdGggY2hhbmdpbmcgdGhl IHBhcmFtZXRlcnMuICBNQVhEU0laIGlzIHRoZSBtYXhpbXVtIHRoYXQgdGhl DQojIGxpbWl0IGNhbiBiZSBzZXQgdG8sIGFuZCB0aGUgREZMRFNJWiBpcyB0 aGUgZGVmYXVsdCB2YWx1ZSBmb3INCiMgdGhlIGxpbWl0LiAgWW91IG1pZ2h0 IHdhbnQgdG8gc2V0IHRoZSBkZWZhdWx0IGxvd2VyIHRoYW4gdGhlDQojIG1h eCwgYW5kIGV4cGxpY2l0bHkgc2V0IHRoZSBtYXhpbXVtIHdpdGggYSBzaGVs bCBjb21tYW5kIGZvciBwcm9jZXNzZXMNCiMgdGhhdCByZWd1bGFybHkgZXhj ZWVkIHRoZSBsaW1pdCBsaWtlIElOTkQuDQojDQpvcHRpb25zCQkiTUFYRFNJ Wj0oMjU2KjEwMjQqMTAyNCkiDQpvcHRpb25zCQkiREZMRFNJWj0oMjU2KjEw MjQqMTAyNCkiDQoNCiMgV2hlbiB0aGlzIGlzIHNldCwgYmUgZXh0cmEgY29u c2VydmF0aXZlIGluIHZhcmlvdXMgcGFydHMgb2YgdGhlIGtlcm5lbA0KIyBh bmQgY2hvb3NlIGZ1bmN0aW9uYWxpdHkgb3ZlciBzcGVlZCAob24gdGhlIHdp ZGVzdCB2YXJpZXR5IG9mIHN5c3RlbXMpLg0KI29wdGlvbnMJCUZBSUxTQUZF DQoNCiMgVGhpcyBhbGxvd3MgeW91IHRvIGFjdHVhbGx5IHN0b3JlIHRoaXMg Y29uZmlndXJhdGlvbiBmaWxlIGludG8NCiMgdGhlIGtlcm5lbCBiaW5hcnkg aXRzZWxmLCB3aGVyZSBpdCBtYXkgYmUgbGF0ZXIgcmVhZCBieSBzYXlpbmc6 DQojICAgIHN0cmluZ3MgL2tlcm5lbCB8IGdyZXAgXl9fXyB8IHNlZCAtZSAn cy9eX19fLy8nID4gTVlLRVJORUwNCiMNCm9wdGlvbnMgICAgICAgICBJTkNM VURFX0NPTkZJR19GSUxFICAgICAjIEluY2x1ZGUgdGhpcyBmaWxlIGluIGtl cm5lbA0KDQojDQojIFRoaXMgZGlyZWN0aXZlIGRlZmluZXMgYSBudW1iZXIg b2YgdGhpbmdzOg0KIyAgLSBUaGUgY29tcGlsZWQga2VybmVsIGlzIHRvIGJl IGNhbGxlZCBga2VybmVsJw0KIyAgLSBUaGUgcm9vdCBmaWxlc3lzdGVtIG1p Z2h0IGJlIG9uIHBhcnRpdGlvbiB3ZDBhDQojICAtIENyYXNoIGR1bXBzIHdp bGwgYmUgd3JpdHRlbiB0byB3ZDBiLCBpZiBwb3NzaWJsZS4gIFNwZWNpZnlp bmcgdGhlDQojICAgIGR1bXAgZGV2aWNlIGhlcmUgaXMgbm90IHJlY29tbWVu ZGVkLiAgVXNlIGR1bXBvbig4KS4NCiMNCmNvbmZpZwkJa2VybmVsCXJvb3Qg b24gc2QwIA0KDQoNCiMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIw0KIyBTTVAg T1BUSU9OUzoNCiMNCiMgU01QIGVuYWJsZXMgYnVpbGRpbmcgb2YgYSBTeW1t ZXRyaWMgTXVsdGlQcm9jZXNzb3IgS2VybmVsLg0KIyBBUElDX0lPIGVuYWJs ZXMgdGhlIHVzZSBvZiB0aGUgSU8gQVBJQyBmb3IgU3ltbWV0cmljIEkvTy4N CiMgTkNQVSBzZXRzIHRoZSBudW1iZXIgb2YgQ1BVcywgZGVmYXVsdHMgdG8g Mi4NCiMgTkJVUyBzZXRzIHRoZSBudW1iZXIgb2YgYnVzc2VzLCBkZWZhdWx0 cyB0byA0Lg0KIyBOQVBJQyBzZXRzIHRoZSBudW1iZXIgb2YgSU8gQVBJQ3Mg b24gdGhlIG1vdGhlcmJvYXJkLCBkZWZhdWx0cyB0byAxLg0KIyBOSU5UUiBz ZXRzIHRoZSB0b3RhbCBudW1iZXIgb2YgSU5UcyBwcm92aWRlZCBieSB0aGUg bW90aGVyYm9hcmQuDQojDQojIE5vdGVzOg0KIw0KIyAgQW4gU01QIGtlcm5l bCB3aWxsIE9OTFkgcnVuIG9uIGFuIEludGVsIE1QIHNwZWMuIHF1YWxpZmll ZCBtb3RoZXJib2FyZC4NCiMNCiMgIEJlIHN1cmUgdG8gZGlzYWJsZSAnY3B1 ICJJMzg2X0NQVSInICYmICdjcHUgIkk0ODZfQ1BVIicgZm9yIFNNUCBrZXJu ZWxzLg0KIw0KIyAgQ2hlY2sgdGhlICdSb2d1ZSBTTVAgaGFyZHdhcmUnIHNl Y3Rpb24gdG8gc2VlIGlmIGFkZGl0aW9uYWwgb3B0aW9ucw0KIyAgIGFyZSBy ZXF1aXJlZCBieSB5b3VyIGhhcmR3YXJlLg0KIw0KDQojIE1hbmRhdG9yeToN Cm9wdGlvbnMJCVNNUAkJCSMgU3ltbWV0cmljIE11bHRpUHJvY2Vzc29yIEtl cm5lbA0Kb3B0aW9ucwkJQVBJQ19JTwkJCSMgU3ltbWV0cmljIChBUElDKSBJ L08NCg0KDQojIE9wdGlvbmFsIChidWlsdC1pbiBkZWZhdWx0cyB3aWxsIHdv cmsgaW4gbW9zdCBjYXNlcyk6DQpvcHRpb25zICAgICAgICAgICAgICAgIE5D UFU9MiAgICAgICAgICAgICAgICAgICMgbnVtYmVyIG9mIENQVXMNCm9wdGlv bnMgICAgICAgICAgICAgICAgTkJVUz0zICAgICAgICAgICAgICAgICAgIyBu dW1iZXIgb2YgYnVzc2VzDQpvcHRpb25zICAgICAgICAgICAgICAgIE5BUElD PTEgICAgICAgICAgICAgICAgICMgbnVtYmVyIG9mIElPIEFQSUNzDQpvcHRp b25zICAgICAgICAgICAgICAgIE5JTlRSPTM3ICAgICAgICAgICAgICAgICMg bnVtYmVyIG9mIElOVHMNCg0KIw0KIyBSb2d1ZSBTTVAgaGFyZHdhcmU6DQoj DQoNCiMgQnJpZGdlZCBQQ0kgY2FyZHM6DQojDQojIFRoZSBNUCB0YWJsZXMg b2YgbW9zdCBvZiB0aGUgY3VycmVudCBnZW5lcmF0aW9uIE1QIG1vdGhlcmJv YXJkcw0KIyAgZG8gTk9UIHByb3Blcmx5IHN1cHBvcnQgYnJpZGdlZCBQQ0kg Y2FyZHMuICBUbyB1c2Ugb25lIG9mIHRoZXNlDQojICBjYXJkcyB5b3Ugc2hv dWxkIHJlZmVyIHRvID8/Pw0KDQoNCiMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj Iw0KIyBDUFUgT1BUSU9OUw0KDQojDQojIFlvdSBtdXN0IHNwZWNpZnkgYXQg bGVhc3Qgb25lIENQVSAodGhlIG9uZSB5b3UgaW50ZW5kIHRvIHJ1biBvbik7 DQojIGRlbGV0aW5nIHRoZSBzcGVjaWZpY2F0aW9uIGZvciBDUFVzIHlvdSBk b24ndCBuZWVkIHRvIHVzZSBtYXkgbWFrZQ0KIyBwYXJ0cyBvZiB0aGUgc3lz dGVtIHJ1biBmYXN0ZXIuICBUaGlzIGlzIGVzcGVjaWFsbHkgdHJ1ZSByZW1v dmluZw0KIyBJMzg2X0NQVS4NCiMNCiNjcHUJCSJJMzg2X0NQVSINCiNjcHUJ CSJJNDg2X0NQVSINCmNwdQkJIkk1ODZfQ1BVIgkJIyBha2EgUGVudGl1bSh0 bSkNCmNwdQkJIkk2ODZfQ1BVIgkJIyBha2EgUGVudGl1bSBQcm8odG0pDQoN CiMNCiMNCiMgTk9fRjAwRl9IQUNLIGRpc2FibGVzIHRoZSBoYWNrIHRoYXQg cHJldmVudHMgUGVudGl1bXMgKGFuZCBPTkxZDQojIFBlbnRpdW1zKSBmcm9t IGxvY2tpbmcgdXAgd2hlbiBhIExPQ0sgQ01QWENIRzhCIGluc3RydWN0aW9u IGlzDQojIGV4ZWN1dGVkLiAgVGhpcyBzaG91bGQgYmUgaW5jbHVkZWQgZm9y IEFMTCBrZXJuZWxzIHRoYXQgd29uJ3QgcnVuDQojIG9uIGEgUGVudGl1bS4N Cg0Kb3B0aW9ucwkiTk9fRjAwRl9IQUNLIg0KDQojDQojIEEgbWF0aCBlbXVs YXRvciBpcyBtYW5kYXRvcnkgaWYgeW91IHdpc2ggdG8gcnVuIG9uIGhhcmR3 YXJlIHdoaWNoDQojIGRvZXMgbm90IGhhdmUgYSBmbG9hdGluZy1wb2ludCBw cm9jZXNzb3IuICBQaWNrIGVpdGhlciB0aGUgb3JpZ2luYWwsDQojIGJvZ3Vz IChidXQgZnJlZWx5LWRpc3RyaWJ1dGFibGUpIG1hdGggZW11bGF0b3IsIG9y IGEgbXVjaCBtb3JlDQojIGZ1bGx5LWZlYXR1cmVkIGJ1dCBHUEwtbGljZW5z ZWQgZW11bGF0b3IgdGFrZW4gZnJvbSBMaW51eC4NCiMNCiNvcHRpb25zCQlN QVRIX0VNVUxBVEUJCSNTdXBwb3J0IGZvciB4ODcgZW11bGF0aW9uDQojIERv bid0IGVuYWJsZSBib3RoIG9mIHRoZXNlIGluIGEgcmVhbCBjb25maWcuDQoj b3B0aW9ucwkJR1BMX01BVEhfRU1VTEFURQkjU3VwcG9ydCBmb3IgeDg3IGVt dWxhdGlvbiB2aWENCgkJCQkJI25ldyBtYXRoIGVtdWxhdG9yIA0KDQoNCiMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIw0KIyBDT01QQVRJQklMSVRZIE9QVElP TlMgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICANCg0KIw0KIyBJbXBsZW1lbnQgc3lzdGVtIGNhbGxzIGNvbXBhdGlibGUg d2l0aCA0LjNCU0QgYW5kIG9sZGVyIHZlcnNpb25zIG9mDQojIEZyZWVCU0Qu ICBZb3UgcHJvYmFibHkgZG8gTk9UIHdhbnQgdG8gcmVtb3ZlIHRoaXMgYXMg bXVjaCBjdXJyZW50IGNvZGUNCiMgc3RpbGwgcmVsaWVzIG9uIHRoZSA0LjMg ZW11bGF0aW9uLg0KIw0Kb3B0aW9ucwkJIkNPTVBBVF80MyINCg0KIw0KIyBB bGxvdyB1c2VyLW1vZGUgcHJvZ3JhbXMgdG8gbWFuaXB1bGF0ZSB0aGVpciBs b2NhbCBkZXNjcmlwdG9yIHRhYmxlcy4NCiMgVGhpcyBvcHRpb24gaXMgcmVx dWlyZWQgZm9yIHRoZSBXSU5FIFdpbmRvd3ModG0pIGVtdWxhdG9yLCBhbmQg aXMNCiMgbm90IHVzZWQgYnkgYW55dGhpbmcgZWxzZSAodGhhdCB3ZSBrbm93 IG9mKS4NCiMNCm9wdGlvbnMJCVVTRVJfTERUCQkjYWxsb3cgdXNlci1sZXZl bCBjb250cm9sIG9mIGkzODYgbGR0DQoNCiMNCiMgVGhlc2UgdGhyZWUgb3B0 aW9ucyBwcm92aWRlIHN1cHBvcnQgZm9yIFN5c3RlbSBWIEludGVyZmFjZQ0K IyBEZWZpbml0aW9uLXN0eWxlIGludGVycHJvY2VzcyBjb21tdW5pY2F0aW9u LCBpbiB0aGUgZm9ybSBvZiBzaGFyZWQNCiMgbWVtb3J5LCBzZW1hcGhvcmVz LCBhbmQgbWVzc2FnZSBxdWV1ZXMsIHJlc3BlY3RpdmVseS4NCiMNCm9wdGlv bnMJCVNZU1ZTSE0NCm9wdGlvbnMJCVNZU1ZTRU0NCm9wdGlvbnMJCVNZU1ZN U0cNCg0KIw0KIyBUaGlzIG9wdGlvbiBpbmNsdWRlcyBhIE1ENSByb3V0aW5l IGluIHRoZSBrZXJuZWwsIHRoaXMgaXMgdXNlZCBmb3INCiMgdmFyaW91cyBh dXRoZW50aWNhdGlvbiBhbmQgcHJpdmFjeSB1c2VzLg0KIw0Kb3B0aW9ucwkJ Ik1ENSINCg0KIw0KIyBBbGxvdyBwcm9jZXNzZXMgdG8gc3dpdGNoIHRvIHZt ODYgbW9kZSwgYXMgd2VsbCBhcyBlbmFibGluZyBkaXJlY3QNCiMgdXNlci1t b2RlIGFjY2VzcyB0byB0aGUgSS9PIHBvcnQgc3BhY2UuICBUaGlzIG9wdGlv biBpcyBuZWNlc3NhcnkgZm9yIA0KIyB0aGUgZG9zY21kIGVtdWxhdG9yIHRv IHJ1bi4NCiMNCm9wdGlvbnMJCSJWTTg2Ig0KDQoNCiMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIw0KIyBERUJVR0dJTkcgT1BUSU9OUw0KDQojDQojIEVuYWJs ZSB0aGUga2VybmVsIGRlYnVnZ2VyLg0KIw0KI29wdGlvbnMJCUREQg0KDQoj DQojIERvbid0IGRyb3AgaW50byBEREIgZm9yIGEgcGFuaWMuIEludGVuZGVk IGZvciB1bmF0dGVuZGVkIG9wZXJhdGlvbg0KIyB3aGVyZSB5b3UgbWF5IHdh bnQgdG8gZHJvcCB0byBEREIgZnJvbSB0aGUgY29uc29sZSwgYnV0IHN0aWxs IHdhbnQNCiMgdGhlIG1hY2hpbmUgdG8gcmVjb3ZlciBmcm9tIGEgcGFuaWMN CiMNCiNvcHRpb25zCQlEREJfVU5BVFRFTkRFRA0KDQojDQojIElmIHVzaW5n IEdEQiByZW1vdGUgbW9kZSB0byBkZWJ1ZyB0aGUga2VybmVsLCB0aGVyZSdz IGEgbm9uLXN0YW5kYXJkDQojIGV4dGVuc2lvbiB0byB0aGUgcmVtb3RlIHBy b3RvY29sIHRoYXQgY2FuIGJlIHVzZWQgdG8gdXNlIHRoZSBzZXJpYWwNCiMg cG9ydCBhcyBib3RoIHRoZSBkZWJ1Z2dpbmcgcG9ydCBhbmQgdGhlIHN5c3Rl bSBjb25zb2xlLiAgSXQncyBub24tDQojIHN0YW5kYXJkIGFuZCB5b3UncmUg b24geW91ciBvd24gaWYgeW91IGVuYWJsZSBpdC4gIFNlZSBhbHNvIHRoZQ0K IyAicmVtb3RlY2hhdCIgdmFyaWFibGVzIGluIHRoZSBGcmVlQlNEIHNwZWNp ZmljIHZlcnNpb24gb2YgZ2RiLg0KIw0KI29wdGlvbnMJCUdEQl9SRU1PVEVf Q0hBVA0KDQojIA0KIyBLVFJBQ0UgZW5hYmxlcyB0aGUgc3lzdGVtLWNhbGwg dHJhY2luZyBmYWNpbGl0eSBrdHJhY2UoMikuDQojDQpvcHRpb25zCQlLVFJB Q0UJCQkja2VybmVsIHRyYWNpbmcNCg0KIw0KIyBUaGUgRElBR05PU1RJQyBv cHRpb24gaXMgdXNlZCBpbiBhIG51bWJlciBvZiBzb3VyY2UgZmlsZXMgdG8g ZW5hYmxlDQojIGV4dHJhIHNhbml0eSBjaGVja2luZyBvZiBpbnRlcm5hbCBz dHJ1Y3R1cmVzLiAgVGhpcyBzdXBwb3J0IGlzIG5vdA0KIyBlbmFibGVkIGJ5 IGRlZmF1bHQgYmVjYXVzZSBvZiB0aGUgZXh0cmEgdGltZSBpdCB3b3VsZCB0 YWtlIHRvIGNoZWNrDQojIGZvciB0aGVzZSBjb25kaXRpb25zLCB3aGljaCBj YW4gb25seSBvY2N1ciBhcyBhIHJlc3VsdCBvZg0KIyBwcm9ncmFtbWluZyBl cnJvcnMuDQojDQojb3B0aW9ucwkJRElBR05PU1RJQw0KDQojDQojIFBFUkZN T04gY2F1c2VzIHRoZSBkcml2ZXIgZm9yIFBlbnRpdW0vUGVudGl1bSBQcm8g cGVyZm9ybWFuY2UgY291bnRlcnMNCiMgdG8gYmUgY29tcGlsZWQuICBTZWUg cGVyZm1vbig0KSBmb3IgbW9yZSBpbmZvcm1hdGlvbi4NCiMNCm9wdGlvbnMJ CVBFUkZNT04NCg0KIyBYWFggLSB0aGlzIGRvZXNuJ3QgYmVsb25nIGhlcmUu DQojIEFsbG93IG9yZGluYXJ5IHVzZXJzIHRvIHRha2UgdGhlIGNvbnNvbGUg LSB0aGlzIGlzIHVzZWZ1bCBmb3IgWC4NCm9wdGlvbnMJCVVDT05TT0xFDQoN CiMgWFhYIC0gdGhpcyBkb2Vzbid0IGJlbG9uZyBoZXJlIGVpdGhlcg0Kb3B0 aW9ucwkJVVNFUkNPTkZJRwkJI2Jvb3QgLWMgZWRpdG9yDQojb3B0aW9ucwkJ VVNFUkNPTkZJR19CT09UCQkjaW1wbHkgLWMgYW5kIHBhcnNlIGluZm8gYXJl YQ0Kb3B0aW9ucwkJVklTVUFMX1VTRVJDT05GSUcJI3Zpc3VhbCBib290IC1j IGVkaXRvcg0KDQojIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMNCiMgTkVUV09S S0lORyBPUFRJT05TDQoNCiMNCiMgUHJvdG9jb2wgZmFtaWxpZXM6DQojICBP bmx5IHRoZSBJTkVUIChJbnRlcm5ldCkgZmFtaWx5IGlzIG9mZmljaWFsbHkg c3VwcG9ydGVkIGluIEZyZWVCU0QuDQojICBTb3VyY2UgY29kZSBmb3IgdGhl IE5TIChYZXJveCBOZXR3b3JrIFNlcnZpY2UpIGlzIHByb3ZpZGVkIGZvciBh bXVzZW1lbnQNCiMgIHZhbHVlLg0KIw0Kb3B0aW9ucwkJSU5FVAkJCSNJbnRl cm5ldCBjb21tdW5pY2F0aW9ucyBwcm90b2NvbHMNCg0Kb3B0aW9ucwkJSVBY CQkJI0lQWC9TUFggY29tbXVuaWNhdGlvbnMgcHJvdG9jb2xzDQojb3B0aW9u cwkJSVBYSVAJCQkjSVBYIGluIElQIGVuY2Fwc3VsYXRpb24gKG5vdCBhdmFp bGFibGUpDQojb3B0aW9ucwkJSVBUVU5ORUwJCSNJUCBpbiBJUFggZW5jYXBz dWxhdGlvbiAobm90IGF2YWlsYWJsZSkNCg0KI29wdGlvbnMJCU5FVEFUQUxL CQkjQXBwbGV0YWxrIGNvbW11bmljYXRpb25zIHByb3RvY29scw0KDQoNCiMg TmV0d29yayBpbnRlcmZhY2VzOg0KIyAgVGhlIGBsb29wJyBwc2V1ZG8tZGV2 aWNlIGlzIE1BTkRBVE9SWSB3aGVuIG5ldHdvcmtpbmcgaXMgZW5hYmxlZC4N CiMgIFRoZSBgZXRoZXInIHBzZXVkby1kZXZpY2UgcHJvdmlkZXMgZ2VuZXJp YyBjb2RlIHRvIGhhbmRsZQ0KIyAgRXRoZXJuZXRzOyBpdCBpcyBNQU5EQVRP Ulkgd2hlbiBhIEV0aGVybmV0IGRldmljZSBkcml2ZXIgaXMNCiMgIGNvbmZp Z3VyZWQuDQojICBUaGUgJ2ZkZGknIHBzZXVkby1kZXZpY2UgcHJvdmlkZXMg Z2VuZXJpYyBjb2RlIHRvIHN1cHBvcnQgRkRESS4NCiMgIFRoZSBgc3BwcCcg cHNldWRvLWRldmljZSBzZXJ2ZXMgYSBzaW1pbGFyIHJvbGUgZm9yIGNlcnRh aW4gdHlwZXMNCiMgIG9mIHN5bmNocm9ub3VzIFBQUCBsaW5rcyAobGlrZSBg Y3gnLCBgYXInKS4NCiMgIFRoZSBgc2wnIHBzZXVkby1kZXZpY2UgaW1wbGVt ZW50cyB0aGUgU2VyaWFsIExpbmUgSVAgKFNMSVApIHNlcnZpY2UuDQojICBU aGUgYHBwcCcgcHNldWRvLWRldmljZSBpbXBsZW1lbnRzIHRoZSBQb2ludC10 by1Qb2ludCBQcm90b2NvbC4NCiMgIFRoZSBgYnBmaWx0ZXInIHBzZXVkby1k ZXZpY2UgZW5hYmxlcyB0aGUgQmVya2VsZXkgUGFja2V0IEZpbHRlci4gIEJl DQojICBhd2FyZSBvZiB0aGUgbGVnYWwgYW5kIGFkbWluaXN0cmF0aXZlIGNv bnNlcXVlbmNlcyBvZiBlbmFibGluZyB0aGlzDQojICBvcHRpb24uICBUaGUg bnVtYmVyIG9mIGRldmljZXMgZGV0ZXJtaW5lcyB0aGUgbWF4aW11bSBudW1i ZXIgb2YNCiMgIHNpbXVsdGFuZW91cyBCUEYgY2xpZW50cyBwcm9ncmFtcyBy dW5uYWJsZS4NCiMgIFRoZSBgZGlzYycgcHNldWRvLWRldmljZSBpbXBsZW1l bnRzIGEgbWluaW1hbCBuZXR3b3JrIGludGVyZmFjZSwNCiMgIHdoaWNoIHRo cm93cyBhd2F5IGFsbCBwYWNrZXRzIHNlbnQgYW5kIG5ldmVyIHJlY2VpdmVz IGFueS4gIEl0IGlzDQojICBpbmNsdWRlZCBmb3IgdGVzdGluZyBwdXJwb3Nl cy4NCiMgIFRoZSBgdHVuJyBwc2V1ZG8tZGV2aWNlIGltcGxlbWVudHMgdGhl IFVzZXIgUHJvY2VzcyBQUFAgKGlpanBwcCkNCiMNCiMgVGhlIFBQUF9CU0RD T01QIG9wdGlvbiBlbmFibGVzIHN1cHBvcnQgZm9yIGNvbXByZXNzKDEpIHN0 eWxlIGVudGlyZQ0KIyBwYWNrZXQgY29tcHJlc3Npb24sIHRoZSBQUFBfREVG TEFURSBpcyBmb3IgemxpYi9nemlwIHN0eWxlIGNvbXByZXNzaW9uLg0KIyBQ UFBfRklMVEVSIGVuYWJsZXMgY29kZSBmb3IgZmlsdGVyaW5nIHRoZSBwcHAg ZGF0YSBzdHJlYW0gYW5kIHNlbGVjdGluZw0KIyBldmVudHMgZm9yIHJlc2V0 dGluZyB0aGUgZGVtYW5kIGRpYWwgYWN0aXZpdHkgdGltZXIgLSByZXF1aXJl cyBicGZpbHRlci4NCiMgU2VlIHBwcGQoOCkgZm9yIG1vcmUgZGV0YWlscy4N CiMNCnBzZXVkby1kZXZpY2UJZXRoZXIJCQkjR2VuZXJpYyBFdGhlcm5ldA0K I3BzZXVkby1kZXZpY2UJZmRkaQkJCSNHZW5lcmljIEZEREkNCnBzZXVkby1k ZXZpY2UJc3BwcAkJCSNHZW5lcmljIFN5bmNocm9ub3VzIFBQUA0KcHNldWRv LWRldmljZQlsb29wCQkJI05ldHdvcmsgbG9vcGJhY2sgZGV2aWNlDQpwc2V1 ZG8tZGV2aWNlCWJwZmlsdGVyCTQJI0JlcmtlbGV5IHBhY2tldCBmaWx0ZXIN CnBzZXVkby1kZXZpY2UJZGlzYwkJCSNEaXNjYXJkIGRldmljZQ0KI3BzZXVk by1kZXZpY2UJdHVuCTEJCSNUdW5uZWwgZHJpdmVyICh1c2VyIHByb2Nlc3Mg cHBwKDgpKQ0KcHNldWRvLWRldmljZQlzbAkyCQkjU2VyaWFsIExpbmUgSVAN CnBzZXVkby1kZXZpY2UJcHBwCTIJCSNQb2ludC10by1wb2ludCBwcm90b2Nv bA0Kb3B0aW9ucyBQUFBfQlNEQ09NUAkJCSNQUFAgQlNELWNvbXByZXNzIHN1 cHBvcnQNCm9wdGlvbnMgUFBQX0RFRkxBVEUJCQkjUFBQIHpsaWIvZGVmbGF0 ZS9nemlwIHN1cHBvcnQNCm9wdGlvbnMgUFBQX0ZJTFRFUgkJCSNlbmFibGUg YnBmIGZpbHRlcmluZyAobmVlZHMgYnBmaWx0ZXIpDQoNCiMNCiMgSW50ZXJu ZXQgZmFtaWx5IG9wdGlvbnM6DQojDQojIFRDUF9DT01QQVRfNDIgY2F1c2Vz IHRoZSBUQ1AgY29kZSB0byBlbXVsYXRlIGNlcnRhaW4gYnVncyBwcmVzZW50 IGluDQojIDQuMkJTRC4gIFRoaXMgb3B0aW9uIHNob3VsZCBub3QgYmUgdXNl ZCB1bmxlc3MgeW91IGhhdmUgYSA0LjJCU0QNCiMgbWFjaGluZSBhbmQgVENQ IGNvbm5lY3Rpb25zIGZhaWwuDQojDQojIE1ST1VUSU5HIGVuYWJsZXMgdGhl IGtlcm5lbCBtdWx0aWNhc3QgcGFja2V0IGZvcndhcmRlciwgd2hpY2ggd29y a3MNCiMgd2l0aCBtcm91dGVkKDgpLg0KIw0KIyBJUEZJUkVXQUxMIGVuYWJs ZXMgc3VwcG9ydCBmb3IgSVAgZmlyZXdhbGwgY29uc3RydWN0aW9uLCBpbg0K IyBjb25qdW5jdGlvbiB3aXRoIHRoZSBgaXBmdycgcHJvZ3JhbS4gIElQRklS RVdBTExfVkVSQk9TRSBzZW5kcw0KIyBsb2dnZWQgcGFja2V0cyB0byB0aGUg c3lzdGVtIGxvZ2dlci4gIElQRklSRVdBTExfVkVSQk9TRV9MSU1JVA0KIyBs aW1pdHMgdGhlIG51bWJlciBvZiB0aW1lcyBhIG1hdGNoaW5nIGVudHJ5IGNh biBiZSBsb2dnZWQuDQojDQojIFdBUk5JTkc6ICBJUEZJUkVXQUxMIGRlZmF1 bHRzIHRvIGEgcG9saWN5IG9mICJkZW55IGlwIGZyb20gYW55IHRvIGFueSIN CiMgYW5kIGlmIHlvdSBkbyBub3QgYWRkIG90aGVyIHJ1bGVzIGR1cmluZyBz dGFydHVwIHRvIGFsbG93IGFjY2VzcywNCiMgWU9VIFdJTEwgTE9DSyBZT1VS U0VMRiBPVVQuICBJdCBpcyBzdWdnZXN0ZWQgdGhhdCB5b3Ugc2V0IGZpcmV3 YWxsPW9wZW4NCiMgaW4gL2V0Yy9yYy5jb25mIHdoZW4gZmlyc3QgZW5hYmxp bmcgdGhpcyBmZWF0dXJlLCB0aGVuIHJlZmluaW5nIHRoZQ0KIyBmaXJld2Fs bCBydWxlcyBpbiAvZXRjL3JjLmZpcmV3YWxsIGFmdGVyIHlvdSd2ZSB0ZXN0 ZWQgdGhhdCB0aGUgbmV3IGtlcm5lbA0KIyBmZWF0dXJlIHdvcmtzIHByb3Bl cmx5Lg0KIw0KIyBJUEZJUkVXQUxMX0RFRkFVTFRfVE9fQUNDRVBUIGNhdXNl cyB0aGUgZGVmYXVsdCBydWxlIChhdCBib290KSB0bw0KIyBhbGxvdyBldmVy eXRoaW5nLiAgVXNlIHdpdGggY2FyZSwgaWYgYSBjcmFja2VyIGNhbiBjcmFz aCB5b3VyDQojIGZpcmV3YWxsIG1hY2hpbmUsIHRoZXkgY2FuIGdldCB0byB5 b3VyIHByb3RlY3RlZCBtYWNoaW5lcy4gIEhvd2V2ZXIsDQojIGlmIHlvdSBh cmUgdXNpbmcgaXQgYXMgYW4gYXMtbmVlZGVkIGZpbHRlciBmb3Igc3BlY2lm aWMgcHJvYmxlbXMgYXMNCiMgdGhleSBhcmlzZSwgdGhlbiB0aGlzIG1heSBi ZSBmb3IgeW91LiAgQ2hhbmdpbmcgdGhlIGRlZmF1bHQgdG8gJ2FsbG93Jw0K IyBtZWFucyB0aGF0IHlvdSB3b24ndCBnZXQgc3R1Y2sgaWYgdGhlIGtlcm5l bCBhbmQgL3NiaW4vaXBmdyBiaW5hcnkgZ2V0DQojIG91dCBvZiBzeW5jLg0K Iw0KIyBJUERJVkVSVCBlbmFibGVzIHRoZSBkaXZlcnQgSVAgc29ja2V0cywg dXNlZCBieSBgYGlwZncgZGl2ZXJ0JycNCiMNCiMgVENQREVCVUcgaXMgdW5k b2N1bWVudGVkLg0KIw0KI29wdGlvbnMJCSJUQ1BfQ09NUEFUXzQyIgkJI2Vt dWxhdGUgNC4yQlNEIFRDUCBidWdzDQojb3B0aW9ucwkJTVJPVVRJTkcJCSMg TXVsdGljYXN0IHJvdXRpbmcNCiNvcHRpb25zICAgICAgICAgSVBGSVJFV0FM TCAgICAgICAgICAgICAgI2ZpcmV3YWxsDQojb3B0aW9ucyAgICAgICAgIElQ RklSRVdBTExfVkVSQk9TRSAgICAgICNwcmludCBpbmZvcm1hdGlvbiBhYm91 dA0KCQkJCQkjIGRyb3BwZWQgcGFja2V0cw0KI29wdGlvbnMJCSJJUEZJUkVX QUxMX1ZFUkJPU0VfTElNSVQ9MTAwIiAjbGltaXQgdmVyYm9zaXR5DQojb3B0 aW9ucwkJSVBGSVJFV0FMTF9ERUZBVUxUX1RPX0FDQ0VQVCAjYWxsb3cgZXZl cnl0aGluZyBieSBkZWZhdWx0DQojb3B0aW9ucwkJSVBESVZFUlQJCSNkaXZl cnQgc29ja2V0cw0KI29wdGlvbnMJCVRDUERFQlVHDQoNCg0KIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjDQojIEZJTEVTWVNURU0gT1BUSU9OUw0KDQojDQoj IE9ubHkgdGhlIHJvb3QsIC91c3IsIGFuZCAvdG1wIGZpbGVzeXN0ZW1zIG5l ZWQgYmUgc3RhdGljYWxseQ0KIyBjb21waWxlZDsgZXZlcnl0aGluZyBlbHNl IHdpbGwgYmUgYXV0b21hdGljYWxseSBsb2FkZWQgYXQgbW91bnQNCiMgdGlt ZS4gIChFeGNlcHRpb246IHRoZSBVRlMgZmFtaWx5LS0tRkZTLCBNRlMsIGFu ZCBMRlMtLS1jYW5ub3QNCiMgY3VycmVudGx5IGJlIGRlbWFuZC1sb2FkZWQu KSAgU29tZSBwZW9wbGUgc3RpbGwgcHJlZmVyIHRvIHN0YXRpY2FsbHkNCiMg Y29tcGlsZSBvdGhlciBmaWxlc3lzdGVtcyBhcyB3ZWxsLg0KIw0KIyBOQjog VGhlIExGUywgUE9SVEFMLCBhbmQgVU5JT04gZmlsZXN5c3RlbXMgYXJlIGtu b3duIHRvIGJlIGJ1Z2d5LA0KIyBhbmQgV0lMTCBwYW5pYyB5b3VyIHN5c3Rl bSBpZiB5b3UgYXR0ZW1wdCB0byBkbyBhbnl0aGluZyB3aXRoIHRoZW0uDQoj IFRoZXkgYXJlIGluY2x1ZGVkIGhlcmUgYXMgYW4gaW5jZW50aXZlIGZvciBz b21lIGVudGVycHJpc2luZyBzb3VsIHRvDQojIHNpdCBkb3duIGFuZCBmaXgg dGhlbS4NCiMNCg0KIyBPbmUgb2YgdGhlc2UgaXMgbWFuZGF0b3J5Og0Kb3B0 aW9ucwkJRkZTCQkJI0Zhc3QgZmlsZXN5c3RlbQ0Kb3B0aW9ucwkJTkZTCQkJ I05ldHdvcmsgRmlsZSBTeXN0ZW0NCg0KIyBUaGUgcmVzdCBhcmUgb3B0aW9u YWw6DQojIG9wdGlvbnMJTkZTX05PU0VSVkVSCQkjRGlzYWJsZSB0aGUgTkZT LXNlcnZlciBjb2RlLg0Kb3B0aW9ucwkJIkNEOTY2MCIJCSNJU08gOTY2MCBm aWxlc3lzdGVtDQpvcHRpb25zCQlGREVTQwkJCSNGaWxlIGRlc2NyaXB0b3Ig ZmlsZXN5c3RlbQ0Kb3B0aW9ucwkJS0VSTkZTCQkJI0tlcm5lbCBmaWxlc3lz dGVtDQojb3B0aW9ucwlMRlMJCQkjTG9nIGZpbGVzeXN0ZW0NCm9wdGlvbnMJ CU1GUwkJCSNNZW1vcnkgRmlsZSBTeXN0ZW0NCm9wdGlvbnMJCU1TRE9TRlMJ CQkjTVMgRE9TIEZpbGUgU3lzdGVtDQojb3B0aW9ucwkJTlVMTEZTCQkJI05V TEwgZmlsZXN5c3RlbQ0KI29wdGlvbnMJCVBPUlRBTAkJCSNQb3J0YWwgZmls ZXN5c3RlbQ0Kb3B0aW9ucwkJUFJPQ0ZTCQkJI1Byb2Nlc3MgZmlsZXN5c3Rl bQ0KI29wdGlvbnMJCVVNQVBGUwkJCSNVSUQgbWFwIGZpbGVzeXN0ZW0NCiNv cHRpb25zCQlVTklPTgkJCSNVbmlvbiBmaWxlc3lzdGVtDQpvcHRpb25zCQki Q0Q5NjYwX1JPT1QiCQkjQ0QtUk9NIHVzYWJsZSBhcyByb290IGRldmljZQ0K b3B0aW9ucwkJRkZTX1JPT1QJCSNGRlMgdXNhYmxlIGFzIHJvb3QgZGV2aWNl DQojb3B0aW9ucwlMRlNfUk9PVAkJI0xGUyB1c2FibGUgYXMgcm9vdCBkZXZp Y2UNCm9wdGlvbnMJCU5GU19ST09UCQkjTkZTIHVzYWJsZSBhcyByb290IGRl dmljZQ0KIyBUaGlzIERFVkZTIGlzIGV4cGVyaW1lbnRhbCBidXQgc2VlbXMg dG8gd29yaw0KI29wdGlvbnMJCURFVkZTCQkJI2RldmljZXMgZmlsZXN5c3Rl bQ0KDQojIE1ha2Ugc3BhY2UgaW4gdGhlIGtlcm5lbCBmb3IgYSBNRlMgcm9v dCBmaWxlc3lzdGVtLiAgRGVmaW5lIHRvIHRoZSBudW1iZXINCiMgb2Yga2ls b2J5dGVzIHRvIHJlc2VydmUgZm9yIHRoZSBmaWxlc3lzdGVtLg0KI29wdGlv bnMJCU1GU19ST09UPTEwDQojIEFsbG93IHRoZSBNRlNfUk9PVCBjb2RlIHRv IGxvYWQgdGhlIE1GUyBpbWFnZSBmcm9tIGZsb3BweSBpZiBpdCBpcyBtaXNz aW5nLg0KI29wdGlvbnMJCU1GU19BVVRPTE9BRA0KDQojIEFsbG93IHRoaXMg bWFueSBzd2FwLWRldmljZXMuDQpvcHRpb25zCQlOU1dBUERFVj01DQoNCiMg RGlzayBxdW90YXMgYXJlIHN1cHBvcnRlZCB3aGVuIHRoaXMgb3B0aW9uIGlz IGVuYWJsZWQuICBJZiB5b3UNCiMgY2hhbmdlIHRoZSB2YWx1ZSBvZiB0aGlz IG9wdGlvbiwgeW91IG11c3QgZG8gYSBgbWFrZSBjbGVhbicgaW4geW91cg0K IyBrZXJuZWwgY29tcGlsZSBkaXJlY3RvcnkgaW4gb3JkZXIgdG8gZ2V0IGEg d29ya2luZyBrZXJuZWwuDQojDQojb3B0aW9ucwkJUVVPVEEJCQkjZW5hYmxl IGRpc2sgcXVvdGFzDQoNCiMgQWRkIG1vcmUgY2hlY2tpbmcgY29kZSB0byB2 YXJpb3VzIGZpbGVzeXN0ZW1zDQojb3B0aW9ucwkJTlVMTEZTX0RJQUdOT1NU SUMNCiNvcHRpb25zCQlLRVJORlNfRElBR05PU1RJQw0KI29wdGlvbnMJCVVN QVBGU19ESUFHTk9TVElDDQojb3B0aW9ucwkJVU5JT05fRElBR05PU1RJQw0K DQojIEluIHBhcnRpY3VsYXIgbXVsdGktc2Vzc2lvbiBDRC1ScyBtaWdodCBy ZXF1aXJlIGEgaHVnZSBhbW91bnQgb2YNCiMgdGltZSBpbiBvcmRlciB0byAi c2V0dGxlIi4gIElmIHdlIGFyZSBhYm91dCBtb3VudGluZyB0aGVtIGFzIHRo ZQ0KIyByb290IGYvcywgd2UgZ290dGEgd2FpdCBhIGxpdHRsZS4NCiMNCiMg VGhlIG51bWJlciBpcyBzdXBwb3NlZCB0byBiZSBpbiBzZWNvbmRzLg0KI29w dGlvbnMJCSJDRDk2NjBfUk9PVERFTEFZPTIwIg0KDQojIEFkZCBzb21lIGVy cm9yIGNoZWNraW5nIGNvZGUgdG8gdGhlIG51bGxfYnlwYXNzIHJvdXRpbmUN CiMgaW4gdGhlIE5VTEwgZmlsZXN5c3RlbQ0KIyNvcHRpb25zCQlTQUZFVFkN Cg0KDQojIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMNCiMgU0NTSSBERVZJQ0VT DQoNCiMgU0NTSSBERVZJQ0UgQ09ORklHVVJBVElPTg0KDQojIFRoZSBTQ1NJ IHN1YnN5c3RlbSBjb25zaXN0cyBvZiB0aGUgYGJhc2UnIFNDU0kgY29kZSwg YSBudW1iZXIgb2YNCiMgaGlnaC1sZXZlbCBTQ1NJIGRldmljZSBgdHlwZScg ZHJpdmVycywgYW5kIHRoZSBsb3ctbGV2ZWwgaG9zdC1hZGFwdGVyDQojIGRl dmljZSBkcml2ZXJzLiAgVGhlIGhvc3QgYWRhcHRlcnMgYXJlIGxpc3RlZCBp biB0aGUgSVNBIGFuZCBQQ0kNCiMgZGV2aWNlIGNvbmZpZ3VyYXRpb24gc2Vj dGlvbnMgYmVsb3cuDQojDQojIEJlZ2lubmluZyB3aXRoIEZyZWVCU0QgMi4w LjUgeW91IGNhbiB3aXJlIGRvd24geW91ciBTQ1NJIGRldmljZXMgc28NCiMg dGhhdCBhIGdpdmVuIGJ1cywgdGFyZ2V0LCBhbmQgTFVOIGFsd2F5cyBjb21l IG9uIGxpbmUgYXMgdGhlIHNhbWUNCiMgZGV2aWNlIHVuaXQuICBJbiBlYXJs aWVyIHZlcnNpb25zIHRoZSB1bml0IG51bWJlcnMgd2VyZSBhc3NpZ25lZA0K IyBpbiB0aGUgb3JkZXIgdGhhdCB0aGUgZGV2aWNlcyB3ZXJlIHByb2JlZCBv biB0aGUgU0NTSSBidXMuICBUaGlzDQojIG1lYW5zIHRoYXQgaWYgeW91IHJl bW92ZWQgYSBkaXNrIGRyaXZlLCB5b3UgbWF5IGhhdmUgaGFkIHRvIHJld3Jp dGUNCiMgeW91ciAvZXRjL2ZzdGFiIGZpbGUsIGFuZCBhbHNvIHRoYXQgeW91 IGhhZCB0byBiZSBjYXJlZnVsIHdoZW4gYWRkaW5nDQojIGEgbmV3IGRpc2sg YXMgaXQgbWF5IGhhdmUgYmVlbiBwcm9iZWQgZWFybGllciBhbmQgbW92ZWQg eW91ciBkZXZpY2UNCiMgY29uZmlndXJhdGlvbiBhcm91bmQuDQoNCiMgVGhp cyBvbGQgYmVoYXZpb3IgaXMgbWFpbnRhaW5lZCBhcyB0aGUgZGVmYXVsdCBi ZWhhdmlvci4gIFRoZSB1bml0DQojIGFzc2lnbm1lbnQgYmVnaW5zIHdpdGgg dGhlIGZpcnN0IG5vbi13aXJlZCBkb3duIHVuaXQgZm9yIGEgZGV2aWNlDQoj IHR5cGUuICBGb3IgZXhhbXBsZSwgaWYgeW91IHdpcmUgYSBkaXNrIGFzICJz ZDMiIHRoZW4gdGhlIGZpcnN0DQojIG5vbi13aXJlZCBkaXNrIHdpbGwgYmUg YXNzaWduZWQgc2Q0Lg0KDQojIFRoZSBzeW50YXggZm9yIHdpcmluZyBkb3du IGRldmljZXMgaXM6DQoNCiMgY29udHJvbGxlcglzY2J1czAgYXQgYWhjMAkJ IyBTaW5nbGUgYnVzIGRldmljZQ0KIyBjb250cm9sbGVyCXNjYnVzMSBhdCBh aGMxIGJ1cyAwCSMgU2luZ2xlIGJ1cyBkZXZpY2UNCiMgY29udHJvbGxlcglz Y2J1czMgYXQgYWhjMiBidXMgMAkjIFR3aW4gYnVzIGRldmljZQ0KIyBjb250 cm9sbGVyCXNjYnVzMiBhdCBhaGMyIGJ1cyAxCSMgVHdpbiBidXMgZGV2aWNl DQojIGRpc2sgCQlzZDAgYXQgc2NidXMwIHRhcmdldCAwIHVuaXQgMA0KIyBk aXNrCQlzZDEgYXQgc2NidXMzIHRhcmdldCAxDQojIGRpc2sJCXNkMiBhdCBz Y2J1czIgdGFyZ2V0IDMNCiMgdGFwZQkJc3QxIGF0IHNjYnVzMSB0YXJnZXQg Ng0KIyBkZXZpY2UJY2QwIGF0IHNjYnVzPw0KDQojICJ1bml0cyIgKFNDU0kg bG9naWNhbCB1bml0IG51bWJlcikgdGhhdCBhcmUgbm90IHNwZWNpZmllZCBh cmUNCiMgdHJlYXRlZCBhcyBpZiBzcGVjaWZpZWQgYXMgTFVOIDAuDQoNCiMg QWxsIFNDU0kgZGV2aWNlcyBhbGxvY2F0ZSBhcyBtYW55IHVuaXRzIGFzIGFy ZSByZXF1aXJlZC4NCg0KIyBUaGUgInVua25vd24iIGRldmljZSAodWs/IGlu IHByZS0yLjAuNSkgaXMgbm93IHBhcnQgb2YgdGhlIGJhc2UgU0NTSQ0KIyBj b25maWd1cmF0aW9uIGFuZCBkb2Vzbid0IGhhdmUgdG8gYmUgZXhwbGljaXRs eSBjb25maWd1cmVkLg0KDQpjb250cm9sbGVyCXNjYnVzMAkjYmFzZSBTQ1NJ IGNvZGUNCmRldmljZQkJY2gwCSNTQ1NJIG1lZGlhIGNoYW5nZXJzDQpkZXZp Y2UJCXNkMAkjU0NTSSBkaXNrcw0KZGV2aWNlCQlzdDAJI1NDU0kgdGFwZXMN CmRldmljZQkJY2QwCSNTQ1NJIENELVJPTXMNCmRldmljZQkJb2QwCSNTQ1NJ IG9wdGljYWwgZGlzaw0KDQojIFRoZSBwcmV2aW91cyBkZXZpY2VzIChjaCwg c2QsIHN0LCBjZCkgYXJlIHJlY29nbml6ZWQgYnkgY29uZmlnLg0KIyBjb25m aWcgZG9lc24ndCAoYW5kIHNob3VsZG4ndCkga25vdyBhYm91dCB0aGVzZSBu ZXdlciBvbmVzLA0KIyBzbyB3ZSBoYXZlIHRvIHNwZWNpZnkgdGhhdCB0aGV5 IGFyZSBvbiBhIFNDU0kgYnVzIHdpdGggdGhlICJhdCBzY2J1cz8iDQojIGNs YXVzZS4NCg0KZGV2aWNlIHdvcm0wIGF0IHNjYnVzPwkjIFNDU0kgd29ybQ0K I2RldmljZSBwdDAgYXQgc2NidXM/CSMgU0NTSSBwcm9jZXNzb3IgdHlwZQ0K I2RldmljZSBzY3RhcmcwIGF0IHNjYnVzPyAjIFNDU0kgdGFyZ2V0DQoNCiMg U0NTSSBPUFRJT05TOg0KDQojIFNDU0lERUJVRzogV2hlbiBkZWZpbmVkIGVu YWJsZXMgZGVidWdnaW5nIG1hY3Jvcw0KIyBOT19TQ1NJX1NFTlNFOiBXaGVu IGRlZmluZWQgZGlzYWJsZXMgc2Vuc2UgZGVzY3JpcHRpb25zIChhYm91dCA0 aykNCiMgU0NTSV9SRVBPUlRfR0VPTUVUUlk6IEFsd2F5cyByZXBvcnQgZGlz ayBnZW9tZXRyeSBhdCBib290IHVwIGluc3RlYWQNCiMgICAgICAgICAgICAg ICAgICAgICAgIG9mIG9ubHkgd2hlbiBib290aW5nIHZlcmJvc2VseS4NCiNv cHRpb25zCQlTQ1NJREVCVUcNCiNvcHRpb25zCU5PX1NDU0lfU0VOU0UNCm9w dGlvbnMJCVNDU0lfUkVQT1JUX0dFT01FVFJZDQoNCiMgT3B0aW9ucyBmb3Ig dGhlIGBvZCcgb3B0aWNhbCBkaXNrIGRyaXZlcjoNCiMNCiMgSWYgZHJpdmUg cmV0dXJucyBzZW5zZSBrZXkgYXMgMHgwMiB3aXRoIHZlbmRvciBzcGVjaWZp YyBhZGRpdGlvbmFsDQojIHNlbnNlIGNvZGUgKEFTQykgYW5kIGFkZGl0aW9u YWwgc2Vuc2UgY29kZSBxdWFsaWZpZXIgKEFTQ1EpLCBvcg0KIyBpbGxlZ2Fs IEFTQyBhbmQgQVNDUS4gVGhpcyBjYXVzZSBhbiBlcnJvciAoTk9UIFJFQURZ KSBhbmQgcmV0cnlpbmcuDQojIFRvIHN1cHByZXNzIHRoaXMsIHVzZSB0aGUg Zm9sbG93aW5nIG9wdGlvbi4NCiMNCiNvcHRpb25zCQlPRF9CT0dVU19OT1Rf UkVBRFkNCiMNCiMgRm9yIGFuIGF1dG9tYXRpYyBzcGluZG93biwgdHJ5IHRo aXMuICBBZ2FpbiwgcHJlZmVyYWJseSBhcyBhbg0KIyBvcHRpb24gaW4geW91 ciBjb25maWcgZmlsZS4NCiMgV0FSTklORyEgIFVzZSBhdCB5b3VyIG93biBy aXNrLiAgSm9lcmcncyBhbmNpZW50IFNPTlkgU01PIGRyaXZlDQojIGdyb2tz IGl0IGZpbmUsIHdoaWxlIFNodW5zdWtlJ3MgRnVqaXRzdSBjaG9rZXMgb24g aXQgYW5kIHRpbWVzDQojIG91dC4NCiMNCiNvcHRpb25zCQlPRF9BVVRPX1RV Uk5PRkYNCg0KDQoNCiMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIw0KIyBNSVND RUxMQU5FT1VTIERFVklDRVMgQU5EIE9QVElPTlMNCg0KIyBUaGUgYHB0eScg ZGV2aWNlIHVzdWFsbHkgdHVybnMgb3V0IHRvIGJlIGBgZWZmZWN0aXZlbHkg bWFuZGF0b3J5JycsDQojIGFzIGl0IGlzIHJlcXVpcmVkIGZvciBgdGVsbmV0 ZCcsIGBybG9naW5kJywgYHNjcmVlbicsIGBlbWFjcycsIGFuZA0KIyBgeHRl cm0nLCBhbW9uZyBvdGhlcnMuDQoNCnBzZXVkby1kZXZpY2UJcHR5CTY0CSNQ c2V1ZG8gdHR5cyAtIGNhbiBnbyBhcyBoaWdoIGFzIDI1Ng0KcHNldWRvLWRl dmljZQlzcGVha2VyCQkjUGxheSBJQk0gQkFTSUMtc3R5bGUgbm9pc2VzIG91 dCB5b3VyIHNwZWFrZXINCnBzZXVkby1kZXZpY2UJZ3ppcAkJI0V4ZWMgZ3pp cHBlZCBhLm91dCdzDQpwc2V1ZG8tZGV2aWNlCXZuCQkjVm5vZGUgZHJpdmVy ICh0dXJucyBhIGZpbGUgaW50byBhIGRldmljZSkNCnBzZXVkby1kZXZpY2UJ c25wCTMJI1Nub29wIGRldmljZSAtIHRvIGxvb2sgYXQgcHR5L3Z0eS9ldGMu Lg0KcHNldWRvLWRldmljZQljY2QJNAkjQ29uY2F0ZW5hdGVkIGRpc2sgZHJp dmVyDQoNCiMgVGhlc2UgYXJlIG9ubHkgZm9yIHdhdGNoaW5nIGZvciBiaXRy b3QgaW4gb2xkIHR0eSBjb2RlLg0KIyBicm9rZW4NCiNwc2V1ZG8tZGV2aWNl CXRiDQoNCiMgVGhlc2UgYXJlIG9ubHkgZm9yIHdhdGNoaW5nIGZvciBiaXRy b3QgaW4gb2xkIFNDU0kgY29kZS4NCiNwc2V1ZG8tZGV2aWNlCXN1CQkjc2Nz aSB1c2VyDQojcHNldWRvLWRldmljZQlzc2MJCSNzdXBlciBzY3NpDQoNCg0K IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjDQojIEhBUkRXQVJFIERFVklDRSBD T05GSUdVUkFUSU9ODQoNCiMgSVNBIGFuZCBFSVNBIGRldmljZXM6DQojIEVJ U0Egc3VwcG9ydCBpcyBhdmFpbGFibGUgZm9yIHNvbWUgZGV2aWNlLCBzbyB0 aGV5IGNhbiBiZSBhdXRvLXByb2JlZC4NCiMgTWljcm8gQ2hhbm5lbCBpcyBu b3Qgc3VwcG9ydGVkIGF0IGFsbC4NCg0KIw0KIyBNYW5kYXRvcnkgSVNBIGRl dmljZXM6IGlzYSwgbnB4DQojDQpjb250cm9sbGVyCWlzYTANCg0KIw0KIyBP cHRpb25zIGZvciBgaXNhJzoNCiMNCiMgQVVUT19FT0lfMSBlbmFibGVzIHRo ZSBgYXV0b21hdGljIEVPSScgZmVhdHVyZSBmb3IgdGhlIG1hc3RlciA4MjU5 QQ0KIyBpbnRlcnJ1cHQgY29udHJvbGxlci4gIFRoaXMgc2F2ZXMgYWJvdXQg MC43LTEuMjUgdXNlYyBmb3IgZWFjaCBpbnRlcnJ1cHQuDQojIFRoaXMgb3B0 aW9uIGJyZWFrcyBzdXNwZW5kL3Jlc3VtZSBvbiBzb21lIHBvcnRhYmxlcy4N CiMNCiMgQVVUT19FT0lfMiBlbmFibGVzIHRoZSBgYXV0b21hdGljIEVPSScg ZmVhdHVyZSBmb3IgdGhlIHNsYXZlIDgyNTlBDQojIGludGVycnVwdCBjb250 cm9sbGVyLiAgVGhpcyBzYXZlcyBhYm91dCAwLjctMS4yNSB1c2VjIGZvciBl YWNoIGludGVycnVwdC4NCiMgQXV0b21hdGljIEVPSSBpcyBkb2N1bWVudGVk IG5vdCB0byB3b3JrIGZvciBmb3IgdGhlIHNsYXZlIHdpdGggdGhlDQojIG9y aWdpbmFsIGk4MjU5QSwgYnV0IGl0IHdvcmtzIGZvciBzb21lIGNsb25lcyBh bmQgc29tZSBpbnRlZ3JhdGVkDQojIHZlcnNpb25zLg0KIw0KIyBCT1VOQ0Vf QlVGRkVSUyBwcm92aWRlcyBzdXBwb3J0IGZvciBJU0EgRE1BIG9uIG1hY2hp bmVzIHdpdGggbW9yZQ0KIyB0aGFuIDE2IG1lZ2FieXRlcyBvZiBtZW1vcnku ICBJdCBkb2Vzbid0IGh1cnQgb24gb3RoZXIgbWFjaGluZXMuDQojIFNvbWUg YnJva2VuIEVJU0EgYW5kIFZMQiBoYXJkd2FyZSBtYXkgbmVlZCB0aGlzLCB0 b28uDQojDQojIE1BWE1FTSBzcGVjaWZpZXMgdGhlIGFtb3VudCBvZiBSQU0g b24gdGhlIG1hY2hpbmU7IGlmIHRoaXMgaXMgbm90DQojIHNwZWNpZmllZCwg RnJlZUJTRCB3aWxsIGZpcnN0IHJlYWQgdGhlIGFtb3VudCBvZiBtZW1vcnkg ZnJvbSB0aGUgQ01PUw0KIyBSQU0sIHNvIHRoZSBhbW91bnQgb2YgbWVtb3J5 IHdpbGwgaW5pdGlhbGx5IGJlIGxpbWl0ZWQgdG8gNjRNQiBvciAxNk1CDQoj IGRlcGVuZGluZyBvbiB0aGUgQklPUy4gIElmIHRoZSBCSU9TIHJlcG9ydHMg NjRNQiwgYSBtZW1vcnkgcHJvYmUgd2lsbA0KIyB0aGVuIGF0dGVtcHQgdG8g ZGV0ZWN0IHRoZSBpbnN0YWxsZWQgYW1vdW50IG9mIFJBTS4gIElmIHRoaXMg cHJvYmUNCiMgZmFpbHMgdG8gZGV0ZWN0ID42NE1CIFJBTSB5b3Ugd2lsbCBo YXZlIHRvIHVzZSB0aGUgTUFYTUVNIG9wdGlvbi4NCiMgVGhlIGFtb3VudCBp cyBpbiBraWxvYnl0ZXMsIHNvIGZvciBhIG1hY2hpbmUgd2l0aCAxMjhNQiBv ZiBSQU0sIGl0IHdvdWxkDQojIGJlIDEzMTA3MiAoMTI4ICogMTAyNCkuDQoj DQojIFRVTkVfMTU0MiBlbmFibGVzIHRoZSBhdXRvbWF0aWMgSVNBIGJ1cyBz cGVlZCBzZWxlY3Rpb24gZm9yIHRoZQ0KIyBBZGFwdGVjIDE1NDIgYm9hcmRz LiBEb2VzIG5vdCB3b3JrIGZvciBhbGwgYm9hcmRzLCB1c2UgaXQgd2l0aCBj YXV0aW9uLg0KIw0KIyBCUk9LRU5fS0VZQk9BUkRfUkVTRVQgZGlzYWJsZXMg dGhlIHVzZSBvZiB0aGUga2V5Ym9hcmQgY29udHJvbGxlciB0bw0KIyByZXNl dCB0aGUgQ1BVIGZvciByZWJvb3QuICBUaGlzIGlzIG5lZWRlZCBvbiBzb21l IHN5c3RlbXMgd2l0aCBicm9rZW4NCiMga2V5Ym9hcmQgY29udHJvbGxlcnMu DQojDQojIFBBU19KT1lTVElDS19FTkFCTEUgZW5hYmxlcyB0aGUgZ2FtZXBv cnQgb24gdGhlIFByb0F1ZGlvIFNwZWN0cnVtDQoNCm9wdGlvbnMJCSJBVVRP X0VPSV8xIg0KI29wdGlvbnMJIkFVVE9fRU9JXzIiDQpvcHRpb25zCQlCT1VO Q0VfQlVGRkVSUw0KI29wdGlvbnMJCSJNQVhNRU09KDEyOCoxMDI0KSINCiNv cHRpb25zICAgICAgICAiVFVORV8xNTQyIg0KI29wdGlvbnMJQlJPS0VOX0tF WUJPQVJEX1JFU0VUDQojb3B0aW9ucwlQQVNfSk9ZU1RJQ0tfRU5BQkxFDQoN CiMgRW5hYmxlIHN1cHBvcnQgZm9yIHRoZSBrZXJuZWwgUExMIHRvIHVzZSBh biBleHRlcm5hbCBQUFMgc2lnbmFsLA0KIyB1bmRlciBzdXBlcnZpc2lvbiBv ZiBbeF1udHBkKDgpDQojIE1vcmUgaW5mbyBpbiBmdHA6Ly9mdHAudWRlbC5l ZHUvcHViL250cC9rZXJuZWwudGFyLloNCg0KI29wdGlvbnMJCVBQU19TWU5D DQoNCiMgRW5hYmxlIFBuUCBzdXBwb3J0IGluIHRoZSBrZXJuZWwuICBUaGlz IGFsbG93cyB5b3UgdG8gYXV0b21hdGljbHkNCiMgYXR0YWNoIHRvIFBuUCBj YXJkcyBmb3IgZHJpdmVycyB0aGF0IHN1cHBvcnQgaXQgYW5kIGFsbG93cyB5 b3UgdG8NCiMgY29uZmlndXJlIGNhcmRzIGZyb20gVVNFUkNPTkZJRy4gIFNl ZSBwbnAoNCkgZm9yIG1vcmUgaW5mby4NCmNvbnRyb2xsZXIJcG5wMA0KDQoj IFRoZSBzeXNjb25zIGNvbnNvbGUgZHJpdmVyIChzY28gY29sb3IgY29uc29s ZSBjb21wYXRpYmxlKSAtIGRlZmF1bHQuDQpkZXZpY2UJCXNjMAlhdCBpc2E/ IHBvcnQgIklPX0tCRCIgdHR5IGlycSAxIHZlY3RvciBzY2ludHINCm9wdGlv bnMJCU1BWENPTlM9MTIJCSMgbnVtYmVyIG9mIHZpcnR1YWwgY29uc29sZXMN CiNvcHRpb25zCQlTTE9XX1ZHQQkJIyBkbyBieXRlLXdpZGUgaS9vJ3MgdG8g VFMgYW5kIEdEQyByZWdzDQojb3B0aW9ucwkJIlNURDhYMTZGT05UIgkJIyBD b21waWxlIGZvbnQgaW4NCiNtYWtlb3B0aW9ucwkiU1REOFgxNkZPTlQiPSJj cDg1MCINCm9wdGlvbnMJCVNDX0hJU1RPUllfU0laRT01MDAJIyBudW1iZXIg b2YgaGlzdG9yeSBidWZmZXIgbGluZXMNCg0KIw0KIyBgZmxhZ3MnIGZvciBz YzA6DQojICAgICAgIDB4MDEgICAgVXNlIGEgJ3Zpc3VhbCcgYmVsbA0KIyAg ICAgICAweDAyICAgIFVzZSBhICdibGluaycgY3Vyc29yDQojICAgICAgIDB4 MDQgICAgVXNlIGEgJ3VuZGVybGluZScgY3Vyc29yDQojICAgICAgIDB4MDYg ICAgVXNlIGEgJ2JsaW5raW5nIHVuZGVybGluZScgKGRlc3RydWN0aXZlKSBj dXJzb3INCiMgICAgICAgMHgwOCAgICBGb3JjZSBkZXRlY3Rpb24gb2Yga2V5 Ym9hcmQsIGVsc2Ugd2UgYWx3YXlzIGFzc3VtZSBhIGtleWJvYXJkDQojICAg ICAgIDB4MTAgICAgT2xkLXN0eWxlIChYVCkga2V5Ym9hcmQgc3VwcG9ydCwg dXNlZnVsIGZvciBvbGRlciBUaGlua1BhZHMNCiMgICAgICAgMHgyMCAgICBE b24ndCByZXNldCBrZXlib2FyZCwgdXNlZnVsIGZvciBzb21lIG5ld2VyIFRo aW5rUGFkcw0KDQojDQojIFRoZSBOdW1lcmljIFByb2Nlc3NpbmcgZVh0ZW5z aW9uIGRyaXZlci4gIFRoaXMgc2hvdWxkIGJlIGNvbmZpZ3VyZWQgaWYNCiMg eW91ciBtYWNoaW5lIGhhcyBhIG1hdGggY28tcHJvY2Vzc29yLCB1bmxlc3Mg dGhlIGNvcHJvY2Vzc29yIGlzIHZlcnkNCiMgYnVnZ3kuIElmIGl0IGlzIG5v dCBjb25maWd1cmVkIHRoZW4geW91ICptdXN0KiBjb25maWd1cmUgbWF0aCBl bXVsYXRpb24NCiMgKHNlZSBhYm92ZSkuICBJZiBib3RoIG5weDAgYW5kIGVt dWxhdGlvbiBhcmUgY29uZmlndXJlZCwgdGhlbiBvbmx5IG5weDANCiMgaXMg dXNlZCAocHJvdmlkZWQgaXQgd29ya3MpLg0KZGV2aWNlCQlucHgwCWF0IGlz YT8gcG9ydCAiSU9fTlBYIiBpb3NpeiAweDAgZmxhZ3MgMHgwIGlycSAxMyB2 ZWN0b3IgbnB4aW50cg0KDQojDQojIGBmbGFncycgZm9yIG5weDA6DQojCTB4 MDEJZG9uJ3QgdXNlIHRoZSBucHggcmVnaXN0ZXJzIHRvIG9wdGltaXplIGJj b3B5DQojCTB4MDIJZG9uJ3QgdXNlIHRoZSBucHggcmVnaXN0ZXJzIHRvIG9w dGltaXplIGJ6ZXJvDQojCTB4MDQJZG9uJ3QgdXNlIHRoZSBucHggcmVnaXN0 ZXJzIHRvIG9wdGltaXplIGNvcHlpbiBvciBjb3B5b3V0Lg0KIyBUaGUgbnB4 IHJlZ2lzdGVycyBhcmUgbm9ybWFsbHkgdXNlZCB0byBvcHRpbWl6ZSBjb3B5 aW5nIGFuZCB6ZXJvaW5nIHdoZW4NCiMgYWxsIG9mIHRoZSBmb2xsb3dpbmcg Y29uZGl0aW9ucyBhcmUgc2F0aXNmaWVkOg0KIwkiSTU4Nl9DUFUiIGlzIGFu IG9wdGlvbg0KIwl0aGUgY3B1IGlzIGFuIGk1ODYgKHBlcmhhcHMgbm90IGEg UGVudGl1bSkNCiMJdGhlIHByb2JlIGZvciBucHgwIHN1Y2NlZWRzDQojCUlO VCAxNiBleGNlcHRpb24gaGFuZGxpbmcgd29ya3MuDQojIFRoZW4gY29weWlu ZyBhbmQgemVyb2luZyB1c2luZyB0aGUgbnB4IHJlZ2lzdGVycyBpcyBub3Jt YWxseSAzMC0xMDAlIGZhc3Rlci4NCiMgVGhlIGZsYWdzIGNhbiBiZSB1c2Vk IHRvIGNvbnRyb2wgY2FzZXMgd2hlcmUgaXQgZG9lc24ndCB3b3JrIG9yIGlz IHNsb3dlci4NCiMgU2V0dGluZyB0aGVtIGF0IGJvb3QgdGltZSB1c2luZyB1 c2VyY29uZmlnIHdvcmtzIHJpZ2h0ICh0aGUgb3B0aW1pemF0aW9ucw0KIyBh cmUgbm90IHVzZWQgdW50aWwgbGF0ZXIgaW4gdGhlIGJvb3RzdHJhcCB3aGVu IG5weDAgaXMgYXR0YWNoZWQpLg0KIw0KDQojDQojIGBpb3NpeicgZm9yIG5w eDA6DQojIFRoaXMgY2FuIGJlIHVzZWQgaW5zdGVhZCBvZiB0aGUgTUFYTUVN IG9wdGlvbiB0byBzZXQgdGhlIG1lbW9yeSBzaXplLiAgSWYNCiMgaXQgaXMg bm9uemVybywgdGhlbiBpdCBvdmVycmlkZXMgYm90aCB0aGUgTUFYTUVNIG9w dGlvbiBhbmQgdGhlIG1lbW9yeQ0KIyBzaXplIHJlcG9ydGVkIGJ5IHRoZSBC SU9TLiAgU2V0dGluZyBpdCBhdCBib290IHRpbWUgdXNpbmcgdXNlcmNvbmZp ZyB0YWtlcw0KIyBlZmZlY3Qgb24gdGhlIG5leHQgcmVib290IGFmdGVyIHRo ZSBjaGFuZ2UgaGFzIGJlZW4gcmVjb3JkZWQgaW4gdGhlIGtlcm5lbA0KIyBi aW5hcnkgKHRoZSBzaXplIGlzIHVzZWQgZWFybHkgaW4gdGhlIGJvb3QgYmVm b3JlIHVzZXJjb25maWcgaGFzIGEgY2hhbmNlDQojIHRvIGNoYW5nZSBpdCku DQojDQoNCiMNCiMgT3B0aW9uYWwgSVNBIGFuZCBFSVNBIGRldmljZXM6DQoj DQoNCiMNCiMgU0NTSSBob3N0IGFkYXB0ZXJzOiBgYWhhJywgYGFpYycsIGBi dCcsIGBuY2EnDQojDQojIGFoYTogQWRhcHRlYyAxNTR4DQojIGFoYzogQWRh cHRlYyAyNzR4LzI4NHgvMjk0eA0KIyBhaWM6IEFkYXB0ZWMgMTUyeCBhbmQg c291bmQgY2FyZHMgdXNpbmcgdGhlIEFkYXB0ZWMgQUlDLTYzNjAgKHNsb3ch KQ0KIyBidDogTW9zdCBCdXNsb2dpYyBjb250cm9sbGVycw0KIyBuY2E6IFBy b0F1ZGlvU3BlY3RydW0gY2FyZHMgdXNpbmcgdGhlIE5DUiA1MzgwIG9yIFRy YW50b3IgVDEzMA0KIyB1aGE6IFVsdHJhU3RvcmUgMTRGIGFuZCAzNEYNCiMg c2VhOiBTZWFnYXRlIFNUMDEvMDIgOCBiaXQgY29udHJvbGxlciAoc2xvdyEp DQojIHdkczogV2VzdGVybiBEaWdpdGFsIFdENzAwMCBjb250cm9sbGVyIChu byBzY2F0dGVyL2dhdGhlciEpLg0KIw0KIyBOb3RlIHRoYXQgdGhlIG9yZGVy IGlzIGltcG9ydGFudCBpbiBvcmRlciBmb3IgQnVzbG9naWMgY2FyZHMgdG8g YmUNCiMgcHJvYmVkIGNvcnJlY3RseS4NCiMNCg0KY29udHJvbGxlciAgICAg IGFpYzAgICAgYXQgaXNhPyBwb3J0IDB4MzQwIGJpbyBpcnEgMTEgdmVjdG9y IGFpY2ludHINCg0KIyBTVC01MDYsIEVTREksIGFuZCBJREUgaGFyZCBkaXNr czogYHdkYycgYW5kIGB3ZCcNCiMNCiMgVGhlIGZsYWdzIGZpZWxkcyBhcmUg dXNlZCB0byBlbmFibGUgdGhlIG11bHRpLXNlY3RvciBJL08gYW5kDQojIHRo ZSAzMkJJVCBJL08gbW9kZXMuICBUaGUgZmxhZ3MgbWF5IGJlIHVzZWQgaW4g ZWl0aGVyIHRoZSBjb250cm9sbGVyDQojIGRlZmluaXRpb24gb3IgaW4gdGhl IGluZGl2aWR1YWwgZGlzayBkZWZpbml0aW9ucy4gIFRoZSBjb250cm9sbGVy DQojIGRlZmluaXRpb24gaXMgc3VwcG9ydGVkIGZvciB0aGUgYm9vdCBjb25m aWd1cmF0aW9uIHN0dWZmLg0KIw0KIyBFYWNoIGRyaXZlIGhhcyBhIDE2IGJp dCBmbGFncyB2YWx1ZSBkZWZpbmVkOg0KIwlUaGUgbG93IDggYml0cyBhcmUg dGhlIG1heGltdW0gdmFsdWUgZm9yIHRoZSBtdWx0aS1zZWN0b3IgSS9PLA0K Iwl3aGVyZSAweGZmIGRlZmF1bHRzIHRvIHRoZSBtYXhpbXVtIHRoYXQgdGhl IGRyaXZlIGNhbiBoYW5kbGUuDQojCVRoZSBoaWdoIGJpdCBvZiB0aGUgMTYg Yml0IGZsYWdzICgweDgwMDApIGFsbG93cyBwcm9iaW5nIGZvcg0KIwkzMiBi aXQgdHJhbnNmZXJzLiAgQml0IDE0ICgweDQwMDApIGVuYWJsZXMgYSBoYWNr IHRvIHdha2UNCiMJdXAgcG93ZXJlZC1kb3duIGxhcHRvcCBkcml2ZXMuICBC aXQgMTMgKDB4MjAwMCkgYWxsb3dzDQojCXByb2JpbmcgZm9yIFBDSSBJREUg RE1BIGNvbnRyb2xsZXJzLCBzdWNoIGFzIEludGVsJ3MgUElJWA0KIwlzb3V0 aCBicmlkZ2VzLiAgU2VlIHRoZSB3ZC40IG1hbiBwYWdlLg0KIw0KIyBUaGUg ZmxhZ3MgZmllbGQgZm9yIHRoZSBkcml2ZXMgY2FuIGJlIHNwZWNpZmllZCBp biB0aGUgY29udHJvbGxlcg0KIyBzcGVjaWZpY2F0aW9uIHdpdGggdGhlIGxv dyAxNiBiaXRzIGZvciBkcml2ZSAwLCBhbmQgdGhlIGhpZ2ggMTYgYml0cw0K IyBmb3IgZHJpdmUgMS4NCiMgZS5nLjoNCiNjb250cm9sbGVyCXdkYzAJYXQg aXNhPyBwb3J0ICJJT19XRDEiIGJpbyBpcnEgMTQgZmxhZ3MgMHgwMGZmODAw NCB2ZWN0b3Igd2RpbnRyDQojDQojIHNwZWNpZmllcyB0aGF0IGRyaXZlIDAg d2lsbCBiZSBhbGxvd2VkIHRvIHByb2JlIGZvciAzMiBiaXQgdHJhbnNmZXJz IGFuZA0KIyBhIG1heGltdW0gbXVsdGktc2VjdG9yIHRyYW5zZmVyIG9mIDQg c2VjdG9ycywgYW5kIGRyaXZlIDEgd2lsbCBub3QgYmUNCiMgYWxsb3dlZCB0 byBwcm9iZSBmb3IgMzIgYml0IHRyYW5zZmVycywgYnV0IHdpbGwgYWxsb3cg bXVsdGktc2VjdG9yDQojIHRyYW5zZmVycyB1cCB0byB0aGUgbWF4aW11bSB0 aGF0IHRoZSBkcml2ZSBzdXBwb3J0cy4NCiMNCiMgSWYgeW91IGFyZSB1c2lu ZyBhIFBDSSBjb250cm9sbGVyIHRoYXQgaXMgbm90IHJ1bm5pbmcgaW4gY29t cGF0aWJpbGl0eQ0KIyBtb2RlIChmb3IgZXhhbXBsZSwgaXQgaXMgYSAybmQg SURFIFBDSSBpbnRlcmZhY2UpLCB0aGVuIHVzZSBjb25maWcgbGluZShzKQ0K IyBzdWNoIGFzOg0KIw0KI2NvbnRyb2xsZXIJd2RjMglhdCBpc2E/IHBvcnQg IjAiIGJpbyBpcnEgPyBmbGFncyAweGEwZmZhMGZmIHZlY3RvciB3ZGludHIN CiNkaXNrCQl3ZDQJYXQgd2RjMiBkcml2ZSAwDQojZGlzawkJd2Q1CWF0IHdk YzIgZHJpdmUgMQ0KIw0KI2NvbnRyb2xsZXIJd2RjMwlhdCBpc2E/IHBvcnQg IjAiIGJpbyBpcnEgPyBmbGFncyAweGEwZmZhMGZmIHZlY3RvciB3ZGludHIN CiNkaXNrCQl3ZDYJYXQgd2RjMyBkcml2ZSAwDQojZGlzawkJd2Q3CWF0IHdk YzMgZHJpdmUgMQ0KIw0KIyBOb3RlIHRoYXQgdGhlIGFib3ZlIGNvbmZpZyB3 b3VsZCBiZSB1c2VmdWwgZm9yIGEgUHJvbWlzZSBjYXJkLCB3aGVuIHVzZWQN CiMgb24gYSBNQiB0aGF0IGFscmVhZHkgaGFzIGEgUElJWCBjb250cm9sbGVy LiAgTm90ZSB0aGUgYm9ndXMgaXJxIGFuZCBwb3J0DQojIGVudHJpZXMuICBU aGVzZSBhcmUgYXV0b21hdGljYWxseSBmaWxsZWQgaW4gYnkgdGhlIElERS9Q Q0kgc3VwcG9ydC4NCiMNCg0KY29udHJvbGxlcgl3ZGMwCWF0IGlzYT8gcG9y dCAiSU9fV0QxIiBiaW8gaXJxIDE0IHZlY3RvciB3ZGludHINCmRpc2sJCXdk MAlhdCB3ZGMwIGRyaXZlIDANCmRpc2sJCXdkMQlhdCB3ZGMwIGRyaXZlIDEN CmNvbnRyb2xsZXIJd2RjMQlhdCBpc2E/IHBvcnQgIklPX1dEMiIgYmlvIGly cSAxNSB2ZWN0b3Igd2RpbnRyDQpkaXNrCQl3ZDIJYXQgd2RjMSBkcml2ZSAw DQpkaXNrCQl3ZDMJYXQgd2RjMSBkcml2ZSAxDQoNCiMNCiMgT3B0aW9ucyBm b3IgYHdkYyc6DQojDQojIENNRDY0MCBlbmFibGVzIHNlcmlhbGl6aW5nIGFj Y2VzcyB0byBwcmltYXJ5IGFuZCBzZWNvbmRhcnkgY2hhbm5lbA0KIyBvZiB0 aGUgQ01ENjQwQiBJREUgQ2hpcC4gVGhlIHNlcmlhbGl6aW5nIHdpbGwgb25s eSB0YWtlIHBsYWNlDQojIGlmIHRoaXMgb3B0aW9uIGlzIHNldCAqYW5kKiB0 aGUgY2hpcCBpcyBwcm9iZWQgYnkgdGhlIHBjaS1zeXN0ZW0uDQojDQojb3B0 aW9ucyAgICAgICAgICJDTUQ2NDAiCSNFbmFibGUgd29yayBhcm91bmQgZm9y IENNRDY0MCBoL3cgYnVnDQojDQojIEFUQVBJIGVuYWJsZXMgdGhlIHN1cHBv cnQgZm9yIEFUQVBJLWNvbXBhdGlibGUgSURFIGRldmljZXMNCiMNCm9wdGlv bnMgICAgICAgICBBVEFQSSAgICNFbmFibGUgQVRBUEkgc3VwcG9ydCBmb3Ig SURFIGJ1cw0Kb3B0aW9ucwkJQVRBUElfU1RBVElDCSNEb24ndCBkbyBpdCBh cyBhbiBMS00NCg0KIyBJREUgQ0QtUk9NIGRyaXZlciAtIHJlcXVpcmVzIHdk YyBjb250cm9sbGVyIGFuZCBBVEFQSSBvcHRpb24NCmRldmljZSAgICAgICAg ICB3Y2QwDQoNCiMgSURFIGZsb3BweSBkcml2ZXIgLSByZXF1aXJlcyB3ZGMg Y29udHJvbGxlciBhbmQgQVRBUEkgb3B0aW9uDQojZGV2aWNlICAgICAgICAg IHdmZDANCg0KDQojDQojIFN0YW5kYXJkIGZsb3BweSBkaXNrIGNvbnRyb2xs ZXJzIGFuZCBmbG9wcHkgdGFwZXM6IGBmZGMnLCBgZmQnLCBhbmQgYGZ0Jw0K Iw0KY29udHJvbGxlcglmZGMwCWF0IGlzYT8gcG9ydCAiSU9fRkQxIiBiaW8g aXJxIDYgZHJxIDIgdmVjdG9yIGZkaW50cg0KIw0KIyBGRENfREVCVUcgZW5h YmxlcyBmbG9wcHkgZGVidWdnaW5nLiAgU2luY2UgdGhlIGRlYnVnIG91dHB1 dCBpcyBodWdlLCB5b3UNCiMgZ290dGEgdHVybiBpdCBhY3R1YWxseSBvbiBi eSBzZXR0aW5nIHRoZSB2YXJpYWJsZSBmZF9kZWJ1ZyB3aXRoIEREQiwNCiMg aG93ZXZlci4NCiNvcHRpb25zCQlGRENfREVCVUcNCiMgVGhpcyBvcHRpb24g aXMgdW5kb2N1bWVudGVkIG9uIHB1cnBvc2UuDQojb3B0aW9ucwkJRkRDX1BS SU5UX0JPR1VTX0NISVBUWVBFDQojDQojIEFjdGl2YXRlIHRoaXMgbGluZSBp bnN0ZWFkIG9mIHRoZSBmZGMwIGxpbmUgYWJvdmUgaWYgeW91IGhhcHBlbiB0 bw0KIyBoYXZlIGFuIEluc2lnaHQgZmxvcHB5IHRhcGUuICBQcm9iaW5nIHRo ZW0gcHJvdmVkIHRvIGJlIGRhbmdlcm91cw0KIyBmb3IgcGVvcGxlIHdpdGgg ZmxvcHB5IGRpc2tzIG9ubHksIHNvIGl0J3MgImhpZGRlbiIgYmVoaW5kIGEg ZmxhZzoNCiNjb250cm9sbGVyIGZkYzAgYXQgaXNhPyBwb3J0ICJJT19GRDEi IGJpbyBmbGFncyAxIGlycSA2IGRycSAyIHZlY3RvciBmZGludHINCg0KZGlz awkJZmQwCWF0IGZkYzAgZHJpdmUgMA0KI2Rpc2sJCWZkMQlhdCBmZGMwIGRy aXZlIDENCiN0YXBlCQlmdDAJYXQgZmRjMCBkcml2ZSAyDQoNCg0KIw0KIyBP dGhlciBzdGFuZGFyZCBQQyBoYXJkd2FyZTogYGxwdCcsIGBtc2UnLCBgcHNt JywgYHNpbycsIGV0Yy4NCiMNCiMgbHB0OiBwcmludGVyIHBvcnQNCiMJbHB0 IHNwZWNpYWxzOg0KIwkJcG9ydCBjYW4gYmUgc3BlY2lmaWVkIGFzID8sIHRo aXMgd2lsbCBjYXVzZSB0aGUgZHJpdmVyIHRvIHNjYW4NCiMJCXRoZSBCSU9T IHBvcnQgbGlzdDsNCiMJCXRoZSBpcnEgYW5kIHZlY3RvciBjbGF1c2VzIG1h eSBiZSBvbWl0dGVkLCB0aGlzDQojCQl3aWxsIGZvcmNlIHRoZSBwb3J0IGlu dG8gcG9sbGluZyBtb2RlLg0KIyBtc2U6IExvZ2l0ZWNoIGFuZCBBVEkgSW5Q b3J0IGJ1cyBtb3VzZSBwb3J0cw0KIyBwc206IFBTLzIgbW91c2UgcG9ydCBb bm90ZTogY29uZmxpY3RzIHdpdGggc2MwL3Z0MCwgdGh1cyAiY29uZmxpY3Rz IiBrZXl3ZF0NCiMgc2lvOiBzZXJpYWwgcG9ydHMgKHNlZSBzaW8oNCkpDQoN CmRldmljZQkJbHB0MAlhdCBpc2E/IHBvcnQ/IHR0eSBpcnEgNyB2ZWN0b3Ig bHB0aW50cg0KI2RldmljZQkJbHB0MQlhdCBpc2E/IHBvcnQgIklPX0xQVDMi IHR0eSBpcnEgNSB2ZWN0b3IgbHB0aW50cg0KI2RldmljZQkJbXNlMAlhdCBp c2E/IHBvcnQgMHgyM2MgdHR5IGlycSA1IHZlY3RvciBtc2VpbnRyDQpkZXZp Y2UJCXBzbTAJYXQgaXNhPyBwb3J0ICJJT19LQkQiIGNvbmZsaWN0cyB0dHkg aXJxIDEyIHZlY3RvciBwc21pbnRyDQoNCiMNCiMgYGZsYWdzJyBmb3IgcHNt Og0KIwkweDAwMFIJc2V0IHJlc29sdXRpb24gdG8gUiAoMS4uNCkuIFNvbWUg TW91c2VTeXN0ZW1zIFBTLzIgbWljZQ0KIwkJcmVxdWlyZSB0aGlzIHZhbHVl IHRvIGJlIDQuDQojCTB4MDBOMAlzZXQgYWNjZWxhcmF0aW9uIGZhY3RvciB0 byBOICgxLi4xNSkuDQojCTB4MDEwMAlkaXNhYmxlIHN5bmNocm9uaXphdGlv biBjaGVjay4gVGhpcyByZXBsYWNlcyB0aGUgb3B0aW9uDQojCQlQU01fQ0hF Q0tTWU5DIGluIHByZXZpb3VzIHZlcnNpb25zLg0KIw0KDQojIE9wdGlvbnMg Zm9yIHBzbToNCiMjb3B0aW9ucwkJUFNNX0hPT0tBUE0JCSNob29rIHRoZSBB UE0gcmVzdW1lIGV2ZW50LCB1c2VmdWwNCgkJCQkJI2ZvciBzb21lIGxhcHRv cHMNCiNvcHRpb25zCQlQU01fUkVTRVRBRlRFUlNVU1BFTkQJI3Jlc2V0IHRo ZSBkZXZpY2UgYXQgdGhlIHJlc3VtZSBldmVudA0KDQpkZXZpY2UJCXNpbzAJ YXQgaXNhPyBwb3J0ICJJT19DT00xIiB0dHkgZmxhZ3MgMHgxMCBpcnEgNCB2 ZWN0b3Igc2lvaW50cg0KZGV2aWNlCQlzaW8xCWF0IGlzYT8gcG9ydCAiSU9f Q09NMiIgdHR5IGZsYWdzIDB4MTAgaXJxIDMgdmVjdG9yIHNpb2ludHINCiNk ZXZpY2UJCXNpbzIJYXQgaXNhPyBwb3J0ICJJT19DT00zIiB0dHkgZmxhZ3Mg MHgxMCBpcnEgNCB2ZWN0b3Igc2lvaW50ciANCg0KIw0KIyBgZmxhZ3MnIGZv ciBzZXJpYWwgZHJpdmVycyB0aGF0IHN1cHBvcnQgY29uc29sZXMgKG9ubHkg Zm9yIHNpbyBub3cpOg0KIwkweDEwCWVuYWJsZSBjb25zb2xlIHN1cHBvcnQg Zm9yIHRoaXMgdW5pdC4gIFRoZSBvdGhlciBjb25zb2xlIGZsYWdzDQojCQlh cmUgaWdub3JlZCB1bmxlc3MgdGhpcyBpcyBzZXQuICBFbmFibGluZyBjb25z b2xlIHN1cHBvcnQgZG9lcw0KIwkJbm90IG1ha2UgdGhlIHVuaXQgdGhlIHBy ZWZlcnJlZCBjb25zb2xlIC0gYm9vdCB3aXRoIC1oIG9yIHNldA0KIwkJdGhl IDB4MjAgZmxhZyBmb3IgdGhhdC4gIEN1cnJlbnRseSwgYXQgbW9zdCBvbmUg dW5pdCBjYW4gaGF2ZQ0KIwkJY29uc29sZSBzdXBwb3J0OyB0aGUgZmlyc3Qg b25lIChpbiBjb25maWcgZmlsZSBvcmRlcikgd2l0aA0KIwkJdGhpcyBmbGFn IHNldCBpcyBwcmVmZXJyZWQuICBTZXR0aW5nIHRoaXMgZmxhZyBmb3Igc2lv MCBnaXZlcw0KIwkJdGhlIG9sZCBiZWhhdmlvdXIuDQojCTB4MjAJZm9yY2Ug dGhpcyB1bml0IHRvIGJlIHRoZSBjb25zb2xlICh1bmxlc3MgdGhlcmUgaXMg YW5vdGhlcg0KIwkJaGlnaGVyIHByaW9yaXR5IGNvbnNvbGUpLiAgVGhpcyBy ZXBsYWNlcyB0aGUgQ09NQ09OU09MRSBvcHRpb24uDQojCTB4NDAJcmVzZXJ2 ZSB0aGlzIHVuaXQgZm9yIGxvdyBsZXZlbCBjb25zb2xlIG9wZXJhdGlvbnMu ICBEbyBub3QNCiMNCiMgUG5QIGBmbGFncycgKHNldCB2aWEgdXNlcmNvbmZp ZyB1c2luZyBwbnAgeCBmbGFncyB5KQ0KIwkweDEJZGlzYWJsZSBwcm9iaW5n IG9mIHRoaXMgZGV2aWNlLiAgVXNlZCB0byBwcmV2ZW50IHlvdXIgbW9kZW0N CiMJCWZyb20gYmVpbmcgYXR0YWNoZWQgYXMgYSBQblAgbW9kZW0uDQojDQoN CiMgT3B0aW9ucyBmb3Igc2VyaWFsIGRyaXZlcnMgdGhhdCBzdXBwb3J0IGNv bnNvbGVzIChvbmx5IGZvciBzaW8gbm93KToNCiNvcHRpb25zCQlCUkVBS19U T19ERUJVR0dFUgkjYSBCUkVBSyBvbiBhIGNvbWNvbnNvbGUgZ29lcyB0byAN CgkJCQkJI0REQiwgaWYgYXZhaWxhYmxlLg0KI29wdGlvbnMJCUNPTlNQRUVE PTk2MDAJCSNkZWZhdWx0IHNwZWVkIGZvciBzZXJpYWwgY29uc29sZSAoZGVm YXVsdCA5NjAwKQ0KDQojIE9wdGlvbnMgZm9yIHNpbzoNCiNvcHRpb25zCQlD T01fRVNQCQkJI2NvZGUgZm9yIEhheWVzIEVTUA0KI29wdGlvbnMJCUNPTV9N VUxUSVBPUlQJCSNjb2RlIGZvciBzb21lIGNhcmRzIHdpdGggc2hhcmVkIElS UXMNCiNvcHRpb25zCQlEU0lfU09GVF9NT0RFTQkJI2NvZGUgZm9yIERTSSBT b2Z0bW9kZW1zDQojb3B0aW9ucwkJIkVYVFJBX1NJTz0yIgkJI251bWJlciBv ZiBleHRyYSBzaW8gcG9ydHMgdG8gYWxsb2NhdGUNCg0KIyBPdGhlciBmbGFn cyBmb3Igc2lvIHRoYXQgYXJlbid0IGRvY3VtZW50ZWQgaW4gdGhlIG1hbiBw YWdlLg0KIwkweDIwMDAwCWVuYWJsZSBoYXJkd2FyZSBSVFMvQ1RTIGFuZCBs YXJnZXIgRklGT3MuICBPbmx5IHdvcmtzIGZvcg0KIwkJU1QxNjY1MEEtY29t cGF0aWJsZSBVQVJUcy4NCg0KDQojDQojIEF1ZGlvIGRyaXZlcnM6IGBzbmQn LCBgc2InLCBgcGFzJywgYGd1cycsIGBwY2EnDQojDQojIHNuZDogVm94d2Fy ZSBzb3VuZCBzdXBwb3J0IGNvZGUNCiMgc2I6IFNvdW5kQmxhc3RlciBQQ00g LSBTb3VuZEJsYXN0ZXIsIFNCIFBybywgU0IxNiwgUHJvQXVkaW9TcGVjdHJ1 bQ0KIyBjc3M6IENyeXN0YWwgU291bmQgU3lzdGVtIChDU1MgNDIzeCBQblAp DQojIG9wbDogWWFtYWhhIE9QTC0yIGFuZCBPUEwtMyBGTSAtIFNCLCBTQiBQ cm8sIFNCIDE2LCBQcm9BdWRpb1NwZWN0cnVtDQojIHVhcnQ6IHN0YW5kLWFs b25lIDY4NTAgVUFSVCBmb3IgTUlESQ0KIyBtcHU6IFJvbGFuZCBNUFUtNDAx IHN0YW5kLWFsb25lIGNhcmQNCiMgDQojIEJld2FyZSEgIFRoZSBhZGRyZXNz ZXMgc3BlY2lmaWVkIGJlbG93IGFyZSBhbHNvIGhhcmQtY29kZWQgaW4NCiMg aTM4Ni9pc2Evc291bmQvc291bmRfY29uZmlnLmguICBJZiB5b3UgY2hhbmdl IHRoZSB2YWx1ZXMgaGVyZSwgeW91DQojIG11c3QgYWxzbyBjaGFuZ2UgdGhl IHZhbHVlcyBpbiB0aGUgaW5jbHVkZSBmaWxlLg0KIw0KIyBwY206IFBDTSBh dWRpbyB0aHJvdWdoIHZhcmlvdXMgc291bmQgY2FyZHMuDQojDQojIFRoaXMg aXMgdGhlIHdvcmsgaW4gcHJvZ3Jlc3MgZnJvbSBMdWlnaSBSaXp6by4gIFRo aXMgaGFzIHN1cHBvcnQgZm9yDQojIENTNDIzeCBiYXNlZCBjYXJkcywgT1BU aTkzMSwgU0IxNiBQblAsIEd1c1BuUC4gIEZvciBtb3JlIGluZm9ybWF0aW9u DQojIGFib3V0IHRoaXMgZHJpdmVyLCB0YWtlIGEgbG9vayBhdCBzeXMvaTM4 Ni9pc2Evc25kL1JFQURNRS4NCiMNCiMgVGhlIGZsYWdzIG9mIHRoZSBkZXZp Y2UgdGVsbHMgdGhlIGRldmljZSBhIGJpdCBtb3JlIGluZm8gYWJvdXQgdGhl DQojIGRldmljZSB0aGF0IG5vcm1hbGx5IGlzIG9idGFpbmVkIHRocm91Z2gg dGhlIFBuUCBpbnRlcmZhY2UuDQojCWJpdCAgMi4uMCAgIHNlY29uZGFyeSBE TUEgY2hhbm5lbDsNCiMJYml0ICA0ICAgICAgc2V0IGlmIHRoZSBib2FyZCB1 c2VzIHR3byBkbWEgY2hhbm5lbHM7DQojCWJpdCAxNS4uOCAgIGJvYXJkIHR5 cGUsIG92ZXJyaWRlcyBhdXRvZGV0ZWN0aW9uOyBsZWF2ZSBpdA0KIwkJICAg IHplcm8gaWYgZG9uJ3Qga25vdyB3aGF0IHRvIHB1dCBpbiAoYW5kIHlvdSBk b24ndCwNCiMJCSAgICBzaW5jZSB0aGlzIGlzIHVuc3VwcG9ydGVkIGF0IHRo ZSBtb21lbnQuLi4pLg0KIw0KIyBUaGlzIGRyaXZlciB3aWxsIHVzZSB0aGUg bmV3IFBuUCBjb2RlIGlmIGl0J3MgYXZhaWxhYmxlLg0KIw0KIyBwY2E6IFBD TSBhdWRpbyB0aHJvdWdoIHlvdXIgUEMgc3BlYWtlcg0KIw0KIyBUaGUgaTM4 Ni9pc2Evc291bmQvc291bmQuZG9jIGhhcyBtb3JlIGluZm9ybWF0aW9uLg0K DQojIENvbnRyb2xzIGFsbCBzb3VuZCBkZXZpY2VzDQojY29udHJvbGxlcglz bmQwDQojZGV2aWNlIHNiMCAgICAgIGF0IGlzYT8gcG9ydCAweDIyMCBpcnEg NSBkcnEgMSB2ZWN0b3Igc2JpbnRyDQojZGV2aWNlIGNzczAJYXQgaXNhPyBw b3J0IDB4NTM0IGlycSA1IGRycSAzIGZsYWdzIDB4MDggdmVjdG9yIGFkaW50 cg0KI2RldmljZSBvcGwwICAgICBhdCBpc2E/IHBvcnQgMHgzODgNCiNkZXZp Y2UgbXB1MCAgICAgYXQgaXNhPyBwb3J0IDB4MzMwIGRycSA0DQojZGV2aWNl IHVhcnQwIGF0IGlzYT8gcG9ydCAweDMzMCBpcnEgNSB2ZWN0b3IgIm02ODUw aW50ciINCg0KIyBMdWlnaSdzIHNuZCBjb2RlDQpkZXZpY2UgcGNtMCBhdCBp c2EgPyBwb3J0IDB4NTM0IHR0eSBpcnEgNSBkcnEgMSBmbGFncyAweDEzIHZl Y3RvciBwY21pbnRyDQoNCiMgTm90IGNvbnRyb2xsZWQgYnkgYHNuZCcNCmRl dmljZSBwY2EwIGF0IGlzYT8gcG9ydCBJT19USU1FUjEgdHR5DQoNCiMNCiMg TWlzY2VsbGFuZW91cyBoYXJkd2FyZToNCiMNCiMgYmt0cjogQnQ4NDggY2Fw dHVyZSBib2FyZHMgKGh0dHA6Ly93d3cuZnJlZWJzZC5vcmcvfmZzbXAvSG9t ZUF1dG8vQnQ4NDguaHRtbCkNCg0KI2RldmljZQkJcWNhbTAJYXQgaXNhPyBw b3J0ICJJT19MUFQxIiB0dHkNCg0KDQojIGVuYWJsZSB0YWdnZWQgY29tbWFu ZCBxdWV1aW5nLCB3aGljaCBpcyBhIG1ham9yIHBlcmZvcm1hbmNlIHdpbiBv bg0KIyBkZXZpY2VzIHRoYXQgc3VwcG9ydCBpdCAoYW5kIGNvbnRyb2xsZXJz IHdpdGggZW5vdWdoIFNDQidzKQ0Kb3B0aW9ucwlBSENfVEFHRU5BQkxFDQoN CiMgZW5hYmxlIFNDQiBwYWdpbmcgLSBTZWUgdGhlIGFoYy40IG1hbiBwYWdl DQpvcHRpb25zCUFIQ19TQ0JQQUdJTkdfRU5BQkxFDQoNCiMgVGhlIGFpYzd4 eHggZHJpdmVyIHdpbGwgYXR0ZW1wdCB0byB1c2UgbWVtb3J5IG1hcHBlZCBJ L08gZm9yIGFsbCBQQ0kNCiMgY29udHJvbGxlcnMgdGhhdCBoYXZlIGl0IGNv bmZpZ3VyZWQgb25seSBpZiB0aGlzIG9wdGlvbiBpcyBzZXQuIFVuZm9ydHVu YXRlbHksDQojIHRoaXMgZG9lc24ndCB3b3JrIG9uIHNvbWUgbW90aGVyYm9h cmRzLCB3aGljaCBwcmV2ZW50cyBpdCBmcm9tIGJlaW5nIHRoZQ0KIyBkZWZh dWx0Lg0Kb3B0aW9ucyBBSENfQUxMT1dfTUVNSU8NCg0KDQojIFBDSSBkZXZp Y2VzOg0KIw0KIyBUaGUgbWFpbiBQQ0kgYnVzIGRldmljZSBpcyBgcGNpJy4g IEl0IHByb3ZpZGVzIGF1dG8tZGV0ZWN0aW9uIGFuZA0KIyBjb25maWd1cmF0 aW9uIHN1cHBvcnQgZm9yIGFsbCBkZXZpY2VzIG9uIHRoZSBQQ0kgYnVzLCB1 c2luZyBlaXRoZXINCiMgY29uZmlndXJhdGlvbiBtb2RlIGRlZmluZWQgaW4g dGhlIFBDSSBzcGVjaWZpY2F0aW9uLg0KIw0KIyBUaGUgYGFoYycgZGV2aWNl IHByb3ZpZGVzIHN1cHBvcnQgZm9yIHRoZSBBZGFwdGVjIDI5LzM5NDAoVSko VykNCiMgYW5kIG1vdGhlcmJvYXJkIGJhc2VkIEFJQzc4NzAvQUlDNzg4MCBh ZGFwdGVycy4NCiMNCiMgVGhlIGBuY3InIGRldmljZSBwcm92aWRlcyBzdXBw b3J0IGZvciB0aGUgTkNSIDUzQzgxMCBhbmQgNTNDODI1DQojIHNlbGYtY29u dGFpbmVkIFNDU0kgaG9zdCBhZGFwdGVycy4NCiMNCiMgVGhlIGBhbWQnIGRl dmljZSBwcm92aWRlcyBzdXBwb3J0IGZvciB0aGUgVGVrcmFtIERDLTM5MCBh bmQgMzkwVA0KIyBTQ1NJIGhvc3QgYWRhcHRlcnMsIGJ1dCBpcyBleHBlY3Rl ZCB0byB3b3JrIHdpdGggYW55IEFNRCA1M2M5NzQNCiMgUENJIFNDU0kgY2hp cCBhbmQgdGhlIEFNRCBFdGhlcm5ldCtTQ1NJIENvbWJvIGNoaXAsIGFmdGVy IHNvbWUNCiMgbG9jYWwgcGF0Y2hlcyB3ZXJlIGFwcGxpZWQgdG8gdGhlIHNv dXJjZXMgKHRoYXQgaGFkIG9yaWdpbmFsbHkNCiMgYmVlbiB3cml0dGVuIGJ5 IFRla3JhbSBhbmQgbGltaXRlZCB0byB3b3JrIHdpdGggdGhlaXIgU0NTSSBj YXJkcykuDQojDQojIFRoZSBgZGUnIGRldmljZSBwcm92aWRlcyBzdXBwb3J0 IGZvciB0aGUgRGlnaXRhbCBFcXVpcG1lbnQgREMyMTA0MA0KIyBzZWxmLWNv bnRhaW5lZCBFdGhlcm5ldCBhZGFwdGVyLg0KIw0KIyBUaGUgYGZ4cCcgZGV2 aWNlIHByb3ZpZGVzIHN1cHBvcnQgZm9yIHRoZSBJbnRlbCBFdGhlckV4cHJl c3MgUHJvLzEwMEINCiMgUENJIEZhc3QgRXRoZXJuZXQgYWRhcHRlcnMuDQoj DQojIFRoZSBgdHgnIGRldmljZSBwcm92aWRlcyBzdXBwb3J0IGZvciB0aGUg U01DIDk0MzJUWCBjYXJkcy4NCiMNCiMgVGhlIGB2eCcgZGV2aWNlIHByb3Zp ZGVzIHN1cHBvcnQgZm9yIHRoZSAzQ29tIDNDNTkwIGFuZCAzQzU5NQ0KIyBl YXJseSBzdXBwb3J0DQojDQojIFRoZSBgZnBhJyBkZXZpY2UgcHJvdmlkZXMg c3VwcG9ydCBmb3IgdGhlIERpZ2l0YWwgREVGUEEgUENJIEZEREkNCiMgYWRh cHRlci4gcHNldWRvLWRldmljZSBmZGRpIGlzIGFsc28gbmVlZGVkLg0KIw0K IyBUaGUgYG1ldGVvcicgZGV2aWNlIGlzIGEgUENJIHZpZGVvIGNhcHR1cmUg Ym9hcmQuIEl0IGNhbiBhbHNvIGhhdmUgdGhlDQojIGZvbGxvd2luZyBvcHRp b25zOg0KIyAgIG9wdGlvbnMgTUVURU9SX0FMTE9DX1BBR0VTPXh4eAlwcmVh bGxvY2F0ZSBrZXJuZWwgcGFnZXMgZm9yIGRhdGEgZW50cnkNCiMJZmlndXJl IChST1dTKkNPTFVNTipCWVRFU19QRVJfUElYRUwqRlJBTUUrUEFHRV9TSVpF LTEpL1BBR0VfU0laRQ0KIyAgIG9wdGlvbnMgTUVURU9SX0RFQUxMT0NfUEFH RVMJcmVtb3ZlIGFsbCBhbGxvY2F0ZWQgcGFnZXMgb24gY2xvc2UoMikNCiMg ICBvcHRpb25zIE1FVEVPUl9ERUFMTE9DX0FCT1ZFPXh4eAlyZW1vdmUgYWxs IGFsbG9jYXRlZCBwYWdlcyBhYm92ZSB0aGUNCiMJc3BlY2lmaWVkIGFtb3Vu dC4gSWYgdGhpcyB2YWx1ZSBpcyBiZWxvdyB0aGUgYWxsb2NhdGVkIGFtb3Vu dCBubyBhY3Rpb24NCiMJdGFrZW4NCiMgICBvcHRpb24gTUVURU9SX1NZU1RF TV9ERUZBVUxUPXtNRVRFT1JfUEFMfE1FVEVPUl9OVFNDfE1FVEVPUl9TRUNB TX0sIHVzZWQNCiMJZm9yIGluaXRpYWxpemF0aW9uIG9mIGZwcyByb3V0aW5l IHdoZW4gYSBzaWduYWwgaXMgbm90IHByZXNlbnQuDQojDQojIFRoZSAnYmt0 cicgZGV2aWNlIGlzIGEgUENJIHZpZGVvIGNhcHR1cmUgYm9hcmQuIEl0IGFs c28gaGFzIGEgVFYgdHVuZXINCiMgb24gYm9hcmQuDQojDQpjb250cm9sbGVy CXBjaTANCmNvbnRyb2xsZXIJYWhjMA0KZGV2aWNlCQlkZTANCmRldmljZQkJ ZnhwMA0KZGV2aWNlCQl2eDANCiNkZXZpY2UJCWJrdHIwDQoNCm9wdGlvbnMg U09GVFVQREFURVMNCg== --0-361759001-889594724=:17172-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 21:43:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20323 for freebsd-current-outgoing; Tue, 10 Mar 1998 21:43:51 -0800 (PST) (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 VAA20314 for ; Tue, 10 Mar 1998 21:43:49 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id AAA17187; Wed, 11 Mar 1998 00:42:42 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 11 Mar 1998 00:42:41 -0500 (EST) From: "Alok K. Dhir" To: hasty@rah.star-gate.com cc: current@FreeBSD.ORG Subject: Re: Amazing :-) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1483767944-889594961=:17172" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1483767944-889594961=:17172 Content-Type: TEXT/PLAIN; charset=US-ASCII It's attached... On Wed, 11 Mar 1998 hasty@rah.star-gate.com wrote: > > > If you can post the output of your dmesg . > > Tnks, > Amancio > > > > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ R7-003, ITSMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." --0-1483767944-889594961=:17172 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=dmesg Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Q29weXJpZ2h0IChjKSAxOTkyLTE5OTggRnJlZUJTRCBJbmMuDQpDb3B5cmln aHQgKGMpIDE5ODIsIDE5ODYsIDE5ODksIDE5OTEsIDE5OTMNCglUaGUgUmVn ZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmln aHRzIHJlc2VydmVkLg0KRnJlZUJTRCAzLjAtQ1VSUkVOVCAjMTA6IFR1ZSBN YXIgMTAgMjI6MTk6NTkgRVNUIDE5OTgNCiAgICBhZGhpckBzaGFkb3cud29y bGRiYW5rLm9yZzovdXNyL3NyYy9zeXMvY29tcGlsZS9TSEFET1ctU01QDQpU aW1lY291bnRlciAiaTgyNTQiICBmcmVxdWVuY3kgMTE5MzE4MiBIeiAgY29z dCAzMTIzIG5zDQpDUFU6IFBlbnRpdW0gUHJvICg2ODYtY2xhc3MgQ1BVKQ0K ICBPcmlnaW4gPSAiR2VudWluZUludGVsIiAgSWQgPSAweDYzNCAgU3RlcHBp bmc9NA0KICBGZWF0dXJlcz0weDgwZmJmZjxGUFUsVk1FLERFLFBTRSxUU0Ms TVNSLFBBRSxNQ0UsQ1g4LEFQSUMsU0VQLE1UUlIsUEdFLE1DQSxDTU9WLE1N WD4NCnJlYWwgbWVtb3J5ICA9IDI2ODQzNTQ1NiAoMjYyMTQ0SyBieXRlcykN CmF2YWlsIG1lbW9yeSA9IDI1ODM1OTI5NiAoMjUyMzA0SyBieXRlcykNCkZy ZWVCU0QvU01QOiBNdWx0aXByb2Nlc3NvciBtb3RoZXJib2FyZA0KIGNwdTAg KEJTUCk6IGFwaWMgaWQ6ICAwLCB2ZXJzaW9uOiAweDAwMDQwMDExLCBhdCAw eGZlZTAwMDAwDQogY3B1MSAoQVApOiAgYXBpYyBpZDogIDEsIHZlcnNpb246 IDB4MDAwNDAwMTEsIGF0IDB4ZmVlMDAwMDANCiBpbzAgKEFQSUMpOiBhcGlj IGlkOiAgMiwgdmVyc2lvbjogMHgwMDE3MDAxMSwgYXQgMHhmZWMwMDAwMA0K UHJvYmluZyBmb3IgZGV2aWNlcyBvbiBQQ0kgYnVzIDA6DQpjaGlwMDogPElu dGVsIDgyNDQwRlggKE5hdG9tYSkgUENJIGFuZCBtZW1vcnkgY29udHJvbGxl cj4gcmV2IDB4MDIgb24gcGNpMC4wLjANCmNoaXAxOiA8SW50ZWwgODIzNzFT QiBQQ0kgdG8gSVNBIGJyaWRnZT4gcmV2IDB4MDEgb24gcGNpMC4xMy4wDQpp ZGVfcGNpMDogPEludGVsIFBJSVgzIEJ1cy1tYXN0ZXIgSURFIGNvbnRyb2xs ZXI+IHJldiAweDAwIG9uIHBjaTAuMTMuMQ0KY2hpcDI6IDxQQ0kgdG8gUENJ IGJyaWRnZSAodmVuZG9yPTEwMTEgZGV2aWNlPTAwMjQpPiByZXYgMHgwMiBv biBwY2kwLjE0LjANCnZnYTA6IDxNYXRyb3ggTUdBIDIxNjRXIGdyYXBoaWNz IGFjY2VsZXJhdG9yPiByZXYgMHgwMCBpbnQgYSBpcnEgMTYgb24gcGNpMC4x Ni4wDQpQcm9iaW5nIGZvciBkZXZpY2VzIG9uIFBDSSBidXMgMToNCnZ4MDog PDNDT00gM0M5MDUgRmFzdCBFdGhlcmxpbmsgWEwgUENJPiByZXYgMHgwMCBp bnQgYSBpcnEgMTkgb24gcGNpMS44LjANCm1paVsqbWlpKl0gYWRkcmVzcyAw MDpjMDo0ZjphMzo1Mjo3Ng0KYWhjMDogPEFkYXB0ZWMgMjk0MCBVbHRyYSBT Q1NJIGhvc3QgYWRhcHRlcj4gcmV2IDB4MDAgaW50IGEgaXJxIDE5IG9uIHBj aTEuOS4wDQphaGMwOiBhaWM3ODgwIFdpZGUgQ2hhbm5lbCwgU0NTSSBJZD03 LCAxNi8yNTUgU0NCcw0Kc2NidXMwIGF0IGFoYzAgYnVzIDANCmFoYzA6IHRh cmdldCAwIFRhZ2dlZCBRdWV1aW5nIERldmljZQ0Kc2QwIGF0IHNjYnVzMCB0 YXJnZXQgMCBsdW4gMA0Kc2QwOiA8V0RJR1RMIFdERTQzNjAtMTgwN0EzIDEu ODA+IHR5cGUgMCBmaXhlZCBTQ1NJIDINCnNkMDogRGlyZWN0LUFjY2VzcyA0 MDk1TUIgKDgzODgzMTQgNTEyIGJ5dGUgc2VjdG9ycykNCnNkMDogd2l0aCA1 NzIwIGN5bHMsIDggaGVhZHMsIGFuZCBhbiBhdmVyYWdlIDE4MyBzZWN0b3Jz L3RyYWNrDQphaGMwOiB0YXJnZXQgMSBUYWdnZWQgUXVldWluZyBEZXZpY2UN CnNkMSBhdCBzY2J1czAgdGFyZ2V0IDEgbHVuIDANCnNkMTogPFdESUdUTCBX REU0MzYwLTE4MDdBMyAxLjgwPiB0eXBlIDAgZml4ZWQgU0NTSSAyDQpzZDE6 IERpcmVjdC1BY2Nlc3MgNDA5NU1CICg4Mzg4MzE0IDUxMiBieXRlIHNlY3Rv cnMpDQpzZDE6IHdpdGggNTcyMCBjeWxzLCA4IGhlYWRzLCBhbmQgYW4gYXZl cmFnZSAxODMgc2VjdG9ycy90cmFjaw0KYWhjMDogdGFyZ2V0IDIgVGFnZ2Vk IFF1ZXVpbmcgRGV2aWNlDQpzZDIgYXQgc2NidXMwIHRhcmdldCAyIGx1biAw DQpzZDI6IDxXRElHVEwgV0RFNDM2MC0xODA3QTMgMS44MD4gdHlwZSAwIGZp eGVkIFNDU0kgMg0Kc2QyOiBEaXJlY3QtQWNjZXNzIDQwOTVNQiAoODM4ODMx NCA1MTIgYnl0ZSBzZWN0b3JzKQ0Kc2QyOiB3aXRoIDU3MjAgY3lscywgOCBo ZWFkcywgYW5kIGFuIGF2ZXJhZ2UgMTgzIHNlY3RvcnMvdHJhY2sNCmFoYzA6 QTo1OiByZWZ1c2VzIFdJREUgbmVnb3RpYXRpb24uICBVc2luZyA4Yml0IHRy YW5zZmVycw0KY2QwIGF0IHNjYnVzMCB0YXJnZXQgNSBsdW4gMA0KY2QwOiA8 TkVDIENELVJPTSBEUklWRTo0NjQgMS4wND4gdHlwZSA1IHJlbW92YWJsZSBT Q1NJIDINCmNkMDogQ0QtUk9NIGNkIHByZXNlbnQgWzEyMDIwMSB4IDIwNDgg Ynl0ZSByZWNvcmRzXQ0KUHJvYmluZyBmb3IgUG5QIGRldmljZXM6DQpDU04g MSBWZW5kb3IgSUQ6IENTQzY4MzYgWzB4MzY2ODYzMGVdIFNlcmlhbCAweGZm ZmZmZmZmDQptc3NfYXR0YWNoIDxDUzQyMzY+MSBhdCAweDUzMCBpcnEgNSBk bWEgMTozIGZsYWdzIDB4MTMNCnBjbTEgKENTNDIzeC9ZYW1haGEgPENTNDIz Nj4gc24gMHhmZmZmZmZmZikgYXQgMHg1MzAtMHg1MzcgaXJxIDUgZHJxIDEg ZmxhZ3MgMHgxMyBvbiBpc2ENClByb2JpbmcgZm9yIGRldmljZXMgb24gdGhl IElTQSBidXM6DQpzYzAgYXQgMHg2MC0weDZmIGlycSAxIG9uIG1vdGhlcmJv YXJkDQpzYzA6IFZHQSBjb2xvciA8MTIgdmlydHVhbCBjb25zb2xlcywgZmxh Z3M9MHgwPg0KbHB0MCBhdCAweDM3OC0weDM3ZiBpcnEgNyBvbiBpc2ENCmxw dDA6IEludGVycnVwdC1kcml2ZW4gcG9ydA0KbHAwOiBUQ1AvSVAgY2FwYWJs ZSBpbnRlcmZhY2UNCnBzbTAgYXQgMHg2MC0weDY0IGlycSAxMiBvbiBtb3Ro ZXJib2FyZA0KcHNtMDogbW9kZWwgR2VuZXJpYyBQUy8yIG1vdXNlLCBkZXZp Y2UgSUQgMA0Kc2lvMCBhdCAweDNmOC0weDNmZiBpcnEgNCBmbGFncyAweDEw IG9uIGlzYQ0Kc2lvMDogdHlwZSAxNjU1MEENCnNpbzEgYXQgMHgyZjgtMHgy ZmYgaXJxIDMgZmxhZ3MgMHgxMCBvbiBpc2ENCnNpbzE6IHR5cGUgMTY1NTBB DQpwY20wIG5vdCBwcm9iZWQgZHVlIHRvIEkvTyBhZGRyZXNzIGNvbmZsaWN0 IHdpdGggcGNtMSBhdCAweDUzNA0KcGNhMCBvbiBtb3RoZXJib2FyZA0KcGNh MDogUEMgc3BlYWtlciBhdWRpbyBkcml2ZXINCmFpYzAgYXQgMHgzNDAtMHgz NWYgaXJxIDExIG9uIGlzYQ0Kc2NidXMxIGF0IGFpYzAgYnVzIDANCmNkMSBh dCBzY2J1czEgdGFyZ2V0IDQgbHVuIDANCmNkMTogPFlBTUFIQSBDRFI0MDBj IDEuMGs+IHR5cGUgNSByZW1vdmFibGUgU0NTSSAyDQpjZDE6IENELVJPTSBj YW4ndCBnZXQgdGhlIHNpemUNCndkYzAgbm90IGZvdW5kIGF0IDB4MWYwDQp3 ZGMxIG5vdCBmb3VuZCBhdCAweDE3MA0KZmRjMCBhdCAweDNmMC0weDNmNyBp cnEgNiBkcnEgMiBvbiBpc2ENCmZkYzA6IEZJRk8gZW5hYmxlZCwgOCBieXRl cyB0aHJlc2hvbGQNCmZkMDogMS40NE1CIDMuNWluDQpucHgwIG9uIG1vdGhl cmJvYXJkDQpucHgwOiBJTlQgMTYgaW50ZXJmYWNlDQpBUElDX0lPOiByb3V0 aW5nIDgyNTQgdmlhIDgyNTkgb24gcGluIDANCmNjZDAtMzogQ29uY2F0ZW5h dGVkIGRpc2sgZHJpdmVycw0KY2hhbmdpbmcgcm9vdCBkZXZpY2UgdG8gc2Qw czNhDQpTTVA6IEFQIENQVSAjMSBMYXVuY2hlZCENCmZmc19tb3VudGZzOiBz dXBlcmJsb2NrIHVwZGF0ZWQNCmZmc19tb3VudGZzOiBzdXBlcmJsb2NrIHVw ZGF0ZWQNCk9sZCBtb3VudF9tc2Rvc2ZzLCBmbGFncz0wDQo= --0-1483767944-889594961=:17172-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 21:57:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22101 for freebsd-current-outgoing; Tue, 10 Mar 1998 21:57:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22094 for ; Tue, 10 Mar 1998 21:57:34 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id NAA17854; Wed, 11 Mar 1998 13:55:48 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199803110555.NAA17854@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: peter@netplex.com.au (Peter Wemm), jdp@polstra.com, root@mantar.slip.netcom.com, current@FreeBSD.ORG Subject: Re: netscape 4.0 fails after make world In-reply-to: Your message of "Tue, 10 Mar 1998 19:06:21 GMT." <199803101906.MAA06001@usr01.primenet.com> Date: Wed, 11 Mar 1998 13:55:45 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > > GCC must change its name mangling between ELF and a.out after all. :-( > > > > > > Implementation namespace. > > > > > > This has to do with the "_" prefix. The semantics dictated by ELF > > > are different than those dictated by a.out. > > > > Actually, no, it's because gcc was accidently compiled with > > NO_DOLLAR_IN_LABEL, which came in via svr4.h. So, __vt$8stdiobuf got > > remapped to __vt.8stdiobuf - the gas that we use doesn't need this > > hand-holding (unlike the svr4 assembler), so it was fixed 2(?) days ago. > > Just recompile cc*, and libstdc++ and libg++ and this will be the way it > > was. > > Ah. I thought you were trying to Link an a.out binary dynamically > against an ELF shared library. My mistake... Funny you should mention that... There are some interesting things in the pipeline in that department.. :-) No, I'm not saying any more than that.. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 23:05:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27339 for freebsd-current-outgoing; Tue, 10 Mar 1998 23:05:32 -0800 (PST) (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 XAA27334 for ; Tue, 10 Mar 1998 23:05:31 -0800 (PST) (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.6.9) with ESMTP id XAA26180; Tue, 10 Mar 1998 23:04:27 -0800 (PST) To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. In-reply-to: Your message of "Tue, 10 Mar 1998 18:59:13 PST." <3505FE01.695678E2@whistle.com> Date: Tue, 10 Mar 1998 23:04:27 -0800 Message-ID: <26176.889599867@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We have 2 (possibly but not neccesarily related) crash scenarios, > and also a dependency tracking failure. Actually, on an SMP machine I can crash the box in 2 seconds flat. Just mount the filesystem where /usr/obj lies with soft updates enabled and ``make world''. Bye box. :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 23:07:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27789 for freebsd-current-outgoing; Tue, 10 Mar 1998 23:07:35 -0800 (PST) (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 XAA27781 for ; Tue, 10 Mar 1998 23:07:33 -0800 (PST) (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.6.9) with ESMTP id XAA26198; Tue, 10 Mar 1998 23:06:28 -0800 (PST) To: "Alok K. Dhir" cc: current@FreeBSD.ORG, Daniel Ingber Subject: Re: Amazing :-) In-reply-to: Your message of "Tue, 10 Mar 1998 22:19:49 EST." Date: Tue, 10 Mar 1998 23:06:28 -0800 Message-ID: <26195.889599988@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just enabled softupdates on all filesystems except root on my SMP > -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB RAM). > The "make world" time just went from ~6 hours to 2 hours 20 mins. That actually says more odd things about your disk layout. On The dual PII/300 box we have here with 128MB of RAM and /usr/{src,obj} striped across a 5 disk CCD (all IBM DCAS 4.3GB 5400 RPM drives), the build time is 1:25 without any sort of soft updates being used, just async mounts. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 23:30:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00600 for freebsd-current-outgoing; Tue, 10 Mar 1998 23:30:11 -0800 (PST) (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 XAA00591; Tue, 10 Mar 1998 23:30:10 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA11212; Tue, 10 Mar 1998 23:23:08 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd011210; Tue Mar 10 23:23:06 1998 Date: Tue, 10 Mar 1998 23:18:46 -0800 (PST) From: Julian Elischer To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. In-Reply-To: <26176.889599867@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can make world all day (and have for a week) on a UP P6-200 Adding a process that untars and then cleans up a copy of X11R6 makes the system crash after about N hours ( 1 < N < 12 ) Having 2 such process makes no further difference. Amancio has N where ( 1 < N < 3 ) so it's dependant on timing and other factors. On Tue, 10 Mar 1998, Jordan K. Hubbard wrote: > > We have 2 (possibly but not neccesarily related) crash scenarios, > > and also a dependency tracking failure. > > Actually, on an SMP machine I can crash the box in 2 seconds flat. > Just mount the filesystem where /usr/obj lies with soft updates > enabled and ``make world''. Bye box. :-) > > Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 23:40:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01489 for freebsd-current-outgoing; Tue, 10 Mar 1998 23:40:58 -0800 (PST) (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 XAA01481; Tue, 10 Mar 1998 23:40:54 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id XAA04756; Tue, 10 Mar 1998 23:40:51 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803110740.XAA04756@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: "Alok K. Dhir" , current@FreeBSD.ORG, Daniel Ingber Subject: Re: Amazing :-) In-reply-to: Your message of "Tue, 10 Mar 1998 23:06:28 PST." <26195.889599988@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Mar 1998 23:40:51 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I just enabled softupdates on all filesystems except root on my SMP > > -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB RAM). > > The "make world" time just went from ~6 hours to 2 hours 20 mins. > > That actually says more odd things about your disk layout. On The > dual PII/300 box we have here with 128MB of RAM and /usr/{src,obj} > striped across a 5 disk CCD (all IBM DCAS 4.3GB 5400 RPM drives), the > build time is 1:25 without any sort of soft updates being used, just > async mounts. Me seriously thinks that you need 10000 rpms disks real bad 8) Something like this: sd0: type 0 fixed SCSI 2 On a serious note if you are constantly doing "make worlds" it pays to have a very fast disk subsystem and the group can consider my note a hint 8) Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 10 23:46:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02146 for freebsd-current-outgoing; Tue, 10 Mar 1998 23:46:08 -0800 (PST) (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 XAA02137; Tue, 10 Mar 1998 23:46:05 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id XAA04791; Tue, 10 Mar 1998 23:46:01 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803110746.XAA04791@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. In-reply-to: Your message of "Tue, 10 Mar 1998 23:18:46 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Mar 1998 23:46:01 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have to echo what Julian is saying additionally if you are not prepared to give a kernel stack trace and possibly nice printfs of kernel data structures then don't try soft updates. I hate bug reports like "soft update crashed my system" 8) 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 Wed Mar 11 00:07:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03833 for freebsd-current-outgoing; Wed, 11 Mar 1998 00:07:26 -0800 (PST) (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 AAA03828; Wed, 11 Mar 1998 00:07:23 -0800 (PST) (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.6.9) with ESMTP id AAA26503; Wed, 11 Mar 1998 00:06:11 -0800 (PST) To: Amancio Hasty cc: "Jordan K. Hubbard" , "Alok K. Dhir" , current@FreeBSD.ORG, Daniel Ingber Subject: Re: Amazing :-) In-reply-to: Your message of "Tue, 10 Mar 1998 23:40:51 PST." <199803110740.XAA04756@rah.star-gate.com> Date: Wed, 11 Mar 1998 00:06:11 -0800 Message-ID: <26499.889603571@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Me seriously thinks that you need 10000 rpms disks real bad 8) Sure, send us one. :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 00:15:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05208 for freebsd-current-outgoing; Wed, 11 Mar 1998 00:15:59 -0800 (PST) (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 AAA05184; Wed, 11 Mar 1998 00:15:54 -0800 (PST) (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.6.9) with ESMTP id AAA26562; Wed, 11 Mar 1998 00:14:48 -0800 (PST) To: Amancio Hasty cc: Julian Elischer , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. In-reply-to: Your message of "Tue, 10 Mar 1998 23:46:01 PST." <199803110746.XAA04791@rah.star-gate.com> Date: Wed, 11 Mar 1998 00:14:48 -0800 Message-ID: <26558.889604088@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have to echo what Julian is saying additionally if you are not prepared > to give a kernel stack trace and possibly nice printfs of kernel data > structures then don't try soft updates. I hate bug reports like > "soft update crashed my system" 8) Oh, I never meant to imply that such wouldn't be available on request. We can reproduce the crash so easily that Julian can have all the stack traces and core dumps and kernel images that he likes, we can even put them up for anon FTP if he needs it. :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 00:17:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05666 for freebsd-current-outgoing; Wed, 11 Mar 1998 00:17:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rvc1.informatik.ba-stuttgart.de (rvc1.informatik.ba-stuttgart.de [141.31.112.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05631; Wed, 11 Mar 1998 00:17:25 -0800 (PST) (envelope-from helbig@Informatik.BA-Stuttgart.DE) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.8/8.8.5) id JAA00343; Wed, 11 Mar 1998 09:17:16 +0100 (MET) From: Wolfgang Helbig Message-Id: <199803110817.JAA00343@rvc1.informatik.ba-stuttgart.de> Subject: Re: Amazing :-) In-Reply-To: <14680.889593344@gjp.erols.com> from Gary Palmer at "Mar 11, 98 00:15:44 am" To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Wed, 11 Mar 1998 09:17:16 +0100 (MET) Cc: adhir@worldbank.org, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (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 in message ID > : > > > > I just enabled softupdates on all filesystems except root on my SMP > > -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB RAM). > > The "make world" time just went from ~6 hours to 2 hours 20 mins. > > Are you sure thats not a 486 DX2 66 in disguise? A dual 300 MHz PII > should do a make world (even with no filesystem optimization options > enabled) in under 2 hours EASILY (unless your /usr/obj is a magneto- > optical drive). 6 hours is about the par for a 486, from what I > remember of the good old days of my doing test builds of pre-2.0 on > thud.cdrom.com :) By now it's 12 hours on a 486 DX4 100. Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 00:19:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06230 for freebsd-current-outgoing; Wed, 11 Mar 1998 00:19:26 -0800 (PST) (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 AAA06216; Wed, 11 Mar 1998 00:19:20 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id JAA01243; Wed, 11 Mar 1998 09:19:08 +0100 (MET) (envelope-from sos) Message-Id: <199803110819.JAA01243@sos.freebsd.dk> Subject: Re: Amazing :-) In-Reply-To: <199803110740.XAA04756@rah.star-gate.com> from Amancio Hasty at "Mar 10, 98 11:40:51 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Wed, 11 Mar 1998 09:19:08 +0100 (MET) Cc: jkh@FreeBSD.ORG, adhir@worldbank.org, current@FreeBSD.ORG, ingber@worldbank.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 Amancio Hasty who wrote: > > > The "make world" time just went from ~6 hours to 2 hours 20 mins. > > > > That actually says more odd things about your disk layout. On The > > dual PII/300 box we have here with 128MB of RAM and /usr/{src,obj} > > striped across a 5 disk CCD (all IBM DCAS 4.3GB 5400 RPM drives), the > > build time is 1:25 without any sort of soft updates being used, just > > async mounts. > > Me seriously thinks that you need 10000 rpms disks real bad 8) > Something like this: > sd0: type 0 fixed SCSI 2 > On a serious note if you are constantly doing "make worlds" it pays to > have a very fast disk subsystem and the group can consider my note > a hint 8) Well not nessesarily, my setup is like this: Dual P6/200Mhz, 128M RAM, 2x4.3G Maxtor IDE 5200 RPM. /usr/src/ & /usr/obj on different drives, mounted async. Full make world takes 1:15-1.25 depending on how much I use the system in between, and oh, its running under X while doing this... So either the PII is a bunch'o'crap (which we allready know), or we are bound by other things than pure CPU & disk bandwidth :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Mar 11 00:31:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08444 for freebsd-current-outgoing; Wed, 11 Mar 1998 00:31:11 -0800 (PST) (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 AAA08427; Wed, 11 Mar 1998 00:31:05 -0800 (PST) (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 TAA22145; Wed, 11 Mar 1998 19:01:02 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id TAA01474; Wed, 11 Mar 1998 19:01:01 +1030 (CST) (envelope-from grog) Message-ID: <19980311190101.14276@freebie.lemis.com> Date: Wed, 11 Mar 1998 19:01:01 +1030 From: Greg Lehey To: Julian Elischer , "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. References: <26176.889599867@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Julian Elischer on Tue, Mar 10, 1998 at 11:18:46PM -0800 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 Tue, 10 March 1998 at 23:18:46 -0800, Julian Elischer wrote: > On Tue, 10 Mar 1998, Jordan K. Hubbard wrote: > >>> We have 2 (possibly but not neccesarily related) crash scenarios, >>> and also a dependency tracking failure. >> >> Actually, on an SMP machine I can crash the box in 2 seconds flat. >> Just mount the filesystem where /usr/obj lies with soft updates >> enabled and ``make world''. Bye box. :-) > > I can make world all day (and have for a week) > on a UP P6-200 > Adding a process that untars and then cleans up a copy of X11R6 > makes the system crash after about N hours ( 1 < N < 12 ) > Having 2 such process makes no further difference. > Amancio has N where ( 1 < N < 3 ) so it's dependant on > timing and other factors. I have one where I can make world until the cows come home, but if I wait much longer my nightly backup starts, and then it crashes within about half an hour. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 00:40:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09440 for freebsd-current-outgoing; Wed, 11 Mar 1998 00:40:12 -0800 (PST) (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 AAA09435; Wed, 11 Mar 1998 00:40:11 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA12509; Wed, 11 Mar 1998 00:39:14 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd012507; Wed Mar 11 00:39:09 1998 Date: Wed, 11 Mar 1998 00:34:48 -0800 (PST) From: Julian Elischer To: "Jordan K. Hubbard" cc: Amancio Hasty , current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. In-Reply-To: <26558.889604088@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For what it's worth, I didn't take Jordan's comment as a negative one, and When I'm in a position to tackle it I'm sore it will be useful. no-one expects soft-updates to be perfect ESPECIALLY on SMP quite yet.. teh thing that is getting me is that FreeBSD has diverged enough from 4.4 that we appear to have a whole new depdndency path to intercept that kirk hasn't had to deal with before.. the way I trap this is: two machines sharing a SCSI bus. one runs 'make world' every now and then the 2nd machine forces it into the kernel debugger (serial) and then does a fsck -n on the disk. When this is complete the 2nd machine allows the 1st to continue. If soft-updates were working, then there should never be any problem other than 'free blocks marked in use' or an unreferenced file. but we are seeing some that are NOT supposed to happen. (i.e the dependancies have not benn done in order). On Wed, 11 Mar 1998, Jordan K. Hubbard wrote: > > I have to echo what Julian is saying additionally if you are not prepared > > to give a kernel stack trace and possibly nice printfs of kernel data > > structures then don't try soft updates. I hate bug reports like > > "soft update crashed my system" 8) > > Oh, I never meant to imply that such wouldn't be available on request. > We can reproduce the crash so easily that Julian can have all the > stack traces and core dumps and kernel images that he likes, we can > even put them up for anon FTP if he needs it. :) > > Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 01:15:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13163 for freebsd-current-outgoing; Wed, 11 Mar 1998 01:15:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf52.cruzers.com [205.215.232.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA13136 for ; Wed, 11 Mar 1998 01:14:59 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 581 invoked by uid 100); 11 Mar 1998 09:16:06 -0000 Message-ID: <19980311011603.A562@top.worldcontrol.com> Date: Wed, 11 Mar 1998 01:16:03 -0800 To: gorski@poboxes.com, current@FreeBSD.ORG Subject: Re: Hylafax faxgetty eats 100% CPU on 3.0-980304-SNAP References: <199803102207.XAA01205@poboxes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.8i In-Reply-To: <199803102207.XAA01205@poboxes.com>; from gorski@poboxes.com on Tue, Mar 10, 1998 at 11:07:26PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On %M 0, gorski@poboxes.com wrote: > > On my 3.0-980304-SNAP the Hylafax faxgetty prg eats the whole > CPU time, but works. Does anybody has the same problem and is > there a solution? > > Thanks for information & advice. In the configure program add freebsd to the list of OSes that need O_RDWR when dealing with FIFOs. /usr/ports/comms/hylafax/work/hylafax-v4.0pl1/configure around line 1655: *-ultrix*) CONFIG_OPENFIFO=O_RDWR;; *-freebsd*) CONFIG_OPENFIFO=O_RDWR;; # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 01:32:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15497 for freebsd-current-outgoing; Wed, 11 Mar 1998 01:32:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isvara.net (root@[130.88.148.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15467 for ; Wed, 11 Mar 1998 01:32:04 -0800 (PST) (envelope-from freebsd@challenge.isvara.net) Received: from challenge.isvara.net ([130.88.66.5]) by isvara.net (8.8.7/8.8.7) with ESMTP id JAA00314 for ; Wed, 11 Mar 1998 09:31:27 GMT Message-ID: <35065A02.3C9F648@challenge.isvara.net> Date: Wed, 11 Mar 1998 09:31:46 +0000 From: freebsd@isvara.net X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: FreeBSD Current Subject: Re: Amazing :-) 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: > I just enabled softupdates on all filesystems except root on my SMP > -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB RAM). > The "make world" time just went from ~6 hours to 2 hours 20 mins. Woa! It takes my Cyrix 6x86 PR200+ (150Mhz) w/ 32MB SDRAM + 2.5GB UDMA HD about 3hrs flat with no user intervention. The FreeBSD partition is only 500MB, and is at the end of the disk, in slower recording zones! What are other people getting? Dan _____________________________________ Daniel J Blueman BSc Computation, UMIST, Manchester Email: blue@challenge.isvara.net Web: http://www.challenge.isvara.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 01:53:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA17362 for freebsd-current-outgoing; Wed, 11 Mar 1998 01:53:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hydrogen.nike.efn.org (d182-89.uoregon.edu [128.223.182.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17357 for ; Wed, 11 Mar 1998 01:53:52 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id BAA09779; Wed, 11 Mar 1998 01:53:43 -0800 (PST) Message-ID: <19980311015343.43864@hydrogen.nike.efn.org> Date: Wed, 11 Mar 1998 01:53:43 -0800 From: John-Mark Gurney To: freebsd@isvara.net Cc: FreeBSD Current Subject: Re: Amazing :-) References: <35065A02.3C9F648@challenge.isvara.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <35065A02.3C9F648@challenge.isvara.net>; from freebsd@isvara.net on Wed, Mar 11, 1998 at 09:31:46AM +0000 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 freebsd@isvara.net scribbled this message on Mar 11: > What are other people getting? I get: 6548.77 real 4071.43 user 1540.82 sys or just under one hour 50 minutes... this is with a k6/225 (75mhz bus), Bt946C w/ 1gig for /, /usr, a 2gig (95% full, async) MICROP 4421-07 0329SJ 0329 for src, and a 2gig (98% full, async) SAMSUNG WN32162U 0100 for obj... 48megs ram, 72pin simms, one bank fast page, other bank EDO (don't know which bank is which)... I'm running a PA-2007 motherboard that is based on the VIA Apollo VP2 chipset w/ 1meg L2 cache.. I am doing the buildworld on a 2.2.1-R box... command used is: make BINGRP=admin BINOWN=jmg TMACOWN=jmg TMACGRP=admin SHAREOWN=jmg SHAREGRP=admin NOINFO= NOPROFILE= NOTCL= NOTERMCAP= -j6 buildworld from make.conf: CFLAGS= -pipe -m486 -O the NOTERMCAP is a special hack as nvi uses a special syscall that doesn't exist in 2.2.1-R... I do continue to use the machine while the build is going on but the times don't vary much even though it does take about 3 seconds of processor time to save/sort my mailbox along with having to dump ~10megs to the src partition... -- 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 Mar 11 02:04:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA18798 for freebsd-current-outgoing; Wed, 11 Mar 1998 02:04:00 -0800 (PST) (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 CAA18790 for ; Wed, 11 Mar 1998 02:03:57 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id CAA03679; Wed, 11 Mar 1998 02:03:49 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803111003.CAA03679@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd@isvara.net cc: FreeBSD Current Subject: Re: Amazing :-) In-reply-to: Your message of "Wed, 11 Mar 1998 09:31:46 GMT." <35065A02.3C9F648@challenge.isvara.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Mar 1998 02:03:49 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get about hours and 30 minutes however I did not specify the async flag just the noatime . My system is PPro 200Mhz with seagate 10k rpm disk . Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 03:04:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25158 for freebsd-current-outgoing; Wed, 11 Mar 1998 03:04:47 -0800 (PST) (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 DAA25140 for ; Wed, 11 Mar 1998 03:04:14 -0800 (PST) (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 MAA27699; Wed, 11 Mar 1998 12:04:08 +0100 (MET) 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: Date: Wed, 11 Mar 1998 12:04:07 +0100 (MET) Organization: university of bayreuth From: Werner Griessl To: "Alok K. Dhir" Subject: RE: Amazing :-) Cc: Daniel Ingber , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Mar-98 Alok K. Dhir wrote: > > I just enabled softupdates on all filesystems except root on my SMP > -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB RAM). > The "make world" time just went from ~6 hours to 2 hours 20 mins. > > That is one hell of a performance increase! > > Al > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: Werner Griessl Date: 11-Mar-98 Time: 11:46:47 This message was sent by XFMail ---------------------------------- This is a "buildworld" from today on a single P-II/266 with 128MB, src=async,noatime on a 4134MB (5400rpm) on NCR(SCSI) obj=async,noatime on a 3337MB 32-bit, multi-block-32 IDE Building is with profile,without tcl,without installworld from a clean objtree. #!/bin/csh chflags -R noschg /usr/obj/* rm -rf /usr/obj/* find /usr/src/ -name obj -type l | xargs rm echo 'Begin doit.world '`date` make -DNOTCL buildworld >& world.log.`hostname -s` echo 'End doit.world '`date` Begin doit.world Wed Mar 11 10:12:11 CET 1998 End doit.world Wed Mar 11 11:42:29 CET 1998 Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 04:06:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA00496 for freebsd-current-outgoing; Wed, 11 Mar 1998 04:06:20 -0800 (PST) (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 EAA00469 for ; Wed, 11 Mar 1998 04:06:12 -0800 (PST) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.5/8.7.3) id NAA07524; Wed, 11 Mar 1998 13:08:13 +0100 (CET) Message-ID: <19980311130811.56794@cons.org> Date: Wed, 11 Mar 1998 13:08:11 +0100 From: Martin Cracauer To: Bruce Evans Cc: cracauer@cons.org, freebsd-current@FreeBSD.ORG Subject: make/SIGINT (Re: cvs commit: src/bin/sh jobs.c) References: <199802121713.EAA30328@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199802121713.EAA30328@godzilla.zeta.org.au>; from Bruce Evans on Fri, Feb 13, 1998 at 04:13:51AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199802121713.EAA30328@godzilla.zeta.org.au>, Bruce Evans wrote: > I've seen some problems with my version of the fix. The serious ones > (2-3) probably affect all versions. > > 1) When `make' of a kernel is killed by ^C, the newline to clean up > the output is printed after the shell prompt appears, so it messes > up the output. This problem doesn't occur if /bin/sh is bash-1. > > 2) Shell scripts with `make' commands in them are hard to kill. This > problem still occurs if /bin/sh is bash-1. It seems to be a bug in > `make'. According to a draft of POSIX.2, `make' shall catch SIGINT, > SIGQUIT, SIGTERM and SIGHUP in order to clean up, but it shall resend > SIGINT, SIGTERM and SIGHUP (but not necessarily SIGQUIT) to itself in > order to exit with a signal status. `make' doesn't do this (at least > in -current). Gnu make does it. > > 3) Recursive makes (e.g., of /usr/src) are very hard to kill. This seems > to be caused by the same bug in `make'. What about the appended fix for make? It seems to fix the problem for the non-compat mode of make. As our make is in compat mode by default even if -B is not given, people would have to use `make -j 1` for now to test it. What were the reasons to use compat mode by default, BTW? Anyone has test cases that fail in new mode with just one job allowed? I added a few make tests to the sh-testsuite regarding SIGINT handling, as usual at hub.freebsd.org:/home/cracauer/public_html/ or http://www.freebsd.org/~cracauer/ in directory testsuite/makestuff/ 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 diff -c make.original/job.c make.work/job.c *** make.original/job.c Tue Aug 26 12:06:38 1997 --- make.work/job.c Wed Mar 11 12:49:52 1998 *************** *** 2904,2910 **** } } (void) eunlink(tfile); ! exit(signo); } /* --- 2904,2918 ---- } } (void) eunlink(tfile); ! ! /* ! * For some signals, we don't want a direct exit, but to ! * let them resent to ourself, which is done by the calling ! * Routine. ! */ ! ! if (signo != SIGINT && signo != SIGTERM && signo != SIGHUP) ! exit(signo); } /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 05:01:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA06638 for freebsd-current-outgoing; Wed, 11 Mar 1998 05:01:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhost (user-38lcbdl.dialup.mindspring.com [209.86.45.181]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA06632 for ; Wed, 11 Mar 1998 05:01:06 -0800 (PST) (envelope-from rlb@mindspring.com) Received: from mindspring.com by mailhost with smtp (Smail3.1.29.1 #1) id m0yCl85-000FzeC; Wed, 11 Mar 98 08:01 EST Message-ID: <35068B20.86EE317B@mindspring.com> Date: Wed, 11 Mar 1998 08:01:20 -0500 From: Ron Bolin X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.6 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: Mounting root in single used mode. 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 no longer use the command "mount /" to mount root when booting up single user with the 3-10-98 current" What command do I need to use to mount root now when in single user mode. I must have missed this somewhere along the line. Thanks in advance Ron -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 05:03:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07155 for freebsd-current-outgoing; Wed, 11 Mar 1998 05:03:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhost (user-38lcbdl.dialup.mindspring.com [209.86.45.181]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA07150 for ; Wed, 11 Mar 1998 05:03:36 -0800 (PST) (envelope-from rlb@mindspring.com) Received: from mindspring.com by mailhost with smtp (Smail3.1.29.1 #1) id m0yClAV-000FzeC; Wed, 11 Mar 98 08:03 EST Message-ID: <35068BB8.2377E53D@mindspring.com> Date: Wed, 11 Mar 1998 08:03:52 -0500 From: Ron Bolin X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.6 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: Mounting root in single used mode. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forgot to say mount root in rw mode. It is already mounted in ro mode. Thanks >I can no longer use the command "mount /" to mount root when >booting up single user with the 3-10-98 current" What command >do I need to use to mount root now when in single user mode. >I must have missed this somewhere along the line. >Thanks in advance Ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 05:08:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07747 for freebsd-current-outgoing; Wed, 11 Mar 1998 05:08:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07742 for ; Wed, 11 Mar 1998 05:08:41 -0800 (PST) (envelope-from taob@tor-adm1.nbc.netcom.ca) Received: (from taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) id IAA06572; Wed, 11 Mar 1998 08:08:31 -0500 (EST) Date: Wed, 11 Mar 1998 08:08:30 -0500 (EST) From: Brian Tao X-Sender: taob@tor-adm1 To: freebsd@isvara.net cc: FreeBSD Current Subject: Re: Amazing :-) In-Reply-To: <35065A02.3C9F648@challenge.isvara.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, 11 Mar 1998 freebsd@isvara.net wrote: > > What are other people getting? *** *** make buildworld started Wed Mar 11 05:02:29 EST 1998 *** -------------------------------------------------------------- Cleaning up the temporary build tree -------------------------------------------------------------- [...] symorder -c symb.tmp tmp.o mv tmp.o wcd_mod.o *** *** make buildworld ended Wed Mar 11 06:50:07 EST 1998 *** This is on a PII-233, 96MB SDRAM, NCR53c810, single Quantum Viking 4.5GB 7200RPM ultrascsi drive, no parallel makes. /usr/{src,obj} are symlinks to /usr/local/{src,obj}. Async mounts, no soft updates. /dev/sd0s3a on / (local, writes: sync 5537 async 2076) /dev/sd0s3e on /usr (local, read-only, writes: sync 0 async 0) /dev/sd0s3h on /usr/X11R6 (asynchronous, local, writes: sync 8 async 196) /dev/sd0s3g on /usr/local (asynchronous, local, writes: sync 46058 async 61438) /dev/sd0s3f on /var (asynchronous, local, writes: sync 33042 async 3638) Personal computing power sure has come a long way. :) I remember someone posting their make world time a couple years ago, on something like a 386sx/16 with 4MB (some of that on ISA RAM boards), with NFS-mounted swap, /usr/src and /usr/obj, and it took 6 straight days to make the world. Christians now realize that their god is a 386. ;-) -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 06:09:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13864 for freebsd-current-outgoing; Wed, 11 Mar 1998 06:09:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tyree.iii.co.uk (tyree.iii.co.uk [195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13850 for ; Wed, 11 Mar 1998 06:09:41 -0800 (PST) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id OAA19807; Wed, 11 Mar 1998 14:03:38 GMT Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.7/8.8.7) id OAA29907; Wed, 11 Mar 1998 14:08:38 GMT Message-ID: <19980311140837.25123@iii.co.uk> Date: Wed, 11 Mar 1998 14:08:37 +0000 To: Ron Bolin Cc: FreeBSD Current Mailing List Subject: Re: Mounting root in single used mode. References: <35068BB8.2377E53D@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <35068BB8.2377E53D@mindspring.com>; from Ron Bolin on Wed, Mar 11, 1998 at 08:03:52AM -0500 Organization: interactive investor Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 11, 1998 at 08:03:52AM -0500, Ron Bolin wrote: > Forgot to say mount root in rw mode. It is already mounted in ro mode. # mount -u -o rw / -u = Update a currently mounted filesystem -o = options to use (in this case, 'rw'). Do % man mount for more information. N -- Work: nik@iii.co.uk | FreeBSD + Perl + Apache Rest: nik@nothing-going-on.demon.co.uk | Remind me again why we need Play: nik@freebsd.org | Microsoft? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 06:23:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15659 for freebsd-current-outgoing; Wed, 11 Mar 1998 06:23:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhost (user-38lcd68.dialup.mindspring.com [209.86.52.200]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA15643 for ; Wed, 11 Mar 1998 06:23:13 -0800 (PST) (envelope-from rlb@mindspring.com) Received: from mindspring.com by mailhost with smtp (Smail3.1.29.1 #1) id m0yCmPV-000FzxC; Wed, 11 Mar 98 09:23 EST Message-ID: <35069E5D.75137C43@mindspring.com> Date: Wed, 11 Mar 1998 09:23:25 -0500 From: Ron Bolin X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.6 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: Mounting root in single used mode. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Found the problem. Normally I do a make buildworld then build and install the new kernel. Then I boot single user, mount /, mount /usr, swapon -a, and then make installworld. Since mount must have changed, I installed the new mount b4 booting single user. Sorry for the post, I need to be more patient in looking for the answer:-) Ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 07:15:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22208 for freebsd-current-outgoing; Wed, 11 Mar 1998 07:15:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from murkwood.gaffaneys.com (dialup7.gaffaneys.com [208.155.161.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22201 for ; Wed, 11 Mar 1998 07:15:25 -0800 (PST) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by murkwood.gaffaneys.com (8.8.8/8.8.8) id JAA13761; Wed, 11 Mar 1998 09:15:07 -0600 (CST) (envelope-from zach) Message-ID: <19980311091507.60115@gaffaneys.com> Date: Wed, 11 Mar 1998 09:15:07 -0600 From: Zach Heilig To: Wolfgang Helbig Cc: current@FreeBSD.ORG Subject: Re: Amazing :-) References: <14680.889593344@gjp.erols.com> <199803110817.JAA00343@rvc1.informatik.ba-stuttgart.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803110817.JAA00343@rvc1.informatik.ba-stuttgart.de>; from Wolfgang Helbig on Wed, Mar 11, 1998 at 09:17:16AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 11, 1998 at 09:17:16AM +0100, Wolfgang Helbig wrote: > By now it's 12 hours on a 486 DX4 100. Well, it's still ~6 hours for my -current machine (dx4-133). The only "performance" option is a noasync /usr, and a 'rm -rf /usr/obj'. Everything is on a single IDE drive. -- Zach Heilig -- zach@gaffaneys.com Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 09:07:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08692 for freebsd-current-outgoing; Wed, 11 Mar 1998 09:07:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (root@duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08678; Wed, 11 Mar 1998 09:07:07 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id LAA13460; Wed, 11 Mar 1998 11:06:43 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 11 Mar 1998 11:06:43 -0600 (CST) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Amancio Hasty cc: "Jordan K. Hubbard" , "Alok K. Dhir" , current@FreeBSD.ORG, Daniel Ingber Subject: Re: Amazing :-) In-Reply-To: <199803110740.XAA04756@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 Tue, 10 Mar 1998, Amancio Hasty wrote: > > > I just enabled softupdates on all filesystems except root on my SMP > > > -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB RAM). > > > The "make world" time just went from ~6 hours to 2 hours 20 mins. > > > > That actually says more odd things about your disk layout. On The > > dual PII/300 box we have here with 128MB of RAM and /usr/{src,obj} > > striped across a 5 disk CCD (all IBM DCAS 4.3GB 5400 RPM drives), the > > build time is 1:25 without any sort of soft updates being used, just > > async mounts. > > Me seriously thinks that you need 10000 rpms disks real bad 8) > Something like this: > > sd0: type 0 fixed SCSI 2 > > On a serious note if you are constantly doing "make worlds" it pays to > have a very fast disk subsystem and the group can consider my note > a hint 8) > I think a couple of people have found out those particular 5400RPM drives are as fast (and in at least one case, faster) than some other-brand 7200RPM drives. :-) Platter rotation speed isn't the only indicator of overall speed as the manufacturers may want you to believe (though common sense tells you that faster platter rotation CAN reduce certain latencies, but obviously not in every case), -- Chris Dillon --- cdillon@inter-linc.net --- cdillon@wolves.k12.mo.us /* Powered by FreeBSD, the best operating system on the planet. Available for Intel x86 and compatible computers. SPARC and Alpha ports currently under development. (http://www.freebsd.org) */ _____________________________________________________________________ Windows 95/NT - 32 bit extensions and a graphical shell for a 16 bit | patch to an 8 bit operating system originally coded for a 4 bit | microprocessor, written by a 2 bit company that can't stand 1 bit of | competition. -UGU | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 09:41:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14797 for freebsd-current-outgoing; Wed, 11 Mar 1998 09:41:24 -0800 (PST) (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 JAA14736 for ; Wed, 11 Mar 1998 09:41:08 -0800 (PST) (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 RAA04582 for ; Wed, 11 Mar 1998 17:41:01 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id MAA00835 for freebsd-current@freebsd.org; Wed, 11 Mar 1998 12:40:59 -0500 (EST) From: Mikhail Teterin Message-Id: <199803111740.MAA00835@rtfm.ziplink.net> Subject: idprio/rtprio To: freebsd-current@FreeBSD.ORG Date: Wed, 11 Mar 1998 12:40:58 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" broken right now? I upgraded to current as of Mar 8, but only rebooted to the new kernel today. First, contrary to what the manpage says, an ordinary user can no longer run idprio. Should I file a PR? Now, something less obvious. I run rc5des (start it as myself, then make it idprio as SU). The machine slows down more then it used to under the same conditions. Top reports the rc5des' nice level as 31: CPU states: 1.1% user, 97.4% nice, 1.1% system, 0.4% interrupt, 0.0% idle Mem: 3444K Active, 38M Inact, 14M Wired, 5112K Cache, 7620K Buf, 1656K Free Swap: 96M Total, 3320K Used, 93M Free, 3% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 729 mi 101 31 1060K 292K RUN 14:53 97.35% 97.35% rc5des 424 mi 2 0 4216K 3392K select 0:54 0.38% 0.38% Xaccel 824 root 29 0 820K 760K RUN 0:00 0.84% 0.31% top 455 mi 2 0 264K 496K select 0:00 0.04% 0.04% xload Load is 1.44-1.55 -- it was at the strict 1.0 before, unless I was running something else that was cpu. hungry. My machine is Pentium 90 with 64Mb RAM. The swap is only used for 3% right now. Thanks! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 09:43:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15336 for freebsd-current-outgoing; Wed, 11 Mar 1998 09:43:03 -0800 (PST) (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 JAA15303 for ; Wed, 11 Mar 1998 09:42:55 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id MAA19032; Wed, 11 Mar 1998 12:40:55 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 11 Mar 1998 12:40:54 -0500 (EST) From: "Alok K. Dhir" To: hasty@rah.star-gate.com cc: freebsd@isvara.net, current@FreeBSD.ORG Subject: Re: Amazing :-) 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 Wed, 11 Mar 1998 hasty@rah.star-gate.com wrote: > I get about hours and 30 minutes however I did not specify the async > flag just the noatime . > My system is PPro 200Mhz with seagate 10k rpm disk . How many hours? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 09:43:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15359 for freebsd-current-outgoing; Wed, 11 Mar 1998 09:43:09 -0800 (PST) (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 JAA15302 for ; Wed, 11 Mar 1998 09:42:55 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id MAA19011; Wed, 11 Mar 1998 12:40:02 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 11 Mar 1998 12:40:02 -0500 (EST) From: "Alok K. Dhir" To: gurney_j@efn.org cc: freebsd@isvara.net, current@FreeBSD.ORG Subject: Re: Amazing :-) In-Reply-To: <63FE1A19B2D07E24852565C40036C106.0035DF8B852565C4@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 On Wed, 11 Mar 1998 gurney_j@efn.org wrote: > or just under one hour 50 minutes... this is with a k6/225 (75mhz bus), > Bt946C w/ 1gig for /, /usr, a 2gig (95% full, async) MICROP 4421-07 > 0329SJ 0329 for src, and a 2gig (98% full, async) SAMSUNG WN32162U 0100 > for obj... 48megs ram, 72pin simms, one bank fast page, other bank EDO > (don't know which bank is which)... I'm running a PA-2007 motherboard > that is based on the VIA Apollo VP2 chipset w/ 1meg L2 cache.. > > I am doing the buildworld on a 2.2.1-R box... I'm going to hazard a guess here that 3.0-current is larger than 2.2... -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ R7-003, ITSMC 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 Wed Mar 11 09:43:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15345 for freebsd-current-outgoing; Wed, 11 Mar 1998 09:43:05 -0800 (PST) (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 JAA15304 for ; Wed, 11 Mar 1998 09:42:55 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id MAA19049; Wed, 11 Mar 1998 12:42:24 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 11 Mar 1998 12:42:23 -0500 (EST) From: "Alok K. Dhir" To: rlb@mindspring.com cc: freebsd-current@FreeBSD.ORG Subject: Re: Mounting root in single used mode. In-Reply-To: <4D361389F2D62CF9852565C40047FFBA.00473E2E852565C4@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 Try "mount -u /"... On Wed, 11 Mar 1998 rlb@mindspring.com wrote: > > > Forgot to say mount root in rw mode. It is already mounted in ro mode. > Thanks > > > >I can no longer use the command "mount /" to mount root when > >booting up single user with the 3-10-98 current" What command > >do I need to use to mount root now when in single user mode. > >I must have missed this somewhere along the line. > > >Thanks in advance > > Ron > > > > > 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 \ R7-003, ITSMC 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 Wed Mar 11 10:03:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20491 for freebsd-current-outgoing; Wed, 11 Mar 1998 10:03:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20451 for ; Wed, 11 Mar 1998 10:03:19 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id LAA22230 for ; Wed, 11 Mar 1998 11:03:18 -0700 (MST) Message-Id: <199803111803.LAA22230@pluto.plutotech.com> Date: Wed, 11 Mar 1998 11:00:08 -0700 From: "Justin T. Gibbs" Subject: CAM testimonials? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: undisclosed-recipients:; ------- Blind-Carbon-Copy X-Mailer: exmh version 2.0.1 12/23/97 To: scsi@FreeBSD.org Subject: CAM testimonials? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Mar 1998 11:00:08 -0700 From: "Justin T. Gibbs" I haven't gotten much feedback on the latest CAM snapshot. If you are running CAM, I'd appreciate a small note listing your configuration along with any other comments you have. Thanks! - -- Justin ------- End of Blind-Carbon-Copy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 10:04:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21008 for freebsd-current-outgoing; Wed, 11 Mar 1998 10:04:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa2-01.ix.netcom.com [206.214.137.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20945 for ; Wed, 11 Mar 1998 10:04:45 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id KAA00541; Wed, 11 Mar 1998 10:04:40 -0800 (PST) (envelope-from tomdean) Date: Wed, 11 Mar 1998 10:04:40 -0800 (PST) Message-Id: <199803111804.KAA00541@ix.netcom.com> From: Thomas Dean To: current@FreeBSD.ORG In-reply-to: (message from Brian Tao on Wed, 11 Mar 1998 08:08:30 -0500 (EST)) Subject: Re: Amazing :-) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD ocupies all of sd1. >df Filesystem 1M-blocks Used Avail Capacity Mounted on /dev/sd1s1a 37 20 13 59% / /dev/sd1s1f 2617 1896 511 79% /usr /dev/sd1s1e 105 2 94 3% /var procfs 0 0 0 100% /proc I use make -j4 world. It takes about 6 hours. If I use -j12, make hangs. make world started on Sun Mar 8 20:41:42 PST 1998 ... make world completed on Mon Mar 9 02:38:32 PST 1998 ====== dmesg ================= Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #4: Tue Mar 10 15:30:47 PST 1998 root@celebris:/usr/src/sys/compile/CELEBRIS-SMP Timecounter "i8254" frequency 1193182 Hz cost 2527 ns CPU: Pentium (586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x3bf real memory = 33554432 (32768K bytes) avail memory = 30384128 (29672K 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: routing 8254 via 8259 on pin 0 changing root device to sd1s2a SMP: AP CPU #1 Launched! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 10:13:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22993 for freebsd-current-outgoing; Wed, 11 Mar 1998 10:13:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA22983 for ; Wed, 11 Mar 1998 10:12:50 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Wed, 11 Mar 1998 13:11:40 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA28864; Wed, 11 Mar 98 13:11:36 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id NAA15968; Wed, 11 Mar 1998 13:11:29 -0500 Message-Id: <19980311131129.14004@ct.picker.com> Date: Wed, 11 Mar 1998 13:11:29 -0500 From: Randall Hopper To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: HEADS UP! (was: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c) Mail-Followup-To: Mike Smith , current@freebsd.org References: <199803081506.HAA06931@freefall.freebsd.org> <199803081518.HAA10644@dingo.cdrom.com> <19980309100806.34950@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980309100806.34950@freebie.lemis.com>; from Greg Lehey on Mon, Mar 09, 1998 at 10:08:07AM +1030 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey: |On Sun, 8 March 1998 at 7:18:50 -0800, Mike Smith wrote: |>> Construct the minor number for the root device taking into account the |>> slice number passed in by the bootblocks. This means the kernel will |>> not use the compatability slice to obtain the root filesystem when |>> booting from a sliced disk. ... |> /dev/xd0s2a / ufs ... |> /dev/xd0s2e /usr ufs ... |> |> Note that the root filesystem is now consistent with the others. If |> you are using a 'dedicated' disk, you will have entries like Great! Been looking forward to someday putting multiple FreeBSD versions on the same disk for a good while. With this batch of changes, can multiple FreeBSD versions now be installed pretty effortlessly to separate slices on the same disk, or are there other pieces out there (which depend on the 1st BSD root partition) that will need touched first? Thanks, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 10:34:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28022 for freebsd-current-outgoing; Wed, 11 Mar 1998 10:34:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27931; Wed, 11 Mar 1998 10:33:58 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id TAA01345; Wed, 11 Mar 1998 19:30:08 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.7) id TAA16860; Wed, 11 Mar 1998 19:21:04 +0100 (CET) (envelope-from andreas) Message-ID: <19980311192103.05566@klemm.gtn.com> Date: Wed, 11 Mar 1998 19:21:03 +0100 From: Andreas Klemm To: ports@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: New XFree86 port: .....o: Undefined symbol `_panic' referenced from text segment Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When trying to install XFree86 this problem came up. -current related ? rm -f XF86Setup cc -o XF86Setup -O2 -ansi -pedantic -Dasm=__asm -L../../../../../exports/lib main.o tclmisc.o tclvidmode.o tclcards.o tclother.o tclkbd.o tclxfconf.o xf86Config.o cards.o tclxkbui.o tkother.o -lxkbui -lxkbfile -Wl,-Bstatic -L/usr/local/lib -ltk41 -Wl,-Bdynamic -Wl,-Bstatic -L/usr/local/lib -ltcl75 -Wl,-Bdynamic -lXxf86vm -lXxf86misc -lXaw -lXmu -L../../../../../exports/lib -lXt -lX11 -lXt -lSM -lICE -lXext -lX11 -lm -L/usr/X11R6/lib -Wl,-R,/usr/X11R6/lib tkUnixWm.o: Undefined symbol `_panic' referenced from text segment tkUnixWm.o: Undefined symbol `_panic' referenced from text segment tkUnixWm.o: Undefined symbol `_panic' referenced from text segment tkUnixWm.o: Undefined symbol `_panic' referenced from text segment tkFrame.o: Undefined symbol `_panic' referenced from text segment tkVisual.o: Undefined symbol `_panic' referenced from text segment tkVisual.o: Undefined symbol `_panic' referenced from text segment tk3d.o: Undefined symbol `_panic' referenced from text segment tk3d.o: Undefined symbol `_panic' referenced from text segment tkGC.o: More undefined symbol _panic refs follow *** Error code 1 -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 10:49:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03522 for freebsd-current-outgoing; Wed, 11 Mar 1998 10:49:31 -0800 (PST) (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 KAA03505 for ; Wed, 11 Mar 1998 10:49:23 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id NAA26056; Wed, 11 Mar 1998 13:48:40 -0500 (EST) From: Peter Dufault Message-Id: <199803111848.NAA26056@hda.hda.com> Subject: Re: idprio/rtprio In-Reply-To: <199803111740.MAA00835@rtfm.ziplink.net> from Mikhail Teterin at "Mar 11, 98 12:40:58 pm" To: mi@aldan.algebra.com (Mikhail Teterin) Date: Wed, 11 Mar 1998 13:48:39 -0500 (EST) Cc: 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 > Is the broken right now? > > I upgraded to current as of Mar 8, but only rebooted to the new > kernel today. > > First, contrary to what the manpage says, an ordinary user can no > longer run idprio. > > Should I file a PR? The code comment shows that is done on purpose to avoid priority inversion. > Now, something less obvious. I run rc5des (start it as myself, then > make it idprio as SU). The machine slows down more then it used to > under the same conditions. Top reports the rc5des' nice level as 31: > > CPU states: 1.1% user, 97.4% nice, 1.1% system, 0.4% interrupt, 0.0% idle > Mem: 3444K Active, 38M Inact, 14M Wired, 5112K Cache, 7620K Buf, 1656K Free > Swap: 96M Total, 3320K Used, 93M Free, 3% Inuse > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 729 mi 101 31 1060K 292K RUN 14:53 97.35% 97.35% rc5des > 424 mi 2 0 4216K 3392K select 0:54 0.38% 0.38% Xaccel > 824 root 29 0 820K 760K RUN 0:00 0.84% 0.31% top > 455 mi 2 0 264K 496K select 0:00 0.04% 0.04% xload > > Load is 1.44-1.55 -- it was at the strict 1.0 before, unless I was > running something else that was cpu. hungry. > I broke it at 1.47 of kern_synch - idle priority processes are not getting preempted until the next round robin interval instead of as soon as a higher priority process is runnable. I did this locally a while ago so I have to dig up why I added that test to only do need_resched for the same type of process. Eliminating that check in maybe_resched for the scheduler types should set things back the way they were. I'll run a few tests with that off and see why I added it. 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 Mar 11 11:04:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07999 for freebsd-current-outgoing; Wed, 11 Mar 1998 11:04:16 -0800 (PST) (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 LAA07985 for ; Wed, 11 Mar 1998 11:04:08 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id LAA29402; Wed, 11 Mar 1998 11:03:59 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803111903.LAA29402@rah.star-gate.com> cc: "Alok K. Dhir" , hasty@rah.star-gate.com, freebsd@isvara.net, current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Amazing :-) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29399.889643039.1@rah> Date: Wed, 11 Mar 1998 11:03:59 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am sorry . I redid make world with async,noatime and it takes 1:15 minutes to do a make world and I had X running on my system mount /dev/sd0a on / (local) devfs on dummy_mount (local) /dev/sd0f on /usr (asynchronous, NFS exported, local, noatime) /dev/sd0e on /var (local) procfs on /proc (local) CPU is PPro 200Mhz with 96MB of memory scsi controller adpatec 2940UW disk : sd0: type 0 fixed SCSI 2 thats a 4gig 10000rpm disk really good to record live yuv streams for mpeg encoding 8) My mods to /etc/make.conf: NOCLEAN=true CFLAGS= -O -pipe NOPROFILE= true It is not clear that with a faster i/o subsystem that we will get much better times. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 11:08:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09006 for freebsd-current-outgoing; Wed, 11 Mar 1998 11:08:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08983 for ; Wed, 11 Mar 1998 11:08:23 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id OAA04188; Wed, 11 Mar 1998 14:08:11 -0500 (EST) (envelope-from wollman) Date: Wed, 11 Mar 1998 14:08:11 -0500 (EST) From: Garrett Wollman Message-Id: <199803111908.OAA04188@khavrinen.lcs.mit.edu> To: Amancio Hasty Cc: "Alok K. Dhir" , freebsd@isvara.net, current@FreeBSD.ORG Subject: Re: Amazing :-) In-Reply-To: <199803111903.LAA29402@rah.star-gate.com> References: <199803111903.LAA29402@rah.star-gate.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > My mods to /etc/make.conf: > NOCLEAN=true > NOPROFILE= true In the WorldStone race, that's cheating. I could compile faster, too, if I left out a third of the libraries. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 11:30:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14798 for freebsd-current-outgoing; Wed, 11 Mar 1998 11:30:21 -0800 (PST) (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 LAA14728 for ; Wed, 11 Mar 1998 11:30:04 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: (from hasty@localhost) by rah.star-gate.com (8.8.8/8.8.8) id LAA29537 for current@freebsd.org; Wed, 11 Mar 1998 11:30:03 -0800 (PST) (envelope-from hasty) Date: Wed, 11 Mar 1998 11:30:03 -0800 (PST) From: Amancio Hasty Message-Id: <199803111930.LAA29537@rah.star-gate.com> To: current@FreeBSD.ORG Subject: my worldstone Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't consider cheating if I post my mods to my make.conf and I do consider them reasonable given thats what I use here in my system. Last but not least I am not in a world stone race because I don't have a system suitable to compete. Different topic, It will be nice if people with very fast systems and i/o subsystems to post their world stone. It has been alluded in the past that we have a bottle neck in the system we seem to hover around 100 minutes. For instance, Simon Shapiro posted in the past that increasing the i/o subsystem like by using a DPT couple with fast disks didn't seem to improve his relative world stone benchmark. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 11:33:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15749 for freebsd-current-outgoing; Wed, 11 Mar 1998 11:33:33 -0800 (PST) (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 LAA15693 for ; Wed, 11 Mar 1998 11:33:18 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id OAA27454; Wed, 11 Mar 1998 14:31:43 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 11 Mar 1998 14:31:43 -0500 (EST) From: "Alok K. Dhir" To: hasty@rah.star-gate.com cc: freebsd@isvara.net, current@FreeBSD.ORG Subject: Re: Amazing :-) 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 What is a profiled library, BTW? Thanks... On Wed, 11 Mar 1998 hasty@rah.star-gate.com wrote: > My mods to /etc/make.conf: > NOCLEAN=true > CFLAGS= -O -pipe > NOPROFILE= true To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 11:36:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17095 for freebsd-current-outgoing; Wed, 11 Mar 1998 11:36:53 -0800 (PST) (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 LAA17031 for ; Wed, 11 Mar 1998 11:36:39 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id OAA27473; Wed, 11 Mar 1998 14:35:32 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 11 Mar 1998 14:35:32 -0500 (EST) From: "Alok K. Dhir" To: lamaster@george.arc.nasa.gov cc: current@FreeBSD.ORG Subject: Re: Amazing :-) 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 Wed, 11 Mar 1998 lamaster@george.arc.nasa.gov wrote: > Or, here is another idea: somehow your disk geometry (translated > rather than CHS I assume) is wrong performance-wise: that is, > perhaps the translation is such that the disk thrashes? I believe > that may have happened to me once when I had a setup with a small > DOS partition on my drive and used translation. I now always use > a dedicated FreeBSD boot disk with CHS addressing and the "true" geometry. This could be, I suppose. Thanks... Here's the fdisk output of my root/usr disk: ******* Working on device /dev/rsd0 ******* parameters extracted from in-core disklabel are: cylinders=522 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=522 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 6,(Primary 'big' DOS (> 32MB)) start 63, size 2056257 (1004 Meg), flag 80 beg: cyl 0/ sector 1/ head 1; end: cyl 127/ sector 63/ head 254 The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 2056320, size 6329610 (3090 Meg), flag 0 beg: cyl 128/ sector 1/ head 0; end: cyl 521/ sector 63/ head 254 The data for partition 3 is: The data for partition 4 is: And here's the disklabel, if it matters: # /dev/rsd0c: type: SCSI disk: sd0s2 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 394 sectors/unit: 6329610 rpm: 7200 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 409600 0 4.2BSD 0 0 0 # (Cyl. 0 - 25*) b: 524288 409600 swap # (Cyl. 25*- 58*) c: 6329610 0 unused 0 0 # (Cyl. 0 - 393) e: 5395722 933888 4.2BSD 0 0 0 # (Cyl. 58*- 393*) -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ R7-003, ITSMC 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 Wed Mar 11 11:40:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18517 for freebsd-current-outgoing; Wed, 11 Mar 1998 11:40:45 -0800 (PST) (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 LAA18449 for ; Wed, 11 Mar 1998 11:40:16 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id NAA27575; Wed, 11 Mar 1998 13:39:58 -0600 (CST) From: Kevin Day Message-Id: <199803111939.NAA27575@home.dragondata.com> Subject: Re: my worldstone In-Reply-To: <199803111930.LAA29537@rah.star-gate.com> from Amancio Hasty at "Mar 11, 98 11:30:03 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Wed, 11 Mar 1998 13:39:57 -0600 (CST) 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 > > It will be nice if people with very fast systems and i/o subsystems to > post their world stone. It has been alluded in the past that we have > a bottle neck in the system we seem to hover around 100 minutes. For > instance, Simon Shapiro posted in the past that increasing the i/o > subsystem like by using a DPT couple with fast disks didn't seem > to improve his relative world stone benchmark. > yy As a point of reference: My dual PII/333, two 10000 rpm 4G ultra wide scsi drives, each on their own adaptec controller(/usr/src in one, and obj in the other), 256M Ram, and no other tasks running still took around one hour 45 minutes to complete a make buildworld -j4. Is it just memory bandwidth we're hitting? Putting both directories one drive slightly slowed things down.... Same with going to a UP kernel. But nowhere near the differences it made on a similar dual P/200. This system is my main 'work' machine, that isn't usually running fbsd. If anyone has anything they want me to try on it, next time I load it up, let me know. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 11:44:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19746 for freebsd-current-outgoing; Wed, 11 Mar 1998 11:44:21 -0800 (PST) (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 LAA19551 for ; Wed, 11 Mar 1998 11:43:55 -0800 (PST) (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 UAA04070; Wed, 11 Mar 1998 20:42:54 +0100 (CET) To: "Alok K. Dhir" cc: hasty@rah.star-gate.com, freebsd@isvara.net, current@FreeBSD.ORG Subject: Re: Amazing :-) In-reply-to: Your message of "Wed, 11 Mar 1998 14:31:43 EST." Date: Wed, 11 Mar 1998 20:42:53 +0100 Message-ID: <4068.889645373@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Alok K. Dhir" writes: > >What is a profiled library, BTW? A library compiled with -p (man cc!) -- 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 Wed Mar 11 11:51:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22293 for freebsd-current-outgoing; Wed, 11 Mar 1998 11:51:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA22160 for ; Wed, 11 Mar 1998 11:50:54 -0800 (PST) (envelope-from dyson@iquest.net) From: dyson@iquest.net Received: (qmail 15873 invoked from network); 11 Mar 1998 19:50:45 -0000 Received: from iquest7.iquest.net (206.53.230.110) by iquest3.iquest.net with SMTP; 11 Mar 1998 19:50:45 -0000 Received: (qmail 19669 invoked by uid 4420); 11 Mar 1998 19:50:46 -0000 Message-ID: <19980311195045.19668.qmail@iquest7.iquest.net> Subject: Re: Softupdates code not Prime Time yet. To: hasty@rah.star-gate.com (Amancio Hasty) Date: Wed, 11 Mar 1998 14:50:45 -0500 (EST) Cc: julian@whistle.com, jkh@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199803110746.XAA04791@rah.star-gate.com> from "Amancio Hasty" at Mar 10, 98 11:46:01 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 to echo what Julian is saying additionally if you are not prepared > to give a kernel stack trace and possibly nice printfs of kernel data > structures then don't try soft updates. I hate bug reports like > "soft update crashed my system" 8) > Pretty much the same with the VM and NFS stuff that I have been working on. Please, whenever you have problems with the kernel, a traceback and other such information is very useful. Alot of traffic for the VM and NFS stuff happens in the background, where the groups don't see it... People who know the issues about working on the kernel, also generally know that a statement about a crash without any kind of information is useless, and often just gets ignored. IF one sends the output of a panic only, without the appropriate portion of the namelist, the info is useless. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 11:53:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23294 for freebsd-current-outgoing; Wed, 11 Mar 1998 11:53:50 -0800 (PST) (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 LAA23180 for ; Wed, 11 Mar 1998 11:53:24 -0800 (PST) (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 LAA24155; Wed, 11 Mar 1998 11:50:53 -0800 (PST) Message-Id: <199803111950.LAA24155@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Randall Hopper cc: Mike Smith , current@FreeBSD.ORG Subject: Re: HEADS UP! (was: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c) In-reply-to: Your message of "Wed, 11 Mar 1998 13:11:29 EST." <19980311131129.14004@ct.picker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Mar 1998 11:50:52 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > With this batch of changes, can multiple FreeBSD versions now be installed > pretty effortlessly to separate slices on the same disk, or are there other > pieces out there (which depend on the 1st BSD root partition) that will need > touched first? The bootstrap needs to be taught how to parse the slice number, perhaps in an extended syntax such as xd(unit,slice,part)kernel although it would make more sense to me to switch to eg. sd0s1a:/kernel. (This isn't going to happen in the short term though; too much backwards-compatability grief.) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 11:55:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23788 for freebsd-current-outgoing; Wed, 11 Mar 1998 11:55:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt050ndd.san.rr.com (root@dt050ndd.san.rr.com [204.210.31.221]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23676 for ; Wed, 11 Mar 1998 11:54:53 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (dougdougdougdoug@localhost [127.0.0.1]) by dt050ndd.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA02876; Wed, 11 Mar 1998 11:54:36 -0800 (PST) (envelope-from Studded@dal.net) Message-ID: <3506EBFC.2636AF67@dal.net> Date: Wed, 11 Mar 1998 11:54:36 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-BETA-0310 i386) MIME-Version: 1.0 To: Amancio Hasty CC: current@FreeBSD.ORG Subject: Re: my worldstone References: <199803111930.LAA29537@rah.star-gate.com> 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: > Different topic, > > It will be nice if people with very fast systems and i/o subsystems to > post their world stone. If you're interested in -Stable stats: PII 266, 128M Ram, Maxtor 72004 AP IDE drive /usr (including src and obj) mounted noatime,async rm -rf /usr/obj/* cvsup'ed -Stable on 3 March CFLAGS= -0 -pipe make -DCLOBBER -DNOPROFILE -DNOCLEAN -DNOPERL world Elapsed Time: 1:01 Hope this helps, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (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 Wed Mar 11 11:57:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24475 for freebsd-current-outgoing; Wed, 11 Mar 1998 11:57:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hydrogen.nike.efn.org (d182-89.uoregon.edu [128.223.182.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24343 for ; Wed, 11 Mar 1998 11:57:08 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id LAA13506; Wed, 11 Mar 1998 11:56:46 -0800 (PST) Message-ID: <19980311115645.13975@hydrogen.nike.efn.org> Date: Wed, 11 Mar 1998 11:56:45 -0800 From: John-Mark Gurney To: "Alok K. Dhir" Cc: freebsd@isvara.net, current@FreeBSD.ORG Subject: Re: Amazing :-) References: <63FE1A19B2D07E24852565C40036C106.0035DF8B852565C4@worldbank.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Alok K. Dhir on Wed, Mar 11, 1998 at 12:40:02PM -0500 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 Alok K. Dhir scribbled this message on Mar 11: > On Wed, 11 Mar 1998 gurney_j@efn.org wrote: > > > or just under one hour 50 minutes... this is with a k6/225 (75mhz bus), > > Bt946C w/ 1gig for /, /usr, a 2gig (95% full, async) MICROP 4421-07 > > 0329SJ 0329 for src, and a 2gig (98% full, async) SAMSUNG WN32162U 0100 > > for obj... 48megs ram, 72pin simms, one bank fast page, other bank EDO > > (don't know which bank is which)... I'm running a PA-2007 motherboard > > that is based on the VIA Apollo VP2 chipset w/ 1meg L2 cache.. > > > > I am doing the buildworld on a 2.2.1-R box... > > I'm going to hazard a guess here that 3.0-current is larger than 2.2... nope, these are -current sources as of about March 2 or so... it's just that my main machine runs 2.2.1-R, but it builds -current source.. it's either that or my 486/66dx2... :) -- 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 Mar 11 12:03:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26529 for freebsd-current-outgoing; Wed, 11 Mar 1998 12:03:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA26454 for ; Wed, 11 Mar 1998 12:03:05 -0800 (PST) (envelope-from dyson@iquest.net) From: dyson@iquest.net Received: (qmail 23524 invoked from network); 11 Mar 1998 20:03:01 -0000 Received: from iquest7.iquest.net (206.53.230.110) by iquest3.iquest.net with SMTP; 11 Mar 1998 20:03:01 -0000 Received: (qmail 20016 invoked by uid 4420); 11 Mar 1998 20:03:02 -0000 Message-ID: <19980311200302.20015.qmail@iquest7.iquest.net> Subject: Re: Softupdates code not Prime Time yet. To: julian@whistle.com (Julian Elischer) Date: Wed, 11 Mar 1998 15:03:01 -0500 (EST) Cc: jkh@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: from "Julian Elischer" at Mar 10, 98 11:18: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 > > > We have 2 (possibly but not neccesarily related) crash scenarios, > > > and also a dependency tracking failure. > > > > Actually, on an SMP machine I can crash the box in 2 seconds flat. > > Just mount the filesystem where /usr/obj lies with soft updates > > enabled and ``make world''. Bye box. :-) > > > The -current system has undergone some progression, but also some regression. I am going to do another marathon bug-fix session this weekend. I am not sure that all of the problems are due to the softupdates code, but maybe it is tickling some other problems. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 12:14:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29497 for freebsd-current-outgoing; Wed, 11 Mar 1998 12:14:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c243.moon.jic.com [206.156.18.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29480 for ; Wed, 11 Mar 1998 12:14:22 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id PAA16400; Wed, 11 Mar 1998 15:14:02 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Amancio Hasty cc: current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: my worldstone In-reply-to: Your message of "Wed, 11 Mar 1998 11:30:03 PST." <199803111930.LAA29537@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Mar 1998 15:14:02 -0500 Message-ID: <16396.889647242@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote in message ID <199803111930.LAA29537@rah.star-gate.com>: > It will be nice if people with very fast systems and i/o subsystems to > post their world stone. It has been alluded in the past that we have > a bottle neck in the system we seem to hover around 100 minutes. For > instance, Simon Shapiro posted in the past that increasing the i/o > subsystem like by using a DPT couple with fast disks didn't seem > to improve his relative world stone benchmark. Probably memory or processor busses. As far as I know none of the current high end systems interleave memory to improve accesses. I think the Orion P6 chipset was the last that allowed interleaving? It would certainly be interesting to see how fast a dual PII 300MHz with fast disks and plenty of RAM could do... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 12:28:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01745 for freebsd-current-outgoing; Wed, 11 Mar 1998 12:28:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from george.arc.nasa.gov (george.arc.nasa.gov [128.102.194.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01739 for ; Wed, 11 Mar 1998 12:28:07 -0800 (PST) (envelope-from lamaster@george.arc.nasa.gov) Received: (from lamaster@localhost) by george.arc.nasa.gov (8.8.7/8.8.7) id MAA18435; Wed, 11 Mar 1998 12:23:14 -0800 (PST) From: Hugh LaMaster Message-Id: <199803112023.MAA18435@george.arc.nasa.gov> Subject: Re: my worldstone To: current@FreeBSD.ORG Date: Wed, 11 Mar 1998 12:23:13 -0800 (PST) Cc: lamaster@george.arc.nasa.gov In-Reply-To: <199803111939.NAA27575@home.dragondata.com> from "Kevin Day" at Mar 11, 98 01:39:57 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It will be nice if people with very fast systems and i/o subsystems to > > post their world stone. It has been alluded in the past that we have > > a bottle neck in the system we seem to hover around 100 minutes. For BTW, I notice some folks posting "make world" and others "make buildworld". What are the "official" parameters for "world stone"? > > instance, Simon Shapiro posted in the past that increasing the i/o > > subsystem like by using a DPT couple with fast disks didn't seem > > to improve his relative world stone benchmark. > > > yy > As a point of reference: > > My dual PII/333, two 10000 rpm 4G ultra wide scsi drives, each on their own ^^^^^^^ What chipset? I assume LX chipset, because I don't think the Natoma boards for PII were supposed to go over 300 MHz, but, you could be overclocking. How much memory? What memory? SDRAM? w/ ECC? Are the memory timings set properly for SDRAM in the BIOS? (x-1-1-1 with SDRAM?). > adaptec controller(/usr/src in one, and obj in the other), 256M Ram, and no > other tasks running still took around one hour 45 minutes to complete a make > buildworld -j4. Curiously, for me this (that is, "make buildworld") was ~ 2 hrs 30 minutes for me on a PPro 200, Natoma chipset (ASUS P/I-6NP5 I think it was - I don't remember the exact model number) with 3.0-current, in January. "make installworld" added another ~1/2 hour. I don't have the system anymore, or exact timings. PPro200, Natoma, 64 MB FP parity DRAM with parity enabled Buslogic BT-958 SCSI controller Quantum Atlas 4.x GB disk - 1 disk, everything on it, filesystems synchronous 3.0-Current as of mid-January, 1998. Since this system has pretty bad write bandwidth, I assume that its relatively good performance on "world stone" is due to the low-latency L2 cache. > Is it just memory bandwidth we're hitting? Putting both directories one > drive slightly slowed things down.... Same with going to a UP kernel. But > nowhere near the differences it made on a similar dual P/200. Write memory bandwidth should be significantly better on the PII/333 than PPro200. L1 cache is bigger, faster, L2 cache is bigger, *slower*. Significantly longer latency. According to the specs. Could the longer L2 cache latency hurt PII/333 performance that much? On some other benchmarks, PII/233 - PII/266 on Natoma seems roughly the somewhere around ~ PPro200. PII/333 on LX "should" be way faster. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 12:40:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03927 for freebsd-current-outgoing; Wed, 11 Mar 1998 12:40:22 -0800 (PST) (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 MAA03902 for ; Wed, 11 Mar 1998 12:40:14 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA28099; Wed, 11 Mar 1998 12:38:48 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd028093; Wed Mar 11 12:38:44 1998 Message-ID: <3506F54D.41C67EA6@whistle.com> Date: Wed, 11 Mar 1998 12:34:21 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Amancio Hasty CC: current@FreeBSD.ORG Subject: Re: my worldstone References: <199803111930.LAA29537@rah.star-gate.com> 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: > > It will be nice if people with very fast systems and i/o subsystems to > post their world stone. It has been alluded in the past that we have > a bottle neck in the system we seem to hover around 100 minutes. For > instance, Simon Shapiro posted in the past that increasing the i/o > subsystem like by using a DPT couple with fast disks didn't seem > to improve his relative world stone benchmark. Though I'd like to see the result with soft-updates added to the mix. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 12:58:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06850 for freebsd-current-outgoing; Wed, 11 Mar 1998 12:58:28 -0800 (PST) (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 MAA06836 for ; Wed, 11 Mar 1998 12:58:20 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id VAA00325; Wed, 11 Mar 1998 21:57:40 +0100 (MET) (envelope-from sos) Message-Id: <199803112057.VAA00325@sos.freebsd.dk> Subject: Re: my worldstone In-Reply-To: <3506F54D.41C67EA6@whistle.com> from Julian Elischer at "Mar 11, 98 12:34:21 pm" To: julian@whistle.com (Julian Elischer) Date: Wed, 11 Mar 1998 21:57:40 +0100 (MET) Cc: hasty@rah.star-gate.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 Julian Elischer who wrote: > Amancio Hasty wrote: > > > > It will be nice if people with very fast systems and i/o subsystems to > > post their world stone. It has been alluded in the past that we have > > a bottle neck in the system we seem to hover around 100 minutes. For > > instance, Simon Shapiro posted in the past that increasing the i/o > > subsystem like by using a DPT couple with fast disks didn't seem > > to improve his relative world stone benchmark. > > > Though I'd like to see the result with soft-updates added to the mix. Not possible on SMP systems... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Mar 11 12:58:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06895 for freebsd-current-outgoing; Wed, 11 Mar 1998 12:58:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isvara.net (root@[130.88.148.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06837 for ; Wed, 11 Mar 1998 12:58:21 -0800 (PST) (envelope-from freebsd@challenge.isvara.net) Received: from challenge.isvara.net ([130.88.66.5]) by isvara.net (8.8.7/8.8.7) with ESMTP id UAA01640 for ; Wed, 11 Mar 1998 20:57:52 GMT Message-ID: <3506FAE0.21094C16@challenge.isvara.net> Date: Wed, 11 Mar 1998 20:58:08 +0000 From: freebsd@isvara.net X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: FreeBSD Current Subject: Re: Amazing :-) References: <14680.889593344@gjp.erols.com> 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 have a number of questions/points: 1. It would be interesting to recent, standard, untuned 'make world' and compare the times for different processors, I/O subsystems. This would give us a good idea of what platform is ideal as a compiling machine, etc. 2. Doesn't make use timestamps (updating killed with 'noatime') for compiling (ie. seeing what is changed)? 3. What does CFLAGS= -pipe do in the make.conf file? 4. Can we tweak the CFLAGS= -m486 for out CPU-class? 5. Can we specify -O2 instead of -O (ie. what order of performance increase be)? 6. What is NOCLEAN=true & NOPROFILE=true ? (I know what they will kinda do, but how will it affect resultant 'world') Any answers to these would be nice, Dan _____________________________________ Daniel J Blueman BSc Computation, UMIST, Manchester Email: blue@challenge.isvara.net Web: http://www.challenge.isvara.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 12:59:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07260 for freebsd-current-outgoing; Wed, 11 Mar 1998 12:59:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mynet.ml.org (pc-19628.on.rogers.wave.ca [24.112.74.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07244 for ; Wed, 11 Mar 1998 12:59:38 -0800 (PST) (envelope-from ihuang@mynet.ml.org) Received: from localhost (ihuang@localhost) by mynet.ml.org (8.8.7/8.8.6) with SMTP id PAA17730; Wed, 11 Mar 1998 15:58:34 -0500 (EST) Date: Wed, 11 Mar 1998 15:58:34 -0500 (EST) From: Ian Huang To: freebsd@isvara.net cc: FreeBSD Current Subject: Re: Amazing :-) In-Reply-To: <35065A02.3C9F648@challenge.isvara.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 my Cyrix PR166 overclocked to 200, it takes just under 3 hours, even with a 2-year-old Quantum Fireball 1200AT(IDE). I have 64MB SDRAM though. On Wed, 11 Mar 1998 freebsd@isvara.net wrote: > Alok K. Dhir wrote: > > > I just enabled softupdates on all filesystems except root on my SMP > > -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB > RAM). > > The "make world" time just went from ~6 hours to 2 hours 20 mins. > > Woa! It takes my Cyrix 6x86 PR200+ (150Mhz) w/ 32MB SDRAM + 2.5GB UDMA > HD > about 3hrs flat with no user intervention. The FreeBSD partition is only > > 500MB, and is at the > end of the disk, in slower recording zones! > > What are other people getting? > > Dan > > _____________________________________ > Daniel J Blueman > BSc Computation, UMIST, Manchester > Email: blue@challenge.isvara.net > Web: http://www.challenge.isvara.net/ > > > > 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 Mar 11 13:01:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07799 for freebsd-current-outgoing; Wed, 11 Mar 1998 13:01:11 -0800 (PST) (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 NAA07741 for ; Wed, 11 Mar 1998 13:00:56 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id QAA26544; Wed, 11 Mar 1998 16:00:31 -0500 (EST) From: Peter Dufault Message-Id: <199803112100.QAA26544@hda.hda.com> Subject: Re: idprio/rtprio In-Reply-To: <199803111740.MAA00835@rtfm.ziplink.net> from Mikhail Teterin at "Mar 11, 98 12:40:58 pm" To: mi@aldan.algebra.com (Mikhail Teterin) Date: Wed, 11 Mar 1998 16:00:30 -0500 (EST) Cc: 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 > Load is 1.44-1.55 -- it was at the strict 1.0 before, unless I was > running something else that was cpu. hungry. I had forgotten aobut idprio processes. I duplicated the problem and committed the fix I sent you off line. With a process coming ready randomly in the time slice, the load average would have averaged out to 1.50. Now it is back to 1.0. Thanks, 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 Mar 11 13:30:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14062 for freebsd-current-outgoing; Wed, 11 Mar 1998 13:30:28 -0800 (PST) (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 NAA14034 for ; Wed, 11 Mar 1998 13:30:18 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA29658 for ; Wed, 11 Mar 1998 13:22:29 -0800 (PST) Received: from UNKNOWN(), claiming to be "crab.whistle.com" via SMTP by alpo.whistle.com, id smtpd029654; Wed Mar 11 13:22:27 1998 Received: (from ambrisko@localhost) by crab.whistle.com (8.8.8/8.6.12) id NAA15073 for freebsd-current@freebsd.org; Wed, 11 Mar 1998 13:20:54 -0800 (PST) From: Doug Ambrisko Message-Id: <199803112120.NAA15073@crab.whistle.com> Subject: Netboot problem: RPC timeout for server 0x0 To: freebsd-current@FreeBSD.ORG Date: Wed, 11 Mar 1998 13:20:54 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL29 (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'm having trouble with the netboot stuff. I can boot 2.2.5, and -current kernel as of ~1 month ago, but every since last week any kernel I build starts displaying RPC timeout for server 0x0 contiously. When it should be trying to mount the rootfs. I recall someone making a change, but couldn't test it. Does anyboby remember and can point me in the right direction? I tried search some CVS logs & the mailing lists and haven't found it yet. So I'm going to dig some more. I wanted to test out some of the NFS changes, since I was having a panic with a netbooted machine when it started to do compiles etc. Thanks, Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 13:46:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18517 for freebsd-current-outgoing; Wed, 11 Mar 1998 13:46:26 -0800 (PST) (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 NAA18449; Wed, 11 Mar 1998 13:46:08 -0800 (PST) (envelope-from jmz@cabri.obs-besancon.fr) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA18564; Wed, 11 Mar 98 22:49:42 +0100 Date: Wed, 11 Mar 98 22:49:42 +0100 Message-Id: <9803112149.AA18564@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: andreas@klemm.gtn.com Cc: ports@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <19980311192103.05566@klemm.gtn.com> (message from Andreas Klemm on Wed, 11 Mar 1998 19:21:03 +0100) Subject: Re: New XFree86 port: .....o: Undefined symbol `_panic' referenced from text segment X-Mailer: Emacs Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Andreas Klemm writes: > When trying to install XFree86 this problem came up. > -current related ? Not -current related because I don't see this: rm -f XF86Setup cc -o XF86Setup -O2 -ansi -pedantic -Dasm=__asm -L../../../../../exports/lib main.o tclmisc.o tclvidmode.o tclcards.o tclother.o tclkbd.o tclx fconf.o xf86Config.o cards.o tclxkbui.o tkother.o -lxkbui -lxkbfile -Wl,-Bstatic -L/usr/local/lib -ltk42 -Wl,-Bdynamic -Wl,-Bstatic -L/usr/local/lib -ltcl76 -Wl,-Bdynamic -lXxf86vm -lXxf86misc lXaw -lXmu -L../../../../../exports/lib -lXt -lX11 -lXt -lSM -lICE -lXext -lX11 -lm -L/usr/X11R6/lib -Wl,-R,/usr/X11R6/lib making all in programs/Xserver/hw/xfree86/XF86Setup/scripts... > rm -f XF86Setup > cc -o XF86Setup -O2 -ansi -pedantic -Dasm=__asm -L../../../../../exports/lib main.o tclmisc.o tclvidmode.o tclcards.o tclother.o tclkbd.o tclxfconf.o xf86Config.o cards.o tclxkbui.o tkother.o -lxkbui -lxkbfile -Wl,-Bstatic -L/usr/local/lib -ltk41 -Wl,-Bdynamic -Wl,-Bstatic -L/usr/local/lib -ltcl75 -Wl,-Bdynamic -lXxf86vm -lXxf86misc -lXaw -lXmu -L../../../../../exports/lib -lXt -lX11 -lXt -lSM -lICE -lXext -lX11 -lm -L/usr/X11R6/lib -Wl,-R,/usr/X11R6/lib > tkUnixWm.o: Undefined symbol `_panic' referenced from text segment > tkUnixWm.o: Undefined symbol `_panic' referenced from text segment > tkUnixWm.o: Undefined symbol `_panic' referenced from text segment > tkUnixWm.o: Undefined symbol `_panic' referenced from text segment > tkFrame.o: Undefined symbol `_panic' referenced from text segment > tkVisual.o: Undefined symbol `_panic' referenced from text segment > tkVisual.o: Undefined symbol `_panic' referenced from text segment > tk3d.o: Undefined symbol `_panic' referenced from text segment > tk3d.o: Undefined symbol `_panic' referenced from text segment > tkGC.o: More undefined symbol _panic refs follow > *** Error code 1 The difference I see is that you are linking with tk4.1/tcl7.5 where I have tk4.2/tcl7.6 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 Wed Mar 11 14:11:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24250 for freebsd-current-outgoing; Wed, 11 Mar 1998 14:11:34 -0800 (PST) (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 OAA24241; Wed, 11 Mar 1998 14:11:29 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA01396; Wed, 11 Mar 1998 14:01:26 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd001389; Wed Mar 11 14:01:17 1998 Message-ID: <350708A7.167EB0E7@whistle.com> Date: Wed, 11 Mar 1998 13:56:55 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: dyson@iquest.net CC: jkh@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. References: <19980311200302.20015.qmail@iquest7.iquest.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dyson@iquest.net wrote: > > > > > We have 2 (possibly but not neccesarily related) crash scenarios, > > > > and also a dependency tracking failure. > > > > > > Actually, on an SMP machine I can crash the box in 2 seconds flat. > > > Just mount the filesystem where /usr/obj lies with soft updates > > > enabled and ``make world''. Bye box. :-) > > > > > > The -current system has undergone some progression, but also some > regression. I am going to do another marathon bug-fix session > this weekend. I am not sure that all of the problems are due > to the softupdates code, but maybe it is tickling some other > problems. > > John John, I believe you ar ehere in the bay area.. if you need a realy well equiped debugging setup, with as many machines as you need, then I can set you up here at whistle. (besides we should go have pizza) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 14:26:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27087 for freebsd-current-outgoing; Wed, 11 Mar 1998 14:26:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27054 for ; Wed, 11 Mar 1998 14:26:40 -0800 (PST) (envelope-from bsdcur@shadows.aeon.net) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.8/8.8.3) id AAA19544 for current@freebsd.org; Thu, 12 Mar 1998 00:28:40 +0200 (EET) From: mika ruohotie Message-Id: <199803112228.AAA19544@shadows.aeon.net> Subject: Re: Amazing :-) In-Reply-To: <14680.889593344@gjp.erols.com> from Gary Palmer at "Mar 11, 98 00:15:44 am" To: current@FreeBSD.ORG Date: Thu, 12 Mar 1998 00:28:40 +0200 (EET) 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 > > -current machine (dual 300Mhz Pentium II, Adaptec 2940UW SCSI, 256MB RAM). > > The "make world" time just went from ~6 hours to 2 hours 20 mins. > Are you sure thats not a 486 DX2 66 in disguise? A dual 300 MHz PII > should do a make world (even with no filesystem optimization options > enabled) in under 2 hours EASILY (unless your /usr/obj is a magneto- uh. in the days i had 486/33 it took some 36 hours to make a world on my eide drive system. i think it got bit better with drive updates, to somewhere around 20 hours. that was in the days of 2.2-current. then i got p75 and it went to 7 hours, then i got p133 and it was 6 and it went down to 5 when i replaced 256 async cache with 512 pipeline. it was already 3.0-current with the pentiums. then i got different setups (at work mostly) and fastest i've seen was a while ago with pro200, 1:20 with ccd:ed filesystems and asyncs. currently my p6/208 (83 bus, ofcourse) makes it around 2 hours with an eide drive and async. scsi pII262.5 (75 bus) wasnt that much faster, even tho the disk is fastest i've seen, WD 9GB UW. soonish i get to benchmark pII 290.5 (83 bus) but not until i get that scsi-to-scsi raid system (onboard uw into which it'll connect) mickey ps. while i'm posting, chat doesnt let me to re-join myself into it, been that way ever since the major crash a while ago To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 14:58:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02269 for freebsd-current-outgoing; Wed, 11 Mar 1998 14:58:47 -0800 (PST) (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 OAA02260 for ; Wed, 11 Mar 1998 14:58:45 -0800 (PST) (envelope-from jmz@cabri.obs-besancon.fr) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA18945; Thu, 12 Mar 98 00:02:35 +0100 Date: Thu, 12 Mar 98 00:02:35 +0100 Message-Id: <9803112302.AA18945@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: current@FreeBSD.ORG Subject: unresolved c++ symbols X-Mailer: Emacs Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Was not this problem solved? I just did 'make all && make installworld' and I still have errors from the loader. What needs to be reinstalled? 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 Wed Mar 11 15:07:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03337 for freebsd-current-outgoing; Wed, 11 Mar 1998 15:07:41 -0800 (PST) (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 PAA03317 for ; Wed, 11 Mar 1998 15:07:28 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.8.8/8.8.7) with SMTP id SAA09847; Wed, 11 Mar 1998 18:07:20 -0500 (EST) Date: Wed, 11 Mar 1998 18:07:20 -0500 (EST) From: jack To: Amancio Hasty cc: current@FreeBSD.ORG Subject: Re: my worldstone In-Reply-To: <199803111930.LAA29537@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 Wed, 11 Mar 1998, Amancio Hasty wrote: > It will be nice if people with very fast systems and i/o subsystems to > post their world stone. It has been alluded in the past that we have > a bottle neck in the system we seem to hover around 100 minutes. For > instance, Simon Shapiro posted in the past that increasing the i/o > subsystem like by using a DPT couple with fast disks didn't seem > to improve his relative world stone benchmark. If you don't object to stable, cvsup'ed this morning. PPro200 (actually an overclocked 180), 96 megs EDO RAM, 2940UW, /usr/src on a Seagate ST31055W, /usr/obj on an IBM DCAS-34330W both mounted noatime async. /etc/make.conf CFLAGS= -O -pipe utmp.h and param.h edited for 16 character usernames make world 1 hour 44 minutes P133, 32 megs parity RAM, adatec 1542, /usr/src and /usr/obj on different 5400 rpm Seagate spindles, no mount options, no /etc/make.conf changes, same include file changes make world ~4 hours and counting. Final figures tomorrow, I'm going home. :) -------------------------------------------------------------------------- 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 Wed Mar 11 15:14:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05112 for freebsd-current-outgoing; Wed, 11 Mar 1998 15:14:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04999; Wed, 11 Mar 1998 15:13:52 -0800 (PST) (envelope-from bsd-curr@artorius.sunflower.com) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by artorius.sunflower.com (8.8.8/8.8.7) with SMTP id RAA04553; Wed, 11 Mar 1998 17:12:56 -0600 (CST) (envelope-from bsd-curr@artorius.sunflower.com) Date: Wed, 11 Mar 1998 17:12:55 -0600 (CST) From: "Stephen D. Spencer" To: "Justin T. Gibbs" cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: CAM testimonials? In-Reply-To: <199803111803.LAA22230@pluto.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Mar 1998, Justin T. Gibbs wrote: > > I haven't gotten much feedback on the latest CAM snapshot. If you are > running CAM, I'd appreciate a small note listing your configuration along > with any other comments you have. > rev 0x00 int a irq 11 on pci0.11.0 da3: Fixed Direct Access SCSI2 device da2: Fixed Direct Access SCSI2 device da1: Fixed Direct Access SCSI2 device da0: Fixed Direct Access SCSI2 device cd0: Removable CD-ROM SCSI2 device motherboard is an Asus TX w/ 64 Mb SDRAM DIMM, AMD-200MMX, 4Mb s3/virge, gus-pnp, blah blah blah... Um... it flies? ;) No problems whatsoever. As with the last snapshot, performance improvements are extremely noticable. I will be borrowing an HP DAT to test on that system in a couple days. Thanks for the fantastic work! Regards, Stephen --------------------------------------------------------------------- - Stephen Spencer finger gladiatr@artorius.sunflower.com for - - administrator PGP key. - - Sunflower Datavision http://www.sunflower.com - --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 15:53:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11192 for freebsd-current-outgoing; Wed, 11 Mar 1998 15:53:28 -0800 (PST) (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 PAA11167 for ; Wed, 11 Mar 1998 15:52:51 -0800 (PST) (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 BAA17283 for ; Thu, 12 Mar 1998 01:52:39 +0200 (EET) 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 BAA00271 for ; Thu, 12 Mar 1998 01:52:38 +0200 (EET) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.8.8/8.8.8/8.Who.Cares) with UUCP id BAA10759 for current@freebsd.org; Thu, 12 Mar 1998 01:46:03 +0200 (EET) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id BAA02402; Thu, 12 Mar 1998 01:32:38 +0200 (EET) (envelope-from archer) Date: Thu, 12 Mar 1998 01:32:38 +0200 (EET) From: Alexander Litvin Message-Id: <199803112332.BAA02402@grape.carrier.kiev.ua> To: current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. X-Newsgroups: grape.freebsd.current In-Reply-To: <19980311195045.19668.qmail@iquest7.iquest.net> 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 <19980311195045.19668.qmail@iquest7.iquest.net> you wrote: >> >> I have to echo what Julian is saying additionally if you are not prepared >> to give a kernel stack trace and possibly nice printfs of kernel data >> structures then don't try soft updates. I hate bug reports like >> "soft update crashed my system" 8) >> > Pretty much the same with the VM and NFS stuff that I have been > working on. Please, whenever you have problems with the kernel, > a traceback and other such information is very useful. Alot > of traffic for the VM and NFS stuff happens in the background, > where the groups don't see it... People who know the issues > about working on the kernel, also generally know that a statement > about a crash without any kind of information is useless, and > often just gets ignored. > IF one sends the output of a panic only, without the appropriate > portion of the namelist, the info is useless. Sorry, but it would be much easier if it were possible to boot stripped kernels. > John > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Alexander Litvin 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 Wed Mar 11 15:58:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12026 for freebsd-current-outgoing; Wed, 11 Mar 1998 15:58:41 -0800 (PST) (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 PAA12013 for ; Wed, 11 Mar 1998 15:58:33 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id AAA02105 for current@FreeBSD.ORG; Thu, 12 Mar 1998 00:58:25 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id AAA13563; Thu, 12 Mar 1998 00:42:16 +0100 (CET) (envelope-from roberto) Message-ID: <19980312004215.A13486@keltia.freenix.fr> Date: Thu, 12 Mar 1998 00:42:15 +0100 From: Ollivier Robert To: FreeBSD Current Subject: Re: Amazing :-) Mail-Followup-To: FreeBSD Current References: <14680.889593344@gjp.erols.com> <3506FAE0.21094C16@challenge.isvara.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <3506FAE0.21094C16@challenge.isvara.net>; from freebsd@isvara.net on Wed, Mar 11, 1998 at 08:58:08PM +0000 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4121 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to freebsd@isvara.net: > 2. Doesn't make use timestamps (updating killed with 'noatime') for > compiling (ie. seeing what is changed)? It uses mtime (modification time), not atime (access time). Access time has a very limited interest for some things. > 3. What does CFLAGS= -pipe do in the make.conf file? Get rid of temporary files for gcc/cpp/cc1 by using pipes. > 4. Can we tweak the CFLAGS= -m486 for out CPU-class? I don't know what you really mean by this but you can use pgcc to compile the world for better processors (Pentium, Pentium Pro, K6 & Cyrix). > 5. Can we specify -O2 instead of -O (ie. what order of performance > increase > be)? Compilation time will increase while running time should decrease but it is very difficult to evaluate... > 6. What is NOCLEAN=true & NOPROFILE=true ? > (I know what they will kinda do, but how will it affect resultant 'world') NOCLEAN will avoid a potentially long "rm -rf" operation (unless you use softupdates :-)). NOPROFILE will avoid recompiling all the libraries with '-p' for profiling purposes. With the same settings as Amancio (NOCLEAN & NOPROFILE but an empty /usr/obj) I get _1h20_ on my K6-225, 64 MB, all disks on a SC-875 (ultra wide), /usr/src on a DCAS-34330W (async,noatime) and /usr/obj on a DORS-32160 (async,noatime). sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: WIDE SCSI (16 bit) enabled sd0: 40.0 MB/s (50 ns, offset 15) 4134MB (8467200 512 byte sectors) sd2 at scbus0 target 2 lun 0 sd2: type 0 fixed SCSI 2 sd2: Direct-Access sd2: 20.0 MB/s (50 ns, offset 15) 2063MB (4226725 512 byte sectors) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 15:58:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12069 for freebsd-current-outgoing; Wed, 11 Mar 1998 15:58:51 -0800 (PST) (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 PAA12041 for ; Wed, 11 Mar 1998 15:58:45 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id AAA02106 for current@FreeBSD.ORG; Thu, 12 Mar 1998 00:58:42 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id AAA13572; Thu, 12 Mar 1998 00:44:03 +0100 (CET) (envelope-from roberto) Message-ID: <19980312004403.B13486@keltia.freenix.fr> Date: Thu, 12 Mar 1998 00:44:03 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Amazing :-) Mail-Followup-To: current@FreeBSD.ORG References: <14680.889593344@gjp.erols.com> <199803112228.AAA19544@shadows.aeon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <199803112228.AAA19544@shadows.aeon.net>; from mika ruohotie on Thu, Mar 12, 1998 at 12:28:40AM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4121 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to mika ruohotie: > uh. in the days i had 486/33 it took some 36 hours to make a world > on my eide drive system. i think it got bit better with drive > updates, to somewhere around 20 hours. 20 hours ? My DX33 was around 9h50 in 2.2 days (ok, I had 2 SCSI controllers and already used async...). 4h50 when I upgraded to a 486DX4/100. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 15:59:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12220 for freebsd-current-outgoing; Wed, 11 Mar 1998 15:59:19 -0800 (PST) (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 PAA12086 for ; Wed, 11 Mar 1998 15:58:55 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id AAA02108 for current@FreeBSD.ORG; Thu, 12 Mar 1998 00:58:53 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id AAA13588; Thu, 12 Mar 1998 00:49:23 +0100 (CET) (envelope-from roberto) Message-ID: <19980312004923.C13486@keltia.freenix.fr> Date: Thu, 12 Mar 1998 00:49:23 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: my worldstone Mail-Followup-To: current@FreeBSD.ORG References: <199803111930.LAA29537@rah.star-gate.com> <3506F54D.41C67EA6@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <3506F54D.41C67EA6@whistle.com>; from Julian Elischer on Wed, Mar 11, 1998 at 12:34:21PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4121 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Julian Elischer: > Though I'd like to see the result with soft-updates added to the mix. I tried this at work but with an empty /usr/obj (so it will create and expand my directories), it panic'ed during it. Sorry... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 16:49:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20767 for freebsd-current-outgoing; Wed, 11 Mar 1998 16:49:22 -0800 (PST) (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 QAA20722 for ; Wed, 11 Mar 1998 16:49:17 -0800 (PST) (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 LAA23069; Thu, 12 Mar 1998 11:18:59 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id LAA06081; Thu, 12 Mar 1998 11:18:58 +1030 (CST) (envelope-from grog) Message-ID: <19980312111858.40450@freebie.lemis.com> Date: Thu, 12 Mar 1998 11:18:58 +1030 From: Greg Lehey To: Alexander Litvin , current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. References: <19980311195045.19668.qmail@iquest7.iquest.net> <199803112332.BAA02402@grape.carrier.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803112332.BAA02402@grape.carrier.kiev.ua>; from Alexander Litvin on Thu, Mar 12, 1998 at 01:32:38AM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 March 1998 at 1:32:38 +0200, Alexander Litvin wrote: > In article <19980311195045.19668.qmail@iquest7.iquest.net> you wrote: >>> >>> I have to echo what Julian is saying additionally if you are not prepared >>> to give a kernel stack trace and possibly nice printfs of kernel data >>> structures then don't try soft updates. I hate bug reports like >>> "soft update crashed my system" 8) >>> >> Pretty much the same with the VM and NFS stuff that I have been >> working on. Please, whenever you have problems with the kernel, >> a traceback and other such information is very useful. Alot >> of traffic for the VM and NFS stuff happens in the background, >> where the groups don't see it... People who know the issues >> about working on the kernel, also generally know that a statement >> about a crash without any kind of information is useless, and >> often just gets ignored. > >> IF one sends the output of a panic only, without the appropriate >> portion of the namelist, the info is useless. > > Sorry, but it would be much easier if it were possible to > boot stripped kernels. I don't think there's any particular problem with booting stripped kernels (modulo some problems reported with strip recently). But I agree wholeheartedly that bug fixing is a pain without a minumum of information. What do people say about making something like this a policy? 1. Build a kernel with debugging avaialable. 2. Enable dumps. 3. If you wish, strip the kernel before booting, but keep the debug version in /var/crash for later analysis. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 17:04:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22912 for freebsd-current-outgoing; Wed, 11 Mar 1998 17:04:27 -0800 (PST) (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 RAA22906 for ; Wed, 11 Mar 1998 17:04:24 -0800 (PST) (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 BAA07325; Thu, 12 Mar 1998 01:02:58 GMT Date: Thu, 12 Mar 1998 10:02:58 +0900 (JST) From: Michael Hancock To: dave adkins cc: current@FreeBSD.ORG Subject: Re: ext2_sync and NULL inode and VNON v_type 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 You can just OR it into the check below it for a more canonical fix. if ((vp->v_type == VNON) || ((ip->i_flag & Make this patch and post it so some ext2 fs users can test it. Mike Hancock On Tue, 10 Mar 1998, dave adkins wrote: > In current as of 980310, a r/w mounted ext2 filesystem panics on the first > sync. This happens when a vnode of type VNON with ip == NULL is processed. > > I have added a test for a v_type of VNON in ext2_sync(). > > if (VOP_ISLOCKED(vp)) > continue; > + if ( vp->v_type == VNON ) > + continue; > ip = VTOI(vp); > if (ip == NULL) { > > > I haven't yet tried writing to the mounted file system with this patch. > > dave adkins > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- michaelh@cet.co.jp http://www.cet.co.jp CET Inc., Daiichi Kasuya BLDG 8F, 2-5-12 Higashi Shinbashi, Minato-ku, Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 17:19:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25381 for freebsd-current-outgoing; Wed, 11 Mar 1998 17:19:16 -0800 (PST) (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 RAA25344 for ; Wed, 11 Mar 1998 17:19:08 -0800 (PST) (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 BAA27226 for ; Thu, 12 Mar 1998 01:19:06 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id CAA26024; Thu, 12 Mar 1998 02:19:06 +0100 (MET) Message-ID: <19980312021906.27780@follo.net> Date: Thu, 12 Mar 1998 02:19:06 +0100 From: Eivind Eklund To: current@FreeBSD.ORG Subject: Request for objections: 'make regress' 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 This probably goes in tomorrow unless someone protests. Added bonus: Included with the introduction is a _free_ regression test for the LKMs symbol resolving. :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 17:32:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28317 for freebsd-current-outgoing; Wed, 11 Mar 1998 17:32:28 -0800 (PST) (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 RAA28305 for ; Wed, 11 Mar 1998 17:32:27 -0800 (PST) (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.6.9) with ESMTP id RAA01103; Wed, 11 Mar 1998 17:31:24 -0800 (PST) To: Mikhail Teterin cc: freebsd-current@FreeBSD.ORG Subject: Re: idprio/rtprio In-reply-to: Your message of "Wed, 11 Mar 1998 12:40:58 EST." <199803111740.MAA00835@rtfm.ziplink.net> Date: Wed, 11 Mar 1998 17:31:24 -0800 Message-ID: <1099.889666284@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > First, contrary to what the manpage says, an ordinary user can no > longer run idprio. It's the man page that's wrong since this was disallowed awhile back after BEST Internet filed a PR noting that an ordinary user could put your system in very bad shape by using it. The man page has been fixed, thanks. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 17:42:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00429 for freebsd-current-outgoing; Wed, 11 Mar 1998 17:42:33 -0800 (PST) (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 RAA00422 for ; Wed, 11 Mar 1998 17:42:31 -0800 (PST) (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.6.9) with ESMTP id RAA01237; Wed, 11 Mar 1998 17:41:14 -0800 (PST) To: Garrett Wollman cc: Amancio Hasty , "Alok K. Dhir" , freebsd@isvara.net, current@FreeBSD.ORG Subject: Re: Amazing :-) In-reply-to: Your message of "Wed, 11 Mar 1998 14:08:11 EST." <199803111908.OAA04188@khavrinen.lcs.mit.edu> Date: Wed, 11 Mar 1998 17:41:13 -0800 Message-ID: <1233.889666873@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In the WorldStone race, that's cheating. I could compile faster, too, > if I left out a third of the libraries. Absolutely. I think the "informal rules" for comparing worldstone numbers stipulate that all you can change is CFLAGS to add -pipe in /etc/make.conf. :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 17:43:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00506 for freebsd-current-outgoing; Wed, 11 Mar 1998 17:43:04 -0800 (PST) (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 RAA00497 for ; Wed, 11 Mar 1998 17:43:03 -0800 (PST) (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.6.9) with ESMTP id RAA01255; Wed, 11 Mar 1998 17:42:01 -0800 (PST) To: Amancio Hasty cc: current@FreeBSD.ORG Subject: Re: my worldstone In-reply-to: Your message of "Wed, 11 Mar 1998 11:30:03 PST." <199803111930.LAA29537@rah.star-gate.com> Date: Wed, 11 Mar 1998 17:42:01 -0800 Message-ID: <1252.889666921@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It will be nice if people with very fast systems and i/o subsystems to > post their world stone. It has been alluded in the past that we have As long as they don't modify their make.conf files. :-) :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 17:47:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01495 for freebsd-current-outgoing; Wed, 11 Mar 1998 17:47:37 -0800 (PST) (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 RAA01490; Wed, 11 Mar 1998 17:47:35 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: (from hasty@localhost) by rah.star-gate.com (8.8.8/8.8.8) id RAA01017; Wed, 11 Mar 1998 17:47:33 -0800 (PST) (envelope-from hasty) Date: Wed, 11 Mar 1998 17:47:33 -0800 (PST) From: Amancio Hasty Message-Id: <199803120147.RAA01017@rah.star-gate.com> To: hasty@rah.star-gate.com, jkh@FreeBSD.ORG Subject: Re: my worldstone Cc: current@FreeBSD.ORG In-Reply-To: <1252.889666921@time.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >As long as they don't modify their make.conf files. :-) :-) Absolutly , now sit there and wait for my world stone 8) Honest, I have no use for profiled libraries they really should not be built by default -- thats akeen to asking to build your libraries with -g -- perhaps we should add that as default . Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 18:04:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03719 for freebsd-current-outgoing; Wed, 11 Mar 1998 18:04:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03707 for ; Wed, 11 Mar 1998 18:04:14 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA09328; Thu, 12 Mar 1998 12:52:03 +1100 Date: Thu, 12 Mar 1998 12:52:03 +1100 From: Bruce Evans Message-Id: <199803120152.MAA09328@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org Subject: Re: make/SIGINT (Re: cvs commit: src/bin/sh jobs.c) Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >What about the appended fix for make? It seems to fix the problem for >the non-compat mode of make. As our make is in compat mode by default >even if -B is not given, people would have to use `make -j 1` for now >to test it. > >What were the reasons to use compat mode by default, BTW? Anyone has >test cases that fail in new mode with just one job allowed? Compatibility? :-) >diff -c make.original/job.c make.work/job.c >*** make.original/job.c Tue Aug 26 12:06:38 1997 >--- make.work/job.c Wed Mar 11 12:49:52 1998 >*************** >*** 2904,2910 **** > } > } > (void) eunlink(tfile); >! exit(signo); > } > > /* >--- 2904,2918 ---- > } > } > (void) eunlink(tfile); >! >! /* >! * For some signals, we don't want a direct exit, but to >! * let them resent to ourself, which is done by the calling >! * Routine. >! */ >! >! if (signo != SIGINT && signo != SIGTERM && signo != SIGHUP) >! exit(signo); > } > > /* I just removed the exit() in my version. This seems to be what was intended, and seems to work. I thought that the fix was necessary for compat mode too. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 18:11:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05074 for freebsd-current-outgoing; Wed, 11 Mar 1998 18:11:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05068 for ; Wed, 11 Mar 1998 18:11:27 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA09967; Thu, 12 Mar 1998 13:03:57 +1100 Date: Thu, 12 Mar 1998 13:03:57 +1100 From: Bruce Evans Message-Id: <199803120203.NAA09967@godzilla.zeta.org.au> To: mike@smith.net.au, rhh@ct.picker.com Subject: Re: HEADS UP! (was: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Great! Been looking forward to someday putting multiple FreeBSD versions >on the same disk for a good while. That's always been possible, at least if you don't need multiple ufs file systems. E.g.: sd0a: FreeBSD-1.1.x sd0b: swap sd0c: reserved sd0d: reserved for pre-2.0.5 sd0e: FreeBSD-2.0.x sd0f: FreeBSD-2.1.x sd0g: FreeBSD-2.2.x sd0h: FreeBSD-current Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 18:11:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05090 for freebsd-current-outgoing; Wed, 11 Mar 1998 18:11:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05067; Wed, 11 Mar 1998 18:11:26 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id MAA10246; Thu, 12 Mar 1998 12:39:59 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id GWQLBWLM; Thu, 12 Mar 1998 12:40:28 +0930 Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id MAA23076; Thu, 12 Mar 1998 12:41:06 +1030 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id MAA03632; Thu, 12 Mar 1998 12:41:06 +1030 (CST) Message-ID: <3507443A.CBB933AE@dsto.defence.gov.au> Date: Thu, 12 Mar 1998 12:41:06 +1030 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: current@FreeBSD.ORG Subject: Worldstone rules (was: Re: Amazing :-)) References: <1233.889666873@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We cant have formal rules for the majority of -CURRENT users because most people are running -CURRENT on their one and only machine and dont have much choice as to their /etc/make.conf settings. For example I am NOT going to build TCL as I have it installed from the ports collection. So I will always have NOTCL= true no matter what. So we can make rules for people who want to participate in a real scientific experiment but for most people all we can ask for is full disclosure. i.e. people must quote the following: 1) Their /etc/make.conf settings... e.g. I use: CFLAGS= -O -pipe NOTCL= true (But dont bother quoting your MASTER_SITE_OVERIDE settings) 2) The location of /usr/src, /usr/obj and /var/tmp e.g.: /usr/src is on an IBM 305 MB blah blah SCSI-II disk so is /usr/obj (different disk) /var/tmp is in the /var filesystem on my Maxtor EIDE SCSI controller is an ASUS PC-2000 SCSI-II (ncr chipset) 3) The mounting options used on each of the above filesystems e.g: I am using softupdates for all filesystems mentioned. I am not using any other options such as noatime or async. 4) The build sources. e.g. quote the CTM-src-cur delta number OR the date that you last cvs or cvsuped and INCLUDE THE TIMEZONE! Jordan K. Hubbard wrote: > > > In the WorldStone race, that's cheating. I could compile faster, too, > > if I left out a third of the libraries. > > Absolutely. I think the "informal rules" for comparing worldstone > numbers stipulate that all you can change is CFLAGS to add -pipe > in /etc/make.conf. :) > > Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 18:31:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08207 for freebsd-current-outgoing; Wed, 11 Mar 1998 18:31:16 -0800 (PST) (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 SAA08202; Wed, 11 Mar 1998 18:31:12 -0800 (PST) (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.6.9) with ESMTP id SAA01838; Wed, 11 Mar 1998 18:30:10 -0800 (PST) To: Amancio Hasty cc: jkh@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: my worldstone In-reply-to: Your message of "Wed, 11 Mar 1998 17:47:33 PST." <199803120147.RAA01017@rah.star-gate.com> Date: Wed, 11 Mar 1998 18:30:10 -0800 Message-ID: <1834.889669810@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Honest, I have no use for profiled libraries they really should > not be built by default -- thats akeen to asking to build your > libraries with -g -- perhaps we should add that as default . I know, but the real problem here is that people are still comparing this "worldstone" figure in the same way they'd compare dhrystones or xstones or whatever and ultimately people are going to be making hardware decisions based on those numbers. It's no use saying now foolish such a practice is, it's simply inevitable - *people like numbers*. :-) So, if we're going to be tossing around numbers in a highly comparative fashion (and say what you like but any posting that says "2 hours? Huh. I get 1hr 10 minutes!" is attempting to compare numbers) we need to level the playing field since the last thing anybody needs is to go chasing after that extra illusive half-hour only to be told later that the half hour speedup had nothing to do with the hardware, it had to do with a smaller build set. :-) Whether the profiled libraries are useful or not is almost irrelevant; statistics compare numbers, not usefulness. ;-) So, in the spirit of getting specific, I'd like to suggest the following set of prototype ground rules to anyone daring to post their "worldstone rating" here: Before beginning a make world test, the following conditions must be met: 1. /usr/obj must be empty (no "clean" pass to add minutes to time). 2. /usr/obj *must* be mounted async (too few mount it sync and it does bestow a large advantage). 3. /usr/src must reside on a physically different disk (unless ccd is in use, in which case this should be noted). I know that's hard for some folks, but if you're running off a single drive then your numbers just won't be competetive. 4. -pipe must be added to CFLAGS in /etc/make.conf. *no other build optimizations or omissions can be done!* Same goes for additions - no kerberos bits enabled. 5. Source tree must be -current to within 7 days of the other people comparing numbers. No point in compiling old bits just before perl5 entered the tree, or whatever, since that obviously skews the numbers. And in posting your worldstone rating: 1. List number of CPUs, memory configuration and motherboard. 2. List types of drives involved in holding /usr/src and /usr/obj for this test. 3. List type of disk controller used. Anything on this list I'm forgetting? Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 18:32:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08397 for freebsd-current-outgoing; Wed, 11 Mar 1998 18:32:10 -0800 (PST) (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 SAA08371; Wed, 11 Mar 1998 18:32:03 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id SAA00379; Wed, 11 Mar 1998 18:31:52 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Wed, 11 Mar 1998 18:31:52 -0800 (PST) From: Manfred Antar To: current@FreeBSD.ORG cc: smp@FreeBSD.ORG Subject: spkrtest locks up system 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 a current SMP system when I run spkrtest the system locks up. On a kernel built around the 26th of Feb no problem. I have a old version of spkrtest v1.0 by Eric S. Raymond (Feb 1990) that I use as sort of a backup alarm clock. I was wondering why for the past couple of weeks I'd wake up and the machine would be locked up. The current graphical version does the same thing. I have no sound card installed. One time it dropped into the debugger , now it just locks up. There was something about _mplock if i remember right. There was alot of changes to current around the end of Feb. (SMP and locking) and I'm not sure which is causing the problem. Sorry I can't be of more help. 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 Wed Mar 11 18:36:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09183 for freebsd-current-outgoing; Wed, 11 Mar 1998 18:36:34 -0800 (PST) (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 SAA09177; Wed, 11 Mar 1998 18:36:26 -0800 (PST) (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.6.9) with ESMTP id SAA01881; Wed, 11 Mar 1998 18:35:13 -0800 (PST) To: Matthew Thyer cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: Worldstone rules (was: Re: Amazing :-)) In-reply-to: Your message of "Thu, 12 Mar 1998 12:41:06 +1030." <3507443A.CBB933AE@dsto.defence.gov.au> Date: Wed, 11 Mar 1998 18:35:13 -0800 Message-ID: <1877.889670113@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We cant have formal rules for the majority of -CURRENT users > because most people are running -CURRENT on their one and only > machine and dont have much choice as to their /etc/make.conf > settings. Those people don't have to post worldstone ratings either, they can just chatter informally about what they're doing, but if we're going to have a pissing contest then let's do it right. :-) [and there does appear to be a set of folks on this list who are perpetually keen to do this, so let's not get into a debate on the merits of such contents please :)]. And really, for the rest I have to say that the numbers are too meaningless to be useful. So you post your workstone rating without TCL, and Joe posts his without profiled libs, and Harry posts his with Kerberos enabled and what use are the numbers then to me? They're useless since to meaningfully compare them with anything I've now got to go compile my own tree 3 times with these various options set, and I'm as unlikely to do that as your -current users with one box are likely to spam themselves. And if a number has no comparative value, why even bother to communicate it to anyone else? :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 18:43:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10142 for freebsd-current-outgoing; Wed, 11 Mar 1998 18:43:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mhub2.tc.umn.edu (0@mhub2.tc.umn.edu [128.101.131.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA10136 for ; Wed, 11 Mar 1998 18:43:21 -0800 (PST) (envelope-from adkin003@tc.umn.edu) Received: from pub-19-c-222.dialup.umn.edu by mhub2.tc.umn.edu; Wed, 11 Mar 98 20:43:06 -0600 Date: Wed, 11 Mar 1998 20:39:51 -0600 (CST) From: dave adkins X-Sender: adkin003@samthedog To: Michael Hancock cc: dave adkins , current@FreeBSD.ORG Subject: Re: ext2_sync and NULL inode and VNON v_type 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, 12 Mar 1998, Michael Hancock wrote: > Date: Thu, 12 Mar 1998 10:02:58 +0900 (JST) > From: Michael Hancock > To: dave adkins > Cc: current@FreeBSD.ORG > Subject: Re: ext2_sync and NULL inode and VNON v_type > > You can just OR it into the check below it for a more canonical fix. > > if ((vp->v_type == VNON) || ((ip->i_flag & > > Make this patch and post it so some ext2 fs users can test it. > > Mike Hancock > > On Tue, 10 Mar 1998, dave adkins wrote: > > > In current as of 980310, a r/w mounted ext2 filesystem panics on the first > > sync. This happens when a vnode of type VNON with ip == NULL is processed. > > > > I have added a test for a v_type of VNON in ext2_sync(). > > > > if (VOP_ISLOCKED(vp)) > > continue; > > + if ( vp->v_type == VNON ) > > + continue; > > ip = VTOI(vp); > > if (ip == NULL) { > > > > > > I haven't yet tried writing to the mounted file system with this patch. > > > > dave adkins > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > michaelh@cet.co.jp http://www.cet.co.jp > CET Inc., Daiichi Kasuya BLDG 8F, 2-5-12 Higashi Shinbashi, Minato-ku, > Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > Here's the patch to fix the ext2_sync() panic. --- ext2_vfsops.c.orig Mon Mar 9 08:46:57 1998 +++ ext2_vfsops.c Wed Mar 11 15:59:45 1998 @@ -857,7 +859,7 @@ continue; ip = VTOI(vp); - if ((ip->i_flag & - (IN_ACCESS | IN_CHANGE | IN_MODIFIED | IN_UPDATE)) == 0 && - vp->v_dirtyblkhd.lh_first == NULL) + if ( (vp->v_type == VNON) || (ip->i_flag & + (IN_ACCESS | IN_CHANGE | IN_MODIFIED | IN_UPDATE) ) == 0 && + vp->v_dirtyblkhd.lh_first == NULL) continue; if (vget(vp, LK_EXCLUSIVE, p)) There do seem to be bigger problems with ext2fs. Writing a small file that (<17Kbytes) works if EXT2_PREALLOCATE is undefined. With preallocation defined, ext2fs writes generates alot of "Freeing blocks not in datazone" messages before crashing. Larger files even with preallocation undefined appear to write correctly and show the correct size but are unreadable. And require the use of debugfs on the linux side to clean up the filesystem. With either preallocation inodes, or files larger that can be held in the direct blocks, there are problems. I haven't used the ext2fs very often and remember having similar problems quite a while ago, I use it very infrequently, and them mostly for reading. I would recommend making it a readonly file system for now. I've been meaning to get rid of the linux entirely and get another 700 Mbytes back, but ... dave adkins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 18:44:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10512 for freebsd-current-outgoing; Wed, 11 Mar 1998 18:44:49 -0800 (PST) (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 SAA10491; Wed, 11 Mar 1998 18:44:35 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id SAA01221; Wed, 11 Mar 1998 18:44:33 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803120244.SAA01221@rah.star-gate.com> To: "Jordan K. Hubbard" cc: Amancio Hasty , current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: my worldstone In-reply-to: Your message of "Wed, 11 Mar 1998 18:30:10 PST." <1834.889669810@time.cdrom.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1218.889670673.1@rah> Date: Wed, 11 Mar 1998 18:44:33 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Anything on this list I'm forgetting? Sure take the profile libs out. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 19:01:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12941 for freebsd-current-outgoing; Wed, 11 Mar 1998 19:01:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gorillanet.gorilla.net (gorillanet.gorilla.net [208.128.8.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA12901 for ; Wed, 11 Mar 1998 19:01:10 -0800 (PST) (envelope-from tom@gorilla.net) Received: from [208.143.84.39] by gorillanet.gorilla.net (NTMail 3.03.0014/18.aaac) with ESMTP id ea022078 for ; Wed, 11 Mar 1998 21:00:38 -0600 Received: (from tom@localhost) by gorilla.net (8.8.8/8.8.8) id VAA00654; Wed, 11 Mar 1998 21:00:40 -0600 (CST) (envelope-from tom) Message-ID: <19980311210038.28154@TOJ.org> Date: Wed, 11 Mar 1998 21:00:38 -0600 From: Tom Jackson To: "Justin T. Gibbs" , freebsd-current@FreeBSD.ORG Subject: Re: CAM testimonials? Mail-Followup-To: "Justin T. Gibbs" , freebsd-current@freebsd.org References: <199803111803.LAA22230@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=zhXaljGHf11kAtnf X-Mailer: Mutt 0.89.1i In-Reply-To: <199803111803.LAA22230@pluto.plutotech.com>; from Justin T. Gibbs on Wed, Mar 11, 1998 at 11:00:08AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii On Wed, Mar 11, 1998 at 11:00:08AM -0700, Justin T. Gibbs wrote: > ------- Blind-Carbon-Copy > > X-Mailer: exmh version 2.0.1 12/23/97 > To: scsi@FreeBSD.org > Subject: CAM testimonials? > Mime-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Date: Wed, 11 Mar 1998 11:00:08 -0700 > From: "Justin T. Gibbs" > > I haven't gotten much feedback on the latest CAM snapshot. If you are > running CAM, I'd appreciate a small note listing your configuration along > with any other comments you have. > > Thanks! > - -- > Justin > Any idea why I'm getting seg11 with dset and dmesg at bootup and beyond? Attaching /var/log/messages reg and verbose. This is asus p2l97-ds w/pII-266 and regular 2940. --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Description: regular messages Content-Disposition: attachment; filename="dmesg.cam" Mar 11 16:25:35 peeper /kernel.cam: ev=0 Mar 11 16:25:36 peeper /kernel.cam: found-> vendor=0x8086, dev=0x7112, revid=0x01 Mar 11 16:25:36 peeper /kernel.cam: class=0c-03-00, hdrtype=0x00, mfdev=0 Mar 11 16:25:36 peeper /kernel.cam: intpin=d, irq=255 Mar 11 16:25:36 peeper /kernel.cam: chip3: rev 0x01 int d irq 255 on pci0.4.2 Mar 11 16:25:36 peeper /kernel.cam: found-> vendor=0x8086, dev=0x7113, revid=0x01 Mar 11 16:25:36 peeper /kernel.cam: class=06-80-00, hdrtype=0x00, mfdev=0 Mar 11 16:25:36 peeper /kernel.cam: chip4: rev 0x01 on pci0.4.3 Mar 11 16:25:36 peeper /kernel.cam: found-> vendor=0x9004, dev=0x8078, revid=0x00 Mar 11 16:25:36 peeper /kernel.cam: class=01-00-00, hdrtype=0x00, mfdev=0 Mar 11 16:25:36 peeper /kernel.cam: intpin=a, irq=9 Mar 11 16:25:36 peeper /kernel.cam: map[0]: type 4, range 32, base 0000d000, size 8 Mar 11 16:25:36 peeper /kernel.cam: map[1]: type 1, range 32, base e3000000, size 12 Mar 11 16:25:36 peeper /kernel.cam: ahc0: rev 0x00 int a irq 9 on pci0.6.0 Mar 11 16:25:36 peeper /kernel.cam: ahc0: Reading SEEPROM...done. Mar 11 16:25:36 peeper /kernel.cam: ahc0: SE Low byte termination Enabled Mar 11 16:25:36 peeper /kernel.cam: ahc0: SE High byte termination Enabled Mar 11 16:25:36 peeper /kernel.cam: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Mar 11 16:25:36 peeper /kernel.cam: ahc0: Resetting Channel A Mar 11 16:25:36 peeper /kernel.cam: ahc0: Downloading Sequencer Program... 417 instructions downloaded Mar 11 16:25:36 peeper /kernel.cam: found-> vendor=0x5333, dev=0x88f0, revid=0x00 Mar 11 16:25:36 peeper /kernel.cam: class=03-00-00, hdrtype=0x00, mfdev=0 Mar 11 16:25:36 peeper /kernel.cam: intpin=a, irq=12 Mar 11 16:25:36 peeper /kernel.cam: map[0]: type 1, range 32, base e0000000, size 25 Mar 11 16:25:36 peeper /kernel.cam: vga0: rev 0x00 int a irq 12 on pci0.10.0 Mar 11 16:25:36 peeper /kernel.cam: found-> vendor=0x9004, dev=0x8178, revid=0x00 Mar 11 16:25:36 peeper /kernel.cam: class=01-00-00, hdrtype=0x00, mfdev=0 Mar 11 16:25:36 peeper /kernel.cam: intpin=a, irq=11 Mar 11 16:25:36 peeper /kernel.cam: map[0]: type 4, range 32, base 0000b800, size 8 Mar 11 16:25:36 peeper /kernel.cam: map[1]: type 1, range 32, base df800000, size 12 Mar 11 16:25:36 peeper /kernel.cam: ahc1: rev 0x00 int a irq 11 on pci0.11.0 Mar 11 16:25:36 peeper /kernel.cam: ahc1: Reading SEEPROM...done. Mar 11 16:25:36 peeper /kernel.cam: ahc1: internal SE 50 cable is present, internal SE 68 cable not present Mar 11 16:25:36 peeper /kernel.cam: ahc1: external SE cable not present Mar 11 16:25:36 peeper /kernel.cam: ahc1: BIOS eeprom not present Mar 11 16:25:36 peeper /kernel.cam: ahc1: SE Low byte termination Enabled Mar 11 16:25:36 peeper /kernel.cam: ahc1: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs Mar 11 16:25:36 peeper /kernel.cam: ahc1: Resetting Channel A Mar 11 16:25:36 peeper /kernel.cam: ahc1: Downloading Sequencer Program... 417 instructions downloaded Mar 11 16:25:36 peeper /kernel.cam: Probing for devices on PCI bus 1: Mar 11 16:25:37 peeper /kernel.cam: Initializing PnP override table Mar 11 16:25:37 peeper /kernel.cam: Probing for PnP devices: Mar 11 16:25:37 peeper /kernel.cam: Trying Read_Port at 203 Mar 11 16:25:37 peeper /kernel.cam: Trying Read_Port at 243 Mar 11 16:25:37 peeper /kernel.cam: CSN 1 Vendor ID: CTL0043 [0x43008c0e] Serial 0x00011822 Mar 11 16:25:37 peeper /kernel.cam: Called nullpnp_probe with tag 0x00000001, type 0x43008c0e Mar 11 16:25:37 peeper /kernel.cam: Probing for devices on the ISA bus: Mar 11 16:25:37 peeper /kernel.cam: kbdio: RESET_KBD return code:00fa Mar 11 16:25:37 peeper /kernel.cam: kbdio: RESET_KBD status:00aa Mar 11 16:25:37 peeper /kernel.cam: vt0 at 0x60-0x6f irq 1 on motherboard Mar 11 16:25:37 peeper /kernel.cam: vt0: unkown s3, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] Mar 11 16:25:37 peeper /kernel.cam: ed0 at 0x300-0x31f irq 15 on isa Mar 11 16:25:37 peeper /kernel.cam: ed0: address 00:40:05:58:53:3a, type NE2000 (16 bit) Mar 11 16:25:37 peeper /kernel.cam: bpf: ed0 attached Mar 11 16:25:37 peeper /kernel.cam: sio0 at 0x3f8-0x3ff irq 4 on isa Mar 11 16:25:37 peeper /kernel.cam: sio0: type 16550A Mar 11 16:25:37 peeper /kernel.cam: sio1 at 0x2f8-0x2ff irq 3 on isa Mar 11 16:25:37 peeper /kernel.cam: sio1: type 16550A Mar 11 16:25:37 peeper /kernel.cam: lpt0 at 0x378-0x37f irq 7 on isa Mar 11 16:25:37 peeper /kernel.cam: lpt0: Interrupt-driven port Mar 11 16:25:37 peeper /kernel.cam: lp0: TCP/IP capable interface Mar 11 16:25:37 peeper /kernel.cam: bpf: lp0 attached Mar 11 16:25:37 peeper /kernel.cam: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Mar 11 16:25:37 peeper /kernel.cam: fdc0: FIFO enabled, 8 bytes threshold Mar 11 16:25:37 peeper /kernel.cam: fd0: 1.44MB 3.5in Mar 11 16:25:37 peeper /kernel.cam: npx0 on motherboard Mar 11 16:25:37 peeper /kernel.cam: npx0: INT 16 interface Mar 11 16:25:37 peeper /kernel.cam: sb0 at 0x220 irq 5 drq 1 on isa Mar 11 16:25:37 peeper /kernel.cam: snd0: Mar 11 16:25:37 peeper /kernel.cam: sbxvi0 at ? drq 5 on isa Mar 11 16:25:37 peeper /kernel.cam: snd0: Mar 11 16:25:37 peeper /kernel.cam: sbmidi0 at 0x330 on isa Mar 11 16:25:37 peeper /kernel.cam: snd0: Mar 11 16:25:37 peeper /kernel.cam: awe0 at 0x620 on isa Mar 11 16:25:37 peeper /kernel.cam: AWE32: not detected Mar 11 16:25:37 peeper /kernel.cam: Mar 11 16:25:37 peeper /kernel.cam: opl0 at 0x388 on isa Mar 11 16:25:37 peeper /kernel.cam: snd0: Mar 11 16:25:37 peeper /kernel.cam: imasks: bio c0080040, tty c003009a, net c0068000 Mar 11 16:25:37 peeper /kernel.cam: BIOS Geometries: Mar 11 16:25:37 peeper /kernel.cam: 0:03fe3f20 0..1022=1023 cylinders, 0..63=64 heads, 1..32=32 sectors Mar 11 16:25:37 peeper /kernel.cam: 1:03fe3f20 0..1022=1023 cylinders, 0..63=64 heads, 1..32=32 sectors Mar 11 16:25:37 peeper /kernel.cam: 0 accounted for Mar 11 16:25:37 peeper /kernel.cam: Device configuration finished. Mar 11 16:25:37 peeper /kernel.cam: Linux-ELF exec handler installed Mar 11 16:25:38 peeper /kernel.cam: bpf: tun0 attached Mar 11 16:25:38 peeper /kernel.cam: bpf: lo0 attached Mar 11 16:25:38 peeper /kernel.cam: SCSI bus reset delivered. 0 SCBs aborted. Mar 11 16:25:38 peeper /kernel.cam: SCSI bus reset delivered. 0 SCBs aborted. Mar 11 16:25:38 peeper /kernel.cam: ahc1: target 5 synchronous at 5.0MHz, offset = 0xf Mar 11 16:25:38 peeper /kernel.cam: ahc0: target 4 synchronous at 5.0MHz, offset = 0xf Mar 11 16:25:38 peeper /kernel.cam: ahc0: target 4 using asynchronous transfers Mar 11 16:25:38 peeper /kernel.cam: ahc0: target 4 synchronous at 5.0MHz, offset = 0xf Mar 11 16:25:38 peeper /kernel.cam: ahc0: target 2 synchronous at 10.0MHz, offset = 0xf Mar 11 16:25:38 peeper /kernel.cam: ahc0: target 0 synchronous at 20.0MHz, offset = 0xf Mar 11 16:25:38 peeper /kernel.cam: (probe16:ahc1:0:1:0): SCB 0x1 - timed out in datain phase, SCSISIGI == 0x44 Mar 11 16:25:38 peeper /kernel.cam: SEQADDR == 0x10e Mar 11 16:25:38 peeper /kernel.cam: SSTAT1 == 0x2 Mar 11 16:25:38 peeper /kernel.cam: (probe20:ahc1:0:5:0): SCB 0x5 - timed out in datain phase, SCSISIGI == 0x44 Mar 11 16:25:38 peeper /kernel.cam: SEQADDR == 0x10e Mar 11 16:25:38 peeper /kernel.cam: SSTAT1 == 0x2 Mar 11 16:25:38 peeper /kernel.cam: (probe20:ahc1:0:5:0): BDR message in message buffer Mar 11 16:25:38 peeper /kernel.cam: (probe20:ahc1:0:5:0): SCB 0x5 - timed out in datain phase, SCSISIGI == 0x54 Mar 11 16:25:38 peeper /kernel.cam: SEQADDR == 0x10e Mar 11 16:25:38 peeper /kernel.cam: SSTAT1 == 0x2 Mar 11 16:25:38 peeper /kernel.cam: (probe20:ahc1:0:5:0): no longer in timeout Mar 11 16:25:38 peeper /kernel.cam: ahc1: Issued Channel A Bus Reset. 3 SCBs aborted Mar 11 16:25:38 peeper /kernel.cam: ahc1: target 6 synchronous at 10.0MHz, offset = 0xf Mar 11 16:25:38 peeper /kernel.cam: ahc1: target 6 using asynchronous transfers Mar 11 16:25:38 peeper /kernel.cam: ahc1: target 6 synchronous at 10.0MHz, offset = 0xf Mar 11 16:25:38 peeper /kernel.cam: ahc1: target 1 synchronous at 8.0MHz, offset = 0xf Mar 11 16:25:38 peeper /kernel.cam: sa0 at ahc1 bus 0 target 5 lun 0 Mar 11 16:25:38 peeper /kernel.cam: sa0: Removable Sequential Access SCSI2 device Mar 11 16:25:38 peeper /kernel.cam: sa0: Serial Number Mar 11 16:25:38 peeper /kernel.cam: sa0: 3.300MB/s transfers Mar 11 16:25:38 peeper /kernel.cam: ahc1: target 6 using asynchronous transfers Mar 11 16:25:38 peeper /kernel.cam: pass0 at ahc0 bus 0 target 0 lun 0 Mar 11 16:25:38 peeper /kernel.cam: pass0: Fixed Direct Access SCSI2 device Mar 11 16:25:38 peeper /kernel.cam: pass0: Serial Number 50082685 Mar 11 16:25:38 peeper /kernel.cam: pass0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled Mar 11 16:25:38 peeper /kernel.cam: ahc0: target 4 using asynchronous transfers Mar 11 16:25:38 peeper /kernel.cam: pass1 at ahc0 bus 0 target 2 lun 0 Mar 11 16:25:38 peeper /kernel.cam: pass1: Fixed Direct Access SCSI2 device Mar 11 16:25:38 peeper /kernel.cam: pass1: Serial Number 06056905 Mar 11 16:25:38 peeper /kernel.cam: pass1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled Mar 11 16:25:38 peeper /kernel.cam: pass2 at ahc0 bus 0 target 4 lun 0 Mar 11 16:25:38 peeper /kernel.cam: pass2: Removable CD-ROM SCSI2 device Mar 11 16:25:38 peeper /kernel.cam: pass2: 3.300MB/s transfers Mar 11 16:25:38 peeper /kernel.cam: pass3 at ahc1 bus 0 target 1 lun 0 Mar 11 16:25:38 peeper /kernel.cam: pass3: Fixed Direct Access SCSI2 device Mar 11 16:25:38 peeper /kernel.cam: pass3: Serial Number 6082781130 Mar 11 16:25:38 peeper /kernel.cam: pass3: 8.64MB/s transfers (8.64MHz, offset 15), Tagged Queueing Enabled Mar 11 16:25:38 peeper /kernel.cam: ahc1: target 6 synchronous at 10.0MHz, offset = 0xf Mar 11 16:25:38 peeper /kernel.cam: pass4 at ahc1 bus 0 target 5 lun 0 Mar 11 16:25:38 peeper /kernel.cam: pass4: Removable Sequential Access SCSI2 device Mar 11 16:25:38 peeper /kernel.cam: pass4: Serial Number Mar 11 16:25:38 peeper /kernel.cam: pass4: 3.300MB/s transfers Mar 11 16:25:38 peeper /kernel.cam: pass5 at ahc1 bus 0 target 6 lun 0 Mar 11 16:25:38 peeper /kernel.cam: pass5: Removable Direct Access SCSI2 device Mar 11 16:25:38 peeper /kernel.cam: pass5: 10.0MB/s transfers (10.0MHz, offset 15) Mar 11 16:25:38 peeper /kernel.cam: da2 at ahc0 bus 0 target 2 lun 0 Mar 11 16:25:38 peeper /kernel.cam: da2: Fixed Direct Access SCSI2 device Mar 11 16:25:38 peeper /kernel.cam: da2: Serial Number 06056905 Mar 11 16:25:38 peeper /kernel.cam: da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled Mar 11 16:25:38 peeper /kernel.cam: da2: 1041MB (2131992 512 byte sectors: 64H 32S/T 1041C) Mar 11 16:25:38 peeper /kernel.cam: da0 at ahc0 bus 0 target 0 lun 0 Mar 11 16:25:39 peeper /kernel.cam: da0: Fixed Direct Access SCSI2 device Mar 11 16:25:39 peeper /kernel.cam: da0: Serial Number 50082685 Mar 11 16:25:39 peeper /kernel.cam: da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled Mar 11 16:25:39 peeper /kernel.cam: da0: 4149MB (8498506 512 byte sectors: 64H 32S/T 4149C) Mar 11 16:25:39 peeper /kernel.cam: da1 at ahc1 bus 0 target 1 lun 0 Mar 11 16:25:39 peeper /kernel.cam: da1: Fixed Direct Access SCSI2 device Mar 11 16:25:39 peeper /kernel.cam: da1: Serial Number 6082781130 Mar 11 16:25:39 peeper /kernel.cam: da1: 8.64MB/s transfers (8.64MHz, offset 15), Tagged Queueing Enabled Mar 11 16:25:39 peeper /kernel.cam: da1: 2047MB (4193360 512 byte sectors: 64H 32S/T 2047C) Mar 11 16:25:39 peeper /kernel.cam: da3 at ahc1 bus 0 target 6 lun 0 Mar 11 16:25:39 peeper /kernel.cam: da3: Removable Direct Access SCSI2 device Mar 11 16:25:39 peeper /kernel.cam: da3: 10.0MB/s transfers (10.0MHz, offset 15) Mar 11 16:25:39 peeper /kernel.cam: da3: 220MB (450560 512 byte sectors: 64H 32S/T 220C) Mar 11 16:25:39 peeper /kernel.cam: Consideringahc0: target 4 synchronous at 5.0MHz, offset = 0xf Mar 11 16:25:39 peeper /kernel.cam: FFS root f/s. Mar 11 16:25:39 peeper /kernel.cam: changing root device to da0s3a Mar 11 16:25:39 peeper /kernel.cam: cd0 at ahc0 bus 0 target 4 lun 0 Mar 11 16:25:39 peeper /kernel.cam: cd0: Removable CD-ROM SCSI2 device Mar 11 16:25:39 peeper /kernel.cam: cd0: 5.0MB/s transfers (5.0MHz, offset 15) Mar 11 16:25:39 peeper /kernel.cam: cd0: cd present [320495 x 2048 byte records] Mar 11 16:25:39 peeper /kernel.cam: sd0s1: type 0x6, start 32, end = 511999, size 511968 : OK Mar 11 16:25:39 peeper /kernel.cam: sd0s2: type 0xa5, start 512000, end = 4503551, size 3991552 : OK Mar 11 16:25:39 peeper /kernel.cam: sd0s3: type 0xa5, start 4503552, end = 8497151, size 3993600 : OK Mar 11 16:25:39 peeper /kernel.cam: sd1s1: type 0x6, start 32, end = 511999, size 511968 : OK Mar 11 16:25:39 peeper /kernel.cam: sd1s2: type 0xa5, start 512000, end = 4192255, size 3680256 : OK Mar 11 16:25:39 peeper /kernel.cam: sd2s1: type 0xa5, start 32, end = 2131967, size 2131936 : OK Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 using asynchronous transfers Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 synchronous at 20.0MHz, offset = 0xf Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 using asynchronous transfers Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 synchronous at 20.0MHz, offset = 0xf Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 using asynchronous transfers Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 synchronous at 20.0MHz, offset = 0xf Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 using asynchronous transfers Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 synchronous at 20.0MHz, offset = 0xf Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 using asynchronous transfers Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 synchronous at 20.0MHz, offset = 0xf Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 using asynchronous transfers Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 synchronous at 20.0MHz, offset = 0xf Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 using asynchronous transfers Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 synchronous at 20.0MHz, offset = 0xf Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 using asynchronous transfers Mar 11 16:25:39 peeper /kernel.cam: ahc0: target 0 synchronous at 20.0MHz, offset = 0xf Mar 11 16:25:39 peeper /kernel.cam: sd2s1: type 0xa5, start 32, end = 2131967, size 2131936 : OK Mar 11 16:25:39 peeper /kernel.cam: pid 39 (dmesg), uid 0: exited on signal 11 Mar 11 16:25:39 peeper /kernel.cam: pid 87 (dset), uid 0: exited on signal 11 Mar 11 16:25:39 peeper /kernel.cam: pid 96 (savecore), uid 0: exited on signal 11 Mar 11 16:25:40 peeper /kernel.cam: Old mount_msdosfs, flags=0 Mar 11 16:25:40 peeper /kernel.cam: Old mount_msdosfs, flags=0 Mar 11 16:25:41 peeper /kernel.cam: pid 129 (kvm_mkdb), uid 0: exited on signal 11 Mar 11 16:25:41 peeper lpd[146]: restarted Mar 11 16:26:35 peeper su: tom to root on /dev/ttyv3 Mar 11 16:27:13 peeper /kernel.cam: pid 320 (dmesg), uid 0: exited on signal 11 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Description: verbose messages Content-Disposition: attachment; filename="dmesg3.cam" Mar 11 19:37:43 peeper /kernel.cam: Copyright (c) 1992-1998 FreeBSD Inc. Mar 11 19:37:43 peeper /kernel.cam: Copyright (c) 1982, 1986, 1989, 1991, 1993 Mar 11 19:37:43 peeper /kernel.cam: The Regents of the University of California. All rights reserved. Mar 11 19:37:44 peeper /kernel.cam: FreeBSD 3.0-CURRENT #3: Wed Mar 11 16:23:11 CST 1998 Mar 11 19:37:44 peeper /kernel.cam: tom@peeper.TOJ.org:/usr/src/sys/compile/CAM Mar 11 19:37:44 peeper /kernel.cam: Timecounter "i8254" frequency 1193182 Hz cost 3119 ns Mar 11 19:37:44 peeper /kernel.cam: Timecounter "TSC" frequency 267359375 Hz cost 216 ns Mar 11 19:37:44 peeper /kernel.cam: CPU: Pentium Pro (267.36-MHz 686-class CPU) Mar 11 19:37:44 peeper /kernel.cam: Origin = "GenuineIntel" Id = 0x633 Stepping=3 Mar 11 19:37:44 peeper /kernel.cam: Features=0x80fbff Mar 11 19:37:44 peeper /kernel.cam: real memory = 134217728 (131072K bytes) Mar 11 19:37:44 peeper /kernel.cam: avail memory = 128196608 (125192K bytes) Mar 11 19:37:44 peeper /kernel.cam: Probing for devices on PCI bus 0: Mar 11 19:37:44 peeper /kernel.cam: chip0: rev 0x03 on pci0.0.0 Mar 11 19:37:44 peeper /kernel.cam: chip1: rev 0x03 on pci0.1.0 Mar 11 19:37:44 peeper /kernel.cam: chip2: rev 0x01 on pci0.4.0 Mar 11 19:37:44 peeper /kernel.cam: chip3: rev 0x01 int d irq 255 on pci0.4.2 Mar 11 19:37:44 peeper /kernel.cam: chip4: rev 0x01 on pci0.4.3 Mar 11 19:37:44 peeper /kernel.cam: ahc0: rev 0x00 int a irq 9 on pci0.6.0 Mar 11 19:37:44 peeper /kernel.cam: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Mar 11 19:37:44 peeper /kernel.cam: vga0: rev 0x00 int a irq 12 on pci0.10.0 Mar 11 19:37:44 peeper /kernel.cam: ahc1: rev 0x00 int a irq 11 on pci0.11.0 Mar 11 19:37:44 peeper /kernel.cam: ahc1: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs Mar 11 19:37:44 peeper /kernel.cam: Probing for devices on PCI bus 1: Mar 11 19:37:44 peeper /kernel.cam: Probing for PnP devices: Mar 11 19:37:44 peeper /kernel.cam: CSN 1 Vendor ID: CTL0043 [0x43008c0e] Serial 0x00011822 Mar 11 19:37:44 peeper /kernel.cam: Probing for devices on the ISA bus: Mar 11 19:37:44 peeper /kernel.cam: vt0 at 0x60-0x6f irq 1 on motherboard Mar 11 19:37:44 peeper /kernel.cam: vt0: unkown s3, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] Mar 11 19:37:44 peeper /kernel.cam: ed0 at 0x300-0x31f irq 15 on isa Mar 11 19:37:44 peeper /kernel.cam: ed0: address 00:40:05:58:53:3a, type NE2000 (16 bit) Mar 11 19:37:44 peeper /kernel.cam: sio0 at 0x3f8-0x3ff irq 4 on isa Mar 11 19:37:44 peeper /kernel.cam: sio0: type 16550A Mar 11 19:37:44 peeper /kernel.cam: sio1 at 0x2f8-0x2ff irq 3 on isa Mar 11 19:37:44 peeper /kernel.cam: sio1: type 16550A Mar 11 19:37:44 peeper /kernel.cam: lpt0 at 0x378-0x37f irq 7 on isa Mar 11 19:37:44 peeper /kernel.cam: lpt0: Interrupt-driven port Mar 11 19:37:44 peeper /kernel.cam: lp0: TCP/IP capable interface Mar 11 19:37:44 peeper /kernel.cam: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Mar 11 19:37:44 peeper /kernel.cam: fdc0: FIFO enabled, 8 bytes threshold Mar 11 19:37:44 peeper /kernel.cam: fd0: 1.44MB 3.5in Mar 11 19:37:44 peeper /kernel.cam: npx0 on motherboard Mar 11 19:37:44 peeper /kernel.cam: npx0: INT 16 interface Mar 11 19:37:44 peeper /kernel.cam: sb0 at 0x220 irq 5 drq 1 on isa Mar 11 19:37:44 peeper /kernel.cam: snd0: Mar 11 19:37:44 peeper /kernel.cam: sbxvi0 at ? drq 5 on isa Mar 11 19:37:44 peeper /kernel.cam: snd0: Mar 11 19:37:44 peeper /kernel.cam: sbmidi0 at 0x330 on isa Mar 11 19:37:44 peeper /kernel.cam: snd0: Mar 11 19:37:44 peeper /kernel.cam: awe0 at 0x620 on isa Mar 11 19:37:44 peeper /kernel.cam: AWE32: not detected Mar 11 19:37:44 peeper /kernel.cam: Mar 11 19:37:44 peeper /kernel.cam: opl0 at 0x388 on isa Mar 11 19:37:44 peeper /kernel.cam: snd0: Mar 11 19:37:44 peeper /kernel.cam: (probe16:ahc1:0:1:0): SCB 0x1 - timed out in datain phase, SCSISIGI == 0x44 Mar 11 19:37:44 peeper /kernel.cam: SEQADDR == 0x10d Mar 11 19:37:44 peeper /kernel.cam: SSTAT1 == 0x2 Mar 11 19:37:44 peeper /kernel.cam: (probe20:ahc1:0:5:0): SCB 0x5 - timed out in datain phase, SCSISIGI == 0x44 Mar 11 19:37:44 peeper /kernel.cam: SEQADDR == 0x10d Mar 11 19:37:44 peeper /kernel.cam: SSTAT1 == 0x2 Mar 11 19:37:44 peeper /kernel.cam: (probe20:ahc1:0:5:0): BDR message in message buffer Mar 11 19:37:45 peeper /kernel.cam: (probe20:ahc1:0:5:0): SCB 0x5 - timed out in datain phase, SCSISIGI == 0x54 Mar 11 19:37:45 peeper /kernel.cam: SEQADDR == 0x10d Mar 11 19:37:45 peeper /kernel.cam: SSTAT1 == 0x2 Mar 11 19:37:45 peeper /kernel.cam: (probe20:ahc1:0:5:0): no longer in timeout Mar 11 19:37:45 peeper /kernel.cam: ahc1: Issued Channel A Bus Reset. 3 SCBs aborted Mar 11 19:37:45 peeper /kernel.cam: sa0 at ahc1 bus 0 target 5 lun 0 Mar 11 19:37:45 peeper /kernel.cam: sa0: Removable Sequential Access SCSI2 device Mar 11 19:37:45 peeper /kernel.cam: sa0: Serial Number Mar 11 19:37:45 peeper /kernel.cam: sa0: 3.300MB/s transfers Mar 11 19:37:45 peeper /kernel.cam: da2 at ahc0 bus 0 target 2 lun 0 Mar 11 19:37:45 peeper /kernel.cam: da2: Fixed Direct Access SCSI2 device Mar 11 19:37:45 peeper /kernel.cam: da2: Serial Number 06056905 Mar 11 19:37:45 peeper /kernel.cam: da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled Mar 11 19:37:45 peeper /kernel.cam: da2: 1041MB (2131992 512 byte sectors: 64H 32S/T 1041C) Mar 11 19:37:45 peeper /kernel.cam: da0 at ahc0 bus 0 target 0 lun 0 Mar 11 19:37:45 peeper /kernel.cam: da0: Fixed Direct Access SCSI2 device Mar 11 19:37:45 peeper /kernel.cam: da0: Serial Number 50082685 Mar 11 19:37:45 peeper /kernel.cam: da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled Mar 11 19:37:45 peeper /kernel.cam: da0: 4149MB (8498506 512 byte sectors: 64H 32S/T 4149C) Mar 11 19:37:45 peeper /kernel.cam: changing root device to da0s3a Mar 11 19:37:45 peeper /kernel.cam: da1 at ahc1 bus 0 target 1 lun 0 Mar 11 19:37:45 peeper /kernel.cam: da1: Fixed Direct Access SCSI2 device Mar 11 19:37:45 peeper /kernel.cam: da1: Serial Number 6082781130 Mar 11 19:37:45 peeper /kernel.cam: da1: 8.64MB/s transfers (8.64MHz, offset 15), Tagged Queueing Enabled Mar 11 19:37:45 peeper /kernel.cam: da1: 2047MB (4193360 512 byte sectors: 64H 32S/T 2047C) Mar 11 19:37:45 peeper /kernel.cam: da3 at ahc1 bus 0 target 6 lun 0 Mar 11 19:37:45 peeper /kernel.cam: da3: Removable Direct Access SCSI2 device Mar 11 19:37:45 peeper /kernel.cam: da3: 10.0MB/s transfers (10.0MHz, offset 15) Mar 11 19:37:45 peeper /kernel.cam: da3: 220MB (450560 512 byte sectors: 64H 32S/T 220C) Mar 11 19:37:45 peeper /kernel.cam: cd0 at ahc0 bus 0 target 4 lun 0 Mar 11 19:37:45 peeper /kernel.cam: cd0: Removable CD-ROM SCSI2 device Mar 11 19:37:45 peeper /kernel.cam: cd0: 5.0MB/s transfers (5.0MHz, offset 15) Mar 11 19:37:45 peeper /kernel.cam: cd0: cd present [320495 x 2048 byte records] Mar 11 19:37:45 peeper /kernel.cam: pid 39 (dmesg), uid 0: exited on signal 11 Mar 11 19:37:45 peeper /kernel.cam: pid 87 (dset), uid 0: exited on signal 11 Mar 11 19:37:45 peeper /kernel.cam: pid 96 (savecore), uid 0: exited on signal 11 Mar 11 19:37:45 peeper /kernel.cam: Old mount_msdosfs, flags=0 Mar 11 19:37:45 peeper /kernel.cam: Old mount_msdosfs, flags=0 Mar 11 19:37:46 peeper /kernel.cam: pid 129 (kvm_mkdb), uid 0: exited on signal 11 Mar 11 19:37:47 peeper lpd[146]: restarted Mar 11 19:38:56 peeper su: tom to root on /dev/ttyv3 Mar 11 19:39:19 peeper /kernel.cam: pid 310 (dmesg), uid 0: exited on signal 11 --zhXaljGHf11kAtnf-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 19:08:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14309 for freebsd-current-outgoing; Wed, 11 Mar 1998 19:08:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14299; Wed, 11 Mar 1998 19:08:35 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA12807; Thu, 12 Mar 1998 14:04:22 +1100 Date: Thu, 12 Mar 1998 14:04:22 +1100 From: Bruce Evans Message-Id: <199803120304.OAA12807@godzilla.zeta.org.au> To: hasty@rah.star-gate.com, jkh@FreeBSD.ORG Subject: Re: my worldstone Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >So, in the spirit of getting specific, I'd like to suggest the >following set of prototype ground rules to anyone daring to post their >"worldstone rating" here: > >Before beginning a make world test, the following conditions must be >met: > >1. /usr/obj must be empty (no "clean" pass to add minutes to time). > >2. /usr/obj *must* be mounted async (too few mount it sync and it does > bestow a large advantage). It should be mounted -noatime too, unless you want to throw away "free" optimizations. >3. /usr/src must reside on a physically different disk (unless ccd > is in use, in which case this should be noted). I know that's hard > for some folks, but if you're running off a single drive then your > numbers just won't be competetive. /usr/src should probably be mounted -noatime too. My numbers are competitive (1:37 on a K6/233 FIC-2007 64MB with 1 Quantum ST IDE drive in DMA mode, and /usr/src/Makefile tweaked to build al tools static, and DESTDIR on the same file system as /usr/obj (async,noatime,not-the-root-fs)). makewhorldstone should not be disk intensive on systems with enough RAM. If I had more time, then I would repeat the benchmark with the drive in PIO mode to prove how unimportant DMA mode and fast disk seek times are for non-disk-intensive non-seek-intensive benchmarks like this. The more useful "makeahllstone" is disk intensive, since it usually spends most of its time traversing trees to find nothing to do. >4. -pipe must be added to CFLAGS in /etc/make.conf. *no other build > optimizations or omissions can be done!* Same goes for additions - > no kerberos bits enabled. > >5. Source tree must be -current to within 7 days of the other people > comparing numbers. No point in compiling old bits just before > perl5 entered the tree, or whatever, since that obviously skews the > numbers. Building an agreed-on old version would be better (check one out from cvs). This would defeat my Makefile optimizations :-). >... 8(?) $TMPDIR should probably be on an mfs. I haven't tried this yet. K6/233: 5273.18 real 3496.20 user 993.51 sys 8620 maximum resident set size 605 average shared memory size 608 average unshared data size 130 average unshared stack size 5923250 page reclaims 18460 page faults 0 swaps 50889 block input operations 28885 block output operations 0 messages sent 0 messages received 8 signals received 384427 voluntary context switches 250941 involuntary context switches Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 19:23:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15969 for freebsd-current-outgoing; Wed, 11 Mar 1998 19:23:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA15956 for ; Wed, 11 Mar 1998 19:23:32 -0800 (PST) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Wed, 11 Mar 1998 22:22:25 -0500 (EST) Received: from elmer.ct.picker.com by ct.picker.com (4.1/SMI-4.1) id AA12213; Wed, 11 Mar 98 22:22:20 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id WAA18045; Wed, 11 Mar 1998 22:22:13 -0500 Message-Id: <19980311222213.10997@ct.picker.com> Date: Wed, 11 Mar 1998 22:22:13 -0500 From: Randall Hopper To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: HEADS UP! (was: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c) Mail-Followup-To: Bruce Evans , current@FreeBSD.ORG References: <199803120203.NAA09967@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803120203.NAA09967@godzilla.zeta.org.au>; from Bruce Evans on Thu, Mar 12, 1998 at 01:03:57PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans: |>Great! Been looking forward to someday putting multiple FreeBSD versions |>on the same disk for a good while. | |That's always been possible, at least if you don't need multiple ufs file |systems. E.g.: | |sd0a: FreeBSD-1.1.x |sd0b: swap |sd0c: reserved |sd0d: reserved for pre-2.0.5 |sd0e: FreeBSD-2.0.x |sd0f: FreeBSD-2.1.x |sd0g: FreeBSD-2.2.x |sd0h: FreeBSD-current Ok. For my purposes, I guess I'd want separate UFSs (separate slices). I'd like to have both -stable and -current-SNAP installed on one disk (with stock sysinstall) such that, if one gets toasted (UFS corrupted; kernel unstable, etc.), I could still boot the other without any boot block tricks (i.e. just select a different slice in OS/BS, loading a different slice's boot record, which would load the kernel from the FreeBSD root in that slice). When I asked about doing this before, the boot block assumption of root on 1st UFS was one of the problems with this scheme. This would make upgrades easier too -- just alternate sysinstalling between the two FreeBSD root UFS slices. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 19:25:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16392 for freebsd-current-outgoing; Wed, 11 Mar 1998 19:25:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hydrogen.nike.efn.org (d182-89.uoregon.edu [128.223.182.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA16373 for ; Wed, 11 Mar 1998 19:25:51 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id TAA14110; Wed, 11 Mar 1998 19:25:40 -0800 (PST) Message-ID: <19980311192540.51520@hydrogen.nike.efn.org> Date: Wed, 11 Mar 1998 19:25:40 -0800 From: John-Mark Gurney To: Ollivier Robert Cc: FreeBSD Current Subject: Re: Amazing :-) References: <14680.889593344@gjp.erols.com> <3506FAE0.21094C16@challenge.isvara.net> <19980312004215.A13486@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <19980312004215.A13486@keltia.freenix.fr>; from Ollivier Robert on Thu, Mar 12, 1998 at 12:42:15AM +0100 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 Ollivier Robert scribbled this message on Mar 12: > With the same settings as Amancio (NOCLEAN & NOPROFILE but an empty > /usr/obj) I get _1h20_ on my K6-225, 64 MB, all disks on a SC-875 (ultra > wide), /usr/src on a DCAS-34330W (async,noatime) and /usr/obj on a > DORS-32160 (async,noatime). what type of ram are you running? and what is the chipset on your motherboard? -- 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 Mar 11 19:42:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18386 for freebsd-current-outgoing; Wed, 11 Mar 1998 19:42:50 -0800 (PST) (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 TAA18381 for ; Wed, 11 Mar 1998 19:42:29 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 14212 invoked by uid 1000); 12 Mar 1998 03:49:56 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [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: <19980312021906.27780@follo.net> Date: Wed, 11 Mar 1998 19:49:56 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Eivind Eklund Subject: RE: Request for objections: 'make regress' Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Mar-98 Eivind Eklund wrote: > This probably goes in tomorrow unless someone protests. > > Added bonus: Included with the introduction is a _free_ regression > test for the LKMs symbol resolving. :-) Go for it! Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 20:01:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21449 for freebsd-current-outgoing; Wed, 11 Mar 1998 20:01:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21434; Wed, 11 Mar 1998 20:01:49 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA14910; Thu, 12 Mar 1998 14:52:02 +1100 Date: Thu, 12 Mar 1998 14:52:02 +1100 From: Bruce Evans Message-Id: <199803120352.OAA14910@godzilla.zeta.org.au> To: bde@zeta.org.au, hasty@rah.star-gate.com, jkh@FreeBSD.ORG Subject: Re: my worldstone Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: >K6/233: > 5273.18 real 3496.20 user 993.51 sys Oops. This was with NOLIBC_R. Add 9 minutes for building libc_r. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 21:06:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29181 for freebsd-current-outgoing; Wed, 11 Mar 1998 21:06:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29162 for ; Wed, 11 Mar 1998 21:06:08 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id VAA04101; Wed, 11 Mar 1998 21:05:51 -0800 (PST) (envelope-from jdp) Message-Id: <199803120505.VAA04101@austin.polstra.com> To: archer@lucky.net Subject: Re: Softupdates code not Prime Time yet. In-Reply-To: <199803112332.BAA02402@grape.carrier.kiev.ua> References: <199803112332.BAA02402@grape.carrier.kiev.ua> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Wed, 11 Mar 1998 21:05:51 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199803112332.BAA02402@grape.carrier.kiev.ua>, Alexander Litvin wrote: > > IF one sends the output of a panic only, without the appropriate > > portion of the namelist, the info is useless. > > Sorry, but it would be much easier if it were possible to > boot stripped kernels. Tor Egge posted a patch to strip on this list a day or two ago that works around the problem. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 21:40:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09153 for freebsd-current-outgoing; Wed, 11 Mar 1998 21:40:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09128; Wed, 11 Mar 1998 21:40:29 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id QAA30374; Thu, 12 Mar 1998 16:09:17 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id GWQLBZYP; Thu, 12 Mar 1998 16:09:45 +0930 Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id QAA09891; Thu, 12 Mar 1998 16:05:48 +1030 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id QAA03855; Thu, 12 Mar 1998 16:05:48 +1030 (CST) Message-ID: <35077432.46050201@dsto.defence.gov.au> Date: Thu, 12 Mar 1998 16:05:46 +1030 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: current@FreeBSD.ORG Subject: Re: Worldstone rules (was: Re: Amazing :-)) References: <1877.889670113@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All very true. So I guess the point is: There should be a set of rules somewhere for people who insist on comparing Worldstones. For people who dont follow the rules: Dont advertise your times unless you're prepared to give full disclosure. I also agree that the numbers dont mean much at all but it is nice to know the ballpark figures for various classes of machines. Jordan K. Hubbard wrote: > > > We cant have formal rules for the majority of -CURRENT users > > because most people are running -CURRENT on their one and only > > machine and dont have much choice as to their /etc/make.conf > > settings. > > Those people don't have to post worldstone ratings either, they can > just chatter informally about what they're doing, but if we're going > to have a pissing contest then let's do it right. :-) [and there does > appear to be a set of folks on this list who are perpetually keen to > do this, so let's not get into a debate on the merits of such contents > please :)]. > > And really, for the rest I have to say that the numbers are too > meaningless to be useful. So you post your workstone rating without > TCL, and Joe posts his without profiled libs, and Harry posts his with > Kerberos enabled and what use are the numbers then to me? They're > useless since to meaningfully compare them with anything I've now got > to go compile my own tree 3 times with these various options set, and > I'm as unlikely to do that as your -current users with one box are > likely to spam themselves. And if a number has no comparative value, > why even bother to communicate it to anyone else? :-) > > Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 22:16:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13653 for freebsd-current-outgoing; Wed, 11 Mar 1998 22:16:18 -0800 (PST) (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 WAA13642 for ; Wed, 11 Mar 1998 22:16:12 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id FAA12574; Thu, 12 Mar 1998 05:47:27 +0100 From: Luigi Rizzo Message-Id: <199803120447.FAA12574@labinfo.iet.unipi.it> Subject: Re: Netboot problem: RPC timeout for server 0x0 To: ambrisko@whistle.com (Doug Ambrisko) Date: Thu, 12 Mar 1998 05:47:27 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199803112120.NAA15073@crab.whistle.com> from "Doug Ambrisko" at Mar 11, 98 01:20:35 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm having trouble with the netboot stuff. I can boot 2.2.5, and -current > kernel as of ~1 month ago, but every since last week any kernel I build starts > displaying > RPC timeout for server 0x0 > contiously. When it should be trying to mount the rootfs. > > I recall someone making a change, but couldn't test it. Does anyboby > remember and can point me in the right direction? possibly "option BOOTP_COMPAT" in the kernel config file ? some bootp implementation send the reply to the client's IP and the latter discards the packet because the IP does not match... the above option does something to ip_input to make this address accepted again. 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 Wed Mar 11 22:30:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15489 for freebsd-current-outgoing; Wed, 11 Mar 1998 22:30:19 -0800 (PST) (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 WAA15484; Wed, 11 Mar 1998 22:30:15 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id WAA15193; Wed, 11 Mar 1998 22:24:25 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd015191; Wed Mar 11 22:24:16 1998 Date: Wed, 11 Mar 1998 22:19:54 -0800 (PST) From: Julian Elischer To: Amancio Hasty cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: my worldstone In-Reply-To: <199803120244.SAA01221@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 that would ruin the test, since I always do the full build.. On Wed, 11 Mar 1998, Amancio Hasty wrote: > >Anything on this list I'm forgetting? > Sure take the profile libs out. > > Amancio > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 22:40:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16425 for freebsd-current-outgoing; Wed, 11 Mar 1998 22:40:55 -0800 (PST) (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 WAA16419; Wed, 11 Mar 1998 22:40:50 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id WAA02299; Wed, 11 Mar 1998 22:40:44 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803120640.WAA02299@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: my worldstone In-reply-to: Your message of "Wed, 11 Mar 1998 22:19:54 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Mar 1998 22:40:43 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Unless you really use the profiled libraries just simply take them out of /etc/make.conf Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 11 23:34:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21092 for freebsd-current-outgoing; Wed, 11 Mar 1998 23:34:47 -0800 (PST) (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 XAA21086 for ; Wed, 11 Mar 1998 23:34:43 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id IAA23092 for current@FreeBSD.ORG; Thu, 12 Mar 1998 08:34:40 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id HAA15466; Thu, 12 Mar 1998 07:42:04 +0100 (CET) (envelope-from roberto) Message-ID: <19980312074204.A15461@keltia.freenix.fr> Date: Thu, 12 Mar 1998 07:42:04 +0100 From: Ollivier Robert To: FreeBSD Current Subject: Re: Amazing :-) Mail-Followup-To: FreeBSD Current References: <14680.889593344@gjp.erols.com> <3506FAE0.21094C16@challenge.isvara.net> <19980312004215.A13486@keltia.freenix.fr> <19980311192540.51520@hydrogen.nike.efn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <19980311192540.51520@hydrogen.nike.efn.org>; from John-Mark Gurney on Wed, Mar 11, 1998 at 07:25:40PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4121 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to John-Mark Gurney: > what type of ram are you running? and what is the chipset on your > motherboard? ASUS P/I P55T2P4 rev.3.1, HX chipset, 64 MB EDO, CPU running at 3x 75 MHz. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 00:52:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28486 for freebsd-current-outgoing; Thu, 12 Mar 1998 00:52:32 -0800 (PST) (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 AAA28477 for ; Thu, 12 Mar 1998 00:52:29 -0800 (PST) (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 IAA10592; Thu, 12 Mar 1998 08:51:45 GMT Date: Thu, 12 Mar 1998 17:51:45 +0900 (JST) From: Michael Hancock To: dave adkins cc: current@FreeBSD.ORG Subject: Re: ext2_sync and NULL inode and VNON v_type 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 Wed, 11 Mar 1998, dave adkins wrote: > There do seem to be bigger problems with ext2fs. Writing a small file that I think ext2fs was done on Lite1 code and no one as really been maintaining it through lite2, the VM changes, and softupdates. It will probably take some time to get it up to date. If someone volunteers they could use ffs as a guide. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 03:36:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA13631 for freebsd-current-outgoing; Thu, 12 Mar 1998 03:36:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from internal.mail.demon.net (internal.mail.demon.net [193.195.224.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13618; Thu, 12 Mar 1998 03:36:29 -0800 (PST) (envelope-from geoffb@demon.net) Received: from office.demon.net (office.demon.net [193.195.224.1]) by internal.mail.demon.net with SMTP id LAA18449; Thu, 12 Mar 1998 11:36:41 GMT Subject: Re: my worldstone To: "Jordan K. Hubbard" Date: Thu, 12 Mar 1998 11:36:23 +0000 (GMT) From: Geoff Buckingham Cc: hasty@rah.star-gate.com, jkh@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <1834.889669810@time.cdrom.com> from "Jordan K. Hubbard" at Mar 11, 98 06:30:10 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-ID: <889702583.0011397.0@office.demon.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Anything on this list I'm forgetting? > Other disk tuneing such as: options AHC_TAGENABLE options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO Does FAILSAFE still have an effect on the NCR driver? Softupdates ? Async mount of the filessystem your writing to? Are people going to go so far as to use a non-standard block and frag sizes? -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 04:47:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19879 for freebsd-current-outgoing; Thu, 12 Mar 1998 04:47:41 -0800 (PST) (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 EAA19872 for ; Thu, 12 Mar 1998 04:47:36 -0800 (PST) (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 MAA04753; Thu, 12 Mar 1998 12:47:35 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id NAA00198; Thu, 12 Mar 1998 13:47:33 +0100 (MET) Message-ID: <19980312134733.38685@follo.net> Date: Thu, 12 Mar 1998 13:47:33 +0100 From: Eivind Eklund To: Michael Hancock , dave adkins Cc: current@FreeBSD.ORG Subject: Re: ext2_sync and NULL inode and VNON v_type References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Michael Hancock on Thu, Mar 12, 1998 at 05:51:45PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 12, 1998 at 05:51:45PM +0900, Michael Hancock wrote: > On Wed, 11 Mar 1998, dave adkins wrote: > > > There do seem to be bigger problems with ext2fs. Writing a small file that > > I think ext2fs was done on Lite1 code and no one as really been > maintaining it through lite2, the VM changes, and softupdates. It will > probably take some time to get it up to date. If someone volunteers they > could use ffs as a guide. AFAIK, it worked fine before the soft-updates integration. After the soft-updates integration it didn't even _compile_. I fixed this - it took three lines of changes, which I snarfed from FFS - but I haven't done any testing etc, and it wouldn't surprise me if there are other, more insidious problems from the integration. I just needed it to compile so it wouldn't block LINT. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 05:42:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25746 for freebsd-current-outgoing; Thu, 12 Mar 1998 05:42:16 -0800 (PST) (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 FAA25735 for ; Thu, 12 Mar 1998 05:42:14 -0800 (PST) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.5/8.7.3) id OAA10903; Thu, 12 Mar 1998 14:44:05 +0100 (CET) Message-ID: <19980312144404.06129@cons.org> Date: Thu, 12 Mar 1998 14:44:04 +0100 From: Martin Cracauer To: Bruce Evans Cc: cracauer@cons.org, freebsd-current@FreeBSD.ORG Subject: Re: make/SIGINT (Re: cvs commit: src/bin/sh jobs.c) References: <199803120152.MAA09328@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199803120152.MAA09328@godzilla.zeta.org.au>; from Bruce Evans on Thu, Mar 12, 1998 at 12:52:03PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The appended fix seems to treat signals right for compat mode, too. I'll do some make world's with patched make and sh over the weekend and look for further trouble. Will try this patched make on Solaris as well, could be fun :-) 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 diff -C 3 -r make.original/compat.c make.work/compat.c *** make.original/compat.c Tue Aug 26 12:06:36 1997 --- make.work/compat.c Thu Mar 12 14:34:33 1998 *************** *** 125,131 **** } } ! exit (signo); } /*- --- 125,132 ---- } } ! (void) signal(signo,SIG_DFL); ! (void) kill(getpid(),signo); } /*- Binary files make.original/compat.o and make.work/compat.o differ diff -C 3 -r make.original/job.c make.work/job.c *** make.original/job.c Tue Aug 26 12:06:38 1997 --- make.work/job.c Thu Mar 12 14:34:55 1998 *************** *** 2904,2910 **** } } (void) eunlink(tfile); - exit(signo); } /* --- 2904,2909 ---- Binary files make.original/job.o and make.work/job.o differ Binary files make.original/make and make.work/make differ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 06:12:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28851 for freebsd-current-outgoing; Thu, 12 Mar 1998 06:12:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from itesec.hsc.fr (root@itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28813; Thu, 12 Mar 1998 06:12:31 -0800 (PST) (envelope-from pb@hsc.fr) Received: from mars.hsc.fr (pb@mars.hsc.fr [192.70.106.44]) by itesec.hsc.fr (8.8.8/8.8.5/itesec-1.10-nospam) with ESMTP id PAA16340; Thu, 12 Mar 1998 15:12:03 +0100 (MET) Received: (from pb@localhost) by mars.hsc.fr (8.8.5/8.8.5/pb-19970301) id PAA00428; Thu, 12 Mar 1998 15:10:59 +0100 (MET) Message-ID: <19980312151059.HP44817@mars.hsc.fr> Date: Thu, 12 Mar 1998 15:10:59 +0100 From: Pierre.Beyssac@hsc.fr (Pierre Beyssac) To: jkh@FreeBSD.ORG (Jordan K. Hubbard) Cc: hasty@rah.star-gate.com (Amancio Hasty), current@FreeBSD.ORG Subject: Re: my worldstone References: <199803120147.RAA01017@rah.star-gate.com> <1834.889669810@time.cdrom.com> X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 In-Reply-To: <1834.889669810@time.cdrom.com>; from Jordan K. Hubbard on Mar 11, 1998 18:30:10 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jordan K. Hubbard: > I know, but the real problem here is that people are still comparing > this "worldstone" figure in the same way they'd compare dhrystones or > xstones or whatever and ultimately people are going to be making > hardware decisions based on those numbers. It's no use saying now > foolish such a practice is, it's simply inevitable - *people like > numbers*. :-) There are two reasons why people do these worldstones: (1) compare hardware (2) compare system configuration tweaks, or other software improvements (different compilers, for example) As long as people keep changing their system config (including removing huge steps of the make world process) to improve their compile time, there's absolutely no point in comparing anything about hardware. Most people posting their results here want (and do) (2) on their own system, and they end up comparing (1) on the list. IMHO this makes no sense. > 4. -pipe must be added to CFLAGS in /etc/make.conf. *no other build > optimizations or omissions can be done!* Same goes for additions - > no kerberos bits enabled. IMHO absolutely no change should be made regarding make world by anybody wanting to compare times with each other. Why not directly include -pipe in the official make.conf if that is so useful? -- Pierre.Beyssac@hsc.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 06:55:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02470 for freebsd-current-outgoing; Thu, 12 Mar 1998 06:55:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02452 for ; Thu, 12 Mar 1998 06:54:52 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id PAA17427; Thu, 12 Mar 1998 15:49:42 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199803121449.PAA17427@ocean.campus.luth.se> Subject: Re: HEADS UP! (was: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c) In-Reply-To: <199803111950.LAA24155@dingo.cdrom.com> from Mike Smith at "Mar 11, 98 11:50:52 am" To: mike@smith.net.au (Mike Smith) Date: Thu, 12 Mar 1998 15:49:42 +0100 (CET) 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 According to Mike Smith: > The bootstrap needs to be taught how to parse the slice number, perhaps > in an extended syntax such as xd(unit,slice,part)kernel although it > would make more sense to me to switch to eg. sd0s1a:/kernel. That would be most welcome. Then it would be possible, even easy, to remember it, and way more logical from a user perspective, at least. > (This isn't going to happen in the short term though; too much > backwards-compatability grief.) Hmm... Isn't this something which is purely userinterface? And if not, why not? /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 07:20:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04182 for freebsd-current-outgoing; Thu, 12 Mar 1998 07:20:36 -0800 (PST) (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 HAA04165; Thu, 12 Mar 1998 07:20:32 -0800 (PST) (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.6.9) with ESMTP id HAA05018; Thu, 12 Mar 1998 07:18:58 -0800 (PST) To: Pierre.Beyssac@hsc.fr (Pierre Beyssac) cc: jkh@FreeBSD.ORG (Jordan K. Hubbard), hasty@rah.star-gate.com (Amancio Hasty), current@FreeBSD.ORG Subject: Re: my worldstone In-reply-to: Your message of "Thu, 12 Mar 1998 15:10:59 +0100." <19980312151059.HP44817@mars.hsc.fr> Date: Thu, 12 Mar 1998 07:18:58 -0800 Message-ID: <5015.889715938@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > IMHO absolutely no change should be made regarding make world by anybody > wanting to compare times with each other. Why not directly include -pipe > in the official make.conf if that is so useful? Because CFLAGS is not set at all in the default make.conf, but merely left as an example. Perhaps that policy should be changed! Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 07:23:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05423 for freebsd-current-outgoing; Thu, 12 Mar 1998 07:23:50 -0800 (PST) (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 HAA05416 for ; Thu, 12 Mar 1998 07:23:47 -0800 (PST) (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 HAA27524; Thu, 12 Mar 1998 07:20:37 -0800 (PST) Message-Id: <199803121520.HAA27524@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mikael Karpberg cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG Subject: bootstrap syntax (was Re: HEADS UP! (was: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c) ) In-reply-to: Your message of "Thu, 12 Mar 1998 15:49:42 +0100." <199803121449.PAA17427@ocean.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Mar 1998 07:20:37 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to Mike Smith: > > The bootstrap needs to be taught how to parse the slice number, perhaps > > in an extended syntax such as xd(unit,slice,part)kernel although it > > would make more sense to me to switch to eg. sd0s1a:/kernel. > > That would be most welcome. Then it would be possible, even easy, > to remember it, and way more logical from a user perspective, at least. At least it would share something in common with other similar namings, just as the current scheme shares something with a number of now-extinct historical namings. > > (This isn't going to happen in the short term though; too much > > backwards-compatability grief.) > > Hmm... > Isn't this something which is purely userinterface? And if not, why not? It would bite: - people with old boot.config files - people with old boot.help files - people that expected the old syntax to work The support issues this would raise would be enormous. -- \\ 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 Mar 12 07:35:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06599 for freebsd-current-outgoing; Thu, 12 Mar 1998 07:35:11 -0800 (PST) (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 HAA06587 for ; Thu, 12 Mar 1998 07:35:08 -0800 (PST) (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 PAA08085; Thu, 12 Mar 1998 15:34:44 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id QAA00872; Thu, 12 Mar 1998 16:34:43 +0100 (MET) Message-ID: <19980312163438.62825@follo.net> Date: Thu, 12 Mar 1998 16:34:38 +0100 From: Eivind Eklund To: Mike Smith , Mikael Karpberg Cc: current@FreeBSD.ORG Subject: Re: bootstrap syntax (was Re: HEADS UP! (was: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c) ) References: <199803121449.PAA17427@ocean.campus.luth.se> <199803121520.HAA27524@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803121520.HAA27524@dingo.cdrom.com>; from Mike Smith on Thu, Mar 12, 1998 at 07:20:37AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 12, 1998 at 07:20:37AM -0800, Mike Smith wrote: > > > (This isn't going to happen in the short term though; too much > > > backwards-compatability grief.) > > > > Hmm... > > Isn't this something which is purely userinterface? And if not, why not? > > It would bite: > > - people with old boot.config files > - people with old boot.help files > - people that expected the old syntax to work > > The support issues this would raise would be enormous. boot.config and boot.help is fairly new files (post 2.2.5, aren't they?); and updating bootblocks is usually not done, at least not be people that don't know enough to also know those files. If we are going to change the format, I think _now_ would be a good time, before it has been in a release. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 07:50:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08454 for freebsd-current-outgoing; Thu, 12 Mar 1998 07:50:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08426 for ; Thu, 12 Mar 1998 07:50:11 -0800 (PST) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id QAA29809; Thu, 12 Mar 1998 16:49:55 +0100 (MET) Message-ID: <19980312164954.50515@geophysik.tu-freiberg.de> Date: Thu, 12 Mar 1998 16:49:54 +0100 From: Holm Tiffe To: freebsd-current@FreeBSD.ORG Subject: make release --- > broken ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, as a non USA resident person I think "make release" is broken under -current, make doRELEASE fails on target release.2 in the kerberosIV stuff. in /usr/src/release/Makefile on line 261: .if exists(${.CURDIR}/../kerberosIV) && !defined(NOKERBEROS) should'nt the NOKERBEROS be NOCRYPT ? Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Strasse der Einheit 26 * * 09599 Freiberg Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 08:43:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14733 for freebsd-current-outgoing; Thu, 12 Mar 1998 08:43:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14694; Thu, 12 Mar 1998 08:43:15 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id RAA17665; Thu, 12 Mar 1998 17:38:08 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199803121638.RAA17665@ocean.campus.luth.se> Subject: Re: idprio/rtprio In-Reply-To: <1099.889666284@time.cdrom.com> from "Jordan K. Hubbard" at "Mar 11, 98 05:31:24 pm" To: jkh@FreeBSD.ORG (Jordan K. Hubbard) Date: Thu, 12 Mar 1998 17:38:08 +0100 (CET) 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 According to Jordan K. Hubbard: > > First, contrary to what the manpage says, an ordinary user can no > > longer run idprio. > > It's the man page that's wrong since this was disallowed awhile back > after BEST Internet filed a PR noting that an ordinary user could put > your system in very bad shape by using it. The man page has been > fixed, thanks. Hmm... I just can't seem to remember how. Breif summary? Also, is it possible to allow users to run things as idleprio with some sysctl, or something? (I trust the users on my machine... me and my GF :) /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 09:10:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17112 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:10:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17105 for ; Thu, 12 Mar 1998 09:10:05 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.8) with ESMTP id LAA00367; Thu, 12 Mar 1998 11:09:45 -0600 (CST) (envelope-from ccsanady@friley585.res.iastate.edu) Message-Id: <199803121709.LAA00367@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: Amancio Hasty cc: current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. In-reply-to: Your message of "Tue, 10 Mar 1998 23:46:01 PST." <199803110746.XAA04791@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Mar 1998 11:09:45 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have to echo what Julian is saying additionally if you are not prepared >to give a kernel stack trace and possibly nice printfs of kernel data >structures then don't try soft updates. I hate bug reports like >"soft update crashed my system" 8) I would, although my system is unable to do a dump. I have been wondering for a while why this is, but it seems that dumpon is just plain broken. It will not work on anything other that the first disk. (no, this is not specific to cam..) This is what happens.. $ dumpon /dev/da1s1b dumpon: sysctl: kern.dumpdev: No space left on device Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 09:10:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17225 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:10:43 -0800 (PST) (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 JAA17218; Thu, 12 Mar 1998 09:10:39 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id JAA02727; Thu, 12 Mar 1998 09:10:33 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803121710.JAA02727@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Pierre.Beyssac@hsc.fr (Pierre Beyssac), current@FreeBSD.ORG Subject: Re: my worldstone In-reply-to: Your message of "Thu, 12 Mar 1998 07:18:58 PST." <5015.889715938@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Mar 1998 09:10:33 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > IMHO absolutely no change should be made regarding make world by anybody > > wanting to compare times with each other. Why not directly include -pipe > > in the official make.conf if that is so useful? > > Because CFLAGS is not set at all in the default make.conf, but > merely left as an example. Perhaps that policy should be changed! > > Jordan Now you are getting it and please change the default behavior of generating profiled libraries. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 09:15:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18413 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:15:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18396 for ; Thu, 12 Mar 1998 09:14:59 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA08296; Thu, 12 Mar 1998 09:14:38 -0800 (PST) (envelope-from jdp) Message-Id: <199803121714.JAA08296@austin.polstra.com> To: ccsanady@friley585.res.iastate.edu Subject: Re: Softupdates code not Prime Time yet. In-Reply-To: <199803121709.LAA00367@friley585.res.iastate.edu> References: <199803121709.LAA00367@friley585.res.iastate.edu> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 12 Mar 1998 09:14:37 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199803121709.LAA00367@friley585.res.iastate.edu>, Chris Csanady wrote: > I would, although my system is unable to do a dump. I have been wondering > for a while why this is, but it seems that dumpon is just plain broken. > It will not work on anything other that the first disk. (no, this is not > specific to cam..) > > This is what happens.. > > $ dumpon /dev/da1s1b > dumpon: sysctl: kern.dumpdev: No space left on device Probably you've added RAM recently. Remember, the dump is the full size of the system RAM, so the dump device has to be at least that large. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 09:23:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19476 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:23:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19456 for ; Thu, 12 Mar 1998 09:23:34 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.8) with ESMTP id LAA00459; Thu, 12 Mar 1998 11:23:04 -0600 (CST) (envelope-from ccsanady@friley585.res.iastate.edu) Message-Id: <199803121723.LAA00459@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. In-reply-to: Your message of "Thu, 12 Mar 1998 09:14:37 PST." <199803121714.JAA08296@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Mar 1998 11:23:04 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In article <199803121709.LAA00367@friley585.res.iastate.edu>, >Chris Csanady wrote: > >> I would, although my system is unable to do a dump. I have been wondering >> for a while why this is, but it seems that dumpon is just plain broken. >> It will not work on anything other that the first disk. (no, this is not >> specific to cam..) >> >> This is what happens.. >> >> $ dumpon /dev/da1s1b >> dumpon: sysctl: kern.dumpdev: No space left on device > >Probably you've added RAM recently. Remember, the dump is the full >size of the system RAM, so the dump device has to be at least that >large. I wish. :) I still have only 64M of ram, and 80M of swap on that disk. Do I still need more than this? If this is the case, I would like to repartition sometime soon anyways.. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 09:29:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20067 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:29:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from UPIMSSMTPUSR03 (smtp.email.msn.com [207.68.143.159]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20062 for ; Thu, 12 Mar 1998 09:29:50 -0800 (PST) (envelope-from danialaa1@email.msn.com) Received: from julieaa - 153.34.40.118 by email.msn.com with Microsoft SMTPSVC; Thu, 12 Mar 1998 09:28:52 -0800 From: "Dan & Julie Aalberg" To: Subject: to the Admin of this list Date: Wed, 11 Mar 1998 21:41:36 -0800 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Message-ID: <045595228170c38UPIMSSMTPUSR03@email.msn.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG it seems that an unsubscribe does not work. Can you please remove me from this list Thanks you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 09:30:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20249 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:30:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20241 for ; Thu, 12 Mar 1998 09:30:09 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA08449; Thu, 12 Mar 1998 09:30:02 -0800 (PST) (envelope-from jdp) Message-Id: <199803121730.JAA08449@austin.polstra.com> To: Chris Csanady cc: current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. In-reply-to: Your message of "Thu, 12 Mar 1998 11:23:04 CST." <199803121723.LAA00459@friley585.res.iastate.edu> Date: Thu, 12 Mar 1998 09:30:02 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> $ dumpon /dev/da1s1b > >> dumpon: sysctl: kern.dumpdev: No space left on device ... > I still have only 64M of ram, and 80M of swap on that disk. Do I > still need more than this? I didn't think so, but I could be wrong. Hopefully somebody who knows for sure will pipe up with an answer. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 09:35:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21149 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:35:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA21138 for ; Thu, 12 Mar 1998 09:35:41 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yDBsf-0004u0-00; Thu, 12 Mar 1998 09:34:57 -0800 Date: Thu, 12 Mar 1998 09:34:55 -0800 (PST) From: Tom To: Eivind Eklund cc: Mike Smith , Mikael Karpberg , current@FreeBSD.ORG Subject: Re: bootstrap syntax (was Re: HEADS UP! (was: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c) ) In-Reply-To: <19980312163438.62825@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Mar 1998, Eivind Eklund wrote: > boot.config and boot.help is fairly new files (post 2.2.5, aren't No, they were in 2.2.5-RELEASE Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 09:37:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21658 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:37:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sophie.bolix.com (sophie.bolix.com [209.107.35.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21647; Thu, 12 Mar 1998 09:37:41 -0800 (PST) (envelope-from imp@pencil-box.village.org) Received: from pencil-box.village.org (tape-box [209.107.35.22]) by sophie.bolix.com (8.8.6/8.8.6) with ESMTP id KAA21438; Thu, 12 Mar 1998 10:37:22 -0700 (MST) Received: from pencil-box.village.org (localhost [127.0.0.1]) by pencil-box.village.org (8.8.8/8.8.3) with ESMTP id KAA00274; Thu, 12 Mar 1998 10:36:47 -0700 (MST) Message-Id: <199803121736.KAA00274@pencil-box.village.org> To: "Gary Palmer" Subject: Re: Amazing :-) Cc: "Alok K. Dhir" , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 11 Mar 1998 00:15:44 EST." <14680.889593344@gjp.erols.com> References: <14680.889593344@gjp.erols.com> Date: Thu, 12 Mar 1998 10:36:47 -0700 From: "M. Warner Losh" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14680.889593344@gjp.erols.com> "Gary Palmer" writes: : Are you sure thats not a 486 DX2 66 in disguise? A dual 300 MHz PII My make buildworlds are in the 2hr range for a PPro 200 with 192M with very few optimizations. -j 4 shaves 10-15% off these times. 13 hours was what I was seeing on my 486 DX2 66 a while ago.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 09:40:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22381 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:40:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from itesec.hsc.fr (root@itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22163; Thu, 12 Mar 1998 09:39:37 -0800 (PST) (envelope-from pb@hsc.fr) Received: from mars.hsc.fr (pb@mars.hsc.fr [192.70.106.44]) by itesec.hsc.fr (8.8.8/8.8.5/itesec-1.10-nospam) with ESMTP id SAA19190; Thu, 12 Mar 1998 18:23:21 +0100 (MET) Received: (from pb@localhost) by mars.hsc.fr (8.8.5/8.8.5/pb-19970301) id SAA01396; Thu, 12 Mar 1998 18:22:17 +0100 (MET) Message-ID: <19980312182217.YM22047@mars.hsc.fr> Date: Thu, 12 Mar 1998 18:22:17 +0100 From: Pierre.Beyssac@hsc.fr (Pierre Beyssac) To: hasty@rah.star-gate.com (Amancio Hasty) Cc: jkh@FreeBSD.ORG (Jordan K. Hubbard), Pierre.Beyssac@hsc.fr (Pierre Beyssac), current@FreeBSD.ORG Subject: Re: my worldstone References: <5015.889715938@time.cdrom.com> <199803121710.JAA02727@rah.star-gate.com> X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 In-Reply-To: <199803121710.JAA02727@rah.star-gate.com>; from Amancio Hasty on Mar 12, 1998 09:10:33 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Amancio Hasty: > Now you are getting it and please change the default behavior of > generating profiled libraries. Personally, I like that default. I sometimes (rarely) profile code and it's good to know profiled libs are here and up-to-date with respect to the other libs. They are the kind of thing I expect to be part of the base OS, that means I expect them to be built by default. -- Pierre.Beyssac@hsc.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 09:42:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23130 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:42:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23112; Thu, 12 Mar 1998 09:42:31 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199803121742.JAA23112@hub.freebsd.org> Subject: Re: to the Admin of this list In-Reply-To: <045595228170c38UPIMSSMTPUSR03@email.msn.com> from Dan & Julie Aalberg at "Mar 11, 98 09:41:36 pm" To: danialaa1@email.msn.com (Dan & Julie Aalberg) Date: Thu, 12 Mar 1998 09:42:30 -0800 (PST) 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 Dan & Julie Aalberg wrote: > it seems that an unsubscribe does not work. Can you please remove me from > this list it works fine. IF you use the same address to unsubscribe as you used to subscribe. your address has changed, that is why you are having trouble. msn changed your address on you ;( i will remove you from both mailing lists. freebsd-announce:danialaa1@msn.com freebsd-current-digest:danialaa1@msn.com jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 09:57:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24781 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:57:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24753 for ; Thu, 12 Mar 1998 09:57:28 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.8) with ESMTP id LAA00619; Thu, 12 Mar 1998 11:57:12 -0600 (CST) (envelope-from ccsanady@friley585.res.iastate.edu) Message-Id: <199803121757.LAA00619@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. In-reply-to: Your message of "Thu, 12 Mar 1998 09:30:02 PST." <199803121730.JAA08449@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Mar 1998 11:57:12 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> $ dumpon /dev/da1s1b >> >> dumpon: sysctl: kern.dumpdev: No space left on device >... >> I still have only 64M of ram, and 80M of swap on that disk. Do I >> still need more than this? > >I didn't think so, but I could be wrong. Hopefully somebody who >knows for sure will pipe up with an answer. Hmm. I feel really terrible now. It seems that my swap was not on the slice that I thought it was. I dislike bios partitions.. Sorry about that.. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 09:57:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24807 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:57:43 -0800 (PST) (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 JAA24758; Thu, 12 Mar 1998 09:57:31 -0800 (PST) (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 SAA05731; Thu, 12 Mar 1998 18:53:43 +0100 (MET) Message-Id: <199803121753.SAA05731@pat.idi.ntnu.no> To: root@mantar.slip.netcom.com Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: spkrtest locks up system In-Reply-To: Your message of "Wed, 11 Mar 1998 18:31:52 -0800 (PST)" References: 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: Thu, 12 Mar 1998 18:53:42 +0100 From: Tor Egge Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On a current SMP system when I run spkrtest the system locks up. > On a kernel built around the 26th of Feb no problem. I have a old version > of spkrtest v1.0 by Eric S. Raymond (Feb 1990) that I use as sort of > a backup alarm clock. I was wondering why for the past couple of weeks > I'd wake up and the machine would be locked up. The current graphical > version does the same thing. I have no sound card installed. One time > it dropped into the debugger , now it just locks up. There was something > about _mplock if i remember right. There was alot of changes to current > around the end of Feb. (SMP and locking) and I'm not sure which is causing > the problem. Sorry I can't be of more help. > Manfred The following patch might be appropiate. Without this patch, the kernel can deadlock or panic when attempting to enter a critical region protected by disable_intr()/enable_intr(), since the mpintr_lock might be held by the last cpu having prezeroed a page. Index: sys/i386/i386/vm_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/vm_machdep.c,v retrieving revision 1.101 diff -u -r1.101 vm_machdep.c --- vm_machdep.c 1998/02/25 03:56:09 1.101 +++ vm_machdep.c 1998/03/08 06:00:49 @@ -950,7 +967,7 @@ if (try_mplock()) { #endif s = splvm(); - enable_intr(); + __asm __volatile("sti" : : : "memory"); m = vm_page_list_find(PQ_FREE, free_rover); if (m != NULL) { --(*vm_page_queues[m->queue].lcnt); @@ -973,7 +990,7 @@ ++cnt_prezero; } splx(s); - disable_intr(); + __asm __volatile("cli" : : : "memory"); #ifdef SMP rel_mplock(); return (1); - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 09:58:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25185 for freebsd-current-outgoing; Thu, 12 Mar 1998 09:58:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25172 for ; Thu, 12 Mar 1998 09:58:38 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA09113; Thu, 12 Mar 1998 09:58:27 -0800 (PST) (envelope-from jdp) Message-Id: <199803121758.JAA09113@austin.polstra.com> To: Chris Csanady cc: current@FreeBSD.ORG Subject: Re: Softupdates code not Prime Time yet. In-reply-to: Your message of "Thu, 12 Mar 1998 11:57:12 CST." <199803121757.LAA00619@friley585.res.iastate.edu> Date: Thu, 12 Mar 1998 09:58:27 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm. I feel really terrible now. It seems that my swap was not on > the slice that I thought it was. :-) Thanks for letting us know. That was a real mystery. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 10:31:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29684 for freebsd-current-outgoing; Thu, 12 Mar 1998 10:31:19 -0800 (PST) (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 KAA29643; Thu, 12 Mar 1998 10:31:16 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id KAA00323; Thu, 12 Mar 1998 10:30:52 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Thu, 12 Mar 1998 10:30:52 -0800 (PST) From: Manfred Antar To: Tor Egge cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: spkrtest locks up system In-Reply-To: <199803121753.SAA05731@pat.idi.ntnu.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Mar 1998, Tor Egge wrote: > > On a current SMP system when I run spkrtest the system locks up. > > On a kernel built around the 26th of Feb no problem. I have a old version > > of spkrtest v1.0 by Eric S. Raymond (Feb 1990) that I use as sort of > > a backup alarm clock. I was wondering why for the past couple of weeks > > I'd wake up and the machine would be locked up. The current graphical > > version does the same thing. I have no sound card installed. One time > > it dropped into the debugger , now it just locks up. There was something > > about _mplock if i remember right. There was alot of changes to current > > around the end of Feb. (SMP and locking) and I'm not sure which is causing > > the problem. Sorry I can't be of more help. > > Manfred > > The following patch might be appropiate. > > Without this patch, the kernel can deadlock or panic when attempting > to enter a critical region protected by disable_intr()/enable_intr(), > since the mpintr_lock might be held by the last cpu having prezeroed > a page. > > Index: sys/i386/i386/vm_machdep.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/i386/vm_machdep.c,v > retrieving revision 1.101 > diff -u -r1.101 vm_machdep.c > --- vm_machdep.c 1998/02/25 03:56:09 1.101 > +++ vm_machdep.c 1998/03/08 06:00:49 > @@ -950,7 +967,7 @@ > if (try_mplock()) { > #endif > s = splvm(); > - enable_intr(); > + __asm __volatile("sti" : : : "memory"); > m = vm_page_list_find(PQ_FREE, free_rover); > if (m != NULL) { > --(*vm_page_queues[m->queue].lcnt); > @@ -973,7 +990,7 @@ > ++cnt_prezero; > } > splx(s); > - disable_intr(); > + __asm __volatile("cli" : : : "memory"); > #ifdef SMP > rel_mplock(); > return (1); > > > - Tor Egge > That did the trick. Thanks 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 Thu Mar 12 10:34:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00733 for freebsd-current-outgoing; Thu, 12 Mar 1998 10:34:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dan.emsphone.com (dan@dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00715; Thu, 12 Mar 1998 10:34:29 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.6/8.8.6) id MAA13009; Thu, 12 Mar 1998 12:34:27 -0600 (CST) Message-ID: <19980312123427.A12954@emsphone.com> Date: Thu, 12 Mar 1998 12:34:27 -0600 From: Dan Nelson To: Mikael Karpberg , "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.ORG Subject: Re: idprio/rtprio References: <1099.889666284@time.cdrom.com> <199803121638.RAA17665@ocean.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.5i In-Reply-To: <199803121638.RAA17665@ocean.campus.luth.se>; from "Mikael Karpberg" on Thu Mar 12 17:38:08 GMT 1998 X-OS: FreeBSD 2.2.5-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Mar 12), Mikael Karpberg said: > According to Jordan K. Hubbard: > > > First, contrary to what the manpage says, an ordinary user can no > > > longer run idprio. > > > > It's the man page that's wrong since this was disallowed awhile > > back after BEST Internet filed a PR noting that an ordinary user > > could put your system in very bad shape by using it. The man page > > has been fixed, thanks. > > Hmm... I just can't seem to remember how. Breif summary? > How? Easy. Run rc564 at idlepri, and run another high-CPU process. Eventually, the rc564 process will try a filesystem operation. After that, every process trying to hit a file will hang too. If you unidprio the rc564 process or kill the high-cpu process (letting rc564 run again) everything will return to normal. I've done this to myself three or four times, and have resorted to running rc564 at nice 20 for now. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 11:27:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07534 for freebsd-current-outgoing; Thu, 12 Mar 1998 11:27:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07479; Thu, 12 Mar 1998 11:27:11 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA01288; Thu, 12 Mar 1998 12:27:08 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd001229; Thu Mar 12 12:26:59 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id MAA09436; Thu, 12 Mar 1998 12:26:53 -0700 (MST) From: Terry Lambert Message-Id: <199803121926.MAA09436@usr08.primenet.com> Subject: Re: spkrtest locks up system To: Tor.Egge@idi.ntnu.no (Tor Egge) Date: Thu, 12 Mar 1998 19:26:53 +0000 (GMT) Cc: root@mantar.slip.netcom.com, current@FreeBSD.ORG, smp@FreeBSD.ORG In-Reply-To: <199803121753.SAA05731@pat.idi.ntnu.no> from "Tor Egge" at Mar 12, 98 06:53:42 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 [ ...yet another good patch from Tor Egge... ] Whoo hoo! Yee-haa! Go, Tor, Go! Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 11:28:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08097 for freebsd-current-outgoing; Thu, 12 Mar 1998 11:28:52 -0800 (PST) (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 LAA08088 for ; Thu, 12 Mar 1998 11:28:50 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id NAA07993 for current@freebsd.org; Thu, 12 Mar 1998 13:28:50 -0600 (CST) From: Kevin Day Message-Id: <199803121928.NAA07993@home.dragondata.com> Subject: Panic: invalid wire count To: current@FreeBSD.ORG Date: Thu, 12 Mar 1998 13:28:49 -0600 (CST) 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 Got this today... Kernel made on March 7th. IdlePTD 259000 initial pcb at 202dd4 panicstr: vm_page_free: invalid wire count (%d), pindex: 0x%x panic messages: --- panic: vm_page_free: invalid wire count (65280), pindex: 0x0 mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 panic: from debugger mp_lock = 01000002; cpuid = 1; lapic.id = 01000000 boot() called on cpu#1 I'm on cpu#1, I need to be on cpu#0, sleeping.. I'm on cpu#1, I need to be on cpu#0, sleeping.. I'm on cpu#1, I need to be on cpu#0, sleeping.. I'm on cpu#1, I need to be on cpu#0, sleeping.. timeout waiting for cpu #0! dumping to dev 20011, offset 85764 dump 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:286 286 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:286 #1 0xf0114242 in panic (fmt=0xf01014e8 "from debugger") at ../../kern/kern_shutdown.c:426 #2 0xf0101505 in db_panic (addr=-266625463, have_addr=0, count=-1, modif=0xf8ccdd54 "") at ../../ddb/db_command.c:432 #3 0xf01013e5 in db_command (last_cmdp=0xf01f3ab4, cmd_table=0xf01f3914, aux_cmd_tablep=0xf020020c) at ../../ddb/db_command.c:332 #4 0xf0101572 in db_command_loop () at ../../ddb/db_command.c:454 #5 0xf0103c33 in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #6 0xf01b9be4 in kdb_trap (type=3, code=0, regs=0xf8ccde44) at ../../i386/i386/db_interface.c:157 #7 0xf01caa58 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -119287392, tf_esi = 256, tf_ebp = -120791416, tf_isp = -120791444, tf_ebx = -266668462, tf_edx = -266625516, tf_ecx = 16777217, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -266625463, tf_cs = 8, tf_eflags = 582, tf_esp = -266625532, tf_ss = -267304541}) at ../../i386/i386/trap.c:474 #8 0xf01b9e49 in Debugger (msg=0xf01141a3 "panic") at ../../i386/i386/db_interface.c:316 #9 0xf0114239 in panic ( fmt=0xf01af652 "vm_page_free: invalid wire count (%d), pindex: 0x%x") at ../../kern/kern_shutdown.c:424 #10 0xf01af738 in vm_page_freechk_and_unqueue (m=0xf0545610) at ../../vm/vm_page.c:1113 ---Type to continue, or q to quit--- #11 0xf01af8e8 in vm_page_free_zero (m=0xf0545610) at ../../vm/vm_page.c:1220 #12 0xf01c7621 in pmap_release_free_page (pmap=0xf8e3d1a0, p=0xf0545610) at ../../i386/i386/pmap.c:1211 #13 0xf01c7789 in pmap_release (pmap=0xf8e3d1a0) at ../../i386/i386/pmap.c:1373 #14 0xf01a8c1b in vmspace_free (vm=0xf8e3d140) at ../../vm/vm_map.c:244 #15 0xf01d0625 in cpu_wait (p=0xf8ea2800) at ../../i386/i386/vm_machdep.c:715 #16 0xf010d363 in wait1 (q=0xf8c7e840, uap=0xf8ccdf94, compat=0) at ../../kern/kern_exit.c:495 #17 0xf010d17c in wait4 (p=0xf8c7e840, uap=0xf8ccdf94) at ../../kern/kern_exit.c:395 #18 0xf01cb5cb in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 0, tf_esi = 52, tf_ebp = -272638588, tf_isp = -120791068, tf_ebx = 537419872, tf_edx = -1, tf_ecx = 33504, tf_eax = 7, tf_trapno = 12, tf_err = 7, tf_eip = 537177729, tf_cs = 31, tf_eflags = 534, tf_esp = -272638612, tf_ss = 39}) at ../../i386/i386/trap.c:994 #19 0x2004ae81 in ?? () #20 0x1be5 in ?? () #21 #22 0x1b63 in ?? () #23 0x1b63 in ?? () #24 0x1875 in ?? () #25 0x1099 in ?? () I'm grabbing new sources now, just thought I'd report this. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 11:39:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10499 for freebsd-current-outgoing; Thu, 12 Mar 1998 11:39:28 -0800 (PST) (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 LAA10447; Thu, 12 Mar 1998 11:39:21 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id MAA17943; Thu, 12 Mar 1998 12:39:17 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd017919; Thu Mar 12 12:39:12 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id MAA10032; Thu, 12 Mar 1998 12:39:08 -0700 (MST) From: Terry Lambert Message-Id: <199803121939.MAA10032@usr08.primenet.com> Subject: Re: Worldstone rules (was: Re: Amazing :-)) To: Matthew.Thyer@dsto.defence.gov.au (Matthew Thyer) Date: Thu, 12 Mar 1998 19:39:08 +0000 (GMT) Cc: jkh@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <35077432.46050201@dsto.defence.gov.au> from "Matthew Thyer" at Mar 12, 98 04:05: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 > So I guess the point is: There should be a set of rules somewhere > for people who insist on comparing Worldstones. Someone (who cares about it) should write a shell script that check the environment for "worldstone compliance" by grovelling /etc/make.conf and whatever other things you decide the environment needs to have set. I'd say it should grovel dmesg and/or /var/log/messages for as much information as it can get on the hardware, grovel mount options on drives, and so on, as well. This script should be run when you type "make worldstone", and either deny the build (explaining why), or print out "You could be a contender!", the start time, and then go for it. The output of the configuration grovelling, and the timing, should be written to a file called "worldstone", probably in /usr/src. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 11:42:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11420 for freebsd-current-outgoing; Thu, 12 Mar 1998 11:42:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11374 for ; Thu, 12 Mar 1998 11:41:46 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA06328; Thu, 12 Mar 1998 12:41:34 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd006242; Thu Mar 12 12:41:23 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id MAA10146; Thu, 12 Mar 1998 12:41:18 -0700 (MST) From: Terry Lambert Message-Id: <199803121941.MAA10146@usr08.primenet.com> Subject: Re: ext2_sync and NULL inode and VNON v_type To: eivind@yes.no (Eivind Eklund) Date: Thu, 12 Mar 1998 19:41:17 +0000 (GMT) Cc: michaelh@cet.co.jp, adkin003@tc.umn.edu, current@FreeBSD.ORG In-Reply-To: <19980312134733.38685@follo.net> from "Eivind Eklund" at Mar 12, 98 01:47:33 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 > AFAIK, it worked fine before the soft-updates integration. After the > soft-updates integration it didn't even _compile_. I fixed this - it > took three lines of changes, which I snarfed from FFS - but I haven't > done any testing etc, and it wouldn't surprise me if there are other, > more insidious problems from the integration. I just needed it to > compile so it wouldn't block LINT. I'm curious, but not enough to drive home during lunch. What did you have to change? There was not supposed to be an impact. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 11:47:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12752 for freebsd-current-outgoing; Thu, 12 Mar 1998 11:47:14 -0800 (PST) (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 LAA12743 for ; Thu, 12 Mar 1998 11:47:10 -0800 (PST) (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 TAA11390; Thu, 12 Mar 1998 19:47:06 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id UAA03066; Thu, 12 Mar 1998 20:47:05 +0100 (MET) Message-ID: <19980312204704.62898@follo.net> Date: Thu, 12 Mar 1998 20:47:04 +0100 From: Eivind Eklund To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: ext2_sync and NULL inode and VNON v_type References: <19980312134733.38685@follo.net> <199803121941.MAA10146@usr08.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199803121941.MAA10146@usr08.primenet.com>; from Terry Lambert on Thu, Mar 12, 1998 at 07:41:17PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 12, 1998 at 07:41:17PM +0000, Terry Lambert wrote: > > AFAIK, it worked fine before the soft-updates integration. After the > > soft-updates integration it didn't even _compile_. I fixed this - it > > took three lines of changes, which I snarfed from FFS - but I haven't > > done any testing etc, and it wouldn't surprise me if there are other, > > more insidious problems from the integration. I just needed it to > > compile so it wouldn't block LINT. > > I'm curious, but not enough to drive home during lunch. What did > you have to change? There was not supposed to be an impact. Here is the diff: Index: ext2_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/gnu/ext2fs/ext2_vfsops.c,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- ext2_vfsops.c 1998/03/01 22:45:52 1.29 +++ ext2_vfsops.c 1998/03/09 14:46:57 1.30 @@ -648,9 +648,9 @@ ump->um_seqinc = EXT2_FRAGS_PER_BLOCK(fs); for (i = 0; i < MAXQUOTAS; i++) ump->um_quotas[i] = NULLVP; - devvp->v_specflags |= SI_MOUNTEDON; - if (ronly == 0) - ext2_sbupdate(ump, MNT_WAIT); + devvp->v_specmountpoint = mp; + if (ronly == 0) + ext2_sbupdate(ump, MNT_WAIT); return (0); out: if (bp) @@ -706,7 +706,7 @@ if (fs->s_block_bitmap[i]) ULCK_BUF(fs->s_block_bitmap[i]) - ump->um_devvp->v_specflags &= ~SI_MOUNTEDON; + ump->um_devvp->v_specmountpoint = NULL; error = VOP_CLOSE(ump->um_devvp, ronly ? FREAD : FREAD|FWRITE, NOCRED, p); vrele(ump->um_devvp); Note that some of this is whitespace change due to the old formatting being plain wrong. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 11:55:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14718 for freebsd-current-outgoing; Thu, 12 Mar 1998 11:55:00 -0800 (PST) (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 LAA14125 for ; Thu, 12 Mar 1998 11:52:43 -0800 (PST) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.8) id OAA07517; Thu, 12 Mar 1998 14:52:08 -0500 (EST) Message-ID: <19980312145208.07230@rtfm.net> Date: Thu, 12 Mar 1998 14:52:08 -0500 From: Nathan Dorfman To: current@FreeBSD.ORG Subject: Slew of binutils commits lately 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 Sorry if my question is redundant, but I have only had a working computer for a week--my motherboard blew up over a month ago and I couldn't keep track of all the FreeBSD news since all I had were the school 3.11/NetWare computers. Anyway, I'm noticing an onslaught of updates with binutils these past few days--what does this indicate? Anything monumental or earthshaking? Or are these just "routine" upgrades to binutils? Is it safe to cvsup and make world in the middle of this conversion or should I wait until it's complete? FreeBSD limbo 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Wed Jan 21 14:35:01 EST 1998 nathan@limbo:/usr/src/sys/compile/LIMBO i386 :\ -- ________________ _______________________________ / 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 Thu Mar 12 12:03:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16516 for freebsd-current-outgoing; Thu, 12 Mar 1998 12:03:19 -0800 (PST) (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 MAA16433 for ; Thu, 12 Mar 1998 12:02:44 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id PAA15655 for ; Thu, 12 Mar 1998 15:00:57 -0500 (EST) Date: Thu, 12 Mar 1998 15:00:57 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: FreeBSD-current@FreeBSD.ORG Subject: cvs question 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've made modifications to a small part of my checked out src tree that I don't want cvs to reset on me when I do an update. I remember something about using a .cvsignore file, but I don't see anything like what I seem to recall in the man page. I _think_ it was something like sticking an empty .cvsignore file in the top directory of the stuff I want ignored. Do I have it right? ----------------------------+----------------------------------------------- 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 Thu Mar 12 12:09:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17592 for freebsd-current-outgoing; Thu, 12 Mar 1998 12:09:35 -0800 (PST) (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 MAA17582 for ; Thu, 12 Mar 1998 12:09:32 -0800 (PST) (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 UAA11613; Thu, 12 Mar 1998 20:09:20 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id VAA03700; Thu, 12 Mar 1998 21:09:19 +0100 (MET) Message-ID: <19980312210918.13360@follo.net> Date: Thu, 12 Mar 1998 21:09:18 +0100 From: Eivind Eklund To: Nathan Dorfman , current@FreeBSD.ORG Subject: Re: Slew of binutils commits lately References: <19980312145208.07230@rtfm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980312145208.07230@rtfm.net>; from Nathan Dorfman on Thu, Mar 12, 1998 at 02:52:08PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 12, 1998 at 02:52:08PM -0500, Nathan Dorfman wrote: > Sorry if my question is redundant, but I have only had a working computer > for a week--my motherboard blew up over a month ago and I couldn't keep > track of all the FreeBSD news since all I had were the school 3.11/NetWare > computers. Anyway, I'm noticing an onslaught of updates with binutils these > past few days--what does this indicate? Anything monumental or earthshaking? Both alpha build support and i386 ELF support is going in at the same time. > Or are these just "routine" upgrades to binutils? Is it safe to cvsup and > make world in the middle of this conversion or should I wait until it's > complete? It seems to be safe; no reports of build-problems lately, at least. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 12:11:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18109 for freebsd-current-outgoing; Thu, 12 Mar 1998 12:11:51 -0800 (PST) (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 MAA18092 for ; Thu, 12 Mar 1998 12:11:46 -0800 (PST) (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 UAA11634; Thu, 12 Mar 1998 20:11:23 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id VAA03725; Thu, 12 Mar 1998 21:11:22 +0100 (MET) Message-ID: <19980312211122.46447@follo.net> Date: Thu, 12 Mar 1998 21:11:22 +0100 From: Eivind Eklund To: Chuck Robey , FreeBSD-current@FreeBSD.ORG Subject: Re: cvs question References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Chuck Robey on Thu, Mar 12, 1998 at 03:00:57PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 12, 1998 at 03:00:57PM -0500, Chuck Robey wrote: > I've made modifications to a small part of my checked out src tree that > I don't want cvs to reset on me when I do an update. I remember > something about using a .cvsignore file, but I don't see anything like > what I seem to recall in the man page. What do you mean 'reset'? CVS don't "reset" anything for, it just display questionmarks saying that it doesn't know anything about those files. > I _think_ it was something like sticking an empty .cvsignore file in the > top directory of the stuff I want ignored. Do I have it right? ~/.cvsignore contains filenames that should be ignored no matter what dir they are in, one per line. /.cvsignore contains filenames that should be ignored in _that_ directory, one per line. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 12:20:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19679 for freebsd-current-outgoing; Thu, 12 Mar 1998 12:20:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19674 for ; Thu, 12 Mar 1998 12:20:53 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id MAA10040; Thu, 12 Mar 1998 12:20:47 -0800 (PST) (envelope-from jdp) Message-Id: <199803122020.MAA10040@austin.polstra.com> To: eivind@yes.no Subject: Re: Slew of binutils commits lately In-Reply-To: <19980312210918.13360@follo.net> References: <19980312145208.07230@rtfm.net> <19980312210918.13360@follo.net> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 12 Mar 1998 12:20:47 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980312210918.13360@follo.net>, Eivind Eklund wrote: > It seems to be safe; no reports of build-problems lately, at least. I should hope not -- binutils isn't being built by make world yet. :-) It's still disabled in "src/gnu/usr.bin/Makefile". -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 12:34:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21423 for freebsd-current-outgoing; Thu, 12 Mar 1998 12:34:52 -0800 (PST) (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 MAA21411 for ; Thu, 12 Mar 1998 12:34:47 -0800 (PST) (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 UAA11871 for ; Thu, 12 Mar 1998 20:34:41 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id VAA03788; Thu, 12 Mar 1998 21:34:40 +0100 (MET) Message-ID: <19980312213435.09042@follo.net> Date: Thu, 12 Mar 1998 21:34:35 +0100 From: Eivind Eklund To: current@FreeBSD.ORG Subject: 'make regress' added 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 I've added the 'regress' target. To be able to regress-test the LKMs (which are the only test yet added to the tree), you'll have to have all the LKMs and the LKM kernel already built. I'll try to think up a (good) way of including the LKM kernel in the dependecies here. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 12:49:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24381 for freebsd-current-outgoing; Thu, 12 Mar 1998 12:49:01 -0800 (PST) (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 MAA24355; Thu, 12 Mar 1998 12:48:56 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id MAA00687; Thu, 12 Mar 1998 12:48:34 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Thu, 12 Mar 1998 12:48:34 -0800 (PST) From: Manfred Antar To: Terry Lambert cc: Tor Egge , current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: spkrtest locks up system In-Reply-To: <199803121926.MAA09436@usr08.primenet.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, 12 Mar 1998, Terry Lambert wrote: > [ ...yet another good patch from Tor Egge... ] > > > Whoo hoo! > > Yee-haa! > > Go, Tor, Go! > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > Here Here ============================== || 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 Thu Mar 12 12:54:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25510 for freebsd-current-outgoing; Thu, 12 Mar 1998 12:54:24 -0800 (PST) (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 MAA25412 for ; Thu, 12 Mar 1998 12:53:56 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id PAA15755; Thu, 12 Mar 1998 15:52:10 -0500 (EST) Date: Thu, 12 Mar 1998 15:52:10 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Eivind Eklund cc: FreeBSD-current@FreeBSD.ORG Subject: Re: cvs question In-Reply-To: <19980312211122.46447@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Mar 1998, Eivind Eklund wrote: > On Thu, Mar 12, 1998 at 03:00:57PM -0500, Chuck Robey wrote: > > I've made modifications to a small part of my checked out src tree that > > I don't want cvs to reset on me when I do an update. I remember > > something about using a .cvsignore file, but I don't see anything like > > what I seem to recall in the man page. > > What do you mean 'reset'? CVS don't "reset" anything for, it just > display questionmarks saying that it doesn't know anything about those > files. Thanks. I knew what I meant by reset (but you can't read my mind, can you?), I didn't want cvs to touch the files at all, under any circumstances, for about a month. I didn't want any updates merged. I think I can do that by using the .cvsignore, which it seems I _did_ have partially wrong, but your response is clear enough for me. Thanks. > > > I _think_ it was something like sticking an empty .cvsignore file in the > > top directory of the stuff I want ignored. Do I have it right? > > ~/.cvsignore contains filenames that should be ignored no matter what > dir they are in, one per line. > > /.cvsignore contains filenames that should be ignored in > _that_ directory, one per line. > > Eivind. > > ----------------------------+----------------------------------------------- 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 Thu Mar 12 13:08:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28375 for freebsd-current-outgoing; Thu, 12 Mar 1998 13:08:34 -0800 (PST) (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 NAA28347; Thu, 12 Mar 1998 13:08:29 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id QAA00516; Thu, 12 Mar 1998 16:01:21 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Thu, 12 Mar 1998 16:01:21 -0500 (EST) From: "Alok K. Dhir" To: Tor.Egge@idi.ntnu.no cc: root@mantar.slip.netcom.com, current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: spkrtest locks up system 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 Could this patch be related to the lockups I've been experiencing when trying to play sounds on recent -current kernels? Sound (dsp, etc) hasn't worked for at least a couple of weeks now... Thanks On Thu, 12 Mar 1998 Tor.Egge@idi.ntnu.no wrote: > > > > On a current SMP system when I run spkrtest the system locks up. > > On a kernel built around the 26th of Feb no problem. I have a old version > > of spkrtest v1.0 by Eric S. Raymond (Feb 1990) that I use as sort of > > a backup alarm clock. I was wondering why for the past couple of weeks > > I'd wake up and the machine would be locked up. The current graphical > > version does the same thing. I have no sound card installed. One time > > it dropped into the debugger , now it just locks up. There was something > > about _mplock if i remember right. There was alot of changes to current > > around the end of Feb. (SMP and locking) and I'm not sure which is > causing > > the problem. Sorry I can't be of more help. > > Manfred > > The following patch might be appropiate. > > Without this patch, the kernel can deadlock or panic when attempting > to enter a critical region protected by disable_intr()/enable_intr(), > since the mpintr_lock might be held by the last cpu having prezeroed > a page. > > Index: sys/i386/i386/vm_machdep.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/i386/vm_machdep.c,v > retrieving revision 1.101 > diff -u -r1.101 vm_machdep.c > --- vm_machdep.c 1998/02/25 03:56:09 1.101 > +++ vm_machdep.c 1998/03/08 06:00:49 > @@ -950,7 +967,7 @@ > if (try_mplock()) { > #endif > s = splvm(); > - enable_intr(); > + __asm __volatile("sti" : : : "memory"); > m = vm_page_list_find(PQ_FREE, free_rover); > if (m != NULL) { > --(*vm_page_queues[m->queue].lcnt); > @@ -973,7 +990,7 @@ > ++cnt_prezero; > } > splx(s); > - disable_intr(); > + __asm __volatile("cli" : : : "memory"); > #ifdef SMP > rel_mplock(); > return (1); > > > - Tor Egge > > 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 \ R7-003, ITSMC 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 Thu Mar 12 13:21:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00997 for freebsd-current-outgoing; Thu, 12 Mar 1998 13:21:06 -0800 (PST) (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 NAA00956; Thu, 12 Mar 1998 13:20:55 -0800 (PST) (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 WAA19505; Thu, 12 Mar 1998 22:16:58 +0100 (MET) Message-Id: <199803122116.WAA19505@pat.idi.ntnu.no> To: adhir@worldbank.org Cc: root@mantar.slip.netcom.com, current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: spkrtest locks up system In-Reply-To: Your message of "Thu, 12 Mar 1998 16:01:21 -0500 (EST)" References: 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: Thu, 12 Mar 1998 22:16:57 +0100 From: Tor Egge Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Could this patch be related to the lockups I've been experiencing when > trying to play sounds on recent -current kernels? > > Sound (dsp, etc) hasn't worked for at least a couple of weeks now... No. Prezeroing of pages in SMP mode was not enabled before Mar 1 1998 04:18:50 UTC, which is less than a couple of weeks ago. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 13:47:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05327 for freebsd-current-outgoing; Thu, 12 Mar 1998 13:47:00 -0800 (PST) (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 NAA05318 for ; Thu, 12 Mar 1998 13:46:55 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id OAA03355; Thu, 12 Mar 1998 14:46:53 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd003200; Thu Mar 12 14:46:45 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id OAA19166; Thu, 12 Mar 1998 14:46:43 -0700 (MST) From: Terry Lambert Message-Id: <199803122146.OAA19166@usr06.primenet.com> Subject: Re: cvs question To: eivind@yes.no (Eivind Eklund) Date: Thu, 12 Mar 1998 21:46:42 +0000 (GMT) Cc: chuckr@glue.umd.edu, FreeBSD-current@FreeBSD.ORG In-Reply-To: <19980312211122.46447@follo.net> from "Eivind Eklund" at Mar 12, 98 09:11:22 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 > On Thu, Mar 12, 1998 at 03:00:57PM -0500, Chuck Robey wrote: > > I've made modifications to a small part of my checked out src tree that > > I don't want cvs to reset on me when I do an update. I remember > > something about using a .cvsignore file, but I don't see anything like > > what I seem to recall in the man page. > > What do you mean 'reset'? CVS don't "reset" anything for, it just > display questionmarks saying that it doesn't know anything about those > files. He means CVSUP. I've had the same problem myself. Effectively, there's supposed to be two ways around this, but I'll be damned if I could get either one of them to ever work properly. Primus There is supposedly a branch tag called "LOCAL" that will be checked in "real soon now" (stated in June of 1996; hasn't happened yet). If you check changes in with this tag (guaranteed to never be used in the source tree, and therefore never updated), they are supposed to be able to live across a CVSUP. Secondus There is supposedly a "magic" revision ID that you can use on a local branch point that CVSUP won't touch. I've been told "1000" and "1001" and various other values, but I haven't seen a way for it to actually work. One real problem here is that you really want to CVSUP FreeBSD down to a local tree, as if you owned the local tree, and FreeBSD was on a continuously updated vendor branch. This would let you "merge to head" incrementally. For instance, I have a huge number of local changes, some of which have been committed to FreeBSD, and most of which haven't. I want to "merge to HEAD" for all the changes that *have* been committed, because they show as deltas in my local repository (if FreeBSD is actually a vendor-tagged branch). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 13:57:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07211 for freebsd-current-outgoing; Thu, 12 Mar 1998 13:57:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA07206 for ; Thu, 12 Mar 1998 13:57:07 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yDFxx-0004CU-00; Thu, 12 Mar 1998 13:56:41 -0800 Date: Thu, 12 Mar 1998 13:56:39 -0800 (PST) From: Tom To: Terry Lambert cc: Eivind Eklund , chuckr@glue.umd.edu, FreeBSD-current@FreeBSD.ORG Subject: Re: cvs question In-Reply-To: <199803122146.OAA19166@usr06.primenet.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, 12 Mar 1998, Terry Lambert wrote: > Secondus There is supposedly a "magic" revision ID that you > can use on a local branch point that CVSUP won't > touch. I've been told "1000" and "1001" and various > other values, but I haven't seen a way for it to > actually work. Not quite. There is an enviroment variable you can set with a revision number. "1000" is recommended, but it is unlikely anything else is using a number that high. Any changes you check it, get this revision number. Can't remember, the environment variable to use... This method is still pretty rough. AFAIK, you still have to checkout your local changes after checking out the main branch. For the tiny changes I required, just using cvsup in check out mode, and maintaining a patch kit which I just re-apply after cvsup'ing saved a lot of time, and a lot of storage. I just can't build my own release. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 14:47:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17854 for freebsd-current-outgoing; Thu, 12 Mar 1998 14:47:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from katipo.niwa.cri.nz (home.niwa.cri.nz [131.203.55.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17652; Thu, 12 Mar 1998 14:47:06 -0800 (PST) (envelope-from wdk@katipo.niwa.cri.nz) Received: from localhost (wdk@localhost) by katipo.niwa.cri.nz (8.8.6/8.8.6) with SMTP id LAA26864; Fri, 13 Mar 1998 11:48:04 +1300 (NZDT) Date: Fri, 13 Mar 1998 11:48:03 +1300 (NZDT) From: Wayne Knowles To: Bruce Evans cc: hasty@rah.star-gate.com, jkh@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: my worldstone In-Reply-To: <199803120304.OAA12807@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Mar 1998, Bruce Evans wrote: > Building an agreed-on old version would be better (check one out from > cvs). This would defeat my Makefile optimizations :-). > > >... > > 8(?) $TMPDIR should probably be on an mfs. I haven't tried this yet. I would seriously suggest you give it a try. From some benchmarks earlier in the year I found that creating a 8MB mfs for /var/tmp shaved 20 minutes off my make world time vs. using -pipe Since we are playing the worldstone game, here is my results but I will admit to cheating and building with NOCLEAN and NOPROFILE Pentium II 300 MHz, 128MB RAM Adaptec 2940UW with TAGGING and SCB Paging enabled 2 x Cheetah 4.5GB Fast & Wide 10,000 rpm Disks /usr/obj Mounted noatime,async /usr/src Mounted noatime,async /var/tmp 8MB mfs filesystem (seems to be big enough) /etc/make.conf - as shipped empty /usr/obj Build: make -DNOCLEAN -DNOPROFILE -j3 buildworld Build time: 55 minutes and 30 seconds (Wow!) >From memory dropping the NOCLEAN and NOPROFILE options clocked in around 1:15, but that was several weeks ago. The exact figures are at home. As another comparison, I did a make release on -current last weekend and it built in just on 2 hrs 30 minutes - a significant improvement over 12 hrs++ on my old P100 system. A releasestone might be a better benchmark as the master CVS repository valules are used for make.conf and it is almost impossible to change what is built (correct me if I am wrong here) If I get time over the weekend, I am going to backup my system and install the softupdate patches followed by the CAM patches to see what improvement they make. Wayne -- _____ Wayne Knowles, Systems Manager / o \/ National Institute of Water & Atmospheric Research Ltd \/ v /\ P.O. Box 14-901 Kilbirnie, Wellington, NEW ZEALAND `---' Email: w.knowles@niwa.cri.nz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 16:02:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02555 for freebsd-current-outgoing; Thu, 12 Mar 1998 16:02:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.scsn.net (scsn.net [206.25.246.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02430 for ; Thu, 12 Mar 1998 16:02:17 -0800 (PST) (envelope-from dmaddox@scsn.net) Received: from rhiannon.scsn.net ([208.133.153.66]) by mail.scsn.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-41950U6000L1100S0) with ESMTP id AAA158 for ; Thu, 12 Mar 1998 18:58:07 -0500 Received: (from root@localhost) by rhiannon.scsn.net (8.8.8/8.8.7) id TAA00331; Thu, 12 Mar 1998 19:02:27 -0500 (EST) (envelope-from root) Message-ID: <19980312190227.64220@scsn.net> Date: Thu, 12 Mar 1998 19:02:27 -0500 From: dmaddox@scsn.net (Donald J. Maddox) To: current@FreeBSD.ORG Subject: Panics with SoftUpdates Reply-To: dmaddox@scsn.net Mail-Followup-To: current@FreeBSD.ORG 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 I have seen this post-panic trace several times after enabling the softupdates stuff (just FYI): db> trace _Debugger(f0120d08) at _Debugger+0x35 _panic(f0186540,f018651d,3000c,1c78,f073e8d4) at _panic+0x5a _ffs_blkfree(f2c2de4c,1c78,2000,410d00,f2c2de4c) at _ffs_blkfree+0x1b7 _indir_trunc(f2c2de4c,410d00,0,c,f2c2de3c) at _indir_trunc+0x14c _handle_workitem_freeblocks(f089f180) at _handle_workitem_freeblocks+0x110 _softdep_process_worklist(0) at _softdep_process_worklist+0x94 _sched_sync(f2c21bef,f0141e63,f02022e4,1fff000,f01aeb93) at _sched_sync+0x12e _kproc_start(f02022e4) at _kproc_start+0x32 _fork_trampoline() at _fork_trampoline+0x13 db> -------- # dmesg Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Mon Mar 9 20:57:42 EST 1998 root@rhiannon.scsn.net:/usr/src/sys/compile/RHIANNON Timecounter "i8254" frequency 1193182 Hz cost 2422 ns Timecounter "TSC" frequency 166193864 Hz cost 212 ns CPU: Pentium (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30388224 (29676K bytes) Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x00 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 ahc0: rev 0x00 int a irq 10 on pci0.10.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs scbus0 at ahc0 bus 0 ahc0: target 0 Tagged Queuing Device sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 507MB (1039329 512 byte sectors) sd0: with 2380 cyls, 6 heads, and an average 72 sectors/track cd0 at scbus0 target 1 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM cd present [318523 x 2048 byte records] vga0: rev 0x00 int a irq 11 on pci0.12.0 Probing for PnP devices: CSN 1 Vendor ID: CTL009e [0x9e008c0e] Serial 0x09f665ec Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 12 flags 0x20000 on isa sio2: type ST16650A sio3 at 0x2e8-0x2ef irq 9 on isa sio3: type 16550A pca0 on motherboard pca0: PC speaker audio driver wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-32 wd0: 1277MB (2615760 sectors), 2595 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , DMA, 32-bit, multi-block-16 wd1: 5009MB (10258920 sectors), 10856 cyls, 15 heads, 63 S/T, 512 B/S fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at ? drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: awe0 at 0x620 on isa awe0: opl0 at 0x388 on isa snd0: joy0 at 0x201 on isa joy0: joystick Intel Pentium F00F detected, installing workaround changing root device to wd1s2a ffs_mountfs: superblock updated To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 16:41:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08258 for freebsd-current-outgoing; Thu, 12 Mar 1998 16:41:48 -0800 (PST) (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 QAA08249 for ; Thu, 12 Mar 1998 16:41:44 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA12067; Thu, 12 Mar 1998 16:37:06 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd012064; Thu Mar 12 16:37:00 1998 Message-ID: <35087EA5.4487EB71@whistle.com> Date: Thu, 12 Mar 1998 16:32:37 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: dmaddox@scsn.net CC: current@FreeBSD.ORG Subject: Re: Panics with SoftUpdates References: <19980312190227.64220@scsn.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donald J. Maddox wrote: > > I have seen this post-panic trace several times after enabling the > softupdates stuff (just FYI): > > db> trace > _Debugger(f0120d08) at _Debugger+0x35 thanks.. noted.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 17:01:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12477 for freebsd-current-outgoing; Thu, 12 Mar 1998 17:01:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhost (user-38lcb34.dialup.mindspring.com [209.86.44.100]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA12419 for ; Thu, 12 Mar 1998 17:01:07 -0800 (PST) (envelope-from rlb@mindspring.com) Received: from mindspring.com by mailhost with smtp (Smail3.1.29.1 #1) id m0yDIqO-000In7C; Thu, 12 Mar 98 20:01 EST Message-ID: <35088554.ED785058@mindspring.com> Date: Thu, 12 Mar 1998 20:01:08 -0500 From: Ron Bolin X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.6 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: i386 and Alpha Src Tree Question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since I have only Intel class machines like many others. Does it make sense to organize the tree where cvsups and the general make file sequence does not download or depend on the Alpha code being in the tree? It seems like we are going to have lots of space taken up by the Alpha code. Correct me if I am out of line, maybe there are plans for this, but then again I am just inquiring. Maybe I missed the original thread too. Example: # find . -type d -name 'alpha*' -exec du -sk {} \; 284 ./contrib/gcc/config/alpha 27 ./contrib/libgmp/mpn/alpha 2 ./gnu/usr.bin/binutils/ld/alpha 95 ./gnu/usr.bin/binutils/libbfd/alpha 9 ./gnu/usr.bin/binutils/as/alpha 11 ./lib/csu/alpha 124 ./lib/libc/alpha 7 ./lib/msun/alpha 135 ./sys/alpha Thanks Ron -- ------------------------------------------------------------------------------- Ron Bolin, Sr. Software Eng, NetChannel Web: http://www.netchannel.net E-mail: rbolin@netchannel.net Web: http://www.gsu.edu/~gs01rlb Ph: 770-729-2929 Ext 249 Hm: 770-992-8877 Web: http://www.mindspring.com/~rlb ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 17:15:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14994 for freebsd-current-outgoing; Thu, 12 Mar 1998 17:15:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from comp.polyu.edu.hk (csns02.comp.polyu.edu.hk [158.132.25.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA14980 for ; Thu, 12 Mar 1998 17:15:18 -0800 (PST) (envelope-from c5666305@comp.polyu.edu.hk) Received: from cssolar83.COMP.HKP.HK by comp.polyu.edu.hk (SMI-8.6/SMI-SVR4) id JAA20798; Fri, 13 Mar 1998 09:15:10 +0800 Received: (from c5666305@localhost) by cssolar83.COMP.HKP.HK (SMI-8.6/) id JAA24312 for freebsd-current@FreeBSD.ORG; Fri, 13 Mar 1998 09:15:08 +0800 Message-Id: <199803130115.JAA24312@cssolar83.COMP.HKP.HK> Subject: how to upgrade from 2.2.5 to current To: freebsd-current@FreeBSD.ORG Date: Fri, 13 Mar 1998 09:15:07 +0800 (HKT) From: "c5666305" X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I would like to know the procedures to upgrade to current from 2.2.5. Thanks. Clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 17:30:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17476 for freebsd-current-outgoing; Thu, 12 Mar 1998 17:30:19 -0800 (PST) (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 RAA17470 for ; Thu, 12 Mar 1998 17:30:15 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA13598 for ; Thu, 12 Mar 1998 17:22:36 -0800 (PST) Received: from UNKNOWN(), claiming to be "crab.whistle.com" via SMTP by alpo.whistle.com, id smtpd013591; Thu Mar 12 17:22:29 1998 Received: (from ambrisko@localhost) by crab.whistle.com (8.8.8/8.6.12) id RAA02278 for freebsd-current@FreeBSD.ORG; Thu, 12 Mar 1998 17:21:13 -0800 (PST) From: Doug Ambrisko Message-Id: <199803130121.RAA02278@crab.whistle.com> Subject: Re: Netboot problem: RPC timeout for server 0x0 In-Reply-To: <199803112120.NAA15073@crab.whistle.com> from Doug Ambrisko at "Mar 11, 98 01:20:54 pm" To: freebsd-current@FreeBSD.ORG Date: Thu, 12 Mar 1998 17:21:13 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL29 (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've narrowed this problem down but haven't really made any progress. I found the problem is cause by this commit: date: 1998/02/20 16:36:17; author: phk; state: Exp; lines: +1 -1 Replace TOD clock code with more systematic approach. Highlights: * Simple model for underlying hardware. * Hardware basis for timekeeping can be changed on the fly. * Only one hardware clock responsible for TOD keeping. * Provides a real nanotime() function. * Time granularity: .232E-18 seconds. * Frequency granularity: .238E-12 s/s * Frequency adjustment is continuous in time. * Less overhead for frequency adjustment. * Improves xntpd performance. The files touched are: sys/i386/conf/files.i386 sys/i386/include/clock.h sys/i386/isa/clock.c sys/i386/isa/random_machdep.c sys/kern/kern_clock.c sys/kern/kern_ntptime.c sys/kern/kern_time.c sys/sys/time.h sys/sys/timex.h If go back in time just before this then it is fine, just after then it breaks. The time is 2/20/98 8:40:00 then it breaks, 8:30 is fine. I couldn't find anything obvious to me that causes this the netboot stuff to fail. It seems that packets aren't be sent out. However, by removing this change and then doing an update to get to current. The netbooted machine is much more stable and hasn't died yet. Before it used to die when building a kernel, tonight the make world test. So nfs is looking much better which was what I wanted to test in the first place. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 17:32:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18077 for freebsd-current-outgoing; Thu, 12 Mar 1998 17:32:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA18072 for ; Thu, 12 Mar 1998 17:32:45 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yDJKt-0000sC-00; Thu, 12 Mar 1998 17:32:35 -0800 Date: Thu, 12 Mar 1998 17:32:32 -0800 (PST) From: Tom To: c5666305 cc: freebsd-current@FreeBSD.ORG Subject: Re: how to upgrade from 2.2.5 to current In-Reply-To: <199803130115.JAA24312@cssolar83.COMP.HKP.HK> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Mar 1998, c5666305 wrote: > Hello, > > I would like to know the procedures to upgrade to current from 2.2.5. > Thanks. > > Clarence Please read the FreeBSD Handbook on www.freebsd.org It tells you everything you need to know. IMO, if you have to ask how to upgrade to current, current probably isn't right for you. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 17:48:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20390 for freebsd-current-outgoing; Thu, 12 Mar 1998 17:48:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smoke.marlboro.vt.us (smoke.marlboro.vt.us [198.206.215.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20368; Thu, 12 Mar 1998 17:48:37 -0800 (PST) (envelope-from cgull@smoke.marlboro.vt.us) Received: (from cgull@localhost) by smoke.marlboro.vt.us (8.8.7/8.8.7/cgull) id UAA16736; Thu, 12 Mar 1998 20:48:21 -0500 (EST) Date: Thu, 12 Mar 1998 20:48:21 -0500 (EST) Message-Id: <199803130148.UAA16736@smoke.marlboro.vt.us> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 From: cgull+usenet-889752903@smoke.marlboro.vt.us (john hood) To: sos@FreeBSD.ORG Cc: mike@smith.net.au (Mike Smith), freebsd@atipa.com, cgull@smoke.marlboro.vt.us, freebsd-current@FreeBSD.ORG Subject: Re: When will busmastering be committed? In-Reply-To: <199803120733.IAA21265@sos.freebsd.dk> References: <199803120353.TAA25717@dingo.cdrom.com> <199803120733.IAA21265@sos.freebsd.dk> X-Mailer: VM 6.31 under Emacs 19.34.2 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA20382 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [redirected to -current from -stable] Søren Schmidt writes: > In reply to Mike Smith who wrote: > > > > > > More precisely, IDE DMA busmastering for certain chipsets (PIIX-based, et > > > al). I believe the code was by a Mr Hood. (John Hood?) > > > > Ah. I don't think John is a regular -stable reader, nor are Soren nor > > John Dyson, the comitters most serious about the code. > > > > Last I recall, there were some concerns about a number of issues still > > outstanding. I've copied John and Soren on this; let's see what they > > have to say on the matter. > > Hmm, there are no immediate plans to get the DMA stuff backported to > 2.2.X, there are differences between -current and stable that makes > this a nontrivial task. Besides I've just found out that we have some > nasty problems in there that we DONT want to get into -stable. Whee! *More* nasty problems? What are they? I've got some stuff that *was* all ready to commit-- it fixes one major and a few minor problems with the DMA code. (The major problem involved probing for and storing the alternate status port address for PCI controllers). I've been lame about sending it along and getting it committed. The whole wd disk driver really needs a rewrite; there's all kinds of problems in there. I've made unenthusiastic noises about doing this in the past, and I certainly haven't written any code... Soren/John, email me in private so we can smash our code together again, eh? --jh -- Mr. Belliveau said, "the difference was the wise, John Hood, cgull intelligent look on the face of the cow." He was @ *so* right. --Ofer Inbar smoke.marlboro.vt.us To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 18:35:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27565 for freebsd-current-outgoing; Thu, 12 Mar 1998 18:35:10 -0800 (PST) (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 SAA27545 for ; Thu, 12 Mar 1998 18:34:54 -0800 (PST) (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 WAA13097; Thu, 12 Mar 1998 22:36:30 GMT Message-ID: <008101bd4e28$27691b60$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: , "c5666305" Subject: Re: how to upgrade from 2.2.5 to current Date: Thu, 12 Mar 1998 21:31:36 -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 you might be interested in looking at my web page... it has a handy tutorial and a cgi program to generate the nessesary files... -Alfred http://a-t34.rh.sunyit.edu/~perlsta click on the "unix" link, then look at the bottom of the page.. let me add that if you already have the 2.2-stable source tree you will probably want to remove it before upgrading. -----Original Message----- From: c5666305 To: freebsd-current@FreeBSD.ORG Date: Thursday, March 12, 1998 4:19 PM Subject: how to upgrade from 2.2.5 to current >Hello, > >I would like to know the procedures to upgrade to current from 2.2.5. >Thanks. > >Clarence > > >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 Mar 12 18:38:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28479 for freebsd-current-outgoing; Thu, 12 Mar 1998 18:38:55 -0800 (PST) (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 SAA28474 for ; Thu, 12 Mar 1998 18:38:50 -0800 (PST) (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 CAA15111; Fri, 13 Mar 1998 02:37:56 GMT Date: Fri, 13 Mar 1998 11:37:56 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: Eivind Eklund , adkin003@tc.umn.edu, current@FreeBSD.ORG Subject: Re: ext2_sync and NULL inode and VNON v_type In-Reply-To: <199803121941.MAA10146@usr08.primenet.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, 12 Mar 1998, Terry Lambert wrote: > > AFAIK, it worked fine before the soft-updates integration. After the > > soft-updates integration it didn't even _compile_. I fixed this - it > > took three lines of changes, which I snarfed from FFS - but I haven't > > done any testing etc, and it wouldn't surprise me if there are other, > > more insidious problems from the integration. I just needed it to > > compile so it wouldn't block LINT. > > I'm curious, but not enough to drive home during lunch. What did > you have to change? There was not supposed to be an impact. There's a lot of code shared with ext2fs. There are #ifdef EXT2FS's all over the ffs code. There are also ext2fs only modules that are very similar to their ffs counterparts, but slightly different. A good example is ext2_fsync, this one was not lite2ified. The ufs directory code could have been used in it's entirety if it weren't for some small gratutious changes in the ext2 on-disk directory format. The other main differences include a different block allocation scheme and no fragment support. They use block groups, which take the ffs cylinder group wins without the geometry based code. Other than that they look very much the same. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 18:43:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29593 for freebsd-current-outgoing; Thu, 12 Mar 1998 18:43:09 -0800 (PST) (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 SAA29587 for ; Thu, 12 Mar 1998 18:43:06 -0800 (PST) (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.6.9) with ESMTP id SAA08876; Thu, 12 Mar 1998 18:41:55 -0800 (PST) To: "c5666305" cc: freebsd-current@FreeBSD.ORG Subject: Re: how to upgrade from 2.2.5 to current In-reply-to: Your message of "Fri, 13 Mar 1998 09:15:07 +0800." <199803130115.JAA24312@cssolar83.COMP.HKP.HK> Date: Thu, 12 Mar 1998 18:41:55 -0800 Message-ID: <8873.889756915@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, > > I would like to know the procedures to upgrade to current from 2.2.5. See the handbook at http://www.freebsd.org - leading people through upgrades is not really a function of this mailing list. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 19:10:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03681 for freebsd-current-outgoing; Thu, 12 Mar 1998 19:10:23 -0800 (PST) (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 TAA03671 for ; Thu, 12 Mar 1998 19:10:17 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 1452 invoked by uid 1000); 13 Mar 1998 03:17:45 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 12 Mar 1998 19:17:45 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: freebsd-current@FreeBSD.ORG Subject: A question about sys/sys/queue.h Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why was the definition of some macros changed from: #define FOO { ... } to: #define FOO do { ... } while(0) I thought these are the same... ---------- 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 Thu Mar 12 19:39:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10314 for freebsd-current-outgoing; Thu, 12 Mar 1998 19:39:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10294; Thu, 12 Mar 1998 19:39:40 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199803130339.TAA10294@hub.freebsd.org> Subject: Re: A question about sys/sys/queue.h In-Reply-To: from Simon Shapiro at "Mar 12, 98 07:17:45 pm" To: shimon@simon-shapiro.org Date: Thu, 12 Mar 1998 19:39:39 -0800 (PST) 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 Simon Shapiro wrote: > Why was the definition of some macros changed > from: > > #define FOO { ... } > > to: > > #define FOO do { ... } while(0) > > I thought these are the same... > the difference lies in how you use them. in the first case one writes "FOO" in the second "FOO;" ^ make a macro act more like a statement. imagine the code around the macro rather then the macro itself. first saw this in _C_traps_and_pitfalls_ by andrew koenig (sp?) jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 20:17:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15087 for freebsd-current-outgoing; Thu, 12 Mar 1998 20:17:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from unix.tfs.net (as2-p80.tfs.net [139.146.205.80] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15061 for ; Thu, 12 Mar 1998 20:17:07 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id WAA00360 for freebsd-current@freebsd.org; Thu, 12 Mar 1998 22:16:54 -0600 (CST) From: Jim Bryant Message-Id: <199803130416.WAA00360@unix.tfs.net> Subject: cal(1) To: freebsd-current@FreeBSD.ORG Date: Thu, 12 Mar 1998 22:16:54 -0600 (CST) Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #5: Sun Mar 8 12:29:10 CST 1998 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ??????????????????? -=[WHY]=- ???????????????????????? [from a cvsup of a few minutes ago] Delete src/usr.bin/cal/Makefile Delete src/usr.bin/cal/README Delete src/usr.bin/cal/cal.1 Delete src/usr.bin/cal/cal.c ??????????????????? -=[WHY]=- ???????????????????????? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 20:21:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16262 for freebsd-current-outgoing; Thu, 12 Mar 1998 20:21:24 -0800 (PST) (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 UAA16247 for ; Thu, 12 Mar 1998 20:21:13 -0800 (PST) (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 FAA16144; Fri, 13 Mar 1998 05:21:06 +0100 (MET) Message-Id: <199803130421.FAA16144@pat.idi.ntnu.no> To: ambrisko@whistle.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Netboot problem: RPC timeout for server 0x0 In-Reply-To: Your message of "Thu, 12 Mar 1998 17:21:13 -0800 (PST)" References: <199803130121.RAA02278@crab.whistle.com> 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: Fri, 13 Mar 1998 05:21:05 +0100 From: Tor Egge Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If go back in time just before this then it is fine, just after then > it breaks. The time is 2/20/98 8:40:00 then it breaks, 8:30 is fine. This is actually a very good indication of what's going wrong. Try this patch. Index: sys/nfs/bootp_subr.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/bootp_subr.c,v retrieving revision 1.9 diff -u -r1.9 bootp_subr.c --- bootp_subr.c 1998/02/09 06:10:32 1.9 +++ bootp_subr.c 1998/03/13 04:17:52 @@ -766,10 +766,10 @@ return; /* - * Bump time if 0. + * Wait until arp entries can be handled. */ - if (!time.tv_sec) - time.tv_sec++; + while (time.tv_sec == 0) + tsleep(&time, PZERO+8, "arpkludge", 10); /* * Find a network interface. Index: sys/nfs/nfs_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_vfsops.c,v retrieving revision 1.55 diff -u -r1.55 nfs_vfsops.c --- nfs_vfsops.c 1998/03/01 22:46:30 1.55 +++ nfs_vfsops.c 1998/03/13 04:20:09 @@ -399,8 +399,8 @@ * XXX time must be non-zero when we init the interface or else * the arp code will wedge... */ - if (time.tv_sec == 0) - time.tv_sec = 1; + while (time.tv_sec == 0) + tsleep(&time, PZERO+8, "arpkludge", 10); if (nfs_diskless_valid==1) nfs_convert_diskless(); Index: sys/nfs/krpc_subr.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/krpc_subr.c,v retrieving revision 1.7 diff -u -r1.7 krpc_subr.c --- krpc_subr.c 1997/10/28 15:59:03 1.7 +++ krpc_subr.c 1998/03/13 04:13:11 @@ -337,7 +337,7 @@ timo++; else printf("RPC timeout for server 0x%x\n", - ntohl(sin->sin_addr.s_addr)); + ntohl(sa->sin_addr.s_addr)); /* * Wait for up to timo seconds for a reply. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 20:23:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16712 for freebsd-current-outgoing; Thu, 12 Mar 1998 20:23:06 -0800 (PST) (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 UAA16681 for ; Thu, 12 Mar 1998 20:23:00 -0800 (PST) (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 EAA15820 for ; Fri, 13 Mar 1998 04:22:20 GMT Date: Fri, 13 Mar 1998 13:22:20 +0900 (JST) From: Michael Hancock To: freebsd-current@FreeBSD.ORG Subject: 4 WILLRELE's to bite the dust Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-1804928587-889762940=:15693" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---559023410-1804928587-889762940=:15693 Content-Type: TEXT/PLAIN; charset=US-ASCII This patch regularizes the releasing of dvp's for vop_create, vop_mkdir, vop_mknod, and vop_symlink. 4 down, 12 to go. Again lock state will be done at a later time. Please test these, especially nfs and ipfilter. I've only been able to test on ffs, nullfs, and union. My testing just consisted of make world while doing ... find / -type f -exec head {} \; > /dev/null. I did some simple testing of nullfs and union. It's seems Kato-san has gotten them pretty stable. What kind of things cause problems with null and union? To apply do: cd /tmp tar -zxvf vop1.tgz cd /sys patch < /tmp/vop1/vop1.diff recompile kernel To reverse: patch -R < /tmp/vop1/vop1.diff Don't commit right away, I'm going to do a few more vops to minimize the number of commits needed. I'll handle the special cases like a vgone'd OUT **vpp which was a work-around to take care of aliases on block devices, etc. in later commits. Regards, Mike Hancock ---559023410-1804928587-889762940=:15693 Content-Type: APPLICATION/octet-stream; name="vop1.tgz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: H4sIAEKkCDUAA+08+XfaSNL5Ff6K3uStH9hgdCCuHDMeB8/y4oA/wJ5819OT JRFrDRKrA8eZyf7tW9XdEpKQbPDBJLv0S9yi1equrrurS1o4c7H24nkLqQtN RSEvCBaB101e80bSUARJlMRmvY43FUl6QZRnhouWwPM1l5AXruP4d/W7tOxt gLPtskD6459D/8ud639EEQWhAWTNpb8kR/SXhLpEiAiMILwgwjPBkyj/4fQf mp+DqeZaX01SJ7/1Tk+H3dMuAYYgmvvZOywWC3Ct6q6p+WYF29XZtWG54aXt GOzSu51NLfu6WBw7RJvPp7edYlE3SM279YpzzdevyBtC2cywJhPaK7DDfux+ dRjv8Gfj5T+lLOUf8f48c9wt/4okN5pJ/S+KclPeyf82Ss82zC8d8tkOauYX X5p4tFIXtjP3DvXi28eX4vB4RCbW1OyQWuC5NX3h1TxXR81Qy5m2sii6pu9a 5sKyPxMXKs9ybCIeykoR2ZRUA1J18SdJQFutVhMNBbHdbtUEuSaIRBA7crMj twp0lIODg5yeDSIKHbHVkYTizz+TaqspV5rkgFU//1wkhULh68Q1zZKtzUxL /erYoBd1e159p9vq3L4MJuXXtNf5yUi9OBl2uyV/Ma8QC3pYqh3MLk3QnsbM MUzecTEPfOwDP6vhT4P+PICfF4Mz9bx/Ojj+gI0VIsRmcx2djwHoClyblEzX dVzW9q1IXpk2oIuto9Wg66AVW8day1h3FclFJNew1hJWV5BcQFtp4gJYxRaw r8EgmrqYz8lbAnPDQ07gd+DW/UurJmFcB8QVCF8FIDwTQt73hr+cfhj1/gea oMGyzWUT3O1eqL/AVZcuQxTaLVwHr+lC6ICwBIrro1OAggGB2F3CATYYbO0e wzEpWJMQEvL7etR8QroULET5xXjQ4zSnSxPrlMd4/XTCsm1ZEUWlzRZC66eS li0Kiyi2GJexGlfAWaYUDjaZap89skdGRxfd0fhoOC6Tt2+JUF6XlzYWn/24 nEYrEPAeh5lLhriUDLJPQDL8K5OAz2nqvuPeEs8hMzDaxDC16dTRwS+lHSxw Rc1D+kztuTQApyc6urASYdmEyCR/vCW9vnr8t6P+r128FaMyt7LXpmvXAmuu q2AIXfMfz29gV2fMt61S0rZKJAkpGtdEC7eZErWZUkeUOxK1rhK1rlldwby2 0bwq0LVNiV6XKw1yUA+N6yvL1qeBYZI3CDyu6fDqXVazYXp6xq0ZkBabD1LN TmD7Gd0pe2S0I8Gzm33Hu8E7CLtSp1pCUYSKKDB+XWi+7x4uNNW/nZuoIUfA T6/jN1AJwI3S0fFxdzQ66w4/jkAI/wlcNFcnRvXdxFD1meZdU35DnjztHo26 Jds4tC2VMib+w94BMwj0vvrbsDfuUqaO7AJOD88fD7tH48QAe+w6dqnbaFko jOUyyMJjnkdZQhguUBXiZnL5aPXdQqWkqJCojc5XmGu2pZdeBvZcBT/b6IBv NgdxNw0SDUO8YD53XP9lNANTftnqcIGqJoSTNeDsnqNfmz7cClC0cTrWkpTQ xcSD/ayng37Zgg+cMWWujLaT/m9bISlYUUiTTUvRaxGh3VGaHUks0JFQSnP6 Aj8LrY4sgcvMvZa6gIJK6xa3iN+IOfVM5n0kWObjh/7gfTbH0L5QchinsDnr RMxDgxH3cQ6z9QnQEeKjXwbD8eAsA2aAMHRvhLbMPTclX+BPeieDTIEfHR8N fy0FGvfryiD14OpRBQDX/yQrGuChCiAUhnsokSn7r1PCv+Hzj5H92fXEmjj3 S/6KrH9D36a2H/oQCuVTSYj4dHMckgQORv/98bTX/7A2FmBkzb+iwxyNRt3h WF26Ft0EMl/yoNnLRyGOD3I/5+dDkwYmfxvFl4a4lmSpXWmTA0mWGxVRTMnD XWy/NH1PyfkkxbmwBduMc++jFg18Po5WdIj7KYXD/2Vp3qgjGYJPZXxtUO+l eqxnhmSlreKWwkLp+XLtoSIk7KEikDiUoTFMxnikmqQQQekorU69WaBjhJZw JRhEvVVwbIUGj0GAUjlA9S+G21sk1YQy+x4ZqN1Px6dlZuMWGJwAQVhobKcF u4OLI9rhfNS76LKtaJzLoXuMz7N1eyHfvYs9vhf+QoOLD2GYNWqkbA/QcfO5 0WDU3hYyR8s239FACdGIWlMmfGGrzty07zcChZQDmLmpz2H92NpesnONl6v9 U71TnRNigftO1ZocAvNuRy5iE+YKhthICIbYIAk4qWTEGjKcxEaBjkJFI6sn uoh1KkR1FmAUaXxRDHdyfyUMX6C95oUqOSVVaCyS5WkSeF/VQq+/PHTyfDfQ fTYb2TfQbz/ADhntpDA4H6duYHwB7yyf0J3ZHKyW7aMFI/uwnU/ep6qf7AP3 hh4ed/Dk5SKoV8nX8Cm2Btr++CXkPPn4tUhNujllVbQW0PUZ9KDt3x85ZKGO S2AVXUJh7niedTm9JTeWf0U0Mglc/8p0CdvIRwvirsx3Sh6uPWaWp0+8mmEu wr/bMq/5M+cb2mRwSJFIEmJUKImWhJ5odzA+1C7QcVCj5HcFfSJ3ZIXxcAt9 eWkZwUyFYzRXm2WEaeC/P3uCKBBqW3OacWPq6NdhEEiuSwikXJejfXFt/9On T0S/MvVrMgHbumQi0/cBrx4pIS5NF9iljMHKV7gZxSdXHVh2wkGNVXTYEV4C k0WtoQFO2t/o6Zj1jdq47eWml1FkvT00DzQDwJegya/DAK6s1CkqlOYTo4K7 JT8SLkRJlCqigjtRsYkXiI900a800Ama6mvuZ4xBRTe+0Rj27wBTUu8wxWTZ PgH04KVhq3NiMGUT2CiqGIew7IlDLm9pB3Nhz6AP/kEHMmO8Inn/y9mw1x+X or3k/9kvy3wjgg4VkCEUWN8x7Bgh9mDucpnqWbZLWWI0fZgRo54Qo1r2wQZf HoZqChyfsNkUZcSnXMcLyl8AlaoZhgrc496WCslBUaznuB03kDfwFG502v8A Du3lLQ1D9c9PTyuE/d1D/GSt2IAVL+wS3q6+w4H2YGnkeVdMgw7d8dF4PCwt 4mydHoTtEXIGThyO4iqjIwm+h8yAflPgOewCj8IkDZsdTKe8UgGV27RsWVPn mjYpGVOFzWESZDRtiZZ4VoEkdeqNjojnHhKLqGZ3BY4VYBspdQRm2uqCiFtJ rDgz/76UbKr4EKlAkto+/CH75FgDLWqAVNMJCJVfzyEL15yaBNYxdW5MdzEn lgf3fGKbpmEa7FFwkMxDQkYmHpJpum8tTKLZBuBAn2rW7DAeOYnU5cfBeX88 HiDj0MvSbF6GrRDMPcPVsUAuoYx1cTYenA5+6w4vzpC3KCehAjtAhkP4SvzI Oj/AwOlGVRj7q3rBpbs1hlmdOJ9d2kl2aZMEvPSULNawDDo0kAMkuaPUC3QU eki22jP0mLCzku0Hh1qcPc1UeWCHJ5JJFf8lZIy3nFav089TWwgDzKALp/p5 vzfoR2Snp0rQ5Urzrmjwi19HR6Dwe4FBjvAHKGN+WbhGX8k0mEPfkukhAlYr sdko7mEfRpotFd/LjPDR56gjsKfbNJyXEaBLWv3VUyeKhmvvSjOcm/ujc5kR aBYeUsIUleX5AIsChccDw+6vr2PNPEqqY52MegY2nk+psDG7MyCUEw5KPr23 CNEThn02fGQVo/HeMdTGmzNwvLD53v/RB3wpXhicdfvUVk54zgxFVuzkPUPO t7vZypg5f7OVtEiKQpIQL3XMSmQzUjIYvlGUmJLJ3pcJzU6dJbpJAmVeVsW1 DFp7so8KJG7/Q1lH+YaNGHhgsQ5hbgl6EmdHw25/vKHWiQtsOea30sA/2fe0 hWlQJfF66SOv3IvrJ8u7ubJ80wn8uIqkm/KFFjrtikDju1iF8lsA1jzhOSLw i/N3FNE976sfTvkRf2GGOFrdZrze2FXkk2UIqRHJ5v0bntk8puqScrieEJKV KOuqGFK0iTQzTxGXyVKZ+Ukb+pxJn6E7HJyM4spWadQpsRqN745Y7NT0iWi1 7rH2eqRq0hQrpSVtk1Si1GhXJAE3b025Irb5zHfSZzN8R55ANr6rhWS6JE0d pJ5pispruQ1p+qxxpHdwL32qNDEhvjI2PM1xW8xLKxGPnEgGz7Bgvh5HBeIk bBB5zuHK6ldZaLlZ3BKbyEqL7fHlhhjGTAqFk96n8zNwOCLSryvlTyDJ4dl/ Hm+FlyyC82AeWvsIf3VXzxz65yZP6EV5huOBM8PrrblQ2dPm+k+NpP/UUEga YPSgUm3xNwDAMYJdvYx5Ug3mQ+V2bhNR7EB//rqA2GoyFmY14+DPju+QS80I j/afNgd3TereHSB63x0PLkqGmeQBlpyLoG+UVP9QiHI3VpJIzRareDKzYU60 YErTVDIgSwWsUhnwTxSzK3V7/Yuj01DcCrV90h+MwVM7/lv3PUZAKEfUZXaq yOp/C45g66qLbF318My3oE8DzzddCuccfRrbvOFtzALh07Bs6c9lJ1GRBAo6 q8Po27pcRAkdzxpcOZiAJ8qvyU8//YRM8JSR1lJ3cAYsNjo/O0upZtv0Lfhf m00nqjWfPr9SXpkwP2KWDJiRJYhUDYe/lunkddzEygJTwOzAMN0rzM2pix1Z 4gfeNJUcq/D0KUpGcw1zgcloMII60/4O5v3NG9Iqkz+IFTmbK8lmeuAi+qOL OxLPHpsz+YCsV+4/WHNEizp1tIfvEWgL02ErzGRvm5nsjZnJTjCTnWATsSaL RJAwTUWRY8xkZzOT0hE5Myk0UolVK5XYyHkpYqU3b1q5+YobsNCflHW7PvNk BuRC1uESKKYkMF8AAWvlP8Qd4hji2jSHQGo31kSctENc7OwxVFp44oevM5ju YgsaKzFbfii3lQzltkgMRHqyGP1c2r82ERod0EeyUqAj0GPFdL8wA0+udxSF e2QKTZihdWgD+U6f0QJfdfcNK8yPtP/huQsVNq7TOOn77+OW7WHvAuUnhK7/ PgesGKBbO1QZT5rm76RgKkWBDeNc/h0e56PFc6lptGTV84vWchhz/BiSWwpz e1vLU57wXZhiIvM3lF3MUvDL+GtNtGfl+a4rofSEh6aOPMwr2Tblkrm8nHB3 MS0SdKa65nx6y3YjiH1GmkajQfm/0RSXPmDuSOtw/+OY/8FeHUPgJpHf2NsC 63Jz7C0ohr0mDeOLjVY9xth0p8qPTVg+zjrs+wTc+yjm3QbmDzIY9w6+TSGS 2n1JaFPDL4ntkGERxWtw5sNeUKIRS3yFR886013fhjMsrR21TBryXBzFmFGS 2YvBkqwoj8DMui8BZZ9xb4qPzV/uYVyz8q5q4fKr6Tqlkq4ZhgumY3IF8HrW V9OZlOzJVbm84vNsKRCbmi7X62mJCa+nJRI7FXy1s2Kp4bsHCr6WA2OEfk9G 0BX2dHWpI9XDZEuxIko02ZJe8JMtZn+FLxNeYkyWeu/T4KH98mM/yJCMz7BP ZaR04a88tY+fKbBXBpMpfYnxy88IbvKjHoBrEEjfO3Tnum77/9s/GZ0NB8dM /f7/wQH3gKSmRA0Fq1kez3gAnSkQ1Xd29DmE/sfB+95Jr/s+4vsbXcebVBGk HkJEwPT0YFZ4mg+0LE+WZPZlElbHPofxYxAGIU2/T7aXeJ2szJ1TgX24hNU/ BGmaLeZ2sPo7Arm2X6QfIPkwDYzPoA0/anPS7X7qjcbk7TsiEM3zghkqPv9K 84mFOSZEI9QxJWDq8dJ3b8MvkrDDIYl94aQltX5ENpyadizJBx1MaOFKocXe /+I1M9jRnihxsGCbN8zMbecjTbEYeYB5WOz/tixmxpS5VrOZzCxttkmQsppB vtVsd+qYV9rkeaW5VhMjoS2uFLmykJfK4sf8tpkoS8wisfpH/LpZlub+tuXP mUWnrYLYYKmAYvQdr3+TT5RJgsSXJoVLe2VN8CNu/3U+GB/hYIlsQh463Q90 5phDHdOALAGxysgIjNorHixfB6LmA+1Hb0JuTKK5Jk3Mx09VOTe26RJnkvyw VYX3x9R8/sCVpl+jkqAPeDSRv0JKjg0WxnDgabA4N9gI9mZqwJ8yX2RDYots SE8q2NuWa0lo8pzUpvKEcr1FsZZEgWcuCD/Md9hgD8VhFr/v77CZk0nGp9jW +zrbn/3Z1V3ZlV3ZlV3ZlV3ZlV3ZlV3ZlV3ZlV3ZlV3ZlV3ZlV3ZlV3ZlV3Z lWcp/wLPydUJAHgAAA== ---559023410-1804928587-889762940=:15693-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 20:53:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20775 for freebsd-current-outgoing; Thu, 12 Mar 1998 20:53:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feldman.dyn.ml.org (green@1Cust1.max1.washington.dc.ms.uu.net [153.34.49.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20766 for ; Thu, 12 Mar 1998 20:52:54 -0800 (PST) (envelope-from green@feldman.dyn.ml.org) Received: from localhost (green@localhost) by feldman.dyn.ml.org (8.8.8/8.8.8) with SMTP id XAA02838; Thu, 12 Mar 1998 23:52:36 -0500 (EST) (envelope-from green@feldman.dyn.ml.org) Date: Thu, 12 Mar 1998 23:52:35 -0500 (EST) From: Brian Feldman To: Chuck Robey cc: Brian Feldman , freebsd-current@FreeBSD.ORG Subject: Re: C++ libs are broken In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, you're right. I was quite miffed when I wrote that message. It's just that 3.0 can be so stable, and working, I hate to see it get messed up all the time. Some people really take too much liberty committing any change they want. I know right now, Alpha stuff, ELF stuff, and soft-updates (bleh, it's SO unstable!), are getting worked on, but I think people really do need to test their changes and compile to make sure they didn't break anything like this. I really should read commit mail, but I have no good mail box to use, since this is just my dynamic IP'd 28.8 part-time dial-up anyway. *sigh* I need to go send a pr, because mounted synchronously, mount's output shows my drives with async (!) and sync write.... majorly weird. Maybe we need to get softupdates backed out a bit. Happy alpha-testing, Brian Feldman On Mon, 9 Mar 1998, Chuck Robey wrote: > On Mon, 9 Mar 1998, Brian Feldman wrote: > > > > > You know, I'm surprised I've only seen this twice (cut out the damn > > stackable FS talk, so we can talk about what's happening NOW!), and have > > noticed it quite a bit myself, that the newest C++ libraries ARE BROKEN! I > > wish someone might pay a tiny bit of attention to this, because it's > > really annoying (2.2.5-RELEASE's C++ libs are less than fully functional > > to use). Might someone want to see what commit changes have been made and > > fix these libraries? > > Keep some perspective ... current's been the target of some folks who > abused the privilege, but the stuff about the filesystems IS a good, and > really interesting "current" topic. You can ask about the C++ libs, but > not at the expense of what others are doing ... that's selfish. > > Besides, if you're reading the commit mail, you know that the C++ libs > are currently the topic of a lot of work, they haven't been badly busted > all that long, give them some time. They already know things are > unstable (the reason is because the ELF stuff *and* the Alpha stuff are > both hitting the C++ libs at the same time) so this just calls for a > little patience. A heads up ("this is broken") is a good thing, but not > calling off debate of important topics in design. > > > > > -Brian Feldman > > brianfeldman@hotmail.com > > > > > > 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 Thu Mar 12 21:33:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25767 for freebsd-current-outgoing; Thu, 12 Mar 1998 21:33:41 -0800 (PST) (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 VAA25745 for ; Thu, 12 Mar 1998 21:33:34 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id AAA16647; Fri, 13 Mar 1998 00:31:16 -0500 (EST) Date: Fri, 13 Mar 1998 00:31:15 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Brian Feldman cc: freebsd-current@FreeBSD.ORG Subject: Re: C++ libs are broken 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, 12 Mar 1998, Brian Feldman wrote: > Yes, you're right. I was quite miffed when I wrote that message. It's just > that 3.0 can be so stable, and working, I hate to see it get messed up all > the time. Some people really take too much liberty committing any change > they want. I know right now, Alpha stuff, ELF stuff, and soft-updates > (bleh, it's SO unstable!), are getting worked on, but I think people > really do need to test their changes and compile to make sure they didn't > break anything like this. I really should read commit mail, but I have no > good mail box to use, since this is just my dynamic IP'd 28.8 part-time > dial-up anyway. *sigh* I need to go send a pr, because mounted > synchronously, mount's output shows my drives with async (!) and sync > write.... majorly weird. Maybe we need to get softupdates backed out a > bit. > Happy alpha-testing, > Brian Feldman Well, really, current _is for_ alpha-testing. It's not for production systems. What you should be asking for, is for your favorite features that are in current and not in 2.2.5, to be brought in, not (please!) for current to be moved back! Softupdates really isn't in current yet, at least not the most of it. The breakage normally in the past has been attributable to a couple of people breaking things haphazardly, whilst doing things that, while needed, weren't truly of primary importance (stuff like style changes). This time, it's been improvements to the NFS and VM system, which is a completely different animal, and (in my mind) truly excuseable because: a) it's really difficult (monstrously so) and really does need the testing efforts of all the current users, and b) it's of major importance to speed, filesystem, and memory usage. Since it's got such importance, it's so terribly hard to do, and needs the testing, there isn't any other choice. It's actually the real reason that current exists. Take my advice and really read the commit mail. The guys doing the (take your pick: ELF upgrades, Alpha port introduction, VM system improvements, NFS improvements, softupdates introduction) are making groundbreaking changes in FreeBSD, and we haven't seen such an exciting group of MAJOR things like this all at one time in years! Personally, I wonder why the FreeBSD web page, and WC's advertising, hasn't picked up on this, and begun some early PR work? The potential, inside the next year, is astounding! Anybody who follows up on this, please do it in FreeBSD-chat ... this doesn't belong in current anymore, and I won't reply here in current. ----------------------------+----------------------------------------------- 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 Thu Mar 12 21:33:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25849 for freebsd-current-outgoing; Thu, 12 Mar 1998 21:33:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25843 for ; Thu, 12 Mar 1998 21:33:57 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.8.8/8.8.5) id VAA27472; Thu, 12 Mar 1998 21:35:20 -0800 (PST) From: Steve Kargl Message-Id: <199803130535.VAA27472@troutmask.apl.washington.edu> Subject: Re: C++ libs are broken In-Reply-To: from Brian Feldman at "Mar 12, 98 11:52:35 pm" To: green@feldman.dyn.ml.org (Brian Feldman) Date: Thu, 12 Mar 1998 21:35:19 -0800 (PST) Cc: chuckr@glue.umd.edu, green@feldman.dyn.ml.org, 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 According to Brian Feldman: > Yes, you're right. I was quite miffed when I wrote that message. It's just > that 3.0 can be so stable, and working, I hate to see it get messed up all > the time. Some people really take too much liberty committing any change > they want. I know right now, Alpha stuff, ELF stuff, and soft-updates > (bleh, it's SO unstable!), are getting worked on, but I think people > really do need to test their changes and compile to make sure they didn't If you're not prepared to run -current, then you should be running either 2.2.5 or -stable. > break anything like this. I really should read commit mail, but I have no > good mail box to use, since this is just my dynamic IP'd 28.8 part-time If you don't have time to scan the commit mail, then you definitely shouldn't be running -current. > dial-up anyway. *sigh* I need to go send a pr, because mounted > synchronously, mount's output shows my drives with async (!) and sync > write.... majorly weird. Maybe we need to get softupdates backed out a > bit. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 21:43:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27731 for freebsd-current-outgoing; Thu, 12 Mar 1998 21:43:50 -0800 (PST) (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 VAA27719 for ; Thu, 12 Mar 1998 21:43:46 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 15190 invoked by uid 1000); 13 Mar 1998 05:51:08 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [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: <199803130339.TAA10294@hub.freebsd.org> Date: Thu, 12 Mar 1998 21:51:07 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: "Jonathan M. Bresler" Subject: Re: A question about sys/sys/queue.h Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Mar-98 Jonathan M. Bresler wrote: > Simon Shapiro wrote: >> Why was the definition of some macros changed >> from: >> >> #define FOO { ... } >> >> to: >> >> #define FOO do { ... } while(0) >> >> I thought these are the same... >> > > the difference lies in how you use them. > in the first case one writes "FOO" > in the second "FOO;" cute. Wonder what the compiled code looks like... Thanx > ^ > make a macro act more like a statement. > > imagine the code around the macro > rather then the macro itself. > > first saw this in _C_traps_and_pitfalls_ > by andrew koenig (sp?) > jmb > > 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 Thu Mar 12 21:47:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28366 for freebsd-current-outgoing; Thu, 12 Mar 1998 21:47:38 -0800 (PST) (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 VAA28354; Thu, 12 Mar 1998 21:47:32 -0800 (PST) (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 QAA26319; Fri, 13 Mar 1998 16:17:16 +1030 (CST) Message-Id: <199803130547.QAA26319@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: shimon@simon-shapiro.org cc: "Jonathan M. Bresler" , freebsd-current@FreeBSD.ORG Subject: Re: A question about sys/sys/queue.h In-reply-to: Your message of "Thu, 12 Mar 1998 21:51:07 -0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Mar 1998 16:17:16 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > in the first case one writes "FOO" > > in the second "FOO;" > cute. Wonder what the compiled code looks like... It would be OK.. gcc removes extra goo like that even if you don't have optimisation enabled.. --------------------------------------------------------------------- |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 Mar 12 23:25:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08584 for freebsd-current-outgoing; Thu, 12 Mar 1998 23:25:06 -0800 (PST) (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 XAA08577 for ; Thu, 12 Mar 1998 23:25:04 -0800 (PST) (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.6.9) with ESMTP id XAA18397; Thu, 12 Mar 1998 23:24:04 -0800 (PST) To: Ron Bolin cc: FreeBSD Current Mailing List Subject: Re: i386 and Alpha Src Tree Question In-reply-to: Your message of "Thu, 12 Mar 1998 20:01:08 EST." <35088554.ED785058@mindspring.com> Date: Thu, 12 Mar 1998 23:24:04 -0800 Message-ID: <18394.889773844@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Since I have only Intel class machines like many others. Does it > make sense to organize the tree where cvsups and the general make file > sequence does not download or depend on the Alpha code being in the > tree? Probably not, no. It's not something that's entirely confined to a single hierarchy (support is and must be intertwined at many different levels of the source tree). > It seems like we are going to have lots of space taken up by the Alpha > code. Bite the bullet. The OpenBSD and NetBSD folks have been bearing this cost for ages, and you should count yourself lucky that you don't also have to deal with m68k or PPC or VAX code, for example, in your tree. :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 23:41:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11807 for freebsd-current-outgoing; Thu, 12 Mar 1998 23:41:44 -0800 (PST) (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 XAA11740 for ; Thu, 12 Mar 1998 23:41:38 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id IAA01746 for freebsd-current@FreeBSD.ORG; Fri, 13 Mar 1998 08:41:29 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta1/keltia-2.14/nospam) id IAA22700; Fri, 13 Mar 1998 08:10:30 +0100 (CET) (envelope-from roberto) Message-ID: <19980313081030.A22674@keltia.freenix.fr> Date: Fri, 13 Mar 1998 08:10:30 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: cal(1) Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199803130416.WAA00360@unix.tfs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <199803130416.WAA00360@unix.tfs.net>; from Jim Bryant on Thu, Mar 12, 1998 at 10:16:54PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4121 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jim Bryant: > Delete src/usr.bin/cal/Makefile > Delete src/usr.bin/cal/README > Delete src/usr.bin/cal/cal.1 > Delete src/usr.bin/cal/cal.c ncal(1) rules. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sun Mar 1 18:50:39 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 12 23:45:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13098 for freebsd-current-outgoing; Thu, 12 Mar 1998 23:45:46 -0800 (PST) (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 XAA13090 for ; Thu, 12 Mar 1998 23:45:40 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id SAA08763; Fri, 13 Mar 1998 18:46:56 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803130746.SAA08763@cimlogic.com.au> Subject: Re: i386 and Alpha Src Tree Question In-Reply-To: <35088554.ED785058@mindspring.com> from Ron Bolin at "Mar 12, 98 08:01:08 pm" To: rlb@mindspring.com (Ron Bolin) Date: Fri, 13 Mar 1998 18:46:56 +1100 (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 Ron Bolin wrote: > Example: > # find . -type d -name 'alpha*' -exec du -sk {} \; > 284 ./contrib/gcc/config/alpha > 27 ./contrib/libgmp/mpn/alpha > 2 ./gnu/usr.bin/binutils/ld/alpha > 95 ./gnu/usr.bin/binutils/libbfd/alpha > 9 ./gnu/usr.bin/binutils/as/alpha > 11 ./lib/csu/alpha > 124 ./lib/libc/alpha > 7 ./lib/msun/alpha > 135 ./sys/alpha Look at the sizes! Now look at the sizes of src/sys/pc98. That's not alpha. -- 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 Thu Mar 12 23:53:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14798 for freebsd-current-outgoing; Thu, 12 Mar 1998 23:53:18 -0800 (PST) (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 XAA14778; Thu, 12 Mar 1998 23:53:14 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id SAA08823; Fri, 13 Mar 1998 18:54:37 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803130754.SAA08823@cimlogic.com.au> Subject: Re: i386 and Alpha Src Tree Question In-Reply-To: <18394.889773844@time.cdrom.com> from "Jordan K. Hubbard" at "Mar 12, 98 11:24:04 pm" To: jkh@FreeBSD.ORG (Jordan K. Hubbard) Date: Fri, 13 Mar 1998 18:54:37 +1100 (EST) Cc: rlb@mindspring.com, 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 Jordan K. Hubbard wrote: > Bite the bullet. The OpenBSD and NetBSD folks have been bearing this > cost for ages, and you should count yourself lucky that you don't also > have to deal with m68k or PPC or VAX code, for example, in your > tree. :-) Now that you come to mention it, I'd still like to have m68k support around. 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 Fri Mar 13 00:37:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22692 for freebsd-current-outgoing; Fri, 13 Mar 1998 00:37:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rvc1.informatik.ba-stuttgart.de (rvc1.informatik.ba-stuttgart.de [141.31.112.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22441 for ; Fri, 13 Mar 1998 00:36:43 -0800 (PST) (envelope-from helbig@Informatik.BA-Stuttgart.DE) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.8/8.8.5) id JAA00252; Fri, 13 Mar 1998 09:31:20 +0100 (MET) From: Wolfgang Helbig Message-Id: <199803130831.JAA00252@rvc1.informatik.ba-stuttgart.de> Subject: Re: cal(1) In-Reply-To: <199803130416.WAA00360@unix.tfs.net> from Jim Bryant at "Mar 12, 98 10:16:54 pm" To: jbryant@unix.tfs.net Date: Fri, 13 Mar 1998 09:31:19 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (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 > ??????????????????? -=[WHY]=- ???????????????????????? > > [from a cvsup of a few minutes ago] > > Delete src/usr.bin/cal/Makefile > Delete src/usr.bin/cal/README > Delete src/usr.bin/cal/cal.1 > Delete src/usr.bin/cal/cal.c > > ??????????????????? -=[WHY]=- ???????????????????????? OOPS. How could that happen? Seriously: cal(1) is replaced by ncal(1), which has some more features. Binary and man page of cal is linked to ncal. Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 02:11:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00635 for freebsd-current-outgoing; Fri, 13 Mar 1998 02:11:32 -0800 (PST) (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 CAA00629 for ; Fri, 13 Mar 1998 02:11:29 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id FAA01489; Fri, 13 Mar 1998 05:10:47 -0500 (EST) From: Peter Dufault Message-Id: <199803131010.FAA01489@hda.hda.com> Subject: Re: A question about sys/sys/queue.h In-Reply-To: from Simon Shapiro at "Mar 12, 98 09:51:07 pm" To: shimon@simon-shapiro.org Date: Fri, 13 Mar 1998 05:10:47 -0500 (EST) 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 > cute. Wonder what the compiled code looks like... This is a standard idiom safe to use around "ifs" etc without extra curly braces - if (test) this_macro_expands_ok(); the generated code is fine even on some bad DSP and microcontroller compilers I use. I try to always use this. 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 Fri Mar 13 02:17:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01704 for freebsd-current-outgoing; Fri, 13 Mar 1998 02:17:32 -0800 (PST) (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 CAA01698 for ; Fri, 13 Mar 1998 02:17:29 -0800 (PST) (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.6.9) with ESMTP id CAA19165; Fri, 13 Mar 1998 02:15:44 -0800 (PST) To: Brian Feldman cc: Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: C++ libs are broken In-reply-to: Your message of "Thu, 12 Mar 1998 23:52:35 EST." Date: Fri, 13 Mar 1998 02:15:44 -0800 Message-ID: <19161.889784144@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, you're right. I was quite miffed when I wrote that message. It's just > that 3.0 can be so stable, and working, I hate to see it get messed up all > the time. Some people really take too much liberty committing any change Well, FWIW, we've talked before and I've already told you several times that I didn't think you should be running -current; you haven't got the prerequisites (you don't read the right mailing lists and you definitely shouldn't be out on the bleeding edge in general). I don't think -current should be blamed for inappropriate use here. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 03:13:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA08144 for freebsd-current-outgoing; Fri, 13 Mar 1998 03:13:43 -0800 (PST) (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 DAA08129 for ; Fri, 13 Mar 1998 03:13:38 -0800 (PST) (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 LAA20224; Fri, 13 Mar 1998 11:13:32 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id MAA06896; Fri, 13 Mar 1998 12:13:30 +0100 (MET) Message-ID: <19980313121330.54903@follo.net> Date: Fri, 13 Mar 1998 12:13:30 +0100 From: Eivind Eklund To: shimon@simon-shapiro.org, freebsd-current@FreeBSD.ORG Subject: Re: A question about sys/sys/queue.h References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Simon Shapiro on Thu, Mar 12, 1998 at 07:17:45PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 12, 1998 at 07:17:45PM -0800, Simon Shapiro wrote: > Why was the definition of some macros changed > from: > > #define FOO(a) { ... } > > to: > > #define FOO(a) do { ... } while(0) > > I thought these are the same... Imagine these used in a dual if () statement: if (bar) if (baz) FOO(1); else printf ("You loose!\n"); With the former, you get something that (with proper indentation) map as if (bar) if (baz) { ... }; else printf ("You loose!\n"); while with the do {...} while (0) trick, you get if (bar) if (baz) do { ... } while(0); else printf ("You loose!\n"); For any onlookerss: You can't get the correct binding with if () tricks, BTW. Stick with the good old "do { ... } while(0)" Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 05:16:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21666 for freebsd-current-outgoing; Fri, 13 Mar 1998 05:16:09 -0800 (PST) (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 FAA21658; Fri, 13 Mar 1998 05:16:06 -0800 (PST) (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 IAA17290; Fri, 13 Mar 1998 08:16:03 -0500 (EST) Date: Fri, 13 Mar 1998 08:16:03 -0500 (EST) From: Andrew Herdman X-Sender: andrew@why To: "Jordan K. Hubbard" cc: Ron Bolin , FreeBSD Current Mailing List Subject: Re: i386 and Alpha Src Tree Question In-Reply-To: <18394.889773844@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Mar 1998, Jordan K. Hubbard wrote: >> Since I have only Intel class machines like many others. Does it >> make sense to organize the tree where cvsups and the general make file >> sequence does not download or depend on the Alpha code being in the >> tree? > >Probably not, no. It's not something that's entirely confined to a >single hierarchy (support is and must be intertwined at many different >levels of the source tree). > >> It seems like we are going to have lots of space taken up by the Alpha >> code. > >Bite the bullet. The OpenBSD and NetBSD folks have been bearing this >cost for ages, and you should count yourself lucky that you don't also >have to deal with m68k or PPC or VAX code, for example, in your >tree. :-) Yet. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 07:19:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05793 for freebsd-current-outgoing; Fri, 13 Mar 1998 07:19:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05766 for ; Fri, 13 Mar 1998 07:19:35 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA27634; Sat, 14 Mar 1998 02:13:11 +1100 Date: Sat, 14 Mar 1998 02:13:11 +1100 From: Bruce Evans Message-Id: <199803131513.CAA27634@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org Subject: Re: make/SIGINT (Re: cvs commit: src/bin/sh jobs.c) Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The appended fix seems to treat signals right for compat mode, >too. I'll do some make world's with patched make and sh over the >weekend and look for further trouble. I changed the handling of SIGQUIT and fixed the style bugs: diff -c2 compat.c~ compat.c *** compat.c~ Mon Feb 24 01:43:20 1997 --- compat.c Sat Mar 14 01:53:45 1998 *************** *** 126,130 **** } ! exit (signo); } --- 126,133 ---- } ! if (signo == SIGQUIT) ! exit(signo); ! (void) signal(signo, SIG_DFL); ! (void) kill(getpid(), signo); } diff -c2 job.c~ job.c *** job.c~ Mon Feb 24 01:43:21 1997 --- job.c Fri Feb 13 05:06:16 1998 *************** *** 2905,2909 **** } (void) eunlink(tfile); - exit(signo); } --- 2905,2908 ---- 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. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 07:41:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09358 for freebsd-current-outgoing; Fri, 13 Mar 1998 07:41:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gloria.cord.edu (twschulz@gloria.cord.edu [138.129.254.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09341 for ; Fri, 13 Mar 1998 07:41:30 -0800 (PST) (envelope-from twschulz@gloria.cord.edu) Received: from localhost (twschulz@localhost) by gloria.cord.edu (8.8.5/8.6.5) with SMTP id JAA27451 for ; Fri, 13 Mar 1998 09:41:11 -0600 (CST) Date: Fri, 13 Mar 1998 09:41:11 -0600 (CST) From: Trenton Schulz To: FreeBSD-current@FreeBSD.ORG Subject: trouble booting Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My recent CVSUP from 3/9 on seems to give me trouble when I'm booting. My computer's hard disk has two partitions one for DOS and one for FreeBSD. The Make World and re-making the kernel go alright, but when I boot, the kernel tells me it is switching the root device to wd0s3a. At this point it seems to fsck the disks but then gives the message that the "filesystem failed to mount" and puts me in single user mode with a read-only root filesystem. Luckily the previous kernel still boots correctly. This allowed the correct specification of devices is fstab, (wd0s2a for root device, wd0s3a causing the system to not do anything) but when I reboot the machine it still gives me the same error about the filesystem failing. When I try to remount root it tells me that wd0s2a doesn't match mounted device, but yet if I mount wd0s2a on /mnt, it _is_ the root partition. I thought a new make world and kernel would solve this problem, but it hasn't. I'm sorry for being so ignorant on what to do, but could someone please help me get my system to boot on something besides an old kernel? Trenton Schulz twschulz@cord.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 07:53:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11948 for freebsd-current-outgoing; Fri, 13 Mar 1998 07:53:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.linkdesign.com (relay.linkdesign.com [194.42.128.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11940 for ; Fri, 13 Mar 1998 07:52:55 -0800 (PST) (envelope-from Michael.Bielicki@linkdesign.com) Received: from cyprus.vds.linkdesign.com (host27.bln.de [194.162.193.235]) by relay.linkdesign.com (8.8.8/8.8.6) with ESMTP id RAA23550 for ; Fri, 13 Mar 1998 17:52:11 +0200 (EET) Received: from technik1.vds.linkdesign.com (technik1.vds.linkdesign.com [192.168.0.15]) by cyprus.vds.linkdesign.com (8.8.8/8.8.8) with SMTP id QAA12056 for ; Fri, 13 Mar 1998 16:51:29 +0100 (CET) (envelope-from Michael.Bielicki@LinkDesign.com) From: Michael Bielicki Date: Fri, 13 Mar 1998 15:45:58 GMT Message-ID: <19980313.15455822@technik1.vds.linkdesign.com> Subject: SCSI PCMCIA CARDS for CURRENT ?? To: current@FreeBSD.ORG X-Mailer: Mozilla/3.0 (compatible; StarOffice/4.0; WinNT/Win95) X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA11944 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I want to install CURRENT on my notebook on an external SCSI Drive (the 800 MB internal is used for Windoze and is IDE). Which controller should I use ?? Thx Michael Bielicki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 08:00:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13288 for freebsd-current-outgoing; Fri, 13 Mar 1998 08:00:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gorgon.lovett.com (root@gorgon.lovett.com [38.155.241.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA13275; Fri, 13 Mar 1998 08:00:20 -0800 (PST) (envelope-from ade@demon.net) Received: from gorgon.lovett.com [38.155.241.3] (ade) by gorgon.lovett.com with esmtp (Exim 1.82 #1) id 0yDWsZ-0000dD-00; Fri, 13 Mar 1998 10:00:15 -0600 To: "Jordan K. Hubbard" cc: FreeBSD Current Mailing List Subject: Re: i386 and Alpha Src Tree Question Organization: Demon Internet Reply-To: ade@demon.net In-reply-to: Your message of "Thu, 12 Mar 1998 23:24:04 PST." <18394.889773844@time.cdrom.com> Date: Fri, 13 Mar 1998 10:00:15 -0600 From: Ade Lovett Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > >Bite the bullet. The OpenBSD and NetBSD folks have been bearing this >cost for ages, and you should count yourself lucky that you don't also >have to deal with m68k or PPC or VAX code, for example, in your >tree. :-) Aww.. and there was me hoping for a FreeBSD/Fridge_Freezer port so I could do a worldstone benchmark on it whilst drinking the contents that looked like beer... fridge: panic: out of beer.. run to the store.. :) -aDe -- Ade Lovett, Demon Internet, Austin, Texas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 08:06:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14687 for freebsd-current-outgoing; Fri, 13 Mar 1998 08:06:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isvara.net (root@[130.88.148.77]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14633 for ; Fri, 13 Mar 1998 08:06:17 -0800 (PST) (envelope-from freebsd@challenge.isvara.net) Received: from challenge.isvara.net ([130.88.66.5]) by isvara.net (8.8.7/8.8.7) with ESMTP id QAA04959 for ; Fri, 13 Mar 1998 16:06:01 GMT Message-ID: <3509596C.AEB9AE62@challenge.isvara.net> Date: Fri, 13 Mar 1998 16:06:05 +0000 From: freebsd@isvara.net X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: FreeBSD Current Subject: make world -j 4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, what does the '-j 4' do for make world? I've seen -j 3, etc. What differences are there? Dan _____________________________________ Daniel J Blueman BSc Computation, UMIST, Manchester Email: blue@challenge.isvara.net Web: http://www.challenge.isvara.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 08:27:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19492 for freebsd-current-outgoing; Fri, 13 Mar 1998 08:27:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19478 for ; Fri, 13 Mar 1998 08:27:15 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id LAA17076; Fri, 13 Mar 1998 11:27:07 -0500 (EST) Date: Fri, 13 Mar 1998 11:27:06 -0500 (EST) From: Snob Art Genre To: freebsd@isvara.net cc: current@FreeBSD.ORG Subject: Re: make world -j 4 In-Reply-To: <3509596C.AEB9AE62@challenge.isvara.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 >From the man page: -j max_jobs Specify the maximum number of jobs that make may have running at any one time. Turns compatibility mode off, unless the B flag is also specified. *thwack* On Fri, 13 Mar 1998 freebsd@isvara.net wrote: > Hi, > what does the '-j 4' do for make world? > I've seen -j 3, etc. What differences are there? > > Dan > > _____________________________________ > Daniel J Blueman > BSc Computation, UMIST, Manchester > Email: blue@challenge.isvara.net > Web: http://www.challenge.isvara.net/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 08:31:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20325 for freebsd-current-outgoing; Fri, 13 Mar 1998 08:31:21 -0800 (PST) (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 IAA20312 for ; Fri, 13 Mar 1998 08:31:15 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id LAA01059 for current@freebsd.org; Fri, 13 Mar 1998 11:31:12 -0500 (EST) (envelope-from toor) Message-Id: <199803131631.LAA01059@dyson.iquest.net> Subject: My machine is back alive!!! :-) To: current@FreeBSD.ORG Date: Fri, 13 Mar 1998 11:31:11 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@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 I am back from the bay area, will be ready to take on the VM and NFS issues. Tor seems to have made some good VM progress :-). BTW, my machine died due to the new compatibility slice thing -- that is what I get for on the fly kernel updates 2000mi away :-(. -- 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 Fri Mar 13 08:46:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23731 for freebsd-current-outgoing; Fri, 13 Mar 1998 08:46:19 -0800 (PST) (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 IAA23705; Fri, 13 Mar 1998 08:46:14 -0800 (PST) (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 KAA28779; Fri, 13 Mar 1998 10:46:11 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id KAA28758; Fri, 13 Mar 1998 10:45:36 -0600 Message-ID: <19980313104536.00177@right.PCS> Date: Fri, 13 Mar 1998 10:45:36 -0600 From: Jonathan Lemon To: shimon@simon-shapiro.org Cc: "Jonathan M. Bresler" , freebsd-current@FreeBSD.ORG Subject: Re: A question about sys/sys/queue.h References: <199803130339.TAA10294@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from Simon Shapiro on Mar 03, 1998 at 09:51:07PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mar 03, 1998 at 09:51:07PM -0800, Simon Shapiro wrote: > > On 13-Mar-98 Jonathan M. Bresler wrote: > > Simon Shapiro wrote: > >> Why was the definition of some macros changed > >> from: > >> > >> #define FOO { ... } > >> > >> to: > >> > >> #define FOO do { ... } while(0) > >> > >> I thought these are the same... > >> > > > > the difference lies in how you use them. > > in the first case one writes "FOO" > > in the second "FOO;" Huh? Did I miss something, or am I too used to gcc? I thought semicolons after braces were optional. The following code works: main() { { printf("hello world!\n"); };;;;;; } All the change does is make the trailing semicolon mandatory. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 08:53:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25447 for freebsd-current-outgoing; Fri, 13 Mar 1998 08:53:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailout05.btx.dtag.de (mailout05.btx.dtag.de [194.25.2.153]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA25438 for ; Fri, 13 Mar 1998 08:53:37 -0800 (PST) (envelope-from lennartz.electronic@t-online.de) Received: from fwd09.btx.dtag.de (fwd09.btx.dtag.de [194.25.2.169]) by mailout05.btx.dtag.de with smtp id 0yDXgT-0000g2-00; Fri, 13 Mar 1998 17:51:49 +0100 Received: from fw.tue.le (0707193550-0001(btxid)@[193.159.35.17]) by fwd09.btx.dtag.de with smtp id ; Fri, 13 Mar 1998 17:51:35 +0100 Received: from mezcal.tue.le (mezcal.tue.le [192.168.201.20]) by fw.tue.le (8.8.8/8.8.8) with ESMTP id RAA01742 for ; Fri, 13 Mar 1998 17:49:43 +0100 (CET) (envelope-from thz@mezcal.tue.le) Received: (from thz@localhost) by mezcal.tue.le (8.8.5/8.8.8) id RAA00952; Fri, 13 Mar 1998 17:49:43 +0100 (MET) (envelope-from thz) Message-ID: <19980313174942.53822@tue.le> Date: Fri, 13 Mar 1998 17:49:42 +0100 To: freebsd-current@FreeBSD.ORG Subject: Re: A question about sys/sys/queue.h References: <19980313121330.54903@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980313121330.54903@follo.net>; from Eivind Eklund on Fri, Mar 13, 1998 at 12:13:30PM +0100 X-Sender: 0707193550-0001@t-online.de From: lennartz.electronic@t-online.de (Thomas Zenker) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 13, 1998 at 12:13:30PM +0100, Eivind Eklund wrote: > On Thu, Mar 12, 1998 at 07:17:45PM -0800, Simon Shapiro wrote: > > Why was the definition of some macros changed > > from: > > > > #define FOO(a) { ... } > > > > to: > > > > #define FOO(a) do { ... } while(0) > > > > I thought these are the same... > > Imagine these used in a dual if () statement: > > if (bar) > if (baz) > FOO(1); > else > printf ("You loose!\n"); > > With the former, you get something that (with proper indentation) map > as > > if (bar) > if (baz) > { ... }; > else > printf ("You loose!\n"); > > while with the do {...} while (0) trick, you get > > if (bar) > if (baz) > do { ... } while(0); > else > printf ("You loose!\n"); > It will not compile anyway. The version w/ "{ ... };" is syntactically incorrect, because there are two statements after the if, leaving the else w/o partner. if (bar) if (baz) { ... } /* compound_statement */ ; /* empty but existing statment! */ else /* else without matching if! */ ... while the second version "do { ... } while (0);" still is a simple statement. -- Thomas Zenker at work thz@lennartz-electronic.de private thz@tuebingen.netsurf.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 09:18:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00131 for freebsd-current-outgoing; Fri, 13 Mar 1998 09:18:20 -0800 (PST) (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 JAA00117 for ; Fri, 13 Mar 1998 09:18:17 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 4395 invoked by uid 1000); 13 Mar 1998 17:25:28 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [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: <199803131010.FAA01489@hda.hda.com> Date: Fri, 13 Mar 1998 09:25:27 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Peter Dufault Subject: Re: A question about sys/sys/queue.h Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Mar-98 Peter Dufault wrote: >> cute. Wonder what the compiled code looks like... > > This is a standard idiom safe to use around "ifs" etc without extra > curly braces - > > if (test) > this_macro_expands_ok(); > > the generated code is fine even on some bad DSP and microcontroller > compilers I use. I try to always use this. I understand the code works. I was wondering about: a. differences in actual object generated - I am assured that GCC is knowledgable enough to remove the logically useless code. b. The sanity of writing useless code, knowing it will be thrown out by or frienfdly, thinking, machine, only to gain a `;' so something looks like what it is not - I do admit to the somewhat more convineient look of the sesultant code, although an inline function would have accomplished the same thing while being semantically saner, but as it works... ---------- 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 Fri Mar 13 09:21:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00977 for freebsd-current-outgoing; Fri, 13 Mar 1998 09:21:16 -0800 (PST) (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 JAA00889 for ; Fri, 13 Mar 1998 09:20:42 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA01990; Fri, 13 Mar 1998 09:12:47 -0800 (PST) Received: from UNKNOWN(), claiming to be "crab.whistle.com" via SMTP by alpo.whistle.com, id smtpd001988; Fri Mar 13 09:12:44 1998 Received: (from ambrisko@localhost) by crab.whistle.com (8.8.8/8.6.12) id JAA13572; Fri, 13 Mar 1998 09:08:44 -0800 (PST) From: Doug Ambrisko Message-Id: <199803131708.JAA13572@crab.whistle.com> Subject: Re: Netboot problem: RPC timeout for server 0x0 In-Reply-To: <199803130421.FAA16144@pat.idi.ntnu.no> from Tor Egge at "Mar 13, 98 05:21:05 am" To: Tor.Egge@idi.ntnu.no (Tor Egge) Date: Fri, 13 Mar 1998 09:08:44 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (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 Tor Egge writes: | > If go back in time just before this then it is fine, just after then | > it breaks. The time is 2/20/98 8:40:00 then it breaks, 8:30 is fine. | | This is actually a very good indication of what's going wrong. | | Try this patch. Yes this fixed it. Thanks, I have attached a diff to current that has your fix and a new feature in the BOOTP code. I have created a kernel config option: options "BOOTP_WIRED_TO=fxp0" # Use interface fxp0 for BOOTP This is useful in a machine that has multiple ethernet cards and the first card detected is not the card that was used for BOOTP. Index: sys/conf/options =================================================================== RCS file: /cvs/freebsd/src/sys/conf/options,v retrieving revision 1.66 diff -u -r1.66 options --- options 1998/03/10 15:55:38 1.66 +++ options 1998/03/13 16:51:46 @@ -161,6 +161,7 @@ BOOTP_COMPAT opt_bootp.h BOOTP_NFSROOT opt_bootp.h BOOTP_NFSV3 opt_bootp.h +BOOTP_WIRED_TO opt_bootp.h GATEWAY opt_defunct.h MROUTING opt_mrouting.h INET opt_inet.h Index: sys/i386/conf/LINT =================================================================== RCS file: /cvs/freebsd/src/sys/i386/conf/LINT,v retrieving revision 1.416 diff -u -r1.416 LINT --- LINT 1998/03/10 15:42:13 1.416 +++ LINT 1998/03/13 16:51:48 @@ -1375,6 +1375,7 @@ options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info options "BOOTP_NFSV3" # Use NFS v3 to NFS mount root options BOOTP_COMPAT # Workaround for broken bootp daemons. +options "BOOTP_WIRED_TO=fxp0" # Use interface fxp0 for BOOTP. # # An obsolete option to test kern_opt.c. Index: sys/nfs/bootp_subr.c =================================================================== RCS file: /cvs/freebsd/src/sys/nfs/bootp_subr.c,v retrieving revision 1.9 diff -u -r1.9 bootp_subr.c --- bootp_subr.c 1998/02/09 06:10:32 1.9 +++ bootp_subr.c 1998/03/13 16:51:53 @@ -766,18 +766,32 @@ return; /* - * Bump time if 0. + * Wait until arp entries can be handled. */ - if (!time.tv_sec) - time.tv_sec++; + while (time.tv_sec == 0) + tsleep(&time, PZERO+8, "arpkludge", 10); /* * Find a network interface. */ +#ifdef BOOTP_WIRED_TO +#define xstr(s) str(s) +#define str(s) #s + printf("bootpc_init: wired to interface '%s'\n", + xstr(BOOTP_WIRED_TO)); +#endif for (ifp = TAILQ_FIRST(&ifnet); ifp != 0; ifp = TAILQ_NEXT(ifp,if_link)) +#ifdef BOOTP_WIRED_TO + { + sprintf(ireq.ifr_name, "%s%d", ifp->if_name,ifp->if_unit); + if (strcmp(ireq.ifr_name,xstr(BOOTP_WIRED_TO)) == 0) + break; + } +#else if ((ifp->if_flags & (IFF_LOOPBACK|IFF_POINTOPOINT)) == 0) break; +#endif if (ifp == NULL) panic("bootpc_init: no suitable interface"); bzero(&ireq,sizeof(ireq)); Index: sys/nfs/krpc_subr.c =================================================================== RCS file: /cvs/freebsd/src/sys/nfs/krpc_subr.c,v retrieving revision 1.7 diff -u -r1.7 krpc_subr.c --- krpc_subr.c 1997/10/28 15:59:03 1.7 +++ krpc_subr.c 1998/03/13 16:51:53 @@ -337,7 +337,7 @@ timo++; else printf("RPC timeout for server 0x%x\n", - ntohl(sin->sin_addr.s_addr)); + ntohl(sa->sin_addr.s_addr)); /* * Wait for up to timo seconds for a reply. Index: sys/nfs/nfs_vfsops.c =================================================================== RCS file: /cvs/freebsd/src/sys/nfs/nfs_vfsops.c,v retrieving revision 1.55 diff -u -r1.55 nfs_vfsops.c --- nfs_vfsops.c 1998/03/01 22:46:30 1.55 +++ nfs_vfsops.c 1998/03/13 16:51:53 @@ -399,8 +399,8 @@ * XXX time must be non-zero when we init the interface or else * the arp code will wedge... */ - if (time.tv_sec == 0) - time.tv_sec = 1; + while (time.tv_sec == 0) + tsleep(&time, PZERO+8, "arpkludge", 10); if (nfs_diskless_valid==1) nfs_convert_diskless(); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 09:30:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02969 for freebsd-current-outgoing; Fri, 13 Mar 1998 09:30:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from damon.com (+kSgQEoAh8Dn+1PVDWM3C0a/0AjNKVlG@damon.com [207.170.114.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02948 for ; Fri, 13 Mar 1998 09:30:31 -0800 (PST) (envelope-from dap@damon.com) Received: (from dap@localhost) by damon.com (8.8.7/8.8.7) id LAA07600; Fri, 13 Mar 1998 11:28:34 -0600 (CST) (envelope-from dap) From: Damon Permezel Message-Id: <199803131728.LAA07600@damon.com> Subject: Re: A question about sys/sys/queue.h In-Reply-To: from Simon Shapiro at "Mar 13, 98 09:25:27 am" To: shimon@simon-shapiro.org Date: Fri, 13 Mar 1998 11:28:34 -0600 (CST) Cc: dufault@hda.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 "Simon Shapiro sez: " > > I understand the code works. I was wondering about: > > b. The sanity of writing useless code, knowing it will be thrown out by or > frienfdly, thinking, machine, only to gain a `;' so something looks > like what it is not - I do admit to the somewhat more convineient look > of the sesultant code, although an inline function would have > accomplished the same thing while being semantically saner, but as it > works... This falls into aesthetics, where sanity is not an issue. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 09:48:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06345 for freebsd-current-outgoing; Fri, 13 Mar 1998 09:48:47 -0800 (PST) (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 JAA06259 for ; Fri, 13 Mar 1998 09:48:21 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 7175 invoked by uid 1000); 13 Mar 1998 17:54:59 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [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: <19980313121330.54903@follo.net> Date: Fri, 13 Mar 1998 09:54:59 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Eivind Eklund Subject: Re: A question about sys/sys/queue.h Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Mar-98 Eivind Eklund wrote: ... > For any onlookerss: You can't get the correct binding with if () > tricks, BTW. Stick with the good old "do { ... } while(0)" What you are describing is probably a compiler (or maybe even language) deficiency. ``do { ... } while (0)'' should be identical to ``{ ... }'' as they both do logically, the same thing. I have no argument with any of it. I was just trying to understand something that caught my eye. I have my explanation. Thanx! ---------- 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 Fri Mar 13 10:08:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11497 for freebsd-current-outgoing; Fri, 13 Mar 1998 10:08:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11455 for ; Fri, 13 Mar 1998 10:08:52 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id LAA15797; Fri, 13 Mar 1998 11:08:41 -0700 (MST) Message-Id: <199803131808.LAA15797@pluto.plutotech.com> To: Damon Permezel cc: current@FreeBSD.ORG Subject: Re: A question about sys/sys/queue.h Newsgroups: pluto.freebsd.current In-Reply-To: <199803131728.LAA07600@damon.com> Date: Fri, 13 Mar 1998 11:05:32 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199803131728.LAA07600@damon.com> you wrote: > "Simon Shapiro sez: " >> >> I understand the code works. I was wondering about: >> >> b. The sanity of writing useless code, knowing it will be thrown out by or >> frienfdly, thinking, machine, only to gain a `;' so something looks >> like what it is not - I do admit to the somewhat more convineient look >> of the sesultant code, although an inline function would have >> accomplished the same thing while being semantically saner, but as it >> works... > > This falls into aesthetics, where sanity is not an issue. Actually, inline functions will not work for the queue macros unless you change the way you specify the "links" portion of the object. I agree that, in general, using an inline is better than using a macro. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 10:53:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19054 for freebsd-current-outgoing; Fri, 13 Mar 1998 10:47:12 -0800 (PST) (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 KAA18971 for ; Fri, 13 Mar 1998 10:46:27 -0800 (PST) (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 TAA26656; Fri, 13 Mar 1998 19:45:20 +0100 (MET) Message-Id: <199803131845.TAA26656@pat.idi.ntnu.no> To: michaelh@cet.co.jp Cc: freebsd-current@FreeBSD.ORG Subject: Re: 4 WILLRELE's to bite the dust In-Reply-To: Your message of "Fri, 13 Mar 1998 13:22:20 +0900 (JST)" References: 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: Fri, 13 Mar 1998 19:45:20 +0100 From: Tor Egge Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I did some simple testing of nullfs and union. It's seems Kato-san has > gotten them pretty stable. What kind of things cause problems with null > and union? - coherence. When the different layers operates on separate vm objects, the vm objects might get out of sync. E.g. page fault algorithms checks the size of the upper vm object, and gets the wrong value, since a VOP_WRITE only extended the size of the lower vm object. Symptom: install -C during make world gets a SIBGUS if /usr/obj is nullfs mounted. - freeing of resources. When the file is unlinked, the lower vnode still has a reference from the upper vnode which is left until the upper vnode is recycled. Currently null_inactive calls VOP_INACTIVE on the lower vnode. This is wrong (e.g. a process directly accessing the lower vnode will see a truncated file, which is an unintended side effect). Symptom: Removing a file that has been opend via nullfs will not necessarily free the space on the file system before the null vnode is recycled. - locking. - Missing vnode locking during vnode recycling, i.e. does not wait for inactive to complete. Symptom: lock manager panic when trying to release the lock in vclean. - During object recycling, the VOP_ISLOCKED method can cause a trap 12. This problem might not occur anymore, since vfs_msync now checks for the VXLOCK vnode flag. - Use of VOP_ISLOCKED() is very often a kludge, since it is assumed that the current process is the owner of an exclusive lock on the vnode, while it might be a different process or a shared lock. - vnode leakage in null_node_alloc. - During vnode recycling, fsync is called several times on the lower vnode. This only affects performance. - Access to files on a nullfs file system gives spurious EDEADLK errors, due to a bogus deadlock detection in nullfs_root. That deadlock detection is not needed if the generic mount system call is slightly changed. (most local file systems has the same kind of deadlock problem, thus a generic solution is preferrable). I've been using nullfs since Nov 7 1997 without any serious problems after having fixed some of the above mentioned problems in my local source tree. The code is not perfect, panics are still possible due to heuristics (due to VOP_ISLOCKED()) being wrong, but I've yet not experienced any problems. Using the nullfs in -current without any fixes, a make world would very likely not succeed if /usr/obj is nullfs mounted. By modifying null_mount, I've played around with hierarchical mounts: ikke# find /usr/zzz -print /usr/zzz /usr/zzz/zzz4 /usr/zzz/zzz4/test4 ikke# mount -t null /usr/zzz /usr/zzz null: Resource deadlock avoided ikke# mount -t null /usr/zzz /usr/zzz/zzz4 ikke# find /usr/zzz -print /usr/zzz /usr/zzz/zzz4 /usr/zzz/zzz4/zzz4 /usr/zzz/zzz4/zzz4/test4 ikke# umount /usr/zzz/zzz4 ikke# mount -t null /usr/zzz/zzz4 /usr/zzz ikke# find /usr/zzz -print /usr/zzz /usr/zzz/test4 ikke# umount /usr/zzz ikke# mount -t null /usr/zzz /usr/yyy ikke# mount -t null /usr/zzz /usr/yyy null: Resource deadlock avoided ikke# mount -t null /usr/yyy /usr/zzz null: Resource deadlock avoided ikke# mount -t null /usr/yyy /usr/yyy null: Resource deadlock avoided ikke# mount -t null /usr/zzz /usr/yyy null: Resource deadlock avoided ikke# mount -t null /usr/zzz /usr/zzz null: Resource deadlock avoided ikke# umount /usr/yyy I saw the need for a general change in the mount system call when I issued mount /usr/zzz /usr/zzz instead of mount -t null /usr/zzz /usr/zzz when testing the nullfs deadlock handling, and got a panic, due to bugs in the the ufs mount code. With a changed mount system call, I get ikke# mount /usr/zzz /usr/zzz /usr/zzz on /usr/zzz: Block device required ikke# mount -t null /usr/zzz /usr/zzz null: Device busy ikke# mount -t msdos /usr/zzz /usr/zzz msdos: /usr/zzz: Block device required ikke# mount -t cd9660 /usr/zzz /usr/zzz cd9660: Block device required ikke# ls -ld /usr/zzz drwxr-xr-x 3 root wheel 512 Feb 10 02:02 /usr/zzz - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 11:02:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21076 for freebsd-current-outgoing; Fri, 13 Mar 1998 11:02:12 -0800 (PST) (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 LAA21049; Fri, 13 Mar 1998 11:02:07 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id LAA11818; Fri, 13 Mar 1998 11:01:59 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803131901.LAA11818@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dyson@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: Re: My machine is back alive!!! :-) In-reply-to: Your message of "Fri, 13 Mar 1998 11:31:11 EST." <199803131631.LAA01059@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Mar 1998 11:01:59 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't forget about Soft-updates and the vm related panics. Tnks Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 13:24:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17054 for freebsd-current-outgoing; Fri, 13 Mar 1998 13:24:16 -0800 (PST) (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 NAA17015 for ; Fri, 13 Mar 1998 13:24:02 -0800 (PST) (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 NAA02020; Fri, 13 Mar 1998 13:21:06 -0800 (PST) Message-Id: <199803132121.NAA02020@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Justin T. Gibbs" cc: Damon Permezel , current@FreeBSD.ORG Subject: Re: A question about sys/sys/queue.h In-reply-to: Your message of "Fri, 13 Mar 1998 11:05:32 MST." <199803131808.LAA15797@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Mar 1998 13:21:05 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, inline functions will not work for the queue macros unless you > change the way you specify the "links" portion of the object. I agree > that, in general, using an inline is better than using a macro. Just speaking of the queue macros, has anyone noticed (been bitten by) the odd behaviour of the TAILQ_PREV/TAILQ_NEXT macros? (ie. they're not reflexive, and certainly not what you expect of them.) -- \\ 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 Mar 13 13:26:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17694 for freebsd-current-outgoing; Fri, 13 Mar 1998 13:26:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17663 for ; Fri, 13 Mar 1998 13:25:56 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id OAA15617; Fri, 13 Mar 1998 14:25:24 -0700 (MST) Message-Id: <199803132125.OAA15617@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Mike Smith cc: "Justin T. Gibbs" , Damon Permezel , current@FreeBSD.ORG Subject: Re: A question about sys/sys/queue.h In-reply-to: Your message of "Fri, 13 Mar 1998 13:21:05 PST." <199803132121.NAA02020@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Mar 1998 14:22:15 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Just speaking of the queue macros, has anyone noticed (been bitten by) >the odd behaviour of the TAILQ_PREV/TAILQ_NEXT macros? > >(ie. they're not reflexive, and certainly not what you expect of them.) They are reflexive now. They didn't used to be. I've used this new feature successfully in the latest version of the aic7xxx assembler for CAM. >-- >\\ 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 > > > -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 13:31:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18879 for freebsd-current-outgoing; Fri, 13 Mar 1998 13:31:03 -0800 (PST) (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 NAA18829 for ; Fri, 13 Mar 1998 13:30:41 -0800 (PST) (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 NAA02066; Fri, 13 Mar 1998 13:27:26 -0800 (PST) Message-Id: <199803132127.NAA02066@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Justin T. Gibbs" cc: Mike Smith , Damon Permezel , current@FreeBSD.ORG Subject: Re: A question about sys/sys/queue.h In-reply-to: Your message of "Fri, 13 Mar 1998 14:22:15 MST." <199803132125.OAA15617@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Mar 1998 13:27:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Just speaking of the queue macros, has anyone noticed (been bitten by) > >the odd behaviour of the TAILQ_PREV/TAILQ_NEXT macros? > > > >(ie. they're not reflexive, and certainly not what you expect of them.) > > They are reflexive now. They didn't used to be. I've used this new > feature successfully in the latest version of the aic7xxx assembler for > CAM. Yay! The number of times I've had to go to using CIRCLEQ's when all I wanted was backwards traversal is legion. Thanks. (btw, you could update the manpage... 8) -- \\ 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 Mar 13 13:43:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22152 for freebsd-current-outgoing; Fri, 13 Mar 1998 13:43:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22073 for ; Fri, 13 Mar 1998 13:43:01 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id OAA17179; Fri, 13 Mar 1998 14:42:46 -0700 (MST) Message-Id: <199803132142.OAA17179@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Mike Smith cc: "Justin T. Gibbs" , Damon Permezel , current@FreeBSD.ORG Subject: Re: A question about sys/sys/queue.h In-reply-to: Your message of "Fri, 13 Mar 1998 13:27:24 PST." <199803132127.NAA02066@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Mar 1998 14:39:37 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Yay! The number of times I've had to go to using CIRCLEQ's when all I >wanted was backwards traversal is legion. > >Thanks. (btw, you could update the manpage... 8) Don't look at me. Julian brought in the changes which came from Kirk to support soft updates. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 15:01:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03782 for freebsd-current-outgoing; Fri, 13 Mar 1998 15:01:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from marge.infinity.com (pm2-11-10.tor.idirect.com [207.136.127.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA03020; Fri, 13 Mar 1998 14:58:44 -0800 (PST) (envelope-from Chris34343@mci.net) Date: Fri, 13 Mar 1998 14:58:44 -0800 (PST) From: Chris34343@mci.net Message-Id: <199803132258.OAA03020@hub.freebsd.org> Subject: Hi, How are you? To: undisclosed-recipients:; Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG

Please accept my apology if this was sent to you in error! Dear Friend, The enclosed information is something I almost let slip through my fingers. Fortunately, sometime later I re-read everything and gave some thought and study to it. My name is Christopher Erickson. Two years ago, the corporation I worked at for the past twelve years down-sized and my position was eliminated. After unproductive job interviews, I decided to open my own business, Over the past year, I incurred many unforseen financial problems. I owed my family, friends and creditors over $35,000. The economy was taking a toll on my business and I just couldn't seem to make ends meet. I had to refinance and borrow against my home to support my family and stuggling business. I truly believe it was wrong for me to be in debt like this. AT THE MOMENT something significant happened in my life and I am writing to share my experience in hopes that this will change your life FOREVER...FINANCIALLY!!! In mid December, I received this program via email. Six months prior to receiving this program I had been sending away for information on various business opportunities. All of the programs I received, in my opinion, were not cost effective. They were either too difficult for me to comprehend or the initial investment was too much for me to risk to see if they worked or not. One claimed I'd make a million dollars in one year...it didn't tell me I'd have to write a book to make it. But like i was saying, in December of "92" I received this program. I didn't send for it, or ask for it, they just got my name off a mailing list. THANKS GOODNESS FOR THAT!!! After reading it several times, to make sure I was reading it correctly, I couldn't believe my eyes. Here was a MONEY-MAKING PHENOMENON. I could invest as much as I wanted to start, without putting me in further debt. After I got a pencil and paper and figured it out, I would at least get my money back. After determining that the program is LEGAL and NOT A CHAIN LETTER, I decided "WHY NOT". Initially I sent out 10,000 emails. It only cost me about $15.00 for my time on-line. The great thing about email is that I didn't need any money for printing to send out the program, only the cost to fulfill my orders. I am telling you like it is, i hope it doesn't turn you off, but i promised myself that I would not "rip-off" anyone, no matter how much money it cost me! In less than one week, I was starting to receive orders for REPORT #1. By January 13th, I had received 26 orders for REPORT #1. When you read the GUARANTEE in the program, you will see that "YOU MUST RECEIVE 15 TO 20 ORDERS FOR REPORT #1 WITHIN 2 WEEKS. IF YOU DON'T, SEND OUT MORE PROGRAMS UNTIL YOU DO!" My first step in making $50,000 in 20 to 90 days was done. By January 30th, I had received 196 orders for REPORT #2. If you go back to the GUARANTEE, "YOU MUST RECEIVE 100 OR MORE ORDERS FOR REPORT #2 WITHIN TWO WEEKS. IF NOT SEND OUT MORE PROGRAMS UNTIL YOU DO. ONCE YOU HAVE 100 ORDERS, THE REST IS EASY. RELAX, YOU WILL MAKE YOUR $50,000 GOAL." Well, I had 196 orders for REPORT #2, 96 more than I needed. So I sat back and relaxed. By March 19th, of my emailing of 10,000, I received $58,000 with more coming in every day. I paid off ALL my debts and bought a much needed new car. Please take time to read the attached program. IT WILL CHANGE YOUR LIFE FOREVER! Remember, it won't work if you don't try it. This program does work, but you must follow it EXACTLY! Especially the rules of not trying to place your name in a different place. It doesn't work, you'll lose out on a lot of money! REPORT #2 explains this. Always follow the guarantee, 15 to 20 orders of REPORT #1 and 100 or more orders for REPORT #2 and you will make $50,000 or more in 20 to 90 days. I AM LIVING PROOF THAT IT WORKS!!! If you choose not to participate in this program, I'm sorry, It really is a great oppotunity with little cost or risk to you. if you choose to participate, follow the program and you will be on your way to financial security. If you are a fellow business owner and you are in financial trouble like I was, or you want to start your own business, consider this a sign. I DID! Sincerely, Christopher Erickson P.S. Do you have any idea what 11,700 $5 bills ($58,000) look like piled up on a kitchen table? IT'S AWESOME! "THREW IT AWAY" "I had received this program before. I threw it away, but later wondered if i shouldn't have given it a try. of course, I had no idea who to contact to get a copy, so I had to wait until I was emailed another copy of the program. Eleven months passed, then it came. I DIDN'T throw this one away. I made $41,000 on the first try." Dawn W., Evensville, IN "NO FREE LUNCH" "My late fater always told me, 'remember, Alan there is no free lunch in life. You get out of life what you put into it.' Though trial and error and a somewhat slow frustrating start, I finally figured it out. The program works very well, I just had to find the right target group of people to email to. So far this year, I have made over $63,000 using the program. I know my dad would have been very proud of me" Alan B., Philadelphia, PA A PERSONAL NOTE FROM THE ORIGINATOR OF THIS PROGRAM By the time you have read the enclosed information and looked over the enclosed programs and reports, you should have concluded that such a program, and one that is legal, could not have been created by an amateur. Let me tell you a little about myself. I had a profitable business for ten years. Then in 1979 my business began falling off. I was doing the same things that were previously successful for me, but it wasn't working. Finally, I figured it out. It wasn't me, it was the economy. Inflation and recession had replaced the stable economy that had been with us since 1945. I don't have to tell you what happened to the unemployment rate...because many of you know from first hand experience. There were more failures and bankruptcies than ever before. The middle class was vanishing. Those who knew what they were doing invested wisely and moved up. Those who did not, including those who never had anything to save or invest, were moving down into the ranks of the poor. As the saying goes, "THE RICH GET RICHER AND THE POOR GET POORER." The traditional methods of making money will never allow you to "move up" or "get rich", inflation will see to that. You have just received information that can give you financial freedom for the rest of your life, with "NO RISK" and "JUST A LITTLE BIT OF EFFORT." You can make more money in the next few months than you have ever imagined. I should also point out that I will not see a penny of your money, nor anyone else who has provided a testimonial for this program. I have already made over FOUR MILLION DOLLARS! I have retired from the program after sending out over 16,000 programs. Now I have several offices which market this and several other programs here in the U.S. and overseas. By the spring, we wish to market the "Internet" by a partnership with AMERICA ONLINE. Follow this program EXACTLY AS INSTRUCTED. Do not change it in any way. It works exceedingly well as it is now. Remember to email a copy of this exciting program to everyone you can think of. One of the people you send this to may send out 50,000... and your name will be on every one of them! Remember though, the more you send out, the more potential customers you will reach. So my friend, I have given you the ideas, information, materials and opportunity to become financially independent, IT IS UP TO YOU NOW! "THINK ABOUT IT" Before you delete this program from your mailbox, as I almost did, take a little to read it and REALLY THINK ABOUT IT. Get a pencil and figure out what could happen when YOU participate. Figure out the worst possible response and no matter how you calculate it, you will still make alot of money! Definitely get back what you invested. Any doubts you have will vanish when your first orders come in. IT WORKS! Paul Johnson, Raleigh, NC HERE'S HOW THIS AMAZING PROGRAM WILL MAKE YOU $$$$$$ Let's say you decide to start small, just to see how it goes, and we'll assume you and all those involved send out 2,000 programs each. Let's also assume that the mailing receives a .5% response. Using a good list the response could be much better. Also many people will send out hundreds of thousands of programs instead of 2,000. But continuing with this example, you send out only 2,000 programs. With a 5% response, that is only 10 orders for REPORT #1. Those 10 people respond by sending out 2,000 programs each for a total of total of 20,000. Out of those .5%, 100 people respond and order REPORT #2. Those 100 mail out 2,000 programs each for a total of 200,000. The .5% response to that is 1,000 orders for REPORT #3. Those 1,000 send out 2,000 programs each for a 2,000,000 total. The .5% response to that is 10,000 orders for REPORT #4. That's 10,000 five dollar bills for you CASH!!!! Your total income in this example is $50.00 + $500.00 + $5,000.00 + $50,000.00 for a total of $55,550.00!!!! REMEMBER FRIEND, THIS IS ASSUMING 1,990 OUT OF 2,000 PEOPLE YOU MAIL TO WILL DO ABSOLUTELY NOTHING...AND TRASH THIS PROGRAM! DARE TO THINK FOR A MOMENT WHAT WOULD HAPPEN IF EVERYONE OR HALF SENT OUT 100,000 PROGRAMS INSTEAD OF ONLY 2,000. Believe me, many people will do that and more! By the way, your cost to participate in this is practically nothing. You obviously already have an internet connection and email is FREE!!! REPORT #3 will show you the best methods for bulk emailing and purchasing email lists. THIS IS A LEGITIMATE, LEGAL, MONEY MAKING OPPORTUNITY, It does not require you to come in contact with people, do any hard work, and best of all, you never have to leave your house except to get the mail. If you believe that someday you'll get that big break that you've been waiting for, THIS IS IT! Simply follow the instuctions, and your dream will come true. This multi-level email order marketing program works perfectly...100% EVERY TIME. Email is the sales tool of the future. Take advantage of this non-commercialized method of advertising NOW!! The longer you wait, the more people will be doing business using email. Get your piece of this action!! MULTI-LEVEL MARKETING (MLM) has finally gained respectability. It is being taught in the Harvard business school, and both Stanford research and the Wall street journal have stated that between 50% and 65% of all goods and services will be sold thoughout Multi-Level methods by the mid 1990's. This is a Multi-Billion Dollar industry and of the 500,000 millionares in the U.S., 20% (100,000) made their fortune in the last several years in MLM. Moreover statistics show 45 people become millionares everyday through Multi-Level Marketing. INSTRUCTIONS We at Erris Mail Order Marketing Business, have a method of raising capital that REALLY WORKS 100% EVERY TIME. I am really sure that you could use $50,000 to $125,000 in the next 20 to 90 days. Before you say "Bull", please read the program carefully. This is not a chain letter, but a perfectly legal money making opportunity. Basically, this is what we do: As with all multi-level business, we build our business by recruiting new partners and selling our products. Every state in the U.S.A. allows you to recruit new multi- level business partners, and we offer a product for EVERY dollar sent. YOUR ORDERS COME AND ARE FILLED THROUGH THE MAIL, so you are not involved in personal selling. You do it privately in your own home, store or office. This is the GREATEST Multi-Level Mail Order Marketing anywhere. Step (1) Order all 4 REPORTS listed by NAME AND NUMBER. Do this by ordering the REPORT from each of the four names listed on the next page. For each REPORT, send $5 CASH and a SELF- ADDRESSED, STAMPED envelope (BUSINESS SIZE #10) to the person listed for the SPECIFIC REPORT. International orders should also include $1 extra postage. Be sure to include your internet address incase of any problems.It is essential that you specify the NAME and NUMBER of the report requested to the person you are ordering from. You will need ALL FOUR REPORTS because you will be REPRINTING and RESELLING them. DO NOT alter the names or sequence other than what the instructions say. IMPORTANT: Always provide same-day service on all orders. Step (2) Replace the name and address under REPORT #1 with yours, moving the one that was there down to REPORT #2. Drop the name and address under REPORT #2 to REPORT #3, moving the one that was there to REPORT #4. The name and address that was under REPORT #4 is dropped from the list and this party is in no doubt on the way to the bank. When doing this, make certain you type the names and addresses ACCURATELY! DO NOT MIX UP MOVING PRODUCT/REPORT POSITIONS!!! Step (3) Having made the required changes in the NAME list, save it as a text (.txt) file in it's own directory to be used with whatever email program you like. Again, REPORT #3 will tell you the best methods of bulk emailing and acquiring email lists. You will also receive the address to a website to assist you. Any and all programs needed will be available free of charge. Including bulk mailers and email collectors. Step (4) Email a copy of the entire program (all of this is very important) to everyone whose addresses you can get your hands on. Start with friends and relatives since you can encourage them to take advantage of this fabulous money-making opportunity. That's what I did. And they love me now, more than ever. Then email to anyone and everyone whose address you collect with the programs available to you at the above mentioned site. Use your imagination! REQUIRED REPORTS ***Order each REPORT by NUMBER and NAME*** ALWAYS SEND A SELF ADDRESSED, STAMPED ENVELOPE, INTERNET ADDRESS AND $5 CASH FOR EACH ORDER REQUESTING THE SPECIFIC REPORT NAME AND NUMBER __________________________________________________ REPORT #1 "HOW TO MAKE $250,000 THROUGH MULTI-LEVEL SALES" ORDER REPORT #1 FROM: D.M.1 2133 Jane St. #5 Box#154 Downsview, Ontario Canada M3M-1A2 __________________________________________________ REPORT #2 "MAJOR CORPORATIONS AND MULTI-LEVEL SALES" ORDER REPORT #2 FROM: R.P. Marketing 1051 Stuyvesant Ave. Suite 193 Union, New Jersey 07083 __________________________________________________ REPORT #3 "SOURCES OF BEST MAILING LISTS" ORDER REPORT #3 FROM: Twin Marketing P.O. Box 673 Harbor City, California 90710-0673 __________________________________________________ REPORT #4 "EVALUATING MULTI-LEVEL SALES" ORDER REPORT #4 FROM: M.O.C. Marketing P.O. Box 146 Gaithersburg, Maryland 20884-0146 __________________________________________________ CONCLUSION I am enjoying my fortune that I made by sending out this program. You too, will be making money in 20 to 90 days, if you follow the SIMPLE STEPS outlined in this mailing. To be financially independent is to be FREE. Free to make financial decisions as never before. Go into business, get into investments, retire or take a vacation. No longer will a lack of money hold you back. However very few people reach financial independence, because when opportunity knocks, they choose to ignore it. It is much easier to say "NO" than "YES", and this is the question that you must answer. Will YOU ignore this amazing opportunity or will you take advantage of it? If you do nothing, you have indeed missed something and nothing will change. Please re-read this material, this is a special opportunity. My method is simple. I sell thousands of people a product for $5 that costs me pennies to produce and mail. I should also point out that this program is legal and everyone who participates WILL make money. This is not a chain letter or pyramid scam. At times you have probably received chain letters, asking you to send money, on faith, but getting NOTHING in return, No product what so-ever! Not only are chain letters illegal, but the risk of someone breaking the chain makes them quite unattractive. You are offering a legitimate product to your people. After they purchase the product from you, they reproduce more and resell them. It's simple free enterprise. As you learned from the enclosed material, the PRODUCT is a series of 4 FINANCIAL AND BUSINESS REPORTS. The information contained in these REPORTS will not only help you in making your participation in this program more rewarding, but it will be usefull to you in any other business decisions you make in the years ahead. You are also buying the rights to reprint all of the REPORTS, which will be ordered from you by those to whom you mail this program. The concise one and two page REPORTS you will be buying can easily be reproduced at a local copt center for a cost of about 3 cents a copy. Best wishes with the program and Good Luck! "IT WAS TRULY AMAZING" "Not being the gambling type, it took me several weeks to make up my mind to participate in this program. But conservative as I am, I decided that the initial investment was so little that there was no way that I could not get enough orders to at least get my money back. BOY was I ever surprised when I found my medium sized post office box crammed with orders! I will make more money this year than any ten years of my life before." Mary Riceland, Lansing, MI TIPS FOR SUCCESS Send for you four 4 REPORTS immediately so you will have them when the orders start coming in. When you receive $5 order, you MUST send out the product/service to comply with U.S. Postal and Lottery laws. Title 18 Sections 1302 and 1341 specifically state that: "A PRODUCT OR SERVICE MUST BE EXCHANGED FOR MONEY RECEIVED." IMPORTANT: WHEN SENDING A SELF ADDRESSED, STAMPED EVELOPE, IF MAILING TO A DIFFERENT COUNTRY, PURCHASE AN I.R.C (INTERNATIONAL RESPONSE COUPON). DO NOT SEND POSTAGE FROM YOUR COUNTRY OR THE PERSON FROM THE OTHER COUNTRY WILL NOT BE ABLE TO USE THAT POSTAGE. WHILE YOU WAIT FOR THE REPORTS TO ARRIVE: 1. Name your new company. You can use your own name if you desire. 2. Get a post office box (preffered) 3. Edit the names and addresses on the program. You must remember, your name and address go next to REPORT #1 and all the others all move down one, with the fourth one being bumped OFF the list. 4. Obtain as many email addresses as possible to send until you receive the information on mailing list companies in REPORT #3. 5. Decide on the number of programs you intend to send out. The more you send, and the quicker you send them, the more money you will make. 6. After mailing the programs, get ready to fill orders. 7. Copy the 4 REPORTS so you are able to send them out as soon as you receive an order. IMPORTANT: ALWAYS PROVIDE SAME-DAY SERVICE ON ORDERS YOU RECEIVE! 8. Make certain the letter and reports are neat and legible. YOUR GUARANTEE The check point which GUARANTEES your success is simply this: You must receive 15 to 20 orders for REPORT #1. This is a must!!! If you don't within 2 weeks, email out more programs until you do. Then a couple of weeks later you should receive at least 100 orders for REPORT #2, if you don't, send out more programs until you do. Once you have received 100 or more orders for REPORT #2, (take a deep breath) you can sit back and relax, because YOU ARE GOING TO MAKE AT LEAST $50,000. Mathematically it is a proven guarantee. One of those who have participated in the program and reached the above GUARANTEES-ALL have reached their $50,000 goal. Also, remember, everytime your name is moved down the list you are infront of a different REPORT, so you can keep track of your program by knowing what people are ordering from you, IT'S THAT EASY, REALLY IT IS!!! REMEMBER: "HE WHO DARES NOTHING, NEED NOT HOPE FOR ANYTHING." "INVEST A LITTLE TIME, ENERGY AND MONEY NOW OR SEARCH FOR IT FOR THE REST OF YOUR LIFE."

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 15:16:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07523 for freebsd-current-outgoing; Fri, 13 Mar 1998 15:16:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07513 for ; Fri, 13 Mar 1998 15:16:05 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id AAA20821; Sat, 14 Mar 1998 00:11:00 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199803132311.AAA20821@ocean.campus.luth.se> Subject: Re: A question about sys/sys/queue.h In-Reply-To: <199803131808.LAA15797@pluto.plutotech.com> from "Justin T. Gibbs" at "Mar 13, 98 11:05:32 am" To: gibbs@plutotech.com (Justin T. Gibbs) Date: Sat, 14 Mar 1998 00:11:00 +0100 (CET) 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 According to Justin T. Gibbs: > Actually, inline functions will not work for the queue macros unless you > change the way you specify the "links" portion of the object. I agree > that, in general, using an inline is better than using a macro. Just FYI. Inline functions also result in non-inlined code when compiling with -g. Also, inlines should be declared "static inline" to act as "real inlines" in gcc. I was rather stunned when I was pointed to gcc info pages about this, when I was trying to argue that "static" was completely useless to add to inline functions. I was proved wrong, for gcc inlines. I haven't checked, but I would think g++ generates "real inlines" without the "static" keyword. /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 16:02:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15087 for freebsd-current-outgoing; Fri, 13 Mar 1998 16:02:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15081 for ; Fri, 13 Mar 1998 16:02:51 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-3-16.camtech.net.au [203.28.0.112]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id KAA04770; Sat, 14 Mar 1998 10:30:27 +1030 (CST) Message-ID: <3509C8D7.60F8C892@camtech.net.au> Date: Sat, 14 Mar 1998 10:31:27 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Trenton Schulz CC: FreeBSD CURRENT Subject: Re: trouble booting References: Content-Type: multipart/mixed; boundary="------------F3C3EFE07EC20F8D389F9818" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------F3C3EFE07EC20F8D389F9818 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Change your /etc/fstab root filesystem entry. You obviously haven't been reading the cvs-all mailing list and thus should not be running current. from: /dev/wd0a / ufs rw 1 1 to: /dev/wd0s2a / ufs rw 1 1 Trenton Schulz wrote: > > My recent CVSUP from 3/9 on seems to give me trouble when I'm booting. My > computer's hard disk has two partitions one for DOS and one for FreeBSD. > The Make World and re-making the kernel go alright, but when I boot, the > kernel tells me it is switching the root device to wd0s3a. At this point > it seems to fsck the disks but then gives the message that the "filesystem > failed to mount" and puts me in single user mode with a read-only root > filesystem. Luckily the previous kernel still boots correctly. This > allowed the correct specification of devices is fstab, (wd0s2a for root > device, wd0s3a causing the system to not do anything) but when I reboot > the machine it still gives me the same error about the filesystem failing. > When I try to remount root it tells me that wd0s2a doesn't match mounted > device, but yet if I mount wd0s2a on /mnt, it _is_ the root partition. I > thought a new make world and kernel would solve this problem, but it > hasn't. I'm sorry for being so ignorant on what to do, but could someone > please help me get my system to boot on something besides an old kernel? > > Trenton Schulz > twschulz@cord.edu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 --------------F3C3EFE07EC20F8D389F9818 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Received: from y.physics.usyd.edu.au (y.physics.usyd.edu.au [129.78.129.110]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id BAA11542 for ; Mon, 9 Mar 1998 01:57:41 +1030 (CST) Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by y.physics.usyd.edu.au (8.8.5/8.8.2) with ESMTP id CAA27901; Mon, 9 Mar 1998 02:24:27 +1100 (EST) Received: from localhost (daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA05589; Sun, 8 Mar 1998 07:24:24 -0800 (PST) (envelope-from owner-freebsd-current) Received: by hub.freebsd.org (bulk_mailer v1.6); Sun, 8 Mar 1998 07:20:16 -0800 Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04712 for freebsd-current-outgoing; Sun, 8 Mar 1998 07:20:12 -0800 (PST) (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 HAA04706; Sun, 8 Mar 1998 07:20:06 -0800 (PST) (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 HAA10644; Sun, 8 Mar 1998 07:18:50 -0800 (PST) Message-Id: <199803081518.HAA10644@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Michael Smith cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c In-reply-to: Your message of "Sun, 08 Mar 1998 07:06:58 PST." <199803081506.HAA06931@freefall.freebsd.org> Mime-Version: 1.0 Date: Sun, 08 Mar 1998 07:18:50 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.ORG Content-Type: text/plain; charset=us-ascii > Modified files: > sys/i386/i386 autoconf.c > Log: > Construct the minor number for the root device taking into account the > slice number passed in by the bootblocks. This means the kernel will > not use the compatability slice to obtain the root filesystem when > booting from a sliced disk. *WARNING* If your boot disk is sliced (has a partition table), and you have not upgraded /sbin/mount to the most recent version preceeding this change, you will have problems booting. This change means that if your current /etc/fstab looks like this: /dev/xd0a / ufs ... /dev/xd0s2e /usr ufs ... you need to update it to look like: /dev/xd0s2a / ufs ... /dev/xd0s2e /usr ufs ... Note that the root filesystem is now consistent with the others. If you are using a 'dedicated' disk, you will have entries like /dev/xd0a / ufs ... /dev/xd0e /usr ufs ... and you should *not* change. The recent update to /sbin/mount includes compatability support which will ease this transition. -- \\ 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 --------------F3C3EFE07EC20F8D389F9818-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 16:13:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16358 for freebsd-current-outgoing; Fri, 13 Mar 1998 16:13:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16347 for ; Fri, 13 Mar 1998 16:13:49 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-3-16.camtech.net.au [203.28.0.112]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id KAA05569; Sat, 14 Mar 1998 10:41:24 +1030 (CST) Message-ID: <3509CB68.C87849FA@camtech.net.au> Date: Sat, 14 Mar 1998 10:42:24 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Trenton Schulz , FreeBSD CURRENT Subject: Re: trouble booting References: <3509C8D7.60F8C892@camtech.net.au> Content-Type: multipart/mixed; boundary="------------39B25067C1D6E5EBA1BC3139" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------39B25067C1D6E5EBA1BC3139 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Oops. Sorry for that last mail. I had not read all your message before sending it. I'm not sure what is wrong.. I have successfully gone through that point in CURRENT. I always make a new kernel, boot on it and then make world. I updated my fstab before booting the first new kernel and my make world and next kernel worked fine. Matthew Thyer wrote: > > Change your /etc/fstab root filesystem entry. > You obviously haven't been reading the cvs-all > mailing list and thus should not be running current. > > from: > /dev/wd0a / ufs rw 1 1 > > to: > /dev/wd0s2a / ufs rw 1 1 > > Trenton Schulz wrote: > > > > My recent CVSUP from 3/9 on seems to give me trouble when I'm booting. My > > computer's hard disk has two partitions one for DOS and one for FreeBSD. > > The Make World and re-making the kernel go alright, but when I boot, the > > kernel tells me it is switching the root device to wd0s3a. At this point > > it seems to fsck the disks but then gives the message that the "filesystem > > failed to mount" and puts me in single user mode with a read-only root > > filesystem. Luckily the previous kernel still boots correctly. This > > allowed the correct specification of devices is fstab, (wd0s2a for root > > device, wd0s3a causing the system to not do anything) but when I reboot > > the machine it still gives me the same error about the filesystem failing. > > When I try to remount root it tells me that wd0s2a doesn't match mounted > > device, but yet if I mount wd0s2a on /mnt, it _is_ the root partition. I > > thought a new make world and kernel would solve this problem, but it > > hasn't. I'm sorry for being so ignorant on what to do, but could someone > > please help me get my system to boot on something besides an old kernel? > > > > Trenton Schulz > > twschulz@cord.edu > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > /=====================================================================\ > |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| > \=====================================================================/ > "If it is true that our Universe has a zero net value for all conserved > quantities, then it may simply be a fluctuation of the vacuum of some > larger space in which our Universe is imbedded. In answer to the > question of why it happened, I offer the modest proposal that our > Universe is simply one of those things which happen from time to time." > E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 > > ------------------------------------------------------------------------------ > > Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c > Date: Sun, 08 Mar 1998 07:18:50 -0800 > From: Mike Smith > To: Michael Smith > CC: current@FreeBSD.ORG > > > Modified files: > > sys/i386/i386 autoconf.c > > Log: > > Construct the minor number for the root device taking into account the > > slice number passed in by the bootblocks. This means the kernel will > > not use the compatability slice to obtain the root filesystem when > > booting from a sliced disk. > > *WARNING* > > If your boot disk is sliced (has a partition table), and you have not > upgraded /sbin/mount to the most recent version preceeding this change, > you will have problems booting. > > This change means that if your current /etc/fstab looks like this: > > /dev/xd0a / ufs ... > /dev/xd0s2e /usr ufs ... > > you need to update it to look like: > > /dev/xd0s2a / ufs ... > /dev/xd0s2e /usr ufs ... > > Note that the root filesystem is now consistent with the others. If > you are using a 'dedicated' disk, you will have entries like > > /dev/xd0a / ufs ... > /dev/xd0e /usr ufs ... > > and you should *not* change. > > The recent update to /sbin/mount includes compatability support which > will ease this transition. > > -- > \\ 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 -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 --------------39B25067C1D6E5EBA1BC3139 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Received: from y.physics.usyd.edu.au (y.physics.usyd.edu.au [129.78.129.110]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id NAA03211 for ; Mon, 9 Mar 1998 13:13:41 +1030 (CST) Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by y.physics.usyd.edu.au (8.8.5/8.8.2) with ESMTP id NAA02176; Mon, 9 Mar 1998 13:37:38 +1100 (EST) Received: from localhost (daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA28027; Sun, 8 Mar 1998 18:37:21 -0800 (PST) (envelope-from owner-freebsd-current) Received: by hub.freebsd.org (bulk_mailer v1.6); Sun, 8 Mar 1998 18:30:46 -0800 Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26613 for freebsd-current-outgoing; Sun, 8 Mar 1998 18:30:44 -0800 (PST) (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 SAA26608 for ; Sun, 8 Mar 1998 18:30:40 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id SAA17159; Sun, 8 Mar 1998 18:24:15 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd017156; Sun Mar 8 18:24:11 1998 Date: Sun, 8 Mar 1998 18:19:53 -0800 (PST) From: Julian Elischer To: Chuck Robey cc: Mike Smith , Thomas Dean , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys reboot.h src/sys/i386/i386 autoconf.c In-Reply-To: Message-ID: MIME-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.ORG Content-Type: TEXT/PLAIN; charset=US-ASCII the easiest way is to see the output of fdisk /dev/rwd0 if the BSD partition starts at 0 then it's dangerously dedicated. if it starts above 0 then it's not On Sun, 8 Mar 1998, Chuck Robey wrote: > On Sun, 8 Mar 1998, Mike Smith wrote: > > Mike, regarding the disk, I can't remember if I made the disk I'm using > right now "dangerously dedicated" or not, and there isn't, obviously > (else I wouldn't be confused) any msdos partition. Seeing as I don't > dare make a mistake on this, and don't do all that much installation, > would you kindly tell me exactly what I should do to find out if I have > to change my fstab or not? > > I'm purposely omitting my fstab so that your answer will be general > enough so that everyone will have no excuse for not reading your answer, > and won't end up screwed if they make some messy mistake. > > I am not sure what to look for in doing disklabel, to show me if the > disk is dangerously dedicated or not. > > ----------------------------+----------------------------------------------- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message --------------39B25067C1D6E5EBA1BC3139-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 16:41:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21416 for freebsd-current-outgoing; Fri, 13 Mar 1998 16:41:10 -0800 (PST) (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 QAA21387 for ; Fri, 13 Mar 1998 16:41:05 -0800 (PST) (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 AAA20929; Sat, 14 Mar 1998 00:40:12 GMT Date: Sat, 14 Mar 1998 09:40:12 +0900 (JST) From: Michael Hancock To: Tor Egge cc: freebsd-current@FreeBSD.ORG Subject: Re: 4 WILLRELE's to bite the dust In-Reply-To: <199803131845.TAA26656@pat.idi.ntnu.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tor, Excellent! I'm not fixing bugs at this stage, but after all the rele's and locks have moved to the right place it should be easier to solve some of the problems you've listed. I'm being conservative because of the volume of code I need to go through, but maybe we can coordinate on fixing some of the easier problems as I do these changes. Regards, Mike Hancock On Fri, 13 Mar 1998, Tor Egge wrote: > > I did some simple testing of nullfs and union. It's seems Kato-san has > > gotten them pretty stable. What kind of things cause problems with null > > and union? > > - coherence. When the different layers operates on separate > vm objects, the vm objects might get out of sync. > E.g. page fault algorithms checks the size of the upper > vm object, and gets the wrong value, since a VOP_WRITE > only extended the size of the lower vm object. > > Symptom: install -C during make world gets a SIBGUS > if /usr/obj is nullfs mounted. > > - freeing of resources. When the file is unlinked, the > lower vnode still has a reference from the upper vnode > which is left until the upper vnode is recycled. Currently > null_inactive calls VOP_INACTIVE on the lower vnode. > This is wrong (e.g. a process directly accessing the lower > vnode will see a truncated file, which is an unintended > side effect). > > Symptom: Removing a file that has been opend via nullfs > will not necessarily free the space on the file system > before the null vnode is recycled. > > - locking. > > - Missing vnode locking during vnode recycling, > i.e. does not wait for inactive to complete. > Symptom: lock manager panic when trying > to release the lock in vclean. > > - During object recycling, the VOP_ISLOCKED method > can cause a trap 12. This problem might not > occur anymore, since vfs_msync now checks for > the VXLOCK vnode flag. > > - Use of VOP_ISLOCKED() is very often a kludge, since > it is assumed that the current process is the owner > of an exclusive lock on the vnode, while it might > be a different process or a shared lock. > > - vnode leakage in null_node_alloc. > > - During vnode recycling, fsync is called several times on > the lower vnode. This only affects performance. > > - Access to files on a nullfs file system gives spurious > EDEADLK errors, due to a bogus deadlock detection in > nullfs_root. That deadlock detection is not needed > if the generic mount system call is slightly changed. > (most local file systems has the same kind of deadlock > problem, thus a generic solution is preferrable). > > > I've been using nullfs since Nov 7 1997 without any serious problems > after having fixed some of the above mentioned problems in my local > source tree. The code is not perfect, panics are still possible due > to heuristics (due to VOP_ISLOCKED()) being wrong, but I've yet > not experienced any problems. > > Using the nullfs in -current without any fixes, a make world would > very likely not succeed if /usr/obj is nullfs mounted. > > By modifying null_mount, I've played around with hierarchical mounts: > > ikke# find /usr/zzz -print > /usr/zzz > /usr/zzz/zzz4 > /usr/zzz/zzz4/test4 > ikke# mount -t null /usr/zzz /usr/zzz > null: Resource deadlock avoided > ikke# mount -t null /usr/zzz /usr/zzz/zzz4 > ikke# find /usr/zzz -print > /usr/zzz > /usr/zzz/zzz4 > /usr/zzz/zzz4/zzz4 > /usr/zzz/zzz4/zzz4/test4 > ikke# umount /usr/zzz/zzz4 > ikke# mount -t null /usr/zzz/zzz4 /usr/zzz > ikke# find /usr/zzz -print > /usr/zzz > /usr/zzz/test4 > ikke# umount /usr/zzz > ikke# mount -t null /usr/zzz /usr/yyy > ikke# mount -t null /usr/zzz /usr/yyy > null: Resource deadlock avoided > ikke# mount -t null /usr/yyy /usr/zzz > null: Resource deadlock avoided > ikke# mount -t null /usr/yyy /usr/yyy > null: Resource deadlock avoided > ikke# mount -t null /usr/zzz /usr/yyy > null: Resource deadlock avoided > ikke# mount -t null /usr/zzz /usr/zzz > null: Resource deadlock avoided > ikke# umount /usr/yyy > > I saw the need for a general change in the mount system call when I issued > > mount /usr/zzz /usr/zzz > > instead of > > mount -t null /usr/zzz /usr/zzz > > when testing the nullfs deadlock handling, and got a panic, due to bugs in the > the ufs mount code. > > With a changed mount system call, I get > > ikke# mount /usr/zzz /usr/zzz > /usr/zzz on /usr/zzz: Block device required > ikke# mount -t null /usr/zzz /usr/zzz > null: Device busy > ikke# mount -t msdos /usr/zzz /usr/zzz > msdos: /usr/zzz: Block device required > ikke# mount -t cd9660 /usr/zzz /usr/zzz > cd9660: Block device required > ikke# ls -ld /usr/zzz > drwxr-xr-x 3 root wheel 512 Feb 10 02:02 /usr/zzz > > > - Tor Egge > -- michaelh@cet.co.jp http://www.cet.co.jp CET Inc., Daiichi Kasuya BLDG 8F, 2-5-12 Higashi Shinbashi, Minato-ku, Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 17:12:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26722 for freebsd-current-outgoing; Fri, 13 Mar 1998 17:12:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt050ndd.san.rr.com (@dt050n33.san.rr.com [204.210.31.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26703 for ; Fri, 13 Mar 1998 17:12:29 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (Studded@localhost [127.0.0.1]) by dt050ndd.san.rr.com (8.8.8/8.8.8) with ESMTP id RAA26392; Fri, 13 Mar 1998 17:12:07 -0800 (PST) (envelope-from Studded@dal.net) Message-ID: <3509D966.DAE44397@dal.net> Date: Fri, 13 Mar 1998 17:12:06 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-BETA-0312 i386) MIME-Version: 1.0 To: Matthew Thyer CC: FreeBSD CURRENT Subject: Re: trouble booting References: <3509C8D7.60F8C892@camtech.net.au> <3509CB68.C87849FA@camtech.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Thyer wrote: > I always make a new kernel, boot on it and then make world. I'm curious about this. This isn't a dig, although my incredulity might make it seem so. Every piece of documentation I've seen says to do it the other way around. Make world first, then build kernel, then boot. Experience tells me that this is a good thing, and there have been numerous changes made in the past that require you to build the world first (like ipfw). So the question is, why do you build the kernel first? What advantage do you think it will provide? Curious, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 17:25:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29143 for freebsd-current-outgoing; Fri, 13 Mar 1998 17:25:56 -0800 (PST) (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 RAA29135 for ; Fri, 13 Mar 1998 17:25:52 -0800 (PST) (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 BAA09634 for ; Sat, 14 Mar 1998 01:25:44 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id UAA21665 for freebsd-current@freebsd.org; Fri, 13 Mar 1998 20:25:43 -0500 (EST) From: Mikhail Teterin Message-Id: <199803140125.UAA21665@rtfm.ziplink.net> Subject: Kerberos and telnet, su, rsh.... To: freebsd-current@FreeBSD.ORG Date: Fri, 13 Mar 1998 20:25:43 -0500 (EST) 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 SAA04559 for freebsd-current-outgoing; Fri, 13 Mar 1998 18:05:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04543 for ; Fri, 13 Mar 1998 18:05:53 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id DAA21272; Sat, 14 Mar 1998 03:00:40 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199803140200.DAA21272@ocean.campus.luth.se> Subject: Re: idprio/rtprio In-Reply-To: <19980312123427.A12954@emsphone.com> from Dan Nelson at "Mar 12, 98 12:34:27 pm" To: dnelson@emsphone.com (Dan Nelson) Date: Sat, 14 Mar 1998 03:00:40 +0100 (CET) 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 According to Dan Nelson: > In the last episode (Mar 12), Mikael Karpberg said: > > > It's the man page that's wrong since this was disallowed awhile > > > back after BEST Internet filed a PR noting that an ordinary user > > > could put your system in very bad shape by using it. The man page > > > has been fixed, thanks. > > > > Hmm... I just can't seem to remember how. Breif summary? > > > > How? Easy. Run rc564 at idlepri, and run another high-CPU process. > Eventually, the rc564 process will try a filesystem operation. After > that, every process trying to hit a file will hang too. If you > unidprio the rc564 process or kill the high-cpu process (letting rc564 > run again) everything will return to normal. I've done this to myself > three or four times, and have resorted to running rc564 at nice 20 for > now. Ah, I see. But... shouldn't that be handled by some priority inheritance thingie in the scheduler, instead? I mean, it's no better if root runs it, is it? So it renders idleprio basically useless, no? Or is this one of those "YES! Exactly right. Where's your patches?" cases? /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 18:51:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09875 for freebsd-current-outgoing; Fri, 13 Mar 1998 18:51:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09841; Fri, 13 Mar 1998 18:51:13 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.7/8.6.12) id CAA21517; Sat, 14 Mar 1998 02:51:06 GMT Message-ID: <19980313185105.21172@nuxi.com> Date: Fri, 13 Mar 1998 18:51:05 -0800 From: "David E. O'Brien" To: Mike Smith Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG, joerg@FreeBSD.ORG Subject: Re: *HEADS UP* Correction to previous postings. Reply-To: obrien@NUXI.com References: <199803090852.AAA14131@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199803090852.AAA14131@dingo.cdrom.com>; from Mike Smith on Mon, Mar 09, 1998 at 12:52:38AM -0800 X-Warning: Mutt Bites! X-Operating-System: FreeBSD 2.2.5-STABLE Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In light of the new mount changes, how should these instructions from Jo"rg be updated? dd if=/dev/zero of=/dev/rsd2 bs=1k count=1 disklabel -Brw sd2 auto disklabel -e sd2 newfs -d0 /dev/rsd2e fsck /dev/sd2e Is the slice created by ``disklable .. auto'' always "s1"? Doesn't a dedicatedly partitioned disk, really not contain slices? fdisk(8) reports them as living in [fdisk] partition 4. Can't tell what sysinstall would do in "dangerous dedicated mode" as it won't see the drives on my second SCSI bus. :( fsck /dev/sd2s1e Can't open /dev/rsd2s1e: Device not configured fsck /dev/sd2s4e Can't open /dev/rsd2s4e: Device not configured dd if=/dev/zero of=/dev/rsd2 bs=1k count=1 disklabel -Brw sd2s1 auto disklabel: /dev/rsd2s1e: Device not configured disklabel -Brw sd2s4 auto disklabel: /dev/rsd2s4e: Device not configured So what's the new way? -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 19:10:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14510 for freebsd-current-outgoing; Fri, 13 Mar 1998 19:10:39 -0800 (PST) (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 TAA14419 for ; Fri, 13 Mar 1998 19:10:14 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id OAA16205 for current@freebsd.org; Sat, 14 Mar 1998 14:11:49 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803140311.OAA16205@cimlogic.com.au> Subject: binutils bloat To: current@FreeBSD.ORG Date: Sat, 14 Mar 1998 14:11:49 +1100 (EST) 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 Are people going to object if we keep _all_ the binutils source in src/contrib/binutils so that we can define a few things in /etc/make.conf and get cross tools out of a `make world'? I've had a play with this and I've found it is annoying to have to go back and figure out which sources you have to add to your local cvs tree to get this to work. -- 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 Mar 13 19:26:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19813 for freebsd-current-outgoing; Fri, 13 Mar 1998 19:26:38 -0800 (PST) (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 TAA19802 for ; Fri, 13 Mar 1998 19:26:34 -0800 (PST) (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 TAA03012; Fri, 13 Mar 1998 19:23:59 -0800 (PST) Message-Id: <199803140323.TAA03012@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: John Birrell cc: current@FreeBSD.ORG Subject: Re: binutils bloat In-reply-to: Your message of "Sat, 14 Mar 1998 14:11:49 +1100." <199803140311.OAA16205@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Mar 1998 19:23:57 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are people going to object if we keep _all_ the binutils source in > src/contrib/binutils so that we can define a few things in /etc/make.conf > and get cross tools out of a `make world'? > > I've had a play with this and I've found it is annoying to have to > go back and figure out which sources you have to add to your local > cvs tree to get this to work. Are the cross tools only useful for targetting FreeBSD systems? Can you poke it so that it produces more than one set of cross tools in a given world build? (does binutils support multitargetting? I seem to recall something that implied it was going to way-back-when.) I could see the sense in putting bits in for likely targets (sparc, alpha, ppc, maybe a few others), but dinosaurs like the Vax, m88k, amd29k etc. could probably be ignored. OTOH, what is the actual footprint we're talking about here? Disk is cheap. 8) -- \\ 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 Mar 13 19:33:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22177 for freebsd-current-outgoing; Fri, 13 Mar 1998 19:33:37 -0800 (PST) (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 TAA22106 for ; Fri, 13 Mar 1998 19:33:32 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id OAA16288; Sat, 14 Mar 1998 14:35:03 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803140335.OAA16288@cimlogic.com.au> Subject: Re: binutils bloat In-Reply-To: <199803140323.TAA03012@dingo.cdrom.com> from Mike Smith at "Mar 13, 98 07:23:57 pm" To: mike@smith.net.au (Mike Smith) Date: Sat, 14 Mar 1998 14:35:03 +1100 (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 Mike Smith wrote: > Are the cross tools only useful for targetting FreeBSD systems? Can > you poke it so that it produces more than one set of cross tools in a > given world build? (does binutils support multitargetting? I seem to > recall something that implied it was going to way-back-when.) The cross tools are useful for any of the operating systems supported by bfd/opcodes in binutils, not just FreeBSD. In my case, I'm interested in cross tools to build on either i386 or alpha, targeted at an mvme147 (m68k) which takes forever to compile things itself. > I could see the sense in putting bits in for likely targets (sparc, > alpha, ppc, maybe a few others), but dinosaurs like the Vax, m88k, > amd29k etc. could probably be ignored. It's a pain working out which bits are required without building to find out. For example, the alpha gas code needs a vax floating point file. 8-) > OTOH, what is the actual footprint we're talking about here? Disk is > cheap. 8) du -ks /u2/gnu/binutils-2.8.1 /u/freebsd/src/src/contrib/binutils 22818 /u2/gnu/binutils-2.8.1 10575 /u/freebsd/src/src/contrib/binutils 12Mb worst case. A bit less if you leave of the testsuites. -- 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 Mar 13 19:43:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25957 for freebsd-current-outgoing; Fri, 13 Mar 1998 19:43:50 -0800 (PST) (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 TAA25866 for ; Fri, 13 Mar 1998 19:43:33 -0800 (PST) (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 TAA03092; Fri, 13 Mar 1998 19:40:26 -0800 (PST) Message-Id: <199803140340.TAA03092@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: John Birrell cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG Subject: Re: binutils bloat In-reply-to: Your message of "Sat, 14 Mar 1998 14:35:03 +1100." <199803140335.OAA16288@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Mar 1998 19:40:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > Are the cross tools only useful for targetting FreeBSD systems? Can > > you poke it so that it produces more than one set of cross tools in a > > given world build? (does binutils support multitargetting? I seem to > > recall something that implied it was going to way-back-when.) > > The cross tools are useful for any of the operating systems supported > by bfd/opcodes in binutils, not just FreeBSD. In my case, I'm interested > in cross tools to build on either i386 or alpha, targeted at an mvme147 > (m68k) which takes forever to compile things itself. Understood, but that doesn't answer the initial question, which was "if you build binutils supporting other systems, do you still get tools that support FreeBSD", ie. do the new tools suddenly multitarget, or do you run the risk of overwriting your normal tools? > > I could see the sense in putting bits in for likely targets (sparc, > > alpha, ppc, maybe a few others), but dinosaurs like the Vax, m88k, > > amd29k etc. could probably be ignored. > > It's a pain working out which bits are required without building to > find out. For example, the alpha gas code needs a vax floating point > file. 8-) Hmm. Maybe come up with a list of desirable targets? > > OTOH, what is the actual footprint we're talking about here? Disk is > > cheap. 8) > > du -ks /u2/gnu/binutils-2.8.1 /u/freebsd/src/src/contrib/binutils > 22818 /u2/gnu/binutils-2.8.1 > 10575 /u/freebsd/src/src/contrib/binutils > > 12Mb worst case. A bit less if you leave of the testsuites. Hmm. If you win this one, I think I can use the precedent. 8) -- \\ 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 Mar 13 19:49:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27855 for freebsd-current-outgoing; Fri, 13 Mar 1998 19:49:03 -0800 (PST) (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 TAA27761 for ; Fri, 13 Mar 1998 19:48:44 -0800 (PST) (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 TAA29832; Fri, 13 Mar 1998 19:44:08 -0800 (PST) Message-Id: <199803140344.TAA29832@implode.root.com> To: Mikael Karpberg cc: dnelson@emsphone.com (Dan Nelson), freebsd-current@FreeBSD.ORG Subject: Re: idprio/rtprio In-reply-to: Your message of "Sat, 14 Mar 1998 03:00:40 +0100." <199803140200.DAA21272@ocean.campus.luth.se> From: David Greenman Reply-To: dg@root.com Date: Fri, 13 Mar 1998 19:44:08 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Or is this one of those "YES! Exactly right. Where's your patches?" cases? Right. We had two choices: disable/remove it completely or restrict it to just root. I chose the latter. -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 Fri Mar 13 19:52:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28862 for freebsd-current-outgoing; Fri, 13 Mar 1998 19:52:18 -0800 (PST) (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 TAA28784 for ; Fri, 13 Mar 1998 19:52:02 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id OAA16327; Sat, 14 Mar 1998 14:53:34 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803140353.OAA16327@cimlogic.com.au> Subject: Re: binutils bloat In-Reply-To: <199803140340.TAA03092@dingo.cdrom.com> from Mike Smith at "Mar 13, 98 07:40:26 pm" To: mike@smith.net.au (Mike Smith) Date: Sat, 14 Mar 1998 14:53:34 +1100 (EST) Cc: jb@cimlogic.com.au, mike@smith.net.au, 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 Mike Smith wrote: > Understood, but that doesn't answer the initial question, which was "if > you build binutils supporting other systems, do you still get tools > that support FreeBSD", ie. do the new tools suddenly multitarget, or do > you run the risk of overwriting your normal tools? Yes the tools (except gas) multitarget. For example, objdump on alpha can disassemble an aout i386 object without you telling what system the object was for. Same for nm, strip, etc. I'm having a go at building m68k into binutils on alpha now. I'll see if it can recognise NetBSD/mvme68k. I tried to get i386 to disassemble elf64 but the code wouldn't compile without bit overflow (ie > 32) warnings and it asserted when run. For gas, a few subdirs of src/gnu/usr.bin/binutils with optional defines could build gas_m68k etc. But only if you enabled something in /etc/make.conf. > Hmm. If you win this one, I think I can use the precedent. 8) After saying that, it's probably not winable. 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 Fri Mar 13 20:04:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01769 for freebsd-current-outgoing; Fri, 13 Mar 1998 20:04:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01751 for ; Fri, 13 Mar 1998 20:04:32 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-13-15.camtech.net.au [203.55.242.79]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id OAA22672; Sat, 14 Mar 1998 14:32:02 +1030 (CST) Message-ID: <350A0175.F8D28907@camtech.net.au> Date: Sat, 14 Mar 1998 14:33:01 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Studded CC: FreeBSD CURRENT Subject: Re: trouble booting References: <3509C8D7.60F8C892@camtech.net.au> <3509CB68.C87849FA@camtech.net.au> <3509D966.DAE44397@dal.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm curious too. I hope someone else might comment on the possible benefits of making a new kernel first ! I think I read somewhere once that occasionally a make world may require this... i.e. the new code uses new features in the kernel during compilation or something like that. Is this real anyone ? Or am I just wasting 8 minutes or so doing this. Studded wrote: > > Matthew Thyer wrote: > > > I always make a new kernel, boot on it and then make world. > > I'm curious about this. This isn't a dig, although my incredulity might > make it seem so. Every piece of documentation I've seen says to do it > the other way around. Make world first, then build kernel, then boot. > Experience tells me that this is a good thing, and there have been > numerous changes made in the past that require you to build the world > first (like ipfw). > > So the question is, why do you build the kernel first? What advantage > do you think it will provide? > > Curious, > > Doug > > -- > *** Chief Operations Officer, DALnet IRC network *** > *** Proud operator, designer and maintainer of the world's largest > *** Internet Relay Chat server. 5,328 clients and still growing. > *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 20:16:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04084 for freebsd-current-outgoing; Fri, 13 Mar 1998 20:16:33 -0800 (PST) (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 UAA04073 for ; Fri, 13 Mar 1998 20:16:29 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id PAA16394; Sat, 14 Mar 1998 15:17:41 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803140417.PAA16394@cimlogic.com.au> Subject: Re: trouble booting In-Reply-To: <350A0175.F8D28907@camtech.net.au> from Matthew Thyer at "Mar 14, 98 02:33:01 pm" To: thyerm@camtech.net.au (Matthew Thyer) Date: Sat, 14 Mar 1998 15:17:41 +1100 (EST) Cc: Studded@dal.net, 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 Matthew Thyer wrote: > I'm curious too. > > I hope someone else might comment on the possible benefits of > making a new kernel first ! > > I think I read somewhere once that occasionally a make world > may require this... i.e. the new code uses new features in > the kernel during compilation or something like that. > > Is this real anyone ? Or am I just wasting 8 minutes or so > doing this. Last year, NetBSD designed a new stat syscall. The old one continued to exist (same number), but any new compiles would use __stat13 when you called stat(). In this case, you had to build and boot a new kernel before building libc. The old programs continued to work with the new kernel, but new programs failed with the old kernel because of the missing syscall. So it depends on what the changes are. If you don't follow -current closely (and continuously like I didn't last year 8-), then this sort of thing bites. -- 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 Mar 13 20:40:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08310 for freebsd-current-outgoing; Fri, 13 Mar 1998 20:40:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08259; Fri, 13 Mar 1998 20:40:33 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA19697; Sat, 14 Mar 1998 15:37:00 +1100 Date: Sat, 14 Mar 1998 15:37:00 +1100 From: Bruce Evans Message-Id: <199803140437.PAA19697@godzilla.zeta.org.au> To: mike@smith.net.au, obrien@NUXI.com Subject: Re: *HEADS UP* Correction to previous postings. Cc: current@FreeBSD.ORG, joerg@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In light of the new mount changes, how should these instructions from >Jo"rg be updated? > > dd if=/dev/zero of=/dev/rsd2 bs=1k count=1 > disklabel -Brw sd2 auto > disklabel -e sd2 > newfs -d0 /dev/rsd2e > fsck /dev/sd2e No change. >Is the slice created by ``disklable .. auto'' always "s1"? It depends. If you have cleared the DOS partition table using dd as above, then `disklabel ... auto' gives a bogus partition entry in the slot normally occupied by slice s4. The kernel initially reports this as slice s5, but the driver won't create any slices, and the kernel will later mount sd2e (if you booted from that instead of the default sd2a, and nothing else goes wrong). >Doesn't a dedicatedly partitioned disk, really not contain slices? Depends how it was dedicated. There are several cases: 1. as above. 2. as above, then run fdisk to change the 4th partition entry in any way (e.g., to de-bogotify or clear it). Then you really get real slices (probably broken ones if the 4th entry is changed to anything except an entry covering the whole disk). 3. as in (2), but prepare the 4th entry before running disklabel, and skip the dd step. 4. as in (1), but leave out -B. Then you get an all-zero MBR, really without real slices. Disks configured in this way can't be booted from directly. 5. as in (1), but edit the MBR to remove the 0xAA55 signature. Then you get an ignored MBR, effectively without real slices. It may be possible to boot from disk configured in this way (depends on the BIOS). >fdisk(8) reports them as living in [fdisk] partition 4. Can't tell what >sysinstall would do in "dangerous dedicated mode" as it won't see the >drives on my second SCSI bus. :( Sysinstall doesn't seem to provide d.d. mode by default. The default for "A Use Entire Disk" seems to be to not actually use the entire disk, but to use real slices and the entire disk except for the MBR (and other sectors on the first "track"?). > fsck /dev/sd2s1e > Can't open /dev/rsd2s1e: Device not configured > fsck /dev/sd2s4e > Can't open /dev/rsd2s4e: Device not configured > > dd if=/dev/zero of=/dev/rsd2 bs=1k count=1 > disklabel -Brw sd2s1 auto > disklabel: /dev/rsd2s1e: Device not configured > disklabel -Brw sd2s4 auto > disklabel: /dev/rsd2s4e: Device not configured > >So what's the new way? Same as before: don't use slices when you don't have them. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 20:50:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09841 for freebsd-current-outgoing; Fri, 13 Mar 1998 20:50:27 -0800 (PST) (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 UAA09836 for ; Fri, 13 Mar 1998 20:50:25 -0800 (PST) (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 UAA03267; Fri, 13 Mar 1998 20:47:54 -0800 (PST) Message-Id: <199803140447.UAA03267@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: John Birrell cc: current@FreeBSD.ORG Subject: Re: binutils bloat In-reply-to: Your message of "Sat, 14 Mar 1998 14:53:34 +1100." <199803140353.OAA16327@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Mar 1998 20:47:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For gas, a few subdirs of src/gnu/usr.bin/binutils with optional > defines could build gas_m68k etc. But only if you enabled something > in /etc/make.conf. Erk. That's kinda ugly; this isn't something that could be trivially automated I suppose. > > Hmm. If you win this one, I think I can use the precedent. 8) > > After saying that, it's probably not winable. 8-( Perhaps. See if you can sell a few people on the value involved. -- \\ 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 Mar 13 21:03:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10927 for freebsd-current-outgoing; Fri, 13 Mar 1998 21:03:14 -0800 (PST) (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 VAA10921 for ; Fri, 13 Mar 1998 21:03:08 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id QAA16504; Sat, 14 Mar 1998 16:04:36 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803140504.QAA16504@cimlogic.com.au> Subject: Re: binutils bloat In-Reply-To: <199803140447.UAA03267@dingo.cdrom.com> from Mike Smith at "Mar 13, 98 08:47:53 pm" To: mike@smith.net.au (Mike Smith) Date: Sat, 14 Mar 1998 16:04:35 +1100 (EST) Cc: jb@cimlogic.com.au, 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 Mike Smith wrote: > > For gas, a few subdirs of src/gnu/usr.bin/binutils with optional > > defines could build gas_m68k etc. But only if you enabled something > > in /etc/make.conf. > > Erk. That's kinda ugly; this isn't something that could be trivially > automated I suppose. It was born ugly (GPL). Automated? I'm not sure. Somewhere you have to store the config and it's not just a matter of running `configure' To me, the simplest way of storing that config is to chuck it in a makefile, like the one that builds gas for i386: BINDIR= /usr/libexec/elf SRCS+= tc-i386.c (yes, that's the entire makefile) or alpha: BINDIR= /usr/bin SRCS+= tc-alpha.c LDADD+= -L${RELTOP}/libopcodes -lopcodes (more complicated). The cross version would probably be significantly more complicated, because it would have to specify the program name and target architecture. (2 more lines?) Trying to automate this sounds like over-kill to me. -- 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 Mar 13 21:08:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11599 for freebsd-current-outgoing; Fri, 13 Mar 1998 21:08:07 -0800 (PST) (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 VAA11594 for ; Fri, 13 Mar 1998 21:08:06 -0800 (PST) (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 VAA03336; Fri, 13 Mar 1998 21:05:36 -0800 (PST) Message-Id: <199803140505.VAA03336@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: John Birrell cc: current@FreeBSD.ORG Subject: Re: binutils bloat In-reply-to: Your message of "Sat, 14 Mar 1998 16:04:35 +1100." <199803140504.QAA16504@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Mar 1998 21:05:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Erk. That's kinda ugly; this isn't something that could be trivially > > automated I suppose. > > It was born ugly (GPL). Automated? I'm not sure. Somewhere you have > to store the config and it's not just a matter of running `configure' ... or more to the point the configuration isn't a uniform item; it varies with target. So unless you have a list of known targets on hand, you can't do it "automatically". IMHO that's a pretty strong selection criteria for what to include from binutils; if there's a canned gas config for a target, then the files that target requires should be included. -- \\ 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 Mar 13 21:29:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13724 for freebsd-current-outgoing; Fri, 13 Mar 1998 21:29:07 -0800 (PST) (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 VAA13716 for ; Fri, 13 Mar 1998 21:29:03 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id QAA16560; Sat, 14 Mar 1998 16:30:36 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803140530.QAA16560@cimlogic.com.au> Subject: Re: binutils bloat In-Reply-To: <199803140505.VAA03336@dingo.cdrom.com> from Mike Smith at "Mar 13, 98 09:05:34 pm" To: mike@smith.net.au (Mike Smith) Date: Sat, 14 Mar 1998 16:30:36 +1100 (EST) Cc: jb@cimlogic.com.au, 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 Mike Smith wrote: > IMHO that's a pretty strong selection criteria for what to include from > binutils; if there's a canned gas config for a target, then the files > that target requires should be included. You're probably right. FWIW, adding m68knetbsd support to both libbfd and libopcodes on i386 and alpha enables them both to disassemble a NetBSD/mvme68k object (e.g. crt0.o). I compared the output to see if there were differences, expecting the outputs to be identical. No such luck. The alpha generously reports all hex addresses in 64-bits. 8-) diff m68kcrt0.out1 m68kcrt0.out2 6c6 < 00000000 : --- > 0000000000000000 : 9c9 < 8: 41f7 0c08 lea %sp@(00000008,%d0:l:4),%a0 --- > 8: 41f7 0c08 lea %sp@(0000000000000008,%d0:l:4),%a0 23c23 < 32: 2031 3939 372f movel %a1@(372f3130,%d3:l)@(00000000),%d0 --- > 32: 2031 3939 372f movel %a1@(00000000372f3130,%d3:l)@(0000000000000000),%d0 So that gives me a tool for use with NetBSD that I don't get from NetBSD! And since my mvme68k system has very little disk space, it NFS mounts it's src and obj from a FreeBSD system, having a FreeBSD tool is quite convenient. And from FreeBSD/Alpha, the objdump built there can disassemble /cimaxp/usr/ccs/lib/cmplrs/cc/crt0.o which is an OSF/1 (ecoff) object. -- 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 Mar 13 21:37:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14606 for freebsd-current-outgoing; Fri, 13 Mar 1998 21:37:19 -0800 (PST) (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 VAA14599 for ; Fri, 13 Mar 1998 21:37:14 -0800 (PST) (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 QAA06461; Sat, 14 Mar 1998 16:37:11 +1100 (EST) Message-ID: <19980314163711.02597@rf900.physics.usyd.edu.au> Date: Sat, 14 Mar 1998 16:37:11 +1100 From: David Dawes To: current@FreeBSD.ORG Subject: Building XF86Setup (Was Re: silo overflows (Was Re: 3.0-RELEASE?)) References: <350527AA.3139AD63@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Simon Shapiro on Tue, Mar 10, 1998 at 09:30:45AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 10, 1998 at 09:30:45AM -0800, Simon Shapiro wrote: >I built XF86--3.3.2, XFSetup does not link, has lots of tk/tcl undefined >stuff. When it is installed, it does funny things with interrupts; mouse >events seem to be generated out of thin air. The "ports" Tk and/or Tcl static libraries are broken again. I always end up needing to build my own static libs when building the XFree86 binary dists. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 21:38:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15001 for freebsd-current-outgoing; Fri, 13 Mar 1998 21:38:04 -0800 (PST) (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 VAA14985 for ; Fri, 13 Mar 1998 21:38:00 -0800 (PST) (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 FAA21918; Sat, 14 Mar 1998 05:37:10 GMT Date: Sat, 14 Mar 1998 14:37:10 +0900 (JST) From: Michael Hancock To: Tor Egge cc: freebsd-current@FreeBSD.ORG Subject: Re: 4 WILLRELE's to bite the dust In-Reply-To: <199803131845.TAA26656@pat.idi.ntnu.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Mar 1998, Tor Egge wrote: > I've been using nullfs since Nov 7 1997 without any serious problems > after having fixed some of the above mentioned problems in my local > source tree. The code is not perfect, panics are still possible due > to heuristics (due to VOP_ISLOCKED()) being wrong, but I've yet > not experienced any problems. What would you need to do to fix VOP_ISLOCKED()? Does it really make sense to have an VOP_ISLOCKED()? This ownership issue looks like a big can of worms. Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 21:44:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15968 for freebsd-current-outgoing; Fri, 13 Mar 1998 21:44:18 -0800 (PST) (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 VAA15861 for ; Fri, 13 Mar 1998 21:43:55 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 23112 invoked by uid 1000); 14 Mar 1998 05:49:48 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [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: <19980314163711.02597@rf900.physics.usyd.edu.au> Date: Fri, 13 Mar 1998 21:49:47 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: David Dawes Subject: RE: Building XF86Setup (Was Re: silo overflows (Was Re: 3.0-RELE Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Mar-98 David Dawes wrote: > On Tue, Mar 10, 1998 at 09:30:45AM -0800, Simon Shapiro wrote: > >>I built XF86--3.3.2, XFSetup does not link, has lots of tk/tcl undefined >>stuff. When it is installed, it does funny things with interrupts; >>mouse >>events seem to be generated out of thin air. > > The "ports" Tk and/or Tcl static libraries are broken again. I always > end up needing to build my own static libs when building the XFree86 > binary dists. That's good to know. How do I do that? Pick up the distfiles from ucb, and build in a private area? ---------- 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 Fri Mar 13 22:07:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18461 for freebsd-current-outgoing; Fri, 13 Mar 1998 22:07:21 -0800 (PST) (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 WAA18455 for ; Fri, 13 Mar 1998 22:07:16 -0800 (PST) (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 RAA06541; Sat, 14 Mar 1998 17:07:00 +1100 (EST) Message-ID: <19980314170659.11950@rf900.physics.usyd.edu.au> Date: Sat, 14 Mar 1998 17:06:59 +1100 From: David Dawes To: shimon@simon-shapiro.org Cc: current@FreeBSD.ORG Subject: Re: Building XF86Setup (Was Re: silo overflows (Was Re: 3.0-RELE References: <19980314163711.02597@rf900.physics.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Simon Shapiro on Fri, Mar 13, 1998 at 09:49:47PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 13, 1998 at 09:49:47PM -0800, Simon Shapiro wrote: > >On 14-Mar-98 David Dawes wrote: >> On Tue, Mar 10, 1998 at 09:30:45AM -0800, Simon Shapiro wrote: >> >>>I built XF86--3.3.2, XFSetup does not link, has lots of tk/tcl undefined >>>stuff. When it is installed, it does funny things with interrupts; >>>mouse >>>events seem to be generated out of thin air. >> >> The "ports" Tk and/or Tcl static libraries are broken again. I always >> end up needing to build my own static libs when building the XFree86 >> binary dists. > >That's good to know. How do I do that? Pick up the distfiles from ucb, and >build in a private area? That's more or less what I do. I usually use tcl 7.6 and tk 4.2, and do a "standard" build (no shared libs). An alternative is to edit your xc/config/cf/host.def file to say you're using shared tcl/tk libs instead of static (see the xf86site.def file in the same directory for an example of what to do). BTW, are you seeing some different undefined symbols, or just one (panic) like someone else reported? David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 22:12:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18982 for freebsd-current-outgoing; Fri, 13 Mar 1998 22:12:41 -0800 (PST) (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 WAA18976 for ; Fri, 13 Mar 1998 22:12:37 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 755 invoked by uid 1000); 14 Mar 1998 06:19:05 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [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: <19980314170659.11950@rf900.physics.usyd.edu.au> Date: Fri, 13 Mar 1998 22:19:05 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: David Dawes Subject: Re: Building XF86Setup (Was Re: silo overflows (Was Re: 3.0-RELE Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Mar-98 David Dawes wrote: > On Fri, Mar 13, 1998 at 09:49:47PM -0800, Simon Shapiro wrote: >> >>On 14-Mar-98 David Dawes wrote: >>> On Tue, Mar 10, 1998 at 09:30:45AM -0800, Simon Shapiro wrote: >>> >>>>I built XF86--3.3.2, XFSetup does not link, has lots of tk/tcl >>>>undefined >>>>stuff. When it is installed, it does funny things with interrupts; >>>>mouse >>>>events seem to be generated out of thin air. >>> >>> The "ports" Tk and/or Tcl static libraries are broken again. I always >>> end up needing to build my own static libs when building the XFree86 >>> binary dists. >> >>That's good to know. How do I do that? Pick up the distfiles from ucb, >>and >>build in a private area? > > That's more or less what I do. I usually use tcl 7.6 and tk 4.2, and do > a "standard" build (no shared libs). An alternative is to edit > your xc/config/cf/host.def file to say you're using shared tcl/tk libs > instead of static (see the xf86site.def file in the same directory for > an example of what to do). > > BTW, are you seeing some different undefined symbols, or just one (panic) > like someone else reported? > > David Many references to panic, but others too. i just had ``make buildworld'' fail on a number of tcl/tk symbols too. If you try to build tk tools, they make you remove all traces of all versions of these. Then other things break. I never understood any of this. Seems like there is no cross version compatability, like tkman will run with wish 8.0, but not wish 8.1, I do not know what build wish 8.0 (with some custom features, of course). I tried to build/install tcl80 and tk80 but that does not impress anyone. ---------- 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 Fri Mar 13 22:53:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22378 for freebsd-current-outgoing; Fri, 13 Mar 1998 22:53:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from murkwood.gaffaneys.com (dialup8.gaffaneys.com [208.155.161.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22370 for ; Fri, 13 Mar 1998 22:52:56 -0800 (PST) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by murkwood.gaffaneys.com (8.8.8/8.8.8) id AAA22968; Sat, 14 Mar 1998 00:53:55 -0600 (CST) (envelope-from zach) Message-ID: <19980314005355.14435@gaffaneys.com> Date: Sat, 14 Mar 1998 00:53:55 -0600 From: Zach Heilig To: current@FreeBSD.ORG Subject: /usr/obj entries not made for these source directories: 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 The objects for these directories appear in the source directory: /usr/src/gnu/usr.bin/ld/rtld /usr/src/lib/libcrypt /usr/src/usr.bin/make And, for some reason, ld.so is not made either (so make installworld fails). This was with a 'make -j4 buildworld' on source checked out today (march 13). -- Zach Heilig -- zach@gaffaneys.com Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 23:08:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24242 for freebsd-current-outgoing; Fri, 13 Mar 1998 23:08:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA24237 for ; Fri, 13 Mar 1998 23:08:55 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0yDl3m-0000e0-00; Sat, 14 Mar 1998 00:08:46 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id AAA11125; Sat, 14 Mar 1998 00:08:32 -0700 (MST) Message-Id: <199803140708.AAA11125@harmony.village.org> To: John Birrell Subject: Re: binutils bloat Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sat, 14 Mar 1998 14:11:49 +1100." <199803140311.OAA16205@cimlogic.com.au> References: <199803140311.OAA16205@cimlogic.com.au> Date: Sat, 14 Mar 1998 00:08:32 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199803140311.OAA16205@cimlogic.com.au> John Birrell writes: : Are people going to object if we keep _all_ the binutils source in : src/contrib/binutils so that we can define a few things in /etc/make.conf : and get cross tools out of a `make world'? I'm all for it. That's one of the features of NetBSD and OpenBSD that I miss... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 13 23:13:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24926 for freebsd-current-outgoing; Fri, 13 Mar 1998 23:13:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA24918 for ; Fri, 13 Mar 1998 23:12:59 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0yDl7e-0000e7-00; Sat, 14 Mar 1998 00:12:46 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id AAA11146; Sat, 14 Mar 1998 00:12:32 -0700 (MST) Message-Id: <199803140712.AAA11146@harmony.village.org> To: John Birrell Subject: Re: binutils bloat Cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG In-reply-to: Your message of "Sat, 14 Mar 1998 16:30:36 +1100." <199803140530.QAA16560@cimlogic.com.au> References: <199803140530.QAA16560@cimlogic.com.au> Date: Sat, 14 Mar 1998 00:12:32 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199803140530.QAA16560@cimlogic.com.au> John Birrell writes: : FWIW, adding m68knetbsd support to both libbfd and libopcodes on i386 : and alpha enables them both to disassemble a NetBSD/mvme68k object I'd be willing to champion the MIPS stuff if each platform needs a champion. My MIPS box is kinda slow and I'd love to be able to cross build for it easily.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 00:21:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02037 for freebsd-current-outgoing; Sat, 14 Mar 1998 00:21:30 -0800 (PST) (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 AAA02032 for ; Sat, 14 Mar 1998 00:21:27 -0800 (PST) (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 IAA22387 for ; Sat, 14 Mar 1998 08:20:38 GMT Date: Sat, 14 Mar 1998 17:20:37 +0900 (JST) From: Michael Hancock To: freebsd-current@FreeBSD.ORG Subject: vop_whiteout - WILLRELE freebie 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 Wee! Found a freebie. The vop_whiteout was marked WILLRELE but isn't. It didn't look like any vrele's were missing at the top either. No bypass anyway so it didn't matter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 00:57:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05728 for freebsd-current-outgoing; Sat, 14 Mar 1998 00:57:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05678 for ; Sat, 14 Mar 1998 00:56:27 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA27521; Sat, 14 Mar 1998 19:52:00 +1100 Date: Sat, 14 Mar 1998 19:52:00 +1100 From: Bruce Evans Message-Id: <199803140852.TAA27521@godzilla.zeta.org.au> To: current@FreeBSD.ORG, zach@gaffaneys.com Subject: Re: /usr/obj entries not made for these source directories: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The objects for these directories appear in the source directory: > >/usr/src/gnu/usr.bin/ld/rtld >/usr/src/lib/libcrypt >/usr/src/usr.bin/make NOCLEANDIR=true in /etc/make.conf should fix at least the first problem (`make -B cleandir obj' doesn't work with all options, -DNOPIC in this case, because `make cleandir' removes everything but `make obj' only re-creates the directories for the current options). >And, for some reason, ld.so is not made either (so make installworld fails). ld.so is rtld. Perhaps the normal rtld object directory was created after rtld was built in the wrong place, leaving nothing to install from the right place. Why doesn't the old rtld work? Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 01:13:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07578 for freebsd-current-outgoing; Sat, 14 Mar 1998 01:13:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA07572; Sat, 14 Mar 1998 01:13:52 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id CAA23921; Sat, 14 Mar 1998 02:13:49 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd023896; Sat Mar 14 02:13:39 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id CAA18517; Sat, 14 Mar 1998 02:13:36 -0700 (MST) From: Terry Lambert Message-Id: <199803140913.CAA18517@usr08.primenet.com> Subject: Re: A question about sys/sys/queue.h To: jmb@FreeBSD.ORG (Jonathan M. Bresler) Date: Sat, 14 Mar 1998 09:13:36 +0000 (GMT) Cc: shimon@simon-shapiro.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199803130339.TAA10294@hub.freebsd.org> from "Jonathan M. Bresler" at Mar 12, 98 07:39:39 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 > > #define FOO do { ... } while(0) > > > > I thought these are the same... > > > > the difference lies in how you use them. > in the first case one writes "FOO" > in the second "FOO;" > ^ > make a macro act more like a statement. > > imagine the code around the macro > rather then the macro itself. > > first saw this in _C_traps_and_pitfalls_ > by andrew koenig (sp?) One problem with this approach is register optimization triggered by loop_start/loop_stop marking for possible unrolling by the optimizer. For example, if you reference a variable which is volaatile (but not marked volatile) outside a loop, or using an if/goto to implement the loop instead of a loop construct, you won't get the register optimization. This will potentially case (admittedly "incorrect" according to ANSI) code that was working to now break. I had this problem one time; it was bugger-all to track down (before you ask, no, it was not my incorrect non-marking of the variable; I was maintaining ssomeone else's code). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 01:22:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08539 for freebsd-current-outgoing; Sat, 14 Mar 1998 01:22:19 -0800 (PST) (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 BAA08534; Sat, 14 Mar 1998 01:22:08 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id EAA07880; Sat, 14 Mar 1998 04:22:08 -0500 (EST) (envelope-from toor) Message-Id: <199803140922.EAA07880@dyson.iquest.net> Subject: Re: My machine is back alive!!! :-) In-Reply-To: <199803131901.LAA11818@rah.star-gate.com> from Amancio Hasty at "Mar 13, 98 11:01:59 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sat, 14 Mar 1998 04:22:08 -0500 (EST) Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Amancio Hasty said: > > Don't forget about Soft-updates and the vm related panics. > The VM panics of course, soft-updates will be coming along a little later. I am not good at doing multiple things at a time. (I want to work on soft-updates, but the VM stuff is much more important to a wider group.) -- 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 Mar 14 01:22:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08707 for freebsd-current-outgoing; Sat, 14 Mar 1998 01:22:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bubba.NMSU.Edu (bubba.NMSU.Edu [128.123.3.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08690 for ; Sat, 14 Mar 1998 01:22:42 -0800 (PST) (envelope-from ian@NMSU.Edu) Received: from NMSU.Edu by bubba.NMSU.Edu (8.8.7/NMSU) id CAA05463; Sat, 14 Mar 1998 02:22:04 -0700 (MST) Received: from wilma by NMSU.Edu (8.8.8/NMSU-1.18) id CAA27497; Sat, 14 Mar 1998 02:23:08 -0700 (MST) Date: Sat, 14 Mar 1998 02:23:08 -0700 (MST) From: Ian Logan Message-Id: <199803140923.CAA27497@NMSU.Edu> Received: by wilma (8.8.8/NMSU) id CAA15885; Sat, 14 Mar 1998 02:21:52 -0700 (MST) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Warner Losh , John Birrell Subject: Re: binutils bloat Cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199803140530.QAA16560@cimlogic.com.au> John Birrell writes: > : FWIW, adding m68knetbsd support to both libbfd and libopcodes on i386 > : and alpha enables them both to disassemble a NetBSD/mvme68k object > > I'd be willing to champion the MIPS stuff if each platform needs a > champion. My MIPS box is kinda slow and I'd love to be able to cross > build for it easily.... > > Warner Sounds like a great idea to me. If platforms need champions I'll be more than willing to do whatever is needed for SPARC. Ian Ian Logan Computing & Networking New Mexico State University Email: ian@nmsu.edu Phone: 505-646-6034 Fax: 505-646-5278 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 01:53:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11545 for freebsd-current-outgoing; Sat, 14 Mar 1998 01:53:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11539 for ; Sat, 14 Mar 1998 01:53:33 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id CAA18199; Sat, 14 Mar 1998 02:53:33 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd018182; Sat Mar 14 02:53:31 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id CAA19801; Sat, 14 Mar 1998 02:53:27 -0700 (MST) From: Terry Lambert Message-Id: <199803140953.CAA19801@usr08.primenet.com> Subject: Re: 4 WILLRELE's to bite the dust To: michaelh@cet.co.jp (Michael Hancock) Date: Sat, 14 Mar 1998 09:53:27 +0000 (GMT) Cc: Tor.Egge@idi.ntnu.no, freebsd-current@FreeBSD.ORG In-Reply-To: from "Michael Hancock" at Mar 14, 98 02:37:10 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've been using nullfs since Nov 7 1997 without any serious problems > > after having fixed some of the above mentioned problems in my local > > source tree. The code is not perfect, panics are still possible due > > to heuristics (due to VOP_ISLOCKED()) being wrong, but I've yet > > not experienced any problems. > > What would you need to do to fix VOP_ISLOCKED()? Does it really make > sense to have an VOP_ISLOCKED()? This ownership issue looks like a big > can of worms. Proxy the lock down with VOP_FINALVP. Alternately, put the locking in common upper level code, and assume it will be honored in the downpath, and move to veto-based VOP_LOCK. I prefer the veto method, because it buys you some nice wins in the fan-out/fan-in cases that would be difficult and costly to do otherwise. The vn_lock would assert the lock on the vp, and call the underlying VOP_LOCK on the vp, and if it was veto'ed, back it out. The coherency would be maintained by the stacking layer proxying the lock to the covered vnode (the downcall is needed in NULLFS only because it exposes the underlying FS multiple times in the namespace, so you must explicitly maintain choherency; things like union FS don't expose, so you could be sure that the underlying vp was locked, in effect, by the upper level vp being locked). The problem with the nullfs/nullfs mount (which *should* be permitted to work, since a -> nullfs -> nullfs -> otherfs stack is a perfectly reasonable thing to want to do so you can *avoid* exposing the stacked upon FS) is that the real VOP_LOCK occurs twice on the same vp because it's a real operation, not a proxy operation. There are other coherency problems having to do with the backing vp's associated VM object. John's recent changes allow aliases to work, so in theory, a finalvp is not necessary; the problem here is what gets marked dirty, however, so I have a hard time trusting anything that does aliases, even if John's code appeared to "do the right thing". My soloution would be to proxy the call to VOP_{GET|PUT}PAGES to the real underlying VP, via the bypass mechanism, and disallow aliases entirely. You could do the same thing with a VOP_FINALVP (which is useful for things other than locking, and not necessary in the veto implementation for locks; the advisory locks want to get hung off the object with the pages, and the vp's want to get locks if they get exposed anywhere in the namespace, but probably not otherwise (except in the allocation case, where they should be locked until they are pointed to by the covering layer, and the covering layer's vp should be locked, after which the covered layer can be unlocked (because it's ref'ed). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 02:09:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13676 for freebsd-current-outgoing; Sat, 14 Mar 1998 02:09:25 -0800 (PST) (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 CAA13640 for ; Sat, 14 Mar 1998 02:09:17 -0800 (PST) (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 CAA07633; Sat, 14 Mar 1998 02:08:01 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Studded cc: Matthew Thyer , FreeBSD CURRENT Subject: Re: trouble booting In-reply-to: Your message of "Fri, 13 Mar 1998 17:12:06 PST." <3509D966.DAE44397@dal.net> Date: Sat, 14 Mar 1998 02:08:01 -0800 Message-ID: <7629.889870081@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm curious about this. This isn't a dig, although my incredulity might > make it seem so. Every piece of documentation I've seen says to do it > the other way around. Make world first, then build kernel, then boot. This is correct. If you've just done major things to the build tools, or even if you've merely changed config(8) in a way that will blow out a new kernel (and this happens fairly often, actually) the make world will fix this for you before you move on to building the kernel. Also, building just the kernel and then rebooting from it (otherwise, what would be the point of building it first?) can truly hang you if your LKMs are out of date. Building the kernel first is therefore NOT recommended practice. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 02:14:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14474 for freebsd-current-outgoing; Sat, 14 Mar 1998 02:14:46 -0800 (PST) (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 CAA14462 for ; Sat, 14 Mar 1998 02:14:43 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id LAA00426; Sat, 14 Mar 1998 11:13:57 +0100 (MET) (envelope-from sos) Message-Id: <199803141013.LAA00426@sos.freebsd.dk> Subject: Re: binutils bloat In-Reply-To: <199803140923.CAA27497@NMSU.Edu> from Ian Logan at "Mar 14, 98 02:23:08 am" To: ian@NMSU.Edu (Ian Logan) Date: Sat, 14 Mar 1998 11:13:46 +0100 (MET) Cc: imp@village.org, jb@cimlogic.com.au, mike@smith.net.au, 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 Ian Logan who wrote: > > In message <199803140530.QAA16560@cimlogic.com.au> John Birrell writes: > > : FWIW, adding m68knetbsd support to both libbfd and libopcodes on i386 > > : and alpha enables them both to disassemble a NetBSD/mvme68k object > > > > I'd be willing to champion the MIPS stuff if each platform needs a > > champion. My MIPS box is kinda slow and I'd love to be able to cross > > build for it easily.... > > > > Warner > Sounds like a great idea to me. If platforms need champions > I'll be more than willing to do whatever is needed for SPARC. > Ian Erhm, we've just found new problems with the binutils ability to cope with a.out. We will have to install all the utils in /usr/libexec/elf fornow, and have the original aout in /usr/libexec/aout. /usr/bin/objformat will then decide which one to call. This means that until we go completely ELF, you will not have default access to the tools from binutils. I suggest (strongly) that the other architectures (well alpha) stick to the same directory structure that the i386 version does, everything else will just make a mess of makefiles etc. Having /usr/libexec/aout empty becuase its not supported is no excuse for not following the std layout. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Sat Mar 14 02:25:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15746 for freebsd-current-outgoing; Sat, 14 Mar 1998 02:25:47 -0800 (PST) (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 CAA15741 for ; Sat, 14 Mar 1998 02:25:45 -0800 (PST) (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 CAA07790; Sat, 14 Mar 1998 02:24:21 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: John Birrell cc: current@FreeBSD.ORG Subject: Re: binutils bloat In-reply-to: Your message of "Sat, 14 Mar 1998 14:11:49 +1100." <199803140311.OAA16205@cimlogic.com.au> Date: Sat, 14 Mar 1998 02:24:21 -0800 Message-ID: <7786.889871061@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are people going to object if we keep _all_ the binutils source in > src/contrib/binutils so that we can define a few things in /etc/make.conf > and get cross tools out of a `make world'? I think many would object if it were otherwise. :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 02:30:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16258 for freebsd-current-outgoing; Sat, 14 Mar 1998 02:30:53 -0800 (PST) (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 CAA16253 for ; Sat, 14 Mar 1998 02:30:50 -0800 (PST) (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 CAA07818; Sat, 14 Mar 1998 02:29:17 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: John Birrell cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG Subject: Re: binutils bloat In-reply-to: Your message of "Sat, 14 Mar 1998 14:53:34 +1100." <199803140353.OAA16327@cimlogic.com.au> Date: Sat, 14 Mar 1998 02:29:17 -0800 Message-ID: <7814.889871357@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After saying that, it's probably not winable. 8-( Oh, I dunno about that... You might find yourself with some powerful backers on this proposal - the technical elegance of being able to say "I'd like executables for platform foo please", especially with FreeBSD planning to go both Alpha and Sparc in the hopefully not-too-distant future, is still compelling and disk drive prices are still falling. :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 02:32:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16689 for freebsd-current-outgoing; Sat, 14 Mar 1998 02:32:35 -0800 (PST) (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 CAA16683 for ; Sat, 14 Mar 1998 02:32:34 -0800 (PST) (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 CAA07845; Sat, 14 Mar 1998 02:31:09 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: John Birrell cc: thyerm@camtech.net.au (Matthew Thyer), Studded@dal.net, current@FreeBSD.ORG Subject: Re: trouble booting In-reply-to: Your message of "Sat, 14 Mar 1998 15:17:41 +1100." <199803140417.PAA16394@cimlogic.com.au> Date: Sat, 14 Mar 1998 02:31:09 -0800 Message-ID: <7842.889871469@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > you called stat(). In this case, you had to build and boot a new kernel > before building libc. The old programs continued to work with the new Woog. Needless to say, we've really really tried to avoid situations like that for exactly this reason. :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 02:46:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17561 for freebsd-current-outgoing; Sat, 14 Mar 1998 02:46:33 -0800 (PST) (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 CAA17520; Sat, 14 Mar 1998 02:45:27 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id VAA18108; Sat, 14 Mar 1998 21:47:07 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803141047.VAA18108@cimlogic.com.au> Subject: Re: binutils bloat In-Reply-To: <199803141013.LAA00426@sos.freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Mar 14, 98 11:13:46 am" To: sos@FreeBSD.ORG Date: Sat, 14 Mar 1998 21:47:07 +1100 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (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 Søren Schmidt wrote: > Erhm, we've just found new problems with the binutils ability to > cope with a.out. We will have to install all the utils in > /usr/libexec/elf fornow, and have the original aout in /usr/libexec/aout. > /usr/bin/objformat will then decide which one to call. > This means that until we go completely ELF, you will not have default > access to the tools from binutils. > I suggest (strongly) that the other architectures (well alpha) stick > to the same directory structure that the i386 version does, everything > else will just make a mess of makefiles etc. Having /usr/libexec/aout > empty becuase its not supported is no excuse for not following the > std layout. The build directory structure has nothing to do with where the binaries are installed. I'll send you (and jdp and peter) details of an alternative makefile design that treats the architecture specific makefiles as additive rather than exclusive [Sorry to sound like Terry 8-) ] so that more than one architecture is built. Apart from gas which is a special case, the other binutils can be built on the host architecture with additional architecture support by adding something like this (example for i386 and m68k on alpha) in /etc/make.conf: --- # Architectures for which cross tools are required: CROSS_TOOLS= i386 m68k --- After the make world, I get one each of: addr2line ar ld nm objcopy objdump ranlib size string strip to run on the (alpha) host plus an `as' for the host, and an as_${arch} for each additional architecture specified in CROSS_TOOLS. The makefiles aren't that bad - just different. And I'm not talking about aout support that is covered by usr.bin/ar, usr.bin/ranlib, etc. Those tools can stay as they are. Nothing lost, nothing gained. 8-) Also bear in mind that the only tools you are installing in /usr/libexec/elf are ar, as, ld and ranlib. The other tools are being installed in /usr/bin. -- 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 Sat Mar 14 02:48:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA18026 for freebsd-current-outgoing; Sat, 14 Mar 1998 02:48:45 -0800 (PST) (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 CAA18021 for ; Sat, 14 Mar 1998 02:48:42 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id VAA18125; Sat, 14 Mar 1998 21:50:12 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199803141050.VAA18125@cimlogic.com.au> Subject: Re: binutils bloat In-Reply-To: <7814.889871357@time.cdrom.com> from "Jordan K. Hubbard" at "Mar 14, 98 02:29:17 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 14 Mar 1998 21:50:12 +1100 (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: > Oh, I dunno about that... You might find yourself with some powerful > backers on this proposal - the technical elegance of being able to say > "I'd like executables for platform foo please", especially with > FreeBSD planning to go both Alpha and Sparc in the hopefully > not-too-distant future, is still compelling and disk drive prices are > still falling. :) I like the idea of being able to pick up a CD with all the supported tools installed. So if we do this, are you prepared to build all for releases, even though they might not be enabled by default? -- 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 Sat Mar 14 03:13:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20178 for freebsd-current-outgoing; Sat, 14 Mar 1998 03:13:02 -0800 (PST) (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 DAA20155; Sat, 14 Mar 1998 03:12:54 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id MAA00597; Sat, 14 Mar 1998 12:12:45 +0100 (MET) (envelope-from sos) Message-Id: <199803141112.MAA00597@sos.freebsd.dk> Subject: Re: binutils bloat In-Reply-To: <199803141047.VAA18108@cimlogic.com.au> from John Birrell at "Mar 14, 98 09:47:07 pm" To: jb@cimlogic.com.au (John Birrell) Date: Sat, 14 Mar 1998 12:12:45 +0100 (MET) 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 John Birrell who wrote: > > The build directory structure has nothing to do with where the binaries > are installed. I'll send you (and jdp and peter) details of an alternative > makefile design that treats the architecture specific makefiles as > additive rather than exclusive [Sorry to sound like Terry 8-) ] so > that more than one architecture is built. Hmm, lets see that first before I comment on that... > Also bear in mind that the only tools you are installing in > /usr/libexec/elf are ar, as, ld and ranlib. The other tools are > being installed in /usr/bin. NOPE!, the rest of binutils goes there too, John P. has found new problems with binutils "aout unwilllingnes". We cannot use binutils for our aout format. If we are going to have crosstarget development tools, it should be completely optional, preferably a port. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Sat Mar 14 03:20:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21168 for freebsd-current-outgoing; Sat, 14 Mar 1998 03:20:56 -0800 (PST) (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 DAA21086; Sat, 14 Mar 1998 03:19:51 -0800 (PST) (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 DAA04346; Sat, 14 Mar 1998 03:17:49 -0800 (PST) Message-Id: <199803141117.DAA04346@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: sos@FreeBSD.ORG cc: jb@cimlogic.com.au (John Birrell), current@FreeBSD.ORG Subject: Re: binutils bloat In-reply-to: Your message of "Sat, 14 Mar 1998 12:12:45 +0100." <199803141112.MAA00597@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sat, 14 Mar 1998 03:17:47 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA21087 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If we are going to have crosstarget development tools, it should be > completely optional, preferably a port. Uh, this is cross-for-FreeBSD-on-other-architectures. Making this a port would, to put it succinctly, suck. -- \\ 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 Sat Mar 14 03:34:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA22892 for freebsd-current-outgoing; Sat, 14 Mar 1998 03:34:25 -0800 (PST) (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 DAA22886 for ; Sat, 14 Mar 1998 03:34:17 -0800 (PST) (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 DAA08213; Sat, 14 Mar 1998 03:33:02 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: John Birrell cc: current@FreeBSD.ORG Subject: Re: binutils bloat In-reply-to: Your message of "Sat, 14 Mar 1998 21:50:12 +1100." <199803141050.VAA18125@cimlogic.com.au> Date: Sat, 14 Mar 1998 03:33:02 -0800 Message-ID: <8209.889875182@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I like the idea of being able to pick up a CD with all the supported > tools installed. So if we do this, are you prepared to build all > for releases, even though they might not be enabled by default? I'm not quite sure what you mean by "all" in this context, but I'm certainly willing to talk about 3.0's release bit generation and how things might (within reason) be added to it. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 03:38:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23426 for freebsd-current-outgoing; Sat, 14 Mar 1998 03:38:36 -0800 (PST) (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 DAA23417; Sat, 14 Mar 1998 03:38:26 -0800 (PST) (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 DAA08253; Sat, 14 Mar 1998 03:37:19 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: sos@FreeBSD.ORG cc: jb@cimlogic.com.au (John Birrell), current@FreeBSD.ORG Subject: Re: binutils bloat In-reply-to: Your message of "Sat, 14 Mar 1998 12:12:45 +0100." <199803141112.MAA00597@sos.freebsd.dk> Date: Sat, 14 Mar 1998 03:37:18 -0800 Message-ID: <8250.889875438@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If we are going to have crosstarget development tools, it should be > completely optional, preferably a port. Ports are actually a really nasty solution for anything that might involve building an eventual release, trust me! Just breaking out the SGML stuff for docs was painful enough, and that was exceedingly peripheral. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 03:40:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23962 for freebsd-current-outgoing; Sat, 14 Mar 1998 03:40:46 -0800 (PST) (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 DAA23884; Sat, 14 Mar 1998 03:40:25 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id MAA11404; Sat, 14 Mar 1998 12:40:14 +0100 (MET) (envelope-from sos) Message-Id: <199803141140.MAA11404@sos.freebsd.dk> Subject: Re: binutils bloat In-Reply-To: <199803141117.DAA04346@dingo.cdrom.com> from Mike Smith at "Mar 14, 98 03:17:47 am" To: mike@smith.net.au (Mike Smith) Date: Sat, 14 Mar 1998 12:40:14 +0100 (MET) Cc: sos@FreeBSD.ORG, jb@cimlogic.com.au, 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 Mike Smith who wrote: > > If we are going to have crosstarget development tools, it should be > > completely optional, preferably a port. > > Uh, this is cross-for-FreeBSD-on-other-architectures. Making this a > port would, to put it succinctly, suck. Bloating every installation with crosstools will suck even more... Make it an option then, that's OFF by default. And wait until we have the ELF stuff completed, this is not going to make it any easier... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Sat Mar 14 03:42:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24407 for freebsd-current-outgoing; Sat, 14 Mar 1998 03:42:27 -0800 (PST) (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 DAA24314; Sat, 14 Mar 1998 03:42:03 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id MAA16622; Sat, 14 Mar 1998 12:41:48 +0100 (MET) (envelope-from sos) Message-Id: <199803141141.MAA16622@sos.freebsd.dk> Subject: Re: binutils bloat In-Reply-To: <8250.889875438@time.cdrom.com> from "Jordan K. Hubbard" at "Mar 14, 98 03:37:18 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 14 Mar 1998 12:41:48 +0100 (MET) Cc: sos@FreeBSD.ORG, jb@cimlogic.com.au, 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 Jordan K. Hubbard who wrote: > > If we are going to have crosstarget development tools, it should be > > completely optional, preferably a port. > > Ports are actually a really nasty solution for anything that might > involve building an eventual release, trust me! Just breaking out the > SGML stuff for docs was painful enough, and that was exceedingly > peripheral. You mean you would build all the different machine releases on ONE platform ??? That will be quite a task :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Sat Mar 14 03:45:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25332 for freebsd-current-outgoing; Sat, 14 Mar 1998 03:45:27 -0800 (PST) (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 DAA25275; Sat, 14 Mar 1998 03:45:00 -0800 (PST) (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 DAA09212; Sat, 14 Mar 1998 03:43:52 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: sos@FreeBSD.ORG cc: jb@cimlogic.com.au, current@FreeBSD.ORG Subject: Re: binutils bloat In-reply-to: Your message of "Sat, 14 Mar 1998 12:41:48 +0100." <199803141141.MAA16622@sos.freebsd.dk> Date: Sat, 14 Mar 1998 03:43:51 -0800 Message-ID: <9183.889875831@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You mean you would build all the different machine releases on ONE > platform ??? That will be quite a task :) No, I simply meant that I wouldn't want to go have to add a port in order to get my toolchain for _any_ of the platforms I might eventually have to build releases for. :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 04:08:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29460 for freebsd-current-outgoing; Sat, 14 Mar 1998 04:08:47 -0800 (PST) (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 EAA29452; Sat, 14 Mar 1998 04:08:11 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id NAA14058; Sat, 14 Mar 1998 13:07:56 +0100 (MET) (envelope-from sos) Message-Id: <199803141207.NAA14058@sos.freebsd.dk> Subject: Re: binutils bloat In-Reply-To: <9183.889875831@time.cdrom.com> from "Jordan K. Hubbard" at "Mar 14, 98 03:43:51 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 14 Mar 1998 13:07:56 +0100 (MET) Cc: sos@FreeBSD.ORG, jb@cimlogic.com.au, 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 Jordan K. Hubbard who wrote: > > You mean you would build all the different machine releases on ONE > > platform ??? That will be quite a task :) > > No, I simply meant that I wouldn't want to go have to add a port in > order to get my toolchain for _any_ of the platforms I might > eventually have to build releases for. :-) Then I must have misunderstood something. I was under the impression that it was about having CROSS development tools around, of cause you will have your NATIVE tools around. But if you want alpha tools on i386, then I say you have to pkg_add alpha_tools.tgz, or do a special make target to get them... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Sat Mar 14 04:11:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29937 for freebsd-current-outgoing; Sat, 14 Mar 1998 04:11:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29924 for ; Sat, 14 Mar 1998 04:10:47 -0800 (PST) (envelope-from mark@greenpeace.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 OAA12631; Sat, 14 Mar 1998 14:10:41 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id OAA13837; Sat, 14 Mar 1998 14:10:21 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199803141210.OAA13837@greenpeace.grondar.za> X-Mailer: exmh version 2.0.1 12/23/97 To: Mikhail Teterin cc: freebsd-current@FreeBSD.ORG Subject: Re: Kerberos and telnet, su, rsh.... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Mar 1998 14:10:20 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > After I rebuilt the world with Kerberos support, things like > su, telnet, rsh stopped working, unless explicitly given the > ``-K'' option. I do not have Kerberos set up yet, but I remember, > that previosly in this cases I was just getting something "remote > side does not support Kerberos" or "not in root acl". Now the > programs hang for a while, then dump core... > > Clarifications? Thanks! Configure properly for Kerberos, or build without Kerberos. 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 Sat Mar 14 04:16:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA00649 for freebsd-current-outgoing; Sat, 14 Mar 1998 04:16:23 -0800 (PST) (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 EAA00640; Sat, 14 Mar 1998 04:16:18 -0800 (PST) (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 EAA07122; Sat, 14 Mar 1998 04:14:20 -0800 (PST) Message-Id: <199803141214.EAA07122@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: sos@FreeBSD.ORG cc: jkh@time.cdrom.com (Jordan K. Hubbard), jb@cimlogic.com.au, current@FreeBSD.ORG Subject: Re: binutils bloat In-reply-to: Your message of "Sat, 14 Mar 1998 12:41:48 +0100." <199803141141.MAA16622@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sat, 14 Mar 1998 04:14:18 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA00642 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In reply to Jordan K. Hubbard who wrote: > > > If we are going to have crosstarget development tools, it should be > > > completely optional, preferably a port. > > > > Ports are actually a really nasty solution for anything that might > > involve building an eventual release, trust me! Just breaking out the > > SGML stuff for docs was painful enough, and that was exceedingly > > peripheral. > > You mean you would build all the different machine releases on ONE > platform ??? That will be quite a task :) You really do want to put that P6 I just shipped to you to good use. Building releases for everything we have that's releasable is getting pretty boring. By the time we're ready to release for Alpha and Sparc, we're going to *want* a challenge. -- \\ 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 Sat Mar 14 04:21:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01898 for freebsd-current-outgoing; Sat, 14 Mar 1998 04:21:11 -0800 (PST) (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 EAA01886; Sat, 14 Mar 1998 04:21:03 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id NAA15406; Sat, 14 Mar 1998 13:20:48 +0100 (MET) (envelope-from sos) Message-Id: <199803141220.NAA15406@sos.freebsd.dk> Subject: Re: binutils bloat In-Reply-To: <199803141214.EAA07122@dingo.cdrom.com> from Mike Smith at "Mar 14, 98 04:14:18 am" To: mike@smith.net.au (Mike Smith) Date: Sat, 14 Mar 1998 13:20:48 +0100 (MET) Cc: sos@FreeBSD.ORG, jkh@time.cdrom.com, jb@cimlogic.com.au, 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 Mike Smith who wrote: > > In reply to Jordan K. Hubbard who wrote: > > > > If we are going to have crosstarget development tools, it should be > > > > completely optional, preferably a port. > > > > > > Ports are actually a really nasty solution for anything that might > > > involve building an eventual release, trust me! Just breaking out the > > > SGML stuff for docs was painful enough, and that was exceedingly > > > peripheral. > > > > You mean you would build all the different machine releases on ONE > > platform ??? That will be quite a task :) > > You really do want to put that P6 I just shipped to you to good use. > Building releases for everything we have that's releasable is getting > pretty boring. By the time we're ready to release for Alpha and Sparc, > we're going to *want* a challenge. Whoa! Now that's a man with visions !! :) :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Sat Mar 14 04:44:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04247 for freebsd-current-outgoing; Sat, 14 Mar 1998 04:44:10 -0800 (PST) (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 EAA04241 for ; Sat, 14 Mar 1998 04:44:08 -0800 (PST) (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 MAA06124; Sat, 14 Mar 1998 12:44:07 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id NAA13592; Sat, 14 Mar 1998 13:44:03 +0100 (MET) Message-ID: <19980314134403.44728@follo.net> Date: Sat, 14 Mar 1998 13:44:03 +0100 From: Eivind Eklund To: shimon@simon-shapiro.org Cc: freebsd-current@FreeBSD.ORG Subject: Re: A question about sys/sys/queue.h References: <19980313121330.54903@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Simon Shapiro on Fri, Mar 13, 1998 at 09:54:59AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 13, 1998 at 09:54:59AM -0800, Simon Shapiro wrote: > > On 13-Mar-98 Eivind Eklund wrote: > ... > > > For any onlookerss: You can't get the correct binding with if () > > tricks, BTW. Stick with the good old "do { ... } while(0)" > > What you are describing is probably a compiler (or maybe even > language) deficiency. ``do { ... } while (0)'' should be identical to > ``{ ... }'' as they both do logically, the same thing. Again, for onlookers: It's a language 'feature'. Off the top of my head, I can't think of any way of parsing this that would be cleaner. (Any follow-ups to chat, please) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 06:30:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11841 for freebsd-current-outgoing; Sat, 14 Mar 1998 06:30:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11795 for ; Sat, 14 Mar 1998 06:29:56 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id PAA04739 for current@FreeBSD.ORG; Sat, 14 Mar 1998 15:15:07 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.7) id OAA10734; Sat, 14 Mar 1998 14:58:57 +0100 (CET) (envelope-from andreas) Message-ID: <19980314145857.51318@klemm.gtn.com> Date: Sat, 14 Mar 1998 14:58:57 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: Re: binutils bloat References: <199803141112.MAA00597@sos.freebsd.dk> <8250.889875438@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <8250.889875438@time.cdrom.com>; from Jordan K. Hubbard on Sat, Mar 14, 1998 at 03:37:18AM -0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 14, 1998 at 03:37:18AM -0800, Jordan K. Hubbard wrote: > > If we are going to have crosstarget development tools, it should be > > completely optional, preferably a port. > > Ports are actually a really nasty solution for anything that might > involve building an eventual release, trust me! Just breaking out the > SGML stuff for docs was painful enough, and that was exceedingly > peripheral. Yes it's "pain in the ass" (= expensive for me), that the doctools are fetched every time I build a release... -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 07:09:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16562 for freebsd-current-outgoing; Sat, 14 Mar 1998 07:09:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from P2 (p2.isdn.net.il [192.115.104.72]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15898; Sat, 14 Mar 1998 07:05:46 -0800 (PST) (envelope-from qt8-news@connect9.com) From: qt8-news@connect9.com Received: from connect9.com - 194.90.232.47 by isdn.net.il with Microsoft SMTPSVC; Sat, 14 Mar 1998 17:00:08 +0200 To: qt8-news@connect9.com Subject: Hebrew/English wp & HTML generator Message-ID: <009040800150e38P2@isdn.net.il> Date: 14 Mar 1998 17:00:28 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -------------------------------------------------------------------------- Please find REMOVE instructions at the bottom. -------------------------------------------------------------------------- Hebrew/English word processor and HTML generator ========================================================================= QT/8 is an advanced multilingual word processor and HTML generator, operating on any MS Windows PC platform, regardless of the Windows local version. User interface is in both Hebrew and English. QT/8 is specifically targeted for users who devote their time for creating all kind of documents and HTML pages, in various languages, to be printed, faxed or published on the WEB. QT/8 has state-of-the-art tools and solutions for rich text editing, easy HTML authoring and smart document management - using both Hebrew and English interfaces and supports upto 30 languages on the same document during writing, editing and publishing. Hebrew, English, Yidish, Spanish, French, German, Arabic, Russian, Italian, Swedish are few while many more are supported. QT/8 comes with 12 special Hebrew/Yidish fonts. QT/8 offers known word processing features such as: Smart table editing including table calculations, cell split and combine, various row width etc. Enhanced capability for drawing illustrations and flow charts in the document. Edit Columns, Paragraph numbering, Hebrew Nikud, Mail Merge, make Labels. Headers & Footers, Footnotes, Table of Contents, Indexing. QT/8 Faxing module - Send & Receive faxes directly from and to QT/8 - there is no need for an external fax program. You can keep MS Fax together with QT-Fax on the same system. QT/8 advanced Document management - Use Hebrew or English document names to file documents in directories and libraries. Keep thousands of documents in an organized fashion with fast and efficient look-up and retrieve features. Open as many libraries as required. QT/8 HTML generator - Use QT/8 for creating multiple languages - Fully Enriched HTML pages. You design your page on-the-fly without any prior knowledge in HTML syntax. Upload your work to the WEB with our built in-fully supported FTP module. Create colorfull HTML graphical pages for foreign browser support (so people in China can read your Hebrew and other pages too...). QT/8 Editing and Proofing - Enhanced Hebrew/English speller, Hebrew/English English/Hebrew dictionary and Hebrew thesaurus. Spelling is also available for Spanish, French, German, Italian, Swedish, Dutch and Finish. Comes with a wide variety of TrueType fonts - including Biblical fonts ! QT/8 Drawing and Multimedia support - Enrich your HTML pages with Tables manipulation and a range of graphics format support (pcx, gif, jpeg, bmp, wmf). Rich library of Clipart images - included. QT/8 can Import MS-word 6 documents QT/8 can Import and Export RTF and ASCII files You will find QT/8 serving all your publishing needs. You won't need any additional software to write, edit and publish your documents. Minimum System Requirements: Windows 3.1 or 95 or NT in any language version, 486 and up processor, 8MB RAM, 40MB hard disk drive space. VGA or SVGA monitor. ----------------------------------------------------------------------------- For a FREE demo download - mailto:qt8@connect9.com?subject=qt_moreInfo (Please note your reply settings - TO: qt8@connect9.com SUBJECT: qt_moreinfo) To remove your name from this mailing list mailto:qt8-rmv@connect9.com?subject=qt_remove (Please note your reply settings - TO: qt8-rmv@connect9.com SUBJECT: qt_remove) Thank you for your time, Connections Marketing Co. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 07:54:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22137 for freebsd-current-outgoing; Sat, 14 Mar 1998 07:54:09 -0800 (PST) (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 HAA22130 for ; Sat, 14 Mar 1998 07:54:04 -0800 (PST) (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 HAA00868; Sat, 14 Mar 1998 07:52:36 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Andreas Klemm cc: current@FreeBSD.ORG Subject: Re: binutils bloat In-reply-to: Your message of "Sat, 14 Mar 1998 14:58:57 +0100." <19980314145857.51318@klemm.gtn.com> Date: Sat, 14 Mar 1998 07:52:36 -0800 Message-ID: <863.889890756@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes it's "pain in the ass" (= expensive for me), that the doctools > are fetched every time I build a release... Actually, fetch the distfiles once "outside" your release build area and it will copy them in - you don't have to fetch them every single time. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 08:38:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28615 for freebsd-current-outgoing; Sat, 14 Mar 1998 08:38:19 -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 IAA28533; Sat, 14 Mar 1998 08:37:24 -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 TAA21954; Sat, 14 Mar 1998 19:28:11 +0300 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 TAA00972; Sat, 14 Mar 1998 19:23:35 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199803141623.TAA00972@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Bruce Evans cc: mike@smith.net.au, obrien@NUXI.com, current@FreeBSD.ORG, joerg@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: *HEADS UP* Correction to previous postings. In-reply-to: Your message of "Sat, 14 Mar 1998 15:37:00 +1100." <199803140437.PAA19697@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Mar 1998 19:23:35 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > > Sysinstall doesn't seem to provide d.d. mode by default. The default > for "A Use Entire Disk" seems to be to not actually use the entire > disk, but to use real slices and the entire disk except for the MBR > (and other sectors on the first "track"?). > Sysinstall _provide_ "dangerous dedicated" mode, but don't "turn it on" by default. After "A Use Entire Disk" it ask: Do you want to do this with a true partition entry so as to remain cooperative with any future possible operating systems on the drive(s)? (See also the section about ``dangerously dedicated'' disks in the FreeBSD FAQ.) If press Enter, (answer "Yes"), it leaves out the first "track". If answer "No", it will use entire disk (dangerously dedicated), and create correct entry in the partition table. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 08:40:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29448 for freebsd-current-outgoing; Sat, 14 Mar 1998 08:40:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.153.65.3] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29429 for ; Sat, 14 Mar 1998 08:40:26 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id LAA17154; Sat, 14 Mar 1998 11:39:47 -0500 (EST) Date: Sat, 14 Mar 1998 11:39:46 -0500 (EST) From: "Matthew N. Dodd" To: Ian Logan cc: Warner Losh , John Birrell , Mike Smith , current@FreeBSD.ORG Subject: Re: binutils bloat In-Reply-To: <199803140923.CAA27497@NMSU.Edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Mar 1998, Ian Logan wrote: > > In message <199803140530.QAA16560@cimlogic.com.au> John Birrell writes: > > : FWIW, adding m68knetbsd support to both libbfd and libopcodes on i386 > > : and alpha enables them both to disassemble a NetBSD/mvme68k object > > > > I'd be willing to champion the MIPS stuff if each platform needs a > > champion. My MIPS box is kinda slow and I'd love to be able to cross > > build for it easily.... > Sounds like a great idea to me. If platforms need champions > I'll be more than willing to do whatever is needed for SPARC. As slow as the old VAXen are I'd think the people that use them would appriciate a crosscompiling enviornment; I know I would. (And the PMAX boxes too) I don't see a reason that it has to ship out of the box with that ability though... /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 09:41:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08013 for freebsd-current-outgoing; Sat, 14 Mar 1998 09:41:11 -0800 (PST) (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 JAA07999 for ; Sat, 14 Mar 1998 09:40:59 -0800 (PST) (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 MAA07249 for ; Sat, 14 Mar 1998 12:40:26 -0500 (EST) X-Sender: ckempfm@enigami.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 14 Mar 1998 12:36:36 -0500 To: freebsd-current@FreeBSD.ORG From: Cory Kempf Subject: Today's kernel doesn't work on (my) DK440LX Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I had a (mostly) working kernel based on 10 March sources. Today, 'round 2 PM EST, I sup'd again, and built the world. I can no longer build a (mostly) working kernel. My system seems to be dependent on the line: config kernel root on da0 swap on generic In my kernel config file. Especially the 'swap on generic' part. If I take it out, or replace it with anything I have tried so far, my kernel doesn't work at all. If I attempt to boot, the system attempts to change root to wd0s2b, and I get a Fatal Trap 12. Doing a trace says that it is happening in _ffs_mount(). In my (mostly) working kernel, I can succussfully boot only when I type '0:sd(0,a)/kernel -a' at the boot prompt. Anything else, and I get the same fatal trap 12 in _ffs_mount(). I suspect this may be related, which is why I bring it up. Unfortunately, today's sources don't seem to allow the 'swap on generic' anymore. Perhaps I am looking in the wrong places, but I can't seem to find any documentation as to what "swap on generic" means and what I should replace it with. help? Suggestions? Thanks, +C My hardware: DK440LX m'board, 333 MHz PII, 128 MB RAM, Seagate Cheetah 9 GB UW SCSI drive (bus A ID 0 LUN 0), Toshiba 32X CD ROM drive (bus B ID 1 LUN 0), No Nine I-128 series 2 video board. My config file: (this doesn't work... I have been trying to figure out why, and how to fix, but the swap on generic seems to be the problem). # # DM # machine "i386" #cpu "I586_CPU" cpu "I686_CPU" ident CORY_II maxusers 32 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem #options MFS options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options KTRACE #kernel tracing options SYSVSHM options DDB options "AHC_ALLOW_MEMIO" # # The following line generates an error at config(8) time... # #options "PQ_MEDIUMCACHE" options CONSPEED=115200 #default speed for serial console options USERCONFIG options VISUAL_USERCONFIG # # swap on generic isn't in LINT. Without it, or with swap on da0, # it builds, but doesn't work. # config kernel root on da0s1a swap on da0 #swap on generic controller isa0 controller pci0 controller pnp0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller ahc0 controller scbus0 at ahc0 bus 0 controller scbus1 at ahc0 bus 1 #device sa0 #tape device pass0 device da0 at scbus0 target 0 #device cd0 at scbus1 target 1 # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Mandatory, don't remove device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr #device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr #device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr #device lpt0 at isa? port? tty irq 7 vector lptintr device fxp0 #ether pseudo-device loop pseudo-device ether pseudo-device pty 16 #pseudo-device bpfilter 4 #pseudo-device tun 2 # keep this if you want to be able to continue to use /stand/sysinstall pseudo-device gzip # Exec gzipped a.out's #CORY: controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr options INCLUDE_CONFIG_FILE options "MD5" options "VM86" options NETATALK options MSDOSFS options FFS_ROOT pseudo-device speaker -- 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 Sat Mar 14 10:06:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13011 for freebsd-current-outgoing; Sat, 14 Mar 1998 10:06:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shaw.fidalgo.net (root@shaw.fidalgo.net [206.129.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13003 for ; Sat, 14 Mar 1998 10:06:13 -0800 (PST) (envelope-from jason@godsey.net) Received: from orbit (godsey.fidalgo.net [206.129.156.164]) by shaw.fidalgo.net (8.8.8/8.8) with SMTP id KAA19761 for ; Sat, 14 Mar 1998 10:06:07 -0800 (PST) Message-ID: <002b01bd4f73$c6d31ec0$a49c81ce@orbit> From: "Jason Godsey" To: Subject: ports. Date: Sat, 14 Mar 1998 10:05:22 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0025_01BD4F30.B38B0960" 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 This is a multi-part message in MIME format. ------=_NextPart_000_0025_01BD4F30.B38B0960 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable After make world last night, ports stoped working. They were wanting me to remove files from /usr/local/lib. I copied old /usr/share/mk/* files back and ports work again. Is this something I'm doing wrong? ------=_NextPart_000_0025_01BD4F30.B38B0960 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
After make world last = night, ports=20 stoped working.
 
They were wanting me to = remove files=20 from /usr/local/lib.
 
I copied old = /usr/share/mk/* files=20 back and ports work again.
 
Is this something I'm = doing=20 wrong?
------=_NextPart_000_0025_01BD4F30.B38B0960-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 12:08:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27039 for freebsd-current-outgoing; Sat, 14 Mar 1998 12:08:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shire.domestic.de (kuebart.stuttgart.netsurf.de [194.233.216.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27005 for ; Sat, 14 Mar 1998 12:07:58 -0800 (PST) (envelope-from joki@kuebart.stuttgart.netsurf.de) Received: from yacht.domestic.de (yacht.domestic.de [192.168.1.4]) by shire.domestic.de (8.8.8/8.8.7) with ESMTP id VAA16808 for ; Sat, 14 Mar 1998 21:06:10 +0100 (CET) (envelope-from joki@shire.domestic.de) From: Joachim Kuebart Received: (from joki@localhost) by yacht.domestic.de (8.8.8/8.8.7) id VAA01248 for current@freebsd.org; Sat, 14 Mar 1998 21:09:56 +0100 (CET) (envelope-from joki@shire.domestic.de) Message-Id: <199803142009.VAA01248@yacht.domestic.de> Subject: Joliet FS Support in CD9660 To: current@FreeBSD.ORG Date: Sat, 14 Mar 1998 21:09:56 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM889906196-1194-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM889906196-1194-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, attached is a patch to support Joliet extensions to CD9660. The file cd9660_joliet.c is also needed in /sys/isofs/cd9660. The patch applies to the source as of March 6. I do not have time to update now and just hope not too much has changed. It does NOT YET run with rrip extensions, since I do not know how these are to be intermixed. I am also not sure about High Sierra (if this can be intermixed at all). Note that you need to add the file cd9660_joliet.c and the line isofs/cd9660/cd9660_joliet.c optional cd9660 to conf/files or to lkm/cd9660/Makefile in order for this to work. I would be glad to hear feedback. Note that I am not currently subscribed to -current, so please answer personally as well. cu Jo --------------------------------------------------------------------- FreeBSD: The Power to Serve Joachim Kuebart Tel: +49 711 653706 Replicants are like any other machine -- Germany they're either a benefit or a hazard. --ELM889906196-1194-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=joliet.diff Content-Description: joliet.diff Content-Transfer-Encoding: 7bit Index: cd9660_lookup.c =================================================================== RCS file: /usr/CVS-Repository/src/sys/isofs/cd9660/cd9660_lookup.c,v retrieving revision 1.20 diff -u -r1.20 cd9660_lookup.c --- cd9660_lookup.c 1997/11/07 08:52:50 1.20 +++ cd9660_lookup.c 1998/03/14 17:43:48 @@ -237,8 +237,9 @@ if (namelen != 1 || ep->name[0] != 0) goto notfound; - } else if (!(res = isofncmp(name,len, - ep->name,namelen))) { + } else if (!(res = (imp->joliet_level == 0? + isofncmp(name,len,ep->name,namelen): + jolietfncmp(name,len,ep->name,namelen)))) { if (isoflags & 2) ino = isodirino(ep, imp); else Index: cd9660_vfsops.c =================================================================== RCS file: /usr/CVS-Repository/src/sys/isofs/cd9660/cd9660_vfsops.c,v retrieving revision 1.34 diff -u -r1.34 cd9660_vfsops.c --- cd9660_vfsops.c 1998/03/01 22:46:00 1.34 +++ cd9660_vfsops.c 1998/03/14 20:45:32 @@ -271,9 +271,12 @@ int ronly = (mp->mnt_flag & MNT_RDONLY) != 0; int iso_bsize; int iso_blknum; + int pri_blknum; + int joliet_level; struct iso_volume_descriptor *vdp = 0; struct iso_primary_descriptor *pri; struct iso_sierra_primary_descriptor *pri_sierra; + struct iso_supplementary_descriptor *supp; struct iso_directory_record *rootp; int logical_block_size; @@ -303,6 +306,8 @@ */ iso_bsize = ISO_DEFAULT_BLOCK_SIZE; + joliet_level = 0; + pri_blknum = -1; for (iso_blknum = 16 + argp->ssector; iso_blknum < 100 + argp->ssector; iso_blknum++) { @@ -320,19 +325,40 @@ high_sierra = 1; } - if (isonum_711 (high_sierra? vdp->type_sierra: vdp->type) == ISO_VD_END) { - error = EINVAL; - goto out; - } + if (isonum_711 (high_sierra? vdp->type_sierra: vdp->type) == ISO_VD_END) + break; if (isonum_711 (high_sierra? vdp->type_sierra: vdp->type) == ISO_VD_PRIMARY) - break; + pri_blknum = iso_blknum; + + if (isonum_711 (high_sierra? vdp->type_sierra: vdp->type) == ISO_VD_SUPPLEMENTARY) { + supp = (struct iso_supplementary_descriptor *)vdp; + if (bcmp(supp->escape, "%/@", 3) == 0) + joliet_level = 1; + if (bcmp(supp->escape, "%/C", 3) == 0) + joliet_level = 2; + if (bcmp(supp->escape, "%/E", 3) == 0) + joliet_level = 3; + if (isonum_711 (supp->flags) & 1) + joliet_level = 0; + if (joliet_level) + break; + } + brelse(bp); } - if (isonum_711 (high_sierra? vdp->type_sierra: vdp->type) != ISO_VD_PRIMARY) { - error = EINVAL; - goto out; + if (isonum_711 (high_sierra? vdp->type_sierra: vdp->type) != ISO_VD_SUPPLEMENTARY) { + if (pri_blknum == -1) { + error = EINVAL; + goto out; + } + + brelse(bp); + if (error = bread(devvp, pri_blknum * btodb(iso_bsize), + iso_bsize, NOCRED, &bp)) + goto out; + vdp = (struct iso_volume_descriptor *)bp->b_data; } pri = (struct iso_primary_descriptor *)vdp; @@ -361,6 +387,7 @@ isonum_733 (high_sierra? pri_sierra->volume_space_size: pri->volume_space_size); + isomp->joliet_level = joliet_level; /* * Since an ISO9660 multi-session CD can also access previous * sessions, we have to include them into the space consider- @@ -375,9 +402,12 @@ isomp->root_size = isonum_733 (rootp->size); isomp->im_bmask = logical_block_size - 1; +/* isomp->im_bshift = 0; while ((1 << isomp->im_bshift) < isomp->logical_block_size) isomp->im_bshift++; +*/ + isomp->im_bshift = ffs(logical_block_size) - 1; bp->b_flags |= B_AGE; brelse(bp); Index: cd9660_vnops.c =================================================================== RCS file: /usr/CVS-Repository/src/sys/isofs/cd9660/cd9660_vnops.c,v retrieving revision 1.52 diff -u -r1.52 cd9660_vnops.c --- cd9660_vnops.c 1998/03/06 09:46:14 1.52 +++ cd9660_vnops.c 1998/03/14 19:55:51 @@ -549,26 +549,28 @@ break; default: /* ISO_FTYPE_DEFAULT || ISO_FTYPE_9660 || ISO_FTYPE_HIGH_SIERRA*/ strcpy(idp->current.d_name,".."); - switch (ep->name[0]) { - case 0: + if (idp->current.d_namlen == 1 && ep->name[0] == 0) { idp->current.d_namlen = 1; error = iso_uiodir(idp,&idp->current,idp->curroff); - break; - case 1: + } else if (idp->current.d_namlen == 1 && ep->name[0] == 1) { idp->current.d_namlen = 2; error = iso_uiodir(idp,&idp->current,idp->curroff); - break; - default: - isofntrans(ep->name,idp->current.d_namlen, - idp->current.d_name, &namelen, - imp->iso_ftype == ISO_FTYPE_9660, - isonum_711(ep->flags)&4); + } else { + if (imp->joliet_level) + jolietfntrans(ep->name,idp->current.d_namlen, + idp->current.d_name, &namelen, + imp->iso_ftype == ISO_FTYPE_9660, + isonum_711(ep->flags)&4); + else + isofntrans(ep->name,idp->current.d_namlen, + idp->current.d_name, &namelen, + imp->iso_ftype == ISO_FTYPE_9660, + isonum_711(ep->flags)&4); idp->current.d_namlen = (u_char)namelen; if (imp->iso_ftype == ISO_FTYPE_DEFAULT) error = iso_shipdir(idp); else error = iso_uiodir(idp,&idp->current,idp->curroff); - break; } } if (error) Index: iso.h =================================================================== RCS file: /usr/CVS-Repository/src/sys/isofs/cd9660/iso.h,v retrieving revision 1.16 diff -u -r1.16 iso.h --- iso.h 1997/05/07 13:23:04 1.16 +++ iso.h 1998/03/12 12:52:17 @@ -54,6 +54,7 @@ /* volume descriptor types */ #define ISO_VD_PRIMARY 1 +#define ISO_VD_SUPPLEMENTARY 2 #define ISO_VD_END 255 #define ISO_STANDARD_ID "CD001" @@ -135,6 +136,42 @@ char unused4 [ISODCL (856, 2048)]; }; +struct iso_supplementary_descriptor { + char type [ISODCL ( 1, 1)]; /* 711 */ + char id [ISODCL ( 2, 6)]; + char version [ISODCL ( 7, 7)]; /* 711 */ + char flags [ISODCL ( 8, 8)]; /* 711? */ + char system_id [ISODCL ( 9, 40)]; /* achars */ + char volume_id [ISODCL ( 41, 72)]; /* dchars */ + char unused2 [ISODCL ( 73, 80)]; + char volume_space_size [ISODCL ( 81, 88)]; /* 733 */ + char escape [ISODCL ( 89, 120)]; + char volume_set_size [ISODCL (121, 124)]; /* 723 */ + char volume_sequence_number [ISODCL (125, 128)]; /* 723 */ + char logical_block_size [ISODCL (129, 132)]; /* 723 */ + char path_table_size [ISODCL (133, 140)]; /* 733 */ + char type_l_path_table [ISODCL (141, 144)]; /* 731 */ + char opt_type_l_path_table [ISODCL (145, 148)]; /* 731 */ + char type_m_path_table [ISODCL (149, 152)]; /* 732 */ + char opt_type_m_path_table [ISODCL (153, 156)]; /* 732 */ + char root_directory_record [ISODCL (157, 190)]; /* 9.1 */ + char volume_set_id [ISODCL (191, 318)]; /* dchars */ + char publisher_id [ISODCL (319, 446)]; /* achars */ + char preparer_id [ISODCL (447, 574)]; /* achars */ + char application_id [ISODCL (575, 702)]; /* achars */ + char copyright_file_id [ISODCL (703, 739)]; /* 7.5 dchars */ + char abstract_file_id [ISODCL (740, 776)]; /* 7.5 dchars */ + char bibliographic_file_id [ISODCL (777, 813)]; /* 7.5 dchars */ + char creation_date [ISODCL (814, 830)]; /* 8.4.26.1 */ + char modification_date [ISODCL (831, 847)]; /* 8.4.26.1 */ + char expiration_date [ISODCL (848, 864)]; /* 8.4.26.1 */ + char effective_date [ISODCL (865, 881)]; /* 8.4.26.1 */ + char file_structure_version [ISODCL (882, 882)]; /* 711 */ + char unused4 [ISODCL (883, 883)]; + char application_data [ISODCL (884, 1395)]; + char unused5 [ISODCL (1396, 2048)]; +}; + struct iso_directory_record { char length [ISODCL (1, 1)]; /* 711 */ char ext_attr_length [ISODCL (2, 2)]; /* 711 */ @@ -202,6 +239,8 @@ int rr_skip; int rr_skip0; + + int joliet_level; }; #define VFSTOISOFS(mp) ((struct iso_mnt *)((mp)->mnt_data)) @@ -224,6 +263,8 @@ int isofncmp __P((u_char *, int, u_char *, int)); void isofntrans __P((u_char *, int, u_char *, u_short *, int, int)); ino_t isodirino __P((struct iso_directory_record *, struct iso_mnt *)); +int jolietfncmp __P((u_char *, int, u_char *, int)); +void jolietfntrans __P((u_char *, int, u_char *, u_short *, int, int)); #endif /* KERNEL */ --ELM889906196-1194-0_ Content-Type: text/plain Content-Disposition: attachment; filename=cd9660_joliet.c Content-Description: cd9660_joliet.c Content-Transfer-Encoding: 7bit /*- * Copyright (c) 1994 * The Regents of the University of California. All rights reserved. * * This code is derived from software contributed to Berkeley * by Pace Willisson (pace@blitz.com). The Rock Ridge Extension * Support code is derived from software contributed to Berkeley * by Atsushi Murai (amurai@spec.co.jp). * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in the * documentation and/or other materials provided with the distribution. * 3. All advertising materials mentioning features or use of this software * must display the following acknowledgement: * This product includes software developed by the University of * California, Berkeley and its contributors. * 4. Neither the name of the University nor the names of its contributors * may be used to endorse or promote products derived from this software * without specific prior written permission. * * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * $Id$ */ #include #include #include #include #include /* * translate and compare a Joliet filename * Note: Version number plus ';' may be omitted. */ int jolietfncmp(fn, fnlen, isofn, isolen) u_char *fn; int fnlen; u_char *isofn; int isolen; { int i, j; unsigned int c; /* This is a special case for "." and ".." */ if (isolen == 1) { return isofn[0] - fn[0]; } if (isolen % 2) { printf("Joliet filename has odd length\n"); return -1; } while (--fnlen >= 0) { if ((isolen -= 2) < 0) return *fn; c = (isofn[0] << 8) | isofn[1]; isofn += 2; if (c & 0xff00) c = '?'; if (c == ';') { switch (*fn++) { default: return fn[-1]; case 0: return 0; case ';': break; } for (i = 0; --fnlen >= 0; i = i * 10 + *fn++ - '0') if (*fn < '0' || *fn > '9') return -1; for (j = 0; (isolen -= 2) >= 0; j = j * 10 + c - '0') { c = (isofn[0] << 8) | isofn[1]; isofn += 2; if (c & 0xff00) c = '?'; } return i - j; } if (c != *fn) return *fn - c; fn++; } if (isolen > 0) { c = (isofn[0] << 8) | isofn[1]; isofn += 2; if (c & 0xff00) c = '?'; switch (c) { default: return -1; case '.': if (isofn[1] != ';') return -1; case ';': return 0; } } return 0; } /* * translate a Joliet filename */ void jolietfntrans(infn, infnlen, outfn, outfnlen, original, assoc) u_char *infn; int infnlen; u_char *outfn; u_short *outfnlen; int original; int assoc; { int fnidx = 0; if (assoc) { *outfn++ = ASSOCCHAR; fnidx++; infnlen += 2; } if (infnlen % 2) { printf("Odd length in Joliet filename\n"); *outfnlen = 0; return; } for (; fnidx < infnlen / 2; fnidx++) { int c = (infn[0] << 8) | infn[1]; infn += 2; if (!original && c == '.' && infn[0] == 0 && infn[1] == ';') break; else if (!original && c == ';') break; if (c & 0xff00) c = '?'; *outfn++ = c; } *outfnlen = fnidx; } --ELM889906196-1194-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 12:22:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28507 for freebsd-current-outgoing; Sat, 14 Mar 1998 12:22:57 -0800 (PST) (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 MAA28496 for ; Sat, 14 Mar 1998 12:22:54 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 10339 invoked by uid 1000); 14 Mar 1998 20:29:04 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 14 Mar 1998 12:29:04 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: freebsd-current@FreeBSD.ORG Subject: MAke buildworld fails here. help? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, This is NOT a complaint against the source tree, just a question about a possible local corruption. Something broke, maybe you can point me in the right direction. On an otherwise seemingly functional 3.0-current, the buildworld target fails in kadmin with: ===> kerberosIV/usr.bin ===> kerberosIV/usr.bin/kadmin cc -nostdinc -O -pipe -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../cryp to/kerberosIV/include -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../cry pto/kerberosIV/lib/roken -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../ crypto/kerberosIV/lib/sl -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../ crypto/kerberosIV/lib/acl -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../.. /crypto/kerberosIV/lib/kadm -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../ ../crypto/kerberosIV/lib/kdb -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../.. /../crypto/kerberosIV/lib/krb -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../. ./../crypto/kerberosIV/kadmin -I/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kad min/../../lib/libkadm -I/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../. ./lib/libkrb -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../include -I/usr/src /3.0/src/kerberosIV/usr.bin/kadmin/../../include -Wall -DHAVE_CONFIG_H -I/usr/o bj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/3.0/src/tmp/usr/include -c /usr/sr c/3.0/src/kerberosIV/usr.bin/kadmin/../../../crypto/kerberosIV/kadmin/kadmin .c cc -nostdinc -O -pipe -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../cryp to/kerberosIV/include -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../cry pto/kerberosIV/lib/roken -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../ crypto/kerberosIV/lib/sl -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../ crypto/kerberosIV/lib/acl -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../.. /crypto/kerberosIV/lib/kadm -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../ ../crypto/kerberosIV/lib/kdb -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../.. /../crypto/kerberosIV/lib/krb -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../. ./../crypto/kerberosIV/kadmin -I/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kad min/../../lib/libkadm -I/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../. ./lib/libkrb -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../include -I/usr/src /3.0/src/kerberosIV/usr.bin/kadmin/../../include -Wall -DHAVE_CONFIG_H -I/usr/o bj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/3.0/src/tmp/usr/include -c /usr/sr c/3.0/src/kerberosIV/usr.bin/kadmin/../../../crypto/kerberosIV/kadmin/new_pw d.c cc -nostdinc -O -pipe -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../cryp to/kerberosIV/include -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../cry pto/kerberosIV/lib/roken -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../ crypto/kerberosIV/lib/sl -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../ crypto/kerberosIV/lib/acl -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../.. /crypto/kerberosIV/lib/kadm -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../ ../crypto/kerberosIV/lib/kdb -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../.. /../crypto/kerberosIV/lib/krb -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../. ./../crypto/kerberosIV/kadmin -I/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kad min/../../lib/libkadm -I/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../. ./lib/libkrb -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../include -I/usr/src /3.0/src/kerberosIV/usr.bin/kadmin/../../include -Wall -DHAVE_CONFIG_H -I/usr/o bj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/3.0/src/tmp/usr/include -o kadmin kadmin.o new_pwd.o -L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../ lib/libroken -lroken -L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../ lib/libsl -lsl -L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../lib/l ibacl -lacl -L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../lib/libka dm -lkadm -L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../lib/libkdb -lkdb -L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../lib/libkrb -lk rb -ldes -lcom_err -lreadline terminal.o: Undefined symbol `_tgetnum' referenced from text segment terminal.o: Undefined symbol `_tgetnum' referenced from text segment terminal.o: Undefined symbol `_tgetstr' referenced from text segment terminal.o: Undefined symbol `_tgetent' referenced from text segment terminal.o: Undefined symbol `_tgetflag' referenced from text segment terminal.o: Undefined symbol `_tgetflag' referenced from text segment terminal.o: Undefined symbol `_tgetflag' referenced from text segment terminal.o: Undefined symbol `_tgetflag' referenced from text segment terminal.o: Undefined symbol `_tputs' referenced from text segment terminal.o: Undefined symbol `_tputs' referenced from text segment terminal.o: Undefined symbol `_tputs' referenced from text segment terminal.o: Undefined symbol `_tputs' referenced from text segment terminal.o: Undefined symbol `_tputs' referenced from text segment display.o: Undefined symbol `_tputs' referenced from text segment display.o: Undefined symbol `_tputs' referenced from text segment display.o: Undefined symbol `_tputs' referenced from text segment display.o: Undefined symbol `_tputs' referenced from text segment display.o: More undefined symbol _tputs refs follow display.o: Undefined symbol `_tgoto' referenced from text segment display.o: Undefined symbol `_tgoto' referenced from text segment *** Error code 1 Stop. *** Error code 1 What puzzles me is that if I do: ``cd /usr/src/3.0/src/kerberosIV; make'' it completes without an error. Any help will be appreciated. ---------- 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 Sat Mar 14 12:49:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00763 for freebsd-current-outgoing; Sat, 14 Mar 1998 12:49:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00758 for ; Sat, 14 Mar 1998 12:49:35 -0800 (PST) (envelope-from mark@greenpeace.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 WAA13402; Sat, 14 Mar 1998 22:49:27 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id WAA15950; Sat, 14 Mar 1998 22:48:57 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199803142048.WAA15950@greenpeace.grondar.za> X-Mailer: exmh version 2.0.1 12/23/97 To: shimon@simon-shapiro.org cc: freebsd-current@FreeBSD.ORG Subject: Re: MAke buildworld fails here. help? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Mar 1998 22:48:57 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Simon Shapiro wrote: > Hi, > > This is NOT a complaint against the source tree, just a question about a > possible local corruption. Are you sure your tree is 100% clean? The breakage looks like you may have old cruft hanging around. Another theory - try moving your source tree (temporarily) to /usr/src and see if that works... > Something broke, maybe you can point me in the right direction. Does the rest of your system build properly? M > > On an otherwise seemingly functional 3.0-current, the buildworld target > fails in kadmin with: Your mailer mangles the wrapping a bit :-) > > ===> kerberosIV/usr.bin > ===> kerberosIV/usr.bin/kadmin > cc -nostdinc -O -pipe > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../cryp > to/kerberosIV/include > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../cry > pto/kerberosIV/lib/roken > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../ > crypto/kerberosIV/lib/sl > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../ > crypto/kerberosIV/lib/acl > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../.. > /crypto/kerberosIV/lib/kadm > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../ > ../crypto/kerberosIV/lib/kdb > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../.. > /../crypto/kerberosIV/lib/krb > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../. > ./../crypto/kerberosIV/kadmin > -I/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kad > min/../../lib/libkadm > -I/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../. > ./lib/libkrb -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../include > -I/usr/src > /3.0/src/kerberosIV/usr.bin/kadmin/../../include -Wall -DHAVE_CONFIG_H > -I/usr/o > bj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../include > -DBINDIR=\"/usr/bin\" > -DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/3.0/src/tmp/usr/include -c > /usr/sr > c/3.0/src/kerberosIV/usr.bin/kadmin/../../../crypto/kerberosIV/kadmin/kadmin > .c [snip] > cc -nostdinc -O -pipe > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../cryp > to/kerberosIV/include > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../cry > pto/kerberosIV/lib/roken > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../ > crypto/kerberosIV/lib/sl > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../../ > crypto/kerberosIV/lib/acl > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../.. > /crypto/kerberosIV/lib/kadm > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../ > ../crypto/kerberosIV/lib/kdb > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../.. > /../crypto/kerberosIV/lib/krb > -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../. > ./../crypto/kerberosIV/kadmin > -I/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kad > min/../../lib/libkadm > -I/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../. > ./lib/libkrb -I/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../include > -I/usr/src > /3.0/src/kerberosIV/usr.bin/kadmin/../../include -Wall -DHAVE_CONFIG_H > -I/usr/o > bj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../include > -DBINDIR=\"/usr/bin\" > -DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/3.0/src/tmp/usr/include -o > kadmin > kadmin.o new_pwd.o > -L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../ > lib/libroken -lroken > -L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../ > lib/libsl -lsl > -L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../lib/l > ibacl -lacl > -L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../lib/libka > dm -lkadm > -L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../lib/libkdb > -lkdb > -L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../lib/libkrb -lk > rb -ldes -lcom_err -lreadline > terminal.o: Undefined symbol `_tgetnum' referenced from text segment > terminal.o: Undefined symbol `_tgetnum' referenced from text segment > terminal.o: Undefined symbol `_tgetstr' referenced from text segment > terminal.o: Undefined symbol `_tgetent' referenced from text segment > terminal.o: Undefined symbol `_tgetflag' referenced from text segment > terminal.o: Undefined symbol `_tgetflag' referenced from text segment > terminal.o: Undefined symbol `_tgetflag' referenced from text segment > terminal.o: Undefined symbol `_tgetflag' referenced from text segment > terminal.o: Undefined symbol `_tputs' referenced from text segment > terminal.o: Undefined symbol `_tputs' referenced from text segment > terminal.o: Undefined symbol `_tputs' referenced from text segment > terminal.o: Undefined symbol `_tputs' referenced from text segment > terminal.o: Undefined symbol `_tputs' referenced from text segment > display.o: Undefined symbol `_tputs' referenced from text segment > display.o: Undefined symbol `_tputs' referenced from text segment > display.o: Undefined symbol `_tputs' referenced from text segment > display.o: Undefined symbol `_tputs' referenced from text segment > display.o: More undefined symbol _tputs refs follow > display.o: Undefined symbol `_tgoto' referenced from text segment > display.o: Undefined symbol `_tgoto' referenced from text segment > *** Error code 1 > > Stop. > *** Error code 1 > > What puzzles me is that if I do: > > ``cd /usr/src/3.0/src/kerberosIV; make'' > > it completes without an error. Any help will be appreciated. > > > ---------- > > > 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 -- 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 Sat Mar 14 14:23:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10168 for freebsd-current-outgoing; Sat, 14 Mar 1998 14:23:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ppp6552.on.bellglobal.com (ppp6552.on.bellglobal.com [206.172.208.144]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10159 for ; Sat, 14 Mar 1998 14:23:51 -0800 (PST) (envelope-from ac199@hwcn.org) Received: from localhost (tim@localhost) by ppp6552.on.bellglobal.com (8.8.8/8.8.8) with SMTP id RAA00645; Sat, 14 Mar 1998 17:22:13 -0500 (EST) (envelope-from ac199@hwcn.org) X-Authentication-Warning: ppp6552.on.bellglobal.com: tim owned process doing -bs Date: Sat, 14 Mar 1998 17:22:12 -0500 (EST) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Joachim Kuebart cc: current@FreeBSD.ORG Subject: Re: Joliet FS Support in CD9660 In-Reply-To: <199803142009.VAA01248@yacht.domestic.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Mar 1998, Joachim Kuebart wrote: > attached is a patch to support Joliet extensions to CD9660. The file > cd9660_joliet.c is also needed in /sys/isofs/cd9660. See also kern/5038 which also supplies patches to add Joliet support, and kern/5567 which reports reboots related to reading Joliet CDs. -- tIM...HOEk OPTIMIZATION: the process of using many one-letter variables names hoping that the resultant code will run faster. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 15:42:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22779 for freebsd-current-outgoing; Sat, 14 Mar 1998 15:42:35 -0800 (PST) (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 PAA22493 for ; Sat, 14 Mar 1998 15:41:55 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 12743 invoked by uid 1000); 14 Mar 1998 23:47:11 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-030698 [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: <199803142048.WAA15950@greenpeace.grondar.za> Date: Sat, 14 Mar 1998 15:47:11 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mark Murray Subject: Re: MAke buildworld fails here. help? Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Mar-98 Mark Murray wrote: > Simon Shapiro wrote: >> Hi, >> >> This is NOT a complaint against the source tree, just a question about a >> possible local corruption. > > Are you sure your tree is 100% clean? The breakage looks like you may > have old cruft hanging around. Probably. I just noticed this morning the log from cvsup; totally bizarre. I also noticed that in some kernel files, the merging of upstream versions and my local versions is strange too. rm -rf, here we come. > Another theory - try moving your source tree (temporarily) to /usr/src > and see if that works... That was true for 2.2, but unless somethign changed in the last two days, it should be OK. >> Something broke, maybe you can point me in the right direction. > > Does the rest of your system build properly? Up to that point, and the kernel. make buildworld, and make release on 2.2 work fine. Thanx. I strongly belive I got the CVS depository corrupted, or the source tree, or both. ---------- 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 Sat Mar 14 16:03:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29177 for freebsd-current-outgoing; Sat, 14 Mar 1998 16:03:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from murkwood.gaffaneys.com (dialup6.gaffaneys.com [208.155.161.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28925 for ; Sat, 14 Mar 1998 16:02:23 -0800 (PST) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by murkwood.gaffaneys.com (8.8.8/8.8.8) id SAA08665; Sat, 14 Mar 1998 18:02:28 -0600 (CST) (envelope-from zach) Message-ID: <19980314180228.18722@gaffaneys.com> Date: Sat, 14 Mar 1998 18:02:28 -0600 From: Zach Heilig To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: /usr/obj entries not made for these source directories: References: <199803140852.TAA27521@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803140852.TAA27521@godzilla.zeta.org.au>; from Bruce Evans on Sat, Mar 14, 1998 at 07:52:00PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 14, 1998 at 07:52:00PM +1100, Bruce Evans wrote: > >/usr/src/gnu/usr.bin/ld/rtld > >/usr/src/lib/libcrypt > >/usr/src/usr.bin/make > ld.so is rtld. Perhaps the normal rtld object directory was created after > rtld was built in the wrong place, leaving nothing to install from the > right place. Why doesn't the old rtld work? It probably works just fine, it just caused 'make installworld' go blow up. I rm -rf'ed /usr/src, and /usr/obj, and rechecked out the sources, and I noticed the same thing happening (in the same directories, except the make directory, that may have been there from a while ago). I'm not sure how to fix it, but I did go into those directories, and manually did the appropriate steps, which fixed the problems it was having at install time. Here is another interesting problem though: ===> bin/sh --- realinstall --- --- maninstall --- --- realinstall --- install -c -s -o bin -g bin -m 555 sh /bin --- maninstall --- Could not execute shell *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Interesting that it 'could not execute shell' while? it was installing it. 'make installworld' again (without the '-j4' flag) went flawlessly. -- Zach Heilig -- zach@gaffaneys.com Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 16:26:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05838 for freebsd-current-outgoing; Sat, 14 Mar 1998 16:26:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.91.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05824 for ; Sat, 14 Mar 1998 16:26:17 -0800 (PST) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (8.8.8/8.8.8) with SMTP id TAA17510; Sat, 14 Mar 1998 19:22:25 -0500 (EST) (envelope-from root@danberlin.resnet.rochester.edu) Date: Sat, 14 Mar 1998 19:22:24 -0500 (EST) From: Daniel Berlin To: Zach Heilig cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: /usr/obj entries not made for these source directories: In-Reply-To: <19980314180228.18722@gaffaneys.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 That cannot execute shell only happens to me when i use -j4 or -j2. I would guess it's because it can't very well execute the shell while it's copying over it. :) --Dan On Sat, 14 Mar 1998, Zach Heilig wrote: > On Sat, Mar 14, 1998 at 07:52:00PM +1100, Bruce Evans wrote: > > >/usr/src/gnu/usr.bin/ld/rtld > > >/usr/src/lib/libcrypt > > >/usr/src/usr.bin/make > > > ld.so is rtld. Perhaps the normal rtld object directory was created after > > rtld was built in the wrong place, leaving nothing to install from the > > right place. Why doesn't the old rtld work? > > It probably works just fine, it just caused 'make installworld' go blow up. I > rm -rf'ed /usr/src, and /usr/obj, and rechecked out the sources, and I noticed > the same thing happening (in the same directories, except the make directory, > that may have been there from a while ago). I'm not sure how to fix it, but I > did go into those directories, and manually did the appropriate steps, which > fixed the problems it was having at install time. > > Here is another interesting problem though: > > ===> bin/sh > --- realinstall --- > --- maninstall --- > --- realinstall --- > install -c -s -o bin -g bin -m 555 sh /bin > --- maninstall --- > Could not execute shell > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > Interesting that it 'could not execute shell' while? it was installing it. > 'make installworld' again (without the '-j4' flag) went flawlessly. > > -- > Zach Heilig -- zach@gaffaneys.com > Real Programs don't use shared text. Otherwise, how can they use > functions for scratch space after they are finished calling them? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 18:42:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22877 for freebsd-current-outgoing; Sat, 14 Mar 1998 18:42:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from VMSD.CSD.MU.EDU (vmsd.csd.mu.edu [134.48.20.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22839 for ; Sat, 14 Mar 1998 18:42:43 -0800 (PST) (envelope-from 4wg7kolodzie@vmsb.csd.mu.edu) Received: from mcd7-31.mccormick.mu.edu ([134.48.208.1]) by vms.csd.mu.edu (PMDF V5.1-9 #27588) with SMTP id <01IUO4J82B6M07IEFF@vms.csd.mu.edu> for freebsd-current@FreeBSD.ORG; Sat, 14 Mar 1998 20:42:28 CST Date: Sat, 14 Mar 1998 20:39:23 -0600 From: "Justin A. Kolodziej" <4wg7kolodzie@vmsb.csd.mu.edu> Subject: (no subject) To: freebsd-current@FreeBSD.ORG Message-id: <350B3F5B.2781E494@vms.csd.mu.edu> Organization: Marquette University MIME-version: 1.0 X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.0-980314-SNAP i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current end -- I sense a great disturbance in the Source. Justin A. Kolodziej I am vms.csd.mu.edu Marquette University is http://www.mu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 20:14:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03415 for freebsd-current-outgoing; Sat, 14 Mar 1998 20:14:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03401 for ; Sat, 14 Mar 1998 20:14:22 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id XAA25886; Sat, 14 Mar 1998 23:13:02 -0500 (EST) Date: Sat, 14 Mar 1998 23:13:02 -0500 (EST) From: "Matthew N. Dodd" To: Simon Shapiro cc: Mark Murray , freebsd-current@FreeBSD.ORG Subject: Re: MAke buildworld fails here. help? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Mar 1998, Simon Shapiro wrote: > Thanx. I strongly belive I got the CVS depository corrupted, or the source > tree, or both. The CVS depository... The CVS depository... The CVS depository... Damn, he could be anywhere! /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 20:51:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10510 for freebsd-current-outgoing; Sat, 14 Mar 1998 20:51:34 -0800 (PST) (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 UAA10504 for ; Sat, 14 Mar 1998 20:51:31 -0800 (PST) (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 UAA09479; Sat, 14 Mar 1998 20:48:30 -0800 (PST) Message-Id: <199803150448.UAA09479@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: Today's kernel doesn't work on (my) DK440LX In-reply-to: Your message of "Sat, 14 Mar 1998 12:36:36 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Mar 1998 20:48:27 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi all, > I had a (mostly) working kernel based on 10 March sources. Today, 'round 2 > PM EST, I sup'd again, and built the world. > > I can no longer build a (mostly) working kernel. > > My system seems to be dependent on the line: > > config kernel root on da0 swap on generic The 'generic' keyword causes a search for suitable devices. Because the bootstrap doesn't recognise the 'da' device, it passes 0 in as the boot major. The kernel recently started trusting this value; you will need to extend the bootstrap so that it supplies it correctly. > In my kernel config file. Especially the 'swap on generic' part. If I > take it out, or replace it with anything I have tried so far, my kernel > doesn't work at all. If I attempt to boot, the system attempts to change > root to wd0s2b, and I get a Fatal Trap 12. Doing a trace says that it is > happening in _ffs_mount(). This is probably because the disk type on your disk is incorrect. What does 'disklabel' say about your boot disk? > Unfortunately, today's sources don't seem to allow the 'swap on generic' > anymore. ? The configuration is disallowed, or this doesn't work anymore? > Perhaps I am looking in the wrong places, but I can't seem to find any > documentation as to what "swap on generic" means and what I should replace > it with. It's not normally useful, and shouldn't normally be there. It can help in situation such as yours. -- \\ 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 Sat Mar 14 20:56:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11555 for freebsd-current-outgoing; Sat, 14 Mar 1998 20:56:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.91.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11547 for ; Sat, 14 Mar 1998 20:56:49 -0800 (PST) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (8.8.8/8.8.8) with SMTP id XAA25338; Sat, 14 Mar 1998 23:52:32 -0500 (EST) (envelope-from root@danberlin.resnet.rochester.edu) Date: Sat, 14 Mar 1998 23:52:32 -0500 (EST) From: Daniel Berlin To: "Matthew N. Dodd" cc: Simon Shapiro , Mark Murray , freebsd-current@FreeBSD.ORG Subject: Re: MAke buildworld fails here. help? 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 This is nothing out of the unusual, source trees turn themselves inside out ALL THE TIME. On Sat, 14 Mar 1998, Matthew N. Dodd wrote: > On Sat, 14 Mar 1998, Simon Shapiro wrote: > > Thanx. I strongly belive I got the CVS depository corrupted, or the source > > tree, or both. > > The CVS depository... > > The CVS depository... > > The CVS depository... > > Damn, he could be anywhere! > > /* > Matthew N. Dodd | A memory retaining a love you had for life > winter@jurai.net | As cruel as it seems nothing ever seems to > http://www.jurai.net/~winter | go right - FLA M 3.1:53 > */ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 22:00:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17933 for freebsd-current-outgoing; Sat, 14 Mar 1998 22:00:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17926 for ; Sat, 14 Mar 1998 22:00:38 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA27824; Sun, 15 Mar 1998 17:00:00 +1100 Date: Sun, 15 Mar 1998 17:00:00 +1100 From: Bruce Evans Message-Id: <199803150600.RAA27824@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, shimon@simon-shapiro.org Subject: Re: MAke buildworld fails here. help? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > kadmin.o new_pwd.o >-L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../ >lib/libroken -lroken >-L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../ >lib/libsl -lsl >-L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../lib/l >ibacl -lacl >-L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../lib/libka >dm -lkadm >-L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../lib/libkdb > -lkdb >-L/usr/obj/usr/src/3.0/src/kerberosIV/usr.bin/kadmin/../../lib/libkrb -lk >rb -ldes -lcom_err -lreadline >terminal.o: Undefined symbol `_tgetnum' referenced from text segment >terminal.o: Undefined symbol `_tgetnum' referenced from text segment This is because kadmin/Makefile and `make world' are broken. kadmin/Makefile neglects to link to libtermcap after libreadline, so only shared linkage works. Yesterday's version of `make world' doesn't install shared libraries early enough, so shared linkage doesn't get used. >What puzzles me is that if I do: > >``cd /usr/src/3.0/src/kerberosIV; make'' > >it completes without an error. Any help will be appreciated. This is because shared linkage gets used (unless you set NOSHARED=yes in /etc/make.conf). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 22:30:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19736 for freebsd-current-outgoing; Sat, 14 Mar 1998 22:30:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19727 for ; Sat, 14 Mar 1998 22:30:17 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA28682; Sun, 15 Mar 1998 17:27:18 +1100 Date: Sun, 15 Mar 1998 17:27:18 +1100 From: Bruce Evans Message-Id: <199803150627.RAA28682@godzilla.zeta.org.au> To: bde@zeta.org.au, zach@gaffaneys.com Subject: Re: /usr/obj entries not made for these source directories: Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Here is another interesting problem though: > >===> bin/sh >--- realinstall --- >--- maninstall --- >--- realinstall --- >install -c -s -o bin -g bin -m 555 sh /bin >--- maninstall --- >Could not execute shell >*** Error code 1 >... >Interesting that it 'could not execute shell' while? it was installing it. >'make installworld' again (without the '-j4' flag) went flawlessly. The error may be for attempting to exec a shell as part of the maninstall step. I don't know why the line for execing `install' for the man page didn't get printed or why any shells get executed (make -n -j4 only shows execs of `install'). Installing with -C should be safer. Anyway, `install' is fundamentally not -j- safe. Most parts of `make world' use -B for the install steps. `make installworld' is not so careful. You currently have to know not to use -j for it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 22:56:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22009 for freebsd-current-outgoing; Sat, 14 Mar 1998 22:56:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22002 for ; Sat, 14 Mar 1998 22:56:15 -0800 (PST) (envelope-from mark@greenpeace.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 IAA14452; Sun, 15 Mar 1998 08:55:07 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id IAA18067; Sun, 15 Mar 1998 08:54:42 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199803150654.IAA18067@greenpeace.grondar.za> X-Mailer: exmh version 2.0.1 12/23/97 To: Bruce Evans cc: freebsd-current@FreeBSD.ORG, shimon@simon-shapiro.org Subject: Re: MAke buildworld fails here. help? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Mar 1998 08:54:42 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > >terminal.o: Undefined symbol `_tgetnum' referenced from text segment > >terminal.o: Undefined symbol `_tgetnum' referenced from text segment > > This is because kadmin/Makefile and `make world' are broken. > kadmin/Makefile neglects to link to libtermcap after libreadline, > so only shared linkage works. Yesterday's version of `make world' > doesn't install shared libraries early enough, so shared linkage > doesn't get used. AHA! So is the better fix to repair higher up in the tree or to add the -ltermcap to kadmin/Makefile? 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 Sat Mar 14 23:36:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26102 for freebsd-current-outgoing; Sat, 14 Mar 1998 23:36:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26075 for ; Sat, 14 Mar 1998 23:35:59 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA30752; Sun, 15 Mar 1998 18:34:32 +1100 Date: Sun, 15 Mar 1998 18:34:32 +1100 From: Bruce Evans Message-Id: <199803150734.SAA30752@godzilla.zeta.org.au> To: bde@zeta.org.au, mark@grondar.za Subject: Re: MAke buildworld fails here. help? Cc: freebsd-current@FreeBSD.ORG, shimon@simon-shapiro.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >terminal.o: Undefined symbol `_tgetnum' referenced from text segment >> >terminal.o: Undefined symbol `_tgetnum' referenced from text segment >> >> This is because kadmin/Makefile and `make world' are broken. >> kadmin/Makefile neglects to link to libtermcap after libreadline, >> so only shared linkage works. Yesterday's version of `make world' >> doesn't install shared libraries early enough, so shared linkage >> doesn't get used. > >AHA! So is the better fix to repair higher up in the tree or to add the >-ltermcap to kadmin/Makefile? Both bugs should be fixed. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 14 23:48:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27453 for freebsd-current-outgoing; Sat, 14 Mar 1998 23:48:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27448 for ; Sat, 14 Mar 1998 23:48:28 -0800 (PST) (envelope-from mark@greenpeace.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 JAA14555; Sun, 15 Mar 1998 09:47:15 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id JAA18381; Sun, 15 Mar 1998 09:46:49 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199803150746.JAA18381@greenpeace.grondar.za> X-Mailer: exmh version 2.0.1 12/23/97 To: Bruce Evans cc: mark@grondar.za, freebsd-current@FreeBSD.ORG, shimon@simon-shapiro.org Subject: Re: MAke buildworld fails here. help? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Mar 1998 09:46:49 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > >AHA! So is the better fix to repair higher up in the tree or to add the > >-ltermcap to kadmin/Makefile? > > Both bugs should be fixed. Cool. The -ltermcap is obvious and on its way. Who gets to do the other one? 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 Sun Mar 15 00:11:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29012 for freebsd-current-outgoing; Sun, 15 Mar 1998 00:11:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from VMSD.CSD.MU.EDU (vmsd.csd.mu.edu [134.48.20.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29007 for ; Sun, 15 Mar 1998 00:11:26 -0800 (PST) (envelope-from 4wg7kolodzie@vmsb.csd.mu.edu) Received: from mcd7-31.mccormick.mu.edu ([134.48.208.1]) by vms.csd.mu.edu (PMDF V5.1-9 #27588) with SMTP id <01IUOG0PGK3K07I9I8@vms.csd.mu.edu> for freebsd-current@FreeBSD.ORG; Sun, 15 Mar 1998 02:11:08 CST Date: Sun, 15 Mar 1998 02:08:03 -0600 From: "Justin A. Kolodziej" <4wg7kolodzie@vmsb.csd.mu.edu> Subject: Compiling "original" sound code into the kernel bombs To: freebsd-current@FreeBSD.ORG Message-id: <350B8C63.794BDF32@vms.csd.mu.edu> Organization: Marquette University MIME-version: 1.0 X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.0-980314-SNAP i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, now that I've already made a total fool to thousands of users, let me milk the moment: I'm Justin Kolodiej, and I just moved from Linux to FreeBSD a few days ago. I started out with the "release" release, but since the Linux emulation wasn't good enough, I moved to the "current" version. The latest snapshot has been out for a half a day now, so I'm sure the following bug has been already reported hundreds of times, ;-) but here it is: Compiling the "original" sound drivers into a custom kernel causes some strange errors. gcc chokes on the following code, taken from sound_calls.h, with a "parse error before snd_rw_buf": int sound_read_sw (int dev, struct fileinfo *file, snd_rw_buf * buf, int count); int sound_write_sw (int dev, struct fileinfo *file, snd_rw_buf * buf, int count); I believe that is the original version, but I can't guarantee it; I changed the spacing trying to get it to work, but no such luck. In fact, wherever snd_rw_buf appears, there's a "Parse error." The following code, taken from os.h, I assume, is supposed to define snd_rw_buf as a structure, but it doesn't seem to work: typedef struct uio snd_rw_buf; Let me get to the point. If you MUST have sound, use pcm instead. At least that compiles. ;-) Don't flame me TOO hard, Justin K. -- I sense a great disturbance in the Source. Justin A. Kolodziej I am vms.csd.mu.edu Marquette University is http://www.mu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 15 00:13:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29237 for freebsd-current-outgoing; Sun, 15 Mar 1998 00:13:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shire.domestic.de (kuebart.stuttgart.netsurf.de [194.233.216.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29216 for ; Sun, 15 Mar 1998 00:12:59 -0800 (PST) (envelope-from joki@kuebart.stuttgart.netsurf.de) Received: from yacht.domestic.de (yacht.domestic.de [192.168.1.4]) by shire.domestic.de (8.8.8/8.8.7) with ESMTP id JAA26296 for ; Sun, 15 Mar 1998 09:11:43 +0100 (CET) (envelope-from joki@shire.domestic.de) From: Joachim Kuebart Received: (from joki@localhost) by yacht.domestic.de (8.8.8/8.8.7) id JAA00316 for current@freebsd.org; Sun, 15 Mar 1998 09:15:35 +0100 (CET) (envelope-from joki@shire.domestic.de) Message-Id: <199803150815.JAA00316@yacht.domestic.de> Subject: Re: Joliet FS Support in CD9660 In-Reply-To: from Tim Vanderhoek at "Mar 14, 98 05:22:12 pm" To: ac199@hwcn.org Date: Wed, 15 Mar 100 00:52:27 +0100 (CET) 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 Tim Vanderhoek wrote: > On Sat, 14 Mar 1998, Joachim Kuebart wrote: > > > attached is a patch to support Joliet extensions to CD9660. The file > > cd9660_joliet.c is also needed in /sys/isofs/cd9660. > > See also kern/5038 which also supplies patches to add Joliet > support, and kern/5567 which reports reboots related to reading > Joliet CDs. I just retrieved this pr and I'm going to merge it by next week. Please send bug reports anyway, I think this needs to be put into the source (esp. cf. bin/5567). cu Jo --------------------------------------------------------------------- FreeBSD: The Power to Serve Joachim Kuebart Tel: +49 711 653706 Replicants are like any other machine -- Germany they're either a benefit or a hazard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 15 02:23:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00834 for freebsd-current-outgoing; Sun, 15 Mar 1998 02:23:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00529 for ; Sun, 15 Mar 1998 02:22:03 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA01934; Sun, 15 Mar 1998 20:39:33 +1100 Date: Sun, 15 Mar 1998 20:39:33 +1100 From: Bruce Evans Message-Id: <199803150939.UAA01934@godzilla.zeta.org.au> To: bde@zeta.org.au, mark@grondar.za Subject: Re: MAke buildworld fails here. help? Cc: freebsd-current@FreeBSD.ORG, shimon@simon-shapiro.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Both bugs should be fixed. > >Cool. The -ltermcap is obvious and on its way. Who gets to do the other >one? As I said, it was yesterday's bug. Someone already fixed it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 15 04:33:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12735 for freebsd-current-outgoing; Sun, 15 Mar 1998 04:33:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12729 for ; Sun, 15 Mar 1998 04:33:39 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA06847; Sun, 15 Mar 1998 23:25:56 +1100 Date: Sun, 15 Mar 1998 23:25:56 +1100 From: Bruce Evans Message-Id: <199803151225.XAA06847@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org Subject: Re: make/SIGINT (Re: cvs commit: src/bin/sh jobs.c) Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >What about the appended fix for make? It seems to fix the problem for >the non-compat mode of make. As our make is in compat mode by default >even if -B is not given, people would have to use `make -j 1` for now >to test it. I found another problem: time(1) has much the same problem as make(1) has without these changes: #!/bin/sh make foo make bar the whole script is killed by ^C delivered during `make bar' (since our modified `make' kills itself with a SIGINT and our modified sh handles this specially although it does not let itself be killed directly). #!/bin/sh time make foo echo $? time make bar echo $? Now `time' exits normally with status 1, so our modified sh continues. #!/bin/bash gives the same behaviour. My old POSIX.2 docs don't specify time(1). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 15 04:53:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13832 for freebsd-current-outgoing; Sun, 15 Mar 1998 04:53:55 -0800 (PST) (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 EAA13827 for ; Sun, 15 Mar 1998 04:53:51 -0800 (PST) (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 MAA18812; Sun, 15 Mar 1998 12:53:45 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id NAA18403; Sun, 15 Mar 1998 13:53:44 +0100 (MET) Message-ID: <19980315135343.41950@follo.net> Date: Sun, 15 Mar 1998 13:53:43 +0100 From: Eivind Eklund To: "Justin A. Kolodziej" <4wg7kolodzie@vmsb.csd.mu.edu>, freebsd-current@FreeBSD.ORG Subject: Re: Compiling "original" sound code into the kernel bombs References: <350B8C63.794BDF32@vms.csd.mu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <350B8C63.794BDF32@vms.csd.mu.edu>; from Justin A. Kolodziej on Sun, Mar 15, 1998 at 02:08:03AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 15, 1998 at 02:08:03AM -0600, Justin A. Kolodziej wrote: > I'm Justin Kolodiej, and I just moved from Linux to FreeBSD a few days > ago. I started out with the "release" release, but since the Linux > emulation wasn't good enough, I moved to the "current" version. -current is the (really) bleeding edge. You'd probably be more happy with -stable, which is the leading edge for working versions. (-current most often works, too, but it is a killing field - developers put things we think work there, but it has usually only gotten tested locally). > I believe that is the original version, but I can't guarantee it; I > changed the spacing trying to get it to work, but no such luck. > In fact, wherever snd_rw_buf appears, there's a "Parse error." The > following code, taken from os.h, I assume, is supposed to define > snd_rw_buf as a structure, but it doesn't seem to work: > > typedef struct uio snd_rw_buf; Can you provide a copy of your kernel config file, and I'll try to get it to compile again. (Still PCM is most likely much better :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 15 11:25:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17887 for freebsd-current-outgoing; Sun, 15 Mar 1998 11:25:52 -0800 (PST) (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 LAA17882 for ; Sun, 15 Mar 1998 11:25:49 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id UAA05002; Sun, 15 Mar 1998 20:25:42 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id UAA00221; Sun, 15 Mar 1998 20:16:39 +0100 (MET) Message-ID: <19980315201639.23917@uriah.heep.sax.de> Date: Sun, 15 Mar 1998 20:16:39 +0100 From: J Wunsch To: current@FreeBSD.ORG Cc: Mike Smith , obrien@NUXI.com Subject: Re: *HEADS UP* Correction to previous postings. Reply-To: Joerg Wunsch References: <199803090852.AAA14131@dingo.cdrom.com> <19980313185105.21172@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980313185105.21172@nuxi.com>; from David E. O'Brien on Fri, Mar 13, 1998 at 06:51:05PM -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 David E. O'Brien wrote: > In light of the new mount changes, how should these instructions from > Jo"rg be updated? > > dd if=/dev/zero of=/dev/rsd2 bs=1k count=1 > disklabel -Brw sd2 auto > disklabel -e sd2 > newfs -d0 /dev/rsd2e > fsck /dev/sd2e > > Is the slice created by ``disklable .. auto'' always "s1"? No, ``disklabel ... auto'' doesn't create any (valid) slice. It creates a bogus 4th fdisk entry, ``since this used to be so all the time'', and since Bruce's slice code expected something like this (IIRC) in order to accept the disk as a ``classic one'', i.e. one without slices. I hope Mike's changes don't start to unsupport non-sliced disks... I know of quite a number of people who'll scream then. All this mess started with the advent of the slice code in FreeBSD 2.0.5, and with the suggestion ``If you fail to install FreeBSD because of geometry problems, then well, install a small DOS partition first.'' That's simply plain unacceptable (and looks very unprofessional, too), and the intention behind my ``dangerously dedicated'' mode sysinstall changes were simply to support the class of people who Just Don't Care about any f*****ing fdisk table at all (since they don't need it, all they need is a disklabel). Note that ``sd2e'' could have two different meanings by now: it was the partition `e' on the ``compatibility slice'' iff the disk has a valid fdisk table. Alternatively, it was the partition `e' on a disk without an fdisk table. Sorry, i haven't been following -current too close lately, just returned from a vacation. So i don't know the exact details of Mike's changes, i'm just walking through tons of email. -- 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 Sun Mar 15 11:51:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20839 for freebsd-current-outgoing; Sun, 15 Mar 1998 11:51:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from VMSD.CSD.MU.EDU (vmsd.csd.mu.edu [134.48.20.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20834 for ; Sun, 15 Mar 1998 11:51:20 -0800 (PST) (envelope-from 4wg7kolodzie@vmsb.csd.mu.edu) Received: from mcd7-31.mccormick.mu.edu ([134.48.208.1]) by vms.csd.mu.edu (PMDF V5.1-9 #27588) with SMTP id <01IUP4GC1U8407I9R7@vms.csd.mu.edu> for freebsd-current@freebsd.org; Sun, 15 Mar 1998 13:50:56 CST Date: Sun, 15 Mar 1998 13:47:48 -0600 From: "Justin A. Kolodziej" <4wg7kolodzie@vmsb.csd.mu.edu> Subject: Re: Compiling "original" sound code into the kernel bombs To: Eivind Eklund Cc: freebsd-current@FreeBSD.ORG Message-id: <350C3064.41C67EA6@vms.csd.mu.edu> Organization: Marquette University MIME-version: 1.0 X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.0-980314-SNAP i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit References: <350B8C63.794BDF32@vms.csd.mu.edu> <19980315135343.41950@follo.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to have found the source of my problem. I tried to compile another program and found out that some of the things that were supposed to be defined in includes weren't, even though the program explicitly included files that included other files that contained those definitions. No "file not found," just "this is undefined." For some reason, the preprocessor only included header files to one level. I haven't tried replacing gcc with something like pgcc yet; that might solve the problem. Oh well, as they say, "Welcome to freeBSD-current. MUA HA HA HA!!! =;-}" Justin K. -- I sense a great disturbance in the Source. Justin A. Kolodziej I am vms.csd.mu.edu Marquette University is http://www.mu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 15 13:38:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04653 for freebsd-current-outgoing; Sun, 15 Mar 1998 13:38:06 -0800 (PST) (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 NAA04566 for ; Sun, 15 Mar 1998 13:37:53 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id QAA16638; Sun, 15 Mar 1998 16:35:38 -0500 (EST) Date: Sun, 15 Mar 1998 16:35:38 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: "Justin A. Kolodziej" <4wg7kolodzie@vmsb.csd.mu.edu> cc: Eivind Eklund , freebsd-current@FreeBSD.ORG Subject: Re: Compiling "original" sound code into the kernel bombs In-Reply-To: <350C3064.41C67EA6@vms.csd.mu.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 Sun, 15 Mar 1998, Justin A. Kolodziej wrote: > I seem to have found the source of my problem. I tried to compile > another program and found out that some of the things that were supposed > to be defined in includes weren't, even though the program explicitly > included files that included other files that contained those > definitions. No "file not found," just "this is undefined." For some > reason, the preprocessor only included header files to one level. I > haven't tried replacing gcc with something like pgcc yet; that might > solve the problem. No, it won't, Justin. While there are occaisonal breakages in current for a day or two, nothing like that. 99 per cent of the time, it builds fine. If you have found a drastic problem like that, it's either with your tools, or (more likely) your sources. Use cvsup to get them again. The normal gcc tools build current just fine. FreeBSD isn't and never has been as fundametally broken as that. > > Oh well, as they say, "Welcome to freeBSD-current. MUA HA HA HA!!! > =;-}" > > Justin K. > -- > I sense a great disturbance in the Source. > Justin A. Kolodziej > I am vms.csd.mu.edu > Marquette University is http://www.mu.edu > > 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 Sun Mar 15 14:15:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14282 for freebsd-current-outgoing; Sun, 15 Mar 1998 14:15:25 -0800 (PST) (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 OAA14277 for ; Sun, 15 Mar 1998 14:15:24 -0800 (PST) (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 OAA12045; Sun, 15 Mar 1998 14:13:08 -0800 (PST) Message-Id: <199803152213.OAA12045@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Joerg Wunsch cc: current@FreeBSD.ORG, Mike Smith , obrien@NUXI.com Subject: Re: *HEADS UP* Correction to previous postings. In-reply-to: Your message of "Sun, 15 Mar 1998 20:16:39 +0100." <19980315201639.23917@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Mar 1998 14:13:06 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I hope Mike's changes don't start to unsupport non-sliced disks... I You could have just asked. Or you could look at my "disklabel auto" bumper sticker. > problems, then well, install a small DOS partition first.'' That's > simply plain unacceptable (and looks very unprofessional, too), and > the intention behind my ``dangerously dedicated'' mode sysinstall > changes were simply to support the class of people who Just Don't Care > about any f*****ing fdisk table at all (since they don't need it, all > they need is a disklabel). Unfortunately, the "dangerously dedicated" sysinstall code *does* install a valid slice. It is the misinformation that you are propagating here that is the direct cause of the unhappiness with the integration of the "mount the right root filesystem" patches. -- \\ 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 Mar 15 14:49:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22145 for freebsd-current-outgoing; Sun, 15 Mar 1998 14:49:59 -0800 (PST) (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 OAA22106 for ; Sun, 15 Mar 1998 14:49:52 -0800 (PST) (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (ppp100.wcc.net [208.6.232.100]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id QAA04050; Sun, 15 Mar 1998 16:45:43 -0600 (CST) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id QAA01531; Sun, 15 Mar 1998 16:49:33 -0600 (CST) (envelope-from joelh) Date: Sun, 15 Mar 1998 16:49:33 -0600 (CST) Message-Id: <199803152249.QAA01531@detlev.UUCP> To: freebsd-current@FreeBSD.ORG Subject: Odd libalias problem - resolved From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, just in case somebody wants to know: On a CVSup from yesterday, this morning I did a make world, rebuilt my kernel, and rebooted. The PPP launch (command line 'nice --18 ppp -auto -alias wcn') gave me the message Mar 15 13:54:14 detlev ppp[223]: Warning: _PATH_ALIAS_PREFIX (/usr/lib/libalias.so.2.*): Invalid lib: Undefined symbol "_err" in ppp:/usr/lib/libalias.so.2.5 ppp went ahead and loaded, and didn't enable aliasing. Later, I pppctl'd aliasing on, and discovered that whenever aliasing was enabled, no connection over ppp worked, whether or not it originated from the machine ppp was running on. I verified the mtime on libalias, and that the file size was the same as the one in /usr/obj. (I forgot to check ppp.) I cleaned and rebuilt libalias and ppp, and now everything works fine. I'm scratching it up to the full moon that hit during the 'make world', but am documenting it (by writing this message) in case somebody else has similar problems. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 15 15:07:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25556 for freebsd-current-outgoing; Sun, 15 Mar 1998 15:07:23 -0800 (PST) (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 PAA25547 for ; Sun, 15 Mar 1998 15:07:16 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA06846 for current@freebsd.org; Sun, 15 Mar 1998 18:07:07 -0500 (EST) (envelope-from toor) Message-Id: <199803152307.SAA06846@dyson.iquest.net> Subject: Well, more VM/VFS progress made To: current@FreeBSD.ORG Date: Sun, 15 Mar 1998 18:07:07 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@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 I am committing some major improvements tonight, hopefully to make NFS, and the VFS code in general work correctly. If you have had more strange sig-11's than usual, then the stuff going in soon is for you!!! The code finally passes my regression tests and also certain other loading tests. I'll send a message to -current when my commits are done -- it'll likely be a few hours from 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 Mar 15 15:16:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27453 for freebsd-current-outgoing; Sun, 15 Mar 1998 15:16:11 -0800 (PST) (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 PAA27275; Sun, 15 Mar 1998 15:15:57 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA07317; Sun, 15 Mar 1998 18:15:43 -0500 (EST) (envelope-from toor) Message-Id: <199803152315.SAA07317@dyson.iquest.net> Subject: Re: Well, more VM/VFS progress made In-Reply-To: <199803152307.SAA06846@dyson.iquest.net> from "John S. Dyson" at "Mar 15, 98 06:07:07 pm" To: dyson@FreeBSD.ORG Date: Sun, 15 Mar 1998 18:15:43 -0500 (EST) Cc: current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 said: > > I am committing some major improvements tonight, hopefully to make > NFS, and the VFS code in general work correctly. If you have had > more strange sig-11's than usual, then the stuff going in soon is > for you!!! > PS. Not ALL NFS bugs are fixed, but will work much better. -- 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 Mar 15 15:25:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29168 for freebsd-current-outgoing; Sun, 15 Mar 1998 15:25:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coyote.instrumatic.ch (coyote.instrumatic.ch [195.226.4.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29096; Sun, 15 Mar 1998 15:24:13 -0800 (PST) (envelope-from ast@marabu.ch) Received: (from root@localhost) by coyote.instrumatic.ch (8.8.7/8.8.7/ast-971024) with UUCP id AAA19150; Mon, 16 Mar 1998 00:24:05 +0100 (MET) Received: (from uucp@localhost) by hawk.marabu.ch (8.8.8/8.8.8) with UUCP id AAA15292; Mon, 16 Mar 1998 00:18:03 +0100 (MET) (envelope-from ast@marabu.ch) Received: by marabu.marabu.ch (8.7.5/970531-ast-7.9) id AAA25361; Mon, 16 Mar 1998 00:15:26 +0100 (CET) Message-Id: <199803152315.AAA25361@marabu.marabu.ch> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 2.0b6) Received: by NeXT.Mailer (1.118.2) From: Adrian Steinmann Date: Mon, 16 Mar 98 00:15:25 +0100 To: current@FreeBSD.ORG Subject: Re: HEADS UP / disk slicing: a MAKEDEV deficiency for slices>0 ? cc: stable@FreeBSD.ORG X-Organization: Steinmann Consulting, Apollostrasse 21, 8032 Zurich X-Phone-Numbers: Switzerland, Tel +41 1 380 30 83 Fax +41 1 380 30 85 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been watching the escalation of this HEADS UP and must admit that I've become more confused than I was before. So I will add some more confusion myself ;-) It seems that, for now, 'make world' in -stable sets -DROOTSLICE_HUNT to maintain downward compatibility in the mount source files. Good. It also appears, though, that /dev/MAKEDEV only makes the [a-h] partitions for s0, so this might be why some people are having problems booting with their "new /etc/fstab" (in fact, I believe this would happen when their root partition is not on slice 0). I've tracked this feature of MAKEDEV back to revision 1.76: $ co -r1.76 -p MAKEDEV,v |grep s0h MAKEDEV,v --> standard output revision 1.76 for slicepartname in s0h s1 s2 s3 s4 $ co -r1.75 -p MAKEDEV,v |grep s0h MAKEDEV,v --> standard output revision 1.75 Where we read this comment: revision 1.76 date: 1995/03/04 12:22:14; author: bde; state: Exp; lines: +56 -70 For sd, vn and wd: Support sliced devices better. E.g.: `sh MAKEDEV sd0' creates [r]sd0 and [r]sd0s[1-4] as well as [r]sd0[a-h] (the extra devices created by default won't hurt apart from wasting inodes). `sh MAKEDEV sd0s1[a-h]' creates [r]sd0s1[a-h] (any partition creates all). `sh MAKEDEV sd0s5' creates [r]sd0s5. Support unit numbers 0-31 (was 0-6). Note, in particular, that '(cd /dev; ./MAKEDEV all)' will not make the [a-h] partitions on any slices > 0. Maybe it's time to change the line for slicepartname in s0h s1 s2 s3 s4 to for slicepartname in s0h s1h s2h s3h s4h so that /dev/MAKEDEV makes the [a-h] /dev entries for all slices? Adrian _________________________________________________________________________ Dr. Adrian Steinmann Steinmann Consulting Apollostrasse 21 8032 Zurich Tel +41 1 380 30 83 Fax +41 1 380 30 85 Mailto:ast@marabu.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 15 15:33:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01811 for freebsd-current-outgoing; Sun, 15 Mar 1998 15:33:36 -0800 (PST) (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 PAA01773; Sun, 15 Mar 1998 15:33:19 -0800 (PST) (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 PAA12496; Sun, 15 Mar 1998 15:30:32 -0800 (PST) Message-Id: <199803152330.PAA12496@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Adrian Steinmann cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: HEADS UP / disk slicing: a MAKEDEV deficiency for slices>0 ? In-reply-to: Your message of "Mon, 16 Mar 1998 00:15:25 +0100." <199803152315.AAA25361@marabu.marabu.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Mar 1998 15:30:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Note, in particular, that '(cd /dev; ./MAKEDEV all)' will not make > the [a-h] partitions on any slices > 0. > > Maybe it's time to change the line > > for slicepartname in s0h s1 s2 s3 s4 > > to > > for slicepartname in s0h s1h s2h s3h s4h > > so that /dev/MAKEDEV makes the [a-h] /dev entries for all slices? For whatever it's worth, slice 0 isn't actually terribly useful. 8) -- \\ 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 Mar 15 16:49:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12108 for freebsd-current-outgoing; Sun, 15 Mar 1998 16:49:26 -0800 (PST) (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 QAA12090 for ; Sun, 15 Mar 1998 16:49:24 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id RAA07096; Sun, 15 Mar 1998 17:46:13 -0700 (MST) Date: Sun, 15 Mar 1998 17:46:13 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199803160046.RAA07096@narnia.plutotech.com> To: Joerg Wunsch cc: current@FreeBSD.ORG Subject: Re: *HEADS UP* Correction to previous postings. Newsgroups: pluto.freebsd.current In-Reply-To: <199803090852.AAA14131@dingo.cdrom.com> <19980313185105.21172@nuxi.com> <19980315201639.23917@uriah.heep.sax.de> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980315201639.23917@uriah.heep.sax.de> you wrote: > > All this mess > started with the advent of the slice code in FreeBSD 2.0.5, and with > the suggestion ``If you fail to install FreeBSD because of geometry > problems, then well, install a small DOS partition first.'' That's > simply plain unacceptable (and looks very unprofessional, too), and > the intention behind my ``dangerously dedicated'' mode sysinstall > changes were simply to support the class of people who Just Don't Care > about any f*****ing fdisk table at all (since they don't need it, all > they need is a disklabel). It's my hope that with the adoption of CAM, the geometry problems will be a thing of the past. CAM queries the controller driver that is talking to the disk for the proper translated geometry and provides this in the label indead of the bogus physical geometry infromation from mode page 4. This should be sufficient for fdisk and friends to get the geometry right, but more testing is needed to see if other portions of the system need to be told to accept this geometry. > -- > 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. ;-) -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 15 16:58:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13093 for freebsd-current-outgoing; Sun, 15 Mar 1998 16:58:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scsn.net (root@ppp14.coladlp1.scsn.net [208.133.153.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13080 for ; Sun, 15 Mar 1998 16:58:24 -0800 (PST) (envelope-from dmaddox@scsn.net) Received: (from root@localhost) by scsn.net (8.8.8/8.8.8) id TAA23505; Sun, 15 Mar 1998 19:58:41 GMT (envelope-from root) Message-ID: <19980315195841.18574@scsn.net> Date: Sun, 15 Mar 1998 19:58:41 +0000 From: "Donald J.Maddox" To: joelh@gnu.org, freebsd-current@FreeBSD.ORG Subject: Re: Odd libalias problem - resolved Reply-To: dmaddox@scsn.net Mail-Followup-To: joelh@gnu.org, freebsd-current@FreeBSD.ORG References: <199803152249.QAA01531@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803152249.QAA01531@detlev.UUCP>; from Joel Ray Holveck on Sun, Mar 15, 1998 at 04:49:33PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 15, 1998 at 04:49:33PM -0600, Joel Ray Holveck wrote: > Well, just in case somebody wants to know: > > On a CVSup from yesterday, this morning I did a make world, rebuilt my > kernel, and rebooted. The PPP launch (command line 'nice --18 ppp > -auto -alias wcn') gave me the message > > Mar 15 13:54:14 detlev ppp[223]: Warning: _PATH_ALIAS_PREFIX > (/usr/lib/libalias.so.2.*): Invalid lib: Undefined symbol "_err" in > ppp:/usr/lib/libalias.so.2.5 > > ppp went ahead and loaded, and didn't enable aliasing. Later, I > pppctl'd aliasing on, and discovered that whenever aliasing was > enabled, no connection over ppp worked, whether or not it originated > from the machine ppp was running on. > > I verified the mtime on libalias, and that the file size was the same > as the one in /usr/obj. (I forgot to check ppp.) I cleaned and > rebuilt libalias and ppp, and now everything works fine. > > I'm scratching it up to the full moon that hit during the 'make > world', but am documenting it (by writing this message) in case > somebody else has similar problems. Well, for what it's worth, I've had exactly the same experience over the last two 'make world's I've done... The 'ppp' built during the make world doesn't like libalias, but rebuild it alone and it works fine :-/ Maybe something got screwed around in the build order? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 15 17:15:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14450 for freebsd-current-outgoing; Sun, 15 Mar 1998 17:15:23 -0800 (PST) (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 RAA14445 for ; Sun, 15 Mar 1998 17:15:21 -0800 (PST) (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 RAA03835; Sun, 15 Mar 1998 17:13:52 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: "Justin A. Kolodziej" <4wg7kolodzie@vmsb.csd.mu.edu> cc: Eivind Eklund , freebsd-current@FreeBSD.ORG Subject: Re: Compiling "original" sound code into the kernel bombs In-reply-to: Your message of "Sun, 15 Mar 1998 13:47:48 CST." <350C3064.41C67EA6@vms.csd.mu.edu> Date: Sun, 15 Mar 1998 17:13:52 -0800 Message-ID: <3832.890010832@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I seem to have found the source of my problem. I tried to compile > another program and found out that some of the things that were supposed > to be defined in includes weren't, even though the program explicitly > included files that included other files that contained those > definitions. No "file not found," just "this is undefined." For some I don't know about the rest of you, but I can't make any sense whatsoever out of the preceeding paragraph. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 15 18:16:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19858 for freebsd-current-outgoing; Sun, 15 Mar 1998 18:16:00 -0800 (PST) (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 SAA19842 for ; Sun, 15 Mar 1998 18:15:56 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id VAA02210 for current@freebsd.org; Sun, 15 Mar 1998 21:15:55 -0500 (EST) (envelope-from toor) Message-Id: <199803160215.VAA02210@dyson.iquest.net> Subject: Kernel stability commits complete To: current@FreeBSD.ORG Date: Sun, 15 Mar 1998 21:15:55 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@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 My promised fixes are now committed. Good luck, and bug me over the next few days, when I have time to fix things. -- 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 Mar 15 19:31:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29139 for freebsd-current-outgoing; Sun, 15 Mar 1998 19:31:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29090; Sun, 15 Mar 1998 19:30:58 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA02498; Mon, 16 Mar 1998 14:25:59 +1100 Date: Mon, 16 Mar 1998 14:25:59 +1100 From: Bruce Evans Message-Id: <199803160325.OAA02498@godzilla.zeta.org.au> To: ast@marabu.ch, mike@smith.net.au Subject: Re: HEADS UP / disk slicing: a MAKEDEV deficiency for slices>0 ? Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Maybe it's time to change the line >> >> for slicepartname in s0h s1 s2 s3 s4 >> >> to >> >> for slicepartname in s0h s1h s2h s3h s4h >> >> so that /dev/MAKEDEV makes the [a-h] /dev entries for all slices? > >For whatever it's worth, slice 0 isn't actually terribly useful. 8) There is no slice s0. "s0" is handled specially by MAKEDEV (and eventually replaced by "") to give the compatibility slice (slice number 0), which is very useful. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 15 19:36:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00444 for freebsd-current-outgoing; Sun, 15 Mar 1998 19:36:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00435 for ; Sun, 15 Mar 1998 19:36:32 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id OAA13568; Mon, 16 Mar 1998 14:04:34 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id G0BWV37Z; Mon, 16 Mar 1998 14:05:10 +0930 Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id OAA12999; Mon, 16 Mar 1998 14:05:52 +1030 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id OAA00402; Mon, 16 Mar 1998 14:05:41 +1030 (CST) Message-ID: <350C9E0C.2A3B1623@dsto.defence.gov.au> Date: Mon, 16 Mar 1998 14:05:40 +1030 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: Studded , FreeBSD CURRENT Subject: Kernel building before make world (was Re: trouble booting) References: <7629.889870081@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Re: LKM's, I have everything compiled into the kernel and have my DOS partition optioned noauto in /etc/fstab so it wont mount on boot. I've done this after being bitten by the DOS LKM before. I dont want to use "options NO_LKM" as I do mount my dos partition sometimes. Can the DOS filesystem be compiled statically into the kernel ? Oh, I do enable_linux on startup so I suppose that'll bite me one day but it hasn't yet. About the "will blow out a new kernel" bit, I'm not sure what you mean but I assume that my build of a new kernel after the make world would fix it. So given my LKM precautions is there any use building a kernel first ? Am I going to get a better quality world build using a kernel from the same sources ? More importantly, am I going to get a worse quality build doing things this way ? I suppose the answer is that I'm wasting time and blowing out the size of my kernel (with everything static) and I should only build a kernel first when warned to on the list. Jordan K. Hubbard wrote: > > > I'm curious about this. This isn't a dig, although my incredulity might > > make it seem so. Every piece of documentation I've seen says to do it > > the other way around. Make world first, then build kernel, then boot. > > This is correct. If you've just done major things to the build tools, > or even if you've merely changed config(8) in a way that will blow out > a new kernel (and this happens fairly often, actually) the make world > will fix this for you before you move on to building the kernel. > > Also, building just the kernel and then rebooting from it (otherwise, > what would be the point of building it first?) can truly hang you if > your LKMs are out of date. Building the kernel first is therefore NOT > recommended practice. > > Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 15 20:12:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05091 for freebsd-current-outgoing; Sun, 15 Mar 1998 20:12:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt050n33.san.rr.com (@dt050n33.san.rr.com [204.210.31.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05086 for ; Sun, 15 Mar 1998 20:12:05 -0800 (PST) (envelope-from Studded@san.rr.com) Received: from san.rr.com (Studded@localhost [127.0.0.1]) by dt050n33.san.rr.com (8.8.8/8.8.8) with ESMTP id UAA17265 for ; Sun, 15 Mar 1998 20:12:03 -0800 (PST) (envelope-from Studded@san.rr.com) Message-ID: <350CA692.995149F3@san.rr.com> Date: Sun, 15 Mar 1998 20:12:02 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-BETA-0313 i386) MIME-Version: 1.0 To: FreeBSD CURRENT Subject: Re: Kernel building before make world (was Re: trouble booting) References: <7629.889870081@time.cdrom.com> <350C9E0C.2A3B1623@dsto.defence.gov.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Thyer wrote: > Can the DOS filesystem be compiled statically into the kernel ? Yes, options MSDOSFS.. check out LINT. > So given my LKM precautions is there any use building a kernel > first ? Don't build the kernel first. > I suppose the answer is that I'm wasting time and blowing out the > size of my kernel (with everything static) and I should only build > a kernel first when warned to on the list. Voila. :) Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (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 Sun Mar 15 22:41:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15818 for freebsd-current-outgoing; Sun, 15 Mar 1998 22:41:49 -0800 (PST) (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 WAA15811 for ; Sun, 15 Mar 1998 22:41:40 -0800 (PST) (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 HAA00285 for ; Mon, 16 Mar 1998 07:46:28 +0100 (MET) Message-ID: <38D082D4.95C0F30E@giovannelli.it> Date: Thu, 16 Mar 2000 07:44:36 +0100 From: Gianmarco Giovannelli X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: makeworld fails on man install (980316) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- beforeinstall --- install -c -o bin -g bin -m 444 /usr/src/usr.sbin/pcvt/keycap/keycap.src /usr/s hare/misc/keycap.pcvt --- maninstall --- install -c -o bin -g bin -m 444 keycap.3.gz /usr/share/man/man3 --- maninstall --- install -c -o bin -g bin -m 444 keycap.5.gz /usr/share/man/man5 /usr/share/man/man3/kgetent.3.gz -> /usr/share/man/man3/keycap.3.gz --- realinstall --- --- maninstall --- ln: /usr/share/man/man3/keycap.3.gz: No such file or directory --- realinstall --- install -c -o bin -g bin -m 644 libkeycap.a /usr/lib --- maninstall --- *** Error code 1 1 error *** Error code 2 1 error Yesterday evening and this morning cvsup seems not to correct the problem... -- 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 Mon Mar 16 00:46:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28752 for freebsd-current-outgoing; Mon, 16 Mar 1998 00:46:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28747 for ; Mon, 16 Mar 1998 00:46:41 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA15311; Mon, 16 Mar 1998 19:40:32 +1100 Date: Mon, 16 Mar 1998 19:40:32 +1100 From: Bruce Evans Message-Id: <199803160840.TAA15311@godzilla.zeta.org.au> To: current@FreeBSD.ORG, gmarco@giovannelli.it Subject: Re: makeworld fails on man install (980316) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >--- beforeinstall --- >install -c -o bin -g bin -m 444 >/usr/src/usr.sbin/pcvt/keycap/keycap.src /usr/s >hare/misc/keycap.pcvt >--- maninstall --- >install -c -o bin -g bin -m 444 keycap.3.gz /usr/share/man/man3 >--- maninstall --- >install -c -o bin -g bin -m 444 keycap.5.gz /usr/share/man/man5 >/usr/share/man/man3/kgetent.3.gz -> /usr/share/man/man3/keycap.3.gz >--- realinstall --- >--- maninstall --- >ln: /usr/share/man/man3/keycap.3.gz: No such file or directory >--- realinstall --- >install -c -o bin -g bin -m 644 libkeycap.a /usr/lib >--- maninstall --- >*** Error code 1 >1 error >*** Error code 2 >1 error This looks like output from `make -jsomething installworld'. -j doesn't work with the installworld target. `make world' runs most installs, including installworld, with -B to avoid problems like this. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 02:19:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA07833 for freebsd-current-outgoing; Mon, 16 Mar 1998 02:19:50 -0800 (PST) (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 CAA07770 for ; Mon, 16 Mar 1998 02:19:36 -0800 (PST) (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 KAA03675; Mon, 16 Mar 1998 10:19:26 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id LAA01724; Mon, 16 Mar 1998 11:19:26 +0100 (MET) Message-ID: <19980316111926.32046@follo.net> Date: Mon, 16 Mar 1998 11:19:26 +0100 From: Eivind Eklund To: "Jordan K. Hubbard" , "Justin A. Kolodziej" <4wg7kolodzie@vmsb.csd.mu.edu> Cc: Eivind Eklund , freebsd-current@FreeBSD.ORG Subject: Re: Compiling "original" sound code into the kernel bombs References: <350C3064.41C67EA6@vms.csd.mu.edu> <3832.890010832@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <3832.890010832@time.cdrom.com>; from Jordan K. Hubbard on Sun, Mar 15, 1998 at 05:13:52PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 15, 1998 at 05:13:52PM -0800, Jordan K. Hubbard wrote: > > I seem to have found the source of my problem. I tried to compile > > another program and found out that some of the things that were supposed > > to be defined in includes weren't, even though the program explicitly > > included files that included other files that contained those > > definitions. No "file not found," just "this is undefined." For some > > I don't know about the rest of you, but I can't make any sense whatsoever > out of the preceeding paragraph. He had misunderstood the interaction between config(8), preprocessor defines, and his kernel config file. Not too strange. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 04:52:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02511 for freebsd-current-outgoing; Mon, 16 Mar 1998 04:52:01 -0800 (PST) (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 EAA02483 for ; Mon, 16 Mar 1998 04:51:50 -0800 (PST) (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 MAA06101; Mon, 16 Mar 1998 12:49:29 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id NAA02851; Mon, 16 Mar 1998 13:49:07 +0100 (MET) Message-ID: <19980316134906.22804@follo.net> Date: Mon, 16 Mar 1998 13:49:06 +0100 From: Eivind Eklund To: joelh@gnu.org, freebsd-current@FreeBSD.ORG Cc: Charles Mott , Ari Suutari , Brian Somers Subject: Re: Odd libalias problem - resolved References: <199803152249.QAA01531@detlev.UUCP> <19980315195841.18574@scsn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980315195841.18574@scsn.net>; from Donald J.Maddox on Sun, Mar 15, 1998 at 07:58:41PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 15, 1998 at 07:58:41PM +0000, Donald J.Maddox wrote: > On Sun, Mar 15, 1998 at 04:49:33PM -0600, Joel Ray Holveck wrote: > > Mar 15 13:54:14 detlev ppp[223]: Warning: _PATH_ALIAS_PREFIX > > (/usr/lib/libalias.so.2.*): Invalid lib: Undefined symbol "_err" in > > ppp:/usr/lib/libalias.so.2.5 > > > > ppp went ahead and loaded, and didn't enable aliasing. Later, I > > pppctl'd aliasing on, and discovered that whenever aliasing was > > enabled, no connection over ppp worked, whether or not it originated > > from the machine ppp was running on. > > > > I verified the mtime on libalias, and that the file size was the same > > as the one in /usr/obj. (I forgot to check ppp.) I cleaned and > > rebuilt libalias and ppp, and now everything works fine. > > > > I'm scratching it up to the full moon that hit during the 'make > > world', but am documenting it (by writing this message) in case > > somebody else has similar problems. > > Well, for what it's worth, I've had exactly the same experience over > the last two 'make world's I've done... The 'ppp' built during the make > world doesn't like libalias, but rebuild it alone and it works fine :-/ > > Maybe something got screwed around in the build order? Sounds like ppp got built with a shared libalias or using err() at one point, and without it at another point. I'm slightly uncertain at how to handle the problems here. The err() in libalias is for the case where libalias get an error when calling ipfw. There is no error path out of libalias at that point, so there are basically three options: * Ignore the error * Throw an error message somewhere and exit (through err(), in this case) * Throw an abort() party (it's probably best to do this by directly sending the abort() signal to the current process through the syscall). * Change the return values for libalias (this require the cooperation of Charles Mott, the architect for libalias). As the err() solution seems to be causing regular problems, I'd be happy to change it - it was probably a bad choice from my side from the start. I'd like to change the return values, but that mean that they suddenly gain significance - which should really cause a major number bump. This again is bad for -stable... Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 05:59:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18288 for freebsd-current-outgoing; Mon, 16 Mar 1998 05:59:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from netcom1.netcom.com (mvh@netcom15.netcom.com [192.100.81.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18228; Mon, 16 Mar 1998 05:59:49 -0800 (PST) (envelope-from mvh@netcom.com) Received: (from mvh@localhost) by netcom1.netcom.com (8.8.8/8.8.8) id FAA00815; Mon, 16 Mar 1998 05:59:33 -0800 (PST) (envelope-from mvh) Date: Mon, 16 Mar 1998 05:59:33 -0800 (PST) Message-Id: <199803161359.FAA00815@netcom1.netcom.com> From: "Michael V. Harding" To: ast@marabu.ch CC: current@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: <199803152315.AAA25361@marabu.marabu.ch> (message from Adrian Steinmann on Mon, 16 Mar 98 00:15:25 +0100) Subject: Re: HEADS UP / disk slicing: a MAKEDEV deficiency for slices>0 ? References: <199803152315.AAA25361@marabu.marabu.ch> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll concur on this one - with dual boot machines, FreeBSD is often on the second disk or second partitionm - this is why we saw boot fail. Not too hard to fixe once you know what you are doing, but it was awkward because I couldn't even check the FAQ until I got the system running again. I don't know if this is because I have two disks, also, but when I did an upgrade in place to 2.2.6 it ate the entire disk. I'm afraid to use anything but CVSUP now. Luckily I did have the important stuff backed up... Content-Type: text/plain X-Nextstep-Mailer: Mail 3.3 (Enhance 2.0b6) From: Adrian Steinmann Date: Mon, 16 Mar 98 00:15:25 +0100 cc: stable@FreeBSD.ORG X-Organization: Steinmann Consulting, Apollostrasse 21, 8032 Zurich X-Phone-Numbers: Switzerland, Tel +41 1 380 30 83 Fax +41 1 380 30 85 Sender: owner-freebsd-stable@FreeBSD.ORG X-UIDL: 4f9b60e355e64f6e873812ec122fccae I have been watching the escalation of this HEADS UP and must admit that I've become more confused than I was before. So I will add some more confusion myself ;-) It seems that, for now, 'make world' in -stable sets -DROOTSLICE_HUNT to maintain downward compatibility in the mount source files. Good. It also appears, though, that /dev/MAKEDEV only makes the [a-h] partitions for s0, so this might be why some people are having problems booting with their "new /etc/fstab" (in fact, I believe this would happen when their root partition is not on slice 0). I've tracked this feature of MAKEDEV back to revision 1.76: $ co -r1.76 -p MAKEDEV,v |grep s0h MAKEDEV,v --> standard output revision 1.76 for slicepartname in s0h s1 s2 s3 s4 $ co -r1.75 -p MAKEDEV,v |grep s0h MAKEDEV,v --> standard output revision 1.75 Where we read this comment: revision 1.76 date: 1995/03/04 12:22:14; author: bde; state: Exp; lines: +56 -70 For sd, vn and wd: Support sliced devices better. E.g.: `sh MAKEDEV sd0' creates [r]sd0 and [r]sd0s[1-4] as well as [r]sd0[a-h] (the extra devices created by default won't hurt apart from wasting inodes). `sh MAKEDEV sd0s1[a-h]' creates [r]sd0s1[a-h] (any partition creates all). `sh MAKEDEV sd0s5' creates [r]sd0s5. Support unit numbers 0-31 (was 0-6). Note, in particular, that '(cd /dev; ./MAKEDEV all)' will not make the [a-h] partitions on any slices > 0. Maybe it's time to change the line for slicepartname in s0h s1 s2 s3 s4 to for slicepartname in s0h s1h s2h s3h s4h so that /dev/MAKEDEV makes the [a-h] /dev entries for all slices? Adrian _________________________________________________________________________ Dr. Adrian Steinmann Steinmann Consulting Apollostrasse 21 8032 Zurich Tel +41 1 380 30 83 Fax +41 1 380 30 85 Mailto:ast@marabu.ch 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 Mon Mar 16 07:52:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06230 for freebsd-current-outgoing; Mon, 16 Mar 1998 07:52:39 -0800 (PST) (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 HAA06223 for ; Mon, 16 Mar 1998 07:52:33 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 14703 invoked from network); 16 Mar 1998 16:00:48 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 16 Mar 1998 16:00:48 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-031298 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 16 Mar 1998 08:00:48 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: frebsd-doc@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: /usr/share/examples/FreeBSD_version/FreeBSD_version.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I really am not sure where/who this one goes to. Said file is cleaimed to be missing by make release. I saw it on 2.2 last week. Now I see it in 3.0-current. Here is the make output tail: ===> share/examples install -c -o bin -g bin -m 644 FreeBSD_version/FreeBSD_version.c /usr/share/examples/FreeBSD_version/FreeBSD_version.c install: /usr/share/examples/FreeBSD_version/FreeBSD_version.c: No such file or directory *** Error code 71 Stop. ---------- 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 Mon Mar 16 07:58:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07572 for freebsd-current-outgoing; Mon, 16 Mar 1998 07:58:50 -0800 (PST) (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 HAA07562 for ; Mon, 16 Mar 1998 07:58:47 -0800 (PST) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.5/8.7.3) id RAA20971; Mon, 16 Mar 1998 17:00:33 +0100 (CET) Message-ID: <19980316170033.48124@cons.org> Date: Mon, 16 Mar 1998 17:00:33 +0100 From: Martin Cracauer To: Bruce Evans Cc: cracauer@cons.org, freebsd-current@FreeBSD.ORG Subject: Re: make/SIGINT (Re: cvs commit: src/bin/sh jobs.c) References: <199803151225.XAA06847@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199803151225.XAA06847@godzilla.zeta.org.au>; from Bruce Evans on Sun, Mar 15, 1998 at 11:25:56PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199803151225.XAA06847@godzilla.zeta.org.au>, Bruce Evans wrote: > >What about the appended fix for make? It seems to fix the problem for > >the non-compat mode of make. As our make is in compat mode by default > >even if -B is not given, people would have to use `make -j 1` for now > >to test it. > > I found another problem: time(1) has much the same problem as make(1) [...] > #!/bin/sh > time make foo > echo $? > time make bar > echo $? > > Now `time' exits normally with status 1, so our modified sh continues. I finally get used to this kind of stuff :-), proposed patch appended. 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 *** time.original/time.c Tue Aug 26 12:08:45 1997 --- time.work/time.c Mon Mar 16 16:51:30 1998 *************** *** 56,61 **** --- 56,62 ---- #include #include #include + #include static int getstathz __P((void)); static void usage __P((void)); *************** *** 69,74 **** --- 70,76 ---- int ch, status, lflag; struct timeval before, after; struct rusage ru; + int exitonsig = 0; /* Die with same signal as child */ lflag = 0; while ((ch = getopt(argc, argv, "l")) != -1) *************** *** 101,108 **** (void)signal(SIGQUIT, SIG_IGN); while (wait3(&status, 0, &ru) != pid); /* XXX use waitpid */ gettimeofday(&after, (struct timezone *)NULL); ! if (status&0377) warnx("command terminated abnormally"); after.tv_sec -= before.tv_sec; after.tv_usec -= before.tv_usec; if (after.tv_usec < 0) --- 103,112 ---- (void)signal(SIGQUIT, SIG_IGN); while (wait3(&status, 0, &ru) != pid); /* XXX use waitpid */ gettimeofday(&after, (struct timezone *)NULL); ! if ( ! WIFEXITED(status)) warnx("command terminated abnormally"); + if (WIFSIGNALED(status)) + exitonsig = WTERMSIG(status); after.tv_sec -= before.tv_sec; after.tv_usec -= before.tv_usec; if (after.tv_usec < 0) *************** *** 154,159 **** --- 158,169 ---- ru.ru_nvcsw, "voluntary context switches"); fprintf(stderr, "%10ld %s\n", ru.ru_nivcsw, "involuntary context switches"); + } + if (exitonsig) { + if (signal(exitonsig, SIG_DFL) < 0) + perror("signal"); + else + kill(getpid(), exitonsig); } exit (WIFEXITED(status) ? WEXITSTATUS(status) : EXIT_FAILURE); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 08:01:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08158 for freebsd-current-outgoing; Mon, 16 Mar 1998 08:01:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from srv.net (snake.srv.net [199.104.81.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08151 for ; Mon, 16 Mar 1998 08:01:11 -0800 (PST) (envelope-from cmott@srv.net) Received: from darkstar.home (cmott.srv.net [199.104.81.25]) by srv.net (8.8.7/8.8.5) with SMTP id JAA15150; Mon, 16 Mar 1998 09:00:38 -0700 (MST) Date: Mon, 16 Mar 1998 09:00:07 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: Eivind Eklund cc: joelh@gnu.org, freebsd-current@FreeBSD.ORG, Ari Suutari , Brian Somers Subject: Re: Odd libalias problem - resolved In-Reply-To: <19980316134906.22804@follo.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 > * Change the return values for libalias (this require the cooperation > of Charles Mott, the architect for libalias). > > As the err() solution seems to be causing regular problems, I'd be > happy to change it - it was probably a bad choice from my side from > the start. I'd like to change the return values, but that mean that > they suddenly gain significance - which should really cause a major > number bump. This again is bad for -stable... > > Eivind. I can't quite follow what is going on here. If you add a return value and leave the others the same, possibly the major version could be left the same. There are only two programs, natd and ppp which use the library, so compatibility could be checked fairly easily. As far as what to do, I leave it to the best judgment of Eivind and Brian (and Ari if he has an opinion on the matter), all of whom are more experienced programmers than I am. Charles Mott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 08:29:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16445 for freebsd-current-outgoing; Mon, 16 Mar 1998 08:29:18 -0800 (PST) (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 IAA16343 for ; Mon, 16 Mar 1998 08:29:01 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id LAA00521 for ; Mon, 16 Mar 1998 11:26:15 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Mon, 16 Mar 1998 11:26:15 -0500 (EST) From: "Alok K. Dhir" To: current@FreeBSD.ORG Subject: Worldstone Continued... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK - I got a lot out of our last discussion, and now my -current world builds in 1:23 (!!). This is WITHOUT softupdates, but using async mounts... --- world --- -------------------------------------------------------------- make world started on Mon Mar 16 02:20:29 EST 1998 -------------------------------------------------------------- cd /usr/src && make buildworld --- buildworld --- -------------------------------------------------------------- [...crunch...] -------------------------------------------------------------- make world completed on Mon Mar 16 03:43:40 EST 1998 -------------------------------------------------------------- Config: Dell Workstation 400, dual PII300, 256Mb RAM /usr/src on an UW 7200 RPM SCSI Disk (Western Dig. WDE4360), async /usr/obj on a ccd striped part. made of two of the above disks, async make.conf: CFLAGS= -O -pipe (And yes, I am building the profiled libraries)... -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ R7-003, ITSMC 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 Mon Mar 16 09:22:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07982 for freebsd-current-outgoing; Mon, 16 Mar 1998 09:22:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mynet.ml.org ([24.112.74.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07965 for ; Mon, 16 Mar 1998 09:22:35 -0800 (PST) (envelope-from ihuang@mynet.ml.org) Received: from localhost (ihuang@localhost) by mynet.ml.org (8.8.8/8.8.6) with SMTP id MAA13966; Mon, 16 Mar 1998 12:22:29 -0500 (EST) Date: Mon, 16 Mar 1998 12:22:28 -0500 (EST) From: Ian Huang To: "Alok K. Dhir" cc: current@FreeBSD.ORG Subject: Re: Worldstone Continued... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I built world in 1:26 on a K6-250@83Mhz bus clock with 64MB SDRAM, Asus TX97-E mainboard, Maxtor 6.4Gig UDMA drive. The partitions are mounted async, noatime. On Mon, 16 Mar 1998, Alok K. Dhir wrote: > > OK - I got a lot out of our last discussion, and now my -current world > builds in 1:23 (!!). This is WITHOUT softupdates, but using async > mounts... > > --- world --- > -------------------------------------------------------------- > make world started on Mon Mar 16 02:20:29 EST 1998 > -------------------------------------------------------------- > cd /usr/src && make buildworld > --- buildworld --- > -------------------------------------------------------------- > [...crunch...] > -------------------------------------------------------------- > make world completed on Mon Mar 16 03:43:40 EST 1998 > -------------------------------------------------------------- > > Config: > > Dell Workstation 400, dual PII300, 256Mb RAM > /usr/src on an UW 7200 RPM SCSI Disk (Western Dig. WDE4360), async > /usr/obj on a ccd striped part. made of two of the above disks, async > > make.conf: > > CFLAGS= -O -pipe > > (And yes, I am building the profiled libraries)... > > > -------------------------------------------------------------------- \||/_ > Alok K. Dhir Phone: +1.202.473.2446 oo \ > R7-003, ITSMC 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 09:56:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19880 for freebsd-current-outgoing; Mon, 16 Mar 1998 09:56:10 -0800 (PST) (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 JAA19803 for ; Mon, 16 Mar 1998 09:56:03 -0800 (PST) (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 MAA14778 for ; Mon, 16 Mar 1998 12:55:29 -0500 (EST) X-Sender: ckempfm@enigami.com Message-Id: In-Reply-To: References: <199803161201.WAA07459@bioserve.biochem.latrobe.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Mar 1998 12:55:17 -0500 To: freebsd-current@FreeBSD.ORG From: Cory Kempf Subject: CAM based CD? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure if this should go to -scsi or -current, but since anyone using CAM needs to be current, -current should be a superset. Well, I have managed to hose my system. Rebuilding the world from sources is failing, so I suspect that there is still some random corruption I haven't found. At this point, it looks like I am going to need to do a clean install. Joy. The first one took about three days to download everything. Not wanting to do that again, I was wondering... Is a CAM based CD set currently available for purchase? If not, any ideas when such a disc will be pressed? Given that CAM has not been rolled into the -current source tree yet (and according to the web page, 3.0 is due out Q1 98... i.e. NOW), is a CAM based release going to be a post 3.0 sort of thing? 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 Mon Mar 16 10:08:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25097 for freebsd-current-outgoing; Mon, 16 Mar 1998 10:08:35 -0800 (PST) (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 KAA25019 for ; Mon, 16 Mar 1998 10:08:25 -0800 (PST) (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 KAA21259; Mon, 16 Mar 1998 10:06:40 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: CAM based CD? In-reply-to: Your message of "Mon, 16 Mar 1998 12:55:17 EST." Date: Mon, 16 Mar 1998 10:06:40 -0800 Message-ID: <21255.890071600@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is a CAM based CD set currently available for purchase? If not, any ideas > when such a disc will be pressed? When CAM enters -current, basically. Talk to Justin. ;) > Given that CAM has not been rolled into the -current source tree yet (and > according to the web page, 3.0 is due out Q1 98... i.e. NOW), is a CAM s/Q1/Q4/ - we still have time. :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 12:28:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13545 for freebsd-current-outgoing; Mon, 16 Mar 1998 12:28:59 -0800 (PST) (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 MAA13536 for ; Mon, 16 Mar 1998 12:28:57 -0800 (PST) (envelope-from root@mordred.cs.ucla.edu) Received: (qmail 14201 invoked from network); 16 Mar 1998 20:28:25 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 16 Mar 1998 20:28:25 -0000 Received: (from root@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id MAA00664 for freebsd-current@freebsd.org; Mon, 16 Mar 1998 12:28:48 -0800 (PST) (envelope-from root) Date: Mon, 16 Mar 1998 12:28:48 -0800 (PST) From: Sir Mordred Message-Id: <199803162028.MAA00664@mordred.cs.ucla.edu> To: freebsd-current@FreeBSD.ORG Subject: softupdate panic Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From a kernel which was cvsup'd last night. This appears to happen when under load. I won't discount bad memory on my machine, but it's hard to tell... Also, FWIW, the new VM patches from last night: I still end up getting the occaisional spurious sig 11's on sendmail and cron. Restarting the daemons appears to make them go away -- which diminishes my suspicions of memory hardware problems. No panics in VM code, though, which is a good thing. -scooter Traceback: -------------------------------------------------------------------------- IdlePTD b29000 initial pcb at 23bea8 panicstr: flush_pagedep_deps: flush 3 failed panic messages: --- panic: flush_pagedep_deps: flush 3 failed syncing disks... 21 21 16 7 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up 1: dev:0003000e, flags:000002b0, blkno:26784, lblkno:0 dumping to dev 30001, offset 33216 dump 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:296 296 dumppcb.pcb_cr3 = rcr3(); (kgdb) up #1 0xf0124ce3 in panic (fmt=0xf01be1d6 "flush_pagedep_deps: flush 3 failed") at ../../kern/kern_shutdown.c:436 436 boot(bootopt); (kgdb) up #2 0xf01be572 in flush_pagedep_deps (pvp=0xf3626960, mp=0xf0ebfc00, diraddhdp=0xf0f08be8) at ../../ufs/ffs/ffs_softdep.c:4028 4028 panic("flush_pagedep_deps: flush 3 failed"); (kgdb) l 4023 /* 4024 * If we have failed to get rid of all the dependencies 4025 * then something is seriously wrong. 4026 */ 4027 if (dap == LIST_FIRST(diraddhdp)) 4028 panic("flush_pagedep_deps: flush 3 failed"); 4029 ACQUIRE_LOCK(&lk); 4030 } 4031 if (error) 4032 ACQUIRE_LOCK(&lk); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:296 #1 0xf0124ce3 in panic (fmt=0xf01be1d6 "flush_pagedep_deps: flush 3 failed") at ../../kern/kern_shutdown.c:436 #2 0xf01be572 in flush_pagedep_deps (pvp=0xf3626960, mp=0xf0ebfc00, diraddhdp=0xf0f08be8) at ../../ufs/ffs/ffs_softdep.c:4028 #3 0xf01bdd94 in softdep_sync_metadata (ap=0xf3707b70) at ../../ufs/ffs/ffs_softdep.c:3744 #4 0xf01c2546 in ffs_fsync (ap=0xf3707b70) at ../../ufs/ffs/ffs_vnops.c:224 #5 0xf01b7823 in ffs_truncate (vp=0xf3626960, length=0x0000000000000400, flags=4, cred=0xf0f28b00, p=0xf35fb2c0) at vnode_if.h:499 #6 0xf01c51eb in ufs_direnter (dvp=0xf3626960, tvp=0xf3679080, dirp=0xf3707cd4, cnp=0xf3707f24, newdirbp=0x0) at ../../ufs/ufs/ufs_lookup.c:827 #7 0xf01c9b12 in ufs_makeinode (mode=33152, dvp=0xf3626960, vpp=0xf3707f10, cnp=0xf3707f24) at ../../ufs/ufs/ufs_vnops.c:2105 #8 0xf01c6c99 in ufs_create (ap=0xf3707e2c) at ../../ufs/ufs/ufs_vnops.c:151 #9 0xf01c9c65 in ufs_vnoperate (ap=0xf3707e2c) at ../../ufs/ufs/ufs_vnops.c:2234 #10 0xf01502b5 in vn_open (ndp=0xf3707f00, fmode=1539, cmode=384) at vnode_if.h:83 #11 0xf014cd8b in open (p=0xf35fb2c0, uap=0xf3707f94) at ../../kern/vfs_syscalls.c:893 #12 0xf01ed8bf in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 2216864, tf_esi = 384, tf_ebp = 1964888, tf_isp = -210731036, tf_ebx = 271327328, tf_edx = 12, tf_ecx = 608680, tf_eax = 5, tf_trapno = 12, tf_err = 7, tf_eip = 273205361, tf_cs = 31, tf_eflags = 534, tf_esp = 1964868, tf_ss = 39}) at ../../i386/i386/trap.c:994 #13 0x1048c871 in ?? () #14 0x10207510 in ?? () #15 0x13c76 in ?? () #16 0x134fe in ?? () #17 0x10df4 in ?? () #18 0x10aac in ?? () #19 0x102aad58 in ?? () #20 0x102aab6a in ?? () #21 0xefbfdcb0 in ?? () #22 0xf7fe0 in ?? () Cannot access memory at address 0x36000. (kgdb) quit -------------------------------------------------------------------------- machine "i386" ident MORDRED maxusers 10 config kernel root on wd0s2a cpu "I586_CPU" # aka Pentium(tm) options "MAXDSIZ=(256*1024*1024)" options "DFLDSIZ=(256*1024*1024)" options "COMPAT_43" options SYSVSHM options SYSVSEM options SYSVMSG options "MD5" options DDB options DDB_UNATTENDED options KTRACE #kernel tracing options DIAGNOSTIC options PERFMON options UCONSOLE options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INET #Internet communications protocols pseudo-device loop pseudo-device ether #Generic Ethernet pseudo-device bpfilter 4 #Berkeley packet filter options MROUTING # Multicast routing options FFS #Fast filesystem options NFS #NFS #options NFS_NOSERVER options MFS #Memory filesystem options "CD9660" #ISO 9660 filesystem options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options NSWAPDEV=20 options "CD9660_ROOTDELAY=20" #options SOFTUPDATES pseudo-device pty 16 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) controller isa0 options BOUNCE_BUFFERS # The syscons console driver (sco color console compatible) - default. device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=16 # number of virtual consoles #options SLOW_VGA # do byte-wide i/o's to TS and GDC regs device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xe0ffe0ff vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr options ATAPI #Enable ATAPI support for IDE bus #options ATAPI_STATIC #Don't do it as an LKM #device wcd0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device ed0 at isa? port 0x280 net irq 10 iomem 0xcc000 vector edintr # controller snd0 # device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr # device sbxvi0 at isa? drq 5 # device sbmidi0 at isa? port 0x300 # device opl0 at isa? port 0x388 controller pnp0 device pcm0 at isa? port? tty irq 5 drq 1 flags 0x0015 vector pcmintr # options APM_IDLE_CPU # Tell APM to idle rather than halt'ing the cpu # device apm0 at isa? # options APM_BROKEN_STATCLOCK device joy0 at isa? port "IO_GAME" controller pci0 options CLK_CALIBRATION_LOOP options "CLK_USE_I8254_CALIBRATION" options CLK_USE_TSC_CALIBRATION options NMBCLUSTERS=512 options NBUF=512 options COMPAT_LINUX options "EXT2FS" options KBD_MAXRETRY=4 options KBD_MAXWAIT=6 options KBD_RESETDELAY=201 options KBDIO_DEBUG=0 options MSGMNB=2049 options MSGMNI=41 options MSGSEG=2049 options MSGSSZ=16 options MSGTQL=41 options SEMMAP=31 options SEMMNI=11 options SEMMNS=61 options SEMMNU=31 options SEMMSL=61 options SEMOPM=101 options SEMUME=11 options SHOW_BUSYBUFS # List buffers that prevent root unmount options SHMALL=1025 options "SHMMAX=(SHMMAXPGS*PAGE_SIZE+1)" options SHMMAXPGS=1025 options SHMMIN=2 options SHMMNI=33 options SHMSEG=9 -------------------------------------------------------------------------- Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sun Mar 15 21:26:11 PST 1998 root@mordred.cs.ucla.edu:/usr/src/sys/compile/MORDRED Timecounter "i8254" frequency 1193172 Hz cost 2861 ns Timecounter "TSC" frequency 99714871 Hz cost 320 ns CPU: Pentium (99.71-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 50331648 (49152K bytes) avail memory = 37388288 (36512K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.7.0 vga0: rev 0x03 int a irq 11 on pci0.15.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 maddr 0xcc000 msize 16384 on isa ed0: address 00:00:c0:86:e3:b7, type SMC8216/SMC8216C (16 bit) 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 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pcm0 at 0x220 irq 5 drq 1 flags 0x15 on isa wdc0 at 0x1f0-0x1f7 irq 14 flags 0xe0ffe0ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-8, sleep-hack wd0: 1039MB (2128896 sectors), 2112 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , 32-bit, multi-block-16, sleep-hack wd1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface joy0 at 0x201 on isa joy0: joystick Intel Pentium F00F detected, installing workaround WARNING: / was not properly dismounted. Start pid=2 Start pid=3 Start pid=4 ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 12:42:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17610 for freebsd-current-outgoing; Mon, 16 Mar 1998 12:42:52 -0800 (PST) (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 MAA17586 for ; Mon, 16 Mar 1998 12:42:49 -0800 (PST) (envelope-from karl@Mercury.mcs.net) Received: from Mercury.mcs.net (karl@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id OAA00440; Mon, 16 Mar 1998 14:42:49 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id OAA23209; Mon, 16 Mar 1998 14:42:48 -0600 (CST) Message-ID: <19980316144248.56518@mcs.net> Date: Mon, 16 Mar 1998 14:42:48 -0600 From: Karl Denninger To: Sir Mordred Cc: freebsd-current@FreeBSD.ORG Subject: Re: softupdate panic References: <199803162028.MAA00664@mordred.cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199803162028.MAA00664@mordred.cs.ucla.edu>; from Sir Mordred on Mon, Mar 16, 1998 at 12:28:48PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Make sure you have all the patches. I haven't seen a spurious Sig11 since I applied them. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Mon, Mar 16, 1998 at 12:28:48PM -0800, Sir Mordred wrote: > >From a kernel which was cvsup'd last night. This appears to happen > when under load. I won't discount bad memory on my machine, but it's > hard to tell... > > Also, FWIW, the new VM patches from last night: I still end up getting > the occaisional spurious sig 11's on sendmail and cron. Restarting the > daemons appears to make them go away -- which diminishes my suspicions > of memory hardware problems. No panics in VM code, though, which is a > good thing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 14:06:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07958 for freebsd-current-outgoing; Mon, 16 Mar 1998 14:06:04 -0800 (PST) (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 OAA07899 for ; Mon, 16 Mar 1998 14:05:57 -0800 (PST) (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 RAA16288 for ; Mon, 16 Mar 1998 17:04:56 -0500 (EST) X-Sender: ckempfm@enigami.com Message-Id: In-Reply-To: References: <199803161138.GAA25161@web03.globecomm.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Mar 1998 16:55:20 -0500 To: freebsd-current@FreeBSD.ORG From: Cory Kempf Subject: Compilers: 2.8.1 v 2.7.2.1? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, dumb question time: In the current system, in the /usr/ports directory, exists gcc 2.8.1. Under /usr/src, is 2.7.2.1, which seems to be built and installed as part of make world. In that this is -current we are talking about, why is -current still using the older compiler? +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 Mon Mar 16 14:40:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16259 for freebsd-current-outgoing; Mon, 16 Mar 1998 14:40:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16219 for ; Mon, 16 Mar 1998 14:40:06 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.8.8/8.8.5) id OAA00589; Mon, 16 Mar 1998 14:43:01 -0800 (PST) From: Steve Kargl Message-Id: <199803162243.OAA00589@troutmask.apl.washington.edu> Subject: Re: Compilers: 2.8.1 v 2.7.2.1? In-Reply-To: from Cory Kempf at "Mar 16, 98 04:55:20 pm" To: ckempf@enigami.com (Cory Kempf) Date: Mon, 16 Mar 1998 14:43:01 -0800 (PST) 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 According to Cory Kempf: > OK, dumb question time: > > In the current system, in the /usr/ports directory, exists gcc 2.8.1. > Under /usr/src, is 2.7.2.1, which seems to be built and installed as part > of make world. > > In that this is -current we are talking about, why is -current still using > the older compiler? > FreeBSD-current is on the bleeding edge not the edge of insanity ;-) gcc is too crucial to haphazardly upgrade until its stability is well understood. Since 2.8.1 has only been out for a few weeks, I wouldn't look for an update to occur any time soon. (I could be wrong, Peter, jdp?) As a point in case, 2.8.1 appeared with a week or two of 2.8.0. Additionally, if I understand the situation, 2.8.1 probably does not contain the necesssary files to compile a.out format. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 15:09:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22757 for freebsd-current-outgoing; Mon, 16 Mar 1998 15:09:33 -0800 (PST) (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 PAA22745; Mon, 16 Mar 1998 15:09:26 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.7/8.8.7) with ESMTP id XAA11204; Mon, 16 Mar 1998 23:09:04 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199803162309.XAA11204@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: dmaddox@scsn.net cc: joelh@gnu.org, freebsd-current@FreeBSD.ORG, Jordan Hubbard Subject: Re: Odd libalias problem - resolved In-reply-to: Your message of "Sun, 15 Mar 1998 19:58:41 GMT." <19980315195841.18574@scsn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Mar 1998 23:09:03 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm scratching it up to the full moon that hit during the 'make > > world', but am documenting it (by writing this message) in case > > somebody else has similar problems. > > Well, for what it's worth, I've had exactly the same experience over > the last two 'make world's I've done... The 'ppp' built during the make > world doesn't like libalias, but rebuild it alone and it works fine :-/ > > Maybe something got screwed around in the build order? Aliasing is disabled for the boot floppy - it looks like I've got things wrong :-( I was under the impression that release built the DES & NON-DES binaries, then built the crunch stuff. I guess from the above, the final installed version is the crunch version (at least partially) :-( Would someone be able to test this patch (in /usr/src/release) to see if it makes things any better ? I'm not able to build a release at the moment :-| TIA. Index: Makefile =================================================================== RCS file: /home/ncvs/src/release/Makefile,v retrieving revision 1.345 diff -u -r1.345 Makefile --- Makefile 1998/03/10 17:29:44 1.345 +++ Makefile 1998/03/16 23:06:22 @@ -298,6 +298,9 @@ ${MAKE} -DRELEASE_CRUNCH -f $${j}_crunch.mk subclean all \ NOCRYPT=yes "CFLAGS=${CFLAGS} -DCRUNCHED_BINARY") && \ mv $${j}_crunch/$${j}_crunch ${RD}/crunch/$${j} && \ + ( cd $${j}_crunch && \ + ${MAKE} -DRELEASE_CRUNCH -f $${j}_crunch.mk subclean \ + NOCRYPT=yes "CFLAGS=${CFLAGS} -DCRUNCHED_BINARY" ) && \ true || { rm -rf $${j}_crunch ; false ; } ; \ done touch release.4 -- 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 Mon Mar 16 15:12:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23659 for freebsd-current-outgoing; Mon, 16 Mar 1998 15:12:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23619 for ; Mon, 16 Mar 1998 15:12:21 -0800 (PST) (envelope-from max@ludd.luth.se) Received: from taurus.ludd.luth.se (max@taurus.ludd.luth.se [130.240.16.37]) by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id AAA27425 for ; Tue, 17 Mar 1998 00:12:17 +0100 Received: (max@localhost) by taurus.ludd.luth.se (8.6.11/8.6.11) id AAA02394; Tue, 17 Mar 1998 00:12:23 +0100 Message-ID: <19980317001222.23910@taurus.ludd.luth.se> Date: Tue, 17 Mar 1998 00:12:22 +0100 From: Max Nilsson To: freebsd-current@FreeBSD.ORG Subject: Am I using a SCSI tape-device as root file system ? :-) Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.81e Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. My new current-kernel is drunk. cvsup:ed on Tue Mar 16 1998. 'dmesg' tells me the following: npx0 on motherboard npx0: INT 16 interface changing root device to st1s1a ^^^^^^ I did not know that you can use a tape-device as root file-system. :) And I did not know that you can have partition-slices on a tape. :-) /Max -- Max Nilsson E-mail: max@ludd.luth.se -- -- Vänortsvägen 5 Tele: +46-(0)920-94202 -- -- 977 54 Luleå @home: homer.campus.luth.se -- -- Sweden -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 16:54:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01412 for freebsd-current-outgoing; Mon, 16 Mar 1998 16:54:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from VMSD.CSD.MU.EDU (vmsd.csd.mu.edu [134.48.20.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01373 for ; Mon, 16 Mar 1998 16:54:19 -0800 (PST) (envelope-from 4wg7kolodzie@vmsb.csd.mu.edu) Received: from vms.csd.mu.edu ([134.48.208.1]) by vms.csd.mu.edu (PMDF V5.1-9 #27588) with ESMTP id <01IUQTBA1P0207IWSP@vms.csd.mu.edu> for freebsd-current@freebsd.org; Mon, 16 Mar 1998 18:53:52 CST Date: Mon, 16 Mar 1998 18:50:40 -0600 From: Justin A Kolodziej <4wg7kolodzie@vmsb.csd.mu.edu> Subject: Slow CPU To: freebsd-current@FreeBSD.ORG Message-id: <350DC8E0.190A4122@vms.csd.mu.edu> Organization: Marquette University MIME-version: 1.0 X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-980315-SNAP i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got the slowest Pentium Pro ever! Check out the dmesg output: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-980315-SNAP #0: Mon Mar 16 18:39:07 CST 1998 root@mcd7-31.mccormick.mu.edu:/usr/src/sys/compile/MINE Timecounter "i8254" frequency 1193182 Hz cost 3948 ns CPU: Pentium Pro (0.00-MHz 686-class CPU) ^^^^^^^^ Origin = "GenuineIntel" Id = 0x617 Stepping=7 Features=0xf9ff Yet afterstep doesn't seem slow at all ;-) Justin K. -- I sense a great disturbance in the SOurce. Justin A. Kolodziej 4wg7kolodzie@vms.csd.mu.edu Marquette University is http://www.mu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 18:37:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25890 for freebsd-current-outgoing; Mon, 16 Mar 1998 18:37:08 -0800 (PST) (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 SAA25881 for ; Mon, 16 Mar 1998 18:37:06 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id TAA18526; Mon, 16 Mar 1998 19:37:02 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd018502; Mon Mar 16 19:36:59 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id TAA29018; Mon, 16 Mar 1998 19:36:56 -0700 (MST) From: Terry Lambert Message-Id: <199803170236.TAA29018@usr06.primenet.com> Subject: Re: Compilers: 2.8.1 v 2.7.2.1? To: sgk@troutmask.apl.washington.edu (Steve Kargl) Date: Tue, 17 Mar 1998 02:36:56 +0000 (GMT) Cc: ckempf@enigami.com, freebsd-current@FreeBSD.ORG In-Reply-To: <199803162243.OAA00589@troutmask.apl.washington.edu> from "Steve Kargl" at Mar 16, 98 02:43:01 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 > gcc is too crucial to haphazardly upgrade until its stability is well > understood. Since 2.8.1 has only been out for a few weeks, I wouldn't > look for an update to occur any time soon. (I could be wrong, Peter, jdp?) > As a point in case, 2.8.1 appeared with a week or two of 2.8.0. > > Additionally, if I understand the situation, 2.8.1 probably does not > contain the necesssary files to compile a.out format. Bullocks. 8-). The a.out problems are that you can't make a.out using the FSF binutils, not that you can't make a.out with the FreeBSD ld program *not* from binutils. Exceptions will not work with pthreads unless you are running 2.8.x g++ or better. This is as good a reason as any The compiler should be upgraded, but the ld should be the FreeBSD one, and the binutils should go into the other directory (they are needed for ELF, but won't work for a.out, unless someone adds FreeBSD a.out support to the binutils version of the code. 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 Mar 16 18:55:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29558 for freebsd-current-outgoing; Mon, 16 Mar 1998 18:55:39 -0800 (PST) (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 SAA29552 for ; Mon, 16 Mar 1998 18:55:35 -0800 (PST) (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 VAA17258; Mon, 16 Mar 1998 21:54:21 -0500 (EST) X-Sender: ckempfm@enigami.com Message-Id: In-Reply-To: <199803150448.UAA09479@dingo.cdrom.com> References: Your message of "Sat, 14 Mar 1998 12:36:36 EST." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Mar 1998 21:44:33 -0500 To: Mike Smith From: Cory Kempf Subject: Re: Today's kernel doesn't work on (my) DK440LX Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 23:48 -0500 98.03.14, Mike Smith wrote: >> Hi all, >> I had a (mostly) working kernel based on 10 March sources. Today, 'round 2 >> PM EST, I sup'd again, and built the world. >> >> I can no longer build a (mostly) working kernel. Well, actually, I can... it just complains. I took the complaint as an error, instead of continuing. Turns out that is still builds OK (after fixing a minor CAM bug) >> My system seems to be dependent on the line: >> >> config kernel root on da0 swap on generic > >The 'generic' keyword causes a search for suitable devices. Because >the bootstrap doesn't recognise the 'da' device, it passes 0 in as the >boot major. So, what should I use for the device? And (more importantly) where do I find this stuff out? If I try sd0 as the device, config returns that it is unrecognized. After booting, / is mounted on /dev/da0a, which has a major device number of 4 and a minor device number of 0. Perhaps da4a will work... >The kernel recently started trusting this value; you will need to extend >the bootstrap so that it supplies it correctly. Uh, how do I do that? For that matter, what does that mean? >> In my kernel config file. Especially the 'swap on generic' part. If I >> take it out, or replace it with anything I have tried so far, my kernel >> doesn't work at all. If I attempt to boot, the system attempts to change >> root to wd0s2b, and I get a Fatal Trap 12. Doing a trace says that it is >> happening in _ffs_mount(). > >This is probably because the disk type on your disk is incorrect. What >does 'disklabel' say about your boot disk? # /dev/rda0a: type: ESDI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 521 sectors/unit: 8385867 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 65536 0 4.2BSD 0 0 0 # (Cyl. 0 - 4*) b: 544480 65536 swap # (Cyl. 4*- 37*) c: 8385867 0 unused 0 0 # (Cyl. 0 - 521*) e: 61440 610016 4.2BSD 0 0 0 # (Cyl. 37*- 41*) f: 7714411 671456 4.2BSD 0 0 0 # (Cyl. 41*- 521*) It lies: The disk is a SCSI device and the RPM is 10,000. >> Perhaps I am looking in the wrong places, but I can't seem to find any >> documentation as to what "swap on generic" means and what I should replace >> it with. > >It's not normally useful, and shouldn't normally be there. It can help >in situation such as yours. Clearly, what I am doing is not correct. I am wondering what I should be doing instead. +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 Mon Mar 16 19:49:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07490 for freebsd-current-outgoing; Mon, 16 Mar 1998 19:49:23 -0800 (PST) (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 TAA07484 for ; Mon, 16 Mar 1998 19:49:20 -0800 (PST) (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 XAA04448; Mon, 16 Mar 1998 23:51:07 GMT Message-ID: <00fe01bd5157$3e3c8480$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: "Justin A Kolodziej" <4wg7kolodzie@vmsb.csd.mu.edu>, Subject: Re: Slow CPU Date: Mon, 16 Mar 1998 22:46:17 -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 APM does this last i heard... disable APM and you shouldn't have to worry. it shouldn't affect anything desides the dmesg anyhow. (btw, this issue has come up like 10 times in the last 2 weeks) -Alfred -----Original Message----- From: Justin A Kolodziej <4wg7kolodzie@vmsb.csd.mu.edu> To: freebsd-current@FreeBSD.ORG Date: Monday, March 16, 1998 3:58 PM Subject: Slow CPU >I've got the slowest Pentium Pro ever! Check out the dmesg output: >Copyright (c) 1992-1998 FreeBSD Inc. >Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights >reserved. >FreeBSD 3.0-980315-SNAP #0: Mon Mar 16 18:39:07 CST 1998 > root@mcd7-31.mccormick.mu.edu:/usr/src/sys/compile/MINE >Timecounter "i8254" frequency 1193182 Hz cost 3948 ns >CPU: Pentium Pro (0.00-MHz 686-class CPU) > ^^^^^^^^ >Origin = "GenuineIntel" Id = 0x617 Stepping=7 > >Features=0xf9ff > >Yet afterstep doesn't seem slow at all ;-) > >Justin K. >-- >I sense a great disturbance in the SOurce. >Justin A. Kolodziej >4wg7kolodzie@vms.csd.mu.edu >Marquette University is http://www.mu.edu > >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 Mar 16 19:51:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08303 for freebsd-current-outgoing; Mon, 16 Mar 1998 19:51:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cuervo.atl.netchannel.net (firewall-user@cuervo.netchannel.net [205.229.200.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA08246 for ; Mon, 16 Mar 1998 19:51:43 -0800 (PST) (envelope-from rbolin@netchannel.net) Received: by cuervo.atl.netchannel.net; id WAA14934; Mon, 16 Mar 1998 22:38:28 -0500 Received: from hermes.atl.netchannel.net(172.30.5.22) by cuervo.atl.netchannel.net via smap (3.2) id xma014928; Mon, 16 Mar 98 22:38:20 -0500 Received: from 207.205.32.104 by hermes.atl.netchannel.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1458.49) id GYBXQ0DG; Mon, 16 Mar 1998 22:58:47 -0500 Message-ID: <350DF33A.FE83BB4@netchannel.net> Date: Mon, 16 Mar 1998 22:51:22 -0500 From: Ron Bolin X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.6 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: Current Signal 11 Crazy Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After running the 3-11-98 current without any problems I cvsup yesterday and tonight 18:00 EDT and cannot use the system. All I get is sig 11 and core dumps on "ps", "fsck", "vi", "reboot", and lots of other commands. Is anyone else experiencing this? What changed? I did a buildworld, built the kernel installed the kernel, booted single user, did a make installworld (lkms were installed). Still can't use the system with tonights current. Thanks Ron -- ------------------------------------------------------------------------------- E-mail: rbolin@netchannel.net Web: http://www.gsu.edu/~gs01rlb Ph: 770-729-2929 Ext 249 Hm: 770-992-6875 Web: http://www.mindspring.com/~rlb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 19:58:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09393 for freebsd-current-outgoing; Mon, 16 Mar 1998 19:58:24 -0800 (PST) (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 TAA09380 for ; Mon, 16 Mar 1998 19:58:20 -0800 (PST) (envelope-from karl@Mercury.mcs.net) Received: from Mercury.mcs.net (karl@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id VAA23767; Mon, 16 Mar 1998 21:58:19 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id VAA03112; Mon, 16 Mar 1998 21:58:19 -0600 (CST) Message-ID: <19980316215819.34709@mcs.net> Date: Mon, 16 Mar 1998 21:58:19 -0600 From: Karl Denninger To: Ron Bolin Cc: FreeBSD Current Mailing List Subject: Re: Current Signal 11 Crazy References: <350DF33A.FE83BB4@netchannel.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <350DF33A.FE83BB4@netchannel.net>; from Ron Bolin on Mon, Mar 16, 1998 at 10:51:22PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Something has gone drastically wrong today; I am seeing both problems with signals as well as both spontaneous reboots (with no core dump!) and hard freezes (which ignore a drop-to-DDB - argh!) as well. It looks like a couple of changes were committed after Dyson's last-night update in the kernel source tree. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Mon, Mar 16, 1998 at 10:51:22PM -0500, Ron Bolin wrote: > After running the 3-11-98 current without any problems I cvsup > yesterday and tonight 18:00 EDT and cannot use the system. All I get > is sig 11 and core dumps on "ps", "fsck", "vi", "reboot", and lots of > other commands. > > Is anyone else experiencing this? What changed? I did a buildworld, > built the kernel > installed the kernel, booted single user, did a make installworld (lkms > were installed). > Still can't use the system with tonights current. > > Thanks > > Ron > > -- > ------------------------------------------------------------------------------- > E-mail: rbolin@netchannel.net Web: http://www.gsu.edu/~gs01rlb > Ph: 770-729-2929 Ext 249 Hm: 770-992-6875 Web: http://www.mindspring.com/~rlb > > > > > 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 Mar 16 20:13:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12364 for freebsd-current-outgoing; Mon, 16 Mar 1998 20:13:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12348 for ; Mon, 16 Mar 1998 20:13:38 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA27158; Tue, 17 Mar 1998 15:06:43 +1100 Date: Tue, 17 Mar 1998 15:06:43 +1100 From: Bruce Evans Message-Id: <199803170406.PAA27158@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org Subject: Re: make/SIGINT (Re: cvs commit: src/bin/sh jobs.c) Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I found another problem: time(1) has much the same problem as make(1) >[...] >> #!/bin/sh >> time make foo >> echo $? >> time make bar >> echo $? >> >> Now `time' exits normally with status 1, so our modified sh continues. > >I finally get used to this kind of stuff :-), proposed patch appended. :-). truss(1) has much the same problem as make(1). ktrace(1) works right (not surprising - it doesn't fork). Under Linux, time(1) and strace(1) have much the same problem... Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 20:53:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19557 for freebsd-current-outgoing; Mon, 16 Mar 1998 20:53:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19531 for ; Mon, 16 Mar 1998 20:53:13 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.8.8/8.8.5) id UAA01121; Mon, 16 Mar 1998 20:56:10 -0800 (PST) From: Steve Kargl Message-Id: <199803170456.UAA01121@troutmask.apl.washington.edu> Subject: Re: Compilers: 2.8.1 v 2.7.2.1? In-Reply-To: <199803170236.TAA29018@usr06.primenet.com> from Terry Lambert at "Mar 17, 98 02:36:56 am" To: tlambert@primenet.com (Terry Lambert) Date: Mon, 16 Mar 1998 20:56:10 -0800 (PST) Cc: ckempf@enigami.com, 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 According to Terry Lambert: > > gcc is too crucial to haphazardly upgrade until its stability is well > > understood. Since 2.8.1 has only been out for a few weeks, I wouldn't > > look for an update to occur any time soon. (I could be wrong, Peter, jdp?) > > As a point in case, 2.8.1 appeared with a week or two of 2.8.0. > > > > Additionally, if I understand the situation, 2.8.1 probably does not > > contain the necesssary files to compile a.out format. > > Bullocks. 8-). The a.out problems are that you can't make a.out > using the FSF binutils, not that you can't make a.out with the > FreeBSD ld program *not* from binutils. Mea Culpa! I hate spreading misinformation. Yes, I confused the binutil issues with gcc 2.8.1. However, my 1st paragraph above still stands (i.e., newest isn't always the best). > Exceptions will not work with pthreads unless you are running 2.8.x > g++ or better. This is as good a reason as any FWIW, I've been using egcs-1.0.x for testing g77. On my simple, real-world benchmark (my code :-), g77 is giving about a 22% increase in execution speed over f77 (f2c+gcc). Hopefully, whne the next gcc upgrade is merged into -current, g77 will be brought into the tree. (Hint, hint). > The compiler should be upgraded, but the ld should be the FreeBSD one, > and the binutils should go into the other directory (they are needed > for ELF, but won't work for a.out, unless someone adds FreeBSD a.out > support to the binutils version of the code. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 21:32:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25905 for freebsd-current-outgoing; Mon, 16 Mar 1998 21:32:02 -0800 (PST) (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 VAA25859; Mon, 16 Mar 1998 21:31:56 -0800 (PST) (envelope-from karl@Mercury.mcs.net) Received: from Mercury.mcs.net (karl@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id XAA28077; Mon, 16 Mar 1998 23:31:55 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id XAA04330; Mon, 16 Mar 1998 23:31:54 -0600 (CST) Message-ID: <19980316233154.11422@mcs.net> Date: Mon, 16 Mar 1998 23:31:54 -0600 From: Karl Denninger To: current@FreeBSD.ORG Cc: dyson@FreeBSD.ORG Subject: Oh oh... big trouble in little China with -CURRENT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mar 16 23:17:37 Codebase /kernel: spec_getpages: preposterous offset 0xffffff7d7 c01f400 Mar 16 23:17:37 Codebase /kernel: vm_fault: pager input (probably hardware) erro r, PID 29201 failure Mar 16 23:17:37 Codebase /kernel: spec_getpages: preposterous offset 0xffffff7d7 c01f400 Mar 16 23:17:37 Codebase /kernel: vm_fault: pager input (probably hardware) erro r, PID 29201 failure Mar 16 23:17:37 Codebase /kernel: pid 29201 (ls), uid 0: exited on signal 11 Mar 16 23:17:37 Codebase /kernel: spec_getpages: preposterous offset 0xffffff7d7 c01f400 Mar 16 23:17:37 Codebase /kernel: vm_fault: pager input (probably hardware) erro r, PID 29199 failure Mar 16 23:17:37 Codebase /kernel: spec_getpages: preposterous offset 0xffffff7d7 c01f400 Mar 16 23:17:38 Codebase /kernel: vm_fault: pager input (probably hardware) erro r, PID 29199 failure Mar 16 23:17:38 Codebase /kernel: pid 29199 (ls), uid 0: exited on signal 11 Mar 16 23:17:38 Codebase /kernel: spec_getpages: preposterous offset 0xffffff7d7 c01f400 Mar 16 23:17:38 Codebase /kernel: vm_fault: pager input (probably hardware) erro r, PID 29219 failure Mar 16 23:17:38 Codebase /kernel: spec_getpages: preposterous offset 0xffffff7d7 c01f400 Mar 16 23:17:38 Codebase /kernel: vm_fault: pager input (probably hardware) erro r, PID 29219 failure Mar 16 23:17:38 Codebase /kernel: pid 29219 (ls), uid 0: exited on signal 11 Mar 16 23:17:38 Codebase /kernel: spec_getpages: preposterous offset 0xffffff7d7 c01f400 Mar 16 23:17:38 Codebase /kernel: vm_fault: pager input (probably hardware) erro r, PID 29217 failure Mar 16 23:17:38 Codebase /kernel: spec_getpages: preposterous offset 0xffffff7d7 c01f400 Mar 16 23:17:38 Codebase /kernel: vm_fault: pager input (probably hardware) erro r, PID 29217 failure M And a bunch more. This is off a truly -CURRENT kernel (built about an hour ago). Whatever was done with the latest patches, it made the situation worse, not better. Note that this is a system that is all local disks.... (no NFSisms involved). Oh John, Oh John, what did you persecute in the source tree? :-) -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 21:41:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27508 for freebsd-current-outgoing; Mon, 16 Mar 1998 21:41:55 -0800 (PST) (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 VAA27487 for ; Mon, 16 Mar 1998 21:41:51 -0800 (PST) (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 FAA08882; Tue, 17 Mar 1998 05:40:57 GMT Date: Tue, 17 Mar 1998 14:40:57 +0900 (JST) From: Michael Hancock To: Tor Egge cc: freebsd-current@FreeBSD.ORG Subject: Re: 4 WILLRELE's to bite the dust In-Reply-To: <199803131845.TAA26656@pat.idi.ntnu.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 Mar 1998, Tor Egge wrote: > - freeing of resources. When the file is unlinked, the > lower vnode still has a reference from the upper vnode > which is left until the upper vnode is recycled. Currently > null_inactive calls VOP_INACTIVE on the lower vnode. > This is wrong (e.g. a process directly accessing the lower > vnode will see a truncated file, which is an unintended > side effect). > > Symptom: Removing a file that has been opend via nullfs > will not necessarily free the space on the file system > before the null vnode is recycled. So did you delete VOP_INACTIVE(lowervp) from null_inactive and move the vrele to null_inactive from null_reclaim to fix this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 21:48:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29051 for freebsd-current-outgoing; Mon, 16 Mar 1998 21:48:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29036 for ; Mon, 16 Mar 1998 21:48:36 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id VAA07122; Mon, 16 Mar 1998 21:48:33 -0800 (PST) (envelope-from jdp) Message-Id: <199803170548.VAA07122@austin.polstra.com> To: sgk@troutmask.apl.washington.edu Subject: Re: Compilers: 2.8.1 v 2.7.2.1? In-Reply-To: <199803162243.OAA00589@troutmask.apl.washington.edu> References: <199803162243.OAA00589@troutmask.apl.washington.edu> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Mon, 16 Mar 1998 21:48:33 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199803162243.OAA00589@troutmask.apl.washington.edu>, Steve Kargl wrote: > According to Cory Kempf: > > In that this is -current we are talking about, why is -current still using > > the older compiler? > > > > FreeBSD-current is on the bleeding edge not the edge of insanity ;-) Thank you. That was very well put. :-) > gcc is too crucial to haphazardly upgrade until its stability is well > understood. Since 2.8.1 has only been out for a few weeks, I wouldn't > look for an update to occur any time soon. (I could be wrong, Peter, jdp?) No, you are not wrong. We don't leap over each new compiler cliff as soon as it comes along. We let the Linux lemmi^H^H^H^H^Hfolks jump first, and then we count the bodies. :-) Those of you who want cutting edge know where to find it -- in the ports collection. > Additionally, if I understand the situation, 2.8.1 probably does not > contain the necesssary files to compile a.out format. We always have to make some local changes, but that's not what's holding us back. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 21:49:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29333 for freebsd-current-outgoing; Mon, 16 Mar 1998 21:49:31 -0800 (PST) (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 VAA29289; Mon, 16 Mar 1998 21:49:22 -0800 (PST) (envelope-from karl@Mercury.mcs.net) Received: from Mercury.mcs.net (karl@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id XAA28510; Mon, 16 Mar 1998 23:49:21 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id XAA04580; Mon, 16 Mar 1998 23:49:21 -0600 (CST) Message-ID: <19980316234921.07586@mcs.net> Date: Mon, 16 Mar 1998 23:49:21 -0600 From: Karl Denninger To: current@FreeBSD.ORG Cc: dyson@FreeBSD.ORG Subject: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ************ URGENT ************** I strongly advise that you *DO NOT* use -CURRENT as it sits at the present time. The kernel you build may do SEVERE damage to your filesystems. I am working on finding the commit which is causing this and will post to the list as soon as I have identified it. This is not a trivial matter. It is a very good thing indeed that I use a scratch disk for my /usr/obj area, or I would be really rather upset. :-) The symptoms are random core dumps and other problems - but the underlying reason is that the filesystem has been trashed beyond belief! I unmounted the disk in question CLEANLY and found both partially truncated and duplicate inodes all over it, along with severe internal file damage. I suspect the commit today in kern/vfs_cluster.c, as that's the only filesystem or VM related commit that my first-level examination has found. I am backing that out locally right now and will advise if it makes the problem go away. Note that kernels built LAST NIGHT (3/15) at about 23:00 *do not* exhibit the problem. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 21:56:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01241 for freebsd-current-outgoing; Mon, 16 Mar 1998 21:56:36 -0800 (PST) (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 VAA01235; Mon, 16 Mar 1998 21:56:32 -0800 (PST) (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 FAA08990; Tue, 17 Mar 1998 05:55:42 GMT Date: Tue, 17 Mar 1998 14:55:42 +0900 (JST) From: Michael Hancock To: Karl Denninger cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-Reply-To: <19980316234921.07586@mcs.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 Is it possible that the previous kernel quietly trashed your disks and it didn't manifest itself until after the last vm fix commit? Regards, Mike Hancock On Mon, 16 Mar 1998, Karl Denninger wrote: > ************ URGENT ************** > > I strongly advise that you *DO NOT* use -CURRENT as it sits at the > present time. > > The kernel you build may do SEVERE damage to your filesystems. > > I am working on finding the commit which is causing this and will post to > the list as soon as I have identified it. > > This is not a trivial matter. It is a very good thing indeed that I use a > scratch disk for my /usr/obj area, or I would be really rather upset. :-) > > The symptoms are random core dumps and other problems - but the underlying > reason is that the filesystem has been trashed beyond belief! > > I unmounted the disk in question CLEANLY and found both partially truncated > and duplicate inodes all over it, along with severe internal file damage. > > I suspect the commit today in kern/vfs_cluster.c, as that's the only > filesystem or VM related commit that my first-level examination has found. > I am backing that out locally right now and will advise if it makes the > problem go away. > > Note that kernels built LAST NIGHT (3/15) at about 23:00 *do not* exhibit > the problem. > > -- > -- > Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin > http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV > | NEW! Corporate ISDN Prices dropped by up to 50%! > Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS > Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- michaelh@cet.co.jp http://www.cet.co.jp CET Inc., Daiichi Kasuya BLDG 8F, 2-5-12 Higashi Shinbashi, Minato-ku, Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 22:06:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03405 for freebsd-current-outgoing; Mon, 16 Mar 1998 22:06:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.91.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03393; Mon, 16 Mar 1998 22:06:38 -0800 (PST) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (8.8.8/8.8.8) with SMTP id BAA00352; Tue, 17 Mar 1998 01:02:01 -0500 (EST) (envelope-from root@danberlin.resnet.rochester.edu) Date: Tue, 17 Mar 1998 01:02:01 -0500 (EST) From: Daniel Berlin To: Michael Hancock cc: Karl Denninger , current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected 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 No no no, haven't you been watching those IBM commercials? It was probably the malicious hackers who can break through routers blocking their packets, cover their tracks and unleash viruses all over your computer in a matter of seconds, unless you are using IBM certified solutions. I bet it was them. Damn hax0rs. But seriously, i have just started to see a couple weird filesystem related things since building a kernel a couple hours ago and rebooting a couple times that weren't happening yesterday. arghghghgh --Dan On Tue, 17 Mar 1998, Michael Hancock wrote: > Is it possible that the previous kernel quietly trashed your disks and it > didn't manifest itself until after the last vm fix commit? > > Regards, > > Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 22:08:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04106 for freebsd-current-outgoing; Mon, 16 Mar 1998 22:08:06 -0800 (PST) (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 WAA04030; Mon, 16 Mar 1998 22:07:58 -0800 (PST) (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (tnt73.wcc.net [208.10.139.73]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id AAA25340; Tue, 17 Mar 1998 00:03:55 -0600 (CST) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id AAA00912; Tue, 17 Mar 1998 00:07:46 -0600 (CST) (envelope-from joelh) Date: Tue, 17 Mar 1998 00:07:46 -0600 (CST) Message-Id: <199803170607.AAA00912@detlev.UUCP> To: dyson@FreeBSD.ORG CC: dyson@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <199803152315.SAA07317@dyson.iquest.net> Subject: Re: Well, more VM/VFS progress made From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199803152315.SAA07317@dyson.iquest.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I am committing some major improvements tonight, hopefully to make >> NFS, and the VFS code in general work correctly. If you have had >> more strange sig-11's than usual, then the stuff going in soon is >> for you!!! > PS. Not ALL NFS bugs are fixed, but will work much better. Yes, all Dyson's bugs are in excellent working order. :-) Seriously, from J. Random User, I am glad to see NFS in so much better shape... particularly since I just decided to start using it... Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 22:09:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04739 for freebsd-current-outgoing; Mon, 16 Mar 1998 22:09:39 -0800 (PST) (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 WAA04721; Mon, 16 Mar 1998 22:09:34 -0800 (PST) (envelope-from karl@Mercury.mcs.net) Received: from Mercury.mcs.net (karl@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id AAA29248; Tue, 17 Mar 1998 00:09:30 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id AAA04837; Tue, 17 Mar 1998 00:09:30 -0600 (CST) Message-ID: <19980317000929.36464@mcs.net> Date: Tue, 17 Mar 1998 00:09:30 -0600 From: Karl Denninger To: Michael Hancock Cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected References: <19980316234921.07586@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Michael Hancock on Tue, Mar 17, 1998 at 02:55:42PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No. I removed the entire source tree and re-extracted it. If that was the problem then there would be errors in the source files - there aren't. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Tue, Mar 17, 1998 at 02:55:42PM +0900, Michael Hancock wrote: > Is it possible that the previous kernel quietly trashed your disks and it > didn't manifest itself until after the last vm fix commit? > > Regards, > > Mike Hancock > > On Mon, 16 Mar 1998, Karl Denninger wrote: > > > ************ URGENT ************** > > > > I strongly advise that you *DO NOT* use -CURRENT as it sits at the > > present time. > > > > The kernel you build may do SEVERE damage to your filesystems. > > > > I am working on finding the commit which is causing this and will post to > > the list as soon as I have identified it. > > > > This is not a trivial matter. It is a very good thing indeed that I use a > > scratch disk for my /usr/obj area, or I would be really rather upset. :-) > > > > The symptoms are random core dumps and other problems - but the underlying > > reason is that the filesystem has been trashed beyond belief! > > > > I unmounted the disk in question CLEANLY and found both partially truncated > > and duplicate inodes all over it, along with severe internal file damage. > > > > I suspect the commit today in kern/vfs_cluster.c, as that's the only > > filesystem or VM related commit that my first-level examination has found. > > I am backing that out locally right now and will advise if it makes the > > problem go away. > > > > Note that kernels built LAST NIGHT (3/15) at about 23:00 *do not* exhibit > > the problem. > > > > -- > > -- > > Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin > > http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV > > | NEW! Corporate ISDN Prices dropped by up to 50%! > > Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS > > Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > michaelh@cet.co.jp http://www.cet.co.jp > CET Inc., Daiichi Kasuya BLDG 8F, 2-5-12 Higashi Shinbashi, Minato-ku, > Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 22:11:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05343 for freebsd-current-outgoing; Mon, 16 Mar 1998 22:11:20 -0800 (PST) (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 WAA05289; Mon, 16 Mar 1998 22:11:09 -0800 (PST) (envelope-from karl@Mercury.mcs.net) Received: from Mercury.mcs.net (karl@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id AAA29361; Tue, 17 Mar 1998 00:11:00 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id AAA04866; Tue, 17 Mar 1998 00:11:00 -0600 (CST) Message-ID: <19980317001100.18078@mcs.net> Date: Tue, 17 Mar 1998 00:11:00 -0600 From: Karl Denninger To: Daniel Berlin Cc: Michael Hancock , current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Daniel Berlin on Tue, Mar 17, 1998 at 01:02:01AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Be VERY careful Dan. Unmount those disks and run a FSCK on them *right now*. The patch to vfs_cluster IS NOT the problem; I backed it out, and the kernel that I built after that still causes trouble. I'm still searching for the root cause of this. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Tue, Mar 17, 1998 at 01:02:01AM -0500, Daniel Berlin wrote: > No no no, haven't you been watching those IBM commercials? > It was probably the malicious hackers who can break through routers > blocking their packets, cover their tracks and unleash viruses all over > your computer in a matter of seconds, unless you are using IBM certified > solutions. > I bet it was them. > Damn hax0rs. > > But seriously, i have just started to see a couple weird filesystem > related things since building a kernel a couple hours ago and rebooting a > couple times that weren't happening yesterday. > arghghghgh > --Dan > On Tue, 17 Mar 1998, Michael Hancock wrote: > > > Is it possible that the previous kernel quietly trashed your disks and it > > didn't manifest itself until after the last vm fix commit? > > > > Regards, > > > > Mike Hancock > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 22:17:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06523 for freebsd-current-outgoing; Mon, 16 Mar 1998 22:17:45 -0800 (PST) (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 WAA06474; Mon, 16 Mar 1998 22:17:28 -0800 (PST) (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 GAA09185; Tue, 17 Mar 1998 06:16:21 GMT Date: Tue, 17 Mar 1998 15:16:20 +0900 (JST) From: Michael Hancock To: Karl Denninger cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-Reply-To: <19980317000929.36464@mcs.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 Did you newfs /usr/obj? On Tue, 17 Mar 1998, Karl Denninger wrote: > No. I removed the entire source tree and re-extracted it. If that was the > problem then there would be errors in the source files - there aren't. > > -- > -- > Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin > http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV > | NEW! Corporate ISDN Prices dropped by up to 50%! > Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS > Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > > On Tue, Mar 17, 1998 at 02:55:42PM +0900, Michael Hancock wrote: > > Is it possible that the previous kernel quietly trashed your disks and it > > didn't manifest itself until after the last vm fix commit? > > > > Regards, > > > > Mike Hancock > > > > On Mon, 16 Mar 1998, Karl Denninger wrote: > > > > > ************ URGENT ************** > > > > > > I strongly advise that you *DO NOT* use -CURRENT as it sits at the > > > present time. > > > > > > The kernel you build may do SEVERE damage to your filesystems. > > > > > > I am working on finding the commit which is causing this and will post to > > > the list as soon as I have identified it. > > > > > > This is not a trivial matter. It is a very good thing indeed that I use a > > > scratch disk for my /usr/obj area, or I would be really rather upset. :-) > > > > > > The symptoms are random core dumps and other problems - but the underlying > > > reason is that the filesystem has been trashed beyond belief! > > > > > > I unmounted the disk in question CLEANLY and found both partially truncated > > > and duplicate inodes all over it, along with severe internal file damage. > > > > > > I suspect the commit today in kern/vfs_cluster.c, as that's the only > > > filesystem or VM related commit that my first-level examination has found. > > > I am backing that out locally right now and will advise if it makes the > > > problem go away. > > > > > > Note that kernels built LAST NIGHT (3/15) at about 23:00 *do not* exhibit > > > the problem. > > > > > > -- > > > -- > > > Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin > > > http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV > > > | NEW! Corporate ISDN Prices dropped by up to 50%! > > > Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS > > > Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > -- > > michaelh@cet.co.jp http://www.cet.co.jp > > CET Inc., Daiichi Kasuya BLDG 8F, 2-5-12 Higashi Shinbashi, Minato-ku, > > Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 > > > -- michaelh@cet.co.jp http://www.cet.co.jp CET Inc., Daiichi Kasuya BLDG 8F, 2-5-12 Higashi Shinbashi, Minato-ku, Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 22:19:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07125 for freebsd-current-outgoing; Mon, 16 Mar 1998 22:19:22 -0800 (PST) (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 WAA07108; Mon, 16 Mar 1998 22:19:11 -0800 (PST) (envelope-from karl@Mercury.mcs.net) Received: from Mercury.mcs.net (karl@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id AAA29786; Tue, 17 Mar 1998 00:19:10 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id AAA04913; Tue, 17 Mar 1998 00:19:10 -0600 (CST) Message-ID: <19980317001910.56629@mcs.net> Date: Tue, 17 Mar 1998 00:19:10 -0600 From: Karl Denninger To: Michael Hancock Cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected References: <19980317000929.36464@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Michael Hancock on Tue, Mar 17, 1998 at 03:16:20PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, and now I've done it twice more while trying to isolate this thing. The corruption comes back within minutes of starting a "make world". -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Tue, Mar 17, 1998 at 03:16:20PM +0900, Michael Hancock wrote: > Did you newfs /usr/obj? > > On Tue, 17 Mar 1998, Karl Denninger wrote: > > > No. I removed the entire source tree and re-extracted it. If that was the > > problem then there would be errors in the source files - there aren't. > > > > -- > > -- >> Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin >> http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV >> | NEW! Corporate ISDN Prices dropped by up to 50%! >> Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS >> Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 22:44:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12081 for freebsd-current-outgoing; Mon, 16 Mar 1998 22:44:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.91.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12069; Mon, 16 Mar 1998 22:44:22 -0800 (PST) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (8.8.8/8.8.8) with SMTP id BAA00717; Tue, 17 Mar 1998 01:39:45 -0500 (EST) (envelope-from root@danberlin.resnet.rochester.edu) Date: Tue, 17 Mar 1998 01:39:45 -0500 (EST) From: Daniel Berlin To: Karl Denninger cc: Michael Hancock , current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-Reply-To: <19980317001100.18078@mcs.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 hehe. Ogg say scratch disk look like man who went scribble scribble with crayon. more like a pocket knife. Interestingly, it's only ONE of my disks that is affected. strange. Too bad FreeBSD doesn't support the Adaptec 3895W That i got for 30 bucks from Onsale (Yes, they sold a $1000+ controller to me for 30 bucks.) --Dan On Tue, 17 Mar 1998, Karl Denninger wrote: > Be VERY careful Dan. > > Unmount those disks and run a FSCK on them *right now*. > > The patch to vfs_cluster IS NOT the problem; I backed it out, and the kernel > that I built after that still causes trouble. > > I'm still searching for the root cause of this. > > -- > -- > Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin > http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV > | NEW! Corporate ISDN Prices dropped by up to 50%! > Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS > Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > > On Tue, Mar 17, 1998 at 01:02:01AM -0500, Daniel Berlin wrote: > > No no no, haven't you been watching those IBM commercials? > > It was probably the malicious hackers who can break through routers > > blocking their packets, cover their tracks and unleash viruses all over > > your computer in a matter of seconds, unless you are using IBM certified > > solutions. > > I bet it was them. > > Damn hax0rs. > > > > But seriously, i have just started to see a couple weird filesystem > > related things since building a kernel a couple hours ago and rebooting a > > couple times that weren't happening yesterday. > > arghghghgh > > --Dan > > On Tue, 17 Mar 1998, Michael Hancock wrote: > > > > > Is it possible that the previous kernel quietly trashed your disks and it > > > didn't manifest itself until after the last vm fix commit? > > > > > > Regards, > > > > > > Mike Hancock > > > > 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 Mar 16 22:54:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14834 for freebsd-current-outgoing; Mon, 16 Mar 1998 22:54:16 -0800 (PST) (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 WAA14816; Mon, 16 Mar 1998 22:54:09 -0800 (PST) (envelope-from karl@Mercury.mcs.net) Received: from Mercury.mcs.net (karl@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id AAA00768; Tue, 17 Mar 1998 00:54:04 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id AAA05176; Tue, 17 Mar 1998 00:54:03 -0600 (CST) Message-ID: <19980317005403.27423@mcs.net> Date: Tue, 17 Mar 1998 00:54:03 -0600 From: Karl Denninger To: Daniel Berlin Cc: Michael Hancock , current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected References: <19980317001100.18078@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Daniel Berlin on Tue, Mar 17, 1998 at 01:39:45AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You're seeing the same thing I am here. -- Karl On Tue, Mar 17, 1998 at 01:39:45AM -0500, Daniel Berlin wrote: > hehe. > Ogg say scratch disk look like man who went scribble scribble with > crayon. > more like a pocket knife. > Interestingly, it's only ONE of my disks that is affected. > strange. > Too bad FreeBSD doesn't support the Adaptec 3895W That i got for 30 bucks > from Onsale (Yes, they sold a $1000+ controller to me for 30 bucks.) > --Dan > > On Tue, 17 Mar 1998, Karl Denninger wrote: > > > Be VERY careful Dan. > > > > Unmount those disks and run a FSCK on them *right now*. > > > > The patch to vfs_cluster IS NOT the problem; I backed it out, and the kernel > > that I built after that still causes trouble. > > > > I'm still searching for the root cause of this. > > > > -- > > -- > > Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin > > http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV > > | NEW! Corporate ISDN Prices dropped by up to 50%! > > Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS > > Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > > > > On Tue, Mar 17, 1998 at 01:02:01AM -0500, Daniel Berlin wrote: > > > No no no, haven't you been watching those IBM commercials? > > > It was probably the malicious hackers who can break through routers > > > blocking their packets, cover their tracks and unleash viruses all over > > > your computer in a matter of seconds, unless you are using IBM certified > > > solutions. > > > I bet it was them. > > > Damn hax0rs. > > > > > > But seriously, i have just started to see a couple weird filesystem > > > related things since building a kernel a couple hours ago and rebooting a > > > couple times that weren't happening yesterday. > > > arghghghgh > > > --Dan > > > On Tue, 17 Mar 1998, Michael Hancock wrote: > > > > > > > Is it possible that the previous kernel quietly trashed your disks and it > > > > didn't manifest itself until after the last vm fix commit? > > > > > > > > Regards, > > > > > > > > Mike Hancock > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 22:58:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15598 for freebsd-current-outgoing; Mon, 16 Mar 1998 22:58:34 -0800 (PST) (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 WAA15589; Mon, 16 Mar 1998 22:58:29 -0800 (PST) (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 GAA09771; Tue, 17 Mar 1998 06:57:39 GMT Date: Tue, 17 Mar 1998 15:57:39 +0900 (JST) From: Michael Hancock To: Karl Denninger cc: Daniel Berlin , current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-Reply-To: <19980317005403.27423@mcs.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 John, Is this what you meant? Mike Index: vfs_bio.c =================================================================== RCS file: /usr/cvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.156 diff -u -r1.156 vfs_bio.c --- vfs_bio.c 1998/03/16 01:55:22 1.156 +++ vfs_bio.c 1998/03/17 06:03:47 @@ -676,7 +676,7 @@ break; } if (bp->b_flags & (B_NOCACHE|B_ERROR)) { - int poffset = foff & PAGE_MASK; + int poffset = poff & PAGE_MASK; int presid = resid > (PAGE_SIZE - poffset) ? (PAGE_SIZE - poffset) : resid; vm_page_set_invalid(m, poffset, presid); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 23:03:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16728 for freebsd-current-outgoing; Mon, 16 Mar 1998 23:03:54 -0800 (PST) (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 XAA16717 for ; Mon, 16 Mar 1998 23:03:46 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id CAA08868 for current@freebsd.org; Tue, 17 Mar 1998 02:03:44 -0500 (EST) (envelope-from toor) Message-Id: <199803170703.CAA08868@dyson.iquest.net> Subject: Disk munging problem with current solved To: current@FreeBSD.ORG Date: Tue, 17 Mar 1998 02:03:44 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@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 I haven't read any emails or complaints yet about filesystem problems, but I know that those who have tried to run -current in the last day or so have had terrible problems. The problems didn't manifest for me until too late, and I ended up with hosed filesystems. The problems were caused by vtruncbuf doing bad things, and I have corrected them as quickly as possible. My machine has been down due to the creeping crud associated with the flaw in the routine. Things are looking much better now (for me at least), and I have committed the fix. -- 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 Mon Mar 16 23:05:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17241 for freebsd-current-outgoing; Mon, 16 Mar 1998 23:05:31 -0800 (PST) (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 XAA17233; Mon, 16 Mar 1998 23:05:27 -0800 (PST) (envelope-from karl@Mercury.mcs.net) Received: from Mercury.mcs.net (karl@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id BAA00912; Tue, 17 Mar 1998 01:05:24 -0600 (CST) Received: (from karl@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id BAA05230; Tue, 17 Mar 1998 01:05:24 -0600 (CST) Message-ID: <19980317010523.23149@mcs.net> Date: Tue, 17 Mar 1998 01:05:23 -0600 From: Karl Denninger To: Daniel Berlin Cc: Michael Hancock , current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected References: <19980317001100.18078@mcs.net> <19980317005403.27423@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980317005403.27423@mcs.net>; from Karl Denninger on Tue, Mar 17, 1998 at 12:54:03AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, now I really don't get it. My "build" machine here has three drives on it. It has had three drives on it for a long, long time. The /usr/obj drive gets severely damaged during a "make world". The others do not. It is almost like /usr/obj is mounted async (but its not) and then the unmount is not sync'ing the disk before it dismounts it. Also, the drive is getting hosed DURING the build, because the cores that I'm getting are clearly due to damaged object files during the link process (I can rebuild the specific directory that faults, and it stops doing it). Also, I got a BUNCH of VM errors earlier this evening. I'm confused. I'm going to try to reproduce this some more - a kernel from last night (~2200), with CAM in it, doesn't produce the seg faults or the failures. That kernel has John Dyson's patches in it, but not the change to vfs_cluster.c which was committed today. Unfortunately, my attempt to back out the vfs_cluster.c change didn't do anything... so now I'm rather confused. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 23:05:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17397 for freebsd-current-outgoing; Mon, 16 Mar 1998 23:05:47 -0800 (PST) (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 XAA17331; Mon, 16 Mar 1998 23:05:40 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id XAA03576; Mon, 16 Mar 1998 23:05:24 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803170705.XAA03576@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Karl Denninger cc: Daniel Berlin , Michael Hancock , current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-reply-to: Your message of "Tue, 17 Mar 1998 00:54:03 CST." <19980317005403.27423@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Mar 1998 23:05:24 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dyson 1998/03/16 22:30:56 PST Modified files: sys/kern vfs_subr.c Log: Correct a severely evil bug in the vtruncbuf code. It didn't cause me any problems until after the previous commit. This problem then caused a severe case of creeping crud on my diskdrive, and hosed my system so bad, that I needed to do a complete reinstall. Sorry!!! I assume that others have manifest this bug. Revision Changes Path 1.143 +34 -2 src/sys/kern/vfs_subr.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 16 23:12:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18642 for freebsd-current-outgoing; Mon, 16 Mar 1998 23:12:08 -0800 (PST) (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 XAA18583; Mon, 16 Mar 1998 23:11:45 -0800 (PST) (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 XAA23541; Mon, 16 Mar 1998 23:09:30 -0800 (PST) (envelope-from mantar@netcom.com) Message-Id: <199803170709.XAA23541@mantar.slip.netcom.com> X-Sender: null@mantar.slip.netcom.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 16 Mar 1998 23:09:30 -0800 To: Michael Hancock , Karl Denninger From: Manfred Antar Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected Cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG In-Reply-To: References: <19980316234921.07586@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:55 PM 3/17/98 +0900, Michael Hancock wrote: > >Is it possible that the previous kernel quietly trashed your disks and it >didn't manifest itself until after the last vm fix commit? > >Regards, > >Mike Hancock > >On Mon, 16 Mar 1998, Karl Denninger wrote: > >> ************ URGENT ************** >> >> I strongly advise that you *DO NOT* use -CURRENT as it sits at the >> present time. >> >> The kernel you build may do SEVERE damage to your filesystems. >> >> I am working on finding the commit which is causing this and will post to >> the list as soon as I have identified it. >> >> This is not a trivial matter. It is a very good thing indeed that I use a >> scratch disk for my /usr/obj area, or I would be really rather upset. :-) >> >> The symptoms are random core dumps and other problems - but the underlying >> reason is that the filesystem has been trashed beyond belief! >> >> I unmounted the disk in question CLEANLY and found both partially truncated >> and duplicate inodes all over it, along with severe internal file damage. >> >> I suspect the commit today in kern/vfs_cluster.c, as that's the only >> filesystem or VM related commit that my first-level examination has found. >> I am backing that out locally right now and will advise if it makes the >> problem go away. >> >> Note that kernels built LAST NIGHT (3/15) at about 23:00 *do not* exhibit >> the problem. >> >> -- Same thing happened to me. My disk was hosed. Luckily I had just swapped disks last Thursday. I put the old one back in and it runs fine. fstab: /dev/sd0s1a on / /dev/sd0s1e on /var /dev/sd0s1f on /usr /dev/sd0s1g on /usr/obj =====softupdates enabled. most of the damage was on /usr . although after a make -k -j4 world last night lots of / was trashed /sbin/init among others. I don't know if softupdates had any thing to do with it though. I disabled it and rebuilt tools libs sbin bin and a new kernel and the same thing happened. no NFS just the one SCSI drive. 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 Mar 16 23:20:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19781 for freebsd-current-outgoing; Mon, 16 Mar 1998 23:20:15 -0800 (PST) (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 XAA19760; Mon, 16 Mar 1998 23:20:07 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id CAA11514; Tue, 17 Mar 1998 02:18:45 -0500 (EST) (envelope-from toor) Message-Id: <199803170718.CAA11514@dyson.iquest.net> Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-Reply-To: <19980317010523.23149@mcs.net> from Karl Denninger at "Mar 17, 98 01:05:23 am" To: karl@mcs.net (Karl Denninger) Date: Tue, 17 Mar 1998 02:18:45 -0500 (EST) Cc: root@danberlin.resnet.rochester.edu, michaelh@cet.co.jp, current@FreeBSD.ORG, dyson@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Karl Denninger said: > > Ok, now I really don't get it. > Sorry, I think that it is a bug in vtruncbuf. I haven't had any problems yet after the fix. -- 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 Mon Mar 16 23:29:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA20813 for freebsd-current-outgoing; Mon, 16 Mar 1998 23:29:47 -0800 (PST) (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 XAA20807; Mon, 16 Mar 1998 23:29:42 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id CAA11562; Tue, 17 Mar 1998 02:27:41 -0500 (EST) (envelope-from toor) Message-Id: <199803170727.CAA11562@dyson.iquest.net> Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-Reply-To: from Michael Hancock at "Mar 17, 98 03:57:39 pm" To: michaelh@cet.co.jp (Michael Hancock) Date: Tue, 17 Mar 1998 02:27:41 -0500 (EST) Cc: karl@mcs.net, root@danberlin.resnet.rochester.edu, current@FreeBSD.ORG, dyson@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 The code as-is is correct. All of the evil was in vfs_subr.c:vtruncbuf. The vtruncbuf change was needed for some VM/buffer cache coherency problems, and unfortunately it didn't sync out metadata, when the rest of the upper level FFS code expected it to. After a while, the filesystem would irrecoverably loose it's mind. I lost 4 filesystems over this problem, and spent hours trying to recover the system and fix the problem. Michael Hancock said: > John, > > Is this what you meant? > > Mike > > Index: vfs_bio.c > =================================================================== > RCS file: /usr/cvs/src/sys/kern/vfs_bio.c,v > retrieving revision 1.156 > diff -u -r1.156 vfs_bio.c > --- vfs_bio.c 1998/03/16 01:55:22 1.156 > +++ vfs_bio.c 1998/03/17 06:03:47 > @@ -676,7 +676,7 @@ > break; > } > if (bp->b_flags & (B_NOCACHE|B_ERROR)) { > - int poffset = foff & PAGE_MASK; > + int poffset = poff & PAGE_MASK; > int presid = resid > (PAGE_SIZE - poffset) ? > (PAGE_SIZE - poffset) : resid; > vm_page_set_invalid(m, poffset, presid); > > -- 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 Mon Mar 16 23:31:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21516 for freebsd-current-outgoing; Mon, 16 Mar 1998 23:31:46 -0800 (PST) (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 XAA21507; Mon, 16 Mar 1998 23:31:41 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id CAA11588; Tue, 17 Mar 1998 02:31:38 -0500 (EST) (envelope-from toor) Message-Id: <199803170731.CAA11588@dyson.iquest.net> Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-Reply-To: <19980317001910.56629@mcs.net> from Karl Denninger at "Mar 17, 98 00:19:10 am" To: karl@mcs.net (Karl Denninger) Date: Tue, 17 Mar 1998 02:31:38 -0500 (EST) Cc: michaelh@cet.co.jp, current@FreeBSD.ORG, dyson@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Karl Denninger said: > > Yes, and now I've done it twice more while trying to isolate this thing. > > The corruption comes back within minutes of starting a "make world". > Whomever is trying to work with late Sun, early Mon -current should immediately stop, fsck their drives (if there is anything left), and go back to a Sat kernel. If you are very aggressive, try the -current as of now (as committed by me at around 01:00 EST on Tue.) -- 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 Mon Mar 16 23:50:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25416 for freebsd-current-outgoing; Mon, 16 Mar 1998 23:50:33 -0800 (PST) (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 XAA25408 for ; Mon, 16 Mar 1998 23:50:31 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id AAA08738; Tue, 17 Mar 1998 00:50:30 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd008719; Tue Mar 17 00:50:23 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id AAA16965; Tue, 17 Mar 1998 00:50:21 -0700 (MST) From: Terry Lambert Message-Id: <199803170750.AAA16965@usr04.primenet.com> Subject: Re: Compilers: 2.8.1 v 2.7.2.1? To: sgk@troutmask.apl.washington.edu (Steve Kargl) Date: Tue, 17 Mar 1998 07:50:21 +0000 (GMT) Cc: tlambert@primenet.com, ckempf@enigami.com, freebsd-current@FreeBSD.ORG In-Reply-To: <199803170456.UAA01121@troutmask.apl.washington.edu> from "Steve Kargl" at Mar 16, 98 08:56:10 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 > > Exceptions will not work with pthreads unless you are running 2.8.x > > g++ or better. This is as good a reason as any > > FWIW, I've been using egcs-1.0.x for testing g77. On my simple, > real-world benchmark (my code :-), g77 is giving about a 22% increase > in execution speed over f77 (f2c+gcc). egcs makes you make the choice about threading when you compile the compiler, instead of when you compile the code (as in gcc). I think egcs is seriously broken. It *certainly* will not work for C++ exceptions when using pthreads; if you want to compile the CMU ACAPD (for example), you will need the patches against the Moscow Center for SPARC Computing STL, and you *must* use g++ 2.8.0, *NOT* egcs. The problem is that the exception stack needs to be per-thread. The moral to this story? "I can make it run as fast as you want, as long as it doesn't have to actually work". 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 Mar 16 23:55:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26552 for freebsd-current-outgoing; Mon, 16 Mar 1998 23:55:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26545; Mon, 16 Mar 1998 23:55:40 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id AAA02854; Tue, 17 Mar 1998 00:55:39 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd002840; Tue Mar 17 00:55:34 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id AAA17189; Tue, 17 Mar 1998 00:55:31 -0700 (MST) From: Terry Lambert Message-Id: <199803170755.AAA17189@usr04.primenet.com> Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected To: root@danberlin.resnet.rochester.edu (Daniel Berlin) Date: Tue, 17 Mar 1998 07:55:31 +0000 (GMT) Cc: michaelh@cet.co.jp, karl@mcs.net, current@FreeBSD.ORG, dyson@FreeBSD.ORG In-Reply-To: from "Daniel Berlin" at Mar 17, 98 01:02:01 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 > No no no, haven't you been watching those IBM commercials? > It was probably the malicious hackers who can break through routers > blocking their packets, cover their tracks and unleash viruses all over > your computer in a matter of seconds, unless you are using IBM certified > solutions. > I bet it was them. > Damn hax0rs. Never attribute to malice, that which can be adequately expalined by stupidity. Obviously, it was Hadley. He downloaded another virus, from the Internet, cesspool that it is. Terry Lambert terry@lambert.org --- "If you use FreeBSD, you should be aware of the implicit limitations of not using a Microsoft OS. For example, you will be unable to execute many of the popular viruses..." -- Me --- 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 Mar 16 23:57:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26894 for freebsd-current-outgoing; Mon, 16 Mar 1998 23:57:29 -0800 (PST) (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 XAA26837; Mon, 16 Mar 1998 23:57:00 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id IAA00561; Tue, 17 Mar 1998 08:56:46 +0100 (MET) (envelope-from sos) Message-Id: <199803170756.IAA00561@sos.freebsd.dk> Subject: Re: Disk munging problem with current solved In-Reply-To: <199803170703.CAA08868@dyson.iquest.net> from "John S. Dyson" at "Mar 17, 98 02:03:44 am" To: dyson@FreeBSD.ORG Date: Tue, 17 Mar 1998 08:56:46 +0100 (MET) Cc: 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 John S. Dyson who wrote: > I haven't read any emails or complaints yet about filesystem problems, > but I know that those who have tried to run -current in the last day or > so have had terrible problems. The problems didn't manifest for me until > too late, and I ended up with hosed filesystems. The problems were caused > by vtruncbuf doing bad things, and I have corrected them as quickly as > possible. My machine has been down due to the creeping crud associated > with the flaw in the routine. > > Things are looking much better now (for me at least), and I have committed > the fix. Thankyou!!, I was THIS close to trashing my main machine yesterday.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Tue Mar 17 00:29:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00155 for freebsd-current-outgoing; Tue, 17 Mar 1998 00:29:51 -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 AAA00145 for ; Tue, 17 Mar 1998 00:29:46 -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 CAA29956; Tue, 17 Mar 1998 02:29:48 -0600 (CST) Message-ID: <19980317022948.23863@arh0300.urh.uiuc.edu> Date: Tue, 17 Mar 1998 02:29:48 -0600 From: dannyman Cc: current@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! But not if you're IDE? References: <199803170755.AAA17189@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803170755.AAA17189@usr04.primenet.com>; from Terry Lambert on Tue, Mar 17, 1998 at 07:55:31AM +0000 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 Uhmmm, do us IDE lamers have to worry, or should I cvsup/build world/build kernel/reboot ? -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 00:39:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01075 for freebsd-current-outgoing; Tue, 17 Mar 1998 00:39:22 -0800 (PST) (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 AAA01069 for ; Tue, 17 Mar 1998 00:39:18 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id DAA18886; Tue, 17 Mar 1998 03:39:14 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803170839.DAA18886@dyson.iquest.net> Subject: Re: WARNING WILL ROBINSON! But not if you're IDE? In-Reply-To: <19980317022948.23863@arh0300.urh.uiuc.edu> from dannyman at "Mar 17, 98 02:29:48 am" To: djhoward@uiuc.edu (dannyman) Date: Tue, 17 Mar 1998 03:39:14 -0500 (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 > > Uhmmm, do us IDE lamers have to worry, or should I cvsup/build world/build > kernel/reboot ? > I am a IDE lamer, and yes, you need to include the fixes in vfs_subr.c immediately. Also, be careful, because your filesystem might be damaged so bad that fsck will not be able to fix it. Be prepared for an entire backup/restore cycle!!! Sorry again!!! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 00:40:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01559 for freebsd-current-outgoing; Tue, 17 Mar 1998 00:40:31 -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 AAA01548 for ; Tue, 17 Mar 1998 00:40: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 CAA01642; Tue, 17 Mar 1998 02:40:19 -0600 (CST) Message-ID: <19980317024019.32194@arh0300.urh.uiuc.edu> Date: Tue, 17 Mar 1998 02:40:19 -0600 From: dannyman To: "John S. Dyson" Cc: current@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! But not if you're IDE? References: <19980317022948.23863@arh0300.urh.uiuc.edu> <199803170839.DAA18886@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803170839.DAA18886@dyson.iquest.net>; from John S. Dyson on Tue, Mar 17, 1998 at 03:39:14AM -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 Tue, Mar 17, 1998 at 03:39:14AM -0500, John S. Dyson wrote: > > Uhmmm, do us IDE lamers have to worry, or should I cvsup/build world/build > > kernel/reboot ? > I am a IDE lamer, and yes, you need to include the fixes in vfs_subr.c > immediately. Also, be careful, because your filesystem might be damaged > so bad that fsck will not be able to fix it. Be prepared for an entire > backup/restore cycle!!! > > Sorry again!!! Uhhhhh ... shit. Okay, thanks! -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 00:52:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02957 for freebsd-current-outgoing; Tue, 17 Mar 1998 00:52:24 -0800 (PST) (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 AAA02948 for ; Tue, 17 Mar 1998 00:52:21 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id CAA04990; Tue, 17 Mar 1998 02:52:20 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id CAA20160; Tue, 17 Mar 1998 02:52:20 -0600 (CST) Message-ID: <19980317025220.28795@mcs.net> Date: Tue, 17 Mar 1998 02:52:20 -0600 From: Karl Denninger To: dannyman Cc: current@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! But not if you're IDE? References: <199803170755.AAA17189@usr04.primenet.com> <19980317022948.23863@arh0300.urh.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980317022948.23863@arh0300.urh.uiuc.edu>; from dannyman on Tue, Mar 17, 1998 at 02:29:48AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 17, 1998 at 02:29:48AM -0600, dannyman wrote: > Uhmmm, do us IDE lamers have to worry, or should I cvsup/build world/build > kernel/reboot ? Yes you do! -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 01:00:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03911 for freebsd-current-outgoing; Tue, 17 Mar 1998 01:00:03 -0800 (PST) (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 AAA03844; Tue, 17 Mar 1998 00:59:53 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id CAA05027; Tue, 17 Mar 1998 02:59:53 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id CAA20237; Tue, 17 Mar 1998 02:59:53 -0600 (CST) Message-ID: <19980317025953.36408@mcs.net> Date: Tue, 17 Mar 1998 02:59:53 -0600 From: Karl Denninger To: sos@FreeBSD.ORG Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Disk munging problem with current solved References: <199803170703.CAA08868@dyson.iquest.net> <199803170756.IAA00561@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.84 In-Reply-To: =?iso-8859-1?Q?=3C199803170756=2EIAA00561=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Tue=2C_Mar_17=2C_1998_at_08=3A56=3A4?= =?iso-8859-1?Q?6AM_+0100?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 17, 1998 at 08:56:46AM +0100, Søren Schmidt wrote: > In reply to John S. Dyson who wrote: > > I haven't read any emails or complaints yet about filesystem problems, > > but I know that those who have tried to run -current in the last day or > > so have had terrible problems. The problems didn't manifest for me until > > too late, and I ended up with hosed filesystems. The problems were caused > > by vtruncbuf doing bad things, and I have corrected them as quickly as > > possible. My machine has been down due to the creeping crud associated > > with the flaw in the routine. > > > > Things are looking much better now (for me at least), and I have committed > > the fix. > > Thankyou!!, I was THIS close to trashing my main machine yesterday.... > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team I just got another case of the same problem with a kernel that has the believed fix in it, writing to a new filesystem. BE CAREFUL OUT THERE at the present time. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 01:47:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08700 for freebsd-current-outgoing; Tue, 17 Mar 1998 01:47:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08695 for ; Tue, 17 Mar 1998 01:46:58 -0800 (PST) (envelope-from max@ludd.luth.se) Received: from taurus.ludd.luth.se (max@taurus.ludd.luth.se [130.240.16.37]) by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id KAA14212 for ; Tue, 17 Mar 1998 10:46:54 +0100 Received: (max@localhost) by taurus.ludd.luth.se (8.6.11/8.6.11) id KAA12850; Tue, 17 Mar 1998 10:47:00 +0100 Message-ID: <19980317104700.51973@taurus.ludd.luth.se> Date: Tue, 17 Mar 1998 10:47:00 +0100 From: Max Nilsson To: current@FreeBSD.ORG Subject: Am I using a SCSI tape-device as root file system ? :-) Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.81e Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. My new current-kernel is drunk. cvsup:ed and compiled on Tue Mar 16 1998 'dmesg' tells me the following: npx0 on motherboard npx0: INT 16 interface changing root device to st1s1a ^^^^^^ I did not know that you can use a tape-device as root file-system. :) And I did not know that you can have partition-slices on a tape. :-) /Max -- Max Nilsson E-mail: max@ludd.luth.se -- -- Vänortsvägen 5 Tele: +46-(0)920-94202 -- -- 977 54 Luleå @home: homer.campus.luth.se -- -- Sweden -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 01:52:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09673 for freebsd-current-outgoing; Tue, 17 Mar 1998 01:52:16 -0800 (PST) (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 BAA09668 for ; Tue, 17 Mar 1998 01:52:12 -0800 (PST) (envelope-from osa@unibest.ru) Received: (qmail 14021 invoked from network); 17 Mar 1998 09:52:02 -0000 Received: from unknown (HELO hole.etrust.ru) (200.1.6.2) by serv.unibest.ru with SMTP; 17 Mar 1998 09:52:02 -0000 Date: Tue, 17 Mar 1998 12:53:41 +0300 (MSK) From: Ozz!!! X-Sender: osa@hole.etrust.ru To: Max Nilsson cc: current@FreeBSD.ORG Subject: Re: Am I using a SCSI tape-device as root file system ? :-) In-Reply-To: <19980317104700.51973@taurus.ludd.luth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Mar 1998, Max Nilsson wrote: > Hello. > > My new current-kernel is drunk. > cvsup:ed and compiled on Tue Mar 16 1998 > 'dmesg' tells me the following: > > npx0 on motherboard > npx0: INT 16 interface > changing root device to st1s1a > ^^^^^^ > > I did not know that you can use a tape-device as root > file-system. :) > And I did not know that you can have partition-slices > on a tape. :-) > > /Max > > -- Max Nilsson E-mail: max@ludd.luth.se -- > -- Vänortsvägen 5 Tele: +46-(0)920-94202 -- > -- 977 54 Luleå @home: homer.campus.luth.se -- > -- Sweden -- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > What about version of your FreeBSD ??? -RELENG or -CURRENT ??? 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 Tue Mar 17 03:36:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20074 for freebsd-current-outgoing; Tue, 17 Mar 1998 03:36:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA20068 for ; Tue, 17 Mar 1998 03:36:14 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-13-22.camtech.net.au [203.55.242.86]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id WAA10922 for ; Tue, 17 Mar 1998 22:03:49 +1030 (CST) Message-ID: <350E5FCD.BD352CDC@camtech.net.au> Date: Tue, 17 Mar 1998 22:04:37 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Disk munging problem with current solved References: <199803170703.CAA08868@dyson.iquest.net> <199803170756.IAA00561@sos.freebsd.dk> <19980317025953.36408@mcs.net> 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 know you dont want to hear this, But, For all non-developers who run -CURRENT, This is one good reason for using CTM You get to hear about the serious problems from the cvs-uppers before you get the suspect CTM delta! [Me: just thinking I'm glad I haven't lost my filesystems since I dont have many backup options] Karl Denninger wrote: > > On Tue, Mar 17, 1998 at 08:56:46AM +0100, Søren Schmidt wrote: > > In reply to John S. Dyson who wrote: > > > I haven't read any emails or complaints yet about filesystem problems, > > > but I know that those who have tried to run -current in the last day or > > > so have had terrible problems. The problems didn't manifest for me until > > > too late, and I ended up with hosed filesystems. The problems were caused > > > by vtruncbuf doing bad things, and I have corrected them as quickly as > > > possible. My machine has been down due to the creeping crud associated > > > with the flaw in the routine. > > > > > > Things are looking much better now (for me at least), and I have committed > > > the fix. > > > > Thankyou!!, I was THIS close to trashing my main machine yesterday.... > > > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > > I just got another case of the same problem with a kernel that has the > believed fix in it, writing to a new filesystem. > > BE CAREFUL OUT THERE at the present time. > > -- > -- > Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin > http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV > | NEW! Corporate ISDN Prices dropped by up to 50%! > Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS > Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 03:46:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21389 for freebsd-current-outgoing; Tue, 17 Mar 1998 03:46:15 -0800 (PST) (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 DAA21381 for ; Tue, 17 Mar 1998 03:46:10 -0800 (PST) (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 HAA08661; Tue, 17 Mar 1998 07:47:39 GMT Message-ID: <005b01bd5199$cdbfff00$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: "Matthew Thyer" , Subject: Re: Disk munging problem with current solved Date: Tue, 17 Mar 1998 06:42:44 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit 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 bah! wussies... :) can anyone suggest a good tape backup? j/k -Alfred -----Original Message----- From: Matthew Thyer To: current@FreeBSD.ORG Date: Tuesday, March 17, 1998 2:40 AM Subject: Re: Disk munging problem with current solved >I know you dont want to hear this, > >But, > >For all non-developers who run -CURRENT, > >This is one good reason for using CTM > >You get to hear about the serious problems from the cvs-uppers >before you get the suspect CTM delta! > >[Me: just thinking I'm glad I haven't lost my filesystems since >I dont have many backup options] > >Karl Denninger wrote: >> >> On Tue, Mar 17, 1998 at 08:56:46AM +0100, Søren Schmidt wrote: >> > In reply to John S. Dyson who wrote: >> > > I haven't read any emails or complaints yet about filesystem problems, >> > > but I know that those who have tried to run -current in the last day or >> > > so have had terrible problems. The problems didn't manifest for me until >> > > too late, and I ended up with hosed filesystems. The problems were caused >> > > by vtruncbuf doing bad things, and I have corrected them as quickly as >> > > possible. My machine has been down due to the creeping crud associated >> > > with the flaw in the routine. >> > > >> > > Things are looking much better now (for me at least), and I have committed >> > > the fix. >> > >> > Thankyou!!, I was THIS close to trashing my main machine yesterday.... >> > >> > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -=- >> > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team >> >> I just got another case of the same problem with a kernel that has the >> believed fix in it, writing to a new filesystem. >> >> BE CAREFUL OUT THERE at the present time. >> >> -- >> -- >> Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin >> http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV >> | NEW! Corporate ISDN Prices dropped by up to 50%! >> Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS >> Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message > >-- >/=====================================================================\ >|Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| >\=====================================================================/ >"If it is true that our Universe has a zero net value for all conserved >quantities, then it may simply be a fluctuation of the vacuum of some >larger space in which our Universe is imbedded. In answer to the >question of why it happened, I offer the modest proposal that our >Universe is simply one of those things which happen from time to time." > E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 03:55:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA22950 for freebsd-current-outgoing; Tue, 17 Mar 1998 03:55:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA22922 for ; Tue, 17 Mar 1998 03:55:21 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-13-22.camtech.net.au [203.55.242.86]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id WAA13047; Tue, 17 Mar 1998 22:22:45 +1030 (CST) Message-ID: <350E643D.A47CB903@camtech.net.au> Date: Tue, 17 Mar 1998 22:23:33 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: c5666305 CC: current@FreeBSD.ORG Subject: Re: Disk munging problem with current solved References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Send mail to "majordomo@freebsd.org" with the text "subscribe ctm-src-cur" in the body of your message. This will subscribe you to the mailing list which provides the CTM deltas for FreeBSD current. Majordomo will send you a reply saying how to unsubscribe yourself. Dont lose this message unless you already know how to unsubscribe. Note you will also need the last base delta for CURRENT which you can download from: ftp://ftp.freebsd.org/pub/FreeBSD/CTM/src-cur/ You can also send a message with "lists" in the body of the message to see what mailing lists are available. Send a message with "help" in the body to see what the available commands are to use with the majordomo system. If you have to ask such questions you probably shouldn't be running current. Information on the mailing lists is in the handbook. PLEASE PLEASE PLEASE go to the documentation pages from "http://www.freebsd.org" and read what the handbook has to say about using FreeBSD current first before you do any of the above. Note that you can also get CTM updates for the STABLE version of FreeBSD too (and the ports collection too). c5666305 wrote: > > I would like to know how to subscribe the CTM service. Thanks. > > Clarence CHAN > > > > > I know you dont want to hear this, > > > > But, > > > > For all non-developers who run -CURRENT, > > > > This is one good reason for using CTM > > > > You get to hear about the serious problems from the cvs-uppers > > before you get the suspect CTM delta! > > > > [Me: just thinking I'm glad I haven't lost my filesystems since > > I dont have many backup options] > > > > Karl Denninger wrote: > > > > > > On Tue, Mar 17, 1998 at 08:56:46AM +0100, Søren Schmidt wrote: > > > > In reply to John S. Dyson who wrote: > > > > > I haven't read any emails or complaints yet about filesystem problems, > > > > > but I know that those who have tried to run -current in the last day or > > > > > so have had terrible problems. The problems didn't manifest for me until > > > > > too late, and I ended up with hosed filesystems. The problems were caused > > > > > by vtruncbuf doing bad things, and I have corrected them as quickly as > > > > > possible. My machine has been down due to the creeping crud associated > > > > > with the flaw in the routine. > > > > > > > > > > Things are looking much better now (for me at least), and I have committed > > > > > the fix. > > > > > > > > Thankyou!!, I was THIS close to trashing my main machine yesterday.... > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > > > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > > > > > > I just got another case of the same problem with a kernel that has the > > > believed fix in it, writing to a new filesystem. > > > > > > BE CAREFUL OUT THERE at the present time. > > > > > > -- > > > -- > > > Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin > > > http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV > > > | NEW! Corporate ISDN Prices dropped by up to 50%! > > > Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS > > > Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > > /=====================================================================\ > > |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| > > \=====================================================================/ > > "If it is true that our Universe has a zero net value for all conserved > > quantities, then it may simply be a fluctuation of the vacuum of some > > larger space in which our Universe is imbedded. In answer to the > > question of why it happened, I offer the modest proposal that our > > Universe is simply one of those things which happen from time to time." > > E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 05:31:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA12206 for freebsd-current-outgoing; Tue, 17 Mar 1998 05:31:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from VMSB.CSD.MU.EDU (vmsb.csd.mu.edu [134.48.20.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA12201 for ; Tue, 17 Mar 1998 05:31:48 -0800 (PST) (envelope-from 4wg7kolodzie@vmsb.csd.mu.edu) Received: from vms.csd.mu.edu ([134.48.208.1]) by vms.csd.mu.edu (PMDF V5.1-9 #27588) with ESMTP id <01IURJRQ3SC207J12B@vms.csd.mu.edu> for freebsd-current@freebsd.org; Tue, 17 Mar 1998 07:31:35 CST Date: Tue, 17 Mar 1998 07:28:23 -0600 From: Justin A Kolodziej <4wg7kolodzie@vmsb.csd.mu.edu> Subject: Emulated Quake2 a no-go To: freebsd-current@FreeBSD.ORG Message-id: <350E7A77.29BF2D32@vms.csd.mu.edu> Organization: Marquette University MIME-version: 1.0 X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-980315-SNAP i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apparently the Linux emulation in FreeBSD isn't good enough quite yet. Trying to run Quake 2 gives the following: Mar 17 00:09:35 mcd7-31 /kernel: Linux-emul(211): setup() not supported And I *am* running as root, so that's not the problem. Of course, the fs problems are infinitely more important. I haven't noticed any unusual problems yet with Sunday's snapshot (980315) though. So until id decides to port Quake 2 to FreeBSD (not likely) and 3DFX decided to port Glide to FreeBSD (even less likely) OR setup gets supported I have to play bzflag under emulation. Which is not so bad except there aren't any servers out there that I can find. grrr... -- I sense a great disturbance in the Source. Justin A. Kolodziej 4wg7kolodzie@vms.csd.mu.edu Marquette University is http://www.mu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 05:54:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15434 for freebsd-current-outgoing; Tue, 17 Mar 1998 05:54:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA15428 for ; Tue, 17 Mar 1998 05:54:08 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: by watermarkgroup.com (4.1/SMI-4.1) id AA23812; Tue, 17 Mar 98 08:53:37 EST Date: Tue, 17 Mar 98 08:53:37 EST From: luoqi@watermarkgroup.com (Luoqi Chen) Message-Id: <9803171353.AA23812@watermarkgroup.com> To: current@FreeBSD.ORG Subject: softupdates allocindir panic Cc: julian@whistle.com, mckusick@mcKusick.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just had this panic myself. I studied the core dump a little bit. I found something interesting. The relevent piece of code around the crash is static void setup_allocindir_phase2(bp, ip, aip) struct buf *bp; /* in-memory copy of the indirect block */ struct inode *ip; /* inode for file being extended */ struct allocindir *aip; /* allocindir allocated by the above routines */ { ... for (indirdep = NULL, newindirdep = NULL; ; ) { ... newindirdep->ir_saveddata = (ufs_daddr_t *)bp->b_data; newindirdep->ir_savebp = getblk(ip->i_devvp, bp->b_blkno, bp->b_bcount, 0, 0); bcopy((caddr_t)newindirdep->ir_saveddata, newindirdep->ir_savebp->b_data, bp->b_bcount); } } Obviously, the getblk() call assumes VOP_BMAP has been performed, and b_blkno points to device relative block. But upon examining the core, I got b_blkno = b_lblkno (= -12). The same is true for dumps posted on -current. We probably should call VOP_BMAP before getblk() for the blkno == lblkno case. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 06:49:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22884 for freebsd-current-outgoing; Tue, 17 Mar 1998 06:49:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.91.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22879 for ; Tue, 17 Mar 1998 06:49:33 -0800 (PST) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (8.8.8/8.8.8) with SMTP id JAA03011; Tue, 17 Mar 1998 09:44:47 -0500 (EST) (envelope-from root@danberlin.resnet.rochester.edu) Date: Tue, 17 Mar 1998 09:44:47 -0500 (EST) From: Daniel Berlin To: Justin A Kolodziej <4wg7kolodzie@vmsb.csd.mu.edu> cc: freebsd-current@FreeBSD.ORG Subject: Re: Emulated Quake2 a no-go In-Reply-To: <350E7A77.29BF2D32@vms.csd.mu.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 Well, the server portions runs perfectly, as does jailbreak. Then again, i am one of the two people who codes jailbreak, so I would hope I could get my own code working on my own machine :). On Tue, 17 Mar 1998, Justin A Kolodziej wrote: > Apparently the Linux emulation in FreeBSD isn't good enough quite yet. > Trying to run Quake 2 gives the following: > > Mar 17 00:09:35 mcd7-31 /kernel: Linux-emul(211): setup() not supported > And I *am* running as root, so that's not the problem. > > Of course, the fs problems are infinitely more important. I haven't > noticed any unusual problems yet with Sunday's snapshot (980315) though. > > So until id decides to port Quake 2 to FreeBSD (not likely) and 3DFX > decided to port Glide to FreeBSD (even less likely) OR setup gets > supported I have to play bzflag under emulation. Which is not so bad > except there aren't any servers out there that I can find. grrr... > -- > I sense a great disturbance in the Source. > Justin A. Kolodziej > 4wg7kolodzie@vms.csd.mu.edu > Marquette University is http://www.mu.edu > > 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 Mar 17 07:31:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01881 for freebsd-current-outgoing; Tue, 17 Mar 1998 07:31:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA01873 for ; Tue, 17 Mar 1998 07:31:17 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: by watermarkgroup.com (4.1/SMI-4.1) id AA24833; Tue, 17 Mar 98 10:30:38 EST Date: Tue, 17 Mar 98 10:30:38 EST From: luoqi@watermarkgroup.com (Luoqi Chen) Message-Id: <9803171530.AA24833@watermarkgroup.com> To: 4wg7kolodzie@vmsb.csd.mu.edu, freebsd-current@FreeBSD.ORG Subject: Re: Emulated Quake2 a no-go Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Apparently the Linux emulation in FreeBSD isn't good enough quite yet. > Trying to run Quake 2 gives the following: > > Mar 17 00:09:35 mcd7-31 /kernel: Linux-emul(211): setup() not supported > And I *am* running as root, so that's not the problem. Actually setup() is linux syscall #0, to which all unsupported syscalls are mapped. What you saw is really syscall mremap. > > Of course, the fs problems are infinitely more important. I haven't > noticed any unusual problems yet with Sunday's snapshot (980315) though. > > So until id decides to port Quake 2 to FreeBSD (not likely) and 3DFX > decided to port Glide to FreeBSD (even less likely) OR setup gets > supported I have to play bzflag under emulation. Which is not so bad > except there aren't any servers out there that I can find. grrr... I am able to run Q2 under -current. If you search the emulation list carefully, you should find my posting on how to do it. > -- > I sense a great disturbance in the Source. > Justin A. Kolodziej > 4wg7kolodzie@vms.csd.mu.edu > Marquette University is http://www.mu.edu -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 07:58:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08622 for freebsd-current-outgoing; Tue, 17 Mar 1998 07:58:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08617 for ; Tue, 17 Mar 1998 07:58:39 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.8.8/8.8.5) id IAA02101; Tue, 17 Mar 1998 08:01:40 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199803170750.AAA16965@usr04.primenet.com> Date: Tue, 17 Mar 1998 07:53:40 -0800 (PST) Organization: Applied Physics Laboratory From: Steve Kargl To: Terry Lambert Subject: Re: Compilers: 2.8.1 v 2.7.2.1? Cc: freebsd-current@FreeBSD.ORG, ckempf@enigami.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Mar-98 Terry Lambert wrote: >> > Exceptions will not work with pthreads unless you are running 2.8.x >> > g++ or better. This is as good a reason as any >> >> FWIW, I've been using egcs-1.0.x for testing g77. On my simple, >> real-world benchmark (my code :-), g77 is giving about a 22% increase >> in execution speed over f77 (f2c+gcc). > >egcs makes you make the choice about threading when you compile the >compiler, instead of when you compile the code (as in gcc). > >I think egcs is seriously broken. > > >The problem is that the exception stack needs to be per-thread. > > >The moral to this story? "I can make it run as fast as you want, as >long as it doesn't have to actually work". > I don't use C++, so I can't speak about egcs's g++ and exceptions. Sigh. You're moral seems to be a non-sequitur with respect to my g77 observation. Most people would assume a statement of "real-world benchmark (my code)" means not only was g77 22% faster but it also gives the right answer. In fact, I can cook up a Fortran program that runs 16 times faster when complied with g77 than with f2c+gcc. I hardly would call this a real-world benchmark. (Oh yeah, both give the expected results). -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 08:01:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09501 for freebsd-current-outgoing; Tue, 17 Mar 1998 08:01:29 -0800 (PST) (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 IAA09466 for ; Tue, 17 Mar 1998 08:01:23 -0800 (PST) (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 QAA03005 for ; Tue, 17 Mar 1998 16:01:11 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id LAA20677 for freebsd-current@freebsd.org; Tue, 17 Mar 1998 11:01:10 -0500 (EST) From: Mikhail Teterin Message-Id: <199803171601.LAA20677@rtfm.ziplink.net> Subject: Re: Emulated Quake2 a no-go In-Reply-To: <350E7A77.29BF2D32@vms.csd.mu.edu> from "Justin A Kolodziej" at "Mar 17, 98 07:28:23 am" To: 4wg7kolodzie@vmsb.csd.mu.edu (Justin A Kolodziej) Date: Tue, 17 Mar 1998 11:00:28 -0500 (EST) 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 IAA17439 for freebsd-current-outgoing; Tue, 17 Mar 1998 08:36:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17404 for ; Tue, 17 Mar 1998 08:36:41 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id JAA07355; Tue, 17 Mar 1998 09:36:36 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id JAA15027; Tue, 17 Mar 1998 09:36:33 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199803171636.JAA15027@panzer.plutotech.com> Subject: Re: Am I using a SCSI tape-device as root file system ? :-) In-Reply-To: <19980317104700.51973@taurus.ludd.luth.se> from Max Nilsson at "Mar 17, 98 10:47:00 am" To: max@ludd.luth.se (Max Nilsson) Date: Tue, 17 Mar 1998 09:36:33 -0700 (MST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Max Nilsson wrote... > Hello. > > My new current-kernel is drunk. > cvsup:ed and compiled on Tue Mar 16 1998 > 'dmesg' tells me the following: > > npx0 on motherboard > npx0: INT 16 interface > changing root device to st1s1a > ^^^^^^ > > I did not know that you can use a tape-device as root > file-system. :) > And I did not know that you can have partition-slices > on a tape. :-) re-cvsup and recompile your kernel. autoconf.c was broken in rev 1.89, and fixed in rev 1.92. If your kernel works correctly, though, you should be fine. 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 Tue Mar 17 08:46:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22295 for freebsd-current-outgoing; Tue, 17 Mar 1998 08:46:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from symbion.srrc.usda.gov ([199.78.118.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22170 for ; Tue, 17 Mar 1998 08:46:37 -0800 (PST) (envelope-from glenn@nola.srrc.usda.gov) Received: from symbion.srrc.usda.gov (localhost [127.0.0.1]) by symbion.srrc.usda.gov (8.8.8/8.8.8) with ESMTP id KAA29281; Tue, 17 Mar 1998 10:40:51 -0600 (CST) (envelope-from glenn@symbion.srrc.usda.gov) Message-Id: <199803171640.KAA29281@symbion.srrc.usda.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: Steve Kargl cc: Terry Lambert , freebsd-current@FreeBSD.ORG, ckempf@enigami.com From: Glenn Johnson Subject: Re: Compilers: 2.8.1 v 2.7.2.1? In-reply-to: Your message of "Tue, 17 Mar 1998 07:53:40 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 17 Mar 1998 10:40:51 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> FWIW, I've been using egcs-1.0.x for testing g77. On my simple, > >> real-world benchmark (my code :-), g77 is giving about a 22% increase > >> in execution speed over f77 (f2c+gcc). > > > > > >The moral to this story? "I can make it run as fast as you want, as > >long as it doesn't have to actually work". > > > > > You're moral seems to be a non-sequitur with respect to my g77 observation. > Most people would assume a statement of "real-world benchmark (my code)" > means not only was g77 22% faster but it also gives the right answer. > In fact, I can cook up a Fortran program that runs 16 times faster when > complied with g77 than with f2c+gcc. I hardly would call this a > real-world benchmark. (Oh yeah, both give the expected results). > Just to put my 0.02 cents in, there seems to be problems with g77 when compiling "real-world" applications. I am talking about applications such as Gaussian94 and GAMESS (computational chemistry programs). Both of these programs are written in portable Fortan and compile and run on many UNIX platforms. They both compile and run fine when using f2c/cc but g77 chokes on them. On programs that do compile, I have noticed about a 20-30% improvement in execution time, but have also observed some run-time problems, particularly with free(): warning: modified (page-) pointer errors. Interestingly, I only see this with FreeBSD, Linux does not give this error for the equivalent program. Another interesting point is that I can get significant run time speed-ups in Fortran code by compiling the code as a Linux binary using Linux f2c/cc with the -malign-double cc option. I installed the Linux_devel port and added Linux f2c to it to achieve this. Of course, I am working with a small subset ! of Fortran applications but those are my observations, FWIW. -- Glenn Johnson Technician USDA-ARS-SRRC Phone: (504) 286-4252 1100 Robert E. Lee Boulevard FAX: (504) 286-4217 New Orleans, LA 70124 e-mail: gjohnson@nola.srrc.usda.gov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 09:24:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01251 for freebsd-current-outgoing; Tue, 17 Mar 1998 09:24:06 -0800 (PST) (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 JAA01191; Tue, 17 Mar 1998 09:24:02 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA22220; Tue, 17 Mar 1998 09:18:58 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd022215; Tue Mar 17 09:18:50 1998 Date: Tue, 17 Mar 1998 09:14:22 -0800 (PST) From: Julian Elischer To: Manfred Antar cc: Michael Hancock , Karl Denninger , current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-Reply-To: <199803170709.XAA23541@mantar.slip.netcom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been testing soft-updates and was seeing some new crashes I hadn't seen in the last few days. I was just trying to work out if it was soft-updates or the new VM stuff.. On Mon, 16 Mar 1998, Manfred Antar wrote: > At 02:55 PM 3/17/98 +0900, Michael Hancock wrote: > > > >Is it possible that the previous kernel quietly trashed your disks and it > >didn't manifest itself until after the last vm fix commit? > > > >Regards, > > > >Mike Hancock > > > >On Mon, 16 Mar 1998, Karl Denninger wrote: > > > >> ************ URGENT ************** > >> > >> I strongly advise that you *DO NOT* use -CURRENT as it sits at the > >> present time. > >> > >> The kernel you build may do SEVERE damage to your filesystems. > >> > >> I am working on finding the commit which is causing this and will post to > >> the list as soon as I have identified it. > >> > >> This is not a trivial matter. It is a very good thing indeed that I use a > >> scratch disk for my /usr/obj area, or I would be really rather upset. :-) > >> > >> The symptoms are random core dumps and other problems - but the underlying > >> reason is that the filesystem has been trashed beyond belief! > >> > >> I unmounted the disk in question CLEANLY and found both partially > truncated > >> and duplicate inodes all over it, along with severe internal file damage. > >> > >> I suspect the commit today in kern/vfs_cluster.c, as that's the only > >> filesystem or VM related commit that my first-level examination has found. > >> I am backing that out locally right now and will advise if it makes the > >> problem go away. > >> > >> Note that kernels built LAST NIGHT (3/15) at about 23:00 *do not* exhibit > >> the problem. > >> > >> -- > Same thing happened to me. My disk was hosed. Luckily I had just swapped > disks last Thursday. I put the old one back in and > it runs fine. > fstab: > > /dev/sd0s1a on / > /dev/sd0s1e on /var > /dev/sd0s1f on /usr > /dev/sd0s1g on /usr/obj =====softupdates enabled.. > most of the damage was on /usr . although after a make -k -j4 world last > night lots of / was trashed > /sbin/init among others. I don't know if softupdates had any thing to do > with it though. I disabled it > and rebuilt tools libs sbin bin and a new kernel and the same thing > happened. no NFS just the one SCSI drive. > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 09:26:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01940 for freebsd-current-outgoing; Tue, 17 Mar 1998 09:26:53 -0800 (PST) (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 JAA01927 for ; Tue, 17 Mar 1998 09:26:50 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA10092 for current@freebsd.org; Tue, 17 Mar 1998 12:25:53 -0500 (EST) (envelope-from toor) Message-Id: <199803171725.MAA10092@dyson.iquest.net> Subject: Okay, I can reproduce the problem again To: current@FreeBSD.ORG Date: Tue, 17 Mar 1998 12:25:53 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@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 Current still has problems, however, it seems to be better. Still, it is a good idea (in fact, very important) to stay away from it!!! I am offline right now, working on the problem. -- 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 Tue Mar 17 09:39:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04159 for freebsd-current-outgoing; Tue, 17 Mar 1998 09:39:50 -0800 (PST) (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 JAA04140 for ; Tue, 17 Mar 1998 09:39:46 -0800 (PST) (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 RAA03155 for ; Tue, 17 Mar 1998 17:39:39 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id MAA21000 for freebsd-current@freebsd.org; Tue, 17 Mar 1998 12:39:39 -0500 (EST) From: Mikhail Teterin Message-Id: <199803171739.MAA21000@rtfm.ziplink.net> Subject: Re: Kerberos and telnet, su, rsh.... In-Reply-To: <199803141210.OAA13837@greenpeace.grondar.za> from "Mark Murray" at "Mar 14, 98 02:10:20 pm" To: freebsd-current@FreeBSD.ORG Date: Tue, 17 Mar 1998 12:39:38 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" After I rebuilt the world with Kerberos support, things like => su, telnet, rsh stopped working, unless explicitly given the => ``-K'' option. I do not have Kerberos set up yet, but I remember, => that previosly in this cases I was just getting something "remote => side does not support Kerberos" or "not in root acl". Now the => programs hang for a while, then dump core... =Configure properly for Kerberos, or build without Kerberos. I believe this to be an unacceptable explanation of why things _crash_. It is my understanding, that system utilities (as well as all well written programs, actually) shall never crash. Other then due to a hardware error, of course. I can accept, that the policy was changed from "warn but run" to "warn and do not run", but simple "do not run" (or "crash") is not acceptable. Surprisingly, nobody offered a better explanation. I'm afraid, people will install Kerberos on -stable and will rightfully complaint about ``su'' dumping core without saying a word. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 09:50:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05638 for freebsd-current-outgoing; Tue, 17 Mar 1998 09:50:08 -0800 (PST) (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 JAA05632 for ; Tue, 17 Mar 1998 09:50:05 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id JAA06240; Tue, 17 Mar 1998 09:49:50 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803171749.JAA06240@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Justin A Kolodziej <4wg7kolodzie@vmsb.csd.mu.edu> cc: freebsd-current@FreeBSD.ORG Subject: Re: Emulated Quake2 a no-go In-reply-to: Your message of "Tue, 17 Mar 1998 07:28:23 CST." <350E7A77.29BF2D32@vms.csd.mu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 17 Mar 1998 09:49:50 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Apparently the Linux emulation in FreeBSD isn't good enough quite yet. > Trying to run Quake 2 gives the following: > > Mar 17 00:09:35 mcd7-31 /kernel: Linux-emul(211): setup() not supported > And I *am* running as root, so that's not the problem. The problem is that you posted to -current and if you had posted to -multimedia you will have received a response similar to : Download ftp://rah.star-gate.com/pub/README.GLQUAKE for instructions on how to get Quake 2 running on FreeBSD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 10:01:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07786 for freebsd-current-outgoing; Tue, 17 Mar 1998 10:01:03 -0800 (PST) (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 KAA07746 for ; Tue, 17 Mar 1998 10:00:59 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 3115 invoked from network); 17 Mar 1998 18:08:16 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 17 Mar 1998 18:08:16 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-031298 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 17 Mar 1998 10:08:16 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: freebsd-current@FreeBSD.ORG Subject: lib/libcrypt/{.depend, libscrypt.so.2.0} Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Gang, These two files keep on re-appearing in /usr/src, after ``make buildworld'' (I do not have the courage to do ``make world'' in light of the dire warnings from Mr. Dyson and others :-). This is not a major issue, but may indicate some other problem. No? ---------- 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 Mar 17 10:05:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09040 for freebsd-current-outgoing; Tue, 17 Mar 1998 10:05:01 -0800 (PST) (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 KAA09025; Tue, 17 Mar 1998 10:04:56 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id NAA20112; Tue, 17 Mar 1998 13:03:25 -0500 (EST) (envelope-from toor) Message-Id: <199803171803.NAA20112@dyson.iquest.net> Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-Reply-To: from Julian Elischer at "Mar 17, 98 09:14:22 am" To: julian@whistle.com (Julian Elischer) Date: Tue, 17 Mar 1998 13:03:25 -0500 (EST) Cc: mantar@netcom.com, michaelh@cet.co.jp, karl@mcs.net, current@FreeBSD.ORG, dyson@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 said: > > I've been testing soft-updates and was seeing some new crashes I hadn't > seen in the last few days. I was just trying to work out if it was > soft-updates or the new VM stuff.. > I think that it is an unintended interaction with the new vtruncbuf, or perhaps an error in vfs_bio, whereby I am not gratuitiously writing out buffers that are wrongly sized. (That can have very evil effects, but we have gotten by with it in the past.) It is unlikely that it is not a problem with my VFS changes. However, there have been some formatting changes in vfs_cluster, which the additional whitespace could be causing problems :-). -- 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 Tue Mar 17 10:07:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09815 for freebsd-current-outgoing; Tue, 17 Mar 1998 10:07:44 -0800 (PST) (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 KAA09791; Tue, 17 Mar 1998 10:07:36 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id MAA27515; Tue, 17 Mar 1998 12:06:30 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id MAA28734; Tue, 17 Mar 1998 12:06:29 -0600 (CST) Message-ID: <19980317120629.16696@mcs.net> Date: Tue, 17 Mar 1998 12:06:29 -0600 From: Karl Denninger To: dyson@FreeBSD.ORG Cc: Julian Elischer , mantar@netcom.com, michaelh@cet.co.jp, current@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected References: <199803171803.NAA20112@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199803171803.NAA20112@dyson.iquest.net>; from John S. Dyson on Tue, Mar 17, 1998 at 01:03:25PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 17, 1998 at 01:03:25PM -0500, John S. Dyson wrote: > Julian Elischer said: > > > > I've been testing soft-updates and was seeing some new crashes I hadn't > > seen in the last few days. I was just trying to work out if it was > > soft-updates or the new VM stuff.. > > > I think that it is an unintended interaction with the new vtruncbuf, > or perhaps an error in vfs_bio, whereby I am not gratuitiously writing > out buffers that are wrongly sized. (That can have very evil effects, > but we have gotten by with it in the past.) > > It is unlikely that it is not a problem with my VFS changes. However, > there have been some formatting changes in vfs_cluster, which the > additional whitespace could be causing problems :-). > > -- > 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. How DARE you say that whitespace isn't important! For that you deserve to be forced to read the obfuscated C-code contest entries. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 10:50:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23410 for freebsd-current-outgoing; Tue, 17 Mar 1998 10:50:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.91.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23147; Tue, 17 Mar 1998 10:49:37 -0800 (PST) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (8.8.8/8.8.8) with SMTP id NAA01312; Tue, 17 Mar 1998 13:44:51 -0500 (EST) (envelope-from root@danberlin.resnet.rochester.edu) Date: Tue, 17 Mar 1998 13:44:50 -0500 (EST) From: Daniel Berlin To: Karl Denninger cc: dyson@FreeBSD.ORG, Julian Elischer , mantar@netcom.com, michaelh@cet.co.jp, current@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-Reply-To: <19980317120629.16696@mcs.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 One of the best entries was that completely random looking piece of code that actually would decompress gzip'd files. > How DARE you say that whitespace isn't important! > > For that you deserve to be forced to read the obfuscated C-code contest > entries. > > -- > -- > Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin > http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV > | NEW! Corporate ISDN Prices dropped by up to 50%! > Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS > Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 11:03:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29034 for freebsd-current-outgoing; Tue, 17 Mar 1998 11:03:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29019 for ; Tue, 17 Mar 1998 11:03:30 -0800 (PST) (envelope-from mark@greenpeace.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 VAA24375; Tue, 17 Mar 1998 21:03:17 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id VAA08700; Tue, 17 Mar 1998 21:03:16 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199803171903.VAA08700@greenpeace.grondar.za> To: Mikhail Teterin cc: freebsd-current@FreeBSD.ORG Subject: Re: Kerberos and telnet, su, rsh.... Date: Tue, 17 Mar 1998 21:03:07 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > Mark Murray once stated: > =Configure properly for Kerberos, or build without Kerberos. > > I believe this to be an unacceptable explanation of why things > _crash_. It is my understanding, that system utilities (as well > as all well written programs, actually) shall never crash. Other > then due to a hardware error, of course. True. Sorry about the flippant answer, I was answering N-hundred emails after an absence. > I can accept, that the policy was changed from "warn but run" to > "warn and do not run", but simple "do not run" (or "crash") is not > acceptable. Please again supply the symptoms, and do a little debugging if you can, and I'll do what I can. Deal? :-) 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 Mar 17 11:37:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11595 for freebsd-current-outgoing; Tue, 17 Mar 1998 11:37:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fiscodata-pr.netpar.com.br (fiscodata-pr.netpar.com.br [200.255.244.88]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11453; Tue, 17 Mar 1998 11:37:15 -0800 (PST) (envelope-from paulo@fiscodata-pr.netpar.com.br) Received: from fiscodata-pr.netpar.com.br (fiscodata-pr.netpar.com.br [200.255.244.88]) by fiscodata-pr.netpar.com.br (8.8.8/8.8.5) with SMTP id QAA22348; Tue, 17 Mar 1998 16:41:39 GMT Date: Tue, 17 Mar 1998 16:41:39 +0000 (GMT) From: Paulo Cesar Pereira de Andrade Reply-To: Paulo Cesar Pereira de Andrade To: "John S. Dyson" cc: Karl Denninger , michaelh@cet.co.jp, current@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected In-Reply-To: <199803170731.CAA11588@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 Tue, 17 Mar 1998, John S. Dyson wrote: > Karl Denninger said: > > > > Yes, and now I've done it twice more while trying to isolate this thing. > > > > The corruption comes back within minutes of starting a "make world". > > > Whomever is trying to work with late Sun, early Mon -current should > immediately stop, fsck their drives (if there is anything left), and > go back to a Sat kernel. If you are very aggressive, try the -current > as of now (as committed by me at around 01:00 EST on Tue.) I have cvsupped early saturday (about 02:00am Brazil), and while building world, received a error building gcc: .o: malformed input file (not rel or archive) Looking the files, (one of them was /usr/obj/usr/src/gnu/usr.bin/cc/cc1plus/except.o) I saw it was fragments of c source code. This was after a crash while making world. Restarted a clean make world (/var/tmp as 8M MFS, and -j3) and it build with no errors. I got corrupted kernel .o files when compiling a library and the kernel at the same time. When compiling the kernel alone ld does not complain. The two times I thought it was operator error, because restarting did not repeat the problem. -- For perfect happiness, remember two things: (1) Be content with what you've got. (2) Be sure you've got plenty. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 11:45:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15505 for freebsd-current-outgoing; Tue, 17 Mar 1998 11:45:37 -0800 (PST) (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 LAA15482; Tue, 17 Mar 1998 11:45:34 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id NAA02296; Tue, 17 Mar 1998 13:45:32 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id NAA00324; Tue, 17 Mar 1998 13:45:32 -0600 (CST) Message-ID: <19980317134532.55817@mcs.net> Date: Tue, 17 Mar 1998 13:45:32 -0600 From: Karl Denninger To: Paulo Cesar Pereira de Andrade Cc: "John S. Dyson" , michaelh@cet.co.jp, current@FreeBSD.ORG Subject: Re: WARNING WILL ROBINSON! Risk of severe filesystem damage suspected References: <199803170731.CAA11588@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Paulo Cesar Pereira de Andrade on Tue, Mar 17, 1998 at 04:41:39PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 17, 1998 at 04:41:39PM +0000, Paulo Cesar Pereira de Andrade wrote: > On Tue, 17 Mar 1998, John S. Dyson wrote: > > > Karl Denninger said: > > > > > > Yes, and now I've done it twice more while trying to isolate this thing. > > > > > > The corruption comes back within minutes of starting a "make world". > > > > > Whomever is trying to work with late Sun, early Mon -current should > > immediately stop, fsck their drives (if there is anything left), and > > go back to a Sat kernel. If you are very aggressive, try the -current > > as of now (as committed by me at around 01:00 EST on Tue.) > > I have cvsupped early saturday (about 02:00am Brazil), and while > building world, received a error building gcc: > .o: malformed input file (not rel or archive) > > Looking the files, (one of them was > /usr/obj/usr/src/gnu/usr.bin/cc/cc1plus/except.o) I saw it was fragments > of c source code. This was after a crash while making world. Restarted a > clean make world (/var/tmp as 8M MFS, and -j3) and it build with no > errors. > > I got corrupted kernel .o files when compiling a library and the kernel > at the same time. When compiling the kernel alone ld does not complain. > > The two times I thought it was operator error, because restarting did > not repeat the problem. Folks, please, please listen closely to John on this. I will say it LOUDLY as well. -CURRENT, as of AT LEAST Saturday, is critically broken. If you run it on a system which has volatile data, you risk unrecoverable and permanent filesystem damage. PLEASE DON'T, at least for now, unless you're doing so in a controlled environment or don't mind a FULL reload! There ARE conditions under which it appears to be "safe" to use. HOWEVER, I'm not about to elucidate those under which it works here and doesn't destroy data, because (1) I don't understand why I get bit on some machines and not others, and (2) A situation in which I *THINK* is safe might turn out NOT to be safe. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 11:49:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16477 for freebsd-current-outgoing; Tue, 17 Mar 1998 11:49:18 -0800 (PST) (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 LAA16435 for ; Tue, 17 Mar 1998 11:49:08 -0800 (PST) (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 PAA15034; Tue, 17 Mar 1998 15:50:00 GMT Message-ID: <000a01bd51dd$3296ae40$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: "Justin A Kolodziej" <4wg7kolodzie@vmsb.csd.mu.edu>, Subject: Re: Emulated Quake2 a no-go Date: Tue, 17 Mar 1998 14:45:09 -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 You probably know who i am :) Here's what you do: 1) find a linux box 2) kick it 3) repeat step 2 till you feel warm and fuzzy inside 4) type "man setup" on the linux box 5) you might want to do step 2 again now because this is where it gets weird, as setup() seems only to be called in when linux boots up 6) look in /usr/src/sys/i386/linux 7) figure out why we "think" setup is being called (see step 2) 8) enable KTRACE in your kernel, man ktrace 9) retry step 7 now. 10) talk to me on irc if you find anything or post to the list. i'll do the same, i get the same error for x11amp and i've been meaning to find out why. -Alfred -----Original Message----- From: Justin A Kolodziej <4wg7kolodzie@vmsb.csd.mu.edu> To: freebsd-current@FreeBSD.ORG Date: Tuesday, March 17, 1998 4:40 AM Subject: Emulated Quake2 a no-go >Apparently the Linux emulation in FreeBSD isn't good enough quite yet. >Trying to run Quake 2 gives the following: > >Mar 17 00:09:35 mcd7-31 /kernel: Linux-emul(211): setup() not supported >And I *am* running as root, so that's not the problem. > >Of course, the fs problems are infinitely more important. I haven't >noticed any unusual problems yet with Sunday's snapshot (980315) though. > >So until id decides to port Quake 2 to FreeBSD (not likely) and 3DFX >decided to port Glide to FreeBSD (even less likely) OR setup gets >supported I have to play bzflag under emulation. Which is not so bad >except there aren't any servers out there that I can find. grrr... >-- >I sense a great disturbance in the Source. >Justin A. Kolodziej >4wg7kolodzie@vms.csd.mu.edu >Marquette University is http://www.mu.edu > >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 Mar 17 12:23:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26035 for freebsd-current-outgoing; Tue, 17 Mar 1998 12:23:25 -0800 (PST) (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 MAA26007 for ; Tue, 17 Mar 1998 12:23:06 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 13429 invoked from network); 17 Mar 1998 19:30:11 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 17 Mar 1998 19:30:11 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-031298 [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: <199803171739.MAA21000@rtfm.ziplink.net> Date: Tue, 17 Mar 1998 11:30:10 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mikhail Teterin Subject: Re: Kerberos and telnet, su, rsh.... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Mar-98 Mikhail Teterin wrote: > Mark Murray once stated: > > =Mikhail Teterin wrote: > => After I rebuilt the world with Kerberos support, things like > => su, telnet, rsh stopped working, unless explicitly given the > => ``-K'' option. I do not have Kerberos set up yet, but I remember, > => that previosly in this cases I was just getting something "remote > => side does not support Kerberos" or "not in root acl". Now the > => programs hang for a while, then dump core... > > =Configure properly for Kerberos, or build without Kerberos. > > I believe this to be an unacceptable explanation of why things > _crash_. It is my understanding, that system utilities (as well > as all well written programs, actually) shall never crash. Other > then due to a hardware error, of course. > > I can accept, that the policy was changed from "warn but run" to > "warn and do not run", but simple "do not run" (or "crash") is not > acceptable. > > Surprisingly, nobody offered a better explanation. I'm afraid, > people will install Kerberos on -stable and will rightfully complaint > about ``su'' dumping core without saying a word. You are right, of course. Core dumping is normally a side effect of invalid signal. Invalid signal is one that the program has not notified the kernel what it wants done with it. It is a clear mark on unanticipated error/exception. I douby it is the planned-for reaction to unconfigured Kerberos utility running. ---------- 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 Mar 17 12:49:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07560 for freebsd-current-outgoing; Tue, 17 Mar 1998 12:49:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07497 for ; Tue, 17 Mar 1998 12:48:52 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id VAA03286; Tue, 17 Mar 1998 21:16:23 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.7) id UAA28909; Tue, 17 Mar 1998 20:43:10 +0100 (CET) (envelope-from andreas) Message-ID: <19980317204310.37372@klemm.gtn.com> Date: Tue, 17 Mar 1998 20:43:10 +0100 From: Andreas Klemm To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: binutils bloat References: <19980314145857.51318@klemm.gtn.com> <863.889890756@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <863.889890756@time.cdrom.com>; from Jordan K. Hubbard on Sat, Mar 14, 1998 at 07:52:36AM -0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 14, 1998 at 07:52:36AM -0800, Jordan K. Hubbard wrote: > > Yes it's "pain in the ass" (= expensive for me), that the doctools > > are fetched every time I build a release... > > Actually, fetch the distfiles once "outside" your release build area > and it will copy them in - you don't have to fetch them every single > time. good idea. forgot that to do. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas powered by ,,symmetric multiprocessor FreeBSD'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 12:49:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07762 for freebsd-current-outgoing; Tue, 17 Mar 1998 12:49:57 -0800 (PST) (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 MAA07757 for ; Tue, 17 Mar 1998 12:49:55 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id MAA07055; Tue, 17 Mar 1998 12:49:36 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803172049.MAA07055@rah.star-gate.com> To: "Alfred Perlstein" cc: "Justin A Kolodziej" <4wg7kolodzie@vmsb.csd.mu.edu>, freebsd-current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Emulated Quake2 a no-go In-reply-to: Your message of "Tue, 17 Mar 1998 14:45:09 EST." <000a01bd51dd$3296ae40$0600a8c0@win95.local.sunyit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7052.890167776.1@rah> Date: Tue, 17 Mar 1998 12:49:36 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Again with respect to multimedia stuff post on -multimedia. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 14:14:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05590 for freebsd-current-outgoing; Tue, 17 Mar 1998 14:14:32 -0800 (PST) (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 OAA05541 for ; Tue, 17 Mar 1998 14:14:23 -0800 (PST) (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 IAA09870 for ; Wed, 18 Mar 1998 08:44:15 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id IAA08172; Wed, 18 Mar 1998 08:44:14 +1030 (CST) (envelope-from grog) Message-ID: <19980318084414.07315@freebie.lemis.com> Date: Wed, 18 Mar 1998 08:44:14 +1030 From: Greg Lehey To: FreeBSD current users Subject: Memory leak in inetd in last week's -current? 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've just discovered that my inetd has been rejecting connections with the following message: $ ftp ftp.lemis.com Connected to freebie.lemis.com. inetd in realloc(): warning: junk pointer, too high to make sense. ftp> I took a ktrace of it happening, if that's of any use, and restarted inetd, which made the problem go away. Any ideas? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 15:29:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25784 for freebsd-current-outgoing; Tue, 17 Mar 1998 15:29:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from VMSE.CSD.MU.EDU (vmse.csd.mu.edu [134.48.20.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25779 for ; Tue, 17 Mar 1998 15:29:09 -0800 (PST) (envelope-from 4wg7kolodzie@vmsb.csd.mu.edu) Received: from vms.csd.mu.edu ([134.48.208.1]) by vms.csd.mu.edu (PMDF V5.1-9 #27588) with ESMTP id <01IUS4N7I1DE07J7HD@vms.csd.mu.edu> for freebsd-current@freebsd.org; Tue, 17 Mar 1998 17:28:51 CST Date: Tue, 17 Mar 1998 17:25:38 -0600 From: Justin A Kolodziej <4wg7kolodzie@vmsb.csd.mu.edu> Subject: Re: Emulated Quake2 a no-go To: freebsd-current@FreeBSD.ORG Message-id: <350F0672.6E0F2068@vms.csd.mu.edu> Organization: Marquette University MIME-version: 1.0 X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-980315-SNAP i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit References: <01IUS4EJD7N8QTBZOG@vms.csd.mu.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > > > Apparently the Linux emulation in FreeBSD isn't good enough quite yet. > > Trying to run Quake 2 gives the following: > > > > Mar 17 00:09:35 mcd7-31 /kernel: Linux-emul(211): setup() not supported > > And I *am* running as root, so that's not the problem. The problem is that you posted to -current and if you had posted to > -multimedia you will have received a response similar to : > > Download ftp://rah.star-gate.com/pub/README.GLQUAKE for instructions > on how to get Quake 2 running on FreeBSD. To this, my rebuttal is: This file is rather unhelpful. First of all, it tells me the following: "As of right now you should get the linux emulation layer from ftp://rah.star-gate.com/pub/linux_ioctl-3.0-current.tar.gz" That's it. No information on how to install or where in the source tree it should go or anything like that. Second of all, some of the information contained in it is out of date. GL Quake 2 and QL Quake no longer require svgalib to run. There is a hack available that allows Mesa to control the i/o. You'll have to mail David Buccarelli at tech.hmw@plus.it to get the URL because I lost it :( . In addition, Quake 2 is now version 3.14a, which may or may not have the network problems fixed; the original worked fine from the console but not from the menu. I'm not even sure that this relates to the problem, because I believe it used to say "ioctl() not supported" when I was trying the release version. Now it says "setup() not supported", which is claimed to be a generic error message. Third, the date on this is February 11, and it says: "When we are done wrapping up the support for Quake2 the changes will be roll back to 3.0 -current." Well, it's been a month, and obviously this hasn't happened. Do you mind my asking what the status on this project is and when the estimated completion date is? And finally, I flat-out disagree that this is an issue for the multimedia mailing list. First of all, this issue deals with the imperfect emulation of a Linux function, so it belongs in emulation, not multimedia. Had the issue been that the 3dfx doesn't work, or sound access causes a core dump, perhaps that would fit in with the multimedia list. Besides, I was under the impression that the multimedia list referred to native FreeBSD apps that didn't work, not problems with emulated apps. Second of all, the changes are (eventually, supposedly) to be added to the current version, as your little note says, so, yes, this does belong on the current list. Had you just told me "we're working on that problem," or even "We don't care about that particular problem, and if you have to run Quake 2, go back to Linux," I wouldn't have a problem with that. But when you a. avoid the question, b. point me to information that is not actually relevant to my situation, and c. then try to get rid of me by pointing me to the wrong group, that only confirms what I should have suspected when I mistakenly sent my subscribe command to the list: If you're not perfect AND you're not interested in writing code for the next version of FreeBSD, you have no business getting a current snapshot, despite the fact that it's as freely available as the release version. Because it's freely available, that means it should be open to public scrutiny and suggestions. The mailing list being able to be posted to by non-subscribers further supports this view. Unfortunately, the responses I have gotten from this list suggests otherwise. A few final suggestions before I unsubscribe from this list: Make this list moderated so that you can decide whether a message is appropriate or not. Or else be prepared to respond more cordially to those messages you consider "dumb questions," as it appears you felt all of mine were. And second, mail me when Quake 2 works without any modifications to the linux compatibility package and when the filesystem works properly again like it does in Sunday's snapshot. Sincerely, Justin A. Kolodziej -- I sense a great disturbance in the Source. Justin A. Kolodziej 4wg7kolodzie@vms.csd.mu.edu Marquette University is http://www.mu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 15:40:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28315 for freebsd-current-outgoing; Tue, 17 Mar 1998 15:40:08 -0800 (PST) (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 PAA28308 for ; Tue, 17 Mar 1998 15:40:03 -0800 (PST) (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 PAA03976; Tue, 17 Mar 1998 15:39:47 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Justin A Kolodziej <4wg7kolodzie@vmsb.csd.mu.edu> cc: freebsd-current@FreeBSD.ORG Subject: Re: Emulated Quake2 a no-go In-reply-to: Your message of "Tue, 17 Mar 1998 17:25:38 CST." <350F0672.6E0F2068@vms.csd.mu.edu> Date: Tue, 17 Mar 1998 15:39:47 -0800 Message-ID: <3973.890177987@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Amancio Hasty wrote: > > > > > Apparently the Linux emulation in FreeBSD isn't good enough quite > yet. > > > Trying to run Quake 2 gives the following: > > > > > > Mar 17 00:09:35 mcd7-31 /kernel: Linux-emul(211): setup() not > supported > > > And I *am* running as root, so that's not the problem. > The problem is that you posted to -current and if you had posted to > > -multimedia you will have received a response similar to : > > > > Download ftp://rah.star-gate.com/pub/README.GLQUAKE for instructions > > on how to get Quake 2 running on FreeBSD. > To this, my rebuttal is: > > This file is rather unhelpful. > > First of all, it tells me the following: > > "As of right now you should get the linux emulation layer from > ftp://rah.star-gate.com/pub/linux_ioctl-3.0-current.tar.gz" > > That's it. No information on how to install or where in the source > tree > it should go or anything like that. > > Second of all, some of the information contained in it is out of date. > GL Quake 2 and QL Quake no longer require svgalib to run. There is a > hack available that allows Mesa to control the i/o. You'll have to > mail > David Buccarelli at tech.hmw@plus.it to get the URL because I lost it > :( . In addition, Quake 2 is now version 3.14a, which may or may not > have the network problems fixed; the original worked fine from the > console but not from the menu. I'm not even sure that this relates to > the problem, because I believe it used to say "ioctl() not supported" > when I was trying the release version. Now it says "setup() not > supported", which is claimed to be a generic error message. > > Third, the date on this is February 11, and it says: "When we are done > wrapping up the support for Quake2 the changes will be roll back to 3.0 > -current." Well, it's been a month, and obviously this hasn't > happened. Do you mind my asking what the status on this project is and > when the estimated completion date is? > > And finally, I flat-out disagree that this is an issue for the > multimedia mailing list. First of all, this issue deals with the > imperfect emulation of a Linux function, so it belongs in emulation, > not > multimedia. Had the issue been that the 3dfx doesn't work, or sound > access causes a core dump, perhaps that would fit in with the > multimedia > list. Besides, I was under the impression that the multimedia list > referred to native FreeBSD apps that didn't work, not problems with > emulated apps. Second of all, the changes are (eventually, > supposedly) > to be added to the current version, as your little note says, so, yes, > this does belong on the current list. > > Had you just told me "we're working on that problem," or even "We don't > care about that particular problem, and if you have to run Quake 2, go > back to Linux," I wouldn't have a problem with that. But when you a. > avoid the question, b. point me to information that is not actually > relevant to my situation, and c. then try to get rid of me by pointing > me to the wrong group, that only confirms what I should have suspected > when I mistakenly sent my subscribe command to the list: If you're not > perfect AND you're not interested in writing code for the next version > of FreeBSD, you have no business getting a current snapshot, despite > the > fact that it's as freely available as the release version. Because > it's > freely available, that means it should be open to public scrutiny and > suggestions. The mailing list being able to be posted to by > non-subscribers further supports this view. Unfortunately, the > responses I have gotten from this list suggests otherwise. > > A few final suggestions before I unsubscribe from this list: Make this > list moderated so that you can decide whether a message is appropriate > or not. Or else be prepared to respond more cordially to those > messages > you consider "dumb questions," as it appears you felt all of mine were. > And second, mail me when Quake 2 works without any modifications to the > linux compatibility package and when the filesystem works properly > again > like it does in Sunday's snapshot. > > Sincerely, > > Justin A. Kolodziej > -- > I sense a great disturbance in the Source. > Justin A. Kolodziej > 4wg7kolodzie@vms.csd.mu.edu > Marquette University is http://www.mu.edu > > 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 Mar 17 15:48:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00657 for freebsd-current-outgoing; Tue, 17 Mar 1998 15:48:13 -0800 (PST) (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 PAA00632 for ; Tue, 17 Mar 1998 15:48:11 -0800 (PST) (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 PAA04023; Tue, 17 Mar 1998 15:48:06 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Justin A Kolodziej <4wg7kolodzie@vmsb.csd.mu.edu> cc: freebsd-current@FreeBSD.ORG Subject: Re: Emulated Quake2 a no-go In-reply-to: Your message of "Tue, 17 Mar 1998 17:25:38 CST." <350F0672.6E0F2068@vms.csd.mu.edu> Date: Tue, 17 Mar 1998 15:48:06 -0800 Message-ID: <4019.890178486@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [sorry for my null first reply - slip of the fingers] > back to Linux," I wouldn't have a problem with that. But when you a. > avoid the question, b. point me to information that is not actually > relevant to my situation, and c. then try to get rid of me by pointing > me to the wrong group, that only confirms what I should have suspected > when I mistakenly sent my subscribe command to the list: If you're not > perfect AND you're not interested in writing code for the next version > of FreeBSD, you have no business getting a current snapshot, despite > the > fact that it's as freely available as the release version. Because First off, let me just point out a couple of things: 1. The very fact that list subscribership IS open will lead to you getting a very wide range of replies to your queries. Some people will call you an idiot, others will attempt to help you and still others will give you blatant misinformation in response to your queries. Them's the breaks! You either get a tightly controlled list where only the carefully screened can post to it, thus ensuring high quality replies (and not, incidently, the ability for you to post your question in the first place) or you have an open list where pretty much anybody can get on a soap box and speak his mind. Since this is an open list, you either have to be able to cope with the side-effects of its being open or you should indeed unsubscribe. 2. People *should* only run -current if their level of technical skill is better than average. This is stated in the handbook and -current itself, at least in the form of snapshots and the various instructions which describe cvsuping to it, and it's very much the case that there are many people who should NOT be running -current but do anyway, generally forcing others on this list to make up for their shortcomings by posting lots of questions that anyone with a better-than-average level of skill would not. That, quite frankly, sucks and of course there's going to be a set of people constantly saying "don't run -current, dammit!" since abuse in this department runs rather high. People routinely push buttons labelled "danger, high voltage! DO NOT PUSH!" too, and coping with the stupid, curious monkeys that humans often are can get to be a real drag sometimes - I wouldn't blame the people who have the job of scraping such people off the wall too much for being both cynical and embittered at human stupidity. It comes with the job. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 16:37:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10430 for freebsd-current-outgoing; Tue, 17 Mar 1998 16:37:02 -0800 (PST) (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 QAA10424 for ; Tue, 17 Mar 1998 16:36:58 -0800 (PST) (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 LAA04336; Wed, 18 Mar 1998 11:06:35 +1030 (CST) Message-Id: <199803180036.LAA04336@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Justin A Kolodziej <4wg7kolodzie@vmsb.csd.mu.edu> cc: freebsd-current@FreeBSD.ORG Subject: Re: Emulated Quake2 a no-go In-reply-to: Your message of "Tue, 17 Mar 1998 07:28:23 MDT." <350E7A77.29BF2D32@vms.csd.mu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Mar 1998 11:06:34 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Apparently the Linux emulation in FreeBSD isn't good enough quite yet. > Trying to run Quake 2 gives the following: > > Mar 17 00:09:35 mcd7-31 /kernel: Linux-emul(211): setup() not supported > And I *am* running as root, so that's not the problem. Hmm, I get this with gcc too, when I am compiling LInux stuff, but it still works, so I ignored it :) > So until id decides to port Quake 2 to FreeBSD (not likely) and 3DFX > decided to port Glide to FreeBSD (even less likely) OR setup gets > supported I have to play bzflag under emulation. Which is not so bad > except there aren't any servers out there that I can find. grrr... Hey, you can play Quake 1 just fine with a 3Dfx.. I do it :) Look at http://www.dons.net.au/~darius/quake/ for help on getting it running.. --------------------------------------------------------------------- |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 Mar 17 16:40:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10967 for freebsd-current-outgoing; Tue, 17 Mar 1998 16:40:11 -0800 (PST) (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 QAA10932 for ; Tue, 17 Mar 1998 16:40:03 -0800 (PST) (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 LAA04383; Wed, 18 Mar 1998 11:09:49 +1030 (CST) Message-Id: <199803180039.LAA04383@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Justin A Kolodziej <4wg7kolodzie@vmsb.csd.mu.edu> cc: freebsd-current@FreeBSD.ORG Subject: Re: Emulated Quake2 a no-go In-reply-to: Your message of "Tue, 17 Mar 1998 07:28:23 MDT." <350E7A77.29BF2D32@vms.csd.mu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Mar 1998 11:09:48 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Apparently the Linux emulation in FreeBSD isn't good enough quite yet. > Trying to run Quake 2 gives the following: > > Mar 17 00:09:35 mcd7-31 /kernel: Linux-emul(211): setup() not supported > And I *am* running as root, so that's not the problem. Hmm, on this note.. I just got the manpage for setup of a friends Linux machine.. Here is an excerpt - DESCRIPTION setup is called once from within linux/init/main.c. It calls initialization functions for devices and file sys- tems configured into the kernel and then mounts the root file system. No user process may call setup. Any user process, even a process with super-user permission, will receive EPERM. So why the heck does it get called by gcc or Quake 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 Tue Mar 17 17:16:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14547 for freebsd-current-outgoing; Tue, 17 Mar 1998 17:16:48 -0800 (PST) (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 RAA14499 for ; Tue, 17 Mar 1998 17:16:36 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id UAA00442; Tue, 17 Mar 1998 20:16:28 -0500 (EST) (envelope-from toor) Message-Id: <199803180116.UAA00442@dyson.iquest.net> Subject: Re: Memory leak in inetd in last week's -current? In-Reply-To: <19980318084414.07315@freebie.lemis.com> from Greg Lehey at "Mar 18, 98 08:44:14 am" To: grog@lemis.com (Greg Lehey) Date: Tue, 17 Mar 1998 20:16:27 -0500 (EST) Cc: FreeBSD-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Greg Lehey said: > I've just discovered that my inetd has been rejecting connections with > the following message: > > $ ftp ftp.lemis.com > Connected to freebie.lemis.com. > inetd in realloc(): warning: junk pointer, too high to make sense. > ftp> > > I took a ktrace of it happening, if that's of any use, and restarted > inetd, which made the problem go away. Any ideas? > If you are running a kernel after about Saturday, then it is a kernel problem, and immediately you should start running an earlier kernel. -- 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 Tue Mar 17 17:30:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16271 for freebsd-current-outgoing; Tue, 17 Mar 1998 17:30:26 -0800 (PST) (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 RAA16234; Tue, 17 Mar 1998 17:30:21 -0800 (PST) (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 MAA10097; Wed, 18 Mar 1998 12:00:17 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id MAA09198; Wed, 18 Mar 1998 12:00:17 +1030 (CST) (envelope-from grog) Message-ID: <19980318120016.31155@freebie.lemis.com> Date: Wed, 18 Mar 1998 12:00:16 +1030 From: Greg Lehey To: dyson@FreeBSD.ORG Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Memory leak in inetd in last week's -current? References: <19980318084414.07315@freebie.lemis.com> <199803180116.UAA00442@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803180116.UAA00442@dyson.iquest.net>; from John S. Dyson on Tue, Mar 17, 1998 at 08:16:27PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 March 1998 at 20:16:27 -0500, John S. Dyson wrote: > Greg Lehey said: >> I've just discovered that my inetd has been rejecting connections with >> the following message: >> >> $ ftp ftp.lemis.com >> Connected to freebie.lemis.com. >> inetd in realloc(): warning: junk pointer, too high to make sense. >> ftp> >> >> I took a ktrace of it happening, if that's of any use, and restarted >> inetd, which made the problem go away. Any ideas? >> > If you are running a kernel after about Saturday, then it is a kernel > problem, and immediately you should start running an earlier kernel. Yes, I saw the file system mass destruction problems, but that was later. This kernel was built last Thursday (our time), or Wednesday your time. Any danger there? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 18:02:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19951 for freebsd-current-outgoing; Tue, 17 Mar 1998 18:02:39 -0800 (PST) (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 SAA19941; Tue, 17 Mar 1998 18:02:24 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id VAA01899; Tue, 17 Mar 1998 21:02:22 -0500 (EST) (envelope-from toor) Message-Id: <199803180202.VAA01899@dyson.iquest.net> Subject: Re: Memory leak in inetd in last week's -current? In-Reply-To: <19980318120016.31155@freebie.lemis.com> from Greg Lehey at "Mar 18, 98 12:00:16 pm" To: grog@lemis.com (Greg Lehey) Date: Tue, 17 Mar 1998 21:02:22 -0500 (EST) Cc: dyson@FreeBSD.ORG, FreeBSD-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Greg Lehey said: > On Tue, 17 March 1998 at 20:16:27 -0500, John S. Dyson wrote: > > Greg Lehey said: > >> I've just discovered that my inetd has been rejecting connections with > >> the following message: > >> > >> $ ftp ftp.lemis.com > >> Connected to freebie.lemis.com. > >> inetd in realloc(): warning: junk pointer, too high to make sense. > >> ftp> > >> > >> I took a ktrace of it happening, if that's of any use, and restarted > >> inetd, which made the problem go away. Any ideas? > >> > > If you are running a kernel after about Saturday, then it is a kernel > > problem, and immediately you should start running an earlier kernel. > > Yes, I saw the file system mass destruction problems, but that was > later. This kernel was built last Thursday (our time), or Wednesday > your time. Any danger there? > Some problems were known, but not the overt system destruction (so far) on code that old. BTW, I am working on the problem every waking hour (practically), and am getting support/help/ideas from Karl, who is prepared to help regression test the code. -- 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 Tue Mar 17 18:18:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21855 for freebsd-current-outgoing; Tue, 17 Mar 1998 18:18:43 -0800 (PST) (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 SAA21850 for ; Tue, 17 Mar 1998 18:18:41 -0800 (PST) (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 CAA05932 for ; Wed, 18 Mar 1998 02:18:19 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id VAA21983 for FREEBSD-CURRENT@freebsd.org; Tue, 17 Mar 1998 21:18:18 -0500 (EST) From: Mikhail Teterin Message-Id: <199803180218.VAA21983@rtfm.ziplink.net> Subject: Jordan's response to Justin A. K. (was Re: Emulated Quake2 a no-go) In-Reply-To: <4019.890178486@time.cdrom.com> from "Jordan K. Hubbard" at "Mar 17, 98 03:48:06 pm" To: FREEBSD-CURRENT@FreeBSD.ORG Date: Tue, 17 Mar 1998 21:18:18 -0500 (EST) 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 SAA23586 for freebsd-current-outgoing; Tue, 17 Mar 1998 18:29:21 -0800 (PST) (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 SAA23580 for ; Tue, 17 Mar 1998 18:29:19 -0800 (PST) (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 SAA04647; Tue, 17 Mar 1998 18:29:15 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Mikhail Teterin cc: FREEBSD-CURRENT@FreeBSD.ORG Subject: Re: Jordan's response to Justin A. K. (was Re: Emulated Quake2 a no-go) In-reply-to: Your message of "Tue, 17 Mar 1998 21:18:18 EST." <199803180218.VAA21983@rtfm.ziplink.net> Date: Tue, 17 Mar 1998 18:29:15 -0800 Message-ID: <4644.890188155@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Both of the couple of things, while beautifully worded, do not > directly apply to the original complaint, IMHO. Justin A Kolodziej > was, AFAIU, upset about the _tone_ with which he was directed to the > information. He was (convincingly, at least, for me) arguing, that And, as I said, we can't be held responsible for the _tone_ of the various replies people will get from queries sent to -current. My original point still applys. :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 21:05:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06424 for freebsd-current-outgoing; Tue, 17 Mar 1998 21:05:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06417; Tue, 17 Mar 1998 21:05:22 -0800 (PST) (envelope-from andrew@zeta.org.au) Received: from gurney.reilly.home (d1.syd2.zeta.org.au [203.26.11.1]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id QAA22065; Wed, 18 Mar 1998 16:03:54 +1100 Received: (from andrew@localhost) by gurney.reilly.home (8.8.8/8.8.5) id KAA23059; Wed, 18 Mar 1998 10:39:02 +1100 (EST) From: Andrew Reilly Message-Id: <199803172339.KAA23059@gurney.reilly.home> Date: Wed, 18 Mar 1998 10:39:02 +1100 (EST) Subject: Re: Disk munging problem with current solved To: thyerm@camtech.net.au cc: current@FreeBSD.ORG, owner-ctm-ports-cur@FreeBSD.ORG In-Reply-To: <350E643D.A47CB903@camtech.net.au> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17 Mar, Matthew Thyer wrote: > Note that you can also get CTM updates for the STABLE > version of FreeBSD too (and the ports collection too). Side note: Is ctm-ports-cur still alive? I haven't received a delta since 2186 (31st Jan). I've had to grab bits of the ports tree manually since then, so I'm out of synch now... -- Andrew "The steady state of disks is full." -- Ken Thompson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 21:11:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06992 for freebsd-current-outgoing; Tue, 17 Mar 1998 21:11:19 -0800 (PST) (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 VAA06986 for ; Tue, 17 Mar 1998 21:11:13 -0800 (PST) (envelope-from hoek@hwcn.org) Received: from localhost (ac199@localhost) by hwcn.org (8.8.8/8.8.8) with SMTP id AAA09313; Wed, 18 Mar 1998 00:07:27 -0500 (EST) Date: Wed, 18 Mar 1998 00:07:27 -0500 (EST) From: Tim Vanderhoek To: Justin A Kolodziej <4wg7kolodzie@vmsb.csd.mu.edu> cc: freebsd-current@FreeBSD.ORG Subject: Re: Emulated Quake2 a no-go In-Reply-To: <350F0672.6E0F2068@vms.csd.mu.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 Tue, 17 Mar 1998, Justin A Kolodziej wrote: > Had you just told me "we're working on that problem," or even "We don't > care about that particular problem, and if you have to run Quake 2, go > back to Linux," I wouldn't have a problem with that. But when you a. > avoid the question, b. point me to information that is not actually > relevant to my situation, and c. then try to get rid of me by pointing > me to the wrong group, that only confirms what I should have suspected Bah. You got Amancio's standard form-letter reply. Being verbose is not one of his faults and you seem to have interpreted his lack of verbosity as being intentionally curt and offensive. [you insisted on an enumerated list of faults] 1) You accuse him of avoiding the question only because you didn't get the answer you wanted. "avoiding" == "not responding at all" != "answering". 2) To my simple mind, information about running Quake is relevent to running Quake. Your complaint is not that the information wasn't relevent, but that it didn't tell you enough. The correct response would have been to ask more _questions_ on -multimedia. 3) Amancio was definitely not trying to get rid of you. My personal suspecion is that he was actually trying to recruit more participants for his own favourite mailing-list. From his oft-repeated referrals to said list, and from an idea of its main participants, I suspect it's one of the most helpful and responsive FreeBSD ones around. Your more appropriate apply would have been to thank him for pointing you to -multimedia. -- 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 Tue Mar 17 21:17:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07661 for freebsd-current-outgoing; Tue, 17 Mar 1998 21:17:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.91.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07654; Tue, 17 Mar 1998 21:17:11 -0800 (PST) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (8.8.8/8.8.8) with SMTP id AAA02783; Wed, 18 Mar 1998 00:12:22 -0500 (EST) (envelope-from root@danberlin.resnet.rochester.edu) Date: Wed, 18 Mar 1998 00:12:22 -0500 (EST) From: Daniel Berlin To: Andrew Reilly cc: thyerm@camtech.net.au, current@FreeBSD.ORG, owner-ctm-ports-cur@FreeBSD.ORG Subject: Re: Disk munging problem with current solved In-Reply-To: <199803172339.KAA23059@gurney.reilly.home> 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 Too bad, your missing all the fun. On Wed, 18 Mar 1998, Andrew Reilly wrote: > On 17 Mar, Matthew Thyer wrote: > > Note that you can also get CTM updates for the STABLE > > version of FreeBSD too (and the ports collection too). > > Side note: Is ctm-ports-cur still alive? I haven't received a delta > since 2186 (31st Jan). I've had to grab bits of the ports tree > manually since then, so I'm out of synch now... > > -- > Andrew > > "The steady state of disks is full." > -- Ken Thompson > > > 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 Mar 17 21:20:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08135 for freebsd-current-outgoing; Tue, 17 Mar 1998 21:20:06 -0800 (PST) (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 VAA08129 for ; Tue, 17 Mar 1998 21:20:04 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id VAA08348; Tue, 17 Mar 1998 21:19:57 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803180519.VAA08348@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mikhail Teterin cc: FREEBSD-CURRENT@FreeBSD.ORG Subject: Re: Jordan's response to Justin A. K. (was Re: Emulated Quake2 a no-go) In-reply-to: Your message of "Tue, 17 Mar 1998 21:18:18 EST." <199803180218.VAA21983@rtfm.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 17 Mar 1998 21:19:57 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Both of the couple of things, while beautifully worded, do not > directly apply to the original complaint, IMHO. Justin A Kolodziej > was, AFAIU, upset about the _tone_ with which he was directed to the > information. He was (convincingly, at least, for me) arguing, that > his question was indeed relevant to -current. The fact, that Quake > was already discussed on -multimedia and/or that people there > know/care about Quake more is not immediately obvious. Respectfully, You DON"T LIKE MY TONE ---- YOU GOT TO BE KIDDING ME . I bet that you guys are joking, right?? Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 21:27:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09015 for freebsd-current-outgoing; Tue, 17 Mar 1998 21:27:58 -0800 (PST) (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 VAA09010 for ; Tue, 17 Mar 1998 21:27:56 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id VAA08424; Tue, 17 Mar 1998 21:27:33 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803180527.VAA08424@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Tim Vanderhoek cc: Justin A Kolodziej <4wg7kolodzie@vmsb.csd.mu.edu>, freebsd-current@FreeBSD.ORG Subject: Re: Emulated Quake2 a no-go In-reply-to: Your message of "Wed, 18 Mar 1998 00:07:27 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 17 Mar 1998 21:27:32 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, I took a few moments while I was in the middle of intense hacking at work to post so you are right it was an automatic response and you are right I was thinking about recruiting Justin. Think about it an army of Justin lose in the world fighting against Microsoft. Sounds really good to me 8) To the original poster: "I keep forgetting if the glass is half full or is it half-empty" Cheers, Amancio > On Tue, 17 Mar 1998, Justin A Kolodziej wrote: > > > Had you just told me "we're working on that problem," or even "We don't > > care about that particular problem, and if you have to run Quake 2, go > > back to Linux," I wouldn't have a problem with that. But when you a. > > avoid the question, b. point me to information that is not actually > > relevant to my situation, and c. then try to get rid of me by pointing > > me to the wrong group, that only confirms what I should have suspected > > Bah. You got Amancio's standard form-letter reply. Being > verbose is not one of his faults and you seem to have interpreted > his lack of verbosity as being intentionally curt and offensive. > > [you insisted on an enumerated list of faults] > > 1) You accuse him of avoiding the question only because you > didn't get the answer you wanted. "avoiding" == "not responding > at all" != "answering". > > 2) To my simple mind, information about running Quake is relevent > to running Quake. Your complaint is not that the information > wasn't relevent, but that it didn't tell you enough. The correct > response would have been to ask more _questions_ on -multimedia. > > 3) Amancio was definitely not trying to get rid of you. My > personal suspecion is that he was actually trying to recruit more > participants for his own favourite mailing-list. From his > oft-repeated referrals to said list, and from an idea of its main > participants, I suspect it's one of the most helpful and > responsive FreeBSD ones around. Your more appropriate apply > would have been to thank him for pointing you to -multimedia. > > > -- > Outnumbered? Maybe. Outspoken? Never! > tIM...HOEk > > > 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 Mar 17 21:43:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10003 for freebsd-current-outgoing; Tue, 17 Mar 1998 21:43:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09998 for ; Tue, 17 Mar 1998 21:43:55 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id QAA00157; Wed, 18 Mar 1998 16:12:28 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id H1923JHF; Wed, 18 Mar 1998 16:13:05 +0930 Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id QAA07706; Wed, 18 Mar 1998 16:13:48 +1030 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id QAA03522; Wed, 18 Mar 1998 16:13:47 +1030 (CST) Message-ID: <350F5F12.A8334298@dsto.defence.gov.au> Date: Wed, 18 Mar 1998 16:13:46 +1030 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Andrew Reilly CC: current@FreeBSD.ORG Subject: Re: Disk munging problem with current solved References: <199803172339.KAA23059@gurney.reilly.home> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, ctm-ports-cur is still available. I use it all the time as I'm behind a firewall at work and cant use cvsup. Many people 'fell' off the mailing lists when the var filesystem crashed on freefall (or was it some other machine) ? You will probably have to re-subscribe. Andrew Reilly wrote: > > On 17 Mar, Matthew Thyer wrote: > > Note that you can also get CTM updates for the STABLE > > version of FreeBSD too (and the ports collection too). > > Side note: Is ctm-ports-cur still alive? I haven't received a delta > since 2186 (31st Jan). I've had to grab bits of the ports tree > manually since then, so I'm out of synch now... > > -- > Andrew > > "The steady state of disks is full." > -- Ken Thompson > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 17 23:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18253 for freebsd-current-outgoing; Tue, 17 Mar 1998 23:01:42 -0800 (PST) (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 XAA18248 for ; Tue, 17 Mar 1998 23:01:41 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id AAA10211; Wed, 18 Mar 1998 00:01:37 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd010189; Wed Mar 18 00:01:31 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id AAA00396; Wed, 18 Mar 1998 00:01:28 -0700 (MST) From: Terry Lambert Message-Id: <199803180701.AAA00396@usr04.primenet.com> Subject: Re: Compilers: 2.8.1 v 2.7.2.1? To: sgk@troutmask.apl.washington.edu (Steve Kargl) Date: Wed, 18 Mar 1998 07:01:28 +0000 (GMT) Cc: tlambert@primenet.com, freebsd-current@FreeBSD.ORG, ckempf@enigami.com In-Reply-To: from "Steve Kargl" at Mar 17, 98 07:53:40 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 > >The moral to this story? "I can make it run as fast as you want, as > >long as it doesn't have to actually work". > > I don't use C++, so I can't speak about egcs's g++ and exceptions. > > Sigh. > > You're moral seems to be a non-sequitur with respect to my g77 observation. > Most people would assume a statement of "real-world benchmark (my code)" > means not only was g77 22% faster but it also gives the right answer. > In fact, I can cook up a Fortran program that runs 16 times faster when > complied with g77 than with f2c+gcc. I hardly would call this a > real-world benchmark. (Oh yeah, both give the expected results). I have noticed FP exceptions with g77; I have also noticed that some code simply will not run, even though f2c compiles it, as does a VAX as does a CDC Cyber (yeah, it's old code) as does a YMP. Admittedly, it's not terribly useful to run this code on a machine without a vector processor (ie; Intel boxes) if you want to do half a billion P-P pair production collosions, but it's an indicator that the g77 compiler isn't quite there yet. That you can't use threads in C++ with egcs, but you can with the FSF g++ distribution is probably more important than the FORTRAN problems, but the code *is* rather broken in both cases. 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 Tue Mar 17 23:09:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19288 for freebsd-current-outgoing; Tue, 17 Mar 1998 23:09:14 -0800 (PST) (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 XAA19276 for ; Tue, 17 Mar 1998 23:09:13 -0800 (PST) (envelope-from fredriks@Mercury.mcs.net) Received: from Mercury.mcs.net (fredriks@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id BAA09897; Wed, 18 Mar 1998 01:09:05 -0600 (CST) Received: (from fredriks@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id BAA10857; Wed, 18 Mar 1998 01:08:59 -0600 (CST) From: Lars Fredriksen Message-Id: <199803180708.BAA10857@Mercury.mcs.net> Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) To: shimon@simon-shapiro.org Date: Wed, 18 Mar 1998 01:08:59 -0600 (CST) Cc: thyerm@camtech.net.au, mike@smith.net.au, current@FreeBSD.ORG, nate@mt.sri.com In-Reply-To: from "Simon Shapiro" at Mar 10, 98 09:30:45 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Simon Shapiro writes: > > [stuff deleted] > > Because I get the silo overflows consistently, without any X11 on the > machine, I doubt X11 is key to this. From Mike's excellent overview of > interrupts, it is pretty clear that an interrupt is leaking someplace. > I ALWAYS see this silo overflow associated wit ha DPT lost interrupt; > > Some time ago (several months) I noticed that the DPT driver is not getting > certain interrupts. I simply did not get them. It was not a case where I > receive them and not proces them. At first I suspected the hardware. It > happens, under SMP, on two drastically different motherboards. > I added a simple timer to the DPT driver that occasionally wakes up and > checks the hardware for posted interrupt. If I find one, I process it and > complain. > > I always get a silo overflow when using PPP. It always happens with a DPT > lost interrupt recovery. Not every DPT lost interrupt recovery has an > sio.c silo overflow, but every silo overflow has a DPT lost interrupt > associated with it. > > Probably a race condition in interrupt handling. If X11 causes the video > card to generate interrupts, this is our clue; A video card can generate > interrupts very quickly. So can a DPT; Less than 2us between interrupts > is not unusual. > > For all it's worth; Fast Interrupts remind me of Linux interrupts; You > shutdown all interrupts, etc. Linux chronically loses interrupts. If you > block all interrupts, there simply is no way to guarantee you will not lose > one. This is how I understand it. I am probably wrong. > > Simon > Hi, I also see lots of : sio3: 151 more interrupt-level buffer overflows (total 151) Usually serveral thousands per day. All mine are from ppp using the serial link. When using netscape it makes the problem worse but linx hardly ever causes problem. Just as Simon did attribute the problem related to DPT, mine seems related to disk access as well. I am using the ahc driver (cam at the moment), and I wonder if my problems doesn't stem from the funny MP table that SuperMicro puts in. I haven't tried it in UP mode to see if there is a problem there. I hope to try the MP table patches that Tor put together in a couple of days. Just my 2 cents worth. Lars -- ------------------------------------------------------------------- Lars Fredriksen fredriks@mcs.com (home) lars@odin-corporation.com (home-home) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 01:41:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08290 for freebsd-current-outgoing; Wed, 18 Mar 1998 01:41:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA08285 for ; Wed, 18 Mar 1998 01:41:30 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: (qmail 28837 invoked from network); 18 Mar 1998 09:41:26 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-01.cdsnet.net with SMTP; 18 Mar 1998 09:41:26 -0000 Date: Wed, 18 Mar 1998 01:41:26 -0800 (PST) From: Jaye Mathisen To: current@FreeBSD.ORG Subject: Stream_d benchmark... Wow, there really are differences in hardware 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 figured that within reason, most mb's would have similar performance, but I was wrong. All boxes are P6-200's, 256MB RAM (all RAM is 60ns FP as far as I know). Box 1 is a SuperMicro P6DNE: Function Rate (MB/s) RMS time Min time Max time Copy: 60.7395 0.2704 0.2634 0.2832 Scale: 60.8640 0.2719 0.2629 0.3097 Add: 70.9688 0.3508 0.3382 0.3602 Triad: 71.1647 0.3494 0.3372 0.3565 Box 2 is a Digital Prioris HX6000 Function Rate (MB/s) RMS time Min time Max time Copy: 73.3551 0.2197 0.2181 0.2249 Scale: 74.6067 0.2164 0.2145 0.2182 Add: 81.0584 0.2974 0.2961 0.3002 Triad: 77.4268 0.3108 0.3100 0.3122 Box 3 is a Digital Prioris ZX6000 Function Rate (MB/s) RMS time Min time Max time Copy: 84.8807 0.2018 0.1885 0.2834 Scale: 97.5461 0.1661 0.1640 0.1720 Add: 111.6549 0.2179 0.2149 0.2247 Triad: 100.9468 0.2659 0.2377 0.4237 Box 3 uses 256bit interleaved memory, rather than whatever the "standard" is. I thought it was just a marketing gimmick, but it seems to really make a difference. Have to see if it helps on some worldstone's. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 01:51:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13222 for freebsd-current-outgoing; Wed, 18 Mar 1998 01:51:39 -0800 (PST) (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 BAA13147 for ; Wed, 18 Mar 1998 01:51:33 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 21504 invoked from network); 18 Mar 1998 09:57:57 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 18 Mar 1998 09:57:57 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-031298 [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: <199803180708.BAA10857@Mercury.mcs.net> Date: Wed, 18 Mar 1998 01:57:57 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Lars Fredriksen Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) Cc: thyerm@camtech.net.au, mike@smith.net.au, current@FreeBSD.ORG, nate@mt.sri.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Mar-98 Lars Fredriksen wrote: > Simon Shapiro writes: ... > Hi, > I also see lots of : > sio3: 151 more interrupt-level buffer overflows (total 151) > > Usually serveral thousands per day. All mine are from ppp using the > serial link. When using netscape it makes the problem worse but linx > hardly ever causes problem. Just as Simon did attribute the problem > related to DPT, mine seems related to disk access as well. I am using > the ahc driver (cam at the moment), and I wonder if my problems doesn't > stem from the funny MP table that SuperMicro puts in. I haven't tried it > in UP mode to see if there is a problem there. > > I hope to try the MP table patches that Tor put together in a couple of > days. I have done so on a test machine, but have no guts to put it on nomis, or sendero (production). One failure is on SuperMicro, but the other is on an Intel SMP board, which is quite different. If the ahc, with CAM is now capable of fast interrupts, they may collide with the FreeBSD Fast Interrupts code. I do not think this is SuperMicro related, not X, nor DPT, nor CAM problem. I think it is a general problem, that these combinations bring to tthe surface. Sort of reminds me of Linux, they use only (what we call) Fast Interrupts (NMI is more like it), and they also lose interrupts, unles they tweak and tweak and tweak. ---------- 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 Wed Mar 18 02:10:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA22731 for freebsd-current-outgoing; Wed, 18 Mar 1998 02:10:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.com.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22528 for ; Wed, 18 Mar 1998 02:09:54 -0800 (PST) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-13-40.camtech.net.au [203.55.242.104]) by goliath.camtech.com.au (8.8.5/8.8.2) with ESMTP id UAA24761; Wed, 18 Mar 1998 20:36:52 +1030 (CST) Message-ID: <350F9CE6.6C389FB0@camtech.net.au> Date: Wed, 18 Mar 1998 20:37:34 +1030 From: Matthew Thyer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: shimon@simon-shapiro.org CC: Lars Fredriksen , mike@smith.net.au, current@FreeBSD.ORG, nate@mt.sri.com Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a bit more info for the puzzle.... I put the following option back into my /etc/XF86Config file the other day and did manage to get the odd silo overflow. Option "pci_retry" But, I was getting far fewer than earlier. So I'd say that XFree86 is not the cause but rather brings the bug to the surface. Since I have removed the above option again, I have not had one silo overflow. Simon Shapiro wrote: > > On 18-Mar-98 Lars Fredriksen wrote: > > Simon Shapiro writes: > ... > > > Hi, > > I also see lots of : > > sio3: 151 more interrupt-level buffer overflows (total 151) > > > > Usually serveral thousands per day. All mine are from ppp using the > > serial link. When using netscape it makes the problem worse but linx > > hardly ever causes problem. Just as Simon did attribute the problem > > related to DPT, mine seems related to disk access as well. I am using > > the ahc driver (cam at the moment), and I wonder if my problems doesn't > > stem from the funny MP table that SuperMicro puts in. I haven't tried it > > in UP mode to see if there is a problem there. > > > > I hope to try the MP table patches that Tor put together in a couple of > > days. > > I have done so on a test machine, but have no guts to put it on nomis, or > sendero (production). One failure is on SuperMicro, but the other is on an > Intel SMP board, which is quite different. If the ahc, with CAM is now > capable of fast interrupts, they may collide with the FreeBSD Fast > Interrupts code. I do not think this is SuperMicro related, not X, nor > DPT, nor CAM problem. I think it is a general problem, that these > combinations bring to tthe surface. Sort of reminds me of Linux, they use > only (what we call) Fast Interrupts (NMI is more like it), and they also > lose interrupts, unles they tweak and tweak and tweak. > > ---------- > > Sincerely Yours, > > Simon Shapiro > Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 02:57:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10487 for freebsd-current-outgoing; Wed, 18 Mar 1998 02:57:59 -0800 (PST) (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 CAA10466 for ; Wed, 18 Mar 1998 02:57:53 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id LAA01642; Wed, 18 Mar 1998 11:57:29 +0100 (MET) (envelope-from sos) Message-Id: <199803181057.LAA01642@sos.freebsd.dk> Subject: Re: Stream_d benchmark... Wow, there really are differences in hardware In-Reply-To: from Jaye Mathisen at "Mar 18, 98 01:41:26 am" To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Wed, 18 Mar 1998 11:57:28 +0100 (MET) Cc: 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 Jaye Mathisen who wrote: Hmm, Then I should be proud of my noname system (p6/200/128MB 72pEDO): Function Rate (MB/s) RMS time Min time Max time Copy: 117.0286 0.2758 0.2734 0.2812 Scale: 117.0286 0.2782 0.2734 0.2812 Add: 130.7234 0.3784 0.3672 0.4141 Triad: 125.3878 0.3917 0.3828 0.4219 So what ?? > > > I figured that within reason, most mb's would have similar performance, > but I was wrong. > > All boxes are P6-200's, 256MB RAM (all RAM is 60ns FP as far as I know). > > Box 1 is a SuperMicro P6DNE: > Function Rate (MB/s) RMS time Min time Max time > Copy: 60.7395 0.2704 0.2634 0.2832 > Scale: 60.8640 0.2719 0.2629 0.3097 > Add: 70.9688 0.3508 0.3382 0.3602 > Triad: 71.1647 0.3494 0.3372 0.3565 > > > Box 2 is a Digital Prioris HX6000 > Function Rate (MB/s) RMS time Min time Max time > Copy: 73.3551 0.2197 0.2181 0.2249 > Scale: 74.6067 0.2164 0.2145 0.2182 > Add: 81.0584 0.2974 0.2961 0.3002 > Triad: 77.4268 0.3108 0.3100 0.3122 > > Box 3 is a Digital Prioris ZX6000 > Function Rate (MB/s) RMS time Min time Max time > Copy: 84.8807 0.2018 0.1885 0.2834 > Scale: 97.5461 0.1661 0.1640 0.1720 > Add: 111.6549 0.2179 0.2149 0.2247 > Triad: 100.9468 0.2659 0.2377 0.4237 > > > Box 3 uses 256bit interleaved memory, rather than whatever the > "standard" is. > > > I thought it was just a marketing gimmick, but it seems to really > make a difference. > > > > Have to see if it helps on some worldstone's. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Mar 18 04:47:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26711 for freebsd-current-outgoing; Wed, 18 Mar 1998 04:47:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA26705 for ; Wed, 18 Mar 1998 04:47:23 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg by adelphi.physics.adelaide.edu.au (5.65/AndrewR-930902) id AA09626; Wed, 18 Mar 1998 23:11:16 +1030 Received: by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA17943; Wed, 18 Mar 1998 23:11:16 +1030 Date: Wed, 18 Mar 1998 23:11:15 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Matthew Thyer Cc: Andrew Reilly , current@FreeBSD.ORG Subject: Re: Disk munging problem with current solved In-Reply-To: <350F5F12.A8334298@dsto.defence.gov.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Mar 1998, Matthew Thyer wrote: > I use it all the time as I'm behind a firewall at work and cant > use cvsup. If you have an account on a machine which has unshielded access to the net (e.g. the firewall machine itself) you can install a SOCKS proxy on the machine and use it as a gateway to traverse the firewall for things like cvsup (and ftp, telnet, etc). If set up correctly this is a secure gateway to the outside. You dont even need root access on the machine to do this (though you probably should clear it first, depending on how tight your site security policy is). Using this you can then use m3socks to get cvsup talking through the SOCK proxy. Kris WOWBO /\ . Through the darkness of future past, /\ . BWOWB OBWOW /##\/#\ The Magician longs to see. /##\/#\ BOBWO WBOBW / \ One chance out between two worlds, / \ OWBOB WOWBO / \ Fire, Walk with me! / \ BWOWB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 06:21:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16550 for freebsd-current-outgoing; Wed, 18 Mar 1998 06:21:48 -0800 (PST) (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 GAA16450 for ; Wed, 18 Mar 1998 06:21:08 -0800 (PST) (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 OAA06940 for ; Wed, 18 Mar 1998 14:20:50 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id JAA01147 for freebsd-current@freebsd.org; Wed, 18 Mar 1998 09:20:49 -0500 (EST) From: Mikhail Teterin Message-Id: <199803181420.JAA01147@rtfm.ziplink.net> Subject: Re: Jordan's response to Justin A. K. (was Re: Emulated Quake2 a no-go) In-Reply-To: <199803180519.VAA08348@rah.star-gate.com> from "Amancio Hasty" at "Mar 17, 98 09:19:57 pm" To: freebsd-current@FreeBSD.ORG Date: Wed, 18 Mar 1998 09:20:49 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Both of the couple of things, while beautifully worded, do not => directly apply to the original complaint, IMHO. Justin A Kolodziej => was, AFAIU, upset about the _tone_ with which he was directed to => the information. He was (convincingly, at least, for me) arguing, => that his question was indeed relevant to -current. The fact, that => Quake was already discussed on -multimedia and/or that people there => know/care about Quake more is not immediately obvious. Respectfully, =You DON"T LIKE MY TONE ---- YOU GOT TO BE KIDDING ME . I believe, I so far managed to avoid expressing my own opinion about it. If you ask, though, I think, that it is a very common problem -- a person who knows something underestimates how hard (or possible) it is to obtain this knowledge without asking. This includes all kinds of knowledge from cooking, to NFS setup, to the relevance of particular questions to particular mailing lists. =I bet that you guys are joking, right?? At least one person was/is so upset, the honorable President had to intervene :) -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 06:32:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18685 for freebsd-current-outgoing; Wed, 18 Mar 1998 06:32:10 -0800 (PST) (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 GAA18556 for ; Wed, 18 Mar 1998 06:31:14 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id JAA02459; Wed, 18 Mar 1998 09:29:52 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 18 Mar 1998 09:29:52 -0500 (EST) From: "Alok K. Dhir" To: ortmann@sparc.isl.net cc: current@FreeBSD.ORG Subject: Re: Worldstone Continued... 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, 17 Mar 1998 ortmann@sparc.isl.net wrote: > > OK - I got a lot out of our last discussion, and now my -current > > world builds in 1:23 (!!). This is WITHOUT softupdates, but using > > async mounts... > > Were you the gentleman who posted about compiling in 6+/4+ hours? Indeed - that was me. My original post claimed ~6 to ~2.5 due to softupdates. The ~6 was heavily disputed, though, and I had to concede that it may have been substantially less, like ~4. > What were the main tricks to speeding your system up? 1. I seperated /usr/src and /usr/obj onto two seperate physical disks. 2. I uncommented the "CFLAGS= -O -pipe" line in /etc/make.conf (which really ought to be the default). 3. I mounted both disks async (I thought some crashes/hangs I was having may have been related to softupdates). Since then, I have gone back to softupdates (since I traced the problem to something other than softupdates). In fact, I don't believe I've had a single softupdates related crash so far (* knock knock *). I haven't reran the worldstone test yet, though. I'm waiting for the recent rash of -current problems to settle a bit. > (I have been less impressed than I could have been using async,noatime.) For speeding up writes, there's nothing like softupdates (if you're brave, and the system is not for production use that is...). > Thanks! No problem. Cheers! -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ R7-003, ITSMC 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 Wed Mar 18 08:23:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05031 for freebsd-current-outgoing; Wed, 18 Mar 1998 08:23:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05026 for ; Wed, 18 Mar 1998 08:23:18 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id IAA20128; Wed, 18 Mar 1998 08:23:03 -0800 (PST) (envelope-from jdp) Message-Id: <199803181623.IAA20128@austin.polstra.com> To: Matthew.Thyer@dsto.defence.gov.au Subject: Re: Disk munging problem with current solved In-Reply-To: <350F5F12.A8334298@dsto.defence.gov.au> References: <199803172339.KAA23059@gurney.reilly.home> <350F5F12.A8334298@dsto.defence.gov.au> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Wed, 18 Mar 1998 08:23:03 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <350F5F12.A8334298@dsto.defence.gov.au>, Matthew Thyer wrote: > ctm-ports-cur is still available. > > I use it all the time as I'm behind a firewall at work and cant > use cvsup. Does your firewall allow you to make simple outbound TCP connections? If you can connect outbound to port 5999, and if you specify "-P m" on the cvsup command line, then it will work through your firewall. I just mention this because a lot of people aren't aware of it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 09:01:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10592 for freebsd-current-outgoing; Wed, 18 Mar 1998 09:01:48 -0800 (PST) (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 JAA10571 for ; Wed, 18 Mar 1998 09:01:43 -0800 (PST) (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 MAA24371; Wed, 18 Mar 1998 12:01:09 -0500 (EST) X-Sender: ckempfm@enigami.com Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 18 Mar 1998 11:59:37 -0500 To: freebsd-current@FreeBSD.ORG From: Cory Kempf Subject: Kernel / Compiler bug? Cc: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry if this is a re-run, but it looks like the original got lost somewhere. This problem may be CAM specific. I am not sure what to do about this one. Since I got my machine I have not been able to build a kernel that runs, without using "swap on generic" and -a at the boot prompt Well, after doing some debugging, it looks like the line dev_t rootdev = makedev(4, 0x000020000); in swapkernel.c (/usr/src/sys/compile//swapkernel.c) isn't being run. The fatal trap 12 I was getting is caused by major(rootdev) being 0, thus deferencing bdevsw[major(rootdev)] deferences null. If I copy the rootdev assignment into setconf() (in swapkernel.c), the resultant kernel does not need the "swap on generic", and will happily boot unattended. Anyway, yes, I realize that the global variable *should* be set. On my machine thoough, using a freshly built system from current sources (e.g. this week), it isn't. So, what need to be done to get this fix in place? It seems I am not the only one with this problem. +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 Wed Mar 18 09:03:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11140 for freebsd-current-outgoing; Wed, 18 Mar 1998 09:03:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from george.arc.nasa.gov (george.arc.nasa.gov [128.102.194.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11121 for ; Wed, 18 Mar 1998 09:03:27 -0800 (PST) (envelope-from lamaster@george.arc.nasa.gov) Received: (from lamaster@localhost) by george.arc.nasa.gov (8.8.7/8.8.7) id IAA02816; Wed, 18 Mar 1998 08:58:06 -0800 (PST) From: Hugh LaMaster Message-Id: <199803181658.IAA02816@george.arc.nasa.gov> Subject: Re: Stream_d benchmark... Wow, there really are differences in hardware To: freebsd-current@FreeBSD.ORG Date: Wed, 18 Mar 1998 08:58:06 -0800 (PST) Cc: lamaster@george.arc.nasa.gov In-Reply-To: <199803181057.LAA01642@sos.freebsd.dk> from "Søren Schmidt" at Mar 18, 98 11:57:28 am X-Mailer: ELM [version 2.4 PL24] 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 Soeren Schmidt (sos@FreeBSD.org) wrote: > In reply to Jaye Mathisen who wrote: > > Hmm, Then I should be proud of my noname system (p6/200/128MB 72pEDO): > > Function Rate (MB/s) RMS time Min time Max time > Copy: 117.0286 0.2758 0.2734 0.2812 : > Triad: 125.3878 0.3917 0.3828 0.4219 > > So what ?? Like all benchmarks, there is the question of "pride". However, computer performance is also a major problem/interest, and, stream is particularly informative for a "toy benchmark". Your numbers seem very high for a Natoma board - what type of EDO are you using and what are your BIOS settings? Exactly what kind of "noname" board is it? If these numbers are correct, I want one. Have you run the c't ctcm benchmark on it also? That gives a nice profile of the different memory bandwidth numbers from L1 cache, L2 cache, and main memory. [Note also, stream sometimes doesn't get the clock HZ set properly. Are you sure it is correct with these numbers?] [Maybe you have the 45ns EDO? What are your leadoff timings?] I'm impressed, anyway. I want to know more. In particular, I might be better off with one of your "noname" configurations than a 333 MHz P - II for driving some fast network interfaces. Your numbers look more like one of the specially-built and tweaked expensive "server" Orion boards. > > I figured that within reason, most mb's would have similar performance, > > but I was wrong. First of all, it depends on the chipset. Does the Digital Prioris ZX6000 system use the Orion chipset? It appears so. Note also whether using FP DRAM or EDO, and, how fast the memory is (the BIOS settings for lead-off timings may be slightly more aggressive for slightly faster memory. > > All boxes are P6-200's, 256MB RAM (all RAM is 60ns FP as far as I know). > > > > Box 1 is a SuperMicro P6DNE: > > Function Rate (MB/s) RMS time Min time Max time > > Copy: 60.7395 0.2704 0.2634 0.2832 > > Triad: 71.1647 0.3494 0.3372 0.3565 Typical for Natoma with FP DRAM I would guess. > > > Box 2 is a Digital Prioris HX6000 > > Copy: 73.3551 0.2197 0.2181 0.2249 > > Triad: 77.4268 0.3108 0.3100 0.3122 Is this with EDO? > > Box 3 is a Digital Prioris ZX6000 > > Function Rate (MB/s) RMS time Min time Max time > > Copy: 84.8807 0.2018 0.1885 0.2834 > > Scale: 97.5461 0.1661 0.1640 0.1720 > > Add: 111.6549 0.2179 0.2149 0.2247 > > Triad: 100.9468 0.2659 0.2377 0.4237 > > > > > > Box 3 uses 256bit interleaved memory, rather than whatever the > > "standard" is. I assume that this is an Orion GX chipset board. Yes, it does have higher memory bandwidth than Natoma if properly configured. Yes, IMHO, that does make a significant difference in the real world. > > I thought it was just a marketing gimmick, but it seems to really > > make a difference. Orion chipset boards had kind of a negative press at first due to problems with PCI bandwidth, but, I assume (?) those were worked out long ago. In any case, the Orion chipset never achieved the mass-market commodity status of Natoma chipset. As a consequence, boards remained, and remain expensive, and now, the PPro200 is being phased out. I wouldn't mind having one, but, there are only a few, expensive boards out there, such as the American Megatrends Goliath, and PPro200 prices never dropped that much, I guess because Intel wanted to phase it out in favor of the P-II. > > Have to see if it helps on some worldstone's. It should help a little bit, although, the real benefit tends to be on user apps which stream through a lot of memory. The classical FP applications, of course, but also, things like digital video, image processing, graphics, etc. - anything which streams through 1-4 MB of memory repeatedly. And, network performance to/from userland, which usually requires at least one data copy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 09:17:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13753 for freebsd-current-outgoing; Wed, 18 Mar 1998 09:17:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from george.arc.nasa.gov (george.arc.nasa.gov [128.102.194.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13747 for ; Wed, 18 Mar 1998 09:17:36 -0800 (PST) (envelope-from lamaster@george.arc.nasa.gov) Received: (from lamaster@localhost) by george.arc.nasa.gov (8.8.7/8.8.7) id JAA05027; Wed, 18 Mar 1998 09:12:43 -0800 (PST) From: Hugh LaMaster Message-Id: <199803181712.JAA05027@george.arc.nasa.gov> Subject: Re: Worldstone Continued... To: current@FreeBSD.ORG Date: Wed, 18 Mar 1998 09:12:42 -0800 (PST) Cc: lamaster@george.arc.nasa.gov In-Reply-To: from "Alok K. Dhir" at Mar 18, 98 09:29:52 am X-Mailer: ELM [version 2.4 PL24] 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 (adhir@worldbank.org) wrote: > On Tue, 17 Mar 1998 ortmann@sparc.isl.net wrote: > > > > OK - I got a lot out of our last discussion, and now my -current > > > world builds in 1:23 (!!). This is WITHOUT softupdates, but using > > > async mounts... > > > > Were you the gentleman who posted about compiling in 6+/4+ hours? : > > What were the main tricks to speeding your system up? > > 1. I seperated /usr/src and /usr/obj onto two seperate physical disks. I just wanted to note that while everyone getting ~1:20 has done this, the 6/4 hours for NOT doing it makes me think that the disks used must be have unusually slow seeks (for today) or something, because, I get < 3 hrs on a single disk, single filesystem, for all of /usr, with with everything sync (or not async, however you want to say it). I do have -O -pipe as below: > 2. I uncommented the "CFLAGS= -O -pipe" line in /etc/make.conf (which > really ought to be the default). > 3. I mounted both disks async (I thought some crashes/hangs I was having > may have been related to softupdates). > > (I have been less impressed than I could have been using async,noatime.) > > For speeding up writes, there's nothing like softupdates (if you're brave, > and the system is not for production use that is...). I don't think any of this is disputed, but, if the very long timings from before are correct, I would like to suggest that you get some faster-seeking disks for your system- e.g. people posting higher numbers often use disks with fast seeks such as Quantum Atlas series, Seagate Barracuda or Cheetah, IBM Ultrastar 2ES or 2XP, ... Then, you might see that number drop even further. The goal, in my mind, is do to a complete buildworld and installworld in less than an hour. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 09:26:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16062 for freebsd-current-outgoing; Wed, 18 Mar 1998 09:26:29 -0800 (PST) (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 JAA16027 for ; Wed, 18 Mar 1998 09:26:22 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id SAA02309; Wed, 18 Mar 1998 18:25:51 +0100 (MET) (envelope-from sos) Message-Id: <199803181725.SAA02309@sos.freebsd.dk> Subject: Re: Stream_d benchmark... Wow, there really are differences in hardware In-Reply-To: <199803181658.IAA02816@george.arc.nasa.gov> from Hugh LaMaster at "Mar 18, 98 08:58:06 am" To: lamaster@george.arc.nasa.gov (Hugh LaMaster) Date: Wed, 18 Mar 1998 18:25:51 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG, lamaster@george.arc.nasa.gov 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 Hugh LaMaster who wrote: > > Soeren Schmidt (sos@FreeBSD.org) wrote: > > In reply to Jaye Mathisen who wrote: > > > > Hmm, Then I should be proud of my noname system (p6/200/128MB 72pEDO): > > > > Function Rate (MB/s) RMS time Min time Max time > > Copy: 117.0286 0.2758 0.2734 0.2812 > : > > Triad: 125.3878 0.3917 0.3828 0.4219 > > > > So what ?? > > Like all benchmarks, there is the question of "pride". However, > computer performance is also a major problem/interest, and, stream > is particularly informative for a "toy benchmark". Your numbers > seem very high for a Natoma board - what type of EDO are you using > and what are your BIOS settings? Exactly what kind of "noname" board > is it? If these numbers are correct, I want one. Have you run the > c't ctcm benchmark on it also? That gives a nice profile of the > different memory bandwidth numbers from L1 cache, L2 cache, and > main memory. [Note also, stream sometimes doesn't get the clock > HZ set properly. Are you sure it is correct with these numbers?] > [Maybe you have the 45ns EDO? What are your leadoff timings?] > I'm impressed, anyway. I want to know more. In particular, I might > be better off with one of your "noname" configurations than a 333 MHz > P - II for driving some fast network interfaces. Your numbers look > more like one of the specially-built and tweaked expensive "server" > Orion boards. Well, "noname" was more in the sort that its not a "brand name" machine, but one build out of garden varity parts. It's a TYAN s1662D dual PPro board with dual P6/200/256K, memory is 4 stock 32Mb 72pin 60Ns EDO RAM. Timing is set as std for the 4.0E BIOS with 60Ns memory timing, disks are two Maxtor DiamondMax 4.3G in DMA mode. I havn't run the CT benchmark, I'd have to find a DOS disk somewhere to do that. On the whole TYAN is know to have a much more agressive memory timing than say ASUS, and the board is pretty picky about RAM quality (I use Hyundai here). Worldstone (a WHOLE world with -j9 -O -pipe and src & obj async on different disks) on this machine is ~1h10min dependend on how much happens in between (it runs X during the make as I have no text console :) ). -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Mar 18 10:21:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26335 for freebsd-current-outgoing; Wed, 18 Mar 1998 10:21:35 -0800 (PST) (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 KAA26327 for ; Wed, 18 Mar 1998 10:21:33 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id NAA00740; Wed, 18 Mar 1998 13:20:16 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 18 Mar 1998 13:20:16 -0500 (EST) From: "Alok K. Dhir" To: lamaster@george.arc.nasa.gov cc: current@FreeBSD.ORG Subject: Re: Worldstone Continued... 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 Wed, 18 Mar 1998 lamaster@george.arc.nasa.gov wrote: > Then, you might see that number drop even further. The goal, in my > mind, is do to a complete buildworld and installworld in less than > an hour. I wouldn't be surprised to see my 1:20 go under an hour with softupdates. I'll keep you posted... -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ R7-003, ITSMC 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 Wed Mar 18 10:57:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02949 for freebsd-current-outgoing; Wed, 18 Mar 1998 10:57:12 -0800 (PST) (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 KAA02943 for ; Wed, 18 Mar 1998 10:57:10 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id KAA17189; Wed, 18 Mar 1998 10:56:49 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803181856.KAA17189@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mikhail Teterin cc: freebsd-current@FreeBSD.ORG Subject: Re: Jordan's response to Justin A. K. (was Re: Emulated Quake2 a no-go) In-reply-to: Your message of "Wed, 18 Mar 1998 09:20:49 EST." <199803181420.JAA01147@rtfm.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Mar 1998 10:56:49 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is Okay to ask and I am fully aware that we have people that are afraid to ask however I don't deal with that issue thats an entirely different mailing list 8) Relax and Have Fun not sure about where you guys are however the weather here in San Francisco is gorgeous --- in fact to hell with you guys --- where are my sunglasses. Later Dudes 8) Amancio > Amancio Hasty once stated: > > => Both of the couple of things, while beautifully worded, do not > => directly apply to the original complaint, IMHO. Justin A Kolodziej > => was, AFAIU, upset about the _tone_ with which he was directed to > => the information. He was (convincingly, at least, for me) arguing, > => that his question was indeed relevant to -current. The fact, that > => Quake was already discussed on -multimedia and/or that people there > => know/care about Quake more is not immediately obvious. Respectfully, > > =You DON"T LIKE MY TONE ---- YOU GOT TO BE KIDDING ME . > > I believe, I so far managed to avoid expressing my own opinion > about it. If you ask, though, I think, that it is a very common > problem -- a person who knows something underestimates how hard > (or possible) it is to obtain this knowledge without asking. This > includes all kinds of knowledge from cooking, to NFS setup, to the > relevance of particular questions to particular mailing lists. > > =I bet that you guys are joking, right?? > > At least one person was/is so upset, the honorable President had > to intervene :) > > -mi > > 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 Mar 18 13:28:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26665 for freebsd-current-outgoing; Wed, 18 Mar 1998 13:28:57 -0800 (PST) (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 NAA26660 for ; Wed, 18 Mar 1998 13:28:55 -0800 (PST) (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 NAA23054; Wed, 18 Mar 1998 13:25:48 -0800 (PST) Message-Id: <199803182125.NAA23054@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: FreeBSD current users Subject: Re: Memory leak in inetd in last week's -current? In-reply-to: Your message of "Wed, 18 Mar 1998 08:44:14 +1030." <19980318084414.07315@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Mar 1998 13:25:46 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've just discovered that my inetd has been rejecting connections with > the following message: > > $ ftp ftp.lemis.com > Connected to freebie.lemis.com. > inetd in realloc(): warning: junk pointer, too high to make sense. > ftp> > > I took a ktrace of it happening, if that's of any use, and restarted > inetd, which made the problem go away. Any ideas? Bug in inetd, normally associated with malloc failure (system out of memory). Possibly bad use of a low (nonzero) magic pointer value, or possibly attempting to use a pointer to a static item as a substitute. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 13:43:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28489 for freebsd-current-outgoing; Wed, 18 Mar 1998 13:43:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (danberlin.resnet.rochester.edu [128.151.91.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28476 for ; Wed, 18 Mar 1998 13:43:00 -0800 (PST) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (8.8.8/8.8.8) with SMTP id QAA00502; Wed, 18 Mar 1998 16:37:56 -0500 (EST) (envelope-from root@danberlin.resnet.rochester.edu) Date: Wed, 18 Mar 1998 16:37:56 -0500 (EST) From: Daniel Berlin To: Mike Smith cc: Greg Lehey , FreeBSD current users Subject: Re: Memory leak in inetd in last week's -current? In-Reply-To: <199803182125.NAA23054@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 Ah, i had fun with that message yesterday while converting tin 1.4pre's local xover caching to use zlib. was tired of huge local cache files in 40000 article newsgroups. cache size went from about 10 meg to about 2 when i was finished. Only took 30 minutes too. I had gotten this message while stupidly forgetting that one of the reading functions makes a recursive call to itself and was expecting a FILE * when I gave it a gzFile *. It didn't give an error on compilation, but while running the tin_fgets function would fail with that error message. On Wed, 18 Mar 1998, Mike Smith wrote: > Bug in inetd, normally associated with malloc failure (system out of > memory). > > Possibly bad use of a low (nonzero) magic pointer value, or possibly > attempting to use a pointer to a static item as a substitute. > > -- > \\ 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 13:46:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29324 for freebsd-current-outgoing; Wed, 18 Mar 1998 13:46:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.video-collage.com (www.video-collage.com [206.15.171.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29309 for ; Wed, 18 Mar 1998 13:46:31 -0800 (PST) (envelope-from mi@xxx.video-collage.com) Received: from xxx.video-collage.com (xxx.video-collage.com [199.232.254.68]) by www.video-collage.com (8.8.5/8.8.5) with ESMTP id QAA15617 for ; Wed, 18 Mar 1998 16:45:12 -0500 (EST) Received: (from mi@localhost) by xxx.video-collage.com (8.8.8/8.8.7) id QAA05712 for freebsd-current@freebsd.org; Wed, 18 Mar 1998 16:46:23 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199803182146.QAA05712@xxx.video-collage.com> Subject: StarOffice In-Reply-To: <199803182054.MAA22897@dingo.cdrom.com> from Mike Smith at "Mar 18, 98 12:54:21 pm" To: freebsd-current@FreeBSD.ORG Date: Wed, 18 Mar 1998 16:46:23 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Another problem child is StarOffice-4.0 for Linux. It runs, but eats => up all the shared memory. It does not release it when exits either -- => requires an explicit ``ipcrm'' . Fortunately, the output of ``ipcs'' => is easy to parse :) = =SO4 runs fine under -current on some systems, but not others. It seems =to be extremely sensitive to trivial things. Well, runs for me. And I have the script to clean up after it already. I just thought it may be usefull for the developers to know about the shared memory anomalies as related to Linux emulation/whatever else. =If you are just looking for a wordprocessor, I strongly recommend =Wordperfect 7. (start at www.turbolinux.com) AFAIK, Wordperfect is not free. StarOffice for Linux is free for personal use... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 13:47:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29712 for freebsd-current-outgoing; Wed, 18 Mar 1998 13:47:58 -0800 (PST) (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 NAA29618 for ; Wed, 18 Mar 1998 13:47:44 -0800 (PST) (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 0yFQgR-0007b0-00; Wed, 18 Mar 1998 15:47:35 -0600 X-Mailer: exmh version 2.0zeta 7/24/97 To: Hugh LaMaster cc: freebsd-current@FreeBSD.ORG Subject: Re: Stream_d benchmark... Wow, there really are differences in hardware In-reply-to: Your message of "Wed, 18 Mar 1998 08:58:06 PST." <199803181658.IAA02816@george.arc.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Mar 1998 15:47:34 -0600 From: Ted Spradley Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Like all benchmarks, there is the question of "pride". However, > computer performance is also a major problem/interest, and, stream > is particularly informative for a "toy benchmark". OK, just what is this "stream_d" and where can I find out more? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 13:50:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00854 for freebsd-current-outgoing; Wed, 18 Mar 1998 13:50:15 -0800 (PST) (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 NAA00642 for ; Wed, 18 Mar 1998 13:49:37 -0800 (PST) (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 WAA00589; Wed, 18 Mar 1998 22:47:03 +0100 (CET) To: Mike Smith cc: Greg Lehey , FreeBSD current users Subject: Re: Memory leak in inetd in last week's -current? In-reply-to: Your message of "Wed, 18 Mar 1998 13:25:46 PST." <199803182125.NAA23054@dingo.cdrom.com> Date: Wed, 18 Mar 1998 22:47:03 +0100 Message-ID: <587.890257623@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199803182125.NAA23054@dingo.cdrom.com>, Mike Smith writes: >> I've just discovered that my inetd has been rejecting connections with >> the following message: >> >> $ ftp ftp.lemis.com >> Connected to freebie.lemis.com. >> inetd in realloc(): warning: junk pointer, too high to make sense. >> ftp> >> >> I took a ktrace of it happening, if that's of any use, and restarted >> inetd, which made the problem go away. Any ideas? > >Bug in inetd, normally associated with malloc failure (system out of >memory). > >Possibly bad use of a low (nonzero) magic pointer value, or possibly >attempting to use a pointer to a static item as a substitute. Wrong. It says "too >high< to make sense". Likely causes: pointer to a stack item pointer to a previously free'ed piece of memory. pointer to mmaped memory, for instance shlib data uninitialized pointer. Technically it means that the pointer is higher than sbrk(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 Wed Mar 18 13:50:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00972 for freebsd-current-outgoing; Wed, 18 Mar 1998 13:50:53 -0800 (PST) (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 NAA00941 for ; Wed, 18 Mar 1998 13:50:39 -0800 (PST) (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 IAA11128; Thu, 19 Mar 1998 08:20:34 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id IAA12474; Thu, 19 Mar 1998 08:20:33 +1030 (CST) (envelope-from grog) Message-ID: <19980319082033.12206@freebie.lemis.com> Date: Thu, 19 Mar 1998 08:20:33 +1030 From: Greg Lehey To: Poul-Henning Kamp , Mike Smith Cc: FreeBSD current users Subject: Re: Memory leak in inetd in last week's -current? References: <199803182125.NAA23054@dingo.cdrom.com> <587.890257623@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <587.890257623@critter.freebsd.dk>; from Poul-Henning Kamp on Wed, Mar 18, 1998 at 10:47:03PM +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 Wed, 18 March 1998 at 22:47:03 +0100, Poul-Henning Kamp wrote: > In message <199803182125.NAA23054@dingo.cdrom.com>, Mike Smith writes: >>> I've just discovered that my inetd has been rejecting connections with >>> the following message: >>> >>> $ ftp ftp.lemis.com >>> Connected to freebie.lemis.com. >>> inetd in realloc(): warning: junk pointer, too high to make sense. >>> ftp> >>> >>> I took a ktrace of it happening, if that's of any use, and restarted >>> inetd, which made the problem go away. Any ideas? >> >> Bug in inetd, normally associated with malloc failure (system out of >> memory). >> >> Possibly bad use of a low (nonzero) magic pointer value, or possibly >> attempting to use a pointer to a static item as a substitute. > > Wrong. > > It says "too >high< to make sense". > > Likely causes: > > pointer to a stack item > pointer to a previously free'ed piece of memory. > pointer to mmaped memory, for instance shlib data > uninitialized pointer. > > Technically it means that the pointer is higher than sbrk(0). Now *that*'s the kind of information which makes sense to me. OK, that looks like a program logic bug, not the results of loss of swap space (of which I should have always had at least 80 MB over). Any ideas about how to look for this particular needle in a haystack? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 14:14:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05043 for freebsd-current-outgoing; Wed, 18 Mar 1998 14:14:50 -0800 (PST) (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 OAA05023 for ; Wed, 18 Mar 1998 14:14:27 -0800 (PST) (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 XAA00678; Wed, 18 Mar 1998 23:13:33 +0100 (CET) To: Greg Lehey cc: Mike Smith , FreeBSD current users Subject: Re: Memory leak in inetd in last week's -current? In-reply-to: Your message of "Thu, 19 Mar 1998 08:20:33 +1030." <19980319082033.12206@freebie.lemis.com> Date: Wed, 18 Mar 1998 23:13:33 +0100 Message-ID: <676.890259213@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Wrong. >> >> It says "too >high< to make sense". >> >> Likely causes: >> >> pointer to a stack item >> pointer to a previously free'ed piece of memory. >> pointer to mmaped memory, for instance shlib data >> uninitialized pointer. >> >> Technically it means that the pointer is higher than sbrk(0). > >Now *that*'s the kind of information which makes sense to me. > >OK, that looks like a program logic bug, not the results of loss of >swap space (of which I should have always had at least 80 MB over). >Any ideas about how to look for this particular needle in a haystack? You can try to set the AJ options to malloc system wide (see malloc(3)), and see if that makes inetd behave differently. This is the easy thing to do. ("J" costs some performance loss). You may want to make sure that filedescriptor #2 is open to a file somewhere, since that is where malloc will write diagnostics. Doing it by code inspection should also be easy in this case: the message comes after the fork, and after filedescriptor #2 has been associated with the socket. Look at the code after that point and try to find direct calls to free() or indirect ones (fclose ?) If you can reproduce it, run it under a debugger... -- 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 Wed Mar 18 14:41:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11654 for freebsd-current-outgoing; Wed, 18 Mar 1998 14:41:41 -0800 (PST) (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 OAA11604 for ; Wed, 18 Mar 1998 14:41:35 -0800 (PST) (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (tnt189.wcc.net [208.10.139.189]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id QAA18062; Wed, 18 Mar 1998 16:37:24 -0600 (CST) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id QAA07391; Wed, 18 Mar 1998 16:40:31 -0600 (CST) (envelope-from joelh) Date: Wed, 18 Mar 1998 16:40:31 -0600 (CST) Message-Id: <199803182240.QAA07391@detlev.UUCP> To: thyerm@camtech.net.au CC: c5666305@comp.polyu.edu.hk, current@FreeBSD.ORG In-reply-to: <350E643D.A47CB903@camtech.net.au> (message from Matthew Thyer on Tue, 17 Mar 1998 22:23:33 +1030) Subject: Re: Disk munging problem with current solved From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> <350E643D.A47CB903@camtech.net.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Note you will also need the last base delta for CURRENT > which you can download from: > ftp://ftp.freebsd.org/pub/FreeBSD/CTM/src-cur/ This reminds me: I noticed that it is possible to cvsup a current ctm tree from ctm.freebsd.org. I expect this to be either an alternative to using a base delta (for instance, now that you'd have to ftp nearly 100 deltas), or to allow you to resync a partially trashed source tree. However, this is missing .ctm-status, which would seem to be fairly important. (I'll also point out, with details that I didn't write down, that manually looking at deltas and figuring out where .ctm-status should be didn't work... I got a lot of missing stuff.) Am I doing something wrong here, or is that just something nobody's bothered with yet? Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 14:42:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11916 for freebsd-current-outgoing; Wed, 18 Mar 1998 14:42:33 -0800 (PST) (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 OAA11877 for ; Wed, 18 Mar 1998 14:42:18 -0800 (PST) (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 OAA23360; Wed, 18 Mar 1998 14:35:03 -0800 (PST) Message-Id: <199803182235.OAA23360@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Poul-Henning Kamp cc: Mike Smith , Greg Lehey , FreeBSD current users Subject: Re: Memory leak in inetd in last week's -current? In-reply-to: Your message of "Wed, 18 Mar 1998 22:47:03 +0100." <587.890257623@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Mar 1998 14:35:00 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199803182125.NAA23054@dingo.cdrom.com>, Mike Smith writes: > >> I've just discovered that my inetd has been rejecting connections with > >> the following message: > >> > >> $ ftp ftp.lemis.com > >> Connected to freebie.lemis.com. > >> inetd in realloc(): warning: junk pointer, too high to make sense. > >> ftp> > >> > >> I took a ktrace of it happening, if that's of any use, and restarted > >> inetd, which made the problem go away. Any ideas? > > > >Bug in inetd, normally associated with malloc failure (system out of > >memory). > > > >Possibly bad use of a low (nonzero) magic pointer value, or possibly > >attempting to use a pointer to a static item as a substitute. > > Wrong. > > It says "too >high< to make sense". Whooops, that's a new one. The normal one is "too low", which makes me wonder (if the two are the same) whether this is "pointer is garbage"? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 15:23:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20515 for freebsd-current-outgoing; Wed, 18 Mar 1998 15:23:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.scitec.com.au (firewall-user@fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20503 for ; Wed, 18 Mar 1998 15:23:06 -0800 (PST) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id JAA21448; Thu, 19 Mar 1998 09:23:01 +1000 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma021418; Thu, 19 Mar 98 09:22:32 +1000 Received: from hydra.scitec.com.au (hydra.scitec.com.au [203.17.182.101]) by mailhub.scitec.com.au (8.6.12/8.6.9) with ESMTP id JAA27532 for ; Thu, 19 Mar 1998 09:22:28 +1000 Received: from scitec.com.au (saruman.scitec.com.au) by hydra.scitec.com.au with ESMTP (1.40.112.8/16.2) id AA113193347; Thu, 19 Mar 1998 10:22:27 +1100 Message-Id: <35105743.5FD43AB5@scitec.com.au> Date: Thu, 19 Mar 1998 10:22:43 +1100 From: John Saunders Organization: SCITEC LIMITED X-Mailer: Mozilla 4.04 [en] (WinNT; I) Mime-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Kernel panic with 2.2.6-BETA as of about a week ago 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 2.2.6-STABLE (as of about 1 week ago) which was working fine on my P5-200MMX 96MB with the filesystems on sd1. Since then my system has been through some changes and it's now a P2-266 128MB with a 6.4G IDE drive (still has the 1G SCSI). So I wanted to move FreeBSD over to the second slice on the IDE drive (the first is FAT32 with Win95). So I partitioned up wd0s2 with disklabel, newfs and used dump and restore to move everything across. However now I get the following message at boot time... panic: vm_fault: fault on nofault entry, addr: f2e3c000 This occurs just after fsck reports that all disks are clean. I then get the syncing disks message with reducing numbers that reduce to 3 (which gets repeated many time) before the system reboots. I can boot up in single user mode and mount all my filesystem so I can do things like rebuilding kernels and stuff. However it doesn't boot to multiuser mode at all. So I tried doing a clean install to wd0 from the 2.2.5-RELEASE CD. The system now boots correctly from wd0 with 2.2.5-RELEASE. So I tried newfs'ing the partitions and moving everything across again and I still get the same panic. So is there anyway I can trace this, i.e. how would I convert f2e3c000 to something meaningful. Can I enable tracing of the rc file as it starts command (I guess one command is going to be trigger the problem). P.S. I originally had trouble putting the disklabel on the wd0 drive as it was complaining about all types of IOCTL errors. But once I rebooted disklabel reported that the label was in fact written, and I got no errors after that when editing it. Actually I have found this to be a common problem when labeling new disks, spent hours trying to get a label onto a ZIP disk. Only after I stumbled on a certain slice configuration would disklabel stop giving me "no space" errors. P.S. One strange thing about the boot manager program. With the 2nd SCSI disk (the FreeBSD sd1 disk) connected I get "F1 = ???" (FAT32 I guess) and "F2 BSD" (which is the IDE partition). However when I remove the 2nd SCSI disk I get a third option "F3 disk 2" appearing. I have a FAT16 SCSI disk (sd0) which I use for building ISO images for CD burning. Cheers. -- +------------------------------------------------------------+ . | John Saunders mailto:John.Saunders@scitec.com.au (Work) | ,--_|\ | mailto:john@nlc.net.au (Home) | / Oz \ | http://www.nlc.net.au/~john/ | \_,--\_/ | SCITEC LIMITED Phone +61 2 9428 9563 Fax +61 2 9428 9933 | v | "By the time you make ends meet, they move the ends." | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 15:31:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22840 for freebsd-current-outgoing; Wed, 18 Mar 1998 15:31:09 -0800 (PST) (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 PAA22817 for ; Wed, 18 Mar 1998 15:31:04 -0800 (PST) (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 XAA12955; Wed, 18 Mar 1998 23:31:02 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id AAA04476; Thu, 19 Mar 1998 00:31:02 +0100 (MET) Message-ID: <19980319003101.63504@follo.net> Date: Thu, 19 Mar 1998 00:31:01 +0100 From: Eivind Eklund To: Greg Lehey Cc: FreeBSD current users Subject: Re: Memory leak in inetd in last week's -current? References: <199803182125.NAA23054@dingo.cdrom.com> <587.890257623@critter.freebsd.dk> <19980319082033.12206@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980319082033.12206@freebie.lemis.com>; from Greg Lehey on Thu, Mar 19, 1998 at 08:20:33AM +1030 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 19, 1998 at 08:20:33AM +1030, Greg Lehey wrote: > OK, that looks like a program logic bug, not the results of loss of > swap space (of which I should have always had at least 80 MB over). > Any ideas about how to look for this particular needle in a haystack? Change free() to abort() instead of printing a message when it gets this error, and examine the coredump. Go from there. You can do this by % export MALLOC_OPTIONS=A before running inetd. % ln -s A /etc/malloc.conf will do the same for all programs. (If I understood the man-page correct, that is. Using the 'contents' of a symbolic link seems weird.) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 16:20:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01854 for freebsd-current-outgoing; Wed, 18 Mar 1998 16:20:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01847 for ; Wed, 18 Mar 1998 16:20:33 -0800 (PST) (envelope-from andrew@zeta.org.au) Received: from gurney.reilly.home (d29.syd2.zeta.org.au [203.26.11.29]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id LAA32065; Thu, 19 Mar 1998 11:18:15 +1100 Received: (from andrew@localhost) by gurney.reilly.home (8.8.8/8.8.5) id KAA02826; Thu, 19 Mar 1998 10:02:00 +1100 (EST) From: Andrew Reilly Message-Id: <199803182302.KAA02826@gurney.reilly.home> Date: Thu, 19 Mar 1998 10:02:00 +1100 (EST) Subject: Re: Worldstone Continued... To: lamaster@george.arc.nasa.gov cc: current@FreeBSD.ORG In-Reply-To: <199803181712.JAA05027@george.arc.nasa.gov> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Mar, Hugh LaMaster wrote: > Then, you might see that number drop even further. The goal, in my > mind, is do to a complete buildworld and installworld in less than > an hour. It would be interesting to see a "speed of light" figure for buildworld. I note that there are some people on this list with access to machines with seriously big DRAM (.5G?) on their systems. I doubt that any one compile operation exercises more than a few Meg, with -pipe. Does anyone have a system that can attempt a buildworld with src and obj in mfs, mounted noasync (if that makes any difference)? (It may not be important. It certainly appears that the 1:20 figure is getting pretty close to being a completely CPU-limited process.) Has anyone on the Alpha port project timed a buildworld? (If the world can be built there yet.) -- Andrew "The steady state of disks is full." -- Ken Thompson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 16:52:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05840 for freebsd-current-outgoing; Wed, 18 Mar 1998 16:52:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05832 for ; Wed, 18 Mar 1998 16:52:21 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id LAA17936; Thu, 19 Mar 1998 11:20:27 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id H1923TPB; Thu, 19 Mar 1998 11:21:06 +0930 Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id LAA15903; Thu, 19 Mar 1998 11:21:48 +1030 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id LAA04580; Thu, 19 Mar 1998 11:21:47 +1030 (CST) Message-ID: <35106C23.64774CD9@dsto.defence.gov.au> Date: Thu, 19 Mar 1998 11:21:47 +1030 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: joelh@gnu.org CC: c5666305@comp.polyu.edu.hk, current@FreeBSD.ORG Subject: Re: Disk munging problem with current solved References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> <350E643D.A47CB903@camtech.net.au> <199803182240.QAA07391@detlev.UUCP> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alas there is no synchronisation between CTM and cvs. Theoretically if you cvsupped at the same time as the person who makes the CTM deltas and you created the .ctm_status file yourself with the right number in it then you'd be right. However if you cvsup 1 minute later a couple of files somewhere in the tree may have been changed and then future CTM deltas would fail to apply. So no, you cannot use both CVS and CTM. Use one or the other but not both. Joel Ray Holveck wrote: > > > Note you will also need the last base delta for CURRENT > > which you can download from: > > ftp://ftp.freebsd.org/pub/FreeBSD/CTM/src-cur/ > > This reminds me: > > I noticed that it is possible to cvsup a current ctm tree from > ctm.freebsd.org. I expect this to be either an alternative to using a > base delta (for instance, now that you'd have to ftp nearly 100 > deltas), or to allow you to resync a partially trashed source tree. > However, this is missing .ctm-status, which would seem to be fairly > important. > > (I'll also point out, with details that I didn't write down, that > manually looking at deltas and figuring out where .ctm-status should > be didn't work... I got a lot of missing stuff.) > > Am I doing something wrong here, or is that just something nobody's > bothered with yet? > > Cheers, > 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 -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 17:55:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15146 for freebsd-current-outgoing; Wed, 18 Mar 1998 17:55:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA15140 for ; Wed, 18 Mar 1998 17:55:02 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: (qmail 5179 invoked from network); 19 Mar 1998 01:55:02 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-01.cdsnet.net with SMTP; 19 Mar 1998 01:55:02 -0000 Date: Wed, 18 Mar 1998 17:55:02 -0800 (PST) From: Jaye Mathisen To: Andrew Reilly cc: lamaster@george.arc.nasa.gov, current@FreeBSD.ORG Subject: Re: Worldstone Continued... In-Reply-To: <199803182302.KAA02826@gurney.reilly.home> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG YOu know, I did this once, with everything in RAM, but don't have the message anymore. However, it was before all the buildworld tuning, and the parallelizing of the build process, so it would be extremely out of date. But I think I'm going to try it. I can wedge another 512MB in this DEC box, and fire it up... Maybe tonight. On Thu, 19 Mar 1998, Andrew Reilly wrote: > On 18 Mar, Hugh LaMaster wrote: > > Then, you might see that number drop even further. The goal, in my > > mind, is do to a complete buildworld and installworld in less than > > an hour. > > It would be interesting to see a "speed of light" figure for > buildworld. I note that there are some people on this list with access > to machines with seriously big DRAM (.5G?) on their systems. I doubt > that any one compile operation exercises more than a few Meg, with > -pipe. > > Does anyone have a system that can attempt a buildworld with src and > obj in mfs, mounted noasync (if that makes any difference)? > > (It may not be important. It certainly appears that the 1:20 figure is > getting pretty close to being a completely CPU-limited process.) > > Has anyone on the Alpha port project timed a buildworld? (If the world > can be built there yet.) > > -- > Andrew > > "The steady state of disks is full." > -- Ken Thompson > > > 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 Mar 18 18:00:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16274 for freebsd-current-outgoing; Wed, 18 Mar 1998 18:00:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16243; Wed, 18 Mar 1998 18:00:26 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA04545; Thu, 19 Mar 1998 12:59:00 +1100 Date: Thu, 19 Mar 1998 12:59:00 +1100 From: Bruce Evans Message-Id: <199803190159.MAA04545@godzilla.zeta.org.au> To: mrcpu@cdsnet.net, sos@FreeBSD.ORG Subject: Re: Stream_d benchmark... Wow, there really are differences in hardware Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hmm, Then I should be proud of my noname system (p6/200/128MB 72pEDO): > >Function Rate (MB/s) RMS time Min time Max time >Copy: 117.0286 0.2758 0.2734 0.2812 >Scale: 117.0286 0.2782 0.2734 0.2812 >Add: 130.7234 0.3784 0.3672 0.4141 >Triad: 125.3878 0.3917 0.3828 0.4219 > >So what ?? So someone forgot to ensure that the doubles are aligned. This requires using -malign-double and fixing ld so that it actually works. -malign-double -static gives perfect misalignment here: 0000b070 D _edata <- padding not expected by gcc 0000b074 b _a 00191a74 b _b 00318474 b _c 0049f5d4 B _errno I fudged alignment by adding `static int x;' before the declaration of a[], and NOT using -malign-double. >> I figured that within reason, most mb's would have similar performance, >> but I was wrong. >> >> All boxes are P6-200's, 256MB RAM (all RAM is 60ns FP as far as I know). >> >> Box 1 is a SuperMicro P6DNE: >> Function Rate (MB/s) RMS time Min time Max time >> Copy: 60.7395 0.2704 0.2634 0.2832 >> Scale: 60.8640 0.2719 0.2629 0.3097 >> Add: 70.9688 0.3508 0.3382 0.3602 >> Triad: 71.1647 0.3494 0.3372 0.3565 This seems a bit slow, even with misaligned doubles. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 18:16:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17949 for freebsd-current-outgoing; Wed, 18 Mar 1998 18:16:57 -0800 (PST) (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 SAA17942 for ; Wed, 18 Mar 1998 18:16:52 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id VAA23520 for current@freebsd.org; Wed, 18 Mar 1998 21:16:56 -0500 (EST) (envelope-from toor) Message-Id: <199803190216.VAA23520@dyson.iquest.net> Subject: A reminder of toxic -current To: current@FreeBSD.ORG Date: Wed, 18 Mar 1998 21:16:56 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@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 Warning, todays -current is still toxic to your filesystems. I am still working on it, trying to isolate the problem(s). -- 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 Wed Mar 18 18:43:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20803 for freebsd-current-outgoing; Wed, 18 Mar 1998 18:43:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feldman.dyn.ml.org (green@1Cust52.max2.washington.dc.ms.uu.net [153.34.49.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20798 for ; Wed, 18 Mar 1998 18:43:00 -0800 (PST) (envelope-from green@feldman.dyn.ml.org) Received: from localhost (green@localhost) by feldman.dyn.ml.org (8.8.8/8.8.8) with SMTP id VAA04887; Wed, 18 Mar 1998 21:42:22 -0500 (EST) (envelope-from green@feldman.dyn.ml.org) Date: Wed, 18 Mar 1998 21:42:22 -0500 (EST) From: Brian Feldman To: "Jordan K. Hubbard" cc: Brian Feldman , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: C++ libs are broken In-Reply-To: <19161.889784144@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's correct, but I have had incredible luck with 3.0. It would be nice to be able to continue using it but it totally broke on me yesterday (almost every program sig1[0-2]'ed). So... I've gone back to 2.2.6-BETA and I'm fine with it, but I wish I had the _time_ to read the mailing lists more often. Oh well, I am content finding any syntax errors that creep into the source and seeing if I can't fix those (which is in my capability, you know, I've been reading =) Jordan: both Number-6 and I have introduced much improved versions of yes(1), and maybe you should consider letting one get into the source tree? Chuck: how good are the computer/programming classes at UMD? It would be nice to go somewhere and not be paying out-of-state-college-fees, you know? Best of luck, Brian "content with FreeBSD 2.2*" Feldman On Fri, 13 Mar 1998, Jordan K. Hubbard wrote: > > Yes, you're right. I was quite miffed when I wrote that message. It's just > > that 3.0 can be so stable, and working, I hate to see it get messed up all > > the time. Some people really take too much liberty committing any change > > Well, FWIW, we've talked before and I've already told you several > times that I didn't think you should be running -current; you haven't > got the prerequisites (you don't read the right mailing lists and you > definitely shouldn't be out on the bleeding edge in general). I don't > think -current should be blamed for inappropriate use here. > > Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 18:44:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20980 for freebsd-current-outgoing; Wed, 18 Mar 1998 18:44:32 -0800 (PST) (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 SAA20973 for ; Wed, 18 Mar 1998 18:44:30 -0800 (PST) (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (ppp62.wcc.net [208.6.232.62]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id UAA11900; Wed, 18 Mar 1998 20:40:22 -0600 (CST) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id UAA08131; Wed, 18 Mar 1998 20:44:17 -0600 (CST) (envelope-from joelh) Date: Wed, 18 Mar 1998 20:44:17 -0600 (CST) Message-Id: <199803190244.UAA08131@detlev.UUCP> To: Matthew.Thyer@dsto.defence.gov.au CC: c5666305@comp.polyu.edu.hk, current@FreeBSD.ORG In-reply-to: <35106C23.64774CD9@dsto.defence.gov.au> (message from Matthew Thyer on Thu, 19 Mar 1998 11:21:47 +1030) Subject: Re: Disk munging problem with current solved From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> <350E643D.A47CB903@camtech.net.au> <199803182240.QAA07391@detlev.UUCP> <35106C23.64774CD9@dsto.defence.gov.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I noticed that it is possible to cvsup a current ctm tree from >> ctm.freebsd.org. I expect this to be either an alternative to using a >> base delta (for instance, now that you'd have to ftp nearly 100 >> deltas), or to allow you to resync a partially trashed source tree. >> However, this is missing .ctm-status, which would seem to be fairly >> important. > Alas there is no synchronisation between CTM and cvs. > Theoretically if you cvsupped at the same time as the person > who makes the CTM deltas and you created the .ctm_status > file yourself with the right number in it then you'd be right. > However if you cvsup 1 minute later a couple of files somewhere > in the tree may have been changed and then future CTM deltas > would fail to apply. > So no, you cannot use both CVS and CTM. It was my understanding that the ctm-src (or something like that) tag from ctm.freebsd.org would fetch a CTM sync'd tree. -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 18:45:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21389 for freebsd-current-outgoing; Wed, 18 Mar 1998 18:45:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21360 for ; Wed, 18 Mar 1998 18:45:34 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id TAA14021; Wed, 18 Mar 1998 19:45:27 -0700 (MST) Message-Id: <199803190245.TAA14021@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: Kernel / Compiler bug? In-reply-to: Your message of "Wed, 18 Mar 1998 11:59:37 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Mar 1998 19:42:06 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Sorry if this is a re-run, but it looks like the original got lost somewhere. > >This problem may be CAM specific. > >I am not sure what to do about this one. Since I got my machine I have not >been able to build a kernel that runs, without using "swap on generic" and >-a at the boot prompt > >Well, after doing some debugging, it looks like the line > > dev_t rootdev = makedev(4, 0x000020000); > >in swapkernel.c (/usr/src/sys/compile//swapkernel.c) isn't being run. Are you sure it isn't simply being spammed somewhere in autoconf.c? [narnia::i386]$ grep rootdev *.c autoconf.c: dev_t orootdev; autoconf.c: orootdev = rootdev; autoconf.c: rootdev = makedev(try_cdrom[j].major, i * 8); autoconf.c: bd = bdevsw[major(rootdev)]; autoconf.c: printf("trying %s%d as rootdev (0x%x)\n", autoconf.c: try_cdrom[j].name, i, rootdev); autoconf.c: error = (bd->d_open)(rootdev, FREAD, S_IFBLK, curproc); autoconf.c: (bd->d_close)(rootdev, FREAD, S_IFBLK, autoconf.c: rootdev = orootdev; autoconf.c: /* NB: find_cdrom_root() sets rootdev if successful. */ autoconf.c: * (rootdev is always initialized to NODEV in a autoconf.c: if ((boothowto & RB_ASKNAME) == 0 || rootdev != NODEV) autoconf.c: * (rootdev is always initialized to NODEV in a autoconf.c: if ((boothowto & RB_ASKNAME) == 0 || rootdev != NODEV) autoconf.c: * change rootdev to correspond to the load device. autoconf.c: dev_t orootdev; autoconf.c: orootdev = rootdev; autoconf.c: rootdev = makedev(majdev, mindev); autoconf.c: * If the original rootdev is the same as the one autoconf.c: if ((rootdev & ~0xff0000) == (orootdev & ~0xff0000)) swapgeneric.c:dev_t rootdev = NODEV; swapgeneric.c: if (rootdev != NODEV) swapgeneric.c: rootdev = gc->gc_root; -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 18:47:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21978 for freebsd-current-outgoing; Wed, 18 Mar 1998 18:47:32 -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 SAA21940; Wed, 18 Mar 1998 18:47:26 -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 UAA05105; Wed, 18 Mar 1998 20:47:25 -0600 (CST) Message-ID: <19980318204724.41485@arh0300.urh.uiuc.edu> Date: Wed, 18 Mar 1998 20:47:24 -0600 From: dannyman To: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: A reminder of toxic -current References: <199803190216.VAA23520@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803190216.VAA23520@dyson.iquest.net>; from John S. Dyson on Wed, Mar 18, 1998 at 09:16:56PM -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 Wed, Mar 18, 1998 at 09:16:56PM -0500, John S. Dyson wrote: > Warning, todays -current is still toxic to your filesystems. I > am still working on it, trying to isolate the problem(s). ermmm, i recently rebuilt a second time after the FS scare, and neither of my -current's have shown any trouble. i've backed up my home directory just in case, but if my fs hasn't been destroyed yet, and is stable enough to reliably recompile the OS, I should worry? -dan -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 18:57:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23901 for freebsd-current-outgoing; Wed, 18 Mar 1998 18:57:57 -0800 (PST) (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 SAA23872; Wed, 18 Mar 1998 18:57:33 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id VAA06394; Wed, 18 Mar 1998 21:57:32 -0500 (EST) (envelope-from toor) Message-Id: <199803190257.VAA06394@dyson.iquest.net> Subject: Re: A reminder of toxic -current In-Reply-To: <19980318204724.41485@arh0300.urh.uiuc.edu> from dannyman at "Mar 18, 98 08:47:24 pm" To: dannyman@sasquatch.dannyland.org (dannyman) Date: Wed, 18 Mar 1998 21:57:31 -0500 (EST) Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 dannyman said: > On Wed, Mar 18, 1998 at 09:16:56PM -0500, John S. Dyson wrote: > > Warning, todays -current is still toxic to your filesystems. I > > am still working on it, trying to isolate the problem(s). > > ermmm, i recently rebuilt a second time after the FS scare, and neither of my > -current's have shown any trouble. i've backed up my home directory just in > case, but if my fs hasn't been destroyed yet, and is stable enough to reliably > recompile the OS, I should worry? > Yes. It is an extremely elusive problem. Are you using SMP or UP? Also, any info about your system config might be useful (so I can see how you are using your system.) It has been difficult for me to reproduce the problems since my latest commits, but they still do happen. Current is not stable enough for production use, and I want to make sure that no-one gets hosed. Karl is helping regression test the system, and if you can somehow make the problems occur, it would be useful for me to hear how. If -current works for you, I am still concerned. I would be misleading you and others if I stated otherwise!!! I really do care about people getting messed up filesystems!!! -- 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 Wed Mar 18 19:00:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24612 for freebsd-current-outgoing; Wed, 18 Mar 1998 19:00:57 -0800 (PST) (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 TAA24586; Wed, 18 Mar 1998 19:00:44 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id VAA29107; Wed, 18 Mar 1998 21:00:37 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id VAA25549; Wed, 18 Mar 1998 21:00:37 -0600 (CST) Message-ID: <19980318210037.16941@mcs.net> Date: Wed, 18 Mar 1998 21:00:37 -0600 From: Karl Denninger To: dannyman Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: A reminder of toxic -current References: <199803190216.VAA23520@dyson.iquest.net> <19980318204724.41485@arh0300.urh.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980318204724.41485@arh0300.urh.uiuc.edu>; from dannyman on Wed, Mar 18, 1998 at 08:47:24PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 18, 1998 at 08:47:24PM -0600, dannyman wrote: > On Wed, Mar 18, 1998 at 09:16:56PM -0500, John S. Dyson wrote: > > Warning, todays -current is still toxic to your filesystems. I > > am still working on it, trying to isolate the problem(s). > > ermmm, i recently rebuilt a second time after the FS scare, and neither of my > -current's have shown any trouble. i've backed up my home directory just in > case, but if my fs hasn't been destroyed yet, and is stable enough to reliably > recompile the OS, I should worry? > > -dan YES! I can reproduce this failure within 30 minutes, and it DESTROYS the filesystem in question. FSCK will report it clean after a couple of passes, but the data contained in it is irrecoverably damaged. DO NOT USE CURRENT KERNELS BUILT AFTER THE MEGACOMMIT FROM JOHN OVER THIS LAST WEEKEND! -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 19:01:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24781 for freebsd-current-outgoing; Wed, 18 Mar 1998 19:01:36 -0800 (PST) (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 TAA24775 for ; Wed, 18 Mar 1998 19:01:34 -0800 (PST) (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 SAA24179; Wed, 18 Mar 1998 18:57:38 -0800 (PST) Message-Id: <199803190257.SAA24179@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Justin T. Gibbs" cc: Cory Kempf , freebsd-current@FreeBSD.ORG Subject: Re: Kernel / Compiler bug? In-reply-to: Your message of "Wed, 18 Mar 1998 19:42:06 MST." <199803190245.TAA14021@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Mar 1998 18:57:37 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Sorry if this is a re-run, but it looks like the original got lost somewhere. > > > >This problem may be CAM specific. > > > >I am not sure what to do about this one. Since I got my machine I have not > >been able to build a kernel that runs, without using "swap on generic" and > >-a at the boot prompt > > > >Well, after doing some debugging, it looks like the line > > > > dev_t rootdev = makedev(4, 0x000020000); > > > >in swapkernel.c (/usr/src/sys/compile//swapkernel.c) isn't being run. > > Are you sure it isn't simply being spammed somewhere in autoconf.c? That's likely, if the bootblocks are passing in valid numbers. If the disk is not labelled correctly, the bootstrap may pass in a bad major number. You should check the values of majdev, slice and mindev at the end of autoconf.c:setroot(). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 19:08:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26187 for freebsd-current-outgoing; Wed, 18 Mar 1998 19:08:02 -0800 (PST) (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 TAA26150; Wed, 18 Mar 1998 19:07:54 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id WAA23964; Wed, 18 Mar 1998 22:07:57 -0500 (EST) (envelope-from toor) Message-Id: <199803190307.WAA23964@dyson.iquest.net> Subject: Re: A reminder of toxic -current In-Reply-To: <199803190257.VAA06394@dyson.iquest.net> from "John S. Dyson" at "Mar 18, 98 09:57:31 pm" To: dyson@FreeBSD.ORG Date: Wed, 18 Mar 1998 22:07:57 -0500 (EST) Cc: dannyman@sasquatch.dannyland.org, dyson@FreeBSD.ORG, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 said: > > If -current works for you, I am still concerned. I would be misleading you > and others if I stated otherwise!!! I really do care about people getting > messed up filesystems!!! > Following up on my own posting: Maybe I am not being strong enough in my suggestion: Please do not use the -current kernel unless you know that the consequences will be that you will likely loose filesystem(s). Karl is trying to help with testing and advice, and unless you want to participate in trying to narrow down the problem, please don't use -current until we figure out what is going on. -- 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 Wed Mar 18 19:10:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26598 for freebsd-current-outgoing; Wed, 18 Mar 1998 19:10:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26502 for ; Wed, 18 Mar 1998 19:09:54 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id NAA08896; Thu, 19 Mar 1998 13:38:06 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id H1923VTT; Thu, 19 Mar 1998 13:38:44 +0930 Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id NAA19622; Thu, 19 Mar 1998 13:39:26 +1030 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id NAA04755; Thu, 19 Mar 1998 13:39:26 +1030 (CST) Message-ID: <35108C62.DDFB1544@dsto.defence.gov.au> Date: Thu, 19 Mar 1998 13:39:22 +1030 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: joelh@gnu.org CC: c5666305@comp.polyu.edu.hk, current@FreeBSD.ORG Subject: Using CVSUP and CTM together (Was Re: Disk munging problem with current solved) References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> <350E643D.A47CB903@camtech.net.au> <199803182240.QAA07391@detlev.UUCP> <35106C23.64774CD9@dsto.defence.gov.au> <199803190244.UAA08131@detlev.UUCP> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I dont know about this... hopefully someone else can comment on it. It would be good to be able to cvsup for a latest VM fix and then to be able to re-synchronize with CTM later. Also it would seem that CTM is not very useful for developers as they are required to update their tree before committing changes (in case what they were to change has been changed by others). Joel Ray Holveck wrote: > > >> I noticed that it is possible to cvsup a current ctm tree from > >> ctm.freebsd.org. I expect this to be either an alternative to using a > >> base delta (for instance, now that you'd have to ftp nearly 100 > >> deltas), or to allow you to resync a partially trashed source tree. > >> However, this is missing .ctm-status, which would seem to be fairly > >> important. > > Alas there is no synchronisation between CTM and cvs. > > Theoretically if you cvsupped at the same time as the person > > who makes the CTM deltas and you created the .ctm_status > > file yourself with the right number in it then you'd be right. > > However if you cvsup 1 minute later a couple of files somewhere > > in the tree may have been changed and then future CTM deltas > > would fail to apply. > > So no, you cannot use both CVS and CTM. > > It was my understanding that the ctm-src (or something like that) tag > from ctm.freebsd.org would fetch a CTM sync'd tree. > > -- > Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan > Fourth law of programming: > Anything that can go wrong wi > sendmail: segmentation violation - core dumped > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 19:14:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27832 for freebsd-current-outgoing; Wed, 18 Mar 1998 19:14:22 -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 TAA27703; Wed, 18 Mar 1998 19:14:00 -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 VAA08864; Wed, 18 Mar 1998 21:14:03 -0600 (CST) Message-ID: <19980318211402.23977@arh0300.urh.uiuc.edu> Date: Wed, 18 Mar 1998 21:14:02 -0600 From: dannyman To: dyson@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: A reminder of toxic -current References: <199803190257.VAA06394@dyson.iquest.net> <199803190307.WAA23964@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803190307.WAA23964@dyson.iquest.net>; from John S. Dyson on Wed, Mar 18, 1998 at 10:07:57PM -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 Wed, Mar 18, 1998 at 10:07:57PM -0500, John S. Dyson wrote: > John S. Dyson said: > > > > If -current works for you, I am still concerned. I would be misleading you > > and others if I stated otherwise!!! I really do care about people getting > > messed up filesystems!!! > Following up on my own posting: Maybe I am not being strong enough in > my suggestion: Please do not use the -current kernel unless you know > that the consequences will be that you will likely loose filesystem(s). > > Karl is trying to help with testing and advice, and unless you want to > participate in trying to narrow down the problem, please don't use > -current until we figure out what is going on. John: I am aware of the consequences, but to be honest, I don't know how to "revert" or anything. Some cvsup option that'll reverse the code on my system? I've backed a few things up, I'll back some more up. I'm happy to "ride out the storm" as it were, especially since things have been fine so far. I am happy to share system information if it will help any. -dan -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 19:17:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28641 for freebsd-current-outgoing; Wed, 18 Mar 1998 19:17:42 -0800 (PST) (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 TAA28583; Wed, 18 Mar 1998 19:17:35 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id VAA27188; Wed, 18 Mar 1998 21:17:30 -0600 (CST) From: Kevin Day Message-Id: <199803190317.VAA27188@home.dragondata.com> Subject: Re: A reminder of toxic -current In-Reply-To: <199803190216.VAA23520@dyson.iquest.net> from "John S. Dyson" at "Mar 18, 98 09:16:56 pm" To: dyson@FreeBSD.ORG Date: Wed, 18 Mar 1998 21:17:29 -0600 (CST) 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 > Warning, todays -current is still toxic to your filesystems. I > am still working on it, trying to isolate the problem(s). > > -- > 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 > When was the last 'safe' day that you know of? :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 19:28:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00657 for freebsd-current-outgoing; Wed, 18 Mar 1998 19:28:04 -0800 (PST) (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 TAA00601; Wed, 18 Mar 1998 19:27:57 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id VAA00871; Wed, 18 Mar 1998 21:27:57 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id VAA26012; Wed, 18 Mar 1998 21:27:57 -0600 (CST) Message-ID: <19980318212757.30801@mcs.net> Date: Wed, 18 Mar 1998 21:27:57 -0600 From: Karl Denninger To: dannyman Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: A reminder of toxic -current ** READ THIS ** References: <199803190257.VAA06394@dyson.iquest.net> <199803190307.WAA23964@dyson.iquest.net> <19980318211402.23977@arh0300.urh.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980318211402.23977@arh0300.urh.uiuc.edu>; from dannyman on Wed, Mar 18, 1998 at 09:14:02PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 18, 1998 at 09:14:02PM -0600, dannyman wrote: > On Wed, Mar 18, 1998 at 10:07:57PM -0500, John S. Dyson wrote: > > John S. Dyson said: > > > > > > If -current works for you, I am still concerned. I would be misleading you > > > and others if I stated otherwise!!! I really do care about people getting > > > messed up filesystems!!! > > > Following up on my own posting: Maybe I am not being strong enough in > > my suggestion: Please do not use the -current kernel unless you know > > that the consequences will be that you will likely loose filesystem(s). > > > > Karl is trying to help with testing and advice, and unless you want to > > participate in trying to narrow down the problem, please don't use > > -current until we figure out what is going on. > > John: > > I am aware of the consequences, but to be honest, I don't know how to "revert" > or anything. Some cvsup option that'll reverse the code on my system? > > I've backed a few things up, I'll back some more up. I'm happy to "ride out > the storm" as it were, especially since things have been fine so far. I am > happy to share system information if it will help any. cd /usr/src/sys cvs update -D'03/12/1998' . ..... Kernels built from 3/12 to not contain the bug. At least, so far they appear not to contain the bug. Give me until tomorrow morning and I'll know for sure - I'm running a full regression test on the 3/12 extract right now, and will post something here if/when it either fails or runs to completion. If you're not aware that you're seeing the problem, then you probably are in one of two camps: 1) You're slowly having your data destroyed and don't know it, and by the time you DO know it you'll be completely screwed and need to essentially reformat the disk :-) 2) You are not tripping the condition that is causing the destruction. This *IS* possible; I have two machines in particular uses which do NOT cause the problem, but I don't know why. HOWEVER, be aware that even in case (2), the problematic kernel has problems with lock-ups and other bad behavior (like unsolicited resets without core dump or even a panic message, along with hard wedges which don't respond to anything short of a RESET switch) which may be related. I can readily reproduce the wedge problem on a busy webserver (which has a boot disk that never gets written to, and thus is "safe" to use the bad kernel on otherwise). If you're either unable or unwilling to actually help find this and take the concurrent risk that comes with doing so, you're best off reverting as above so you don't become a victim. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 19:28:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00867 for freebsd-current-outgoing; Wed, 18 Mar 1998 19:28:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00852 for ; Wed, 18 Mar 1998 19:28:37 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id VAA15764; Wed, 18 Mar 1998 21:28:19 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <35106C23.64774CD9@dsto.defence.gov.au> References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> <350E643D.A47CB903@camtech.net.au> <199803182240.QAA07391@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 18 Mar 1998 21:24:09 -0600 To: Matthew Thyer From: Richard Wackerbarth Subject: Re: Disk munging problem with current solved Cc: joelh@gnu.org, c5666305@comp.polyu.edu.hk, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:51 PM -0600 3/18/98, Matthew Thyer wrote: >Alas there is no synchronisation between CTM and cvs. > >Theoretically if you cvsupped at the same time as the person >who makes the CTM deltas and you created the .ctm_status >file yourself with the right number in it then you'd be right. > >However if you cvsup 1 minute later a couple of files somewhere >in the tree may have been changed and then future CTM deltas >would fail to apply. > >So no, you cannot use both CVS and CTM. I presume you mean CVSup. The CVS tree is certainly available by CTM. > >Use one or the other but not both. > This is NOT TRUE. If you use CVSup from ctm.freebsd.org, there is a direct correspondence because THAT distribution point is updated only by CTM. Except for the short "race" condition while updates are calculated and applied, it matches the latest CTM distribution of . This tree is also the tree from which the src trees are extracted to produce the other CTM distributions. The .ctm_status file is not present because that file for (and and ) are not distributed in the CVS tree. To resync , CVSup from ctm.freebsd.org is fine. To sync to the derived distributions is a little harder. By the present schedule, the cvs tree is updated every 8 hours. However, the extracted sources alternate and get updated only on a 16 hour cycle. This means that you would need to pick the appropriate time to do the (final) update in order to be back in sync. Richard Wackerbarth CTM Meister (retired) >Joel Ray Holveck wrote: >> >> > Note you will also need the last base delta for CURRENT >> > which you can download from: >> > ftp://ftp.freebsd.org/pub/FreeBSD/CTM/src-cur/ >> >> This reminds me: >> >> I noticed that it is possible to cvsup a current ctm tree from >> ctm.freebsd.org. I expect this to be either an alternative to using a >> base delta (for instance, now that you'd have to ftp nearly 100 >> deltas), or to allow you to resync a partially trashed source tree. >> However, this is missing .ctm-status, which would seem to be fairly >> important. >> >> (I'll also point out, with details that I didn't write down, that >> manually looking at deltas and figuring out where .ctm-status should >> be didn't work... I got a lot of missing stuff.) >> >> Am I doing something wrong here, or is that just something nobody's >> bothered with yet? >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 19:36:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02816 for freebsd-current-outgoing; Wed, 18 Mar 1998 19:36:01 -0800 (PST) (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 TAA02782; Wed, 18 Mar 1998 19:35:57 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id VAA01102; Wed, 18 Mar 1998 21:35:57 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id VAA26131; Wed, 18 Mar 1998 21:35:56 -0600 (CST) Message-ID: <19980318213556.45381@mcs.net> Date: Wed, 18 Mar 1998 21:35:56 -0600 From: Karl Denninger To: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: UPDATE ON CURRENT KERNEL SITUATION and 3/12/98 kernels Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm now WELL beyond where I always got screwed with the CURRENT kernel (running a 3/12 extract), and the system is fine. So is the disk structure. I would say with ~90% confidence that your disks are safe with a kernel built from 3/12/98 source. I should be able to be essentially 100% confident by morning. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 19:48:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04467 for freebsd-current-outgoing; Wed, 18 Mar 1998 19:48:11 -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 TAA04457; Wed, 18 Mar 1998 19:48:00 -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 VAA12747; Wed, 18 Mar 1998 21:47:58 -0600 (CST) Message-ID: <19980318214758.38114@arh0300.urh.uiuc.edu> Date: Wed, 18 Mar 1998 21:47:58 -0600 From: dannyman To: Karl Denninger Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: A reminder of toxic -current ** READ THIS ** References: <199803190257.VAA06394@dyson.iquest.net> <199803190307.WAA23964@dyson.iquest.net> <19980318211402.23977@arh0300.urh.uiuc.edu> <19980318212757.30801@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980318212757.30801@mcs.net>; from Karl Denninger on Wed, Mar 18, 1998 at 09:27:57PM -0600 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 First off, thanks to Karl, John and Steve for dire warnings, advice, education, tackling the problem, etc. :) On Wed, Mar 18, 1998 at 09:27:57PM -0600, Karl Denninger wrote: > Kernels built from 3/12 to not contain the bug. At least, so far > they appear not to contain the bug. Give me until tomorrow morning and I'll > know for sure - I'm running a full regression test on the 3/12 extract right > now, and will post something here if/when it either fails or runs to > completion. What is a "full regression test" ... outta curiousity? :) > If you're not aware that you're seeing the problem, then you probably are in > one of two camps: > > 1) You're slowly having your data destroyed and don't know it, and by > the time you DO know it you'll be completely screwed and need to > essentially reformat the disk :-) Hmmm ... fair enough. I'm not sure if mpg123 is just picky or maybe my entire mp3 collection is going funny. ;) > 2) You are not tripping the condition that is causing the destruction. > This *IS* possible; I have two machines in particular uses which do > NOT cause the problem, but I don't know why. Are there any commonalities in chipsets, and the like? Particular drivers? My system seems to be working perfectly normally, though to be honest, its normal operation is not perfect. ;) A shuttle motherboard, Intel chips, WDC drives .... K5. *shrug* > HOWEVER, be aware that even in case (2), the problematic kernel has > problems with lock-ups and other bad behavior (like unsolicited resets > without core dump or even a panic message, along with hard wedges which > don't respond to anything short of a RESET switch) which may be related. > I can readily reproduce the wedge problem on a busy webserver (which has > a boot disk that never gets written to, and thus is "safe" to use the bad > kernel on otherwise). Bahhh, Karl, I get lockups even on STABLE sometimes. I think I have flakey hardware somewheres. ;) > If you're either unable or unwilling to actually help find this and take the > concurrent risk that comes with doing so, you're best off reverting as above > so you don't become a victim. If someone wants to observe from my machine ... nahh, I'm reverting/rebuilding coz I'm gonna have to move the system soon anyways. Thanks. -dan -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 19:59:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06151 for freebsd-current-outgoing; Wed, 18 Mar 1998 19:59:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06050 for ; Wed, 18 Mar 1998 19:59:03 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id VAA16374; Wed, 18 Mar 1998 21:58:40 -0600 (CST) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <35108C62.DDFB1544@dsto.defence.gov.au> References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> <350E643D.A47CB903@camtech.net.au> <199803182240.QAA07391@detlev.UUCP> <35106C23.64774CD9@dsto.defence.gov.au> <199803190244.UAA08131@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 18 Mar 1998 21:50:49 -0600 To: Matthew Thyer From: Richard Wackerbarth Subject: Re: Using CVSUP and CTM together (Was Re: Disk munging problem with current solved) Cc: joelh@gnu.org, c5666305@comp.polyu.edu.hk, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:09 PM -0600 3/18/98, Matthew Thyer wrote: >I dont know about this... hopefully someone else can comment on it. > >It would be good to be able to cvsup for a latest VM fix and then >to be able to re-synchronize with CTM later. The ability to do this is somewhat limited by the problems associated in jumping from one CVSup server to another. You can use the CVSup server on ctm.freebsd.org in conjunction with CTM because it's source is the CTM distribution. However, that is not really a help if your intention is to try to beat the latency of CTM. CTM is delayed because (1) it is run only a few times each day, and (2) it does not have access to the master source. The CTM distributions themselves are generated from a copy of a copy of the master tree as it has no better access than to CVSup from one of the CVSup sites just the same as you would do. In fact, the deltas are often delayed because the CVSup update is rejected because those servers are too busy. >Also it would seem that CTM is not very useful for developers as >they are required to update their tree before committing changes >(in case what they were to change has been changed by others). That would depend on the amount of latency that the developer can accept. If he knows that he is the only one working on a particular part of the tree, he is fairly safe in ingoring the pre-undate sync. CVS will "complain" if he gets caught in a race. If this happens, the update is rejected. The user must resync the affected file and try again. As long as such failures are very infrequent, it may not be a problem. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 20:20:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09225 for freebsd-current-outgoing; Wed, 18 Mar 1998 20:20:43 -0800 (PST) (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 UAA09165; Wed, 18 Mar 1998 20:20:16 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id XAA00526; Wed, 18 Mar 1998 23:20:12 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803190420.XAA00526@dyson.iquest.net> Subject: Re: A reminder of toxic -current In-Reply-To: <19980318211402.23977@arh0300.urh.uiuc.edu> from dannyman at "Mar 18, 98 09:14:02 pm" To: dannyman@sasquatch.dannyland.org (dannyman) Date: Wed, 18 Mar 1998 23:20:12 -0500 (EST) Cc: dyson@FreeBSD.ORG, 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 > On Wed, Mar 18, 1998 at 10:07:57PM -0500, John S. Dyson wrote: > > John S. Dyson said: > > > > > > If -current works for you, I am still concerned. I would be misleading you > > > and others if I stated otherwise!!! I really do care about people getting > > > messed up filesystems!!! > > > Following up on my own posting: Maybe I am not being strong enough in > > my suggestion: Please do not use the -current kernel unless you know > > that the consequences will be that you will likely loose filesystem(s). > > > > Karl is trying to help with testing and advice, and unless you want to > > participate in trying to narrow down the problem, please don't use > > -current until we figure out what is going on. > > John: > > I am aware of the consequences, but to be honest, I don't know how to "revert" > or anything. Some cvsup option that'll reverse the code on my system? > > I've backed a few things up, I'll back some more up. I'm happy to "ride out > the storm" as it were, especially since things have been fine so far. I am > happy to share system information if it will help any. > Try checking out a kernel like: cvs co -D12-mar sys build and use that. It is likely safer than current as of today. It took me an entire day to recover my system during the weekend. I can't say it strongly enough to avoid using -current until we figure out the problem! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 20:26:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10231 for freebsd-current-outgoing; Wed, 18 Mar 1998 20:26:11 -0800 (PST) (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 UAA10224 for ; Wed, 18 Mar 1998 20:26:08 -0800 (PST) (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (tnt135.wcc.net [208.10.139.135]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id WAA23434; Wed, 18 Mar 1998 22:21:58 -0600 (CST) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id WAA08511; Wed, 18 Mar 1998 22:24:03 -0600 (CST) (envelope-from joelh) Date: Wed, 18 Mar 1998 22:24:03 -0600 (CST) Message-Id: <199803190424.WAA08511@detlev.UUCP> To: Matthew.Thyer@dsto.defence.gov.au CC: c5666305@comp.polyu.edu.hk, current@FreeBSD.ORG In-reply-to: <35108C62.DDFB1544@dsto.defence.gov.au> (message from Matthew Thyer on Thu, 19 Mar 1998 13:39:22 +1030) Subject: Re: Using CVSUP and CTM together (Was Re: Disk munging problem with current solved) From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> <350E643D.A47CB903@camtech.net.au> <199803182240.QAA07391@detlev.UUCP> <35106C23.64774CD9@dsto.defence.gov.au> <199803190244.UAA08131@detlev.UUCP> <35108C62.DDFB1544@dsto.defence.gov.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It would be good to be able to cvsup for a latest VM fix and then > to be able to re-synchronize with CTM later. The machine I run -current on can afford to sit out a few hours while I wait for changes to hit CTM. (I'm used to waiting for a change to hit the net, what's the difference?) (And that's NOT meant as an insult to the kernel hackers!) > Also it would seem that CTM is not very useful for developers as > they are required to update their tree before committing changes > (in case what they were to change has been changed by others). I prefer to look at code that's not changing. Since most of the fast-paced changes are in the kernel, and I barely understand kernel code, then I'm okay. In other words, I'm relaxed about lag. Living in Texas, I have to be. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 20:41:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11740 for freebsd-current-outgoing; Wed, 18 Mar 1998 20:41:40 -0800 (PST) (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 UAA11730; Wed, 18 Mar 1998 20:41:30 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id XAA00612; Wed, 18 Mar 1998 23:41:26 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803190441.XAA00612@dyson.iquest.net> Subject: Re: A reminder of toxic -current In-Reply-To: <19980318210037.16941@mcs.net> from Karl Denninger at "Mar 18, 98 09:00:37 pm" To: karl@mcs.net (Karl Denninger) Date: Wed, 18 Mar 1998 23:41:26 -0500 (EST) Cc: dannyman@sasquatch.dannyland.org, dyson@FreeBSD.ORG, 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 > On Wed, Mar 18, 1998 at 08:47:24PM -0600, dannyman wrote: > > On Wed, Mar 18, 1998 at 09:16:56PM -0500, John S. Dyson wrote: > > > Warning, todays -current is still toxic to your filesystems. I > > > am still working on it, trying to isolate the problem(s). > > > > ermmm, i recently rebuilt a second time after the FS scare, and neither of my > > -current's have shown any trouble. i've backed up my home directory just in > > case, but if my fs hasn't been destroyed yet, and is stable enough to reliably > > recompile the OS, I should worry? > > > > -dan > > YES! > > I can reproduce this failure within 30 minutes, and it DESTROYS the > filesystem in question. FSCK will report it clean after a couple of passes, > but the data contained in it is irrecoverably damaged. > > DO NOT USE CURRENT KERNELS BUILT AFTER THE MEGACOMMIT FROM JOHN OVER THIS > LAST WEEKEND! > Karl is right. This will be the last warning from me regarding the -current problem. I am not going to broadcast any proclaimations of a corrected kernel but I am working on fixing the problems, with the help of Karl and others. If Karl and others find that the problems are fixed, the information will be slowly exposed. This is one reason that it is said that -current is not for the faint of heart, and assuming that it will work in a production environment without full testing is very dangerous. I didn't even know that my changes had problems, until my system became unusable. That ended up delaying my warnings for over 24 hours, and people found out the hard-way. The bugs are my fault, but please don't assume that because -current normally works OK, that it is always safe to use in production. It is best to know when to cut your losses, and it is best just to back up to a 12-mar or before kernel. Not doing that will simply put your filesystems at risk... So, one-more-time, if you aren't working with Karl or me (or whomever else is trying to solve the problem), please do not use a kernel after 12-mar. I apologize for the inconvieniences, but fretting instead of simply backing up to a 12-mar kernel isn't productive. Karl knows how to protect his systems, and other people who try to use -current in production know how to do it also. Even then, it is possible to get totally hosed, like I did... If people are running the -current kernel without having local copies of the CVS tree and/or backup copies of various kernels, well, that is like playing with fire. FYI, I have probably 100-200 kernel trees that I keep online, and perhaps that is overkill, but keeping your last 10-20 safe kernels isn't a terrible idea. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 21:50:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22994 for freebsd-current-outgoing; Wed, 18 Mar 1998 21:50:37 -0800 (PST) (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 VAA22989 for ; Wed, 18 Mar 1998 21:50:36 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id XAA06224 for ; Wed, 18 Mar 1998 23:50:36 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id XAA29157; Wed, 18 Mar 1998 23:50:36 -0600 (CST) Message-ID: <19980318235036.51789@mcs.net> Date: Wed, 18 Mar 1998 23:50:36 -0600 From: Karl Denninger To: current@FreeBSD.ORG Subject: 3/12/1998 KERNEL TEST RESULT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello again, Just in case you're wondering, my regression tests against the 3/12/98 kernel are complete, and it is ok - at least at the filesystem level. Again, if you're running -CURRENT, I strongly recommend backing out to the 3/12/98 revision of the kernel immediately if you are running anything with a later date. This will be my last note on this topic until I have determined that it is safe to use a more "Current" CURRENT. One last time - if you are running a CURRENT kernel built after this point, you are risking severe and unrecoverable damage to any locally-mounted UFS filesystems. If you do a "make world" and actually get through it with such a kernel (the odds are against this), you will be very, very fortunate if what you install as a consequence of that "make world" boots when you are done! The problem includes destruction of BOTH metadata (ie: inode, directory, etc) AND file data. The first will get fixed (for the most part) by FSCK. The second is COMPLETELY undetectable and absolutely will screw you if you run into it. Back out to 3/12 and it appears that you're safe from my testing here. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 22:26:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27804 for freebsd-current-outgoing; Wed, 18 Mar 1998 22:26:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27797; Wed, 18 Mar 1998 22:26:49 -0800 (PST) (envelope-from mark@greenpeace.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 IAA05539; Thu, 19 Mar 1998 08:26:44 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id IAA00641; Thu, 19 Mar 1998 08:26:43 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199803190626.IAA00641@greenpeace.grondar.za> To: dyson@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: Re: A reminder of toxic -current Date: Thu, 19 Mar 1998 08:26:43 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John S. Dyson" wrote: > Yes. It is an extremely elusive problem. Are you using SMP or UP? Also, > any info about your system config might be useful (so I can see how you > are using your system.) It has been difficult for me to reproduce the > problems since my latest commits, but they still do happen. I am using CURRENT on an SMP box. SCB's are hosed (I have an ahc), so I disabled them; and the vx (ethernet) driver has a problem where it suddenly starts r u n n i n g v e r y s l o w l y, But I have no FS problems, and I reboot and FSCK after doing anything vaguely large. > Current is not stable enough for production use, and I want to make sure > that no-one gets hosed. Karl is helping regression test the system, and > if you can somehow make the problems occur, it would be useful for me to > hear how. I hope I am not coming across as saying "it is not broken". I am not. > If -current works for you, I am still concerned. I would be misleading you > and others if I stated otherwise!!! I really do care about people getting > messed up filesystems!!! Thanks! Is my data point useful, though? 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 Wed Mar 18 22:43:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29744 for freebsd-current-outgoing; Wed, 18 Mar 1998 22:43:23 -0800 (PST) (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 WAA29732 for ; Wed, 18 Mar 1998 22:43:19 -0800 (PST) (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 CAA03931; Thu, 19 Mar 1998 02:44:58 GMT Message-ID: <000f01bd5301$d4573680$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: "John S. Dyson" Cc: Subject: some "testing" of the new kernel. Date: Thu, 19 Mar 1998 01:39:55 -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 still not cool, very erratic bahavior on my box, cvsup'd of today. first time booting: double panic right after mounting the disks (ouch) no sync'ing of disks second time... booted up ok.. a LOT of sig 11's to programs at startup, that scared me enough to go back to my pervious kernel. would you like the kernel config file i'm using? it is an _odd_ configuration. -Alfred (i don't mind helping to test here and there, although i really don't have much in terms of backup..., i can mount most partitions read only just to test for crashes...) -----Original Message----- From: John S. Dyson To: Karl Denninger Cc: dannyman@sasquatch.dannyland.org ; dyson@FreeBSD.ORG ; current@FreeBSD.ORG Date: Wednesday, March 18, 1998 7:49 PM Subject: Re: A reminder of toxic -current >> On Wed, Mar 18, 1998 at 08:47:24PM -0600, dannyman wrote: >> > On Wed, Mar 18, 1998 at 09:16:56PM -0500, John S. Dyson wrote: >> > > Warning, todays -current is still toxic to your filesystems. I >> > > am still working on it, trying to isolate the problem(s). >> > >> > ermmm, i recently rebuilt a second time after the FS scare, and neither of my >> > -current's have shown any trouble. i've backed up my home directory just in >> > case, but if my fs hasn't been destroyed yet, and is stable enough to reliably >> > recompile the OS, I should worry? >> > >> > -dan >> >> YES! >> >> I can reproduce this failure within 30 minutes, and it DESTROYS the >> filesystem in question. FSCK will report it clean after a couple of passes, >> but the data contained in it is irrecoverably damaged. >> >> DO NOT USE CURRENT KERNELS BUILT AFTER THE MEGACOMMIT FROM JOHN OVER THIS >> LAST WEEKEND! >> > >Karl is right. This will be the last warning from me regarding the -current >problem. I am not going to broadcast any proclaimations of a corrected kernel >but I am working on fixing the problems, with the help of Karl and others. If >Karl and others find that the problems are fixed, the information will be slowly >exposed. > >This is one reason that it is said that -current is not for the faint of heart, >and assuming that it will work in a production environment without full testing >is very dangerous. I didn't even know that my changes had problems, until my >system became unusable. That ended up delaying my warnings for over 24 hours, >and people found out the hard-way. The bugs are my fault, but please don't >assume that because -current normally works OK, that it is always safe to use >in production. It is best to know when to cut your losses, and it is best >just to back up to a 12-mar or before kernel. Not doing that will simply >put your filesystems at risk... > >So, one-more-time, if you aren't working with Karl or me (or whomever else >is trying to solve the problem), please do not use a kernel after 12-mar. > >I apologize for the inconvieniences, but fretting instead of simply backing >up to a 12-mar kernel isn't productive. Karl knows how to protect his systems, >and other people who try to use -current in production know how to do it also. >Even then, it is possible to get totally hosed, like I did... > >If people are running the -current kernel without having local copies of the >CVS tree and/or backup copies of various kernels, well, that is like playing >with fire. FYI, I have probably 100-200 kernel trees that I keep online, and >perhaps that is overkill, but keeping your last 10-20 safe kernels isn't a >terrible idea. > >John > >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 Mar 18 22:44:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29930 for freebsd-current-outgoing; Wed, 18 Mar 1998 22:44:43 -0800 (PST) (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 WAA29921; Wed, 18 Mar 1998 22:44:39 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id BAA18228; Thu, 19 Mar 1998 01:44:30 -0500 (EST) (envelope-from toor) Message-Id: <199803190644.BAA18228@dyson.iquest.net> Subject: Re: A reminder of toxic -current In-Reply-To: <199803190626.IAA00641@greenpeace.grondar.za> from Mark Murray at "Mar 19, 98 08:26:43 am" To: mark@grondar.za (Mark Murray) Date: Thu, 19 Mar 1998 01:44:29 -0500 (EST) Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Mark Murray said: > > Thanks! Is my data point useful, though? > Any data is useful. I really do think that I know approx where the problem is, but it is hard to track down. There are some sideffects in the code that sometimes I miss... -- 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 Wed Mar 18 22:53:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01797 for freebsd-current-outgoing; Wed, 18 Mar 1998 22:53:26 -0800 (PST) (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 WAA01791 for ; Wed, 18 Mar 1998 22:53:21 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id BAA27474; Thu, 19 Mar 1998 01:53:19 -0500 (EST) (envelope-from toor) Message-Id: <199803190653.BAA27474@dyson.iquest.net> Subject: Re: some "testing" of the new kernel. In-Reply-To: <000f01bd5301$d4573680$0600a8c0@win95.local.sunyit.edu> from Alfred Perlstein at "Mar 19, 98 01:39:55 am" To: perlsta@cs.sunyit.edu (Alfred Perlstein) Date: Thu, 19 Mar 1998 01:53:19 -0500 (EST) Cc: current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Alfred Perlstein said: > still not cool, very erratic bahavior on my box, cvsup'd of today. > > first time booting: double panic right after mounting the disks (ouch) no > sync'ing of disks > > second time... booted up ok.. a LOT of sig 11's to programs at startup, that > scared me enough to go back to my pervious kernel. > > would you like the kernel config file i'm using? > > it is an _odd_ configuration. > > -Alfred > > (i don't mind helping to test here and there, although i really don't have > much in terms of backup..., i can mount most partitions read only just to > test for crashes...) > I think that I have enough data for now. Nothing is holding up progress except my physical and intellectual limitations. Don't risk any of your work by helping. (Even the time to respond to email is significant, but I really do try to respond to email's as much as possible.) Note that I have disks filled with backup filesystems that can allow for me to restore within a few minutes. The bug can hose your filesystems before you know it, so for you to get work done, I suggest backing up to 12-mar or so. Normally, I solicit help more aggressively, but it is usually in those cases that I am not very concerned about people loosing their files. Right now, it is a good idea to stay away until things have settled down. I really am trying to solve the problems, and the delays associated with email would negate the help of the most expert filesystem person. I strongly suggest staying away from recent -current, until the problems settle out. If people aren't actively working the problems, it is best for them to use 12-mar. -- 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 Wed Mar 18 23:11:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04597 for freebsd-current-outgoing; Wed, 18 Mar 1998 23:11:15 -0800 (PST) (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 XAA04582 for ; Wed, 18 Mar 1998 23:11:03 -0800 (PST) (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 JAA06551; Thu, 19 Mar 1998 09:10:13 +0200 (EET) Date: Thu, 19 Mar 1998 09:10:10 +0200 (EET) From: Vallo Kallaste X-Sender: vallo@solaris To: dannyman cc: current@FreeBSD.ORG Subject: Re: A reminder of toxic -current In-Reply-To: <19980318211402.23977@arh0300.urh.uiuc.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 Wed, 18 Mar 1998, dannyman wrote: > > -current until we figure out what is going on. > > John: > > I am aware of the consequences, but to be honest, I don't know how to "revert" > or anything. Some cvsup option that'll reverse the code on my system? > > I've backed a few things up, I'll back some more up. I'm happy to "ride out > the storm" as it were, especially since things have been fine so far. I am > happy to share system information if it will help any. *** If you don't know how to use cvsup, what you are doing here, anyway ?? I wonder how you can use -current without minimal knowledge about cvsup functionalities ? I think "date=......." field in you cvsup file is what you want. Please try man cvsup and learn about this powerful tool and enjoy. 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 Wed Mar 18 23:13:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05427 for freebsd-current-outgoing; Wed, 18 Mar 1998 23:13:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (root@asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05406 for ; Wed, 18 Mar 1998 23:13:17 -0800 (PST) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.8.8/8.8.8) with ESMTP id KAA25363 for ; Thu, 19 Mar 1998 10:12:30 +0300 (MSK) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.7) with ESMTP id KAA02787 for ; Thu, 19 Mar 1998 10:12:03 +0300 (MSK) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199803190712.KAA02787@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.1 12/23/97 To: current@FreeBSD.ORG Reply-To: tarkhil@asteroid.svib.ru Subject: On toxic current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Mar 1998 10:11:59 +0300 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Due to some troubles with my server, I was out of discussion for several days. Can't anyone please tell me what is the last stable snap date (I'm using 25-Feb, and it's pretty nice)? Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 23:18:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06799 for freebsd-current-outgoing; Wed, 18 Mar 1998 23:18:27 -0800 (PST) (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 XAA06759 for ; Wed, 18 Mar 1998 23:18:22 -0800 (PST) (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 JAA06860; Thu, 19 Mar 1998 09:17:55 +0200 (EET) Date: Thu, 19 Mar 1998 09:17:53 +0200 (EET) From: Vallo Kallaste X-Sender: vallo@solaris To: Kevin Day cc: current@FreeBSD.ORG Subject: Re: A reminder of toxic -current In-Reply-To: <199803190317.VAA27188@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 Wed, 18 Mar 1998, Kevin Day wrote: > When was the last 'safe' day that you know of? :) *** I'm using 98.03.14 version. Works well for me. This is our backup machine doing circa 700MB backup nightly over NFS. 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 Wed Mar 18 23:22:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07862 for freebsd-current-outgoing; Wed, 18 Mar 1998 23:22:10 -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 XAA07839 for ; Wed, 18 Mar 1998 23:22:01 -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 BAA22627; Thu, 19 Mar 1998 01:21:19 -0600 (CST) Message-ID: <19980319012118.03735@arh0300.urh.uiuc.edu> Date: Thu, 19 Mar 1998 01:21:18 -0600 From: dannyman To: Vallo Kallaste , Kevin Day Cc: current@FreeBSD.ORG Subject: Re: A reminder of toxic -current References: <199803190317.VAA27188@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Vallo Kallaste on Thu, Mar 19, 1998 at 09:17:53AM +0200 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, Mar 19, 1998 at 09:17:53AM +0200, Vallo Kallaste wrote: > On Wed, 18 Mar 1998, Kevin Day wrote: > > > When was the last 'safe' day that you know of? :) > > *** > > I'm using 98.03.14 version. Works well for me. This is our backup machine > doing circa 700MB backup nightly over NFS. Dyson seems to be pushing 98.03.12 -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 23:35:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09665 for freebsd-current-outgoing; Wed, 18 Mar 1998 23:35:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf52.cruzers.com [205.215.232.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA09660 for ; Wed, 18 Mar 1998 23:35:57 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 1366 invoked by uid 100); 19 Mar 1998 07:37:14 -0000 Message-ID: <19980318233709.A1293@top.worldcontrol.com> Date: Wed, 18 Mar 1998 23:37:09 -0800 To: current@FreeBSD.ORG Cc: dyson@FreeBSD.ORG Subject: Re: cvs update -D'03/12/1998' . No CVSROOT specified! References: <19980318211402.23977@arh0300.urh.uiuc.edu> <199803190420.XAA00526@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.10i In-Reply-To: <199803190420.XAA00526@dyson.iquest.net>; from John S. Dyson on Wed, Mar 18, 1998 at 11:20:12PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On %M 0, "John S. Dyson" wrote: > Try checking out a kernel like: > > cvs co -D12-mar sys > > build and use that. It is likely safer than current as of today. It took > me an entire day to recover my system during the weekend. I can't say > it strongly enough to avoid using -current until we figure out the > problem! bls2# cd /usr/src bls2# cvs co -D12-mar sys cvs checkout: No CVSROOT specified! Please use the `-d' option cvs [checkout aborted]: or set the CVSROOT environment variable. help! -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Mar 18 23:36:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09810 for freebsd-current-outgoing; Wed, 18 Mar 1998 23:36:14 -0800 (PST) (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 XAA09799 for ; Wed, 18 Mar 1998 23:36:10 -0800 (PST) (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 JAA07728; Thu, 19 Mar 1998 09:35:51 +0200 (EET) Date: Thu, 19 Mar 1998 09:35:48 +0200 (EET) From: Vallo Kallaste X-Sender: vallo@solaris To: Karl Denninger cc: current@FreeBSD.ORG Subject: Re: 3/12/1998 KERNEL TEST RESULT In-Reply-To: <19980318235036.51789@mcs.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, 18 Mar 1998, Karl Denninger wrote: > Hello again, > > Just in case you're wondering, my regression tests against the 3/12/98 > kernel are complete, and it is ok - at least at the filesystem level. > > Again, if you're running -CURRENT, I strongly recommend backing out to the > 3/12/98 revision of the kernel immediately if you are running anything > with a later date. > > This will be my last note on this topic until I have determined that > it is safe to use a more "Current" CURRENT. > > One last time - if you are running a CURRENT kernel built after this point, > you are risking severe and unrecoverable damage to any locally-mounted UFS > filesystems. > > If you do a "make world" and actually get through it with such a kernel (the > odds are against this), you will be very, very fortunate if what you install > as a consequence of that "make world" boots when you are done! > > The problem includes destruction of BOTH metadata (ie: inode, directory, etc) > AND file data. The first will get fixed (for the most part) by FSCK. The > second is COMPLETELY undetectable and absolutely will screw you if you run > into it. > > Back out to 3/12 and it appears that you're safe from my testing here. *** Sorry, I'm emitting wrong info to the -current mailing list. I run 98.03.14 date system without any problems so far, but based to your last message safe way is 98.03.12 dated kernel. So, folks, please don't use 98.03.14 kernel based system as I suggest. This is a big mistake emitting mail to the list before reading latest messages. :-( 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 Wed Mar 18 23:41:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10609 for freebsd-current-outgoing; Wed, 18 Mar 1998 23:41:04 -0800 (PST) (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 XAA10559; Wed, 18 Mar 1998 23:40:52 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id IAA17498; Thu, 19 Mar 1998 08:42:04 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 19 Mar 1998 08:42:03 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: dannyman cc: Karl Denninger , dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: A reminder of toxic -current ** READ THIS ** In-Reply-To: <19980318214758.38114@arh0300.urh.uiuc.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 Wed, 18 Mar 1998, dannyman wrote: > First off, thanks to Karl, John and Steve for dire warnings, advice, > education, tackling the problem, etc. :) Yes. Big thanks, guys! > > 2) You are not tripping the condition that is causing the destruction. > > This *IS* possible; I have two machines in particular uses which do > > NOT cause the problem, but I don't know why. > > Are there any commonalities in chipsets, and the like? Particular drivers? > My system seems to be working perfectly normally, though to be honest, its > normal operation is not perfect. ;) A shuttle motherboard, Intel chips, WDC > drives .... K5. *shrug* Hmm. That's interesting coincidence. I'm running the kernel from Mar 16, the hardware is very similar (shuttle MB with Intel chips, IDE drives and K5 CPU), and I also don't see any problems. I don't like to play with fire - I just did cvsup and rebuild before I've read the warnings. Now, I'm backing off at full speed.. :-) 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 Wed Mar 18 23:42:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11154 for freebsd-current-outgoing; Wed, 18 Mar 1998 23:42:55 -0800 (PST) (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 XAA11133; Wed, 18 Mar 1998 23:42:48 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id CAA19953; Thu, 19 Mar 1998 02:42:50 -0500 (EST) (envelope-from toor) Message-Id: <199803190742.CAA19953@dyson.iquest.net> Subject: Re: cvs update -D'03/12/1998' . No CVSROOT specified! In-Reply-To: <19980318233709.A1293@top.worldcontrol.com> from "brian@worldcontrol.com" at "Mar 18, 98 11:37:09 pm" To: brian@worldcontrol.com Date: Thu, 19 Mar 1998 02:42:50 -0500 (EST) Cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 brian@worldcontrol.com said: > On %M 0, "John S. Dyson" wrote: > > Try checking out a kernel like: > > > > cvs co -D12-mar sys > > > > build and use that. It is likely safer than current as of today. It took > > me an entire day to recover my system during the weekend. I can't say > > it strongly enough to avoid using -current until we figure out the > > problem! > > bls2# cd /usr/src > bls2# cvs co -D12-mar sys > cvs checkout: No CVSROOT specified! Please use the `-d' option > cvs [checkout aborted]: or set the CVSROOT environment variable. > You need to point your CVSROOT environment variable to your CVS tree!!! -- 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 Wed Mar 18 23:52:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13569 for freebsd-current-outgoing; Wed, 18 Mar 1998 23:52:53 -0800 (PST) (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 XAA13552; Wed, 18 Mar 1998 23:52:46 -0800 (PST) (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 SAA18722; Thu, 19 Mar 1998 18:22:34 +1030 (CST) Message-Id: <199803190752.SAA18722@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: brian@worldcontrol.com cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: cvs update -D'03/12/1998' . No CVSROOT specified! In-reply-to: Your message of "Wed, 18 Mar 1998 23:37:09 -0800." <19980318233709.A1293@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Mar 1998 18:22:34 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > bls2# cd /usr/src > bls2# cvs co -D12-mar sys > cvs checkout: No CVSROOT specified! Please use the `-d' option > cvs [checkout aborted]: or set the CVSROOT environment variable. Urgh.. It appears you cvsup a current tree, and therefore don't have a CVS repository, so you just tell cvsup to get a copy of source which is further back. I haven't done it, but adding 'date=98.03.12.00.00' to your cvsup file and rerunning cvsup on this config file should do it.. (Every else seemed to assume you havea a CVS repo) --------------------------------------------------------------------- |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 Mar 19 02:11:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00171 for freebsd-current-outgoing; Thu, 19 Mar 1998 02:11:02 -0800 (PST) (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 CAA00166 for ; Thu, 19 Mar 1998 02:10:57 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id CAA21492; Thu, 19 Mar 1998 02:10:43 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803191010.CAA21492@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Hugh LaMaster cc: freebsd-current@FreeBSD.ORG Subject: Re: Stream_d benchmark... Wow, there really are differences in hardware In-reply-to: Your message of "Wed, 18 Mar 1998 08:58:06 PST." <199803181658.IAA02816@george.arc.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Thu, 19 Mar 1998 02:10:43 -0800 From: Amancio Hasty Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA00167 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is an Asus motherboard dying to double or more my memory system. My PPro200 is about a 1.5 years old and I hope that the new 100Mhz bus based systems fair better than my system. Cheers, Amancio ------------------------------------------------------------- Your clock granularity/precision appears to be 7812 microseconds. Each test below will take on the order of 101562 microseconds. (= 13 clock ticks) Increase the size of the arrays if this shows that you are not getting at least 20 clock ticks per test. ------------------------------------------------------------- WARNING -- The above is only a rough guideline. For best results, please be sure you know the precision of your system timer. ------------------------------------------------------------- Function Rate (MB/s) RMS time Min time Max time Copy: 113.7778 0.1557 0.1406 0.1719 Scale: 107.7895 0.1565 0.1484 0.1719 Add: 118.1538 0.2158 0.2031 0.2344 Triad: 118.1538 0.2213 0.2031 0.2344 > > Soeren Schmidt (sos@FreeBSD.org) wrote: > > In reply to Jaye Mathisen who wrote: > > > > Hmm, Then I should be proud of my noname system (p6/200/128MB 72pEDO): > > > > Function Rate (MB/s) RMS time Min time Max time > > Copy: 117.0286 0.2758 0.2734 0.2812 > : > > Triad: 125.3878 0.3917 0.3828 0.4219 > > > > So what ?? > > Like all benchmarks, there is the question of "pride". However, > computer performance is also a major problem/interest, and, stream > is particularly informative for a "toy benchmark". Your numbers > seem very high for a Natoma board - what type of EDO are you using > and what are your BIOS settings? Exactly what kind of "noname" board > is it? If these numbers are correct, I want one. Have you run the > c't ctcm benchmark on it also? That gives a nice profile of the > different memory bandwidth numbers from L1 cache, L2 cache, and > main memory. [Note also, stream sometimes doesn't get the clock > HZ set properly. Are you sure it is correct with these numbers?] > [Maybe you have the 45ns EDO? What are your leadoff timings?] > I'm impressed, anyway. I want to know more. In particular, I might > be better off with one of your "noname" configurations than a 333 MHz > P - II for driving some fast network interfaces. Your numbers look > more like one of the specially-built and tweaked expensive "server" > Orion boards. > > > > I figured that within reason, most mb's would have similar performance, > > > but I was wrong. > > First of all, it depends on the chipset. Does the Digital Prioris > ZX6000 system use the Orion chipset? It appears so. Note also > whether using FP DRAM or EDO, and, how fast the memory is (the > BIOS settings for lead-off timings may be slightly more aggressive > for slightly faster memory. > > > > All boxes are P6-200's, 256MB RAM (all RAM is 60ns FP as far as I know). > > > > > > Box 1 is a SuperMicro P6DNE: > > > Function Rate (MB/s) RMS time Min time Max time > > > Copy: 60.7395 0.2704 0.2634 0.2832 > > > Triad: 71.1647 0.3494 0.3372 0.3565 > > Typical for Natoma with FP DRAM I would guess. > > > > > > Box 2 is a Digital Prioris HX6000 > > > Copy: 73.3551 0.2197 0.2181 0.2249 > > > Triad: 77.4268 0.3108 0.3100 0.3122 > > Is this with EDO? > > > > Box 3 is a Digital Prioris ZX6000 > > > Function Rate (MB/s) RMS time Min time Max time > > > Copy: 84.8807 0.2018 0.1885 0.2834 > > > Scale: 97.5461 0.1661 0.1640 0.1720 > > > Add: 111.6549 0.2179 0.2149 0.2247 > > > Triad: 100.9468 0.2659 0.2377 0.4237 > > > > > > > > > Box 3 uses 256bit interleaved memory, rather than whatever the > > > "standard" is. > > I assume that this is an Orion GX chipset board. Yes, it does > have higher memory bandwidth than Natoma if properly configured. > Yes, IMHO, that does make a significant difference in the > real world. > > > > I thought it was just a marketing gimmick, but it seems to really > > > make a difference. > > Orion chipset boards had kind of a negative press at first due > to problems with PCI bandwidth, but, I assume (?) those were > worked out long ago. In any case, the Orion chipset never > achieved the mass-market commodity status of Natoma chipset. > As a consequence, boards remained, and remain expensive, and > now, the PPro200 is being phased out. I wouldn't mind having > one, but, there are only a few, expensive boards out there, > such as the American Megatrends Goliath, and PPro200 prices > never dropped that much, I guess because Intel wanted to phase > it out in favor of the P-II. > > > > > Have to see if it helps on some worldstone's. > > It should help a little bit, although, the real benefit tends > to be on user apps which stream through a lot of memory. The > classical FP applications, of course, but also, things like > digital video, image processing, graphics, etc. - anything > which streams through 1-4 MB of memory repeatedly. And, > network performance to/from userland, which usually requires > at least one data copy. > > > > 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 Mar 19 02:20:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01209 for freebsd-current-outgoing; Thu, 19 Mar 1998 02:20:56 -0800 (PST) (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 CAA01204 for ; Thu, 19 Mar 1998 02:20:53 -0800 (PST) (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 LAA02119; Thu, 19 Mar 1998 11:20:10 +0100 (CET) To: Michael Hancock cc: freebsd-current@FreeBSD.ORG Subject: Re: 4 WILLRELE's to bite the dust In-reply-to: Your message of "Fri, 13 Mar 1998 13:22:20 +0900." Date: Thu, 19 Mar 1998 11:20:09 +0100 Message-ID: <2117.890302809@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi mike, I let this patch run on a machine for some days and it slowly ground to a halt and finally locked up solid. No dump, sorry. -- 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 Mar 19 03:00:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA05758 for freebsd-current-outgoing; Thu, 19 Mar 1998 03:00:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from itesec.hsc.fr (root@itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA05736 for ; Thu, 19 Mar 1998 03:00:14 -0800 (PST) (envelope-from pb@hsc.fr) Received: from mars.hsc.fr (pb@mars.hsc.fr [192.70.106.44]) by itesec.hsc.fr (8.8.8/8.8.5/itesec-1.12-nospam) with ESMTP id LAA26040; Thu, 19 Mar 1998 11:59:24 +0100 (MET) Received: (from pb@localhost) by mars.hsc.fr (8.8.5/8.8.5/pb-19970301) id LAA28244; Thu, 19 Mar 1998 11:58:14 +0100 (MET) Message-ID: <19980319115813.MB01769@mars.hsc.fr> Date: Thu, 19 Mar 1998 11:58:13 +0100 From: pb@fasterix.frmug.org (Pierre Beyssac) To: Matthew.Thyer@dsto.defence.gov.au (Matthew Thyer) Cc: joelh@gnu.org, c5666305@comp.polyu.edu.hk, current@FreeBSD.ORG Subject: Re: Using CVSUP and CTM together (Was Re: Disk munging problem with current solved) References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> <350E643D.A47CB903@camtech.net.au> <199803182240.QAA07391@detlev.UUCP> <35106C23.64774CD9@dsto.defence.gov.au> <199803190244.UAA08131@detlev.UUCP> <35108C62.DDFB1544@dsto.defence.gov.au> X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 In-Reply-To: <35108C62.DDFB1544@dsto.defence.gov.au>; from Matthew Thyer on Mar 19, 1998 13:39:22 +1030 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Matthew Thyer: > Also it would seem that CTM is not very useful for developers as > they are required to update their tree before committing changes > (in case what they were to change has been changed by others). With CTM there are at least two solutions, as far as I know: A) Receive the CVS tree via CTM. It's expensive (you have to keep a whole source tree CVS repository PLUS a whole checked-out source tree). When you have local changes, you just "cvs update" to merge FreeBSD commits with your code. However, you can't commit your own changes even locally as this would desynchronize your CVS files from the FreeBSD repository, causing subsequent CTM patches to fail. In addition, this allows you to retrieve older versions of the files. B) Receive /usr/src via CTM. Update your tree locally, keep copies of the original files you modified. When CTM complains about a MD5 mismatch, copy the original file by adding a .ctm extension to it (CTM looks for these first). This allows you to extract the CTM patch. Then use diff3 to merge the changes back in your locally modified code. This goes someting like this (foobar.c is the locally modified file, foobar.c.ref is the "official" version) : 1) copy the original file back with a name to please CTM: cp foobar.c.ref foobar.c.ctm 2) extract CTM ctm_rmail .... 3) merge with diff3; if I remember correctly this is something like: diff3 -A -m foobar.c foobar.c.ref foobar.c.ctm > foobar.c.new 4) possibly resolve conflicts in foobar.c.new ('<<<<<' lines) 5) replace the files: mv foobar.c.new foobar.c mv foobar.c.ctm foobar.c.ref (A) is probably the easiest, but it's a bit heavy if you're short on disk space. I've been using (B) for a week now on a large set of changes (roughly 300 files changed) and it's fairly easy to manage after you've written a few helper scripts to do the boring job for you (the hard part is already written, it's diff3). I'm considering trying (A) due to peer (and Guinness) pressure :-))). The missing step here is that I haven't yet generated usable diffs between the code I changed and -current (I will, as soon as my patches are functional enough) In (A), you just need to "cvs diff". In (B), one more helper script should do the trick. BTW, the code is the INRIA IPv6 code I ported from the FreeBSD 2.2.5 version. I hope to be able to release it within less than a week now. -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 03:10:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA06971 for freebsd-current-outgoing; Thu, 19 Mar 1998 03:10:20 -0800 (PST) (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 DAA06959 for ; Thu, 19 Mar 1998 03:10:14 -0800 (PST) (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 LAA14751; Thu, 19 Mar 1998 11:06:30 GMT Date: Thu, 19 Mar 1998 20:06:30 +0900 (JST) From: Michael Hancock To: Poul-Henning Kamp cc: freebsd-current@FreeBSD.ORG Subject: Re: 4 WILLRELE's to bite the dust In-Reply-To: <2117.890302809@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 19 Mar 1998, Poul-Henning Kamp wrote: > Hi mike, I let this patch run on a machine for some days and it slowly > ground to a halt and finally locked up solid. No dump, sorry. Umm. What fs's are you using and what was the kernel build date? Thanks for the info, it sounds like I have more vops that share the fs code I touched and they need a VRELE at the top layer. Are you using NFS? Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 03:30:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09357 for freebsd-current-outgoing; Thu, 19 Mar 1998 03:30:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.ftf.dk (root@mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09344 for ; Thu, 19 Mar 1998 03:30:33 -0800 (PST) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.2]) by firewall.ftf.dk (8.7.6/8.7.3) with ESMTP id OAA13594; Thu, 19 Mar 1998 14:22:15 +0100 Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.5/8.8.5/prosa-1.1) with ESMTP id MAA25339; Thu, 19 Mar 1998 12:42:27 +0100 (CET) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.7/8.8.5/prosa-1.1) id MAA13278; Thu, 19 Mar 1998 12:29:22 +0100 (CET) Message-ID: <19980319122922.28659@deepo.prosa.dk> Date: Thu, 19 Mar 1998 12:29:22 +0100 From: Philippe Regnauld To: Pierre Beyssac Cc: current@FreeBSD.ORG Subject: Re: Using CVSUP and CTM together (Was Re: Disk munging problem with current solved) References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> <350E643D.A47CB903@camtech.net.au> <199803182240.QAA07391@detlev.UUCP> <35106C23.64774CD9@dsto.defence.gov.au> <199803190244.UAA08131@detlev.UUCP> <35108C62.DDFB1544@dsto.defence.gov.au> <19980319115813.MB01769@mars.hsc.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88e In-Reply-To: <19980319115813.MB01769@mars.hsc.fr>; from Pierre Beyssac on Thu, Mar 19, 1998 at 11:58:13AM +0100 X-Operating-System: FreeBSD 2.2.5-RELEASE i386 Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pierre Beyssac writes: > > BTW, the code is the INRIA IPv6 code I ported from the FreeBSD 2.2.5 > version. I hope to be able to release it within less than a week now. Note to the Core team: Is it likely that this implementation will make it into -current ? Or is it too big a piece to fit in the 3.0 puzzle ? -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- «Pluto placed his bad dog at the entrance of Hades to keep the dead IN and the living OUT! The archetypical corporate firewall?» - S. Kelly Bootle, ("MYTHOLOGY", in Marutukku distrib) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 03:46:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA10773 for freebsd-current-outgoing; Thu, 19 Mar 1998 03:46:36 -0800 (PST) (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 DAA10768 for ; Thu, 19 Mar 1998 03:46:33 -0800 (PST) (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 MAA02544; Thu, 19 Mar 1998 12:46:09 +0100 (CET) To: Michael Hancock cc: freebsd-current@FreeBSD.ORG Subject: Re: 4 WILLRELE's to bite the dust In-reply-to: Your message of "Thu, 19 Mar 1998 20:06:30 +0900." Date: Thu, 19 Mar 1998 12:46:09 +0100 Message-ID: <2542.890307969@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Mich ael Hancock writes: >On Thu, 19 Mar 1998, Poul-Henning Kamp wrote: > >> Hi mike, I let this patch run on a machine for some days and it slowly >> ground to a halt and finally locked up solid. No dump, sorry. > >Umm. What fs's are you using and what was the kernel build date? > >Thanks for the info, it sounds like I have more vops that share the fs >code I touched and they need a VRELE at the top layer. Are you using NFS? FFS+NFS, although NFS only occasionally. The FFS must be responsible for the problem, since NFS wasn't mounted for most of the time. -- 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 Mar 19 03:48:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11009 for freebsd-current-outgoing; Thu, 19 Mar 1998 03:48:42 -0800 (PST) (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 DAA11002 for ; Thu, 19 Mar 1998 03:48:38 -0800 (PST) (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 MAA02558; Thu, 19 Mar 1998 12:47:07 +0100 (CET) To: Philippe Regnauld cc: Pierre Beyssac , current@FreeBSD.ORG Subject: Re: Using CVSUP and CTM together (Was Re: Disk munging problem with current solved) In-reply-to: Your message of "Thu, 19 Mar 1998 12:29:22 +0100." <19980319122922.28659@deepo.prosa.dk> Date: Thu, 19 Mar 1998 12:47:07 +0100 Message-ID: <2556.890308027@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980319122922.28659@deepo.prosa.dk>, Philippe Regnauld writes: >Pierre Beyssac writes: >> >> BTW, the code is the INRIA IPv6 code I ported from the FreeBSD 2.2.5 >> version. I hope to be able to release it within less than a week now. > > Note to the Core team: > Is it likely that this implementation will make it into -current ? > Or is it too big a piece to fit in the 3.0 puzzle ? I still think it is to early for us to decide which IPv6 stack to choose, so I don't expect to see IPv6 in 3.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 Thu Mar 19 05:31:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21003 for freebsd-current-outgoing; Thu, 19 Mar 1998 05:31:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mnw.eas.slu.edu (mnw.eas.slu.edu [165.134.8.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA20998 for ; Thu, 19 Mar 1998 05:31:36 -0800 (PST) (envelope-from ejh@mnw.eas.slu.edu) Received: (from ejh@localhost) by mnw.eas.slu.edu (8.8.8/8.8.8) id HAA12970 for current@freebsd.org; Thu, 19 Mar 1998 07:31:35 -0600 (CST) Date: Thu, 19 Mar 1998 07:31:35 -0600 (CST) From: Eric Haug Message-Id: <199803191331.HAA12970@mnw.eas.slu.edu> To: current@FreeBSD.ORG Subject: aio with rtprio anomally Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I was using John Dyson's fcp program, the aio example posted around 1 Dec 1997 to stream to a tape drive. i think is was a tar | fcp sort of task. I kicked one of the processes to rtprio to see the effect, if any. This all seemed to do the right thing. After this completed i noted that the system was strangely sluggish. After rebooting, the system is back to normal. The current in question is from around Feb 27 1998. Just thought i would comment about this I have not had time to look into this further. eric haug Saint Louis Univ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 07:24:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03891 for freebsd-current-outgoing; Thu, 19 Mar 1998 07:24:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kamna.eunet.cz (kamna.eunet.cz [193.85.255.30]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA03885 for ; Thu, 19 Mar 1998 07:24:25 -0800 (PST) (envelope-from martin@eunet.cz) Message-Id: <199803191524.HAA03885@hub.freebsd.org> Received: (qmail 23670 invoked from network); 19 Mar 1998 15:23:46 -0000 Received: from woody.eunet.cz (HELO eunet.cz) (@193.85.255.60) by kamna.eunet.cz with SMTP; 19 Mar 1998 15:23:46 -0000 X-Mailer: exmh version 2.0.1 12/23/97 To: freebsd-current@FreeBSD.ORG Subject: problem with samba on 3.0 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Mar 1998 16:23:45 +0100 From: Martin Machacek Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've a strange problem with samba-1.9.18.3 port on FreeBSD-3.0-CURRENT (cvsuped and world made yesterday). If I build the port on 3.0-CURRENT (builds without problems) and run smbd and nmbd I cannot connect to the machine using SMB. When I try to connect with smbclient (1.9.18.3) from the localhost smbclient dies on bus error. I can connect with the cleint to other machines without problems. The same happens if i try to connect to the 3.0 machine with smbclient (same version) from a 2.2.5 machine. Actually sometimes the client at least asks for password connects and then dies on any command given to it including quit. Winblowz95 reports something like "name does not exist". If I run on the 3.0 machine smbd and nmbd (same version) build on 2.2.5 everything works ok Ican connect both from Windoz and Unix machines. It looks like a problem with smbd build on 3.0. The only interesting messages I was able to find in the /var/log/log.smb logfile is: 03/19/1998 15:14:52 Transaction 2 of length 93 switch message SMBsesssetupX (pid 470) Domain=[WORKGROUP] NativeOS=[Unix] NativeLanMan=[Samba] sesssetupX:name=[MARTIN] 03/19/1998 15:14:52 error packet at line 588 cmd=115 (SMBsesssetupX) eclass=2 ecode=2 error string = No such file or directory 03/19/1998 15:15:53 Closing idle connection This was when I tried to connect from the 2.2.5 machine. Another intersting portion might be right after smbd (and nmbd) startup where (I guess) smbd says: pm_process() returned Yes adding IPC service Failed to set socket option SO_KEEPALIVE <<< WHY? 03/19/1998 15:14:52 changed root to / open_oplock_ipc: opening loopback UDP socket. bind succeeded on port 0 <<< port 0? Has anybody seen this happening already? -- Martin Machacek [Internet CZ, Zirovnicka 6/3133, 106 00 Prague 10, Czech Republic] [phone: +420 2 71760337 fax: +420 2 24245125] [PGP KeyID 00F9E4BD] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 08:27:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16767 for freebsd-current-outgoing; Thu, 19 Mar 1998 08:27:58 -0800 (PST) (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 IAA16761; Thu, 19 Mar 1998 08:27:54 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id LAA05005; Thu, 19 Mar 1998 11:26:46 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Thu, 19 Mar 1998 11:26:46 -0500 (EST) From: "Alok K. Dhir" To: mark@grondar.za cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: A reminder of toxic -current In-Reply-To: <98A8C50807D608D8852565CC00240560.002337FE852565CC@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 On Thu, 19 Mar 1998 mark@grondar.za wrote: > "John S. Dyson" wrote: > > Yes. It is an extremely elusive problem. Are you using SMP or UP? Also, > > any info about your system config might be useful (so I can see how you > > are using your system.) It has been difficult for me to reproduce the > > problems since my latest commits, but they still do happen. > > I am using CURRENT on an SMP box. SCB's are hosed (I have an ahc), > so I disabled them; and the vx (ethernet) driver has a problem > where it suddenly starts r u n n i n g v e r y s l o w l y, But > I have no FS problems, and I reboot and FSCK after doing anything > vaguely large. In case it matters, I am also running a very current -current (March 17 kernel, 2:30 pm) on an SMP box, and so far (*knock knock) haven't had any problems with filesystem corruption, etc. Just another datapoint... Al To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 08:36:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18461 for freebsd-current-outgoing; Thu, 19 Mar 1998 08:36:42 -0800 (PST) (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 IAA18445 for ; Thu, 19 Mar 1998 08:36:35 -0800 (PST) (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 0yFiIj-0000VG-00; Thu, 19 Mar 1998 10:36:17 -0600 X-Mailer: exmh version 2.0zeta 7/24/97 To: Martin Machacek cc: freebsd-current@FreeBSD.ORG Subject: Re: problem with samba on 3.0 In-reply-to: Your message of "Thu, 19 Mar 1998 16:23:45 +0100." <199803191524.HAA03885@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Mar 1998 10:36:16 -0600 From: Ted Spradley Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've a strange problem with samba-1.9.18.3 port on FreeBSD-3.0-CURRENT > (cvsuped and world made yesterday). If I build the port on 3.0-CURRENT You poor soul! Shutdown now, boot your oldest kernel, and while you're fsck'ing and restoring backups, try to read the archives of this list from the last day or so. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 08:42:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20026 for freebsd-current-outgoing; Thu, 19 Mar 1998 08:42:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20019 for ; Thu, 19 Mar 1998 08:42:46 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id IAA28951 for ; Thu, 19 Mar 1998 08:41:57 -0800 (PST) (envelope-from jdp) Message-Id: <199803191641.IAA28951@austin.polstra.com> To: current@FreeBSD.ORG Subject: Re: cvs update -D'03/12/1998' . No CVSROOT specified! In-Reply-To: <199803190752.SAA18722@cain.gsoft.com.au> References: <199803190752.SAA18722@cain.gsoft.com.au> Organization: Polstra & Co., Seattle, WA Date: Thu, 19 Mar 1998 08:41:56 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199803190752.SAA18722@cain.gsoft.com.au>, Daniel O'Connor wrote: > It appears you cvsup a current tree, and therefore don't have a CVS > repository, so you just tell cvsup to get a copy of source which is further > back. > I haven't done it, but adding 'date=98.03.12.00.00' to your cvsup file and > rerunning cvsup on this config file should do it.. That's right, except you left out the seconds field. It should be: date=98.03.12.00.00.00 Warning to everybody else: DON'T do this unless your usual supfile already has a "tag" or "date" specification in it. If you don't already have that, then you've been CVSupping the CVS repository, not the checked-out -current tree. In that case, you should use something like "cvs -q upd -D 3/12/98" to revert your tree. If you are uncertain about this, read and reread cvsup(1) until you understand the difference between CVS mode and checkout mode. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 08:45:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20491 for freebsd-current-outgoing; Thu, 19 Mar 1998 08:45:20 -0800 (PST) (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 IAA20482; Thu, 19 Mar 1998 08:45:12 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id LAA05071; Thu, 19 Mar 1998 11:43:45 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Thu, 19 Mar 1998 11:43:45 -0500 (EST) From: "Alok K. Dhir" To: brian@worldcontrol.com cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: cvs update -D'03/12/1998' . No CVSROOT specified! In-Reply-To: <6A1BAD1B8DB6D5DE852565CC002AFBD7.002A3682852565CC@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 "man cvs", or simply reading the output of the cvs command below, should have helped you to discover the "-d" option. > bls2# cvs co -D12-mar sys > cvs checkout: No CVSROOT specified! Please use the `-d' option > cvs [checkout aborted]: or set the CVSROOT environment variable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 08:47:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21028 for freebsd-current-outgoing; Thu, 19 Mar 1998 08:47:13 -0800 (PST) (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 IAA21023 for ; Thu, 19 Mar 1998 08:47:09 -0800 (PST) (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 LAA10440 for ; Thu, 19 Mar 1998 11:44:01 -0500 (EST) Date: Thu, 19 Mar 1998 11:46:54 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: current@FreeBSD.ORG Subject: Line for cvsup users on current to grab safe sources 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 a note here for those using cvsup. Someone asked how to retrieve older src trees with cvsup, and I havent seen an answer for him/her yet. John and karl replied but they are using CVS, and he was asking about cvsup. I dont think anyone replied with a cvsup line to back peddle his src, or i may have skipped that mail on acident if they did. All you have to do is add : *default date=98.03.12.00.00.00 below the rest of the "*default" lines and cvsup away! So for all of you using cvsup and not CVS and running current, and are concerned that your current machine past the 12th is possesed and about to spew grean pea soup on you, use that line in your standard-supfile config and you'll feel better after a cvsup run and a new kernel :) Chris -- "I am closed minded. It keeps the rain out." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.5 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 Mar 19 09:07:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23734 for freebsd-current-outgoing; Thu, 19 Mar 1998 09:07:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mexcom.net (tol1-100.uninet.net.mx [200.38.135.100] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23579; Thu, 19 Mar 1998 09:05:34 -0800 (PST) (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix (telmex@sunix.mexcom.net [206.103.64.3]) by ns.mexcom.net (8.8.8/8.8.7) with SMTP id LAA16436; Thu, 19 Mar 1998 11:02:54 -0600 (CST) Message-ID: <3511516B.35416BB9@ver1.telmex.net.mx> Date: Thu, 19 Mar 1998 11:10:03 -0600 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: "Daniel O'Connor" CC: brian@worldcontrol.com, current@FreeBSD.ORG, dyson@FreeBSD.ORG Subject: Re: cvs update -D'03/12/1998' . No CVSROOT specified! References: <199803190752.SAA18722@cain.gsoft.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > > > bls2# cd /usr/src > > bls2# cvs co -D12-mar sys > > cvs checkout: No CVSROOT specified! Please use the `-d' option > > cvs [checkout aborted]: or set the CVSROOT environment variable. > Urgh.. > It appears you cvsup a current tree, and therefore don't have a CVS > repository, so you just tell cvsup to get a copy of source which is further > back. > I haven't done it, but adding 'date=98.03.12.00.00' to your cvsup file and > rerunning cvsup on this config file should do it.. > (Every else seemed to assume you havea a CVS repo) Interesting, but when I try it I get : Server message: Unknown collection date=98.03.12.00.00 Establishing active-mode data connection Running Skipping collection date=98.03.12.00.00/cvs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 09:11:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24371 for freebsd-current-outgoing; Thu, 19 Mar 1998 09:11:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mexcom.net (tol1-100.uninet.net.mx [200.38.135.100] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23987 for ; Thu, 19 Mar 1998 09:09:51 -0800 (PST) (envelope-from eculp@ver1.telmex.net.mx) Received: from sunix (telmex@sunix.mexcom.net [206.103.64.3]) by ns.mexcom.net (8.8.8/8.8.7) with SMTP id LAA16541; Thu, 19 Mar 1998 11:08:02 -0600 (CST) Message-ID: <3511529F.51D122F@ver1.telmex.net.mx> Date: Thu, 19 Mar 1998 11:15:11 -0600 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: Open Systems Networking CC: current@FreeBSD.ORG Subject: Re: Line for cvsup users on current to grab safe sources References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Open Systems Networking wrote: > > Just a note here for those using cvsup. > Someone asked how to retrieve older src trees with cvsup, and I havent > seen an answer for him/her yet. John and karl replied but they are using > CVS, and he was asking about cvsup. I dont think anyone replied with a > cvsup line to back peddle his src, or i may have skipped that mail on > acident if they did. All you have to do is add : > > *default date=98.03.12.00.00.00 > > below the rest of the "*default" lines > and cvsup away! > So for all of you using cvsup and not CVS and running current, and are > concerned that your current machine past the 12th is possesed and about to > spew grean pea soup on you, use that line in your standard-supfile config > and you'll feel better after a cvsup run and a new kernel :) Thanks, that solved my date problem. Seems to be running fine. Please disregard my previous mail. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 09:54:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02163 for freebsd-current-outgoing; Thu, 19 Mar 1998 09:54:23 -0800 (PST) (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 JAA02158 for ; Thu, 19 Mar 1998 09:54:18 -0800 (PST) (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 LAA18078 for ; Thu, 19 Mar 1998 11:54:14 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <020c01bd535f$0bf8dfa0$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: Subject: Re: Line for cvsup users on current to grab safe sources Date: Thu, 19 Mar 1998 11:47:11 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.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: Open Systems Networking To: current@FreeBSD.ORG Date: Thursday, March 19, 1998 10:51 AM Subject: Line for cvsup users on current to grab safe sources > >Just a note here for those using cvsup. >Someone asked how to retrieve older src trees with cvsup, and I havent >seen an answer for him/her yet. John and karl replied but they are using >CVS, and he was asking about cvsup. I dont think anyone replied with a >cvsup line to back peddle his src, or i may have skipped that mail on >acident if they did. All you have to do is add : > >*default date=98.03.12.00.00.00 > >below the rest of the "*default" lines >and cvsup away! How about just adding: *default date=98.03.12.00.00.00 src-sys to the end of the cvsupfile. That way you get current src's for most of the tree, and March 12 src's for the kernel. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 09:56:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02610 for freebsd-current-outgoing; Thu, 19 Mar 1998 09:56:28 -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 JAA02601 for ; Thu, 19 Mar 1998 09:56:26 -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 LAA29615; Thu, 19 Mar 1998 11:56:27 -0600 (CST) Message-ID: <19980319115627.54781@arh0300.urh.uiuc.edu> Date: Thu, 19 Mar 1998 11:56:27 -0600 From: dannyman To: "Scot W. Hetzel" , current@FreeBSD.ORG Subject: Re: Line for cvsup users on current to grab safe sources References: <020c01bd535f$0bf8dfa0$c3e0d9cf@admin.westbend.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=QahgC5+KEYLbs62T X-Mailer: Mutt 0.89i In-Reply-To: <020c01bd535f$0bf8dfa0$c3e0d9cf@admin.westbend.net>; from Scot W. Hetzel on Thu, Mar 19, 1998 at 11:47:11AM -0600 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 --QahgC5+KEYLbs62T Content-Type: text/plain; charset=us-ascii On Thu, Mar 19, 1998 at 11:47:11AM -0600, Scot W. Hetzel wrote: > How about just adding: > > *default date=98.03.12.00.00.00 > src-sys > > to the end of the cvsupfile. That way you get current src's for most of the > tree, and March 12 src's for the kernel. I've attached my /etc/cvsupfile which shows the simple lazy mods I did, if anyone mind find it useful. -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement --QahgC5+KEYLbs62T Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=cvsupfile *default host=cvsup2.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs ###*default tag=RELENG_2_2 *default tag=. *default delete use-rel-suffix ### Temporary, until fs problems disappear *default date=98.03.12.08.00.00 src-all src-crypto src-secure *default tag=. ### Temporary, until fs problems disappear *default date=. ports-all doc-all --QahgC5+KEYLbs62T-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 10:05:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05387 for freebsd-current-outgoing; Thu, 19 Mar 1998 10:05:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from george.arc.nasa.gov (george.arc.nasa.gov [128.102.194.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05332 for ; Thu, 19 Mar 1998 10:04:59 -0800 (PST) (envelope-from lamaster@george.arc.nasa.gov) Received: (from lamaster@localhost) by george.arc.nasa.gov (8.8.7/8.8.7) id KAA01635; Thu, 19 Mar 1998 10:00:04 -0800 (PST) From: Hugh LaMaster Message-Id: <199803191800.KAA01635@george.arc.nasa.gov> Subject: Re: Stream_d benchmark... Wow, there really are differences in To: freebsd-current@FreeBSD.ORG Date: Thu, 19 Mar 1998 10:00:03 -0800 (PST) Cc: lamaster@george.arc.nasa.gov Reply-To: lamaster@george.arc.nasa.gov In-Reply-To: <199803191010.CAA21492@rah.star-gate.com> from "Amancio Hasty" at Mar 19, 98 02:10:43 am X-Mailer: ELM [version 2.4 PL24] 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 For the discussion of the chipsets, I refer to my previous post. This is just to put the numbers in one place so that they can be compared to previous numbers. This discussion should probably be elsewhere - in - hardware perhaps? > This is an Asus motherboard dying to double or more my memory system. > > My PPro200 is about a 1.5 years old and I hope that the new 100Mhz bus > based systems fair better than my system. > ------------------------------------------------------------- > Function Rate (MB/s) RMS time Min time Max time > Copy: 113.7778 0.1557 0.1406 0.1719 > Scale: 107.7895 0.1565 0.1484 0.1719 > Add: 118.1538 0.2158 0.2031 0.2344 > Triad: 118.1538 0.2213 0.2031 0.2344 These numbers are quite good. Hard to tell how much of the differences seen are due to board design, aggressive BIOS settings, memory technology, and chipset. And, perhaps, compilers, although the compiler can't do anything about the poor PPro200/Natoma write bandwidth. These numbers seem high to me based on what I have read previously for generic EDO. Anybody using BEDO out there? > > Soeren Schmidt (sos@FreeBSD.org) wrote: > > > In reply to Jaye Mathisen who wrote: > > > > > > Hmm, Then I should be proud of my noname system (p6/200/128MB 72pEDO): > > > > > > Function Rate (MB/s) RMS time Min time Max time > > > Copy: 117.0286 0.2758 0.2734 0.2812 > > : > > > Triad: 125.3878 0.3917 0.3828 0.4219 Higher yet for generic EDO. > > > > All boxes are P6-200's, 256MB RAM (all RAM is 60ns FP as far as I know). > > > > > > > > Box 1 is a SuperMicro P6DNE: > > > > Function Rate (MB/s) RMS time Min time Max time > > > > Copy: 60.7395 0.2704 0.2634 0.2832 > > > > Triad: 71.1647 0.3494 0.3372 0.3565 > > > > Box 2 is a Digital Prioris HX6000 > > > > Copy: 73.3551 0.2197 0.2181 0.2249 > > > > Triad: 77.4268 0.3108 0.3100 0.3122 > > > > Box 3 is a Digital Prioris ZX6000 > > > > Function Rate (MB/s) RMS time Min time Max time > > > > Copy: 84.8807 0.2018 0.1885 0.2834 > > > > Scale: 97.5461 0.1661 0.1640 0.1720 > > > > Add: 111.6549 0.2179 0.2149 0.2247 > > > > Triad: 100.9468 0.2659 0.2377 0.4237 > > > > Box 3 uses 256bit interleaved memory, rather than whatever the > > > > "standard" is. The web site for stream is http://www.cs.virginia.edu/stream and down in ../standard/Bandwidth.html we see the following for x86 boards tested. Note that some people have complained of the difficulty approaching Intel's "Alder" numbers, for the Orion chipset. That board presumably had a very aggressive memory design, and used Orion with full memory interleaving. Various magazines have reported on what bandwidth the consumer actually gets in a typical system with typical software, and the picture has usually been unpleasant. So -- Interesting that some of the numbers above seem to almost reach the Alder numbers using Natoma w/ EDO. I admit I am surprised. Here are a few numbers, with the big systems for reference and entertainment, and the PC's at the bottom. Note that the highest Intel board tested is a Dell PII_300; unfortunately, chipset is not specified. Note that the way this benchmark counts bandwidth (in and out), a copy shows twice the bandwidth that, e.g., the *rate* of bcopy() would show. All results are in MB/s --- 1 MB=10^6 B, *not* 2^20 B ------------------------------------------------------------------ Machine ID ncpus COPY SCALE ADD TRIAD ------------------------------------------------------------------ [Big Iron - now that's memory bandwidth. About 100X the bandwidth per CPU of the PCs. Too bad the CPUs are so expensive.] NEC_SX_4 32 434784.0 432886.0 437358.0 436954.0 NEC_SX_4 1 15983.0 15984.0 15989.0 15898.0 Cray_T932_321024-3E 32 310721.0 302182.0 359841.0 359270.0 Cray_T932_321024-3E 1 10653.0 10221.0 13014.0 13682.0 Cray_C90 1 6965.4 6965.4 9378.7 9500.7 [Interesting workstation-server numbers, but, not all up to date or the latest models.] SGI_Origin_2000_2 128 21857.6 23351.7 24459.5 22913.6 SGI_Origin_2000_1 32 8556.0 8670.0 9733.0 9435.0 SGI_Origin_2000_1 1 296.0 300.0 315.0 317.0 IBM_RS6000-591 1 711.1 695.7 750.0 800.0 DEC_600au_600 1 227.7 223.0 243.5 248.2 Sun_Ultra2-2200 1 228.5 227.5 258.9 189.9 HP_C180 1 262.3 262.3 244.9 242.4 [PC numbers, unfortunately without the chipset and memory technology info which would help sort this out.] Compaq_Proliant_5000 1 123.1 114.3 141.2 126.3 Dell_P166s 1 119.5 102.4 107.5 104.1 Dell_Pentium_133 1 88.0 125.7 132.0 120.0 Dell_486_DX-2-66 1 33.3 16.5 22.0 18.8 Dell_P6_200 1 102.4 102.4 112.9 112.9 Dell_PII_300 1 188.2 173.0 213.3 188.2 Gateway_2000_P6-200 1 107.9 89.5 100.5 101.6 Gateway_2000_P5-133-66 1 91.4 114.3 126.0 114.0 Intel_Alder_Pentium_Pr 1 140.0 140.0 163.9 167.6 Intel_Pentium-133 1 84.4 77.1 85.7 85.9 Intel_Pentium-100 1 85.1 74.4 77.0 75.2 Intel_Pentium-90 1 46.4 69.9 69.9 69.9 Intel_Pentium-60 1 37.2 62.1 61.3 58.5 PC-clone-AMD-486DX-50 1 38.1 26.2 28.6 23.3 PC-clone-AMD-486DX-80 1 83.9 41.9 39.3 39.3 Viglen_Pentium_60 1 47.1 61.5 63.1 60.0 Micron_P6-200 1 98.4 97.4 106.5 105.0 Micron_P5-120 1 79.3 100.4 109.9 107.7 Asus_Pentium_180 1 76.2 110.3 109.1 100.0 Asus_Pentium_200 1 84.2 123.1 123.1 111.6 Triton_II_Pentium_133 1 93.5 113.3 116.6 110.3 Triton_II_Pentium_133 1 75.9 85.3 87.8 85.3 Gigabyte_586HX 1 88.9 118.5 126.3 117.1 Note: These numbers don't tell the entire bandwidth story - the cache hierarchy, latency, read and write bandwidth at each level, not to mention MP performance, cache-coherency, prefetch, multiple outstanding transactions, etc. etc. etc. are enough to write a (large) book about. However, my experience is that many applications are sensitive to bandwidth and it is worth a little effort to get the most out the CPU. -- Hugh LaMaster, M/S 233-21, ASCII Email: hlamaster@mail.arc.nasa.gov NASA Ames Research Center Or: lamaster@george.arc.nasa.gov Moffett Field, CA 94035-1000 No Junkmail: USC 18 section 2701 Phone: 650/604-1056 Disclaimer: Unofficial, 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 Mar 19 10:22:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09786 for freebsd-current-outgoing; Thu, 19 Mar 1998 10:22:12 -0800 (PST) (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 KAA09764 for ; Thu, 19 Mar 1998 10:22:06 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id KAA01912; Thu, 19 Mar 1998 10:22:02 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803191822.KAA01912@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: lamaster@george.arc.nasa.gov cc: freebsd-current@FreeBSD.ORG Subject: Re: Stream_d benchmark... Wow, there really are differences in In-reply-to: Your message of "Thu, 19 Mar 1998 10:00:03 PST." <199803191800.KAA01635@george.arc.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Mar 1998 10:22:02 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi My PCI chipset is: chip0: I am using 60ns EDO . My compilation line : gcc -o stream_d stream_d.c second_cpu.c -maligne-double -O3 Would be nice to have SDRAM four way interleaved 8) Cheers, Amancio > > For the discussion of the chipsets, I refer to my previous post. > This is just to put the numbers in one place so that they can be > compared to previous numbers. This discussion should probably be > elsewhere - in - hardware perhaps? > > > > This is an Asus motherboard dying to double or more my memory system. > > > > My PPro200 is about a 1.5 years old and I hope that the new 100Mhz bus > > based systems fair better than my system. > > > ------------------------------------------------------------- > > Function Rate (MB/s) RMS time Min time Max time > > Copy: 113.7778 0.1557 0.1406 0.1719 > > Scale: 107.7895 0.1565 0.1484 0.1719 > > Add: 118.1538 0.2158 0.2031 0.2344 > > Triad: 118.1538 0.2213 0.2031 0.2344 > > These numbers are quite good. Hard to tell how much of the > differences seen are due to board design, aggressive BIOS settings, > memory technology, and chipset. And, perhaps, compilers, although > the compiler can't do anything about the poor PPro200/Natoma write > bandwidth. These numbers seem high to me based on what I have read > previously for generic EDO. Anybody using BEDO out there? > > > > Soeren Schmidt (sos@FreeBSD.org) wrote: > > > > In reply to Jaye Mathisen who wrote: > > > > > > > > Hmm, Then I should be proud of my noname system (p6/200/128MB 72pEDO): > > > > > > > > Function Rate (MB/s) RMS time Min time Max time > > > > Copy: 117.0286 0.2758 0.2734 0.2812 > > > : > > > > Triad: 125.3878 0.3917 0.3828 0.4219 > > Higher yet for generic EDO. > > > > > > All boxes are P6-200's, 256MB RAM (all RAM is 60ns FP as far as I know). > > > > > > > > > > Box 1 is a SuperMicro P6DNE: > > > > > Function Rate (MB/s) RMS time Min time Max time > > > > > Copy: 60.7395 0.2704 0.2634 0.2832 > > > > > Triad: 71.1647 0.3494 0.3372 0.3565 > > > > > > Box 2 is a Digital Prioris HX6000 > > > > > Copy: 73.3551 0.2197 0.2181 0.2249 > > > > > Triad: 77.4268 0.3108 0.3100 0.3122 > > > > > > Box 3 is a Digital Prioris ZX6000 > > > > > Function Rate (MB/s) RMS time Min time Max time > > > > > Copy: 84.8807 0.2018 0.1885 0.2834 > > > > > Scale: 97.5461 0.1661 0.1640 0.1720 > > > > > Add: 111.6549 0.2179 0.2149 0.2247 > > > > > Triad: 100.9468 0.2659 0.2377 0.4237 > > > > > > Box 3 uses 256bit interleaved memory, rather than whatever the > > > > > "standard" is. > > > The web site for stream is http://www.cs.virginia.edu/stream > and down in ../standard/Bandwidth.html we see the following > for x86 boards tested. Note that some people have complained > of the difficulty approaching Intel's "Alder" numbers, for the > Orion chipset. That board presumably had a very aggressive > memory design, and used Orion with full memory interleaving. > Various magazines have reported on what bandwidth the consumer > actually gets in a typical system with typical software, > and the picture has usually been unpleasant. So -- > > Interesting that some of the numbers above seem to almost > reach the Alder numbers using Natoma w/ EDO. I admit I am > surprised. Here are a few numbers, with the big systems > for reference and entertainment, and the PC's at the bottom. > Note that the highest Intel board tested is a Dell PII_300; > unfortunately, chipset is not specified. Note that the > way this benchmark counts bandwidth (in and out), a copy > shows twice the bandwidth that, e.g., the *rate* of bcopy() > would show. > > > > All results are in MB/s --- 1 MB=10^6 B, *not* 2^20 B > > ------------------------------------------------------------------ > Machine ID ncpus COPY SCALE ADD TRIAD > ------------------------------------------------------------------ > > > [Big Iron - now that's memory bandwidth. About 100X the > bandwidth per CPU of the PCs. Too bad the CPUs are so > expensive.] > > NEC_SX_4 32 434784.0 432886.0 437358.0 436954.0 > NEC_SX_4 1 15983.0 15984.0 15989.0 15898.0 > Cray_T932_321024-3E 32 310721.0 302182.0 359841.0 359270.0 > Cray_T932_321024-3E 1 10653.0 10221.0 13014.0 13682.0 > Cray_C90 1 6965.4 6965.4 9378.7 9500.7 > > > > [Interesting workstation-server numbers, but, not all up to > date or the latest models.] > > SGI_Origin_2000_2 128 21857.6 23351.7 24459.5 22913.6 > SGI_Origin_2000_1 32 8556.0 8670.0 9733.0 9435.0 > SGI_Origin_2000_1 1 296.0 300.0 315.0 317.0 > IBM_RS6000-591 1 711.1 695.7 750.0 800.0 > DEC_600au_600 1 227.7 223.0 243.5 248.2 > Sun_Ultra2-2200 1 228.5 227.5 258.9 189.9 > HP_C180 1 262.3 262.3 244.9 242.4 > > > > [PC numbers, unfortunately without the chipset and memory > technology info which would help sort this out.] > > Compaq_Proliant_5000 1 123.1 114.3 141.2 126.3 > Dell_P166s 1 119.5 102.4 107.5 104.1 > Dell_Pentium_133 1 88.0 125.7 132.0 120.0 > Dell_486_DX-2-66 1 33.3 16.5 22.0 18.8 > Dell_P6_200 1 102.4 102.4 112.9 112.9 > Dell_PII_300 1 188.2 173.0 213.3 188.2 > Gateway_2000_P6-200 1 107.9 89.5 100.5 101.6 > Gateway_2000_P5-133-66 1 91.4 114.3 126.0 114.0 > Intel_Alder_Pentium_Pr 1 140.0 140.0 163.9 167.6 > Intel_Pentium-133 1 84.4 77.1 85.7 85.9 > Intel_Pentium-100 1 85.1 74.4 77.0 75.2 > Intel_Pentium-90 1 46.4 69.9 69.9 69.9 > Intel_Pentium-60 1 37.2 62.1 61.3 58.5 > PC-clone-AMD-486DX-50 1 38.1 26.2 28.6 23.3 > PC-clone-AMD-486DX-80 1 83.9 41.9 39.3 39.3 > Viglen_Pentium_60 1 47.1 61.5 63.1 60.0 > Micron_P6-200 1 98.4 97.4 106.5 105.0 > Micron_P5-120 1 79.3 100.4 109.9 107.7 > Asus_Pentium_180 1 76.2 110.3 109.1 100.0 > Asus_Pentium_200 1 84.2 123.1 123.1 111.6 > Triton_II_Pentium_133 1 93.5 113.3 116.6 110.3 > Triton_II_Pentium_133 1 75.9 85.3 87.8 85.3 > Gigabyte_586HX 1 88.9 118.5 126.3 117.1 > > > > > Note: These numbers don't tell the entire bandwidth story - > the cache hierarchy, latency, read and write bandwidth at > each level, not to mention MP performance, cache-coherency, > prefetch, multiple outstanding transactions, etc. etc. etc. > are enough to write a (large) book about. > > However, my experience is that many applications are sensitive > to bandwidth and it is worth a little effort to get the most > out the CPU. > > > -- > Hugh LaMaster, M/S 233-21, ASCII Email: hlamaster@mail.arc.nasa.gov > NASA Ames Research Center Or: lamaster@george.arc.nasa.gov > Moffett Field, CA 94035-1000 No Junkmail: USC 18 section 2701 > Phone: 650/604-1056 Disclaimer: Unofficial, personal *opinion*. > > > 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 Mar 19 14:23:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16363 for freebsd-current-outgoing; Thu, 19 Mar 1998 14:23:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16345 for ; Thu, 19 Mar 1998 14:23:46 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id OAA02377; Thu, 19 Mar 1998 14:23:39 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Thu, 19 Mar 1998 14:23:39 -0800 (PST) From: Chris Timmons To: John Polstra cc: current@FreeBSD.ORG Subject: Re: cvs update -D'03/12/1998' . No CVSROOT specified! In-Reply-To: <199803191641.IAA28951@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And let us not forget that CVS is aware of your timezone, so if John Dyson in America's Heartland says: cvs -q update -D"March 12, 1998" the actual tag will be offset from UTC by 6 hours, whereas if I do it here on PST, the tag will be offset from UTC by 8 hours. As a result we could be talking about different source code snapshots. cvs -q update -D"March 12, 1998 00:00 UTC" is a more precise specification, which is what I used and built a kernel from this morning. (Actually I also supplied -APd on my command line to cvs.) -Chris On Thu, 19 Mar 1998, John Polstra wrote: > Warning to everybody else: DON'T do this unless your usual supfile > already has a "tag" or "date" specification in it. If you don't > already have that, then you've been CVSupping the CVS repository, > not the checked-out -current tree. In that case, you should use > something like "cvs -q upd -D 3/12/98" to revert your tree. If > you are uncertain about this, read and reread cvsup(1) until you > understand the difference between CVS mode and checkout mode. > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 14:56:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21677 for freebsd-current-outgoing; Thu, 19 Mar 1998 14:56:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bmccane.maxbaud.net ([208.155.166.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21667 for ; Thu, 19 Mar 1998 14:56:05 -0800 (PST) (envelope-from toor@bmccane.maxbaud.net) Received: (from root@localhost) by bmccane.maxbaud.net (8.8.8/8.8.7) id QAA06506; Thu, 19 Mar 1998 16:55:52 -0600 (CST) (envelope-from toor) Date: Thu, 19 Mar 1998 16:55:51 -0600 (CST) From: Wm Brian McCane To: current@FreeBSD.ORG Subject: soft updates 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 missed this. I pulled the softupdates7.tar file from incoming. Is this the latest version or is there somewhere else I need to go? brian +-----------------------------------+------------------------------------------+ He rides a cycle of mighty days, and \ Wm Brian and Lori McCane represents the last great schizm among\ McCane Consulting the gods. Evil though he obviously is, \ root@bmccane.cavtech.com he is a mighty figure, this father of \ http://bmccane.cavtech.com/ my spirit, and I respect him as the sons \ http://bmccane.cavtech.com/~pictures/ of old did the fathers of their bodies. \ http://bmccane.cavtech.com/~bmccane/ Roger Zelazny - "Lord of Light" \ +-------------------------------------------+----------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 15:32:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27958 for freebsd-current-outgoing; Thu, 19 Mar 1998 15:32:01 -0800 (PST) (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 PAA27823 for ; Thu, 19 Mar 1998 15:31:18 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA10013; Thu, 19 Mar 1998 18:30:55 -0500 (EST) (envelope-from toor) Message-Id: <199803192330.SAA10013@dyson.iquest.net> Subject: Re: soft updates In-Reply-To: from Wm Brian McCane at "Mar 19, 98 04:55:51 pm" To: root@bmccane.maxbaud.net (Wm Brian McCane) Date: Thu, 19 Mar 1998 18:30:54 -0500 (EST) Cc: current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Wm Brian McCane said: > I missed this. I pulled the softupdates7.tar file from incoming. Is > this the latest version or is there somewhere else I need to go? > The stubs are now in -current (but better not use -current newer than 12 Mar 98.) You'll still need the encumbered softupdates parts. -- 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 Thu Mar 19 16:00:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03955 for freebsd-current-outgoing; Thu, 19 Mar 1998 16:00:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bmccane.maxbaud.net ([208.155.166.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03756; Thu, 19 Mar 1998 15:58:56 -0800 (PST) (envelope-from toor@bmccane.maxbaud.net) Received: (from root@localhost) by bmccane.maxbaud.net (8.8.8/8.8.7) id RAA07847; Thu, 19 Mar 1998 17:56:39 -0600 (CST) (envelope-from toor) Date: Thu, 19 Mar 1998 17:56:37 -0600 (CST) From: Wm Brian McCane To: "John S. Dyson" cc: current@FreeBSD.ORG Subject: Re: soft updates In-Reply-To: <199803192330.SAA10013@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 Thu, 19 Mar 1998, John S. Dyson wrote: > Wm Brian McCane said: > > I missed this. I pulled the softupdates7.tar file from incoming. Is > > this the latest version or is there somewhere else I need to go? > > > The stubs are now in -current (but better not use -current newer than > 12 Mar 98.) You'll still need the encumbered softupdates parts. > > -- > 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. > Yah! I have seen all of the various warnings (and noticed that some people still didn't get the hint ;). I am downloading the CVS trees as I type so I can do a cvs update -D"03/12/98" sys brian Think anyone noticed it that time 8). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 16:27:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07712 for freebsd-current-outgoing; Thu, 19 Mar 1998 16:27:28 -0800 (PST) (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 QAA07699; Thu, 19 Mar 1998 16:27:22 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id QAA02957; Thu, 19 Mar 1998 16:26:44 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803200026.QAA02957@rah.star-gate.com> To: Wm Brian McCane cc: "John S. Dyson" , current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: soft updates In-reply-to: Your message of "Thu, 19 Mar 1998 17:56:37 CST." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2954.890353603.1@rah> Date: Thu, 19 Mar 1998 16:26:43 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And softupdates is not ready for prime time. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 16:29:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07897 for freebsd-current-outgoing; Thu, 19 Mar 1998 16:29:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07876 for ; Thu, 19 Mar 1998 16:28:35 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id QAA01550 for ; Thu, 19 Mar 1998 16:28:22 -0800 (PST) (envelope-from jdp) Message-Id: <199803200028.QAA01550@austin.polstra.com> To: current@FreeBSD.ORG Subject: Re: cvs update -D'03/12/1998' . No CVSROOT specified! In-Reply-To: <3511516B.35416BB9@ver1.telmex.net.mx> References: <199803190752.SAA18722@cain.gsoft.com.au> <3511516B.35416BB9@ver1.telmex.net.mx> Organization: Polstra & Co., Seattle, WA Date: Thu, 19 Mar 1998 16:28:22 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3511516B.35416BB9@ver1.telmex.net.mx>, Edwin Culp wrote: > Interesting, but when I try it I get : > > Server message: Unknown collection date=98.03.12.00.00 Five minutes looking at the output of "man cvsup" would solve this problem for you. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 17:01:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14626 for freebsd-current-outgoing; Thu, 19 Mar 1998 17:01:04 -0800 (PST) (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 RAA14594 for ; Thu, 19 Mar 1998 17:00:56 -0800 (PST) (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 LAA24874 for ; Fri, 20 Mar 1998 11:30:52 +1030 (CST) Message-Id: <199803200100.LAA24874@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@FreeBSD.ORG Subject: More wank^H^H^H^Hspeed tests Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Mar 1998 11:30:51 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is my 6x86/P166+ with an rev 0x02 on pci0.0.0. stream_d was compiled with gcc -o stream_d stream_d.c second_cpu.c -malign-double -O3 -lm I don't have a world stone ATM, but it sucks anyway :) ------------------------------------------------------------- This system uses 8 bytes per DOUBLE PRECISION word. ------------------------------------------------------------- Array size = 1000000, Offset = 0 Total memory required = 22.9 MB. Each test is run 10 times, but only the *best* time for each is used. ------------------------------------------------------------- Your clock granularity/precision appears to be 7812 microseconds. Each test below will take on the order of 164062 microseconds. (= 21 clock ticks) Increase the size of the arrays if this shows that you are not getting at least 20 clock ticks per test. ------------------------------------------------------------- WARNING -- The above is only a rough guideline. For best results, please be sure you know the precision of your system timer. ------------------------------------------------------------- Function Rate (MB/s) RMS time Min time Max time Copy: 93.0909 0.1774 0.1719 0.1797 Scale: 89.0435 0.1852 0.1797 0.1875 Add: 96.0000 0.2595 0.2500 0.2656 Triad: 93.0909 0.2618 0.2578 0.2734 IMHO this isn't too bad for a M/B which was one of the cheapest I could find, I think it cost me around AU$180 or so, and I bought it a while ago. --------------------------------------------------------------------- |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 Mar 19 17:14:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16319 for freebsd-current-outgoing; Thu, 19 Mar 1998 17:14:52 -0800 (PST) (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 RAA16313 for ; Thu, 19 Mar 1998 17:14:50 -0800 (PST) (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 BAA18826; Fri, 20 Mar 1998 01:11:14 GMT Date: Fri, 20 Mar 1998 10:11:14 +0900 (JST) From: Michael Hancock To: Poul-Henning Kamp cc: freebsd-current@FreeBSD.ORG Subject: Re: 4 WILLRELE's to bite the dust In-Reply-To: <2542.890307969@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-890356274=:18686" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---559023410-851401618-890356274=:18686 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 19 Mar 1998, Poul-Henning Kamp wrote: > >Thanks for the info, it sounds like I have more vops that share the fs > >code I touched and they need a VRELE at the top layer. Are you using NFS? > > FFS+NFS, although NFS only occasionally. The FFS must be responsible > for the problem, since NFS wasn't mounted for most of the time. I tagged through ufs_makeinode which is shared by a few vops, but I'm sure I've got all of them. Here are the diffs that Mike Smith has with vop_link and vop_rmdir dvp's done. If it's a vnode leak, then they should go away by implementing everything unless I'm vreleing the wrong thing and in that case we should get a panic in getnewvnode. Are you using ipfilter? This also makes vop calls. Did you have a chance to look at vmstat -m before the crash? Regards, Mike ---559023410-851401618-890356274=:18686 Content-Type: APPLICATION/octet-stream; name="vop1.tgz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: H4sIABPQDTUAA+09a1fbSLLzVfyK3uRs1mAMelh+ZZIZBpyMT4jNBcPkvo6P kGTQYkteSTZhdmZ/+62qbj0tgQ3EM9kbnYS2W61WdXVVdb26vfBmyv53X/Zi dbmp6+w7hpcsyqYoRSVr6LKqqEqzXsebuqp+x/QvDBdd8yA0fMa+8z0vvK/d peNuApxNXwucf/yzF36+d/xPuBRZbsC0ls5/o6HR/Gtavdms64wpilpvfMfk LwRP5vp/Pv8fjRsb5gIogBn+VcB8e2IbgeNewafxxP7sLOw9xtps6vk2Cz12 5cHXg/HYNkPbwscC5rjmZG7Zna0tCb6PTN82QnsX742mN5bjRx9dz+Ifg7vp xHFv+Jfbaye0vXnIH07q/Sk8urWVbsJujYAZE+jfumMetAs89kvv+Pi0e9yl eyEMxmXGrXHHbp3wGns13DtmepbNzGvDvbKDva2tnuuEzIDa+WxiM2MeejgG Nncdz8UhThElt4bvAhYCGDB1CM8dAWpCm6nwmkuAw7VYeG0zqAttn/2t9zdm jPGTwV7aruWMqc9xMFq4gKQ9Ezr46C1sFoT+3AzZLPTxXSHg3RsTEGziBADX NYwOqwLTmBg+QWbZi6Sfra1nnf+E/wHk8bN2HV/3839DV9SY/xuyJiP/aw3t G/9v4uq5lv25w67c+b79OVTHARUxsb15+rV1enjGxs7E7rD9eeDvm4tgP/DN /eAu2C957e5iy7dD37EXXBAtnAB5U9nT9C0kU1abs5qPX1kG2lqtlqmQlHa7 tS9r+7LCZKWjNTtaS6JeqtVqcUulweRmR1c7emPrxx9ZTWs0d5usyosff9xi EnB2JbQWM/aXN2wx24Ya6WJwMjrvHw8OP1QWs10m77LZ9ustBvJH7WzVpMVs HtIjUFlNN8Y6am66s9pb0x3NfM/EJyUY/tx3WcX2fc/Hmt+3GMHTamoIDy8I Hkn6dezbdsU1prYz+tVz7VR/7uV8TB1K0vm7s9HFu9NutxLiWx1o4Yzc+fTS BgltTUFGioYcXIK2Fn2NgM+MtRR6aRl+SYIRcMHIx9Fq0Dio4ONYaRirjiI7 iOwYVhrC8giyA2jrRBi84APYMaATY7SYzdgbBu/mJNCBWw8PrZaFcRUQlyB8 OQdmHjN21Dv96fjDWe+/oAoqHNdOquBu92L0E3zq0jAUWVFwHKKkgVgcqbgW 12qv44rxxLhiv71hvf7o8OeD/vsu3jIN89oezeb+lS2Af8RIkJvesP758TF+ 29+BP2yHDf25a4IqAUsgTCuoHUNYbj13cgdr6ByEwMQeh2IMmszHQCWNIQ1X bzi4qDiz7e1kQpCJEcLHEQc9QQ8UciqHqd3iMFFJMFETGCjR8MExvIO/Aqk2 eQvoT6AnvQpF/wgp75v9czUueUZ6lxycmIvhoCd4iYam1Il3Rfl8QmjTMkhR 9DYfCJXPJYU2KIQUpcWpjJc4AkEylagz5NqAvWJnBxfds+HB6XCbvXnD5O1V aWltZt5Jy794BDLeEzALzlASzgBuB85AdRqUfjAtPP8OlfspKGeg/RqTiUeC ABtwYUDP7H8pyeokAhBGIidVhSIwNctCm7qxfXd/7szMESg8vv2PL69ILb+x XIdSszqUyrKQohKVqRG6kbovN5iidhSto5IWpZIWVdQU1Kg6k+sd0KTqbZr0 urbbYNV6pLS8FDYj+x6BxzHtXb8tqrbswCy4NYWpxepqrtqbu2FBcyKPgnqc 8OJqsAlv8Q7CrtdJSui6vKvInF4XRhj6ewtjFN7NbJSQZ0BPr9M3UAjAjcrB 4WH37Oyke/rxDJjwX0BFs9HYqr0dWyNzagQ3RG9Ik8fdg7NuxbX2XGdEhIn/ sPWcLwh0f/TLaW/YJaKO1wV8PTx/eNo9GGY6eMU/pz6aLq4sBOP2NvDCU55H XkIYLlAUogWePFp7uxjRVOyyuI7eJ80M1zErL+bubAT2lNUBHXzGPQlxNyyY z2aeH76I38CFX7E4JMUhgpNX4NsDz7yxQ7g1R9bG1/GaLIeiVQ3zDYb2ZAO2 TsErS3m0nbVz2jrLwYpMmq1KbJ0Wk9sdvdlRFYl6Qi4taYvWThvZVFOE1lKX kVGpbIkV8XdmTwKbax8Zkvn4oT84KqYYagtXCeFI65NOTDzkSHqIcvhanwEd IT74aXA6HJwUwAwQRuqN3NaE5qaXM/y73rtBIcOfHR6cvq/MDaHXbQPXg6pH AgA+/4stSYDHCoCIGR6YiULef51j/jWffwrvT2/Gzth7mPMLLWAGtoFQQVWi U6XejOlUktCdlEUTVSfYfRCt1D6NmeNe/0MaMUskQ6T5CGqO8IFKxgrUTOTM aTrSonTCgCqrEQbWpyKWGevZf37MD/deOoCejfCaujk4O+ueDkeJctXNkNML 4fJ98STSEZ08jK1yaPLAlBvoYmiIa1VT27ttVlU1rbWrKDmJcB/jJ4v/c/I+ y/EuGPfr8e5Ds0Vu+6fNFXXx8Exh939JFnhSpSPwScqtDOqDs55qWWKzq1qL pIqqwQoQSZXHTM+aEic9m6cfc7NZNJlc7KwvdMTcUGjl4blZd/FkHKT4NtqZ 6GLJq1wb8i3n31eqbOlyRtnSZZaGMtK0so5idV/Vmax39Fan3pSoj0jNWvIo R6YQtOGOQ6CtKuoWSrRwIdrGJEdescGo++nweJuvRAv0KIKMWRjcjAfT8+KA Gpyf9S66fGVIUyg0T9FoseIgldsOqcdfRd9Qm6uJxTWuJIkC0AnCWqszvvwV 9lasG8YdZUg7rs3phwt35M1s92ENQ8pZF4UeoxKpkhrbCx7wfLHcPtc61zjD FujUGDnjPSDezfBF6oWljKE0MowBxkIGTuKMVEWBBdKQqBdijaKW3P5QGh21 yaMC5ItuRZ7ol39lHF+wMMykGjtmNajcYkmYGaRTTer1kzCwCK/S29iOhUZh FRsU1DNpcD7M3UDnFd5JnjC96QwUAjdE5YDtmG7uPq2qbAeolysL3Hhoa8kQ ovC1hDwMo6ilRhGHtp80jhWgddyQkQzB1S4ydISdk4KVjCuB7U8pOKn+6cgu efLpWFf1Oo6FF2IsqONJEsbYpGN2zs7jwZBf7/6xhGWDCZdQLm6sNBMC82qT PEq8iDEPi3IBnVP9n4/M1TaFXHghhkB6hbSEbqp+MoGXPLgO2jWZiIQXBLM0 84LAuZzwfBFmsPHcD69tn3GPYTwEYTH8SRlArCRTJzDHwT5li+xnc0a+8JJS /uZypSvrhdbVXJYLLi6ZmmTNkGnNUDtKW6J+cHUpaUrB/HqrI3PVS22Rep+E SnJ+X8M3pgX+YPgfTp/B3Ywrrz0puDHxzJvI26xxz4ZWT0yQ/Z1Pnz4x89o2 b9gY9KyEiOwwpCSlCuLS9oFctjEq8hIV97xlwe1EHqImxSWOVkcfgcji2kgZ y+pi8dMpTSyuyxoZfEZWc9aJiBYAfAmr+k0UKdJAmiMq9OYzo0KoqF8TLhSl zYOuqhxpR9H1O9vZB1oGO+3op5PTXn9YESbe/7gvtpMAWAJbLgyWQoOcGn5B yDvCUtqIlpOQt6qou4qOMCpN/JAGMrrMawPEljEKDf8K/fGZUeAgqlKRgEf1 BWaQkgUAKmZxeShy9u5mtuOOPXZ5Rw3shTuFNvgHR1/QXxpVQrYLZKFLAvV/ oJRIpoSe5aaQ9Arevb1NS0ERYtfGbIRIMTzy8wl8qu1dRUN8anX8wJMz7MXI sKwRELh/V5GynaLkmaFjzkLyxUyPs+P+B7C/Lu/IJY8pFruM/32F+CkasQUj XrgVvF17ix29gqGxLzticj92hwfD4Wllkea8fCfcpC3pOJOAE6WTJMkaz8II GbJnubXXnU8mohgBKje5+Ba9unT1VbPxJVVnWZBx9c3UpDPpVLVTb3QUjAGr PLpU3FRpMlnu4Frd4uK8TdYdL/j6i6k+bIcdgrIzsadA0pgTa0wmDKeQYxoh x363atAQhX8NbBkndKDVHc8GwqxkO2S+Q3mz0Yqwt1WFBybere0vZswJGGUE WSAjCFzmUtJNYGNGgWGGzsKmlF7fNieGM91DuPYRQHZw+v7s/Kx7RN+D0Agd E60pMaQ2unGqVHKBF4kbWhHYzpTkVIEIQkkHvWfvCHBf89wGIfRo2UJ6AwKO V7F4Gfo4OO8PhwOkdvpYmc62a29xiFOcksh3g/cvToaD48Ev3dOLE2QIIv/9 BEdvihoRKFVkI8wM53xU5c+tD0v0qqTXwihPlqdIxvO/o2B+6W+Mo5ZfXM5P 7Sw/tVkGXkqpSFUkTkRQULWOqnX0ukS9UEbFcstlL+KSLRPRGH+ak9PcjdJX smT2OT/lr/PPC+qdT6GJmNXzfm/Qj6eVUhCgybURXFOcQHyO82Xg+wIdDtEX WK3ER+kG9V3b4kZZS6OIMxZLYazYj+nuxaI/5z0vDIaISB06Hk2XIh8FsYys 5racokBouAmuDcu7fdhZXpqw29b1KE80CSZzr24USz7tvn+dqhYBJRPLbIBo 7mIywwhUu3sdvCXu3ezTrxYReiI37pqPLGM03TqF2nR1AY4XrvDlPTkbJEcL g5Nun5SJsUiwJGSl0rQK+HyzBnPBm8sN5uySressC3EiY5YiFbGQQXesrqeE TJHBTLa1ypdsVSbi5UVayqA6xHZQgKQVpIjXkb/BmMb1PGkQJSKiqnVycNrt D9eUOmmG3U4p9hRWYzuBsbAtEhKvEyNi6V5aPjlB5H5Ni0hyrCyMyPDSZYrX YBHxrwSk+U4kFMI3Qd9xhOa8P/pwLPLBpCniaNlUfL22Lj1bjhUKJrVi3nzY aJ3OUqIuy4erMSFbipossyGhTaH0eF1JMmsLk1nXVMqzOdfd08G7s7Sw1Rt1 mqxG4083WTzF5pnmatUcqNWmqkn5uHpL3eRUKUpd3lV4Dg9Yt23x5ghl1P51 nM4cZ8BnZyIsn4owNxfFQ2LSu96n8xNYuqKGRC5hRC/l5FIrhOMBMHJpW5Rt E8Z5RaY7W07NKmizvPKGWWUmLNZmVkmeKUu8yhk+itpo76oy+iaajWT27uWu 9bgl1uOKuaUmLdGFMFFyPLqS0pfnrhXyI6oPcldNEiQWj4x3T+nsi1nsTZvt FsicVJ1IpuSaukAF4iSqUMT2gqXRLwuA9MaVjTC5pvCdOZqSbBXhHGclLJcT 0dZ9TPcoOZzncf7Ch5cEMYQ2Jdppqh67oRGtfDLBOBA6BPWfdVNlnEd8BrLa ELztaPDLz6C4D86HJblAMevHDqlHE/ZqiT8voWeZO9vJ4UK+iEymFseLyjfP aFqyAy5L6NObGDc09mWVjj7i7iyY8+1EueMUH9EBgGb7GQTENoVI0nskWSz7 tBO61Vvc9aqhKqFnKLeUcJ+dbouSM8tkYvSRO9YfTSIr51guO1u5G+FLi5XI dgssLwATSpQbM9yKX1tqtTWyVltDZ3mA0W7L1SXOVjLH6o2Ohqn8DW65lTUW wc5GFOxUWk1OwrzkFHzlhR67NKwo9/J5t4mtOLv3++2PuiQQ7CwN8P1jCPpa +2kfC1GpO0dVSFnmhdhvZ9ljYz6hPOICyHJxhNwmzWcKpVS6vf7FwXHEbii6 +4Mh2IeHP3PPNbmiVFqMeUH0QKHDHYP7o1kmyzOtvqZXnnX13vvDKN3BCcB5 dn5yktYa6hrPTOLlvwXl8nHV+V5rXvJ9ypN5ENo+wTlDi8+1b0Ud1/DwaRi2 +seSvVJvC9Dj6A1u2sQNmZSgQsEVCqBM7BDPTPHGdFN4gZJdnZad3b+5if3j 2X2l4bWBrh92aaOstuhQF2uPj1KXubrKy6WN5IvoWIfNbCHXVQFNzLD/LCSC YglDQmCZo/MMzX744QeciucMjlYSts4t264dOvB/fzoZj5zZ5Msv2EsvLI/h ZEM4LAGRlujoW7Ibto5uVU3mizNPQ8q3SsdtFJH6RzthsYiMiXgniW/ZC9xJ Aj2MpsbfQfX7/nvW2ma/MSc2oJe2IphzH9Eff1h1o8Ejtnw9fseBM0O0jCae 8XivFdXw9W2JmNxNE5O7NjG5GWJyM2Si7GsKk1XcTaBrKWJyHyImnWJnWLRy u5IELcWk9P33rWws6XEk9AdtGlydeApDRBHpCA5UchxYzoCAte3flG+IEym/ fHdUu7Ei4tRviEulC0VCC5N0cDe27S82ILEybysPLraywcUWS4FIyUDx12T9 azO50VFg/dMl6oEygfLt4pii3pEbQpXUKQ2XynjvLvde8rnAE9lCUNj4aiC5 /wj8xejKDifpqe8fZTbtPuoog/ItR6tvR4cRA3QrB8/SfjSxpR6zHyXejXf5 d3hc9JbeCEke4GXNLx7LXkrx40hu6VxfbyV5B9FW/q3M3rKIdzGxMNzGbyui vWgn2aocSjkHlAP1OK1k0zOX3S0mJu4+osUJnY58eza54xYgbeGmqWk0GkT/ DViIYh2wtKdVqP9pxP9orY4jcJ1YZGqr76rUnNqHyrHXpMCy0mjVU4RN3gER yOcptKuQ7zNQ75OIdxOYrxYQ7j10m0MkTwJp830TipwI7BR6l+kxdfPzvcS6 yukKT0TSat7s59jrHItrjjVAG2FNVWM2R8JcgZ8fdyYDxQAwIGIWRYhX13w4 2laOA2TVn1LKSrGwqvHToNTUxo5HYGbVcw+Kc9XWxcf65xlwYlo6oEi6/NX2 vUrFNCzLhwV3fA3wBs6vtjeuuOPrbbGAq3VADiKpnvIUrLIW3MuYmz5pgONu g+cNJDyYU7c3FB/Kva5U4W4pGYW7pTA3FxNyi+JB0cZqHc8cgD4ilbs4FqS1 Oqocbc1RdhWVtubQB5Hmw1U/+fNYXClOzU2ClSSfPO0ow6xrkB8ymVuG34uN ICLUyY+auS+y/gXBzR6HCbjGRJhgz5+Zphv+d//d2cnp4JCv/P9brQrlW22q fK9WM06puhgOoDEBUXvrxgcJ9j8Ojnrvet2jWHjcmibe5OcKZx9CRMDrKUtN fp4jY5OAt9YQ0fzGbuYgya9jYhDS/GEZrzJnZYishbrMsxZ4+VVMTaNFqadV +tBKz01KBONp1JkssALcZ1AfH2MtTmlJEqjCKA5DoiA5fzVJtssfgZ07k7X8 WOtECnw66l5kUy6aPGMUyjjZOMJyMZLLZyW8f1rWO4o7Cid9mMytK5D5H40Z 63Y/9c6G7M1bJjMjCOZTFO88sESxJYOR5Ue7mXAfk38XRbz4UFtiqC39z0WE X2CsLZWf9tpSv0rBMrHdVA47WqtQI8R8ix9XorTicxxSDpZMZNi1b7n2t5mD wGOeaqs8kN5WlaJ4ZpS5tBzjXN41+WQy6g+6/UIyuvPm7NrA/XellCSUuTnu meD/N6XQFbyyVKlrZneBNdvp3//gGzTKlbp2p457wJpiD1iRUtfEHzGQ5Y6u 0ew2dQoP8wLnlv/eAMiS/uhkcHzcvQCEk9DHb300I2l2Mre53MPviV/kYSFZ GreOtAmxymrJKvt1/kyBoqlclePl1/hDBUUqz+8b/mWCJI1ErHy8jE3/kiSL R7z6Adq/L+2C+7ooUbkqyn+nY/tVWRVDi1fil84YfzDiP84HwwPsLLNpSsTj duYm91tAmVoJ+T6rGqcz4KTeVjU5uYLkPy4AvTG7Bbnu28z1QsrD8W5d24+y g+KknF3RHhOIxAPXhnlDe7/xgYBd2z7grEIbvi0PngbN4xYrYbWYWPBHeN3k hsoH2VCfVfJsWvCoclNsvWvqzyh4Nih3yF2sNIXfWPkKfp0gyi6N1JdffCe0 xTZ3zzTnPrIFaCWkuXhsPrMyP0oA4Kz/OwZVemb8Z/vtA3s8Lvj5g9V+EeGP /kmrb9e369v17fp2rXD9H93r180AeAAA ---559023410-851401618-890356274=:18686-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 17:19:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17187 for freebsd-current-outgoing; Thu, 19 Mar 1998 17:19:26 -0800 (PST) (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 RAA17156 for ; Thu, 19 Mar 1998 17:19:20 -0800 (PST) (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 BAA18856; Fri, 20 Mar 1998 01:17:26 GMT Date: Fri, 20 Mar 1998 10:17:25 +0900 (JST) From: Michael Hancock To: Amancio Hasty cc: Wm Brian McCane , current@FreeBSD.ORG Subject: Re: soft updates In-Reply-To: <199803200026.QAA02957@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 Thu, 19 Mar 1998, Amancio Hasty wrote: > And softupdates is not ready for prime time. Unless you are an experienced enough fs developer/tester, then we would be happy to have your input. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 18:38:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01080 for freebsd-current-outgoing; Thu, 19 Mar 1998 18:38:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (garbanzo@ghana-160.ppp.hooked.net [206.169.228.160]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01068 for ; Thu, 19 Mar 1998 18:38:13 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id SAA00352; Thu, 19 Mar 1998 18:39:34 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 19 Mar 1998 18:39:33 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org Reply-To: Alex To: "Daniel O'Connor" cc: current@FreeBSD.ORG Subject: Re: More wank^H^H^H^Hspeed tests In-Reply-To: <199803200100.LAA24874@cain.gsoft.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 20 Mar 1998, Daniel O'Connor wrote: > This is my 6x86/P166+ with an rev > 0x02 on pci0.0.0. > > stream_d was compiled with gcc -o stream_d stream_d.c second_cpu.c > -malign-double -O3 -lm [...] > Your clock granularity/precision appears to be 7812 microseconds. > Each test below will take on the order of 164062 microseconds. > (= 21 clock ticks) > Increase the size of the arrays if this shows that > you are not getting at least 20 clock ticks per test. [...] > Function Rate (MB/s) RMS time Min time Max time > Copy: 93.0909 0.1774 0.1719 0.1797 > Scale: 89.0435 0.1852 0.1797 0.1875 > Add: 96.0000 0.2595 0.2500 0.2656 > Triad: 93.0909 0.2618 0.2578 0.2734 > > IMHO this isn't too bad for a M/B which was one of the cheapest I could find, > I think it cost me around AU$180 or so, and I bought it a while ago. ------------------------------------------------------------- This system uses 8 bytes per DOUBLE PRECISION word. ------------------------------------------------------------- Array size = 1000000, Offset = 0 Total memory required = 22.9 MB. Each test is run 10 times, but only the *best* time for each is used. ------------------------------------------------------------- Your clock granularity/precision appears to be 7812 microseconds. Each test below will take on the order of 117187 microseconds. (= 15 clock ticks) Increase the size of the arrays if this shows that you are not getting at least 20 clock ticks per test. [...] ------------------------------------------------------------- Function Rate (MB/s) RMS time Min time Max time Copy: 93.0909 0.1838 0.1719 0.1953 Scale: 113.7778 0.1469 0.1406 0.1484 Add: 122.8800 0.2024 0.1953 0.2031 Triad: 118.1538 0.2031 0.2031 0.2031 This was with my p180 (60mhz*3) after some tweaking with the memory timing settings using 60ns EDO ram. No cache controller shows up upon bootup, and I used an oldish pgcc w/ -O9 (cc -O3 were about 20MB/s slower). I'm not even sure who makes my motherboard, tis very generic with even cheaper RAM used in the second bank. - alex A person who has both feet planted firmly in the air can be safely called a liberal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 18:38:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01192 for freebsd-current-outgoing; Thu, 19 Mar 1998 18:38:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (garbanzo@ghana-160.ppp.hooked.net [206.169.228.160]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01183 for ; Thu, 19 Mar 1998 18:38:54 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id SAA00373 for ; Thu, 19 Mar 1998 18:41:00 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 19 Mar 1998 18:41:00 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: current Subject: Re: More wank^H^H^H^Hspeed tests 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, 19 Mar 1998, Alex wrote: > This was with my p180 (60mhz*3) after some tweaking with the memory timing > settings using 60ns EDO ram. No cache controller shows up upon bootup, > and I used an oldish pgcc w/ -O9 (cc -O3 were about 20MB/s slower). I'm > not even sure who makes my motherboard, tis very generic with even > cheaper RAM used in the second bank. Whoops, that slowdown was due to the -static option. - alex A person who has both feet planted firmly in the air can be safely called a liberal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 20:37:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19199 for freebsd-current-outgoing; Thu, 19 Mar 1998 20:37:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19190 for ; Thu, 19 Mar 1998 20:37:22 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id UAA00718; Thu, 19 Mar 1998 20:37:18 -0800 (PST) (envelope-from jdp) Message-Id: <199803200437.UAA00718@austin.polstra.com> To: hetzels@westbend.net Subject: Re: Line for cvsup users on current to grab safe sources In-Reply-To: <020c01bd535f$0bf8dfa0$c3e0d9cf@admin.westbend.net> References: <020c01bd535f$0bf8dfa0$c3e0d9cf@admin.westbend.net> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 19 Mar 1998 20:37:18 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <020c01bd535f$0bf8dfa0$c3e0d9cf@admin.westbend.net>, Scot W. Hetzel wrote: > How about just adding: > > *default date=98.03.12.00.00.00 > src-sys > > to the end of the cvsupfile. That way you get current src's for most of the > tree, and March 12 src's for the kernel. That will work fine. Or, you can do it all on one line: src-sys date=98.03.12.00.00.00 John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 21:11:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22648 for freebsd-current-outgoing; Thu, 19 Mar 1998 21:11:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22642 for ; Thu, 19 Mar 1998 21:11:10 -0800 (PST) (envelope-from andrew@zeta.org.au) Received: from gurney.reilly.home (d14.syd2.zeta.org.au [203.26.11.14]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id QAA04697; Fri, 20 Mar 1998 16:08:08 +1100 Received: (from andrew@localhost) by gurney.reilly.home (8.8.8/8.8.5) id HAA08094; Fri, 20 Mar 1998 07:59:03 +1100 (EST) From: Andrew Reilly Message-Id: <199803192059.HAA08094@gurney.reilly.home> Date: Fri, 20 Mar 1998 07:59:02 +1100 (EST) Subject: Re: Stream_d benchmark... Wow, there really are differences in har dware To: hasty@rah.star-gate.com cc: lamaster@george.arc.nasa.gov, freebsd-current@FreeBSD.ORG In-Reply-To: <199803191010.CAA21492@rah.star-gate.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19 Mar, Amancio Hasty wrote: > Function Rate (MB/s) RMS time Min time Max time > Copy: 113.7778 0.1557 0.1406 0.1719 > Scale: 107.7895 0.1565 0.1484 0.1719 > Add: 118.1538 0.2158 0.2031 0.2344 > Triad: 118.1538 0.2213 0.2031 0.2344 >> Soeren Schmidt (sos@FreeBSD.org) wrote: >> > Function Rate (MB/s) RMS time Min time Max time >> > Copy: 117.0286 0.2758 0.2734 0.2812 >> : >> > Triad: 125.3878 0.3917 0.3828 0.4219 >> > > Box 1 is a SuperMicro P6DNE: >> > > Function Rate (MB/s) RMS time Min time Max time >> > > Copy: 60.7395 0.2704 0.2634 0.2832 >> > > Triad: 71.1647 0.3494 0.3372 0.3565 >> >> Typical for Natoma with FP DRAM I would guess. I have to say that these are all really terrible numbers! Does anyone know what the DRAM controller on these motherboards is doing? Posit: A Pentium or Pentium pro memory system is 64 bits wide (8 bytes), clocked at 66MHz, or 15ns/cycle. EDO dram shouldn't have trouble doing four cycle bursts as 4-1-1-1, or perhaps 5-1-1-1: say 120ns/cache line of 32 bytes. That's 265M/s in my book. I assume that the benchmark code for stream is small, sits in the internal cache, and just thrashes through long vectors, which should result in back-to-back cache reads (and writes?) Does anyone know where that factor of two is going? Maybe PC's only get EDO to do -2-2-2? Do any PC chipsets notice sequential address blocks and avoid the unnecessary row address cycles? Seemingly not... -- Andrew "The steady state of disks is full." -- Ken Thompson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Mar 19 22:41:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06956 for freebsd-current-outgoing; Thu, 19 Mar 1998 22:41:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06945 for ; Thu, 19 Mar 1998 22:40:55 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA08667; Fri, 20 Mar 1998 17:39:57 +1100 Date: Fri, 20 Mar 1998 17:39:57 +1100 From: Bruce Evans Message-Id: <199803200639.RAA08667@godzilla.zeta.org.au> To: hasty@rah.star-gate.com, reilly@zeta.org.au Subject: Re: Stream_d benchmark... Wow, there really are differences in har dware Cc: freebsd-current@FreeBSD.ORG, lamaster@george.arc.nasa.gov Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> > > Box 1 is a SuperMicro P6DNE: >>> > > Function Rate (MB/s) RMS time Min time Max time >>> > > Copy: 60.7395 0.2704 0.2634 0.2832 >>> > > Triad: 71.1647 0.3494 0.3372 0.3565 >>> >>> Typical for Natoma with FP DRAM I would guess. > >I have to say that these are all really terrible numbers! Does anyone >know what the DRAM controller on these motherboards is doing? Pentium Pros and K6's normally use write allocation. This reduces write bandwith by a factor of 2 and thrashes the L2 cache to get no benefits in the stream benchmark. 60MB/sec for `copy' is still very bad. Assuming a typical main memory bandwidth of about 180MB/sec and no other penalties, 60MB/sec would be used for reading, 60MB/sec for write allocation and 60MB/sec for writing. The stream benchmark would report this as 120MB/sec. Ignore half of what I said in other mail about -malign-double being important. It is important for P5's but not for CPUs with write allocation. I get the following speeds for copying: P5/133 ASUS Triton 1 non-EDO: stream, misaligned doubles: 85MB/s (1) P5/133 ASUS Triton 1 non-EDO: stream, aligned doubles: 78MB/s (2) P5/133 ASUS Triton 1 non-EDO: kernel bcopy (3): 156MB/s (4) K6/233 FIC PA2007 SDRAM: stream, misaligned doubles: 99MB/s K6/233 FIC PA2007 SDRAM: stream, aligned doubles: 98MB/s K6/233 FIC PA2007 SDRAM: best bcopy (5): 98MB/s (4) (6) (1) 1MB is 1000000 bytes. (2) Yes, aligned copying is slower. Alignment makes all the other stream benchmarks significantly faster. The slowdown is probably caused by the penalty for accessing a cache line that is being loaded. (3) A slightly optimized version of FreeBSD's kernel bcopy, running in user space. It copies through the FPU in a similar way to the stream benchmark but is careful to avoid the P5 cache access and memory system penalties. The "non-EDO" RAM is FastPage IIRC. It has access cycles of x-3-3-3 (read) and (x-2-2-2) write at 66 MHz. 4K at a time is first read into the L1 cache at 3-3-3-3; then it is written at not quite 3-3-3-3 (2-2-2-2 is not possible on a P5/133, since the very slow `fistpq' instruction must be used for writing, and it takes 6 cycles (6 * 66 / 133 = 3 bus cycles). Speeds of more than 160MB/sec have been reported for slighyly faster systems with EDO RAM. On i386's, gcc generates `fstl' for the corresponding part of the copy in the stream benchmark. `fstl' is much faster than `fistpq', so it is possible for a stream-like benchmark to saturate the bus with this h/w configuration. Going back an forth like the stream copy benchmark actually does is the second worst reasonable way to copy on P5's. The h/w `rep movsl' is the worst :-). (4) Translated to stream benchmark units (2 * bytes/sec copied). (5) `rep movsl' is the best. (6) After multipying by 3/2 to allow for write allocation, the K6/233 system is still slightly slower at copying than the P5/133 system, although it has SDRAM instead of nondescript RAM. The SDRAM seems to be only 1 bus cycle per burst faster in practice (11 instead of 12). K6's apparently have worse cache access penalties than P5. The P5 trick of reading ahead doesn't help on K6's. >Posit: > >A Pentium or Pentium pro memory system is 64 bits wide (8 bytes), >clocked at 66MHz, or 15ns/cycle. EDO dram shouldn't have trouble doing >four cycle bursts as 4-1-1-1, or perhaps 5-1-1-1: say 120ns/cache line >of 32 bytes. That's 265M/s in my book. I assume that the benchmark Most memory systems are not that fast. I believe 5-2-2-2 is the best possible for EDO (except the `5' in it can probably be reduced for sequential accesses). SDRAM can do 5-1-1-1, but I haven't seen that. >code for stream is small, sits in the internal cache, and just thrashes >through long vectors, which should result in back-to-back cache reads >(and writes?) Does anyone know where that factor of two is going? >Maybe PC's only get EDO to do -2-2-2? It's a factor of 4 for the system that gets only 60MB/sec for the stream copy benchmark :-]. >Do any PC chipsets notice sequential address blocks and avoid the >unnecessary row address cycles? Seemingly not... Even Triton 1 does something good for sequential accesses, but the stream benchmark defeats sequentiality by going back and forth to read and write. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 02:06:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00366 for freebsd-current-outgoing; Fri, 20 Mar 1998 02:06:11 -0800 (PST) (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 CAA00347 for ; Fri, 20 Mar 1998 02:06:03 -0800 (PST) (envelope-from osa@unibest.ru) Received: (qmail 24046 invoked from network); 20 Mar 1998 10:05:56 -0000 Received: from unknown (HELO hole.etrust.ru) (200.1.6.2) by serv.unibest.ru with SMTP; 20 Mar 1998 10:05:56 -0000 Date: Fri, 20 Mar 1998 13:07:12 +0300 (MSK) From: Ozz!!! X-Sender: osa@hole.etrust.ru To: freebsd-current@FreeBSD.ORG Subject: Some stranges in -CURRENT ??? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All! I have some stranges in -CURRENT... After work in XFree86-3.3.2 with fvwm95, I shutdown X-server. In command prompt : # who osa ttyv0 20 ÍÁÒ 12:58 osa ttyp0 19 ÍÁÒ 17:48 (:0.0) osa ttyp1 19 ÍÁÒ 17:48 (:0.0) osa ttyp2 19 ÍÁÒ 17:48 (:0.0) osa ttyp3 19 ÍÁÒ 17:48 (:0.0) Hmmm... Then say : # w 12:59ÐÐ up 19:11, 5 users, load averages: 0.01, 0.02, 0.00 USER TTY FROM LOGIN@ IDLE WHAT osa v0 - 12:58ÐÐ - - osa p0 :0.0 ÞÔ 05ÐÐ 9days - osa p1 :0.0 ÞÔ 05ÐÐ 13days - osa p2 :0.0 ÞÔ 05ÐÐ 13days - osa p3 :0.0 ÞÔ 05ÐÐ 13days - Hmmmm.......... I think its too strange ... 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 Mar 20 05:59:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28152 for freebsd-current-outgoing; Fri, 20 Mar 1998 05:59:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28138 for ; Fri, 20 Mar 1998 05:59:15 -0800 (PST) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.8.8/8.8.8) id HAA26566; Fri, 20 Mar 1998 07:59:03 -0600 (CST) (envelope-from bob) Message-ID: <19980320075903.61829@pmr.com> Date: Fri, 20 Mar 1998 07:59:03 -0600 From: Bob Willcox To: "Daniel O'Connor" , current@FreeBSD.ORG Subject: Re: More wank^H^H^H^Hspeed tests Reply-To: Bob Willcox References: <199803200100.LAA24874@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803200100.LAA24874@cain.gsoft.com.au>; from Daniel O'Connor on Fri, Mar 20, 1998 at 11:30:51AM +1030 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Where can I get a copy of stream_d? Thanks, -- Bob Willcox The husband who doesn't tell his wife everything bob@luke.pmr.com probably reasons that what she doesn't know won't Austin, TX hurt him. -- Leo J. Burke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 08:07:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15541 for freebsd-current-outgoing; Fri, 20 Mar 1998 08:07:28 -0800 (PST) (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 IAA15526 for ; Fri, 20 Mar 1998 08:07:17 -0800 (PST) (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 LAA04901 for ; Fri, 20 Mar 1998 11:04:21 -0500 (EST) X-Sender: ckempfm@enigami.com Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 20 Mar 1998 10:57:30 -0500 To: freebsd-current@FreeBSD.ORG From: Cory Kempf Subject: Pathetic FTP performance Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am getting really pathetic FTP performance across my LAN. From any machine to any other machine, I am seeing several hundred k / sec via FTP. E.g. from my Mac to my SGI, I see between 300k/s - 1M/s, depending on file size. However, when I am running FreeBSD (-Current as of 12 March), I am getting really pathetic performance... on the order of 0-2 k / second. The network is 10baseT, My ethernet is the intel EtherExpress Pro 10/100B rev 0x02 that is built into the DK440LX motherboard. The net is almost completely unloaded, so it isn't traffic. Running ping generally has a transit time of just under 1 ms, although I am seeing 4% packet loss (2 packets out of 40). Generally, what I am seeing is both low transfer rates as well as *LOTS* of stalling. Any suggestions what is causing this, and how to diagnose / fix it? 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 Fri Mar 20 08:32:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21050 for freebsd-current-outgoing; Fri, 20 Mar 1998 08:32:37 -0800 (PST) (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 IAA21044 for ; Fri, 20 Mar 1998 08:32:34 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id KAA00555; Fri, 20 Mar 1998 10:31:41 -0600 (CST) From: Kevin Day Message-Id: <199803201631.KAA00555@home.dragondata.com> Subject: Re: Pathetic FTP performance In-Reply-To: from Cory Kempf at "Mar 20, 98 10:57:30 am" To: ckempf@enigami.com (Cory Kempf) Date: Fri, 20 Mar 1998 10:31:40 -0600 (CST) Cc: freebsd-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 am getting really pathetic FTP performance across my LAN. From any > machine to any other machine, I am seeing several hundred k / sec via FTP. > E.g. from my Mac to my SGI, I see between 300k/s - 1M/s, depending on file > size. > > However, when I am running FreeBSD (-Current as of 12 March), I am getting > really pathetic performance... on the order of 0-2 k / second. > > The network is 10baseT, My ethernet is the intel EtherExpress Pro 10/100B > rev 0x02 that is built into the DK440LX motherboard. The net is almost > completely unloaded, so it isn't traffic. > > Running ping generally has a transit time of just under 1 ms, although I am > seeing 4% packet loss (2 packets out of 40). > > Generally, what I am seeing is both low transfer rates as well as *LOTS* of > stalling. > > Any suggestions what is causing this, and how to diagnose / fix it? > > Thanks, > > +C > > I saw something similar when I upgraded from a 2.1 kernel to 2.2.5 here... What I see now is a *flood* of traffic (putting the ethernet at 100%) with nearily 50% collisions, then a long stall, then it picks back up, and flood the ethernet again. With a 2.1 kernel I saw a nice steady stream... I've been unable to find what change prompted this. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 08:47:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25402 for freebsd-current-outgoing; Fri, 20 Mar 1998 08:47:43 -0800 (PST) (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 IAA25350 for ; Fri, 20 Mar 1998 08:47:37 -0800 (PST) (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 LAA17720 for ; Fri, 20 Mar 1998 11:44:42 -0500 (EST) Date: Fri, 20 Mar 1998 11:47:33 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: current@FreeBSD.ORG Subject: Current status? 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 current still trashed? I saw johns last commit about an embarrasing bug, and thought that might be the fix to the invisible run current and nuke your FS problem. But nothing has been said about that fix, or if current is still hosed. I don't want to start up another flood of "current is trashed / mine is running fine" posts, but a simple {yes|no} to wether the FS problem is fixed yet is all im looking for. And to throw out a thanks to Karl for finding this hooha of a bug and being VOCAL about it and what it is doing to your current machine, and john for being the slave to the VM system he is :) and doing his best to fix the bug. Thanks to both of you. Chris -- "I am closed minded. It keeps the rain out." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.5 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 Fri Mar 20 09:22:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04644 for freebsd-current-outgoing; Fri, 20 Mar 1998 09:22:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA04567 for ; Fri, 20 Mar 1998 09:22:13 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0yG5UR-00053V-00; Fri, 20 Mar 1998 10:21:55 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id KAA00713; Fri, 20 Mar 1998 10:21:50 -0700 (MST) Message-Id: <199803201721.KAA00713@harmony.village.org> To: Kevin Day Subject: Re: Pathetic FTP performance Cc: ckempf@enigami.com (Cory Kempf), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 20 Mar 1998 10:31:40 CST." <199803201631.KAA00555@home.dragondata.com> References: <199803201631.KAA00555@home.dragondata.com> Date: Fri, 20 Mar 1998 10:21:50 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199803201631.KAA00555@home.dragondata.com> Kevin Day writes: : With a 2.1 kernel I saw a nice steady stream... I've been unable to find : what change prompted this. :) I'm seeing something that is similar that I've not had time to track down. When I connect via lynx or netscape to certain sites (www.onsale.com is one), I get 300-odd bytes and then nothing else for the life of the conenction. I'm seeing this on a early Feb 2.2 as well as a Julyish -current system. Yes, tcp extentions are turned off on both of these systems. The S4000 running OS/MP on the same subnet can get to these sites with lynx no problems. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 09:39:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08740 for freebsd-current-outgoing; Fri, 20 Mar 1998 09:39:12 -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 JAA08704; Fri, 20 Mar 1998 09:39:03 -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 LAA02064; Fri, 20 Mar 1998 11:38:59 -0600 (CST) Message-ID: <19980320113849.20091@arh0300.urh.uiuc.edu> Date: Fri, 20 Mar 1998 11:38:49 -0600 From: dannyman To: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: apologies for mail loop Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i 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 hello, for about two hours this morning, i had a bad bad bad bad majordomo recipe which was causing every piece of mail I received to be auto-responded to. i would like to apologise for any crap spewed upon the lists because of this. i feel pretty dumb. sorry everyone. -dan -- //Dan -=- This message brought to you by djhoward@uiuc.edu -=- \\/yori -=- Information - http://www.uiuc.edu/ph/www/djhoward/ -=- aiokomete -=- Our Honored Symbol deserves an Honorable Retirement To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 09:44:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10321 for freebsd-current-outgoing; Fri, 20 Mar 1998 09:44:22 -0800 (PST) (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 JAA10300 for ; Fri, 20 Mar 1998 09:44:17 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id LAA03666; Fri, 20 Mar 1998 11:44:12 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id LAA04153; Fri, 20 Mar 1998 11:44:12 -0600 (CST) Message-ID: <19980320114412.42502@mcs.net> Date: Fri, 20 Mar 1998 11:44:12 -0600 From: Karl Denninger To: Open Systems Networking Cc: current@FreeBSD.ORG Subject: Re: Current status? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Open Systems Networking on Fri, Mar 20, 1998 at 11:47:33AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 20, 1998 at 11:47:33AM -0500, Open Systems Networking wrote: > > Is current still trashed? I saw johns last commit about an embarrasing > bug, and thought that might be the fix to the invisible run current and > nuke your FS problem. But nothing has been said about that fix, or if > current is still hosed. I don't want to start up another flood of "current > is trashed / mine is running fine" posts, but a simple {yes|no} to wether > the FS problem is fixed yet is all im looking for. And to throw out a > thanks to Karl for finding this hooha of a bug and being VOCAL about it > and what it is doing to your current machine, and john for being the slave > to the VM system he is :) and doing his best to fix the bug. Thanks to > both of you. > > Chris I have completed my first-level regression testing, and it look ok now. MAKE CERTAIN you have the commits from last night however - they were the ones which make it appear, at least, to be "ok". I'm not 100% solid on this yet, and was intending to wait until the weekend was over to say "yes, its ok now" for certain. My confidence level in -CURRENT right now, at least as far as the problem with destroying filesystems goes, is about 90%. However, note that I got a distinctly evil hard lockup with it a while back (ie: no DDB trap possible, etc). No idea what caused it yet, but I'm trying to reproduce that now. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 10:00:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13379 for freebsd-current-outgoing; Fri, 20 Mar 1998 10:00:08 -0800 (PST) (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 KAA13369 for ; Fri, 20 Mar 1998 10:00:04 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id JAA07245; Fri, 20 Mar 1998 09:59:42 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803201759.JAA07245@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Open Systems Networking cc: current@FreeBSD.ORG Subject: Re: Current status? In-reply-to: Your message of "Fri, 20 Mar 1998 11:47:33 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Mar 1998 09:59:41 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try to stay away from -current for at least a couple of more days . We have to give Karl and John breathing room to really test the system for at least a couple of days. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 10:01:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13533 for freebsd-current-outgoing; Fri, 20 Mar 1998 10:01:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from george.arc.nasa.gov (george.arc.nasa.gov [128.102.194.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13517 for ; Fri, 20 Mar 1998 10:01:10 -0800 (PST) (envelope-from lamaster@george.arc.nasa.gov) Received: (from lamaster@localhost) by george.arc.nasa.gov (8.8.7/8.8.7) id JAA18761 for freebsd-current@freebsd.org; Fri, 20 Mar 1998 09:56:13 -0800 (PST) From: Hugh LaMaster Message-Id: <199803201756.JAA18761@george.arc.nasa.gov> Subject: Re: More wank^H^H^H^Hspeed tests To: freebsd-current@FreeBSD.ORG Date: Fri, 20 Mar 1998 09:56:12 -0800 (PST) In-Reply-To: <19980320075903.61829@pmr.com> from "Bob Willcox" at Mar 20, 98 07:59:03 am X-Mailer: ELM [version 2.4 PL24] 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 Bob Willcox (bob@luke.pmr.com) wrote: > Where can I get a copy of stream_d? http://www.cs.virginia.edu/stream To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 10:12:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16907 for freebsd-current-outgoing; Fri, 20 Mar 1998 10:12:23 -0800 (PST) (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 KAA16872 for ; Fri, 20 Mar 1998 10:12:13 -0800 (PST) (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 KAA29995; Fri, 20 Mar 1998 10:08:26 -0800 (PST) Message-Id: <199803201808.KAA29995@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: Open Systems Networking , current@FreeBSD.ORG Subject: Re: Current status? In-reply-to: Your message of "Fri, 20 Mar 1998 09:59:41 PST." <199803201759.JAA07245@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Mar 1998 10:08:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Try to stay away from -current for at least a couple of more days . > We have to give Karl and John breathing room to really test the system > for at least a couple of days. I'd just like to take a moment to publically thank Karl for participating so closely in this testing cycle. I think it would be fair to say that his complaints over the last years have not necessarily endeared him to a great number of people, but it would be extremely remiss of us not to appreciate these more recent efforts. Without any fear of contradiction, I can say that we would be overjoyed to see more of this. Participation and testing at this level is a most valuable service. Thanks Karl! -- \\ 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 Mar 20 10:23:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19493 for freebsd-current-outgoing; Fri, 20 Mar 1998 10:23:10 -0800 (PST) (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 KAA19483 for ; Fri, 20 Mar 1998 10:23:07 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id MAA05980; Fri, 20 Mar 1998 12:22:59 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id MAA04876; Fri, 20 Mar 1998 12:22:59 -0600 (CST) Message-ID: <19980320122259.30056@mcs.net> Date: Fri, 20 Mar 1998 12:22:59 -0600 From: Karl Denninger To: Mike Smith Cc: Amancio Hasty , Open Systems Networking , current@FreeBSD.ORG Subject: Re: Current status? References: <199803201759.JAA07245@rah.star-gate.com> <199803201808.KAA29995@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199803201808.KAA29995@dingo.cdrom.com>; from Mike Smith on Fri, Mar 20, 1998 at 10:08:24AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 20, 1998 at 10:08:24AM -0800, Mike Smith wrote: > > Try to stay away from -current for at least a couple of more days . > > We have to give Karl and John breathing room to really test the system > > for at least a couple of days. > > I'd just like to take a moment to publically thank Karl for > participating so closely in this testing cycle. I think it would be > fair to say that his complaints over the last years have not necessarily > endeared him to a great number of people, but it would be extremely > remiss of us not to appreciate these more recent efforts. > > Without any fear of contradiction, I can say that we would be overjoyed > to see more of this. Participation and testing at this level is a most > valuable service. > > Thanks Karl! You're welcome. I just call 'em like I see 'em. Sometimes that makes people happy, and sometimes it makes people pissed. :-) It comes with how I live my life. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 10:29:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20712 for freebsd-current-outgoing; Fri, 20 Mar 1998 10:29:33 -0800 (PST) (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 KAA20705 for ; Fri, 20 Mar 1998 10:29:31 -0800 (PST) (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 KAA04554; Fri, 20 Mar 1998 10:29:23 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Mike Smith cc: Amancio Hasty , Open Systems Networking , current@FreeBSD.ORG Subject: Re: Current status? In-reply-to: Your message of "Fri, 20 Mar 1998 10:08:24 PST." <199803201808.KAA29995@dingo.cdrom.com> Date: Fri, 20 Mar 1998 10:29:23 -0800 Message-ID: <4547.890418563@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Without any fear of contradiction, I can say that we would be overjoyed > to see more of this. Participation and testing at this level is a most > valuable service. I wasn't sure that I should say anything given my own history with the man, but I can certainly echo these sentiments. The work that Karl is doing is of benefit to us all and greatly appreciated, whatever might have happened in the past. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 10:31:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21284 for freebsd-current-outgoing; Fri, 20 Mar 1998 10:31:21 -0800 (PST) (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 KAA21257 for ; Fri, 20 Mar 1998 10:31:17 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id KAA07618; Fri, 20 Mar 1998 10:28:05 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803201828.KAA07618@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Karl Denninger cc: Mike Smith , Open Systems Networking , current@FreeBSD.ORG Subject: Re: Current status? In-reply-to: Your message of "Fri, 20 Mar 1998 12:22:59 CST." <19980320122259.30056@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Mar 1998 10:28:05 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tnks Karl ! Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 10:38:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23691 for freebsd-current-outgoing; Fri, 20 Mar 1998 10:38:25 -0800 (PST) (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 KAA23686 for ; Fri, 20 Mar 1998 10:38:23 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id MAA07382 for ; Fri, 20 Mar 1998 12:38:11 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id MAA05065; Fri, 20 Mar 1998 12:38:10 -0600 (CST) Message-ID: <19980320123810.63763@mcs.net> Date: Fri, 20 Mar 1998 12:38:10 -0600 From: Karl Denninger To: current@FreeBSD.ORG Subject: CURRENT Kernel Status Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, its better :-) The filesystem problem appears to be truly gone. HOWEVER, I have seen two pieces of "bad" behavior in the last six hours. 1. A complete and total wedge, including the keyboard controller. DDB was inop during this, of course (no keyboard = no interrupt = no DDB) 2. An unsolicited reset (NOT a panic!) from the same kernel. This one REALLY bothers me, as its darn hard to debug something without a dump! But, from the standpoint of disk destruction, I believe it is now safe to compile and run the CURRENT kernel. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 10:49:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25489 for freebsd-current-outgoing; Fri, 20 Mar 1998 10:49:53 -0800 (PST) (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 KAA25480 for ; Fri, 20 Mar 1998 10:49:51 -0800 (PST) (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 OAA22371; Fri, 20 Mar 1998 14:51:15 GMT Message-ID: <00f201bd5430$7f16b580$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: "Karl Denninger" , Subject: Re: CURRENT Kernel Status Date: Fri, 20 Mar 1998 13:46: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 i saw this problem (reboots) a while before the filesystem problems cropped up. no lockups though. i'd say mid week before the bad FS code this problem kinda "surfaced" before that i couldn't tell the difference between -current and -stable except that -current was a lot more interesting. -Alfred -----Original Message----- From: Karl Denninger To: current@FreeBSD.ORG Date: Friday, March 20, 1998 9:45 AM Subject: CURRENT Kernel Status > >Well, its better :-) > >The filesystem problem appears to be truly gone. > >HOWEVER, I have seen two pieces of "bad" behavior in the last six hours. > >1. A complete and total wedge, including the keyboard controller. > DDB was inop during this, of course (no keyboard = no interrupt = > no DDB) > >2. An unsolicited reset (NOT a panic!) from the same kernel. This one > REALLY bothers me, as its darn hard to debug something without a > dump! > >But, from the standpoint of disk destruction, I believe it is now safe to >compile and run the CURRENT kernel. > >-- >-- >Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin >http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV > | NEW! Corporate ISDN Prices dropped by up to 50%! >Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS >Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 10:54:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26720 for freebsd-current-outgoing; Fri, 20 Mar 1998 10:54:08 -0800 (PST) (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 KAA26169; Fri, 20 Mar 1998 10:52:08 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id SAA05208; Fri, 20 Mar 1998 18:14:52 +0100 From: Luigi Rizzo Message-Id: <199803201714.SAA05208@labinfo.iet.unipi.it> Subject: patch for Vibra16X -- test please! To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Fri, 20 Mar 1998 18:14:52 +0100 (MET) Cc: multimedia@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [forgive me for the crosspost but I'm trying to get some feedback quickly... since this might go into -stable and the deadline is close...] By popular demand, enclosed is a small patch to hopefully add PARTIAL Vibra16X support for playback (there is also some still non-functional code for the ESS -- don't worry about that bu i prefer not to handcraft the patchfile). This is mostly derived from code contributed by Torsten Ackemann. The diff is against snd980215 which is essentially what is now in -current and -stable. The modified files are only sb_dsp.c and sbcard.h Note that, assuming this code works at all: * it might affect plain SB16 support, so I'd like to have feedback from someone with the SB16 (it should still work fine); * it only works in playback; we haven't figured out yet how to tell capture from playback interrupts. And I have not been successful in getting documentation from Creative or Realtek (the latter make a Vibra16X clone). * you might have to add the PnP vend_id of your card near the end of sb_dsp.c -- there is a comment marked with VIBRA16X in this patch in the point where you should make the addition. As usual, feedback is not only welcome but absolutely necessay since I don't have a Vibra16X or clone. I need to know both if it works and if it not works. Do not forget to give details about your card (e.g. brand, PnP vendor ID) cheers luigi diff -ubwr snd/sb_dsp.c /sys/i386/isa/snd/sb_dsp.c --- snd/sb_dsp.c Tue Jan 27 21:01:49 1998 +++ /sys/i386/isa/snd/sb_dsp.c Fri Mar 20 19:32:52 1998 @@ -275,9 +275,12 @@ * SB < 4.0 is half duplex and has only 1 bit for int source, * so we fake it. SB 4.x (SB16) has the int source in a separate * register. + * The Vibra16X has separate flags for 8 and 16 bit transfers, but + * I have no idea how to tell capture from playback interrupts... */ +#define PLAIN_SB16(x) ( ( (x) & (BD_F_SB16|BD_F_SB16X) ) == BD_F_SB16) again: - if (d->bd_flags & BD_F_SB16) { + if (PLAIN_SB16(d->bd_flags)) { c = sb_getmixer(io_base, IRQ_STAT); /* this tells us if the source is 8-bit or 16-bit dma. We * have to check the io channel to map it to read or write... @@ -302,7 +305,7 @@ if ( d->dbuf_out.dl ) dsp_wrintr(d); else { - if (d->bd_flags & BD_F_SB16) + if (PLAIN_SB16(d->bd_flags)) printf("WARNING: wrintr but write DMA inactive!\n"); } } @@ -310,7 +313,7 @@ if ( d->dbuf_in.dl ) dsp_rdintr(d); else { - if (d->bd_flags & BD_F_SB16) + if (PLAIN_SB16(d->bd_flags)) printf("WARNING: rdintr but read DMA inactive!\n"); } } @@ -353,7 +356,7 @@ else d->flags &= ~SND_F_XLAT8 ; - if (d->bd_flags & BD_F_SB16) { + if (PLAIN_SB16(d->bd_flags)) { u_char c, c1 ; /* the SB16 can do full duplex using one 16-bit channel @@ -392,6 +395,29 @@ d->dbuf_in.chan = d->dbuf_out.chan; d->dbuf_out.chan = c ; } + } else if (d->bd_flags & BD_F_ESS) { + u_char c ; + if (d->play_fmt == 0) { + /* initialize for record */ + static u_char cmd[] = { + 0x51,0xd0,0x71,0xf4,0x51,0x98,0x71,0xbc + }; + ess_write(d->io_base, 0xb8, 0x0e); + c = ( ess_read(d->io_base, 0xa8) & 0xfc ) | 1 ; + if (d->flags & SND_F_STEREO) + c++ ; + ess_write(d->io_base, 0xa8, c); + ess_write(d->io_base, 0xb9, 2); /* 4bytes/transfer */ + /* + * set format in b6, b7 + */ + } else { + /* initialize for play */ + static u_char cmd[] = { + 0x80,0x51,0xd0,0x00,0x71,0xf4, + 0x80,0x51,0x98,0x00,0x71,0xbc + }; + } } reset_dbuf(& (d->dbuf_in), SND_CHAN_RD ); reset_dbuf(& (d->dbuf_out), SND_CHAN_WR ); @@ -406,7 +432,10 @@ * is assigned. This means that if the application * tries to use a bad format, the sound will not be nice. */ - if ( b->chan > 4 ) { + if ( b->chan > 4 + || (rd && d->rec_fmt == AFMT_S16_LE) + || (!rd && d->play_fmt == AFMT_S16_LE) + ) { c = DSP_F16_AUTO | DSP_F16_FIFO_ON | DSP_DMA16 ; c1 = DSP_F16_SIGNED ; l /= 2 ; @@ -455,7 +484,10 @@ case SND_CB_STOP : { int cmd = DSP_CMD_DMAPAUSE_8 ; /* default: halt 8 bit chan */ - if ( d->bd_flags & BD_F_SB16 && b->chan > 4 ) + if ( b->chan > 4 + || (rd && d->rec_fmt == AFMT_S16_LE) + || (!rd && d->play_fmt == AFMT_S16_LE) + ) cmd = DSP_CMD_DMAPAUSE_16 ; if (d->bd_flags & BD_F_HISPEED) { sb_reset_dsp(d->io_base); @@ -618,7 +650,7 @@ printf("ESS1868 (rev %d)\n", rev); else printf("ESS688 (rev %d)\n", rev); - d->audio_fmt |= AFMT_S16_LE; /* in fact it is U16_LE */ + /* d->audio_fmt |= AFMT_S16_LE; */ /* not yet... */ break ; /* XXX */ } else { printf("Unknown card 0x%x 0x%x -- hope it is SBPRO\n", @@ -661,6 +693,14 @@ /* * Common code for the midi and pcm functions + * + * sb_cmd write a single byte to the CMD port. + * sb_cmd2 write a CMD + 1 byte arg + * sb_cmd3 write a CMD + 2 byte arg + * sb_get_byte returns a single byte from the DSP data port + * + * ess_write is actually sb_cmd2 + * ess_read access ext. regs via sb_cmd(0xc0, reg) followed by sb_get_byte */ int @@ -726,9 +766,9 @@ u_long flags; flags = spltty(); - outb(io_base + 4, (u_char) (port & 0xff)); /* Select register */ + outb(io_base + SB_MIX_ADDR, (u_char) (port & 0xff)); /* Select register */ DELAY(10); - val = inb(io_base + 5); + val = inb(io_base + SB_MIX_DATA); DELAY(10); splx(flags); @@ -748,6 +788,19 @@ return 0xffff; } +int +ess_write(int io_base, u_char reg, int val) +{ + return sb_cmd2(io_base, reg, val); +} + +int +ess_read(int io_base, u_char reg) +{ + if (!sb_cmd(io_base, 0xc0) || !sb_cmd(io_base, reg) ) + return 0xffff ; + return sb_get_byte(io_base); +} /* @@ -786,17 +839,21 @@ */ if (d->bd_flags & BD_F_ESS) { int t; - RANGE (speed, 4000, 48000); + RANGE (speed, 5000, 49000); if (speed > 22000) { t = (795500 + speed / 2) / speed; speed = (795500 + t / 2) / t ; - t = ( 256 - (795500 + speed / 2) / speed ) | 0x80 ; + t = (256 - t ) | 0x80 ; } else { t = (397700 + speed / 2) / speed; speed = (397700 + t / 2) / t ; - t = 128 - (397700 + speed / 2) / speed ; + t = 128 - t ; } - sb_cmd2(d->io_base, 0xa1, t); /* set time constant */ + ess_write(d->io_base, 0xa1, t); /* set time constant */ + d->play_speed = d->rec_speed = speed ; + speed = (speed * 9 ) / 20 ; + t = 256-7160000/(speed*82); + ess_write(d->io_base,0xa2,t); return speed ; } @@ -1154,6 +1211,7 @@ * A driver for some SB16pnp and compatibles... * * Avance Asound 100 -- 0x01009305 + * Avance Logic ALS100+ -- 0x10019305 * xxx -- 0x2b008c0e * */ @@ -1187,6 +1245,8 @@ s = "SB16 PnP"; else if (vend_id == 0x01009305) s = "Avance Asound 100" ; + else if (vend_id == 0x10009305) + s = "Avance Logic 100+" ; if (s) { struct pnp_cinfo d; read_pnp_parms(&d, 0); @@ -1224,6 +1284,12 @@ pcm_info[dev->id_unit] = tmp_d; snddev_last_probed->probe(dev); /* not really necessary but doesn't harm */ + if (vend_id == 0x10009305) { + /* + * VIBRA16X please add here the vend_id for other vibra16X cards... + */ + pcm_info[dev->id_unit].bd_flags |= BD_F_SB16X ; + } pcmattach(dev); } #endif /* NPNP */ Only in /sys/i386/isa/snd: sb_dsp.c.v16 diff -ubwr snd/sbcard.h /sys/i386/isa/snd/sbcard.h --- snd/sbcard.h Fri Jan 16 19:03:44 1998 +++ /sys/i386/isa/snd/sbcard.h Thu Mar 12 09:40:16 1998 @@ -19,9 +19,9 @@ #define DSP_DATA_AVAIL (io_base + 0xE) #define DSP_DATA_AVL16 (io_base + 0xF) +#define SB_MIX_ADDR 0x4 +#define SB_MIX_DATA 0x5 #if 0 -#define MIXER_ADDR (io_base + 0x4) -#define MIXER_DATA (io_base + 0x5) #define OPL3_LEFT (io_base + 0x0) #define OPL3_RIGHT (io_base + 0x2) #define OPL3_BOTH (io_base + 0x8) @@ -138,7 +138,7 @@ #define BD_F_MIX_CT1745 0x0030 /* CT1745 */ #define BD_F_SB16 0x0100 /* this is a SB16 */ -#define BD_F_NOREC 0x0200 /* recording not supported on this board */ +#define BD_F_SB16X 0x0200 /* this is a vibra16X or clone */ #define BD_F_MIDIBUSY 0x0400 /* midi busy */ #define BD_F_ESS 0x0800 /* this is an ESS chip */ diff -ubwr snd/sound.c /sys/i386/isa/snd/sound.c --- snd/sound.c Fri Feb 13 15:33:08 1998 +++ /sys/i386/isa/snd/sound.c Sat Mar 14 23:11:35 1998 @@ -717,7 +717,7 @@ snd_chan_param *p = (snd_chan_param *)arg; d->play_speed = p->play_rate; d->rec_speed = p->play_rate; /* XXX one speed allowed */ - if (p->play_format & SND_F_STEREO) + if (p->play_format & AFMT_STEREO) d->flags |= SND_F_STEREO ; else d->flags &= ~SND_F_STEREO ; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 11:06:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00473 for freebsd-current-outgoing; Fri, 20 Mar 1998 11:06:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00407 for ; Fri, 20 Mar 1998 11:06:16 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id MAA16870; Fri, 20 Mar 1998 12:06:15 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd016848; Fri Mar 20 12:06:12 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id MAA17435; Fri, 20 Mar 1998 12:06:10 -0700 (MST) From: Terry Lambert Message-Id: <199803201906.MAA17435@usr05.primenet.com> Subject: Re: 4 WILLRELE's to bite the dust To: michaelh@cet.co.jp (Michael Hancock) Date: Fri, 20 Mar 1998 19:06:10 +0000 (GMT) Cc: phk@critter.freebsd.dk, freebsd-current@FreeBSD.ORG In-Reply-To: from "Michael Hancock" at Mar 20, 98 10:11:14 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 > I tagged through ufs_makeinode which is shared by a few vops, but I'm sure > I've got all of them. Here are the diffs that Mike Smith has with > vop_link and vop_rmdir dvp's done. If it's a vnode leak, then they should > go away by implementing everything unless I'm vreleing the wrong thing and > in that case we should get a panic in getnewvnode. > > Are you using ipfilter? This also makes vop calls. > > Did you have a chance to look at vmstat -m before the crash? You probably want to get: http://www.freebsd.org/~terry/testset.txt http://www.freebsd.org/~terry/testset.tar.gz.uu Which is a test toolkit that knows how to detect kernel memory leaks over a series of system calls used to exercise various code paths. The sample implementation looks for namei() path buffer leaks; I used it to verify the nameifree() code before I submitted it the first time. 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 Mar 20 11:19:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03302 for freebsd-current-outgoing; Fri, 20 Mar 1998 11:19:05 -0800 (PST) (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 LAA03291 for ; Fri, 20 Mar 1998 11:19:03 -0800 (PST) (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 LAA20686; Fri, 20 Mar 1998 11:13:34 -0800 (PST) Message-Id: <199803201913.LAA20686@implode.root.com> To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: Pathetic FTP performance In-reply-to: Your message of "Fri, 20 Mar 1998 10:57:30 EST." From: David Greenman Reply-To: dg@root.com Date: Fri, 20 Mar 1998 11:13:34 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I am getting really pathetic FTP performance across my LAN. From any >machine to any other machine, I am seeing several hundred k / sec via FTP. >E.g. from my Mac to my SGI, I see between 300k/s - 1M/s, depending on file >size. > >However, when I am running FreeBSD (-Current as of 12 March), I am getting >really pathetic performance... on the order of 0-2 k / second. > >The network is 10baseT, My ethernet is the intel EtherExpress Pro 10/100B >rev 0x02 that is built into the DK440LX motherboard. The net is almost >completely unloaded, so it isn't traffic. > >Running ping generally has a transit time of just under 1 ms, although I am >seeing 4% packet loss (2 packets out of 40). > >Generally, what I am seeing is both low transfer rates as well as *LOTS* of >stalling. That's enough packet loss to cause very low transfer rates for ethernet. >Any suggestions what is causing this, and how to diagnose / fix it? Look at the input stats on the receiving machine - are you seeing input errors? It sounds like you might have a bad cable segment. -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 Fri Mar 20 11:23:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04095 for freebsd-current-outgoing; Fri, 20 Mar 1998 11:23:45 -0800 (PST) (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 LAA04090 for ; Fri, 20 Mar 1998 11:23:43 -0800 (PST) (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 LAA20772; Fri, 20 Mar 1998 11:18:15 -0800 (PST) Message-Id: <199803201918.LAA20772@implode.root.com> To: Warner Losh cc: Kevin Day , ckempf@enigami.com (Cory Kempf), freebsd-current@FreeBSD.ORG Subject: Re: Pathetic FTP performance In-reply-to: Your message of "Fri, 20 Mar 1998 10:21:50 MST." <199803201721.KAA00713@harmony.village.org> From: David Greenman Reply-To: dg@root.com Date: Fri, 20 Mar 1998 11:18:15 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In message <199803201631.KAA00555@home.dragondata.com> Kevin Day writes: >: With a 2.1 kernel I saw a nice steady stream... I've been unable to find >: what change prompted this. :) > >I'm seeing something that is similar that I've not had time to track >down. When I connect via lynx or netscape to certain sites >(www.onsale.com is one), I get 300-odd bytes and then nothing else for >the life of the conenction. I'm seeing this on a early Feb 2.2 as >well as a Julyish -current system. Yes, tcp extentions are turned off >on both of these systems. > >The S4000 running OS/MP on the same subnet can get to these sites with >lynx no problems. This is probably caused by an interaction between Path MTU Discovery and misconfigured firewalls at www.onsale.com and other places which are dropping ICMP packets. You can disable PMTU Discovery with the following addition to your 'defaultrouter' line in /etc/sysconfig: -lock -mtu 1500 -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 Fri Mar 20 11:29:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05198 for freebsd-current-outgoing; Fri, 20 Mar 1998 11:29:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (root@danberlin.resnet.rochester.edu [128.151.91.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05189 for ; Fri, 20 Mar 1998 11:29:11 -0800 (PST) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (8.8.8/8.8.8) with SMTP id OAA03312; Fri, 20 Mar 1998 14:24:20 -0500 Date: Fri, 20 Mar 1998 14:24:20 -0500 (EST) From: root X-Sender: root@danberlin To: Karl Denninger cc: current@FreeBSD.ORG Subject: Re: CURRENT Kernel Status In-Reply-To: <19980320123810.63763@mcs.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 ah yes, i received number 1 as well Quite NOT fun. I also got an ffs panic, but i think that's cause my system still hasn't nomralized from fun with filesystems. :) On Fri, 20 Mar 1998, Karl Denninger wrote: > > Well, its better :-) > > The filesystem problem appears to be truly gone. > > HOWEVER, I have seen two pieces of "bad" behavior in the last six hours. > > 1. A complete and total wedge, including the keyboard controller. > DDB was inop during this, of course (no keyboard = no interrupt = > no DDB) > > 2. An unsolicited reset (NOT a panic!) from the same kernel. This one > REALLY bothers me, as its darn hard to debug something without a > dump! > > But, from the standpoint of disk destruction, I believe it is now safe to > compile and run the CURRENT kernel. > > -- > -- > Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin > http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV > | NEW! Corporate ISDN Prices dropped by up to 50%! > Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS > Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 12:25:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16970 for freebsd-current-outgoing; Fri, 20 Mar 1998 12:25:05 -0800 (PST) (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 MAA16934 for ; Fri, 20 Mar 1998 12:24:55 -0800 (PST) (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 PAA06294; Fri, 20 Mar 1998 15:23:45 -0500 (EST) X-Sender: ckempfm@enigami.com Message-Id: In-Reply-To: <199803201913.LAA20686@implode.root.com> References: Your message of "Fri, 20 Mar 1998 10:57:30 EST." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 20 Mar 1998 15:16:18 -0500 To: dg@root.com From: Cory Kempf Subject: Re: Pathetic FTP performance Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 14:13 -0500 98.03.20, David Greenman wrote: >>I am getting really pathetic FTP performance across my LAN. From any >>machine to any other machine, I am seeing several hundred k / sec via FTP. >>E.g. from my Mac to my SGI, I see between 300k/s - 1M/s, depending on file >>size. > Look at the input stats on the receiving machine - are you seeing input >errors? It sounds like you might have a bad cable segment. Yes, on looking, it was generating a lot of errors. Taking this idea, I swapped cables with the other machine on my desktop -- a Mac. Now, an interesting thing: this same 'bad' cable was being used without problem from a Mac running variously MacOS and MkLinux. When I swapped cables, the difference was like night and day on the FBSD box. OK, so I tested the 'bad' cable on my Mac... 0% packet loss, FTP speeds of 700 k/s (which is what I normally expect). I presume from this that the intel hardware is not as uh, something. Sensative? forgiving? whatever. Wierd. +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 Fri Mar 20 12:27:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17729 for freebsd-current-outgoing; Fri, 20 Mar 1998 12:27:10 -0800 (PST) (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 MAA17672 for ; Fri, 20 Mar 1998 12:26:46 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id PAA17448; Fri, 20 Mar 1998 15:25:38 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803202025.PAA17448@dyson.iquest.net> Subject: Re: CURRENT Kernel Status In-Reply-To: from root at "Mar 20, 98 02:24:20 pm" To: root@danberlin.resnet.rochester.edu (root) Date: Fri, 20 Mar 1998 15:25:38 -0500 (EST) Cc: karl@mcs.net, 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 > ah yes, i received number 1 as well > Quite NOT fun. > I also got an ffs panic, but i think that's cause my system still > hasn't nomralized from fun with filesystems. > :) > Following up, just wanted to say that this latest set of bugs will leave crud on your filesystems that fsck cannot fix. So, if you get straight ffs panics, I want to hear about them. Most of the time, I'll discount them as "expected", but if there is something interesting, I really do want to know about them. I'll tell everyone to "shut-up" when I don't want to hear about them anymore :-). John dyson@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Mar 20 12:38:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20577 for freebsd-current-outgoing; Fri, 20 Mar 1998 12:35:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from danberlin.resnet.rochester.edu (root@danberlin.resnet.rochester.edu [128.151.91.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20444 for ; Fri, 20 Mar 1998 12:35:23 -0800 (PST) (envelope-from root@danberlin.resnet.rochester.edu) Received: from localhost (root@localhost) by danberlin.resnet.rochester.edu (8.8.8/8.8.8) with SMTP id PAA03358; Fri, 20 Mar 1998 15:30:26 -0500 Date: Fri, 20 Mar 1998 15:30:26 -0500 (EST) From: root X-Sender: root@danberlin To: Cory Kempf cc: dg@root.com, freebsd-current@FreeBSD.ORG Subject: Re: Pathetic FTP performance 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 The word you are looking for is painfully slow. The intel hardware is not as painfully slow. :) --Dan > > I presume from this that the intel hardware is not as uh, something. > Sensative? forgiving? whatever. > > Wierd. > > +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 Fri Mar 20 12:48:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22858 for freebsd-current-outgoing; Fri, 20 Mar 1998 12:48:54 -0800 (PST) (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 MAA22851 for ; Fri, 20 Mar 1998 12:48:51 -0800 (PST) (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 MAA21498; Fri, 20 Mar 1998 12:43:16 -0800 (PST) Message-Id: <199803202043.MAA21498@implode.root.com> To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: Pathetic FTP performance In-reply-to: Your message of "Fri, 20 Mar 1998 15:16:18 EST." From: David Greenman Reply-To: dg@root.com Date: Fri, 20 Mar 1998 12:43:16 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >When I swapped cables, the difference was like night and day on the FBSD box. > >OK, so I tested the 'bad' cable on my Mac... 0% packet loss, FTP speeds of >700 k/s (which is what I normally expect). > >I presume from this that the intel hardware is not as uh, something. >Sensative? forgiving? whatever. I think it's a mixed bag...I heard exactly the opposite from someone else a month or so ago; I think all you can really say is that whatever was wrong with the cable affected the Intel card. -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 Fri Mar 20 13:27:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29121 for freebsd-current-outgoing; Fri, 20 Mar 1998 13:27:15 -0800 (PST) (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 NAA29070 for ; Fri, 20 Mar 1998 13:27:03 -0800 (PST) (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 RAA23719; Fri, 20 Mar 1998 17:28:05 GMT Message-ID: <013701bd5446$6237a620$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: "Cory Kempf" Cc: Subject: Re: Pathetic FTP performance Date: Fri, 20 Mar 1998 16:23:10 -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 yes this is the problem, it has been discussed before. -Alfred -----Original Message----- From: Cory Kempf To: dg@root.com Cc: freebsd-current@FreeBSD.ORG Date: Friday, March 20, 1998 11:34 AM Subject: Re: Pathetic FTP performance >At 14:13 -0500 98.03.20, David Greenman wrote: >>>I am getting really pathetic FTP performance across my LAN. From any >>>machine to any other machine, I am seeing several hundred k / sec via FTP. >>>E.g. from my Mac to my SGI, I see between 300k/s - 1M/s, depending on file >>>size. > >> Look at the input stats on the receiving machine - are you seeing input >>errors? It sounds like you might have a bad cable segment. > >Yes, on looking, it was generating a lot of errors. Taking this idea, I >swapped cables with the other machine on my desktop -- a Mac. > >Now, an interesting thing: this same 'bad' cable was being used without >problem from a Mac running variously MacOS and MkLinux. > >When I swapped cables, the difference was like night and day on the FBSD box. > >OK, so I tested the 'bad' cable on my Mac... 0% packet loss, FTP speeds of >700 k/s (which is what I normally expect). > >I presume from this that the intel hardware is not as uh, something. >Sensative? forgiving? whatever. > >Wierd. > >+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 Fri Mar 20 23:09:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03705 for freebsd-current-outgoing; Fri, 20 Mar 1998 23:09:18 -0800 (PST) (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 XAA03700 for ; Fri, 20 Mar 1998 23:09:16 -0800 (PST) (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 HAA27076; Sat, 21 Mar 1998 07:05:54 GMT Date: Sat, 21 Mar 1998 16:05:54 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: phk@critter.freebsd.dk, freebsd-current@FreeBSD.ORG Subject: Re: 4 WILLRELE's to bite the dust In-Reply-To: <199803201906.MAA17435@usr05.primenet.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, 20 Mar 1998, Terry Lambert wrote: > You probably want to get: > > http://www.freebsd.org/~terry/testset.txt > http://www.freebsd.org/~terry/testset.tar.gz.uu > > Which is a test toolkit that knows how to detect kernel memory > leaks over a series of system calls used to exercise various > code paths. > > The sample implementation looks for namei() path buffer leaks; I > used it to verify the nameifree() code before I submitted it the > first time. I'll take a look. It's an interesting coincidence that most of the WILLRELE violations were in the name creation and name management vops. Just about every place I corrected a vrele/vput was a also a nameifree() screaming to be moved/corrected too. I've done the dvp's for 5 name creation ops, vop_create, vop_mkdir, vop_symlink, vop_link, and vop_mknod; and 1 of 3 name modification ops, vop_rmdir. I think I'll press on and do the other 2, and vop_remove and vop_rename. Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 07:22:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17226 for freebsd-current-outgoing; Sat, 21 Mar 1998 07:22:41 -0800 (PST) (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 HAA17197 for ; Sat, 21 Mar 1998 07:22:38 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id KAA03910 for current@freebsd.org; Sat, 21 Mar 1998 10:22:50 -0500 (EST) (envelope-from toor) Message-Id: <199803211522.KAA03910@dyson.iquest.net> Subject: Be careful, looking good To: current@FreeBSD.ORG Date: Sat, 21 Mar 1998 10:22:49 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@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 I am not going to make any further comments about this latest fiasco about -current, except some testing by me and others is showing that it is looking okay. The filesystem corruption looks like it is gone now. No guarantees, just be careful. Don't assume that it is perfect. -- 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 Mar 21 07:33:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18126 for freebsd-current-outgoing; Sat, 21 Mar 1998 07:33:07 -0800 (PST) (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 HAA18093 for ; Sat, 21 Mar 1998 07:32:46 -0800 (PST) (envelope-from kong@kkk.ml.org) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.00) with SMTP id SAA00408 for ; Sat, 21 Mar 1998 18:32:27 +0300 (MSK) (envelope-from kong@kkk.ml.org) Date: Sat, 21 Mar 1998 18:32:27 +0300 (MSK) From: Hostas Red X-Sender: kong@kong.dorms.spbu.ru To: current@FreeBSD.ORG Subject: Having problems with msdosfs 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! Still having problems with writing onto msdosfs partition (FAT32). It reads ok, but when i'm trying to write a couple of files there, system hangs, and need a reset to reboot. It hangs in a strange way - keyboard on this console works, but has no effect (^C etc doesn't work), just typing symbols, i can switch to other consoles, but can't type a symbol there. So, only reset can help. Any ideas? It was on 12/03, it is on current. :( Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 07:56:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20475 for freebsd-current-outgoing; Sat, 21 Mar 1998 07:56:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20470 for ; Sat, 21 Mar 1998 07:56:57 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id HAA18058 for ; Sat, 21 Mar 1998 07:56:58 -0800 (PST) (envelope-from jdp) Message-Id: <199803211556.HAA18058@austin.polstra.com> To: current@FreeBSD.ORG Subject: Re: Using CVSUP and CTM together (Was Re: Disk munging problem with current solved) In-Reply-To: References: <199803171142.TAA07037@cssolar85.COMP.HKP.HK> <35106C23.64774CD9@dsto.defence.gov.au> <199803190244.UAA08131@detlev.UUCP> Organization: Polstra & Co., Seattle, WA Date: Sat, 21 Mar 1998 07:56:58 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Richard Wackerbarth wrote: > At 9:09 PM -0600 3/18/98, Matthew Thyer wrote: > >I dont know about this... hopefully someone else can comment on it. > > > >It would be good to be able to cvsup for a latest VM fix and then > >to be able to re-synchronize with CTM later. > > The ability to do this is somewhat limited by the problems > associated in jumping from one CVSup server to another. I want to make sure nobody is misled by the above statement. There is _no_ inherent problem with jumping from one CVSup server to another. It works just fine as long as you're not trying to mix CVSup and CTM updates. What Richard was referring to (I guess) is that the various CVSup mirrors make no attempt to stay in lock-step with each other, or with the CTM deltas. So what you find on one CVSup mirror might be a little more or a little less up to date than what you find on a different mirror. This doesn't bother CVSup in the least. Also, the variation between servers is quite small in practice, since most of the mirrors update their files from the master site hourly. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 08:54:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27297 for freebsd-current-outgoing; Sat, 21 Mar 1998 08:54:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ha1.rdc1.sdca.home.com (siteadm@ha1.rdc1.sdca.home.com [24.0.3.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27251 for ; Sat, 21 Mar 1998 08:54:00 -0800 (PST) (envelope-from slafla@home.com) Received: from home.com ([24.0.130.231]) by ha1.rdc1.sdca.home.com (Netscape Mail Server v2.02) with ESMTP id AAA12946 for ; Sat, 21 Mar 1998 08:52:17 -0800 Message-ID: <3513F0AA.E817DA74@home.com> Date: Sat, 21 Mar 1998 08:54:02 -0800 From: Scott Long Reply-To: slafla@home.com X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: current breakage 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 just cvsuped current at 0730pst and tried to make world. It fails here: building standard ln library ranlib libln.a install -c -o bin -g bin -m 444 libln.a /usr/obj/usr/src/tmp/usr/lib /usr/obj/usr/src/tmp/usr/lib/libl.a -> /usr/obj/usr/src/tmp/usr/lib/libln.a /usr/obj/usr/src/tmp/usr/lib/libfl.a -> /usr/obj/usr/src/tmp/usr/lib/libln.a /usr/obj/usr/src/usr.bin/lex/lib created for /usr/src/usr.bin/lex/lib cd /usr/src/usr.bin/mk_cmds && /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMA N -DNOPROFILE -DNOSHARED depend && /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO - DNOMAN -DNOPROFILE -DNOSHARED all && /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B install && /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj yacc -d /usr/src/usr.bin/mk_cmds/ct.y mv y.tab.c ct.c lex -t -l /usr/src/usr.bin/mk_cmds/cmd_tbl.l > cmd_tbl.c Bus error - core dumped *** Error code 138 Stop. A subsequent try at make world results in a panic during the "rm -rf /usr/obj/usr/src/tmp" at the beginning. Is the tree in a rather unstable state right now? My dmesg output is: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 FreeBSD 3.0-CURRENT #2: Thu Mar 19 20:25:03 PST 1998 scottl@cx67628-a.dt1.sdca.home.com:/usr/src/sys/compile/SLAFLA Timecounter "i8254" frequency 1193210 Hz cost 2687 ns Timecounter "TSC" frequency 200458990 Hz cost 176 ns CPU: Pentium (200.46-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 50331648 (49152K bytes) avail memory = 47079424 (45976K bytes) Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip2: rev 0x01 int d irq 11 on pci0.7.2 chip3: rev 0x01 on pci0.7.3 vga0: rev 0x00 int a irq 10 on pci0.18.0 ed0: rev 0x00 int a irq 9 on pci0.19.0 ed0: address 00:40:05:5e:b0:a7, type NE2000 (16 bit) Probing for PnP devices: CSN 1 Vendor ID: USR2050 [0x50207256] Serial 0x46464646 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 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 5009MB (10258920 sectors), 10856 cyls, 15 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, accel, dma, iordis wcd0: 1378Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray wcd0: no disc inside, unlocked wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): , DMA, 32-bit, multi-b lock-16 wd2: 1032MB (2113776 sectors), 2097 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 1 (wd3): , 32-bit, multi-block-16 wd3: 405MB (830760 sectors), 989 cyls, 15 heads, 56 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isasbmidi0 at 0x330 on isa snd0: opl0 at 0x388 on isa snd0: Intel Pentium F00F detected, installing workaround WARNING: / was not properly dismounted. pid 19187 (lex), uid 0: exited on signal 10 (core dumped) Hope this helps Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 11:11:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08941 for freebsd-current-outgoing; Sat, 21 Mar 1998 11:11:10 -0800 (PST) (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 LAA08935 for ; Sat, 21 Mar 1998 11:11:07 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id NAA23129; Sat, 21 Mar 1998 13:11:08 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id NAA23425; Sat, 21 Mar 1998 13:11:07 -0600 (CST) Message-ID: <19980321131107.42741@mcs.net> Date: Sat, 21 Mar 1998 13:11:07 -0600 From: Karl Denninger To: slafla@home.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: current breakage References: <3513F0AA.E817DA74@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <3513F0AA.E817DA74@home.com>; from Scott Long on Sat, Mar 21, 1998 at 08:54:02AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 21, 1998 at 08:54:02AM -0800, Scott Long wrote: > Hi. I just cvsuped current at 0730pst and tried to make world. It > fails > here: > > building standard ln library > ranlib libln.a > install -c -o bin -g bin -m 444 libln.a /usr/obj/usr/src/tmp/usr/lib > /usr/obj/usr/src/tmp/usr/lib/libl.a -> > /usr/obj/usr/src/tmp/usr/lib/libln.a > /usr/obj/usr/src/tmp/usr/lib/libfl.a -> > /usr/obj/usr/src/tmp/usr/lib/libln.a > /usr/obj/usr/src/usr.bin/lex/lib created for /usr/src/usr.bin/lex/lib > cd /usr/src/usr.bin/mk_cmds && /usr/obj/usr/src/tmp/usr/bin/make > -DNOINFO -DNOMA > N -DNOPROFILE -DNOSHARED depend && /usr/obj/usr/src/tmp/usr/bin/make > -DNOINFO - > DNOMAN -DNOPROFILE -DNOSHARED all && /usr/obj/usr/src/tmp/usr/bin/make > -DNOINFO > -DNOMAN -DNOPROFILE -DNOSHARED -B install && > /usr/obj/usr/src/tmp/usr/bin/make > -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj > yacc -d /usr/src/usr.bin/mk_cmds/ct.y > mv y.tab.c ct.c > lex -t -l /usr/src/usr.bin/mk_cmds/cmd_tbl.l > cmd_tbl.c > Bus error - core dumped > *** Error code 138 > > Stop. > > A subsequent try at make world results in a panic during the "rm -rf > /usr/obj/usr/src/tmp" at the beginning. Is the tree in a rather > unstable state right now? > My dmesg output is: > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > FreeBSD 3.0-CURRENT #2: Thu Mar 19 20:25:03 PST 1998 > scottl@cx67628-a.dt1.sdca.home.com:/usr/src/sys/compile/SLAFLA Aeeeeeeiiiiii!!!! Get that kernel off the system RIGHT NOW. You MUST, and I repeat - MUST - immediately back out to roughly March 12th, then update your kernel source tree to AT LEAST Friday and rebuild a new kernel. Then and only then will you have anything approaching a stable system. It is entirely possible that the filesystem(s) which you had mounted read/write have been irrevocably damaged. Please folks, if you're going to run CURRENT, READ THIS LIST! -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 11:21:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10489 for freebsd-current-outgoing; Sat, 21 Mar 1998 11:21:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tor-dev1.nbc.netcom.ca (tor-dev1.nbc.netcom.ca [207.181.89.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10444 for ; Sat, 21 Mar 1998 11:21:49 -0800 (PST) (envelope-from taob@tor-dev1.nbc.netcom.ca) Received: (from taob@localhost) by tor-dev1.nbc.netcom.ca (8.8.8/8.8.8) id OAA12727; Sat, 21 Mar 1998 14:21:07 -0500 (EST) Date: Sat, 21 Mar 1998 14:21:06 -0500 (EST) From: Brian Tao To: Andrew Reilly cc: current@FreeBSD.ORG Subject: Re: Worldstone Continued... In-Reply-To: <199803182302.KAA02826@gurney.reilly.home> 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, 19 Mar 1998, Andrew Reilly wrote: > > It would be interesting to see a "speed of light" figure for > buildworld. I note that there are some people on this list with > access to machines with seriously big DRAM (.5G?) on their systems. > I doubt that any one compile operation exercises more than a few > Meg, with -pipe. If you have that much RAM to spare on a system, make a 384MB memory filesystem, and stick /var/tmp, /usr/obj and /usr/src on it. Then try a buildworld and see how fast it goes. /usr/obj and /usr/src should fit in 384MB. -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 11:32:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12474 for freebsd-current-outgoing; Sat, 21 Mar 1998 11:32:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12467 for ; Sat, 21 Mar 1998 11:32:40 -0800 (PST) (envelope-from johan@mail.elpost.com) Received: from pegasys (t1o41p38.telia.com [195.67.252.38]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with SMTP id UAA00175; Sat, 21 Mar 1998 20:32:33 +0100 Message-Id: <199803211932.UAA00175@mail.elpost.com> Comments: Authenticated sender is From: "Johan Granlund" To: Scott Long Date: Sat, 21 Mar 1998 20:31:58 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: current breakage CC: freebsd-current@FreeBSD.ORG In-reply-to: <3513F0AA.E817DA74@home.com> X-mailer: Pegasus Mail for Win32 (v2.54) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi. I just cvsuped current at 0730pst and tried to make world. It > fails > here: > > building standard ln library Your filesystem is probably hoosed. Boot a kernel before Mars 12 and check your system. The problems with disintegrating filesystems is hopefully fixed now as of yesterday. Read the -Current mailinglist, its been plenty of "Heads Up" for a week now... /Johan > My dmesg output is: > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > FreeBSD 3.0-CURRENT #2: Thu Mar 19 20:25:03 PST 1998 > scottl@cx67628-a.dt1.sdca.home.com:/usr/src/sys/compile/SLAFLA > Pentium F00F detected, installing workaround WARNING: / was not properly > dismounted. pid 19187 (lex), uid 0: exited on signal 10 (core dumped) > > Hope this helps > > Scott > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ___________________________________________________________ Internet: Johan@elpost.com I don't even speak for myself To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 13:39:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06260 for freebsd-current-outgoing; Sat, 21 Mar 1998 13:39:42 -0800 (PST) (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 NAA06254 for ; Sat, 21 Mar 1998 13:39:39 -0800 (PST) (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 VAA25852; Sat, 21 Mar 1998 21:39:33 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id WAA21303; Sat, 21 Mar 1998 22:39:28 +0100 (MET) Message-ID: <19980321223928.41465@follo.net> Date: Sat, 21 Mar 1998 22:39:28 +0100 From: Eivind Eklund To: Karl Denninger , slafla@home.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: current breakage References: <3513F0AA.E817DA74@home.com> <19980321131107.42741@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980321131107.42741@mcs.net>; from Karl Denninger on Sat, Mar 21, 1998 at 01:11:07PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 21, 1998 at 01:11:07PM -0600, Karl Denninger wrote: > On Sat, Mar 21, 1998 at 08:54:02AM -0800, Scott Long wrote: > > My dmesg output is: > > > > Copyright (c) 1992-1998 FreeBSD Inc. > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > FreeBSD 3.0-CURRENT #2: Thu Mar 19 20:25:03 PST 1998 > > scottl@cx67628-a.dt1.sdca.home.com:/usr/src/sys/compile/SLAFLA > > Aeeeeeeiiiiii!!!! > > Get that kernel off the system RIGHT NOW. > > You MUST, and I repeat - MUST - immediately back out to roughly March 12th, > then update your kernel source tree to AT LEAST Friday and rebuild a new > kernel. I don't know what the case is here (likely he is running a hosed kernel), but using dmesg output to say which kernel source version people is running is just wrong.. Please don't stomp all over the guy before having checked. My dmesg says I've built my system on March 17, in the middle of the bad period. This is quite correct, and I'm running March 13 sources (before the breakage). I've re-compiled to test other changes. And now I'll repeat Karl's advice: If that kernel is built from the -current sources of vintage newer than March 12 and older March 21, back down to March 12 or older, and the recompile true -current. Other kernels will cut your disks to tiny slices. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 13:52:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08056 for freebsd-current-outgoing; Sat, 21 Mar 1998 13:52:58 -0800 (PST) (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 NAA08051 for ; Sat, 21 Mar 1998 13:52:56 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 781 invoked from network); 21 Mar 1998 21:52:20 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 21 Mar 1998 21:52:20 -0000 Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id NAA00417 for freebsd-current@freebsd.org; Sat, 21 Mar 1998 13:52:43 -0800 (PST) (envelope-from scottm) Date: Sat, 21 Mar 1998 13:52:43 -0800 (PST) From: Scott Michel Message-Id: <199803212152.NAA00417@mordred.cs.ucla.edu> To: freebsd-current@FreeBSD.ORG Subject: John's latest round of changes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been running a CVSup'd kernel from yesterday, relatively trouble free. I'd concur with John: it seems OK for the moment, but be prepared to back out at a moment's notice. Do not use soft updates. That's still pretty unstable (although I've yet to get a decent panic and traceback -- machine spontaneously reboots under load.) Also, I did manage to get through a 'make world' w/minimal problems last night, and my disks (I'm a WD wanker too!) pass fsck checks. I'm going to try to track down the problems I've encountered, but since the kernel doesn't panic, these are notoriously NP hard to locate. -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 14:00:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09470 for freebsd-current-outgoing; Sat, 21 Mar 1998 14:00:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09464 for ; Sat, 21 Mar 1998 14:00:23 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA19618; Sat, 21 Mar 1998 15:00:24 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd019600; Sat Mar 21 15:00:22 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA06995; Sat, 21 Mar 1998 15:00:18 -0700 (MST) From: Terry Lambert Message-Id: <199803212200.PAA06995@usr09.primenet.com> Subject: Re: CURRENT Kernel Status To: toor@dyson.iquest.net (John S. Dyson) Date: Sat, 21 Mar 1998 22:00:18 +0000 (GMT) Cc: root@danberlin.resnet.rochester.edu, karl@mcs.net, current@FreeBSD.ORG In-Reply-To: <199803202025.PAA17448@dyson.iquest.net> from "John S. Dyson" at Mar 20, 98 03:25:38 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 > Following up, just wanted to say that this latest set of bugs will > leave crud on your filesystems that fsck cannot fix. I'd like more detail on this. The fsck program is supposed to return your disk to a consistent state, regardless of whether or not the data resulted from bad writes or from physical problems with the disk (though in the latter case, you'd be silly to not back it up as soon as it was consistent, and throw the old disk away). I know that fsck will not necessarily be able to return the disk to the state that it would have been without the failure, but it should be possible for it to return it to a self-consistent state. If it can't, then we need to fix it (IMO). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 14:03:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10205 for freebsd-current-outgoing; Sat, 21 Mar 1998 14:03:34 -0800 (PST) (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 OAA10145 for ; Sat, 21 Mar 1998 14:03:19 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 17195 invoked from network); 21 Mar 1998 22:09:00 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 21 Mar 1998 22:09:00 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-031798 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 21 Mar 1998 14:09:00 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Brian Tao Subject: Re: Worldstone Continued... Cc: current@FreeBSD.ORG, Andrew Reilly Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Mar-98 Brian Tao wrote: > On Thu, 19 Mar 1998, Andrew Reilly wrote: >> >> It would be interesting to see a "speed of light" figure for >> buildworld. I note that there are some people on this list with >> access to machines with seriously big DRAM (.5G?) on their systems. >> I doubt that any one compile operation exercises more than a few >> Meg, with -pipe. > > If you have that much RAM to spare on a system, make a 384MB > memory filesystem, and stick /var/tmp, /usr/obj and /usr/src on it. > Then try a buildworld and see how fast it goes. /usr/obj and /usr/src > should fit in 384MB. My very humble opinion is that we are barking up the wrong tree. Disk I/O is not the limiting factor here. I am looking at disk bandwidth utilization of less than 20%. From idle observation, it appears that parsing Makefiles is 4-5 times the amount of time it takes to actually compile anything. The curious could take the kernel directory and write a simple script to compile it without make at all. Tell us the results. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 15:11:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17417 for freebsd-current-outgoing; Sat, 21 Mar 1998 15:11:19 -0800 (PST) (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 PAA17400; Sat, 21 Mar 1998 15:11:16 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id RAA28878; Sat, 21 Mar 1998 17:11:16 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id RAA26688; Sat, 21 Mar 1998 17:11:16 -0600 (CST) Message-ID: <19980321171116.21165@mcs.net> Date: Sat, 21 Mar 1998 17:11:16 -0600 From: Karl Denninger To: Scott Michel Cc: freebsd-current@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: John's latest round of changes References: <199803212152.NAA00417@mordred.cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199803212152.NAA00417@mordred.cs.ucla.edu>; from Scott Michel on Sat, Mar 21, 1998 at 01:52:43PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One other thing - it appears that the CAM patches with John's fixes are SERIOUSLY unstable. Without CAM John's latest commits appear to fix the stability and disk corruption problems. With CAM the corruption doesn't happen, but stability is in the toilet. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Sat, Mar 21, 1998 at 01:52:43PM -0800, Scott Michel wrote: > I've been running a CVSup'd kernel from yesterday, relatively trouble > free. I'd concur with John: it seems OK for the moment, but be prepared > to back out at a moment's notice. > > Do not use soft updates. That's still pretty unstable (although I've > yet to get a decent panic and traceback -- machine spontaneously > reboots under load.) > > Also, I did manage to get through a 'make world' w/minimal problems > last night, and my disks (I'm a WD wanker too!) pass fsck checks. > > I'm going to try to track down the problems I've encountered, but > since the kernel doesn't panic, these are notoriously NP hard to > locate. > > > -scooter > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 15:13:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18114 for freebsd-current-outgoing; Sat, 21 Mar 1998 15:13:29 -0800 (PST) (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 PAA18089 for ; Sat, 21 Mar 1998 15:13:26 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id RAA28894; Sat, 21 Mar 1998 17:12:11 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id RAA26697; Sat, 21 Mar 1998 17:12:11 -0600 (CST) Message-ID: <19980321171211.55116@mcs.net> Date: Sat, 21 Mar 1998 17:12:11 -0600 From: Karl Denninger To: Terry Lambert Cc: "John S. Dyson" , root@danberlin.resnet.rochester.edu, current@FreeBSD.ORG Subject: Re: CURRENT Kernel Status References: <199803202025.PAA17448@dyson.iquest.net> <199803212200.PAA06995@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199803212200.PAA06995@usr09.primenet.com>; from Terry Lambert on Sat, Mar 21, 1998 at 10:00:18PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 21, 1998 at 10:00:18PM +0000, Terry Lambert wrote: > > Following up, just wanted to say that this latest set of bugs will > > leave crud on your filesystems that fsck cannot fix. > > I'd like more detail on this. The fsck program is supposed to return > your disk to a consistent state, regardless of whether or not the > data resulted from bad writes or from physical problems with the > disk (though in the latter case, you'd be silly to not back it up > as soon as it was consistent, and throw the old disk away). > > I know that fsck will not necessarily be able to return the disk > to the state that it would have been without the failure, but it > should be possible for it to return it to a self-consistent state. > > If it can't, then we need to fix it (IMO). It doesn't in this particular case. Further, that the METADATA is ok doesn't mean the file contents are undamaged! This last round destroyed or damaged BOTH metadata and the file contents. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 15:26:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20869 for freebsd-current-outgoing; Sat, 21 Mar 1998 15:26:35 -0800 (PST) (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 PAA20855; Sat, 21 Mar 1998 15:26:28 -0800 (PST) (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 JAA17165; Sun, 22 Mar 1998 09:56:25 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id JAA29698; Sun, 22 Mar 1998 09:56:25 +1030 (CST) (envelope-from grog) Message-ID: <19980322095625.59024@freebie.lemis.com> Date: Sun, 22 Mar 1998 09:56:25 +1030 From: Greg Lehey To: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Be careful, looking good References: <199803211522.KAA03910@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803211522.KAA03910@dyson.iquest.net>; from John S. Dyson on Sat, Mar 21, 1998 at 10:22:49AM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 March 1998 at 10:22:49 -0500, John S. Dyson wrote: > I am not going to make any further comments about this latest > fiasco about -current, except some testing by me and others > is showing that it is looking okay. The filesystem corruption > looks like it is gone now. > > No guarantees, just be careful. Don't assume that it is > perfect. Fine. Somebody (Karl) mentioned hangs and spontaneous reboots a day or two ago. Any comments on them? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 15:31:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21866 for freebsd-current-outgoing; Sat, 21 Mar 1998 15:31:22 -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 PAA21859 for ; Sat, 21 Mar 1998 15:31:17 -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 CAA25095; Sun, 22 Mar 1998 02:27:09 +0300 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 CAA02181; Sun, 22 Mar 1998 02:36:27 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199803212336.CAA02181@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Hostas Red cc: current@FreeBSD.ORG Subject: Re: Having problems with msdosfs In-reply-to: Your message of "Sat, 21 Mar 1998 18:32:27 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Mar 1998 02:36:27 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hostas Red wrote: > Still having problems with writing onto msdosfs partition (FAT32). It > reads ok, but when i'm trying to write a couple of files there, system > hangs, and need a reset to reboot. Please compile DDB in kernel, and when it happens, press Ctrl-Alt-Esc, say "trace" on the ddb prompt, and send me the result. I already seen similar reports, but couldn't catch the bug. Thanks Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 15:44:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23253 for freebsd-current-outgoing; Sat, 21 Mar 1998 15:44:37 -0800 (PST) (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 PAA23247; Sat, 21 Mar 1998 15:44:34 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA04221; Sat, 21 Mar 1998 18:44:37 -0500 (EST) (envelope-from toor) Message-Id: <199803212344.SAA04221@dyson.iquest.net> Subject: Re: Be careful, looking good In-Reply-To: <19980322095625.59024@freebie.lemis.com> from Greg Lehey at "Mar 22, 98 09:56:25 am" To: grog@lemis.com (Greg Lehey) Date: Sat, 21 Mar 1998 18:44:36 -0500 (EST) Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Greg Lehey said: > On Sat, 21 March 1998 at 10:22:49 -0500, John S. Dyson wrote: > > I am not going to make any further comments about this latest > > fiasco about -current, except some testing by me and others > > is showing that it is looking okay. The filesystem corruption > > looks like it is gone now. > > > > No guarantees, just be careful. Don't assume that it is > > perfect. > > Fine. Somebody (Karl) mentioned hangs and spontaneous reboots a day > or two ago. Any comments on them? > We aren't sure where they are coming from. -- 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 Mar 21 15:47:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24033 for freebsd-current-outgoing; Sat, 21 Mar 1998 15:47:52 -0800 (PST) (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 PAA24019 for ; Sat, 21 Mar 1998 15:47:42 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA04236; Sat, 21 Mar 1998 18:47:38 -0500 (EST) (envelope-from toor) Message-Id: <199803212347.SAA04236@dyson.iquest.net> Subject: Re: CURRENT Kernel Status In-Reply-To: <199803212200.PAA06995@usr09.primenet.com> from Terry Lambert at "Mar 21, 98 10:00:18 pm" To: tlambert@primenet.com (Terry Lambert) Date: Sat, 21 Mar 1998 18:47:38 -0500 (EST) Cc: root@danberlin.resnet.rochester.edu, karl@mcs.net, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Terry Lambert said: > > I know that fsck will not necessarily be able to return the disk > to the state that it would have been without the failure, but it > should be possible for it to return it to a self-consistent state. > > If it can't, then we need to fix it (IMO). > Excellent!!! A project to keep Terry out of trouble :-). -- 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 Mar 21 16:29:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28969 for freebsd-current-outgoing; Sat, 21 Mar 1998 16:29:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28962 for ; Sat, 21 Mar 1998 16:29:15 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from bonsai.hiwaay.net (tnt3-9.HiWAAY.net [208.147.146.9]) by fly.HiWAAY.net (8.8.8/8.8.6) with SMTP id SAA21924 for ; Sat, 21 Mar 1998 18:29:11 -0600 (CST) Message-ID: <35145B61.41C67EA6@hiwaay.net> Date: Sat, 21 Mar 1998 18:29:21 -0600 From: Steve Price X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: panic: cannot mount root Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I finally decided to try a March 12th kernel and have been unsuccessful in getting it to work. Here is my /etc/fstab for a kernel from around February 25th. $ cat /etc/fstab /dev/wd0a / ufs rw 1 1 /dev/wd0s2 none swap sw 0 0 proc /proc procfs rw 0 0 /dev/wcd0c /cdrom cd9660 ro,noauto 0 0 /dev/wd1s1 /u ufs rw 1 1 $ I have tried changing /dev/wd0a to /dev/wd0s1 but to no avail. The really odd thing is that the kernel says something like this on startup setting root_device to /dev/wd0s2a As can be seen from above /dev/wd0s2 is my swap device and I didn't know a beast like /dev/wd0s2a even existed (at least /etc/MAKEDEV doesn't create it). What am I missing? Thanks, Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 16:35:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29584 for freebsd-current-outgoing; Sat, 21 Mar 1998 16:35:00 -0800 (PST) (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 QAA29570 for ; Sat, 21 Mar 1998 16:34:56 -0800 (PST) (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 AAA28449; Sun, 22 Mar 1998 00:34:51 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id BAA29569; Sun, 22 Mar 1998 01:34:49 +0100 (MET) Message-ID: <19980322013448.19287@follo.net> Date: Sun, 22 Mar 1998 01:34:48 +0100 From: Eivind Eklund To: Steve Price , current@FreeBSD.ORG Subject: Re: panic: cannot mount root References: <35145B61.41C67EA6@hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <35145B61.41C67EA6@hiwaay.net>; from Steve Price on Sat, Mar 21, 1998 at 06:29:21PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 21, 1998 at 06:29:21PM -0600, Steve Price wrote: > Hi All, > > I finally decided to try a March 12th kernel and > have been unsuccessful in getting it to work. Here > is my /etc/fstab for a kernel from around February > 25th. It seems OK to run true -current now. > $ cat /etc/fstab > /dev/wd0a / ufs rw 1 1 > /dev/wd0s2 none swap sw 0 0 > proc /proc procfs rw 0 0 > /dev/wcd0c /cdrom cd9660 ro,noauto 0 0 > /dev/wd1s1 /u ufs rw 1 1 > $ > > I have tried changing /dev/wd0a to /dev/wd0s1 but > to no avail. You want /dev/wd0s1a for the above case, I guess. > The really odd thing is that the > kernel says something like this on startup > > setting root_device to /dev/wd0s2a This is due to a bug in the kernel. If I understood correctly, it is fairly hard to fix properly (and doesn't have any ill effects). It only affect what is printed. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 16:53:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02170 for freebsd-current-outgoing; Sat, 21 Mar 1998 16:53:12 -0800 (PST) (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 QAA02157; Sat, 21 Mar 1998 16:53:08 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id TAA00249; Sat, 21 Mar 1998 19:53:10 -0500 (EST) (envelope-from toor) Message-Id: <199803220053.TAA00249@dyson.iquest.net> Subject: Re: John's latest round of changes In-Reply-To: <19980321171116.21165@mcs.net> from Karl Denninger at "Mar 21, 98 05:11:16 pm" To: karl@mcs.net (Karl Denninger) Date: Sat, 21 Mar 1998 19:53:10 -0500 (EST) Cc: scottm@cs.ucla.edu, freebsd-current@FreeBSD.ORG, scsi@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Karl Denninger said: > One other thing - it appears that the CAM patches with John's fixes are > SERIOUSLY unstable. Without CAM John's latest commits appear to fix the > stability and disk corruption problems. > > With CAM the corruption doesn't happen, but stability is in the toilet. > I'll grab a copy of Justin's patches. I don't have any SCSI hard drives (yet), so can only do limited testing with a CDROM. -- 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 Mar 21 16:55:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02775 for freebsd-current-outgoing; Sat, 21 Mar 1998 16:55:27 -0800 (PST) (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 QAA02710 for ; Sat, 21 Mar 1998 16:55:21 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id TAA00257; Sat, 21 Mar 1998 19:55:28 -0500 (EST) (envelope-from toor) Message-Id: <199803220055.TAA00257@dyson.iquest.net> Subject: Re: John's latest round of changes In-Reply-To: <199803212152.NAA00417@mordred.cs.ucla.edu> from Scott Michel at "Mar 21, 98 01:52:43 pm" To: scottm@cs.ucla.edu (Scott Michel) Date: Sat, 21 Mar 1998 19:55:28 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Scott Michel said: > I've been running a CVSup'd kernel from yesterday, relatively trouble > free. I'd concur with John: it seems OK for the moment, but be prepared > to back out at a moment's notice. > > Do not use soft updates. That's still pretty unstable (although I've > yet to get a decent panic and traceback -- machine spontaneously > reboots under load.) > I have been finding numerous little problems with softupdates. Most of 'em are nits, but bad enough to crash the system at times. As I find them, I have been committing fixes. So far, they has been little interface problems regarding assumptions made by Kirk, and changes made in our usage. I haven't found any bugs in the softupdates code per-se lately though. -- 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 Mar 21 17:02:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04222 for freebsd-current-outgoing; Sat, 21 Mar 1998 17:02:31 -0800 (PST) (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 RAA04145; Sat, 21 Mar 1998 17:02:15 -0800 (PST) (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 LAA17263; Sun, 22 Mar 1998 11:32:05 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id LAA00116; Sun, 22 Mar 1998 11:32:05 +1030 (CST) (envelope-from grog) Message-ID: <19980322113204.33738@freebie.lemis.com> Date: Sun, 22 Mar 1998 11:32:04 +1030 From: Greg Lehey To: dyson@FreeBSD.ORG, Karl Denninger Cc: scottm@cs.ucla.edu, freebsd-current@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: John's latest round of changes References: <19980321171116.21165@mcs.net> <199803220053.TAA00249@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803220053.TAA00249@dyson.iquest.net>; from John S. Dyson on Sat, Mar 21, 1998 at 07:53:10PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 21 March 1998 at 19:53:10 -0500, John S. Dyson wrote: > Karl Denninger said: >> One other thing - it appears that the CAM patches with John's fixes are >> SERIOUSLY unstable. Without CAM John's latest commits appear to fix the >> stability and disk corruption problems. >> >> With CAM the corruption doesn't happen, but stability is in the toilet. >> > I'll grab a copy of Justin's patches. I don't have any SCSI hard drives > (yet), so can only do limited testing with a CDROM. Can't some kind soul lend John a SCSI drive or two? It looks like it would be a good investment. Yes, I would, but the shipping would cost more than the value of 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 Sat Mar 21 17:05:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05172 for freebsd-current-outgoing; Sat, 21 Mar 1998 17:05:14 -0800 (PST) (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 RAA05165; Sat, 21 Mar 1998 17:05:10 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id TAA01108; Sat, 21 Mar 1998 19:05:10 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id TAA27629; Sat, 21 Mar 1998 19:05:10 -0600 (CST) Message-ID: <19980321190510.26472@mcs.net> Date: Sat, 21 Mar 1998 19:05:10 -0600 From: Karl Denninger To: Greg Lehey Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Be careful, looking good References: <199803211522.KAA03910@dyson.iquest.net> <19980322095625.59024@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980322095625.59024@freebie.lemis.com>; from Greg Lehey on Sun, Mar 22, 1998 at 09:56:25AM +1030 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 22, 1998 at 09:56:25AM +1030, Greg Lehey wrote: > On Sat, 21 March 1998 at 10:22:49 -0500, John S. Dyson wrote: > > I am not going to make any further comments about this latest > > fiasco about -current, except some testing by me and others > > is showing that it is looking okay. The filesystem corruption > > looks like it is gone now. > > > > No guarantees, just be careful. Don't assume that it is > > perfect. > > Fine. Somebody (Karl) mentioned hangs and spontaneous reboots a day > or two ago. Any comments on them? > > Greg They're still open as issues; I am trying to produce a set of conditions that reliably reproduces these problems. For the hangs, that's where you have to start (since you don't get a dump and can't trap to DDB) One new issue is that the CAM code (if you use it) appears to have some bad interactions with the fixed -CURRENT. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 17:07:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05872 for freebsd-current-outgoing; Sat, 21 Mar 1998 17:07:55 -0800 (PST) (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 RAA05852; Sat, 21 Mar 1998 17:07:51 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id TAA01164; Sat, 21 Mar 1998 19:07:47 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id TAA27658; Sat, 21 Mar 1998 19:07:46 -0600 (CST) Message-ID: <19980321190746.28923@mcs.net> Date: Sat, 21 Mar 1998 19:07:46 -0600 From: Karl Denninger To: dyson@FreeBSD.ORG Cc: scottm@cs.ucla.edu, freebsd-current@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: John's latest round of changes References: <19980321171116.21165@mcs.net> <199803220053.TAA00249@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199803220053.TAA00249@dyson.iquest.net>; from John S. Dyson on Sat, Mar 21, 1998 at 07:53:10PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 21, 1998 at 07:53:10PM -0500, John S. Dyson wrote: > Karl Denninger said: > > One other thing - it appears that the CAM patches with John's fixes are > > SERIOUSLY unstable. Without CAM John's latest commits appear to fix the > > stability and disk corruption problems. > > > > With CAM the corruption doesn't happen, but stability is in the toilet. > > > I'll grab a copy of Justin's patches. I don't have any SCSI hard drives > (yet), so can only do limited testing with a CDROM. Note that one patch to ccd.c has an offset problem with the latest version (no big deal, but you have to go fix it up manually) and the patch to autoconf.c is just plain broken (but doesn't hurt to leave out). -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 17:09:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06291 for freebsd-current-outgoing; Sat, 21 Mar 1998 17:09:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org ([195.166.142.168]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06272; Sat, 21 Mar 1998 17:08:56 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.7/8.8.7) with ESMTP id BAA28490; Sun, 22 Mar 1998 01:01:12 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199803220101.BAA28490@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: dyson@FreeBSD.ORG cc: grog@lemis.com (Greg Lehey), current@FreeBSD.ORG Subject: Re: Be careful, looking good In-reply-to: Your message of "Sat, 21 Mar 1998 18:44:36 EST." <199803212344.SAA04221@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Mar 1998 01:01:11 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Greg Lehey said: > > On Sat, 21 March 1998 at 10:22:49 -0500, John S. Dyson wrote: > > > I am not going to make any further comments about this latest > > > fiasco about -current, except some testing by me and others > > > is showing that it is looking okay. The filesystem corruption > > > looks like it is gone now. > > > > > > No guarantees, just be careful. Don't assume that it is > > > perfect. > > > > Fine. Somebody (Karl) mentioned hangs and spontaneous reboots a day > > or two ago. Any comments on them? > > > We aren't sure where they are coming from. I got a freeze running with code from 4-5 hours ago (code from ~19:00GMT). I was running X at the time - I can't tell you anything :-( I'll install more com ports in my -release machine and use one as a console for my -current machine soon - sorry the info is pretty useless. > -- > 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. -- 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 Sat Mar 21 17:37:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11744 for freebsd-current-outgoing; Sat, 21 Mar 1998 17:37:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11721 for ; Sat, 21 Mar 1998 17:37:46 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from bonsai.hiwaay.net (tnt3-132.HiWAAY.net [208.147.146.132]) by fly.HiWAAY.net (8.8.8/8.8.6) with SMTP id TAA04884; Sat, 21 Mar 1998 19:37:37 -0600 (CST) Message-ID: <35146B6A.41C67EA6@hiwaay.net> Date: Sat, 21 Mar 1998 19:37:46 -0600 From: Steve Price X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Eivind Eklund CC: current@FreeBSD.ORG Subject: Re: panic: cannot mount root References: <35145B61.41C67EA6@hiwaay.net> <19980322013448.19287@follo.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund wrote: > > You want /dev/wd0s1a for the above case, I guess. Still doesn't work right. Here is a more detailed version of what I am seeing. ... changing root device to wd0s2a ... Filesytem mount failed, startup aborted. ... # /sbin/mount /dev/wd0s1 / /dev/wd0s1 on /: Specified device does not match mounted device. # /sbin/mount /dev/wd0s1a / /dev/wd0s1a on /: No such file or directory # /sbin/mount /dev/wd0s1 /mnt WARNING: R/W mount of / denied. Filesystem is not clean - run fsck. /dev/wd0s1 on /mnt: Operation not permitted # Yet if I revert to an older kernel everything works fine. And yes the root_device is clean so running fsck is not required with this older kernel. Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 17:59:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13377 for freebsd-current-outgoing; Sat, 21 Mar 1998 17:59:07 -0800 (PST) (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 RAA13369 for ; Sat, 21 Mar 1998 17:59:00 -0800 (PST) (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 0yGa2D-000332-00; Sat, 21 Mar 1998 19:58:49 -0600 X-Mailer: exmh version 2.0zeta 7/24/97 To: Steve Price cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: panic: cannot mount root In-reply-to: Your message of "Sat, 21 Mar 1998 19:37:46 CST." <35146B6A.41C67EA6@hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Mar 1998 19:58:48 -0600 From: Ted Spradley Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Filesytem mount failed, startup aborted. > ... > # /sbin/mount /dev/wd0s1 / > /dev/wd0s1 on /: Specified device does not match mounted device. > # /sbin/mount /dev/wd0s1a / > /dev/wd0s1a on /: No such file or directory Is there a /dev/wd0s1a ? If not, you need to upgrade your /dev/MAKEDEV from /usr/src/etc/etc.i386/MAKEDEV (and /dev/MAKEDEV.local from /usr/src/etc/MAKEDEV.local) and run (cd /dev; sh ./MAKEDEV all) to make sure wd0s1[a-h] exist. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 18:14:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15286 for freebsd-current-outgoing; Sat, 21 Mar 1998 18:14:51 -0800 (PST) (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 SAA15281 for ; Sat, 21 Mar 1998 18:14:48 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 12187 invoked from network); 22 Mar 1998 02:20:49 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 22 Mar 1998 02:20:49 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-031798 [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: <35146B6A.41C67EA6@hiwaay.net> Date: Sat, 21 Mar 1998 18:20:49 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Steve Price Subject: Re: panic: cannot mount root Cc: current@FreeBSD.ORG, Eivind Eklund Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Mar-98 Steve Price wrote: > Eivind Eklund wrote: >> >> You want /dev/wd0s1a for the above case, I guess. > > Still doesn't work right. Here is a more detailed version > of what I am seeing. > > ... > changing root device to wd0s2a > ... > Filesytem mount failed, startup aborted. > ... ># /sbin/mount /dev/wd0s1 / > /dev/wd0s1 on /: Specified device does not match mounted device. ># /sbin/mount /dev/wd0s1a / > /dev/wd0s1a on /: No such file or directory ># /sbin/mount /dev/wd0s1 /mnt > WARNING: R/W mount of / denied. Filesystem is not clean - run fsck. > /dev/wd0s1 on /mnt: Operation not permitted This is easy. cd /dev;./MAKEDEV wds1a Make sure you have, in /dev: brw-r----- 1 root operator 0, 0x00020002 Mar 21 18:20 /dev/wd0s1 brw-r----- 1 root operator 0, 0x00020000 Mar 21 18:20 /dev/wd0s1a brw-r----- 1 root operator 0, 0x00020001 Mar 21 18:20 /dev/wd0s1b brw-r----- 1 root operator 0, 0x00020002 Mar 21 18:20 /dev/wd0s1c brw-r----- 1 root operator 0, 0x00020003 Mar 21 18:20 /dev/wd0s1d brw-r----- 1 root operator 0, 0x00020004 Mar 21 18:20 /dev/wd0s1e brw-r----- 1 root operator 0, 0x00020005 Mar 21 18:20 /dev/wd0s1f brw-r----- 1 root operator 0, 0x00020006 Mar 21 18:20 /dev/wd0s1g brw-r----- 1 root operator 0, 0x00020007 Mar 21 18:20 /dev/wd0s1h ># > > Yet if I revert to an older kernel everything works > fine. And yes the root_device is clean so running > fsck is not required with this older kernel. > > Steve > > 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 Sat Mar 21 18:18:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15868 for freebsd-current-outgoing; Sat, 21 Mar 1998 18:18:54 -0800 (PST) (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 SAA15863 for ; Sat, 21 Mar 1998 18:18:51 -0800 (PST) (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 SAA07284; Sat, 21 Mar 1998 18:13:51 -0800 (PST) Message-Id: <199803220213.SAA07284@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ted Spradley cc: Steve Price , Eivind Eklund , current@FreeBSD.ORG Subject: Re: panic: cannot mount root In-reply-to: Your message of "Sat, 21 Mar 1998 19:58:48 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Mar 1998 18:13:49 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Filesytem mount failed, startup aborted. > > ... > > # /sbin/mount /dev/wd0s1 / > > /dev/wd0s1 on /: Specified device does not match mounted device. > > # /sbin/mount /dev/wd0s1a / > > /dev/wd0s1a on /: No such file or directory > > Is there a /dev/wd0s1a ? If not, you need to upgrade your /dev/MAKEDEV > from /usr/src/etc/etc.i386/MAKEDEV (and /dev/MAKEDEV.local from > /usr/src/etc/MAKEDEV.local) and run (cd /dev; sh ./MAKEDEV all) to make > sure wd0s1[a-h] exist. This won't create it. # cd /dev # ./MAKEDEV wd0s1a will create wd0s1[a-h]. The original plaintiff will also want to update /sbin/mount. -- \\ 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 Sat Mar 21 18:21:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16188 for freebsd-current-outgoing; Sat, 21 Mar 1998 18:21:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16182 for ; Sat, 21 Mar 1998 18:21:16 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from bonsai.hiwaay.net (tnt3-132.HiWAAY.net [208.147.146.132]) by fly.HiWAAY.net (8.8.8/8.8.6) with SMTP id UAA17572; Sat, 21 Mar 1998 20:21:03 -0600 (CST) Message-ID: <35147598.167EB0E7@hiwaay.net> Date: Sat, 21 Mar 1998 20:21:13 -0600 From: Steve Price X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Ted Spradley CC: current@FreeBSD.ORG Subject: Re: panic: cannot mount root References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Spradley wrote: > > Is there a /dev/wd0s1a ? If not, you need to upgrade your /dev/MAKEDEV > from /usr/src/etc/etc.i386/MAKEDEV (and /dev/MAKEDEV.local from > /usr/src/etc/MAKEDEV.local) and run (cd /dev; sh ./MAKEDEV all) to make > sure wd0s1[a-h] exist. I cvsup'd from freefall about an hour ago and did just that. I still don't get any wd0s1* devices. root[/dev]# ls -l wd0* brw-r----- 1 root operator 0, 0x00010002 Mar 21 20:07 wd0 brw-r----- 1 root operator 0, 0 Mar 21 20:07 wd0a brw-r----- 1 root operator 0, 1 Mar 21 20:07 wd0b brw-r----- 1 root operator 0, 2 Mar 21 20:07 wd0c brw-r----- 1 root operator 0, 3 Mar 21 20:07 wd0d brw-r----- 1 root operator 0, 4 Mar 21 20:07 wd0e brw-r----- 1 root operator 0, 5 Mar 21 20:07 wd0f brw-r----- 1 root operator 0, 6 Mar 21 20:07 wd0g brw-r----- 1 root operator 0, 7 Mar 21 20:07 wd0h brw-r----- 1 root operator 0, 0x00020002 Mar 21 20:07 wd0s1 brw-r----- 1 root operator 0, 0x00030002 Mar 21 20:07 wd0s2 brw-r----- 1 root operator 0, 0x00040002 Mar 21 20:07 wd0s3 brw-r----- 1 root operator 0, 0x00050002 Mar 21 20:07 wd0s4 root[/dev]# To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 18:21:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16365 for freebsd-current-outgoing; Sat, 21 Mar 1998 18:21:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16347 for ; Sat, 21 Mar 1998 18:21:37 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id SAA10407; Sat, 21 Mar 1998 18:21:18 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Sat, 21 Mar 1998 18:21:17 -0800 (PST) From: Chris Timmons To: Martin Machacek cc: freebsd-current@FreeBSD.ORG Subject: Re: problem with samba on 3.0 In-Reply-To: <199803191524.HAA03885@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just upgraded to 1.9.18p3 of samba on -current with a pre-mayhem "safe" kernel that happily runs the last pre-1.9.18 alpha of samba. BLAM! I'm running into a floating point exception (signal 8) here: #0 0x12648 in put_long_date (p=0x8d03d "", t=890531747) at time.c:297 297 tlow = (uint32)(d - ((double)thigh)*4.0*(double)(1<<30)); Do you see signal 8's in your dmesg? -Chris On Thu, 19 Mar 1998, Martin Machacek wrote: > I've a strange problem with samba-1.9.18.3 port on FreeBSD-3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 18:23:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16899 for freebsd-current-outgoing; Sat, 21 Mar 1998 18:23:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16894 for ; Sat, 21 Mar 1998 18:23:51 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from bonsai.hiwaay.net (tnt3-132.HiWAAY.net [208.147.146.132]) by fly.HiWAAY.net (8.8.8/8.8.6) with SMTP id UAA17174; Sat, 21 Mar 1998 20:23:45 -0600 (CST) Message-ID: <3514763A.2781E494@hiwaay.net> Date: Sat, 21 Mar 1998 20:23:54 -0600 From: Steve Price X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: shimon@simon-shapiro.org CC: current@FreeBSD.ORG Subject: Re: panic: cannot mount root References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Simon Shapiro wrote: > > This is easy. > > cd /dev;./MAKEDEV wds1a > > Make sure you have, in /dev: > > brw-r----- 1 root operator 0, 0x00020002 Mar 21 18:20 /dev/wd0s1 > brw-r----- 1 root operator 0, 0x00020000 Mar 21 18:20 /dev/wd0s1a > brw-r----- 1 root operator 0, 0x00020001 Mar 21 18:20 /dev/wd0s1b > brw-r----- 1 root operator 0, 0x00020002 Mar 21 18:20 /dev/wd0s1c > brw-r----- 1 root operator 0, 0x00020003 Mar 21 18:20 /dev/wd0s1d > brw-r----- 1 root operator 0, 0x00020004 Mar 21 18:20 /dev/wd0s1e > brw-r----- 1 root operator 0, 0x00020005 Mar 21 18:20 /dev/wd0s1f > brw-r----- 1 root operator 0, 0x00020006 Mar 21 18:20 /dev/wd0s1g > brw-r----- 1 root operator 0, 0x00020007 Mar 21 18:20 /dev/wd0s1h > Yes, that did it. :) Now I'm off to reboot again and see what comes of it. Thanks, Steve > ---------- > > 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 Sat Mar 21 18:31:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18644 for freebsd-current-outgoing; Sat, 21 Mar 1998 18:31:33 -0800 (PST) (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 SAA18615 for ; Sat, 21 Mar 1998 18:31:29 -0800 (PST) (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 NAA17331; Sun, 22 Mar 1998 13:01:16 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id NAA00344; Sun, 22 Mar 1998 13:01:16 +1030 (CST) (envelope-from grog) Message-ID: <19980322130115.17589@freebie.lemis.com> Date: Sun, 22 Mar 1998 13:01:15 +1030 From: Greg Lehey To: Karl Denninger Cc: FreeBSD current users Subject: Re: John's latest round of changes References: <19980321171116.21165@mcs.net> <199803220053.TAA00249@dyson.iquest.net> <19980321190746.28923@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980321190746.28923@mcs.net>; from Karl Denninger on Sat, Mar 21, 1998 at 07:07:46PM -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 Sat, 21 March 1998 at 19:07:46 -0600, Karl Denninger wrote: > On Sat, Mar 21, 1998 at 07:53:10PM -0500, John S. Dyson wrote: >> Karl Denninger said: >>> One other thing - it appears that the CAM patches with John's fixes are >>> SERIOUSLY unstable. Without CAM John's latest commits appear to fix the >>> stability and disk corruption problems. >>> >>> With CAM the corruption doesn't happen, but stability is in the toilet. >>> >> I'll grab a copy of Justin's patches. I don't have any SCSI hard drives >> (yet), so can only do limited testing with a CDROM. > > Note that one patch to ccd.c has an offset problem with the latest version > (no big deal, but you have to go fix it up manually) and the patch to > autoconf.c is just plain broken (but doesn't hurt to leave out). Which ccd patch is that? There was one with a big offset that did the rounds a while ago which was just plain incorrect. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 18:32:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19131 for freebsd-current-outgoing; Sat, 21 Mar 1998 18:32:56 -0800 (PST) (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 SAA19126 for ; Sat, 21 Mar 1998 18:32:54 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id UAA03324; Sat, 21 Mar 1998 20:32:51 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id UAA28289; Sat, 21 Mar 1998 20:32:51 -0600 (CST) Message-ID: <19980321203250.62692@mcs.net> Date: Sat, 21 Mar 1998 20:32:51 -0600 From: Karl Denninger To: Greg Lehey Cc: FreeBSD current users Subject: Re: John's latest round of changes References: <19980321171116.21165@mcs.net> <199803220053.TAA00249@dyson.iquest.net> <19980321190746.28923@mcs.net> <19980322130115.17589@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <19980322130115.17589@freebie.lemis.com>; from Greg Lehey on Sun, Mar 22, 1998 at 01:01:15PM +1030 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 22, 1998 at 01:01:15PM +1030, Greg Lehey wrote: > On Sat, 21 March 1998 at 19:07:46 -0600, Karl Denninger wrote: > > On Sat, Mar 21, 1998 at 07:53:10PM -0500, John S. Dyson wrote: > >> Karl Denninger said: > >>> One other thing - it appears that the CAM patches with John's fixes are > >>> SERIOUSLY unstable. Without CAM John's latest commits appear to fix the > >>> stability and disk corruption problems. > >>> > >>> With CAM the corruption doesn't happen, but stability is in the toilet. > >>> > >> I'll grab a copy of Justin's patches. I don't have any SCSI hard drives > >> (yet), so can only do limited testing with a CDROM. > > > > Note that one patch to ccd.c has an offset problem with the latest version > > (no big deal, but you have to go fix it up manually) and the patch to > > autoconf.c is just plain broken (but doesn't hurt to leave out). > > Which ccd patch is that? There was one with a big offset that did the > rounds a while ago which was just plain incorrect. > > Greg This is the patch included in the CAM snapshot; if you're not interested in the CAM patches (for SCSI), this is not relavent. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 18:42:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21272 for freebsd-current-outgoing; Sat, 21 Mar 1998 18:42:05 -0800 (PST) (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 SAA21262 for ; Sat, 21 Mar 1998 18:42:01 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 912 invoked from network); 22 Mar 1998 02:47:59 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 22 Mar 1998 02:47:59 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-031798 [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: <35147598.167EB0E7@hiwaay.net> Date: Sat, 21 Mar 1998 18:47:59 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Steve Price Subject: Re: panic: cannot mount root Cc: current@FreeBSD.ORG, Ted Spradley Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You have to do a make world to update stuff so the kernel finds a friendly, compatible environment. Your MAKEDEV is old/wrong for sure. See my other note on this. Simon On 22-Mar-98 Steve Price wrote: > Ted Spradley wrote: >> >> Is there a /dev/wd0s1a ? If not, you need to upgrade your /dev/MAKEDEV >> from /usr/src/etc/etc.i386/MAKEDEV (and /dev/MAKEDEV.local from >> /usr/src/etc/MAKEDEV.local) and run (cd /dev; sh ./MAKEDEV all) to make >> sure wd0s1[a-h] exist. > > I cvsup'd from freefall about an hour ago and did just > that. I still don't get any wd0s1* devices. > > root[/dev]# ls -l wd0* > brw-r----- 1 root operator 0, 0x00010002 Mar 21 20:07 wd0 > brw-r----- 1 root operator 0, 0 Mar 21 20:07 wd0a > brw-r----- 1 root operator 0, 1 Mar 21 20:07 wd0b > brw-r----- 1 root operator 0, 2 Mar 21 20:07 wd0c > brw-r----- 1 root operator 0, 3 Mar 21 20:07 wd0d > brw-r----- 1 root operator 0, 4 Mar 21 20:07 wd0e > brw-r----- 1 root operator 0, 5 Mar 21 20:07 wd0f > brw-r----- 1 root operator 0, 6 Mar 21 20:07 wd0g > brw-r----- 1 root operator 0, 7 Mar 21 20:07 wd0h > brw-r----- 1 root operator 0, 0x00020002 Mar 21 20:07 wd0s1 > brw-r----- 1 root operator 0, 0x00030002 Mar 21 20:07 wd0s2 > brw-r----- 1 root operator 0, 0x00040002 Mar 21 20:07 wd0s3 > brw-r----- 1 root operator 0, 0x00050002 Mar 21 20:07 wd0s4 > root[/dev]# > > 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 Sat Mar 21 18:48:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22072 for freebsd-current-outgoing; Sat, 21 Mar 1998 18:48:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22064 for ; Sat, 21 Mar 1998 18:48:10 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from bonsai.hiwaay.net (tnt2-11.HiWAAY.net [208.147.148.11]) by fly.HiWAAY.net (8.8.8/8.8.6) with SMTP id UAA09149; Sat, 21 Mar 1998 20:47:27 -0600 (CST) Message-ID: <35147BC9.167EB0E7@hiwaay.net> Date: Sat, 21 Mar 1998 20:47:37 -0600 From: Steve Price X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Mike Smith CC: current@FreeBSD.ORG Subject: Filesystem mount failed, startup aborted (was Re: panic: cannot mount root) References: <199803220213.SAA07284@dingo.cdrom.com> 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: > > This won't create it. > > # cd /dev > # ./MAKEDEV wd0s1a > > will create wd0s1[a-h]. > > The original plaintiff will also want to update /sbin/mount. Yes, I did this before I rebooted the first time. :) I am back from rebooting and everything works now. Just for everyone else's sake that may come across this in the future. Here's what I did to get up and going after grabbing a fresh -current tree. cd /usr/src/include; make all install cd /usr/src/sbin/mount; make all install cd /usr/src/sys/conf/i386; config mykernel cd ../../compile/mykernel; make depend all install cd /dev cp /usr/src/etc/MAKEDEV.local . cp /usr/src/etc/etc.i386/MAKEDEV . sh ./MAKEDEV all sh ./MAKEDEV wd0s1a Reboot and viola. You will also want to change /etc/fstab as suggested in the boot messages and 'make world' after you come back up. Many thanks to all who responded! Steve > -- > \\ 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 19:27:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25289 for freebsd-current-outgoing; Sat, 21 Mar 1998 19:27:45 -0800 (PST) (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 TAA25283 for ; Sat, 21 Mar 1998 19:27:42 -0800 (PST) (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 DAA00663; Sun, 22 Mar 1998 03:27:38 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id EAA00397; Sun, 22 Mar 1998 04:27:37 +0100 (MET) Message-ID: <19980322042736.47898@follo.net> Date: Sun, 22 Mar 1998 04:27:36 +0100 From: Eivind Eklund To: Chris Timmons , Martin Machacek Cc: freebsd-current@FreeBSD.ORG Subject: Re: problem with samba on 3.0 References: <199803191524.HAA03885@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Chris Timmons on Sat, Mar 21, 1998 at 06:21:17PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 21, 1998 at 06:21:17PM -0800, Chris Timmons wrote: > > I just upgraded to 1.9.18p3 of samba on -current with a pre-mayhem "safe" > kernel that happily runs the last pre-1.9.18 alpha of samba. > > BLAM! > > I'm running into a floating point exception (signal 8) here: > > #0 0x12648 in put_long_date (p=0x8d03d "", t=890531747) at time.c:297 > 297 tlow = (uint32)(d - ((double)thigh)*4.0*(double)(1<<30)); > > Do you see signal 8's in your dmesg? That's what known as bug-which-is-masked-but-present-otherwhere. It is exposed in FreeBSD, due to our unusual handling of floating point errors. You can hide it by calling fpsetmask() with other flags; that will make the bug silently create wrong results, instead. You should report it to the samba team. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 19:32:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25930 for freebsd-current-outgoing; Sat, 21 Mar 1998 19:32:03 -0800 (PST) (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 TAA25905 for ; Sat, 21 Mar 1998 19:31:58 -0800 (PST) (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 DAA00722; Sun, 22 Mar 1998 03:31:57 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id EAA00422; Sun, 22 Mar 1998 04:31:57 +0100 (MET) Message-ID: <19980322043156.03042@follo.net> Date: Sun, 22 Mar 1998 04:31:56 +0100 From: Eivind Eklund To: Steve Price Cc: current@FreeBSD.ORG Subject: Re: Filesystem mount failed, startup aborted (was Re: panic: cannot mount root) References: <199803220213.SAA07284@dingo.cdrom.com> <35147BC9.167EB0E7@hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <35147BC9.167EB0E7@hiwaay.net>; from Steve Price on Sat, Mar 21, 1998 at 08:47:37PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 21, 1998 at 08:47:37PM -0600, Steve Price wrote: > Mike Smith wrote: > > > > This won't create it. > > > > # cd /dev > > # ./MAKEDEV wd0s1a > > > > will create wd0s1[a-h]. > > > > The original plaintiff will also want to update /sbin/mount. > > Yes, I did this before I rebooted the first time. :) > > I am back from rebooting and everything works now. > Just for everyone else's sake that may come across > this in the future. Here's what I did to get up > and going after grabbing a fresh -current tree. > > cd /usr/src/include; make all install > cd /usr/src/sbin/mount; make all install > cd /usr/src/sys/conf/i386; config mykernel > cd ../../compile/mykernel; make depend all install You don't want to compile things this way. You want each of the special targets to be in a separate run of make. Especially, you want make depend && make && make install for compiling your kernel. The .depend file is not read if you do the compile in the same run of make. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 19:35:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26619 for freebsd-current-outgoing; Sat, 21 Mar 1998 19:35:58 -0800 (PST) (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 TAA26611 for ; Sat, 21 Mar 1998 19:35:54 -0800 (PST) (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 TAA07597; Sat, 21 Mar 1998 19:31:37 -0800 (PST) Message-Id: <199803220331.TAA07597@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Cory Kempf cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: Today's kernel doesn't work on (my) DK440LX In-reply-to: Your message of "Mon, 16 Mar 1998 21:44:33 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Mar 1998 19:31:35 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 23:48 -0500 98.03.14, Mike Smith wrote: > >> My system seems to be dependent on the line: > >> > >> config kernel root on da0 swap on generic > > > >The 'generic' keyword causes a search for suitable devices. Because > >the bootstrap doesn't recognise the 'da' device, it passes 0 in as the > >boot major. > > So, what should I use for the device? And (more importantly) where do I > find this stuff out? You shouldn't care, especially if you just use config kernel on wd0 > If I try sd0 as the device, config returns that it is unrecognized. > > After booting, / is mounted on /dev/da0a, which has a major device number > of 4 and a minor device number of 0. Perhaps da4a will work... It sounds like the CAM code replaces "sd" everywhere with "da". Maybe you haven't updated config? > >The kernel recently started trusting this value; you will need to extend > >the bootstrap so that it supplies it correctly. > > Uh, how do I do that? For that matter, what does that mean? You can ignore the advice; the bootstrap will believe that it is booting from a SCSI disk, but now SCSI disks are called 'da'. > >> In my kernel config file. Especially the 'swap on generic' part. If I > >> take it out, or replace it with anything I have tried so far, my kernel > >> doesn't work at all. If I attempt to boot, the system attempts to change > >> root to wd0s2b, and I get a Fatal Trap 12. Doing a trace says that it is > >> happening in _ffs_mount(). > > > >This is probably because the disk type on your disk is incorrect. What > >does 'disklabel' say about your boot disk? > > # /dev/rda0a: > type: ESDI ... > It lies: The disk is a SCSI device and the RPM is 10,000. You should use 'disklabel -e' to correct ESDI->SCSI. The rpm value is ignored, but you can change it anyway if it offends your sensibilities. 8) The missing SCSI value is the problem here; because the disk is mislabelled, the bootstrap is passing the wrong value in to the kernel, and the kernel is trying to mount the wrong device. Because you have no 'wd' code in your kernel, the attempt to use that driver fails more spectacularly. Sorry for the delay in the response to your problem. -- \\ 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 Sat Mar 21 19:57:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28248 for freebsd-current-outgoing; Sat, 21 Mar 1998 19:57:46 -0800 (PST) (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 TAA28141 for ; Sat, 21 Mar 1998 19:57:31 -0800 (PST) (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 0yGbsY-00038V-00; Sat, 21 Mar 1998 21:56:58 -0600 X-Mailer: exmh version 2.0zeta 7/24/97 To: Mike Smith cc: Steve Price , Eivind Eklund , current@FreeBSD.ORG Subject: Re: panic: cannot mount root In-reply-to: Your message of "Sat, 21 Mar 1998 18:13:49 PST." <199803220213.SAA07284@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Mar 1998 21:56:57 -0600 From: Ted Spradley Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [...] > > Is there a /dev/wd0s1a ? If not, you need to upgrade your /dev/MAKEDEV > > from /usr/src/etc/etc.i386/MAKEDEV (and /dev/MAKEDEV.local from > > /usr/src/etc/MAKEDEV.local) and run (cd /dev; sh ./MAKEDEV all) to make > > sure wd0s1[a-h] exist. > > This won't create it. > > # cd /dev > # ./MAKEDEV wd0s1a Sorry for the misinformation. Will ./MAKEDEV wd0s1a make wd0s1b thru h as well? I just assumed that 'all' would take care of what was needed, but I do recall that ./MAKEDEV sd0s1a did not make sd1s1a. > > will create wd0s1[a-h]. > > The original plaintiff will also want to update /sbin/mount. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 20:39:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02439 for freebsd-current-outgoing; Sat, 21 Mar 1998 20:39:25 -0800 (PST) (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 UAA02425 for ; Sat, 21 Mar 1998 20:39:19 -0800 (PST) (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 XAA22859 for ; Sat, 21 Mar 1998 23:38:44 -0500 (EST) X-Sender: ckempfm@enigami.com Message-Id: In-Reply-To: <19980321171211.55116@mcs.net> References: <199803212200.PAA06995@usr09.primenet.com>; from Terry Lambert on Sat, Mar 21, 1998 at 10:00:18PM +0000 <199803202025.PAA17448@dyson.iquest.net> <199803212200.PAA06995@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 21 Mar 1998 23:33:10 -0500 To: current@FreeBSD.ORG From: Cory Kempf Subject: Where does one report bugs? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I checked out a (mostly) current system, I think. Build world fails, because /usr/src/lib/termcap/termcap.h has a prototype for __set_ospeed(), and tospeed.c in the same directory has a different definition. So, who do I report this to, so the fix can be applied? (the fix being either move the def'n of speed_t from tospeed.c to termcap.h, or change __set_ospeed() to accept an unsigned long). +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 Sat Mar 21 21:02:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05886 for freebsd-current-outgoing; Sat, 21 Mar 1998 21:02:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05878 for ; Sat, 21 Mar 1998 21:02:57 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from bonsai.hiwaay.net (tnt2-103.HiWAAY.net [208.147.148.103]) by fly.HiWAAY.net (8.8.8/8.8.6) with SMTP id XAA29723; Sat, 21 Mar 1998 23:02:50 -0600 (CST) Message-ID: <35149B84.446B9B3D@hiwaay.net> Date: Sat, 21 Mar 1998 23:03:00 -0600 From: Steve Price X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Cory Kempf CC: current@FreeBSD.ORG, bde@zeta.org.au Subject: Re: Where does one report bugs? References: <199803212200.PAA06995@usr09.primenet.com>; from Terry Lambert on Sat, Mar 21, 1998 at 10:00:18PM +0000 <199803202025.PAA17448@dyson.iquest.net> <199803212200.PAA06995@usr09.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cory Kempf wrote: > > I checked out a (mostly) current system, I think. > > Build world fails, because /usr/src/lib/termcap/termcap.h has a prototype > for __set_ospeed(), and tospeed.c in the same directory has a different > definition. > > So, who do I report this to, so the fix can be applied? (the fix being > either move the def'n of speed_t from tospeed.c to termcap.h, or change > __set_ospeed() to accept an unsigned long). > To report a bug use http://www.freebsd.org/send-pr.html The attached patch seems to fix the problem. Steve Index: tospeed.c =================================================================== RCS file: /u/FreeBSD/cvs/src/lib/libtermcap/tospeed.c,v retrieving revision 1.2 diff -u -r1.2 tospeed.c --- tospeed.c 1995/08/05 21:22:02 1.2 +++ tospeed.c 1998/03/22 04:58:02 @@ -52,7 +52,7 @@ {-1, -1} }; -void __set_ospeed(speed_t speed) +void __set_ospeed(unsigned long speed) { struct stable *stable; > +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 Sat Mar 21 21:40:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09304 for freebsd-current-outgoing; Sat, 21 Mar 1998 21:40:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09283 for ; Sat, 21 Mar 1998 21:40:29 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA24645; Sun, 22 Mar 1998 16:39:31 +1100 Date: Sun, 22 Mar 1998 16:39:31 +1100 From: Bruce Evans Message-Id: <199803220539.QAA24645@godzilla.zeta.org.au> To: ckempf@enigami.com, sprice@hiwaay.net Subject: Re: Where does one report bugs? Cc: bde@zeta.org.au, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I checked out a (mostly) current system, I think. >> >> Build world fails, because /usr/src/lib/termcap/termcap.h has a prototype >> for __set_ospeed(), and tospeed.c in the same directory has a different >> definition. Update to a (fully) current system where there is no incompatibility (except in termcap.3. Oops). You also need an up to date >To report a bug use http://www.freebsd.org/send-pr.html >The attached patch seems to fix the problem. >... >Index: tospeed.c >=================================================================== >RCS file: /u/FreeBSD/cvs/src/lib/libtermcap/tospeed.c,v >retrieving revision 1.2 >diff -u -r1.2 tospeed.c >--- tospeed.c 1995/08/05 21:22:02 1.2 >+++ tospeed.c 1998/03/22 04:58:02 >@@ -52,7 +52,7 @@ > {-1, -1} > }; > >-void __set_ospeed(speed_t speed) >+void __set_ospeed(unsigned long speed) > { > struct stable *stable; > No, it hides the problem :-). The arg type is supposed to be speed_t, but speed_t is not visible in . Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Mar 21 22:10:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12141 for freebsd-current-outgoing; Sat, 21 Mar 1998 22:10:38 -0800 (PST) (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 WAA12094 for ; Sat, 21 Mar 1998 22:10:35 -0800 (PST) (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 BAA23140; Sun, 22 Mar 1998 01:08:18 -0500 (EST) X-Sender: ckempfm@enigami.com Message-Id: In-Reply-To: <199803220539.QAA24645@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 22 Mar 1998 01:02:29 -0500 To: Bruce Evans , sprice@hiwaay.net From: Cory Kempf Subject: Re: Where does one report bugs? Cc: bde@zeta.org.au, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 00:39 -0500 98.03.22, Bruce Evans wrote: >>> I checked out a (mostly) current system, I think. >>> >>> Build world fails, because /usr/src/lib/termcap/termcap.h has a prototype >>> for __set_ospeed(), and tospeed.c in the same directory has a different >>> definition. > >Update to a (fully) current system where there is no incompatibility No can do: I need CAM, from the postings here, CAM and -current are not playing nice yet. So SYS is still at 12 March, possibly everything after that line as well (don't grok cvsup *that* well yet...) In any case, the bad version was present long enough to do a build world, have it die and re-update (on the off chance that someone was in the middle of doing an update when I checked out, although it did rather seem like a long shot -- I can't think of a good reason for speed_t to be defined in the .c file!) I made the Q&D fix (changed to ulong) and am still compiling, so haven't looked to see if it is fixed in the source tree yet. +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