From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 01:18:27 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6F471065674 for ; Sun, 6 Jul 2008 01:18:27 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: from mail7.sea5.speakeasy.net (mail7.sea5.speakeasy.net [69.17.117.9]) by mx1.freebsd.org (Postfix) with ESMTP id BFB828FC0C for ; Sun, 6 Jul 2008 01:18:27 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: (qmail 14580 invoked from network); 6 Jul 2008 01:18:27 -0000 Received: from april.chuckr.org (HELO april.telenix.org) (chuckr@[66.92.151.30]) (envelope-sender ) by mail7.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 6 Jul 2008 01:18:27 -0000 Message-ID: <48701AA2.3010907@telenix.org> Date: Sat, 05 Jul 2008 21:06:42 -0400 From: Chuck Robey User-Agent: Thunderbird 2.0.0.6 (X11/20071107) MIME-Version: 1.0 To: Robert Watson References: <486FD2BA.8050505@telenix.org> <20080705220254.I51796@fledge.watson.org> In-Reply-To: <20080705220254.I51796@fledge.watson.org> X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: kernel modules wont load X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 01:18:28 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robert Watson wrote: > > On Sat, 5 Jul 2008, Chuck Robey wrote: > >> I can't get my oss sound to load, and the first error I get is this: >> >> osscore.ko: depends on kernel - not available >> >> That came from both the oss logging file and dmesg. I don't >> understand what "depends on kernel" means, could I get a hint on >> that? I think it's the reason that later oss modules don't load >> correctly. >> >> Thanks for any help on this, I'd like to get my sound working again. > > In HEAD, we're currently building all modules with an automatic version > dependency on the version of the kernel they are intended to run in. > The error message should be telling you need version X but it found > version Y, but doesn't, unfortunately. Rebuilding the module should get > it working. I seem to recall printing the error better is awkward > because the dependency failure is generated somewhere deep in the > linker, and the error is printed on the surface, but should be fixable. Umm. OK, I'm pleased to hear about it, but just a touch skeptical that's my problem, because I recompiled the osscore 2 hours ago, and the kernel is less than 2 weeks old. It is possible, though, and I really appreciate the answer (I'd never have tracked that one down, from your description). > > Robert N M Watson > Computer Laboratory > University of Cambridge > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhwGqEACgkQz62J6PPcoOmZ1ACfSV12S7iLVWzAAM0356KxDLcC Ux8AoKK4GtUMFyIVSHlS5e/J93I+z0Xu =E2+z -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 07:27:02 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A49191065681; Sun, 6 Jul 2008 07:27:02 +0000 (UTC) (envelope-from mtm@wubethiopia.com) Received: from dire.wubethiopia.com (j071.v.rootbsd.net [208.79.82.223]) by mx1.freebsd.org (Postfix) with ESMTP id 74F848FC0C; Sun, 6 Jul 2008 07:27:02 +0000 (UTC) (envelope-from mtm@wubethiopia.com) Received: from rogue.mike.lan (unknown [213.55.87.239]) by dire.wubethiopia.com (Postfix) with ESMTPSA id 616304FD97EE; Sun, 6 Jul 2008 07:25:56 +0000 (UTC) Message-ID: <487074AA.20103@wubethiopia.com> Date: Sun, 06 Jul 2008 10:30:50 +0300 From: Mike Makonnen User-Agent: Thunderbird 2.0.0.12 (X11/20080323) MIME-Version: 1.0 To: Robert Watson References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486F8C57.9050908@wubethiopia.com> <20080705161614.O19209@fledge.watson.org> In-Reply-To: <20080705161614.O19209@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Lothar Braun , freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 07:27:02 -0000 Robert Watson wrote: > On Sat, 5 Jul 2008, Mike Makonnen wrote: > >> The installer can already install a basic FreeBSD system (including >> the ports collection) from CD, UFS, or DOS partition. I'm currently >> working on getting FTP/HTTP/NFS installation to work. Next on my list >> after that is setting Date and Time Zone. At that stage the installer >> will be more or less feature-complete, and I can start code cleanup, >> getting it to work on additional architectures, etc. I had initially >> intended to include package installation as one of the criteria for >> feature-completeness, but after reading through this thread I've >> decided not to use sysinstall's package installation code and instead >> write one from scratch once I'm happy with the rest of the installer. > > Sounds pretty much in line with what I was looking for. However, I > think I would like to see it be a bit more complete than sysinstall in > the area of geom partition labeling (concat/strip/raid/encryption), > and perhaps also ZFS support. I realize that adds complexity a fair > amount, but one of the biggest areas of feature lack in sysinstall > today is that you are basically stuck with the original BSD partition > structure and UFS, whereas we expect increasing numbers of users to > deploy ZFS. We don't have boot support currently, but being able to > set up /data as a ZFS file system would be great. Today, people have > to do an initial install on, say, a small boot partition and then > relabel/deal with the rest of the disk, boot a live CD, or worse, > discover they have to repartition, which really fails to expose some > of the excellent ease-of-use, auto-configuration, etc, features that > we otherwise have in this area. I agree absolutely. I should have said ".... more or less feature-complete for a 1.0 release". Cheers. -- Mike Makonnen | GPG-KEY: http://people.freebsd.org/~mtm/mtm.asc mtm @ FreeBSD.Org | AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55 FreeBSD | http://www.freebsd.org From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 07:37:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA1581065676; Sun, 6 Jul 2008 07:37:15 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 499118FC19; Sun, 6 Jul 2008 07:37:15 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (adsl135-103.kln.forthnet.gr [77.49.254.103]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-4) with ESMTP id m667Wivw020286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 6 Jul 2008 10:32:50 +0300 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.2/8.14.2) with ESMTP id m667Wi6l037727; Sun, 6 Jul 2008 10:32:44 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.2/8.14.2/Submit) id m667Wg1h037693; Sun, 6 Jul 2008 10:32:42 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) From: Giorgos Keramidas To: Holger Kipp References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <486BFE3B.3040509@gmail.com> <486C0928.8050607@yahoo.fr> <20080703085629.GA1590@intserv.int1.b.intern> Date: Sun, 06 Jul 2008 10:32:41 +0300 In-Reply-To: <20080703085629.GA1590@intserv.int1.b.intern> (Holger Kipp's message of "Thu, 3 Jul 2008 10:56:29 +0200") Message-ID: <877ibzlb6u.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: m667Wivw020286 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.758, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.64, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, jan6146@gmail.com, Curtis Penner , Antoine BRUNEL Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 07:37:16 -0000 On Thu, 3 Jul 2008 10:56:29 +0200, Holger Kipp wrote: > Dear Antoine Brunel, > > I completely 100% agree. Actually I don't see the need for a new > sysinstall. It does what it needs to do. I have seen the later > RH- and SUSE-Installer, but I don't want them. What's the use of > a graphical installer? Graphical installers are not useless. They usually 'look' easier for the average user. They may not always _be_ easier to use, but it is often the first impression that counts. Localization tends to be easier for GUI installers too. Now, it may seem pretty useless for someone who knows English already, but a *lot* of people feel more comfortable with an installer that speaks their native language. After the installation is finished, English may be a lot more useful (think "manpages", for instance). But it still 'looks' nicer to be able to install in one's native language. > I am more than happy with sysinstall, have used it for years (starting > with 2.2.8 actually) and don't want to see a colorful chingeling > whistleblowing hard-to-maintain suitable for all graphics card gui > installer. Agreed :) From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 07:47:45 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A7F61065679; Sun, 6 Jul 2008 07:47:45 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 6C6268FC15; Sun, 6 Jul 2008 07:47:38 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (adsl135-103.kln.forthnet.gr [77.49.254.103]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-4) with ESMTP id m667lQw3020831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 6 Jul 2008 10:47:32 +0300 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.2/8.14.2) with ESMTP id m667lQY4060324; Sun, 6 Jul 2008 10:47:26 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.2/8.14.2/Submit) id m667lP9D060229; Sun, 6 Jul 2008 10:47:25 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) From: Giorgos Keramidas To: "Aggelidis Nikos" References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <486DA7FC.8050304@math.missouri.edu> <784966050807032138g7ed2da8chf15f185a6a6bf302@mail.gmail.com> <486DB3CB.9000906@infoweapons.com> <30fc78250807032338p2388be7ax56e1ae38aaafadd8@mail.gmail.com> Date: Sun, 06 Jul 2008 10:47:25 +0300 In-Reply-To: <30fc78250807032338p2388be7ax56e1ae38aaafadd8@mail.gmail.com> (Aggelidis Nikos's message of "Fri, 4 Jul 2008 09:38:37 +0300") Message-ID: <873amnlaia.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: m667lQw3020831 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.759, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.64, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 07:47:45 -0000 On Fri, 4 Jul 2008 09:38:37 +0300, "Aggelidis Nikos" wrote: >> I'm sorry I started a kind of flame war. All I wanted was two >> things: 1. CD's that installed without being switched in and out >> dozens of times. That was fixed by the suggestion of using a DVD. I >> didn't even know the DVD install existed, but will do that next time. > > I also had the same problem {cd switching} to get around it, i created > an installation DVD with all the contents of cd1-2-3. You can find > such guide Hi Nikos :) The DVD-ROM doesn't even have to be bootable. Just collecting all the `packages/All/*' files from the CD-ROMs in a single directory makes it much easier to run: # cd /nfs/blah ; pkg_add vim* From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 07:51:30 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A9E4106567A; Sun, 6 Jul 2008 07:51:30 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 9BCA38FC0A; Sun, 6 Jul 2008 07:51:29 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (adsl135-103.kln.forthnet.gr [77.49.254.103]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-4) with ESMTP id m667pDY0020980 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 6 Jul 2008 10:51:19 +0300 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.2/8.14.2) with ESMTP id m667pDg9087563; Sun, 6 Jul 2008 10:51:13 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.2/8.14.2/Submit) id m667pCND087309; Sun, 6 Jul 2008 10:51:12 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) From: Giorgos Keramidas To: "Paul B. Mahol" References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <868wwhhmms.fsf@ds4.des.no> <486E14F2.3060906@psg.com> <3a142e750807040531k27938f0ay9bd9923ec57f3f1@mail.gmail.com> Date: Sun, 06 Jul 2008 10:51:10 +0300 In-Reply-To: <3a142e750807040531k27938f0ay9bd9923ec57f3f1@mail.gmail.com> (Paul B. Mahol's message of "Fri, 4 Jul 2008 14:31:51 +0200") Message-ID: <87y74fjvrl.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: m667pDY0020980 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.759, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.64, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: Randy Bush , Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , freebsd-current@freebsd.org, Rob Lytle , freebsd-hackers@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 07:51:30 -0000 On Fri, 4 Jul 2008 14:31:51 +0200, "Paul B. Mahol" wrote: > On 7/4/08, Randy Bush wrote: >>> This is why there are precompiled packages on ftp.freebsd.org which you >>> can install with 'pkg_add -r'. You can install them from any FTP >>> mirror, actually; just point PACKAGEROOT at the mirror: >> >> why isn't this stuff in the docs? oh, it is! silly me. is the problem >> that there are just too much doc or two little reading? >> >> > > It is in pkg_add(1), If you are talking about handbook only > PACKAGESITE is documented: should get fixed. Hi Paul, Can you please open a docs/* problem report for this? Feel free to add `keramida' to the `X-GNATS-Notify:' header. I'll try to add at least a reference to pkg_add(1) to read more about the `PACKAGEROOT' environment variable. I'm just getting back from a 8-10 day period of ${offline_world} stuff, but it would be a shame to lose the opportunity to document this, because it got hidden in the `noise' of the mailing lists. From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 08:00:50 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 719F21065676; Sun, 6 Jul 2008 08:00:50 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id D2A388FC18; Sun, 6 Jul 2008 08:00:49 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (adsl135-103.kln.forthnet.gr [77.49.254.103]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-4) with ESMTP id m6680akp021381 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 6 Jul 2008 11:00:42 +0300 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.2/8.14.2) with ESMTP id m6680aAW039270; Sun, 6 Jul 2008 11:00:36 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.2/8.14.2/Submit) id m6680a8u039269; Sun, 6 Jul 2008 11:00:36 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) From: Giorgos Keramidas To: "Paul B. Mahol" References: <784966050807022128g6a6ebfebtc1f57c0da66779bc@mail.gmail.com> <20080703215537.6F3114504E@ptavv.es.net> <784966050807032126m69eedb98nf0ccaed548fc96ef@mail.gmail.com> <868wwhhmms.fsf@ds4.des.no> <486E14F2.3060906@psg.com> <3a142e750807040531k27938f0ay9bd9923ec57f3f1@mail.gmail.com> <87y74fjvrl.fsf@kobe.laptop> Date: Sun, 06 Jul 2008 11:00:36 +0300 In-Reply-To: <87y74fjvrl.fsf@kobe.laptop> (Giorgos Keramidas's message of "Sun, 06 Jul 2008 10:51:10 +0300") Message-ID: <87bq1bigrf.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: m6680akp021381 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.759, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.64, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: Randy Bush , Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , freebsd-current@freebsd.org, Rob Lytle , freebsd-hackers@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 08:00:50 -0000 On Sun, 06 Jul 2008 10:51:10 +0300, Giorgos Keramidas wrote: > On Fri, 4 Jul 2008 14:31:51 +0200, "Paul B. Mahol" wrote: >> On 7/4/08, Randy Bush wrote: >>>> This is why there are precompiled packages on ftp.freebsd.org which you >>>> can install with 'pkg_add -r'. You can install them from any FTP >>>> mirror, actually; just point PACKAGEROOT at the mirror: >>> >>> why isn't this stuff in the docs? oh, it is! silly me. is the problem >>> that there are just too much doc or two little reading? >>> >>> >> >> It is in pkg_add(1), If you are talking about handbook only >> PACKAGESITE is documented: should get fixed. > > Hi Paul, > > Can you please open a docs/* problem report for this? Feel free to add > `keramida' to the `X-GNATS-Notify:' header. I'll try to add at least a > reference to pkg_add(1) to read more about the `PACKAGEROOT' environment > variable. Nevermind, that was easy. I just opened a PR for it... From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 08:16:43 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC3A41065673 for ; Sun, 6 Jul 2008 08:16:43 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id BA27F8FC1D for ; Sun, 6 Jul 2008 08:16:43 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so1045812wah.3 for ; Sun, 06 Jul 2008 01:16:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=epC2q333q2UKso6u0GY9Gv1rRJSLH3uHuvpAK038xlk=; b=LimdROHfOopg/TwRPIz3/Uo3DQoazYpewfG16M04+MC/t7BoE9BfBhVp2XNSQ7X2fe tYGaOu8bNTKs2uoZe33gry5sU7gyAYCVexzATiGV7tUGAcTeR7HxlgllnyWCs42URM9s WFkPlLje3J1ssYURt/vu9Qaaf9f1BBNuRv9zU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=TQ05kZQyutqBGz5vNL0weZXucCt2DiskpDJ7eEXegUu+01odIWztq8UNxIKDU6z5X8 c8yiWBPKcuelLodTru2E+tgtx2ZgU6ynXCFVy3JPM/7z++XqUOWJlZSpaBh8Gkop6Q3X KQhGMsqkNz0D85z11TXirTot1H5lxSxppQtWA= Received: by 10.114.38.2 with SMTP id l2mr5090689wal.200.1215332203230; Sun, 06 Jul 2008 01:16:43 -0700 (PDT) Received: by 10.115.78.5 with HTTP; Sun, 6 Jul 2008 01:16:43 -0700 (PDT) Message-ID: Date: Sun, 6 Jul 2008 12:16:43 +0400 From: "Vladimir Ermakov" To: "Sam Leffler" In-Reply-To: <486F91CC.60009@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <486F91CC.60009@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: wireless access point is don`t scaning X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 08:16:44 -0000 On Sat, Jul 5, 2008 at 7:22 PM, Sam Leffler wrote: > Vladimir Ermakov wrote: >> >> Hello >> >> after creation access point, she is don`t scaning >> >> outputs: >> ============================================================= >> # ifconfig -a >> re0: flags=8843 metric 0 mtu 1500 >> >> options=399b >> ether 00:1e:90:88:92:85 >> inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255 >> media: Ethernet autoselect (100baseTX ) >> status: active >> ath0: flags=8843 metric 0 mtu 2290 >> ether 00:11:6b:63:47:12 >> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g >> status: running >> lo0: flags=8049 metric 0 mtu 16384 >> inet 127.0.0.1 netmask 0xff000000 >> wlan0: flags=8843 metric 0 mtu >> 2290 >> ether 00:11:6b:63:47:12 >> inet 192.168.5.1 netmask 0xffffff00 broadcast 192.168.5.255 >> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g >> status: running >> ssid ora channel 6 (2437 Mhz 11g) bssid 00:11:6b:63:47:12 >> country US ecm authmode WPA privacy MIXED deftxkey 2 TKIP 2:128-bit >> TKIP 3:128-bit txpower 18.5 scanvalid 60 protmode CTS wme burst ff >> dturbo dtimperiod 1 -dfs >> >> # ifconfig wlan0 up scan >> # >> # uname -a >> FreeBSD 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Fri Jul 4 20:01:51 MSD >> 2008 root@:/usr/obj/usr/src/sys/GRAVICAPA i386 >> ============================================================= >> >> messages output: >> ============================================================= >> Jul 5 13:02:05 kernel: wlan0: ieee80211_ioctl_scanreq: flags 0x13 >> duration 0x7fffffff mindwell 0 maxdwell 0 nssid 0 >> Jul 5 13:02:05 kernel: wlan0: start_scan_locked: active scan, >> duration 2147483647 mindwell 0 maxdwell 0, desired mode auto, append, >> nopick, once >> Jul 5 13:02:05 kernel: wlan0: scan set 6g dwell min 200 max 200 >> Jul 5 13:02:05 kernel: wlan0: scan_next: chan 6g -> 6g [active, >> dwell min 200 max 200] >> Jul 5 13:02:05 kernel: wlan0: send probe req on channel 6 bssid >> ff:ff:ff:ff:ff:ff ssid "" >> Jul 5 13:02:05 kernel: wlan0: scan_next: done, [ticks 5242290, dwell >> min 200 scanend 2152725736] >> Jul 5 13:02:05 kernel: wlan0: notify scan done >> ============================================================= >> >> please, any solution? > > The "scan set" lists only channel 6. Looks like you locked down the > channel. > > Sam > thx this my mistake hostap is working and scanning from remote system P.S. - (ath0 & wlan0) both interfaces have status `running` /Vladimir Ermakov From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 11:01:03 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52682106567D; Sun, 6 Jul 2008 11:01:03 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.freebsd.org (Postfix) with ESMTP id 79EF98FC15; Sun, 6 Jul 2008 11:01:02 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=ywGvsW0yCX0A:10 a=be0l799Llq4A:10 a=NMGBx6iLSXY/3qZKdJo9Bw==:17 a=FZ1FRupOBxy0YMaDUWIA:9 a=9tZDJXQOZ6AjPMbABJUKDsc6k1sA:4 a=50e4U0PicR4A:10 Received: from [62.113.135.207] (account mc467741@c2i.net [62.113.135.207] verified) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 1003480341; Sun, 06 Jul 2008 13:00:52 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sun, 6 Jul 2008 13:02:27 +0200 User-Agent: KMail/1.9.7 References: <20080704191043.87CFE5B4B@mail.bitblocks.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807061302.28853.hselasky@c2i.net> Cc: gnn@freebsd.org, current@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 11:01:03 -0000 Hi, Maybe you have some piece of hardware in the box that does not support 32 address lines. You were using 4GB of RAM? I've seen USB controllers for example that does not support more than 2GB of ram, even though the OHCI, UHCI and EHCI specifications are all 32-bits at least. And when you program a too high addresses things go wrong simply put :-) --HPS From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 11:01:03 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52682106567D; Sun, 6 Jul 2008 11:01:03 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.freebsd.org (Postfix) with ESMTP id 79EF98FC15; Sun, 6 Jul 2008 11:01:02 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=ywGvsW0yCX0A:10 a=be0l799Llq4A:10 a=NMGBx6iLSXY/3qZKdJo9Bw==:17 a=FZ1FRupOBxy0YMaDUWIA:9 a=9tZDJXQOZ6AjPMbABJUKDsc6k1sA:4 a=50e4U0PicR4A:10 Received: from [62.113.135.207] (account mc467741@c2i.net [62.113.135.207] verified) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 1003480341; Sun, 06 Jul 2008 13:00:52 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sun, 6 Jul 2008 13:02:27 +0200 User-Agent: KMail/1.9.7 References: <20080704191043.87CFE5B4B@mail.bitblocks.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807061302.28853.hselasky@c2i.net> Cc: gnn@freebsd.org, current@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 11:01:03 -0000 Hi, Maybe you have some piece of hardware in the box that does not support 32 address lines. You were using 4GB of RAM? I've seen USB controllers for example that does not support more than 2GB of ram, even though the OHCI, UHCI and EHCI specifications are all 32-bits at least. And when you program a too high addresses things go wrong simply put :-) --HPS From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 11:54:18 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E510E1065672 for ; Sun, 6 Jul 2008 11:54:18 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.9]) by mx1.freebsd.org (Postfix) with ESMTP id 995218FC12 for ; Sun, 6 Jul 2008 11:54:18 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail01.m-online.net (mail.m-online.net [192.168.3.149]) by mail-out.m-online.net (Postfix) with ESMTP id B142143BE0F; Sun, 6 Jul 2008 13:54:40 +0200 (CEST) Received: from localhost (unknown [192.168.1.157]) by mail.m-online.net (Postfix) with ESMTP id B96779038C; Sun, 6 Jul 2008 13:54:16 +0200 (CEST) X-Virus-Scanned: amavisd-new at mnet-online.de Received: from localhost ([192.168.3.149]) by localhost (scanner1.m-online.net [192.168.1.157]) (amavisd-new, port 10024) with ESMTP id hm66LQbjSBBq; Sun, 6 Jul 2008 13:54:15 +0200 (CEST) Received: from mail.reifenberger.com (ppp-88-217-84-251.dynamic.mnet-online.de [88.217.84.251]) by mail.mnet-online.de (Postfix) with ESMTP; Sun, 6 Jul 2008 13:54:15 +0200 (CEST) Received: by mail.reifenberger.com (Postfix, from userid 1001) id EBB4821B5; Sun, 6 Jul 2008 13:54:14 +0200 (CEST) Date: Sun, 6 Jul 2008 13:54:14 +0200 From: Michael Reifenberger To: Patrick =?iso-8859-15?Q?Lamaizi=E8re?= Message-ID: <20080706115414.GA20076@gw.reifenberger.com> References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20080606234135.46144207@baby-jane-lamaiziere-net.local> User-Agent: Mutt/1.4.2.3i Priority: normal Cc: current@freebsd.org Subject: Re: AMD Geode LX crypto accelerator (glxsb) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 11:54:19 -0000 Hi, On Fri, Jun 06, 2008 at 11:41:35PM +0200, Patrick Lamaizière wrote: > Dears, > > I'm trying to port the glxsb driver from OpenBSD to FreeBSD 7-STABLE > (via the NetBSD port). > " The glxsb driver supports the security block of the Geode LX > series processors. The Geode LX is a member of the AMD Geode family > of integrated x86 system chips. > Is allready one of the FreeBSD developers working on integrating your ported driver into HEAD? -- Bye/2 --- Michael Reifenberger Michael@Reifenberger.com http://www.Reifenberger.com From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 12:00:51 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29041106567F for ; Sun, 6 Jul 2008 12:00:51 +0000 (UTC) (envelope-from duncan.young@pobox.com) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id DA9E48FC1B for ; Sun, 6 Jul 2008 12:00:50 +0000 (UTC) (envelope-from duncan.young@pobox.com) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 8AFD6136E9D for ; Sun, 6 Jul 2008 07:43:21 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Sun, 06 Jul 2008 07:43:21 -0400 X-Sasl-enc: DfydEm8+qKWEFm56Q2r9NhAGfYlDckdCl66Qs8p1FJ9i 1215344600 Received: from triple0.qld.optushome.com.au (c122-108-168-198.rochd4.qld.optusnet.com.au [122.108.168.198]) by mail.messagingengine.com (Postfix) with ESMTPSA id DABF41397B for ; Sun, 6 Jul 2008 07:43:20 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by triple0.qld.optushome.com.au (Postfix) with ESMTP id 9B468C09F4 for ; Sun, 6 Jul 2008 21:43:15 +1000 (EST) From: Duncan Young To: freebsd-current@freebsd.org Date: Sun, 6 Jul 2008 21:43:12 +1000 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807062143.14016.duncan.young@pobox.com> Subject: zfs and glabel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: duncan.young@pobox.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 12:00:51 -0000 Hi all I believe I'm having a few problems with using geom to label disks and then use them in zfs. # zpool status rootzfs pool: rootzfs state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM rootzfs ONLINE 0 0 0 mirror ONLINE 0 0 0 label/sysdisk_A ONLINE 0 0 0 label/sysdisk_B ONLINE 0 0 0 errors: No known data errors # glabel status Name Status Components label/bootdisk_A N/A ad0s1a label/swap_A N/A ad0s1b label/sysdisk_A N/A ad0s1d label/bootdisk_B N/A ad2s1a label/swap_B N/A ad2s1b label/sysdisk_B N/A ad2s1d # gmirror status Name Status Components mirror/swap_AB COMPLETE label/swap_A label/swap_B # swapinfo Device 1K-blocks Used Avail Capacity /dev/mirror/swap_AB 4194300 158224 4036076 4% # mount -t ufs /dev/label/bootdisk_A on /bootdirA (ufs, local) /dev/label/bootdisk_B on /bootdirB (ufs, local) As can be seen I have the boot disk set up with separate /boot partitions (independent of each other), mirrored swap and the rest of the root file system in zfs. Currently I am watching the following appearing every second or two in the messages file: kernel: vdev_geom_detach:177[1]: Closing access to label/sysdisk_B. kernel: vdev_geom_detach:177[1]: Closing access to label/sysdisk_A. kernel: vdev_geom_detach:181[1]: Destroyed consumer to label/sysdisk_A. kernel: vdev_geom_detach:177[1]: Closing access to label/sysdisk_B. kernel: vdev_geom_detach:181[1]: Destroyed consumer to label/sysdisk_B. kernel: vdev_geom_open:371[1]: Found provider by name /dev/label/sysdisk_A. kernel: vdev_geom_attach:116[1]: Attaching to label/sysdisk_A. kernel: vdev_geom_attach:157[1]: Created consumer for label/sysdisk_A. kernel: vdev_geom_open:385[1]: ID match for provider /dev/label/sysdisk_A. kernel: vdev_geom_open:371[1]: Found provider by name /dev/label/sysdisk_B. kernel: vdev_geom_attach:116[1]: Attaching to label/sysdisk_B. kernel: vdev_geom_attach:157[1]: Created consumer for label/sysdisk_B. kernel: vdev_geom_open:385[1]: ID match for provider /dev/label/sysdisk_B. much of the time only one disk is "lost" at a time. I also get "kernel: ZFS WARNING: Cannot open ad2 for writting" (also for ad0) upon imports etc. I'm running 7.0-RELEASE-p2 on amd64. I also have another raidz set of 6 disks, but I don't use labels on them and have no messages as a result. Any suggestions if I should be concerned or not. I also have periodic lockups (under load) which I believe are zfs related, but I have only just set up the serial console and I am waiting to get a crash dump. regards Duncan From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 12:18:25 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C706710656CA for ; Sun, 6 Jul 2008 12:18:25 +0000 (UTC) (envelope-from duncan.young@pobox.com) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 7DC228FC1A for ; Sun, 6 Jul 2008 12:18:25 +0000 (UTC) (envelope-from duncan.young@pobox.com) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id CED0913739A for ; Sun, 6 Jul 2008 08:18:24 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 06 Jul 2008 08:18:24 -0400 X-Sasl-enc: MG5t/OLGaIKW+QtIuWb/gyZtU1wF177qVhI3DMVrr+5j 1215346704 Received: from triple0.qld.optushome.com.au (c122-108-168-198.rochd4.qld.optusnet.com.au [122.108.168.198]) by mail.messagingengine.com (Postfix) with ESMTPSA id 31FA1FE2A for ; Sun, 6 Jul 2008 08:18:24 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by triple0.qld.optushome.com.au (Postfix) with ESMTP id 80B26B25C7 for ; Sun, 6 Jul 2008 22:18:21 +1000 (EST) From: Duncan Young To: freebsd-current@freebsd.org Date: Sun, 6 Jul 2008 22:18:20 +1000 User-Agent: KMail/1.9.7 References: <200807062143.14016.duncan.young@pobox.com> In-Reply-To: <200807062143.14016.duncan.young@pobox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807062218.20956.duncan.young@pobox.com> Subject: Re: zfs and glabel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: duncan.young@pobox.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 12:18:26 -0000 Forgot to mention, all these messages are a result of vfs.zfs.debug=1, so should I assume this is normal behaviour?? The "Cannot open ad2 for writting" occur regardless of the debug setting. regards Duncan On Sun, 6 Jul 2008 09:43:12 pm Duncan Young wrote: > Hi all > > I believe I'm having a few problems with using geom to label disks and then > use them in zfs. > > # zpool status rootzfs > pool: rootzfs > state: ONLINE > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > rootzfs ONLINE 0 0 0 > mirror ONLINE 0 0 0 > label/sysdisk_A ONLINE 0 0 0 > label/sysdisk_B ONLINE 0 0 0 > > errors: No known data errors > > > # glabel status > Name Status Components > label/bootdisk_A N/A ad0s1a > label/swap_A N/A ad0s1b > label/sysdisk_A N/A ad0s1d > label/bootdisk_B N/A ad2s1a > label/swap_B N/A ad2s1b > label/sysdisk_B N/A ad2s1d > > # gmirror status > Name Status Components > mirror/swap_AB COMPLETE label/swap_A > label/swap_B > > # swapinfo > Device 1K-blocks Used Avail Capacity > /dev/mirror/swap_AB 4194300 158224 4036076 4% > > # mount -t ufs > /dev/label/bootdisk_A on /bootdirA (ufs, local) > /dev/label/bootdisk_B on /bootdirB (ufs, local) > > > As can be seen I have the boot disk set up with separate /boot partitions > (independent of each other), mirrored swap and the rest of the root file > system in zfs. > > Currently I am watching the following appearing every second or two in the > messages file: > kernel: vdev_geom_detach:177[1]: Closing access to label/sysdisk_B. > kernel: vdev_geom_detach:177[1]: Closing access to label/sysdisk_A. > kernel: vdev_geom_detach:181[1]: Destroyed consumer to label/sysdisk_A. > kernel: vdev_geom_detach:177[1]: Closing access to label/sysdisk_B. > kernel: vdev_geom_detach:181[1]: Destroyed consumer to label/sysdisk_B. > kernel: vdev_geom_open:371[1]: Found provider by name /dev/label/sysdisk_A. > kernel: vdev_geom_attach:116[1]: Attaching to label/sysdisk_A. > kernel: vdev_geom_attach:157[1]: Created consumer for label/sysdisk_A. > kernel: vdev_geom_open:385[1]: ID match for provider /dev/label/sysdisk_A. > kernel: vdev_geom_open:371[1]: Found provider by name /dev/label/sysdisk_B. > kernel: vdev_geom_attach:116[1]: Attaching to label/sysdisk_B. > kernel: vdev_geom_attach:157[1]: Created consumer for label/sysdisk_B. > kernel: vdev_geom_open:385[1]: ID match for provider /dev/label/sysdisk_B. > > much of the time only one disk is "lost" at a time. > > I also get "kernel: ZFS WARNING: Cannot open ad2 for writting" (also for > ad0) upon imports etc. > > I'm running 7.0-RELEASE-p2 on amd64. > > I also have another raidz set of 6 disks, but I don't use labels on them > and have no messages as a result. > > Any suggestions if I should be concerned or not. > > I also have periodic lockups (under load) which I believe are zfs related, > but I have only just set up the serial console and I am waiting to get a > crash dump. > > regards > > Duncan From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 14:10:30 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 608841065695 for ; Sun, 6 Jul 2008 14:10:30 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 18B148FC13 for ; Sun, 6 Jul 2008 14:10:29 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so746610ywe.13 for ; Sun, 06 Jul 2008 07:10:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=1OHXu3+0LomwLKbMYB3xF5dfuVHIJsNMSCFqz99hr3Q=; b=hVv1mr/ZKQPwlNvzEPTRfkgq5SlGG2mEdliq13kVJPg8zOEoNBx+wWzR3m3I5lqwgJ ZuL1rC8ODOnN2YaLy+Giv/77DxT3N/bvtK20kOrfP9JYZ9ANp8MvkNQsih6clwaHRaKI E4ypYt7GWgr4Emnl+TELEwqIXKvXHQhrhMnJg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=H7DeztGimGtXymwmkJ7aAwLbKSi+4bOAObWaQ7UD6/+mo1C80iXl/kqa4wzzcd7U+o h/S6b2Wbd7mbct3E/B5rIsHYd4yBJUAdi7DKaFsKoR1GbFpJLXQjpYZX8qltn6kbWoRX M+l9utYTADJDdLLcKmxaRMuhGvsBmhu4osFxs= Received: by 10.151.155.19 with SMTP id h19mr6161185ybo.36.1215351912772; Sun, 06 Jul 2008 06:45:12 -0700 (PDT) Received: by 10.150.178.1 with HTTP; Sun, 6 Jul 2008 06:45:12 -0700 (PDT) Message-ID: <2fd864e0807060645j65b67f97s5dc1e81145660c9d@mail.gmail.com> Date: Sun, 6 Jul 2008 21:45:12 +0800 From: Astrodog To: "gnn@freebsd.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: current@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 14:10:30 -0000 On 7/5/08, gnn@freebsd.org wrote: > Hi, > > I've been working on the following brain teasing (breaking?) problem > for about a week now. What I'm seeing is that on large memory > machines, those with more than 4G of RAM, the ungzipping/untarring of > files fails due to gzip thinking the file is corrupt. The way to > reproduce this is: > > 1) Create a bunch of gzip/tar balls in the 1-20MB range. > 2) Reboot FreeBSD 7.0 release > 3) Run gzip -t over all the files. > > I have hundreds of these files to run this over, and a full check > takes about 3 hours, but I usually see some form of corruption within > the first 20 minutes. > > Other important factors: > > 1) This is on very modern, 2P/4Core (8 cores total) hardware > 2) The disks are 1TB SATA set up in JBOD. > 3) The machines have 16G of RAM. > 4) Corruption is seen only after a reboot, if the machines continue to > run corruption is never seen again, until another reboot. > 5) The systems are all Xeon running amd64 > 6) The disk controller is an AMCC 9650, but we do see this very rarely > with the on board controlller. > 7) All boards are > > http://www.supermicro.com/products/motherboard/Xeon1333/5400/X7DWU.cfm > > 8) All machines have 3 1TB drives. > 9) The corruption is in 4K chunks. That is N x 4K. > 10) Files are not normally corrupted on disk, but this can happen. > > I have already tried a few of the obvious things, such as making sure > that we sync pages before we shutdown the twa driver. > > Given what I have seen I believe this is something that happens from > startup, and not at shutdown. > > Thoughts? > > Best, > George > As a datapoint for you, I use a number of the 9650s with 15 750GB or 1TB drives, on a Supermicro motherboard with Opteron processors and 4GB of memory. With this configuration I have not experienced any data corruption. --- Harrison From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 15:04:21 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEFA41065676; Sun, 6 Jul 2008 15:04:21 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from fallbackmx09.syd.optusnet.com.au (fallbackmx09.syd.optusnet.com.au [211.29.132.242]) by mx1.freebsd.org (Postfix) with ESMTP id B90C68FC12; Sun, 6 Jul 2008 15:04:20 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by fallbackmx09.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m651x1wY009059; Sat, 5 Jul 2008 11:59:01 +1000 Received: from c220-239-252-11.carlnfd3.nsw.optusnet.com.au (c220-239-252-11.carlnfd3.nsw.optusnet.com.au [220.239.252.11]) by mail02.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m651wYda023278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Jul 2008 11:58:37 +1000 Date: Sat, 5 Jul 2008 11:58:34 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Ed Schouten In-Reply-To: <20080704092244.GY14567@hoeg.nl> Message-ID: <20080705095912.M12433@delplex.bde.org> References: <20080702190901.GS14567@hoeg.nl> <20080703193406.GS29380@server.vk2pj.dyndns.org> <20080703205220.GW14567@hoeg.nl> <20080704022125.GA32475@server.vk2pj.dyndns.org> <20080704092244.GY14567@hoeg.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Sun, 06 Jul 2008 15:49:23 +0000 Cc: Peter Jeremy , FreeBSD Current , FreeBSD Arch Subject: Re: MPSAFE TTY schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 15:04:21 -0000 On Fri, 4 Jul 2008, Ed Schouten wrote: >>>> cy(4), digi(4), rp(4), rc(4), si(4). >>> >>> Who actually owns one of these devices? If you do, please contact me. If >>> I didn't make myself clear enough: I *am* willing to (assist in >>> porting|port) these drivers. I have 24 ports on cy devices, but don't use them except for testing. >> I have access to a Digi Xem boards at work and have poked around >> inside the digi(4) code in the past. My difficulty is that the cards >> are all in use and upgrading to a FreeBSD-current that doesn't support >> them and then porting the driver is probably not an option (whereas >> converting it from using shims to access the TTY layer to doing so >> directly would probably be acceptable - because I can get the board >> going again in a hurry if needed). > > The problem with the old TTY layer, is that drivers tend to access the > internals of the TTY structure very often. A good example of this is the > clists, where TTY drivers tamper around inside the clist and cblock > structures. There is not much room to implement a compatibility layer > there. This is a very bad example. Clist accesses are, or should be, a non- problem. No (non-broken) tty drivers access the internals of clists directly, except for read-only accesses to the character count (c_cc), which isn't clist-specific. All of them use the old KPI functions (putc/getc/b_to_q/q_to_b, etc) for accessing the tty queues, and the implementation of the tty queues can be changed to anything without any KPI changes except possibly to the spelling of c_cc. Non-drivers like slip and ppp have slightly more clist-specific knowledge, but again their interface is limited mainly to the KPI (clist_alloc_cblocks, ...) and a read-only character count (cfreecount). if_sl.c still has has a lot of comments about its knowledge of clists, but these barely apply since its implementation only depends on an adequate buffering mechanism for characters (not sure if the characters need to be quotable). Driver-specific locking for clists is even less of a problem. No driver-specific locking is needed for the calls, since they are locked (using spl or Giant) in clist internals. The direct accesses to c_cc should be locked in the same way, but missing locking for these is almost harmless since the accesses are read-only and reading a stale value is usually harmless. Internal locking at each entry point of the KPI encourages unlocked accesses to c_cc, since c_cc becomes volatile immediately after releasing the internal lock. In practice, things like t_oproc() routines use higher-level locking so that there is no race and the internal locking in getc/q_to_b is bogus: xxxstart: /* * Lock whole loop. Without this, getc()'s access to c_cc would * give the same race as our direct access after getc() unlocks. * With this, getc()'s locking is just a waste of time (it's * recursive so that this isn't fatal, so the waste of time * hopefully isn't very large, but this requires recursive locking * to be used all over, so there are time and robustness costs all * over). * spltty(); /* Or Giant in bad drivers. */ /* * Non-Giant locking at a higher level than here might be OK, or * might not, depending on whether the driver wants very fine-grained * locking. If this is done, then we can remove all these fine- * grained spl lock calls in drivers instead of replacing them by * a tty lock. Meanwhile, the spls serve as placeholders to remind * us where to put the tty locks. */ while (tp->t_outq.c_cc != 0 && /* XXX efficiency hack. */ (ch = getc(&tp->t_outq)) != -1) move_ch_to_driver_buffer(...) splx(); A possibly better way to handle this is to accept losing races on the read-only variable but ensure that the driver is woken up without much delay if the variable changes. This already happens in most or all cases, since changing c_cc requires action to process the new state The number of KPI and c_cc accesses is also very small. In most drivers it consists of a whole 1 getc or q_to_b call in t_oproc() and a whole 1 c_cc read to avoid this call. A few drivers implement a bulk input routine that bypasses t_rint() in the TS_CAN_BYPASS_L_RINT case. This requires 1 b_to_q call and 1 c_cc read to implement flow control. This should be in the tty layer. It doesn't break the clist layering but it breaks the tty layering. slip and ppp make much heavier use of the KPI by count of the number of calls (about 5 putc's, 2 unputc's.... each). By churning the KPI, you create a lot of work. Bruce From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 21:58:39 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CC821065681 for ; Sun, 6 Jul 2008 21:58:39 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [91.121.44.19]) by mx1.freebsd.org (Postfix) with ESMTP id CD43A8FC13 for ; Sun, 6 Jul 2008 21:58:38 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from baby-jane.lamaiziere.net (27.6.192-77.rev.gaoland.net [77.192.6.27]) by smtp.lamaiziere.net (Postfix) with ESMTPA id CD6B0633655; Sun, 6 Jul 2008 21:42:31 +0000 (UTC) Received: from baby-jane-lamaiziere-net.local (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id 36C6C55E9A8; Sun, 6 Jul 2008 23:42:33 +0200 (CEST) Date: Sun, 6 Jul 2008 23:42:31 +0200 From: Patrick =?ISO-8859-15?Q?Lamaizi=E8re?= To: Michael Reifenberger Message-ID: <20080706234231.3d18e15a@baby-jane-lamaiziere-net.local> In-Reply-To: <20080706115414.GA20076@gw.reifenberger.com> References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> <20080706115414.GA20076@gw.reifenberger.com> Organization: /dave/nulle X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i386-apple-darwin9.3.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Cc: current@freebsd.org Subject: Re: AMD Geode LX crypto accelerator (glxsb) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 21:58:39 -0000 Le Sun, 6 Jul 2008 13:54:14 +0200, Michael Reifenberger a écrit : Hi, > On Fri, Jun 06, 2008 at 11:41:35PM +0200, Patrick Lamaizière wrote: > > Dears, > > > > I'm trying to port the glxsb driver from OpenBSD to FreeBSD 7-STABLE > > (via the NetBSD port). > > " The glxsb driver supports the security block of the Geode LX > > series processors. The Geode LX is a member of the AMD Geode family > > of integrated x86 system chips. > > > Is allready one of the FreeBSD developers working on integrating > your ported driver into HEAD? Pawel Jakub Dawidek proposed to look and commit it when it will be ready. A lot of code comes from padlock(4) so may be it's better if the author can rewiew the code. I think that the driver is ready and works fine, i didn't change anything since the latest version "22/06/08" http://user.lamaiziere.net/patrick/glxsb-220608.tar.gz It is not clear if i shall provide a patch against HEAD or do something else ? Regards. From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 04:30:06 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D0AB106567B for ; Mon, 7 Jul 2008 04:30:06 +0000 (UTC) (envelope-from unga888@yahoo.com) Received: from web57008.mail.re3.yahoo.com (web57008.mail.re3.yahoo.com [66.196.97.112]) by mx1.freebsd.org (Postfix) with SMTP id 1C5098FC16 for ; Mon, 7 Jul 2008 04:30:05 +0000 (UTC) (envelope-from unga888@yahoo.com) Received: (qmail 6485 invoked by uid 60001); 7 Jul 2008 04:03:24 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=fnQvH4BRRK1WhTsTnRPO2WNuSXsOGSlLE0FszpSusn/74N7mm9fb89A24tnJWC78SmElE2/hEbPNzCUg+vUE/dSp0fuTXekdx6MixGMJH6omH0uK36GNYAxvu7Pv4YjYDDQTqafwhr3SNr+yrdGXh41o3M4NH7haYVcnnzHVVoI=; Received: from [220.255.7.234] by web57008.mail.re3.yahoo.com via HTTP; Sun, 06 Jul 2008 21:03:23 PDT X-Mailer: YahooMailWebService/0.7.199 Date: Sun, 6 Jul 2008 21:03:23 -0700 (PDT) From: Unga To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-2042182583-1215403403=:6371" Message-ID: <232537.6371.qm@web57008.mail.re3.yahoo.com> Subject: [PATCH] Fix /usr/src/usr.sbin/pw/pwupd.c - pw_update() return success on failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 04:30:06 -0000 --0-2042182583-1215403403=:6371 Content-Type: text/plain; charset=us-ascii Hi all In the present implementation even if the pwdb() fails, pw_update() still return rc=0, therefore, subsequent functions still continue to proceed without passwd and master.passwd been updated. The attached patch fixes this issue. If this patch is acceptable, appreciate if it could be applied to both current and RELENG_7. Kind regards Unga --0-2042182583-1215403403=:6371 Content-Type: application/octet-stream; name="pw_update-return-code-fix.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="pw_update-return-code-fix.patch" ZGlmZiAtTmF1ciBwdy5vcmlnL3B3dXBkLmMgcHcvcHd1cGQuYwotLS0gcHcu b3JpZy9wd3VwZC5jCTIwMDgtMDctMDcgMTA6Mjg6NTIuMDAwMDAwMDAwICsw ODAwCisrKyBwdy9wd3VwZC5jCTIwMDgtMDctMDcgMTE6Mjc6MzcuMDAwMDAw MDAwICswODAwCkBAIC0xMzksNyArMTM5LDcgQEAKIHN0YXRpYyBpbnQKIHB3 X3VwZGF0ZShzdHJ1Y3QgcGFzc3dkICogcHdkLCBjaGFyIGNvbnN0ICogdXNl ciwgaW50IG1vZGUpCiB7Ci0JaW50ICAgICAgICAgICAgIHJjID0gMDsKKwlp bnQgcmM7CiAKIAlFTkRQV0VOVCgpOwogCkBAIC0xNDgsNyArMTQ4LDggQEAK IAkgKiBOb3RlOiAtQyBpcyBvbmx5IGF2YWlsYWJsZSBpbiBGcmVlQlNEIDIu MiBhbmQgYWJvdmUKIAkgKi8KICNpZmRlZiBIQVZFX1BXREJfQwotCWlmIChw d2RiKCItQyIsIChjaGFyICopTlVMTCkgPT0gMCkgewkvKiBDaGVjayBvbmx5 ICovCisJcmMgPSBwd2RiKCItQyIsIChjaGFyICopTlVMTCk7IC8qIENoZWNr IG9ubHkgKi8KKwlpZiAocmMgPT0gMCkgewogI2Vsc2UKIAl7CQkJCS8qIE5v IC1DICovCiAjZW5kaWYK --0-2042182583-1215403403=:6371-- From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 12:01:53 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3131106564A for ; Mon, 7 Jul 2008 12:01:53 +0000 (UTC) (envelope-from william88@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.232]) by mx1.freebsd.org (Postfix) with ESMTP id 9CC068FC18 for ; Mon, 7 Jul 2008 12:01:53 +0000 (UTC) (envelope-from william88@gmail.com) Received: by wx-out-0506.google.com with SMTP id h27so734923wxd.7 for ; Mon, 07 Jul 2008 05:01:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:mime-version:content-type:content-disposition:user-agent; bh=+IsUVOpn/uOMzktCH5v8FZVs7Rwz/9x93wwHPIgJgpc=; b=JzwARrFj3knNm3iXzHJ+QcuyEdZV28yGYgC2I4fDcY/7S7nRn8cHPW+urrUFKGEo0f Hxd6JkeHa4/JN9W2EsRiL3dJaK+2/RINoilWWiiAnKl3goQac//HXpOB1reE/eAW3X7c +ZPZXNOPtU4/z4LXP39cZS3aw0txGk93RPOYg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; b=GdsI807LBv9q8iDlzZ04YPlyaEIgcBpxe2mSSjQnim723Qz6PbOcIbIQN09CbdVCPg 7Rk+uAQQ/0Z9xXZxvzB8usMjKZ/++q3V6BRkG1QjuhcGwLtcmbdEa3TJVJQ8o3iATTJY CZ9GMUxqMoIQlPCm0lYX5bKa9SU755/5zpPwQ= Received: by 10.70.66.18 with SMTP id o18mr6691007wxa.66.1215430445376; Mon, 07 Jul 2008 04:34:05 -0700 (PDT) Received: from localhost ( [201.21.178.127]) by mx.google.com with ESMTPS id i11sm3699083wxd.25.2008.07.07.04.34.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 07 Jul 2008 04:34:04 -0700 (PDT) Date: Mon, 7 Jul 2008 08:34:01 -0300 From: William Grzybowski To: freebsd-current@freebsd.org Message-ID: <20080707113401.GA1672@venon.lost.garden> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Subject: mount ext2fs - geom_label X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 12:01:54 -0000 Hi! I'm running -CURRENT from 4 July. I can mount my ext3 partition without any errors but I can't access it: # mount -t ext2fs /dev/ad0s1 /media/ # cd /media cd: not a directory: /media # ls /media ls: /media: Bad file descriptor I enabled debug flags for geom: kern.geom.label.debug=1 kern.geom.debugflags=1 And i get this from dmesg: g_post_event_x(0xc05d11f0, 0xc3f6a180, 2, 0) ref 0xc3f6a180 GEOM_LABEL[0]: Label ext2fs// removed. g_slice_spoiled(0xc42c3dc0/ad0s1) g_wither_geom(0xc45c8000(ad0s1)) g_orphan_provider(0xc45c7e80(ext2fs//), 6) g_orphan_register(ext2fs//) g_dev_orphan(0xc5d82540(ext2fs//)) g_detach(0xc5d82540) g_destroy_consumer(0xc5d82540) g_destroy_geom(0xc463d180(ext2fs//)) g_detach(0xc42c3dc0) g_destroy_consumer(0xc42c3dc0) g_destroy_geom(0xc45c8000(ad0s1)) g_wither_geom_close(0xc461eb80(ext2fs.ad0s1)) g_post_event_x(0xc05d1580, 0xc3f6a180, 2, 0) ref 0xc3f6a180 g_wither_geom(0xc461eb80(ext2fs.ad0s1)) g_label_taste(LABEL, ad0s1) GEOM_LABEL[1]: MSDOSFS: ad0s1: no FAT signature found. GEOM_LABEL[1]: ext2fs file system detected on ad0s1. g_slice_config(ad0s1, 0, 1) g_post_event_x(0xc05d1580, 0xc45c8480, 2, 0) ref 0xc45c8480 ref 0xc45c8680 GEOM_LABEL[0]: Label for provider ad0s1 is ext2fs//. g_detach(0xc455b280) g_destroy_consumer(0xc455b280) g_destroy_geom(0xc45c7980(label:taste)) mbr_taste(MBR,ad0s1) g_mbrext_taste(MBREXT,ad0s1) g_slice_spoiled(0xc4008900/ad0s1) g_wither_geom(0xc45c7880(ad0s1)) bsd_taste(BSD,ad0s1) g_slice_spoiled(0xc3e57c40/ad0s1) g_wither_geom(0xc45c7a80(ad0s1)) g_part_taste(PART,ad0s1) g_wither_geom(0xc45f9600(ad0s1)) g_label_taste(LABEL, ext2fs//) mbr_taste(MBR,ext2fs//) g_slice_spoiled(0xc3fdd7c0/ext2fs//) g_wither_geom(0xc463d080(ext2fs//)) g_mbrext_taste(MBREXT,ext2fs//) dev_taste(DEV,ext2fs//) bsd_taste(BSD,ext2fs//) g_slice_spoiled(0xc3fdd840/ext2fs//) g_wither_geom(0xc45f9580(ext2fs//)) g_part_taste(PART,ext2fs//) g_wither_geom(0xc463d580(ext2fs//)) g_detach(0xc455b380) g_destroy_consumer(0xc455b380) g_destroy_geom(0xc461eb80(ext2fs.ad0s1)) g_detach(0xc3fdd7c0) g_destroy_consumer(0xc3fdd7c0) g_destroy_geom(0xc463d080(ext2fs//)) g_detach(0xc4008900) g_destroy_consumer(0xc4008900) g_destroy_geom(0xc45c7880(ad0s1)) g_detach(0xc3fdd840) g_destroy_consumer(0xc3fdd840) g_destroy_geom(0xc45f9580(ext2fs//)) g_detach(0xc3e57c40) g_destroy_consumer(0xc3e57c40) g_destroy_geom(0xc45c7a80(ad0s1)) g_detach(0xc455cc40) g_destroy_consumer(0xc455cc40) g_destroy_geom(0xc463d580(ext2fs//)) g_detach(0xc5d82300) g_destroy_consumer(0xc5d82300) g_destroy_geom(0xc45f9600(ad0s1)) g_post_event_x(0xc05d11f0, 0xc3f6a180, 2, 0) ref 0xc3f6a180 GEOM_LABEL[0]: Label ext2fs// removed. g_slice_spoiled(0xc4009540/ad0s1) g_wither_geom(0xc45c8680(ad0s1)) g_orphan_provider(0xc45c8480(ext2fs//), 6) g_orphan_register(ext2fs//) g_dev_orphan(0xc455cd00(ext2fs//)) g_detach(0xc455cd00) g_destroy_consumer(0xc455cd00) g_destroy_geom(0xc463d200(ext2fs//)) g_detach(0xc4009540) g_destroy_consumer(0xc4009540) g_destroy_geom(0xc45c8680(ad0s1)) I'm not sure if this slice was mounting fine over an older build but for sure it is ext3. Another partition with ext3 is (at least was) working. Am I missing something? Is that some kind of bug? Should i file it? Thanks. -- William Grzybowski /"\ Jabber: william88(at)gmail_dot_com \ / ASCII Ribbon Campaign Curitiba/PR - Brazil (GMT -3:00) X against HTML email & vCards ......... / \ From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 12:13:00 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 164261065684 for ; Mon, 7 Jul 2008 12:13:00 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 92EED8FC26 for ; Mon, 7 Jul 2008 12:12:59 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KFpaQ-0005gZ-0g for freebsd-current@freebsd.org; Mon, 07 Jul 2008 12:12:54 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 07 Jul 2008 12:12:54 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 07 Jul 2008 12:12:54 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Mon, 07 Jul 2008 14:12:44 +0200 Lines: 84 Message-ID: References: <20080707113401.GA1672@venon.lost.garden> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig72E359E2FB81A2C10A28E02D" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.14 (X11/20080505) In-Reply-To: <20080707113401.GA1672@venon.lost.garden> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: mount ext2fs - geom_label X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 12:13:00 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig72E359E2FB81A2C10A28E02D Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable William Grzybowski wrote: > Hi! >=20 > I'm running -CURRENT from 4 July. > I can mount my ext3 partition without any errors but I can't access it:= >=20 > # mount -t ext2fs /dev/ad0s1 /media/ > # cd /media > cd: not a directory: /media > # ls /media > ls: /media: Bad file descriptor >=20 > I enabled debug flags for geom: > kern.geom.label.debug=3D1 > kern.geom.debugflags=3D1 >=20 > And i get this from dmesg:=20 >=20 > g_post_event_x(0xc05d11f0, 0xc3f6a180, 2, 0) > ref 0xc3f6a180 > GEOM_LABEL[0]: Label ext2fs// removed. > g_slice_spoiled(0xc42c3dc0/ad0s1) > g_wither_geom(0xc45c8000(ad0s1)) > g_orphan_provider(0xc45c7e80(ext2fs//), 6) > g_orphan_register(ext2fs//) > g_dev_orphan(0xc5d82540(ext2fs//)) > g_detach(0xc5d82540) > g_destroy_consumer(0xc5d82540) > g_destroy_geom(0xc463d180(ext2fs//)) > g_detach(0xc42c3dc0) > g_destroy_consumer(0xc42c3dc0) > g_destroy_geom(0xc45c8000(ad0s1)) > g_wither_geom_close(0xc461eb80(ext2fs.ad0s1)) > g_post_event_x(0xc05d1580, 0xc3f6a180, 2, 0) > ref 0xc3f6a180 > g_wither_geom(0xc461eb80(ext2fs.ad0s1)) > g_label_taste(LABEL, ad0s1) > GEOM_LABEL[1]: MSDOSFS: ad0s1: no FAT signature found. > GEOM_LABEL[1]: ext2fs file system detected on ad0s1. > g_slice_config(ad0s1, 0, 1) > g_post_event_x(0xc05d1580, 0xc45c8480, 2, 0) > ref 0xc45c8480 > ref 0xc45c8680 > GEOM_LABEL[0]: Label for provider ad0s1 is ext2fs//. This only means that GEOM_LABEL detected an ext2fs-compatible file system with an empty label (or the label might be "/"?). I don't know if this particular thing would cause your error, but you might want to try and change the label on the ext2/3 file system to something using only alphanumeric characters (I think tune2fs -L can do that). > I'm not sure if this slice was mounting fine over an older build but fo= r sure it is ext3. > Another partition with ext3 is (at least was) working. >=20 > Am I missing something? Is that some kind of bug? Should i file it? > Thanks. If it turns out that geom_label is causing your problem, then yes, you should file it. --------------enig72E359E2FB81A2C10A28E02D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIcgg8ldnAQVacBcgRAn3JAKDw/3EadkaKbqLuyoEFFQjXzlmWQgCgm8HF BDGhj+vfns/necCNMYDt5JI= =9tks -----END PGP SIGNATURE----- --------------enig72E359E2FB81A2C10A28E02D-- From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 12:37:06 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 323B31065682 for ; Mon, 7 Jul 2008 12:37:06 +0000 (UTC) (envelope-from william88@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.226]) by mx1.freebsd.org (Postfix) with ESMTP id DEF3A8FC14 for ; Mon, 7 Jul 2008 12:37:05 +0000 (UTC) (envelope-from william88@gmail.com) Received: by wx-out-0506.google.com with SMTP id h27so737444wxd.7 for ; Mon, 07 Jul 2008 05:37:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=4Shhkt5DVwGtRcAvhHHTsWsZOf7Qudinv0odq8dVv4E=; b=JmhF2zbc17nQwguorOBuanDKN7O2c4ypQKNa3agQMZ0VP7ASk3Z7f9EB+AtQuZFuV/ HpKb0jpe4OixFVICjNvWHyU/CvVkElF7R0ufkzjrWU+IgtctuBEJyBUMZCI3ZEqlxGkk I1SvifrAMJZm3639LjPvcxuVRJbm5668JuC2s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=M4y9X9OhisqOhXGH0iBQ+3ao4h1jWMqPuvV8Tl5ssgzpm0CDxU+Ilex5d5q4Srccn1 IfbAqmH8s1uj9003hxOfTI/BAYGK1TCEXWt5flAIE9QNt6ijZcIvoEJfvYWRZQIj2U3y Xfuv6WT+kBAiCo2jpFlIKNGr6UdgyXxCzQ6oE= Received: by 10.70.109.12 with SMTP id h12mr6834642wxc.6.1215434224898; Mon, 07 Jul 2008 05:37:04 -0700 (PDT) Received: from localhost ( [201.21.178.127]) by mx.google.com with ESMTPS id h16sm3717715wxd.15.2008.07.07.05.37.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 07 Jul 2008 05:37:04 -0700 (PDT) Date: Mon, 7 Jul 2008 09:36:55 -0300 From: William Grzybowski To: Ivan Voras Message-ID: <20080707123655.GA1917@venon.lost.garden> References: <20080707113401.GA1672@venon.lost.garden> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-current@freebsd.org Subject: Re: mount ext2fs - geom_label X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 12:37:06 -0000 On Mon, Jul 07, 2008 at 02:12:44PM +0200, Ivan Voras wrote: > William Grzybowski wrote: > > Hi! > > > > I'm running -CURRENT from 4 July. > > I can mount my ext3 partition without any errors but I can't access it: > > > > # mount -t ext2fs /dev/ad0s1 /media/ > > # cd /media > > cd: not a directory: /media > > # ls /media > > ls: /media: Bad file descriptor > > > > I enabled debug flags for geom: > > kern.geom.label.debug=1 > > kern.geom.debugflags=1 > > > > And i get this from dmesg: > > > > g_post_event_x(0xc05d11f0, 0xc3f6a180, 2, 0) > > ref 0xc3f6a180 > > GEOM_LABEL[0]: Label ext2fs// removed. > > g_slice_spoiled(0xc42c3dc0/ad0s1) > > g_wither_geom(0xc45c8000(ad0s1)) > > g_orphan_provider(0xc45c7e80(ext2fs//), 6) > > g_orphan_register(ext2fs//) > > g_dev_orphan(0xc5d82540(ext2fs//)) > > g_detach(0xc5d82540) > > g_destroy_consumer(0xc5d82540) > > g_destroy_geom(0xc463d180(ext2fs//)) > > g_detach(0xc42c3dc0) > > g_destroy_consumer(0xc42c3dc0) > > g_destroy_geom(0xc45c8000(ad0s1)) > > g_wither_geom_close(0xc461eb80(ext2fs.ad0s1)) > > g_post_event_x(0xc05d1580, 0xc3f6a180, 2, 0) > > ref 0xc3f6a180 > > g_wither_geom(0xc461eb80(ext2fs.ad0s1)) > > g_label_taste(LABEL, ad0s1) > > GEOM_LABEL[1]: MSDOSFS: ad0s1: no FAT signature found. > > GEOM_LABEL[1]: ext2fs file system detected on ad0s1. > > g_slice_config(ad0s1, 0, 1) > > g_post_event_x(0xc05d1580, 0xc45c8480, 2, 0) > > ref 0xc45c8480 > > ref 0xc45c8680 > > GEOM_LABEL[0]: Label for provider ad0s1 is ext2fs//. > > This only means that GEOM_LABEL detected an ext2fs-compatible file > system with an empty label (or the label might be "/"?). I don't know if > this particular thing would cause your error, but you might want to try > and change the label on the ext2/3 file system to something using only > alphanumeric characters (I think tune2fs -L can do that). The label was "/", I did change it to "st" and unfortunelly this issue still exists... > > > I'm not sure if this slice was mounting fine over an older build but for sure it is ext3. > > Another partition with ext3 is (at least was) working. > > > > Am I missing something? Is that some kind of bug? Should i file it? > > Thanks. > > If it turns out that geom_label is causing your problem, then yes, you > should file it. OK. -- William Grzybowski /"\ Jabber: william88(at)gmail_dot_com \ / ASCII Ribbon Campaign Curitiba/PR - Brazil (GMT -3:00) X against HTML email & vCards ......... / \ From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 16:30:20 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37268106567E for ; Mon, 7 Jul 2008 16:30:20 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id BA7858FC23 for ; Mon, 7 Jul 2008 16:30:19 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KFtbW-0000jU-Op for freebsd-current@freebsd.org; Mon, 07 Jul 2008 16:30:18 +0000 Received: from mulderlab.f5.com ([205.229.151.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 07 Jul 2008 16:30:18 +0000 Received: from atkin901 by mulderlab.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 07 Jul 2008 16:30:18 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Mark Atkinson Date: Mon, 07 Jul 2008 09:30:07 -0700 Lines: 52 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: mulderlab.f5.com User-Agent: KNode/0.10.5 Sender: news Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 16:30:20 -0000 gnn@freebsd.org wrote: > Hi, > > I've been working on the following brain teasing (breaking?) problem > for about a week now. What I'm seeing is that on large memory > machines, those with more than 4G of RAM, the ungzipping/untarring of > files fails due to gzip thinking the file is corrupt. The way to > reproduce this is: > > 1) Create a bunch of gzip/tar balls in the 1-20MB range. > 2) Reboot FreeBSD 7.0 release > 3) Run gzip -t over all the files. > > I have hundreds of these files to run this over, and a full check > takes about 3 hours, but I usually see some form of corruption within > the first 20 minutes. > > Other important factors: > > 1) This is on very modern, 2P/4Core (8 cores total) hardware > 2) The disks are 1TB SATA set up in JBOD. > 3) The machines have 16G of RAM. > 4) Corruption is seen only after a reboot, if the machines continue to > run corruption is never seen again, until another reboot. > 5) The systems are all Xeon running amd64 > 6) The disk controller is an AMCC 9650, but we do see this very rarely > with the on board controlller. > 7) All boards are > > http://www.supermicro.com/products/motherboard/Xeon1333/5400/X7DWU.cfm > > 8) All machines have 3 1TB drives. > 9) The corruption is in 4K chunks. That is N x 4K. > 10) Files are not normally corrupted on disk, but this can happen. > > I have already tried a few of the obvious things, such as making sure > that we sync pages before we shutdown the twa driver. > > Given what I have seen I believe this is something that happens from > startup, and not at shutdown. > > Thoughts? Have you tried turning off background fsck on boot to see if the problem goes away? -- Mark Atkinson atkin901@yahoo.com (!wired)?(coffee++):(wired); From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 18:12:05 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 486871065678 for ; Mon, 7 Jul 2008 18:12:05 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from proxy.meer.net (proxy.meer.net [64.13.141.13]) by mx1.freebsd.org (Postfix) with ESMTP id 278A58FC1F for ; Mon, 7 Jul 2008 18:12:04 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [64.13.141.3]) by proxy.meer.net (8.14.2/8.14.2) with ESMTP id m67IC16U025360; Mon, 7 Jul 2008 11:12:04 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from mail2.meer.net (mail2.meer.net [64.13.141.16]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id m67IBf7Z031593; Mon, 7 Jul 2008 11:11:41 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (209.249.190.254.available.above.net [209.249.190.254] (may be forged)) (authenticated bits=0) by mail2.meer.net (8.14.1/8.14.1) with ESMTP id m67IBebJ083008; Mon, 7 Jul 2008 11:11:41 -0700 (PDT) (envelope-from gnn@neville-neil.com) Date: Mon, 07 Jul 2008 14:11:40 -0400 Message-ID: From: gnn@freebsd.org To: Mark Atkinson In-Reply-To: References: User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.1.50 (i386-apple-darwin8.11.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Canit-CHI2: 0.50 X-Bayes-Prob: 0.5 (Score 0, tokens from: ) X-Spam-Score: 0.10 () [Tag at 5.00] COMBINED_FROM X-CanItPRO-Stream: default X-Canit-Stats-ID: 880223 - 8260d1aed1fd X-Scanned-By: CanIt (www . roaringpenguin . com) on 64.13.141.13 Cc: freebsd-current@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 18:12:05 -0000 At Mon, 07 Jul 2008 09:30:07 -0700, Mark Atkinson wrote: > > Have you tried turning off background fsck on boot to see if the problem > goes away? The problem persists even without background fsck. I am starting to lean towards some sort of weird gzip bug, but have no real evidence yet. Best, George From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 18:32:33 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E4561065687; Mon, 7 Jul 2008 18:32:33 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id ABC408FC2D; Mon, 7 Jul 2008 18:32:31 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48726140.2000405@FreeBSD.org> Date: Mon, 07 Jul 2008 20:32:32 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: gnn@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Mark Atkinson Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 18:32:33 -0000 gnn@freebsd.org wrote: > At Mon, 07 Jul 2008 09:30:07 -0700, > Mark Atkinson wrote: >> Have you tried turning off background fsck on boot to see if the problem >> goes away? > > The problem persists even without background fsck. > > I am starting to lean towards some sort of weird gzip bug, but have no > real evidence yet. Did you try zfs yet? It will differentiate between corruption that occurs above (or in) or below the filesystem layer. Kris From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 18:40:13 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4310B1065755; Mon, 7 Jul 2008 18:40:13 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from proxy.meer.net (proxy.meer.net [64.13.141.13]) by mx1.freebsd.org (Postfix) with ESMTP id 1F76A8FC0A; Mon, 7 Jul 2008 18:40:12 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [64.13.141.3]) by proxy.meer.net (8.14.2/8.14.2) with ESMTP id m67Ie9Tl026985; Mon, 7 Jul 2008 11:40:12 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from mail2.meer.net (mail2.meer.net [64.13.141.16]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id m67Ie7Nc041858; Mon, 7 Jul 2008 11:40:07 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (209.249.190.254.available.above.net [209.249.190.254] (may be forged)) (authenticated bits=0) by mail2.meer.net (8.14.1/8.14.1) with ESMTP id m67Ie7E9088288; Mon, 7 Jul 2008 11:40:07 -0700 (PDT) (envelope-from gnn@neville-neil.com) Date: Mon, 07 Jul 2008 14:40:06 -0400 Message-ID: From: gnn@FreeBSD.org To: Kris Kennaway In-Reply-To: <48726140.2000405@FreeBSD.org> References: <48726140.2000405@FreeBSD.org> User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.1.50 (i386-apple-darwin8.11.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Canit-CHI2: 0.50 X-Bayes-Prob: 0.5 (Score 0, tokens from: ) X-Spam-Score: 0.10 () [Tag at 5.00] COMBINED_FROM X-CanItPRO-Stream: default X-Canit-Stats-ID: 880495 - a25ea53573bf X-Scanned-By: CanIt (www . roaringpenguin . com) on 64.13.141.13 Cc: freebsd-current@FreeBSD.org, Mark Atkinson Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 18:40:13 -0000 At Mon, 07 Jul 2008 20:32:32 +0200, Kris Kennaway wrote: > > gnn@freebsd.org wrote: > > At Mon, 07 Jul 2008 09:30:07 -0700, > > Mark Atkinson wrote: > >> Have you tried turning off background fsck on boot to see if the problem > >> goes away? > > > > The problem persists even without background fsck. > > > > I am starting to lean towards some sort of weird gzip bug, but have no > > real evidence yet. > > Did you try zfs yet? It will differentiate between corruption that > occurs above (or in) or below the filesystem layer. > Not as yet, that is on the list though. Later, George From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 18:45:54 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70FFC1065678; Mon, 7 Jul 2008 18:45:54 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 84DB88FC18; Mon, 7 Jul 2008 18:45:53 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48726462.3090009@FreeBSD.org> Date: Mon, 07 Jul 2008 20:45:54 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: gnn@FreeBSD.org References: <48726140.2000405@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, Mark Atkinson Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 18:45:54 -0000 gnn@FreeBSD.org wrote: > At Mon, 07 Jul 2008 20:32:32 +0200, > Kris Kennaway wrote: >> gnn@freebsd.org wrote: >>> At Mon, 07 Jul 2008 09:30:07 -0700, >>> Mark Atkinson wrote: >>>> Have you tried turning off background fsck on boot to see if the problem >>>> goes away? >>> The problem persists even without background fsck. >>> >>> I am starting to lean towards some sort of weird gzip bug, but have no >>> real evidence yet. >> Did you try zfs yet? It will differentiate between corruption that >> occurs above (or in) or below the filesystem layer. >> > > Not as yet, that is on the list though. > > Later, > George > > OK, might be worth the time investment IMO, unless you have other ideas to run down. Kris From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 19:24:52 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 618071065678 for ; Mon, 7 Jul 2008 19:24:52 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.185]) by mx1.freebsd.org (Postfix) with ESMTP id DDC3F8FC15 for ; Mon, 7 Jul 2008 19:24:51 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by ti-out-0910.google.com with SMTP id d27so555309tid.3 for ; Mon, 07 Jul 2008 12:24:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=8U922IDw6BowmmwU2jTddE9QX7G7k9n6x0nrGlLm/CQ=; b=vICiF9jQPZMOO2oiV2vjO0R5nxaffQBi+FKIa7Qepk7TIkrCCEffOVyrB7L0Zv/tGZ 7AAM0sF2jNbsI72reArirH7nhngKMSky/x3zyvjcz7lgXYj81cQfcwpnUXz7huqa2Wvz OgIwawO3cIGIsxerW7dZ5pwZnhm9KEEKHEzko= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=bR5qUf0YpNU6r6Bqa/1VH8VbL5amuXLMJm1cI0UAEjLhcaqOaniLYZzqMSBeHi+KOD imsjwJEysZDSYfrl0sOrGOCj+GgwhEh1iEW+rWL11dZIGm9mKmpXZ/1SI5IlOVlr0PiP 4eEhC4C8pqLjA3JlPotxP7sxU5iu4RBry70Vs= Received: by 10.150.227.14 with SMTP id z14mr8686146ybg.145.1215456941749; Mon, 07 Jul 2008 11:55:41 -0700 (PDT) Received: by 10.151.154.17 with HTTP; Mon, 7 Jul 2008 11:55:41 -0700 (PDT) Message-ID: Date: Mon, 7 Jul 2008 11:55:41 -0700 From: "Freddie Cash" To: freebsd-hackers@freebsd.org In-Reply-To: <486F8C57.9050908@wubethiopia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486F8C57.9050908@wubethiopia.com> Cc: freebsd-current@freebsd.org Subject: Re: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 19:24:52 -0000 On Sat, Jul 5, 2008 at 7:59 AM, Mike Makonnen wrote: > Also, the installer's job should only be to install a useable system. Post-installation chores like configuration, > adding/removing users, etc should be done by another application. You shouldn't need the installer once > you've installed the OS. Hear, hear! To be honest, this is the only bit about the current sysinstall that I really dislike: the fact that it can be used for post-installation configuration and package installation. This causes no end of trouble for newbies, who seem to view sysinstall as "The One True System Admin Tool" and try to use it for configuring/installing everything. Too many times, on various BSD forums, I've had to walk people through cleaning up /etc/rc.conf and showing them how to correctly install/configure things (using standard FreeBSD tools), since they used sysinstall for everything. IMO, the installer should allow you to partition the disk(s), format the partition(s), install the OS, configure a user, and reboot the system. Anything beyond that should be handled by the OS tools, from within the installed and running OS. The tricky part will be getting the disk slicing, slice partitioning, and filesystem formatting to work reliably, with all the power of FreeBSD's GEOM modules, and ZFS. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 19:36:44 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7A46106564A; Mon, 7 Jul 2008 19:36:44 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (unknown [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 790AC8FC13; Mon, 7 Jul 2008 19:36:44 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (unknown [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 5013E284E3; Tue, 8 Jul 2008 03:36:43 +0800 (CST) Received: from localhost (unknown [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id 85D93F08603; Tue, 8 Jul 2008 03:36:42 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id RKK3xM31lZxU; Tue, 8 Jul 2008 03:36:30 +0800 (CST) Received: from charlie.delphij.net (71.5.7.139.ptr.us.xo.net [71.5.7.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 09AEBF0859C; Tue, 8 Jul 2008 03:36:28 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:subject:x-enigmail-version:openpgp:content-type; b=qfM4EE3lm4RP7b4rJ/VvW31cHMue7tDSIBASBjCf1j+ojwvJ1H7w4asX+zyqsHtwO XvsosatpkiMTexRSApzKA== Message-ID: <4872703B.9060408@delphij.net> Date: Mon, 07 Jul 2008 12:36:27 -0700 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: ariff@FreeBSD.org, FreeBSD Current X-Enigmail-Version: 0.95.6 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: multipart/mixed; boundary="------------040909030300060209010908" Cc: Subject: [PATCH] Support for Dell D630 sound X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 19:36:45 -0000 This is a multi-part message in MIME format. --------------040909030300060209010908 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Ariff, A friend of mine recently bought a Dell D630 and found that the audio part does not work. I have put together this patch which allows the audio to work. Could you or may I commit against -HEAD? (A MFC of hda related stuff would be required for RELENG_7 to work with it) Thanks in advance! Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhycDoACgkQi+vbBBjt66DUlQCeNMm75JGtHrTTxiiXAP9AyJEQ DtoAniIgEblJ3Ue81v4IBtZ2wB/pLmzu =upDg -----END PGP SIGNATURE----- --------------040909030300060209010908 Content-Type: text/plain; name="sound.diff" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="sound.diff" Index: hdac.c =================================================================== --- hdac.c (版本 180335) +++ hdac.c (工作副本) @@ -193,6 +193,7 @@ /* Dell */ #define DELL_VENDORID 0x1028 +#define DELL_D630_SUBVENDOR HDA_MODEL_CONSTRUCT(DELL, 0x01f9) #define DELL_D820_SUBVENDOR HDA_MODEL_CONSTRUCT(DELL, 0x01cc) #define DELL_V1500_SUBVENDOR HDA_MODEL_CONSTRUCT(DELL, 0x0228) #define DELL_I1300_SUBVENDOR HDA_MODEL_CONSTRUCT(DELL, 0x01c9) @@ -688,6 +689,8 @@ 0, 0, -1, 13, { 14, -1 }, -1 }, { DELL_OPLX745_SUBVENDOR, HDA_CODEC_AD1983, HDAC_HP_SWITCH_CTL, 0, 0, -1, 6, { 5, 7, -1 }, -1 }, + { DELL_D630_SUBVENDOR, HDA_CODEC_STAC9205, HDAC_HP_SWITCH_CTRL, + 0, 0, -1, 10, { 13, -1 }, -1 }, { DELL_V1500_SUBVENDOR, HDA_CODEC_STAC9205, HDAC_HP_SWITCH_CTRL, 0, 0, -1, 10, { 13, -1 }, -1 }, { APPLE_MB3_SUBVENDOR, HDA_CODEC_ALC885, HDAC_HP_SWITCH_CTL, @@ -4255,6 +4258,8 @@ HDA_QUIRK_GPIO0 | HDA_QUIRK_OVREF50, 0}, { APPLE_INTEL_MAC, HDA_CODEC_STAC9221, HDA_QUIRK_GPIO0 | HDA_QUIRK_GPIO1, 0 }, + { DELL_D630_SUBVENDOR, HDA_CODEC_STAC9205, + HDA_QUIRK_GPIO0, 0 }, { DELL_V1500_SUBVENDOR, HDA_CODEC_STAC9205, HDA_QUIRK_GPIO0, 0 }, { HDA_MATCH_ALL, HDA_CODEC_AD1988, @@ -4528,7 +4533,8 @@ } break; case HDA_CODEC_STAC9205: - if (subvendor == DELL_V1500_SUBVENDOR) { + if ((subvendor == DELL_V1500_SUBVENDOR) || + (subvendor == DELL_D630_SUBVENDOR)) { w = hdac_widget_get(devinfo, 29); if (w != NULL) w->selconn = 1; --------------040909030300060209010908-- From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 20:06:33 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31278106568D; Mon, 7 Jul 2008 20:06:33 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1433F8FC23; Mon, 7 Jul 2008 20:06:29 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48727747.7070509@FreeBSD.org> Date: Mon, 07 Jul 2008 22:06:31 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Maxim Sobolev References: <4855EDFE.3010708@FreeBSD.org> <86bq211rqw.fsf@ds4.des.no> <20080617002224.GA16122@nagual.pp.ru> <20080617002808.GB16122@nagual.pp.ru> <20080617004647.GA16546@nagual.pp.ru> <48576610.9080808@FreeBSD.org> <48577510.4020007@aueb.gr> <48577BD2.4070205@bluemedia.pl> <20080617102900.GA46479@nagual.pp.ru> <485798C4.2050605@FreeBSD.org> <20080618055851.GA85018@nagual.pp.ru> <86zlpjduew.fsf@ds4.des.no> <48598C6D.4040102@FreeBSD.org> In-Reply-To: <48598C6D.4040102@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Mon, 07 Jul 2008 20:12:28 +0000 Cc: Doug Barton , current@FreeBSD.org, Andrey Chernov , Konrad Jankowski , Diomidis Spinellis , hackers@FreeBSD.org, Gabor Kovesdan , =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= , Max Khon , "Sean C. Farley" , K?vesd?n G?bor Subject: Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 20:06:33 -0000 Maxim Sobolev wrote: > Dag-Erling Smørgrav wrote: >> Andrey Chernov writes: >>> "BSD sort" as an idea will be a good project indeed, but "BSD sort" >>> implementation we currently have at hand is totally misleading and >>> should be rewritten from the scratch, I realize it when long time ago >>> I try to localize it for single byte locales. >> >> I think part of the problem is that there aren't enough people who truly >> understand localization. I think I understand most of it, but I'm >> pretty sure I *don't* understand how collation works, or is supposed to >> work. Amongst other things, I don't understand how (or whether) it >> handles cases like "aa" and "å", which are considered the same letter in >> Norwegian. >> >> Perhaps you could create a Localization page on wiki.freebsd.org which >> addresses these issues, or at least points to relevant resources? > > Good regression test suite which would include cases in different single > and multi-byte locates for grep/sort/etc could also be a big help. What regression suites do other implementations have? e.g. the GNU textutils. Kris From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 20:15:08 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7953310656A1 for ; Mon, 7 Jul 2008 20:15:08 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 4E4458FC21 for ; Mon, 7 Jul 2008 20:15:08 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.2/8.14.2) with ESMTP id m67KF8I2016992 for ; Mon, 7 Jul 2008 13:15:08 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.2/8.14.2/Submit) id m67KF8gS016991 for freebsd-current@freebsd.org; Mon, 7 Jul 2008 13:15:08 -0700 (PDT) (envelope-from sgk) Date: Mon, 7 Jul 2008 13:15:08 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20080707201508.GA16881@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: wlan0/wpi0 are filling /var/log/messages. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 20:15:08 -0000 What's up with wlan0 and/or wpi0? dmesg is showing a massive amount of noise from mobile:kargl[202] dmesg | wc -l 5469 mobile:kargl[202] dmesg | more 1 retries (70 lines of '1 retries' manually deleted by me) 2 retries 1 retries 2 retries 1 retries (16 lines of '1 retries' manually deleted by me) 1 retries 2 retries 1 retries 1 retries wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP Beacon miss: 20 >= 7 (Same message with numbers 21-228 deleted by me) (Same message with numbers 20-185 deleted by me) (Same message with numbers 20-185 deleted by me) (Same message with numbers 20-141 deleted by me) (Same message with numbers 20-141 deleted by me) Beacon miss: 331 >= 7 wpi_newstate: RUN -> AUTH flags 0x0 config chan 11 flags 8035 cck f ofdm 15 wlan0: link state changed to DOWN wpi_newstate: AUTH -> ASSOC flags 0x0 wpi_newstate: ASSOC -> RUN flags 0x0 config chan 11 flags 8035 wlan0: link state changed to UP Beacon miss: 20 >= 7 4000+ lines deleted. -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 20:15:16 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BE6F1065687; Mon, 7 Jul 2008 20:15:16 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (nagual.pp.ru [194.87.13.69]) by mx1.freebsd.org (Postfix) with ESMTP id E77AD8FC24; Mon, 7 Jul 2008 20:15:15 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.14.2/8.14.2) with ESMTP id m67KEmGM037445; Tue, 8 Jul 2008 00:14:48 +0400 (MSD) (envelope-from ache@nagual.pp.ru) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nagual.pp.ru; s=default; t=1215461688; bh=mA6PH4pcI398wxCi5ZBFMq3QikRtItpBguAj4g6 AXi0=; l=353; h=Date:From:To:Cc:Subject:Message-ID:References: MIME-Version:Content-Type:In-Reply-To; b=PdNwfPwIIyb5KTyuZZI2vONJd +2jnBynxftIKjoP7l3o7Fc3HgVlmhtz7SNmUm+C2BUGbK/VMyoM1XqHnpcSZdE104PS 31Y3ZB2/atoX4vKgybm0VfhjneTDf/BDbN/jcQtLTFeTg0MlA6onYCnKm+Qday69MyE t8KOCjsMJkGA= Received: (from ache@localhost) by nagual.pp.ru (8.14.2/8.14.2/Submit) id m67KEmFv037444; Tue, 8 Jul 2008 00:14:48 +0400 (MSD) (envelope-from ache) Date: Tue, 8 Jul 2008 00:14:47 +0400 From: Andrey Chernov To: Kris Kennaway Message-ID: <20080707201447.GA37354@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Kris Kennaway , Maxim Sobolev , Dag-Erling Sm?rgrav , Doug Barton , current@FreeBSD.org, Konrad Jankowski , Diomidis Spinellis , hackers@FreeBSD.org, Gabor Kovesdan , K?vesd?n G?bor , "Sean C. Farley" , Max Khon References: <20080617004647.GA16546@nagual.pp.ru> <48576610.9080808@FreeBSD.org> <48577510.4020007@aueb.gr> <48577BD2.4070205@bluemedia.pl> <20080617102900.GA46479@nagual.pp.ru> <485798C4.2050605@FreeBSD.org> <20080618055851.GA85018@nagual.pp.ru> <86zlpjduew.fsf@ds4.des.no> <48598C6D.4040102@FreeBSD.org> <48727747.7070509@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48727747.7070509@FreeBSD.org> User-Agent: Mutt/1.5.18 (2008-05-17) X-Mailman-Approved-At: Mon, 07 Jul 2008 20:19:02 +0000 Cc: Maxim Sobolev , Doug Barton , current@FreeBSD.org, Konrad Jankowski , Diomidis Spinellis , hackers@FreeBSD.org, Gabor Kovesdan , Dag-Erling Sm?rgrav , Max Khon , "Sean C. Farley" , K?vesd?n G?bor Subject: Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 20:15:16 -0000 On Mon, Jul 07, 2008 at 10:06:31PM +0200, Kris Kennaway wrote: > What regression suites do other implementations have? e.g. the GNU > textutils. They basically have regex tests, but nothing locale specific, since locale ordering is different from platform to platform (until Unicode Collation Algorithm will win). -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 20:39:51 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D1691065682; Mon, 7 Jul 2008 20:39:51 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 99B158FC18; Mon, 7 Jul 2008 20:39:47 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <48727F14.6090507@FreeBSD.org> Date: Mon, 07 Jul 2008 22:39:48 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Andrey Chernov , Kris Kennaway , Maxim Sobolev , Dag-Erling Sm?rgrav , Doug Barton , current@FreeBSD.org, Konrad Jankowski , Diomidis Spinellis , hackers@FreeBSD.org, Gabor Kovesdan , K?vesd?n G?bor , "Sean C. Farley" , Max Khon References: <20080617004647.GA16546@nagual.pp.ru> <48576610.9080808@FreeBSD.org> <48577510.4020007@aueb.gr> <48577BD2.4070205@bluemedia.pl> <20080617102900.GA46479@nagual.pp.ru> <485798C4.2050605@FreeBSD.org> <20080618055851.GA85018@nagual.pp.ru> <86zlpjduew.fsf@ds4.des.no> <48598C6D.4040102@FreeBSD.org> <48727747.7070509@FreeBSD.org> <20080707201447.GA37354@nagual.pp.ru> In-Reply-To: <20080707201447.GA37354@nagual.pp.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 07 Jul 2008 20:49:56 +0000 Cc: Subject: Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 20:39:51 -0000 Andrey Chernov wrote: > On Mon, Jul 07, 2008 at 10:06:31PM +0200, Kris Kennaway wrote: >> What regression suites do other implementations have? e.g. the GNU >> textutils. > > They basically have regex tests, but nothing locale specific, since locale > ordering is different from platform to platform (until Unicode Collation > Algorithm will win). > OK. Well at least it is a start - passing those existing regression tests should be a goal. Kris From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 20:56:38 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84885106568B; Mon, 7 Jul 2008 20:56:38 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from viefep31-int.chello.at (viefep31-int.chello.at [62.179.121.49]) by mx1.freebsd.org (Postfix) with ESMTP id 4D1DC8FC18; Mon, 7 Jul 2008 20:56:36 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from [89.134.207.83] by viefep31-int.chello.at (InterMail vM.7.08.02.02 201-2186-121-104-20070414) with ESMTP id <20080707205635.XJZM23341.viefep31-int.chello.at@[89.134.207.83]>; Mon, 7 Jul 2008 22:56:35 +0200 Message-ID: <48728301.5070403@FreeBSD.org> Date: Mon, 07 Jul 2008 22:56:33 +0200 From: Gabor Kovesdan User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Kris Kennaway References: <20080617004647.GA16546@nagual.pp.ru> <48576610.9080808@FreeBSD.org> <48577510.4020007@aueb.gr> <48577BD2.4070205@bluemedia.pl> <20080617102900.GA46479@nagual.pp.ru> <485798C4.2050605@FreeBSD.org> <20080618055851.GA85018@nagual.pp.ru> <86zlpjduew.fsf@ds4.des.no> <48598C6D.4040102@FreeBSD.org> <48727747.7070509@FreeBSD.org> <20080707201447.GA37354@nagual.pp.ru> <48727F14.6090507@FreeBSD.org> In-Reply-To: <48727F14.6090507@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Mon, 07 Jul 2008 21:23:36 +0000 Cc: Maxim Sobolev , Doug Barton , current@FreeBSD.org, Andrey Chernov , Konrad Jankowski , Diomidis Spinellis , hackers@FreeBSD.org, Dag-Erling Sm?rgrav , "Sean C. Farley" , Max Khon Subject: Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2008 20:56:38 -0000 Kris Kennaway escribió: > Andrey Chernov wrote: >> On Mon, Jul 07, 2008 at 10:06:31PM +0200, Kris Kennaway wrote: >>> What regression suites do other implementations have? e.g. the GNU >>> textutils. >> >> They basically have regex tests, but nothing locale specific, since >> locale ordering is different from platform to platform (until Unicode >> Collation Algorithm will win). >> > > OK. Well at least it is a start - passing those existing regression > tests should be a goal. Well, it seems you have missed the first nits of the discussion. GNU grep has some regression test, which doesn't pass completely itself either. :) I've mentioned here that I used those tests to find out what incompatible options are there. Unfortunately, I have to say that BSD grep won't pass all of those, because GNU allows some non-standard regexes, which are rejected by our libc-regex library, like for example (a|) is not standard because it has an empty subexpression. First, I tried to pre-edit such expression in the code. It was ugly enough but I thought: "Ok, this code is pretty ugly, but compatibility is important, maybe we can later revise and/or change our regexp library and get rid of these snippets." Later, when Andrey pointed it out, I realized that my workarounds adressed those incompatibilities but didn't work completely, they broke compatibility at other places, thus I just removed them, because it was not that easy to fix. The version that I sent you for the portbuild test, doesn't have those workarounds. The regression test helped though to fix other compatibility issues, like return values. All of these trivial things are supposed to be compatible now, the only exceptions are the non-standard regexes. That's why I'm so curious about the results. If they are inacceptable, we can try to build BSD grep with the GNU regexp lib (it's in the tree, as Pedro F. Giffuni pointed it out). It doesn't work by just linking with that library, so it will need more work and investigation then, not speaking about that GNU regex should go one day... Regards, Gábor From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 00:38:55 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD755106566C; Tue, 8 Jul 2008 00:38:55 +0000 (UTC) (envelope-from lsc@prgmr.com) Received: from luke.xen.prgmr.com (luke.xen.prgmr.com [38.99.2.47]) by mx1.freebsd.org (Postfix) with ESMTP id 9BA778FC14; Tue, 8 Jul 2008 00:38:55 +0000 (UTC) (envelope-from lsc@prgmr.com) Received: by luke.xen.prgmr.com (Postfix, from userid 500) id 483B71041CC; Mon, 7 Jul 2008 20:19:50 -0400 (EDT) Sender: lsc@luke.xen.prgmr.com To: gnn@freebsd.org References: From: Luke S Crawford Date: 07 Jul 2008 20:19:50 -0400 In-Reply-To: Message-ID: Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: current@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 00:38:56 -0000 gnn@freebsd.org writes: > I have hundreds of these files to run this over, and a full check > takes about 3 hours, but I usually see some form of corruption within > the first 20 minutes. I've seen similar problems happen on a groups of new boxes when the ram was slightly out of spec for the motherboard. memtest revealed the problem, returning the lot of ram for a different model fixed the problem. > 4) Corruption is seen only after a reboot, if the machines continue to > run corruption is never seen again, until another reboot. This would indicate that I am wrong. Personally, I'd still run memtest86 for 48 hours or so, just to be sure. does smartctl report weirdness? From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 05:37:26 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF27D106567E; Tue, 8 Jul 2008 05:37:26 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd4mo3so.prod.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by mx1.freebsd.org (Postfix) with ESMTP id AA33B8FC1D; Tue, 8 Jul 2008 05:37:26 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd4mr2so.prod.shaw.ca (pd4mr2so-qfe3.prod.shaw.ca [10.0.141.213]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0K3O007A67GQQ7C0@l-daemon>; Mon, 07 Jul 2008 22:36:26 -0600 (MDT) Received: from pn2ml10so.prod.shaw.ca ([10.0.121.80]) by pd4mr2so.prod.shaw.ca (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0K3O00FH37GQZD70@pd4mr2so.prod.shaw.ca>; Mon, 07 Jul 2008 22:36:27 -0600 (MDT) Received: from soralx ([24.87.3.133]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0K3O003IO7GP2G70@l-daemon>; Mon, 07 Jul 2008 22:36:25 -0600 (MDT) Date: Mon, 07 Jul 2008 21:36:25 -0700 From: soralx@cydem.org In-reply-to: To: fjwcash@gmail.com Message-id: <20080707213625.69bb0bf4@soralx> MIME-version: 1.0 X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486F8C57.9050908@wubethiopia.com> X-Mailman-Approved-At: Tue, 08 Jul 2008 11:12:27 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 05:37:26 -0000 > Hear, hear! To be honest, this is the only bit about the current > sysinstall that I really dislike: the fact that it can be used for > post-installation configuration and package installation. This causes > no end of trouble for newbies, who seem to view sysinstall as "The One > True System Admin Tool" and try to use it for configuring/installing > everything. Too many times, on various BSD forums, I've had to walk > people through cleaning up /etc/rc.conf and showing them how to > correctly install/configure things (using standard FreeBSD tools), > since they used sysinstall for everything. That may be true, but sysinstall did help me do basic, essentical configuration of my very first installed system, and a few installs after that (until I learned about /etc/rc.conf et al). And I never regarded it as The One True Sysadmin Tool, because I did not use Linux distros, thus never got used to their ways. It's just that the simple configuration menu really helped me to get a useful system running in a few minutes (though menu items certainly could make use of more verbose descriptions). And then I could play with the working system and learn ways to configure it. So, IMHO, a basic curses system configuration utility is still needed, and should be run after sysinstall or it should tell the user how to run it (maybe in motd, or sysinstall itself?). > IMO, the installer should allow you to partition the disk(s), format > the partition(s), install the OS, configure a user, and reboot the > system. Anything beyond that should be handled by the OS tools, from > within the installed and running OS. > > The tricky part will be getting the disk slicing, slice partitioning, > and filesystem formatting to work reliably, with all the power of > FreeBSD's GEOM modules, and ZFS. [SorAlx] ridin' VS1400 From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 13:25:06 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C644B1065672; Tue, 8 Jul 2008 13:25:06 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 763358FC18; Tue, 8 Jul 2008 13:25:06 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 9D54A41C70C; Tue, 8 Jul 2008 15:25:05 +0200 (CEST) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id PF60vej65yHT; Tue, 8 Jul 2008 15:25:05 +0200 (CEST) Received: by mail.cksoft.de (Postfix, from userid 66) id 38F2141C733; Tue, 8 Jul 2008 15:25:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id BB99C44487F; Tue, 8 Jul 2008 13:21:12 +0000 (UTC) Date: Tue, 8 Jul 2008 13:21:12 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Ruslan Ermilov In-Reply-To: <20080625202317.GB69011@edoofus.dev.vega.ru> Message-ID: <20080708130323.D57089@maildrop.int.zabbadoz.net> References: <20080618085948.X83875@maildrop.int.zabbadoz.net> <20080618224531.GA20863@what-creek.com> <20080618225126.V83875@maildrop.int.zabbadoz.net> <20080618230633.GB20863@what-creek.com> <20080619151421.Q83875@maildrop.int.zabbadoz.net> <20080623214600.GA51757@sandvine.com> <20080623224150.GA63818@what-creek.com> <20080624085543.S83875@maildrop.int.zabbadoz.net> <20080625202317.GB69011@edoofus.dev.vega.ru> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Ed Maste , John Birrell , FreeBSD current mailing list Subject: Re: problem: world boot strapping from 7-C to HEAD with CDDL on sparc64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 13:25:06 -0000 On Thu, 26 Jun 2008, Ruslan Ermilov wrote: > On Tue, Jun 24, 2008 at 08:57:54AM +0000, Bjoern A. Zeeb wrote: >> On Mon, 23 Jun 2008, John Birrell wrote: >> >>> On Mon, Jun 23, 2008 at 05:46:00PM -0400, Ed Maste wrote: >>>> All that said, I'd really like to be able to continue building head on >>>> RELENG_6. (In my case I have a rather fast RELENG_6 box so I have been >>>> doing my pre-commit testing there.) Do the changes we're discussing >>>> here involve anything that makes that difficult? >>> >>> Possibly. :-) >>> >>> It depends on whether your RELENG_6 box is up-to-date with respect to the >>> RELENG_6 branch. >>> >>> I think that as current diverges more from 7 it will be harder to keep the >>> tree building on 6. >> > Are we talking about changing the build-/cross- tools? If not, > it shouldn't be affected. > >> I think the problem here simply is that you are relying on the headers >> to be installed on the base system instead of in src|obj copies. I do >> not know if/how we do it for bootstrapping though. >> > If it's about build- and cross-tools, then yes, they rely on > the host compiler, headers, etc. because they will be run on > _this_ computer, using its CPU and the current kernel. So if a bootstrap tool cannot be build - what's the solution? The problem is way beyond building HEAD on 6 as we just found out here -- you can no longer update a 6.2-STABLE to 7-STABLE either without going through a latest 6-STABLE or building WITHOUT_CDDL and then rebuilding on 7. Either way its two builds. If I am not mistaken not even 6.3-RELEASE could be source updated to 7-STABLE. And 6.3-RELEASE is the only supported RELENG_6 release at the moment. This is from one STABLE branch to the next STABLE branch. I think this is unacceptable, no matter what and how. -- Bjoern A. Zeeb Stop bit received. Insert coin for new game. From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 13:57:15 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3EB4C1065683; Tue, 8 Jul 2008 13:57:15 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AE8F88FC20; Tue, 8 Jul 2008 13:57:13 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4873723D.7040501@FreeBSD.org> Date: Tue, 08 Jul 2008 15:57:17 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= References: <20080617004647.GA16546@nagual.pp.ru> <48576610.9080808@FreeBSD.org> <48577510.4020007@aueb.gr> <48577BD2.4070205@bluemedia.pl> <20080617102900.GA46479@nagual.pp.ru> <485798C4.2050605@FreeBSD.org> <20080618055851.GA85018@nagual.pp.ru> <86zlpjduew.fsf@ds4.des.no> <48598C6D.4040102@FreeBSD.org> <48727747.7070509@FreeBSD.org> <20080707201447.GA37354@nagual.pp.ru> <48727F14.6090507@FreeBSD.org> <48728301.5070403@FreeBSD.org> <487294AB.3000609@FreeBSD.org> <48736FB7.8070900@FreeBSD.org> In-Reply-To: <48736FB7.8070900@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 13:57:15 -0000 Gábor Kövesdán wrote: > >>> Well, it seems you have missed the first nits of the discussion. GNU >>> grep has some regression test, which doesn't pass completely itself >>> either. :) I've mentioned here that I used those tests to find out >>> what incompatible options are there. Unfortunately, I have to say >>> that BSD grep won't pass all of those, because GNU allows some >>> non-standard regexes, which are rejected by our libc-regex library, >>> like for example (a|) is not standard because it has an empty >>> subexpression. First, I tried to pre-edit such expression in the >>> code. It was ugly enough but I thought: "Ok, this code is pretty >>> ugly, but compatibility is important, maybe we can later revise >>> and/or change our regexp library and get rid of these snippets." >>> Later, when Andrey pointed it out, I realized that my workarounds >>> adressed those incompatibilities but didn't work completely, they >>> broke compatibility at other places, thus I just removed them, >>> because it was not that easy to fix. The version that I sent you for >>> the portbuild test, doesn't have those workarounds. The regression >>> test helped though to fix other compatibility issues, like return >>> values. All of these trivial things are supposed to be compatible >>> now, the only exceptions are the non-standard regexes. That's why I'm >>> so curious about the results. If they are inacceptable, we can try to >>> build BSD grep with the GNU regexp lib (it's in the tree, as Pedro F. >>> Giffuni pointed it out). It doesn't work by just linking with that >>> library, so it will need more work and investigation then, not >>> speaking about that GNU regex should go one day... >> >> OK, yes I did miss the start of the thread, but I was trying to >> suggest that grep doesn't seem to be functional enough yet and this is >> a way to work on identifying what needs to be fixed. > Could you please send me some logs of ports which build with GNU grep > but not with BSD grep? That would help me to identify the problems and > find out if those problems come from non-standard regexes or what's > happening here? No, because every port build fails because egrep -v is failing to work properly in the management scripts :) I sent you mail about this already. Kris From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 14:04:28 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32F3F1065684; Tue, 8 Jul 2008 14:04:28 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) by mx1.freebsd.org (Postfix) with ESMTP id C4EA18FC1D; Tue, 8 Jul 2008 14:04:27 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id C701A14D6582; Tue, 8 Jul 2008 15:46:36 +0200 (CEST) X-Virus-Scanned: amavisd-new at t-hosting.hu Received: from server.mypc.hu ([127.0.0.1]) by localhost (server.mypc.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id jYH+HukW2cdH; Tue, 8 Jul 2008 15:46:31 +0200 (CEST) Received: from [192.168.2.177] (catv-50629c59.catv.broadband.hu [80.98.156.89]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id 99D3514D6581; Tue, 8 Jul 2008 15:46:31 +0200 (CEST) Message-ID: <48736FB7.8070900@FreeBSD.org> Date: Tue, 08 Jul 2008 15:46:31 +0200 From: =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Kris Kennaway References: <20080617004647.GA16546@nagual.pp.ru> <48576610.9080808@FreeBSD.org> <48577510.4020007@aueb.gr> <48577BD2.4070205@bluemedia.pl> <20080617102900.GA46479@nagual.pp.ru> <485798C4.2050605@FreeBSD.org> <20080618055851.GA85018@nagual.pp.ru> <86zlpjduew.fsf@ds4.des.no> <48598C6D.4040102@FreeBSD.org> <48727747.7070509@FreeBSD.org> <20080707201447.GA37354@nagual.pp.ru> <48727F14.6090507@FreeBSD.org> <48728301.5070403@FreeBSD.org> <487294AB.3000609@FreeBSD.org> In-Reply-To: <487294AB.3000609@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 14:04:28 -0000 >> Well, it seems you have missed the first nits of the discussion. GNU >> grep has some regression test, which doesn't pass completely itself >> either. :) I've mentioned here that I used those tests to find out >> what incompatible options are there. Unfortunately, I have to say >> that BSD grep won't pass all of those, because GNU allows some >> non-standard regexes, which are rejected by our libc-regex library, >> like for example (a|) is not standard because it has an empty >> subexpression. First, I tried to pre-edit such expression in the >> code. It was ugly enough but I thought: "Ok, this code is pretty >> ugly, but compatibility is important, maybe we can later revise >> and/or change our regexp library and get rid of these snippets." >> Later, when Andrey pointed it out, I realized that my workarounds >> adressed those incompatibilities but didn't work completely, they >> broke compatibility at other places, thus I just removed them, >> because it was not that easy to fix. The version that I sent you for >> the portbuild test, doesn't have those workarounds. The regression >> test helped though to fix other compatibility issues, like return >> values. All of these trivial things are supposed to be compatible >> now, the only exceptions are the non-standard regexes. That's why I'm >> so curious about the results. If they are inacceptable, we can try to >> build BSD grep with the GNU regexp lib (it's in the tree, as Pedro F. >> Giffuni pointed it out). It doesn't work by just linking with that >> library, so it will need more work and investigation then, not >> speaking about that GNU regex should go one day... > > OK, yes I did miss the start of the thread, but I was trying to > suggest that grep doesn't seem to be functional enough yet and this is > a way to work on identifying what needs to be fixed. Could you please send me some logs of ports which build with GNU grep but not with BSD grep? That would help me to identify the problems and find out if those problems come from non-standard regexes or what's happening here? I've looked at our regex library and it is written by Henry Spencer. He has a slightly newer version, but he seems to be consequent and the implementation choices are the same, those non-standard regexes are still rejected by his library. I've also looked at PCRE, which was mentioned in this list. In fact, PCRE actually has a POSIX-compliant interface, but it's just the interface, the interpreted regexes are still Perl-like. -- Gabor Kovesdan EMAIL: gabor@FreeBSD.org WWW: http://www.kovesdan.org From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 14:16:21 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A6F9106566C; Tue, 8 Jul 2008 14:16:21 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211]) by mx1.freebsd.org (Postfix) with ESMTP id 2B9308FC14; Tue, 8 Jul 2008 14:16:21 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 3AEB41CE27; Tue, 8 Jul 2008 16:16:20 +0200 (CEST) Date: Tue, 8 Jul 2008 16:16:20 +0200 From: Ed Schouten To: FreeBSD Current , FreeBSD Arch Message-ID: <20080708141620.GG14567@hoeg.nl> References: <20080702190901.GS14567@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wQkw7DhpL9hyPo7K" Content-Disposition: inline In-Reply-To: <20080702190901.GS14567@hoeg.nl> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Philip Paeps Subject: MPSAFE TTY schedule - update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 14:16:21 -0000 --wQkw7DhpL9hyPo7K Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello everyone, First of all, I am really impressed by the amount of people that have shown interest in helping me drive this project forward: - kris@ and some other people has been testing the patches. So far they found some small bugs, which should all be fixed now. Thanks! - marcel@ and nyan@ have already been working on uart(4). Last time I heard, they may have already gotten it working on certain pieces of PC98 hardware. - kan@ has committed a patch in the mpsafetty P4 branch to make dcons(4) working again. Thank you! I think I'll continue using this schedule, with some very small changes, based on previous discussions: * Ed Schouten wrote: > - Not all drivers have been ported to the new TTY layer yet. These > drivers still need to be ported: sio(4), cy(4), digi(4), ubser(4), > uftdi(4), nmdm(4), ng_h4(4), ng_tty(4), snp(4), rp(4), rc(4), si(4), > umodem(4), dcons(4). This should now read: - Not all drivers have been ported to the new TTY layer yet. These drivers still need to be ported: sio(4), cy(4), digi(4), ubser(4), nmdm(4), ng_h4(4), ng_tty(4), snp(4), rp(4), rc(4), si(4). If time permits, I'll fix nmdm(4). I've also received some messages about si(4) and digi(4), so I'll contact those people to see what we can do here. Someone emailed me about ng_h4(4), ng_tty(4) and snp(4). There are no short term plans to make these drivers work. I am going to implement a new hooks interface into the TTY layer after we've integrated this patchset. I don't want to bring in too much code in a single run. > July 13 2008: > Make uart(4) the default serial port driver, instead of sio(4). > sio(4) has not been ported to the new TTY layer and is very hard > to do so. uart(4) has been proven to be more portable than > sio(4) and already supports the hardware we need. It looks like we can do this on i386 and amd64. pc98 still needs some polishing, but I've got full confidence this will be sorted out in time. I'll closely track marcel@'s work the next couple of days to make sure we can do this without breaking too much. > August 3 2008: > Disconnect drivers from the build that haven't been patched in > the MPSAFE TTY branch. I won't disconnect drivers here which are in the progress of being ported. If foo@ sends me an email to say he's working on rc(4) for example, I will leave that driver alone. Again, I should bug people with: > Please, make sure we can make this a smooth transition by > testing/reviewing my code. I tend to generate diffs very often. They can > be downloaded here: >=20 > http://www.il.fontys.nl/~ed/projects/mpsafetty/patches/ Thanks! --=20 Ed Schouten WWW: http://80386.nl/ --wQkw7DhpL9hyPo7K Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkhzdrQACgkQ52SDGA2eCwWOnACeLI6jHIyYBGaOOKIYXZIPPEXD W+MAn1BFYUrTZTmYjphD4gL3fnnixZwq =Qe1e -----END PGP SIGNATURE----- --wQkw7DhpL9hyPo7K-- From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 14:48:35 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C174E1065683; Tue, 8 Jul 2008 14:48:35 +0000 (UTC) (envelope-from mtm@wubethiopia.com) Received: from dire.wubethiopia.com (j071.v.rootbsd.net [208.79.82.223]) by mx1.freebsd.org (Postfix) with ESMTP id 9840B8FC14; Tue, 8 Jul 2008 14:48:35 +0000 (UTC) (envelope-from mtm@wubethiopia.com) Received: from rogue.mike.lan (unknown [213.55.70.149]) by dire.wubethiopia.com (Postfix) with ESMTPSA id 778574FD9A90; Tue, 8 Jul 2008 14:48:16 +0000 (UTC) Message-ID: <48737F79.6070401@wubethiopia.com> Date: Tue, 08 Jul 2008 17:53:45 +0300 From: Mike Makonnen User-Agent: Thunderbird 2.0.0.12 (X11/20080323) MIME-Version: 1.0 To: Freddie Cash References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486F8C57.9050908@wubethiopia.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Re: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 14:48:35 -0000 Freddie Cash wrote: > > The tricky part will be getting the disk slicing, slice partitioning, > and filesystem formatting to work reliably, with all the power of > FreeBSD's GEOM modules, and ZFS. > Actually, this is probably the easiest part (at least for UFS). The libdisk(3) library abstracts most of it out of the installer. Cheers. -- Mike Makonnen | GPG-KEY: http://people.freebsd.org/~mtm/mtm.asc mtm @ FreeBSD.Org | AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55 FreeBSD | http://www.freebsd.org From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 14:54:36 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF7F21065685; Tue, 8 Jul 2008 14:54:36 +0000 (UTC) (envelope-from mtm@wubethiopia.com) Received: from dire.wubethiopia.com (j071.v.rootbsd.net [208.79.82.223]) by mx1.freebsd.org (Postfix) with ESMTP id C68528FC25; Tue, 8 Jul 2008 14:54:36 +0000 (UTC) (envelope-from mtm@wubethiopia.com) Received: from rogue.mike.lan (unknown [213.55.81.132]) by dire.wubethiopia.com (Postfix) with ESMTPSA id 575E44FD9A90; Tue, 8 Jul 2008 14:54:26 +0000 (UTC) Message-ID: <487380FA.6080004@wubethiopia.com> Date: Tue, 08 Jul 2008 18:00:10 +0300 From: Mike Makonnen User-Agent: Thunderbird 2.0.0.12 (X11/20080323) MIME-Version: 1.0 To: soralx@cydem.org References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486F8C57.9050908@wubethiopia.com> <20080707213625.69bb0bf4@soralx> In-Reply-To: <20080707213625.69bb0bf4@soralx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, fjwcash@gmail.com Subject: Re: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 14:54:37 -0000 soralx@cydem.org wrote: >> Hear, hear! To be honest, this is the only bit about the current >> sysinstall that I really dislike: the fact that it can be used for >> post-installation configuration and package installation. This causes >> no end of trouble for newbies, who seem to view sysinstall as "The One >> True System Admin Tool" and try to use it for configuring/installing >> everything. Too many times, on various BSD forums, I've had to walk >> people through cleaning up /etc/rc.conf and showing them how to >> correctly install/configure things (using standard FreeBSD tools), >> since they used sysinstall for everything. > > That may be true, but sysinstall did help me do basic, essentical > configuration of my very first installed system, and a few installs after > that (until I learned about /etc/rc.conf et al). And I never regarded it as > The One True Sysadmin Tool, because I did not use Linux distros, thus never > got used to their ways. It's just that the simple configuration menu really > helped me to get a useful system running in a few minutes (though menu items > certainly could make use of more verbose descriptions). And then I could > play with the working system and learn ways to configure it. > > So, IMHO, a basic curses system configuration utility is still needed, and > should be run after sysinstall or it should tell the user how to run it > (maybe in motd, or sysinstall itself?). > Yes, I agree that such a tool is useful, but it does not belong in the installer. In fact, the BSD Installer framework can be used here also to separate the implementation details from the user interface. Cheers. -- Mike Makonnen | GPG-KEY: http://people.freebsd.org/~mtm/mtm.asc mtm @ FreeBSD.Org | AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55 FreeBSD | http://www.freebsd.org From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 15:53:47 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 680EF106564A for ; Tue, 8 Jul 2008 15:53:47 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from proxy.meer.net (proxy.meer.net [64.13.141.13]) by mx1.freebsd.org (Postfix) with ESMTP id 484568FC22 for ; Tue, 8 Jul 2008 15:53:47 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [64.13.141.3]) by proxy.meer.net (8.14.2/8.14.2) with ESMTP id m68FrhXD084449; Tue, 8 Jul 2008 08:53:46 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from mail2.meer.net (mail2.meer.net [64.13.141.16]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id m68FrAGa045034; Tue, 8 Jul 2008 08:53:11 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (209.249.190.254.available.above.net [209.249.190.254] (may be forged)) (authenticated bits=0) by mail2.meer.net (8.14.1/8.14.1) with ESMTP id m68Fr9Ud032185; Tue, 8 Jul 2008 08:53:10 -0700 (PDT) (envelope-from gnn@neville-neil.com) Date: Tue, 08 Jul 2008 11:53:09 -0400 Message-ID: From: gnn@freebsd.org To: Luke S Crawford In-Reply-To: References: User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.1.50 (i386-apple-darwin8.11.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Canit-CHI2: 0.50 X-Bayes-Prob: 0.5 (Score 0, tokens from: ) X-Spam-Score: 0.10 () [Tag at 5.00] COMBINED_FROM X-CanItPRO-Stream: default X-Canit-Stats-ID: 888573 - 34d56a77d41c X-Scanned-By: CanIt (www . roaringpenguin . com) on 64.13.141.13 Cc: current@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 15:53:47 -0000 At 07 Jul 2008 20:19:50 -0400, Luke S Crawford wrote: > > gnn@freebsd.org writes: > > I have hundreds of these files to run this over, and a full check > > takes about 3 hours, but I usually see some form of corruption within > > the first 20 minutes. > > I've seen similar problems happen on a groups of new boxes when the ram was > slightly out of spec for the motherboard. memtest revealed the problem, > returning the lot of ram for a different model fixed the problem. > > > 4) Corruption is seen only after a reboot, if the machines continue to > > run corruption is never seen again, until another reboot. > > This would indicate that I am wrong. Personally, I'd still run memtest86 for > 48 hours or so, just to be sure. > That's been tried. > > does smartctl report weirdness? Nope. Thanks, George From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 19:23:40 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C050106566B; Tue, 8 Jul 2008 19:23:40 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx1.rink.nu (gloom.rink.nu [213.34.49.2]) by mx1.freebsd.org (Postfix) with ESMTP id 513BD8FC1F; Tue, 8 Jul 2008 19:23:40 +0000 (UTC) (envelope-from rink@rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx1.rink.nu (Postfix) with ESMTP id C0B446D41E; Tue, 8 Jul 2008 21:04:11 +0200 (CEST) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx1.rink.nu ([213.34.49.2]) by localhost (gloom.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WKCCkw5yaY-q; Tue, 8 Jul 2008 21:04:07 +0200 (CEST) Received: by mx1.rink.nu (Postfix, from userid 1000) id 86AAB6D41B; Tue, 8 Jul 2008 21:04:07 +0200 (CEST) Date: Tue, 8 Jul 2008 21:04:07 +0200 From: Rink Springer To: Mike Makonnen Message-ID: <20080708190407.GA68713@rink.nu> References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486F8C57.9050908@wubethiopia.com> <48737F79.6070401@wubethiopia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48737F79.6070401@wubethiopia.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, Freddie Cash Subject: Re: Re: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 19:23:40 -0000 On Tue, Jul 08, 2008 at 05:53:45PM +0300, Mike Makonnen wrote: > Freddie Cash wrote: > > > > The tricky part will be getting the disk slicing, slice partitioning, > > and filesystem formatting to work reliably, with all the power of > > FreeBSD's GEOM modules, and ZFS. > > > > Actually, this is probably the easiest part (at least for UFS). The > libdisk(3) library abstracts most of it out of the installer. ...except that libdisk(3) was supposed to be a temporary hack. I'd really suggest that something cleaner is to be written; libdisk(3) really is not the way to go. Have a look at the code and see for yourself. Regards, -- Rink P.W. Springer - http://rink.nu "Anyway boys, this is America. Just because you get more votes doesn't mean you win." - Fox Mulder From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 19:37:49 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C23C7106566C for ; Tue, 8 Jul 2008 19:37:49 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.76]) by mx1.freebsd.org (Postfix) with ESMTP id A36858FC16 for ; Tue, 8 Jul 2008 19:37:49 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp019-bge351000.mac.com (asmtp019-bge351000 [10.150.69.82]) by smtpoutm.mac.com (Xserve/smtpout013/MantshX 4.0) with ESMTP id m68JbnTH016812; Tue, 8 Jul 2008 12:37:49 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from macbook-pro.jnpr.net (natint3.juniper.net [66.129.224.36]) by asmtp019.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3P00H29D70KW20@asmtp019.mac.com>; Tue, 08 Jul 2008 12:37:49 -0700 (PDT) Sender: xcllnt@mac.com Message-id: <47A12EFB-2433-4E60-BE15-48E1BDD22238@mac.com> From: Marcel Moolenaar To: Rink Springer In-reply-to: <20080708190407.GA68713@rink.nu> Date: Tue, 08 Jul 2008 12:37:48 -0700 References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486F8C57.9050908@wubethiopia.com> <48737F79.6070401@wubethiopia.com> <20080708190407.GA68713@rink.nu> X-Mailer: Apple Mail (2.926) Cc: Mike Makonnen , freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 19:37:49 -0000 On Jul 8, 2008, at 12:04 PM, Rink Springer wrote: > On Tue, Jul 08, 2008 at 05:53:45PM +0300, Mike Makonnen wrote: >> Freddie Cash wrote: >>> >>> The tricky part will be getting the disk slicing, slice >>> partitioning, >>> and filesystem formatting to work reliably, with all the power of >>> FreeBSD's GEOM modules, and ZFS. >>> >> >> Actually, this is probably the easiest part (at least for UFS). The >> libdisk(3) library abstracts most of it out of the installer. > > ...except that libdisk(3) was supposed to be a temporary hack. I'd > really > suggest that something cleaner is to be written; libdisk(3) really is > not the way to go. Have a look at the code and see for yourself. Yes, libdisk is bad. GEOM_PART has been designed for use by installers. It can be interfaced faily easily. See gpart(8) for example. FYI, -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 19:45:32 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89BDF1065677 for ; Tue, 8 Jul 2008 19:45:32 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.181]) by mx1.freebsd.org (Postfix) with ESMTP id 0D2268FC24 for ; Tue, 8 Jul 2008 19:45:26 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by ik-out-1112.google.com with SMTP id c30so1432522ika.3 for ; Tue, 08 Jul 2008 12:45:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:received :date:from:to:subject:message-id:mail-followup-to:mime-version :content-type:content-disposition:user-agent; bh=SIe5WdmzHrMz1azvIIo56VEsMnhTZKKhx8sQDhCyTFs=; b=qyUCaob8+hFNYbfLCxuES0vbphul/LEx3i+W9u56g52zdW8I3t4QvaonLUGQrR8wXB cm/o+8aULGpS2gzCBzWx8j6FLiIYq53PXTmVsdFX/EqK2dD92wJcRHEknKuyQ6i7rARi bueRJgqRtkzZ4iRT9+736e1aJJPkBnGlpd280= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-type:content-disposition:user-agent; b=ARMJVVotO/3qdGfNlfWbKRY96P9cfx6Wmc3TxwWC0uf024PqsuPq2VS/T0up0LID+j DB+87H/d4XLpk8INloIG/xgm0J2B70L+VI4IQOEuP5NbJ8iXT38unC4TQmTqflrVaFRZ L32Rg68R7sb6zdt+fQISl24wfhwBQtpEJJhwQ= Received: by 10.210.46.12 with SMTP id t12mr4394184ebt.64.1215546325201; Tue, 08 Jul 2008 12:45:25 -0700 (PDT) Received: from acme.spoerlein.net ( [217.172.44.86]) by mx.google.com with ESMTPS id c25sm9254555ika.11.2008.07.08.12.45.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 08 Jul 2008 12:45:24 -0700 (PDT) Received: from roadrunner.spoerlein.net (e180158225.adsl.alicedsl.de [85.180.158.225]) by acme.spoerlein.net (8.14.2/8.14.2) with ESMTP id m68JiUOc014189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 8 Jul 2008 21:44:31 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: from roadrunner.spoerlein.net (localhost [127.0.0.1]) by roadrunner.spoerlein.net (8.14.2/8.14.2) with ESMTP id m68JjJHX009845 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 8 Jul 2008 21:45:19 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: (from uqs@localhost) by roadrunner.spoerlein.net (8.14.2/8.14.2/Submit) id m68JjIQP009844 for current@freebsd.org; Tue, 8 Jul 2008 21:45:18 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Date: Tue, 8 Jul 2008 21:45:18 +0200 From: Ulrich Spoerlein To: current@freebsd.org Message-ID: <20080708194517.GA9655@roadrunner.spoerlein.net> Mail-Followup-To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Subject: OpenBSD finds 33 year old bug in yacc(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 19:45:32 -0000 Hi, I may have used yacc(1) once, but am in no position to analyze our yacc wrt. the bug found here[1] I grepped the offending pattern, though and it matches right here: % grep -A1 -r 'yym.*=.*yylen' /usr/src/usr.bin/yacc /usr/src/usr.bin/yacc/skeleton.c: " yym = yylen[yyn];", /usr/src/usr.bin/yacc/skeleton.c- " yyval = yyvsp[1-yym];", -- /usr/src/usr.bin/yacc/test/error.tab.c: yym = yylen[yyn]; /usr/src/usr.bin/yacc/test/error.tab.c- yyval = yyvsp[1-yym]; -- /usr/src/usr.bin/yacc/test/ftp.tab.c: yym = yylen[yyn]; /usr/src/usr.bin/yacc/test/ftp.tab.c- yyval = yyvsp[1-yym]; I didn't find any recent commits to these files, so perhaps the bug is still there? [1] http://undeadly.org/cgi?action=article&sid=20080708155228 Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 19:56:03 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E87481065674 for ; Tue, 8 Jul 2008 19:56:03 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.64]) by mx1.freebsd.org (Postfix) with ESMTP id B73B98FC22 for ; Tue, 8 Jul 2008 19:56:03 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtp022-bge351000.mac.com (asmtp022-bge351000 [10.150.69.85]) by smtpoutm.mac.com (Xserve/smtpout001/MantshX 4.0) with ESMTP id m68Ju354010754 for ; Tue, 8 Jul 2008 12:56:03 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed Received: from macbook-pro.jnpr.net (natint3.juniper.net [66.129.224.36]) by asmtp022.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3P0013VE1DQG80@asmtp022.mac.com> for current@freebsd.org; Tue, 08 Jul 2008 12:56:03 -0700 (PDT) Sender: xcllnt@mac.com Message-id: <80A53B28-6F03-4448-A231-7AB770E2EEFC@mac.com> From: Marcel Moolenaar To: Ulrich Spoerlein In-reply-to: <20080708194517.GA9655@roadrunner.spoerlein.net> Date: Tue, 08 Jul 2008 12:56:01 -0700 References: <20080708194517.GA9655@roadrunner.spoerlein.net> X-Mailer: Apple Mail (2.926) Cc: current@freebsd.org Subject: Re: OpenBSD finds 33 year old bug in yacc(1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 19:56:04 -0000 On Jul 8, 2008, at 12:45 PM, Ulrich Spoerlein wrote: > I didn't find any recent commits to these files, so perhaps the bug is > still there? Yes, it looks like it. -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Tue Jul 8 22:12:10 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 918E81065675 for ; Tue, 8 Jul 2008 22:12:10 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.183]) by mx1.freebsd.org (Postfix) with ESMTP id 486AB8FC19 for ; Tue, 8 Jul 2008 22:12:10 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: by el-out-1112.google.com with SMTP id v27so410733ele.13 for ; Tue, 08 Jul 2008 15:12:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=lrQfrgAbbXcSIgxvtTaeH7Cp0+oiEsgb3HKOxS6X4Co=; b=AV7Ctpayl2leYfkv4jSOyG85iKg6PC7pcWXZw0cqE1GlD0MNSOIMLlM5bO/lkHQKid zwHHE8zkglpbrgAvwdJSlE3UzAuv6LSd/HmhXWT1scrhCLKhEirhp46zbDvZ9EhnIOOQ cQVj/CXYJKZi/ZIGX8KydKVI1yu7AezOfN7rk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=pLVjBJY+SPzj2Dpgxg9rIqX9spOFCUQAGXBFcPzCaX+36cPkO3JNHfcrQ5lbzKW8lT Emsy4T9ZOI9A3lWvw2INObrHoz5Sscg/QLuUYyPTGIHCfsGgMpDyPIQbfFC6H8ucyZ0Q AwLvFZjFfCIfgN/kv3ps7yq2/mVE6Fg0d5l0s= Received: by 10.151.142.16 with SMTP id u16mr11095707ybn.177.1215555129537; Tue, 08 Jul 2008 15:12:09 -0700 (PDT) Received: by 10.150.178.1 with HTTP; Tue, 8 Jul 2008 15:12:09 -0700 (PDT) Message-ID: <2fd864e0807081512j1326c321w72d54cc5bae69b61@mail.gmail.com> Date: Wed, 9 Jul 2008 06:12:09 +0800 From: Astrodog To: "gnn@freebsd.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: current@freebsd.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2008 22:12:10 -0000 On 7/8/08, gnn@freebsd.org wrote: > At 07 Jul 2008 20:19:50 -0400, > > Luke S Crawford wrote: > > > > gnn@freebsd.org writes: > > > I have hundreds of these files to run this over, and a full check > > > takes about 3 hours, but I usually see some form of corruption within > > > the first 20 minutes. > > > > I've seen similar problems happen on a groups of new boxes when the ram was > > slightly out of spec for the motherboard. memtest revealed the problem, > > returning the lot of ram for a different model fixed the problem. > > > > > 4) Corruption is seen only after a reboot, if the machines continue to > > > run corruption is never seen again, until another reboot. > > > > This would indicate that I am wrong. Personally, I'd still run memtest86 for > > 48 hours or so, just to be sure. > > > > > That's been tried. > > > > > does smartctl report weirdness? > > Nope. I've got a few systems with in a nearly identical configuration that are not displaying this behavior. Is there anything special about these systems? Are there any PCI cards aside from the controller? --- Harrison From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 03:28:52 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC96D106568A for ; Wed, 9 Jul 2008 03:28:52 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id 6C1158FC1E for ; Wed, 9 Jul 2008 03:28:52 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 55324 invoked by uid 2001); 9 Jul 2008 03:02:10 -0000 Date: Tue, 8 Jul 2008 22:02:09 -0500 From: "Rick C. Petty" To: Freddie Cash Message-ID: <20080709030209.GA55030@keira.kiwi-computer.com> References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486F8C57.9050908@wubethiopia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Wed, 09 Jul 2008 03:36:57 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 03:28:53 -0000 On Mon, Jul 07, 2008 at 11:55:41AM -0700, Freddie Cash wrote: > > IMO, the installer should allow you to partition the disk(s), format > the partition(s), install the OS, configure a user, and reboot the > system. Anything beyond that should be handled by the OS tools, from > within the installed and running OS. It already does all of that, but why reboot right away? The first thing I do while the system is installing is run csup(1) to get the latest source, build and install world/kernel, and build all my ports. I also setup my gmirror and do all my configuration. The only reason I reboot is to use the latest kernel and mount from the mirror. I'd like to see other OSes do all of that. -- Rick C. Petty From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 05:52:13 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0002C106566B for ; Wed, 9 Jul 2008 05:52:12 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.191]) by mx1.freebsd.org (Postfix) with ESMTP id 634968FC17 for ; Wed, 9 Jul 2008 05:52:11 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: by ti-out-0910.google.com with SMTP id d27so982792tid.3 for ; Tue, 08 Jul 2008 22:52:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:to:subject :message-id:mail-followup-to:mime-version:content-type :content-disposition:user-agent:organization:x-operation-sytem:from; bh=WZd9IWmIFzmm+flPOPqP+v1h/JdHm/6EbX17ImLmWdg=; b=nsR46KNeJpG7II0XuoDq0QdXdPFIepJTEEu5zz58Eqk7ejBWJbkvh0WZNXLEP5QGIa HLItT6NojipG9vAYPsDOrcv/DNu57GYyKfndg2YQSIJUmnphA7xCIR4xeeQ+FOt6/lTR 7wM1D2b47SNrAXZVPW1nHa3wJoOnxRVhOZDZo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:to:subject:message-id:mail-followup-to:mime-version :content-type:content-disposition:user-agent:organization :x-operation-sytem:from; b=dTfPP1zMHB0qHHD0nmCxArMicQdSIG/1Uq9ALpCgb2nwGAEsCCYJgobP/gNhO20oOS R3nzKPuooXWekaAQBRi5T14OG3B2JRRJ5QTZrgWHp8mad5bAiT3fGunpfc/ENKkpSzL6 eR3wmeZVynHlFGDtq9WwUdlo1zKz2ARYNsPD4= Received: by 10.110.70.17 with SMTP id s17mr4193286tia.55.1215581171849; Tue, 08 Jul 2008 22:26:11 -0700 (PDT) Received: from freebsd.weongyo.org ( [211.53.35.67]) by mx.google.com with ESMTPS id d7sm9292089tib.4.2008.07.08.22.26.09 (version=SSLv3 cipher=RC4-MD5); Tue, 08 Jul 2008 22:26:09 -0700 (PDT) Received: by freebsd.weongyo.org (sSMTP sendmail emulation); Wed, 9 Jul 2008 14:25:43 +0900 Date: Wed, 9 Jul 2008 14:25:43 +0900 To: FreeBSD Current Message-ID: <20080709052543.GC26288@freebsd.weongyo.org> Mail-Followup-To: FreeBSD Current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD From: Weongyo Jeong Subject: CFT: upgt(4) - Conexant/Intersil PrismGT wireless USB driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 05:52:13 -0000 Hello, I'd like to get problem reports of upgt(4) driver before committing this work to HEAD. This driver obtained from OpenBSD upgt(4) and a patch can be found here: http://people.freebsd.org/~weongyo/patch_upgt_20080709.diff In current implementations, It supports USB 2.0 adapters based on GW3887 chipset and I succeeded to connect to AP with normal connection and WPA. (My device was Netgear WG111v2) AFAIK this device also supports big/little endian archs though it's not tested. You needs to load a firmware module (upgtfw) whose URL can be found the upgt(4) manpage. Please see it. regards, Weongyo Jeong From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 09:40:07 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E9EC106566C; Wed, 9 Jul 2008 09:40:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id E604C8FC1A; Wed, 9 Jul 2008 09:40:06 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 38BB541C76D; Wed, 9 Jul 2008 11:40:05 +0200 (CEST) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id AqDoDvZnYIk2; Wed, 9 Jul 2008 11:40:04 +0200 (CEST) Received: by mail.cksoft.de (Postfix, from userid 66) id DA27D41C759; Wed, 9 Jul 2008 11:40:04 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id C697C44487F; Wed, 9 Jul 2008 09:39:10 +0000 (UTC) Date: Wed, 9 Jul 2008 09:39:10 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Ruslan Ermilov In-Reply-To: <20080708130323.D57089@maildrop.int.zabbadoz.net> Message-ID: <20080709093344.A57089@maildrop.int.zabbadoz.net> References: <20080618085948.X83875@maildrop.int.zabbadoz.net> <20080618224531.GA20863@what-creek.com> <20080618225126.V83875@maildrop.int.zabbadoz.net> <20080618230633.GB20863@what-creek.com> <20080619151421.Q83875@maildrop.int.zabbadoz.net> <20080623214600.GA51757@sandvine.com> <20080623224150.GA63818@what-creek.com> <20080624085543.S83875@maildrop.int.zabbadoz.net> <20080625202317.GB69011@edoofus.dev.vega.ru> <20080708130323.D57089@maildrop.int.zabbadoz.net> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Ed Maste , John Birrell , FreeBSD current mailing list Subject: Re: problem: world boot strapping from 7-C to HEAD with CDDL on sparc64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 09:40:07 -0000 On Tue, 8 Jul 2008, Bjoern A. Zeeb wrote: > The problem is way beyond building HEAD on 6 as we just found out > here -- you can no longer update a 6.2-STABLE to 7-STABLE either > without going through a latest 6-STABLE or building WITHOUT_CDDL > and then rebuilding on 7. Either way its two builds. I take that back. Do not try to assume you are building 7 when you checked out HEAD:( Is the DTRACE work on any MFC list? If yes, we'll make sure to not get into the trap I assumed we are entrapped already. /bz -- Bjoern A. Zeeb Stop bit received. Insert coin for new game. From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 11:32:03 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 284DF106564A; Wed, 9 Jul 2008 11:32:03 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id A3A358FC0A; Wed, 9 Jul 2008 11:32:02 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.2/8.14.2) with ESMTP id m69BW1aY064246; Wed, 9 Jul 2008 15:32:01 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Wed, 9 Jul 2008 15:32:01 +0400 (MSD) From: Dmitry Morozovsky To: Kris Kennaway In-Reply-To: <48749EA7.40702@FreeBSD.org> Message-ID: <20080709152739.Q58331@woozle.rinet.ru> References: <20080708100701.57031cda@twoflower.in.publishing.hu> <4873C4FA.2020004@FreeBSD.org> <20080709062533.J58331@woozle.rinet.ru> <48749087.4070802@FreeBSD.org> <20080709145010.Q58331@woozle.rinet.ru> <48749EA7.40702@FreeBSD.org> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (woozle.rinet.ru [0.0.0.0]); Wed, 09 Jul 2008 15:32:01 +0400 (MSD) Cc: current@FreeBSD.org Subject: Re: Thinking of using ZFS/FBSD for a backup system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 11:32:03 -0000 On Wed, 9 Jul 2008, Kris Kennaway wrote: KK> > marck@wizzle:/usr/ports> grep -Ril zfs Tools/ KK> > Tools/portbuild/scripts/claim-chroot KK> > Tools/portbuild/scripts/clean-chroot KK> > Tools/portbuild/scripts/cleanup-chroots KK> > KK> > ;-) KK> > KK> > Any pitfalls while using this? Thanks! KK> KK> It's still settling on pointyhat, but you could check it out there if you KK> like. The most annoying thing is actually a limitation of the FreeBSD NFS KK> server, since it returns errors to clients while it is reloading the export KK> list. Argh. And, which process is reporting an error? nfsd or some of kthreads? In the former case, is it possible to create new master-slave process tree, rebinding and signalling old tree to exit when all requests are finished? The same approach is used by www/nginx to both seamless configuration change and also binary file upgrade. CC:ing -current@ to ensure the theme have a bit broader audience. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 11:43:17 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33FAA1065683 for ; Wed, 9 Jul 2008 11:43:17 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6B3B88FC14; Wed, 9 Jul 2008 11:43:16 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4874A453.7060406@FreeBSD.org> Date: Wed, 09 Jul 2008 13:43:15 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Dmitry Morozovsky References: <20080708100701.57031cda@twoflower.in.publishing.hu> <4873C4FA.2020004@FreeBSD.org> <20080709062533.J58331@woozle.rinet.ru> <48749087.4070802@FreeBSD.org> <20080709145010.Q58331@woozle.rinet.ru> <48749EA7.40702@FreeBSD.org> <20080709152739.Q58331@woozle.rinet.ru> In-Reply-To: <20080709152739.Q58331@woozle.rinet.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org Subject: Re: Thinking of using ZFS/FBSD for a backup system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 11:43:17 -0000 Dmitry Morozovsky wrote: > On Wed, 9 Jul 2008, Kris Kennaway wrote: > > KK> > marck@wizzle:/usr/ports> grep -Ril zfs Tools/ > KK> > Tools/portbuild/scripts/claim-chroot > KK> > Tools/portbuild/scripts/clean-chroot > KK> > Tools/portbuild/scripts/cleanup-chroots > KK> > > KK> > ;-) > KK> > > KK> > Any pitfalls while using this? Thanks! > KK> > KK> It's still settling on pointyhat, but you could check it out there if you > KK> like. The most annoying thing is actually a limitation of the FreeBSD NFS > KK> server, since it returns errors to clients while it is reloading the export > KK> list. > > Argh. And, which process is reporting an error? nfsd or some of kthreads? In > the former case, is it possible to create new master-slave process > tree, rebinding and signalling old tree to exit when all requests are finished? > > The same approach is used by www/nginx to both seamless configuration change > and also binary file upgrade. > > CC:ing -current@ to ensure the theme have a bit broader audience. The problem is that updating the NFS export list is not atomic. Instead, it is deleted and reloaded. This means that client I/O requests that are received during the window do not correspond to a valid export, and the server dutifully returns an error to the client. This is made worse by the practice of mount(8) (and zfs(8)) of SIGHUP'ing mountd every time a new filesystem is mounted (even if it's not exported). I have disabled this locally, but it doesn't help when I really do want to export a newly mounted filesystem but I have clients doing I/O. A few years ago there was a patch from Andrey Simonenko that implemented atomically reloading the mount list, although it was unfortunately a mixture of these and other changes including some that might be seen as gratuitous (e.g. it depended on a new library). Unfortunately the patch no longer seems to be available on the original website and my attempt to contact Andrey has failed. Kris From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 12:35:58 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23010106564A; Wed, 9 Jul 2008 12:35:58 +0000 (UTC) (envelope-from aslam_mohamed@wordbank.com) Received: from mail.wordbank.com (mail.wordbank.com [213.86.82.65]) by mx1.freebsd.org (Postfix) with ESMTP id 757D28FC0A; Wed, 9 Jul 2008 12:35:57 +0000 (UTC) (envelope-from aslam_mohamed@wordbank.com) Received: from mail.wordbank.com (mail.wordbank.com [10.1.1.10]) by spammy.wordbank.com (Postfix) with ESMTP id 35B0F5C004; Wed, 9 Jul 2008 13:05:22 +0100 (BST) Received: from 10.1.1.115 by mail.wordbank.com ([10.1.1.10] running VPOP3) with ESMTP; Wed, 9 Jul 2008 13:02:35 +0100 Message-ID: <4874A981.7080106@wordbank.com> Date: Wed, 09 Jul 2008 13:05:21 +0100 From: aslam_mohamed@wordbank.com Organization: Wordbank User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Kris Kennaway References: <20080708100701.57031cda@twoflower.in.publishing.hu> <4873C4FA.2020004@FreeBSD.org> <20080709062533.J58331@woozle.rinet.ru> <48749087.4070802@FreeBSD.org> <20080709145010.Q58331@woozle.rinet.ru> <48749EA7.40702@FreeBSD.org> <20080709152739.Q58331@woozle.rinet.ru> <4874A453.7060406@FreeBSD.org> In-Reply-To: <4874A453.7060406@FreeBSD.org> X-Server: VPOP3 V1.5.4 - Registered Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Dmitry Morozovsky , current@FreeBSD.org Subject: Re: Thinking of using ZFS/FBSD for a backup system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 12:35:58 -0000 Hi, I have been using FreeBSD/ZFS for our backup system for last few months.. We had 6TB external disks connected through Firewire to the Server. Last week all the backup data disappeared along with the pool and everything!!!..When I typed zpool status - it says no pool available..Build up to this incident has always been a firefighting situation for me. We use Rsync to sync all the servers to FreeBSD's ZFS pool everyday. Most of the time Rsync hung on the middle of the syncing process. When this happen I have to restart the server to run the backup again and mount the ZFS pool (it requires manual mounting most of the time!!). Sometimes it throws some error like - GEOM: da0: corrupt or invalid GPT detected. GEOM: da0: GPT rejected -- may not be recoverable. GEOM: da1: corrupt or invalid GPT detected. GEOM: da1: GPT rejected -- may not be recoverable I don't know what caused the disappearance of the ZFS pool and if someone could explain how I can retrieve the data from the external disks, that would be really helpful?.. Many Thanks Aslam Mohamed Network Support Analyst Kris Kennaway wrote: > Dmitry Morozovsky wrote: >> On Wed, 9 Jul 2008, Kris Kennaway wrote: >> >> KK> > marck@wizzle:/usr/ports> grep -Ril zfs Tools/ >> KK> > Tools/portbuild/scripts/claim-chroot >> KK> > Tools/portbuild/scripts/clean-chroot >> KK> > Tools/portbuild/scripts/cleanup-chroots >> KK> > KK> > ;-) >> KK> > KK> > Any pitfalls while using this? Thanks! >> KK> KK> It's still settling on pointyhat, but you could check it out >> there if you >> KK> like. The most annoying thing is actually a limitation of the >> FreeBSD NFS >> KK> server, since it returns errors to clients while it is reloading >> the export >> KK> list. >> >> Argh. And, which process is reporting an error? nfsd or some of >> kthreads? In the former case, is it possible to create new >> master-slave process tree, rebinding and signalling old tree to exit >> when all requests are finished? >> >> The same approach is used by www/nginx to both seamless configuration >> change and also binary file upgrade. >> >> CC:ing -current@ to ensure the theme have a bit broader audience. > > The problem is that updating the NFS export list is not atomic. > Instead, it is deleted and reloaded. This means that client I/O > requests that are received during the window do not correspond to a > valid export, and the server dutifully returns an error to the client. > > This is made worse by the practice of mount(8) (and zfs(8)) of > SIGHUP'ing mountd every time a new filesystem is mounted (even if it's > not exported). I have disabled this locally, but it doesn't help when > I really do want to export a newly mounted filesystem but I have > clients doing I/O. > > A few years ago there was a patch from Andrey Simonenko > that implemented atomically reloading > the mount list, although it was unfortunately a mixture of these and > other changes including some that might be seen as gratuitous (e.g. it > depended on a new library). Unfortunately the patch no longer seems > to be available on the original website and my attempt to contact > Andrey has failed. > > Kris > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 12:56:45 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51A4D1065678 for ; Wed, 9 Jul 2008 12:56:45 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4C2318FC12; Wed, 9 Jul 2008 12:56:44 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4874B58B.7000108@FreeBSD.org> Date: Wed, 09 Jul 2008 14:56:43 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: aslam_mohamed@wordbank.com References: <20080708100701.57031cda@twoflower.in.publishing.hu> <4873C4FA.2020004@FreeBSD.org> <20080709062533.J58331@woozle.rinet.ru> <48749087.4070802@FreeBSD.org> <20080709145010.Q58331@woozle.rinet.ru> <48749EA7.40702@FreeBSD.org> <20080709152739.Q58331@woozle.rinet.ru> <4874A453.7060406@FreeBSD.org> <4874A981.7080106@wordbank.com> In-Reply-To: <4874A981.7080106@wordbank.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Dmitry Morozovsky , current@FreeBSD.org Subject: Re: Thinking of using ZFS/FBSD for a backup system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 12:56:45 -0000 aslam_mohamed@wordbank.com wrote: > Hi, > I have been using FreeBSD/ZFS for our backup system for last few > months.. We had 6TB external disks connected through Firewire to the > Server. Last week all the backup data disappeared along with the pool > and everything!!!..When I typed zpool status - it says no pool > available..Build up to this incident has always been a firefighting > situation for me. We use Rsync to sync all the servers to FreeBSD's ZFS > pool everyday. Most of the time Rsync hung on the middle of the syncing > process. When this happen I have to restart the server to run the > backup again and mount the ZFS pool (it requires manual mounting most > of the time!!). Sometimes it throws some error like - > GEOM: da0: corrupt or invalid GPT detected. > GEOM: da0: GPT rejected -- may not be recoverable. > GEOM: da1: corrupt or invalid GPT detected. > GEOM: da1: GPT rejected -- may not be recoverable > I don't know what caused the disappearance of the ZFS pool and if > someone could explain how I can retrieve the data from the external > disks, that would be really helpful?.. What you pasted says that the disks were rejected by GEOM because the partition table was "corrupt or invalid". I don't know for sure why this might be, but one possible cause would be if there is data corruption in your I/O path. Do you get errors from ZFS about checksum failures or other errors? Maybe there is a problem with the firewire stack, or support for your firewire hardware. The rsync hanging is almost certainly either for the same memory reasons we have been discussing, or a side effect of I/O problems to the disks. Kris From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 13:37:05 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C71DE1065671; Wed, 9 Jul 2008 13:37:05 +0000 (UTC) (envelope-from aslam_mohamed@wordbank.com) Received: from mail.wordbank.com (mail.wordbank.com [213.86.82.65]) by mx1.freebsd.org (Postfix) with ESMTP id 5AB148FC1C; Wed, 9 Jul 2008 13:37:05 +0000 (UTC) (envelope-from aslam_mohamed@wordbank.com) Received: from mail.wordbank.com (mail.wordbank.com [10.1.1.10]) by spammy.wordbank.com (Postfix) with ESMTP id 485DF5C001; Wed, 9 Jul 2008 14:37:04 +0100 (BST) Received: from 10.1.1.115 by mail.wordbank.com ([10.1.1.10] running VPOP3) with ESMTP; Wed, 9 Jul 2008 14:34:18 +0100 Message-ID: <4874BEFF.20202@wordbank.com> Date: Wed, 09 Jul 2008 14:37:03 +0100 From: aslam_mohamed@wordbank.com Organization: Wordbank User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Kris Kennaway References: <20080708100701.57031cda@twoflower.in.publishing.hu> <4873C4FA.2020004@FreeBSD.org> <20080709062533.J58331@woozle.rinet.ru> <48749087.4070802@FreeBSD.org> <20080709145010.Q58331@woozle.rinet.ru> <48749EA7.40702@FreeBSD.org> <20080709152739.Q58331@woozle.rinet.ru> <4874A453.7060406@FreeBSD.org> <4874A981.7080106@wordbank.com> <4874B58B.7000108@FreeBSD.org> In-Reply-To: <4874B58B.7000108@FreeBSD.org> X-Server: VPOP3 V1.5.4 - Registered Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Dmitry Morozovsky , current@FreeBSD.org Subject: Re: Thinking of using ZFS/FBSD for a backup system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 13:37:05 -0000 Thanks for your reply. I did get some weired messages like ' vdev failure' just two days before the ZFS pool disappeared, but I don't know whether this is from ZFS or another GEOM issue. I shut the machine down and restarted everything back and got it to do the sync again. Later I noticed zpool status was showing some big numbers like (83, 90 ...) on checksum column. I did the zpool clear and it cleared the numbers. Then I think couple days later the sync process stopped in the middle. When I investigated it, I found that zpool status is not there. I think the firewire/FreeBSD could be a potential contributor to this problem. Now I am trying to recover the backup data (if there is any in external disks!!) by connecting the external disks to SUN Solaris and getting the SUN/ZFS to see the pool!!!.. I cant think of any other ways to recover the backup!!!.. Aslam Kris Kennaway wrote: > aslam_mohamed@wordbank.com wrote: >> Hi, >> I have been using FreeBSD/ZFS for our backup system for last few >> months.. We had 6TB external disks connected through Firewire to the >> Server. Last week all the backup data disappeared along with the pool >> and everything!!!..When I typed zpool status - it says no pool >> available..Build up to this incident has always been a firefighting >> situation for me. We use Rsync to sync all the servers to FreeBSD's >> ZFS pool everyday. Most of the time Rsync hung on the middle of the >> syncing process. When this happen I have to restart the server to >> run the backup again and mount the ZFS pool (it requires manual >> mounting most of the time!!). Sometimes it throws some error like - >> GEOM: da0: corrupt or invalid GPT detected. >> GEOM: da0: GPT rejected -- may not be recoverable. >> GEOM: da1: corrupt or invalid GPT detected. >> GEOM: da1: GPT rejected -- may not be recoverable >> I don't know what caused the disappearance of the ZFS pool and if >> someone could explain how I can retrieve the data from the external >> disks, that would be really helpful?.. > > What you pasted says that the disks were rejected by GEOM because the > partition table was "corrupt or invalid". I don't know for sure why > this might be, but one possible cause would be if there is data > corruption in your I/O path. Do you get errors from ZFS about > checksum failures or other errors? Maybe there is a problem with the > firewire stack, or support for your firewire hardware. > > The rsync hanging is almost certainly either for the same memory > reasons we have been discussing, or a side effect of I/O problems to > the disks. > > Kris > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 13:56:33 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8803F1065672 for ; Wed, 9 Jul 2008 13:56:33 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DB91D8FC12; Wed, 9 Jul 2008 13:56:31 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4874C38F.9040706@FreeBSD.org> Date: Wed, 09 Jul 2008 15:56:31 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: aslam_mohamed@wordbank.com References: <20080708100701.57031cda@twoflower.in.publishing.hu> <4873C4FA.2020004@FreeBSD.org> <20080709062533.J58331@woozle.rinet.ru> <48749087.4070802@FreeBSD.org> <20080709145010.Q58331@woozle.rinet.ru> <48749EA7.40702@FreeBSD.org> <20080709152739.Q58331@woozle.rinet.ru> <4874A453.7060406@FreeBSD.org> <4874A981.7080106@wordbank.com> <4874B58B.7000108@FreeBSD.org> <4874BEFF.20202@wordbank.com> In-Reply-To: <4874BEFF.20202@wordbank.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Dmitry Morozovsky , current@FreeBSD.org Subject: Re: Thinking of using ZFS/FBSD for a backup system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 13:56:33 -0000 aslam_mohamed@wordbank.com wrote: > Thanks for your reply. I did get some weired messages like ' vdev > failure' just two days before the ZFS pool disappeared, but I don't > know whether this is from ZFS or another GEOM issue. I shut the machine > down and restarted everything back and got it to do the sync again. > Later I noticed zpool status was showing some big numbers like (83, 90 > ...) on checksum column. I did the zpool clear and it cleared the > numbers. Then I think couple days later the sync process stopped in the > middle. When I investigated it, I found that zpool status is not there. > I think the firewire/FreeBSD could be a potential contributor to this > problem. Now I am trying to recover the backup data (if there is any in > external disks!!) by connecting the external disks to SUN Solaris and > getting the SUN/ZFS to see the pool!!!.. I cant think of any other ways > to recover the backup!!!.. It probably should have set off alarms for you when you first started seeing checksum failures. That indicates a serious problem! At this point, it sounds like your data might be highly corrupted, and unfortunately, perhaps too corrupted to recover. Kris From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 14:23:39 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA482106567F; Wed, 9 Jul 2008 14:23:39 +0000 (UTC) (envelope-from aslam_mohamed@wordbank.com) Received: from mail.wordbank.com (mail.wordbank.com [213.86.82.65]) by mx1.freebsd.org (Postfix) with ESMTP id 4CF588FC1F; Wed, 9 Jul 2008 14:23:39 +0000 (UTC) (envelope-from aslam_mohamed@wordbank.com) Received: from mail.wordbank.com (mail.wordbank.com [10.1.1.10]) by spammy.wordbank.com (Postfix) with ESMTP id 6FD085C005; Wed, 9 Jul 2008 15:23:38 +0100 (BST) Received: from 10.1.1.115 by mail.wordbank.com ([10.1.1.10] running VPOP3) with ESMTP; Wed, 9 Jul 2008 15:20:52 +0100 Message-ID: <4874C9E9.1050206@wordbank.com> Date: Wed, 09 Jul 2008 15:23:37 +0100 From: aslam_mohamed@wordbank.com Organization: Wordbank User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Kris Kennaway References: <20080708100701.57031cda@twoflower.in.publishing.hu> <4873C4FA.2020004@FreeBSD.org> <20080709062533.J58331@woozle.rinet.ru> <48749087.4070802@FreeBSD.org> <20080709145010.Q58331@woozle.rinet.ru> <48749EA7.40702@FreeBSD.org> <20080709152739.Q58331@woozle.rinet.ru> <4874A453.7060406@FreeBSD.org> <4874A981.7080106@wordbank.com> <4874B58B.7000108@FreeBSD.org> <4874BEFF.20202@wordbank.com> <4874C38F.9040706@FreeBSD.org> In-Reply-To: <4874C38F.9040706@FreeBSD.org> X-Server: VPOP3 V1.5.4 - Registered Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Dmitry Morozovsky , current@FreeBSD.org Subject: Re: Thinking of using ZFS/FBSD for a backup system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 14:23:39 -0000 Something interesting, I just slot couple of 1TB SATA in to the same FreeBSD machine and re-created the zfs pool (this is just to make sure that without firewire the ZFS can work well in FeeBSD) . When I reboot the machine I see the following appears on booting... This is the same thing appeared before with Firewire!! ad4: 76324MB at ata2-master SATA150 ad8: 953869MB at ata4-master SATA150 ad10: 953869MB at ata5-master SATA150 **GEOM: ad8: corrupt or invalid GPT detected.** **GEOM: ad8: GPT rejected -- may not be recoverable.** **GEOM: ad10: corrupt or invalid GPT detected.** **GEOM: ad10: GPT rejected -- may not be recoverable.** SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad4s1a WARNING: ZFS is considered to be an experimental feature in FreeBSD. ZFS filesystem version 6 ZFS storage pool version 6 Now I am running Rsync to backup all the file servers and it had done up to 1TB without complaining.. Currently, the Zpool status looks pretty OK.. pool: backup state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM backup ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad10 ONLINE 0 0 0 errors: No known data errors I don't know in the future there will be any issue because of this Geom messages... is there any known problem like zfs/geom/gpt incompatibility?.. is it the ZFS causing this error(!) messages?..any thoughts?... Thanks Kris Kennaway wrote: > aslam_mohamed@wordbank.com wrote: >> Thanks for your reply. I did get some weired messages like ' vdev >> failure' just two days before the ZFS pool disappeared, but I don't >> know whether this is from ZFS or another GEOM issue. I shut the >> machine down and restarted everything back and got it to do the sync >> again. Later I noticed zpool status was showing some big numbers like >> (83, 90 ...) on checksum column. I did the zpool clear and it cleared >> the numbers. Then I think couple days later the sync process stopped >> in the middle. When I investigated it, I found that zpool status is >> not there. I think the firewire/FreeBSD could be a potential >> contributor to this problem. Now I am trying to recover the backup >> data (if there is any in external disks!!) by connecting the external >> disks to SUN Solaris and getting the SUN/ZFS to see the pool!!!.. I >> cant think of any other ways to recover the backup!!!.. > > It probably should have set off alarms for you when you first started > seeing checksum failures. That indicates a serious problem! At this > point, it sounds like your data might be highly corrupted, and > unfortunately, perhaps too corrupted to recover. > > Kris > From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 14:29:31 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A4311065677 for ; Wed, 9 Jul 2008 14:29:31 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3522C8FC22; Wed, 9 Jul 2008 14:29:30 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4874CB49.50705@FreeBSD.org> Date: Wed, 09 Jul 2008 16:29:29 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: aslam_mohamed@wordbank.com References: <20080708100701.57031cda@twoflower.in.publishing.hu> <4873C4FA.2020004@FreeBSD.org> <20080709062533.J58331@woozle.rinet.ru> <48749087.4070802@FreeBSD.org> <20080709145010.Q58331@woozle.rinet.ru> <48749EA7.40702@FreeBSD.org> <20080709152739.Q58331@woozle.rinet.ru> <4874A453.7060406@FreeBSD.org> <4874A981.7080106@wordbank.com> <4874B58B.7000108@FreeBSD.org> <4874BEFF.20202@wordbank.com> <4874C38F.9040706@FreeBSD.org> <4874C9E9.1050206@wordbank.com> In-Reply-To: <4874C9E9.1050206@wordbank.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Dmitry Morozovsky , current@FreeBSD.org Subject: Re: Thinking of using ZFS/FBSD for a backup system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 14:29:31 -0000 aslam_mohamed@wordbank.com wrote: > Something interesting, I just slot couple of 1TB SATA in to the same > FreeBSD machine and re-created the zfs pool (this is just to make sure > that without firewire the ZFS can work well in FeeBSD) . When I reboot > the machine I see the following appears on booting... This is the same > thing appeared before with Firewire!! > > ad4: 76324MB at ata2-master SATA150 > ad8: 953869MB at ata4-master SATA150 > ad10: 953869MB at ata5-master SATA150 > **GEOM: ad8: corrupt or invalid GPT detected.** > **GEOM: ad8: GPT rejected -- may not be recoverable.** > **GEOM: ad10: corrupt or invalid GPT detected.** > **GEOM: ad10: GPT rejected -- may not be recoverable.** > SMP: AP CPU #1 Launched! > Trying to mount root from ufs:/dev/ad4s1a > WARNING: ZFS is considered to be an experimental feature in FreeBSD. > ZFS filesystem version 6 > ZFS storage pool version 6 > > Now I am running Rsync to backup all the file servers and it had done up > to 1TB without complaining.. Currently, the Zpool status looks pretty OK.. > > pool: backup > state: ONLINE > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > backup ONLINE 0 0 0 > ad8 ONLINE 0 0 0 > ad10 ONLINE 0 0 0 > > errors: No known data errors > > I don't know in the future there will be any issue because of this Geom > messages... is there any known problem like zfs/geom/gpt > incompatibility?.. is it the ZFS causing this error(!) messages?..any > thoughts?... It does not have anything to do with ZFS. GEOM is at a lower layer than ZFS is. The messages *may* be harmless but you should investigate further. Presumably you did the GPT configuration yourself - you should verify or redo it. Kris From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 22:06:34 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 324411065679 for ; Wed, 9 Jul 2008 22:06:34 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id D16EF8FC1B for ; Wed, 9 Jul 2008 22:06:33 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so819538yxb.13 for ; Wed, 09 Jul 2008 15:06:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=G3VOg3/aJH/6D6V9xDvSq/YuXqLig0tXgvwD19Q67b4=; b=XuDC3NIkvapp856KLHyM6wA7YcN9iqEMTcV8cw+joE/Gx+FCuuBFy7plxDo9RHCK3L uWHaGMC/lO/lgpDMga4biGe5dCm4FnDZwtPp3LqbeBrlkK42H7oZnQY/EIRbPBYZisDD WqGINPh25ktBQkyou7VG5uXMKv40B/dmab3S4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=AgynoLWguQDBL84h9b7CJgZ3VNB4A43PPgLPHI6tEcQKw+bsWQC3/rtOVoHF3pdPMc IuefFIVMJzur9GwW2YhjA7Yd8puGOXz0Y2CiZXsA57ne3rKjtQmBtJ2phzetS8UdAiKI siEDbrjgDI65sQLX6kCnPcnxLntoJBuWmY88s= Received: by 10.151.141.16 with SMTP id t16mr13197872ybn.114.1215641193157; Wed, 09 Jul 2008 15:06:33 -0700 (PDT) Received: by 10.151.154.17 with HTTP; Wed, 9 Jul 2008 15:06:33 -0700 (PDT) Message-ID: Date: Wed, 9 Jul 2008 15:06:33 -0700 From: "Freddie Cash" To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org In-Reply-To: <487380FA.6080004@wubethiopia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486F8C57.9050908@wubethiopia.com> <20080707213625.69bb0bf4@soralx> <487380FA.6080004@wubethiopia.com> Cc: Subject: Re: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jul 2008 22:06:34 -0000 On Tue, Jul 8, 2008 at 8:00 AM, Mike Makonnen wrote: > soralx@cydem.org wrote: >>> Hear, hear! To be honest, this is the only bit about the current >>> sysinstall that I really dislike: the fact that it can be used for >>> post-installation configuration and package installation. This causes >>> no end of trouble for newbies, who seem to view sysinstall as "The One >>> True System Admin Tool" and try to use it for configuring/installing >>> everything. Too many times, on various BSD forums, I've had to walk >>> people through cleaning up /etc/rc.conf and showing them how to >>> correctly install/configure things (using standard FreeBSD tools), >>> since they used sysinstall for everything. >> >> That may be true, but sysinstall did help me do basic, essentical >> configuration of my very first installed system, and a few installs after >> that (until I learned about /etc/rc.conf et al). And I never regarded it >> as The One True Sysadmin Tool, because I did not use Linux distros, thus >> never got used to their ways. It's just that the simple configuration menu >> really helped me to get a useful system running in a few minutes (though menu >> items certainly could make use of more verbose descriptions). And then I could >> play with the working system and learn ways to configure it. >> >> So, IMHO, a basic curses system configuration utility is still needed, and >> should be run after sysinstall or it should tell the user how to run it >> (maybe in motd, or sysinstall itself?). > > Yes, I agree that such a tool is useful, but it does not belong in the > installer. In fact, the BSD Installer framework can be used here also to > separate the implementation details from the user interface. Exactly. There's nothing wrong with having an TUI/GUI for configuring /etc/rc.conf, or ports, or whatever. And there are pointers to the handbook and man pages in the default motd, so one can learn to do it manually via a text editor. All I'm saying is that a generic system configuration tool should not be an integral part of the installer (and all mentions of sysinstall, IMO, should be removed from the default motd). They are separate tasks. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 01:14:40 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7E76106567A for ; Thu, 10 Jul 2008 01:14:40 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by mx1.freebsd.org (Postfix) with ESMTP id 7325D8FC17 for ; Thu, 10 Jul 2008 01:14:40 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from [10.11.16.99] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Wed, 09 Jul 2008 18:00:16 -0700 X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031 Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id 1C5322B2; Wed, 9 Jul 2008 18:00:16 -0700 (PDT) Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.11.18.52]) by mail-irva-10.broadcom.com (Postfix) with ESMTP id EE9902B0 for ; Wed, 9 Jul 2008 18:00:15 -0700 (PDT) Received: from mail-irva-13.broadcom.com (mail-irva-13.broadcom.com [10.11.16.103]) by mail-irva-8.broadcom.com (MOS 3.7.5a-GA) with ESMTP id GZO15477; Wed, 9 Jul 2008 18:00:07 -0700 (PDT) Received: from NT-IRVA-0751.brcm.ad.broadcom.com (nt-irva-0751 [10.8.194.65]) by mail-irva-13.broadcom.com (Postfix) with ESMTP id 6F16874D05 for ; Wed, 9 Jul 2008 18:00:02 -0700 (PDT) Received: from IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) by NT-IRVA-0751.brcm.ad.broadcom.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 9 Jul 2008 18:00:02 -0700 Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Wed, 9 Jul 2008 18:00:02 -0700 From: "David Christensen" To: "freebsd-current@freebsd.org" Date: Wed, 9 Jul 2008 18:00:45 -0700 Thread-Topic: Proper Printf Format for Printing Physical Addresses on 32 and 64 bit Systems Thread-Index: AcjiKF0L8PB31+ZRTCusYWB3OOIbhw== Message-ID: <5D267A3F22FD854F8F48B3D2B52381932677CC83F1@IRVEXCHCCR01.corp.ad.broadcom.com> Accept-Language: en-US Content-Language: en-US x-cr-hashedpuzzle: AXEG AXdu BbbM CJA4 DWHi D5+H GLVs GlN5 HaEa IM5Z I8Vm JlCK JzEZ KIAE KLPY KNu6; 1; ZgByAGUAZQBiAHMAZAAtAGMAdQByAHIAZQBuAHQAQABmAHIAZQBlAGIAcwBkAC4AbwByAGcA; Sosha1_v1; 7; {FE1D0C8B-EF06-4BA7-89E7-D4F7E26381AE}; ZABhAHYAaQBkAGMAaABAAGIAcgBvAGEAZABjAG8AbQAuAGMAbwBtAA==; Thu, 10 Jul 2008 01:00:45 GMT; UAByAG8AcABlAHIAIABQAHIAaQBuAHQAZgAgAEYAbwByAG0AYQB0ACAAZgBvAHIAIABQAHIAaQBuAHQAaQBuAGcAIABQAGgAeQBzAGkAYwBhAGwAIABBAGQAZAByAGUAcwBzAGUAcwAgAG8AbgAgADMAMgAgAGEAbgBkACAANgA0ACAAYgBpAHQAIABTAHkAcwB0AGUAbQBzAA== x-cr-puzzleid: {FE1D0C8B-EF06-4BA7-89E7-D4F7E26381AE} acceptlanguage: en-US MIME-Version: 1.0 X-OriginalArrivalTime: 10 Jul 2008 01:00:02.0450 (UTC) FILETIME=[48973F20:01C8E228] X-WSS-ID: 646B80AA3D083674637-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Proper Printf Format for Printing Physical Addresses on 32 and 64 bit Systems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 01:14:40 -0000 I have some debugging code in my network driver and I'd like to print out the physical address of a memory block. What's the right way to use a printf() that works on both 32 and 64 bit platforms? Dave From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 02:25:29 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C639A1065829; Thu, 10 Jul 2008 02:25:29 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id D58428FC18; Thu, 10 Jul 2008 02:25:28 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m6A2OvAx028341; Wed, 9 Jul 2008 22:25:22 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: gnn@FreeBSD.org Date: Wed, 9 Jul 2008 22:09:35 -0400 User-Agent: KMail/1.9.7 References: <200807041521.25711.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807092209.35780.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Wed, 09 Jul 2008 22:25:22 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/7680/Wed Jul 9 19:31:16 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-current@FreeBSD.org Subject: Re: Has anyone else seen any form of in memory or on disk corruption? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 02:25:30 -0000 On Saturday 05 July 2008 12:15:16 pm gnn@freebsd.org wrote: > At Fri, 4 Jul 2008 15:21:25 -0400, > John Baldwin wrote: > > > > If this is one of the ATA controllers where it tries to use 63k > > transfers (126 * DEV_BSIZE) instead of 64k, then change it to 32k > > (64 * DEV_BSIZE). W/o this fix I see massive data corruption > > (couldn't even build a kernel with the fix, had to reinstall the > > box) on HT1000 ATA chipsets. Crashdumps also don't seem to work > > reliably w/o changing that. > > > > Hmm, I don't see quite that much corruption. > > Reading over ata-chipset.c I see that there are 4 controllers which > may have this issue: > > Cyrix > Marvell > National > Serverworks > > This has been happening on AMCC cards and very occasionally Supermicro > motherboards. Is there an easy way to determine if either of those > are using these chips? PCI device IDs of the atapciX devices (and see if they match up with what devices use the chipset routines that set '126 * DEV_BSIZE' -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 03:50:35 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D69CE106564A for ; Thu, 10 Jul 2008 03:50:35 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 6C0C08FC1A for ; Thu, 10 Jul 2008 03:50:35 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m6A3oUNK053273; Wed, 9 Jul 2008 21:50:31 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <48758706.6040900@samsco.org> Date: Wed, 09 Jul 2008 21:50:30 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: David Christensen References: <5D267A3F22FD854F8F48B3D2B52381932677CC83F1@IRVEXCHCCR01.corp.ad.broadcom.com> In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381932677CC83F1@IRVEXCHCCR01.corp.ad.broadcom.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: "freebsd-current@freebsd.org" Subject: Re: Proper Printf Format for Printing Physical Addresses on 32 and 64 bit Systems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 03:50:35 -0000 David Christensen wrote: > I have some debugging code in my network driver and I'd like > to print out the physical address of a memory block. What's > the right way to use a printf() that works on both 32 and 64 > bit platforms? > > Dave > > Cast it to a uintmax_t and use %ju or %jx Scott From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 03:54:09 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 937B9106566C for ; Thu, 10 Jul 2008 03:54:09 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.freebsd.org (Postfix) with ESMTP id 1E4468FC0A for ; Thu, 10 Jul 2008 03:54:08 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail17.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m6A3s3x4002801 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Jul 2008 13:54:04 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m6A3s38N084305; Thu, 10 Jul 2008 13:54:03 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m6A3s3ox084304; Thu, 10 Jul 2008 13:54:03 +1000 (EST) (envelope-from peter) Date: Thu, 10 Jul 2008 13:54:03 +1000 From: Peter Jeremy To: David Christensen Message-ID: <20080710035403.GZ62764@server.vk2pj.dyndns.org> References: <5D267A3F22FD854F8F48B3D2B52381932677CC83F1@IRVEXCHCCR01.corp.ad.broadcom.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yr/DzoowOgTDcSCF" Content-Disposition: inline In-Reply-To: <5D267A3F22FD854F8F48B3D2B52381932677CC83F1@IRVEXCHCCR01.corp.ad.broadcom.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: "freebsd-current@freebsd.org" Subject: Re: Proper Printf Format for Printing Physical Addresses on 32 and 64 bit Systems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 03:54:09 -0000 --yr/DzoowOgTDcSCF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Jul-09 18:00:45 -0700, David Christensen wro= te: >I have some debugging code in my network driver and I'd like >to print out the physical address of a memory block. What's >the right way to use a printf() that works on both 32 and 64 >bit platforms? %p - see printf(3) or printf(9) --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --yr/DzoowOgTDcSCF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkh1h9sACgkQ/opHv/APuIfsqgCfZuR8fkl3i8jj6asBMlghk1OE TR4AnRlSz2E6QiE3qPGvPHQLg8UytjK6 =CSXz -----END PGP SIGNATURE----- --yr/DzoowOgTDcSCF-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 04:10:28 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D9B51065671 for ; Thu, 10 Jul 2008 04:10:28 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outS.internet-mail-service.net (outs.internet-mail-service.net [216.240.47.242]) by mx1.freebsd.org (Postfix) with ESMTP id F2EDB8FC12 for ; Thu, 10 Jul 2008 04:10:27 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 3BFAF2353; Wed, 9 Jul 2008 21:10:28 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 628E02D600F; Wed, 9 Jul 2008 21:10:27 -0700 (PDT) Message-ID: <48758BB2.8040706@elischer.org> Date: Wed, 09 Jul 2008 21:10:26 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Peter Jeremy References: <5D267A3F22FD854F8F48B3D2B52381932677CC83F1@IRVEXCHCCR01.corp.ad.broadcom.com> <20080710035403.GZ62764@server.vk2pj.dyndns.org> In-Reply-To: <20080710035403.GZ62764@server.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: David Christensen , "freebsd-current@freebsd.org" Subject: Re: Proper Printf Format for Printing Physical Addresses on 32 and 64 bit Systems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 04:10:28 -0000 Peter Jeremy wrote: > On 2008-Jul-09 18:00:45 -0700, David Christensen wrote: >> I have some debugging code in my network driver and I'd like >> to print out the physical address of a memory block. What's >> the right way to use a printf() that works on both 32 and 64 >> bit platforms? > > %p - see printf(3) or printf(9) unfortunately he specified PHYSICAL address. in a PAE machine you need a 64 bit number to hold it on a "32 bit" machine. and that isn't the only machine where physical and virtual addresses are not the same. (think original x86 :-) > From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 05:13:57 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD08A106564A; Thu, 10 Jul 2008 05:13:57 +0000 (UTC) (envelope-from mtm@wubethiopia.com) Received: from dire.wubethiopia.com (j071.v.rootbsd.net [208.79.82.223]) by mx1.freebsd.org (Postfix) with ESMTP id 96B2A8FC13; Thu, 10 Jul 2008 05:13:57 +0000 (UTC) (envelope-from mtm@wubethiopia.com) Received: from rogue.mike.lan (unknown [213.55.68.187]) by dire.wubethiopia.com (Postfix) with ESMTPSA id 14BB94FD9551; Thu, 10 Jul 2008 05:13:46 +0000 (UTC) Message-ID: <48759BD8.20404@wubethiopia.com> Date: Thu, 10 Jul 2008 08:19:20 +0300 From: Mike Makonnen User-Agent: Thunderbird 2.0.0.12 (X11/20080323) MIME-Version: 1.0 To: Marcel Moolenaar References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486F8C57.9050908@wubethiopia.com> <48737F79.6070401@wubethiopia.com> <20080708190407.GA68713@rink.nu> <47A12EFB-2433-4E60-BE15-48E1BDD22238@mac.com> In-Reply-To: <47A12EFB-2433-4E60-BE15-48E1BDD22238@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Rink Springer , freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 05:13:57 -0000 Marcel Moolenaar wrote: > > On Jul 8, 2008, at 12:04 PM, Rink Springer wrote: > >> On Tue, Jul 08, 2008 at 05:53:45PM +0300, Mike Makonnen wrote: >>> Freddie Cash wrote: >>>> >>>> The tricky part will be getting the disk slicing, slice partitioning, >>>> and filesystem formatting to work reliably, with all the power of >>>> FreeBSD's GEOM modules, and ZFS. >>>> >>> >>> Actually, this is probably the easiest part (at least for UFS). The >>> libdisk(3) library abstracts most of it out of the installer. >> >> ...except that libdisk(3) was supposed to be a temporary hack. I'd >> really >> suggest that something cleaner is to be written; libdisk(3) really is >> not the way to go. Have a look at the code and see for yourself. > > Yes, libdisk is bad. GEOM_PART has been designed > for use by installers. It can be interfaced > faily easily. See gpart(8) for example. Is there documentation for the geom_part API somewhere (I couldn't find any) or do I have to look at gpart(8) to figure out how to use it? Is it ok to just use gpart(8) instead of using the geom_part API? Cheers. -- Mike Makonnen | GPG-KEY: http://people.freebsd.org/~mtm/mtm.asc mtm @ FreeBSD.Org | AC7B 5672 2D11 F4D0 EBF8 5279 5359 2B82 7CD4 1F55 FreeBSD | http://www.freebsd.org From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 14:56:53 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A29F11065686 for ; Thu, 10 Jul 2008 14:56:53 +0000 (UTC) (envelope-from therior@ukr.net) Received: from ffe5.ukr.net (ffe5.ukr.net [195.214.192.21]) by mx1.freebsd.org (Postfix) with ESMTP id 66B6E8FC1A for ; Thu, 10 Jul 2008 14:56:53 +0000 (UTC) (envelope-from therior@ukr.net) Received: from mail by ffe5.ukr.net with local ID 1KGxKC-000IBY-2k for freebsd-current@freebsd.org; Thu, 10 Jul 2008 17:40:48 +0300 MIME-Version: 1.0 To: freebsd-current@freebsd.org From: "freebsd kernel panic" X-Life: is great, enjoy it! X-Mailer: freemail.ukr.net mPOP 3.4.1 X-Originating-Ip: 193.201.81.18, 193.201.81.18 via proxy [193.201.81.18] X-Browser: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.12) Gecko/20080510 Firefox/2.0.0.12 Message-Id: Date: Thu, 10 Jul 2008 17:40:48 +0300 X-UkrNet-Flag: 1 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 8bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: /girl/pussy && /girl/ass X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 14:56:53 -0000 when will these devices be? when will a woman be? From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 17:08:52 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 690031065674; Thu, 10 Jul 2008 17:08:52 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout011.mac.com (asmtp011.mac.com [17.148.16.86]) by mx1.freebsd.org (Postfix) with ESMTP id 59D908FC27; Thu, 10 Jul 2008 17:08:52 +0000 (UTC) (envelope-from xcllnt@mac.com) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from [192.168.1.102] (209-128-86-226.BAYAREA.NET [209.128.86.226]) by asmtp011.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3R006Q5YTZ3Z70@asmtp011.mac.com>; Wed, 09 Jul 2008 22:20:24 -0700 (PDT) Sender: xcllnt@mac.com Message-id: From: Marcel Moolenaar To: Mike Makonnen In-reply-to: <48759BD8.20404@wubethiopia.com> Date: Wed, 09 Jul 2008 22:20:23 -0700 References: <784966050807021123l267aa20en39eb513c12c90ad2@mail.gmail.com> <20080702235800.H47773@fledge.watson.org> <486C8700.5020100@lobraun.de> <20080703092511.T69986@fledge.watson.org> <486F8C57.9050908@wubethiopia.com> <48737F79.6070401@wubethiopia.com> <20080708190407.GA68713@rink.nu> <47A12EFB-2433-4E60-BE15-48E1BDD22238@mac.com> <48759BD8.20404@wubethiopia.com> X-Mailer: Apple Mail (2.926) Cc: freebsd-hackers@freebsd.org, Rink Springer , freebsd-current@freebsd.org Subject: Re: Sysinstall is still inadequate after all of these years X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 17:08:52 -0000 On Jul 9, 2008, at 10:19 PM, Mike Makonnen wrote: >> Yes, libdisk is bad. GEOM_PART has been designed >> for use by installers. It can be interfaced >> faily easily. See gpart(8) for example. > > Is there documentation for the geom_part API somewhere (I couldn't > find any) > or do I have to look at gpart(8) to figure out how to use it? I haven't written any documentation yet, so gpart(8) is probably the best place to start. > Is it ok to > just use gpart(8) instead of using the geom_part API? Using gpart(8) works just fine, except that you don't have access to all the information that's in the XML. Things like geometry come to mind. But of course, you can always read the XML, use gpart(8) to make a change and read the XML again. Having that, it's only a tiny step to use the gctl interface directly. FYI, -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 17:16:22 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAE14106566C for ; Thu, 10 Jul 2008 17:16:22 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id 49A798FC12 for ; Thu, 10 Jul 2008 17:16:22 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1929445fgb.35 for ; Thu, 10 Jul 2008 10:16:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=jVp5LGK06zhW2xs0UpuIildZtZ03Zwt/h3rGt8201ao=; b=jIXxUPWg53rpYSNqI/fvrMOBnHzkWfFFgVJ/HSJBeG+Ain2Y7FfwMRPqed6kRZ7ymK r3cfWSIwH8M3KpYLbzumCeTyuik+FBQEPsnel8Jt/4qsQ/QjeWkeDkDD1T+cCcpI1NGV cL8X/eRlHxrYhlgpEW5tFfplYx7HUDyot8KIQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=mxlHHYVoJ05mdLQAeQw5juvAfpREowq9+uF6TN18yL+jAKbi/mwhPCrcybicnOsTku nzMfPVsWctaF84e5VVLTMKFo9qnR8P+PVo05UKOt/cHcLSPnWcpIRoStg7XRPo8hFEX7 8RdDXfFkEi9L8NILuU3acf8cXC3zHXV2713bI= Received: by 10.86.36.11 with SMTP id j11mr8913263fgj.7.1215708478607; Thu, 10 Jul 2008 09:47:58 -0700 (PDT) Received: by 10.86.49.9 with HTTP; Thu, 10 Jul 2008 09:47:58 -0700 (PDT) Message-ID: Date: Thu, 10 Jul 2008 09:47:58 -0700 From: "Maksim Yevmenkin" To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: network protocol stacks in userspace X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 17:16:22 -0000 hello, i'd like to run an idea past the network gurus here. lets say i'd like to implement a network protocol stack (or part of it) in user space. however, i also want to have a socket interface so all the client applications can simply use socket(), bind(), connect() etc. calls just as they would with in-kernel stack. so, one crazy idea is to implement "loop" socket layer that simply loops all the requests back to userspace (similar to tun/tap/fuse/etc.) so there would be another domain, PF_LOOP (or PF_NULL) and possibly 3 or 4 pre-canned protocol families (i.e. one for each STREAM, DGRAM, RAW and SEQPACKET protocol types) with somewhat generic implementation. each pru_xxx request loops back to user space in a form of an event/message. such events could be completely synchronous (blocking connect(), accept(), read() etc.) or asynchronous (non-blocking connect(), etc.). each "loop" socket will have either no or very little pcb associated with it - it will just the socket's state. from user space each "loop" socket will be accessible using its file descriptor and regular socket api and via /dev/loopsock device node (or possibly create device node for each "loop" socket). finally, client applications could simply #define PF_NEW_DOMAIN PF_LOOP #define NEW_DOMAIN_PROTO PF_PROTO_STREAM s = socket(PF_NEW_DOMAIN, SOCK_STREAM, NEW_DOMAIN_PROTO); bind(s, (struct sockaddr *) &sa, sizeof(sa)); ... so what do you guys think? am i way off base here? is there a better way to do it? oh, and one more thing, netgraph is out (sorry Julian :) i personally think netgraph is very cool, but i need something different here. thanks, max From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 19:37:29 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93138106568D for ; Thu, 10 Jul 2008 19:37:29 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk1.360sip.com [72.236.70.240]) by mx1.freebsd.org (Postfix) with ESMTP id 5A2F38FC14 for ; Thu, 10 Jul 2008 19:37:29 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.0.40] ([204.244.149.125]) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.8) with ESMTP id m6AJI2mZ057545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Jul 2008 12:18:04 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Message-ID: <48766067.6090008@FreeBSD.org> Date: Thu, 10 Jul 2008 12:17:59 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Maksim Yevmenkin References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: network protocol stacks in userspace X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 19:37:29 -0000 Maksim Yevmenkin wrote: > somewhat generic implementation. each pru_xxx request loops back to > user space in a form of an event/message. such events could be > completely synchronous (blocking connect(), accept(), read() etc.) or > asynchronous (non-blocking connect(), etc.). each "loop" socket will > have either no or very little pcb associated with it - it will just > the socket's state. from user space each "loop" socket will be > accessible using its file descriptor and regular socket api and via > /dev/loopsock device node (or possibly create device node for each > "loop" socket). Not necessary the best way to do it in this case, but one approach would be to have some kind of "syscall diversion" layer, which would allow some/all syscalls issued by one process to be diverted for actual execution to another userland process. I am sure such layer could have other interesting applications. -Maxim From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 19:43:52 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 253F31065670 for ; Thu, 10 Jul 2008 19:43:52 +0000 (UTC) (envelope-from matteo@freebsd.org) Received: from vsmtp1.tin.it (vsmtp1.tin.it [212.216.176.141]) by mx1.freebsd.org (Postfix) with ESMTP id D966D8FC1D for ; Thu, 10 Jul 2008 19:43:51 +0000 (UTC) (envelope-from matteo@freebsd.org) Received: from krapfengeist.krapfengeist (87.4.189.241) by vsmtp1.tin.it (8.0.016.5) id 48494F1501CFD6E8 for freebsd-current@freebsd.org; Thu, 10 Jul 2008 21:32:07 +0200 Received: from krapfengeist.krapfengeist (smmsp@localhost [127.0.0.1]) by krapfengeist.krapfengeist (8.14.2/8.14.2) with ESMTP id m6AJW4H1001412 for ; Thu, 10 Jul 2008 21:32:04 +0200 (CEST) (envelope-from matteo@freebsd.org) Received: (from rionda@localhost) by krapfengeist.krapfengeist (8.14.2/8.14.2/Submit) id m6AIGmld004282 for freebsd-current@freebsd.org; Thu, 10 Jul 2008 20:16:48 +0200 (CEST) (envelope-from matteo@freebsd.org) X-Authentication-Warning: krapfengeist.krapfengeist: rionda set sender to matteo@freebsd.org using -f Date: Thu, 10 Jul 2008 20:16:48 +0200 From: Matteo Riondato To: freebsd-current@freebsd.org Message-ID: <20080710181647.GB3148@krapfengeist> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="w7PDEPdKQumQfZlR" Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Subject: 802.11 vap support and ndis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 19:43:52 -0000 --w7PDEPdKQumQfZlR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi folks, I just upgraded one of my amd64 boxes from HEAD as of around March to HEAD as of this morning CEST and my ndis(4) card no longer works although I modified rc.conf as suggested (added wlans_ndis0=3D"wlan0" and changed ifconfig_ndis0 to ifconfig_wlan0). The card doesn't seem to associate, or, better said, the wlan0 interface doesn't seem to associate, because the ndis0 interface says it is associated: (output copied by hand) #ifconfig ndis0 ndis0: flags=3D8843 metric 0 mtu 22= 90 ether 00:0c:41:xx:xx:xx media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated #ifconfig wlan0 wlan0: flags=3D8c43 metric = 0 mtu 1500 ether 00:0c:41:xx:xx:xx inet6 fe80::20:xxxx:xxxx:xxxx%wlan0 prefixlen 64 scopeid 0x8 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid ambassador channel 1 (2412 Mhz 11g) country US authmode open privacy ON deftxkey 1 wepkey 1:104-bit txpower 0 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 protmode CTS bintval 0 My wireless lan is on channel 6, so I though there could be problems with scanning, but.. #ifconfig wlan0 channel 6 doesn't print any error message but the output of ifconfig wlan0 is the same, with channel 1. Any hints? Thanks in advance and best regards --=20 Matteo Riondato FreeBSD Committer (http://www.FreeBSD.org) FreeSBIE Developer (http://www.FreeSBIE.org) GUFI Staff Member (http://www.GUFI.org) ----- End forwarded message ----- --=20 Matteo Riondato FreeBSD Committer (http://www.FreeBSD.org) FreeSBIE Developer (http://www.FreeSBIE.org) GUFI Staff Member (http://www.GUFI.org) --w7PDEPdKQumQfZlR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkh2Ug8ACgkQ2Mp4pR7Fa+wbTwCfYlCpP9w0TqWjl0aFzWRY0r8h SPMAoL3+d1mjsR+tBSv2zMsDeBJmIE1D =8VS2 -----END PGP SIGNATURE----- --w7PDEPdKQumQfZlR-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 19:43:52 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28A311065673 for ; Thu, 10 Jul 2008 19:43:52 +0000 (UTC) (envelope-from matteo@freebsd.org) Received: from vsmtp1.tin.it (vsmtp1.tin.it [212.216.176.141]) by mx1.freebsd.org (Postfix) with ESMTP id DD24D8FC1F for ; Thu, 10 Jul 2008 19:43:51 +0000 (UTC) (envelope-from matteo@freebsd.org) Received: from krapfengeist.krapfengeist (87.4.189.241) by vsmtp1.tin.it (8.0.016.5) id 48494F1501CFD705 for freebsd-current@freebsd.org; Thu, 10 Jul 2008 21:32:09 +0200 Received: from krapfengeist.krapfengeist (smmsp@localhost [127.0.0.1]) by krapfengeist.krapfengeist (8.14.2/8.14.2) with ESMTP id m6AJW4H3001412 for ; Thu, 10 Jul 2008 21:32:06 +0200 (CEST) (envelope-from matteo@freebsd.org) Received: (from rionda@localhost) by krapfengeist.krapfengeist (8.14.2/8.14.2/Submit) id m6AI4l1l003840 for freebsd-current@freebsd.org; Thu, 10 Jul 2008 20:04:47 +0200 (CEST) (envelope-from matteo@freebsd.org) X-Authentication-Warning: krapfengeist.krapfengeist: rionda set sender to matteo@freebsd.org using -f Date: Thu, 10 Jul 2008 20:04:47 +0200 From: Matteo Riondato To: freebsd-current@freebsd.org Message-ID: <20080710180423.GA3148@krapfengeist> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Y7xTucakfITjPcLV" Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Subject: 802.11 vap support and ndis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 19:43:52 -0000 --Y7xTucakfITjPcLV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi folks, I just upgraded one of my amd64 boxes from HEAD as of around March to HEAD as of this morning CEST and my ndis(4) card no longer works although I modified rc.conf as suggested (added wlans_ndis0=3D"wlan0" and changed ifconfig_ndis0 to ifconfig_wlan0). The card doesn't seem to associate, or, better said, the wlan0 interface doesn't seem to associate, because the ndis0 interface says it is associated: (output copied by hand) #ifconfig ndis0 ndis0: flags=3D8843 metric 0 mtu 22= 90 ether 00:0c:41:xx:xx:xx media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated #ifconfig wlan0 wlan0: flags=3D8c43 metric = 0 mtu 1500 ether 00:0c:41:xx:xx:xx inet6 fe80::20:xxxx:xxxx:xxxx%wlan0 prefixlen 64 scopeid 0x8 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid ambassador channel 1 (2412 Mhz 11g) country US authmode open privacy ON deftxkey 1 wepkey 1:104-bit txpower 0 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 protmode CTS bintval 0 My wireless lan is on channel 6, so I though there could be problems with scanning, but.. #ifconfig wlan0 channel 6 doesn't print any error message but the output of ifconfig wlan0 is the same, with channel 1. Any hints? Thanks in advance and best regards --=20 Matteo Riondato FreeBSD Committer (http://www.FreeBSD.org) FreeSBIE Developer (http://www.FreeSBIE.org) GUFI Staff Member (http://www.GUFI.org) --Y7xTucakfITjPcLV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkh2TzsACgkQ2Mp4pR7Fa+wb4gCgnHgyAMAD/cl92vmEo74JEk1u OOIAn24oKhPmwKUAZNfhV5hUvXZX+UPD =t93j -----END PGP SIGNATURE----- --Y7xTucakfITjPcLV-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 20:47:52 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDB34106567F for ; Thu, 10 Jul 2008 20:47:52 +0000 (UTC) (envelope-from gomez@telehouse.com) Received: from smtp.telehouse.com (smtp.telehouse.com [209.137.140.4]) by mx1.freebsd.org (Postfix) with ESMTP id ACD9E8FC1E for ; Thu, 10 Jul 2008 20:47:52 +0000 (UTC) (envelope-from gomez@telehouse.com) X-ASG-Debug-ID: 1215722094-28b6000a0000-XDYc8F X-Barracuda-URL: http://smtp.telehouse.com:8000/cgi-bin/mark.cgi Received: from LVA0823 (localhost [127.0.0.1]) by smtp.telehouse.com (Spam Firewall) with ESMTP id 628CC58D31 for ; Thu, 10 Jul 2008 16:34:54 -0400 (EDT) Received: from LVA0823 (mercado.25b.telehouse.com [172.18.6.140]) by smtp.telehouse.com with ESMTP id qoTVZN637oznxZEN (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 10 Jul 2008 16:34:54 -0400 (EDT) From: "Julio Gomez" To: X-ASG-Orig-Subj: Dell's PERC6i Date: Thu, 10 Jul 2008 16:34:45 -0400 Organization: TELEHOUSE America Message-ID: <00db01c8e2cc$640edac0$2c2c9040$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcjizGOxBKEt4/rxRAikU8XGOHMRfQ== Content-Language: en-us X-Barracuda-Connect: mercado.25b.telehouse.com[172.18.6.140] X-Barracuda-Start-Time: 1215722094 X-Barracuda-Encrypted: AES128-SHA X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at telehouse.com Subject: Dell's PERC6i X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 20:47:53 -0000 I am planning to purchase Dell PowerEdge 2950 III with RAID 5 configuration. I checked Hardware Note on FreeBSD site but Dell's PERC6i is not on the list. Is it supported by FreeBSD 7.0 and/or FreeBSD 6.3 Thank you very much for your help in advance. === Hardware Configuration === Backplane: 1x6 Backplane for 3.5-inch Hard Drives [Included in Price] SAS RAID Contoller: PERC6i SAS RAID Controller, 2x4 Connectors, Int, PCIe, 256MB Cache, x6 Back Hard Drive Configuration: Integrated SAS/SATA RAID 5, PERC 6/i Integrated Hard Drive: Five (5) 146GB 15K RPM Serial-Attach SCSI 3Gbps 3.5-in HotPlug Hard Drive Regards, Julio Gomez From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 21:16:57 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACB17106567A for ; Thu, 10 Jul 2008 21:16:57 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (unknown [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 56C418FC16 for ; Thu, 10 Jul 2008 21:16:57 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (unknown [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 80C4528448 for ; Fri, 11 Jul 2008 05:16:56 +0800 (CST) Received: from localhost (unknown [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id 244B2EB2649; Fri, 11 Jul 2008 05:16:56 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id OojDrsyR-JQd; Fri, 11 Jul 2008 05:16:44 +0800 (CST) Received: from charlie.delphij.net (71.5.7.139.ptr.us.xo.net [71.5.7.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 4B9FBEB09A0; Fri, 11 Jul 2008 05:16:43 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=dIYOKvU8xjCTOMkkiyuP7fWmzgzxYq55Gg/HYuXaJWBtkwetExkycg0ugy0Vw4+WM JkMrc18SeJyNrOQjm7iwg== Message-ID: <48767C38.8010206@delphij.net> Date: Thu, 10 Jul 2008 14:16:40 -0700 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: Julio Gomez References: <00db01c8e2cc$640edac0$2c2c9040$@com> In-Reply-To: <00db01c8e2cc$640edac0$2c2c9040$@com> X-Enigmail-Version: 0.95.6 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Dell's PERC6i X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 21:16:57 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Julio Gomez wrote: | I am planning to purchase Dell PowerEdge 2950 III with RAID 5 configuration. | | I checked Hardware Note on FreeBSD site but Dell's PERC6i is not on the | list. Is it supported by FreeBSD 7.0 and/or FreeBSD 6.3 | | Thank you very much for your help in advance. | | === Hardware Configuration === | | Backplane: | 1x6 Backplane for 3.5-inch Hard Drives [Included in Price] | | SAS RAID Contoller: | PERC6i SAS RAID Controller, 2x4 Connectors, Int, PCIe, 256MB Cache, x6 Back | | Hard Drive Configuration: | Integrated SAS/SATA RAID 5, PERC 6/i Integrated | | Hard Drive: | Five (5) 146GB 15K RPM Serial-Attach SCSI 3Gbps 3.5-in HotPlug Hard Drive I *think* that PERC 6/i would appear as "LSI MegaSAS 1078" rather than "Dell PERC 6/i" because of the following catch-all ID quirk: {0x1000, 0x0060, 0xffff, 0xffff, MFI_FLAGS_1078, "LSI MegaSAS 1078"}, Later FreeBSD versions would identify it as "PERC 6": {0x1000, 0x0060, 0x1028, 0xffff, MFI_FLAGS_1078, "Dell PERC 6"}, Therefore this should work just fine (out-of-the-box) on 7.0-R except it gave different names... Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkh2fDgACgkQi+vbBBjt66CA5gCggLzzwwx9oaHcDni1yo5xSxHa qVgAni3XihyBRAZlXsSzrWPGwinBeVKX =bTIP -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 23:21:50 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CC8A1065671 for ; Thu, 10 Jul 2008 23:21:50 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from mailhub.rulez.sk (mailhub.rulez.sk [IPv6:2001:15c0:6672::2]) by mx1.freebsd.org (Postfix) with ESMTP id D63928FC15 for ; Thu, 10 Jul 2008 23:21:49 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by mailhub.rulez.sk (Postfix) with ESMTP id BF9F95C052; Fri, 11 Jul 2008 01:21:47 +0200 (CEST) X-Virus-Scanned: amavisd-new at rulez.sk Received: from mailhub.rulez.sk ([78.47.53.106]) by localhost (genesis.rulez.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9o0AhkFmxlpP; Fri, 11 Jul 2008 01:21:47 +0200 (CEST) Received: from DANGER-PC (danger.mcrn.sk [84.16.37.254]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: danger@rulez.sk) by mailhub.rulez.sk (Postfix) with ESMTPSA id 041695C04D; Fri, 11 Jul 2008 01:21:46 +0200 (CEST) Date: Fri, 11 Jul 2008 01:21:38 +0200 From: Daniel Gerzo X-Mailer: The Bat! (v3.99.3) Professional Organization: The FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1574497.20080711012138@rulez.sk> To: Xin LI In-Reply-To: <48767C38.8010206@delphij.net> References: <00db01c8e2cc$640edac0$2c2c9040$@com> <48767C38.8010206@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: d@delphij.net, freebsd-current@freebsd.org, Julio Gomez Subject: Re[2]: Dell's PERC6i X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Gerzo List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 23:21:50 -0000 Hello Xin, Thursday, July 10, 2008, 11:16:40 PM, you wrote: > I *think* that PERC 6/i would appear as "LSI MegaSAS 1078" rather than > "Dell PERC 6/i" because of the following catch-all ID quirk: > {0x1000, 0x0060, 0xffff, 0xffff, MFI_FLAGS_1078, "LSI MegaSAS 1078"}, > Later FreeBSD versions would identify it as "PERC 6": > {0x1000, 0x0060, 0x1028, 0xffff, MFI_FLAGS_1078, "Dell PERC 6"}, > Therefore this should work just fine (out-of-the-box) on 7.0-R except it > gave different names... Correct, I suppose these will be handled by mfi(4) device driver. I have some Dell SC1430s that have Dell PERC 5i controllers. One disadvantage of these is that there's no native monitoring tool for mfi(4) based devices. There's only a linux utility which I haven't tried so far. However, it seems like porting might be easy and bz@ has idicated some interest in this work. He unfortunately seems to be busy these days ;-( -- Best regards, Daniel mailto:danger@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 23:38:55 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 063BE106567D for ; Thu, 10 Jul 2008 23:38:55 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.freebsd.org (Postfix) with ESMTP id 8B1EF8FC0C for ; Thu, 10 Jul 2008 23:38:54 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: by ug-out-1314.google.com with SMTP id q2so3534uge.37 for ; Thu, 10 Jul 2008 16:38:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:content-transfer-encoding :content-disposition:x-google-sender-auth; bh=OlqEnCITiQjNtt1nTy4QF5gTTCFuud76Qt8JkpFVMp0=; b=wWzsXLeHzOyqgeBs3pYCSr38VBI5P1tTm49hKprvhPz0fxNwGgsd6YSjFWq9qasKtn wzzKC8f/vGcJBW057X8ZLagO+pCFhGQFAd82poGfLXig09sdoepmwEiZSc+grpB39FHU N/VVx49uYL4xsYEG2VoW1l77GS8fji7Pw6vGs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition:x-google-sender-auth; b=p1FRdQULCY6QoElyE0ceSulZ+AEAYlBea2rx3YQ3SHN/WuLu7L07+ZCH4jA0sSrX8r S5W47cl1iNEQYKvYyB1HNUOr/XYXu1HKePKdIndl+xk2tQjsf4sHkUq9acRGz7Qo2gHd ZzeZEvW40YLCIf+6ghj8j8RwWbqLCdYnedXS4= Received: by 10.66.232.9 with SMTP id e9mr80216ugh.17.1215733133102; Thu, 10 Jul 2008 16:38:53 -0700 (PDT) Received: by 10.66.248.12 with HTTP; Thu, 10 Jul 2008 16:38:52 -0700 (PDT) Message-ID: Date: Fri, 11 Jul 2008 00:38:52 +0100 From: "Igor Mozolevsky" Sender: mozolevsky@gmail.com To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: 2bf8ba4969835d53 Subject: OT: anoncvs1.freebsd.org asking for password? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 23:38:55 -0000 Anyone else experiencing this? > cvs -R -z9 -d anoncvs@anoncvs1.freebsd.org:/home/ncvs co -r RELENG_7 src Password: From owner-freebsd-current@FreeBSD.ORG Thu Jul 10 23:56:52 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF0491065671; Thu, 10 Jul 2008 23:56:52 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 8B1968FC27; Thu, 10 Jul 2008 23:56:52 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m6ANuniQ066013; Thu, 10 Jul 2008 19:56:49 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.2/8.14.2) with ESMTP id m6ANunSe065101; Thu, 10 Jul 2008 19:56:49 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 5963073039; Thu, 10 Jul 2008 19:56:49 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080710235649.5963073039@freebsd-current.sentex.ca> Date: Thu, 10 Jul 2008 19:56:49 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93/7040/Mon May 5 21:52:15 2008 clamav-milter version 0.93 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2008 23:56:53 -0000 TB --- 2008-07-10 22:10:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-07-10 22:10:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-07-10 22:10:00 - cleaning the object tree TB --- 2008-07-10 22:10:48 - cvsupping the source tree TB --- 2008-07-10 22:10:48 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-07-10 22:10:54 - building world (CFLAGS=-O -pipe) TB --- 2008-07-10 22:10:54 - cd /src TB --- 2008-07-10 22:10:54 - /usr/bin/make -B buildworld >>> World build started on Thu Jul 10 22:10:57 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Thu Jul 10 23:47:11 UTC 2008 TB --- 2008-07-10 23:47:11 - generating LINT kernel config TB --- 2008-07-10 23:47:11 - cd /src/sys/amd64/conf TB --- 2008-07-10 23:47:11 - /usr/bin/make -B LINT TB --- 2008-07-10 23:47:11 - building LINT kernel (COPTFLAGS=) TB --- 2008-07-10 23:47:11 - cd /src TB --- 2008-07-10 23:47:11 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Jul 10 23:47:11 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/wpi/if_wpi.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/isa/atrtc.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/isa/syscons_isa.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/isa/vga_isa.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/kern/link_elf_obj.c /src/sys/kern/link_elf_obj.c:88: error: redefinition of 'struct elf_file' /src/sys/kern/link_elf_obj.c:119: error: redefinition of typedef 'elf_file_t' /src/sys/sys/link_elf.h:133: error: previous declaration of 'elf_file_t' was here *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-07-10 23:56:49 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-07-10 23:56:49 - ERROR: failed to build lint kernel TB --- 2008-07-10 23:56:49 - tinderbox aborted TB --- 4785.86 user 608.10 system 6408.91 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Fri Jul 11 02:24:29 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C05031065673 for ; Fri, 11 Jul 2008 02:24:29 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.191]) by mx1.freebsd.org (Postfix) with ESMTP id 473038FC14 for ; Fri, 11 Jul 2008 02:24:28 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: by ti-out-0910.google.com with SMTP id d27so1505196tid.3 for ; Thu, 10 Jul 2008 19:24:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:to:cc:subject :message-id:mail-followup-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent:organization :x-operation-sytem:from; bh=g2B1TKDBoUhFP5xLxlt0lJ9xSQ/uxE3a5mx0pvKOtVE=; b=YWozhETjG5OrC9YlL/zXhMFyc86Mti/dvDRQYwDzARGbKNE0th+lBLYAj2/uCWiclH tJCIm6pI0J2lh00X3lnxLEy7jHUPhyTUtejrI9Zx3XUwQhP6KTBeMBylSxPQqsIuRisd SpoGCb9W/mUL/Zu0RszicsR0stnjGkr3Qi2sI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent:organization:x-operation-sytem:from; b=wIgxGyRuWS7P78cMS37xK8PNgNsnsajJdWA+0NFd/qLSjZpSzu2WvnhQsUo/MUG0b8 nV/MjC7e1AczlV+UlIhPV7XLvC8wdJEq3k6LyyzduLk0NZyjN0s188kGgjGajb5lvVuM O/gq4XCbP6sPppI3IWnbr3Bdiy+RLzRVYNvQM= Received: by 10.110.37.17 with SMTP id k17mr5517271tik.13.1215743067715; Thu, 10 Jul 2008 19:24:27 -0700 (PDT) Received: from freebsd.weongyo.org ( [211.53.35.67]) by mx.google.com with ESMTPS id u8sm70109tia.6.2008.07.10.19.24.25 (version=SSLv3 cipher=RC4-MD5); Thu, 10 Jul 2008 19:24:26 -0700 (PDT) Received: by freebsd.weongyo.org (sSMTP sendmail emulation); Fri, 11 Jul 2008 11:23:58 +0900 Date: Fri, 11 Jul 2008 11:23:58 +0900 To: Matteo Riondato Message-ID: <20080711022358.GG26288@freebsd.weongyo.org> Mail-Followup-To: Matteo Riondato , freebsd-current@freebsd.org References: <20080710180423.GA3148@krapfengeist> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080710180423.GA3148@krapfengeist> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD From: Weongyo Jeong Cc: freebsd-current@freebsd.org Subject: Re: 802.11 vap support and ndis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2008 02:24:29 -0000 On Thu, Jul 10, 2008 at 08:04:47PM +0200, Matteo Riondato wrote: > Hi folks, > I just upgraded one of my amd64 boxes from HEAD as of around March to > HEAD as of this morning CEST and my ndis(4) card no longer works > although I modified rc.conf as suggested (added wlans_ndis0="wlan0" > and changed ifconfig_ndis0 to ifconfig_wlan0). > > The card doesn't seem to associate, or, better said, the wlan0 > interface doesn't seem to associate, because the ndis0 interface says > it is associated: (output copied by hand) > #ifconfig ndis0 > ndis0: flags=8843 metric 0 mtu 2290 > ether 00:0c:41:xx:xx:xx > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: associated > #ifconfig wlan0 > wlan0: flags=8c43 metric 0 mtu 1500 > ether 00:0c:41:xx:xx:xx > inet6 fe80::20:xxxx:xxxx:xxxx%wlan0 prefixlen 64 scopeid 0x8 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid ambassador channel 1 (2412 Mhz 11g) > country US authmode open privacy ON deftxkey 1 wepkey 1:104-bit > txpower 0 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 protmode CTS > bintval 0 > > My wireless lan is on channel 6, so I though there could be problems > with scanning, but.. > #ifconfig wlan0 channel 6 > doesn't print any error message but the output of ifconfig wlan0 is the > same, with channel 1. > > Any hints? Can you try to turn on debug level of if_ndis(4) then re-associate to your AP? Please show me the output. # kldload if_ndis # sysctl debug.ndis=1 regards, Weongyo Jeong From owner-freebsd-current@FreeBSD.ORG Fri Jul 11 02:48:53 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 057DF106567B for ; Fri, 11 Jul 2008 02:48:53 +0000 (UTC) (envelope-from vlad.k.sm@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id CD6D88FC13 for ; Fri, 11 Jul 2008 02:48:52 +0000 (UTC) (envelope-from vlad.k.sm@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so4493479rvf.43 for ; Thu, 10 Jul 2008 19:48:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=mC9ehpcZIy/LGG13p47sHVmbpHNRk4DTuObJNjOMv1I=; b=GKN3pR3/BYNiCuFWNPhoAvSWg6ZPHEbbOMedqcgBQoIj/7IcrQHNdoM+ULv8X2qdDE mvFi52Q3QtQflZwXRtPTb63bVVQ4HmR+65MMGEeoX8ZP72soZVyklIDUh8xw1p7YeUqX 5nX4Nly0RysZ99FAIqLjoUsD5mQBoAFbwZ7KQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=WjCnNPVZj0l4p9/70dtPUPK2Qyt26TPaSpqOlsKbbGbMI4jullI6yWodXU5hX00vRB yNtJoo5l232vC9dfOCeQu50E2xe+xW3U+5mlavcC6w6jpFlbZNsmd+XOvczlFzGLWSc3 EaxUi6xtE36eRd7m9A6jV61i/DWvOGdkjH8lI= Received: by 10.140.171.18 with SMTP id t18mr1724530rve.22.1215742881319; Thu, 10 Jul 2008 19:21:21 -0700 (PDT) Received: from ?71.196.209.227? ( [71.196.209.227]) by mx.google.com with ESMTPS id l31sm59363rvb.6.2008.07.10.19.21.19 (version=SSLv3 cipher=RC4-MD5); Thu, 10 Jul 2008 19:21:19 -0700 (PDT) Message-ID: <48762A10.60406@gmail.com> Date: Thu, 10 Jul 2008 20:26:08 +0500 From: Vlad K Sm User-Agent: Thunderbird 2.0.0.14 (X11/20080708) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20080710120018.0A82810656A0@hub.freebsd.org> In-Reply-To: <20080710120018.0A82810656A0@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: /etc/rc.d/syscons question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2008 02:48:53 -0000 Hi, I've found that if in /etc/rc.conf specify: keybell="off" then it affects only tty0 (default console). I checked implementation of /etc/rc.d/syscons snd yes, such flags are set for /dev/ttyv0 only and if you need some flags for all screens, need to use "allscreens_kbdflags". syscons: # keybell # case ${keybell} in [Nn][Oo] | '') ;; *) echo -n ' keybell'; kbdcontrol < ${kbddev} -b ${keybell} ;; esac # set this keyboard mode for all virtual terminals # if [ -n "${allscreens_kbdflags}" ]; then sc_init echo -n ' allscreens_kbd' for ttyv in /dev/ttyv*; do kbdcontrol ${allscreens_kbdflags} < ${ttyv} > ${ttyv} 2>&1 done My question: is it by design that flags in rc.local are set for ttyv0 only or this is an issue which is waiting for improvement? Thanks, Vladimir Kuzmin From owner-freebsd-current@FreeBSD.ORG Fri Jul 11 03:37:28 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD7F11065679 for ; Fri, 11 Jul 2008 03:37:28 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 874858FC1A for ; Fri, 11 Jul 2008 03:37:28 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.2/8.14.2) with ESMTP id m6B3bSIx059766; Thu, 10 Jul 2008 20:37:28 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.2/8.14.2/Submit) id m6B3bRsW059765; Thu, 10 Jul 2008 20:37:27 -0700 (PDT) (envelope-from sgk) Date: Thu, 10 Jul 2008 20:37:27 -0700 From: Steve Kargl To: Igor Mozolevsky Message-ID: <20080711033727.GA59707@troutmask.apl.washington.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: OT: anoncvs1.freebsd.org asking for password? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2008 03:37:28 -0000 On Fri, Jul 11, 2008 at 12:38:52AM +0100, Igor Mozolevsky wrote: > Anyone else experiencing this? > > > cvs -R -z9 -d anoncvs@anoncvs1.freebsd.org:/home/ncvs co -r RELENG_7 src > Password: Yes. I switched to the other anoncvs server listed for the USA region. -- Steve From owner-freebsd-current@FreeBSD.ORG Fri Jul 11 10:43:28 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8E2C1065671; Fri, 11 Jul 2008 10:43:28 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.freebsd.org (Postfix) with ESMTP id 101498FC13; Fri, 11 Jul 2008 10:43:27 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.14.2/8.14.2) with ESMTP id m6BAFCio039209; Fri, 11 Jul 2008 14:15:12 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Fri, 11 Jul 2008 14:15:12 +0400 (MSD) From: Maxim Konovalov To: Ken Smith In-Reply-To: <1215119650.75067.10.camel@neo.cse.buffalo.edu> Message-ID: <20080711141217.B19592@mp2.macomnet.net> References: <1215119650.75067.10.camel@neo.cse.buffalo.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-current@freebsd.org, freebsd-stable Subject: Re: cvsup server reachable via IPv6... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2008 10:43:28 -0000 On Thu, 3 Jul 2008, 17:14-0400, Ken Smith wrote: > > If any of you have been wishing there was an IPv6-capable cvsup server > you could use (with csup as the client obviously since cvsup doesn't do > IPv6...) give cvsup18.freebsd.org a try. With the help of a few other > folks I got nudged into giving inetd/netcat a try as a means to feed > IPv6 connections to the cvsupd server process. > > If you try it and have problems let me know. cvsup18 is my "little > server" (handles between 200 and 300 connects a day) but if this seems > to work OK I can give it a try on my "big server" (handles between 3000 > and 4000 connects a day...). > FWIW, we already running ipv6 cvsup server at cvsup4.ru.freebsd.org. -- Maxim Konovalov From owner-freebsd-current@FreeBSD.ORG Fri Jul 11 11:04:33 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0844A106564A for ; Fri, 11 Jul 2008 11:04:33 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id 98D428FC1B for ; Fri, 11 Jul 2008 11:04:32 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: by ug-out-1314.google.com with SMTP id q2so61788uge.37 for ; Fri, 11 Jul 2008 04:04:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=l36Kr7pASvyCj9TrfuxX1V3/3mZfKSFS04vRCa2UMQk=; b=Syw4i/TMTKqqun8Bgf9nnjYNgo0ew+SnXoPcs1Llah1so9E34c5iYYQ/jhaOAKIuYj dcXjio9iwwvrQgS2KX/N2ddkzAp4FfnCJGy6Qk1cIas1ZLjwMZuZskgcBCdMzgVUTvM3 8Li8Op2MDX77RaOKI8h71LB4e1r/TTvRwRyEk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=Npa9XhR/s/VGaxQBnCRPArmUPGialGvad3ePk0mCpYgEWUiZo13oByJSV9FW9Q0NVM xHDabt7ZCahiOQ3xU3t04ceebvdgEdYZEbGKaFVuOJjfyAtM/bSRgf892K3IJhIHYpbP +g6qBcF/TNbgAGMW1qE0eU4Inv2XBbGW551X0= Received: by 10.67.10.8 with SMTP id n8mr508426ugi.23.1215774270937; Fri, 11 Jul 2008 04:04:30 -0700 (PDT) Received: by 10.66.248.12 with HTTP; Fri, 11 Jul 2008 04:04:30 -0700 (PDT) Message-ID: Date: Fri, 11 Jul 2008 12:04:30 +0100 From: "Igor Mozolevsky" Sender: mozolevsky@gmail.com To: "Steve Kargl" In-Reply-To: <20080711033727.GA59707@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080711033727.GA59707@troutmask.apl.washington.edu> X-Google-Sender-Auth: 0463acd30865c674 Cc: freebsd-current@freebsd.org Subject: Re: OT: anoncvs1.freebsd.org asking for password? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2008 11:04:33 -0000 2008/7/11 Steve Kargl : > On Fri, Jul 11, 2008 at 12:38:52AM +0100, Igor Mozolevsky wrote: >> Anyone else experiencing this? >> >> > cvs -R -z9 -d anoncvs@anoncvs1.freebsd.org:/home/ncvs co -r RELENG_7 src >> Password: > > Yes. I switched to the other anoncvs server listed for the > USA region. cvs -R -z9 -d freebsdanoncvs@anoncvs.freebsd.org:/home/ncvs co -r RELENG_7 src just hangs, but works fine with CURRENT... From owner-freebsd-current@FreeBSD.ORG Fri Jul 11 12:33:19 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B9891065681 for ; Fri, 11 Jul 2008 12:33:19 +0000 (UTC) (envelope-from angelo@hongens.nl) Received: from smtp-out0.tiscali.nl (smtp-out0.tiscali.nl [195.241.79.175]) by mx1.freebsd.org (Postfix) with ESMTP id B9CBC8FC2E for ; Fri, 11 Jul 2008 12:33:18 +0000 (UTC) (envelope-from angelo@hongens.nl) Received: from [82.171.0.168] (helo=krypton.hongens.local) by smtp-out0.tiscali.nl with esmtp id 1KHHY5-0002kh-PL for ; Fri, 11 Jul 2008 14:16:29 +0200 Received: from localhost (localhost.hongens.local [127.0.0.1]) by krypton.hongens.local (Postfix) with ESMTP id 05AB210B4D for ; Fri, 11 Jul 2008 14:16:29 +0200 (CEST) X-Virus-Scanned: amavisd-new at hongens.nl Received: from krypton.hongens.local ([127.0.0.1]) by localhost (krypton.hongens.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TvqbQtwsdpbo for ; Fri, 11 Jul 2008 14:16:25 +0200 (CEST) Received: from [127.0.0.1] (tilburg.netmatch.nl [212.178.110.66]) by krypton.hongens.local (Postfix) with ESMTPA id C2F0110B4C for ; Fri, 11 Jul 2008 14:16:24 +0200 (CEST) Message-ID: <48774F17.4050703@hongens.nl> Date: Fri, 11 Jul 2008 14:16:23 +0200 From: =?ISO-8859-1?Q?Angelo_H=F6ngens?= User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: "freebsd-current@freebsd.org" References: <20080711120009.DA55310656E8@hub.freebsd.org> In-Reply-To: <20080711120009.DA55310656E8@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Dell's PERC6i X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2008 12:33:19 -0000 > Correct, I suppose these will be handled by mfi(4) device driver. I > have some Dell SC1430s that have Dell PERC 5i controllers. > > One disadvantage of these is that there's no native monitoring tool > for mfi(4) based devices. There's only a linux utility which I > haven't tried so far. However, it seems like porting might be easy > and bz@ has idicated some interest in this work. He unfortunately > seems to be busy these days ;-( > > -- Best regards, Daniel > mailto:danger@FreeBSD.org > > I'm running 7.0-RELEASE on a Dell PE 2900II with 10x300GB 15k disks in RAID1 + RAID5 + HS, working fine.. [angelo@zvr-bak-01 ~]$ cat /var/run/dmesg.boot | grep mfi mfi0: port 0xec00-0xecff mem 0xfc680000-0xfc6bffff,0xfc640000-0xfc67ffff irq 16 at device 0.0 on pci1 mfi0: Megaraid SAS driver Ver 2.00 mfi0: 2664 (267900058s/0x0020/0) - Shutdown command received from host mfi0: 2665 (4278190083s/0x0020/0) - PCI 0x041000 0x0460 0x041028 0x041f0c: Firmware initialization started (PCI ID 0060/1000/1f0c/1028) mfi0: 2666 (4278190083s/0x0020/0) - Type 18: Firmware version 1.11.52-0396 mfi0: 2667 (4278190083s/0x0008/0) - Battery Present mfi0: 2668 (4278190083s/0x0020/0) - Type 18: Package version 6.0.2-0002 mfi0: 2669 (4278190089s/0x0004/0) - PD 32(e0/s255) event: Enclosure (SES) discovered on PD 20(c None/p0) mfi0: 2670 (4278190090s/0x0002/0) - PD 32(e32/s255) event: Inserted: Encl PD 20 mfi0: 2671 (4278190090s/0x0002/0) - Type 29: Inserted: PD 20(c None/p0) Info: enclPd=20, scsiType=d, portMap=09, sasAddr=5001e0f0395b0200,0000000000000000 mfi0: 2672 (4278190090s/0x0002/0) - PD 00(e32/s0) event: Inserted: PD 00(e0x20/s0) mfi0: 2673 (4278190090s/0x0002/0) - Type 29: Inserted: PD 00(e0x20/s0) Info: enclPd=20, scsiType=0, portMap=00, sasAddr=1221000000000000,0000000000000000 mfi0: 2674 (4278190090s/0x0002/0) - PD 01(e32/s1) event: Inserted: PD 01(e0x20/s1) mfi0: 2675 (4278190090s/0x0002/0) - Type 29: Inserted: PD 01(e0x20/s1) Info: enclPd=20, scsiType=0, portMap=01, sasAddr=1221000001000000,0000000000000000 mfi0: 2676 (4278190090s/0x0002/0) - PD 02(e32/s2) event: Inserted: PD 02(e0x20/s2) mfi0: 2677 (4278190090s/0x0002/0) - Type 29: Inserted: PD 02(e0x20/s2) Info: enclPd=20, scsiType=0, portMap=02, sasAddr=1221000002000000,0000000000000000 mfi0: 2678 (4278190090s/0x0002/0) - PD 03(e32/s3) event: Inserted: PD 03(e0x20/s3) mfi0: 2679 (4278190090s/0x0002/0) - Type 29: Inserted: PD 03(e0x20/s3) Info: enclPd=20, scsiType=0, portMap=03, sasAddr=1221000003000000,0000000000000000 mfi0: 2680 (4278190090s/0x0002/0) - PD 04(e32/s4) event: Inserted: PD 04(e0x20/s4) mfi0: 2681 (4278190090s/0x0002/0) - Type 29: Inserted: PD 04(e0x20/s4) Info: enclPd=20, scsiType=0, portMap=04, sasAddr=5001e4f32f176804,0000000000000000 mfi0: 2682 (4278190090s/0x0002/0) - PD 05(e32/s5) event: Inserted: PD 05(e0x20/s5) mfi0: 2683 (4278190090s/0x0002/0) - Type 29: Inserted: PD 05(e0x20/s5) Info: enclPd=20, scsiType=0, portMap=04, sasAddr=5001e4f32f176805,0000000000000000 mfi0: 2684 (4278190090s/0x0002/0) - PD 06(e32/s6) event: Inserted: PD 06(e0x20/s6) mfi0: 2685 (4278190090s/0x0002/0) - Type 29: Inserted: PD 06(e0x20/s6) Info: enclPd=20, scsiType=0, portMap=04, sasAddr=5001e4f32f176806,0000000000000000 mfi0: 2686 (4278190090s/0x0002/0) - PD 07(e32/s7) event: Inserted: PD 07(e0x20/s7) mfi0: 2687 (4278190090s/0x0002/0) - Type 29: Inserted: PD 07(e0x20/s7) Info: enclPd=20, scsiType=0, portMap=04, sasAddr=5001e4f32f176807,0000000000000000 mfi0: 2688 (4278190090s/0x0002/0) - PD 08(e32/s8) event: Inserted: PD 08(e0x20/s8) mfi0: 2689 (4278190090s/0x0002/0) - Type 29: Inserted: PD 08(e0x20/s8) Info: enclPd=20, scsiType=0, portMap=04, sasAddr=5001e4f32f176808,0000000000000000 mfi0: 2690 (4278190090s/0x0002/0) - PD 09(e32/s9) event: Inserted: PD 09(e0x20/s9) mfi0: 2691 (4278190090s/0x0002/0) - Type 29: Inserted: PD 09(e0x20/s9) Info: enclPd=20, scsiType=0, portMap=04, sasAddr=5001e4f32f176809,0000000000000000 mfi0: 2692 (4278190091s/0x0042/0) - Type 22: Global Hot Spare created on PD 09(e0x20/s9) (global,rev,ea) mfi0: 2693 (4278190091s/0x0002/0) - PD 09(e32/s9) state prior 0 new 2: State change on PD 09(e0x20/s9) from UNCONFIGURED_GOOD(0) to HOT SPARE(2) mfi0: 2694 (4278190104s/0x0001/0) - VD 01/1 state prior 255 new 3: State change on VD 01/1 from UNKNOWN(ff) to OPTIMAL(3) mfi0: 2695 (4278190104s/0x0001/0) - VD 01/1 event: VD 01/1 is now OPTIMAL mfi0: 2696 (267900089s/0x0020/0) - Adapter ticks 267900089 elapsed 25s: Time established as 06/27/08 16:41:29; (25 seconds since power on) mfi0: 2697 (267900132s/0x0008/0) - Battery temperature is normal mfi0: 2698 (267900132s/0x0008/0) - Current capacity of the battery is above threshold mfi0: [ITHREAD] mfid0: on mfi0 mfid0: 714880MB (1464074240 sectors) RAID volume '' is optimal mfid1: on mfi0 mfid1: 4289280MB (8784445440 sectors) RAID volume '' is optimal Trying to mount root from ufs:/dev/mfid0s1a I must say, this looks quite impressive: [angelo@zvr-bak-01 ~]$ sudo zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT tank1 668G 3.24M 668G 0% ONLINE - tank2 4.06T 1.44T 2.62T 35% ONLINE - I put the ZFS pools on top of the HW RAID, because the controller does not support JBOD. You could export each disk as a single disk RAID0, but I've read that if a disk fails, ZFS won't notice, and the hotspare would not kick in. Not having a native raid management tool is a very bad thing, but this is a non-production machine (well, at least not front-end), so if a disk fails the DRAC will notice me, and I can take appropriate step in the BIOS controller manager. Angelo Hongens. From owner-freebsd-current@FreeBSD.ORG Fri Jul 11 15:08:07 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F11A1065676 for ; Fri, 11 Jul 2008 15:08:07 +0000 (UTC) (envelope-from brdbrd@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by mx1.freebsd.org (Postfix) with ESMTP id 35B838FC13 for ; Fri, 11 Jul 2008 15:08:06 +0000 (UTC) (envelope-from brdbrd@gmail.com) Received: by qw-out-2122.google.com with SMTP id 9so91893qwb.7 for ; Fri, 11 Jul 2008 08:08:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=+wRa9kmnYI9Z7OxNTx8Dh62wFOLyOKHYJqItgxdx244=; b=YubBBT0jPCKqvaAHC1qI05kvpA1L6j5DUtK+pasVZISNYYlLXLrW+tvQslpXLYOWHB TTc+Tmk1/Vlft/OyqyGDLM6SadXX1SFXL+8DO3vHbUrntqor58pxKgZ6dcActq7FWYfF g/HlZ1z8entWgHsYnQopIHd4ehMkLHoYK5K0M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=SGCjj55ZonHxiEgi/Rh2Gl26Sk8fnJI4kvRkO5JRezfgIEQ/552Lv7luIsADwE8TVw G+No2dSitYWDqoFg4/YJ7qUYesmldk7Uszj+w1vCGY9rPrIHtpr7DmmhPDzhva1Rmt7P KUi3opAFdnNEvo0p14q2ZT0UqHfuZOep0ehsc= Received: by 10.150.150.3 with SMTP id x3mr2874053ybd.110.1215787406199; Fri, 11 Jul 2008 07:43:26 -0700 (PDT) Received: by 10.150.151.4 with HTTP; Fri, 11 Jul 2008 07:43:26 -0700 (PDT) Message-ID: <35ffa5710807110743v624be12y716a14b44b9361d@mail.gmail.com> Date: Fri, 11 Jul 2008 08:43:26 -0600 From: "Brad Davis" Sender: brdbrd@gmail.com To: "Igor Mozolevsky" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: 7d294c9a34b3f69d Cc: freebsd-current@freebsd.org Subject: Re: OT: anoncvs1.freebsd.org asking for password? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2008 15:08:07 -0000 On Thu, Jul 10, 2008 at 5:38 PM, Igor Mozolevsky wrote: > Anyone else experiencing this? > >> cvs -R -z9 -d anoncvs@anoncvs1.freebsd.org:/home/ncvs co -r RELENG_7 src > Password: Fixed, sorry I broke the pam.d/sshd in the upgrade from 6.2 to 7.0. Regards, Brad Davis From owner-freebsd-current@FreeBSD.ORG Fri Jul 11 15:35:26 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F2D51065675 for ; Fri, 11 Jul 2008 15:35:26 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout013.mac.com (asmtpout013.mac.com [17.148.16.88]) by mx1.freebsd.org (Postfix) with ESMTP id 2BC6C8FC08 for ; Fri, 11 Jul 2008 15:35:24 +0000 (UTC) (envelope-from xcllnt@mac.com) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from [192.168.1.102] (209-128-86-226.BAYAREA.NET [209.128.86.226]) by asmtp013.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0K3I00C193397YA0@asmtp013.mac.com> for freebsd-current@freebsd.org; Fri, 04 Jul 2008 14:16:23 -0700 (PDT) Message-id: <3F7F280F-C3ED-4E2E-9865-66A11FC3F03F@mac.com> From: Marcel Moolenaar To: Dmitry Morozovsky In-reply-to: <20080705011154.G97379@woozle.rinet.ru> Date: Fri, 04 Jul 2008 14:16:21 -0700 References: <20080701181358.GA93601@wep4017.physik.uni-wuerzburg.de> <20080704135827.H35668@woozle.rinet.ru> <22A6B038-44BB-4072-8A6E-8C1D5855CB14@mac.com> <20080705011154.G97379@woozle.rinet.ru> X-Mailer: Apple Mail (2.926) Cc: Alexey Shuvaev , freebsd-current@freebsd.org Subject: Re: puc(4) man page update? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2008 15:35:26 -0000 On Jul 4, 2008, at 2:12 PM, Dmitry Morozovsky wrote: > On Fri, 4 Jul 2008, Marcel Moolenaar wrote: > > MM> > doesn't splitting uart out of kernel broke serial console? > Last time I > MM> > checked > MM> > it did. > MM> > MM> Yes, it does. The serial console is setup/initialized and > MM> used before pre-loaded modules are linked and/or usable. > MM> We don't have the support in place that allows you to boot > MM> without console until pre-loaded modules are initialized, > MM> at which time add a low-level console device is setup. > MM> It's not that hard to do, I think. > MM> > MM> So, currently low-level console drivers, such as dcons(4), > MM> sio(4) and uart(4) need to be compiled into the kernel. > MM> Consequently any devices/busses to which any of these can > MM> attach must be compiled into the kernel as well. Of these > MM> acpi(4) and puc(4) are good examples. acpi(4) is a good > MM> example because we use hints to work around the issue and > MM> have sio(4) attach to isa(4) instead... > > Well, than, what is the reason to keep puc(4) out of GENERIC then? ;-P It's in GENERIC on ia64 :-) If no one has any strong objections, I'll add puc(4) to GENERIC for all platforms. -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Fri Jul 11 18:15:26 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 516C11065673 for ; Fri, 11 Jul 2008 18:15:26 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id F39638FC16 for ; Fri, 11 Jul 2008 18:15:25 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 94476 invoked by uid 89); 11 Jul 2008 18:18:14 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 11 Jul 2008 18:18:14 -0000 Message-ID: <4877A343.2010602@ibctech.ca> Date: Fri, 11 Jul 2008 14:15:31 -0400 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Boot from ZFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2008 18:15:26 -0000 Hi all, I'm configuring a new storage server, and after reviewing all of my storage type options, I'm going to go with ZFS. I'd like to know if -current provides the following functionality to be had directly from the installer: "In the latest code, it's possible to boot directly from ZFS, no longer requiring a small non-ZFS boot partition. "No you can use only ZFS and just enjoy it," he stated." ...if not, where can I find information on the best procedure to do so? Regards, Steve From owner-freebsd-current@FreeBSD.ORG Fri Jul 11 18:24:32 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12B981065673 for ; Fri, 11 Jul 2008 18:24:32 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.freenix.fr (keltia.freenix.org [IPv6:2001:660:330f:f820:213:72ff:fe15:f44]) by mx1.freebsd.org (Postfix) with ESMTP id C66E98FC17 for ; Fri, 11 Jul 2008 18:24:31 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from localhost (localhost [127.0.0.1]) by keltia.freenix.fr (Postfix/TLS) with ESMTP id AE0D839A6C for ; Fri, 11 Jul 2008 20:24:30 +0200 (CEST) X-Virus-Scanned: amavisd-new at keltia.freenix.fr Received: from keltia.freenix.fr ([127.0.0.1]) by localhost (keltia.freenix.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n7tIkvOjR5m2 for ; Fri, 11 Jul 2008 20:24:30 +0200 (CEST) Received: by keltia.freenix.fr (Postfix/TLS, from userid 101) id 618E439A65; Fri, 11 Jul 2008 20:24:30 +0200 (CEST) Date: Fri, 11 Jul 2008 20:24:30 +0200 From: Ollivier Robert To: freebsd-current@freebsd.org Message-ID: <20080711182430.GA76378@keltia.freenix.fr> References: <4877A343.2010602@ibctech.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4877A343.2010602@ibctech.ca> X-Operating-System: MacOS X / Macbook Pro - FreeBSD 7 / Dell D820 SMP User-Agent: Mutt/1.5.17 (2007-11-01) Subject: Re: Boot from ZFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2008 18:24:32 -0000 According to Steve Bertrand: > "In the latest code, it's possible to boot directly from ZFS, no longer > requiring a small non-ZFS boot partition. "No you can use only ZFS and just > enjoy it," he stated." > > ...if not, where can I find information on the best procedure to do so? This code is not yet committed to CURRENT, it is currently in a P4 branch. Doug Rabson is also doing some work on it according to p4 changes. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Darwin sidhe.keltia.net Version 9.2.0: Tue Feb 5 16:13:22 PST 2008; i386 From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 00:43:17 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 378CB106566B for ; Sat, 12 Jul 2008 00:43:17 +0000 (UTC) (envelope-from duncan.young@pobox.com) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id 0C7CC8FC1A for ; Sat, 12 Jul 2008 00:43:16 +0000 (UTC) (envelope-from duncan.young@pobox.com) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 18A2713A0CB for ; Fri, 11 Jul 2008 20:43:16 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 11 Jul 2008 20:43:16 -0400 X-Sasl-enc: ZSJHhUh8SckvYKzZb7p29Cv1y1rFAB/gUbBatHxLgpuG 1215823395 Received: from triple0.qld.optushome.com.au (c122-108-168-198.rochd4.qld.optusnet.com.au [122.108.168.198]) by mail.messagingengine.com (Postfix) with ESMTPSA id 9DEC22975D for ; Fri, 11 Jul 2008 20:43:15 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by triple0.qld.optushome.com.au (Postfix) with ESMTP id BBE7DD05F for ; Sat, 12 Jul 2008 10:43:11 +1000 (EST) From: Duncan Young To: freebsd-current@freebsd.org Date: Sat, 12 Jul 2008 10:43:09 +1000 User-Agent: KMail/1.9.7 References: <4877A343.2010602@ibctech.ca> <20080711182430.GA76378@keltia.freenix.fr> In-Reply-To: <20080711182430.GA76378@keltia.freenix.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807121043.10473.duncan.young@pobox.com> Subject: Re: Boot from ZFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: duncan.young@pobox.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 00:43:17 -0000 Be carefull, I've just had a 6 disk raidz array die. Complete failure which required restore from backup (the controler card which had access to 4 of the disks, lost one disk, then a second (at which point the machine paniced, Upon reboot the raidz array was useless (Metadata corrupted)). I'm also getting reasonably frequent machine lockups (panics) in the zfs code. I'm going to start collecting crash dumps see if anyone can help in the next week or two. I guess what I'm trying to say is, that you can still lose everything on an entire pool, so backups are still essential, an a couple of smaller pools is probably preferable to one big pool (restore time is less). zfs is not %100 (yet?). The lack of any type of fsck still causes me concern. Duncan PS I do think zfs is great, but it's not perfect. If I can boot directly off zfs, I would make sure I had an offline replication of the boot disk, in case of failure. On Sat, 12 Jul 2008 04:24:30 am Ollivier Robert wrote: > According to Steve Bertrand: > > "In the latest code, it's possible to boot directly from ZFS, no longer > > requiring a small non-ZFS boot partition. "No you can use only ZFS and > > just enjoy it," he stated." > > > > ...if not, where can I find information on the best procedure to do so? > > This code is not yet committed to CURRENT, it is currently in a P4 branch. > Doug Rabson is also doing some work on it according to p4 changes. From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 00:57:54 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACE8C1065671 for ; Sat, 12 Jul 2008 00:57:54 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (unknown [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 420358FC0A for ; Sat, 12 Jul 2008 00:57:54 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (unknown [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 6612728448 for ; Sat, 12 Jul 2008 08:57:53 +0800 (CST) Received: from localhost (unknown [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id D897DEB20A7; Sat, 12 Jul 2008 08:57:52 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id bgngxz-FxLKt; Sat, 12 Jul 2008 08:57:40 +0800 (CST) Received: from charlie.delphij.net (71.5.7.139.ptr.us.xo.net [71.5.7.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id C1AFFEB0DC7; Sat, 12 Jul 2008 08:57:39 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=ozc3sxnZCZh8jLeY0UAddg1M6JkQdFU0NhKdrVoYwltOz18fDRJTxTtzBrs3isR8R /V6mx7PRq1udWjnMjhZ3Q== Message-ID: <48780181.2080905@delphij.net> Date: Fri, 11 Jul 2008 17:57:37 -0700 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: duncan.young@pobox.com References: <4877A343.2010602@ibctech.ca> <20080711182430.GA76378@keltia.freenix.fr> <200807121043.10473.duncan.young@pobox.com> In-Reply-To: <200807121043.10473.duncan.young@pobox.com> X-Enigmail-Version: 0.95.6 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Boot from ZFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 00:57:54 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Duncan Young wrote: | Be carefull, I've just had a 6 disk raidz array die. Complete failure which | required restore from backup (the controler card which had access to 4 of the | disks, lost one disk, then a second (at which point the machine paniced, Upon | reboot the raidz array was useless (Metadata corrupted)). I'm also getting | reasonably frequent machine lockups (panics) in the zfs code. I'm going to | start collecting crash dumps see if anyone can help in the next week or two. That's really unfortunate. Some sort of automated disk monitoring stuff would be essential for RAID, this includes RAID-Z. Did you used the whole disk dedicatedly for the pool, or (g)labeled before adding it into the zpool? Did 'zpool import -f' help? | I guess what I'm trying to say is, that you can still lose everything on an | entire pool, so backups are still essential, an a couple of smaller pools is | probably preferable to one big pool (restore time is less). zfs is not %100 | (yet?). The lack of any type of fsck still causes me concern. It's always true that backup is always important if data is valuable :) ~ The benefit having larger pool is that the administrator would have the ability to use larger disk space in one ZFS file system (which can not come cross zpool boundary), but it is recommended that when creating the zpool, we use smaller raid-z groups, e.g. don't use 48 disks within one raid-z group, a few disks (like 3-5) within one raid-z group would be fine. Regarding to fsck, 'zpool scrub' is pretty much like a fsck plus data integration check. It would be, however, almost impossible to recover data if zpool is completely corrupt according to some Sun sources, but my experience with bad disks within raid-z did not turned me into a unrecoverable state (yet). Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkh4AYEACgkQi+vbBBjt66A0FQCfVM/kpGQYJuNiUffxtsTgAgtJ lJIAnilKkCg1Tvf5JWd6aH9XyMjUfhBX =djMu -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 04:55:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1607F106564A for ; Sat, 12 Jul 2008 04:55:15 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id BBD228FC14 for ; Sat, 12 Jul 2008 04:55:14 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.2/8.14.2) with ESMTP id m6C4t8O0028857; Fri, 11 Jul 2008 23:55:08 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.2/8.14.2/Submit) id m6C4t8x2028856; Fri, 11 Jul 2008 23:55:08 -0500 (CDT) (envelope-from brooks) Date: Fri, 11 Jul 2008 23:55:08 -0500 From: Brooks Davis To: Duncan Young Message-ID: <20080712045508.GA28756@lor.one-eyed-alien.net> References: <4877A343.2010602@ibctech.ca> <20080711182430.GA76378@keltia.freenix.fr> <200807121043.10473.duncan.young@pobox.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline In-Reply-To: <200807121043.10473.duncan.young@pobox.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Fri, 11 Jul 2008 23:55:08 -0500 (CDT) Cc: freebsd-current@freebsd.org Subject: Re: Boot from ZFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 04:55:15 -0000 --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 12, 2008 at 10:43:09AM +1000, Duncan Young wrote: > Be carefull, I've just had a 6 disk raidz array die. Complete failure w= hich=20 > required restore from backup (the controler card which had access to 4 of= the=20 > disks, lost one disk, then a second (at which point the machine paniced, = Upon=20 > reboot the raidz array was useless (Metadata corrupted)). I'm also getti= ng=20 > reasonably frequent machine lockups (panics) in the zfs code. I'm going = to=20 > start collecting crash dumps see if anyone can help in the next week or t= wo. If you look at the research on disk corruption and failure modes both in recent proceeding of FAST and the latest issue of ;LOGIN: it's clear that any RAID-like scheme that does not tolerate double faults is likely to fail. In theory, zfs should tolerate certain classes of faults better than some other technologies, but can't deal with full disk double faults unless you use raidz2. > I guess what I'm trying to say is, that you can still lose everything on = an=20 > entire pool, so backups are still essential, an a couple of smaller pools= is=20 > probably preferable to one big pool (restore time is less). zfs is not %= 100=20 > (yet?). The lack of any type of fsck still causes me concern. Regardless of the technology, backups are essential. If you actually value your data, off-site backups are essential. -- Brooks > Duncan >=20 > PS I do think zfs is great, but it's not perfect. If I can boot directly= off=20 > zfs, I would make sure I had an offline replication of the boot disk, in = case=20 > of failure. >=20 > On Sat, 12 Jul 2008 04:24:30 am Ollivier Robert wrote: > > According to Steve Bertrand: > > > "In the latest code, it's possible to boot directly from ZFS, no long= er > > > requiring a small non-ZFS boot partition. "No you can use only ZFS and > > > just enjoy it," he stated." > > > > > > ...if not, where can I find information on the best procedure to do s= o? > > > > This code is not yet committed to CURRENT, it is currently in a P4 bran= ch. > > Doug Rabson is also doing some work on it according to p4 changes. >=20 >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >=20 --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFIeDkrXY6L6fI4GtQRApf4AJ9y5UeJKCsywim81Uo0vOAT5LsUPACdGXrA FuJFlcQ5WWcBt2WWMZQfopw= =3oyq -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z-- From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 08:37:16 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2AAA4106567E for ; Sat, 12 Jul 2008 08:37:16 +0000 (UTC) (envelope-from duncan.young@pobox.com) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id DE04E8FC29 for ; Sat, 12 Jul 2008 08:37:15 +0000 (UTC) (envelope-from duncan.young@pobox.com) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 86B5E1396F5; Sat, 12 Jul 2008 04:37:15 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sat, 12 Jul 2008 04:37:15 -0400 X-Sasl-enc: Kq01FZD6Hxx6ovj7soenJ3//jB+FTJ86A/u0wVA8T3eD 1215851834 Received: from triple0.qld.optushome.com.au (c122-108-168-198.rochd4.qld.optusnet.com.au [122.108.168.198]) by mail.messagingengine.com (Postfix) with ESMTPSA id 7BA9C3F44; Sat, 12 Jul 2008 04:37:14 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by triple0.qld.optushome.com.au (Postfix) with ESMTP id 302E21B744; Sat, 12 Jul 2008 18:37:12 +1000 (EST) From: Duncan Young To: d@delphij.net Date: Sat, 12 Jul 2008 18:37:11 +1000 User-Agent: KMail/1.9.7 References: <4877A343.2010602@ibctech.ca> <200807121043.10473.duncan.young@pobox.com> <48780181.2080905@delphij.net> In-Reply-To: <48780181.2080905@delphij.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200807121837.11812.duncan.young@pobox.com> Cc: freebsd-current@freebsd.org Subject: Re: Boot from ZFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: duncan.young@pobox.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 08:37:16 -0000 I did use whole disks (the root disks (mirrored) are sliced into boot, swap, and root. zpool status pool: big state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM big ONLINE 0 0 0 raidz1 ONLINE 0 0 0 ad4 ONLINE 0 0 0 ad6 ONLINE 0 0 0 da0 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 0 errors: No known data errors pool: rootzfs state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM rootzfs ONLINE 0 0 0 mirror ONLINE 0 0 0 label/sysdisk_A ONLINE 0 0 0 label/sysdisk_B ONLINE 0 0 0 errors: No known data errors The zpool import -f didn't want to work. The problem with scrubbing is that the pool needs to be online first (I think). I couldn't import it, it just said that the metadata was corrupt. The frustrating thing was that the problem wasn't from the disks, but from the controller. Upon reboot all the disks were OK, but the meta data wasn't. Kind of frustrating. If you're interested, from /var/log/messages: root: ZFS: checksum mismatch, zpool=big path=/dev/da0 offset=469395789824 size=512 kernel: hptrr: start channel [0,2] kernel: hptrr: channel [0,2] started successfully kernel: hptrr: start channel [0,2] kernel: hptrr: channel [0,2] started successfully kernel: hptrr: start channel [0,0] kernel: hptrr: start channel [0,2] kernel: hptrr: channel [0,2] started successfully kernel: hptrr: channel [0,0] started successfully root: ZFS: checksum mismatch, zpool=big path=/dev/da0 offset=468971378176 size=512 root: ZFS: checksum mismatch, zpool=big path=/dev/da0 offset=468971382272 size=512 root: ZFS: checksum mismatch, zpool=big path=/dev/da0 offset=468971412480 size=512 kernel: hptrr: start channel [0,2] kernel: hptrr: [0 2 ] failed to perform Soft Reset kernel: hptrr: [0,2,0] device disconnected on channel root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=92035899904 size=512 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=277797371392 size=512 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=91641628160 size=1536 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=92035900928 size=4608 error=22 <100 lines snipped> root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=92035913216 size=1024 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=92035914240 size=512 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=191856965120 size=512 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=191856964608 size=512 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=277797383680 size=1536 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=277797384704 size=512 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=277797383680 size=1024 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=92035915264 size=512 error=22 kernel: (da0:hptrr0:0:0:0): Synchronize cache failed, status == 0x39, scsi status == 0x0 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=92035914752 size=512 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=92035915776 size=1024 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=191856965632 size=2560 error=22 <90 lines snipped> root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=277797380608 size=1024 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=277797385216 size=512 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=277797382656 size=512 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=277797386240 size=1024 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=455680 size=1024 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=193536 size=1024 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=500027814912 size=1024 error=22 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=500028077056 size=1024 error=22 root: ZFS: vdev failure, zpool=big type=vdev.open_failed kernel: hptrr: start channel [0,0] kernel: hptrr: [0 0 ] failed to perform Soft Reset kernel: hptrr: [0,0,0] device disconnected on channel root: ZFS: vdev I/O failure, zpool=big path=/dev/da1 offset=56768110080 size=512 error=22 syslogd: kernel boot file is /boot/kernel/kernel kernel: Copyright (c) 1992-2008 The FreeBSD Project. kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 etc regards Duncan On Sat, 12 Jul 2008 10:57:37 am Xin LI wrote: > Duncan Young wrote: > | Be carefull, I've just had a 6 disk raidz array die. Complete > > failure which > > | required restore from backup (the controler card which had access to 4 > > of the > > | disks, lost one disk, then a second (at which point the machine > > paniced, Upon > > | reboot the raidz array was useless (Metadata corrupted)). I'm also > > getting > > | reasonably frequent machine lockups (panics) in the zfs code. I'm > > going to > > | start collecting crash dumps see if anyone can help in the next week > > or two. > > That's really unfortunate. Some sort of automated disk monitoring stuff > would be essential for RAID, this includes RAID-Z. Did you used the > whole disk dedicatedly for the pool, or (g)labeled before adding it into > the zpool? Did 'zpool import -f' help? > > | I guess what I'm trying to say is, that you can still lose everything > > on an > > | entire pool, so backups are still essential, an a couple of smaller > > pools is > > | probably preferable to one big pool (restore time is less). zfs is > > not %100 > > | (yet?). The lack of any type of fsck still causes me concern. > > It's always true that backup is always important if data is valuable :) > ~ The benefit having larger pool is that the administrator would have the > ability to use larger disk space in one ZFS file system (which can not > come cross zpool boundary), but it is recommended that when creating the > zpool, we use smaller raid-z groups, e.g. don't use 48 disks within one > raid-z group, a few disks (like 3-5) within one raid-z group would be fine. > > Regarding to fsck, 'zpool scrub' is pretty much like a fsck plus data > integration check. It would be, however, almost impossible to recover > data if zpool is completely corrupt according to some Sun sources, but > my experience with bad disks within raid-z did not turned me into a > unrecoverable state (yet). > > Cheers, From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 08:53:20 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F09D1065670 for ; Sat, 12 Jul 2008 08:53:20 +0000 (UTC) (envelope-from duncan.young@pobox.com) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id DD0948FC1A for ; Sat, 12 Jul 2008 08:53:19 +0000 (UTC) (envelope-from duncan.young@pobox.com) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 574BB13A39C; Sat, 12 Jul 2008 04:53:19 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sat, 12 Jul 2008 04:53:19 -0400 X-Sasl-enc: PvbVXLUdZHXdZjN0YvQ2NtbIKx4vqCadVW2MEMWl1VQH 1215852798 Received: from triple0.qld.optushome.com.au (c122-108-168-198.rochd4.qld.optusnet.com.au [122.108.168.198]) by mail.messagingengine.com (Postfix) with ESMTPSA id AE205C0A0; Sat, 12 Jul 2008 04:53:18 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by triple0.qld.optushome.com.au (Postfix) with ESMTP id 68E411B791; Sat, 12 Jul 2008 18:53:16 +1000 (EST) From: Duncan Young To: Brooks Davis Date: Sat, 12 Jul 2008 18:53:15 +1000 User-Agent: KMail/1.9.7 References: <4877A343.2010602@ibctech.ca> <200807121043.10473.duncan.young@pobox.com> <20080712045508.GA28756@lor.one-eyed-alien.net> In-Reply-To: <20080712045508.GA28756@lor.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807121853.16083.duncan.young@pobox.com> Cc: freebsd-current@freebsd.org Subject: Re: Boot from ZFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: duncan.young@pobox.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 08:53:20 -0000 On Sat, 12 Jul 2008 02:55:08 pm Brooks Davis wrote: > On Sat, Jul 12, 2008 at 10:43:09AM +1000, Duncan Young wrote: > > Be carefull, I've just had a 6 disk raidz array die. Complete failure which > > required restore from backup (the controler card which had access to 4 of the > > disks, lost one disk, then a second (at which point the machine paniced, Upon > > reboot the raidz array was useless (Metadata corrupted)). I'm also getting > > reasonably frequent machine lockups (panics) in the zfs code. I'm going to > > start collecting crash dumps see if anyone can help in the next week or two. > > If you look at the research on disk corruption and failure modes both > in recent proceeding of FAST and the latest issue of ;LOGIN: it's clear > that any RAID-like scheme that does not tolerate double faults is likely > to fail. In theory, zfs should tolerate certain classes of faults > better than some other technologies, but can't deal with full disk > double faults unless you use raidz2. In this case the problem, I believe, was the controller card/software. Unfortunately on a home system, I can't spread my disks across different controllers. The disks themselves are fine (I'm using them right now). My only issue is that the pool seems think its corrupted as soon as an error occurred on the second disk, Even though I would have thought that the meta-data (which I believe is spread across multiple disks) should not have a chance to be made irreparable. i.e. from /var/log/messages: Jul 10 18:39:27 triple0 root: ZFS: vdev I/O failure, zpool=big path=/dev/da0 offset=500028077056 size=1024 error=22 Jul 10 18:39:27 triple0 root: ZFS: vdev failure, zpool=big type=vdev.open_failed Jul 10 18:40:14 triple0 kernel: hptrr: start channel [0,0] Jul 10 18:40:25 triple0 kernel: hptrr: [0 0 ] failed to perform Soft Reset Jul 10 18:40:25 triple0 kernel: hptrr: [0,0,0] device disconnected on channel Jul 10 18:40:25 triple0 root: ZFS: vdev I/O failure, zpool=big path=/dev/da1 offset=56768110080 size=512 error=22 Jul 10 20:15:36 triple0 syslogd: kernel boot file is /boot/kernel/kernel I have had quite a few corruptions from writing to non-parity USB/firewire drives (which have an unfortunate tendency to "drop out" partway through a send/receive, but this just requires a scrub, and destroying of the corrupted snapshot. Never had a problem with importing the pool, until now. regards Duncan > > > I guess what I'm trying to say is, that you can still lose everything on an > > entire pool, so backups are still essential, an a couple of smaller pools is > > probably preferable to one big pool (restore time is less). zfs is not %100 > > (yet?). The lack of any type of fsck still causes me concern. > > Regardless of the technology, backups are essential. If you actually value > your data, off-site backups are essential. From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 14:34:32 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6EAD106566C for ; Sat, 12 Jul 2008 14:34:32 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by mx1.freebsd.org (Postfix) with ESMTP id AC00F8FC0A for ; Sat, 12 Jul 2008 14:34:32 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so2311706wah.3 for ; Sat, 12 Jul 2008 07:34:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:x-google-sender-auth; bh=bG+JRxhru9C0RDZB7sIJRe+b3R8U/EI/c4YU+MxnRdQ=; b=sKvDlrOuyLPea7d09ps6O8V7UllzetMCs7RgwTlyaOVnJrhPAZeBRnEjl5HvTkyj7V u+7AGqtoGNUlVw4M3UC7pra8CO5P/VHlpcD0pN8+mTQGUsBrEo6UTIgpGnmUzlKBsXOE HvqY3572Gfrk+jomPyG3qddI6jSST1G9qTEyg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :x-google-sender-auth; b=S6POHzMjMwNVAyDSCpQQRbCftRgP3K10eZeASuMNg7FKCvDQON0xOaF0gsc7Clei8g 3Xk6FWwyZ2VsNh2Xn0m0o4LVxBhigUi3dgn3fYhzB9klK+lY/1iiy0/GSCQn+zCVwcRm GkmXYO/uh7+PsgijPf0XL6muhBlrhUHt29IQI= Received: by 10.115.79.8 with SMTP id g8mr15509134wal.215.1215871525963; Sat, 12 Jul 2008 07:05:25 -0700 (PDT) Received: by 10.114.80.5 with HTTP; Sat, 12 Jul 2008 07:05:25 -0700 (PDT) Message-ID: <2e77fc10807120705ud76cea2g1cc634c3012df684@mail.gmail.com> Date: Sat, 12 Jul 2008 17:05:25 +0300 From: "Niki Denev" Sender: ndenev@gmail.com To: "FreeBSD Current" MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_39179_11444668.1215871525963" X-Google-Sender-Auth: 1e963b0fb7ee078e Subject: [PATCH] dhclient link timeout option X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 14:34:33 -0000 ------=_Part_39179_11444668.1215871525963 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello, I've noticed that when I have both my wired and wireless interfaces on my laptop enabled with DHCP, it is always started on boot, but if there is no cable plugged or known wifi ap, dhclient waits for 10 seconds for link for each interface and thus delaying the boot process by 20 seconds. (background_dhclient didn't help). So I've decided to add a link timeout option to dhclient to specify how long it should wait for link on startup, which seems to work pretty nicely in my setup. I hope others might find this useful too. Regards, Niki ------=_Part_39179_11444668.1215871525963 Content-Type: application/octet-stream; name=dhclient-linktimeout.patch Content-Transfer-Encoding: base64 X-Attachment-Id: f_fijvful80 Content-Disposition: attachment; filename=dhclient-linktimeout.patch ZGlmZiAtdXIgc2Jpbi9kaGNsaWVudC5vcmlnL2RoY2xpZW50Ljggc2Jpbi9kaGNsaWVudC9kaGNs aWVudC44Ci0tLSBzYmluL2RoY2xpZW50Lm9yaWcvZGhjbGllbnQuOAkyMDA4LTA3LTEyIDA5OjQw OjM5LjAwMDAwMDAwMCArMDMwMAorKysgc2Jpbi9kaGNsaWVudC9kaGNsaWVudC44CTIwMDgtMDct MTIgMDk6NTM6MTcuMDAwMDAwMDAwICswMzAwCkBAIC04Myw2ICs4Myw4IEBACiBTcGVjaWZ5IGFu IGFsdGVybmF0ZSBsb2NhdGlvbiwKIC5BciBmaWxlICwKIGZvciB0aGUgbGVhc2VzIGZpbGUuCisu SXQgRmwgdCBBciB0aW1lb3V0CitTcGVjaWZ5IGhvdyBtYW55IHNlY29uZHMgdG8gd2FpdCBmb3Ig bGluay4KIC5JdCBGbCBxCiBGb3JjZXMKIC5ObQpkaWZmIC11ciBzYmluL2RoY2xpZW50Lm9yaWcv ZGhjbGllbnQuYyBzYmluL2RoY2xpZW50L2RoY2xpZW50LmMKLS0tIHNiaW4vZGhjbGllbnQub3Jp Zy9kaGNsaWVudC5jCTIwMDgtMDctMTIgMDk6NDA6MzkuMDAwMDAwMDAwICswMzAwCisrKyBzYmlu L2RoY2xpZW50L2RoY2xpZW50LmMJMjAwOC0wNy0xMiAwOTo1Mzo0Ni4wMDAwMDAwMDAgKzAzMDAK QEAgLTMxMiwxMyArMzEyLDE0IEBACiAJaW50CQkJIGNoLCBmZCwgcXVpZXQgPSAwLCBpID0gMDsK IAlpbnQJCQkgcGlwZV9mZFsyXTsKIAlpbnQJCQkgaW1tZWRpYXRlX2RhZW1vbiA9IDA7CisJaW50 CQkJIGxpbmtfdGltZW91dCA9IDEwOwogCXN0cnVjdCBwYXNzd2QJCSpwdzsKIAogCS8qIEluaXRp YWxseSwgbG9nIGVycm9ycyB0byBzdGRlcnIgYXMgd2VsbCBhcyB0byBzeXNsb2dkLiAqLwogCW9w ZW5sb2coX19wcm9nbmFtZSwgTE9HX1BJRCB8IExPR19OREVMQVksIERIQ1BEX0xPR19GQUNJTElU WSk7CiAJc2V0bG9nbWFzayhMT0dfVVBUTyhMT0dfREVCVUcpKTsKIAotCXdoaWxlICgoY2ggPSBn ZXRvcHQoYXJnYywgYXJndiwgImJjOmRsOnF1IikpICE9IC0xKQorCXdoaWxlICgoY2ggPSBnZXRv cHQoYXJnYywgYXJndiwgImJjOmRsOnQ6cXUiKSkgIT0gLTEpCiAJCXN3aXRjaCAoY2gpIHsKIAkJ Y2FzZSAnYic6CiAJCQlpbW1lZGlhdGVfZGFlbW9uID0gMTsKQEAgLTMzNSw2ICszMzYsMTMgQEAK IAkJY2FzZSAncSc6CiAJCQlxdWlldCA9IDE7CiAJCQlicmVhazsKKwkJY2FzZSAndCc6CisJCQls aW5rX3RpbWVvdXQgPSAoaW50KXN0cnRvbChvcHRhcmcsIChjaGFyICoqKU5VTEwsIDEwKTsKKwkJ CWlmIChsaW5rX3RpbWVvdXQgPCAwKQorCQkJICAgbGlua190aW1lb3V0ID0gMDsKKwkJCWlmIChs aW5rX3RpbWVvdXQgPiAxMCkKKwkJCSAgIGxpbmtfdGltZW91dCA9IDEwOworCQkJYnJlYWs7CiAJ CWNhc2UgJ3UnOgogCQkJdW5rbm93bl9vayA9IDA7CiAJCQlicmVhazsKQEAgLTM3OCw3ICszODYs NyBAQAogCQl3aGlsZSAoIWludGVyZmFjZV9saW5rX3N0YXR1cyhpZmktPm5hbWUpKSB7CiAJCQlm cHJpbnRmKHN0ZGVyciwgIi4iKTsKIAkJCWZmbHVzaChzdGRlcnIpOwotCQkJaWYgKCsraSA+IDEw KSB7CisJCQlpZiAoKytpID4gbGlua190aW1lb3V0KSB7CiAJCQkJZnByaW50ZihzdGRlcnIsICIg Z2l2aW5nIHVwXG4iKTsKIAkJCQlleGl0KDEpOwogCQkJfQpAQCAtNDU1LDcgKzQ2Myw4IEBACiAJ ZXh0ZXJuIGNoYXIJKl9fcHJvZ25hbWU7CiAKIAlmcHJpbnRmKHN0ZGVyciwgInVzYWdlOiAlcyBb LWJkcXVdICIsIF9fcHJvZ25hbWUpOwotCWZwcmludGYoc3RkZXJyLCAiWy1jIGNvbmZmaWxlXSBb LWwgbGVhc2VmaWxlXSBpbnRlcmZhY2VcbiIpOworCWZwcmludGYoc3RkZXJyLCAiWy10IGxpbmsg dGltZW91dF0gWy1jIGNvbmZmaWxlXSAiKTsKKwlmcHJpbnRmKHN0ZGVyciwgIlstbCBsZWFzZWZp bGVdIGludGVyZmFjZVxuIik7CiAJZXhpdCgxKTsKIH0KIAo= ------=_Part_39179_11444668.1215871525963-- From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 15:29:11 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0FA31065677 for ; Sat, 12 Jul 2008 15:29:11 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id 74D478FC17 for ; Sat, 12 Jul 2008 15:29:11 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 32926 invoked by uid 89); 12 Jul 2008 15:32:06 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 12 Jul 2008 15:32:06 -0000 Message-ID: <4878CDCD.5060700@ibctech.ca> Date: Sat, 12 Jul 2008 11:29:17 -0400 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Brooks Davis References: <4877A343.2010602@ibctech.ca> <20080711182430.GA76378@keltia.freenix.fr> <200807121043.10473.duncan.young@pobox.com> <20080712045508.GA28756@lor.one-eyed-alien.net> In-Reply-To: <20080712045508.GA28756@lor.one-eyed-alien.net> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Duncan Young , freebsd-current@freebsd.org Subject: Re: Boot from ZFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 15:29:11 -0000 Brooks Davis wrote: > On Sat, Jul 12, 2008 at 10:43:09AM +1000, Duncan Young wrote: >> Be carefull, I've just had a 6 disk raidz array die. Complete failure which >> required restore from backup (the controler card which had access to 4 of the >> disks, lost one disk, then a second (at which point the machine paniced, Upon >> reboot the raidz array was useless (Metadata corrupted)). I'm also getting >> reasonably frequent machine lockups (panics) in the zfs code. I'm going to >> start collecting crash dumps see if anyone can help in the next week or two. > > If you look at the research on disk corruption and failure modes both > in recent proceeding of FAST and the latest issue of ;LOGIN: it's clear > that any RAID-like scheme that does not tolerate double faults is likely > to fail. In theory, zfs should tolerate certain classes of faults > better than some other technologies, but can't deal with full disk > double faults unless you use raidz2. Going back to my initial question (ie: subject), I've implemented the box in such a way that I boot via USB disk that contains only the /boot partition. This allows me to use all four entire disks in my ZFS pool instead of creating a UFS slice on one of them first. It then mounts / via ZFS and the system takes over from there. This box IS a backup box...in the sense of convenience. We still have off-site backup, this is just for quick retrieval of information if the need arises. If this box fails, We build a new one. That said, I did use raidz and sacrificed the equivalent of one drive. I did some testing (pop out a drive, reboot, etc) and it works very well. I do like the raidz2 idea, and when my needs justify adding more disks, I'll double the space and use the double protection. > Regardless of the technology, backups are essential. If you actually value > your data, off-site backups are essential. I fully agree with this statement. I've also been a long time believer that a backup is only as good as the time and difficulty level it takes to restore from it. Steve From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 16:53:06 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3030E1065676 for ; Sat, 12 Jul 2008 16:53:06 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 992238FC14 for ; Sat, 12 Jul 2008 16:53:05 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.2/8.14.2) with ESMTP id m6CGr4xJ036934 for ; Sat, 12 Jul 2008 20:53:04 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sat, 12 Jul 2008 20:53:04 +0400 (MSD) From: Dmitry Morozovsky To: current@FreeBSD.org Message-ID: <20080712204239.I58331@woozle.rinet.ru> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (woozle.rinet.ru [0.0.0.0]); Sat, 12 Jul 2008 20:53:04 +0400 (MSD) Cc: Subject: A bit of offtopic: msdosfs recovery tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 16:53:06 -0000 Dear colleagues, I have CF card which failed somewhere very close to the beginning; I did copy by recoverdisk, and can find start of at least one of FAT copies (though can't be sure of its consistency); I can't find root directory yet, neither subdirs. So - it there any tool to automate/speed up such a process? Thanks in advance. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 20:47:33 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2DB71065673; Sat, 12 Jul 2008 20:47:33 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.freebsd.org (Postfix) with ESMTP id 4C67F8FC16; Sat, 12 Jul 2008 20:47:33 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=Wa_Jn9kyDXQA:10 a=Ufi7cdQaAv4A:10 a=rzYPlMw5AAAA:8 a=pgK9qUdLsLP84TaCG60A:9 a=Zo1xdcZhnaPr56tGLNx-VlyeoLwA:4 a=LY0hPdMaydYA:10 Received: from [193.217.167.134] (account mc467741@c2i.net HELO [10.0.0.249]) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 983894255; Sat, 12 Jul 2008 22:47:31 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sat, 12 Jul 2008 22:49:01 +0200 User-Agent: KMail/1.9.7 References: <20080712204239.I58331@woozle.rinet.ru> In-Reply-To: <20080712204239.I58331@woozle.rinet.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807122249.03951.hselasky@c2i.net> Cc: Dmitry Morozovsky , current@freebsd.org Subject: Re: A bit of offtopic: msdosfs recovery tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 20:47:34 -0000 On Saturday 12 July 2008, Dmitry Morozovsky wrote: > Dear colleagues, > > I have CF card which failed somewhere very close to the beginning; I did > copy by recoverdisk, and can find start of at least one of FAT copies > (though can't be sure of its consistency); I can't find root directory yet, > neither subdirs. > > So - it there any tool to automate/speed up such a process? > Hi, You are fortunately not the first one into that water ;-) http://www.cgsecurity.org/wiki/PhotoRec We should have this in ports. It is a pretty good utility! If the program crashes, just remove the format scanners that are crashing from the build and run the scan again. --HPS From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 20:47:33 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2DB71065673; Sat, 12 Jul 2008 20:47:33 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.freebsd.org (Postfix) with ESMTP id 4C67F8FC16; Sat, 12 Jul 2008 20:47:33 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=Wa_Jn9kyDXQA:10 a=Ufi7cdQaAv4A:10 a=rzYPlMw5AAAA:8 a=pgK9qUdLsLP84TaCG60A:9 a=Zo1xdcZhnaPr56tGLNx-VlyeoLwA:4 a=LY0hPdMaydYA:10 Received: from [193.217.167.134] (account mc467741@c2i.net HELO [10.0.0.249]) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.4b) with ESMTPA id 983894255; Sat, 12 Jul 2008 22:47:31 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Sat, 12 Jul 2008 22:49:01 +0200 User-Agent: KMail/1.9.7 References: <20080712204239.I58331@woozle.rinet.ru> In-Reply-To: <20080712204239.I58331@woozle.rinet.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807122249.03951.hselasky@c2i.net> Cc: Dmitry Morozovsky , current@freebsd.org Subject: Re: A bit of offtopic: msdosfs recovery tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 20:47:34 -0000 On Saturday 12 July 2008, Dmitry Morozovsky wrote: > Dear colleagues, > > I have CF card which failed somewhere very close to the beginning; I did > copy by recoverdisk, and can find start of at least one of FAT copies > (though can't be sure of its consistency); I can't find root directory yet, > neither subdirs. > > So - it there any tool to automate/speed up such a process? > Hi, You are fortunately not the first one into that water ;-) http://www.cgsecurity.org/wiki/PhotoRec We should have this in ports. It is a pretty good utility! If the program crashes, just remove the format scanners that are crashing from the build and run the scan again. --HPS From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 21:47:41 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97C4D1065670 for ; Sat, 12 Jul 2008 21:47:41 +0000 (UTC) (envelope-from me@janh.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.freebsd.org (Postfix) with ESMTP id 1961F8FC18 for ; Sat, 12 Jul 2008 21:47:41 +0000 (UTC) (envelope-from me@janh.de) Received: from janh.freebsd (f054098089.adsl.alicedsl.de [78.54.98.89]) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis) id 0MKxQS-1KHmji17zv-0001iO; Sat, 12 Jul 2008 23:34:34 +0200 Message-ID: <4879236B.2030902@janh.de> Date: Sat, 12 Jul 2008 23:34:35 +0200 From: Jan Henrik Sylvester User-Agent: Thunderbird 2.0.0.14 (X11/20080615) MIME-Version: 1.0 To: current-list freebsd References: 20080712204239.I58331@woozle.rinet.ru Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19tAL57suH2xvR8lNCdDx20DtKWGmtKyEcmNTC 5zMy8afgCdMRLEMTK2vOnkLpqEKzgpeskDtI8NpuUh1pdm4THJ AvwYFJpwbfeJatj0TwLsw== X-Mailman-Approved-At: Sat, 12 Jul 2008 23:07:05 +0000 Cc: Dmitry Morozovsky Subject: Re: A bit of offtopic: msdosfs recovery tool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 21:47:41 -0000 Dmitry wrote: > I have CF card which failed somewhere very close to the beginning; I > did copy by recoverdisk, and can find start of at least one of FAT > copies (though can't be sure of its consistency); I can't find root ve > directory yet, neither subdirs. Have you tried sysutils/fatback? I used it once to undelete with intact FAT, but I guess it can do without, too. Jan Henrik From owner-freebsd-current@FreeBSD.ORG Sat Jul 12 22:35:07 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58939106566C for ; Sat, 12 Jul 2008 22:35:07 +0000 (UTC) (envelope-from diizzyy@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id DEFD98FC15 for ; Sat, 12 Jul 2008 22:35:06 +0000 (UTC) (envelope-from diizzyy@gmail.com) Received: by ug-out-1314.google.com with SMTP id q2so105670uge.37 for ; Sat, 12 Jul 2008 15:35:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=2eVKeRYavNqDSLmm2wqg/sfjCo6gGK6gT3WDqbikeuQ=; b=ia9vMT3kGidiI++qrF1l4dN/us7/Q2H5tIl7NXKNo8XFNdcWXSy4D7tTwQ92GtMaAY l6IaF4PKOWnWVlo5DpuQtl4es0z7raLseXQPMxCGfb4GNotiiiuBudTHEoTR9nwfnH0c 0MZAGO5eerkUAbjQRCOKW2JsfRSygardJAB40= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=nFvMtbc9r7Say+x1GISKYIZim0WcZrKf7pKtUNOBdZn3P14kv+7FDoDx8vR9HB/fBC VgJoxPUU4w8r5hWEC5QwMy4kTkin/9yPLlf+ZrkDMddVT/DgQt95w5VH5mwyTyxo5w1E ziESJYhoF85Msj+k741aQzZkrLJwHTX2pHtL4= Received: by 10.67.116.7 with SMTP id t7mr544343ugm.64.1215900572399; Sat, 12 Jul 2008 15:09:32 -0700 (PDT) Received: from ?83.178.151.135? ( [83.178.151.135]) by mx.google.com with ESMTPS id 31sm2442443ugg.36.2008.07.12.15.09.28 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 12 Jul 2008 15:09:31 -0700 (PDT) Message-ID: <48792B97.9090201@gmail.com> Date: Sun, 13 Jul 2008 00:09:27 +0200 From: Daniel Engberg User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 12 Jul 2008 23:19:58 +0000 Subject: Re: Sysinstall is still inadequate after all of these years / sorry I started flame war X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2008 22:35:07 -0000 Hi, While the main issue/topic addresses sysinstall's inability to 'nicely' interact with installation of packages and then turns into generic installer issues/thoughts etc I would like to bring up to those who've missed that there is ongoing work with a new installer. Last year(?) Ivan Voras made some research of current "frameworks/installers" to evalute and to get some ideas of what you would want from an installer and this turned into a SoC project founded by Google. While I'm not really sure what it does/doesn't I think it looks like a good solution in general. This is still WIP so it might be worth looking in and contribute. http://wiki.freebsd.org/finstall/Amnesiac - Screens http://ivoras.sharanet.org/stuff/connectserver.png - Remote install (WIP?) A bit late but oh well ;-) //Daniel