From owner-freebsd-stable@FreeBSD.ORG Sun Aug 28 09:27:42 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12DA616A41F for ; Sun, 28 Aug 2005 09:27:42 +0000 (GMT) (envelope-from b_bonev@mail.orbitel.bg) Received: from smtp.orbitel.bg (smtp.orbitel.bg [195.24.32.22]) by mx1.FreeBSD.org (Postfix) with SMTP id 6C17843D48 for ; Sun, 28 Aug 2005 09:27:41 +0000 (GMT) (envelope-from b_bonev@mail.orbitel.bg) Received: (qmail 21137 invoked from network); 28 Aug 2005 09:27:39 -0000 Received: from unknown (HELO localhost) (10.0.0.4) by smtp.orbitel.bg with SMTP; 28 Aug 2005 09:27:39 -0000 Received: from smtp.orbitel.bg ([10.0.0.3]) by localhost (sof-rv2.orbitel.bg [10.0.0.4]) (amavisd-new, port 10024) with ESMTP id 12889-15 for ; Sun, 28 Aug 2005 12:27:39 +0300 (EEST) Received: from ibb.orac.bg (unknown [83.228.34.40]) by smtp.orbitel.bg (Postfix) with ESMTP id ED33AA5CAF1 for ; Sun, 28 Aug 2005 12:27:38 +0300 (EEST) Date: Sun, 28 Aug 2005 12:27:37 +0300 From: "Ivailo Bonev" To: freebsd-stable@freebsd.org Organization: Orac Ltd. Content-Type: text/plain; format=flowed; delsp=yes; charset=windows-1251 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: User-Agent: Opera M2/8.02 (FreeBSD, build 1272) X-Virus-Scanned: by amavisd-new at orbitel.bg Subject: Difference btw installing 5.4 Release in Safe mode and Normal? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 09:27:42 -0000 What is the difference between installing 5.4 Release in Safe mode and Normal installation? Tried installing Normal installation on laptop paniced, but with Safe mode is ok? From owner-freebsd-stable@FreeBSD.ORG Sun Aug 28 11:58:11 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33E1316A41F for ; Sun, 28 Aug 2005 11:58:11 +0000 (GMT) (envelope-from haavard.molland@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEDB443D46 for ; Sun, 28 Aug 2005 11:58:08 +0000 (GMT) (envelope-from haavard.molland@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so853480rne for ; Sun, 28 Aug 2005 04:58:08 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=cytD//DgIT4jrAafMNAVlybPNI1hC2wFeOpfwGC/ha8Pifz4rEGaadAyhfB4Xs93NB4CF9D87/BG4Pu0MdBi8Ae4tRiBA4vpAJ0SnMHy/3nyh62BGZipSyR/1yInNj5Adz8v5M92fJA/lgW/3TXlnCOvtoyeVHelduzcBQyjAkE= Received: by 10.38.89.36 with SMTP id m36mr1310223rnb; Sun, 28 Aug 2005 04:41:36 -0700 (PDT) Received: by 10.38.88.31 with HTTP; Sun, 28 Aug 2005 04:41:04 -0700 (PDT) Message-ID: Date: Sun, 28 Aug 2005 13:41:04 +0200 From: =?ISO-8859-1?Q?H=E5vard_Molland?= To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Microsoft Standard Wireless Optical Mouse usb X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 11:58:11 -0000 Hello saw you had written this mail on the freebsd mailinglist.. I have a Microsoft wireless optical mouse and a keyboard, the keyboard works just fine but I cant get the mouse to work could you help me? how did you get it to work? H=E5vard Molland Hello, =20 I have had a really hard time with this Microsoft Standard Wireless Optical Mouse on usb. Didn't work no matter what I tried as it seemed to have a different-than-standard data placement in the data frame. In the end I had to make some changes (ugly hacks) to ums.c and now it work= s fine (but only with this mouse!). If someone is in (desperate) need for it or wants an advice, maybe I can help.=20 =20 Regards, Daniel From owner-freebsd-stable@FreeBSD.ORG Sun Aug 28 12:31:55 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5D5E16A41F for ; Sun, 28 Aug 2005 12:31:55 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam.ru (gw.ipt.ru [80.253.10.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ECB143D46 for ; Sun, 28 Aug 2005 12:31:55 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam by bsam.ru with local (Exim 4.30; FreeBSD) id 1E9MIl-000IHu-Kt; Sun, 28 Aug 2005 16:30:19 +0400 To: freebsd-stable@FreeBSD.org From: Boris Samorodov Date: Sun, 28 Aug 2005 16:30:19 +0400 Message-ID: <55023220@srv.sem.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: "Boris B. Samorodov" Cc: Subject: 6.0 and -O2 option X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 12:31:55 -0000 Hi! As for 5.x notes about -O2 (libalias, gcc) were removed at revision 1.229.2.7 of /usr/src/share/examples/etc/make.conf. But for 6.0-BETA3 we do have these warnings. Should they be removed as for 5.x? Is it safe to use -O2 to build/install kernel, world, ports fro 6.0? WBR -- bsam From owner-freebsd-stable@FreeBSD.ORG Sun Aug 28 13:16:15 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4939E16A41F for ; Sun, 28 Aug 2005 13:16:15 +0000 (GMT) (envelope-from dom@helenmarks.co.uk) Received: from mail.helenmarks.co.uk (mail.helenmarks.co.uk [82.68.196.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8E1843D45 for ; Sun, 28 Aug 2005 13:16:14 +0000 (GMT) (envelope-from dom@helenmarks.co.uk) Received: from localhost (localhost [127.0.0.1]) by mail.helenmarks.co.uk (Postfix) with ESMTP id 98F8E2710C02; Sun, 28 Aug 2005 14:16:13 +0100 (BST) Received: from mail.helenmarks.co.uk ([127.0.0.1]) by localhost (mail.helenmarks.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 74768-08; Sun, 28 Aug 2005 14:16:08 +0100 (BST) Received: by mail.helenmarks.co.uk (Postfix, from userid 80) id 6923A2710C01; Sun, 28 Aug 2005 14:16:08 +0100 (BST) Received: from wifi.helenmarks.co.uk ([192.168.15.10]) (SquirrelMail authenticated user dom) by www.helenmarks.co.uk with HTTP; Sun, 28 Aug 2005 14:16:08 +0100 (BST) Message-ID: <1490.192.168.15.10.1125234968.squirrel@www.helenmarks.co.uk> In-Reply-To: References: Date: Sun, 28 Aug 2005 14:16:08 +0100 (BST) From: "Dominic Marks" To: "Brian Doherty" User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: By ClamAV 0.85.1 Cc: freebsd-stable@freebsd.org Subject: Re: Dell Latitude D510 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 13:16:15 -0000 Brian Doherty wrote: > Hi all, > > I'm a bit of a newbie, with 5.x and hope someone can help me. :-) Here goes ... > I have a dell Latitude D510 with the mist recent BIOS installed. > I have win XP factory installed, boots fine. > I have tried installing the following on a partition: > > 5.4 FreeBSD > BTX Halted and goes no further straight after the install option screen, > ie > 1 - FreeBSD, 2 - FreeBSD without ACPI Tried booting without ACPI? I have quite a few machines at work which do this, mostly old(ish) PII/PIII systems with low-quality motherboards. > 5.3 FreeBSD > Gets a little further, but drops out on a panic, while trying to load the > usb devices, I think > > 4.11 FreeBSD > Same as 5.3 > 4.10 FreeBSD > Same as 4.10 Try the 6.0 BETA3, it's not too scary, but you will want to recompile your kernel after you install (assuming it works) to get decent performance (hint: remove the debugging options). If you haven't done this don't worry, it isn't complicated and is well covered in the Handbook. If the USB problem comes back, you can still work around it, although it may be challenging for someone new to FreeBSD. However, you will learn quite a bit in the process! Assuming you have a spare machine lying around, or another FreeBSD box already, you can compile your own kernel, removing the USB bits and then modify the ISO image file replacing the stock kernel with your own one. This isn't actually as hard as it might sound :-) You can mount the ISO image (using mdconfig and mount_cd9660) then copy your USB-less kernel over the one on the CD, then burn a copy of the ISO file again and it will have your own special-purpose install CD (haven't tried this but I think it will work, the kernel on the CD is not 'special' as far as I know). If this all sounds far too complex for you, I can probably make you the CD described above as I have a D510 here (which I'm typing from) although it's not running FreeBSD and I won't be fully test the install (it's not really mine). Try the simpler options first, and if not, send the list another E-Mail and see what comes your way. > I did a google, looked in the handbook, but couldn't find anything that it > might be. > > Regards, > > Brian > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Cheers, -- Dominic Marks From owner-freebsd-stable@FreeBSD.ORG Sun Aug 28 13:34:05 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC76716A422 for ; Sun, 28 Aug 2005 13:34:05 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EAF343D48 for ; Sun, 28 Aug 2005 13:34:05 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 7D2915CC2; Sun, 28 Aug 2005 09:34:04 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 97077-02; Sun, 28 Aug 2005 09:34:03 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-79-217.ny325.east.verizon.net [68.161.79.217]) by pi.codefab.com (Postfix) with ESMTP id C1FBA5C46; Sun, 28 Aug 2005 09:34:02 -0400 (EDT) Message-ID: <4311BD5A.1030609@mac.com> Date: Sun, 28 Aug 2005 09:34:18 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD-Stable References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: Ivailo Bonev Subject: Re: Difference btw installing 5.4 Release in Safe mode and Normal? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 13:34:06 -0000 Ivailo Bonev wrote: > What is the difference between installing 5.4 Release in Safe mode and > Normal installation? > Tried installing Normal installation on laptop paniced, but with Safe > mode is ok? Safe mode disables ACPI/APM, it disables APIC and SMP, it slows down the hard drives and so forth from UltraDMA speeds to the safer PIO modes. It would help to report exactly what laptop you have, as well as the panic message, but if you can install in safe mode, you have a chance to update the system sources and build a kernel with various options to try and track down where the problem is. You should also make sure your laptop BIOS is completely up-to-date. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Sun Aug 28 13:53:20 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A20CC16A420 for ; Sun, 28 Aug 2005 13:53:20 +0000 (GMT) (envelope-from grafan@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEE6143D53 for ; Sun, 28 Aug 2005 13:53:19 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by xproxy.gmail.com with SMTP id i31so471397wxd for ; Sun, 28 Aug 2005 06:53:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Vl3jnOQNecmN8yKZT5N9AW/u7glRRodwyrwicVP0OBpNkKNRoP5px1aHWLdcZLftLrQ0RzIUM0pjnbJihsRymRHsebU6ZbEbqKqfsw9PUnIerBB3q2gZYnl/jQIoiun4CIoUl7WQyThpR+X53xYaU7nP2mUKsRRJ7s4nxw8iIms= Received: by 10.70.129.8 with SMTP id b8mr78615wxd; Sun, 28 Aug 2005 06:46:51 -0700 (PDT) Received: by 10.70.129.19 with HTTP; Sun, 28 Aug 2005 06:46:51 -0700 (PDT) Message-ID: <6eb82e05082806466960292@mail.gmail.com> Date: Sun, 28 Aug 2005 21:46:51 +0800 From: Rong-En Fan To: stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline Cc: Subject: got a panic on 5.4-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 13:53:20 -0000 SGksCgpJIGdvdCBhIHBhbmljIG9uIGFuIGkzODYgNS40LVNUQUJMRSBhcm91bmQgQXVnIDI4IHdp dGggU01QIGVuYWJsZWQuCkl0IGhhcyAyIHBoeXNpY2FsIENQVSB3aXRoIEhUVCBlbmFibGVkIChz bywgdG90YWwgNCBjcHVzKS4gClRoaXMgaXMgYSBORlMgc2VydmVyIG9ubHkgd2l0aCBleHRlcm5h bCBzY3NpIHJhaWQgYXR0YWNoZWQuCgpUaGUgY29uc29sZSBsb2csIGtnZGIgb3V0cHV0IGFuZCBz eXNjdGwuY29uZiBhcmUgYXMgYmVsb3cuCkknbGwga2VlcCB0aGlzIGNvcmUgYW5kIGlmIHNvbWVv bmUgaXMgaW50ZXJlc3RlZCwgSSBjYW4gc2VuZCBhbnkgb3RoZXIKaW5mb3JtYXRpb24gcmVxdWVz dGVkLgoKUmVnYXJkcywKUm9uZy1FbiBGYW4KCltzeXNjdGwuY29uZl0KbmV0LmxpbmsuZXRoZXIu aW5ldC5sb2dfYXJwX3dyb25nX2lmYWNlPTAKbmV0LmluZXQudGNwLnNlbmRzcGFjZT02NTUzNgpu ZXQuaW5ldC50Y3AucmVjdnNwYWNlPTY1NTM2Cm5ldC5pbmV0LnVkcC5yZWN2c3BhY2U9NjU1MzYK a2Vybi5pcGMuc29tYXhjb25uPTQwOTYKa2Vybi5tYXhmaWxlcz02NTUzNQprZXJuLmlwYy5zaG1t YXg9MTA0ODU3NjAwCmtlcm4uaXBjLnNobWFsbD0yNTYwMApuZXQuaW5ldC5pcC5yYW5kb21faWQ9 MQprZXJuLmNhbS5kYS5yZXRyeV9jb3VudD0yMAprZXJuLmNhbS5kYS5kZWZhdWx0X3RpbWVvdXQ9 MzAwCmtlcm4ubWF4dm5vZGVzPTEwMDAwMAp2ZnMucmVhZF9tYXg9MTYKCltjb25zb2xlIGxvZ10K RmF0YWwgdHJhcCAxMjogcGFnZSBmYXVsdCB3aGlsZSBpbiBrZXJuZWwgbW9kZQpjcHVpZCA9IDA7 IGFwaWMgaWQgPSAwMApmYXVsdCB2aXJ0dWFsIGFkZHJlc3MgICA9IDB4YwpmYXVsdCBjb2RlICAg ICAgICAgICAgICA9IHN1cGVydmlzb3IgcmVhZCwgcGFnZSBub3QgcHJlc2VudAppbnN0cnVjdGlv biBwb2ludGVyICAgICA9IDB4ODoweGMwNTFkNjJmCnN0YWNrIHBvaW50ZXIgICAgICAgICAgID0g MHgxMDoweGU3MDg4YTY0CmZyYW1lIHBvaW50ZXIgICAgICAgICAgID0gMHgxMDoweGU3MDg4YTk4 CmNvZGUgc2VnbWVudCAgICAgICAgICAgID0gYmFzZSAweDAsIGxpbWl0IDB4ZmZmZmYsIHR5cGUg MHgxYgogICAgICAgICAgICAgICAgICAgICAgICA9IERQTCAwLCBwcmVzIDEsIGRlZjMyIDEsIGdy YW4gMQpwcm9jZXNzb3IgZWZsYWdzICAgICAgICA9IGludGVycnVwdCBlbmFibGVkLCByZXN1bWUs IElPUEwgPSAwCmN1cnJlbnQgcHJvY2VzcyAgICAgICAgID0gNTIzIChuZnNkKQp0cmFwIG51bWJl ciAgICAgICAgICAgICA9IDEyCnBhbmljOiBwYWdlIGZhdWx0CmNwdWlkID0gMApib290KCkgY2Fs bGVkIG9uIGNwdSMwClVwdGltZTogMmg1OW01OXMKRHVtcGluZyAxMDIzIE1CCiAxNiAzMiA0OCA2 NCA4MCA5NiAxMTIgMTI4IDE0NCAxNjAgMTc2IDE5MiAyMDggMjI0IDI0MCAyNTYgMjcyIDI4OCAz MDQKMzIwIDMzNiAzNTIgMzY4IDM4NCA0MDAgNDE2IDQzMiA0NDggNDY0IDQ4MCA0OTYgNTEyIDUy OCA1NDQgNTYwIDU3Ngo1OTIgNjA4IDYyNCA2NDAgNjU2IDY3MiA2ODggNzA0IDcyMCA3MzYgNzUy IDc2OCA3ODQgODAwIDgxNiA4MzIgODQ4Cjg2NCA4ODAgODk2IDkxMiA5MjggOTQ0IDk2MCA5NzYg OTkyIDEwMDgKRHVtcCBjb21wbGV0ZQpBdXRvbWF0aWMgcmVib290IGluIDEgc2Vjb25kcyAtIHBy ZXNzIGEga2V5IG9uIHRoZSBjb25zb2xlIHRvIGFib3J0ClJlYm9vdGluZy4uLgpjcHVfcmVzZXQg Y2FsbGVkIG9uIGNwdSMwCmNwdV9yZXNldDogU3RvcHBpbmcgb3RoZXIgQ1BVcwoKW2tnZGIgb3V0 cHV0XQpVbnJlYWQgcG9ydGlvbiBvZiB0aGUga2VybmVsIG1lc3NhZ2UgYnVmZmVyOgpA77+977+9 P++/ve+/ve+/ve+/ve+/vSDvv73vv70K77+977+977+977+9RDDvv73vv73vv70i77+9cCfvv71A 77+977+977+9MO+/ve+/ve+/ve+/ve+/vTDvv73vv71wJwoKIzAgIGRvYWR1bXAgKCkgYXQgcGNw dS5oOjE2MAoxNjAgICAgICAgICAgICAgX19hc20gX192b2xhdGlsZSgibW92bCAlJWZzOjAsJTAi IDogIj1yIiAodGQpKTsKKGtnZGIpIHVwCiMxICAweGMwNGUwMzg1IGluIGJvb3QgKGhvd3RvPTI2 MCkgYXQgL3Vzci9zcmMvc3lzL2tlcm4va2Vybl9zaHV0ZG93bi5jOjQxMAo0MTAgICAgICAgICAg ICAgICAgICAgICBkb2FkdW1wKCk7CihrZ2RiKQojMiAgMHhjMDRlMDczMyBpbiBwYW5pYyAoZm10 PTB4YzA2NWQwODUgIiVzIikgYXQKL3Vzci9zcmMvc3lzL2tlcm4va2Vybl9zaHV0ZG93bi5jOjU2 Ngo1NjYgICAgICAgICAgICAgYm9vdChib290b3B0KTsKKGtnZGIpCiMzICAweGMwNjQ1MDNkIGlu IHRyYXBfZmF0YWwgKGZyYW1lPTB4ZTcwODhhMjQsIGV2YT0wKSBhdAovdXNyL3NyYy9zeXMvaTM4 Ni9pMzg2L3RyYXAuYzo4MTcKODE3ICAgICAgICAgICAgICAgICAgICAgcGFuaWMoIiVzIiwgdHJh cF9tc2dbdHlwZV0pOwooa2dkYikKIzQgIDB4YzA2NDRkMzQgaW4gdHJhcF9wZmF1bHQgKGZyYW1l PTB4ZTcwODhhMjQsIHVzZXJtb2RlPTAsIGV2YT0xMikKICAgIGF0IC91c3Ivc3JjL3N5cy9pMzg2 L2kzODYvdHJhcC5jOjczNQo3MzUgICAgICAgICAgICAgICAgICAgICB0cmFwX2ZhdGFsKGZyYW1l LCBldmEpOwooa2dkYikKIzUgIDB4YzA2NDQ5MTkgaW4gdHJhcCAoZnJhbWU9CiAgICAgIHt0Zl9m cyA9IC0xMDM4NjE0NTA0LCB0Zl9lcyA9IC00MTg5MDYwOTYsIHRmX2RzID0gMTYsIHRmX2VkaSA9 CjE0ODAsIHRmX2VzaSA9IDAsIHRmX2VicCA9IC00MTg4NzA2MzIsIHRmX2lzcCA9IC00MTg4NzA3 MDQsIHRmX2VieCA9Ci0xMDM5Mjk5MjY0LCB0Zl9lZHggPSAyMCwgdGZfZWN4ID0gMTUwMCwgdGZf ZWF4ID0gLTEwMzkyOTkzMjgsCnRmX3RyYXBubyA9IDEyLCB0Zl9lcnIgPSAwLCB0Zl9laXAgPSAt MTA2ODM3ODU3NywgdGZfY3MgPSA4LCB0Zl9lZmxhZ3MKPSA2NjA1MCwgdGZfZXNwID0gLTEwMzky OTkzMjgsIHRmX3NzID0gMTQ4MH0pIGF0Ci91c3Ivc3JjL3N5cy9pMzg2L2kzODYvdHJhcC5jOjQy NQo0MjUgICAgICAgICAgICAgICAgICAgICAgICAgICAgICh2b2lkKSB0cmFwX3BmYXVsdCgmZnJh bWUsIEZBTFNFLCBldmEpOwooa2dkYikKIzYgIDB4YzA2MzEyMmEgaW4gY2FsbHRyYXAgKCkgYXQg L3Vzci9zcmMvc3lzL2kzODYvaTM4Ni9leGNlcHRpb24uczoxNDAKMTQwICAgICAgICAgICAgIGNh bGwgICAgdHJhcApDdXJyZW50IGxhbmd1YWdlOiAgYXV0bzsgY3VycmVudGx5IGFzbQooa2dkYikK IzcgIDB4YzIxODAwMTggaW4gPz8gKCkKKGtnZGIpCiM4ICAweGU3MDgwMDEwIGluID8/ICgpCihr Z2RiKQojOSAgMHgwMDAwMDAxMCBpbiA/PyAoKQooa2dkYikKIzEwIDB4MDAwMDA1YzggaW4gPz8g KCkKKGtnZGIpCiMxMSAweDAwMDAwMDAwIGluID8/ICgpCihrZ2RiKQojMTIgMHhlNzA4OGE5OCBp biA/PyAoKQooa2dkYikKIzEzIDB4ZTcwODhhNTAgaW4gPz8gKCkKKGtnZGIpCiMxNCAweGMyMGQ4 ZDQwIGluID8/ICgpCihrZ2RiKQojMTUgMHgwMDAwMDAxNCBpbiA/PyAoKQooa2dkYikKIzE2IDB4 MDAwMDA1ZGMgaW4gPz8gKCkKKGtnZGIpCiMxNyAweGMyMGQ4ZDAwIGluID8/ICgpCihrZ2RiKQoj MTggMHgwMDAwMDAwYyBpbiA/PyAoKQooa2dkYikKIzE5IDB4MDAwMDAwMDAgaW4gPz8gKCkKKGtn ZGIpCiMyMCAweGMwNTFkNjJmIGluIG1fY29weW0gKG09MHgwLCBvZmYwPTE1MDAsIGxlbj0xNDgw LCB3YWl0PTEpCiAgICBhdCAvdXNyL3NyYy9zeXMva2Vybi91aXBjX21idWYuYzozODkKMzg5ICAg ICAgICAgICAgICAgICAgICAgbSA9IG0tPm1fbmV4dDsKQ3VycmVudCBsYW5ndWFnZTogIGF1dG87 IGN1cnJlbnRseSBjCihrZ2RiKQojMjEgMHhjMDU3NjgzNSBpbiBpcF9mcmFnbWVudCAoaXA9MHhj MjBkOGRlNCwgbV9mcmFnPTB4ZTcwODhiNDgsCm10dT0tMTAzOTI5OTI2NCwKICAgIGlmX2h3YXNz aXN0X2ZsYWdzPTYsIHN3X2NzdW09MSkgYXQgL3Vzci9zcmMvc3lzL25ldGluZXQvaXBfb3V0cHV0 LmM6OTY3Cjk2NyAgICAgICAgICAgICAgICAgICAgIG0tPm1fbmV4dCA9IG1fY29weShtMCwgb2Zm LCBsZW4pOwooa2dkYikKIzIyIDB4YzA1NzY0YTYgaW4gaXBfb3V0cHV0IChtPTB4YzIwZDhkMDAs IG9wdD0weGMyMGQ4ZGU0LApybz0weGU3MDg4YjE0LCBmbGFncz0wLCBpbW89MHgwLAogICAgaW5w PTB4YzI0MzE3YmMpIGF0IC91c3Ivc3JjL3N5cy9uZXRpbmV0L2lwX291dHB1dC5jOjc5Ngo3OTYg ICAgICAgICAgICAgZXJyb3IgPSBpcF9mcmFnbWVudChpcCwgJm0sIGlmcC0+aWZfbXR1LAppZnAt PmlmX2h3YXNzaXN0LCBzd19jc3VtKTsKKGtnZGIpCiMyMyAweGMwNTg5OTU0IGluIHVkcF9vdXRw dXQgKGlucD0weGMyNDMxN2JjLCBtPTB4YzIwZDhkMDAsCmFkZHI9MHhjMzZmZTZkMCwgY29udHJv bD0weDAsCiAgICB0ZD0weGMyNDNlYTgwKSBhdCAvdXNyL3NyYy9zeXMvbmV0aW5ldC91ZHBfdXNy cmVxLmM6ODcwCjg3MCAgICAgICAgICAgICBlcnJvciA9IGlwX291dHB1dChtLCBpbnAtPmlucF9v cHRpb25zLCBOVUxMLCBpcGZsYWdzLAooa2dkYikKIzI0IDB4YzA1OGE1YjIgaW4gdWRwX3NlbmQg KHNvPTB4MCwgZmxhZ3M9MCwgbT0weDAsIGFkZHI9MHgwLApjb250cm9sPTB4MCwgdGQ9MHgwKQog ICAgYXQgL3Vzci9zcmMvc3lzL25ldGluZXQvdWRwX3VzcnJlcS5jOjEwNDcKMTA0NyAgICAgICAg ICAgIHJldHVybiB1ZHBfb3V0cHV0KGlucCwgbSwgYWRkciwgY29udHJvbCwgdGQpOwooa2dkYikK IzI1IDB4YzA1MjBhYTYgaW4gc29zZW5kIChzbz0weGMyNDQzMTQ0LCBhZGRyPTB4YzM2ZmU2ZDAs IHVpbz0weDAsCnRvcD0weGM1Yjg3YjAwLAogICAgY29udHJvbD0weDAsIGZsYWdzPTAsIHRkPTB4 YzI0M2VhODApIGF0IC91c3Ivc3JjL3N5cy9rZXJuL3VpcGNfc29ja2V0LmM6ODM1CjgzNSAgICAg ICAgICAgICAgICAgICAgICAgICBlcnJvciA9ICgqc28tPnNvX3Byb3RvLT5wcl91c3JyZXFzLT5w cnVfc2VuZCkoc28sCihrZ2RiKQojMjYgMHhjMDVjMDlmNCBpbiBuZnNydl9zZW5kIChzbz0weGMy NDQzMTQ0LCBuYW09MHhjMzZmZTZkMCwgdG9wPTB4MCkKYXQgcGNwdS5oOjE1NwoxNTcgICAgIHsK KGtnZGIpCiMyNyAweGMwNWMzYjVhIGluIG5mc3N2Y19uZnNkICh0ZD0weDApIGF0Ci91c3Ivc3Jj L3N5cy9uZnNzZXJ2ZXIvbmZzX3N5c2NhbGxzLmM6NTA5CjUwOSAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgIGVycm9yID0gbmZzcnZfc2VuZChzbHAtPm5zX3NvLApuZC0+bmRfbmFtMiwg bSk7CihrZ2RiKQojMjggMHhjMDVjMmY4MyBpbiBuZnNzdmMgKHRkPTB4YzI0M2VhODAsIHVhcD0w eGU3MDg4ZDA0KQogICAgYXQgL3Vzci9zcmMvc3lzL25mc3NlcnZlci9uZnNfc3lzY2FsbHMuYzox ODEKMTgxICAgICAgICAgICAgICAgICAgICAgZXJyb3IgPSBuZnNzdmNfbmZzZCh0ZCk7CihrZ2Ri KQojMjkgMHhjMDY0NTNlZiBpbiBzeXNjYWxsIChmcmFtZT0KICAgICAge3RmX2ZzID0gNDcsIHRm X2VzID0gNDcsIHRmX2RzID0gNDcsIHRmX2VkaSA9IDAsIHRmX2VzaSA9IDAsCnRmX2VicCA9IC0x MDc3OTQxNDE2LCB0Zl9pc3AgPSAtNDE4ODY5OTE2LCB0Zl9lYnggPSAwLCB0Zl9lZHggPQoxNzQ2 MjMyODU2LCB0Zl9lY3ggPSAyNSwgdGZfZWF4ID0gMTU1LCB0Zl90cmFwbm8gPSAxMiwgdGZfZXJy ID0gMiwKdGZfZWlwID0gMTc0NTY5MjM1OSwgdGZfY3MgPSAzMSwgdGZfZWZsYWdzID0gNjQyLCB0 Zl9lc3AgPQotMTA3Nzk0MTQ0NCwgdGZfc3MgPSA0N30pIGF0IC91c3Ivc3JjL3N5cy9pMzg2L2kz ODYvdHJhcC5jOjEwMDkKMTAwOSAgICAgICAgICAgICAgICAgICAgZXJyb3IgPSAoKmNhbGxwLT5z eV9jYWxsKSh0ZCwgYXJncyk7CihrZ2RiKQojMzAgMHhjMDYzMTI3ZiBpbiBYaW50MHg4MF9zeXNj YWxsICgpIGF0IC91c3Ivc3JjL3N5cy9pMzg2L2kzODYvZXhjZXB0aW9uLnM6MjAxCjIwMSAgICAg ICAgICAgICBjYWxsICAgIHN5c2NhbGwKQ3VycmVudCBsYW5ndWFnZTogIGF1dG87IGN1cnJlbnRs eSBhc20KKGtnZGIpCiMzMSAweDAwMDAwMDJmIGluID8/ICgpCihrZ2RiKQojMzIgMHgwMDAwMDAy ZiBpbiA/PyAoKQooa2dkYikKIzMzIDB4MDAwMDAwMmYgaW4gPz8gKCkKKGtnZGIpCiMzNCAweDAw MDAwMDAwIGluID8/ICgpCihrZ2RiKQojMzUgMHgwMDAwMDAwMCBpbiA/PyAoKQooa2dkYikKIzM2 IDB4YmZiZmViNTggaW4gPz8gKCkKKGtnZGIpCiMzNyAweGU3MDg4ZDY0IGluID8/ICgpCihrZ2Ri KQojMzggMHgwMDAwMDAwMCBpbiA/PyAoKQooa2dkYikKIzM5IDB4NjgxNTY2MTggaW4gPz8gKCkK KGtnZGIpCiM0MCAweDAwMDAwMDE5IGluID8/ICgpCihrZ2RiKQojNDEgMHgwMDAwMDA5YiBpbiA/ PyAoKQooa2dkYikKIzQyIDB4MDAwMDAwMGMgaW4gPz8gKCkKKGtnZGIpCiM0MyAweDAwMDAwMDAy IGluID8/ICgpCihrZ2RiKQojNDQgMHg2ODBkMjZjNyBpbiA/PyAoKQooa2dkYikKIzQ1IDB4MDAw MDAwMWYgaW4gPz8gKCkKKGtnZGIpCiM0NiAweDAwMDAwMjgyIGluID8/ICgpCihrZ2RiKQojNDcg MHhiZmJmZWIzYyBpbiA/PyAoKQooa2dkYikKIzQ4IDB4MDAwMDAwMmYgaW4gPz8gKCkKKGtnZGIp CiM0OSAweDAwMDAwMDAwIGluID8/ICgpCihrZ2RiKQojNTAgMHgwMDAwMDAwMCBpbiA/PyAoKQoo a2dkYikKIzUxIDB4MDAwMDAwMDAgaW4gPz8gKCkKKGtnZGIpCiM1MiAweDAwMDAwMDAwIGluID8/ ICgpCihrZ2RiKQojNTMgMHgzMWVmZDAwMCBpbiA/PyAoKQooa2dkYikKIzU0IDB4YzI0NDE1NGMg aW4gPz8gKCkKKGtnZGIpCiM1NSAweGMyNDNlYTgwIGluID8/ICgpCihrZ2RiKQojNTYgMHhlNzA4 OGI4OCBpbiA/PyAoKQooa2dkYikKIzU3IDB4ZTcwODhiNzAgaW4gPz8gKCkKKGtnZGIpCiM1OCAw eGMxZTk1NDgwIGluID8/ICgpCihrZ2RiKQojNTkgMHhjMDRmMzQ2MCBpbiBzY2hlZF9zd2l0Y2gg KHRkPTB4MCwgbmV3dGQ9MHgwLCBmbGFncz1DYW5ub3QgYWNjZXNzCm1lbW9yeSBhdCBhZGRyZXNz IDB4YmZiZmViNjgKKQogICAgYXQgL3Vzci9zcmMvc3lzL2tlcm4vc2NoZWRfNGJzZC5jOjg4MQo4 ODEgICAgICAgICAgICAgICAgICAgICBjcHVfc3dpdGNoKHRkLCBuZXd0ZCk7CkN1cnJlbnQgbGFu Z3VhZ2U6ICBhdXRvOyBjdXJyZW50bHkgYwooa2dkYikKUHJldmlvdXMgZnJhbWUgaW5uZXIgdG8g dGhpcyBmcmFtZSAoY29ycnVwdCBzdGFjaz8pCg== From owner-freebsd-stable@FreeBSD.ORG Sun Aug 28 14:26:35 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5120916A41F for ; Sun, 28 Aug 2005 14:26:35 +0000 (GMT) (envelope-from grafan@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF91243D45 for ; Sun, 28 Aug 2005 14:26:34 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by xproxy.gmail.com with SMTP id i31so473349wxd for ; Sun, 28 Aug 2005 07:26:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ysoxs1cR72gtECsFU98QHrf0+0rTsfXISMjyOMwupwp8bWHRRJbktKeeO6CnLlsFFzbv/otBORPgYBXiWzOwj82SSoMm6Dk+cWTqlJuczfYJsaOVhPsSi1pjMQsYt7ERIlAH1T99e5rwNuiAmzvwA3hauiL5y5/wAv373EIgH+w= Received: by 10.70.62.12 with SMTP id k12mr78931wxa; Sun, 28 Aug 2005 07:26:33 -0700 (PDT) Received: by 10.70.129.19 with HTTP; Sun, 28 Aug 2005 07:26:33 -0700 (PDT) Message-ID: <6eb82e050828072614654966@mail.gmail.com> Date: Sun, 28 Aug 2005 22:26:33 +0800 From: Rong-En Fan To: stable@freebsd.org In-Reply-To: <6eb82e05082806466960292@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <6eb82e05082806466960292@mail.gmail.com> Cc: Subject: Re: got a panic on 5.4-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 14:26:35 -0000 T24gOC8yOC8wNSwgUm9uZy1FbiBGYW4gPGdyYWZhbkBnbWFpbC5jb20+IHdyb3RlOgo+IEhpLAo+ IAo+IEkgZ290IGEgcGFuaWMgb24gYW4gaTM4NiA1LjQtU1RBQkxFIGFyb3VuZCBBdWcgMjggd2l0 aCBTTVAgZW5hYmxlZC4KPiBJdCBoYXMgMiBwaHlzaWNhbCBDUFUgd2l0aCBIVFQgZW5hYmxlZCAo c28sIHRvdGFsIDQgY3B1cykuCj4gVGhpcyBpcyBhIE5GUyBzZXJ2ZXIgb25seSB3aXRoIGV4dGVy bmFsIHNjc2kgcmFpZCBhdHRhY2hlZC4KPiAKPiBUaGUgY29uc29sZSBsb2csIGtnZGIgb3V0cHV0 IGFuZCBzeXNjdGwuY29uZiBhcmUgYXMgYmVsb3cuCj4gSSdsbCBrZWVwIHRoaXMgY29yZSBhbmQg aWYgc29tZW9uZSBpcyBpbnRlcmVzdGVkLCBJIGNhbiBzZW5kIGFueSBvdGhlcgo+IGluZm9ybWF0 aW9uIHJlcXVlc3RlZC4KCkkgaGF2ZSB0aGUgZm9sbG93aW5nIGluIG1ha2UuY29uZjoKQ1BVVFlQ RT89IHA0CkNGTEFHUz0gLU8gLXBpcGUKQ09QVEZMQUdTPSAtTyAtcGlwZQoKVGhlIGRpZmZlcmVu Y2UgYmV0d2VlbiBHRU5FUklDIGFuZCBteSBrZXJuZWwgaXMgaGVyZToKaHR0cDovL3d3dy5yYWZh bi5vcmcvRnJlZUJTRC9wYW5pYy9tX2NvcHltL2tlcm5lbC1kaWZmLWFnYWluc3QtR0VORVJJQy50 eHQKCkFuZCBJIGFsc28gbG9va2VkIGF0IHRoZSBkdW1wIGZpbGUsIGxvb2tzIGxpa2UgdGhhdCB3 aGVuIGNhbGxpbmcKbV9jb3B5bSgpLCBtLT5tX2xlbiBpcyAyMCwgb2ZmIGlzIDE1MDAsIG0tPm1f bmV4dCBpcyBOVUxMCkFmdGVyIGZpcnN0IGl0ZXJhdGlvbiwgbSBiZWNvbWVzIE5VTEwuLi4KCiMy MCAweGMwNTFkNjJmIGluIG1fY29weW0gKG09MHgwLCBvZmYwPTE1MDAsIGxlbj0xNDgwLCB3YWl0 PTEpCiAgICBhdCAvdXNyL3NyYy9zeXMva2Vybi91aXBjX21idWYuYzozODkKMzg5ICAgICAgICAg ICAgICAgICAgICAgbSA9IG0tPm1fbmV4dDsKKGtnZGIpIGwKMzg0ICAgICAgICAgICAgIHdoaWxl IChvZmYgPiAwKSB7CjM4NSAgICAgICAgICAgICAgICAgICAgIEtBU1NFUlQobSAhPSBOVUxMLCAo Im1fY29weW0sIG9mZnNldCA+IHNpemUgb2YKbWJ1ZiBjaGFpbiIpKTsKMzg2ICAgICAgICAgICAg ICAgICAgICAgaWYgKG9mZiA8IG0tPm1fbGVuKQozODcgICAgICAgICAgICAgICAgICAgICAgICAg ICAgIGJyZWFrOwozODggICAgICAgICAgICAgICAgICAgICBvZmYgLT0gbS0+bV9sZW47CjM4OSAg ICAgICAgICAgICAgICAgICAgIG0gPSBtLT5tX25leHQ7CjM5MCAgICAgICAgICAgICB9CjM5MSAg ICAgICAgICAgICBucCA9ICZ0b3A7CjM5MiAgICAgICAgICAgICB0b3AgPSAwOwozOTMgICAgICAg ICAgICAgd2hpbGUgKGxlbiA+IDApIHsKKGtnZGIpIHAgb2ZmCiQxNSA9IDE0ODAKKGtnZGIpIHVw CiMyMSAweGMwNTc2ODM1IGluIGlwX2ZyYWdtZW50IChpcD0weGMyMGQ4ZGU0LCBtX2ZyYWc9MHhl NzA4OGI0OCwKbXR1PS0xMDM5Mjk5MjY0LAogICAgaWZfaHdhc3Npc3RfZmxhZ3M9Niwgc3dfY3N1 bT0xKSBhdCAvdXNyL3NyYy9zeXMvbmV0aW5ldC9pcF9vdXRwdXQuYzo5NjcKOTY3ICAgICAgICAg ICAgICAgICAgICAgbS0+bV9uZXh0ID0gbV9jb3B5KG0wLCBvZmYsIGxlbik7CihrZ2RiKSBwIG9m ZgokOSA9IDE1MDAKKGtnZGIpIHAgbGVuCiQxMCA9IDE0ODAKKGtnZGIpIHAgbTAKJDExID0gKHN0 cnVjdCBtYnVmICopIDB4YzIwZDhkMDAKKGtnZGIpIHAgKm0wCiQxMiA9IHttX2hkciA9IHttaF9u ZXh0ID0gMHgwLCBtaF9uZXh0cGt0ID0gMHgwLCBtaF9kYXRhID0gMHhjMjBkOGQ0MAoiRSIsIG1o X2xlbiA9IDIwLAogICAgbWhfZmxhZ3MgPSAyMDUwLCBtaF90eXBlID0gMn0sIE1fZGF0ID0ge01I ID0ge01IX3BrdGhkciA9IHtyY3ZpZiA9CjB4MCwgbGVuID0gODM0OCwKICAgICAgICBoZWFkZXIg PSAweGM1YjI1MDEwLCBjc3VtX2ZsYWdzID0gMCwgY3N1bV9kYXRhID0gNiwgdGFncyA9CntzbGhf Zmlyc3QgPSAweDB9fSwKICAgICAgTUhfZGF0ID0ge01IX2V4dCA9IHsKICAgICAgICAgIGV4dF9i dWYgPSAweGMzM2FlMDAwICJva2VyPC9hPlxub25saW5lIGNhc2lub3MgPGEKaHJlZj1odHRwOi8v d3d3Lmx1Y2t5LTc3Ny1jYXNpbm9zLmNvbT5vbmxpbmUgY2FzaW5vczwvYT5cbnZpYWdyYSA8YQpo cmVmPWh0dHA6Ly93d3cuQUxMLVZJQUdSQS5JTkZPPnZpcO+/vSIsIGV4dF9mcmVlID0gMCwKICAg ICAgICAgIGV4dF9hcmdzID0gMHgwLCBleHRfc2l6ZSA9IDIwNDgsIHJlZl9jbnQgPSAweGRjMDUw MDQ1LApleHRfdHlwZSA9IDU0OTAyMTk2M30sCiAgICAgICAgTUhfZGF0YWJ1ZiA9CiJcMDAw77+9 Ou+/vVwwMDBcMDAwXDAwMFwwMDBcMDAwXDAwMFwwMDBcMDAwXDAwMFxiXDAwMFwwMDBFXDAwMFww MDXvv71cdmnvv70KQFwwICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgCjAyMe+/ve+/vVwy MTRwXDAzNjBcMjE0cFwwMzZcMDM0QFwwMjHvv73vv71cMjE0cFwwMzYwXDIxNHBcMDM2JVxiXDAw MVwwMDMKXDAwMHhV77+9bUpcMjA377+9XDAwMFwwMDBcMDAwXDAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgIDAwMSIsICdcMCcgPHJlcGVhdHMgMjMKdGltZXM+LCAiXDAwMlwwMDBcMDAwXDAw Me+/vVwwMDBcMDAwXDAwMFwwMDJcMDAwXDAwMHHvv71cMDAwXDAwMFwwMDHvv71cMDAwXDAKICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgIAogICAgICAgICAgICAgICAgCjAwMFwwMDBcMDAwXDAwMFwwMDBcMDAyXDAwMFww MDBcMDAwXDAwMFwwMDBcMDAwXDAwMFxiXDAwMFwwMDBcMDAwXDAwMFwwMDFcMDAxXDIxN1wwMDBc MDIxXDAwMFwwMDBcMDAwXDAwMFwwMDBcMDAwXDAwNFwwMzRcMDAwXDAwMFwwMDBcMDAwXDAwMFww MzFcMDI077+9Q1wwMjFt77+9XDAwMFwwMDBcMDAwXDAwMELvv71b77+9XDAwMFwwMDBcMAogICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgCiAgICAgICAgICAgICAgIAowMDBcMDAwQu+/vVvvv71cMDAwXDAwMFwwMDBcMDE2 XGZvXDIxMTdcMDAwXDAxNlxmXsy6XGJcMDAwRVwwMDBcMjM0Clx2aVwwMDBcMDAwQFwwMjHvv73v v71cMjE0cFwwMzYwXDIxNCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICA0cFwwMzZcMDM0 XGJcMDAxXDAwM++/vQpcMjEwTu+/vSJ9fSwKICAgIE1fZGF0YWJ1ZiA9ICJcMDAwXDAwMFwwMDBc MDAwXDIzNApcMDAwXDAwMFwwMjBQ77+977+9XDAwMFwwMDBcMDAwXDAwMFwwMDZcMDAwXDAwMFww MDBcMDAwXDAwMCAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgIDBcMDAwXDAwMFwwMDDv v70677+9XDAwMFwwMDBcMDAwXDAwMFwwMDBcMDAwXDAwMFwwMDBcMDAwXGJcMDAwXDAwMEVcMDAw XDAwNe+/vVx2ae+/vQpAXDAyMe+/ve+/vVwyMTRwXDAzNjAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgCjBcMjE0cFwwMzZcMDM0QFwwMjHvv73vv71cMjE0cFwwMzYwXDIxNHBcMDM2JVxiXDAw MVwwMDMKXDAwMHhV77+9bUpcMjA377+9XDAwMFwwMDBcMDAwXDAwMSIsICdcMCcgPHJlcCAgICAg ICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICBwZWF0cyAyMwp0aW1lcz4sICJcMDAyXDAwMFwwMDBc MDAx77+9XDAwMFwwMDBcMDAwXDAwMlwwMDBcMDAwce+/vVwwMDBcMDAwXDAwMe+/vVwwMDBcMDAw XDAwMFwwMDBcMDAwCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgIAowXDAwMFwwMDJcMDAw XDAwMFwwMDBcMDAwXDAwMFwwMDBcMDAwXGJcMDAwXDAwMFwwMDBcMDAwXDAwMVwwMDFcMjE3XDAw MFwwMjFcMDAwXDAwMFwwMDBcMDAwXDAwMFwwMDBcMDA0XDAzNFwwMDBcMDAwXDAwMFwwMDBcMDAw XDAzMVwwMjTvv71DXDAyMW3vv71cMDAwXDAwMFwwMDBcMDAwQu+/vVvvv71cMDAwXDAwMFwwMDBc MDAwQu+/vVvvv71cMDAwCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAwXDAwMFwwMDBcMDE2 XGZvXDIxMTdcMDAwXDAxNlxmXsy6XGJcMDAwRVwwMDBcMjM0Clx2aVwwMDBcMDAwQCIuLi59fQoo a2dkYikgbAo5NjIgICAgICAgICAgICAgICAgICAgICAgICAgICAgIGxlbiA9IGlwLT5pcF9sZW4g LSBvZmY7Cjk2MyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgbS0+bV9mbGFncyB8PSBNX0xB U1RGUkFHOwo5NjQgICAgICAgICAgICAgICAgICAgICB9IGVsc2UKOTY1ICAgICAgICAgICAgICAg ICAgICAgICAgICAgICBtaGlwLT5pcF9vZmYgfD0gSVBfTUY7Cjk2NiAgICAgICAgICAgICAgICAg ICAgIG1oaXAtPmlwX2xlbiA9IGh0b25zKCh1X3Nob3J0KShsZW4gKyBtaGxlbikpOwo5NjcgICAg ICAgICAgICAgICAgICAgICBtLT5tX25leHQgPSBtX2NvcHkobTAsIG9mZiwgbGVuKTsKOTY4ICAg ICAgICAgICAgICAgICAgICAgaWYgKG0tPm1fbmV4dCA9PSBOVUxMKSB7ICAgICAgICAvKiBjb3B5 IGZhaWxlZCAqLwo5NjkgICAgICAgICAgICAgICAgICAgICAgICAgICAgIG1fZnJlZShtKTsKOTcw ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBlcnJvciA9IEVOT0JVRlM7ICAgICAgICAvKiA/ Pz8gKi8KOTcxICAgICAgICAgICAgICAgICAgICAgICAgICAgICBpcHN0YXQuaXBzX29kcm9wcGVk Kys7CihrZ2RiKSB1cAojMjIgMHhjMDU3NjRhNiBpbiBpcF9vdXRwdXQgKG09MHhjMjBkOGQwMCwg b3B0PTB4YzIwZDhkZTQsCnJvPTB4ZTcwODhiMTQsIGZsYWdzPTAsIGltbz0weDAsCiAgICBpbnA9 MHhjMjQzMTdiYykgYXQgL3Vzci9zcmMvc3lzL25ldGluZXQvaXBfb3V0cHV0LmM6Nzk2Cjc5NiAg ICAgICAgICAgICBlcnJvciA9IGlwX2ZyYWdtZW50KGlwLCAmbSwgaWZwLT5pZl9tdHUsCmlmcC0+ aWZfaHdhc3Npc3QsIHN3X2NzdW0pOwooa2dkYikgcCBpcAokMTYgPSAoc3RydWN0IGlwICopIDB4 YzIwZDhkZTQKKGtnZGIpIHAgKmlwCiQxOSA9IHtpcF9obCA9IDUsIGlwX3YgPSA0LCBpcF90b3Mg PSAwICdcMCcsIGlwX2xlbiA9IDgzNDgsIGlwX2lkID0KMjY4OTEsIGlwX29mZiA9IDAsCiAgaXBf dHRsID0gNjQgJ0AnLCBpcF9wID0gMTcgJ1wwMjEnLCBpcF9zdW0gPSA1NDcxNiwgaXBfc3JjID0g e3NfYWRkcgo9IDgwNzMwMTI2MH0sCiAgaXBfZHN0ID0ge3NfYWRkciA9IDQ3MTc1Njk0MH19CgpU aGFua3MsClJvbmctRW4gZmFuCg== From owner-freebsd-stable@FreeBSD.ORG Sun Aug 28 15:09:56 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17DF016A41F for ; Sun, 28 Aug 2005 15:09:56 +0000 (GMT) (envelope-from rene@82-168-75-155-bbxl.xdsl.tiscali.nl) Received: from 82-168-75-155-bbxl.xdsl.tiscali.nl (82-168-75-155-bbxl.xdsl.tiscali.nl [82.168.75.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3693B43D45 for ; Sun, 28 Aug 2005 15:09:54 +0000 (GMT) (envelope-from rene@82-168-75-155-bbxl.xdsl.tiscali.nl) Received: from 82-168-75-155-bbxl.xdsl.tiscali.nl (localhost [127.0.0.1]) by 82-168-75-155-bbxl.xdsl.tiscali.nl (8.13.4/8.13.4) with ESMTP id j7SF9qQr066426; Sun, 28 Aug 2005 17:09:52 +0200 (CEST) (envelope-from rene@82-168-75-155-bbxl.xdsl.tiscali.nl) Received: (from rene@localhost) by 82-168-75-155-bbxl.xdsl.tiscali.nl (8.13.4/8.13.1/Submit) id j7SF9nsx066384; Sun, 28 Aug 2005 17:09:49 +0200 (CEST) (envelope-from rene) Date: Sun, 28 Aug 2005 17:09:47 +0200 From: Rene Ladan To: Boris Samorodov Message-ID: <20050828150947.GA58038@82-168-75-155-bbxl.xdsl.tiscali.nl> References: <55023220@srv.sem.ipt.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tKW2IUtsqtDRztdT" Content-Disposition: inline In-Reply-To: <55023220@srv.sem.ipt.ru> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: 6.0 and -O2 option X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 15:09:56 -0000 --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 28, 2005 at 04:30:19PM +0400, Boris Samorodov wrote: > Hi! >=20 >=20 > As for 5.x notes about -O2 (libalias, gcc) were removed at revision > 1.229.2.7 of /usr/src/share/examples/etc/make.conf. But for 6.0-BETA3 > we do have these warnings. Should they be removed as for 5.x? Is it > safe to use -O2 to build/install kernel, world, ports fro 6.0? >=20 Kernel and world seem to be ok with -O2, for ports it is not advised. I have this in /etc/make.conf: # -- all -- # =2Eif ${.CURDIR:M/usr/src*} CFLAGS=3D-O2 -pipe =2Eelse CFLAGS=3D-O -pipe =2Eendif CPUTYPE?=3Dpentium3 # -- ports -- # WITH_OPTIMIZED_CFLAGS=3Dyes So kernel and world (which source lives in /usr/src) are built with -O2, while anything else is built with -O. Some ports allow optimized compiler flags with WITH_OPTIMIZED_CFLAGS. > WBR > --=20 > bsam > Regards, Rene --=20 GPG fingerprint =3D 5FFA 3959 3377 C697 8428 24D0 BF3E F4A9 AE33 5DCC "It won't fit on the line." -- me, 2001 --tKW2IUtsqtDRztdT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDEdO6vz70qa4zXcwRAjYMAJ4lSkOoiilLtcT3roO0BWEmDp92DgCZAfUd 8InPasCty7FX7fjGGXsXGCk= =fcTP -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT-- From owner-freebsd-stable@FreeBSD.ORG Sun Aug 28 20:51:08 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 558C816A41F for ; Sun, 28 Aug 2005 20:51:08 +0000 (GMT) (envelope-from bfoz@bfoz.net) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC62B43D48 for ; Sun, 28 Aug 2005 20:51:07 +0000 (GMT) (envelope-from bfoz@bfoz.net) Received: from [192.168.0.5] (c-24-6-134-233.hsd1.ca.comcast.net[24.6.134.233]) by comcast.net (sccrmhc13) with ESMTP id <20050828205101013005d3ihe>; Sun, 28 Aug 2005 20:51:01 +0000 Message-ID: <431223B1.7050406@bfoz.net> Date: Sun, 28 Aug 2005 13:50:57 -0700 From: Brandon Fosdick User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050721) X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Odd rm behavior on 5.4-S with 3ware raid X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 20:51:08 -0000 The machine is an amd64 running 5.4-S with a 3ware 9500S-12 card. I wrote a test script to fill up the raid array with lots of files, and it did just that. Afterwards I did a 'rm *' to clean out the test files and naturally checked the results with ls. All the files were gone. For some reason, after waiting a few seconds, I did ls again. Some of the files had magically reappeared. After a few more seconds, more files were back. Its still happening as I type this. The drive lights are flashing wildly, but I kind of expected that. df is also showing that the array is filling back up. Any ideas? Is my computer possessed? From owner-freebsd-stable@FreeBSD.ORG Sun Aug 28 21:00:38 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6A3516A41F for ; Sun, 28 Aug 2005 21:00:38 +0000 (GMT) (envelope-from bfoz@bfoz.net) Received: from rwcrmhc12.comcast.net (rwcrmhc14.comcast.net [204.127.198.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BDB643D45 for ; Sun, 28 Aug 2005 21:00:38 +0000 (GMT) (envelope-from bfoz@bfoz.net) Received: from [192.168.0.5] (c-24-6-134-233.hsd1.ca.comcast.net[24.6.134.233]) by comcast.net (rwcrmhc14) with ESMTP id <2005082821003601400hdrgje>; Sun, 28 Aug 2005 21:00:36 +0000 Message-ID: <431225F3.6010408@bfoz.net> Date: Sun, 28 Aug 2005 14:00:35 -0700 From: Brandon Fosdick User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050721) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brandon Fosdick References: <431223B1.7050406@bfoz.net> In-Reply-To: <431223B1.7050406@bfoz.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: Odd rm behavior on 5.4-S with 3ware raid X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 21:00:38 -0000 heh...typed too fast. It appears that my array filling script didn't die when I told it to, or maybe an older instance was still running. Hard to say for sure, but it was still running and when I made room on the array it started filling it up. Just like it was supposed to. Sorry for the trouble. Nothing to see here...move along. :) Brandon Fosdick wrote: > The machine is an amd64 running 5.4-S with a 3ware 9500S-12 card. > > I wrote a test script to fill up the raid array with lots of files, and > it did just that. Afterwards I did a 'rm *' to clean out the test files > and naturally checked the results with ls. All the files were gone. For > some reason, after waiting a few seconds, I did ls again. Some of the > files had magically reappeared. After a few more seconds, more files > were back. Its still happening as I type this. The drive lights are > flashing wildly, but I kind of expected that. df is also showing that > the array is filling back up. > > Any ideas? Is my computer possessed? From owner-freebsd-stable@FreeBSD.ORG Sun Aug 28 21:50:22 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDC6416A41F for ; Sun, 28 Aug 2005 21:50:22 +0000 (GMT) (envelope-from bfoz@bfoz.net) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92EB643D48 for ; Sun, 28 Aug 2005 21:50:22 +0000 (GMT) (envelope-from bfoz@bfoz.net) Received: from [192.168.0.5] (c-24-6-134-233.hsd1.ca.comcast.net[24.6.134.233]) by comcast.net (sccrmhc12) with ESMTP id <2005082821501801200076rae>; Sun, 28 Aug 2005 21:50:18 +0000 Message-ID: <43123199.9000306@bfoz.net> Date: Sun, 28 Aug 2005 14:50:17 -0700 From: Brandon Fosdick User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050721) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <200508231131.j7NBV7bW057294@lurza.secnetix.de> In-Reply-To: <200508231131.j7NBV7bW057294@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Install from USB flash drive? Sort of... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 21:50:23 -0000 Oliver Fromme wrote: > Brandon Fosdick wrote: > > [...] > > Determined to press on I tried the "install from existing file > > system" option, w hich I had never noticed before. That didn't work > > since I had no idea what path to give it, or even if the flash drive > > had been mounted. > > It depends on the FreeBSD version. Older versions mounted > it on /dist, if I remember correctly, but newer ones mount > it directly on /. So assuming the flash is mounted as /, what path do I give sysinstall when it asks? I've tried /, /dist and /mnt. None worked. > You can copy directly from the ISO to your flash drive, > excluding the things that you don't need (i.e. packages). > There's no need to make an additional copy on your HD. > For example: > > # cd /cdrom; find . | grep -v /packages | cpio -dump /flash That worked much better. Thanks From owner-freebsd-stable@FreeBSD.ORG Sun Aug 28 22:15:08 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A45D216A41F for ; Sun, 28 Aug 2005 22:15:08 +0000 (GMT) (envelope-from bfoz@bfoz.net) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [204.127.202.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46F0643D46 for ; Sun, 28 Aug 2005 22:15:07 +0000 (GMT) (envelope-from bfoz@bfoz.net) Received: from [192.168.0.5] (c-24-6-134-233.hsd1.ca.comcast.net[24.6.134.233]) by comcast.net (sccrmhc14) with ESMTP id <2005082822150601400sm5jde>; Sun, 28 Aug 2005 22:15:07 +0000 Message-ID: <43123769.2040707@bfoz.net> Date: Sun, 28 Aug 2005 15:15:05 -0700 From: Brandon Fosdick User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050721) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <200508231131.j7NBV7bW057294@lurza.secnetix.de> In-Reply-To: <200508231131.j7NBV7bW057294@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Install from USB flash drive? Sort of... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 22:15:08 -0000 Oliver Fromme wrote: > It depends on the FreeBSD version. Older versions mounted > it on /dist, if I remember correctly, but newer ones mount > it directly on /. I just tried booting to the flash with a cdrom installed so I could run the fixit shell. Apparently the cdrom is mounted on /dist and the flash isn't mounted at all. So either sysinstall isn't recognizing the flash as installation media or its favoring the cd when its present. How can I tell which is happening? How do I get it to mount the flash automatically? I also tried using the fixit shell to mount the flash to /mnt but that didn't work either. However, I can install from cd after booting to flash, but that defeats the purpose. And since the crazy bios on my motherboard renumbers the ata devices I end up with a useless etc/fstab after removing the cd-rom drive. I love the way sysinstall congratulates me for installing FreeBSD after it fails to find the installation media. Its just so friendly. :P From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 03:26:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5ABD316A41F for ; Mon, 29 Aug 2005 03:26:32 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from rwcrmhc12.comcast.net (rwcrmhc13.comcast.net [216.148.227.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1995843D4C for ; Mon, 29 Aug 2005 03:26:31 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from [192.168.1.105] (pcp09554062pcs.verona01.nj.comcast.net[68.36.0.26]) by comcast.net (rwcrmhc13) with ESMTP id <20050829032631015009r1pje>; Mon, 29 Aug 2005 03:26:31 +0000 From: "C. Michailidis" To: freebsd-stable@freebsd.org Date: Sun, 28 Aug 2005 23:30:08 -0400 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508282330.09302.dinom@balstonresearch.com> Subject: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 03:26:32 -0000 Gleaned from /usr/src/usr.sbin/sysinstall/label.c: #define ROOT_DEFAULT_SIZE 256 #define USR_DEFAULT_SIZE 3072 #define VAR_DEFAULT_SIZE 256 #define TMP_DEFAULT_SIZE 256 #define HOME_DEFAULT_SIZE USR_DEFAULT_SIZE //yada yada #define ROOT_NOMINAL_SIZE 192 #define USR_NOMINAL_SIZE 512 #define VAR_NOMINAL_SIZE 64 #define TMP_NOMINAL_SIZE 64 #define HOME_NOMINAL_SIZE USR_NOMINAL_SIZE //yada yada * Attempt to auto-label the disk. 'perc' (0-100) scales * the size of the various partitions within appropriate * bounds (NOMINAL through DEFAULT sizes). These defaults are tiny... are we still living the 1970's? A 200+gb hardrive is now just over $100 (not exactly a small fortune). Isn't it safe to make some of the default sizes a wee bit larger? That is, a 256mb /tmp and /var doesn't seem "appropriate" if you have one of these massive modern disk drives. For christ's sake, I'd gladly give up a GB or two of /usr so I could build openoffice without needing to consider that I may need an extra few megabytes in /var at the time of the system install. Wouldn't it be smart to remove the hardcoded default sizes altogether and dynamically generate them according to a reasonable function? My initial thought is that scaling them up logarithmically (according to slice size) makes a lot more sense. For example, if the default root fs size where calculated during sysinstall runtime to be 32*ln(slice_size_in_mb), sysinstall would auto-label a 512 mb slice with a 199 mb root filesystem (roughly nominal) and a 200gb slice with a 390mb root filesystem (extra space since the slice can obviously afford it). Something similar would occur for /tmp and /var, the rest of the slice would go towards /usr. Did you ever see a 300 lb. bodybuilder with legs like pencils? It's pretty funny. Now imagine a 199gb /usr with a 256mb /tmp /var and /, look similar? This issue became apparent when I attempted to portupgrade OpenOffice and the process failed, indicating that there wasn't enough space in /var/tmp.... I have a 60gb disk drive and my /var and /tmp are a lousey 256mb?!?!? Ugh! Please don't jump down my throat on this one... I know, I know... I'm stupid, yes I should have labelled the disk by hand. I probably should have installed the entire system by some other incredibly painstaking method too, perhaps I should have etched the bits onto the disk with a needle, a spool of wire, a magnet, and a 9-volt battery - IDK. Forgive the chip on my shoulder, but I had to get that out of my system. I've posted to lists like this so often that I know there is a certain faction which is more than ready to blame the naive user (me) for any and every issue that creeps up. I can see it now.. "No! No! No! You don't understand... the system is perfect as it is, the problem is that YOU are an idiot.". Okay, I already know this. Please don't respond unless you have CONSTRUCTIVE input and/or criticism. Don't respond just to call me a dimwit - please provide meaningful content. Here's a decent rule of thumb: if your response is less that 20 words or 100 characters, try and love again. That being said... I understand that the automatically generated values by sysinstall are the "dumbest" settings you can ask for... but auto-allocating a maximum of 256mb for the root, var, and tmp filesystems (even if you have an incredibly large slice in the 100's of GB) seems to be BEYOND dumb. Perhaps I've just pointed out that I am, in fact, beyond dumb, lol! ;-) Anyway, If it's simply a matter of not having enough programming resources, I'd be more than happy to make the changes to sysinstall and offer the unified diffs. Just let me know your thoughts so that the changes may be relevant for all users. -Dino ********************************** The Dude: I could be just sitting at home with pee stains on my rug. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 03:57:35 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E04316A41F for ; Mon, 29 Aug 2005 03:57:35 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9AA743D4C for ; Mon, 29 Aug 2005 03:57:34 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j7T3vT4A080503; Sun, 28 Aug 2005 22:57:29 -0500 (CDT) (envelope-from dan) Date: Sun, 28 Aug 2005 22:57:29 -0500 From: Dan Nelson To: "C. Michailidis" Message-ID: <20050829035729.GH88693@dan.emsphone.com> References: <200508282330.09302.dinom@balstonresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200508282330.09302.dinom@balstonresearch.com> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.9i Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 03:57:35 -0000 In the last episode (Aug 28), C. Michailidis said: > Did you ever see a 300 lb. bodybuilder with legs like pencils? It's > pretty funny. Now imagine a 199gb /usr with a 256mb /tmp /var and /, > look similar? This issue became apparent when I attempted to > portupgrade OpenOffice and the process failed, indicating that there > wasn't enough space in /var/tmp.... I have a 60gb disk drive and my > /var and /tmp are a lousey 256mb?!?!? Ugh! Please don't jump down > my throat on this one... I know, I know... I'm stupid, yes I should > have labelled the disk by hand. I probably should have installed the > entire system by some other incredibly painstaking method too, > perhaps I should have etched the bits onto the disk with a needle, a > spool of wire, a magnet, and a 9-volt battery - IDK. For anything over a 9gb disk, I just make one big / partition. If you sub partition, you'll always end up filling one (either /var or /tmp quickly or /usr eventually) and wish you had picked different sizes. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 06:09:36 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B236016A421 for ; Mon, 29 Aug 2005 06:09:36 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82F8043D5C for ; Mon, 29 Aug 2005 06:09:34 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from [192.168.1.105] (pcp09554062pcs.verona01.nj.comcast.net[68.36.0.26]) by comcast.net (rwcrmhc11) with ESMTP id <20050829060933013005rrhpe>; Mon, 29 Aug 2005 06:09:33 +0000 From: "C. Michailidis" To: freebsd-stable@freebsd.org Date: Mon, 29 Aug 2005 02:13:12 -0400 User-Agent: KMail/1.8.2 References: <200508282330.09302.dinom@balstonresearch.com> <20050829033739.GV26920@bunrab.catwhisker.org> In-Reply-To: <20050829033739.GV26920@bunrab.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508290213.12978.dinom@balstonresearch.com> Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 06:09:36 -0000 On Sunday 28 August 2005 11:37 pm, you wrote: > I don't really understand what you're so worked up about: if you don't > like the defaults, don't use them. Come on now, Dave. I know that you don't really mean this. You are not a zombie, are you? After all, 'like' is an analog, subjective term. There are various grades of likability. For example, I may like something a lot, I may like it just a bit, I may loathe it, or I may love it. I'm sure you can understand that it is not unreasonable to 'like' the default functionality, yet still see room for improvement in it. Right? In the real world, the mantra "don't use, what you don't like" cannot transcend boundaries, no improvements are ever made, and only a finite number of alternatives will ever be available. This is fine for some people, others make an effort to improve the situation. Of course this is much more of a philosophical issue that a technical one. I suppose I'm "worked up" because I am passionate about things that I really DO like - such as FreeBSD. Therefore, if I see something which I believe could use improvement, I take action to try and make that improvement happen. Although I greatly appreciate your response, I was hoping to receive a more technical perspective regarding people's thoughts on the alleged shortcoming. If your opinion is "I think the current functionality is fine" then so be it. Remember, I'm talking about the 'path of least resistance', I understand that I could label the slice manually with any number of different configurations. The issue I was hoping to shed some light on is... "Can the auto-configuration mechanism stand to be improved?". Is it reasonable (in today's era of dirt cheap disk space) to have a mere 256MB allocated to /tmp (or /var or even /) by default? When I looked at the code, it struck me that the 'defaults' aren't so much defaults as they are maximums for the default usage. It is my opinion that the typical end-user should not need to consider the nearly infinite number of ways to configure his or her filesystems. There is a 'best-practice' recommended by experts (e.g. create /, /var, /tmp, /usr) and it presumably should suit the majority of situations encountered. One day, in the near future, a new FreeBSD user will receive a disk drive as a gift that has a capacity in the terabyte range. They will then (unwittingly) proceed to do a very typical, default installation of FreeBSD, and end up with a 256MB /tmp! I'm actually sad to hear that you think this is acceptable. In fact, I think it is this kind of attitude that keeps open-source systems from being accepted by the population at large. Does your average fireman, police officer, accountant, doctor, lawyer, etc. want to think about how they will be laying out their filesystems when the reality is that a reasonable and typical layout could be done automatically? > But if you want to change it so the defaults are computed automatically, > submit a PR with your patches. I really wouldn't have a problem doing this. However, before I even begin thinking about implementing something, I'd like feedback from the community to insure that my reasoning is correct. This should help maximize the utility of the patches as well as the likelyhood that they are actually imported into the tree. For example, I thought that I heard sysinstall was being completely re-written by a Google-summer-of-code sponsored project, I may just be confusing this with something else. It would be an awful waste of time to implement a change twice or to completely botch something for mere lack of knowledge (especially when there is a vast pool of human knowledge to draw from such as this mailing list) Remember, the sysinstall program is used by almost every FreeBSD user to perform an installation... it isn't a piece of code you want to simply 'hack' at. I'm sure you have heard of the stories where a missing semicolon caused a 10 million dollar rocket to explode or a vital telecom network to black-out for hours (if not days) on end. I've lived through these types of stories and it has forced me to be much less capricious when I sit down to write a piece of code. As they say... "a stich in time, saves nine". -Dino *********************************** Walter Sobchak: GOD DAMN IT! Look, just because we're bereaved, that doesn't make us saps! From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 06:21:53 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4733A16A41F for ; Mon, 29 Aug 2005 06:21:53 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [216.148.227.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 154CC43D49 for ; Mon, 29 Aug 2005 06:21:53 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from [192.168.1.105] (pcp09554062pcs.verona01.nj.comcast.net[68.36.0.26]) by comcast.net (rwcrmhc11) with ESMTP id <20050829062152013005s39ge>; Mon, 29 Aug 2005 06:21:52 +0000 From: "C. Michailidis" To: freebsd-stable@freebsd.org Date: Mon, 29 Aug 2005 02:25:32 -0400 User-Agent: KMail/1.8.2 References: <200508282330.09302.dinom@balstonresearch.com> <20050829035729.GH88693@dan.emsphone.com> In-Reply-To: <20050829035729.GH88693@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200508290225.32394.dinom@balstonresearch.com> Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 06:21:53 -0000 On Sunday 28 August 2005 11:57 pm, you wrote: > For anything over a 9gb disk, I just make one big / partition. If you > sub partition, you'll always end up filling one (either /var or /tmp > quickly or /usr eventually) and wish you had picked different sizes. >=20 This is a very straight-forward way of doing things. Do you really think t= hat sysinstall should use a similar method when it attempts to auto-configu= re a slice? =46rom what I understand there are quite valid reasons why you would want a= seperate /, /var, /tmp, and /usr. For some reason I recall being informed= that more critical filesystems should reside closer to the beginning of th= e disk. I'm not too sure why, maybe someone would care to explain why it isn't the = best practice to have a single monster /? I have simply come to accept thi= s as fact and wouldn't mind a refresher myself. =2DDino *************************** Maude Lebowski: What do you do for recreation? The Dude: Oh, the usual. I bowl. Drive around. The occasional acid flashbac= k.=20 From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 06:24:00 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA8D416A420 for ; Mon, 29 Aug 2005 06:24:00 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd4mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 779BE43D8E for ; Mon, 29 Aug 2005 06:23:55 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd2mr7so.prod.shaw.ca (pd2mr7so-qfe3.prod.shaw.ca [10.0.141.10]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0ILZ00IUQ0ERVF90@l-daemon> for freebsd-stable@freebsd.org; Mon, 29 Aug 2005 00:23:15 -0600 (MDT) Received: from pn2ml4so.prod.shaw.ca ([10.0.121.148]) by pd2mr7so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0ILZ003YL0ER1CI0@pd2mr7so.prod.shaw.ca> for freebsd-stable@freebsd.org; Mon, 29 Aug 2005 00:23:15 -0600 (MDT) Received: from [192.168.0.60] (S0106006067227a4a.vc.shawcable.net [24.87.209.6]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)) with ESMTP id <0ILZ00M020EMWH@l-daemon> for freebsd-stable@freebsd.org; Mon, 29 Aug 2005 00:23:15 -0600 (MDT) Date: Sun, 28 Aug 2005 23:23:09 -0700 From: Colin Percival In-reply-to: <200508290213.12978.dinom@balstonresearch.com> To: "C. Michailidis" Message-id: <4312A9CD.8040008@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.92.0.0 References: <200508282330.09302.dinom@balstonresearch.com> <20050829033739.GV26920@bunrab.catwhisker.org> <200508290213.12978.dinom@balstonresearch.com> User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050724) Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 06:24:00 -0000 C. Michailidis wrote: > Remember, I'm talking about the 'path of least resistance', I understand that > I could label the slice manually with any number of different configurations. > The issue I was hoping to shed some light on is... "Can the auto-configuration > mechanism stand to be improved?". Is it reasonable (in today's era of dirt cheap > disk space) to have a mere 256MB allocated to /tmp (or /var or even /) by > default? The default sizes are now currently 512 MB for / and /tmp, and 1024 MB plus space for one crashdump on /var. If anything, these are vast overkill for most systems; on /, for example, it is hard to imagine a situation where a normal user would use more than 150MB of space unless they were doing something which they shouldn't be doing. Colin Percival From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 06:39:15 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98E9E16A41F; Mon, 29 Aug 2005 06:39:15 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from riyal.ugcs.caltech.edu (riyal.ugcs.caltech.edu [131.215.176.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8C6843D4C; Mon, 29 Aug 2005 06:39:14 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by riyal.ugcs.caltech.edu (Postfix, from userid 3640) id BE67A45804; Sun, 28 Aug 2005 23:39:13 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by riyal.ugcs.caltech.edu (Postfix) with ESMTP id 489A545802; Sun, 28 Aug 2005 23:39:13 -0700 (PDT) Date: Sun, 28 Aug 2005 23:39:13 -0700 (PDT) From: Jon Dama To: Colin Percival In-Reply-To: <4312A9CD.8040008@freebsd.org> Message-ID: References: <200508282330.09302.dinom@balstonresearch.com> <20050829033739.GV26920@bunrab.catwhisker.org> <200508290213.12978.dinom@balstonresearch.com> <4312A9CD.8040008@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org, "C. Michailidis" Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 06:39:15 -0000 yes, that's quite generous. why isn't /tmp just an mfs mount though? On Sun, 28 Aug 2005, Colin Percival wrote: > C. Michailidis wrote: > > Remember, I'm talking about the 'path of least resistance', I understand that > > I could label the slice manually with any number of different configurations. > > The issue I was hoping to shed some light on is... "Can the auto-configuration > > mechanism stand to be improved?". Is it reasonable (in today's era of dirt cheap > > disk space) to have a mere 256MB allocated to /tmp (or /var or even /) by > > default? > > The default sizes are now currently 512 MB for / and /tmp, and 1024 MB plus > space for one crashdump on /var. If anything, these are vast overkill for most > systems; on /, for example, it is hard to imagine a situation where a normal > user would use more than 150MB of space unless they were doing something which > they shouldn't be doing. > > Colin Percival > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 06:44:20 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6353316A41F for ; Mon, 29 Aug 2005 06:44:20 +0000 (GMT) (envelope-from rees@ddcom.co.jp) Received: from proxy.ddcom.co.jp (proxy.ddcom.co.jp [211.121.191.163]) by mx1.FreeBSD.org (Postfix) with SMTP id C023B43D53 for ; Mon, 29 Aug 2005 06:44:19 +0000 (GMT) (envelope-from rees@ddcom.co.jp) Received: (qmail 5876 invoked by alias); 29 Aug 2005 06:52:38 -0000 Received: from unknown (HELO ?172.16.1.133?) (10.10.10.11) by mail.ddcom.local with SMTP; 29 Aug 2005 06:52:38 -0000 Mime-Version: 1.0 (Apple Message framework v734) In-Reply-To: <200508282330.09302.dinom@balstonresearch.com> References: <200508282330.09302.dinom@balstonresearch.com> Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed Message-Id: <35B88567-1C0D-411E-9088-561600D09C83@ddcom.co.jp> Content-Transfer-Encoding: quoted-printable From: Joel Rees Date: Mon, 29 Aug 2005 15:44:14 +0900 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.734) Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 06:44:20 -0000 On =E5=B9=B3=E6=88=90 17/08/29, at 12:30, C. Michailidis wrote: > [...] > I understand that the automatically generated values by sysinstall =20 > are the "dumbest" settings you can ask for... but auto-allocating a =20= > maximum of 256mb for the root, var, and tmp filesystems (even if =20 > you have an incredibly large slice in the 100's of GB) seems to be =20 > BEYOND dumb. Perhaps I've just pointed out that I am, in fact, =20 > beyond dumb, lol! ;-) > > Anyway, If it's simply a matter of not having enough programming =20 > resources, I'd be more than happy to make the changes to sysinstall =20= > and offer the unified diffs. Just let me know your thoughts so =20 > that the changes may be relevant for all users. I can sympathize. I've been caught by bad partition sizes. But I never take the default sizes. In particular, I check the size =20 of /var and its sub-partitions carefully. (Seems like nobody uses /=20 tmp that heavily anymore, but /var/tmp gets hit a lot, and /var/log =20 may need to be relatively huge, depending on what the system is =20 doing, etc.) A partition "wizard" (I hate that term, but you know what I mean.) =20 that would coach new users and remind old users about the effects of =20 freeBSD layout on partition sizes would, I'm sure, be welcome, if you =20= want to take the trouble. Mind you, simple ruled apportionment would =20 not be sufficient. We would like to have sets of rules, one for a =20 pure web server, one for a basic home-user websurfing, e-mailing, =20 letter-writing coffee-table-top, several for different kinds of =20 firewalls and bridges, ... And what about older disks, where cylinder sizes, number of reported =20 heads, etc. were meaningful? No, that's probably not relevant except =20 for RAIDs. (As long as I'm making demands on your time, why not think big? ;^) Anyway, it could be a useful project, but you'll want to recognize =20 there's a lot of stuff hiding under the surface there. Joel Rees digitcom, inc. =E6=A0=AA=E5=BC=8F=E4=BC=9A=E7=A4=BE=E3=83=87=E3=82=B8=E3= =82=B3=E3=83=A0 Kobe, Japan +81-78-672-8800 ** ** From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 06:44:34 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6112516A47D for ; Mon, 29 Aug 2005 06:44:34 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id C704843D4C for ; Mon, 29 Aug 2005 06:44:33 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 4082D5C68; Mon, 29 Aug 2005 02:44:33 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00996-07; Mon, 29 Aug 2005 02:44:32 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-79-217.ny325.east.verizon.net [68.161.79.217]) by pi.codefab.com (Postfix) with ESMTP id 166085C72; Mon, 29 Aug 2005 02:44:31 -0400 (EDT) Message-ID: <4312AEE0.8080806@mac.com> Date: Mon, 29 Aug 2005 02:44:48 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jon Dama References: <200508282330.09302.dinom@balstonresearch.com> <20050829033739.GV26920@bunrab.catwhisker.org> <200508290213.12978.dinom@balstonresearch.com> <4312A9CD.8040008@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 06:44:34 -0000 Jon Dama wrote: > yes, that's quite generous. > > why isn't /tmp just an mfs mount though? While I like that suggestion personally, some people get perturbed about files in /tmp going away if the power fails or you reboot. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 06:51:19 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DB7916A41F for ; Mon, 29 Aug 2005 06:51:19 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-3.paradise.net.nz (bm-3a.paradise.net.nz [202.0.58.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02A8643D49 for ; Mon, 29 Aug 2005 06:51:18 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-2.paradise.net.nz (smtp-2a.paradise.net.nz [202.0.32.195]) by linda-3.paradise.net.nz (Paradise.net.nz) with ESMTP id <0ILZ0014N1PEPX@linda-3.paradise.net.nz> for freebsd-stable@freebsd.org; Mon, 29 Aug 2005 18:51:15 +1200 (NZST) Received: from [192.168.1.11] (218-101-14-103.paradise.net.nz [218.101.14.103]) by smtp-2.paradise.net.nz (Postfix) with ESMTP id 270979E39D; Mon, 29 Aug 2005 18:51:14 +1200 (NZST) Date: Mon, 29 Aug 2005 18:51:12 +1200 From: Mark Kirkwood In-reply-to: <200508290225.32394.dinom@balstonresearch.com> To: "C. Michailidis" Message-id: <4312B060.4080104@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050726) References: <200508282330.09302.dinom@balstonresearch.com> <20050829035729.GH88693@dan.emsphone.com> <200508290225.32394.dinom@balstonresearch.com> Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 06:51:19 -0000 C. Michailidis wrote: > > This is a very straight-forward way of doing things. Do you really think that sysinstall should use a similar method when it attempts to auto-configure a slice? > > From what I understand there are quite valid reasons why you would want a seperate /, /var, /tmp, and /usr. For some reason I recall being informed that more critical filesystems should reside closer to the beginning of the disk. > > I'm not too sure why, maybe someone would care to explain why it isn't the best practice to have a single monster /? I have simply come to accept this as fact and wouldn't mind a refresher myself. > The handbook (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disk-organization.html) has quite a sensible discussion about this: Different filesystems can have different mount options. For example, with careful planning, the root filesystem can be mounted read-only, making it impossible for you to inadvertently delete or edit a critical file. Separating user-writable filesystems, such as /home, from other filesystems also allows them to be mounted nosuid; this option prevents the suid/guid bits on executables stored on the filesystem from taking effect, possibly improving security. FreeBSD automatically optimizes the layout of files on a filesystem, depending on how the filesystem is being used. So a filesystem that contains many small files that are written frequently will have a different optimization to one that contains fewer, larger files. By having one big filesystem this optimization breaks down. FreeBSD's filesystems are very robust should you lose power. However, a power loss at a critical point could still damage the structure of the filesystem. By splitting your data over multiple filesystems it is more likely that the system will still come up, making it easier for you to restore from backup as necessary. In addition, there are some security implications - you cannot hard-link across filesystems (well not last time I tried anyway...). Finally, I use everything in / for my workstation, but am reconsidering after a runaway file writing process filled up everything and panicked the box - I am guessing that if I had a separate /home (say), the that would not have happened! Cheers Mark From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 06:52:15 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37FAE16A420 for ; Mon, 29 Aug 2005 06:52:15 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5426143D76 for ; Mon, 29 Aug 2005 06:52:10 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 21388 invoked from network); 29 Aug 2005 16:52:09 +1000 Received: from andromeda.lef.com.au (HELO ?10.168.101.24?) (210.8.93.2) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 29 Aug 2005 16:52:09 +1000 Message-ID: <4312B091.9090104@meijome.net> Date: Mon, 29 Aug 2005 16:52:01 +1000 From: Norberto Meijome User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rene Ladan References: <55023220@srv.sem.ipt.ru> <20050828150947.GA58038@82-168-75-155-bbxl.xdsl.tiscali.nl> In-Reply-To: <20050828150947.GA58038@82-168-75-155-bbxl.xdsl.tiscali.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Boris Samorodov , stable@freebsd.org Subject: Re: 6.0 and -O2 option X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 06:52:15 -0000 Rene Ladan wrote: > On Sun, Aug 28, 2005 at 04:30:19PM +0400, Boris Samorodov wrote: > >>Hi! >> >> >>As for 5.x notes about -O2 (libalias, gcc) were removed at revision >>1.229.2.7 of /usr/src/share/examples/etc/make.conf. But for 6.0-BETA3 >>we do have these warnings. Should they be removed as for 5.x? Is it >>safe to use -O2 to build/install kernel, world, ports fro 6.0? >> > > Kernel and world seem to be ok with -O2, for ports it is not advised. Hi, I may have missed a thread or something (just let me know :) ) - why is -O2 not advised for ports on 6.0? cheers, Beto From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 07:31:36 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8834E16A41F for ; Mon, 29 Aug 2005 07:31:36 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from riyal.ugcs.caltech.edu (riyal.ugcs.caltech.edu [131.215.176.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AC4D43D46 for ; Mon, 29 Aug 2005 07:31:36 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by riyal.ugcs.caltech.edu (Postfix, from userid 3640) id 239E545804; Mon, 29 Aug 2005 00:31:34 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by riyal.ugcs.caltech.edu (Postfix) with ESMTP id CB57E45802; Mon, 29 Aug 2005 00:31:34 -0700 (PDT) Date: Mon, 29 Aug 2005 00:31:34 -0700 (PDT) From: Jon Dama To: Chuck Swiger In-Reply-To: <4312AEE0.8080806@mac.com> Message-ID: References: <200508282330.09302.dinom@balstonresearch.com> <20050829033739.GV26920@bunrab.catwhisker.org> <200508290213.12978.dinom@balstonresearch.com> <4312A9CD.8040008@freebsd.org> <4312AEE0.8080806@mac.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 07:31:36 -0000 Um, that they may be but... I was under the impression (mistaken?) that /tmp is a directory defined under the POSIX standard and is in fact supposed to be flushed in those cases, and that /var/tmp is to be used for programs desiring persistant storage across shutdowns (scheduled and unscheduled). Perhaps it only says that a program is not allowed to rely on /tmp being persistent. I don't have a copy at hand :-/ -Jon On Mon, 29 Aug 2005, Chuck Swiger wrote: > Jon Dama wrote: > > yes, that's quite generous. > > > > why isn't /tmp just an mfs mount though? > > While I like that suggestion personally, some people get perturbed about files > in /tmp going away if the power fails or you reboot. > > -- > -Chuck > From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 08:20:07 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9494016A41F; Mon, 29 Aug 2005 08:20:07 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [204.127.202.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BA8143D49; Mon, 29 Aug 2005 08:20:06 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from [192.168.1.105] (pcp09554062pcs.verona01.nj.comcast.net[68.36.0.26]) by comcast.net (sccrmhc14) with ESMTP id <2005082908200601400skvipe>; Mon, 29 Aug 2005 08:20:06 +0000 From: "C. Michailidis" To: freebsd-stable@freebsd.org Date: Mon, 29 Aug 2005 04:23:46 -0400 User-Agent: KMail/1.8.2 References: <200508282330.09302.dinom@balstonresearch.com> <200508290213.12978.dinom@balstonresearch.com> <4312A9CD.8040008@freebsd.org> In-Reply-To: <4312A9CD.8040008@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508290423.46695.dinom@balstonresearch.com> Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 08:20:07 -0000 On Monday 29 August 2005 02:23 am, Colin Percival wrote: > The default sizes are now currently 512 MB for / and /tmp, and 1024 MB plus > space for one crashdump on /var. If anything, these are vast overkill for most > systems; on /, for example, it is hard to imagine a situation where a normal > user would use more than 150MB of space unless they were doing something which > they shouldn't be doing. > > Colin Percival > Are you referring to 6.x? I ask only because I just cvsuped my 5-stable workstation and the file /usr/src/usr.sbin/sysinstall/label.c still shows: #define ROOT_DEFAULT_SIZE 256 #define USR_DEFAULT_SIZE 3072 #define VAR_DEFAULT_SIZE 256 #define TMP_DEFAULT_SIZE 256 Maybe I'm not looking in the right spot? In any case, this issue is neither here nor there. I trust that "these are vast overkill for most systems" and I *hope* that it will continue to be the case for the foreseeable future. However, a very famous person has been haunted by a quote which has been attributed to him (even though he claims to have never said it). Do you remember "640K ought to be enough for anybody."? LOL ;-) Like I said, I thought of this after an unsuccessful portupgrade (from source) of the openoffice-1.1 port. It bombed during install, complaining that /var/tmp didn't have enough room. I began thinking... hey, I have a 60GB disk drive with plenty of free space in /usr, why are /tmp and /var only 256MB? From what you guys are telling me, I'm beginning to think that the size of my filesystems are fine, but that the latest openoffice is somehow the culprit. I thought I'd try portupgrading openoffice-1.1 from packages (they weren't available last time I had tried). Although that succeeded in downloading and installing... it exploded during runtime complaining about some missing shared object files. Honestly, I don't care too much about this matter though, I just backed 1.1.5rc2 out (after all it is just a *candidate*, and apparently a broken one). Oh, btw, thanks for the update Colin. -Dino *********************************** The Dude: Yeah, well. The Dude abides. The Stranger: The Dude abides. I don't know about you but I take comfort in that. It's good knowin' he's out there. The Dude. Takin' 'er easy for all us sinners. Shoosh. I sure hope he makes the finals. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 08:24:23 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57E1516A41F for ; Mon, 29 Aug 2005 08:24:23 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED59343D49 for ; Mon, 29 Aug 2005 08:24:22 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from SMILEY (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 47F8D19F3B; Mon, 29 Aug 2005 01:27:53 -0700 (PDT) From: "Darren Pilgrim" To: "'C. Michailidis'" , Date: Mon, 29 Aug 2005 01:24:19 -0700 Message-ID: <000d01c5ac73$0e4fbb50$6b2a15ac@SMILEY> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <200508282330.09302.dinom@balstonresearch.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Importance: Normal Cc: Subject: RE: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 08:24:23 -0000 From: C. Michailidis >=20 [sysinstall FS sizing defaults] >=20 > <...> Isn't it safe to make some of the default sizes a=20 > wee bit larger? That is, a 256mb /tmp and /var doesn't seem=20 > "appropriate" if you have one of these massive modern disk=20 > drives. For christ's sake, I'd gladly give up a GB or two of=20 > /usr so I could build openoffice without needing to consider=20 > that I may need an extra few megabytes in /var at the time of=20 > the system install. >=20 <...> >=20 > Wouldn't it be smart to remove the hardcoded default sizes=20 > altogether and dynamically generate them according to a=20 > reasonable function? Probably, but a template for something like this isn't simple unless it's created as part of a general profile-based installer that would inform sysinstall of the machine's purpose in life. For example, a "workstation or Windows replacement" would need several extra GB in /usr whereas a server would get away with a much smaller /usr, but need those extra file-systems for logs, spools and other data. There are, however, some basic constants: If /usr, /var and /home are on another file-system, / doesn't need to be more than 150-200 MB. There just isn't that much in the root file-system. Assuming the default log retention and no spooling, /var will likely never grow past 50MB. Adding a mail, web, db or log server or increasing log retention will go well past that mark, but then such servers should have subordinate file-systems to handle the extra data. What comes with the OS will take less than 300MB in /usr. /usr/src and /usr/obj eat around 500 MB each. /usr/local eats around 1 GB for most servers and 3 GB on a desktop. /usr/X11R6 is empty if X isn't installed, the base Xorg server package is a few hundred MB and a desktop can need several GB. /usr/ports should have 1-2 GB just for distfiles on a desktop built from ports and 3 GB for work if you're building something huge, like KDE. I size /usr/ports to 6 GB on my desktop machines. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 08:36:01 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00F3E16A41F for ; Mon, 29 Aug 2005 08:36:01 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [204.127.198.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A9C543D6B for ; Mon, 29 Aug 2005 08:35:58 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from [192.168.1.105] (pcp09554062pcs.verona01.nj.comcast.net[68.36.0.26]) by comcast.net (rwcrmhc12) with ESMTP id <2005082908355801400kidj7e>; Mon, 29 Aug 2005 08:35:58 +0000 From: "C. Michailidis" To: freebsd-stable@freebsd.org Date: Mon, 29 Aug 2005 04:39:38 -0400 User-Agent: KMail/1.8.2 References: <200508282330.09302.dinom@balstonresearch.com> <200508290225.32394.dinom@balstonresearch.com> <4312B060.4080104@paradise.net.nz> In-Reply-To: <4312B060.4080104@paradise.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508290439.38890.dinom@balstonresearch.com> Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 08:36:01 -0000 On Monday 29 August 2005 02:51 am, you wrote: > The handbook > (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disk-organization.html) > > has quite a sensible discussion about this: I knew that there was a reason I liked using sysinstall's automatic filesystem generation feature :-) Oh, a big TY to everyone for the timely, cordial, and quite informative responses! -Dino P.S. Hope you liked the movie quotes - if you haven't seen the movie "The Big Lebowski" rent it!! It had me in stitches. ************************************ The Dude: Did you ever hear of "The Seattle Seven"? Maude Lebowski: Mmm. The Dude: That was me... and six other guys. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 08:51:47 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A5EE16A41F for ; Mon, 29 Aug 2005 08:51:47 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id CABE043D49 for ; Mon, 29 Aug 2005 08:51:46 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AA9B91.dip0.t-ipconnect.de [84.170.155.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 46A9631DE7; Mon, 29 Aug 2005 10:54:32 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j7T8peso000725; Mon, 29 Aug 2005 10:51:41 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j7T8peYR000724; Mon, 29 Aug 2005 10:51:40 +0200 (CEST) (envelope-from mkb) Date: Mon, 29 Aug 2005 10:51:40 +0200 From: Matthias Buelow To: Mark Kirkwood Message-ID: <20050829085140.GA684@drjekyll.mkbuelow.net> References: <200508282330.09302.dinom@balstonresearch.com> <20050829035729.GH88693@dan.emsphone.com> <200508290225.32394.dinom@balstonresearch.com> <4312B060.4080104@paradise.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4312B060.4080104@paradise.net.nz> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, "C. Michailidis" Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 08:51:47 -0000 Mark Kirkwood wrote: >FreeBSD's filesystems are very robust should you lose power. This sentence is completely bogus (or at best: wishful thinking) and should be deleted. mkb. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 10:06:02 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4394C16A41F for ; Mon, 29 Aug 2005 10:06:02 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from rwcrmhc12.comcast.net (rwcrmhc14.comcast.net [216.148.227.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0176443D45 for ; Mon, 29 Aug 2005 10:06:01 +0000 (GMT) (envelope-from dinom@balstonresearch.com) Received: from [192.168.1.105] (pcp09554062pcs.verona01.nj.comcast.net[68.36.0.26]) by comcast.net (rwcrmhc14) with ESMTP id <2005082910060001400hdtmfe>; Mon, 29 Aug 2005 10:06:01 +0000 From: "C. Michailidis" To: freebsd-stable@freebsd.org Date: Mon, 29 Aug 2005 06:09:41 -0400 User-Agent: KMail/1.8.2 References: <000d01c5ac73$0e4fbb50$6b2a15ac@SMILEY> In-Reply-To: <000d01c5ac73$0e4fbb50$6b2a15ac@SMILEY> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508290609.42070.dinom@balstonresearch.com> Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 10:06:02 -0000 On Monday 29 August 2005 04:24 am, you wrote: > Probably, but a template for something like this isn't simple unless > it's created as part of a general profile-based installer that would > inform sysinstall of the machine's purpose in life. For example, a Sure, I can understand this perfectly. And I agree 99%. Ultimately the "machine's purpose in life" is the most important factor. However, since this can often be an intangible factor (where exactly do you draw the line between server/workstation/embeded system/etc/etc) the sysinstall process needs (perhaps) to rely on the more concrete variables in the puzzle which are available. That is, I may install FreeBSD onto a machine without initially having a specific purpose for the system. In this case, the dominant variable (in my mind) becomes, quite simply... disk size. After all, I have no specific purpose for the system, it will be a general-purpose machine and in a sense "all other factors are equal". It struck me as peculiar that I could be installing to a disk over 200GB in size, indicate to sysinstall that it should layout the filesystems in its default manner... and I would actually end up with a /tmp (or /var or even /) that is 256MB (well, let's say 512MB with the new information Colin has given us). The numbers themselves don't matter in my mind, the fact that they are not a function of the disk size does. The truth is, they are related to the size of the disk (I noticed this while browsing the code for sysinstall) but they only vary if the size of the disk is *smaller* than some already small, fixed number. Effectively, we are taking a known variable that may fluctuate greatly (disk size) and completely ignoring it during installation. Pretty dumb, no? Obviously, this leaves a bad taste in my mouth. Take it to an extreme and maybe I can convert you to my team. Imagine installing to a disk that is 500 terabytes in size... wouldn't it be odd (to say the least) for sysinstall to allocate some infinitesimally small fraction of the disk to /tmp? Isn't /tmp just a place to store temporary files? Isn't there the *possibility* that you are using your system correctly and yet still want to store a large temporary file? I agree, a general profile-based installer would be ideal. Unfortunately, we live in the real world and thus it may not be practical. This fact should not preclude us from making improvements which ARE practical AND *approximate* the ideal? The first thing that came to my mind was to base the sizes on the natural logarithm function. Natual log came to my mind because the existing implementation has a ceiling, I wanted "a wee bit" more - since ln grows slowly I'd have "the best of both worlds"? The more I think about it, the more I want to say the relationship should simply be linear. Bottom line, I don't know what function would be the *best* to use, but I do believe something like this (for starters) is practical and most likely superior to the current functionality. Many people probably agree with Colin... "these [values] are vast overkill for most systems" - I do too, but I believe this is a subjective matter. Having a 200GB disk (IMHO) is also vast overkill for most systems. Does this mean disk manufacturers should force a user to generate valid reasons as to why they need the disk space before selling them the disk drive? The question that needs to be answered (I suppose) is: can we think of a practical, yet more reasonable way of having sysinstall allocate space for the filesystems? It's my opinion that the answer is yes. I do not find it reasonable to always recommend that the user create the same size /, /var, and /tmp no matter how incredibly large (or small) the user's disk drive is. You may agree or disagree... I just pray to God I've made myself clear at this point, lol. Just my 2 cents, Dino From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 10:41:52 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03EBD16A41F for ; Mon, 29 Aug 2005 10:41:52 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 890F343D45 for ; Mon, 29 Aug 2005 10:41:51 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AA805F.dip0.t-ipconnect.de [84.170.128.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 20DEE35874; Mon, 29 Aug 2005 12:44:43 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j7TAfpF9001155; Mon, 29 Aug 2005 12:41:51 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j7TAfpVP001154; Mon, 29 Aug 2005 12:41:51 +0200 (CEST) (envelope-from mkb) Date: Mon, 29 Aug 2005 12:41:50 +0200 From: Matthias Buelow To: "C. Michailidis" Message-ID: <20050829104150.GA1051@drjekyll.mkbuelow.net> References: <000d01c5ac73$0e4fbb50$6b2a15ac@SMILEY> <200508290609.42070.dinom@balstonresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200508290609.42070.dinom@balstonresearch.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 10:41:52 -0000 C. Michailidis wrote: >Effectively, we are taking a known variable that may fluctuate >greatly (disk size) and completely ignoring it during installation. >Pretty dumb, no? Obviously, this leaves a bad taste in my mouth. >Take it to an extreme and maybe I can convert you to my team. >Imagine installing to a disk that is 500 terabytes in size... >wouldn't it be odd (to say the least) for sysinstall to allocate >some infinitesimally small fraction of the disk to /tmp? Isn't >/tmp just a place to store temporary files? Isn't there the >*possibility* that you are using your system correctly and yet still >want to store a large temporary file? >From my experience, 256MB is usually more than enough for /tmp. The /tmp directory isn't typically used to store arbritrary huge datasets but is used only by system utilities, scripts, etc., for storing (small) temporary files. The /tmp directory is often a (virtual-) memory-backed filesystem, and on some systems this is the default setting (Solaris, NetBSD 2), so a developer cannot assume in any case that /tmp will be large. Furthermore, the operating system occupies only a small portion of my large hard drive in my workstation, for example. The rest is occupied by, uhm, user files. It doesn't make sense to scale up the basic filesystems by orders of magnitude relative to disk size. I do agree however, that 256mb might be a bit small for / or /var. Maybe cap those at 1GB (/) for the default settings. The /usr filesystem should be at least 5-6GB for a typical workstation setup, if space permits, but probably not more than 10GB. mkb. P.S.: Please instruct your mail program to wrap lines at about 72 characters, as is conventional. You have lines >700 characters in there, and I had to manually reformat the quoted text, which is annoying. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 11:25:30 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2395E16A41F for ; Mon, 29 Aug 2005 11:25:30 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-3.paradise.net.nz (bm-3a.paradise.net.nz [202.0.58.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90A0C43D4C for ; Mon, 29 Aug 2005 11:25:29 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-3.paradise.net.nz (smtp-3a.paradise.net.nz [202.0.32.196]) by linda-3.paradise.net.nz (Paradise.net.nz) with ESMTP id <0ILZ003NFEEFK4@linda-3.paradise.net.nz> for freebsd-stable@freebsd.org; Mon, 29 Aug 2005 23:25:28 +1200 (NZST) Received: from [192.168.1.11] (218-101-14-103.paradise.net.nz [218.101.14.103]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id A75F5AF007; Mon, 29 Aug 2005 23:08:41 +1200 (NZST) Date: Mon, 29 Aug 2005 23:08:38 +1200 From: Mark Kirkwood In-reply-to: <20050829085140.GA684@drjekyll.mkbuelow.net> To: Matthias Buelow Message-id: <4312ECB6.3000702@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050726) References: <200508282330.09302.dinom@balstonresearch.com> <20050829035729.GH88693@dan.emsphone.com> <200508290225.32394.dinom@balstonresearch.com> <4312B060.4080104@paradise.net.nz> <20050829085140.GA684@drjekyll.mkbuelow.net> Cc: freebsd-stable@freebsd.org, "C. Michailidis" Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 11:25:30 -0000 Matthias Buelow wrote: > Mark Kirkwood wrote: > > >>FreeBSD's filesystems are very robust should you lose power. > > > This sentence is completely bogus (or at best: wishful thinking) > and should be deleted. > It's probably correct if you have hw.ata.wc=0 (and are using IDE drives obviously). From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 12:04:23 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A350016A41F for ; Mon, 29 Aug 2005 12:04:23 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DF7243D46 for ; Mon, 29 Aug 2005 12:04:23 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AA805F.dip0.t-ipconnect.de [84.170.128.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 27D2E3578C; Mon, 29 Aug 2005 14:07:14 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j7TC4GGY001545; Mon, 29 Aug 2005 14:04:22 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j7TC4Fdj001544; Mon, 29 Aug 2005 14:04:15 +0200 (CEST) (envelope-from mkb) Date: Mon, 29 Aug 2005 14:04:15 +0200 From: Matthias Buelow To: Mark Kirkwood Message-ID: <20050829120415.GA1462@drjekyll.mkbuelow.net> References: <200508282330.09302.dinom@balstonresearch.com> <20050829035729.GH88693@dan.emsphone.com> <200508290225.32394.dinom@balstonresearch.com> <4312B060.4080104@paradise.net.nz> <20050829085140.GA684@drjekyll.mkbuelow.net> <4312ECB6.3000702@paradise.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4312ECB6.3000702@paradise.net.nz> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, "C. Michailidis" Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 12:04:23 -0000 Mark Kirkwood wrote: >>>FreeBSD's filesystems are very robust should you lose power. >>This sentence is completely bogus (or at best: wishful thinking) >>and should be deleted. >It's probably correct if you have hw.ata.wc=0 (and are using IDE drives >obviously). I'd like to stress the "probably". I've already seen unrepairable filesystem corruption with softupdates enabled in the past with "good" scsi disks at power loss. Furthermore, disabling the write-back cache in a typical consumer (read: typical PC workstation) environment today, with large IDE/SATA drives, is unrealistic because of the severe performance degradation, and might even be counter-indicated due to the increased wear&tear on the disk, which might significantly reduce the disk's lifetime. Softupdates works only in an idealized environment that doesn't match against reality. In addition, with softupdates there seems to be a much higher probability of losing files, as I have observed.. that is, getting them zero-truncated, or even deleted (which shouldn't happen in that scenario, I'm sure I've seen the results of a bug), than without. Do I still use softupdates? Yes, because of the performance benefit, but I don't treat it as much different than completely asynchronous operation, with the only difference that it's a slightly more resilient in case of a kernel crash (vs. a power outage) and I make frequent backups. mkb. From owner-freebsd-stable@FreeBSD.ORG Sun Aug 28 22:47:06 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CD0E16A41F for ; Sun, 28 Aug 2005 22:47:06 +0000 (GMT) (envelope-from mark_space4@hotmail.com) Received: from hotmail.com (bay105-f38.bay105.hotmail.com [65.54.224.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C8B443D45 for ; Sun, 28 Aug 2005 22:47:06 +0000 (GMT) (envelope-from mark_space4@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 28 Aug 2005 15:47:06 -0700 Message-ID: Received: from 65.54.224.200 by by105fd.bay105.hotmail.msn.com with HTTP; Sun, 28 Aug 2005 22:47:05 GMT X-Originating-IP: [65.54.224.200] X-Originating-Email: [mark_space4@hotmail.com] X-Sender: mark_space4@hotmail.com From: "Mark Space" To: freebsd-stable@freebsd.org Date: Sun, 28 Aug 2005 22:47:05 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 28 Aug 2005 22:47:06.0111 (UTC) FILETIME=[6A3C00F0:01C5AC22] X-Mailman-Approved-At: Mon, 29 Aug 2005 12:10:03 +0000 Subject: Incorrect super block--help! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2005 22:47:06 -0000 Hey, newb BSDer here with a question I've got a brand new 5.4 install. I'm trying to mount the CDROM. As root, I type: mount /dev/acd0 /cdrom and I get "incorrect super block" error message after a bit of CD activity, and no mount. I've tried a CD-RW I burned (the FreeBSD install disk I installed from) and an old copy of SimCity 2000, neither worked, same error message. I'm stuck. Any ideas? _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 12:15:11 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 239B516A41F for ; Mon, 29 Aug 2005 12:15:11 +0000 (GMT) (envelope-from ptroot@iaces.com) Received: from iaces.com (horton.iaces.com [204.147.87.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5E3043D48 for ; Mon, 29 Aug 2005 12:15:10 +0000 (GMT) (envelope-from ptroot@iaces.com) Received: from [204.147.87.125] (borg.iaces.com [204.147.87.125]) (authenticated bits=0) by iaces.com (8.13.3/8.13.3) with ESMTP id j7TCF9P3090576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Aug 2005 07:15:09 -0500 (CDT) (envelope-from ptroot@iaces.com) Message-ID: <4312FC52.3070308@iaces.com> Date: Mon, 29 Aug 2005 07:15:14 -0500 From: "Paul T. Root" User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Space References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Incorrect super block--help! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 12:15:11 -0000 You're trying to mount it as a rw disc and as a UFS file system mount -r -t cd9660 /dev/acd0 /cdrom Mark Space wrote: > Hey, newb BSDer here with a question > > I've got a brand new 5.4 install. I'm trying to mount the CDROM. As > root, I type: > > mount /dev/acd0 /cdrom > > and I get "incorrect super block" error message after a bit of CD > activity, and no mount. I've tried a CD-RW I burned (the FreeBSD > install disk I installed from) and an old copy of SimCity 2000, neither > worked, same error message. > > I'm stuck. Any ideas? -- ______ Paul T. Root / _ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \______/ From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 12:16:57 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C1BB16A41F for ; Mon, 29 Aug 2005 12:16:57 +0000 (GMT) (envelope-from freebsd-stable@auscert.org.au) Received: from titania.auscert.org.au (gw.auscert.org.au [203.5.112.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63FE043D48 for ; Mon, 29 Aug 2005 12:16:55 +0000 (GMT) (envelope-from freebsd-stable@auscert.org.au) Received: from app.auscert.org.au (app [10.0.1.192]) by titania.auscert.org.au (8.12.10/8.12.10) with ESMTP id j7TCGrBV005548 for ; Mon, 29 Aug 2005 22:16:53 +1000 (EST) Received: from app.auscert.org.au (localhost.auscert.org.au [127.0.0.1]) by app.auscert.org.au (8.13.1/8.13.1) with ESMTP id j7TCGsss026612 for ; Mon, 29 Aug 2005 22:16:54 +1000 (EST) (envelope-from freebsd-stable@auscert.org.au) Message-Id: <200508291216.j7TCGsss026612@app.auscert.org.au> To: freebsd-stable@freebsd.org from: freebsd-stable@auscert.org.au In-Reply-To: Your message of "Sun, 28 Aug 2005 22:47:05 GMT." Date: Mon, 29 Aug 2005 22:16:54 +1000 Subject: Re: Incorrect super block--help! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 12:16:57 -0000 > Hey, newb BSDer here with a question > > I've got a brand new 5.4 install. I'm trying to mount the CDROM. As root, > I type: > > mount /dev/acd0 /cdrom > > and I get "incorrect super block" error message after a bit of CD activity, > and no mount. I've tried a CD-RW I burned (the FreeBSD install disk I > installed from) and an old copy of SimCity 2000, neither worked, same error > message. > > I'm stuck. Any ideas? The drive could have just started to fail. Sounds unlikely, but it's the kind of error you might see. Does it work with another OS, or can you substitute another drive and try that way? joel From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 12:46:13 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8B1A16A41F for ; Mon, 29 Aug 2005 12:46:13 +0000 (GMT) (envelope-from scottro@nyc.rr.com) Received: from mail.starlofashions.com (mail.starlofashions.com [12.44.50.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id D55A143D67 for ; Mon, 29 Aug 2005 12:46:05 +0000 (GMT) (envelope-from scottro@nyc.rr.com) Received: from nyserve3.starlofashions.com ([192.0.0.230]) by mail.starlofashions.com (8.9.3/8.9.3) with ESMTP id IAA14395 for ; Mon, 29 Aug 2005 08:44:57 -0400 Received: from uws1.starlofashions.com (uws1.starlofashions.com [192.168.1.230]) by nyserve3.starlofashions.com (Postfix) with SMTP id 8376A60E1 for ; Mon, 29 Aug 2005 08:44:57 -0400 (EDT) Received: by uws1.starlofashions.com (sSMTP sendmail emulation); Mon, 29 Aug 2005 08:44:57 -0400 Date: Mon, 29 Aug 2005 08:44:57 -0400 From: Scott Robbins To: freebsd-stable@freebsd.org Message-ID: <20050829124457.GA90168@uws1.starlofashions.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <200508291216.j7TCGsss026612@app.auscert.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <200508291216.j7TCGsss026612@app.auscert.org.au> User-Agent: mutt-ng/devel (FreeBSD) Subject: Re: Incorrect super block--help! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 12:46:13 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Aug 29, 2005 at 10:16:54PM +1000, freebsd-stable@auscert.org.au wrote: > > Hey, newb BSDer here with a question > > > > I've got a brand new 5.4 install. I'm trying to mount the CDROM. As root, > > I type: > > > > mount /dev/acd0 /cdrom > > > > and I get "incorrect super block" error message after a bit of CD activity, > > and no mount. I've tried a CD-RW I burned (the FreeBSD install disk I > > installed from) and an old copy of SimCity 2000, neither worked, same error > > message. > > > > I'm stuck. Any ideas? The real stupid question (brought on by another post that suggested using -t 9660 or whatever it is, I just use mount_cd9660) Is it shown in /etc/fstab--that is, do you have a line in /etc/fstab something like /dev/acd0 /cdrom cd9660 ro, noauto 0 0 The answer is probably yes, but if not, that would be the issue and you'd need to use mount_cd9660 rather than mount. - -- Scott Robbins GPG KeyID EB3467D6 ( 1B848 077D 66F6 9DB0 FDC2 A409 FA54 D575 EB34 67D6) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Faith: You can't trust guys. Buffy: You can trust some guys. Really, I've read about them. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDEwNJ+lTVdes0Z9YRAmFwAJ4tFc0CRLiT5gcupEy5vpEqSH6l6ACfTYe9 6S4CGw7Hqz8KA7IY9c/7qaE= =AQVp -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 12:58:37 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8624616A420 for ; Mon, 29 Aug 2005 12:58:37 +0000 (GMT) (envelope-from freebsd-stable@auscert.org.au) Received: from titania.auscert.org.au (gw.auscert.org.au [203.5.112.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBB1143D45 for ; Mon, 29 Aug 2005 12:58:36 +0000 (GMT) (envelope-from freebsd-stable@auscert.org.au) Received: from app.auscert.org.au (app [10.0.1.192]) by titania.auscert.org.au (8.12.10/8.12.10) with ESMTP id j7TCwYBV005766 for ; Mon, 29 Aug 2005 22:58:34 +1000 (EST) Received: from app.auscert.org.au (localhost.auscert.org.au [127.0.0.1]) by app.auscert.org.au (8.13.1/8.13.1) with ESMTP id j7TCwZIx032432 for ; Mon, 29 Aug 2005 22:58:35 +1000 (EST) (envelope-from freebsd-stable@auscert.org.au) Message-Id: <200508291258.j7TCwZIx032432@app.auscert.org.au> To: freebsd-stable@freebsd.org from: freebsd-stable@auscert.org.au In-Reply-To: Your message of "Mon, 29 Aug 2005 07:15:14 EST." <4312FC52.3070308@iaces.com> Date: Mon, 29 Aug 2005 22:58:35 +1000 Subject: Re: Incorrect super block--help! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 12:58:37 -0000 > You're trying to mount it as a rw disc and as a UFS file system > > mount -r -t cd9660 /dev/acd0 /cdrom > > Mark Space wrote: > > Hey, newb BSDer here with a question > > > > I've got a brand new 5.4 install. I'm trying to mount the CDROM. As > > root, I type: > > > > mount /dev/acd0 /cdrom > > Of course, this is dead right and ignore my previous response. You'll find that the cdrom drive is almost certainly in /etc/fstab as the other responder mentioned - to mount it with the default fstab options (which should work just fine): mount /cdrom The way you tried will indeed attempt to mount the device by default as a rw UFS file system. Sorry for the wrong steer. joel From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 18:36:45 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C3C716A426 for ; Mon, 29 Aug 2005 18:36:45 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08BC043D45 for ; Mon, 29 Aug 2005 18:36:44 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id j7TIaVEk013147; Mon, 29 Aug 2005 11:36:35 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200508291836.j7TIaVEk013147@gw.catspoiler.org> Date: Mon, 29 Aug 2005 11:36:31 -0700 (PDT) From: Don Lewis To: mkb@incubus.de In-Reply-To: <20050829120415.GA1462@drjekyll.mkbuelow.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-stable@FreeBSD.org, dinom@balstonresearch.com, markir@paradise.net.nz Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 18:36:45 -0000 On 29 Aug, Matthias Buelow wrote: > Mark Kirkwood wrote: > >>>>FreeBSD's filesystems are very robust should you lose power. >>>This sentence is completely bogus (or at best: wishful thinking) >>>and should be deleted. >>It's probably correct if you have hw.ata.wc=0 (and are using IDE drives >>obviously). > > I'd like to stress the "probably". I've already seen unrepairable > filesystem corruption with softupdates enabled in the past with > "good" scsi disks at power loss. Did you remember to disable write caching by setting the WCE mode page bit to zero? At least with SCSI, it doesn't seem to affect performance under most workloads. > In addition, with > softupdates there seems to be a much higher probability of losing > files, as I have observed.. that is, getting them zero-truncated, > or even deleted (which shouldn't happen in that scenario, I'm sure > I've seen the results of a bug), than without. I've seen this when doing compile, run, panic experiments. The executable that I just compiled would end up with a size of zero after the reboot because it was still cached in RAM and executing from RAM when the machine paniced. The executable was scheduled to be written to disk about 30 seconds after it was compiled and linked, but the machine paniced before the 30 seconds was up. Softupdates only tries to guarantee that the on-disk file system is in a consistent state at all times, with the possible exception that not all space may be accounted for. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 18:59:39 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2F2816A420; Mon, 29 Aug 2005 18:59:39 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51F4443D46; Mon, 29 Aug 2005 18:59:39 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AA805F.dip0.t-ipconnect.de [84.170.128.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id F23B635876; Mon, 29 Aug 2005 21:02:26 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j7TIxZxn002888; Mon, 29 Aug 2005 20:59:35 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j7TIxYE5002887; Mon, 29 Aug 2005 20:59:34 +0200 (CEST) (envelope-from mkb) Date: Mon, 29 Aug 2005 20:59:33 +0200 From: Matthias Buelow To: Don Lewis Message-ID: <20050829185933.GB1462@drjekyll.mkbuelow.net> References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200508291836.j7TIaVEk013147@gw.catspoiler.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, dinom@balstonresearch.com, markir@paradise.net.nz Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 18:59:39 -0000 Don Lewis wrote: >> I'd like to stress the "probably". I've already seen unrepairable >> filesystem corruption with softupdates enabled in the past with >> "good" scsi disks at power loss. > >Did you remember to disable write caching by setting the WCE mode page >bit to zero? At least with SCSI, it doesn't seem to affect performance >under most workloads. No.. I thought that with SCSI it is "ok" to leave the cache enabled because SCSI supports some sort of request queueing which doesn't break the order established by softupdates? >I've seen this when doing compile, run, panic experiments. The >executable that I just compiled would end up with a size of zero after >the reboot because it was still cached in RAM and executing from RAM >when the machine paniced. The executable was scheduled to be written to >disk about 30 seconds after it was compiled and linked, but the machine >paniced before the 30 seconds was up. Yes, that would account for the 0-size files but not for ones that got deleted by background fsck, with it logging "UNREF FILE" messages (and that were files that have definitely NOT had directory entries removed since amongst those were dot-files in my homedir, which I had to restore from backup then, and some others where I have not yet found out which they were..) >Softupdates only tries to guarantee that the on-disk file system is in a >consistent state at all times, with the possible exception that not all >space may be accounted for. It doesn't try very hard, though, nor is it very successful. mkb. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 19:32:47 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B22CE16A41F; Mon, 29 Aug 2005 19:32:47 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47AC143D45; Mon, 29 Aug 2005 19:32:47 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 845FD5F62; Mon, 29 Aug 2005 15:32:46 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08337-09; Mon, 29 Aug 2005 15:32:45 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-79-217.ny325.east.verizon.net [68.161.79.217]) by pi.codefab.com (Postfix) with ESMTP id 8943F5F4C; Mon, 29 Aug 2005 15:32:44 -0400 (EDT) Message-ID: <431362ED.9030800@mac.com> Date: Mon, 29 Aug 2005 15:33:01 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthias Buelow References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> In-Reply-To: <20050829185933.GB1462@drjekyll.mkbuelow.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: Don Lewis , freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 19:32:47 -0000 Matthias Buelow wrote: > Don Lewis wrote: [ ... ] >> Did you remember to disable write caching by setting the WCE mode page >> bit to zero? At least with SCSI, it doesn't seem to affect performance >> under most workloads. > > No.. I thought that with SCSI it is "ok" to leave the cache enabled > because SCSI supports some sort of request queueing which doesn't > break the order established by softupdates? That gives you the ability to sequence events, yes, but it doesn't mean that data which has been cached by the drive and not yet written out is fine if the power goes away. Good SCSI/RAID controllers have a small battery backup inside the computer case to address exactly this: aac0: mem 0xf0000000-0xf7ffffff irq 31 at device 2.1 on pci2 aac0: i960RX 100MHz, 118MB cache memory, optional battery present aac0: Kernel 2.5-0, Build 2991, S/N xxxxx That cache will get flushed to disk even if the OS goes bonkers or disappears entirely due to no power. Maybe something like this would make you happier: # cat >> /etc/sysctl.conf kern.filedelay=7 kern.dirdelay=6 kern.metadelay=5 ...? >> Softupdates only tries to guarantee that the on-disk file system is in a >> consistent state at all times, with the possible exception that not all >> space may be accounted for. > > It doesn't try very hard, though, nor is it very successful. Look, there is a tradeoff between price/performance/quality (or reliability) in most circumstances. If you want more reliability, pay more to get good hardware, or accept that there will be performance loss if/when you choose to maximize reliability. It's also true that FreeBSD could do a better job or otherwise be improved. You don't have to argue that point, we're already convinced. Submitting improvements is useful. Would changing the sysctls above to shorter defaults be a good idea? -- -Chuck PS: Haven't we had this conversation before? From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 20:10:36 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AB2B16A41F for ; Mon, 29 Aug 2005 20:10:36 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B67A43D46 for ; Mon, 29 Aug 2005 20:10:34 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A4390.dip.t-dialin.net [84.154.67.144]) (authenticated bits=0) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id j7TKAVxr015558 for ; Mon, 29 Aug 2005 22:10:32 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id j7TKAULT013091 for ; Mon, 29 Aug 2005 22:10:30 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id j7TKB3eP022216 for ; Mon, 29 Aug 2005 22:11:03 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Received: (from jhs@localhost) by fire.jhs.private (8.13.1/8.13.1/Submit) id j7TKB34Z022215; Mon, 29 Aug 2005 22:11:03 +0200 (CEST) (envelope-from jhs) Date: Mon, 29 Aug 2005 22:11:03 +0200 (CEST) Message-Id: <200508292011.j7TKB34Z022215@fire.jhs.private> To: freebsd-stable@freebsd.org From: "Julian Stacey" Organization: http://berklix.com Munich Unix, BSD, Internet Consultancy Fcc: sent-mail User-agent: EXMH http://beedub.com/exmh/ on FreeBSD http://freebsd.org X-URL: http://berklix.com/~jhs/ Subject: 6.0-BETA3 nfs mount of 5.3 hangs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 20:10:36 -0000 Since I upgraded my laptop from 5.3 to 6.0-BETA3 it's doing a lot of hangs on NFS in both directions. Anyone else noticing this ? The laptop is OK when running a 5.3 partition. I'm running AMD on all hosts. I'm about to run mergemaster -sicv to upgrade my /etc from 5.3 to 6.0-BETA3, meanwhile ... ps -laxww | grep nfs 0 49 0 0 8 0 0 8 - SL ?? 0:00.00 [nfsiod 0] 0 50 0 2 8 0 0 8 - IL ?? 0:00.00 [nfsiod 1] 0 51 0 2 8 0 0 8 - IL ?? 0:00.00 [nfsiod 2] 0 52 0 2 8 0 0 8 - IL ?? 0:00.00 [nfsiod 3] 0 580 1 147 114 0 1344 1012 select Is ?? 0:00.06 nfsd: master (nfsd) 0 582 580 0 4 0 1252 844 - I ?? 0:00.01 nfsd: server (nfsd) 0 583 580 104 4 0 1252 844 - I ?? 0:00.00 nfsd: server (nfsd) 0 584 580 104 4 0 1252 844 - I ?? 0:00.00 nfsd: server (nfsd) 0 585 580 147 4 0 1252 844 - I ?? 0:00.00 nfsd: server (nfsd) -- Julian Stacey Muenchner Unix Urlaubs Vertretung http://berklix.com Mail Ascii not HTML. Ihr Rauch = mein allergischer Kopfschmerzen. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 20:30:26 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2444216A41F for ; Mon, 29 Aug 2005 20:30:26 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5601A43D55 for ; Mon, 29 Aug 2005 20:30:25 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id j7TKU8va013397; Mon, 29 Aug 2005 13:30:12 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200508292030.j7TKU8va013397@gw.catspoiler.org> Date: Mon, 29 Aug 2005 13:30:08 -0700 (PDT) From: Don Lewis To: mkb@incubus.de In-Reply-To: <20050829185933.GB1462@drjekyll.mkbuelow.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-stable@FreeBSD.org, dinom@balstonresearch.com, markir@paradise.net.nz Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 20:30:26 -0000 On 29 Aug, Matthias Buelow wrote: > Don Lewis wrote: > >>> I'd like to stress the "probably". I've already seen unrepairable >>> filesystem corruption with softupdates enabled in the past with >>> "good" scsi disks at power loss. >> >>Did you remember to disable write caching by setting the WCE mode page >>bit to zero? At least with SCSI, it doesn't seem to affect performance >>under most workloads. > > No.. I thought that with SCSI it is "ok" to leave the cache enabled > because SCSI supports some sort of request queueing which doesn't > break the order established by softupdates? If WCE is set to 1, the drive immediately acknowledges writes. If WCE is set to 0 and the OS is doing tagged command queuing, the drive won't tell the OS that the write is complete until the data hits the platter, but a typical drive could have up to about 64 outstanding writes (or some combination of reads and writes) that it is free to re-order as it sees fit in order to increase performance. The key is that WCE must be set to 0 so that softupdates knows when each of the writes that it has queued to the drive has completed so that softupdates doesn't queue up any writes that depend on the previously queued writes before those older writes have reached stable storage. If WCE is set to 1, the dependent writes could reach the platter too early and the earlier writes that the later writes depend on could be lost from the drive's cache because of a power failure, which would put the file system into an inconsistent state. >>I've seen this when doing compile, run, panic experiments. The >>executable that I just compiled would end up with a size of zero after >>the reboot because it was still cached in RAM and executing from RAM >>when the machine paniced. The executable was scheduled to be written to >>disk about 30 seconds after it was compiled and linked, but the machine >>paniced before the 30 seconds was up. > > Yes, that would account for the 0-size files but not for ones that > got deleted by background fsck, with it logging "UNREF FILE" messages > (and that were files that have definitely NOT had directory entries > removed since amongst those were dot-files in my homedir, which I > had to restore from backup then, and some others where I have not > yet found out which they were..) I believe I've seen UNREF'ed files, but they always seem to be compiler temporaries, etc. I've never lost any files that I haven't recently touched. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 20:45:10 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1BCE16A41F for ; Mon, 29 Aug 2005 20:45:09 +0000 (GMT) (envelope-from kensmith@FreeBSD.org) Received: from bloom.cse.buffalo.edu (bloom.cse.Buffalo.EDU [128.205.32.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 970BC43D48 for ; Mon, 29 Aug 2005 20:45:09 +0000 (GMT) (envelope-from kensmith@FreeBSD.org) Received: from bloom.cse.buffalo.edu (localhost.cse.buffalo.edu [127.0.0.1]) by bloom.cse.buffalo.edu (8.13.3/8.12.4) with ESMTP id j7TKj8TD026971 for ; Mon, 29 Aug 2005 16:45:08 -0400 (EDT) Received: (from kensmith@localhost) by bloom.cse.buffalo.edu (8.13.3/8.13.1/Submit) id j7TKj8DS026970 for freebsd-stable@freebsd.org; Mon, 29 Aug 2005 16:45:08 -0400 (EDT) (envelope-from kensmith) Date: Mon, 29 Aug 2005 16:45:08 -0400 From: Ken Smith To: freebsd-stable@freebsd.org Message-ID: <20050829204508.GA26955@bloom.cse.buffalo.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: FreeBSD 6.0-BETA3 Available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 20:45:10 -0000 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline [ Sorry - I could have sworn I sent this earlier... ] Announcement ------------ The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 6.0-BETA3. This BETA includes a full set of packages for amd64 and i386 architectures. Alpha has no packages, sparc64 has everything except for KDE and Gnome. The FTP install trees are available. We encourage people to help with testing so any final bugs can be identified and worked out. Availability of ISO images is given below. If you have an older system you want to update using the normal CVS/cvsup source based upgrade the branch tag to use is RELENG_6 (though that will change for the Release Candidates later). Problem reports can be submitted using the send-pr(1) command. The list of open issues and things still being worked on are on the todo list: http://www.freebsd.org/releases/6.0R/todo.html Since this is the first release of a new branch we only have a rough idea for some of the dates. The current rough schedule is available but most dates are still listed as "TBD - To Be Determined": http://www.freebsd.org/releases/6.0R/schedule.html Known Issues ------------ Other than the items listed in the todo list there are no known issues with this BETA. Availability ------------ The BETA3 ISOs are available on most of the FreeBSD Mirror sites. A list of the mirror sites is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html The MD5s are: MD5 (6.0-BETA3-alpha-bootonly.iso) = 7c07c44ff946657440c981455872bab5 MD5 (6.0-BETA3-alpha-disc1.iso) = bf92a2acaa622d23ae6a2f422d34d5ed MD5 (6.0-BETA3-amd64-bootonly.iso) = 45334997ac1ee50dd57be1c439fd1122 MD5 (6.0-BETA3-amd64-disc1.iso) = 7d566188eb66b7588a4ded72d55251c6 MD5 (6.0-BETA3-amd64-disc2.iso) = 84d68c5a90b9eff57ca19d3109966fac MD5 (6.0-BETA3-i386-bootonly.iso) = a917645b25f6d1661cf4e4a030d12eb5 MD5 (6.0-BETA3-i386-disc1.iso) = 1051a03b5d8c43baef907d92147fac9c MD5 (6.0-BETA3-i386-disc2.iso) = f203a81690224ffa7d727fc7b27d5f40 MD5 (6.0-BETA3-ia64-bootonly.iso) = 0986d84103b1d2b51ba988fe50dc8133 MD5 (6.0-BETA3-ia64-disc1.iso) = 05e43d428c94e7dfc2cc00c1e8fb063f MD5 (6.0-BETA3-ia64-livefs.iso) = 2b21241804cff376dce72e2ac7d262cd MD5 (6.0-BETA3-pc98-disc1.iso) = b5b8ff7b8fa3b8cdd38046e23cd272d6 MD5 (6.0-BETA3-powerpc-disc1.iso) = ef468b6843fcd8b06818a5a4d246b09f MD5 (6.0-BETA3-sparc64-bootonly.iso) = 5b27730bc310b7fea5d306f23d069c24 MD5 (6.0-BETA3-sparc64-disc1.iso) = 69eab8d48435de2a5448f7e64e984c43 MD5 (6.0-BETA3-sparc64-disc2.iso) = 64401437f91b1c086e3518ee2ff90a8f -ken --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDE3PS/G14VSmup/YRAhMQAJ9ZDv/nRgEsaDtMbBdSH56h0PDSrgCeMPSk ZXfU4z4XDf3mdhs5h9R9AVQ= =PTLa -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV-- From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 20:47:14 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E770F16A41F; Mon, 29 Aug 2005 20:47:14 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 777EA43D45; Mon, 29 Aug 2005 20:47:14 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AA805F.dip0.t-ipconnect.de [84.170.128.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 5AD3535876; Mon, 29 Aug 2005 22:50:06 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j7TKlFuB003421; Mon, 29 Aug 2005 22:47:15 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j7TKlFLm003420; Mon, 29 Aug 2005 22:47:15 +0200 (CEST) (envelope-from mkb) Date: Mon, 29 Aug 2005 22:47:14 +0200 From: Matthias Buelow To: Chuck Swiger Message-ID: <20050829204714.GC1462@drjekyll.mkbuelow.net> References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <431362ED.9030800@mac.com> User-Agent: Mutt/1.4.2.1i Cc: Don Lewis , freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 20:47:15 -0000 Chuck Swiger wrote: >PS: Haven't we had this conversation before? Yes, indeed, and I don't want to reopen that issue since that would lead to no new insights (and since I don't have the time atm. to contribute anything I couldn't provide any stuff myself). I was just refuting the claim of "very robust" filesystem when power goes out in the context of 200GB consumer-grade hardware that this thread was talking about. I think until a satisfactory solution can be found (by making softupdates and/or a journalled filesystem as reliable as possible through mechanisms like write-request barriers and appropriate flushing at these) users who're running FreeBSD on end-consumer hardware (desktop PC as workstation or personal server) should be warned that softupdates does NOT work as described on their hardware and that the filesystem can easily be corrupted when the power goes out, no matter if softupdates is enabled or not. One often sees the "softupdates" argument being fielded by FreeBSD advocates, typically against Linux users with journalled fs, on web forums, usenet and other less authoritative (and knowledgable) places of discussion, and it is often presented as if it were some kind of magic bullet that makes filesystem corruption impossible. This simply is not so. mkb. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 21:15:27 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 860A716A41F for ; Mon, 29 Aug 2005 21:15:27 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1779B43D48 for ; Mon, 29 Aug 2005 21:15:27 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 66C735F54; Mon, 29 Aug 2005 17:15:26 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16605-06; Mon, 29 Aug 2005 17:15:22 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-79-217.ny325.east.verizon.net [68.161.79.217]) by pi.codefab.com (Postfix) with ESMTP id 099785C74; Mon, 29 Aug 2005 17:15:21 -0400 (EDT) Message-ID: <43137AFB.9060304@mac.com> Date: Mon, 29 Aug 2005 17:15:39 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthias Buelow References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> <20050829204714.GC1462@drjekyll.mkbuelow.net> In-Reply-To: <20050829204714.GC1462@drjekyll.mkbuelow.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 21:15:27 -0000 Matthias Buelow wrote: > Chuck Swiger wrote: >>PS: Haven't we had this conversation before? > > Yes, indeed, and I don't want to reopen that issue since that would > lead to no new insights (and since I don't have the time atm. to > contribute anything I couldn't provide any stuff myself). Yet you seem willing to spend time discussing the matter...? > I was just refuting the claim of "very robust" filesystem when power goes > out in the context of 200GB consumer-grade hardware that this thread > was talking about. Most of the time, a FreeBSD system will come back up without losing data older than about thirty seconds, and that is tunable. Have you even tried to change the syncer sysctls I mentioned? > I think until a satisfactory solution can be > found (by making softupdates and/or a journalled filesystem as > reliable as possible through mechanisms like write-request barriers > and appropriate flushing at these) users who're running FreeBSD on > end-consumer hardware (desktop PC as workstation or personal server) > should be warned that softupdates does NOT work as described on > their hardware and that the filesystem can easily be corrupted when > the power goes out, no matter if softupdates is enabled or not. Great. I think "man ata" already says exactly this: hw.ata.wc set to 1 to enable Write Caching, 0 to disable (default is enabled). WARNING: can cause data loss on power failures. If your hard drive no longer works correctly when write-caching is disabled, it's defective. Nothing FreeBSD or any other system can do is going to change that. > One often sees the "softupdates" argument being fielded by FreeBSD > advocates, typically against Linux users with journalled fs, on web > forums, usenet and other less authoritative (and knowledgable) > places of discussion, and it is often presented as if it were some > kind of magic bullet that makes filesystem corruption impossible. "Often?" Strawman test: can you point out 3 examples by message-id or URL? And if you prefer to run a journalled filesystem under Linux instead of softupdates under FreeBSD, by all means, do whatever makes you happy. > This simply is not so. Very good. -- -Chuck PS: I don't want a thread to end on a negative note. It would be useful if FreeBSD had a more adaptable method for dealing with drive power management and caching; in particular, for laptops it might be nice to cache data for much longer-- perhaps even hours-- if nothing fsync()s, in order to permit the drive to spin down. (This is something both Windows and MacOS X are learning to do pretty well.) From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 21:23:14 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C702016A41F for ; Mon, 29 Aug 2005 21:23:14 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from audi.websitewelcome.com (audi.websitewelcome.com [67.19.210.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F83C43D70 for ; Mon, 29 Aug 2005 21:23:09 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from adsl-065-013-105-239.sip.tys.bellsouth.net ([65.13.105.239]:1471 helo=[192.168.1.33]) by audi.websitewelcome.com with esmtpa (Exim 4.52) id 1E9r5o-0000M3-O2; Mon, 29 Aug 2005 16:23:00 -0500 Message-ID: <43137CDC.6050604@goldsword.com> Date: Mon, 29 Aug 2005 17:23:40 -0400 From: "J. T. Farmer" Organization: GoldSword Systems User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.11) Gecko/20050728 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chuck Swiger References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> <20050829204714.GC1462@drjekyll.mkbuelow.net> <43137AFB.9060304@mac.com> In-Reply-To: <43137AFB.9060304@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - audi.websitewelcome.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - goldsword.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-stable@freebsd.org, Matthias Buelow Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 21:23:14 -0000 Chuck Swiger wrote: > Matthias Buelow wrote: > >> Chuck Swiger wrote: >> >>> PS: Haven't we had this conversation before? >> >> >> Yes, indeed, and I don't want to reopen that issue since that would >> lead to no new insights (and since I don't have the time atm. to >> contribute anything I couldn't provide any stuff myself). > > > Yet you seem willing to spend time discussing the matter...? Chuck, Matthias went on to say in a very simple manner by he thought a quick note was warranted. You don't agree. Why don't the two of you talk about it in private email? Matthias is right. It's been hashed out on the lists multiple times and neither side is willing to change. At this point, it's become a "Did to! Did not! Did to...." argument between children. So like good children, go to your rooms and don't bother Mommy... John ---------------------------------------------------------------------- John T. Farmer Owner & CTO GoldSword Systems jfarmer@goldsword.com 865-691-6498 Knoxville TN Consulting, Design, & Development of Networks & Software From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 21:48:30 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D27DA16A41F for ; Mon, 29 Aug 2005 21:48:30 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64E8E43D48 for ; Mon, 29 Aug 2005 21:48:30 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id ADFBE5F6B; Mon, 29 Aug 2005 17:48:29 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16856-08; Mon, 29 Aug 2005 17:48:27 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-79-217.ny325.east.verizon.net [68.161.79.217]) by pi.codefab.com (Postfix) with ESMTP id 1DEB25D33; Mon, 29 Aug 2005 17:48:27 -0400 (EDT) Message-ID: <431382BC.9090406@mac.com> Date: Mon, 29 Aug 2005 17:48:44 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "J. T. Farmer" References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> <20050829204714.GC1462@drjekyll.mkbuelow.net> <43137AFB.9060304@mac.com> <43137CDC.6050604@goldsword.com> In-Reply-To: <43137CDC.6050604@goldsword.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: freebsd-stable@freebsd.org, Matthias Buelow Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 21:48:30 -0000 J. T. Farmer wrote: > Chuck Swiger wrote: >> Matthias Buelow wrote: >>> Yes, indeed, and I don't want to reopen that issue since that would >>> lead to no new insights (and since I don't have the time atm. to >>> contribute anything I couldn't provide any stuff myself). >> >> Yet you seem willing to spend time discussing the matter...? > > Matthias went on to say in a very simple manner by he thought > a quick note was warranted. You don't agree. I think this matter is documented now. I think it could be documented elsewhere or in more detail if someone wanted to do so, but that involves someone pointing to a specific manpage or section of the handbook, and submitting language. The people on freebsd-doc can help, deal with mdoc or Docbook formatting, etc. > Why don't the two of you talk about it in private email? I am willing to end the discussion if there is nothing productive to say. > Matthias is right. Matthias is right about what? My goodness, you also are aware of people talking about softupdates in comparison to journalled filesystems often? > It's been hashed out on the lists multiple times and > neither side is willing to change. I've suggested a change to the sysctl's governing the syncer's timing, which ought to have a noticable impact on the issues Matthias has brought up. Feedback is welcome. (I generally am happy to look into changes and see if they are improvements.) > At this point, it's become a "Did to! Did not! Did to...." argument > between children. So like good children, go to your rooms and don't > bother Mommy... You're awarded -1 karma for the patronizing tone. Feel free to read other threads if you don't like what I have to say. -- -Chuck PS: Please refrain from stating my position for me, JT. I'd be happier if you quoted what I said and disagreed honestly with it. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 21:56:14 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56A0316A41F for ; Mon, 29 Aug 2005 21:56:14 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF6E143D46 for ; Mon, 29 Aug 2005 21:56:13 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AA805F.dip0.t-ipconnect.de [84.170.128.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 7641F35876; Mon, 29 Aug 2005 23:59:05 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j7TLuEIE003707; Mon, 29 Aug 2005 23:56:14 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j7TLuEV5003706; Mon, 29 Aug 2005 23:56:14 +0200 (CEST) (envelope-from mkb) Date: Mon, 29 Aug 2005 23:56:13 +0200 From: Matthias Buelow To: Chuck Swiger Message-ID: <20050829215613.GD1462@drjekyll.mkbuelow.net> References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> <20050829204714.GC1462@drjekyll.mkbuelow.net> <43137AFB.9060304@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43137AFB.9060304@mac.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 21:56:14 -0000 Chuck Swiger wrote: >Yet you seem willing to spend time discussing the matter...? Because it's somewhat of my pet peeve and I always see the mantra-like repetition of the argument that "you have to disable the write-back cache if you want any safety at all", which is a) extremely disadvantageous with today's IDE/SATA drives and hardly feasible in reality, and b) other systems like Windows and Linux can operate much safer with the cache _enabled_, on most drives except the most pathetic ones which are totally broken. >>One often sees the "softupdates" argument being fielded by FreeBSD >>advocates, typically against Linux users with journalled fs, on web >>forums, usenet and other less authoritative (and knowledgable) >>places of discussion, and it is often presented as if it were some >>kind of magic bullet that makes filesystem corruption impossible. > >"Often?" Strawman test: can you point out 3 examples by message-id or URL? A Google search finds them quickly: http://www.heise.de/ix/foren/go.shtml?read=1&msg_id=7335045&forum_id=70615 (german, argument is that "softupdates is at least a match for a journalled fs"), http://lists.freebsd.org/pipermail/freebsd-questions/2003-June/009967.html ("FS + SoftUpdates is much better than journaling!") http://aussatz.antville.org/topics/HowTos/ (german, argument is "1. practically nothing can break when power goes out", and even that you can switch off the machine without any problems, except for losing the files that have been written to in the last seconds. Of course no mentioning of disk cache or any sophistication whatever.) >And if you prefer to run a journalled filesystem under Linux instead of >softupdates under FreeBSD, by all means, do whatever makes you happy. I don't want to do that (that is, I do want that, of course, if I'm using Linux, but in general I don't care about Linux). The point is, that both Windows and recent Linux make great effort to ensure filesystem correctness by using request barriers and clever flushing, or even complete disabling/reenabling of the cache at these barrier points, even on consumer-grade hardware. While with FreeBSD, the attitude generally seems to be a snobby "here's a dime, kid, go buy yourself a real computer". That might work for server hardware but for the typical PC, which is a commodity product, and where one often cannot even select the hardware (be it because your employer puts the machine in your office, or you just order some machine somewhere because tinkering with components until a PC works flawlessly has become a royal PITA and waste of time) and so the operating system generally has to work with "normal" off-the-shelf hardware, which means, cheap IDE/SATA stuff, and not a super-expensive battery-backed U320 SCSI-RAID with a gratis golden Rolex and 1-year free membership in the Dubai Nad al-Sheba golf club. >PS: I don't want a thread to end on a negative note. It would be useful if >FreeBSD had a more adaptable method for dealing with drive power management >and caching; in particular, for laptops it might be nice to cache data for >much longer-- perhaps even hours-- if nothing fsync()s, in order to permit >the drive to spin down. My notebook lies to me everytime when the battery is going to be out of juice soon (one of the reason I experience powerouts frequently, when I don't pay attention), so that seems to be somewhat unreliable to me.. mkb. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 22:47:49 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAC5816A41F for ; Mon, 29 Aug 2005 22:47:49 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E98543D45 for ; Mon, 29 Aug 2005 22:47:49 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id B1CE45CEA; Mon, 29 Aug 2005 18:47:48 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17107-06; Mon, 29 Aug 2005 18:47:43 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-79-217.ny325.east.verizon.net [68.161.79.217]) by pi.codefab.com (Postfix) with ESMTP id 5CD755C68; Mon, 29 Aug 2005 18:47:43 -0400 (EDT) Message-ID: <431390A0.5080007@mac.com> Date: Mon, 29 Aug 2005 18:48:00 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthias Buelow References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> <20050829204714.GC1462@drjekyll.mkbuelow.net> <43137AFB.9060304@mac.com> <20050829215613.GD1462@drjekyll.mkbuelow.net> In-Reply-To: <20050829215613.GD1462@drjekyll.mkbuelow.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 22:47:50 -0000 Matthias Buelow wrote: > Chuck Swiger wrote: >> Yet you seem willing to spend time discussing the matter...? > > Because it's somewhat of my pet peeve and I always see the mantra-like > repetition of the argument that "you have to disable the write-back > cache if you want any safety at all", No, there are other possible solutions which have been mentioned. I reiterate my question: have you tried adjusting the syncer sysctl's and seeing whether FreeBSD is more stable in the event of a power failure? [ ... ] >>>One often sees the "softupdates" argument being fielded by FreeBSD >>>advocates, typically against Linux users with journalled fs, on web >>>forums, usenet and other less authoritative (and knowledgable) >>>places of discussion, and it is often presented as if it were some >>>kind of magic bullet that makes filesystem corruption impossible. >> >>"Often?" Strawman test: can you point out 3 examples by message-id or URL? > > A Google search finds them quickly: > > http://www.heise.de/ix/foren/go.shtml?read=1&msg_id=7335045&forum_id=70615 > (german, argument is that "softupdates is at least a match for a > journalled fs"), > > http://lists.freebsd.org/pipermail/freebsd-questions/2003-June/009967.html > ("FS + SoftUpdates is much better than journaling!") > > http://aussatz.antville.org/topics/HowTos/ > (german, argument is "1. practically nothing can break when power > goes out", and even that you can switch off the machine without any > problems, except for losing the files that have been written to in > the last seconds. Of course no mentioning of disk cache or any > sophistication whatever.) Conclusion: if you're looking for unbridled FreeBSD advocacy on these lists or in the FreeBSD documentation, you've found very little. A one-line post from 2003: gosh, someone expressed a strong opinion, and even that was promptly followed up with: > FFS+SU does have the disadvantages that a full fsck is still needed > (run in the background), and you risk losing the last `sysctl > kern.metadelay` seconds worth of files written just before a crash. ...by Dan Nelson. I'm going to skip the rest of the monologue and the Dubai Nad al-Sheba golf club as well, but thanks anyway. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 22:56:28 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFD1916A41F for ; Mon, 29 Aug 2005 22:56:28 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86E0443D49 for ; Mon, 29 Aug 2005 22:56:28 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j7TMuNrS081782; Mon, 29 Aug 2005 17:56:23 -0500 (CDT) (envelope-from dan) Date: Mon, 29 Aug 2005 17:56:23 -0500 From: Dan Nelson To: Jason Message-ID: <20050829225623.GC1476@dan.emsphone.com> References: <20050826120500.GA8907@thevoid.delnoch.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050826120500.GA8907@thevoid.delnoch.net> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.9i Cc: freebsd-stable@freebsd.org Subject: Re: pcap and gig speeds. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 22:56:29 -0000 In the last episode (Aug 26), Jason said: > We are planning on updating a number of old machines, being used as > IDS sensors, and in the past, there has been a known issue regarding > gig speeds and pcap with regards to snort. Do you have an URL referring to the issue? As long as your pcap buffers are big enough and your machine can handle snort's CPU load I don't see a problem. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 00:20:52 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC44D16A41F for ; Tue, 30 Aug 2005 00:20:52 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5802143D46 for ; Tue, 30 Aug 2005 00:20:52 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AA805F.dip0.t-ipconnect.de [84.170.128.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id CA0A535876; Tue, 30 Aug 2005 02:23:43 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j7U0Kqil004159; Tue, 30 Aug 2005 02:20:53 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j7U0Kpkr004158; Tue, 30 Aug 2005 02:20:51 +0200 (CEST) (envelope-from mkb) Date: Tue, 30 Aug 2005 02:20:51 +0200 From: Matthias Buelow To: Chuck Swiger Message-ID: <20050830002051.GE1462@drjekyll.mkbuelow.net> References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> <20050829204714.GC1462@drjekyll.mkbuelow.net> <43137AFB.9060304@mac.com> <20050829215613.GD1462@drjekyll.mkbuelow.net> <431390A0.5080007@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <431390A0.5080007@mac.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 00:20:52 -0000 Chuck Swiger wrote: >I reiterate my question: have you tried adjusting the syncer sysctl's and >seeing whether FreeBSD is more stable in the event of a power failure? No, simply because I have no machine at the moment for experimenting if it takes longer until it eats its filesystem. Besides, as I have said, it is not an acute problem for me at the moment and I was merely pointing out the inadequacy of talking about "robust filesystems" in the context of softupdates and end-consumer harddrives. mkb. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 00:45:52 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A88EA16A41F for ; Tue, 30 Aug 2005 00:45:52 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-5.paradise.net.nz (bm-5a.paradise.net.nz [202.0.58.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B5BE43D46 for ; Tue, 30 Aug 2005 00:45:52 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-3.paradise.net.nz (smtp-3a.paradise.net.nz [202.0.32.196]) by linda-5.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IM0008TFFGEHN@linda-5.paradise.net.nz> for freebsd-stable@freebsd.org; Tue, 30 Aug 2005 12:45:50 +1200 (NZST) Received: from [192.168.1.11] (218-101-13-128.paradise.net.nz [218.101.13.128]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id D9BD6AF0C7; Tue, 30 Aug 2005 12:42:54 +1200 (NZST) Date: Tue, 30 Aug 2005 12:42:53 +1200 From: Mark Kirkwood In-reply-to: <20050830002051.GE1462@drjekyll.mkbuelow.net> To: Matthias Buelow Message-id: <4313AB8D.4010807@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050726) References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> <20050829204714.GC1462@drjekyll.mkbuelow.net> <43137AFB.9060304@mac.com> <20050829215613.GD1462@drjekyll.mkbuelow.net> <431390A0.5080007@mac.com> <20050830002051.GE1462@drjekyll.mkbuelow.net> Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 00:45:52 -0000 Matthias Buelow wrote: > (snippage...) I was > merely pointing out the inadequacy of talking about "robust > filesystems" in the context of softupdates and end-consumer harddrives. > Would you be happy if the handbook section added a caution, or referred to the section that discusses the write cache? (FWIW - I have seen Linux + ext3 systems destroyed by power failure because the admins refused to disable write caching on ATA drives - Neither journelling or softupdates is much help if the HW is kidding you about write acknowledgment). Cheers Mark From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 00:54:19 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 746DB16A425 for ; Tue, 30 Aug 2005 00:54:19 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from riyal.ugcs.caltech.edu (riyal.ugcs.caltech.edu [131.215.176.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E9AB43D46 for ; Tue, 30 Aug 2005 00:54:19 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by riyal.ugcs.caltech.edu (Postfix, from userid 3640) id 74F3045804; Mon, 29 Aug 2005 17:54:17 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by riyal.ugcs.caltech.edu (Postfix) with ESMTP id 27DB845802; Mon, 29 Aug 2005 17:54:17 -0700 (PDT) Date: Mon, 29 Aug 2005 17:54:16 -0700 (PDT) From: Jon Dama To: Mark Kirkwood In-Reply-To: <4313AB8D.4010807@paradise.net.nz> Message-ID: References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> <20050829204714.GC1462@drjekyll.mkbuelow.net> <43137AFB.9060304@mac.com> <20050829215613.GD1462@drjekyll.mkbuelow.net> <431390A0.5080007@mac.com> <20050830002051.GE1462@drjekyll.mkbuelow.net> <4313AB8D.4010807@paradise.net.nz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org, Matthias Buelow Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 00:54:19 -0000 On Tue, 30 Aug 2005, Mark Kirkwood wrote: > (FWIW - I have seen Linux + ext3 systems destroyed by power failure > because the admins refused to disable write caching on ATA drives - > Neither journelling or softupdates is much help if the HW is kidding you > about write acknowledgment). This would certainly be case with 2.4 kernels and early 2.6 kernels. Afaik, they only made a decent attempt at solving this problem relatively recently. Ironically, phk backed out the underlying support for this safety fix from the FreeBSD kernel b.c. it wasn't integrated into the softupdates code whereas in reality the proper course of action would have been to hook it in. :-/ From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 00:57:54 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E54F16A41F for ; Tue, 30 Aug 2005 00:57:54 +0000 (GMT) (envelope-from robbak@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB93F43D45 for ; Tue, 30 Aug 2005 00:57:53 +0000 (GMT) (envelope-from robbak@gmail.com) Received: by wproxy.gmail.com with SMTP id 36so472254wra for ; Mon, 29 Aug 2005 17:57:53 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lHUjlcNlpVNfCubkj03kXCQM/mYtap7UkSBAdyeL95v1kedAdZoMJUxEf11Pn0rNISB8F03ObsTqRxzX4CUparPNDvM+KxHMcVoOaGRCT/x0I3iDFRupipJLXyCjrpBzQiAJJzVchzGYlxOSsxFzrVoS3CYx/NqyiuYQiW3Q6tI= Received: by 10.54.49.48 with SMTP id w48mr2489183wrw; Mon, 29 Aug 2005 17:57:53 -0700 (PDT) Received: by 10.54.128.12 with HTTP; Mon, 29 Aug 2005 17:57:53 -0700 (PDT) Message-ID: Date: Tue, 30 Aug 2005 10:57:53 +1000 From: Robert Backhaus To: Norberto Meijome In-Reply-To: <4312B091.9090104@meijome.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <55023220@srv.sem.ipt.ru> <20050828150947.GA58038@82-168-75-155-bbxl.xdsl.tiscali.nl> <4312B091.9090104@meijome.net> Cc: stable@freebsd.org Subject: Re: 6.0 and -O2 option X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 00:57:54 -0000 > > Kernel and world seem to be ok with -O2, for ports it is not advised. >=20 > Hi, > I may have missed a thread or something (just let me know :) ) - why is > -O2 not advised for ports on 6.0? > cheers, > Beto Simply because not every port works with -O2 optimisations. It caused bad code in some circumstances. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 01:11:08 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7721D16A41F for ; Tue, 30 Aug 2005 01:11:08 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BDC543D46 for ; Tue, 30 Aug 2005 01:11:07 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AA805F.dip0.t-ipconnect.de [84.170.128.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 6759435876; Tue, 30 Aug 2005 03:13:58 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j7U1B7IQ008615; Tue, 30 Aug 2005 03:11:07 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j7U1B6Gc008614; Tue, 30 Aug 2005 03:11:06 +0200 (CEST) (envelope-from mkb) Date: Tue, 30 Aug 2005 03:11:06 +0200 From: Matthias Buelow To: Mark Kirkwood Message-ID: <20050830011106.GF1462@drjekyll.mkbuelow.net> References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> <20050829204714.GC1462@drjekyll.mkbuelow.net> <43137AFB.9060304@mac.com> <20050829215613.GD1462@drjekyll.mkbuelow.net> <431390A0.5080007@mac.com> <20050830002051.GE1462@drjekyll.mkbuelow.net> <4313AB8D.4010807@paradise.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4313AB8D.4010807@paradise.net.nz> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 01:11:08 -0000 Mark Kirkwood wrote: >Would you be happy if the handbook section added a caution, or referred >to the section that discusses the write cache? Yes, that would inform the user. >(FWIW - I have seen Linux + ext3 systems destroyed by power failure >because the admins refused to disable write caching on ATA drives - >Neither journelling or softupdates is much help if the HW is kidding you >about write acknowledgment). >From what I understand from googling around on that issue, the write-barrier stuff should make that much more unlikely. Of course there could be the situation that it was a kernel that did not (properly) support write-barriers yet, or the Linux implementation has/had bugs (not too unlikely), or the disk was so broken that even the flushing workaround strategies were ignored or it otherwise didn't properly flush it, etc. But they're at least trying to cope with the issue. BTW., when have you last seen a broken NTFS? While I don't do Windows much, I have had quite a few crashes on Windows (2000, XP) over the years on various machines, and I always asked myself how it could be that the system is up almost immediately (probably due to log replay) with no discernible filesystem damage. Windows (NT) has been doing the write barrier flush tricks (disabling-/ reenabling the cache for flushing it) for longer than Linux and I would think that this contributes to the fault resilience of NTFS. Not that I would imply that NTFS can't be corrupted, of course. mkb. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 01:16:36 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D59916A41F for ; Tue, 30 Aug 2005 01:16:36 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 994ED43D69 for ; Tue, 30 Aug 2005 01:16:34 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from drjekyll.mkbuelow.net (p54AA805F.dip0.t-ipconnect.de [84.170.128.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id 325B235876; Tue, 30 Aug 2005 03:19:23 +0200 (CEST) Received: from drjekyll.mkbuelow.net (mkb@localhost.mkbuelow.net [127.0.0.1]) by drjekyll.mkbuelow.net (8.13.3/8.13.3) with ESMTP id j7U1GXQP008645; Tue, 30 Aug 2005 03:16:33 +0200 (CEST) (envelope-from mkb@drjekyll.mkbuelow.net) Received: (from mkb@localhost) by drjekyll.mkbuelow.net (8.13.3/8.13.3/Submit) id j7U1GXtg008644; Tue, 30 Aug 2005 03:16:33 +0200 (CEST) (envelope-from mkb) Date: Tue, 30 Aug 2005 03:16:32 +0200 From: Matthias Buelow To: Jon Dama Message-ID: <20050830011632.GG1462@drjekyll.mkbuelow.net> References: <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> <20050829204714.GC1462@drjekyll.mkbuelow.net> <43137AFB.9060304@mac.com> <20050829215613.GD1462@drjekyll.mkbuelow.net> <431390A0.5080007@mac.com> <20050830002051.GE1462@drjekyll.mkbuelow.net> <4313AB8D.4010807@paradise.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Mark Kirkwood Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 01:16:36 -0000 Jon Dama wrote: >Ironically, phk backed out the underlying support for this safety fix > from the FreeBSD kernel b.c. it wasn't integrated into the softupdates >code >whereas in reality the proper course of action would have been to hook it >in. :-/ Can it be put into softupdates at all? From what I understand (which is probably a rather sketchy idea of the matter), write barriers work because they are only used here to separate journal writes from data writes (i.e., to make sure the log is written, by flushing the cache, before any filesystem data hits the platters). I've read the softupdates paper some time ago and haven't found similar sequence points where one could insert such flushing. One would have to "flush" all the time, either continuously or in very short intervals, in order to keep the ordering, which then would amount to the same effects as if one simply disabled the cache. But probably I'm wrong here (I hope). mkb. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 01:52:57 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D267816A41F for ; Tue, 30 Aug 2005 01:52:57 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA77D43D45 for ; Tue, 30 Aug 2005 01:52:56 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (pool-141-152-80-192.roa.east.verizon.net [141.152.80.192]) by gromit.dlib.vt.edu (8.13.3/8.13.3) with ESMTP id j7U1qrcp021538 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 29 Aug 2005 21:52:54 -0400 (EDT) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (localhost.Chelsea-Ct.Org [127.0.0.1]) by zappa.Chelsea-Ct.Org (8.13.4/8.13.4) with ESMTP id j7U1qljB029428 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 29 Aug 2005 21:52:48 -0400 (EDT) (envelope-from paul@gromit.dlib.vt.edu) Received: (from paul@localhost) by zappa.Chelsea-Ct.Org (8.13.4/8.13.4/Submit) id j7U1qkow029427; Mon, 29 Aug 2005 21:52:46 -0400 (EDT) (envelope-from paul@gromit.dlib.vt.edu) From: Paul Mather To: Matthias Buelow In-Reply-To: <20050830011106.GF1462@drjekyll.mkbuelow.net> References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> <20050829204714.GC1462@drjekyll.mkbuelow.net> <43137AFB.9060304@mac.com> <20050829215613.GD1462@drjekyll.mkbuelow.net> <431390A0.5080007@mac.com> <20050830002051.GE1462@drjekyll.mkbuelow.net> <4313AB8D.4010807@paradise.net.nz> <20050830011106.GF1462@drjekyll.mkbuelow.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 29 Aug 2005 21:52:45 -0400 Message-Id: <1125366765.29186.17.camel@zappa.Chelsea-Ct.Org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Cc: freebsd-stable@freebsd.org, Mark Kirkwood Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 01:52:57 -0000 On Tue, 2005-08-30 at 03:11 +0200, Matthias Buelow wrote: > BTW., when have you last seen a broken NTFS? While > I don't do Windows much, I have had quite a few crashes on Windows > (2000, XP) over the years on various machines, and I always asked > myself how it could be that the system is up almost immediately > (probably due to log replay) with no discernible filesystem damage. > Windows (NT) has been doing the write barrier flush tricks (disabling-/ > reenabling the cache for flushing it) for longer than Linux and I > would think that this contributes to the fault resilience of NTFS. > Not that I would imply that NTFS can't be corrupted, of course. Funny you should mention it, but the last time I saw a broken NTFS was back in July. It was a friend's Windows 2000 system. The net effect was that the system would not boot fully; was not responsive to the "repair" option; and wouldn't allow the recovery console to start. In the end, a wipe and reinstall was necessary. Oddly enough, trying to mount the NTFS file system via a Knoppix CD before resorting to that yielded complaints about the journal being corrupted. I guess I must be lucky because I've never yet had a corrupted file system with softupdates enabled due to power loss or panic under FreeBSD (though I've experienced plenty of power losses due to the flaky power here and panics due to tracking CURRENT on my desktop system:). By reading your regular dire warnings on the subject, my experience must differ greatly from yours. ;-) BTW, if you consider softupdates fundamentally broken wrt data integrity, why don't you post your concerns to -current or -hackers, say? Surely the developers to address the problem are more likely to be found reading there? Cheers, Paul. -- e-mail: paul@gromit.dlib.vt.edu "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 02:23:39 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5346516A41F for ; Tue, 30 Aug 2005 02:23:39 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-3.paradise.net.nz (bm-3a.paradise.net.nz [202.0.58.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id D031C43D46 for ; Tue, 30 Aug 2005 02:23:38 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-2.paradise.net.nz (smtp-2a.paradise.net.nz [202.0.32.195]) by linda-3.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IM00087OJZCYY@linda-3.paradise.net.nz> for freebsd-stable@freebsd.org; Tue, 30 Aug 2005 14:23:37 +1200 (NZST) Received: from [192.168.1.11] (218-101-13-128.paradise.net.nz [218.101.13.128]) by smtp-2.paradise.net.nz (Postfix) with ESMTP id 661099ECD9; Tue, 30 Aug 2005 14:18:41 +1200 (NZST) Date: Tue, 30 Aug 2005 14:18:40 +1200 From: Mark Kirkwood In-reply-to: <20050830011106.GF1462@drjekyll.mkbuelow.net> To: Matthias Buelow Message-id: <4313C200.9090605@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050726) References: <20050829120415.GA1462@drjekyll.mkbuelow.net> <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> <20050829204714.GC1462@drjekyll.mkbuelow.net> <43137AFB.9060304@mac.com> <20050829215613.GD1462@drjekyll.mkbuelow.net> <431390A0.5080007@mac.com> <20050830002051.GE1462@drjekyll.mkbuelow.net> <4313AB8D.4010807@paradise.net.nz> <20050830011106.GF1462@drjekyll.mkbuelow.net> Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 02:23:39 -0000 Matthias Buelow wrote: > >>From what I understand from googling around on that issue, the > write-barrier stuff should make that much more unlikely. Of course > there could be the situation that it was a kernel that did not > (properly) support write-barriers yet, or the Linux implementation > has/had bugs (not too unlikely), or the disk was so broken that > even the flushing workaround strategies were ignored or it otherwise > didn't properly flush it, etc. But they're at least trying to cope > with the issue. BTW., when have you last seen a broken NTFS? LOL, well quite often - nt4 seemed to specialize in this, win2k and winxp (particularly 2k) however, seem much better... > While > I don't do Windows much, I have had quite a few crashes on Windows > (2000, XP) over the years on various machines, and I always asked > myself how it could be that the system is up almost immediately > (probably due to log replay) with no discernible filesystem damage. > Windows (NT) has been doing the write barrier flush tricks (disabling-/ > reenabling the cache for flushing it) for longer than Linux and I > would think that this contributes to the fault resilience of NTFS. > Not that I would imply that NTFS can't be corrupted, of course. > But otherwise, thanks for a very informative post. Hmm, I think OSX does something like this too. Funnily enough, I have never lost files while using FreeBSD, even tho I'm using ATA disks with the write cache enabled - and I have had power loss situations. The robustness was one of the things that persuaded me to switch from (Redhat 7.3/8.0 I think) to FreeBSD (4.6 I think). However that is ancient history, If everyone is working out how to manipulate the write cache on-demand, then I guess FreeBSD needs to as well...(not volunteering... probably a bit out of my league). Cheers Mark From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 02:59:12 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3960616A41F for ; Tue, 30 Aug 2005 02:59:12 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from riyal.ugcs.caltech.edu (riyal.ugcs.caltech.edu [131.215.176.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id C777643D48 for ; Tue, 30 Aug 2005 02:59:11 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by riyal.ugcs.caltech.edu (Postfix, from userid 3640) id C950645804; Mon, 29 Aug 2005 19:59:10 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by riyal.ugcs.caltech.edu (Postfix) with ESMTP id 7A0BF45802; Mon, 29 Aug 2005 19:59:10 -0700 (PDT) Date: Mon, 29 Aug 2005 19:59:10 -0700 (PDT) From: Jon Dama To: Matthias Buelow In-Reply-To: <20050830011632.GG1462@drjekyll.mkbuelow.net> Message-ID: References: <200508291836.j7TIaVEk013147@gw.catspoiler.org> <20050829185933.GB1462@drjekyll.mkbuelow.net> <431362ED.9030800@mac.com> <20050829204714.GC1462@drjekyll.mkbuelow.net> <43137AFB.9060304@mac.com> <20050829215613.GD1462@drjekyll.mkbuelow.net> <431390A0.5080007@mac.com> <20050830002051.GE1462@drjekyll.mkbuelow.net> <4313AB8D.4010807@paradise.net.nz> <20050830011632.GG1462@drjekyll.mkbuelow.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: mckusick@mckusick.com, freebsd-stable@freebsd.org, Mark Kirkwood Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 02:59:12 -0000 Well, I think one issue is that it destroys one of the fundamental advantages of softupdates which was that you could interleave streams of strongly ordered metadata writes without demanding a sequence for the streams collectively. By using request barriers, you are effectively forcing an additional synchronization requirement, the secret will be not forcing us all the way back to having effectively synchronous metadata writes (see below). As I understand, metadata operations are only added to the WORKLIST when their dependents have already been "completed" i.e., at the lowest level have had biodone called to mark the write operation completed. I am not sure how ffs_softdeps checks this property. It seems you need to add a layer of indirection. (owing to biodone being called merely when the drive has cached the request). What you know is that those operations marked completed by biodone are in fact done only after a (costly) flush cache operation is executed. Therefore you want to delay this operation for as long as possible, in fact until you actually depend on biodone being honest. I.e., at the time another operation is inserted into the WORKLIST. The secret I think is to keep track of which bp's marked B_DONE by biodone that have been certified by a flush cache. Thus permitting you to avoid some cache flushes. Furthermore, the softdep code has to be responsible for envoking the flush cache operation when it notices that the B_DONE flag that it cares about does not have a matching B_REALLY_DONE flag, which every block should have that had B_DONE set before the flush cache operation happened. I do not really know how GEOM has changed this situation. biodone seems to have been stripped of much of its old responsibilities? -Jon I'd guess that it belongs On Tue, 30 Aug 2005, Matthias Buelow wrote: > Jon Dama wrote: > > >Ironically, phk backed out the underlying support for this safety fix > > from the FreeBSD kernel b.c. it wasn't integrated into the softupdates > >code > >whereas in reality the proper course of action would have been to hook it > >in. :-/ > > Can it be put into softupdates at all? From what I understand (which > is probably a rather sketchy idea of the matter), write barriers > work because they are only used here to separate journal writes > from data writes (i.e., to make sure the log is written, by flushing > the cache, before any filesystem data hits the platters). I've read > the softupdates paper some time ago and haven't found similar > sequence points where one could insert such flushing. One would > have to "flush" all the time, either continuously or in very short > intervals, in order to keep the ordering, which then would amount > to the same effects as if one simply disabled the cache. But probably > I'm wrong here (I hope). > > mkb. > From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 03:30:46 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1599916A41F for ; Tue, 30 Aug 2005 03:30:46 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A91C543D49 for ; Tue, 30 Aug 2005 03:30:44 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id j7U3UXi4014113; Mon, 29 Aug 2005 20:30:37 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200508300330.j7U3UXi4014113@gw.catspoiler.org> Date: Mon, 29 Aug 2005 20:30:33 -0700 (PDT) From: Don Lewis To: mkb@incubus.de In-Reply-To: <20050830011632.GG1462@drjekyll.mkbuelow.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-stable@FreeBSD.org, markir@paradise.net.nz Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 03:30:46 -0000 On 30 Aug, Matthias Buelow wrote: > Jon Dama wrote: > >>Ironically, phk backed out the underlying support for this safety fix >> from the FreeBSD kernel b.c. it wasn't integrated into the softupdates >>code >>whereas in reality the proper course of action would have been to hook it >>in. :-/ > > Can it be put into softupdates at all? From what I understand (which > is probably a rather sketchy idea of the matter), write barriers > work because they are only used here to separate journal writes > from data writes (i.e., to make sure the log is written, by flushing > the cache, before any filesystem data hits the platters). I've read > the softupdates paper some time ago and haven't found similar > sequence points where one could insert such flushing. One would > have to "flush" all the time, either continuously or in very short > intervals, in order to keep the ordering, which then would amount > to the same effects as if one simply disabled the cache. But probably > I'm wrong here (I hope). Performance might be bad, but it is still likely to be better than totally disabling write caching. For instance if you had two different write transaction pairs, where write B depends on write A, and write D depends on write C, you could issue writes A and C, flush the drive's write cache, and then issue writes B and D. You could also optimize large sequential writes by writing all the data blocks, flushing the write cache, and then updating the inode and bitmap blocks. Grouping writes to minimize the number of flushes might help performance. The key is that the drive's write cache needs to be flushed before doing a write that depends on an earlier write. The complication is that softupdates tosses the information about a write as soon as the drive acknowledges it, but if write caching is enabled, softupdates would need to retain this information until the drive's write cache is flushed. I think you could still get file system corruption on power failure if you are using ATA drives, because most high capacity drives write a track at a time, in many cases re-writing data that was last touched in the distant past. If the power fails part way through a track rewrite, then the old data on that track may be lost. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 03:36:52 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4764516A41F for ; Tue, 30 Aug 2005 03:36:52 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0DD943D45 for ; Tue, 30 Aug 2005 03:36:51 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id j7U3afcB014128; Mon, 29 Aug 2005 20:36:45 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200508300336.j7U3afcB014128@gw.catspoiler.org> Date: Mon, 29 Aug 2005 20:36:41 -0700 (PDT) From: Don Lewis To: jd@ugcs.caltech.edu In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: mckusick@mckusick.com, freebsd-stable@FreeBSD.org, mkb@incubus.de, markir@paradise.net.nz Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 03:36:52 -0000 On 29 Aug, Jon Dama wrote: > It seems you need to add a layer of indirection. (owing to biodone being > called merely when the drive has cached the request). What you know is > that those operations marked completed by biodone are in fact done only > after a (costly) flush cache operation is executed. > > Therefore you want to delay this operation for as long as possible, in > fact until you actually depend on biodone being honest. I.e., at the time > another operation is inserted into the WORKLIST. > > The secret I think is to keep track of which bp's marked B_DONE by > biodone that have been certified by a flush cache. Thus permitting you to > avoid some cache flushes. Furthermore, the softdep code has to be > responsible for envoking the flush cache operation when it notices that > the B_DONE flag that it cares about does not have a matching > B_REALLY_DONE flag, which every block should have that had B_DONE set > before the flush cache operation happened. I believe you are correct. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 04:57:20 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6F3E16A41F for ; Tue, 30 Aug 2005 04:57:20 +0000 (GMT) (envelope-from nate@root.org) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6051643D48 for ; Tue, 30 Aug 2005 04:57:20 +0000 (GMT) (envelope-from nate@root.org) Received: from ylpvm01.prodigy.net (ylpvm01-int.prodigy.net [207.115.5.207]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id j7U4vFx0021181 for ; Tue, 30 Aug 2005 00:57:16 -0400 X-ORBL: [64.171.187.62] Received: from [10.0.0.115] (adsl-64-171-187-62.dsl.snfc21.pacbell.net [64.171.187.62]) by ylpvm01.prodigy.net (8.13.4 dk-milter linux/8.13.4) with ESMTP id j7U4vEHv016446; Tue, 30 Aug 2005 00:57:15 -0400 Message-ID: <4313E725.70809@root.org> Date: Mon, 29 Aug 2005 21:57:09 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tijl Coosemans References: <200508020022.02992.tijl@ulyssis.org> In-Reply-To: <200508020022.02992.tijl@ulyssis.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: 5-STABLE cpufreq hotter than est from ports X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 04:57:20 -0000 Tijl Coosemans wrote: > A couple days ago I updated my system and was excited to see cpufreq > and powerd in 5-stable. Since then however I noticed that my laptop > temperature is about 5°C higher than with est and estctrl. I found that > cpufreq when setting 200MHz for example set the absolute frequency to > 1600MHz (max for this laptop) and the relative frequency (p4tcc) to > 12.5% instead of using a more power conserving setting like 800MHz/25%. A variant of your patch has been committed and will be MFCd. Thanks! > So, I've worked out a patch (attached) that makes sure > that a lower frequency level has at most the same absolute setting > (preferably less of course). This eliminates quite a few levels so > somebody with a better knowledge of cpufreq should check if this patch > really does something good. This is the first time I've taken a look at > FreeBSD source code by the way. I added back the check for CPUFREQ_CMP since you don't want duplicate levels. This is not currently a problem with est/p4tcc but other combinations of settings could have produced duplicates with the patch's approach. > Also, somewhat related, the p4tcc driver doesn't recognise > acpi_throttle, which means that when you load the cpufreq module after > booting, the freq levels are messed up. I'm not sure what the best > solution for this is. Let p4tcc detect acpi_throttle and don't attach > if it's present (like acpi_throttle does now if it finds p4tcc) or > detach it before attaching? Or maybe p4tcc and acpi_throttle should be > merged into one driver? acpi_throttle is only the same as p4tcc on x86 platforms. We need a better negotiation strategy in general between the different drivers. The logic for these two is already p4tcc > acpi_throttle but we need to support reprobing when cpufreq.ko is loaded after boot by detaching both and then allowing p4tcc to win the probe. -- Nate From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 06:56:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E15C916A420 for ; Tue, 30 Aug 2005 06:56:32 +0000 (GMT) (envelope-from gni@gecko.de) Received: from kirk.baltic.net (kirk.baltic.net [193.189.247.10]) by mx1.FreeBSD.org (Postfix) with SMTP id D1DF843D4C for ; Tue, 30 Aug 2005 06:56:28 +0000 (GMT) (envelope-from gni@gecko.de) Received: (qmail 4139 invoked from network); 30 Aug 2005 06:52:23 -0000 Received: from waldorf.gecko.de (HELO kermit.int.gecko.de) (193.189.247.200) by kirk.baltic.net with SMTP; 30 Aug 2005 06:52:23 -0000 Received: from lorien.int.gecko.de (lorien [192.168.120.159]) by kermit.int.gecko.de (8.12.10+Sun/8.12.10) with ESMTP id j7U6uR6B027580; Tue, 30 Aug 2005 08:56:27 +0200 (CEST) Received: from lorien.int.gecko.de (localhost [127.0.0.1]) by lorien.int.gecko.de (8.12.9/8.12.9) with ESMTP id j7U6vpCu067863; Tue, 30 Aug 2005 08:57:51 +0200 (MEST) (envelope-from munk@lorien.int.gecko.de) Received: (from munk@localhost) by lorien.int.gecko.de (8.12.9/8.12.9/Submit) id j7U6vplV067862; Tue, 30 Aug 2005 08:57:51 +0200 (MEST) Date: Tue, 30 Aug 2005 08:57:50 +0200 From: Gunther Nikl To: Chuck Swiger Message-ID: <20050830065750.GA67835@lorien.int.gecko.de> References: <200508282330.09302.dinom@balstonresearch.com> <20050829033739.GV26920@bunrab.catwhisker.org> <200508290213.12978.dinom@balstonresearch.com> <4312A9CD.8040008@freebsd.org> <4312AEE0.8080806@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4312AEE0.8080806@mac.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 06:56:33 -0000 On Mon, Aug 29, 2005 at 02:44:48AM -0400, Chuck Swiger wrote: > Jon Dama wrote: > >yes, that's quite generous. > > > >why isn't /tmp just an mfs mount though? > > While I like that suggestion personally, some people get perturbed about > files in /tmp going away if the power fails or you reboot. I wish mount_mfs would be smarter on post 4.x systems. Using mount_mfs means it works in compatibility mode. This might seem to be a good idea but it praxis it prevents tuning the mfs parameters: in mfs mode I can't set UFS version, I can't inhibit the .snap directory. Gunther From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 07:22:17 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1706416A41F for ; Tue, 30 Aug 2005 07:22:17 +0000 (GMT) (envelope-from vladgalu@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 696F043D48 for ; Tue, 30 Aug 2005 07:22:16 +0000 (GMT) (envelope-from vladgalu@gmail.com) Received: by zproxy.gmail.com with SMTP id z6so730378nzd for ; Tue, 30 Aug 2005 00:22:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GjGpxDimtXBoZ+btAvK8ymZhVGqLpYRD6hdIa9dZhByePA5CgDv5P+b1RHc4bYq6TjlLbHGahcYpS9zIpebSdPW+JC6O7kJyU+oAGhAwD0fJHbyG0iowsu0POD1uk1xwQcGZTAHT2Lv2o1qlF57Gger8WFtogomcvI1tGFNdez4= Received: by 10.36.119.1 with SMTP id r1mr1511157nzc; Tue, 30 Aug 2005 00:22:14 -0700 (PDT) Received: by 10.36.86.4 with HTTP; Tue, 30 Aug 2005 00:22:13 -0700 (PDT) Message-ID: <79722fad050830002252a1254c@mail.gmail.com> Date: Tue, 30 Aug 2005 10:22:13 +0300 From: Vlad GALU To: Jason In-Reply-To: <20050826120500.GA8907@thevoid.delnoch.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050826120500.GA8907@thevoid.delnoch.net> Cc: freebsd-stable@freebsd.org Subject: Re: pcap and gig speeds. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 07:22:17 -0000 On 8/26/05, Jason wrote: > We are planning on updating a number of old machines, being used as > IDS sensors, and in the past, there has been a known issue regarding > gig speeds and pcap with regards to snort. >=20 > Has this issue been resolved, I searched archives (the search > web interface appears to have some issues, and was only returning 4 > results on a generic search of pcap), nothing usefull. >=20 > Before I spend a significant amount of money on new hardware, I want > to make sure we have the ability to support it, honestly, I would hate > to have to move to linux. I have no tried the ports version of pcap > yet since I don't have the hardware. Linux doesn't behave better than FreeBSD regarding packet capture. I've developed http://freshmeat.net/projects/glflow/ which is now used to sniff ~800Kbps, and I've come to pretty close results on both platforms. Plain BPF with polling on FreeBSD and PF_RING on Linux. So my guess is that your snort spends most of its time in userspace doing its own computing rather than capturing packets. You should write a small tool that only counts sniffed packets and prints out the average every X seconds, for real comparisons. >=20 > Jason > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >=20 --=20 If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 08:33:18 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C321616A41F for ; Tue, 30 Aug 2005 08:33:18 +0000 (GMT) (envelope-from krion@voodoo.oberon.net) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEEF743D45 for ; Tue, 30 Aug 2005 08:33:17 +0000 (GMT) (envelope-from krion@voodoo.oberon.net) Received: from krion by voodoo.oberon.net with local (Exim 4.52 (FreeBSD)) id 1EA1YJ-000IFQ-To for freebsd-stable@FreeBSD.org; Tue, 30 Aug 2005 10:33:07 +0200 Date: Tue, 30 Aug 2005 10:33:07 +0200 From: Kirill Ponomarew To: freebsd-stable@FreeBSD.org Message-ID: <20050830083307.GC67975@voodoo.oberon.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="i9LlY+UWpKt15+FH" Content-Disposition: inline X-NCC-Regid: de.oberon X-NIC-HDL: KP869-RIPE Keywords: 579279786 Cc: Subject: 4.11-RELEASE panics X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 08:33:18 -0000 --i9LlY+UWpKt15+FH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Got 2 identical panics today. Trace attached. -Kirill --i9LlY+UWpKt15+FH Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=log Content-Transfer-Encoding: quoted-printable GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD at physical address 0x00335000 initial pcb at physical address 0x002a8740 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0x5 fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xc02309a0 stack pointer =3D 0x10:0xdfe16db4 frame pointer =3D 0x10:0xdfe16dbc code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 142 (syslogd) interrupt mask =3D net bio cam=20 panic: from debugger Fatal trap 3: breakpoint instruction fault while in kernel mode instruction pointer =3D 0x8:0xc0222b18 stack pointer =3D 0x10:0xdfe16bc8 frame pointer =3D 0x10:0xdfe16bd0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, IOPL =3D 0 current process =3D 142 (syslogd) interrupt mask =3D net bio cam=20 Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0x0 fault code =3D supervisor write, page not present instruction pointer =3D 0x8:0xc028ec47 stack pointer =3D 0x10:0xdfe16b88 frame pointer =3D 0x10:0xdfe16bf0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 142 (syslogd) interrupt mask =3D net bio cam=20 Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0x0 fault code =3D supervisor write, page not present instruction pointer =3D 0x8:0xc028ec47 stack pointer =3D 0x10:0xdfe16b88 frame pointer =3D 0x10:0xdfe16bf0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D resume, IOPL =3D 0 current process =3D 142 (syslogd) interrupt mask =3D net bio cam=20 panic: from debugger Uptime: 1h29m44s dumping to dev #da/0x20001, offset 2097184 dump 1023 1022 1021 1020 1019 1018 1017 1016 1015 1014 1013 1012 1011 1010 = 1009 1008 1007 1006 1005 1004 1003 1002 1001 1000 999 998 997 996 995 994 9= 93 992 991 990 989 988 987 986 985 984 983 982 981 980 979 978 977 976 975 = 974 973 972 971 970 969 968 967 966 965 964 963 962 961 960 959 958 957 956= 955 954 953 952 951 950 949 948 947 946 945 944 943 942 941 940 939 938 93= 7 936 935 934 933 932 931 930 929 928 927 926 925 924 923 922 921 920 919 9= 18 917 916 915 914 913 912 911 910 909 908 907 906 905 904 903 902 901 900 = 899 898 897 896 895 894 893 892 891 890 889 888 887 886 885 884 883 882 881= 880 879 878 877 876 875 874 873 872 871 870 869 868 867 866 865 864 863 86= 2 861 860 859 858 857 856 855 854 853 852 851 850 849 848 847 846 845 844 8= 43 842 841 840 839 838 837 836 835 834 833 832 831 830 829 828 827 826 825 = 824 823 822 821 820 819 818 817 816 815 814 813 812 811 810 809 808 807 806= 805 804 803 802 801 800 799 798 797 796 795 794 793 792 791 790 789 788 78= 7 786 785 784 783 782 781 780 779 778 777 776 775 774 773 772 771 770 769 7= 68 767 766 765 764 763 762 761 760 759 758 757 756 755 754 753 752 751 750 = 749 748 747 746 745 744 743 742 741 740 739 738 737 736 735 734 733 732 731= 730 729 728 727 726 725 724 723 722 721 720 719 718 717 716 715 714 713 71= 2 711 710 709 708 707 706 705 704 703 702 701 700 699 698 697 696 695 694 6= 93 692 691 690 689 688 687 686 685 684 683 682 681 680 679 678 677 676 675 = 674 673 672 671 670 669 668 667 666 665 664 663 662 661 660 659 658 657 656= 655 654 653 652 651 650 649 648 647 646 645 644 643 642 641 640 639 638 63= 7 636 635 634 633 632 631 630 629 628 627 626 625 624 623 622 621 620 619 6= 18 617 616 615 614 613 612 611 610 609 608 607 606 605 604 603 602 601 600 = 599 598 597 596 595 594 593 592 591 590 589 588 587 586 585 584 583 582 581= 580 579 578 577 576 575 574 573 572 571 570 569 568 567 566 565 564 563 56= 2 561 560 559 558 557 556 555 554 553 552 551 550 549 548 547 546 545 544 5= 43 542 541 540 539 538 537 536 535 534 533 532 531 530 529 528 527 526 525 = 524 523 522 521 520 519 518 517 516 515 514 513 512 511 510 509 508 507 506= 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 490 489 488 48= 7 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 469 4= 68 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 = 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431= 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 41= 2 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395 394 3= 93 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 376 375 = 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 357 356= 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 33= 7 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320 319 3= 18 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 301 300 = 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 281= 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 263 26= 2 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 244 2= 43 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 = 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206= 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 18= 7 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 1= 68 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 = 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131= 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 11= 2 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 9= 1 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 6= 6 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 4= 1 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 1= 6 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 \^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^= @\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@\^@ --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 487 if (dumping++) { (kgdb) where #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 #1 0xc018469f in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:3= 16 #2 0xc0184add in panic (fmt=3D0xc024eac4 "from debugger") at /usr/src/sys/= kern/kern_shutdown.c:595 #3 0xc0134d7d in db_panic (addr=3D-1071445600, have_addr=3D0, count=3D-1, = modif=3D0xdfe16c20 "") at /usr/src/sys/ddb/db_command.c:435 #4 0xc0134d1d in db_command (last_cmdp=3D0xc02860e4, cmd_table=3D0xc0285f2= 4, aux_cmd_tablep=3D0xc02a39f8) at /usr/src/sys/ddb/db_command.c:333 #5 0xc0134de2 in db_command_loop () at /usr/src/sys/ddb/db_command.c:457 #6 0xc0136f1f in db_trap (type=3D12, code=3D0) at /usr/src/sys/ddb/db_trap= =2Ec:71 #7 0xc02228ba in kdb_trap (type=3D12, code=3D0, regs=3D0xdfe16d74) at /usr= /src/sys/i386/i386/db_interface.c:158 #8 0xc02322a8 in trap_fatal (frame=3D0xdfe16d74, eva=3D5) at /usr/src/sys/= i386/i386/trap.c:969 #9 0xc0231f81 in trap_pfault (frame=3D0xdfe16d74, usermode=3D0, eva=3D5) a= t /usr/src/sys/i386/i386/trap.c:867 #10 0xc0231b27 in trap (frame=3D{tf_fs =3D 16, tf_es =3D 16, tf_ds =3D 16, = tf_edi =3D 0, tf_esi =3D 6864960, tf_ebp =3D -538874436,=20 tf_isp =3D -538874464, tf_ebx =3D 1, tf_edx =3D 6864960, tf_ecx =3D 0= , tf_eax =3D 6864960, tf_trapno =3D 12, tf_err =3D 0,=20 tf_eip =3D -1071445600, tf_cs =3D 8, tf_eflags =3D 66050, tf_esp =3D = 0, tf_ss =3D -1064370628}) at /usr/src/sys/i386/i386/trap.c:466 #11 0xc02309a0 in pmap_clear_modify (m=3D0xc08efe3c) at /usr/src/sys/i386/i= 386/pmap.c:2865 #12 0xc0205496 in vm_page_set_validclean (m=3D0xc08efe3c, base=3D0, size=3D= 4096) at /usr/src/sys/vm/vm_page.c:1659 #13 0xc01ad6ac in vfs_page_set_valid (bp=3D0xcf8b95f8, off=3D-196608, pagen= o=3D0, m=3D0xc08efe3c) at /usr/src/sys/kern/vfs_bio.c:2947 #14 0xc01ad803 in vfs_busy_pages (bp=3D0xcf8b95f8, clear_modify=3D1) at /us= r/src/sys/kern/vfs_bio.c:3018 #15 0xc01aad0a in bwrite (bp=3D0xcf8b95f8) at /usr/src/sys/kern/vfs_bio.c:7= 26 #16 0xc01b07d2 in vop_stdbwrite (ap=3D0xdfe16ea0) at /usr/src/sys/kern/vfs_= default.c:344 #17 0xc01b061d in vop_defaultop (ap=3D0xdfe16ea0) at /usr/src/sys/kern/vfs_= default.c:152 #18 0xc01f8da1 in ufs_vnoperate (ap=3D0xdfe16ea0) at /usr/src/sys/ufs/ufs/u= fs_vnops.c:2376 #19 0xc01ab0d2 in bawrite (bp=3D0xcf8b95f8) at vnode_if.h:1193 #20 0xc01f21ba in ffs_fsync (ap=3D0xdfe16f08) at /usr/src/sys/ufs/ffs/ffs_v= nops.c:198 #21 0xc01b8258 in fsync (p=3D0xdbf1d8a0, uap=3D0xdfe16f80) at vnode_if.h:558 #22 0xc0232589 in syscall2 (frame=3D{tf_fs =3D 47, tf_es =3D 47, tf_ds =3D = 47, tf_edi =3D 134563033, tf_esi =3D -1077940824,=20 tf_ebp =3D -1077940816, tf_isp =3D -538873900, tf_ebx =3D 134561792, = tf_edx =3D 22, tf_ecx =3D -6, tf_eax =3D 95, tf_trapno =3D 7,=20 tf_err =3D 2, tf_eip =3D 672039296, tf_cs =3D 31, tf_eflags =3D 647, = tf_esp =3D -1077942268, tf_ss =3D 47}) at /usr/src/sys/i386/i386/trap.c:1175 #23 0xc0223795 in Xint0x80_syscall () #24 0x804adbf in ?? () #25 0x804a83c in ?? () #26 0x804a6c4 in ?? () #27 0x804a270 in ?? () #28 0x8049792 in ?? () (kgdb) q --i9LlY+UWpKt15+FH-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 08:43:21 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CC2916A41F for ; Tue, 30 Aug 2005 08:43:21 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam.ru (gw.ipt.ru [80.253.10.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 270A143D46 for ; Tue, 30 Aug 2005 08:43:20 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam by bsam.ru with local (Exim 4.30; FreeBSD) id 1EA1gX-000JIc-Uf; Tue, 30 Aug 2005 12:41:37 +0400 To: Rene Ladan References: <55023220@srv.sem.ipt.ru> <20050828150947.GA58038@82-168-75-155-bbxl.xdsl.tiscali.nl> From: Boris Samorodov Date: Tue, 30 Aug 2005 12:41:37 +0400 In-Reply-To: <20050828150947.GA58038@82-168-75-155-bbxl.xdsl.tiscali.nl> (Rene Ladan's message of "Sun, 28 Aug 2005 17:09:47 +0200") Message-ID: <51471998@srv.sem.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: "Boris B. Samorodov" Cc: stable@freebsd.org Subject: Re: 6.0 and -O2 option X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 08:43:21 -0000 Hi! On Sun, 28 Aug 2005 17:09:47 +0200 Rene Ladan wrote: > On Sun, Aug 28, 2005 at 04:30:19PM +0400, Boris Samorodov wrote: > > Hi! > > > > > > As for 5.x notes about -O2 (libalias, gcc) were removed at revision > > 1.229.2.7 of /usr/src/share/examples/etc/make.conf. But for 6.0-BETA3 > > we do have these warnings. Should they be removed as for 5.x? Is it > > safe to use -O2 to build/install kernel, world, ports fro 6.0? > > > Kernel and world seem to be ok with -O2, for ports it is not advised. Well, as nobody complained so far, should I file a PR to remove notes about -O2 to examples/etc/make.conf for 6.0-BETA3? WBR -- bsam From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 10:19:03 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F1BF16A41F for ; Tue, 30 Aug 2005 10:19:03 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (www1.multiplay.co.uk [212.42.16.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB56043D49 for ; Tue, 30 Aug 2005 10:19:02 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [212.42.16.7]) (MDaemon.PRO.v8.1.0.R) with ESMTP id md50001834550.msg for ; Tue, 30 Aug 2005 11:11:11 +0100 Message-ID: <005401c5ad4c$1349ca90$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Matthias Buelow" , "Jon Dama" References: <200508291836.j7TIaVEk013147@gw.catspoiler.org><20050829185933.GB1462@drjekyll.mkbuelow.net><431362ED.9030800@mac.com><20050829204714.GC1462@drjekyll.mkbuelow.net><43137AFB.9060304@mac.com><20050829215613.GD1462@drjekyll.mkbuelow.net><431390A0.5080007@mac.com><20050830002051.GE1462@drjekyll.mkbuelow.net><4313AB8D.4010807@paradise.net.nz> <20050830011632.GG1462@drjekyll.mkbuelow.net> Date: Tue, 30 Aug 2005 11:17:46 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Processed: multiplay.co.uk, Tue, 30 Aug 2005 11:11:11 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-MDAV-Processed: multiplay.co.uk, Tue, 30 Aug 2005 11:11:13 +0100 Cc: freebsd-stable@freebsd.org, Mark Kirkwood Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 10:19:03 -0000 I must say in the 10 years of using Windows on my desktop and on servers I've never once had to deal with NTFS loosing data. In addition to that I dont have to sit though 1 hour worth of offline checks when it crashes for what ever reason which I do on our FreeBSD boxes. >From our experiences, the issues with the current FS would be the primary factor for begrudgingly moving to another OS as for large FS's its getting simple unwieldy especially since foreground checks are often required :( There is a great amount of new work going into FreeBSD with loads of improvements in a wide range of areas which is great but I do believe the FS really does need to attract some more focus as is not something that can solved quickly and is beginning to become a sticking point. Steve ----- Original Message ----- From: "Matthias Buelow" > Can it be put into softupdates at all? From what I understand (which > is probably a rather sketchy idea of the matter), write barriers > work because they are only used here to separate journal writes > from data writes (i.e., to make sure the log is written, by flushing > the cache, before any filesystem data hits the platters). I've read > the softupdates paper some time ago and haven't found similar > sequence points where one could insert such flushing. One would > have to "flush" all the time, either continuously or in very short > intervals, in order to keep the ordering, which then would amount > to the same effects as if one simply disabled the cache. But probably > I'm wrong here (I hope). ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 10:48:08 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F65216A41F for ; Tue, 30 Aug 2005 10:48:08 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8810943D49 for ; Tue, 30 Aug 2005 10:48:07 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ilclej@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.1/8.13.1) with ESMTP id j7UAm4b1084417 for ; Tue, 30 Aug 2005 12:48:05 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.1/8.13.1/Submit) id j7UAm4ax084416; Tue, 30 Aug 2005 12:48:04 +0200 (CEST) (envelope-from olli) Date: Tue, 30 Aug 2005 12:48:04 +0200 (CEST) Message-Id: <200508301048.j7UAm4ax084416@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG Rely-To: freebsd-stable@FreeBSD.ORG In-Reply-To: <4312AEE0.8080806@mac.com> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-RELEASE (i386)) Cc: Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 10:48:08 -0000 Chuck Swiger wrote: > Jon Dama wrote: > > yes, that's quite generous. > > > > why isn't /tmp just an mfs mount though? > > While I like that suggestion personally, some people get perturbed about files > in /tmp going away if the power fails or you reboot. Then those people should use /var/tmp instead of /tmp. Traditional UNIX behaviour is that contents of /var/tmp must survive a reboot, while contents of /tmp are not guaranteed to survive a reboot (and in fact, /tmp might be cleaned completely at regular time intervals via a periodic cron job or similar). That's why vi puts its recovery files under /var/tmp, not /tmp. However, there are still cases where it's not desirable to make /tmp a memory-based file system, e.g. on systems that have little RAM and/or no swap (or NFS swap). Also, some people argue that a UFS disk partition with softupdates (or even async) is fast enough for most purposes to be mounted on /tmp. (For what it's worth, I've seen systems set up in a way to newfs the /tmp partiton on reboot.) Therefore, I think the best solution would be to make it an option in sysinstall: If the user doesn't create a separate partiton for /tmp in the partition editor, ask him whether he would like to make /tmp a memory-based file system. Or implement a special hotkey in the partition editor for creating a memory-based file system -- I guess this would be the easiest way to implement it. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "I invented Ctrl-Alt-Delete, but Bill Gates made it famous." -- David Bradley, original IBM PC design team From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 12:16:22 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4FAF16A41F for ; Tue, 30 Aug 2005 12:16:22 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0274243D46 for ; Tue, 30 Aug 2005 12:16:21 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A7C0C.dip.t-dialin.net [84.154.124.12]) (authenticated bits=0) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id j7UCGHxr024931; Tue, 30 Aug 2005 14:16:19 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id j7UCGFEn015355; Tue, 30 Aug 2005 14:16:16 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id j7UCGqv6069212; Tue, 30 Aug 2005 14:16:52 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200508301216.j7UCGqv6069212@fire.jhs.private> To: "Steven Hartland" In-Reply-To: Message from "Steven Hartland" of "Tue, 30 Aug 2005 11:17:46 BST." <005401c5ad4c$1349ca90$b3db87d4@multiplay.co.uk> Date: Tue, 30 Aug 2005 14:16:52 +0200 From: "Julian H. Stacey" Cc: freebsd-stable@freebsd.org Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 12:16:22 -0000 "Steven Hartland" wrote: > data. In addition to that I dont have to sit though 1 hour worth > of offline checks when it crashes for what ever reason which I > do on our FreeBSD boxes. [Apologies if I missed something, coming in late on thread, but ...] FreeBSD-4 does fsck on dirty filesystems before going multi user: You wait. FreeBSD-5.* & 6.0-BETA3 : fsck runs in background after boot: No waiting. -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail Ascii not HTML. Ihr Rauch = mein allergischer Kopfschmerzen. From owner-freebsd-stable@FreeBSD.ORG Mon Aug 29 15:50:59 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 566D816A41F for ; Mon, 29 Aug 2005 15:50:59 +0000 (GMT) (envelope-from mark_space4@hotmail.com) Received: from hotmail.com (bay105-f30.bay105.hotmail.com [65.54.224.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0A7943D48 for ; Mon, 29 Aug 2005 15:50:58 +0000 (GMT) (envelope-from mark_space4@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 29 Aug 2005 08:50:58 -0700 Message-ID: Received: from 65.54.224.200 by by105fd.bay105.hotmail.msn.com with HTTP; Mon, 29 Aug 2005 15:50:58 GMT X-Originating-IP: [65.54.224.200] X-Originating-Email: [mark_space4@hotmail.com] X-Sender: mark_space4@hotmail.com In-Reply-To: <200508291258.j7TCwZIx032432@app.auscert.org.au> From: "Mark Space" To: freebsd-stable@auscert.org.au, freebsd-stable@freebsd.org Date: Mon, 29 Aug 2005 15:50:58 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 29 Aug 2005 15:50:58.0940 (UTC) FILETIME=[730DCBC0:01C5ACB1] X-Mailman-Approved-At: Tue, 30 Aug 2005 12:54:27 +0000 Cc: Subject: Re: Incorrect super block--Thanks! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2005 15:50:59 -0000 >From: freebsd-stable@auscert.org.au >Of course, this is dead right and ignore my previous response. You'll find >that the cdrom drive is almost certainly in /etc/fstab as the other >responder mentioned - to mount it with the default fstab options (which >should work just fine): > > mount /cdrom Yup, silly me, I was bypassing the fstab file by giving the full command. Thanks all! _________________________________________________________________ Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 14:12:40 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C21FA16A4F4 for ; Tue, 30 Aug 2005 14:12:39 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D33C43D45 for ; Tue, 30 Aug 2005 14:12:38 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (juzmjk@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.1/8.13.1) with ESMTP id j7UECbkF092797 for ; Tue, 30 Aug 2005 16:12:38 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.1/8.13.1/Submit) id j7UECbaB092796; Tue, 30 Aug 2005 16:12:37 +0200 (CEST) (envelope-from olli) Date: Tue, 30 Aug 2005 16:12:37 +0200 (CEST) Message-Id: <200508301412.j7UECbaB092796@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-RELEASE (i386)) Cc: Subject: WITNESS warning output from 6.0-BETA3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 14:12:40 -0000 Hi, I get the following output under FreeBSD 6.0-BETA3 when WITNESS is enabled. It doesn't seem to cause any harm, though. I cvsupped this system to RELENG_6 a few days ago. I have no idea what is causing this output, whether should worry about it, or even whether this is the right list to report or ask about it. :-) The output occurs when booting, right when the interface (bfe0) is configured for the first time. I have a small self-made script in /etc/rc.d which configures bfe0 several times with different IP addresses and performs a ping test in order to find out in which network the notebook is located, then symlinks various files in /etc depending on the result. The below output happens when that script is executed. Best regards Oliver malloc(M_WAITOK) of "64", forcing M_NOWAIT with the following non-sleepable locks held: exclusive sleep mutex if_addr_mtx r = 0 (0xc23af260) locked @ /usr/src/sys/net/if.c:1905 KDB: stack backtrace: kdb_backtrace(1,40,c104d800,2,e4f46b1c) at kdb_backtrace+0x29 witness_warn(5,0,c06ebd16,c06d9c8c,40) at witness_warn+0x18e uma_zalloc_arg(c104d800,0,102) at uma_zalloc_arg+0x41 malloc(36,c071f4e0,102,0,c23af000) at malloc+0xae ether_resolvemulti(c23af000,e4f46b78,e4f46ba8,c2641bc4,0) at ether_resolvemulti+0x87 if_addmulti(c23af000,e4f46ba8,e4f46ba4,e4f46ba8,10) at if_addmulti+0x84 in_addmulti(e4f46bdc,c23af000) at in_addmulti+0x32 in_ifinit(c23af000,c2641b00,c2627550,0,e4f46c38) at in_ifinit+0x515 in_control(c2707b20,8040691a,c2627540,c23af000,c235b180) at in_control+0x882 ifioctl(c2707b20,8040691a,c2627540,c235b180,0) at ifioctl+0x198 soo_ioctl(c2662360,8040691a,c2627540,c225bd00,c235b180) at soo_ioctl+0x2db ioctl(c235b180,e4f46d04,3,1,286) at ioctl+0x370 syscall(3b,3b,3b,8056da0,0) at syscall+0x22f Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280d0a97, esp = 0xbfbfe99c, ebp = 0xbfbfe9c8 --- malloc(M_WAITOK) of "64", forcing M_NOWAIT with the following non-sleepable locks held: exclusive sleep mutex if_addr_mtx r = 0 (0xc23af260) locked @ /usr/src/sys/net/if.c:1905 KDB: stack backtrace: kdb_backtrace(1,40,c104d800,2,e4f469b0) at kdb_backtrace+0x29 witness_warn(5,0,c06ebd16,c06d9c8c,40) at witness_warn+0x18e uma_zalloc_arg(c104d800,0,102) at uma_zalloc_arg+0x41 malloc(36,c071f4e0,102,0,c23af000) at malloc+0xae ether_resolvemulti(c23af000,e4f46a0c,e4f46a3c,0,0) at ether_resolvemulti+0x124 if_addmulti(c23af000,e4f46a3c,e4f46a38,e4f46a3c,1c) at if_addmulti+0x84 in6_addmulti(e4f46a8c,c23af000,e4f46a84) at in6_addmulti+0x4c in6_update_ifa(c23af000,e4f46b8c,0) at in6_update_ifa+0x4cf in6_ifattach_linklocal(c23af000,0) at in6_ifattach_linklocal+0xe5 in6_ifattach(c23af000,0,8040691a,8040691a,0) at in6_ifattach+0xb9 in6_if_up(c23af000) at in6_if_up+0x13 ifioctl(c2707b20,8040691a,c2627540,c235b180,0) at ifioctl+0x1f8 soo_ioctl(c2662360,8040691a,c2627540,c225bd00,c235b180) at soo_ioctl+0x2db ioctl(c235b180,e4f46d04,3,1,286) at ioctl+0x370 syscall(3b,3b,3b,8056da0,0) at syscall+0x22f Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280d0a97, esp = 0xbfbfe99c, ebp = 0xbfbfe9c8 --- malloc(M_WAITOK) of "64", forcing M_NOWAIT with the following non-sleepable locks held: exclusive sleep mutex if_addr_mtx r = 0 (0xc23af260) locked @ /usr/src/sys/net/if.c:1905 KDB: stack backtrace: kdb_backtrace(1,40,c104d800,2,e4f46998) at kdb_backtrace+0x29 witness_warn(5,0,c06ebd16,c06d9c8c,40) at witness_warn+0x18e uma_zalloc_arg(c104d800,0,102) at uma_zalloc_arg+0x41 malloc(36,c071f4e0,102,0,c23af000) at malloc+0xae ether_resolvemulti(c23af000,e4f469f4,e4f46a24,c2619700,0) at ether_resolvemulti+0x124 if_addmulti(c23af000,e4f46a24,e4f46a20,e4f46a24,1c) at if_addmulti+0x84 in6_addmulti(e4f46ac4,c23af000,e4f46a84,1,e4f46abc,c261a8a0,e4f46a9c,101,0) at in6_addmulti+0x4c in6_update_ifa(c23af000,e4f46b8c,0) at in6_update_ifa+0x60d in6_ifattach_linklocal(c23af000,0) at in6_ifattach_linklocal+0xe5 in6_ifattach(c23af000,0,8040691a,8040691a,0) at in6_ifattach+0xb9 in6_if_up(c23af000) at in6_if_up+0x13 ifioctl(c2707b20,8040691a,c2627540,c235b180,0) at ifioctl+0x1f8 soo_ioctl(c2662360,8040691a,c2627540,c225bd00,c235b180) at soo_ioctl+0x2db ioctl(c235b180,e4f46d04,3,1,286) at ioctl+0x370 syscall(3b,3b,3b,8056da0,0) at syscall+0x22f Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280d0a97, esp = 0xbfbfe99c, ebp = 0xbfbfe9c8 --- -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "anyone new to programming should be kept as far from C++ as possible; actually showing the stuff should be considered a criminal offence" -- Jacek Generowicz From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 16:28:10 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05F6616A41F for ; Tue, 30 Aug 2005 16:28:10 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2285143D46 for ; Tue, 30 Aug 2005 16:28:08 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from palle.girgensohn.se ([213.114.205.87] [213.114.205.87]) by mxfep02.bredband.com with ESMTP id <20050830162808.GUHV27212.mxfep02.bredband.com@palle.girgensohn.se> for ; Tue, 30 Aug 2005 18:28:08 +0200 Received: from localhost (palle.girgensohn.se [127.0.0.1]) by palle.girgensohn.se (Postfix) with ESMTP id E6EF91D982 for ; Tue, 30 Aug 2005 18:28:07 +0200 (CEST) Received: from palle.girgensohn.se ([127.0.0.1]) by localhost (palle.girgensohn.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 45752-05 for ; Tue, 30 Aug 2005 18:28:07 +0200 (CEST) Received: from palle.girgensohn.se (palle.girgensohn.se [127.0.0.1]) by palle.girgensohn.se (Postfix) with ESMTP id ABA9E1D97F for ; Tue, 30 Aug 2005 18:28:07 +0200 (CEST) Date: Tue, 30 Aug 2005 18:28:07 +0200 From: Palle Girgensohn To: stable@freebsd.org Message-ID: <68354869600D842FEADAA117@palle.girgensohn.se> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at pingpong.net Cc: Subject: linking problems with heimdal in base (ports version works) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 16:28:10 -0000 Hi! I'm having some difficulties using the heimdal installed from /usr/src. Here's the difference between the heimdal port and the heimdal distributed in the base: $ ldd /usr/local/lib/libkrb5.so /usr/local/lib/libkrb5.so: libcrypto.so.3 => /lib/libcrypto.so.3 (0x281b3000) libasn1.so.6 => /usr/local/lib/libasn1.so.6 (0x282c4000) libroken.so.16 => /usr/local/lib/libroken.so.16 (0x282ea000) libcrypt.so.2 => /lib/libcrypt.so.2 (0x282f8000) libcom_err.so.2 => /usr/lib/libcom_err.so.2 (0x28311000) $ ldd /usr/lib/libkrb5.so /usr/lib/libkrb5.so: $ This gives me problems. I maintain the postgresql ports, and postgresql supports Kerberos. Problem is, when installing the heimdal port, everything works fine, but when using the base heimdal, I can't get programs linking with postgresq's libpq.so to link, since the configure scripts cannot find symbols that are in for example libasn1.so. Most ports seem to only pick up the -lkrb5, not all the other libs needed. Shouldn't they be provided by libkrb5.so in the same way as the ports' version does? An example: make sure there's no heimdal port installed install databases/postgresql80-client with heimdal kerberos support (make config; make install) then try to build databases/postgresql-libpqxx it fails when it cannot find a bunch of symbols in libkrb5.so (they exist in the other libs listed above). configure:20825: checking for ability to link with libpq configure:20828: checking for main in -lpq configure:20852: cc -o conftest -O -pipe -march=athlon-xp -I/usr/local/include -L/usr/local/lib conftest.c -lpq -L/usr/local/lib >&5 /usr/lib/libkrb5.so.7: undefined reference to `length_PA_ENC_TS_ENC' /usr/lib/libkrb5.so.7: undefined reference to `length_KDC_REQ_BODY' /usr/lib/libkrb5.so.7: undefined reference to `free_Principal' /usr/lib/libkrb5.so.7: undefined reference to `bswap16' /usr/lib/libkrb5.so.7: undefined reference to `length_EncKrbCredPart' /usr/lib/libkrb5.so.7: undefined reference to `copy_Realm' /usr/lib/libkrb5.so.7: undefined reference to `strlwr' /usr/lib/libkrb5.so.7: undefined reference to `length_TGS_REQ' ... I don't now enough about the inner secrets of linking, but I do know that the way the heimdal port's libkrb5.so is built and installed, everything works, whereas the base heimdal makes it fail. FreeBSD-5-stable & 5.4p6 Any ideas how to pursue this? Thanks, Palle From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 18:17:45 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 875C016A41F for ; Tue, 30 Aug 2005 18:17:42 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E80643D95 for ; Tue, 30 Aug 2005 18:11:07 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j7UIApUl003904 for ; Tue, 30 Aug 2005 11:10:51 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j7UIAp6M003903 for freebsd-stable@freebsd.org; Tue, 30 Aug 2005 11:10:51 -0700 Date: Tue, 30 Aug 2005 11:10:51 -0700 From: Brooks Davis To: freebsd-stable@freebsd.org Message-ID: <20050830181051.GB22722@odin.ac.hmc.edu> References: <200508301412.j7UECbaB092796@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gj572EiMnwbLXET9" Content-Disposition: inline In-Reply-To: <200508301412.j7UECbaB092796@lurza.secnetix.de> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Subject: Re: WITNESS warning output from 6.0-BETA3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 18:17:45 -0000 --gj572EiMnwbLXET9 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment Content-Transfer-Encoding: quoted-printable On Tue, Aug 30, 2005 at 04:12:37PM +0200, Oliver Fromme wrote: > Hi, >=20 > I get the following output under FreeBSD 6.0-BETA3 when > WITNESS is enabled. It doesn't seem to cause any harm, > though. I cvsupped this system to RELENG_6 a few days > ago. >=20 > I have no idea what is causing this output, whether=20 > should worry about it, or even whether this is the right > list to report or ask about it. :-) >=20 > The output occurs when booting, right when the interface > (bfe0) is configured for the first time. I have a small > self-made script in /etc/rc.d which configures bfe0 > several times with different IP addresses and performs > a ping test in order to find out in which network the > notebook is located, then symlinks various files in /etc > depending on the result. The below output happens when > that script is executed. This is fixed in HEAD, rev 1.195 of sys/net/if_ethersubr.c. It probably should be further fixed by removing the MALLOC() macros. -- Brooks --gj572EiMnwbLXET9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDFKEqXY6L6fI4GtQRAm3mAKDiDJlwvJ0pHSYc2tppY8O8CdTAIgCeOB2g jjFcVB95rffz0ho0oevfjWI= =PdAi -----END PGP SIGNATURE----- --gj572EiMnwbLXET9-- From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 18:55:51 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51D3916A41F for ; Tue, 30 Aug 2005 18:55:51 +0000 (GMT) (envelope-from pete@he.iki.fi) Received: from rms06.rommon.net (rms06.rommon.net [212.54.5.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03E1143D46 for ; Tue, 30 Aug 2005 18:55:50 +0000 (GMT) (envelope-from pete@he.iki.fi) Received: from [193.64.42.234] (dyn234.helenius.fi [193.64.42.234]) by rms06.rommon.net (Postfix) with ESMTP id AF12F33C1B for ; Tue, 30 Aug 2005 21:55:44 +0300 (EEST) Message-ID: <4314ABB3.2060805@he.iki.fi> Date: Tue, 30 Aug 2005 21:55:47 +0300 From: Petri Helenius User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 6.0-beta3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 18:55:51 -0000 Any idea if 6.0-BETA3 should be able to boot from USB CD-ROM? On a VIA C3 system it hangs after displaying the | / - character at the boot loader? Pete From owner-freebsd-stable@FreeBSD.ORG Tue Aug 30 21:52:11 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E42616A41F for ; Tue, 30 Aug 2005 21:52:11 +0000 (GMT) (envelope-from martin@dbtech.net) Received: from dbtsvr1.dbtech.net (dbtsvr1.dbtech.net [204.214.208.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A480443D49 for ; Tue, 30 Aug 2005 21:52:10 +0000 (GMT) (envelope-from martin@dbtech.net) Received: from [204.214.213.37] (martin.dbtech.net [204.214.213.37]) by dbtsvr1.dbtech.net (8.9.3p2/8.9.3) with ESMTP id QAA00770 for ; Tue, 30 Aug 2005 16:52:08 -0500 (CDT) Mime-Version: 1.0 (Apple Message framework v734) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-stable@freebsd.org From: Martin Dorschler Date: Tue, 30 Aug 2005 16:45:04 -0500 X-Mailer: Apple Mail (2.734) Subject: USB Drive(s) not detected on P4SCE Motherboard under FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 21:52:11 -0000 USB drives are not detected on boot (and rarely when connected after booting) on P4SCE Mobo (Intel E7210 chipset) Tried with Seagate 9w2874 and different enclosures w/ WD & Maxtor Only Occurs under FreeBSD (have tried 5.3 & 5.4) with this board (OpenBSD detects fine and FreeBSD w/ other Mobo's works fine) Suggestions? Patches? From owner-freebsd-stable@FreeBSD.ORG Wed Aug 31 05:01:41 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3319E16A41F for ; Wed, 31 Aug 2005 05:01:41 +0000 (GMT) (envelope-from decibel@decibel.org) Received: from flake.decibel.org (flake.decibel.org [67.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C38A443D46 for ; Wed, 31 Aug 2005 05:01:38 +0000 (GMT) (envelope-from decibel@decibel.org) Received: by flake.decibel.org (Postfix, from userid 1001) id 09D75152BB; Wed, 31 Aug 2005 00:01:37 -0500 (CDT) Date: Wed, 31 Aug 2005 00:01:37 -0500 From: "Jim C. Nasby" To: Robert Backhaus Message-ID: <20050831050137.GQ77007@decibel.org> References: <55023220@srv.sem.ipt.ru> <20050828150947.GA58038@82-168-75-155-bbxl.xdsl.tiscali.nl> <4312B091.9090104@meijome.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 4.11-RELEASE-p10 i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.9i Cc: stable@freebsd.org, Norberto Meijome Subject: Re: 6.0 and -O2 option X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 05:01:41 -0000 On Tue, Aug 30, 2005 at 10:57:53AM +1000, Robert Backhaus wrote: > > > Kernel and world seem to be ok with -O2, for ports it is not advised. > > > > Hi, > > I may have missed a thread or something (just let me know :) ) - why is > > -O2 not advised for ports on 6.0? > > cheers, > > Beto > > Simply because not every port works with -O2 optimisations. It caused > bad code in some circumstances. Is there an automated way to identify those ports so they can be forced not to use -O higer than -O1? -- Jim C. Nasby, Database Architect decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" From owner-freebsd-stable@FreeBSD.ORG Wed Aug 31 06:07:26 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D81E616A41F for ; Wed, 31 Aug 2005 06:07:26 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90F6C43D46 for ; Wed, 31 Aug 2005 06:07:26 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from SMILEY (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id B741519F3B; Tue, 30 Aug 2005 23:10:50 -0700 (PDT) From: "Darren Pilgrim" To: "'Julian H. Stacey'" , "'Steven Hartland'" Date: Tue, 30 Aug 2005 23:07:16 -0700 Message-ID: <002101c5adf2$3db52620$642a15ac@SMILEY> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 In-Reply-To: <200508301216.j7UCGqv6069212@fire.jhs.private> Importance: Normal Cc: freebsd-stable@freebsd.org Subject: RE: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 06:07:27 -0000 From: Julian H. Stacey > "Steven Hartland" wrote: > > data. In addition to that I dont have to sit though 1 hour worth of=20 > > offline checks when it crashes for what ever reason which I do on our=20 > > FreeBSD boxes. >=20 > [Apologies if I missed something, coming in late on thread, but ...] >=20 > FreeBSD-4 does fsck on dirty filesystems before going multi=20 > user: You wait. > FreeBSD-5.* & 6.0-BETA3 : fsck runs in background after boot:=20 > No waiting. A dirty volume can cause some fairly severe problems if it's used before the background fsck completes repairs. I'd rather delay restart than face even more damage when something else dies because the volume was mounted dirty. From owner-freebsd-stable@FreeBSD.ORG Wed Aug 31 10:51:03 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2211B16A41F for ; Wed, 31 Aug 2005 10:51:03 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F5D343D46 for ; Wed, 31 Aug 2005 10:51:02 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from eirik.unicore.no ([213.225.74.166] helo=[10.0.16.10]) by anduin.net with esmtpa (Exim 4.50 (FreeBSD)) id 1EAQBJ-000IQD-4X for stable@freebsd.org; Wed, 31 Aug 2005 12:51:01 +0200 Mime-Version: 1.0 (Apple Message framework v734) Content-Transfer-Encoding: 7bit Message-Id: <25EF7E8A-5186-483C-9032-108CD3F53911@anduin.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: stable@freebsd.org From: =?ISO-8859-1?Q?Eirik_=D8verby?= Date: Wed, 31 Aug 2005 12:51:00 +0200 X-Mailer: Apple Mail (2.734) Cc: Subject: 5.4-dropping to debugger X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 10:51:03 -0000 Hi, every once in a while (about once a week lately), one of my servers has been known to stop responding. Upon connecting the serial console, I find myself at a debugger prompt. This is the output I've gotten this time. I do think I have a debug kernel on that machine, what can I do to get more useful information out? PS: I have seen various kinds of instability on most of my 5.4- installations, no matter the patchlevel. This box is just one of many. Anyone? /Eirik db> db> c Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x2007010 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0581fe8 stack pointer = 0x10:0xe3384c40 frame pointer = 0x10:0xe3384c70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 29 (irq18: fxp0) [thread pid 29 tid 100000 ] Stopped at fxp_add_rfabuf+0x68: movw %ax,0xe(%ebx) db> trace Tracing pid 29 tid 100000 td 0xc22a0000 fxp_add_rfabuf(c2404000,c2404500,2,a6c54bb2,b51487f8) at fxp_add_rfabuf+0x68 fxp_intr_body(c2404000,c2404000,40,ffffffff,8) at fxp_intr_body+0xf1 fxp_intr(c2404000,0,0,0,0) at fxp_intr+0x14e ithread_loop(c22f6500,e3384d38,0,0,0) at ithread_loop+0x1b8 fork_exit(c06a9150,c22f6500,e3384d38) at fork_exit+0x80 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe3384d6c, ebp = 0 --- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 31 13:16:46 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 521A816A41F for ; Wed, 31 Aug 2005 13:16:46 +0000 (GMT) (envelope-from bob@mail.boulderlabs.com) Received: from mail.boulderlabs.com (mail.boulderlabs.com [206.168.112.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C66143D55 for ; Wed, 31 Aug 2005 13:16:45 +0000 (GMT) (envelope-from bob@mail.boulderlabs.com) Received: from easter.boulderlabs.com (cpe-24-221-212-162.co.sprintbbd.net [24.221.212.162]) by mail.boulderlabs.com (8.12.9p2/8.12.9) with ESMTP id j7VDGhR6001082 for ; Wed, 31 Aug 2005 07:16:44 -0600 (MDT) (envelope-from bob@mail.boulderlabs.com) Received: from easter.boulderlabs.com (localhost.boulderlabs.com [127.0.0.1]) by easter.boulderlabs.com (8.13.1/8.13.1) with ESMTP id j7VDGcZZ007559 for ; Wed, 31 Aug 2005 07:16:38 -0600 (MDT) (envelope-from bob@easter.boulderlabs.com) Message-Id: <200508311316.j7VDGcZZ007559@easter.boulderlabs.com> From: Robert Gray To: freebsd-stable@freebsd.org Date: Wed, 31 Aug 2005 07:16:38 -0600 Sender: bob@boulderlabs.com X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (mail.boulderlabs.com [206.168.112.48]); Wed, 31 Aug 2005 07:16:44 -0600 (MDT) Subject: FreeBSD 6.0-BETA3 panic: vm_fault X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 13:16:46 -0000 I have a low end DELL Lattitude that has been successfully running 5.4-RELEASE. I have tried loading 6.0-BETA3 three times and it panics every time early while loading the Minimal system. Does anyone else see this? (I haven't ruled out a disk problem) Hand transcribed from the screen: panic: vm_fault: fault on nofault entry: c7229000 cpuid = 0 [thread pid 26 100026] Stopped at kbd_enter_0x2b: nop For the install process, I pick "Standard", Give the whole disk to slice1 for FreeBSD and take the "Auto" partitions. I ask for a "Minimal" install. (side note: the new default partitions sizes seem strange:) 1a / 512MB 1b swap 230MB 1d /var 1139MB 1e /tmp 512MB 1f /usr 708MB I retried loading 5.4 Release, and it successfully installs. Here is the dmesg from a working 5.4-RELEASE Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (363.96-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 134135808 (127 MB) avail memory = 121597952 (115 MB) npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf4000000-0xf7ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcm0: mem 0xfda00000-0xfdafffff,0xf8c00000-0xf8ffffff irq 5 at device 0.1 on pci1 pcm0: cbb0: at device 3.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: at device 3.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x860-0x86f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at dev ice 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0xece0-0xecff irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 7.3 (no driver attached) acpi_tz0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xcf800-0xcffff,0xcf000-0xcf7ff,0xce800-0xcefff,0xce000-0xce7ff,0xc pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 From owner-freebsd-stable@FreeBSD.ORG Wed Aug 31 14:57:08 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3097216A41F for ; Wed, 31 Aug 2005 14:57:08 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id C14C843D45 for ; Wed, 31 Aug 2005 14:57:07 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 0344C5F72; Wed, 31 Aug 2005 10:57:07 -0400 (EDT) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35527-10; Wed, 31 Aug 2005 10:57:05 -0400 (EDT) Received: from [192.168.1.3] (pool-68-161-79-217.ny325.east.verizon.net [68.161.79.217]) by pi.codefab.com (Postfix) with ESMTP id D76EF5D5D; Wed, 31 Aug 2005 10:57:04 -0400 (EDT) Message-ID: <4315C541.7050000@mac.com> Date: Wed, 31 Aug 2005 10:57:05 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.11) Gecko/20050801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jim C. Nasby" References: <55023220@srv.sem.ipt.ru> <20050828150947.GA58038@82-168-75-155-bbxl.xdsl.tiscali.nl> <4312B091.9090104@meijome.net> <20050831050137.GQ77007@decibel.org> In-Reply-To: <20050831050137.GQ77007@decibel.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: stable@freebsd.org Subject: Re: 6.0 and -O2 option X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 14:57:08 -0000 Jim C. Nasby wrote: > On Tue, Aug 30, 2005 at 10:57:53AM +1000, Robert Backhaus wrote: [ ... ] >> Simply because not every port works with -O2 optimisations. It caused >> bad code in some circumstances. > > Is there an automated way to identify those ports so they can be forced > not to use -O higer than -O1? Regrettably, no. Well, -Werror might be somewhere between overkill and helpful, assuming the compiler can recognize a potential type-punning situation. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Wed Aug 31 18:07:45 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6796216A41F for ; Wed, 31 Aug 2005 18:07:45 +0000 (GMT) (envelope-from ups@tree.com) Received: from smtp.speedfactory.net (smtp.speedfactory.net [66.23.216.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2F5443D48 for ; Wed, 31 Aug 2005 18:07:44 +0000 (GMT) (envelope-from ups@tree.com) Received: (qmail 21810 invoked by uid 210); 31 Aug 2005 18:08:52 +0000 Received: from 66.23.216.49 by talon (envelope-from , uid 201) with qmail-scanner-1.25st (clamdscan: 0.85.1/1048. spamassassin: 3.0.2. perlscan: 1.25st. Clear:RC:1(66.23.216.49):. Processed in 1.392382 secs); 31 Aug 2005 18:08:52 -0000 X-Qmail-Scanner-Mail-From: ups@tree.com via talon X-Qmail-Scanner: 1.25st (Clear:RC:1(66.23.216.49):. Processed in 1.392382 secs Process 21781) Received: from 66-23-216-49.clients.speedfactory.net (HELO palm.tree.com) (66.23.216.49) by smtp.speedfactory.net with AES256-SHA encrypted SMTP; 31 Aug 2005 18:08:51 +0000 Received: from [127.0.0.1] (ups@localhost.tree.com [127.0.0.1]) by palm.tree.com (8.12.10/8.12.10) with ESMTP id j7VI7QrK039211; Wed, 31 Aug 2005 14:07:28 -0400 (EDT) (envelope-from ups@tree.com) From: Stephan Uphoff To: Igor Sysoev In-Reply-To: <20050827113009.T76380@is.park.rambler.ru> References: <6.2.3.4.0.20050823204153.057f8cf0@10.20.30.100> <20050827113009.T76380@is.park.rambler.ru> Content-Type: text/plain Message-Id: <1125511646.74421.1382.camel@palm> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 31 Aug 2005 14:07:26 -0400 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: thanks for commiting (MFC ffs_softdep.c 1.182, softdep.h 1.18) to RELENG_5 and 6. When in 4? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 18:07:45 -0000 On Sat, 2005-08-27 at 03:51, Igor Sysoev wrote: > On Tue, 23 Aug 2005, Tomaz Borstnar wrote: > > > Would some kind soul MFC ffs_softdep.c 1.182, softdep.h 1.18 into > > RELENG_4 as well? This bug is also present in FreeBSD 4.x. Found it ever > > since 4.7. > > I saw this annoying bug at least since 4.5. I think the fix should be > merged not only to RELENG_4, but also at least to RELENG_4_11. > > I use very similar fix on two 4.10 machines and one 4.11 machine for 6 weeks. > Before the fix I had to reboot one of these machines at least once per month > and so. Now the bug has gone. > > Thank you, Stephan! Glad to hear your success. I finally managed to merge it into RELENG_4. (Sorry for the long delay) However I don't think we normally merge non-security related fixes to RELENG_4_11. (But I will ask around to make sure) Stephan From owner-freebsd-stable@FreeBSD.ORG Wed Aug 31 18:28:17 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE65716A41F for ; Wed, 31 Aug 2005 18:28:17 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fileserver.fields.utoronto.ca (fileserver.fields.utoronto.ca [128.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C30243D45 for ; Wed, 31 Aug 2005 18:28:17 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from fields.fields.utoronto.ca (fields.localdomain [192.168.216.11]) by fileserver.fields.utoronto.ca (8.12.8/8.12.8/Fields 6.0) with ESMTP id j7VISFvf001584 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Aug 2005 14:28:15 -0400 Received: from obsecurity.dyndns.org (localhost.localdomain [127.0.0.1]) by fields.fields.utoronto.ca (8.12.8/8.12.8/Fields WS 6.0) with ESMTP id j7VISE6P020646; Wed, 31 Aug 2005 14:28:14 -0400 Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9CD46511FD; Wed, 31 Aug 2005 14:28:13 -0400 (EDT) Date: Wed, 31 Aug 2005 14:28:13 -0400 From: Kris Kennaway To: Eirik ?verby Message-ID: <20050831182813.GA1847@xor.obsecurity.org> References: <25EF7E8A-5186-483C-9032-108CD3F53911@anduin.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline In-Reply-To: <25EF7E8A-5186-483C-9032-108CD3F53911@anduin.net> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: 5.4-dropping to debugger X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 18:28:18 -0000 --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 31, 2005 at 12:51:00PM +0200, Eirik ?verby wrote: > Hi, every once in a while (about once a week lately), one of my =20 > servers has been known to stop responding. Upon connecting the serial =20 > console, I find myself at a debugger prompt. This is the output I've =20 > gotten this time. >=20 > I do think I have a debug kernel on that machine, what can I do to =20 > get more useful information out? See the chapter on kernel debugging in the developers' handbook. Kris >=20 > PS: I have seen various kinds of instability on most of my 5.4-=20 > installations, no matter the patchlevel. This box is just one of many. >=20 > Anyone? >=20 > /Eirik >=20 > db> > db> c > Fatal trap 12: page fault while in kernel mode > cpuid =3D 1; apic id =3D 01 > fault virtual address =3D 0x2007010 > fault code =3D supervisor write, page not present > instruction pointer =3D 0x8:0xc0581fe8 > stack pointer =3D 0x10:0xe3384c40 > frame pointer =3D 0x10:0xe3384c70 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, def32 1, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D 29 (irq18: fxp0) > [thread pid 29 tid 100000 ] > Stopped at fxp_add_rfabuf+0x68: movw %ax,0xe(%ebx) > db> trace > Tracing pid 29 tid 100000 td 0xc22a0000 > fxp_add_rfabuf(c2404000,c2404500,2,a6c54bb2,b51487f8) at =20 > fxp_add_rfabuf+0x68 > fxp_intr_body(c2404000,c2404000,40,ffffffff,8) at fxp_intr_body+0xf1 > fxp_intr(c2404000,0,0,0,0) at fxp_intr+0x14e > ithread_loop(c22f6500,e3384d38,0,0,0) at ithread_loop+0x1b8 > fork_exit(c06a9150,c22f6500,e3384d38) at fork_exit+0x80 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip =3D 0, esp =3D 0xe3384d6c, ebp =3D 0 --- >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >=20 --n8g4imXOkfNTN/H1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDFfa9Wry0BWjoQKURAq8JAKC1XpCwuc9ESQuHIes5J5uDrNEdswCbBnsB WnQkV5oNiEJRjB9ZlMhH0Os= =hYFJ -----END PGP SIGNATURE----- --n8g4imXOkfNTN/H1-- From owner-freebsd-stable@FreeBSD.ORG Wed Aug 31 18:30:29 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BCC016A41F for ; Wed, 31 Aug 2005 18:30:29 +0000 (GMT) (envelope-from is@rambler-co.ru) Received: from yam.park.rambler.ru (yam.park.rambler.ru [81.19.64.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8547A43D4C for ; Wed, 31 Aug 2005 18:30:27 +0000 (GMT) (envelope-from is@rambler-co.ru) Received: from is.park.rambler.ru (is.park.rambler.ru [81.19.64.102]) by yam.park.rambler.ru (8.13.3/8.13.3) with ESMTP id j7VIUPl8096228; Wed, 31 Aug 2005 22:30:25 +0400 (MSD) (envelope-from is@rambler-co.ru) Date: Wed, 31 Aug 2005 22:30:25 +0400 (MSD) From: Igor Sysoev X-X-Sender: is@is.park.rambler.ru To: Stephan Uphoff In-Reply-To: <1125511646.74421.1382.camel@palm> Message-ID: <20050831221131.P9591@is.park.rambler.ru> References: <6.2.3.4.0.20050823204153.057f8cf0@10.20.30.100> <20050827113009.T76380@is.park.rambler.ru> <1125511646.74421.1382.camel@palm> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: thanks for commiting (MFC ffs_softdep.c 1.182, softdep.h 1.18) to RELENG_5 and 6. When in 4? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 18:30:29 -0000 On Wed, 31 Aug 2005, Stephan Uphoff wrote: > On Sat, 2005-08-27 at 03:51, Igor Sysoev wrote: >> On Tue, 23 Aug 2005, Tomaz Borstnar wrote: >> >>> Would some kind soul MFC ffs_softdep.c 1.182, softdep.h 1.18 into >>> RELENG_4 as well? This bug is also present in FreeBSD 4.x. Found it ever >>> since 4.7. >> >> I saw this annoying bug at least since 4.5. I think the fix should be >> merged not only to RELENG_4, but also at least to RELENG_4_11. >> >> I use very similar fix on two 4.10 machines and one 4.11 machine for 6 weeks. >> Before the fix I had to reboot one of these machines at least once per month >> and so. Now the bug has gone. >> >> Thank you, Stephan! > > Glad to hear your success. > I finally managed to merge it into RELENG_4. (Sorry for the long delay) > However I don't think we normally merge non-security related fixes to > RELENG_4_11. (But I will ask around to make sure) The bug is not directly security-related, however, I saw three various consequences of the bug: 1) The free space very quickly ends up. It usually happens when the big log files are used. I saw it very often. The only way to reclaim the space is to reboot. And then fsck would run on these partitions (and probably on other partitions if you forgot to umount them before reboot). 2) The free inodes ends up. I saw it once. Yes, the only way is the reboot. 2) The vnodes ends up. I saw it once: the most processes stuck in "inode" wchan. And yes, probably the only way is the hard reboot: you simply could not start the shutdown procedure. Igor Sysoev http://sysoev.ru/en/ From owner-freebsd-stable@FreeBSD.ORG Wed Aug 31 18:36:48 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEDBC16A41F for ; Wed, 31 Aug 2005 18:36:48 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C2C243D45 for ; Wed, 31 Aug 2005 18:36:48 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from ranger.anduin.net ([81.0.162.52] helo=[192.168.1.10]) by anduin.net with esmtpa (Exim 4.50 (FreeBSD)) id 1EAXS2-000MMk-Np; Wed, 31 Aug 2005 20:36:46 +0200 In-Reply-To: <20050831182813.GA1847@xor.obsecurity.org> References: <25EF7E8A-5186-483C-9032-108CD3F53911@anduin.net> <20050831182813.GA1847@xor.obsecurity.org> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: =?ISO-8859-1?Q?Eirik_=D8verby?= Date: Wed, 31 Aug 2005 20:36:44 +0200 To: Kris Kennaway X-Mailer: Apple Mail (2.734) Cc: stable@freebsd.org Subject: Re: 5.4-dropping to debugger X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 18:36:48 -0000 On Aug 31, 2005, at 8:28 PM, Kris Kennaway wrote: > On Wed, Aug 31, 2005 at 12:51:00PM +0200, Eirik ?verby wrote: > >> Hi, every once in a while (about once a week lately), one of my >> servers has been known to stop responding. Upon connecting the serial >> console, I find myself at a debugger prompt. This is the output I've >> gotten this time. >> >> I do think I have a debug kernel on that machine, what can I do to >> get more useful information out? >> > > See the chapter on kernel debugging in the developers' handbook. Sorry, poorly phrased question. Was in a bit of a hurry. I have a debug kernel, however I have no dump device (and cannot create one; I'm geom-mirroring my disks, and for some reason I'm not able to specify a dump device when that is the case (has been discussed in the past). I've been told that a debug kernel might still help, but the developers handbook does not say anything about what can be done without a dump. I know this has been up on one of the lists (current, stable or amd64) I'm on, so I guess I'll go ahead searching for it. Sorry about the noise. Was just hoping someone recognized the symptoms. /Eirik > Kris > > >> >> PS: I have seen various kinds of instability on most of my 5.4- >> installations, no matter the patchlevel. This box is just one of >> many. >> >> Anyone? >> >> /Eirik >> >> db> >> db> c >> Fatal trap 12: page fault while in kernel mode >> cpuid = 1; apic id = 01 >> fault virtual address = 0x2007010 >> fault code = supervisor write, page not present >> instruction pointer = 0x8:0xc0581fe8 >> stack pointer = 0x10:0xe3384c40 >> frame pointer = 0x10:0xe3384c70 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, def32 1, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 29 (irq18: fxp0) >> [thread pid 29 tid 100000 ] >> Stopped at fxp_add_rfabuf+0x68: movw %ax,0xe(%ebx) >> db> trace >> Tracing pid 29 tid 100000 td 0xc22a0000 >> fxp_add_rfabuf(c2404000,c2404500,2,a6c54bb2,b51487f8) at >> fxp_add_rfabuf+0x68 >> fxp_intr_body(c2404000,c2404000,40,ffffffff,8) at fxp_intr_body+0xf1 >> fxp_intr(c2404000,0,0,0,0) at fxp_intr+0x14e >> ithread_loop(c22f6500,e3384d38,0,0,0) at ithread_loop+0x1b8 >> fork_exit(c06a9150,c22f6500,e3384d38) at fork_exit+0x80 >> fork_trampoline() at fork_trampoline+0x8 >> --- trap 0x1, eip = 0, esp = 0xe3384d6c, ebp = 0 --- >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable- >> unsubscribe@freebsd.org" >> > From owner-freebsd-stable@FreeBSD.ORG Wed Aug 31 18:47:21 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBCC816A420 for ; Wed, 31 Aug 2005 18:47:21 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id A07E043D55 for ; Wed, 31 Aug 2005 18:47:21 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Wed, 31 Aug 2005 11:47:20 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 5505A5D07; Wed, 31 Aug 2005 11:47:20 -0700 (PDT) To: "Darren Pilgrim" In-reply-to: Your message of "Tue, 30 Aug 2005 23:07:16 PDT." <002101c5adf2$3db52620$642a15ac@SMILEY> Date: Wed, 31 Aug 2005 11:47:20 -0700 From: "Kevin Oberman" Message-Id: <20050831184720.5505A5D07@ptavv.es.net> Cc: freebsd-stable@freebsd.org, 'Steven Hartland' , "'Julian H. Stacey'" Subject: Re: Sysinstall automatic filesystem size generation. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 18:47:22 -0000 > From: "Darren Pilgrim" > Date: Tue, 30 Aug 2005 23:07:16 -0700 > Sender: owner-freebsd-stable@freebsd.org > > From: Julian H. Stacey > > "Steven Hartland" wrote: > > > data. In addition to that I dont have to sit though 1 hour worth of > > > offline checks when it crashes for what ever reason which I do on > our > > > FreeBSD boxes. > > > > [Apologies if I missed something, coming in late on thread, but ...] > > > > FreeBSD-4 does fsck on dirty filesystems before going multi > > user: You wait. > > FreeBSD-5.* & 6.0-BETA3 : fsck runs in background after boot: > > No waiting. > > A dirty volume can cause some fairly severe problems if it's used before > the background fsck completes repairs. I'd rather delay restart than > face even more damage when something else dies because the volume was > mounted dirty. This should NOT be the case if you have softupdates enabled for a partition. And fsck should not background if the partition does not have soft updates enabled. If the volume with soft updates is mounted 'dirty', it should have NO implications other then not having all of the free space on the disk available until the fsck completes. Read-write access should always be safe and no data should be effected by the fsck. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Wed Aug 31 18:56:31 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A469416A41F for ; Wed, 31 Aug 2005 18:56:31 +0000 (GMT) (envelope-from decibel@decibel.org) Received: from flake.decibel.org (flake.decibel.org [67.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27AB843D45 for ; Wed, 31 Aug 2005 18:56:30 +0000 (GMT) (envelope-from decibel@decibel.org) Received: by flake.decibel.org (Postfix, from userid 1001) id 6A95C1525C; Wed, 31 Aug 2005 13:56:30 -0500 (CDT) Date: Wed, 31 Aug 2005 13:56:30 -0500 From: "Jim C. Nasby" To: Chuck Swiger Message-ID: <20050831185630.GA98175@decibel.org> References: <55023220@srv.sem.ipt.ru> <20050828150947.GA58038@82-168-75-155-bbxl.xdsl.tiscali.nl> <4312B091.9090104@meijome.net> <20050831050137.GQ77007@decibel.org> <4315C541.7050000@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4315C541.7050000@mac.com> X-Operating-System: FreeBSD 4.11-RELEASE-p10 i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.9i Cc: stable@freebsd.org Subject: Re: 6.0 and -O2 option X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 18:56:31 -0000 On Wed, Aug 31, 2005 at 10:57:05AM -0400, Chuck Swiger wrote: > Jim C. Nasby wrote: > >On Tue, Aug 30, 2005 at 10:57:53AM +1000, Robert Backhaus wrote: > [ ... ] > >>Simply because not every port works with -O2 optimisations. It caused > >>bad code in some circumstances. > > > >Is there an automated way to identify those ports so they can be forced > >not to use -O higer than -O1? > > Regrettably, no. Well, -Werror might be somewhere between overkill and > helpful, assuming the compiler can recognize a potential type-punning > situation. Even if the identification can't be done automatically, it still seems like it would be good to start identifying ports that don't support -O by hand, and having the ports force a correct -O setting. Most ports support -O2 (if not -O3), and it would be nice if people could just put that option in their make.conf and be done with it. -- Jim C. Nasby, Database Architect decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?" From owner-freebsd-stable@FreeBSD.ORG Wed Aug 31 20:14:45 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EE8116A41F for ; Wed, 31 Aug 2005 20:14:45 +0000 (GMT) (envelope-from martin@gneto.com) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6630D43D62 for ; Wed, 31 Aug 2005 20:14:43 +0000 (GMT) (envelope-from martin@gneto.com) Received: from ua-83-227-181-30.cust.bredbandsbolaget.se ([83.227.181.30] [83.227.181.30]) by mxfep02.bredband.com with ESMTP id <20050831201442.SFQZ27212.mxfep02.bredband.com@ua-83-227-181-30.cust.bredbandsbolaget.se>; Wed, 31 Aug 2005 22:14:42 +0200 Received: from [192.168.10.11] (euklides.gneto.com [192.168.10.11]) by ua-83-227-181-30.cust.bredbandsbolaget.se (Postfix) with ESMTP id 74726678B9; Wed, 31 Aug 2005 22:14:41 +0200 (CEST) Message-ID: <43160FB1.5060206@gneto.com> Date: Wed, 31 Aug 2005 22:14:41 +0200 From: Martin Nilsson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050828) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jim C. Nasby" References: <55023220@srv.sem.ipt.ru> <20050828150947.GA58038@82-168-75-155-bbxl.xdsl.tiscali.nl> <4312B091.9090104@meijome.net> <20050831050137.GQ77007@decibel.org> <4315C541.7050000@mac.com> <20050831185630.GA98175@decibel.org> In-Reply-To: <20050831185630.GA98175@decibel.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: 6.0 and -O2 option X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 20:14:45 -0000 Jim C. Nasby wrote: > Even if the identification can't be done automatically, it still seems > like it would be good to start identifying ports that don't support -O > by hand, and having the ports force a correct -O setting. Most ports > support -O2 (if not -O3), and it would be nice if people could just put > that option in their make.conf and be done with it. It would be even better if we had some way to handle ports that work with make -j n and those who don't, as it is now a SMP machine is a total waste when compiling ports. /Martin From owner-freebsd-stable@FreeBSD.ORG Wed Aug 31 22:22:05 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F17F16A41F for ; Wed, 31 Aug 2005 22:22:05 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam.ru (gw.ipt.ru [80.253.10.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCCB043D46 for ; Wed, 31 Aug 2005 22:22:04 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam by bsam.ru with local (Exim 4.30; FreeBSD) id 1EAazw-0000Ha-Ch; Thu, 01 Sep 2005 02:24:00 +0400 To: Rene Ladan References: <55023220@srv.sem.ipt.ru> <20050828150947.GA58038@82-168-75-155-bbxl.xdsl.tiscali.nl> <51471998@srv.sem.ipt.ru> From: Boris Samorodov Date: Thu, 01 Sep 2005 02:24:00 +0400 In-Reply-To: <51471998@srv.sem.ipt.ru> (Boris Samorodov's message of "Tue, 30 Aug 2005 12:41:37 +0400") Message-ID: <62179647@srv.sem.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: "Boris B. Samorodov" Cc: stable@freebsd.org Subject: Re: 6.0 and -O2 option X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 22:22:05 -0000 On Tue, 30 Aug 2005 12:41:37 +0400 Boris Samorodov wrote: > On Sun, 28 Aug 2005 17:09:47 +0200 Rene Ladan wrote: > > On Sun, Aug 28, 2005 at 04:30:19PM +0400, Boris Samorodov wrote: > > > > > > As for 5.x notes about -O2 (libalias, gcc) were removed at revision > > > 1.229.2.7 of /usr/src/share/examples/etc/make.conf. But for 6.0-BETA3 > > > we do have these warnings. Should they be removed as for 5.x? Is it > > > safe to use -O2 to build/install kernel, world, ports fro 6.0? > > > > > Kernel and world seem to be ok with -O2, for ports it is not advised. > Well, as nobody complained so far, should I file a PR to remove notes > about -O2 to examples/etc/make.conf for 6.0-BETA3? OK. Here it is: ----- http://www.freebsd.org/cgi/query-pr.cgi?pr=85548 >Category: conf >Responsible: freebsd-bugs >Synopsis: share/examples/etc/make.conf: delete -O2 warnings for 6.0-BETA3 >Arrival-Date: Wed Aug 31 22:10:30 GMT 2005 ----- Who will take the resposibility? Oh, not all of you, guys... ;-) WBR -- bsam From owner-freebsd-stable@FreeBSD.ORG Thu Sep 1 03:49:10 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B8A216A41F for ; Thu, 1 Sep 2005 03:49:10 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B14C43D4C for ; Thu, 1 Sep 2005 03:49:09 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 2077746BBF for ; Wed, 31 Aug 2005 23:49:09 -0400 (EDT) Date: Thu, 1 Sep 2005 04:49:09 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: freebsd-stable@FreeBSD.ORG In-Reply-To: <200508301412.j7UECbaB092796@lurza.secnetix.de> Message-ID: <20050901044743.H83712@fledge.watson.org> References: <200508301412.j7UECbaB092796@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Re: WITNESS warning output from 6.0-BETA3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 03:49:10 -0000 On Tue, 30 Aug 2005, Oliver Fromme wrote: > I get the following output under FreeBSD 6.0-BETA3 when WITNESS is > enabled. It doesn't seem to cause any harm, though. I cvsupped this > system to RELENG_6 a few days ago. > > I have no idea what is causing this output, whether should worry about > it, or even whether this is the right list to report or ask about it. > :-) > > The output occurs when booting, right when the interface (bfe0) is > configured for the first time. I have a small self-made script in > /etc/rc.d which configures bfe0 several times with different IP > addresses and performs a ping test in order to find out in which network > the notebook is located, then symlinks various files in /etc depending > on the result. The below output happens when that script is executed. This warning is a result of a mis-ordering in merging changes from HEAD to RELENG_6: locking changes were merged shortly before the memory allocation changes they depended in. The warning should be non-harmful (although irritating), and can be corrected by sliding forward a bit on the RELENG_6 branch to pick up the fix that followed a little later. If it isn't corrected by a move to at least if_ethersubr.c:1.177.2.5, please let me know. Thanks, Robert N M Watson > Best regards > Oliver > > malloc(M_WAITOK) of "64", forcing M_NOWAIT with the following non-sleepable locks held: > exclusive sleep mutex if_addr_mtx r = 0 (0xc23af260) locked @ /usr/src/sys/net/if.c:1905 > KDB: stack backtrace: > kdb_backtrace(1,40,c104d800,2,e4f46b1c) at kdb_backtrace+0x29 > witness_warn(5,0,c06ebd16,c06d9c8c,40) at witness_warn+0x18e > uma_zalloc_arg(c104d800,0,102) at uma_zalloc_arg+0x41 > malloc(36,c071f4e0,102,0,c23af000) at malloc+0xae > ether_resolvemulti(c23af000,e4f46b78,e4f46ba8,c2641bc4,0) at ether_resolvemulti+0x87 > if_addmulti(c23af000,e4f46ba8,e4f46ba4,e4f46ba8,10) at if_addmulti+0x84 > in_addmulti(e4f46bdc,c23af000) at in_addmulti+0x32 > in_ifinit(c23af000,c2641b00,c2627550,0,e4f46c38) at in_ifinit+0x515 > in_control(c2707b20,8040691a,c2627540,c23af000,c235b180) at in_control+0x882 > ifioctl(c2707b20,8040691a,c2627540,c235b180,0) at ifioctl+0x198 > soo_ioctl(c2662360,8040691a,c2627540,c225bd00,c235b180) at soo_ioctl+0x2db > ioctl(c235b180,e4f46d04,3,1,286) at ioctl+0x370 > syscall(3b,3b,3b,8056da0,0) at syscall+0x22f > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280d0a97, esp = 0xbfbfe99c, ebp = 0xbfbfe9c8 --- > malloc(M_WAITOK) of "64", forcing M_NOWAIT with the following non-sleepable locks held: > exclusive sleep mutex if_addr_mtx r = 0 (0xc23af260) locked @ /usr/src/sys/net/if.c:1905 > KDB: stack backtrace: > kdb_backtrace(1,40,c104d800,2,e4f469b0) at kdb_backtrace+0x29 > witness_warn(5,0,c06ebd16,c06d9c8c,40) at witness_warn+0x18e > uma_zalloc_arg(c104d800,0,102) at uma_zalloc_arg+0x41 > malloc(36,c071f4e0,102,0,c23af000) at malloc+0xae > ether_resolvemulti(c23af000,e4f46a0c,e4f46a3c,0,0) at ether_resolvemulti+0x124 > if_addmulti(c23af000,e4f46a3c,e4f46a38,e4f46a3c,1c) at if_addmulti+0x84 > in6_addmulti(e4f46a8c,c23af000,e4f46a84) at in6_addmulti+0x4c > in6_update_ifa(c23af000,e4f46b8c,0) at in6_update_ifa+0x4cf > in6_ifattach_linklocal(c23af000,0) at in6_ifattach_linklocal+0xe5 > in6_ifattach(c23af000,0,8040691a,8040691a,0) at in6_ifattach+0xb9 > in6_if_up(c23af000) at in6_if_up+0x13 > ifioctl(c2707b20,8040691a,c2627540,c235b180,0) at ifioctl+0x1f8 > soo_ioctl(c2662360,8040691a,c2627540,c225bd00,c235b180) at soo_ioctl+0x2db > ioctl(c235b180,e4f46d04,3,1,286) at ioctl+0x370 > syscall(3b,3b,3b,8056da0,0) at syscall+0x22f > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280d0a97, esp = 0xbfbfe99c, ebp = 0xbfbfe9c8 --- > malloc(M_WAITOK) of "64", forcing M_NOWAIT with the following non-sleepable locks held: > exclusive sleep mutex if_addr_mtx r = 0 (0xc23af260) locked @ /usr/src/sys/net/if.c:1905 > KDB: stack backtrace: > kdb_backtrace(1,40,c104d800,2,e4f46998) at kdb_backtrace+0x29 > witness_warn(5,0,c06ebd16,c06d9c8c,40) at witness_warn+0x18e > uma_zalloc_arg(c104d800,0,102) at uma_zalloc_arg+0x41 > malloc(36,c071f4e0,102,0,c23af000) at malloc+0xae > ether_resolvemulti(c23af000,e4f469f4,e4f46a24,c2619700,0) at ether_resolvemulti+0x124 > if_addmulti(c23af000,e4f46a24,e4f46a20,e4f46a24,1c) at if_addmulti+0x84 > in6_addmulti(e4f46ac4,c23af000,e4f46a84,1,e4f46abc,c261a8a0,e4f46a9c,101,0) at in6_addmulti+0x4c > in6_update_ifa(c23af000,e4f46b8c,0) at in6_update_ifa+0x60d > in6_ifattach_linklocal(c23af000,0) at in6_ifattach_linklocal+0xe5 > in6_ifattach(c23af000,0,8040691a,8040691a,0) at in6_ifattach+0xb9 > in6_if_up(c23af000) at in6_if_up+0x13 > ifioctl(c2707b20,8040691a,c2627540,c235b180,0) at ifioctl+0x1f8 > soo_ioctl(c2662360,8040691a,c2627540,c225bd00,c235b180) at soo_ioctl+0x2db > ioctl(c235b180,e4f46d04,3,1,286) at ioctl+0x370 > syscall(3b,3b,3b,8056da0,0) at syscall+0x22f > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280d0a97, esp = 0xbfbfe99c, ebp = 0xbfbfe9c8 --- > > > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing > Any opinions expressed in this message may be personal to the author > and may not necessarily reflect the opinions of secnetix in any way. > > "anyone new to programming should be kept as far from C++ as > possible; actually showing the stuff should be considered a > criminal offence" -- Jacek Generowicz > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Thu Sep 1 13:15:27 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35D3816A41F for ; Thu, 1 Sep 2005 13:15:27 +0000 (GMT) (envelope-from edwin.brown@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C27243D48 for ; Thu, 1 Sep 2005 13:15:24 +0000 (GMT) (envelope-from edwin.brown@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so219710nzo for ; Thu, 01 Sep 2005 06:15:24 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=jUVibjdNeeznYb90udOjncWsWLsDYxGdhXzgtVDyryxNqvZZEdUubGKJ6+T+nIiXrKd7i+K7Q/IJY9Db04kzk6g6r2xKPbHL8QVJ0Z3eMCPzKJWadD560h1v6ZeQkzhfqBOdHAV0f86r0a0BPC/vDoxGfFL/uv8XjyWP0ufKWL8= Received: by 10.36.17.7 with SMTP id 7mr1538543nzq; Thu, 01 Sep 2005 06:14:53 -0700 (PDT) Received: by 10.36.61.10 with HTTP; Thu, 1 Sep 2005 06:15:08 -0700 (PDT) Message-ID: <8b6eae9605090106151a81174d@mail.gmail.com> Date: Thu, 1 Sep 2005 09:15:08 -0400 From: Edwin Brown To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: FreeBSD6.0 and VMWare 5.0.. No go X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 13:15:27 -0000 This morning I tried to install FreeBSD6.0 under VMWare 5. I got=20 the following message when it was extracting the base into \=20 directory: Panic: duplicate free of item 0xc1c5a210 from zone 0xc143f000(g_bio) cpuid=3D0 KDB: enter: panic [thread pid 3 tid 100034 ] stopped at kdb_enter+0x2b: nop db>=20 Is this a known issue?=20 Best regards, Edwin From owner-freebsd-stable@FreeBSD.ORG Thu Sep 1 19:59:25 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 245DD16A41F for ; Thu, 1 Sep 2005 19:59:25 +0000 (GMT) (envelope-from mathieu.y.prevot@wanadoo.fr) Received: from smtp7.wanadoo.fr (smtp7.wanadoo.fr [193.252.22.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7D9F43D49 for ; Thu, 1 Sep 2005 19:59:24 +0000 (GMT) (envelope-from mathieu.y.prevot@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0709.wanadoo.fr (SMTP Server) with ESMTP id 693901C000B3 for ; Thu, 1 Sep 2005 21:59:21 +0200 (CEST) Received: from [192.168.0.2] (APuteaux-151-1-2-143.w82-120.abo.wanadoo.fr [82.120.177.143]) by mwinf0709.wanadoo.fr (SMTP Server) with ESMTP id 3AB311C000B0 for ; Thu, 1 Sep 2005 21:59:21 +0200 (CEST) X-ME-UUID: 20050901195921240.3AB311C000B0@mwinf0709.wanadoo.fr Mime-Version: 1.0 (Apple Message framework v622) Content-Transfer-Encoding: 7bit Message-Id: <01ac2b857a762ef9bbaa48dc6b781cb3@wanadoo.fr> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-stable@freebsd.org From: Mathieu PREVOT Date: Thu, 1 Sep 2005 21:59:20 +0200 X-Mailer: Apple Mail (2.622) Subject: autologin only in one ttyv X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 19:59:25 -0000 Hi all! First, I appreciate very much freebsd that I use since nearly one year for scientific computation (simulation etc), writing C - sometimes threaded - programs, on mono and multi-core/CPU stations. I would like to autologin in *only one* ttyv (eg ttyv1) and then launch X with xinit manually or with a script. I used ":al=:" in /etc/gettytab and added or not xinit in /etc/, but it's not very satisfying! Hence, I would like this to occur only for ttyv1. Can someone help me? Regards, MP From owner-freebsd-stable@FreeBSD.ORG Thu Sep 1 19:59:36 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F47316A443 for ; Thu, 1 Sep 2005 19:59:36 +0000 (GMT) (envelope-from stephane@enertiasoft.com) Received: from mx1.enertiatech.com (a72-29-234-73.enertiatech.com [72.29.234.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6A7D43D45 for ; Thu, 1 Sep 2005 19:59:35 +0000 (GMT) (envelope-from stephane@enertiasoft.com) Received: from localhost (localhost [127.0.0.1]) by mx1.enertiatech.com (Postfix) with ESMTP id D3806631D for ; Thu, 1 Sep 2005 11:29:26 -0600 (MDT) Received: from mx1.enertiatech.com ([127.0.0.1]) by localhost (mx1.enertiatech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16944-01 for ; Thu, 1 Sep 2005 11:29:26 -0600 (MDT) Received: from [10.0.0.34] (unknown [10.0.0.34]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.enertiatech.com (Postfix) with ESMTP id 1103262C8 for ; Thu, 1 Sep 2005 11:29:26 -0600 (MDT) Mime-Version: 1.0 (Apple Message framework v734) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-stable@freebsd.org From: Stephane Raimbault Date: Thu, 1 Sep 2005 11:29:24 -0600 X-Mailer: Apple Mail (2.734) X-Virus-Scanned: amavisd-new at enertiasoft.com Subject: 5.4: Can't start ssh due to entropy source blocking? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 19:59:36 -0000 I installed a fresh 5.4-RELEASE/amd64 system on a Dell PE1850 and when attempting to setup sshd for the server I'm getting a weird error: # /etc/rc.d/sshd start /etc/rc.d/sshd: WARNING: Setting entropy source to blocking mode. ==================================================== Type a full screenful of random junk to unblock it and remember to finish with . This will timeout in 300 seconds, but waiting for the timeout without typing junk may make the entropy source deliver predictable output. Just hit for fast+insecure startup. ==================================================== kern.random.sys.seeded: 0 -> 0 PRNG is not seeded PRNG is not seeded PRNG is not seeded # I tried rebooting the system and letting it start a startup, but the same thing occurred. I've setup a few 5.4 systems and this is the first time I ran into this particular problem. Doing some googling I'm guessing that the /dev/random isn't seeded properly? I'm a bit confused about that, but that's all I have found thus far. Any suggestions as to what I need to be doing to resolve my problem would be most helpful. Has anyone else ran into this problem on a 5.4- RELEASE system. Thank you, Stephane. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 1 20:07:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B268916A41F for ; Thu, 1 Sep 2005 20:07:32 +0000 (GMT) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 130F743D48 for ; Thu, 1 Sep 2005 20:07:27 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id E6B0FB80F for ; Thu, 1 Sep 2005 16:07:26 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v734) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Thu, 1 Sep 2005 16:07:25 -0400 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.734) Subject: Re: 5.4: Can't start ssh due to entropy source blocking? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 20:07:32 -0000 On Sep 1, 2005, at 1:29 PM, Stephane Raimbault wrote: > Type a full screenful of random junk to unblock > it and remember to finish with . This will > timeout in 300 seconds, but waiting for > the timeout without typing junk may make the > entropy source deliver predictable output. > > Just hit for fast+insecure startup. > so what did you do, just hit enter or did you follow the instructions and type a screenful of junk? Vivek Khera, Ph.D. +1-301-869-4449 x806 From owner-freebsd-stable@FreeBSD.ORG Thu Sep 1 20:18:27 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE1C616A41F for ; Thu, 1 Sep 2005 20:18:27 +0000 (GMT) (envelope-from stephane@enertiasoft.com) Received: from mx1.enertiatech.com (a72-29-234-73.enertiatech.com [72.29.234.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E63543D46 for ; Thu, 1 Sep 2005 20:18:27 +0000 (GMT) (envelope-from stephane@enertiasoft.com) Received: from localhost (localhost [127.0.0.1]) by mx1.enertiatech.com (Postfix) with ESMTP id B5BA86375; Thu, 1 Sep 2005 14:18:26 -0600 (MDT) Received: from mx1.enertiatech.com ([127.0.0.1]) by localhost (mx1.enertiatech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25037-05; Thu, 1 Sep 2005 14:18:22 -0600 (MDT) Received: from [10.0.0.34] (unknown [10.0.0.34]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.enertiatech.com (Postfix) with ESMTP id BE000631D; Thu, 1 Sep 2005 14:18:22 -0600 (MDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Stephane Raimbault Date: Thu, 1 Sep 2005 14:18:21 -0600 To: Vivek Khera X-Mailer: Apple Mail (2.734) X-Virus-Scanned: amavisd-new at enertiasoft.com Cc: freebsd-stable@freebsd.org Subject: Re: 5.4: Can't start ssh due to entropy source blocking? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 20:18:27 -0000 yes sorry I wasn't more clear. I tried putting a bunch of junk on the screen as well as just left it blank and the result was the same. Is it possible I didn't provide enough junk? I haven't seen this behavior before? Thanks, Stephane On 1-Sep-05, at 2:07 PM, Vivek Khera wrote: > > On Sep 1, 2005, at 1:29 PM, Stephane Raimbault wrote: > > >> Type a full screenful of random junk to unblock >> it and remember to finish with . This will >> timeout in 300 seconds, but waiting for >> the timeout without typing junk may make the >> entropy source deliver predictable output. >> >> Just hit for fast+insecure startup. >> >> > > so what did you do, just hit enter or did you follow the > instructions and type a screenful of junk? > > > Vivek Khera, Ph.D. > +1-301-869-4449 x806 > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable- > unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Thu Sep 1 20:59:10 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE73016A421 for ; Thu, 1 Sep 2005 20:59:10 +0000 (GMT) (envelope-from KBuff@zetron.com) Received: from zetxch01.zetron.com (zetmail2.zetron.com [216.202.42.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1108243D6A for ; Thu, 1 Sep 2005 20:59:00 +0000 (GMT) (envelope-from KBuff@zetron.com) Received: by zetxch01.zetron.com with Internet Mail Service (5.5.2657.72) id ; Thu, 1 Sep 2005 13:58:58 -0700 Message-ID: <054222519C2ED411A68E00508B603AC70A3D08A4@zetxch01.zetron.com> From: Kurt Buff To: 'Stephane Raimbault' , Vivek Khera Date: Thu, 1 Sep 2005 13:58:56 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Cc: freebsd-stable@freebsd.org Subject: RE: 5.4: Can't start ssh due to entropy source blocking? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 20:59:11 -0000 I ran into it just yesterday. I was walking a newb in our IT department through setting up a server, and he used all caps for the domain.tld portion of the server name - testbed.ZETRON.COM. Had the same problem as you describe. Edited the /etc/rc.conf, had him reboot and try again, and it worked just fine. Kurt > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of > Stephane Raimbault > Sent: Thursday, September 01, 2005 13:18 > To: Vivek Khera > Cc: freebsd-stable@freebsd.org > Subject: Re: 5.4: Can't start ssh due to entropy source blocking? > > > yes sorry I wasn't more clear. I tried putting a bunch of junk on > the screen as well as just left it blank and the result was the > same. Is it possible I didn't provide enough junk? I haven't seen > this behavior before? > > Thanks, > Stephane > > On 1-Sep-05, at 2:07 PM, Vivek Khera wrote: > > > > > On Sep 1, 2005, at 1:29 PM, Stephane Raimbault wrote: > > > > > >> Type a full screenful of random junk to unblock > >> it and remember to finish with . This will > >> timeout in 300 seconds, but waiting for > >> the timeout without typing junk may make the > >> entropy source deliver predictable output. > >> > >> Just hit for fast+insecure startup. > >> > >> > > > > so what did you do, just hit enter or did you follow the > > instructions and type a screenful of junk? > > > > > > Vivek Khera, Ph.D. > > +1-301-869-4449 x806 > > > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable- > > unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Thu Sep 1 22:40:54 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2626416A421 for ; Thu, 1 Sep 2005 22:40:54 +0000 (GMT) (envelope-from stephane@enertiasoft.com) Received: from mx1.enertiatech.com (a72-29-234-73.enertiatech.com [72.29.234.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 468AE43D7E for ; Thu, 1 Sep 2005 22:40:43 +0000 (GMT) (envelope-from stephane@enertiasoft.com) Received: from localhost (localhost [127.0.0.1]) by mx1.enertiatech.com (Postfix) with ESMTP id 451BF638B; Thu, 1 Sep 2005 16:40:42 -0600 (MDT) Received: from mx1.enertiatech.com ([127.0.0.1]) by localhost (mx1.enertiatech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29647-06; Thu, 1 Sep 2005 16:40:39 -0600 (MDT) Received: from [10.0.0.34] (unknown [10.0.0.34]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.enertiatech.com (Postfix) with ESMTP id 920806384; Thu, 1 Sep 2005 16:40:39 -0600 (MDT) In-Reply-To: <054222519C2ED411A68E00508B603AC70A3D08A4@zetxch01.zetron.com> References: <054222519C2ED411A68E00508B603AC70A3D08A4@zetxch01.zetron.com> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Stephane Raimbault Date: Thu, 1 Sep 2005 16:40:38 -0600 To: Kurt Buff X-Mailer: Apple Mail (2.734) X-Virus-Scanned: amavisd-new at enertiasoft.com Cc: Vivek Khera , freebsd-stable@freebsd.org Subject: Re: 5.4: Can't start ssh due to entropy source blocking? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 22:40:54 -0000 Thanks for the suggestion, but it doesn't seem to be the case in my situation. However I did notice things like nslookup and host are now reporting this error after attempting to start /etc/rc.d/sshd start # host www.freebsd.org Entropy device is blocking. # nslookup www.freebsd.org Entropy device is blocking. I confirmed by rebooting the server and making sure sshd didn't try to start on bootup nslookup and host are working, as soon as I try to start sshd, I start getting the errors. I am baffled as to what is going on. Thank you, Stephane Raimbault, Systems Administrator Enertiasoft, a Premier Technologies Company 230n, 3015 5th Avenue NE Calgary, AB, Canada T2A 6T8 toll free. 866 ENE RTIA (363 7842) office. 403 228 9292 fax. 403 228 8993 On 1-Sep-05, at 2:58 PM, Kurt Buff wrote: > I ran into it just yesterday. > > I was walking a newb in our IT department through setting up a > server, and > he used all caps for the domain.tld portion of the server name - > testbed.ZETRON.COM. > > Had the same problem as you describe. Edited the /etc/rc.conf, had him > reboot and try again, and it worked just fine. > > Kurt > > >> -----Original Message----- >> From: owner-freebsd-stable@freebsd.org >> [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of >> Stephane Raimbault >> Sent: Thursday, September 01, 2005 13:18 >> To: Vivek Khera >> Cc: freebsd-stable@freebsd.org >> Subject: Re: 5.4: Can't start ssh due to entropy source blocking? >> >> >> yes sorry I wasn't more clear. I tried putting a bunch of junk on >> the screen as well as just left it blank and the result was the >> same. Is it possible I didn't provide enough junk? I haven't seen >> this behavior before? >> >> Thanks, >> Stephane >> >> On 1-Sep-05, at 2:07 PM, Vivek Khera wrote: >> >> >>> >>> On Sep 1, 2005, at 1:29 PM, Stephane Raimbault wrote: >>> >>> >>> >>>> Type a full screenful of random junk to unblock >>>> it and remember to finish with . This will >>>> timeout in 300 seconds, but waiting for >>>> the timeout without typing junk may make the >>>> entropy source deliver predictable output. >>>> >>>> Just hit for fast+insecure startup. >>>> >>>> >>>> >>> >>> so what did you do, just hit enter or did you follow the >>> instructions and type a screenful of junk? >>> >>> >>> Vivek Khera, Ph.D. >>> +1-301-869-4449 x806 >>> >>> >>> _______________________________________________ >>> freebsd-stable@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable- >>> unsubscribe@freebsd.org" >>> >>> >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to >> "freebsd-stable-unsubscribe@freebsd.org" >> >> > > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable- > unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Thu Sep 1 22:45:35 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 301EE16A42A for ; Thu, 1 Sep 2005 22:45:35 +0000 (GMT) (envelope-from stephane@enertiasoft.com) Received: from mx1.enertiatech.com (a72-29-234-73.enertiatech.com [72.29.234.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6FF943D45 for ; Thu, 1 Sep 2005 22:45:34 +0000 (GMT) (envelope-from stephane@enertiasoft.com) Received: from localhost (localhost [127.0.0.1]) by mx1.enertiatech.com (Postfix) with ESMTP id 4146D6328; Thu, 1 Sep 2005 16:45:34 -0600 (MDT) Received: from mx1.enertiatech.com ([127.0.0.1]) by localhost (mx1.enertiatech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30267-04; Thu, 1 Sep 2005 16:45:33 -0600 (MDT) Received: from [10.0.0.34] (unknown [10.0.0.34]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.enertiatech.com (Postfix) with ESMTP id 9DEDB62C8; Thu, 1 Sep 2005 16:45:32 -0600 (MDT) In-Reply-To: References: <054222519C2ED411A68E00508B603AC70A3D08A4@zetxch01.zetron.com> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <54BB9145-3838-4536-942C-8C4389A972C2@enertiasoft.com> Content-Transfer-Encoding: 7bit From: Stephane Raimbault Date: Thu, 1 Sep 2005 16:45:31 -0600 To: Stephane Raimbault X-Mailer: Apple Mail (2.734) X-Virus-Scanned: amavisd-new at enertiasoft.com Cc: Vivek Khera , Kurt Buff , freebsd-stable@freebsd.org Subject: Re: 5.4: Can't start ssh due to entropy source blocking? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 22:45:35 -0000 further more I just did another test and discovered that by setting this sysctl back (seems like /etc/rc.d/sshd start set's it to 0) sysctl -w kern.random.sys.seeded=1 I can do host and nslookup's again... however still the same problem with /etc/rc.d/sshd start. I'm not sure where I've gone wrong, it's was a pretty basic install, setup network, caching dns server, ntpd, and now trying to get sshd running. Any further thoughts or ideas? Thanks, Stephane On 1-Sep-05, at 4:40 PM, Stephane Raimbault wrote: > Thanks for the suggestion, but it doesn't seem to be the case in my > situation. > > However I did notice things like nslookup and host are now > reporting this error after attempting to start /etc/rc.d/sshd start > > # host www.freebsd.org > Entropy device is blocking. > > # nslookup www.freebsd.org > Entropy device is blocking. > > > I confirmed by rebooting the server and making sure sshd didn't try > to start on bootup nslookup and host are working, as soon as I try > to start sshd, I start getting the errors. > > I am baffled as to what is going on. > > Thank you, > Stephane > > On 1-Sep-05, at 2:58 PM, Kurt Buff wrote: > > >> I ran into it just yesterday. >> >> I was walking a newb in our IT department through setting up a >> server, and >> he used all caps for the domain.tld portion of the server name - >> testbed.ZETRON.COM. >> >> Had the same problem as you describe. Edited the /etc/rc.conf, had >> him >> reboot and try again, and it worked just fine. >> >> Kurt >> >> >> >>> -----Original Message----- >>> From: owner-freebsd-stable@freebsd.org >>> [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of >>> Stephane Raimbault >>> Sent: Thursday, September 01, 2005 13:18 >>> To: Vivek Khera >>> Cc: freebsd-stable@freebsd.org >>> Subject: Re: 5.4: Can't start ssh due to entropy source blocking? >>> >>> >>> yes sorry I wasn't more clear. I tried putting a bunch of junk on >>> the screen as well as just left it blank and the result was the >>> same. Is it possible I didn't provide enough junk? I haven't seen >>> this behavior before? >>> >>> Thanks, >>> Stephane >>> >>> On 1-Sep-05, at 2:07 PM, Vivek Khera wrote: >>> >>> >>> >>>> >>>> On Sep 1, 2005, at 1:29 PM, Stephane Raimbault wrote: >>>> >>>> >>>> >>>> >>>>> Type a full screenful of random junk to unblock >>>>> it and remember to finish with . This will >>>>> timeout in 300 seconds, but waiting for >>>>> the timeout without typing junk may make the >>>>> entropy source deliver predictable output. >>>>> >>>>> Just hit for fast+insecure startup. >>>>> >>>>> >>>>> >>>>> >>>> >>>> so what did you do, just hit enter or did you follow the >>>> instructions and type a screenful of junk? >>>> >>>> >>>> Vivek Khera, Ph.D. >>>> +1-301-869-4449 x806 >>>> >>>> >>>> _______________________________________________ >>>> freebsd-stable@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>> To unsubscribe, send any mail to "freebsd-stable- >>>> unsubscribe@freebsd.org" >>>> >>>> >>>> >>> >>> _______________________________________________ >>> freebsd-stable@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to >>> "freebsd-stable-unsubscribe@freebsd.org" >>> >>> >>> >> >> >> >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable- >> unsubscribe@freebsd.org" >> >> > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable- > unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Thu Sep 1 22:56:18 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACCB916A41F for ; Thu, 1 Sep 2005 22:56:18 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from maxlor.mine.nu (c-213-160-32-54.customer.ggaweb.ch [213.160.32.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C4F443D45 for ; Thu, 1 Sep 2005 22:56:18 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from localhost (localhost [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id E2AFD366; Fri, 2 Sep 2005 00:56:16 +0200 (CEST) Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (midgard.intranet [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15482-01; Fri, 2 Sep 2005 00:56:14 +0200 (CEST) Received: from [10.0.0.23] (mini.intranet [10.0.0.23]) by maxlor.mine.nu (Postfix) with ESMTP id 9F03D13E; Fri, 2 Sep 2005 00:56:14 +0200 (CEST) Message-ID: <43178708.3090503@datacomm.ch> Date: Fri, 02 Sep 2005 00:56:08 +0200 From: Benjamin Lutz User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mathieu PREVOT References: <01ac2b857a762ef9bbaa48dc6b781cb3@wanadoo.fr> In-Reply-To: <01ac2b857a762ef9bbaa48dc6b781cb3@wanadoo.fr> X-Enigmail-Version: 0.92.0.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF0F4BABBB68B8D050457745A" X-Virus-Scanned: amavisd-new at maxlor.mine.nu Cc: freebsd-stable@freebsd.org Subject: Re: autologin only in one ttyv X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 22:56:18 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF0F4BABBB68B8D050457745A Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mathieu PREVOT wrote: > I would like to autologin in *only one* ttyv (eg ttyv1) and then launch > X with xinit manually or with a script. Have a look at /etc/gettytab. Instead of starting getty, you could simply start a shell, like this: ttyv1 "/usr/bin/su - username" cons25 on secure If you want to start X right away, you could try ttyv1 "/usr/bin/su - username startx" cons25 on secure Cheers Benjamin --------------enigF0F4BABBB68B8D050457745A 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.0 (Darwin) iD8DBQFDF4cOgShs4qbRdeQRAtQEAJ4pewyb9/GOKdBYidxBOZ9U0MkA5QCdH6tO /X1TkTXm3LevPYk776No/bU= =qbA8 -----END PGP SIGNATURE----- --------------enigF0F4BABBB68B8D050457745A-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 1 23:47:35 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5C3E16A420 for ; Thu, 1 Sep 2005 23:47:35 +0000 (GMT) (envelope-from lists@mawer.org) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFC1143D46 for ; Thu, 1 Sep 2005 23:47:34 +0000 (GMT) (envelope-from lists@mawer.org) Received: from c211-30-90-140.belrs3.nsw.optusnet.com.au (c211-30-246-162.belrs3.nsw.optusnet.com.au [211.30.246.162]) by mail17.syd.optusnet.com.au (8.12.11/8.12.11) with SMTP id j81NlWh1025643 for ; Fri, 2 Sep 2005 09:47:32 +1000 Received: (qmail 96862 invoked from network); 1 Sep 2005 23:47:31 -0000 Received: from unknown (HELO ?127.0.0.1?) (unknown) by unknown with SMTP; 1 Sep 2005 23:47:31 -0000 Message-ID: <43179314.7050008@mawer.org> Date: Fri, 02 Sep 2005 09:47:32 +1000 From: Antony Mawer User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Edwin Brown References: <8b6eae9605090106151a81174d@mail.gmail.com> In-Reply-To: <8b6eae9605090106151a81174d@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD6.0 and VMWare 5.0.. No go X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 23:47:35 -0000 On 1/09/2005 11:15 PM, Edwin Brown wrote: > This morning I tried to install FreeBSD6.0 under VMWare 5. I got > the following message when it was extracting the base into \ > directory: > > Panic: duplicate free of item 0xc1c5a210 from zone 0xc143f000(g_bio) > > cpuid=0 > KDB: enter: panic > [thread pid 3 tid 100034 ] > stopped at kdb_enter+0x2b: nop > db> > > Is this a known issue? I've seen it reported before, but I don't recall seeing a solution. I hope this is a show-stopper for 6.0, as a number of places I know of use VMware for testing and development with FreeBSD... -Antony From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 01:13:25 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CEE116A41F for ; Fri, 2 Sep 2005 01:13:25 +0000 (GMT) (envelope-from subgamer@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1281F43D48 for ; Fri, 2 Sep 2005 01:13:24 +0000 (GMT) (envelope-from subgamer@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so311665nzo for ; Thu, 01 Sep 2005 18:13:24 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=HA4gtlAICJNsBcbKdFggEsNqp3/UhIyoPd3pOpcVB4vTVVt4nsFw65A7qo/KksBejd+JrtiaPahT9/zbYUm6NBMbu4jv05EfYxWPjrFp9rjGkznFbr+Os7LaJk8Ugwn8VmmCHFOd8jM1Vw4xkPqnz0HX/AHW1UxHoqRslAA23TQ= Received: by 10.36.24.18 with SMTP id 18mr2074960nzx; Thu, 01 Sep 2005 18:13:24 -0700 (PDT) Received: by 10.36.19.10 with HTTP; Thu, 1 Sep 2005 18:13:24 -0700 (PDT) Message-ID: Date: Thu, 1 Sep 2005 20:13:24 -0500 From: DUKE NUKEM To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Installation Problem. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 01:13:25 -0000 Hi,=20 I'm having problems getting FreeBSD 5.3, 5.4 and 6.0 BETA3 installed on my box. I downloaded the i386 images, and whenever I boot to cd for the installation, it reboots once 'BTX loader 1.00 BTX version is 1.01' is printed. I've checked the md5 checksum and they matched, so that's not the problem. I've also disabled hardware in BIOS, along with removing any hardware I wouldn't need from my box, and neither of those did the job either. HDD - Seagate ST36540A Processor - Pentium MMX 233MHz BIOS - AMIBIOS v1.00.12.DN0R Graphic Card - Trident TGUI 9680 RAM - 64MB ED0 I'm not sure if you need any of that information, but if you do, there it is. So, any ideas? I plan to build a better computer to run FreeBSD on, just I was eager to try BSD out and I didn't have any other computers laying around other than the one I use. With the exception of this one, but I don't want to replace XP quite yet. Thanks, Jeaton. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 05:49:12 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BADC16A41F for ; Fri, 2 Sep 2005 05:49:12 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC47843D46 for ; Fri, 2 Sep 2005 05:49:11 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id AC6B464BA3B for ; Fri, 2 Sep 2005 02:49:10 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 59579-03 for ; Fri, 2 Sep 2005 05:49:09 +0000 (GMT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 3863A64B98B for ; Fri, 2 Sep 2005 02:49:10 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id DD55E357B4; Fri, 2 Sep 2005 02:49:09 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id D9C8C35518 for ; Fri, 2 Sep 2005 02:49:09 -0300 (ADT) Date: Fri, 2 Sep 2005 02:49:09 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20050902024550.S1044@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Subject: New server, installed 4.11-RELEASE ... hangs ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 05:49:12 -0000 Just built a new Dual-Xeon server, Intel motherboard ... put 4.11-RELEASE onto it, and I'm getting an odd behaviour that I'm wondering if anyone can give me a suggestion on where to look / investigate ... Mainly, it looks like after a period of time (not very long), commands just stop running ... For instance, I'm running cvsup to update my source tree (hoping that its just a bad kernel) and on another console, I login and do a 'ps aux', which just hangs there ... on a third console, I can login and still do a df at the same time as that ps is hanging, but if I then do a ps, that console hangs ... if I then go to the 4th console, it hangs while logging in ... I can get to a DDB prompt, but not sure what I can provide from there that may be useful ... Thoughts? Thanks ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 06:00:50 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE4AF16A41F for ; Fri, 2 Sep 2005 06:00:50 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4316143D46 for ; Fri, 2 Sep 2005 06:00:50 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id 9CB3C64BC5B for ; Fri, 2 Sep 2005 03:00:49 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 92664-01 for ; Fri, 2 Sep 2005 06:00:47 +0000 (GMT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 2082364BC56 for ; Fri, 2 Sep 2005 03:00:49 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 2350A368DA; Fri, 2 Sep 2005 03:00:49 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 209D436838 for ; Fri, 2 Sep 2005 03:00:49 -0300 (ADT) Date: Fri, 2 Sep 2005 03:00:49 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org In-Reply-To: <20050902024550.S1044@ganymede.hub.org> Message-ID: <20050902030011.O1044@ganymede.hub.org> References: <20050902024550.S1044@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Subject: Re: New server, installed 4.11-RELEASE ... hangs ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 06:00:50 -0000 Oh, and before anyone asks why I'm not running something more recent ... 4.11 is the last stable release that has a working unionfs ... so I'm kinda stuck there right now ... On Fri, 2 Sep 2005, Marc G. Fournier wrote: > > Just built a new Dual-Xeon server, Intel motherboard ... put 4.11-RELEASE > onto it, and I'm getting an odd behaviour that I'm wondering if anyone can > give me a suggestion on where to look / investigate ... > > Mainly, it looks like after a period of time (not very long), commands just > stop running ... > > For instance, I'm running cvsup to update my source tree (hoping that its > just a bad kernel) and on another console, I login and do a 'ps aux', which > just hangs there ... on a third console, I can login and still do a df at the > same time as that ps is hanging, but if I then do a ps, that console hangs > ... if I then go to the 4th console, it hangs while logging in ... > > I can get to a DDB prompt, but not sure what I can provide from there that > may be useful ... > > Thoughts? > > Thanks ... > > ---- > Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) > Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 08:00:32 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAE6E16A41F for ; Fri, 2 Sep 2005 08:00:32 +0000 (GMT) (envelope-from mathijs@crooked.net) Received: from amsfep17-int.chello.nl (amsfep17-int.chello.nl [213.46.243.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id E982043D55 for ; Fri, 2 Sep 2005 08:00:31 +0000 (GMT) (envelope-from mathijs@crooked.net) Received: from crooked.net ([62.108.23.9]) by amsfep17-int.chello.nl (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20050902080029.XRTW1343.amsfep17-int.chello.nl@crooked.net>; Fri, 2 Sep 2005 10:00:29 +0200 Received: from [62.58.162.149] (unknown [62.58.162.149]) by crooked.net (Postfix) with ESMTP id 32BDD506AEA; Fri, 2 Sep 2005 10:00:25 +0200 (CEST) Message-ID: <43180696.8010208@crooked.net> Date: Fri, 02 Sep 2005 10:00:22 +0200 From: Mathijs Brands User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: DUKE NUKEM References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Installation Problem. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 08:00:33 -0000 DUKE NUKEM wrote: >Hi, > >I'm having problems getting FreeBSD 5.3, 5.4 and 6.0 BETA3 installed >on my box. I downloaded the i386 images, and whenever I boot to cd >for the installation, it reboots once 'BTX loader 1.00 BTX version is >1.01' is printed. I've checked the md5 checksum and they matched, so >that's not the problem. I've also disabled hardware in BIOS, along >with removing any hardware I wouldn't need from my box, and neither of >those did the job either. > > Have you tried enabling PIO transfer mode for the CD-ROM drive? A have a Compaq Evo that crashes if I boot with a FreeBSD install CD with the CD-ROM drive set to use DMA transfers. Cheers, Mathijs From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 08:25:39 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02DD216A41F for ; Fri, 2 Sep 2005 08:25:39 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (gw.zefyris.com [213.41.131.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CFC543D45 for ; Fri, 2 Sep 2005 08:25:37 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.4/8.13.4) with ESMTP id j828PbWF001834; Fri, 2 Sep 2005 10:25:37 +0200 (CEST) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.4/8.13.1/Submit) id j828Pamp001833; Fri, 2 Sep 2005 10:25:36 +0200 (CEST) (envelope-from ftigeot) Date: Fri, 2 Sep 2005 10:25:36 +0200 From: Francois Tigeot To: Mathieu PREVOT Message-ID: <20050902082536.GA1279@aoi.wolfpond.org> References: <01ac2b857a762ef9bbaa48dc6b781cb3@wanadoo.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01ac2b857a762ef9bbaa48dc6b781cb3@wanadoo.fr> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: autologin only in one ttyv X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 08:25:39 -0000 On Thu, Sep 01, 2005 at 09:59:20PM +0200, Mathieu PREVOT wrote: > > I would like to autologin in *only one* ttyv (eg ttyv1) and then launch > X with xinit manually or with a script. > I used ":al=:" in /etc/gettytab and added or not xinit in > /etc/, but it's not very satisfying! > Hence, I would like this to occur only for ttyv1. Can someone help me? I have done a similar thing for ThinBSD. Look here: http://www.thinbsd.org/cvsweb/ThinBSD/diskimage/files/ In addition to gettytab, I had to modify /etc/ttys to use the autologin feature on only one vt. You can then launch X from the user's .profile -- Francois Tigeot, Zefyris http://www.zefyris.com/ From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 09:55:29 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5AD316A41F for ; Fri, 2 Sep 2005 09:55:29 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from maxlor.mine.nu (c-213-160-32-54.customer.ggaweb.ch [213.160.32.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A48D43D46 for ; Fri, 2 Sep 2005 09:55:28 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from localhost (localhost [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id A04D3388; Fri, 2 Sep 2005 11:55:27 +0200 (CEST) Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (midgard.intranet [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22596-10; Fri, 2 Sep 2005 11:55:26 +0200 (CEST) Received: from [10.0.0.23] (mini.intranet [10.0.0.23]) by maxlor.mine.nu (Postfix) with ESMTP id C9653145; Fri, 2 Sep 2005 11:55:25 +0200 (CEST) Message-ID: <43182189.7020402@datacomm.ch> Date: Fri, 02 Sep 2005 11:55:21 +0200 From: Benjamin Lutz User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD-Stable References: <01ac2b857a762ef9bbaa48dc6b781cb3@wanadoo.fr> <43178708.3090503@datacomm.ch> In-Reply-To: <43178708.3090503@datacomm.ch> X-Enigmail-Version: 0.92.0.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8D7D20B8A1BC919BA3F17429" X-Virus-Scanned: amavisd-new at maxlor.mine.nu Cc: Mathieu PREVOT Subject: Re: autologin only in one ttyv X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 09:55:29 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8D7D20B8A1BC919BA3F17429 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Benjamin Lutz wrote: > Mathieu PREVOT wrote: > >>I would like to autologin in *only one* ttyv (eg ttyv1) and then launch >>X with xinit manually or with a script. > > > Have a look at /etc/gettytab. Instead of starting getty, you could > simply start a shell, like this: > > ttyv1 "/usr/bin/su - username" cons25 on secure > > If you want to start X right away, you could try > > ttyv1 "/usr/bin/su - username startx" cons25 on secure Err obviously it was too late for me to think straight yesterday night... this is /etc/ttys of course, not /etc/gettytab. Cheers Benjamin --------------enig8D7D20B8A1BC919BA3F17429 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.0 (Darwin) iD4DBQFDGCGOgShs4qbRdeQRApJNAJd2DPcEAvWU2qX/diRHnXvh9GWyAJ9JF+CI q+vmMG54Kqifu/7zPue4Bg== =+XrA -----END PGP SIGNATURE----- --------------enig8D7D20B8A1BC919BA3F17429-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 10:16:44 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21BED16A41F for ; Fri, 2 Sep 2005 10:16:44 +0000 (GMT) (envelope-from pierre@ulisch.net) Received: from mailout.kamp-dsl.de (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id 4F36643D46 for ; Fri, 2 Sep 2005 10:16:42 +0000 (GMT) (envelope-from pierre@ulisch.net) Received: (qmail 6385 invoked from network); 2 Sep 2005 10:17:11 -0000 Received: from sponts.kamp.net (195.62.100.50) by mailout.kamp-dsl.de with SMTP; 2 Sep 2005 10:17:11 -0000 Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by sponts.kamp.net (SPONTS v2.2.1) with SMTP id 10616568828-0 for ; Fri, 2 Sep 2005 12:16:41 +0200 Received: (qmail 6381 invoked by uid 513); 2 Sep 2005 10:17:10 -0000 Received: from 82.141.51.79 by dsl-mail (envelope-from , uid 89) with qmail-scanner-1.24 (clamdscan: 0.86.2/1023. spamassassin: 3.0.1. Clear:RC:1(82.141.51.79):SA:0(-1.4/5.0):. Processed in 0.46093 secs); 02 Sep 2005 10:17:10 -0000 X-Spam-Status: No, hits=-1.4 required=5.0 Received: from reverse-82-141-51-79.dialin.kamp-dsl.de (HELO direwolf.5550h.net) (pierre%ulisch.net@82.141.51.79) by dsl-mail.kamp.net with SMTP; 2 Sep 2005 10:17:10 -0000 From: Pierre Ulisch To: freebsd-stable@freebsd.org Date: Fri, 2 Sep 2005 12:15:24 +0200 User-Agent: KMail/1.8.2 References: <8b6eae9605090106151a81174d@mail.gmail.com> <43179314.7050008@mawer.org> In-Reply-To: <43179314.7050008@mawer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509021215.25305.pierre@ulisch.net> X-SPONTS-Version: 2.2.1 Subject: Re: FreeBSD6.0 and VMWare 5.0.. No go X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 10:16:44 -0000 2005 9$B7n(B 2 $B6bMKF|(B 01:47$B!"(BAntony Mawer $B$5$s$O=q$-$^$7$?(B: > On 1/09/2005 11:15 PM, Edwin Brown wrote: > > This morning I tried to install FreeBSD6.0 under VMWare 5. I got > > the following message when it was extracting the base into \ > > directory: > > > > Panic: duplicate free of item 0xc1c5a210 from zone 0xc143f000(g_bio) > > > > cpuid=0 > > KDB: enter: panic > > [thread pid 3 tid 100034 ] > > stopped at kdb_enter+0x2b: nop > > db> > > > > Is this a known issue? > > I've seen it reported before, but I don't recall seeing a solution. I > hope this is a show-stopper for 6.0, as a number of places I know of use > VMware for testing and development with FreeBSD... I just finished installing FreeBSD6.0-Beta3 under VMWare 5. The installation completes flawlessly, if you boot from the CD image, then install everything via FTP instead of using the CD. Installation from CD causes the same panic you mentioned. I haven't noticed any other problems, X is up and running, everything I tested so far worked as it should. I hope this helps a bit :) Pierre From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 10:46:37 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A87A416A41F for ; Fri, 2 Sep 2005 10:46:37 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9CC943D48 for ; Fri, 2 Sep 2005 10:46:36 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: by wproxy.gmail.com with SMTP id i23so39503wra for ; Fri, 02 Sep 2005 03:46:36 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=eAaguX/5uCwFh/ms96+gbrMUdO/p5tMnCZN4lNL+58nQ57qfEdBMvSfNF/6JnSZpkWR+pR7FDUihIvysPMU1cuTBj5DAqvSYGY1bxcZt6FCRzUiWJFjw7E7NJQjztIuko9wUalofnfpNVtf0nW00dPQNbptKbF2TLPiuz3F8U24= Received: by 10.54.40.44 with SMTP id n44mr1994929wrn; Fri, 02 Sep 2005 03:46:36 -0700 (PDT) Received: by 10.54.38.32 with HTTP; Fri, 2 Sep 2005 03:46:36 -0700 (PDT) Message-ID: <70e8236f050902034627163b25@mail.gmail.com> Date: Fri, 2 Sep 2005 11:46:36 +0100 From: Joao Barros To: Pierre Ulisch In-Reply-To: <200509021215.25305.pierre@ulisch.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8b6eae9605090106151a81174d@mail.gmail.com> <43179314.7050008@mawer.org> <200509021215.25305.pierre@ulisch.net> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD6.0 and VMWare 5.0.. No go X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: joao.barros@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 10:46:37 -0000 On 9/2/05, Pierre Ulisch wrote: > 2005 9$B7n(B 2 $B6bMKF|(B 01:47$B!"(BAntony Mawer $B$5$s$O=q$-$^$7$?(B: > > On 1/09/2005 11:15 PM, Edwin Brown wrote: > > > This morning I tried to install FreeBSD6.0 under VMWare 5. I got > > > the following message when it was extracting the base into \ > > > directory: > > > > > > Panic: duplicate free of item 0xc1c5a210 from zone 0xc143f000(g_bio) > > > > > > cpuid=0 > > > KDB: enter: panic > > > [thread pid 3 tid 100034 ] > > > stopped at kdb_enter+0x2b: nop > > > db> > > > > > > Is this a known issue? > > > > I've seen it reported before, but I don't recall seeing a solution. I > > hope this is a show-stopper for 6.0, as a number of places I know of use > > VMware for testing and development with FreeBSD... > > I just finished installing FreeBSD6.0-Beta3 under VMWare 5. The installation > completes flawlessly, if you boot from the CD image, then install everything > via FTP instead of using the CD. Installation from CD causes the same panic > you mentioned. I haven't noticed any other problems, X is up and running, > everything I tested so far worked as it should. > I hope this helps a bit :) > > Pierre For what it's worth I'm running FreeBSD on VMWare 5 back from 5.3, updated to 6.0 Beta 2 recently. As I'm using a real partition, I dual boot FreeBSD either real or under VMware, either with nVidia or VMware drivers. No hickups :) -- Joao Barros From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 11:13:09 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 573A516A41F for ; Fri, 2 Sep 2005 11:13:09 +0000 (GMT) (envelope-from dominique.goncalves@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D66743D45 for ; Fri, 2 Sep 2005 11:13:08 +0000 (GMT) (envelope-from dominique.goncalves@gmail.com) Received: by nproxy.gmail.com with SMTP id x4so191982nfb for ; Fri, 02 Sep 2005 04:13:05 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=bJBX1towelr6VCOetu6eJvBxYs19wsb+bZecz2vZdRaam2hDiEtgICxZbobDEwrpoRfHaRVgZSdoHGlElSAntcQ2I7xFYV1tzU73xLjQ62NYuIree57AOu5J3hIKxEJNEddJVyqL666IH6RENwNcqAXL9rsgBnIU2oFl63Ugm5s= Received: by 10.48.30.19 with SMTP id d19mr152771nfd; Fri, 02 Sep 2005 04:13:05 -0700 (PDT) Received: by 10.49.1.1 with HTTP; Fri, 2 Sep 2005 04:13:05 -0700 (PDT) Message-ID: <7daacbbe050902041329543e23@mail.gmail.com> Date: Fri, 2 Sep 2005 13:13:05 +0200 From: Dominique Goncalves To: Gabor Esperon In-Reply-To: <665CF8C5-482E-4546-A1C1-804EB9BFB609@isncom.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_2829_1661240.1125659585942" References: <200508251139.09787.doconnor@gsoft.com.au> <20050825160426.GA10134@slackbox.xs4all.nl> <665CF8C5-482E-4546-A1C1-804EB9BFB609@isncom.com> Cc: freebsd-stable@freebsd.org Subject: Re: VIA 6420 SATA150 RAID on 5.4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 11:13:09 -0000 ------=_Part_2829_1661240.1125659585942 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 8/25/05, Gabor Esperon wrote: >=20 > On Aug 25, 2005, at 12:04 PM, Roland Smith wrote: >=20 > > On Thu, Aug 25, 2005 at 11:39:08AM +0930, Daniel O'Connor wrote: > > > >> Does anyone have one of these -> > >> atapci1: port 0xc400-0xc4ff, > >> 0xc000-0xc00f, > >> 0xbc00-0xbc03,0xb800-0xb807,0xb400-0xb403,0xb000-0xb007 irq 20 at > >> device 15.0 on pci0 > >> ata4: channel #0 on atapci1 > >> ata5: channel #1 on atapci1 > >> > > > > I've got 2 devices hanging on this controller 120 GB and 160 GD, both > > Western Digital. They both work fine. > > > > > >> With a RAID set up on it? Does it work? > >> > > > > I didn't try the RAID function. I use one of the drives for data, and > > the other one for dumps. > > > > Roland > > -- > > R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as > > plain text. > > public key: http://www.xs4all.nl/~rsmith/pubkey.txt > > >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >=20 Hi, I use the same crontroler and I created a RAID-1 with 2 maxtor HDD but on FreeBSD 6.0-BETA-3. It's works well for the moment. ad4: 194481MB at ata2-master SATA150 ad6: 194481MB at ata3-master SATA150 ar0: 194480MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master # mount | grep ar0s1 /dev/ar0s1 on /raid (ufs, local, soft-updates) # df -h | grep ar0s1 /dev/ar0s1 184G 54G 115G 32% /raid Hope this help Regards. --=20 There's this old saying: "Give a man a fish, feed him for a day. Teach a man to fish, feed him for life." ------=_Part_2829_1661240.1125659585942 Content-Type: text/plain; name="dmesg.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="dmesg.txt" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDUgVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0IChj KSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAxOTkzLCAx OTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmln aHRzIHJlc2VydmVkLgpGcmVlQlNEIDYuMC1CRVRBMyAjMDogVGh1IFNlcCAgMSAxNTo1NzozMCBD RVNUIDIwMDUKICAgIHJvb3RAYmV0YTovdXNyL29iai91c3Ivc3JjL3N5cy9CRVRBClRpbWVjb3Vu dGVyICJpODI1NCIgZnJlcXVlbmN5IDExOTMxODIgSHogcXVhbGl0eSAwCkNQVTogQU1EIFNlbXBy b24odG0pICAgMjQwMCsgKDE2NjYuNDktTUh6IDY4Ni1jbGFzcyBDUFUpCiAgT3JpZ2luID0gIkF1 dGhlbnRpY0FNRCIgIElkID0gMHg2ODEgIFN0ZXBwaW5nID0gMQogIEZlYXR1cmVzPTB4MzgzZmJm ZjxGUFUsVk1FLERFLFBTRSxUU0MsTVNSLFBBRSxNQ0UsQ1g4LEFQSUMsU0VQLE1UUlIsUEdFLE1D QSxDTU9WLFBBVCxQU0UzNixNTVgsRlhTUixTU0U+CiAgQU1EIEZlYXR1cmVzPTB4YzA0ODA4MDA8 U1lTQ0FMTCxNUCxNTVgrLDNETm93KywzRE5vdz4KcmVhbCBtZW1vcnkgID0gMjAxMjYxMDU2ICgx OTEgTUIpCmF2YWlsIG1lbW9yeSA9IDE4NzI0NDU0NCAoMTc4IE1CKQpBQ1BJIEFQSUMgVGFibGU6 IDxLTTQwMCAgQVdSREFDUEk+CmlvYXBpYzAgPFZlcnNpb24gMC4zPiBpcnFzIDAtMjMgb24gbW90 aGVyYm9hcmQKbnB4MDogW0ZBU1RdCm5weDA6IDxtYXRoIHByb2Nlc3Nvcj4gb24gbW90aGVyYm9h cmQKbnB4MDogSU5UIDE2IGludGVyZmFjZQphY3BpMDogPEtNNDAwIEFXUkRBQ1BJPiBvbiBtb3Ro ZXJib2FyZAphY3BpMDogUG93ZXIgQnV0dG9uIChmaXhlZCkKcGNpX2xpbmswOiA8QUNQSSBQQ0kg TGluayBMTktBPiBpcnEgMTAgb24gYWNwaTAKcGNpX2xpbmsxOiA8QUNQSSBQQ0kgTGluayBMTktC PiBpcnEgMTEgb24gYWNwaTAKcGNpX2xpbmsyOiA8QUNQSSBQQ0kgTGluayBMTktDPiBpcnEgMTIg b24gYWNwaTAKcGNpX2xpbmszOiA8QUNQSSBQQ0kgTGluayBMTktEPiBvbiBhY3BpMApwY2lfbGlu azQ6IDxBQ1BJIFBDSSBMaW5rIExOS0U+IG9uIGFjcGkwCnBjaV9saW5rNTogPEFDUEkgUENJIExp bmsgTE5LRj4gb24gYWNwaTAKcGNpX2xpbms2OiA8QUNQSSBQQ0kgTGluayBMTkswPiBvbiBhY3Bp MApwY2lfbGluazc6IDxBQ1BJIFBDSSBMaW5rIExOSzE+IG9uIGFjcGkwCnBjaV9saW5rODogPEFD UEkgUENJIExpbmsgQUxLQT4gaXJxIDAgb24gYWNwaTAKcGNpX2xpbms5OiA8QUNQSSBQQ0kgTGlu ayBBTEtCPiBpcnEgMCBvbiBhY3BpMApwY2lfbGluazEwOiA8QUNQSSBQQ0kgTGluayBBTEtDPiBp cnEgMCBvbiBhY3BpMApwY2lfbGluazExOiA8QUNQSSBQQ0kgTGluayBBTEtEPiBpcnEgMCBvbiBh Y3BpMApUaW1lY291bnRlciAiQUNQSS1mYXN0IiBmcmVxdWVuY3kgMzU3OTU0NSBIeiBxdWFsaXR5 IDEwMDAKYWNwaV90aW1lcjA6IDwyNC1iaXQgdGltZXIgYXQgMy41Nzk1NDVNSHo+IHBvcnQgMHg0 MDA4LTB4NDAwYiBvbiBhY3BpMApjcHUwOiA8QUNQSSBDUFU+IG9uIGFjcGkwCmFjcGlfYnV0dG9u MDogPFBvd2VyIEJ1dHRvbj4gb24gYWNwaTAKYWNwaV9idXR0b24xOiA8U2xlZXAgQnV0dG9uPiBv biBhY3BpMApwY2liMDogPEFDUEkgSG9zdC1QQ0kgYnJpZGdlPiBwb3J0IDB4Y2Y4LTB4Y2ZmIG9u IGFjcGkwCnBjaTA6IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWIwCmFncDA6IDxWSUEgODIzNS84MjM3 IChBcG9sbG8gS000MDAvS000MDBBKSBob3N0IHRvIFBDSSBicmlkZ2U+IG1lbSAweGQwMDAwMDAw LTB4ZDdmZmZmZmYgYXQgZGV2aWNlIDAuMCBvbiBwY2kwCnBjaWIxOiA8UENJLVBDSSBicmlkZ2U+ IGF0IGRldmljZSAxLjAgb24gcGNpMApwY2kxOiA8UENJIGJ1cz4gb24gcGNpYjEKcGNpMTogPGRp c3BsYXksIFZHQT4gYXQgZGV2aWNlIDAuMCAobm8gZHJpdmVyIGF0dGFjaGVkKQphdGFwY2kwOiA8 VklBIDY0MjAgU0FUQTE1MCBjb250cm9sbGVyPiBwb3J0IDB4OTAwMC0weDkwMDcsMHg5NDAwLTB4 OTQwMywweDk4MDAtMHg5ODA3LDB4OWMwMC0weDljMDMsMHhhMDAwLTB4YTAwZiwweGE0MDAtMHhh NGZmIGlycSAyMCBhdCBkZXZpY2UgMTUuMCBvbiBwY2kwCmF0YTI6IDxBVEEgY2hhbm5lbCAwPiBv biBhdGFwY2kwCmF0YTM6IDxBVEEgY2hhbm5lbCAxPiBvbiBhdGFwY2kwCmF0YXBjaTE6IDxWSUEg ODIzNyBVRE1BMTMzIGNvbnRyb2xsZXI+IHBvcnQgMHgxZjAtMHgxZjcsMHgzZjYsMHgxNzAtMHgx NzcsMHgzNzYsMHhhODAwLTB4YTgwZiBhdCBkZXZpY2UgMTUuMSBvbiBwY2kwCmF0YTA6IDxBVEEg Y2hhbm5lbCAwPiBvbiBhdGFwY2kxCmF0YTE6IDxBVEEgY2hhbm5lbCAxPiBvbiBhdGFwY2kxCnVo Y2kwOiA8VklBIDgzQzU3MiBVU0IgY29udHJvbGxlcj4gcG9ydCAweGFjMDAtMHhhYzFmIGlycSAy MSBhdCBkZXZpY2UgMTYuMCBvbiBwY2kwCnVoY2kwOiBbR0lBTlQtTE9DS0VEXQp1c2IwOiA8VklB IDgzQzU3MiBVU0IgY29udHJvbGxlcj4gb24gdWhjaTAKdXNiMDogVVNCIHJldmlzaW9uIDEuMAp1 aHViMDogVklBIFVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRkciAx CnVodWIwOiAyIHBvcnRzIHdpdGggMiByZW1vdmFibGUsIHNlbGYgcG93ZXJlZAp1aGNpMTogPFZJ QSA4M0M1NzIgVVNCIGNvbnRyb2xsZXI+IHBvcnQgMHhiMDAwLTB4YjAxZiBpcnEgMjEgYXQgZGV2 aWNlIDE2LjEgb24gcGNpMAp1aGNpMTogW0dJQU5ULUxPQ0tFRF0KdXNiMTogPFZJQSA4M0M1NzIg VVNCIGNvbnRyb2xsZXI+IG9uIHVoY2kxCnVzYjE6IFVTQiByZXZpc2lvbiAxLjAKdWh1YjE6IFZJ QSBVSENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJldiAxLjAwLzEuMDAsIGFkZHIgMQp1aHViMTog MiBwb3J0cyB3aXRoIDIgcmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQKdWhjaTI6IDxWSUEgODNDNTcy IFVTQiBjb250cm9sbGVyPiBwb3J0IDB4YjQwMC0weGI0MWYgaXJxIDIxIGF0IGRldmljZSAxNi4y IG9uIHBjaTAKdWhjaTI6IFtHSUFOVC1MT0NLRURdCnVzYjI6IDxWSUEgODNDNTcyIFVTQiBjb250 cm9sbGVyPiBvbiB1aGNpMgp1c2IyOiBVU0IgcmV2aXNpb24gMS4wCnVodWIyOiBWSUEgVUhDSSBy b290IGh1YiwgY2xhc3MgOS8wLCByZXYgMS4wMC8xLjAwLCBhZGRyIDEKdWh1YjI6IDIgcG9ydHMg d2l0aCAyIHJlbW92YWJsZSwgc2VsZiBwb3dlcmVkCnVoY2kzOiA8VklBIDgzQzU3MiBVU0IgY29u dHJvbGxlcj4gcG9ydCAweGI4MDAtMHhiODFmIGlycSAyMSBhdCBkZXZpY2UgMTYuMyBvbiBwY2kw CnVoY2kzOiBbR0lBTlQtTE9DS0VEXQp1c2IzOiA8VklBIDgzQzU3MiBVU0IgY29udHJvbGxlcj4g b24gdWhjaTMKdXNiMzogVVNCIHJldmlzaW9uIDEuMAp1aHViMzogVklBIFVIQ0kgcm9vdCBodWIs IGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRkciAxCnVodWIzOiAyIHBvcnRzIHdpdGggMiBy ZW1vdmFibGUsIHNlbGYgcG93ZXJlZAplaGNpMDogPFZJQSBWVDYyMDIgVVNCIDIuMCBjb250cm9s bGVyPiBtZW0gMHhkZTAwMDAwMC0weGRlMDAwMGZmIGlycSAyMSBhdCBkZXZpY2UgMTYuNCBvbiBw Y2kwCmVoY2kwOiBbR0lBTlQtTE9DS0VEXQp1c2I0OiBFSENJIHZlcnNpb24gMS4wCnVzYjQ6IGNv bXBhbmlvbiBjb250cm9sbGVycywgMiBwb3J0cyBlYWNoOiB1c2IwIHVzYjEgdXNiMiB1c2IzCnVz YjQ6IDxWSUEgVlQ2MjAyIFVTQiAyLjAgY29udHJvbGxlcj4gb24gZWhjaTAKdXNiNDogVVNCIHJl dmlzaW9uIDIuMAp1aHViNDogVklBIEVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDIuMDAv MS4wMCwgYWRkciAxCnVodWI0OiA4IHBvcnRzIHdpdGggOCByZW1vdmFibGUsIHNlbGYgcG93ZXJl ZAppc2FiMDogPFBDSS1JU0EgYnJpZGdlPiBhdCBkZXZpY2UgMTcuMCBvbiBwY2kwCmlzYTA6IDxJ U0EgYnVzPiBvbiBpc2FiMApwY2kwOiA8bXVsdGltZWRpYSwgYXVkaW8+IGF0IGRldmljZSAxNy41 IChubyBkcml2ZXIgYXR0YWNoZWQpCnZyMDogPFZJQSBWVDYxMDIgUmhpbmUgSUkgMTAvMTAwQmFz ZVRYPiBwb3J0IDB4YzAwMC0weGMwZmYgbWVtIDB4ZGUwMDEwMDAtMHhkZTAwMTBmZiBpcnEgMjMg YXQgZGV2aWNlIDE4LjAgb24gcGNpMAptaWlidXMwOiA8TUlJIGJ1cz4gb24gdnIwCnVrcGh5MDog PEdlbmVyaWMgSUVFRSA4MDIuM3UgbWVkaWEgaW50ZXJmYWNlPiBvbiBtaWlidXMwCnVrcGh5MDog IDEwYmFzZVQsIDEwYmFzZVQtRkRYLCAxMDBiYXNlVFgsIDEwMGJhc2VUWC1GRFgsIGF1dG8KdnIw OiBFdGhlcm5ldCBhZGRyZXNzOiAwMDowMToyOTo5NDo5MjpkMgpmZGMwOiA8ZmxvcHB5IGRyaXZl IGNvbnRyb2xsZXI+IHBvcnQgMHgzZjAtMHgzZjUsMHgzZjcgaXJxIDYgZHJxIDIgb24gYWNwaTAK ZmRjMDogW0ZBU1RdCmZkMDogPDE0NDAtS0IgMy41IiBkcml2ZT4gb24gZmRjMCBkcml2ZSAwCnNp bzA6IGNvbmZpZ3VyZWQgaXJxIDQgbm90IGluIGJpdG1hcCBvZiBwcm9iZWQgaXJxcyAwCnNpbzA6 IHBvcnQgbWF5IG5vdCBiZSBlbmFibGVkCnNpbzA6IDwxNjU1MEEtY29tcGF0aWJsZSBDT00gcG9y dD4gcG9ydCAweDNmOC0weDNmZiBpcnEgNCBmbGFncyAweDEwIG9uIGFjcGkwCnNpbzA6IHR5cGUg MTY1NTBBCnNpbzE6IDwxNjU1MEEtY29tcGF0aWJsZSBDT00gcG9ydD4gcG9ydCAweDJmOC0weDJm ZiBpcnEgMyBvbiBhY3BpMApzaW8xOiB0eXBlIDE2NTUwQQpwcGMwOiA8U3RhbmRhcmQgcGFyYWxs ZWwgcHJpbnRlciBwb3J0PiBwb3J0IDB4Mzc4LTB4MzdmIGlycSA3IG9uIGFjcGkwCnBwYzA6IEdl bmVyaWMgY2hpcHNldCAoTklCQkxFLW9ubHkpIGluIENPTVBBVElCTEUgbW9kZQpwcGJ1czA6IDxQ YXJhbGxlbCBwb3J0IGJ1cz4gb24gcHBjMApwbGlwMDogPFBMSVAgbmV0d29yayBpbnRlcmZhY2U+ IG9uIHBwYnVzMApscHQwOiA8UHJpbnRlcj4gb24gcHBidXMwCmxwdDA6IEludGVycnVwdC1kcml2 ZW4gcG9ydApwcGkwOiA8UGFyYWxsZWwgSS9PPiBvbiBwcGJ1czAKYXRrYmRjMDogPEtleWJvYXJk IGNvbnRyb2xsZXIgKGk4MDQyKT4gcG9ydCAweDYwLDB4NjQgaXJxIDEgb24gYWNwaTAKYXRrYmQw OiA8QVQgS2V5Ym9hcmQ+IGlycSAxIG9uIGF0a2JkYzAKa2JkMCBhdCBhdGtiZDAKYXRrYmQwOiBb R0lBTlQtTE9DS0VEXQpwbXRpbWVyMCBvbiBpc2EwCm9ybTA6IDxJU0EgT3B0aW9uIFJPTT4gYXQg aW9tZW0gMHhjMDAwMC0weGNkN2ZmIG9uIGlzYTAKc2MwOiA8U3lzdGVtIGNvbnNvbGU+IGF0IGZs YWdzIDB4MTAwIG9uIGlzYTAKc2MwOiBWR0EgPDE2IHZpcnR1YWwgY29uc29sZXMsIGZsYWdzPTB4 MzAwPgp2Z2EwOiA8R2VuZXJpYyBJU0EgVkdBPiBhdCBwb3J0IDB4M2MwLTB4M2RmIGlvbWVtIDB4 YTAwMDAtMHhiZmZmZiBvbiBpc2EwClRpbWVjb3VudGVyICJUU0MiIGZyZXF1ZW5jeSAxNjY2NDky MjM1IEh6IHF1YWxpdHkgODAwClRpbWVjb3VudGVycyB0aWNrIGV2ZXJ5IDEuMDAwIG1zZWMKYWQw OiAzOTIwNU1CIDxNYXh0b3IgNkUwNDBMMCBOQVI2MUhBMD4gYXQgYXRhMC1tYXN0ZXIgVURNQTEz MwphY2QwOiBDRFJPTSA8U0FNU1VORyBDRC1ST00gU0gtMTUyQS9DNTA0PiBhdCBhdGExLW1hc3Rl ciBVRE1BMzMKYWQ0OiAxOTQ0ODFNQiA8TWF4dG9yIDZMMjAwTTAgQkFOQzFHMTA+IGF0IGF0YTIt bWFzdGVyIFNBVEExNTAKYWQ2OiAxOTQ0ODFNQiA8TWF4dG9yIDZMMjAwTTAgQkFOQzFHMTA+IGF0 IGF0YTMtbWFzdGVyIFNBVEExNTAKYXIwOiAxOTQ0ODBNQiA8VklBIFRlY2ggVi1SQUlEIFJBSUQx PiBzdGF0dXM6IFJFQURZCmFyMDogZGlzazAgUkVBRFkgKG1hc3RlcikgdXNpbmcgYWQ0IGF0IGF0 YTItbWFzdGVyCmFyMDogZGlzazEgUkVBRFkgKG1pcnJvcikgdXNpbmcgYWQ2IGF0IGF0YTMtbWFz dGVyClRyeWluZyB0byBtb3VudCByb290IGZyb20gdWZzOi9kZXYvYWQwczFhCnBpZCA1NzA1NSAo Y29uZnRlc3QpLCB1aWQgMDogZXhpdGVkIG9uIHNpZ25hbCAxMSAoY29yZSBkdW1wZWQpCnBpZCAx Njg3NyAoY29uZnRlc3QpLCB1aWQgMDogZXhpdGVkIG9uIHNpZ25hbCAxMiAoY29yZSBkdW1wZWQp CnZyMDogY2hhbmdpbmcgbmFtZSB0byAnbmV0MCcK ------=_Part_2829_1661240.1125659585942-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 11:47:42 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C65F16A41F for ; Fri, 2 Sep 2005 11:47:42 +0000 (GMT) (envelope-from ricardo_bsd@yahoo.com.br) Received: from smtp202.mail.sc5.yahoo.com (smtp202.mail.sc5.yahoo.com [216.136.129.92]) by mx1.FreeBSD.org (Postfix) with SMTP id 1DD6043D46 for ; Fri, 2 Sep 2005 11:47:42 +0000 (GMT) (envelope-from ricardo_bsd@yahoo.com.br) Received: (qmail 34240 invoked from network); 2 Sep 2005 11:47:39 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.br; h=Received:Subject:From:To:Content-Type:Date:Message-Id:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=LJQ8TMLHvhdhSVq5yXe073BHMvZ2G1ci+10e2vUF7NW2CHuUIkAVOFJVzvaQjBm0gQvgYNS3SpIXBJFk7XjJvV3a73aMMXyJjue9P2cTQGIWNOXT4mmwmdtZhzVqdq9CpoNxZEJ3Z4Uh5TZFRR2QGrrC03s3LqREQnhwGI5etB0= ; Received: from unknown (HELO ricardo.epm.br) (ricardo?bsd@200.17.25.161 with plain) by smtp202.mail.sc5.yahoo.com with SMTP; 2 Sep 2005 11:47:37 -0000 From: Ricardo Alves dos Reis To: stable@freebsd.org Content-Type: text/plain Date: Fri, 02 Sep 2005 11:47:11 +0000 Message-Id: <1125661631.3233.9.camel@ricardo.epm.br> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3nb1 Content-Transfer-Encoding: 7bit Cc: Subject: PORTS: Escape Plus Signal in make search X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 11:47:42 -0000 Hi all, I discover one bug in make search target, variable name not escape + /usr/ports# make search name="apache+mod_ssl-1.3.33+2.8.22_1" /usr/ports# This small path add gsub + per /+, --------------------------------------- *** bsd.port.subdir.mk Mon Feb 28 18:09:04 2005 --- bsd.port.subdir.mk.diff Fri Sep 2 08:37:36 2005 *************** *** 365,370 **** --- 365,371 ---- -v xkeylim="$${xkeylim:-${PORTSEARCH_XKEYLIM}}" \ -v display="$${display:-${PORTSEARCH_DISPLAY_FIELDS}}" \ 'BEGIN { \ + gsub(/\+/,"\\+",name);\ if (substr(there, 1, length(top)) == top) \ there = "${PORTSDIR}" substr(there, 1 + length(top)); \ therelen = length(there); \ ----------------------------------------- With the patch /usr/ports# make search name="apache+mod_ssl-1.3.33+2.8.22_1" Port: apache+mod_ssl-1.3.33+2.8.22_1 Path: /usr/ports/www/apache13-modssl Info: The Apache 1.3 webserver with SSL/TLS functionality Maint: dinoex@FreeBSD.org B-deps: expat-1.95.8_3 mm-1.3.1 perl-5.8.7 R-deps: expat-1.95.8_3 mm-1.3.1 WWW: http://www.apache.org/ Ricardo A. Reis UNIFESP - SENAI _______________________________________________________ Yahoo! Messenger com voz: PROMOÇÃO VOCÊ PODE LEVAR UMA VIAGEM NA CONVERSA. Participe! www.yahoo.com.br/messenger/promocao From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 12:00:49 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04B4016A422 for ; Fri, 2 Sep 2005 12:00:49 +0000 (GMT) (envelope-from thomas.novin@fiberdata.se) Received: from hawk.thalamus.net (hawk.thalamus.net [212.31.160.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7968743D45 for ; Fri, 2 Sep 2005 12:00:47 +0000 (GMT) (envelope-from thomas.novin@fiberdata.se) Received: from localhost (localhost.thalamus.net [127.0.0.1]) by hawk.thalamus.net (Postfix) with ESMTP id 0E2B61EE8C8 for ; Fri, 2 Sep 2005 14:00:40 +0200 (CEST) Received: from hawk.thalamus.net ([127.0.0.1]) by localhost (hawk.thalamus.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02375-03 for ; Fri, 2 Sep 2005 14:00:39 +0200 (CEST) Received: from gw.ext.thalamus.se (gw.ext.thalamus.se [212.31.160.253]) by hawk.thalamus.net (Postfix) with ESMTP id 831A91EE8F0 for ; Fri, 2 Sep 2005 14:00:39 +0200 (CEST) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 2 Sep 2005 14:00:45 +0200 Message-ID: <0C0A95AE86344A4A85EE2FC4054F415D0D79D0@th-ms-02.fiberdata.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Buildworld fails, /usr/bin/ld: /usr/lib/libtermcap.a(lib_tputs.o): bad reloc symbol index Thread-Index: AcWvtfMr8aHvlQYKSwak1t75eVyjSw== From: "Thomas Novin" To: X-Virus-Scanned: by amavisd-new at thalamus.net X-Spam-Status: No, score=-2.731 tagged_above=-999 required=4.2 tests=[ALL_TRUSTED=-2.82, AWL=0.089] X-Spam-Score: -2.731 X-Spam-Level: Subject: Buildworld fails, /usr/bin/ld: /usr/lib/libtermcap.a(lib_tputs.o): bad reloc symbol index X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 12:00:49 -0000 I submitted this via send-pr once but they redirected me to freebsd-stable@freebsd.org instead. Anyone knows a reason why this fails? ----- Synopsis Buildworld fails, /usr/bin/ld: /usr/lib/libtermcap.a(lib_tputs.o): bad reloc symbol index Environment FreeBSD xxx 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 root@harlow.cse.buffalo.edu:/ usr/obj/usr/src/sys/GENERIC i386 Description 'make buildworld' fails on a machine cvsupped today. rm -rf of /usr/src and /usr/obj before compilation. cc -O -pipe -DINFODIR=3D\"/usr/share/info:/usr/local/info:/usr/X11R6/info:.\" -DHAVE_CONFIG_H -DLOCALEDIR=3D\"/usr/sh are/locale\" -I/usr/src/gnu/usr.bin/texinfo/info/../../../../contrib/texinfo -I/usr/src/gnu/usr.bin/texinfo/info /../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/gnu/usr.bin/texinfo/info /../../../../contrib/texinfo/info/tilde.c cc -O -pipe -DINFODIR=3D\"/usr/share/info:/usr/local/info:/usr/X11R6/info:.\" -DHAVE_CONFIG_H -DLOCALEDIR=3D\"/usr/sh are/locale\" -I/usr/src/gnu/usr.bin/texinfo/info/../../../../contrib/texinfo -I/usr/src/gnu/usr.bin/texinfo/info /../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/gnu/usr.bin/texinfo/info /../../../../contrib/texinfo/info/variables.c cc -O -pipe -DINFODIR=3D\"/usr/share/info:/usr/local/info:/usr/X11R6/info:.\" -DHAVE_CONFIG_H -DLOCALEDIR=3D\"/usr/sh are/locale\" -I/usr/src/gnu/usr.bin/texinfo/info/../../../../contrib/texinfo -I/usr/src/gnu/usr.bin/texinfo/info /../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/gnu/usr.bin/texinfo/info /../../../../contrib/texinfo/info/window.c cc -O -pipe -DINFODIR=3D\"/usr/share/info:/usr/local/info:/usr/X11R6/info:.\" -DHAVE_CONFIG_H -DLOCALEDIR=3D\"/usr/sh are/locale\" -I/usr/src/gnu/usr.bin/texinfo/info/../../../../contrib/texinfo -I/usr/src/gnu/usr.bin/texinfo/info /../../../../contrib/texinfo/lib -I/usr/obj/usr/src/i386/legacy/usr/include -static -L/usr/obj/usr/src/i386/leg acy/usr/lib -o info dir.o display.o doc.o dribble.o echo-area.o filesys.o footnotes.o gc.o indices.o info-utils.o info.o infodoc.o infomap.o m-x.o man.o nodemenu.o nodes.o search.o session.o signals.o terminal.o tilde.o variab les.o window.o -ltermcap /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/texinfo/info/../libtxi/libtxi. a -legacy /usr/bin/ld: /usr/lib/libtermcap.a(lib_tputs.o): bad reloc symbol index (0x9a >=3D 0x1c) for offset 0x2f9 in sectio n `(null)' /usr/lib/libtermcap.a: could not read symbols: Bad value *** Error code 1 Stop in /usr/src/gnu/usr.bin/texinfo/info. *** Error code 1 Stop in /usr/src/gnu/usr.bin/texinfo. *** Error code 1 How-To-Repeat make buildworld -- Thomas Novin * thomas@fiberdata.se * http://xyz.pp.se/~thnov/pgp_corp.asc System Engineer * Fiberdata AB * http://www.fiberdata.se V: +46 (0)431 445400 * F: +46 (0)431 445410 * GSM: +46 (0)730 667425 From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 12:37:46 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0319316A41F for ; Fri, 2 Sep 2005 12:37:46 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BBE643D48 for ; Fri, 2 Sep 2005 12:37:44 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp215-145.lns1.adl2.internode.on.net [203.122.215.145]) (authenticated bits=0) by cain.gsoft.com.au (8.13.4/8.13.4) with ESMTP id j82CbZdW062980 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 2 Sep 2005 22:07:41 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Fri, 2 Sep 2005 22:07:13 +0930 User-Agent: KMail/1.8.1 References: <200508251139.09787.doconnor@gsoft.com.au> <665CF8C5-482E-4546-A1C1-804EB9BFB609@isncom.com> <7daacbbe050902041329543e23@mail.gmail.com> In-Reply-To: <7daacbbe050902041329543e23@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1457383.yOJ05hNXqx"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200509022207.26152.doconnor@gsoft.com.au> X-Spam-Score: 0.05 () FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.51 on 203.31.81.10 Cc: Gabor Esperon , Dominique Goncalves Subject: Re: VIA 6420 SATA150 RAID on 5.4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 12:37:46 -0000 --nextPart1457383.yOJ05hNXqx Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 02 September 2005 20:43, Dominique Goncalves wrote: > I use the same crontroler and I created a RAID-1 with 2 maxtor HDD but > on FreeBSD 6.0-BETA-3. > It's works well for the moment. OK thanks. > ad4: 194481MB at ata2-master SATA150 > ad6: 194481MB at ata3-master SATA150 > ar0: 194480MB status: READY > ar0: disk0 READY (master) using ad4 at ata2-master > ar0: disk1 READY (mirror) using ad6 at ata3-master Have you tried pulling a disk while it's running to see how it copes? =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1457383.yOJ05hNXqx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDGEeG5ZPcIHs/zowRAi96AJ9b5cofspfIuypwNQE8o/NCagY/bwCcDS2z HDrMO7j/nyCaCmDUKobrn+E= =sX4C -----END PGP SIGNATURE----- --nextPart1457383.yOJ05hNXqx-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 14:52:36 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1FF216A41F for ; Fri, 2 Sep 2005 14:52:36 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3955B43D64 for ; Fri, 2 Sep 2005 14:52:32 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IM700GRM2R14UE0@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Fri, 02 Sep 2005 16:54:37 +0200 (CEST) Received: from kg-work.kg4.no ([80.202.174.153]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IM7000PW2SY1RD0@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Fri, 02 Sep 2005 16:55:47 +0200 (CEST) Date: Fri, 02 Sep 2005 16:52:30 +0200 From: Torfinn Ingolfsen X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH To: freebsd-stable@freebsd.org Message-id: <20050902165230.0d0c2bbf.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 1.0.5 (GTK+ 1.2.10; i386-portbld-freebsd5.4) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: MSI RS480M2-IL and bios upgrades X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 14:52:36 -0000 I'll note this here, in case it helps others. I have a MSI mainboard, model RS480M2-IL 8aka MS-7093). I'm running FreeBSD 5.4-stable amd64 on it. I'm also using a nVidia GeForce 6200 TC (TurboCache) gfx card, because of troubles with the integrated Radeon Xpress 200 gfx chipset (Xorg does't have working support yet). The board was delivered with BIOS version 3.3, and I have been running with it for a long time, even if it has some problems. A few days ago, I checked the MSI web site, and found that the newest bios now was version 3.8. Stupidly enough, I upgraded (in hope that it might cure some of the problems this board has). I should have known better. After the upgrade, Xorg would freeze on startup (or a few seconds after). The machine still worked, I could ssh in and do a shutdown. After reading through a lot of messages on MSI forums, I found others with the same problem, the suggested fix is to downgrade the bios to version 3.5. I reflashed to version 3.5 of the bios, and now the machine works again. Information: mainboard info: http://www.msi.com.tw/program/products/mainboard/mbd/pro_mbd_detail.php?UID=639 BIOS link: http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=639&kind=1 FreeBSD version: FreeBSD kg-quiet.kg4.no 5.4-STABLE FreeBSD 5.4-STABLE #5: Fri Sep 2 15:14:54 CEST 2005 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET amd64 Xorg version: xorg-server-6.8.99.12 = up-to-date with port Graphics card: none3@pci1:0:0: class=0x030000 card=0x81ae1043 chip=0x016110de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GeForce 6200 TurboCache(TM)' class = display subclass = VGA --- Yours, Torfinn Ingolfsen, Norway From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 15:05:34 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2418216A41F for ; Fri, 2 Sep 2005 15:05:34 +0000 (GMT) (envelope-from dominique.goncalves@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80C4A43D45 for ; Fri, 2 Sep 2005 15:05:33 +0000 (GMT) (envelope-from dominique.goncalves@gmail.com) Received: by nproxy.gmail.com with SMTP id x4so213277nfb for ; Fri, 02 Sep 2005 08:05:31 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GiLayAEBwn876Dh+VPzHj6vq/GNO6g57Pzt9L2k4jj4app7uCNM9VX8EYdoQTyXG/zLJKC1vjhRemwNwqyxi73Hikm6IjON+HZ0DeW1yKLShSJSpEuYinN6SncYeJ9u3kac3M60G1qRXvtc7KFUbBr35R/QdHrTq9Bo2Z69LbHE= Received: by 10.48.30.19 with SMTP id d19mr167179nfd; Fri, 02 Sep 2005 08:05:31 -0700 (PDT) Received: by 10.49.1.1 with HTTP; Fri, 2 Sep 2005 08:05:31 -0700 (PDT) Message-ID: <7daacbbe05090208055d1e58a8@mail.gmail.com> Date: Fri, 2 Sep 2005 17:05:31 +0200 From: Dominique Goncalves To: Daniel O'Connor In-Reply-To: <200509022207.26152.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200508251139.09787.doconnor@gsoft.com.au> <665CF8C5-482E-4546-A1C1-804EB9BFB609@isncom.com> <7daacbbe050902041329543e23@mail.gmail.com> <200509022207.26152.doconnor@gsoft.com.au> Cc: Gabor Esperon , freebsd-stable@freebsd.org Subject: Re: VIA 6420 SATA150 RAID on 5.4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 15:05:34 -0000 On 9/2/05, Daniel O'Connor wrote:=20 > Have you tried pulling a disk while it's running to see how it copes? No, because I don't know, if this controler and FreeBSD support hotplug for SATA disks. --=20 There's this old saying: "Give a man a fish, feed him for a day. Teach a man to fish, feed him for life." From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 15:33:15 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14AAB16A420 for ; Fri, 2 Sep 2005 15:33:15 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4684443D46 for ; Fri, 2 Sep 2005 15:33:13 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp200-227.lns1.adl4.internode.on.net [203.122.200.227]) (authenticated bits=0) by cain.gsoft.com.au (8.13.4/8.13.4) with ESMTP id j82FX4vN064130 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 3 Sep 2005 01:03:10 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Dominique Goncalves Date: Sat, 3 Sep 2005 01:02:27 +0930 User-Agent: KMail/1.8.1 References: <200508251139.09787.doconnor@gsoft.com.au> <200509022207.26152.doconnor@gsoft.com.au> <7daacbbe05090208055d1e58a8@mail.gmail.com> In-Reply-To: <7daacbbe05090208055d1e58a8@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4652705.3PjXE6cvQN"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200509030102.50363.doconnor@gsoft.com.au> X-Spam-Score: 0.05 () FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.51 on 203.31.81.10 Cc: Gabor Esperon , freebsd-stable@freebsd.org Subject: Re: VIA 6420 SATA150 RAID on 5.4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 15:33:15 -0000 --nextPart4652705.3PjXE6cvQN Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 03 September 2005 00:35, Dominique Goncalves wrote: > On 9/2/05, Daniel O'Connor wrote: > > Have you tried pulling a disk while it's running to see how it copes? > > No, because I don't know, if this controler and FreeBSD support > hotplug for SATA disks. What about if you do it 'cold'? I like to test my RAID to make sure I can still boot when one disk is=20 'dead' :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart4652705.3PjXE6cvQN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDGHCi5ZPcIHs/zowRAt9CAKCGJfXZC9pryC7lMlFsrnfQFYh/BACgnyKm PkB/LVxhRnkDOU5hasEDeJg= =x+fs -----END PGP SIGNATURE----- --nextPart4652705.3PjXE6cvQN-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 16:32:29 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0C9016A41F for ; Fri, 2 Sep 2005 16:32:29 +0000 (GMT) (envelope-from igor@doom.homeunix.org) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3569643D45 for ; Fri, 2 Sep 2005 16:32:29 +0000 (GMT) (envelope-from igor@doom.homeunix.org) Received: from dialup84124-37.ip.peterstar.net ([84.204.124.37] helo=doom.homeunix.org) by voodoo.oberon.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.52 (FreeBSD)) id 1EBESg-0002mE-DI for freebsd-stable@freebsd.org; Fri, 02 Sep 2005 18:32:19 +0200 Received: from doom.homeunix.org (localhost [127.0.0.1]) by doom.homeunix.org (8.13.3/8.13.3) with ESMTP id j82GVadg001211; Fri, 2 Sep 2005 20:31:39 +0400 (MSD) (envelope-from igor@doom.homeunix.org) Received: (from igor@localhost) by doom.homeunix.org (8.13.3/8.13.3/Submit) id j82GVWR6001210; Fri, 2 Sep 2005 20:31:32 +0400 (MSD) (envelope-from igor) Date: Fri, 2 Sep 2005 20:31:30 +0400 From: Igor Pokrovsky To: "Marc G. Fournier" Message-ID: <20050902163130.GA1185@doom.homeunix.org> Mail-Followup-To: "Marc G. Fournier" , freebsd-stable@freebsd.org References: <20050902024550.S1044@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050902024550.S1044@ganymede.hub.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: New server, installed 4.11-RELEASE ... hangs ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 16:32:29 -0000 On Fri, Sep 02, 2005 at 02:49:09AM -0300, Marc G. Fournier wrote: > > Just built a new Dual-Xeon server, Intel motherboard ... put 4.11-RELEASE > onto it, and I'm getting an odd behaviour that I'm wondering if anyone can > give me a suggestion on where to look / investigate ... > > Mainly, it looks like after a period of time (not very long), commands > just stop running ... > > For instance, I'm running cvsup to update my source tree (hoping that its > just a bad kernel) and on another console, I login and do a 'ps aux', > which just hangs there ... on a third console, I can login and still do a > df at the same time as that ps is hanging, but if I then do a ps, that > console hangs ... if I then go to the 4th console, it hangs while logging > in ... > > I can get to a DDB prompt, but not sure what I can provide from there that > may be useful ... > > Thoughts? I've seen such behaviour myself some time ago and IIRC I removed acpica from kernel. Worth a try I think... -ip -- Beauty is only skin deep, ugly goes clear to the bone. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 2 22:17:10 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA09516A41F; Fri, 2 Sep 2005 22:17:10 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from postfix3-1.free.fr (postfix3-1.free.fr [213.228.0.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 603D243D48; Fri, 2 Sep 2005 22:17:10 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix3-1.free.fr (Postfix) with ESMTP id 0020117348E; Sat, 3 Sep 2005 00:17:08 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 15F3E4080; Sat, 3 Sep 2005 00:17:25 +0200 (CEST) Date: Sat, 3 Sep 2005 00:17:24 +0200 From: Jeremie Le Hen To: Edwin Brown Message-ID: <20050902221724.GC659@obiwan.tataz.chchile.org> References: <8b6eae9605090106151a81174d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8b6eae9605090106151a81174d@mail.gmail.com> User-Agent: Mutt/1.5.9i Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD6.0 and VMWare 5.0.. No go X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 22:17:10 -0000 Hi Edwin, [ Please either post on -stable@ or -current@, not both. In this case you should have post on -current@ only, since 6.0 isn't stable yet. ] > This morning I tried to install FreeBSD6.0 under VMWare 5. I got > the following message when it was extracting the base into \ > directory: > > Panic: duplicate free of item 0xc1c5a210 from zone 0xc143f000(g_bio) > > cpuid=0 > KDB: enter: panic > [thread pid 3 tid 100034 ] > stopped at kdb_enter+0x2b: nop > db> > > Is this a known issue? Don't know if it's a known issue, but can you use the "trace" DDB command and post the output here please, this will greatly help debugging for kernel hackers. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >