From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 15 23:52:59 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB80416A403 for ; Sat, 15 Apr 2006 23:52:59 +0000 (UTC) (envelope-from hannes.hauswedell@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A7C143D46 for ; Sat, 15 Apr 2006 23:52:58 +0000 (GMT) (envelope-from hannes.hauswedell@gmail.com) Received: by uproxy.gmail.com with SMTP id m3so232158ugc for ; Sat, 15 Apr 2006 16:52:57 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:reply-to:to:subject:user-agent:disposition-notification-to:mime-version:content-disposition:date:content-type:content-transfer-encoding:message-id; b=Hul/0yuRWH/DgcNGTbTwnmkFVvfEkGe1jJfSkjsZB8kpqpZbXAP7tEJ4nj+Tl1m6cnsXz3pRaipXRqHopX4qBLC7IbbKUx7l5CtwUJq/gF3kOdirzLA5xpP98GRN5NeyeUKblDbDxsCI2zwgJ4qrKbxOI5WRFLjZgxArJWoM/uM= Received: by 10.66.225.4 with SMTP id x4mr1702784ugg; Sat, 15 Apr 2006 16:52:57 -0700 (PDT) Received: from ?192.168.2.80? ( [85.220.132.38]) by mx.gmail.com with ESMTP id k30sm5407ugc.2006.04.15.16.52.57; Sat, 15 Apr 2006 16:52:57 -0700 (PDT) From: Hannes Hauswedell To: freebsd-hackers@freebsd.org User-Agent: KMail/1.9.1 MIME-Version: 1.0 Date: Sun, 16 Apr 2006 00:11:41 +0000 Message-Id: <200604160011.42334.hannes.hauswedell@gmail.com> X-Mailman-Approved-At: Sun, 16 Apr 2006 00:14:37 +0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: weird problems with porupgrade X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hannes Hauswedell List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Apr 2006 23:53:00 -0000 ok here is the log again, the lines missin in one log are prefixed with an # -> Session started at: Thu, 06 Apr 2006 10:46:10 +0000 ---> Fresh installation of games/angband started at: Thu, 06 Apr 2006 10:46:17 +0000 ---> Checking for the latest package of 'games/angband' ---> Fetching the package(s) for 'angband-3.0.6' (games/angband) # ---> Fetching angband-3.0.6 # ++ Will try the following sites in the order named: # ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/ # ---> Invoking a command: curl ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/All/angband-3.0.6.tbz -o /var/tmp/portupgradeURBFUqpc/angband-3.0.6.tbz # % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed # 0 579k 0 1404 0 0 1423 0 0:06:57 --:--:-- 0:06:57 1423 # 20 579k 20 120k 0 0 75560 0 0:00:07 0:00:01 0:00:06 183k # 59 579k 59 344k 0 0 130k 0 0:00:04 0:00:02 0:00:02 207k # 96 579k 96 559k 0 0 153k 0 0:00:03 0:00:03 --:--:-- 210k # 100 579k 100 579k 0 0 151k 0 0:00:03 0:00:03 --:--:-- 204k # ---> Downloaded as angband-3.0.6.tbz # ---> Identifying the package /var/tmp/portupgradeURBFUqpc/angband-3.0.6.tbz # ** Failed to save the dowloaded tarball as /usr/ports/packages/All/angband-3.0.6.tbz #---> Listing the results (+:done / -:ignored / *:skipped / !:failed) # ! angband-3.0.6 (Permission denied - /usr/ports/packages/All/angband-3.0.6.tbz) # ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed # ** Could not clean up temporary directory: Directory not empty - /var/tmp/portupgradeURBFUqpc ---> Fetching the latest package(s) for 'angband' (games/angband) # ---> Fetching angband # ++ Will try the following sites in the order named: # ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/ # ---> Invoking a command: curl ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/Latest/angband.tbz -o /var/tmp/portupgrade7LnEZ0Si/angband.tbz # % Total % Received % Xferd Average Speed Time Time Time Current # Dload Upload Total Spent Left Speed # 0 579k 0 1404 0 0 1451 0 0:06:49 --:--:-- 0:06:49 1451 #9 579k 9 56160 0 0 39568 0 0:00:15 0:00:01 0:00:14 118k #25 579k 25 147k 0 0 62424 0 0:00:09 0:00:02 0:00:07 100k # 55 579k 55 322k 0 0 95434 0 0:00:06 0:00:03 0:00:03 128k # 80 579k 80 464k 0 0 105k 0 0:00:05 0:00:04 0:00:01 134k #100 579k 100 579k 0 0 110k 0 0:00:05 0:00:05 --:--:-- 135k # ---> Downloaded as angband.tbz # ---> Identifying the package /var/tmp/portupgrade7LnEZ0Si/angband.tbz # ** Failed to save the dowloaded tarball as /usr/ports/packages/All/angband-3.0.6.tbz # ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) # ! angband@ (Permission denied - /usr/ports/packages/All/angband-3.0.6.tbz) # ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed # ** Could not clean up temporary directory: Directory not empty - /var/tmp/portupgrade7LnEZ0Si ---> Fresh installation of games/angband ended at: Thu, 06 Apr 2006 10:46:31 +0000 (consumed 00:00:13) ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) ! games/angband (package not found) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed ---> Session ended at: Thu, 06 Apr 2006 10:46:31 +0000 (consumed 00:00:20) thanks for help! From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 16 02:19:25 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B604816A406 for ; Sun, 16 Apr 2006 02:19:25 +0000 (UTC) (envelope-from viktor.vasilev@stud.tu-darmstadt.de) Received: from lnx131.hrz.tu-darmstadt.de (lnx131.hrz.tu-darmstadt.de [130.83.174.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0901443D46 for ; Sun, 16 Apr 2006 02:19:24 +0000 (GMT) (envelope-from viktor.vasilev@stud.tu-darmstadt.de) Received: from mailserver3.hrz.tu-darmstadt.de (lnx115.hrz.tu-darmstadt.de [130.83.174.27]) by lnx131.hrz.tu-darmstadt.de (8.13.4/8.12.10) with ESMTP id k3G2JMfH005977 for ; Sun, 16 Apr 2006 04:19:22 +0200 Received: from [130.83.20.203] (helo=ABC216.ram1st.wh.tu-darmstadt.de) by mailserver3.hrz.tu-darmstadt.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1FUwrC-0001e9-Oe for hackers@freebsd.org; Sun, 16 Apr 2006 04:19:22 +0200 From: Viktor Vasilev To: hackers@freebsd.org Date: Sun, 16 Apr 2006 04:19:13 +0200 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart11806670.PsUUlUV9QT"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604160419.21976.viktor.vasilev@stud.tu-darmstadt.de> Cc: Subject: freebsd port of gnu parted X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2006 02:19:25 -0000 --nextPart11806670.PsUUlUV9QT Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I've spent some time this saturday trying to port gnu parted over to=20 =46reeBSD. You can find the result and some instructions on building it her= e: http://0xdeadc0de.net/v/parted/ =46or the moment it only handles ATA drives. A chart describing parted's=20 features can be found here: http://www.gnu.org/software/parted/ Since it's a preliminary port, there will be some bugs, so use with caution= =2E=20 It would be best if you experiment on a spare drive with no precious data. Have fun :) Vik =2D-=20 PGP Key: 0xE09DC8D8/6799 4011 EBDE 6412 05A1 090C DBDF 5887 E09D C8D8 Signed/encrypted mail welcome! --nextPart11806670.PsUUlUV9QT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEQamp299Yh+CdyNgRAuIqAJ0RD8nUOgEAKy4y9VCeHu7pxw4VLwCdF5fw Y7N9oV/v1xt6dZYIHp+G6x0= =8hCi -----END PGP SIGNATURE----- --nextPart11806670.PsUUlUV9QT-- From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 16 10:53:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7729816A401 for ; Sun, 16 Apr 2006 10:53:18 +0000 (UTC) (envelope-from bachi@te-clan.ch) Received: from te-clan.ch (ns1.te-clan.ch [217.118.194.40]) by mx1.FreeBSD.org (Postfix) with SMTP id CA6D743D48 for ; Sun, 16 Apr 2006 10:53:17 +0000 (GMT) (envelope-from bachi@te-clan.ch) Received: (qmail 4324 invoked from network); 16 Apr 2006 10:53:14 -0000 Received: from unknown (HELO ?10.0.0.251?) (80.219.57.164) by te-clan.ch with SMTP; 16 Apr 2006 10:53:14 -0000 From: Andreas Bachmann To: freebsd-hardware@freebsd.org Content-Type: text/plain Date: Sun, 16 Apr 2006 12:53:11 +0200 Message-Id: <1145184791.25345.10.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Broadcom 440x on FreeBSD 6.0/6.1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2006 10:53:18 -0000 Hi, Got some problem with my new notebook: Dell Inspiron 9400 After installing 6.0/6.1-BETA4/6.1-RC1 and starting dhclient or setting my IP address, my OS hangs. I load the GENERIC kernel http://bachi.te-clan.ch/freebsd/messages Any suggestions? Andreas From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 16 13:35:41 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89F7A16A403 for ; Sun, 16 Apr 2006 13:35:41 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from mail.ciam.ru (ns.ciam.ru [213.247.195.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27C7A43D45 for ; Sun, 16 Apr 2006 13:35:41 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from [87.240.16.199] (helo=[192.168.0.4]) by mail.ciam.ru with esmtpa (Exim 4.x) id 1FV7Pg-0007Hf-7f; Sun, 16 Apr 2006 17:35:40 +0400 Message-ID: <44424792.4090706@FreeBSD.org> Date: Sun, 16 Apr 2006 17:33:06 +0400 From: Sergey Matveychuk User-Agent: Thunderbird 1.5 (X11/20060116) MIME-Version: 1.0 To: Viktor Vasilev References: <200604160419.21976.viktor.vasilev@stud.tu-darmstadt.de> In-Reply-To: <200604160419.21976.viktor.vasilev@stud.tu-darmstadt.de> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: freebsd port of gnu parted X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2006 13:35:41 -0000 Viktor Vasilev wrote: > Hi, > > I've spent some time this saturday trying to port gnu parted over to > FreeBSD. You can find the result and some instructions on building it here: > > http://0xdeadc0de.net/v/parted/ > > For the moment it only handles ATA drives. A chart describing parted's > features can be found here: > > http://www.gnu.org/software/parted/ > > Since it's a preliminary port, there will be some bugs, so use with caution. > It would be best if you experiment on a spare drive with no precious data. > > Have fun :) You can make a port: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ -- Dixi. Sem. From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 16 14:12:00 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A86016A404 for ; Sun, 16 Apr 2006 14:12:00 +0000 (UTC) (envelope-from hannes.hauswedell@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68DCE43D5C for ; Sun, 16 Apr 2006 14:11:59 +0000 (GMT) (envelope-from hannes.hauswedell@gmail.com) Received: by uproxy.gmail.com with SMTP id m3so292532ugc for ; Sun, 16 Apr 2006 07:11:58 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:user-agent:references:in-reply-to:disposition-notification-to:mime-version:content-disposition:date:reply-to:content-type:content-transfer-encoding:message-id; b=lmlEjcNcGwsnfUiwzXC46jrCpDaeSzMkKdv1CfJY3JmKYFR5IH1yKiV9cxRv7OtMeGBx6Hjd4uiNHkMWcThsYP6GiT0TZE7NUweZ6Sf5Giav6wOsj7iM+37kb0C4KOk/YqxdqupcvakYJ6Sir4Y38Ell7w4QCJqnHqRlgQOtu8c= Received: by 10.67.19.11 with SMTP id w11mr1954824ugi; Sun, 16 Apr 2006 07:11:58 -0700 (PDT) Received: from ?192.168.2.80? ( [85.220.132.38]) by mx.gmail.com with ESMTP id m1sm635500ugc.2006.04.16.07.11.58; Sun, 16 Apr 2006 07:11:58 -0700 (PDT) From: Hannes Hauswedell To: freebsd-hackers@freebsd.org User-Agent: KMail/1.9.1 References: <200604151635.16110.hannes.hauswedell@gmail.com> <20060415213036.GC830@turion.vk2pj.dyndns.org> In-Reply-To: <20060415213036.GC830@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Disposition: inline Date: Sun, 16 Apr 2006 14:30:43 +0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200604161430.43776.hannes.hauswedell@gmail.com> X-Mailman-Approved-At: Sun, 16 Apr 2006 14:16:31 +0000 Subject: Re: weird problems with porupgrade X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hannes Hauswedell List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2006 14:12:00 -0000 > I don't see any red. Could you post a unidiff or similar please. i have reposted it and i have done some browsing in pkgtools' source and although i dont speak ruby i can say for sure it is pkg_fetch's output that is completely missing. so i think that there must be some problem of ruby's subprocess being disconnected from my io-processing under certain circumstances... i am still uncertain where this behaviour is caused and would be grateful for any help! thanks @ jeremy soory for doublepost to you From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 16 16:09:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFB0816A404 for ; Sun, 16 Apr 2006 16:09:35 +0000 (UTC) (envelope-from hannes.hauswedell@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 974E843D45 for ; Sun, 16 Apr 2006 16:09:34 +0000 (GMT) (envelope-from hannes.hauswedell@gmail.com) Received: by uproxy.gmail.com with SMTP id m3so303894ugc for ; Sun, 16 Apr 2006 09:09:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:reply-to:to:subject:date:user-agent:references:in-reply-to:disposition-notification-to:mime-version:content-type:message-id; b=iQnbkdtqMg6Rd1ZRvLycAp/TrSj8JamTim8XKLuRZB6K6y5/y0Hs7cTSb/S+w9lJiTfzUnmTVrxj7K86+/2blyQb45sywZpjn/PsxHhuyJPfUWIWGj9h0aiw5Z9objgafQcnGS7ICYD5K+dFhlEUlRrIcf/rMZHSbIvBrX437O4= Received: by 10.66.221.13 with SMTP id t13mr2201599ugg; Sun, 16 Apr 2006 09:09:33 -0700 (PDT) Received: from ?192.168.2.80? ( [85.220.132.38]) by mx.gmail.com with ESMTP id k2sm360747ugf.2006.04.16.09.09.32; Sun, 16 Apr 2006 09:09:33 -0700 (PDT) From: Hannes Hauswedell To: freebsd-hackers@freebsd.org, FreeBSD-Ports@freebsd.org Date: Sun, 16 Apr 2006 16:28:17 +0000 User-Agent: KMail/1.9.1 References: <200604151635.16110.hannes.hauswedell@gmail.com> <20060415213036.GC830@turion.vk2pj.dyndns.org> <200604161430.43776.hannes.hauswedell@gmail.com> In-Reply-To: <200604161430.43776.hannes.hauswedell@gmail.com> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_iCnQENzYqvt8vWk" Message-Id: <200604161628.18641.hannes.hauswedell@gmail.com> X-Mailman-Approved-At: Sun, 16 Apr 2006 16:36:23 +0000 Cc: Subject: pkgtools-bug? (from freebsd-hackers -> Re: weird problems with porupgrade) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hannes Hauswedell List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2006 16:09:36 -0000 --Boundary-00=_iCnQENzYqvt8vWk Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline i have looked into the pkgtools ruby code.... it seems to be some bug with the logged_command function. i dont think it is a very clean solution but i have provided a diff against /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb that solves the problem. could someone with knowledge of ruby and maybe in charge of portupgrade check this? i have cc'ed to the ports-mailinglists too since it looks like a bug, thanks & happy easter ;) --Boundary-00=_iCnQENzYqvt8vWk Content-Type: text/plain; charset="iso-8859-1"; name="diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="diff" 483,484d482 < elsif STDIN.tty? < ['/usr/bin/script', '-qa', file, *args] 486c484 < ['/bin/sh', '-c', sprintf('%s >>%s 2>&1', shelljoin(*args), shelljoin(file))] --- > ['/usr/bin/script', '-qa', file, *args] --Boundary-00=_iCnQENzYqvt8vWk-- From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 16 16:19:10 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCB7116A404; Sun, 16 Apr 2006 16:19:09 +0000 (UTC) (envelope-from giffunip@asme.org) Received: from antivirus.cable.net.co (antivirus.cable.net.co [200.118.2.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id 046CD43D45; Sun, 16 Apr 2006 16:19:08 +0000 (GMT) (envelope-from giffunip@asme.org) Received: from epicac.cable.net.co ([200.118.2.50]) by antivirus.cable.net.co with ESMTP; 16 Apr 2006 11:15:40 -0500 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAQAAA+k= X-IronPort-AV: i="4.04,123,1144040400"; d="scan'208"; a="210664335:sNHT18669100" Received: from [69.79.218.227] by epicac.cable.net.co (Sun Java System Messaging Server 6.1 HotFix 0.09 (built Dec 14 2004)) with ESMTPA id <0IXS00AQBXAFQF10@epicac.cable.net.co>; Sun, 16 Apr 2006 11:13:28 +0500 (GMT) Date: Sun, 16 Apr 2006 11:19:06 -0500 From: "Pedro F. Giffuni" To: freebsd-hackers@FreeBSD.org Message-id: <44426E7A.9030301@asme.org> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_Os7fh9u+OFEhm8gSNoDjwQ)" X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051013 X-Mailman-Approved-At: Sun, 16 Apr 2006 16:36:39 +0000 Cc: Subject: OpenWatcom [Fwd: Re: OW on FreeBSD] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2006 16:19:10 -0000 This is a multi-part message in MIME format. --Boundary_(ID_Os7fh9u+OFEhm8gSNoDjwQ) Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT Hi; The OpenWatcom on FreeBSD project is one day old but it has advanced greatly(see attached message for current status). FreeBSD experts are welcome. cheers, Pedro. --Boundary_(ID_Os7fh9u+OFEhm8gSNoDjwQ) Content-type: message/rfc822; name="Re: OW on FreeBSD" Content-disposition: inline; filename="Re: OW on FreeBSD" Path: www-1.scitechsoft.com!not-for-mail X-Trace: www-1.scitechsoft.com 1145172236 9420 69.237.93.2 (16 Apr 2006 07:23:56 GMT) Date: Sun, 16 Apr 2006 00:24:11 -0700 From: Michal Necasek Subject: Re: OW on FreeBSD In-reply-to: Message-id: Organization: SciTech Software, Inc. X-Complaints-to: news@www-1.scitechsoft.com MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT NNTP-posting-date: Sun, 16 Apr 2006 07:23:56 +0000 (UTC) Newsgroups: openwatcom.contributors NNTP-posting-host: 69.237.93.2 References: User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8.0.1) Gecko/20060129 SeaMonkey/1.0 Xref: www-1.scitechsoft.com openwatcom.contributors:17364 Okay, I've done some tweaks to the source code so that some of it builds on FreeBSD. Note that currently the build thinks it's targeting Linux, which will need to be fixed. Most of the tools don't really care as long as it's some sort of UNIX, but some do. There are two different ways to build: one uses the build.sh script and the other uses boot.sh. I would suggest concentrating on the latter. The "boot" build uses exclusively the native compiler and builds wmake, wlink, wdis, debugger, profiler, vi, and a few other odds and ends. Right now the rough status is: - wmake builds and appears to work without any problems - wlink builds and partially works but crashes in some situations - wdis builds and works on some objects but not others, apparently because of some ELF reloc type not seen previously - debugger user interface does not build due to Linux-specific ioctls which need replacing with BSD equivalents - trap file does not build because Linux-specific ptrace stuff needs to be modified - profiler doesn't build either for similar reasons - vi builds but crashes at startup because of insufficient error checking; the real problem is that a build ncurses it uses is configured for Linux and fails to init on FreeBSD The "regular" build manages to compile wasm and wcc386, both apparently functional (after I fixed a GCC-specific problem in wcc386). It seems likely that both could be used as cross-compilers as long as wlink works (which it doesn't quite appear to). Anyway I'm no UNIX expert and I've seen FreeBSD for the first time yesterday, so now some real FreeBSD expertise is needed. IMO the best course of action is to port the debugger first, because that has proven extremely useful on Linux. I would also like to have the Watcom vi available, just because I can use the exact same editor on Windows, DOS, OS/2, and Linux (the failing console support stuff is shared by vi, debugger, profiler, and one or two other tools). Since FreeBSD uses ELF+DWARF as far as I can tell, there should be little work needed on the file format support, just the OS debugging interface. The other line of work is adding FreeBSD support to the Watcom clib runtime; I expect this should not be terribly difficult for someone familiar with FreeBSD internals if the Linux clib is used as a starting point. In general, it may be helpful to have a Linux box handy for comparison, because all this works (or at least should work) on Linux. Michal --Boundary_(ID_Os7fh9u+OFEhm8gSNoDjwQ)-- From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 16 19:57:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28B7216A417 for ; Sun, 16 Apr 2006 19:57:41 +0000 (UTC) (envelope-from bachi@te-clan.ch) Received: from te-clan.ch (ns1.te-clan.ch [217.118.194.40]) by mx1.FreeBSD.org (Postfix) with SMTP id 1D66A43D49 for ; Sun, 16 Apr 2006 19:57:39 +0000 (GMT) (envelope-from bachi@te-clan.ch) Received: (qmail 7466 invoked from network); 16 Apr 2006 19:57:37 -0000 Received: from unknown (HELO ?10.0.0.251?) (80.219.57.164) by te-clan.ch with SMTP; 16 Apr 2006 19:57:37 -0000 From: Andreas Bachmann To: Mikko =?ISO-8859-1?Q?Ty=F6l=E4j=E4rvi?= In-Reply-To: <20060416120208.D4092@antec.home> References: <1145184791.25345.10.camel@localhost> <20060416120208.D4092@antec.home> Content-Type: text/plain Date: Sun, 16 Apr 2006 21:57:34 +0200 Message-Id: <1145217454.25345.36.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Broadcom 440x on FreeBSD 6.0/6.1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2006 19:57:41 -0000 > The bfe driver is broken for RAM sizes above 1G, and you have 2G. > > For kicks, you could try booting with hw.physmem="1G" (in loader.conf > or manually). If that doesn't work, you have discovered a new bug. > > The ndis driver works on my H^HDell notebook (see ndisgen(8)). I found your post to freebsd-mobile with the same text :-) After limiting my physical memory, my NIC works now... I will look at the ndisgen. thanks a lot Andreas From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 17 13:05:03 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DC4516A402 for ; Mon, 17 Apr 2006 13:05:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6EB043D48 for ; Mon, 17 Apr 2006 13:05:02 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3HD50TR071639; Mon, 17 Apr 2006 09:05:00 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Marco van Tol Date: Mon, 17 Apr 2006 09:04:58 -0400 User-Agent: KMail/1.8.3 References: <20060412215021.GB1146@tols.org> <200604141017.30635.jhb@freebsd.org> <20060415104005.GB27978@tols.org> In-Reply-To: <20060415104005.GB27978@tols.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200604170904.58902.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1403/Sun Apr 16 05:44:45 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-hackers@freebsd.org Subject: Re: Per CPU cpu-statistics under SMP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2006 13:05:03 -0000 On Saturday 15 April 2006 06:40 am, Marco van Tol wrote: > On Fri, Apr 14, 2006 at 10:17:29AM -0400, John Baldwin wrote: > > On Friday 14 April 2006 06:38, Marco van Tol wrote: > > > On Thu, Apr 13, 2006 at 10:20:40AM -0400, John Baldwin wrote: > > > > On Wednesday 12 April 2006 17:50, Marco van Tol wrote: > > > > > Hi there, > > > > > > > > > > My apologies if this is the wrong list to ask this kind of > > > > > question. I would appreciate a pointer to the correct list if it = is > > > > > please. :) > > > > > > > > > > I noticed in the code for gkrellm /usr/ports/sysutils/gkrellm2 th= at > > > > > SMP per-cpu statistics were not yet supported under FreeBSD, and > > > > > decided to check whether I could add that. (I'm running a > > > > > (dual-core) Athlon64 X2 with FreeBSD 6.1-PRERELEASE) > > > > > I can't find sample code and/or documentation on how to acquire > > > > > that information from the kernel. > > > > > > [...] > > > > > > > > Is there an interface under FreeBSD to acquire the necessary > > > > > per-cpu statistics? > > > > > > > > They don't exist currently. I have a patch to make the stats per-C= PU > > > > for performance reasons (though it only helps out on systems with > > > > lots of CPUs (like 10) and hurts on systems with fewer CPUs (like > > > > 4)). It doesn't include a sysctl to get the per-CPU stats, but I > > > > could add one. > > > > > > OK, that I could use to get started on the code for adding per-CPU > > > stats to gkrellm under FreeBSD. Is the patch against FreeBSD CURRENT? > > > > > > Then if the per-CPU stats code hits the STABLE trunk, it's likely to = be > > > only a few changes to what I did perhaps. Or am I running a bit to far > > > ahead here? :) > > > > > > Is the patch in available your home area on www.freebsd.org? > > > > An early one but it doesn't export the data to userland yet. I need to > > figure out what interface to use for that. I could have the cp_time > > sysctl just include the CPU arrays after the global array and key > > off the passed in length to determine if they should be included or not. > > I must admit that I had to read up a bit to understand what you meant her= e, > but I think I do now. I think it should work. > If I understand correctly, the first array would have the composite CPU > stats, and following arrays would be the CPU specific stats. Right? > That'd be just like the linux /proc/stat. > > In case it's going to be done like this, will the sum of the CPU specific > stats be the composite stats? Yes. > I'm not familiar with the formal process of adding/changing sysctl's for > the kernel, so can't give much more comment. :) > I'm assuming there are formal guidelines to do things like that. I actually did it differently though to try and make it less confusing. I've added a kern.pcpu_time sysctl which is an array of 0..mp_maxid cp_time[] arrays (so (mp_maxid + 1) * CPUSTATES longs) which is just the per-CPU data. Userland can sum them up if it wants a composite total. Userland would first do a sysctl with a NULL buffer to get the required size (since it can vary with the number of CPUs in the system), malloc() a buffer, and then use the malloc'd buffer to make the requests. You should only have to do the malloc() at process start since FreeBSD doesn't currently allow for more CPUs to be added at runtime. You can try out the patch at http://www.FreeBSD.org/~jhb/patches/cp_time.patch =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 17 13:48:30 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CD1216A441; Mon, 17 Apr 2006 13:48:30 +0000 (UTC) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (goofy.demon.nl [83.160.134.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4756E43D48; Mon, 17 Apr 2006 13:48:28 +0000 (GMT) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (localhost [127.0.0.1]) by goofy.tols.org (8.13.4/8.13.4) with ESMTP id k3HDmQgt047515; Mon, 17 Apr 2006 13:48:26 GMT (envelope-from marco@goofy.tols.org) Received: (from marco@localhost) by goofy.tols.org (8.13.4/8.13.4/Submit) id k3HDmQxZ047514; Mon, 17 Apr 2006 13:48:26 GMT (envelope-from marco) Date: Mon, 17 Apr 2006 13:48:25 +0000 From: Marco van Tol To: John Baldwin Message-ID: <20060417134825.GA47043@tols.org> Mail-Followup-To: John Baldwin , freebsd-hackers@freebsd.org References: <20060412215021.GB1146@tols.org> <200604141017.30635.jhb@freebsd.org> <20060415104005.GB27978@tols.org> <200604170904.58902.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604170904.58902.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.88.1/1403/Sun Apr 16 09:44:45 2006 on goofy.tols.org X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on goofy.tols.org Cc: freebsd-hackers@freebsd.org Subject: Re: Per CPU cpu-statistics under SMP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2006 13:48:30 -0000 On Mon, Apr 17, 2006 at 09:04:58AM -0400, John Baldwin wrote: > On Saturday 15 April 2006 06:40 am, Marco van Tol wrote: > > On Fri, Apr 14, 2006 at 10:17:29AM -0400, John Baldwin wrote: [...] > > > An early one but it doesn't export the data to userland yet. I need to > > > figure out what interface to use for that. I could have the cp_time > > > sysctl just include the CPU arrays after the global array and key > > > off the passed in length to determine if they should be included or not. > > > > I must admit that I had to read up a bit to understand what you meant here, > > but I think I do now. I think it should work. > > If I understand correctly, the first array would have the composite CPU > > stats, and following arrays would be the CPU specific stats. Right? > > That'd be just like the linux /proc/stat. > > > > In case it's going to be done like this, will the sum of the CPU specific > > stats be the composite stats? > > Yes. > > > I'm not familiar with the formal process of adding/changing sysctl's for > > the kernel, so can't give much more comment. :) > > I'm assuming there are formal guidelines to do things like that. > > I actually did it differently though to try and make it less confusing. > I've added a kern.pcpu_time sysctl which is an array of 0..mp_maxid > cp_time[] arrays (so (mp_maxid + 1) * CPUSTATES longs) which is just the > per-CPU data. Userland can sum them up if it wants a composite total. > Userland would first do a sysctl with a NULL buffer to get the required > size (since it can vary with the number of CPUs in the system), malloc() > a buffer, and then use the malloc'd buffer to make the requests. You > should only have to do the malloc() at process start since FreeBSD doesn't > currently allow for more CPUs to be added at runtime. You can try out > the patch at http://www.FreeBSD.org/~jhb/patches/cp_time.patch Great thanks! I will try to apply the patch, and try to modify gkrellm to support it. I'll drop them (gkrellm developers) a note that I'm doing this, as it would be a waist of effort if somebody else has been doing preliminary work that I'd be doing again. :) I'll keep you up-to-date. Thanks. Marco -- Ik heb een hekel aan bumper-klevers, vanochtend zat er weer een voor me. From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 16:37:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70B6316A400 for ; Tue, 18 Apr 2006 16:37:42 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0436643D58 for ; Tue, 18 Apr 2006 16:37:41 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k3IGbe69003191 for ; Tue, 18 Apr 2006 11:37:40 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <444515C8.3030406@centtech.com> Date: Tue, 18 Apr 2006 11:37:28 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1404/Tue Apr 18 05:03:40 2006 on mh1.centtech.com X-Virus-Status: Clean Subject: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 16:37:42 -0000 Hi everyone! I've made a patch to /etc/rc.subr that makes the startup/shutdown rc scripting look similar to other OS's (many different linux distros, HP-UX, etc), but without color. The patch shouldn't break anything, and is only enabled if you have this in your /etc/rc.conf: rc_fancy="YES" Several of the /etc/rc.d/* scripts send output to stdout, so that could be cleaned up a bit if needed, but for now I tried to keep the patch as minimal as possible. This is still a first pass, so please give feedback. The patch can be grabbed from here: http://www.googlebit.com/freebsd/patches/rc_fancy.patch Enjoy! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 16:57:30 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B4AE16A403 for ; Tue, 18 Apr 2006 16:57:30 +0000 (UTC) (envelope-from gbergling@0xfce3.net) Received: from einhorn.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id B997E43D46 for ; Tue, 18 Apr 2006 16:57:28 +0000 (GMT) (envelope-from gbergling@0xfce3.net) X-Envelope-From: gbergling@0xfce3.net Received: from central.0xfce3.net (dslb-088-072-033-140.pools.arcor-ip.net [88.72.33.140]) (authenticated bits=128) by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id k3IGvJaH013958 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 18 Apr 2006 18:57:20 +0200 Received: from central.0xfce3.net (localhost [127.0.0.1]) by central.0xfce3.net (8.13.6/8.13.4) with ESMTP id k3IGvAHB017879; Tue, 18 Apr 2006 18:57:10 +0200 (CEST) (envelope-from gbergling@0xfce3.net) Received: (from gordon@localhost) by central.0xfce3.net (8.13.6/8.13.4/Submit) id k3IGv9IC017878; Tue, 18 Apr 2006 18:57:09 +0200 (CEST) (envelope-from gbergling@0xfce3.net) X-Authentication-Warning: central.0xfce3.net: gordon set sender to gbergling@0xfce3.net using -f Date: Tue, 18 Apr 2006 18:57:09 +0200 From: Gordon Bergling To: Eric Anderson Message-ID: <20060418165709.GA17705@central.0xfce3.net> References: <444515C8.3030406@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <444515C8.3030406@centtech.com> X-Url: X-Operating-System: FreeBSD 6.1-RC i386 X-Host-Uptime: 6:43PM up 9:47, 0 users, load averages: 0.14, 0.09, 0.03 User-Agent: Mutt/1.5.11 X-Spam-Score: * (1.377) AWL,BAYES_50,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8 Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 16:57:30 -0000 Hi, * Thus spake Eric Anderson (anderson@centtech.com): > I've made a patch to /etc/rc.subr that makes the startup/shutdown rc > scripting look similar to other OS's (many different linux distros, > HP-UX, etc), but without color. > > The patch shouldn't break anything, and is only enabled if you have this > in your /etc/rc.conf: > > rc_fancy="YES" > > Several of the /etc/rc.d/* scripts send output to stdout, so that could > be cleaned up a bit if needed, but for now I tried to keep the patch as > minimal as possible. > > This is still a first pass, so please give feedback. A short try on my notebook shows some errors. I don't want to let this email getting too big, so I put the "dmesg -a" output online. http://generic.0xfce3.net/dmesg-fancy.txt BTW, the patch applied cleanly. best regards, Gordon -- Gordon Bergling http://www.0xFCE3.net/ PGP Fingerprint: 7732 9BB1 5013 AE8B E42C 28E0 93B9 D32B C76F 02A0 RIPE-HDL: MDTP-RIPE "Minimal Electronic Music" From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 17:43:32 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4FD616A402 for ; Tue, 18 Apr 2006 17:43:32 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AC6943D45 for ; Tue, 18 Apr 2006 17:43:32 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k3IHhPxe006229; Tue, 18 Apr 2006 12:43:25 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44452532.40703@centtech.com> Date: Tue, 18 Apr 2006 12:43:14 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Gordon Bergling References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> In-Reply-To: <20060418165709.GA17705@central.0xfce3.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1404/Tue Apr 18 05:03:40 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 17:43:32 -0000 Gordon Bergling wrote: > Hi, > > * Thus spake Eric Anderson (anderson@centtech.com): >> I've made a patch to /etc/rc.subr that makes the startup/shutdown rc >> scripting look similar to other OS's (many different linux distros, >> HP-UX, etc), but without color. >> >> The patch shouldn't break anything, and is only enabled if you have this >> in your /etc/rc.conf: >> >> rc_fancy="YES" >> >> Several of the /etc/rc.d/* scripts send output to stdout, so that could >> be cleaned up a bit if needed, but for now I tried to keep the patch as >> minimal as possible. >> >> This is still a first pass, so please give feedback. > > A short try on my notebook shows some errors. > I don't want to let this email getting too big, so I put the "dmesg -a" > output online. http://generic.0xfce3.net/dmesg-fancy.txt > > BTW, the patch applied cleanly. Thanks for the feedback! Looks like I made an erroneous assumption that the wc, expr, and printf tools found in /usr/bin and /bin would be available through boot, but that isn't the case on systems with those file systems separate from /. I'm not sure how to resolve some of these issues, since I don't know of a way to do those functions in csh without them. I'm open to suggestions here from anyone. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 17:50:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AF2616A40E for ; Tue, 18 Apr 2006 17:50:18 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F32F43D55 for ; Tue, 18 Apr 2006 17:50:17 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k3IHnUNk082560; Tue, 18 Apr 2006 11:49:30 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 18 Apr 2006 11:49:33 -0600 (MDT) Message-Id: <20060418.114933.69380798.imp@bsdimp.com> To: anderson@centtech.com From: "M. Warner Losh" In-Reply-To: <44452532.40703@centtech.com> References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: gbergling@0xfce3.net, freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 17:50:18 -0000 In message: <44452532.40703@centtech.com> Eric Anderson writes: : Gordon Bergling wrote: : > Hi, : > : > * Thus spake Eric Anderson (anderson@centtech.com): : >> I've made a patch to /etc/rc.subr that makes the startup/shutdown rc : >> scripting look similar to other OS's (many different linux distros, : >> HP-UX, etc), but without color. : >> : >> The patch shouldn't break anything, and is only enabled if you have this : >> in your /etc/rc.conf: : >> : >> rc_fancy="YES" : >> : >> Several of the /etc/rc.d/* scripts send output to stdout, so that could : >> be cleaned up a bit if needed, but for now I tried to keep the patch as : >> minimal as possible. : >> : >> This is still a first pass, so please give feedback. : > : > A short try on my notebook shows some errors. : > I don't want to let this email getting too big, so I put the "dmesg -a" : > output online. http://generic.0xfce3.net/dmesg-fancy.txt : > : > BTW, the patch applied cleanly. : : : Thanks for the feedback! Looks like I made an erroneous assumption that : the wc, expr, and printf tools found in /usr/bin and /bin would be : available through boot, but that isn't the case on systems with those : file systems separate from /. I'm not sure how to resolve some of these : issues, since I don't know of a way to do those functions in csh without : them. I'm open to suggestions here from anyone. /bin and /sbin are available through the entire boot. Only things in /usr are suspect because /usr gets mounted early in the boot process, but not as early as /. Warner From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 18:02:13 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D52516A406 for ; Tue, 18 Apr 2006 18:02:13 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29CC843D4C for ; Tue, 18 Apr 2006 18:02:09 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by nproxy.gmail.com with SMTP id x37so653006nfc for ; Tue, 18 Apr 2006 11:02:08 -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:references; b=T34DbZNkLPoALC0VC5RzPGoMEGNssb53HOJWkiACQK5R2xRb2Aox/7fuPg8TAhhST3O8IPOjQI55upjgFpDdzlC520H6E436VMJHccxVE406OFFCq8aKVlkquZNVva+Z8Zlk13qkmEbADxYA1RLfY8ohsBw5oC/CBmqKNWAjrnY= Received: by 10.48.30.1 with SMTP id d1mr3531601nfd; Tue, 18 Apr 2006 11:02:07 -0700 (PDT) Received: by 10.48.217.6 with HTTP; Tue, 18 Apr 2006 11:02:07 -0700 (PDT) Message-ID: <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> Date: Tue, 18 Apr 2006 14:02:07 -0400 From: "Coleman Kane" To: "M. Warner Losh" In-Reply-To: <20060418.114933.69380798.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_20421_28621655.1145383327836" References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: gbergling@0xfce3.net, freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 18:02:13 -0000 ------=_Part_20421_28621655.1145383327836 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 4/18/06, M. Warner Losh wrote: > > In message: <44452532.40703@centtech.com> > Eric Anderson writes: > : Gordon Bergling wrote: > : > Hi, > : > > : > * Thus spake Eric Anderson (anderson@centtech.com): > : >> I've made a patch to /etc/rc.subr that makes the startup/shutdown rc > : >> scripting look similar to other OS's (many different linux distros, > : >> HP-UX, etc), but without color. > : >> > : >> The patch shouldn't break anything, and is only enabled if you have > this > : >> in your /etc/rc.conf: > : >> > : >> rc_fancy=3D"YES" > : >> > : >> Several of the /etc/rc.d/* scripts send output to stdout, so that > could > : >> be cleaned up a bit if needed, but for now I tried to keep the patch > as > : >> minimal as possible. > : >> > : >> This is still a first pass, so please give feedback. > : > > : > A short try on my notebook shows some errors. > : > I don't want to let this email getting too big, so I put the "dmesg > -a" > : > output online. http://generic.0xfce3.net/dmesg-fancy.txt > : > > : > BTW, the patch applied cleanly. > : > : > : Thanks for the feedback! Looks like I made an erroneous assumption tha= t > : the wc, expr, and printf tools found in /usr/bin and /bin would be > : available through boot, but that isn't the case on systems with those > : file systems separate from /. I'm not sure how to resolve some of thes= e > : issues, since I don't know of a way to do those functions in csh withou= t > : them. I'm open to suggestions here from anyone. > > /bin and /sbin are available through the entire boot. Only things in > /usr are suspect because /usr gets mounted early in the boot process, > but not as early as /. > > Warner Nice work! I too noticed the dependence upon wc, printf, expr. I went ahead and rewrot= e these into equivalents in native sh. (attaching new diff). This diff is against the latest 7-CURRENT rc.subr. I had to manually merge = 3 hunks due to some differences. -- coleman kane ------=_Part_20421_28621655.1145383327836 Content-Type: text/x-patch; name=rc_fancy-cokane.patch; charset=us-ascii Content-Transfer-Encoding: 7bit X-Attachment-Id: f_em6jnmbg Content-Disposition: attachment; filename="rc_fancy-cokane.patch" --- rc.subr.orig Tue Apr 18 13:58:14 2006 +++ rc.subr Tue Apr 18 13:57:36 2006 @@ -313,12 +313,16 @@ break fi _list=$_nlist - echo -n ${_prefix:-"Waiting for PIDS: "}$_list + if ! checkyesno rc_fancy; then + echo -n ${_prefix:-"Waiting for PIDS: "}$_list + fi _prefix=", " sleep 2 done if [ -n "$_prefix" ]; then - echo "." + if ! checkyesno rc_fancy; then + echo "." + fi fi } @@ -564,12 +568,14 @@ # if the precmd failed and force # isn't set, exit # + rcargsize=`echo $rc_arg` + rcargsize=${#rcargsize} if [ -n "$_precmd" ]; then debug "run_rc_command: evaluating ${_precmd}()." eval $_precmd $rc_extra_args _return=$? [ $_return -ne 0 ] && [ -z "$rc_force" ] && - return 1 + (echo_fancy "FAILED" `expr 10 + $rcargsize - 1`) && return 1 fi if [ -n "$_cmd" ]; then @@ -577,7 +583,7 @@ eval $_cmd $rc_extra_args _return=$? [ $_return -ne 0 ] && [ -z "$rc_force" ] && - return 1 + (echo_fancy "FAILED" `expr 10 + $rcargsize - 1`) && return 1 fi if [ -n "$_postcmd" ]; then @@ -585,6 +591,7 @@ eval $_postcmd $rc_extra_args _return=$? fi + echo_fancy " OK " 0 return $_return fi @@ -600,13 +607,16 @@ ;; start) + echo -n "Starting ${name}" if [ -z "$rc_fast" -a -n "$rc_pid" ]; then + echo_fancy " SKIP " 9 echo 1>&2 "${name} already running? (pid=$rc_pid)." return 1 fi if [ ! -x ${_chroot}${command} ]; then info "run_rc_command: cannot run ($command)." + echo_fancy "ERROR " 9 return 1 fi @@ -617,6 +627,7 @@ if ! checkyesno $_f; then warn "\$${_f} is not enabled." if [ -z "$rc_force" ]; then + echo_fancy "ERROR " 9 return 1 fi fi @@ -625,6 +636,7 @@ if [ ! -d "${_f}/." ]; then warn "${_f} is not a directory." if [ -z "$rc_force" ]; then + echo_fancy "ERROR " 9 return 1 fi fi @@ -633,6 +645,7 @@ if [ ! -r "${_f}" ]; then warn "${_f} is not readable." if [ -z "$rc_force" ]; then + echo_fancy "ERROR " 9 return 1 fi fi @@ -646,12 +659,11 @@ eval $_precmd _return=$? [ $_return -ne 0 ] && [ -z "$rc_force" ] && - return 1 + (echo_fancy "ERROR " 9) && return 1 fi # setup the command to run, and run it # - echo "Starting ${name}." if [ -n "$_chroot" ]; then _doit="\ ${_nice:+nice -n $_nice }\ @@ -673,7 +685,7 @@ debug "run_rc_command: _doit: $_doit" eval $_doit _return=$? - [ $_return -ne 0 ] && [ -z "$rc_force" ] && return 1 + [ $_return -ne 0 ] && [ -z "$rc_force" ] && (echo_fancy "FAILED" 9) && return 1 # finally, run postcmd # @@ -681,15 +693,19 @@ debug "run_rc_command: evaluating ${_postcmd}()." eval $_postcmd fi + echo_fancy " OK " 9 ;; stop) + echo -n "Stopping ${name}" if [ -z "$rc_pid" ]; then [ -n "$rc_fast" ] && return 0 if [ -n "$pidfile" ]; then + echo_fancy " SKIP " 9 echo 1>&2 \ "${name} not running? (check $pidfile)." else + echo_fancy " SKIP " 9 echo 1>&2 "${name} not running?" fi return 1 @@ -702,12 +718,11 @@ eval $_precmd _return=$? [ $_return -ne 0 ] && [ -z "$rc_force" ] && - return 1 + (echo_fancy "ERROR " 9) && return 1 fi # send the signal to stop # - echo "Stopping ${name}." _doit="kill -${sig_stop:-TERM} $rc_pid" if [ -n "$_user" ]; then _doit="su -m $_user -c 'sh -c \"$_doit\"'" @@ -718,7 +733,7 @@ # eval $_doit _return=$? - [ $_return -ne 0 ] && [ -z "$rc_force" ] && return 1 + [ $_return -ne 0 ] && [ -z "$rc_force" ] && (echo_fancy "FAILED" 9) && return 1 # wait for the command to exit, # and run postcmd. @@ -727,24 +742,27 @@ eval $_postcmd _return=$? fi + echo_fancy " OK " 9 ;; reload) + echo -n "Reloading ${name} config files" if [ -z "$rc_pid" ]; then if [ -n "$pidfile" ]; then + echo_fancy "SKIPPED" 23 echo 1>&2 \ "${name} not running? (check $pidfile)." else + echo_fancy "SKIPPED" 23 echo 1>&2 "${name} not running?" fi return 1 fi - echo "Reloading ${name} config files." if [ -n "$_precmd" ]; then eval $_precmd _return=$? [ $_return -ne 0 ] && [ -z "$rc_force" ] && - return 1 + (echo_fancy "FAILED" 23) && return 1 fi _doit="kill -${sig_reload:-HUP} $rc_pid" if [ -n "$_user" ]; then @@ -752,11 +770,12 @@ fi eval $_doit _return=$? - [ $_return -ne 0 ] && [ -z "$rc_force" ] && return 1 + [ $_return -ne 0 ] && [ -z "$rc_force" ] && (echo_fancy "FAILED" 23) && return 1 if [ -n "$_postcmd" ]; then eval $_postcmd _return=$? fi + echo_fancy " OK " 23 ;; restart) @@ -1428,3 +1447,33 @@ } fi + +echo_fancy () { + columns=80 + label=$1 + namesize=`echo -n $name` + namesize=${#namesize} + rc_argsize=`echo -n $rc_arg` + rc_argsize=${#rc_argsize} + padding="" + paddingsize=$(($columns - 15 - $2 - $namesize)) + until [ 0 = ${paddingsize} ]; do + padding=" $padding" + paddingsize=$(($paddingsize - 1)) + done + if checkyesno rc_fancy; then + if [ $2 = 0 ]; then + padding="" + paddingsize=$((60 - $namesize - $rc_argsize)) + until [ 0 = ${paddingsize} ]; do + padding=" $padding" + paddingsize=$(($paddingsize - 1)) + done + echo -e "\rRunning ${rc_arg} $name $padding [$label]" + else + echo " ... $padding [$label]" + fi + else + echo "." + fi +} ------=_Part_20421_28621655.1145383327836-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 18:12:46 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D14716A401 for ; Tue, 18 Apr 2006 18:12:46 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93D6843D70 for ; Tue, 18 Apr 2006 18:12:33 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so771920nfc for ; Tue, 18 Apr 2006 11:12:32 -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:references; b=LKCh+v6oDI1a9+1nboj6cnqL7LAPXWTGcJiKpSHyJz9CECr8lozcOwIO2DL8bkxlbCgeqKXuwRXvPepGK3CNCJJbE84w6X7GVG8n/yYWMc91yT/eUxntwC+AyTFCSmkaVcX6jcLhXvZd2yBE5j7CElmFUMXs/ei46/VWYZrimQI= Received: by 10.49.68.11 with SMTP id v11mr2441985nfk; Tue, 18 Apr 2006 11:06:26 -0700 (PDT) Received: by 10.48.217.6 with HTTP; Tue, 18 Apr 2006 11:06:26 -0700 (PDT) Message-ID: <346a80220604181106q209d04f8s87c92f0dd3c158fe@mail.gmail.com> Date: Tue, 18 Apr 2006 14:06:26 -0400 From: "Coleman Kane" To: "M. Warner Losh" In-Reply-To: <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> MIME-Version: 1.0 References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> 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: gbergling@0xfce3.net, freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 18:12:46 -0000 On 4/18/06, Coleman Kane wrote: > > On 4/18/06, M. Warner Losh wrote: > > > In message: <44452532.40703@centtech.com> > > Eric Anderson writes: > > : > > : Thanks for the feedback! Looks like I made an erroneous assumption > > that > > : the wc, expr, and printf tools found in /usr/bin and /bin would be > > : available through boot, but that isn't the case on systems with those > > : file systems separate from /. I'm not sure how to resolve some of > > these > > : issues, since I don't know of a way to do those functions in csh > > without > > : them. I'm open to suggestions here from anyone. > > > > /bin and /sbin are available through the entire boot. Only things in > > /usr are suspect because /usr gets mounted early in the boot process, > > but not as early as /. > > > > Warner > > > Nice work! > > I too noticed the dependence upon wc, printf, expr. I went ahead and > rewrote these into equivalents in native sh. (attaching new diff). > > This diff is against the latest 7-CURRENT rc.subr. I had to manually merg= e > 3 hunks due to some differences. > > -- > coleman kane > I did some ugly-looking loops to build the space-padding expansion. Does anybody know of a better, more elegant way to accomplish the same thing wit= h sh (and/or stuff in /bin,/sbin)? -- coleman From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 18:30:48 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8312D16A406 for ; Tue, 18 Apr 2006 18:30:48 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id D872443D4C for ; Tue, 18 Apr 2006 18:30:46 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so775745nfc for ; Tue, 18 Apr 2006 11:30:45 -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:references; b=jPLDBUUQr9GLBvlaQYJvFzQhrTjqFLoDJUOW01PvNKB/B5bFIorz5qAnriCJO2tCjB7k6CfF4iEkzniz/OObM4qPYQWzXmhsvX7zmIlRDruneYfNp44cWzbRvdnzPRcEu1cb9F9ZPTHOtseh1X8zFjP2jMj4J0t5AwYDulTaZ6w= Received: by 10.49.58.1 with SMTP id l1mr97591nfk; Tue, 18 Apr 2006 11:04:43 -0700 (PDT) Received: by 10.48.217.6 with HTTP; Tue, 18 Apr 2006 11:04:43 -0700 (PDT) Message-ID: <346a80220604181104y63bee2efi426d0a4755be305c@mail.gmail.com> Date: Tue, 18 Apr 2006 14:04:43 -0400 From: "Coleman Kane" To: "M. Warner Losh" In-Reply-To: <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> MIME-Version: 1.0 References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> 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: gbergling@0xfce3.net, freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 18:30:48 -0000 On 4/18/06, Coleman Kane wrote: > > On 4/18/06, M. Warner Losh wrote: > > > In message: <44452532.40703@centtech.com> > > Eric Anderson writes: > > : Gordon Bergling wrote: > > : > Hi, > > : > > > : > * Thus spake Eric Anderson (anderson@centtech.com): > > : >> I've made a patch to /etc/rc.subr that makes the startup/shutdown > > rc > > : >> scripting look similar to other OS's (many different linux distros= , > > > > : >> HP-UX, etc), but without color. > > : >> > > : >> The patch shouldn't break anything, and is only enabled if you hav= e > > this > > : >> in your /etc/rc.conf: > > : >> > > : >> rc_fancy=3D"YES" > > : >> > > : >> Several of the /etc/rc.d/* scripts send output to stdout, so that > > could > > : >> be cleaned up a bit if needed, but for now I tried to keep the > > patch as > > : >> minimal as possible. > > : >> > > : >> This is still a first pass, so please give feedback. > > : > > > : > A short try on my notebook shows some errors. > > : > I don't want to let this email getting too big, so I put the "dmesg > > -a" > > : > output online. http://generic.0xfce3.net/dmesg-fancy.txt > > : > > > : > BTW, the patch applied cleanly. > > : > > : > > : Thanks for the feedback! Looks like I made an erroneous assumption > > that > > : the wc, expr, and printf tools found in /usr/bin and /bin would be > > : available through boot, but that isn't the case on systems with those > > : file systems separate from /. I'm not sure how to resolve some of > > these > > : issues, since I don't know of a way to do those functions in csh > > without > > : them. I'm open to suggestions here from anyone. > > Also, /bin/sh is used to execute rc NOT /bin/csh. So you are writing in Bourne shell and not C-Shell. -- > coleman kane > > > > From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 18:38:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C371D16A404 for ; Tue, 18 Apr 2006 18:38:18 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45E0443D49 for ; Tue, 18 Apr 2006 18:38:18 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k3IIc8rD008663; Tue, 18 Apr 2006 13:38:08 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44453204.3030906@centtech.com> Date: Tue, 18 Apr 2006 13:37:56 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: cokane@cokane.org References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> In-Reply-To: <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1404/Tue Apr 18 05:03:40 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: gbergling@0xfce3.net, freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 18:38:19 -0000 Coleman Kane wrote: > On 4/18/06, *M. Warner Losh* > wrote: > > In message: <44452532.40703@centtech.com > > > Eric Anderson > writes: > : Gordon Bergling wrote: > : > Hi, > : > > : > * Thus spake Eric Anderson (anderson@centtech.com > ): > : >> I've made a patch to /etc/rc.subr that makes the > startup/shutdown rc > : >> scripting look similar to other OS's (many different linux > distros, > : >> HP-UX, etc), but without color. > : >> > : >> The patch shouldn't break anything, and is only enabled if you > have this > : >> in your /etc/rc.conf: > : >> > : >> rc_fancy="YES" > : >> > : >> Several of the /etc/rc.d/* scripts send output to stdout, so > that could > : >> be cleaned up a bit if needed, but for now I tried to keep the > patch as > : >> minimal as possible. > : >> > : >> This is still a first pass, so please give feedback. > : > > : > A short try on my notebook shows some errors. > : > I don't want to let this email getting too big, so I put the > "dmesg -a" > : > output online. http://generic.0xfce3.net/dmesg-fancy.txt > : > > : > BTW, the patch applied cleanly. > : > : > : Thanks for the feedback! Looks like I made an erroneous > assumption that > : the wc, expr, and printf tools found in /usr/bin and /bin would be > : available through boot, but that isn't the case on systems with those > : file systems separate from /. I'm not sure how to resolve some of > these > : issues, since I don't know of a way to do those functions in csh > without > : them. I'm open to suggestions here from anyone. > > /bin and /sbin are available through the entire boot. Only things in > /usr are suspect because /usr gets mounted early in the boot process, > but not as early as /. > > Warner > > > Nice work! > > I too noticed the dependence upon wc, printf, expr. I went ahead and > rewrote these into equivalents in native sh. (attaching new diff). > > This diff is against the latest 7-CURRENT rc.subr. I had to manually > merge 3 hunks due to some differences. Thanks!! I've put the updated version (for 6-STABLE) here: http://www.googlebit.com/freebsd/patches/rc_fancy.patch-2 Gordon - can you give this version a try? Thanks, Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 18:59:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B38816A401 for ; Tue, 18 Apr 2006 18:59:49 +0000 (UTC) (envelope-from gbergling@0xfce3.net) Received: from einhorn.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F56143D46 for ; Tue, 18 Apr 2006 18:59:47 +0000 (GMT) (envelope-from gbergling@0xfce3.net) X-Envelope-From: gbergling@0xfce3.net Received: from central.0xfce3.net (dslb-088-072-033-140.pools.arcor-ip.net [88.72.33.140]) (authenticated bits=128) by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id k3IIxNSn002510 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 18 Apr 2006 20:59:23 +0200 Received: from central.0xfce3.net (localhost [127.0.0.1]) by central.0xfce3.net (8.13.6/8.13.4) with ESMTP id k3IIxEPL018630; Tue, 18 Apr 2006 20:59:14 +0200 (CEST) (envelope-from gbergling@0xfce3.net) Received: (from gordon@localhost) by central.0xfce3.net (8.13.6/8.13.4/Submit) id k3IIxCZa018629; Tue, 18 Apr 2006 20:59:12 +0200 (CEST) (envelope-from gbergling@0xfce3.net) X-Authentication-Warning: central.0xfce3.net: gordon set sender to gbergling@0xfce3.net using -f Date: Tue, 18 Apr 2006 20:59:11 +0200 From: Gordon Bergling To: Eric Anderson Message-ID: <20060418185911.GA18485@central.0xfce3.net> References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> <44453204.3030906@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44453204.3030906@centtech.com> X-Url: X-Operating-System: FreeBSD 6.1-RC i386 X-Host-Uptime: 8:44PM up 11:47, 0 users, load averages: 0.08, 0.05, 0.01 User-Agent: Mutt/1.5.11 X-Spam-Score: * (1.394) AWL,BAYES_50,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8 Cc: gbergling@0xfce3.net, freebsd-hackers@freebsd.org, cokane@cokane.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 18:59:49 -0000 * Thus spake Eric Anderson (anderson@centtech.com): > Coleman Kane wrote: > >On 4/18/06, *M. Warner Losh* > > >wrote: > > > > In message: <44452532.40703@centtech.com > > > > > Eric Anderson > > writes: > > : Gordon Bergling wrote: > > : > Hi, > > : > > > : > * Thus spake Eric Anderson (anderson@centtech.com > > ): > > : >> I've made a patch to /etc/rc.subr that makes the > > startup/shutdown rc > > : >> scripting look similar to other OS's (many different linux > > distros, > > : >> HP-UX, etc), but without color. > > : >> > > : >> The patch shouldn't break anything, and is only enabled if you > > have this > > : >> in your /etc/rc.conf: > > : >> > > : >> rc_fancy="YES" > > : >> > > : >> Several of the /etc/rc.d/* scripts send output to stdout, so > > that could > > : >> be cleaned up a bit if needed, but for now I tried to keep the > > patch as > > : >> minimal as possible. > > : >> > > : >> This is still a first pass, so please give feedback. > > : > > > : > A short try on my notebook shows some errors. > > : > I don't want to let this email getting too big, so I put the > > "dmesg -a" > > : > output online. http://generic.0xfce3.net/dmesg-fancy.txt > > : > > > : > BTW, the patch applied cleanly. > > : > > : > > : Thanks for the feedback! Looks like I made an erroneous > > assumption that > > : the wc, expr, and printf tools found in /usr/bin and /bin would be > > : available through boot, but that isn't the case on systems with those > > : file systems separate from /. I'm not sure how to resolve some of > > these > > : issues, since I don't know of a way to do those functions in csh > > without > > : them. I'm open to suggestions here from anyone. > > > > /bin and /sbin are available through the entire boot. Only things in > > /usr are suspect because /usr gets mounted early in the boot process, > > but not as early as /. > > > > Warner > > > > > >Nice work! > > > >I too noticed the dependence upon wc, printf, expr. I went ahead and > >rewrote these into equivalents in native sh. (attaching new diff). > > > >This diff is against the latest 7-CURRENT rc.subr. I had to manually > >merge 3 hunks due to some differences. > > Thanks!! I've put the updated version (for 6-STABLE) here: > > http://www.googlebit.com/freebsd/patches/rc_fancy.patch-2 > > > Gordon - can you give this version a try? Much better now. :) The [OK] Messages printed correctly. Some [failed] messages are missing a \t I think. But this should be the error of the respective scripts. Nice work so far... ;) best regards, Gordon -- Gordon Bergling http://www.0xFCE3.net/ PGP Fingerprint: 7732 9BB1 5013 AE8B E42C 28E0 93B9 D32B C76F 02A0 RIPE-HDL: MDTP-RIPE "Minimal Electronic Music" From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 19:30:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECDD516A405 for ; Tue, 18 Apr 2006 19:30:27 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C6AA43D53 for ; Tue, 18 Apr 2006 19:30:26 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail16.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k3IJUJ1s013024 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Apr 2006 05:30:19 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k3IJUJc1003063; Wed, 19 Apr 2006 05:30:19 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k3IJUIbx003062; Wed, 19 Apr 2006 05:30:18 +1000 (EST) (envelope-from peter) Date: Wed, 19 Apr 2006 05:30:18 +1000 From: Peter Jeremy To: cokane@cokane.org Message-ID: <20060418193018.GB694@turion.vk2pj.dyndns.org> References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 19:30:28 -0000 On Tue, 2006-Apr-18 14:02:07 -0400, Coleman Kane wrote: A few comments on the shellscript: >+ rcargsize=`echo $rc_arg` >+ rcargsize=${#rcargsize} Try rcargsize=$((${#rc_arg} + 1)) >- return 1 >+ (echo_fancy "FAILED" `expr 10 + $rcargsize - 1`) && return 1 Try echo_fancy "FAILED" $((10 + $rcargsize - 1)) && return 1 >+echo_fancy () { ... >+ namesize=`echo -n $name` >+ namesize=${#namesize} or namesize=${#name} >+ padding="" >+ paddingsize=$(($columns - 15 - $2 - $namesize)) >+ until [ 0 = ${paddingsize} ]; do >+ padding=" $padding" >+ paddingsize=$(($paddingsize - 1)) >+ done This particular block of code appears unnecessary (since $padding is unused). >+ paddingsize=$((60 - $namesize - $rc_argsize)) >+ until [ 0 = ${paddingsize} ]; do >+ padding=" $padding" >+ paddingsize=$(($paddingsize - 1)) >+ done For safety, the conditions should probably be [ 0 -ge ${paddingsize} ] I don't see any alternative to the until loop. If efficiency turns out to be a real issue then you could try doing the expansion in multiple goes. Eg: until [ 8 -gt ${paddingsize} ]; do padding=" $padding" paddingsize=$(($paddingsize - 8)) done until [ 0 -ge ${paddingsize} ]; do padding=" $padding" paddingsize=$(($paddingsize - 1)) done -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 20:02:44 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 397E916A4EF for ; Tue, 18 Apr 2006 20:02:42 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C16EB43D48 for ; Tue, 18 Apr 2006 20:02:41 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k3IK2dMd012609; Tue, 18 Apr 2006 15:02:39 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <444545D3.5010405@centtech.com> Date: Tue, 18 Apr 2006 15:02:27 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Peter Jeremy References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> <20060418193018.GB694@turion.vk2pj.dyndns.org> In-Reply-To: <20060418193018.GB694@turion.vk2pj.dyndns.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1404/Tue Apr 18 05:03:40 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, cokane@cokane.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 20:02:44 -0000 Peter Jeremy wrote: > On Tue, 2006-Apr-18 14:02:07 -0400, Coleman Kane wrote: > A few comments on the shellscript: > >> + rcargsize=`echo $rc_arg` >> + rcargsize=${#rcargsize} > > Try rcargsize=$((${#rc_arg} + 1)) > >> - return 1 >> + (echo_fancy "FAILED" `expr 10 + $rcargsize - 1`) && return 1 > > Try echo_fancy "FAILED" $((10 + $rcargsize - 1)) && return 1 > >> +echo_fancy () { > ... >> + namesize=`echo -n $name` >> + namesize=${#namesize} > or namesize=${#name} > >> + padding="" >> + paddingsize=$(($columns - 15 - $2 - $namesize)) >> + until [ 0 = ${paddingsize} ]; do >> + padding=" $padding" >> + paddingsize=$(($paddingsize - 1)) >> + done > > This particular block of code appears unnecessary (since $padding is unused). I must be missing something, because I'm pretty sure it's used.. What did I miss? >> + paddingsize=$((60 - $namesize - $rc_argsize)) >> + until [ 0 = ${paddingsize} ]; do >> + padding=" $padding" >> + paddingsize=$(($paddingsize - 1)) >> + done > > For safety, the conditions should probably be [ 0 -ge ${paddingsize} ] > I don't see any alternative to the until loop. If efficiency turns out > to be a real issue then you could try doing the expansion in multiple > goes. Eg: > > until [ 8 -gt ${paddingsize} ]; do > padding=" $padding" > paddingsize=$(($paddingsize - 8)) > done > until [ 0 -ge ${paddingsize} ]; do > padding=" $padding" > paddingsize=$(($paddingsize - 1)) > done Thanks for the hints. I was testing the same changes to the namesize/etc as you suggested, and it does work and is more readable and more efficient. I've included your suggestions and put the latest changes here: http://www.googlebit.com/freebsd/patches/rc_fancy.patch-3 Thanks for all the feedback! Keep it coming! :) Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 20:33:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8329816A400 for ; Tue, 18 Apr 2006 20:33:57 +0000 (UTC) (envelope-from gbergling@0xfce3.net) Received: from einhorn.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5784243D46 for ; Tue, 18 Apr 2006 20:33:55 +0000 (GMT) (envelope-from gbergling@0xfce3.net) X-Envelope-From: gbergling@0xfce3.net Received: from central.0xfce3.net (dslb-088-072-033-140.pools.arcor-ip.net [88.72.33.140]) (authenticated bits=128) by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id k3IKXi0s014338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 18 Apr 2006 22:33:45 +0200 Received: from central.0xfce3.net (localhost [127.0.0.1]) by central.0xfce3.net (8.13.6/8.13.4) with ESMTP id k3IKXaBR019213; Tue, 18 Apr 2006 22:33:36 +0200 (CEST) (envelope-from gbergling@0xfce3.net) Received: (from gordon@localhost) by central.0xfce3.net (8.13.6/8.13.4/Submit) id k3IKXXN7019212; Tue, 18 Apr 2006 22:33:33 +0200 (CEST) (envelope-from gbergling@0xfce3.net) X-Authentication-Warning: central.0xfce3.net: gordon set sender to gbergling@0xfce3.net using -f Date: Tue, 18 Apr 2006 22:33:33 +0200 From: Gordon Bergling To: Eric Anderson Message-ID: <20060418203333.GA19094@central.0xfce3.net> References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> <20060418193018.GB694@turion.vk2pj.dyndns.org> <444545D3.5010405@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <444545D3.5010405@centtech.com> X-Url: X-Operating-System: FreeBSD 6.1-RC i386 X-Host-Uptime: 10:32PM up 13:36, 0 users, load averages: 0.02, 0.02, 0.00 User-Agent: Mutt/1.5.11 X-Spam-Score: * (1.426) AWL,BAYES_50,FORGED_RCVD_HELO X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8 Cc: cokane@cokane.org, freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 20:33:57 -0000 * Thus spake Eric Anderson (anderson@centtech.com): > Peter Jeremy wrote: > >On Tue, 2006-Apr-18 14:02:07 -0400, Coleman Kane wrote: > >A few comments on the shellscript: > > > >>+ rcargsize=`echo $rc_arg` > >>+ rcargsize=${#rcargsize} > > > >Try rcargsize=$((${#rc_arg} + 1)) > > > >>- return 1 > >>+ (echo_fancy "FAILED" `expr 10 + > >>$rcargsize - 1`) && return 1 > > > >Try echo_fancy "FAILED" $((10 + $rcargsize - > >1)) && return 1 > > > >>+echo_fancy () { > >... > >>+ namesize=`echo -n $name` > >>+ namesize=${#namesize} > >or namesize=${#name} > > > >>+ padding="" > >>+ paddingsize=$(($columns - 15 - $2 - $namesize)) > >>+ until [ 0 = ${paddingsize} ]; do > >>+ padding=" $padding" > >>+ paddingsize=$(($paddingsize - 1)) > >>+ done > > > >This particular block of code appears unnecessary (since $padding is > >unused). > > I must be missing something, because I'm pretty sure it's used.. What > did I miss? > > > > >>+ paddingsize=$((60 - $namesize - $rc_argsize)) > >>+ until [ 0 = ${paddingsize} ]; do > >>+ padding=" $padding" > >>+ paddingsize=$(($paddingsize - 1)) > >>+ done > > > >For safety, the conditions should probably be [ 0 -ge ${paddingsize} ] > >I don't see any alternative to the until loop. If efficiency turns out > >to be a real issue then you could try doing the expansion in multiple > >goes. Eg: > > > > until [ 8 -gt ${paddingsize} ]; do > > padding=" $padding" > > paddingsize=$(($paddingsize - 8)) > > done > > until [ 0 -ge ${paddingsize} ]; do > > padding=" $padding" > > paddingsize=$(($paddingsize - 1)) > > done > > Thanks for the hints. I was testing the same changes to the > namesize/etc as you suggested, and it does work and is more readable and > more efficient. > > I've included your suggestions and put the latest changes here: > > http://www.googlebit.com/freebsd/patches/rc_fancy.patch-3 Patch -3 is working good here. :) best regards, Gordon PS: next try... fancy_color_rc="YES" ;) -- Gordon Bergling http://www.0xFCE3.net/ PGP Fingerprint: 7732 9BB1 5013 AE8B E42C 28E0 93B9 D32B C76F 02A0 RIPE-HDL: MDTP-RIPE "Minimal Electronic Music" From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 20:35:58 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D30216A468 for ; Tue, 18 Apr 2006 20:35:58 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEA7643D58 for ; Tue, 18 Apr 2006 20:35:51 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k3IKZkCJ014006; Tue, 18 Apr 2006 15:35:46 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44454D96.3030004@centtech.com> Date: Tue, 18 Apr 2006 15:35:34 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Gordon Bergling References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> <20060418193018.GB694@turion.vk2pj.dyndns.org> <444545D3.5010405@centtech.com> <20060418203333.GA19094@central.0xfce3.net> In-Reply-To: <20060418203333.GA19094@central.0xfce3.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1405/Tue Apr 18 13:30:25 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: cokane@cokane.org, freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 20:35:58 -0000 Gordon Bergling wrote: > * Thus spake Eric Anderson (anderson@centtech.com): >> Peter Jeremy wrote: >>> On Tue, 2006-Apr-18 14:02:07 -0400, Coleman Kane wrote: >>> A few comments on the shellscript: >>> >>>> + rcargsize=`echo $rc_arg` >>>> + rcargsize=${#rcargsize} >>> Try rcargsize=$((${#rc_arg} + 1)) >>> >>>> - return 1 >>>> + (echo_fancy "FAILED" `expr 10 + >>>> $rcargsize - 1`) && return 1 >>> Try echo_fancy "FAILED" $((10 + $rcargsize - >>> 1)) && return 1 >>> >>>> +echo_fancy () { >>> ... >>>> + namesize=`echo -n $name` >>>> + namesize=${#namesize} >>> or namesize=${#name} >>> >>>> + padding="" >>>> + paddingsize=$(($columns - 15 - $2 - $namesize)) >>>> + until [ 0 = ${paddingsize} ]; do >>>> + padding=" $padding" >>>> + paddingsize=$(($paddingsize - 1)) >>>> + done >>> This particular block of code appears unnecessary (since $padding is >>> unused). >> I must be missing something, because I'm pretty sure it's used.. What >> did I miss? >> >> >> >>>> + paddingsize=$((60 - $namesize - $rc_argsize)) >>>> + until [ 0 = ${paddingsize} ]; do >>>> + padding=" $padding" >>>> + paddingsize=$(($paddingsize - 1)) >>>> + done >>> For safety, the conditions should probably be [ 0 -ge ${paddingsize} ] >>> I don't see any alternative to the until loop. If efficiency turns out >>> to be a real issue then you could try doing the expansion in multiple >>> goes. Eg: >>> >>> until [ 8 -gt ${paddingsize} ]; do >>> padding=" $padding" >>> paddingsize=$(($paddingsize - 8)) >>> done >>> until [ 0 -ge ${paddingsize} ]; do >>> padding=" $padding" >>> paddingsize=$(($paddingsize - 1)) >>> done >> Thanks for the hints. I was testing the same changes to the >> namesize/etc as you suggested, and it does work and is more readable and >> more efficient. >> >> I've included your suggestions and put the latest changes here: >> >> http://www.googlebit.com/freebsd/patches/rc_fancy.patch-3 > > Patch -3 is working good here. :) > > best regards, > > Gordon > > PS: next try... fancy_color_rc="YES" ;) If I could figure out how to make sh do colors, I'd do it. :) Thanks for testing! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 20:51:09 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35EAD16A408 for ; Tue, 18 Apr 2006 20:51:09 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77DD643D5E for ; Tue, 18 Apr 2006 20:51:06 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.4) with ESMTP id k3IL7Qtv051167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Apr 2006 17:07:32 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-hackers@freebsd.org Date: Tue, 18 Apr 2006 16:50:55 -0400 User-Agent: KMail/1.9.1 References: <444515C8.3030406@centtech.com> <20060418203333.GA19094@central.0xfce3.net> <44454D96.3030004@centtech.com> In-Reply-To: <44454D96.3030004@centtech.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart11550951.phmSzyb89C"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604181651.03040.mistry.7@osu.edu> X-Spam-Status: No, score=-5.5 required=5.0 tests=ALL_TRUSTED,BAYES_50, MYFREEBSD2 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88.1/1405/Tue Apr 18 14:30:25 2006 on mail.united-ware.com X-Virus-Status: Clean Cc: Gordon Bergling , cokane@cokane.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 20:51:09 -0000 --nextPart11550951.phmSzyb89C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 18 April 2006 16:35, Eric Anderson wrote: > Gordon Bergling wrote: > > * Thus spake Eric Anderson (anderson@centtech.com): > >> Peter Jeremy wrote: > >>> On Tue, 2006-Apr-18 14:02:07 -0400, Coleman Kane wrote: > >>> > >>> A few comments on the shellscript: > >>>> + rcargsize=3D`echo $rc_arg` > >>>> + rcargsize=3D${#rcargsize} > >>> > >>> Try rcargsize=3D$((${#rc_arg} + 1)) > >>> > >>>> - return 1 > >>>> + (echo_fancy "FAILED" `expr 10 + > >>>> $rcargsize - 1`) && return 1 > >>> > >>> Try echo_fancy "FAILED" $((10 + $rcargsize - > >>> 1)) && return 1 > >>> > >>>> +echo_fancy () { > >>> > >>> ... > >>> > >>>> + namesize=3D`echo -n $name` > >>>> + namesize=3D${#namesize} > >>> > >>> or namesize=3D${#name} > >>> > >>>> + padding=3D"" > >>>> + paddingsize=3D$(($columns - 15 - $2 - $namesize)) > >>>> + until [ 0 =3D ${paddingsize} ]; do > >>>> + padding=3D" $padding" > >>>> + paddingsize=3D$(($paddingsize - 1)) > >>>> + done > >>> > >>> This particular block of code appears unnecessary (since > >>> $padding is unused). > >> > >> I must be missing something, because I'm pretty sure it's used.. > >> What did I miss? > >> > >>>> + paddingsize=3D$((60 - $namesize - $rc_argsize)) > >>>> + until [ 0 =3D ${paddingsize} ]; do > >>>> + padding=3D" $padding" > >>>> + paddingsize=3D$(($paddingsize - 1)) > >>>> + done > >>> > >>> For safety, the conditions should probably be [ 0 -ge > >>> ${paddingsize} ] I don't see any alternative to the until loop. > >>> If efficiency turns out to be a real issue then you could try > >>> doing the expansion in multiple goes. Eg: > >>> > >>> until [ 8 -gt ${paddingsize} ]; do > >>> padding=3D" $padding" > >>> paddingsize=3D$(($paddingsize - 8)) > >>> done > >>> until [ 0 -ge ${paddingsize} ]; do > >>> padding=3D" $padding" > >>> paddingsize=3D$(($paddingsize - 1)) > >>> done > >> > >> Thanks for the hints. I was testing the same changes to the > >> namesize/etc as you suggested, and it does work and is more > >> readable and more efficient. > >> > >> I've included your suggestions and put the latest changes here: > >> > >> http://www.googlebit.com/freebsd/patches/rc_fancy.patch-3 > > > > Patch -3 is working good here. :) > > > > best regards, > > > > Gordon > > > > PS: next try... fancy_color_rc=3D"YES" ;) > > If I could figure out how to make sh do colors, I'd do it. :) Is that all? :) #!/bin/sh ############################################################ # Nico Golde Homepage: http://www.ngolde.de # Last change: Mon Feb 16 16:24:41 CET 2004 ############################################################ for attr in 0 1 4 5 7 ; do =20 echo "----------------------------------------------------------------" printf "ESC[%s;Foreground;Background - \n" $attr for fore in 30 31 32 33 34 35 36 37; do for back in 40 41 42 43 44 45 46 47; do printf '\033[%s;%s;%sm %02s;%02s ' $attr $fore $back=20 $fore $back done printf '\n' done printf '\033[0m' done =2D-=20 Anish Mistry --nextPart11550951.phmSzyb89C Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBERVE3xqA5ziudZT0RAo2UAJ95Bonq6NpYQ3Qk/KhDsNdJOS49UwCgw5z8 lnTRSCsdkFYNSVg2ySBKfDI= =TrAy -----END PGP SIGNATURE----- --nextPart11550951.phmSzyb89C-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 20:57:10 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01FD916A404 for ; Tue, 18 Apr 2006 20:57:10 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F13843D46 for ; Tue, 18 Apr 2006 20:57:09 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k3IKv3v5014909; Tue, 18 Apr 2006 15:57:03 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44455294.3030101@centtech.com> Date: Tue, 18 Apr 2006 15:56:52 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Anish Mistry References: <444515C8.3030406@centtech.com> <20060418203333.GA19094@central.0xfce3.net> <44454D96.3030004@centtech.com> <200604181651.03040.mistry.7@osu.edu> In-Reply-To: <200604181651.03040.mistry.7@osu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1405/Tue Apr 18 13:30:25 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, cokane@cokane.org, Gordon Bergling Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 20:57:10 -0000 Anish Mistry wrote: > On Tuesday 18 April 2006 16:35, Eric Anderson wrote: >> Gordon Bergling wrote: >>> * Thus spake Eric Anderson (anderson@centtech.com): >>>> Peter Jeremy wrote: >>>>> On Tue, 2006-Apr-18 14:02:07 -0400, Coleman Kane wrote: >>>>> >>>>> A few comments on the shellscript: >>>>>> + rcargsize=`echo $rc_arg` >>>>>> + rcargsize=${#rcargsize} >>>>> Try rcargsize=$((${#rc_arg} + 1)) >>>>> >>>>>> - return 1 >>>>>> + (echo_fancy "FAILED" `expr 10 + >>>>>> $rcargsize - 1`) && return 1 >>>>> Try echo_fancy "FAILED" $((10 + $rcargsize - >>>>> 1)) && return 1 >>>>> >>>>>> +echo_fancy () { >>>>> ... >>>>> >>>>>> + namesize=`echo -n $name` >>>>>> + namesize=${#namesize} >>>>> or namesize=${#name} >>>>> >>>>>> + padding="" >>>>>> + paddingsize=$(($columns - 15 - $2 - $namesize)) >>>>>> + until [ 0 = ${paddingsize} ]; do >>>>>> + padding=" $padding" >>>>>> + paddingsize=$(($paddingsize - 1)) >>>>>> + done >>>>> This particular block of code appears unnecessary (since >>>>> $padding is unused). >>>> I must be missing something, because I'm pretty sure it's used.. >>>> What did I miss? >>>> >>>>>> + paddingsize=$((60 - $namesize - $rc_argsize)) >>>>>> + until [ 0 = ${paddingsize} ]; do >>>>>> + padding=" $padding" >>>>>> + paddingsize=$(($paddingsize - 1)) >>>>>> + done >>>>> For safety, the conditions should probably be [ 0 -ge >>>>> ${paddingsize} ] I don't see any alternative to the until loop. >>>>> If efficiency turns out to be a real issue then you could try >>>>> doing the expansion in multiple goes. Eg: >>>>> >>>>> until [ 8 -gt ${paddingsize} ]; do >>>>> padding=" $padding" >>>>> paddingsize=$(($paddingsize - 8)) >>>>> done >>>>> until [ 0 -ge ${paddingsize} ]; do >>>>> padding=" $padding" >>>>> paddingsize=$(($paddingsize - 1)) >>>>> done >>>> Thanks for the hints. I was testing the same changes to the >>>> namesize/etc as you suggested, and it does work and is more >>>> readable and more efficient. >>>> >>>> I've included your suggestions and put the latest changes here: >>>> >>>> http://www.googlebit.com/freebsd/patches/rc_fancy.patch-3 >>> Patch -3 is working good here. :) >>> >>> best regards, >>> >>> Gordon >>> >>> PS: next try... fancy_color_rc="YES" ;) >> If I could figure out how to make sh do colors, I'd do it. :) > Is that all? :) > #!/bin/sh > ############################################################ > # Nico Golde Homepage: http://www.ngolde.de > # Last change: Mon Feb 16 16:24:41 CET 2004 > ############################################################ > > for attr in 0 1 4 5 7 ; do > > echo "----------------------------------------------------------------" > printf "ESC[%s;Foreground;Background - \n" $attr > for fore in 30 31 32 33 34 35 36 37; do > for back in 40 41 42 43 44 45 46 47; do > printf '\033[%s;%s;%sm %02s;%02s ' $attr $fore $back > $fore $back > done > printf '\n' > done > printf '\033[0m' > done But can you do it without the printf's? That's the key. We don't have printf until later in the boot process.. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 21:06:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3895116A404 for ; Tue, 18 Apr 2006 21:06:35 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [213.238.47.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF86443D70 for ; Tue, 18 Apr 2006 21:06:27 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from [44.128.40.11] (janus.spock.tallence.de [44.128.40.11]) (authenticated bits=0) by koef.zs64.net (8.13.6/8.13.4) with ESMTP id k3IL5wYU080440 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 18 Apr 2006 23:06:09 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <44455294.3030101@centtech.com> References: <444515C8.3030406@centtech.com> <20060418203333.GA19094@central.0xfce3.net> <44454D96.3030004@centtech.com> <200604181651.03040.mistry.7@osu.edu> <44455294.3030101@centtech.com> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Tue, 18 Apr 2006 23:06:07 +0200 To: Eric Anderson X-Mailer: Apple Mail (2.749.3) Cc: freebsd-hackers@freebsd.org, Gordon Bergling , cokane@cokane.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 21:06:35 -0000 Am 18.04.2006 um 22:56 schrieb Eric Anderson: > Anish Mistry wrote: >>> If I could figure out how to make sh do colors, I'd do it. :) >> Is that all? :) >> #!/bin/sh >> ############################################################ >> # Nico Golde Homepage: http://www.ngolde.de >> # Last change: Mon Feb 16 16:24:41 CET 2004 >> ############################################################ >> for attr in 0 1 4 5 7 ; do >> echo >> "----------------------------------------------------------------" >> printf "ESC[%s;Foreground;Background - \n" $attr >> for fore in 30 31 32 33 34 35 36 37; do >> for back in 40 41 42 43 44 45 46 47; do >> printf '\033[%s;%s;%sm %02s;%02s ' $attr $fore $back >> $fore $back >> done >> printf '\n' >> done >> printf '\033[0m' >> done > > But can you do it without the printf's? That's the key. We don't > have printf until later in the boot process.. echo -e is your friend, see sh(1). $ echo -e '\e[0;32;46m' gives green on cyan in my xterm. Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 21:11:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A82416A400 for ; Tue, 18 Apr 2006 21:11:37 +0000 (UTC) (envelope-from sthalik@tehran.lain.pl) Received: from tehran.lain.pl (tehran.lain.pl [85.221.230.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8807343D48 for ; Tue, 18 Apr 2006 21:11:36 +0000 (GMT) (envelope-from sthalik@tehran.lain.pl) Received: from sthalik by tehran.lain.pl with local (envelope-from ) id 1FVxTz-0007wa-AE for freebsd-hackers@freebsd.org; Tue, 18 Apr 2006 23:11:35 +0200 Date: Tue, 18 Apr 2006 23:11:35 +0200 From: Stanislaw Halik To: freebsd-hackers@freebsd.org Message-ID: <20060418211135.GA30492@tehran.lain.pl> Mail-Followup-To: freebsd-hackers@freebsd.org References: <444515C8.3030406@centtech.com> <20060418203333.GA19094@central.0xfce3.net> <44454D96.3030004@centtech.com> <200604181651.03040.mistry.7@osu.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline In-Reply-To: <200604181651.03040.mistry.7@osu.edu> X-PGP-Key: http://tehran.lain.pl/public.key User-Agent: Mutt/1.5.11 X-User: sthalik Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 21:11:37 -0000 --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 18, 2006, Anish Mistry wrote: > printf '\033[%s;%s;%sm %02s;%02s ' $attr $fore $back=20 however, as stated previously in this thread: `printf is /usr/bin/printf'. embedding raw ^[s in the rc script would do, is this acceptable? -- sh --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFERVYHadU+vjT62TERAntmAJ98xJjje9SghbtnoZ2+ua1UHMr7kQCfbfxo HZ0kt3ttd9jyIb0pN7r+lAI= =A1eU -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 21:41:47 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3471A16A402 for ; Tue, 18 Apr 2006 21:41:47 +0000 (UTC) (envelope-from aren.tyr@gawab.com) Received: from info3.gawab.com (info3.gawab.com [204.97.230.45]) by mx1.FreeBSD.org (Postfix) with SMTP id B93F643D46 for ; Tue, 18 Apr 2006 21:41:46 +0000 (GMT) (envelope-from aren.tyr@gawab.com) Received: (qmail 5379 invoked by uid 1004); 18 Apr 2006 21:43:33 -0000 Received: from unknown (HELO yggdrasil) (aren.tyr@gawab.com@212.225.58.238) by gawab.com with SMTP; 18 Apr 2006 21:43:33 -0000 X-Trusted: Whitelisted From: Aren Olvalde Tyr To: freebsd-hackers@freebsd.org Date: Tue, 18 Apr 2006 22:41:30 +0100 User-Agent: KMail/1.9.1 References: <444515C8.3030406@centtech.com> <20060418193018.GB694@turion.vk2pj.dyndns.org> <444545D3.5010405@centtech.com> In-Reply-To: <444545D3.5010405@centtech.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1205149.Uy3fXFqdmO"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604182241.41009.aren.tyr@gawab.com> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 21:41:47 -0000 --nextPart1205149.Uy3fXFqdmO Content-Type: multipart/mixed; boundary="Boundary-01=_K0VREns31mdFl1M" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_K0VREns31mdFl1M Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi > I've included your suggestions and put the latest changes here: > > http://www.googlebit.com/freebsd/patches/rc_fancy.patch-3 > > > Thanks for all the feedback! Keep it coming! :) Works great on my FreeBSD 6-STABLE system too. Excellent. Now, colour please!=20 :^) Aren. --Boundary-01=_K0VREns31mdFl1M-- --nextPart1205149.Uy3fXFqdmO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBERV0UoWGxb6IQ4B4RAoXNAJ44w+qnBF4vHYwjfit7liDZ4Sc1ogCdFMu8 NQkYMKws62OBrHT6/PIlyQ0= =u6hq -----END PGP SIGNATURE----- --nextPart1205149.Uy3fXFqdmO-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 21:44:30 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9600216A401 for ; Tue, 18 Apr 2006 21:44:30 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 168FB43D55 for ; Tue, 18 Apr 2006 21:44:30 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 17771 invoked by uid 399); 18 Apr 2006 21:44:29 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 18 Apr 2006 21:44:29 -0000 Message-ID: <44455DC2.9080504@FreeBSD.org> Date: Tue, 18 Apr 2006 14:44:34 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Eric Anderson References: <444515C8.3030406@centtech.com> In-Reply-To: <444515C8.3030406@centtech.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 21:44:30 -0000 While I personally am not necessarily opposed to this kind of patch, you should be aware that this idea has been proposed in the past, and roundly rejected. The consensus has been that we don't necessarily want FreeBSD to look like other OSes that do this. That said, when you have something that you're ready for a wider review on, please submit it first to freebsd-rc@, then freebsd-arch@. Doug -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 22:07:46 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7682D16A402 for ; Tue, 18 Apr 2006 22:07:46 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF86B43D55 for ; Tue, 18 Apr 2006 22:07:45 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [127.0.0.1] (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 10C1A19F2C; Tue, 18 Apr 2006 15:07:43 -0700 (PDT) Message-ID: <44456323.9070306@bitfreak.org> Date: Tue, 18 Apr 2006 15:07:31 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Eric Anderson References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> <20060418193018.GB694@turion.vk2pj.dyndns.org> <444545D3.5010405@centtech.com> <20060418203333.GA19094@central.0xfce3.net> <44454D96.3030004@centtech.com> In-Reply-To: <44454D96.3030004@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 22:07:47 -0000 Eric Anderson wrote: > > If I could figure out how to make sh do colors, I'd do it. :) Please do not use colors in rc. Escape-sequenced colors make unacceptable assumptions about the user and syslogd strips escape sequences anyway, so it would be of no use to logged consoles. Serial consoles introduce other problems with buggy escape handling in third-party terminal programs. A good text layout and descriptive status messages do far more for clarity and readability than any use of color ever can. From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 22:15:09 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8468116A400; Tue, 18 Apr 2006 22:15:09 +0000 (UTC) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (goofy.demon.nl [83.160.134.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB1DE43D45; Tue, 18 Apr 2006 22:15:08 +0000 (GMT) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (localhost [127.0.0.1]) by goofy.tols.org (8.13.4/8.13.4) with ESMTP id k3IMF57Q059252; Tue, 18 Apr 2006 22:15:05 GMT (envelope-from marco@goofy.tols.org) Received: (from marco@localhost) by goofy.tols.org (8.13.4/8.13.4/Submit) id k3IMF5Q1059251; Tue, 18 Apr 2006 22:15:05 GMT (envelope-from marco) Date: Tue, 18 Apr 2006 22:15:05 +0000 From: Marco van Tol To: freebsd-hackers@freebsd.org Message-ID: <20060418221505.GC58081@tols.org> Mail-Followup-To: freebsd-hackers@freebsd.org, John Baldwin References: <20060412215021.GB1146@tols.org> <200604141017.30635.jhb@freebsd.org> <20060415104005.GB27978@tols.org> <200604170904.58902.jhb@freebsd.org> <20060417134825.GA47043@tols.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060417134825.GA47043@tols.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.88.1/1407/Tue Apr 18 21:01:55 2006 on goofy.tols.org X-Virus-Status: Clean X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on goofy.tols.org Cc: Subject: Re: Per CPU cpu-statistics under SMP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 22:15:09 -0000 On Mon, Apr 17, 2006 at 01:48:25PM +0000, Marco van Tol wrote: > On Mon, Apr 17, 2006 at 09:04:58AM -0400, John Baldwin wrote: [...] > > I actually did it differently though to try and make it less confusing. > > I've added a kern.pcpu_time sysctl which is an array of 0..mp_maxid > > cp_time[] arrays (so (mp_maxid + 1) * CPUSTATES longs) which is just the > > per-CPU data. Userland can sum them up if it wants a composite total. > > Userland would first do a sysctl with a NULL buffer to get the required > > size (since it can vary with the number of CPUs in the system), malloc() > > a buffer, and then use the malloc'd buffer to make the requests. You > > should only have to do the malloc() at process start since FreeBSD doesn't > > currently allow for more CPUs to be added at runtime. You can try out > > the patch at http://www.FreeBSD.org/~jhb/patches/cp_time.patch > > Great thanks! > > I will try to apply the patch, and try to modify gkrellm to support it. > I'll drop them (gkrellm developers) a note that I'm doing this, as it would > be a waist of effort if somebody else has been doing preliminary work that > I'd be doing again. :) > > I'll keep you up-to-date. I'm trying to apply the patch. Tried it to both todays current and todays RELENG_6, but both have failing hunks in sys/kern/kern_clock.c. The rest succeeds. I can do two things: - Try to manually patch it against todays current. - re-checkout todays RELENG_6, and download the relevant files from the cvsweb interface from the date you posted the patch from that days CURRENT. Then try to apply the patch. For the latter it may break the kernelbuild, but I'm very tempted to try that one ahead of the manual patching attempt. ;) I'll keep you posted on how far I'm getting with this. Guess I should have gone straight to current the day you posted the patch. Sorry. Marco -- Nothing takes the past away like the future - Madonna in Nothing Really Matters From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 22:33:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24A3E16A408 for ; Tue, 18 Apr 2006 22:33:14 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id B620043D79 for ; Tue, 18 Apr 2006 22:33:02 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so819140nfc for ; Tue, 18 Apr 2006 15:33:01 -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:references; b=pnVotxWuKLepdOYkw7dDYLASSO9U7NftT05w7O2Zg7JurnhJZrHhrif6TW94siioGB/LGVd/ADf7xAeaak9IvS3su+pTRl9UW7zMFVvJVD9edSd1l4Pi6BsA6Kk6iP3MZTAhSqrLhpbnaBGYk0bWQVbUXG2KK87df/frktaLWZo= Received: by 10.49.93.4 with SMTP id v4mr3592194nfl; Tue, 18 Apr 2006 15:26:33 -0700 (PDT) Received: by 10.48.217.6 with HTTP; Tue, 18 Apr 2006 15:26:33 -0700 (PDT) Message-ID: <346a80220604181526m80f6566s72a85bd62f0f7e18@mail.gmail.com> Date: Tue, 18 Apr 2006 18:26:33 -0400 From: "Coleman Kane" To: "Darren Pilgrim" In-Reply-To: <44456323.9070306@bitfreak.org> MIME-Version: 1.0 References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> <20060418193018.GB694@turion.vk2pj.dyndns.org> <444545D3.5010405@centtech.com> <20060418203333.GA19094@central.0xfce3.net> <44454D96.3030004@centtech.com> <44456323.9070306@bitfreak.org> 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: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 22:33:14 -0000 On 4/18/06, Darren Pilgrim wrote: > > Eric Anderson wrote: > > > > If I could figure out how to make sh do colors, I'd do it. :) > > Please do not use colors in rc. Escape-sequenced colors make unacceptabl= e > assumptions about the user and syslogd strips escape sequences anyway, so > it > would be of no use to logged consoles. Serial consoles introduce other > problems with buggy escape handling in third-party terminal programs. A > good text layout and descriptive status messages do far more for clarity > and > readability than any use of color ever can. I understand your concerns regarding the "pollution" of rc messages with excess baggage such as ANSI-color sequences and attributes. The patches hav= e been set up in such a way as to provide the "fancy" capability only on demand, and the "fancy w/ color" only as another toggle. I think that havin= g a more defined status interface would be very beneficial (and using colors and other attributes supported by advanced terminal types seems to be what people would like). For instance, right now we just have the name of the service printed if it is started, otherwise an ugly (in my eyes) dump of its stderr is displayed on-screen. If we instead defined an API that defined a "Service Name" "Service Description" "Service Status" and "Error Code" then we could have = a more manageable service structure (IMHO). I think this work toward making the service status messages prettier CAN ONLY BE GOOD. Even if "pretty colors" are deemed "too fancy" by the freebsd gods in the end. As for your "buggy escape handling" of third-party terminals: 1) Don't enable the feature and it won't be a problem, or 2) Don't use crappy third-party terminal software that will die when it recieves ^[[0;31;40m rather than setting the attributes to NormalText-Red-on-Black. In fact, I haven't heard of one for some time. -- Coleman Kane From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 22:39:05 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CADA16A400 for ; Tue, 18 Apr 2006 22:39:05 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C4CF43D53 for ; Tue, 18 Apr 2006 22:39:04 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so819950nfc for ; Tue, 18 Apr 2006 15:39:03 -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:references; b=Cra/JvkCDu3vBvOTbN+biHq2gbzPCAeGykwjnXdfM3i2R93dXZvAVyncsW35pmevQIrA/RlamixG8v76oW1M3D2p28l8Ntap/SxQQEgNRaofBRBQgc7Kv9u3F3RgbAMJn1SayRuJzFfYk27+WkK/4gyWiGESbkiDgVj5DXOyaLU= Received: by 10.48.223.3 with SMTP id v3mr22129nfg; Tue, 18 Apr 2006 15:10:04 -0700 (PDT) Received: by 10.48.217.6 with HTTP; Tue, 18 Apr 2006 15:10:04 -0700 (PDT) Message-ID: <346a80220604181510i10c82020s633816faec8ad3e1@mail.gmail.com> Date: Tue, 18 Apr 2006 18:10:04 -0400 From: "Coleman Kane" To: "Doug Barton" In-Reply-To: <44455DC2.9080504@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_24891_26292795.1145398204205" References: <444515C8.3030406@centtech.com> <44455DC2.9080504@FreeBSD.org> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 22:39:05 -0000 ------=_Part_24891_26292795.1145398204205 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 4/18/06, Doug Barton wrote: > > While I personally am not necessarily opposed to this kind of patch, you > should be aware that this idea has been proposed in the past, and roundly > rejected. The consensus has been that we don't necessarily want FreeBSD t= o > look like other OSes that do this. I remember a time back when the idea of an /etc/rc.d/ was taboo to bring up.... hopefully times are better now! That said, when you have something that you're ready for a wider review on, > please submit it first to freebsd-rc@, then freebsd-arch@. > > Doug > > -- > > This .signature sanitized for your protection > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > You want colors?!? You can have them! (attached) --- Coleman Kane ------=_Part_24891_26292795.1145398204205 Content-Type: text/x-patch; name=rc_fancy-cokane-colors.patch; charset=us-ascii Content-Transfer-Encoding: 7bit X-Attachment-Id: f_em6shyg9 Content-Disposition: attachment; filename="rc_fancy-cokane-colors.patch" --- rc.subr.orig Tue Apr 18 18:06:20 2006 +++ rc.subr Tue Apr 18 18:09:24 2006 @@ -313,12 +313,16 @@ break fi _list=$_nlist - echo -n ${_prefix:-"Waiting for PIDS: "}$_list + if ! checkyesno rc_fancy; then + echo -n ${_prefix:-"Waiting for PIDS: "}$_list + fi _prefix=", " sleep 2 done if [ -n "$_prefix" ]; then - echo "." + if ! checkyesno rc_fancy; then + echo "." + fi fi } @@ -564,12 +568,14 @@ # if the precmd failed and force # isn't set, exit # + rcargsize=`echo $rc_arg` + rcargsize=${#rcargsize} if [ -n "$_precmd" ]; then debug "run_rc_command: evaluating ${_precmd}()." eval $_precmd $rc_extra_args _return=$? [ $_return -ne 0 ] && [ -z "$rc_force" ] && - return 1 + (echo_fancy "FAILED" `expr 10 + $rcargsize - 1`) && return 1 fi if [ -n "$_cmd" ]; then @@ -577,7 +583,7 @@ eval $_cmd $rc_extra_args _return=$? [ $_return -ne 0 ] && [ -z "$rc_force" ] && - return 1 + (echo_fancy "FAILED" `expr 10 + $rcargsize - 1`) && return 1 fi if [ -n "$_postcmd" ]; then @@ -585,6 +591,7 @@ eval $_postcmd $rc_extra_args _return=$? fi + echo_fancy " OK " 0 return $_return fi @@ -600,13 +607,16 @@ ;; start) + echo -n "Starting ${name}" if [ -z "$rc_fast" -a -n "$rc_pid" ]; then + echo_fancy " SKIP " 9 echo 1>&2 "${name} already running? (pid=$rc_pid)." return 1 fi if [ ! -x ${_chroot}${command} ]; then info "run_rc_command: cannot run ($command)." + echo_fancy "ERROR " 9 return 1 fi @@ -617,6 +627,7 @@ if ! checkyesno $_f; then warn "\$${_f} is not enabled." if [ -z "$rc_force" ]; then + echo_fancy "ERROR " 9 return 1 fi fi @@ -625,6 +636,7 @@ if [ ! -d "${_f}/." ]; then warn "${_f} is not a directory." if [ -z "$rc_force" ]; then + echo_fancy "ERROR " 9 return 1 fi fi @@ -633,6 +645,7 @@ if [ ! -r "${_f}" ]; then warn "${_f} is not readable." if [ -z "$rc_force" ]; then + echo_fancy "ERROR " 9 return 1 fi fi @@ -646,12 +659,11 @@ eval $_precmd _return=$? [ $_return -ne 0 ] && [ -z "$rc_force" ] && - return 1 + (echo_fancy "ERROR " 9) && return 1 fi # setup the command to run, and run it # - echo "Starting ${name}." if [ -n "$_chroot" ]; then _doit="\ ${_nice:+nice -n $_nice }\ @@ -673,7 +685,7 @@ debug "run_rc_command: _doit: $_doit" eval $_doit _return=$? - [ $_return -ne 0 ] && [ -z "$rc_force" ] && return 1 + [ $_return -ne 0 ] && [ -z "$rc_force" ] && (echo_fancy "FAILED" 9) && return 1 # finally, run postcmd # @@ -681,15 +693,19 @@ debug "run_rc_command: evaluating ${_postcmd}()." eval $_postcmd fi + echo_fancy " OK " 9 ;; stop) + echo -n "Stopping ${name}" if [ -z "$rc_pid" ]; then [ -n "$rc_fast" ] && return 0 if [ -n "$pidfile" ]; then + echo_fancy " SKIP " 9 echo 1>&2 \ "${name} not running? (check $pidfile)." else + echo_fancy " SKIP " 9 echo 1>&2 "${name} not running?" fi return 1 @@ -702,12 +718,11 @@ eval $_precmd _return=$? [ $_return -ne 0 ] && [ -z "$rc_force" ] && - return 1 + (echo_fancy "ERROR " 9) && return 1 fi # send the signal to stop # - echo "Stopping ${name}." _doit="kill -${sig_stop:-TERM} $rc_pid" if [ -n "$_user" ]; then _doit="su -m $_user -c 'sh -c \"$_doit\"'" @@ -718,7 +733,7 @@ # eval $_doit _return=$? - [ $_return -ne 0 ] && [ -z "$rc_force" ] && return 1 + [ $_return -ne 0 ] && [ -z "$rc_force" ] && (echo_fancy "FAILED" 9) && return 1 # wait for the command to exit, # and run postcmd. @@ -727,24 +742,27 @@ eval $_postcmd _return=$? fi + echo_fancy " OK " 9 ;; reload) + echo -n "Reloading ${name} config files" if [ -z "$rc_pid" ]; then if [ -n "$pidfile" ]; then + echo_fancy "SKIPPED" 23 echo 1>&2 \ "${name} not running? (check $pidfile)." else + echo_fancy "SKIPPED" 23 echo 1>&2 "${name} not running?" fi return 1 fi - echo "Reloading ${name} config files." if [ -n "$_precmd" ]; then eval $_precmd _return=$? [ $_return -ne 0 ] && [ -z "$rc_force" ] && - return 1 + (echo_fancy "FAILED" 23) && return 1 fi _doit="kill -${sig_reload:-HUP} $rc_pid" if [ -n "$_user" ]; then @@ -752,11 +770,12 @@ fi eval $_doit _return=$? - [ $_return -ne 0 ] && [ -z "$rc_force" ] && return 1 + [ $_return -ne 0 ] && [ -z "$rc_force" ] && (echo_fancy "FAILED" 23) && return 1 if [ -n "$_postcmd" ]; then eval $_postcmd _return=$? fi + echo_fancy " OK " 23 ;; restart) @@ -1428,3 +1447,47 @@ } fi + +echo_fancy () { + columns=80 + label=$1 + labelprefix="" + labelsuffix="" + if [ x$rc_fancy_color = "xYES" ]; then + labelsuffix="\e[0m" + case $label in + *OK*) + labelprefix="\e[1;32;40m" + ;; + *FAILED*|*ERROR*) + labelprefix="\e[1;31;40m" + ;; + *SKIP*) + labelprefix="\e[1;33;40m" + ;; + esac + fi + namesize=${#name} + rc_argsize=${#rc_arg} + padding="" + paddingsize=$(($columns - 15 - $2 - $namesize)) + until [ 0 = ${paddingsize} ]; do + padding=" $padding" + paddingsize=$(($paddingsize - 1)) + done + if checkyesno rc_fancy; then + if [ $2 = 0 ]; then + padding="" + paddingsize=$((60 - $namesize - $rc_argsize)) + until [ 0 = ${paddingsize} ]; do + padding=" $padding" + paddingsize=$(($paddingsize - 1)) + done + echo -e "\rRunning ${rc_arg} $name $padding [${labelprefix}${label}${labelsuffix}]" + else + echo -e " ... $padding [$labelprefix$label$labelsuffix]" + fi + else + echo "." + fi +} ------=_Part_24891_26292795.1145398204205-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 18 22:39:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D87A016A405 for ; Tue, 18 Apr 2006 22:39:49 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 141EA43D62 for ; Tue, 18 Apr 2006 22:39:44 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3IMdhcG097587; Tue, 18 Apr 2006 18:39:44 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Marco van Tol Date: Tue, 18 Apr 2006 18:38:26 -0400 User-Agent: KMail/1.9.1 References: <20060412215021.GB1146@tols.org> <20060417134825.GA47043@tols.org> <20060418221505.GC58081@tols.org> In-Reply-To: <20060418221505.GC58081@tols.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604181838.27713.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1407/Tue Apr 18 17:01:55 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-hackers@freebsd.org Subject: Re: Per CPU cpu-statistics under SMP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 22:39:49 -0000 On Tuesday 18 April 2006 18:15, Marco van Tol wrote: > On Mon, Apr 17, 2006 at 01:48:25PM +0000, Marco van Tol wrote: > > On Mon, Apr 17, 2006 at 09:04:58AM -0400, John Baldwin wrote: > > [...] > > > > I actually did it differently though to try and make it less confusing. > > > I've added a kern.pcpu_time sysctl which is an array of 0..mp_maxid > > > cp_time[] arrays (so (mp_maxid + 1) * CPUSTATES longs) which is just the > > > per-CPU data. Userland can sum them up if it wants a composite total. > > > Userland would first do a sysctl with a NULL buffer to get the required > > > size (since it can vary with the number of CPUs in the system), malloc() > > > a buffer, and then use the malloc'd buffer to make the requests. You > > > should only have to do the malloc() at process start since FreeBSD doesn't > > > currently allow for more CPUs to be added at runtime. You can try out > > > the patch at http://www.FreeBSD.org/~jhb/patches/cp_time.patch > > > > Great thanks! > > > > I will try to apply the patch, and try to modify gkrellm to support it. > > I'll drop them (gkrellm developers) a note that I'm doing this, as it would > > be a waist of effort if somebody else has been doing preliminary work that > > I'd be doing again. :) > > > > I'll keep you up-to-date. > > I'm trying to apply the patch. Tried it to both todays current and todays > RELENG_6, but both have failing hunks in sys/kern/kern_clock.c. > The rest succeeds. > > I can do two things: > - Try to manually patch it against todays current. > - re-checkout todays RELENG_6, and download the relevant files from the > cvsweb interface from the date you posted the patch from that days > CURRENT. Then try to apply the patch. > > For the latter it may break the kernelbuild, but I'm very tempted to try > that one ahead of the manual patching attempt. ;) > > I'll keep you posted on how far I'm getting with this. Guess I should have > gone straight to current the day you posted the patch. Sorry. Ah, hmm. On 6.x we don't have per-thread stat ticks yet, which is probably why it is failing. It also isn't safe to move sched_lock down either on 6.x. You can still apply the rest of the patch by hand, just leave the 'mtx_lock_spin(&sched_lock)' where it is and change all the 'cp_time[FOO]++' to 'PCPU_LAZY_INC(cp_time[FOO])'. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 03:43:11 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5865516A403 for ; Wed, 19 Apr 2006 03:43:11 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C735443D49 for ; Wed, 19 Apr 2006 03:43:10 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id D6C4E46B0C; Tue, 18 Apr 2006 23:43:09 -0400 (EDT) Date: Wed, 19 Apr 2006 04:43:09 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: cokane@cokane.org In-Reply-To: <346a80220604181526m80f6566s72a85bd62f0f7e18@mail.gmail.com> Message-ID: <20060419043726.F40377@fledge.watson.org> References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> <20060418193018.GB694@turion.vk2pj.dyndns.org> <444545D3.5010405@centtech.com> <20060418203333.GA19094@central.0xfce3.net> <44454D96.3030004@centtech.com> <44456323.9070306@bitfreak.org> <346a80220604181526m80f6566s72a85bd62f0f7e18@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Darren Pilgrim , freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 03:43:11 -0000 On Tue, 18 Apr 2006, Coleman Kane wrote: > I understand your concerns regarding the "pollution" of rc messages with > excess baggage such as ANSI-color sequences and attributes. The patches have > been set up in such a way as to provide the "fancy" capability only on > demand, and the "fancy w/ color" only as another toggle. I think that having > a more defined status interface would be very beneficial (and using colors > and other attributes supported by advanced terminal types seems to be what > people would like). > > For instance, right now we just have the name of the service printed if it > is started, otherwise an ugly (in my eyes) dump of its stderr is displayed > on-screen. If we instead defined an API that defined a "Service Name" > "Service Description" "Service Status" and "Error Code" then we could have a > more manageable service structure (IMHO). I think this work toward making > the service status messages prettier CAN ONLY BE GOOD. Even if "pretty > colors" are deemed "too fancy" by the freebsd gods in the end. > > As for your "buggy escape handling" of third-party terminals: 1) Don't > enable the feature and it won't be a problem, or 2) Don't use crappy > third-party terminal software that will die when it recieves ^[[0;31;40m > rather than setting the attributes to NormalText-Red-on-Black. In fact, I > haven't heard of one for some time. If adding color, please... (1) Confirm that the results "just work" with /var/log/console.log turned on. (2) Confirm that the results "just work" with dmesg -a. It has always struck me that what we have right now is the easiest to implement model for logging service startup, but the least useful from the perspective of consumers: we have script output that varies by application, component, etc. It would be nice to have either, and possibly both, of consistently user friendly output, or entirely machine-parseable content that could be used to generate user friendly output. I've wondered for a while if it wouldn't be useful to consider having a flag in syslogd to indicate that syslog should store log entries in the target logfile in binary format, so that log messages could be reviewed, sorted, searched, etc, by facility, criticality, source process, etc... Robert N M Watson From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 04:07:06 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3878016A400 for ; Wed, 19 Apr 2006 04:07:06 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05D5C43D45 for ; Wed, 19 Apr 2006 04:07:04 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id l8so1115643nzf for ; Tue, 18 Apr 2006 21:07:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=NWJg0j97FP9HeevvZVpF1A3SUaqHo/VkZqPfrcR2eMZ3mL8Qtpf2MSdBFyKMCBz+3C24AqaSz5fvCZKA8L2DGfmglZtF39wapQSRZYxqP1D0yWF3hmZdS4wx6wmnhdjbzEWdTF5ffhRhrw+cToW0OyN3AoYGFGhAPTLgLKGeYSE= Received: by 10.36.224.27 with SMTP id w27mr1543882nzg; Tue, 18 Apr 2006 21:07:04 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id c12sm921093nzc.2006.04.18.21.07.02; Tue, 18 Apr 2006 21:07:04 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k3J47Q8U010809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Apr 2006 13:07:27 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k3J47P9F010808; Wed, 19 Apr 2006 13:07:25 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 19 Apr 2006 13:07:25 +0900 From: Pyun YongHyeon To: Andreas Bachmann Message-ID: <20060419040725.GA9899@cdnetworks.co.kr> References: <1145184791.25345.10.camel@localhost> <20060416120208.D4092@antec.home> <1145217454.25345.36.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1145217454.25345.36.camel@localhost> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, Mikko Ty?l?j?rvi , freebsd-hardware@freebsd.org Subject: Re: Broadcom 440x on FreeBSD 6.0/6.1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 04:07:06 -0000 On Sun, Apr 16, 2006 at 09:57:34PM +0200, Andreas Bachmann wrote: > > The bfe driver is broken for RAM sizes above 1G, and you have 2G. > > > > For kicks, you could try booting with hw.physmem="1G" (in loader.conf > > or manually). If that doesn't work, you have discovered a new bug. > > > > The ndis driver works on my H^HDell notebook (see ndisgen(8)). > I found your post to freebsd-mobile with the same text :-) > After limiting my physical memory, my NIC works now... > I will look at the ndisgen. > It seems that BCM440x has DMA address limit at 1GB. How about this? Index: if_bfe.c =================================================================== RCS file: /pool/ncvs/src/sys/dev/bfe/if_bfe.c,v retrieving revision 1.32 diff -u -r1.32 if_bfe.c --- if_bfe.c 4 Apr 2006 22:30:12 -0000 1.32 +++ if_bfe.c 19 Apr 2006 04:01:47 -0000 @@ -200,7 +200,7 @@ /* parent tag */ error = bus_dma_tag_create(NULL, /* parent */ PAGE_SIZE, 0, /* alignment, boundary */ - BUS_SPACE_MAXADDR, /* lowaddr */ + 0x3fffffff, /* lowaddr */ BUS_SPACE_MAXADDR_32BIT, /* highaddr */ NULL, NULL, /* filter, filterarg */ MAXBSIZE, /* maxsize */ -- Regards, Pyun YongHyeon From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 06:00:19 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52CAF16A402 for ; Wed, 19 Apr 2006 06:00:19 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from mail.asahi-net.or.jp (mail1.asahi-net.or.jp [202.224.39.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD99843D48 for ; Wed, 19 Apr 2006 06:00:18 +0000 (GMT) (envelope-from ota@j.email.ne.jp) Received: from dynabook-freebsd.advok.com (pool-151-197-120-136.phil.east.verizon.net [151.197.120.136]) by mail.asahi-net.or.jp (Postfix) with ESMTP id 09C8F2AD61 for ; Wed, 19 Apr 2006 15:00:16 +0900 (JST) Date: Wed, 19 Apr 2006 02:00:15 -0500 From: Yoshihiro Ota To: freebsd-hackers@freebsd.org Message-Id: <20060419020015.d3e23e5b.ota@j.email.ne.jp> X-Mailer: Sylpheed version 2.2.3 (GTK+ 2.8.16; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [patch] mkuzip to compress without stat.st_size X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 06:00:19 -0000 mkuzip and GEOM_UZIP has been quite useful to store files I change rarely myself such as /usr/src and /usr/ports. I now keep 6.1-RC1-src.uzip, 6.1-BETA4-src.zip and so on. If all of these were extracted, I would run out of i-nodes. One problem with mkuzip is it can only handle regular files but not devices or though pipe. The solution suggested here is for user to provide alternative size of the input. If st_size is available from stat.2, this patch uses it. However, if not available, it uses the user supplied size. The size of input is important in cloop format because it needs to store index entries to each block at the begging of file. As a result, if you don't know the size of a file, you cannot pre-allocate the space for this index. When EOF is reached, it creates and writes one compressed block whose contents are all 0's. All remaining indexes point to the block. Therefore, the cost of extra block is rather small. (user-size - actual-input-size)/block-size x 64bit-index-size + compressed-0'ed-block Futher enhancement to this patch is to use lseek(SEEK_END) to get the actual size when possible. I am not fully sure if I picked up the appropreate type for sizes; if someone can check them, it will be nice. I hope other people find this useful. I found other people had the same issue on this list a couple years ago although I couldn't find the e-mails again. Regards, Hiro --- mkuzip.c.orig Sat Apr 15 17:10:12 2006 +++ mkuzip.c Tue Apr 18 06:14:53 2006 @@ -24,6 +24,7 @@ #include #include #include +#include #define CLSTSIZE 16384 #define DEFAULT_SUFX ".uzip" @@ -33,6 +34,7 @@ "m=geom_uzip\n(kldstat -m $m 2>&-||kldload $m)>&-&&" "mount_cd9660 /dev/`mdconfig -af $0`.uzip $1\nexit $?\n"; +static uint32_t get_size(char *); static char *readblock(int, char *, u_int32_t); static void usage(void); static void *safe_malloc(size_t); @@ -43,12 +45,16 @@ int main(int argc, char **argv) { char *iname, *oname, *obuf, *ibuf; + char *p; uint64_t *toc; - int fdr, fdw, i, opt, verbose, tmp; + int fdr, fdw, opt, verbose, tmp; struct iovec iov[2]; - struct stat sb; uLongf destlen; uint64_t offset; + off_t i; + off_t *inputsz; /* we try file size first; otherwise user supplied */ + off_t filesz; /* file size */ + off_t usersz; /* user supplied size */ struct cloop_header { char magic[CLOOP_MAGIC_LEN]; /* cloop magic */ uint32_t blksz; /* block size */ @@ -61,7 +67,7 @@ oname = NULL; verbose = 0; - while((opt = getopt(argc, argv, "o:s:v")) != -1) { + while((opt = getopt(argc, argv, "o:s:S:v")) != -1) { switch(opt) { case 'o': oname = optarg; @@ -86,6 +92,27 @@ hdr.blksz = tmp; break; + case 'S': + usersz = (off_t)strtoumax(optarg, &p, 0); + if(p == NULL || *p == '\0') + break; + switch(*p) + { + case 't': case 'T': + usersz <<= 10; + case 'g': case 'G': + usersz <<= 10; + case 'm': case 'M': + usersz <<= 10; + case 'k': case 'K': + usersz <<= 10; + case 'b': case 'B': + break; + default: + err(1, "Unknown suffix on -S argument"); + } + break; + case 'v': verbose = 1; break; @@ -122,12 +149,21 @@ signal(SIGXFSZ, exit); atexit(cleanup); - if (stat(iname, &sb) != 0) { - err(1, "%s", iname); + + filesz = get_size(iname); + if(filesz > 0) + inputsz = &filesz; + else + inputsz = &usersz; + + if(*inputsz < 0) { + err(1, "input file size is not avaiable;\n" + "try -S input_size option with large enough size"); /* Not reached */ } - hdr.nblocks = sb.st_size / hdr.blksz; - if ((sb.st_size % hdr.blksz) != 0) { + + hdr.nblocks = *inputsz / hdr.blksz; + if ((*inputsz % hdr.blksz) != 0) { if (verbose != 0) fprintf(stderr, "file size is not multiple " "of %d, padding data\n", hdr.blksz); @@ -160,21 +196,23 @@ if (verbose != 0) fprintf(stderr, "data size %ju bytes, number of clusters " - "%u, index length %zu bytes\n", sb.st_size, + "%u, index length %zu bytes\n", *inputsz, hdr.nblocks, iov[1].iov_len); - for(i = 0; i == 0 || ibuf != NULL; i++) { - ibuf = readblock(fdr, ibuf, hdr.blksz); - if (ibuf != NULL) { - destlen = compressBound(hdr.blksz); - if (compress2(obuf, &destlen, ibuf, hdr.blksz, - Z_BEST_COMPRESSION) != Z_OK) { - errx(1, "can't compress data: compress2() " - "failed"); + for(i = 0; i <= hdr.nblocks; i++) { + p = readblock(fdr, ibuf, hdr.blksz); + + /* compress 0'ed data even if no data is read */ + destlen = compressBound(hdr.blksz); + if (compress2(obuf, &destlen, ibuf, hdr.blksz, + Z_BEST_COMPRESSION) != Z_OK) { + errx(1, "can't compress data: compress2() failed"); /* Not reached */ - } + } + + if (p != NULL) { if (verbose != 0) - fprintf(stderr, "cluster #%d, in %u bytes, " + fprintf(stderr, "cluster #%ju, in %u bytes, " "out %lu bytes\n", i, hdr.blksz, destlen); } else { destlen = DEV_BSIZE - (offset % DEV_BSIZE); @@ -189,14 +227,27 @@ /* Not reached */ } toc[i] = htobe64(offset); + if(p == NULL) { + /* -S size was too large; the rest points to zero filled block */ + for(; i <= hdr.nblocks; i++) + toc[i] = htobe64(offset); + break; + } offset += destlen; } + if(p != NULL && i > hdr.nblocks) { /* check if we can read more */ + if(readblock(fdr, ibuf, hdr.blksz) != NULL) { + /* file has grown or -S was too smal */ + err(1, "uziped file was not large enought"); + /* Not reached */ + } + } close(fdr); if (verbose != 0) fprintf(stderr, "compressed data to %ju bytes, saved %lld " - "bytes, %.2f%% decrease.\n", offset, (long long)(sb.st_size - offset), - 100.0 * (long long)(sb.st_size - offset) / (float)sb.st_size); + "bytes, %.2f%% decrease.\n", offset, (long long)(*inputsz - offset), + 100.0 * (long long)(*inputsz - offset) / (float)*inputsz); /* Convert to big endian */ hdr.blksz = htonl(hdr.blksz); @@ -213,6 +264,20 @@ exit(0); } +static uint32_t +get_size(char *filename) +{ + struct stat sb; + if (stat(filename, &sb) != 0) { + err(1, "%s", filename); + /* Not reached */ + } + if(sb.st_size > 0) /* we got the actual size */ + return sb.st_size; + + return 0; +} + static char * readblock(int fd, char *ibuf, u_int32_t clstsize) { @@ -234,7 +299,9 @@ usage(void) { - fprintf(stderr, "usage: mkuzip [-v] [-o outfile] [-s cluster_size] infile\n"); + fprintf(stderr, + "usage: mkuzip [-v] [-o outfile] " + "[-s cluster_size] [-S input_size] infile\n"); exit(1); } From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 07:26:30 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB4CC16A48C; Wed, 19 Apr 2006 07:26:30 +0000 (UTC) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (goofy.demon.nl [83.160.134.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB96A43D69; Wed, 19 Apr 2006 07:26:29 +0000 (GMT) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (localhost [127.0.0.1]) by goofy.tols.org (8.13.4/8.13.4) with ESMTP id k3J7QRAu066065; Wed, 19 Apr 2006 07:26:27 GMT (envelope-from marco@goofy.tols.org) Received: (from marco@localhost) by goofy.tols.org (8.13.4/8.13.4/Submit) id k3J7QRD0066064; Wed, 19 Apr 2006 07:26:27 GMT (envelope-from marco) Date: Wed, 19 Apr 2006 07:26:27 +0000 From: Marco van Tol To: John Baldwin Message-ID: <20060419072627.GA66012@tols.org> Mail-Followup-To: John Baldwin , freebsd-hackers@freebsd.org References: <20060412215021.GB1146@tols.org> <20060417134825.GA47043@tols.org> <20060418221505.GC58081@tols.org> <200604181838.27713.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604181838.27713.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.88.1/1407/Tue Apr 18 21:01:55 2006 on goofy.tols.org X-Virus-Status: Clean X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on goofy.tols.org Cc: freebsd-hackers@freebsd.org Subject: Re: Per CPU cpu-statistics under SMP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 07:26:31 -0000 On Tue, Apr 18, 2006 at 06:38:26PM -0400, John Baldwin wrote: > On Tuesday 18 April 2006 18:15, Marco van Tol wrote: [...] > > I'm trying to apply the patch. Tried it to both todays current and todays > > RELENG_6, but both have failing hunks in sys/kern/kern_clock.c. > > The rest succeeds. > > > > I can do two things: > > - Try to manually patch it against todays current. > > - re-checkout todays RELENG_6, and download the relevant files from the > > cvsweb interface from the date you posted the patch from that days > > CURRENT. Then try to apply the patch. > > > > For the latter it may break the kernelbuild, but I'm very tempted to try > > that one ahead of the manual patching attempt. ;) > > > > I'll keep you posted on how far I'm getting with this. Guess I should have > > gone straight to current the day you posted the patch. Sorry. > > Ah, hmm. On 6.x we don't have per-thread stat ticks yet, which is > probably why it is failing. It also isn't safe to move sched_lock > down either on 6.x. You can still apply the rest of the patch by > hand, just leave the 'mtx_lock_spin(&sched_lock)' where it is and > change all the 'cp_time[FOO]++' to 'PCPU_LAZY_INC(cp_time[FOO])'. OK, thanks. What I will do is replace my gentoo partition with a BSD current partition so I don't loose my workstation as it were, and use that to work on this. Will let you know how that goes. Thanks. Marco -- Als de redding het hoogst is, is de nood nabij! From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 07:44:28 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 571D416A401 for ; Wed, 19 Apr 2006 07:44:28 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail24.syd.optusnet.com.au (mail24.syd.optusnet.com.au [211.29.133.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88EDB43D45 for ; Wed, 19 Apr 2006 07:44:27 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail24.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k3J7iCXP012713 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Apr 2006 17:44:22 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k3J7iCMJ000829; Wed, 19 Apr 2006 17:44:12 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k3J7iBa7000828; Wed, 19 Apr 2006 17:44:12 +1000 (EST) (envelope-from peter) Date: Wed, 19 Apr 2006 17:44:11 +1000 From: Peter Jeremy To: cokane@cokane.org Message-ID: <20060419074411.GA704@turion.vk2pj.dyndns.org> References: <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> <20060418193018.GB694@turion.vk2pj.dyndns.org> <444545D3.5010405@centtech.com> <20060418203333.GA19094@central.0xfce3.net> <44454D96.3030004@centtech.com> <44456323.9070306@bitfreak.org> <346a80220604181526m80f6566s72a85bd62f0f7e18@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <346a80220604181526m80f6566s72a85bd62f0f7e18@mail.gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 07:44:28 -0000 On Tue, 2006-Apr-18 18:26:33 -0400, Coleman Kane wrote: >As for your "buggy escape handling" of third-party terminals: 1) Don't >enable the feature and it won't be a problem, or 2) Don't use crappy >third-party terminal software that will die when it recieves ^[[0;31;40m >rather than setting the attributes to NormalText-Red-on-Black. In fact, I >haven't heard of one for some time. I have a number of genuine DEC VT510 terminals that I could probably give away to anyone who wants to disprove this :-) -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 07:57:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0364816A402 for ; Wed, 19 Apr 2006 07:57:38 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail12.syd.optusnet.com.au (mail12.syd.optusnet.com.au [211.29.132.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id E473B43D5D for ; Wed, 19 Apr 2006 07:57:32 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail12.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k3J7vNCF010885 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 19 Apr 2006 17:57:24 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k3J7vNko000884; Wed, 19 Apr 2006 17:57:23 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k3J7vLlD000883; Wed, 19 Apr 2006 17:57:22 +1000 (EST) (envelope-from peter) Date: Wed, 19 Apr 2006 17:57:21 +1000 From: Peter Jeremy To: Eric Anderson Message-ID: <20060419075721.GB704@turion.vk2pj.dyndns.org> References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> <20060418193018.GB694@turion.vk2pj.dyndns.org> <444545D3.5010405@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <444545D3.5010405@centtech.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org, cokane@cokane.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 07:57:38 -0000 On Tue, 2006-Apr-18 15:02:27 -0500, Eric Anderson wrote: >Peter Jeremy wrote: >>>+ padding="" >>>+ paddingsize=$(($columns - 15 - $2 - $namesize)) >>>+ until [ 0 = ${paddingsize} ]; do >>>+ padding=" $padding" >>>+ paddingsize=$(($paddingsize - 1)) >>>+ done >> >>This particular block of code appears unnecessary (since $padding is >>unused). > >I must be missing something, because I'm pretty sure it's used.. What >did I miss? Actually, I had a closer look and I was wrong, sorry. I missed the '[ $2 = 0 ]' test. The code might be more legible (and is definitely more efficient) if the above code was moved into the else clause for that test. Also '[ $2 = 0 ]' should probably be written as '[ "0$2" -eq 0 ]', or similar, so that it doesn't blow up if there is no $2. -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 09:52:16 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09A3916A400 for ; Wed, 19 Apr 2006 09:52:16 +0000 (UTC) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5470A43D45 for ; Wed, 19 Apr 2006 09:52:15 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.13.6/8.13.1) with ESMTP id k3J9qCHH021726 for ; Wed, 19 Apr 2006 05:52:13 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.13.6/8.13.1/Submit) id k3J9q7Ph021725 for freebsd-hackers@freebsd.org; Wed, 19 Apr 2006 05:52:07 -0400 (EDT) (envelope-from bv) Date: Wed, 19 Apr 2006 05:52:07 -0400 From: Bill Vermillion To: freebsd-hackers@freebsd.org Message-ID: <20060419095207.GC19339@wjv.com> References: <20060419040716.4F26116A45F@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060419040716.4F26116A45F@hub.freebsd.org> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on bilver.wjv.com Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 09:52:16 -0000 Somewhere around Wed, Apr 19, 2006 at 04:07 , the world stopped and listened as freebsd-hackers-request@freebsd.org graced us with this profound tidbit of wisdom that would fulfill the enjoyment of future generations: > Message: 20 > Date: Tue, 18 Apr 2006 15:07:31 -0700 > From: Darren Pilgrim > Eric Anderson wrote: > > If I could figure out how to make sh do colors, I'd do it. :) > Please do not use colors in rc. Escape-sequenced colors make > unacceptable assumptions about the user and syslogd strips > escape sequences anyway, so it would be of no use to logged > consoles. Serial consoles introduce other problems with buggy > escape handling in third-party terminal programs. A good text > layout and descriptive status messages do far more for clarity > and readability than any use of color ever can. Let me add to that. About 10% of the male population has some color vision problem. Mine is a bit more than others. Everytime I get called to work on a Linux system, I have to go in and disable the colors as the reds and other colors become very hard to see against a dark background. The problem is the luminance value of colors such a red is quite low compared to others. That's one of the reasons why fire-trucks in this area are lime-green, as red trucks disappear into the blackness at night. If you add color make sure it is a user selectable option and not turned on by default. IMO everything you need to admin a system needs to be able to run on something as lowly as a pure serial terminal as the above poster notes. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 12:24:58 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11D5716A401 for ; Wed, 19 Apr 2006 12:24:58 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8126C43D72 for ; Wed, 19 Apr 2006 12:24:52 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k3JCOpDo052775; Wed, 19 Apr 2006 07:24:51 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44462C07.4030903@centtech.com> Date: Wed, 19 Apr 2006 07:24:39 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: bv@wjv.com References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> In-Reply-To: <20060419095207.GC19339@wjv.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1407/Tue Apr 18 16:01:55 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 12:24:58 -0000 Bill Vermillion wrote: > Somewhere around Wed, Apr 19, 2006 at 04:07 , the world stopped > and listened as freebsd-hackers-request@freebsd.org graced us with > this profound tidbit of wisdom that would fulfill the enjoyment of > future generations: > >> Message: 20 >> Date: Tue, 18 Apr 2006 15:07:31 -0700 >> From: Darren Pilgrim > >> Eric Anderson wrote: > >> > If I could figure out how to make sh do colors, I'd do it. :) > >> Please do not use colors in rc. Escape-sequenced colors make >> unacceptable assumptions about the user and syslogd strips >> escape sequences anyway, so it would be of no use to logged >> consoles. Serial consoles introduce other problems with buggy >> escape handling in third-party terminal programs. A good text >> layout and descriptive status messages do far more for clarity >> and readability than any use of color ever can. > > Let me add to that. About 10% of the male population has some > color vision problem. Mine is a bit more than others. Everytime > I get called to work on a Linux system, I have to go in and disable > the colors as the reds and other colors become very hard to see > against a dark background. The problem is the luminance value of > colors such a red is quite low compared to others. That's one of > the reasons why fire-trucks in this area are lime-green, as red > trucks disappear into the blackness at night. > > If you add color make sure it is a user selectable option > and not turned on by default. IMO everything you need to admin a > system needs to be able to run on something as lowly as a pure > serial terminal as the above poster notes. Ok. So I've received mass amounts of mail regarding this, and most of it has been positively in favor of having the option to enable the rc_fancy, and then an additional option to turn on coloring, with the default to be non-colored but still rc_fancy="YES" which should work ok on serial and other terminals (it did for me). I completely agree about all the coloring comments, and terminal issues. I personally think it should be an available option, easily enabled or disabled at will. I've put up an updated version, with many changes. This version includes optional coloring (with rc_fancy_color="YES" in rc.conf), better checking, cleaner coding, and no loops. This version is *much* more refined than the others - thanks for all the hints everyone! http://www.googlebit.com/freebsd/patches/rc_fancy.patch-5 Also - could I check the kern.console sysctl and decide if it's starting using a console or not, and then automatically override the rc.conf settings if it is booting to a serial console? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 13:02:07 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 618A116A402 for ; Wed, 19 Apr 2006 13:02:07 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01B4443D46 for ; Wed, 19 Apr 2006 13:02:06 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k3JD26FU054308; Wed, 19 Apr 2006 08:02:06 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <444634C1.9080206@centtech.com> Date: Wed, 19 Apr 2006 08:01:53 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Eric Anderson References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> In-Reply-To: <44462C07.4030903@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1407/Tue Apr 18 16:01:55 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 13:02:07 -0000 Eric Anderson wrote: > Bill Vermillion wrote: >> Somewhere around Wed, Apr 19, 2006 at 04:07 , the world stopped >> and listened as freebsd-hackers-request@freebsd.org graced us with >> this profound tidbit of wisdom that would fulfill the enjoyment of >> future generations: >> >>> Message: 20 >>> Date: Tue, 18 Apr 2006 15:07:31 -0700 >>> From: Darren Pilgrim >> >>> Eric Anderson wrote: >> >>> > If I could figure out how to make sh do colors, I'd do it. :) >> >>> Please do not use colors in rc. Escape-sequenced colors make >>> unacceptable assumptions about the user and syslogd strips >>> escape sequences anyway, so it would be of no use to logged >>> consoles. Serial consoles introduce other problems with buggy >>> escape handling in third-party terminal programs. A good text >>> layout and descriptive status messages do far more for clarity >>> and readability than any use of color ever can. >> >> Let me add to that. About 10% of the male population has some >> color vision problem. Mine is a bit more than others. Everytime >> I get called to work on a Linux system, I have to go in and disable >> the colors as the reds and other colors become very hard to see >> against a dark background. The problem is the luminance value of >> colors such a red is quite low compared to others. That's one of >> the reasons why fire-trucks in this area are lime-green, as red >> trucks disappear into the blackness at night. >> >> If you add color make sure it is a user selectable option >> and not turned on by default. IMO everything you need to admin a >> system needs to be able to run on something as lowly as a pure >> serial terminal as the above poster notes. > > > Ok. So I've received mass amounts of mail regarding this, and most of it > has been positively in favor of having the option to enable the > rc_fancy, and then an additional option to turn on coloring, with the > default to be non-colored but still rc_fancy="YES" which should work ok > on serial and other terminals (it did for me). > > > I completely agree about all the coloring comments, and terminal issues. > I personally think it should be an available option, easily enabled or > disabled at will. > > I've put up an updated version, with many changes. This version > includes optional coloring (with rc_fancy_color="YES" in rc.conf), > better checking, cleaner coding, and no loops. This version is *much* > more refined than the others - thanks for all the hints everyone! > > > http://www.googlebit.com/freebsd/patches/rc_fancy.patch-5 Looks like this version does something strange - from an xterm, the spacing is correct, but from console, it doesn't do anything with the \033[71G in the echo. I've played with term types, but can't seem to make it act the same under console as it does in an xterm. Anyone know the issue? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 14:40:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B92216A403 for ; Wed, 19 Apr 2006 14:40:14 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6A7C43D46 for ; Wed, 19 Apr 2006 14:40:13 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k3JEeC57058564 for ; Wed, 19 Apr 2006 09:40:12 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44464BBF.5040801@centtech.com> Date: Wed, 19 Apr 2006 09:39:59 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> In-Reply-To: <444634C1.9080206@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1407/Tue Apr 18 16:01:55 2006 on mh1.centtech.com X-Virus-Status: Clean Subject: Re: [PATCH] Fancy rc startup style RFC - v6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 14:40:14 -0000 Eric Anderson wrote: > Eric Anderson wrote: >> Bill Vermillion wrote: >>> Somewhere around Wed, Apr 19, 2006 at 04:07 , the world stopped >>> and listened as freebsd-hackers-request@freebsd.org graced us with >>> this profound tidbit of wisdom that would fulfill the enjoyment of >>> future generations: >>> >>>> Message: 20 >>>> Date: Tue, 18 Apr 2006 15:07:31 -0700 >>>> From: Darren Pilgrim >>> >>>> Eric Anderson wrote: >>> >>>> > If I could figure out how to make sh do colors, I'd do it. :) >>> >>>> Please do not use colors in rc. Escape-sequenced colors make >>>> unacceptable assumptions about the user and syslogd strips >>>> escape sequences anyway, so it would be of no use to logged >>>> consoles. Serial consoles introduce other problems with buggy >>>> escape handling in third-party terminal programs. A good text >>>> layout and descriptive status messages do far more for clarity >>>> and readability than any use of color ever can. >>> >>> Let me add to that. About 10% of the male population has some >>> color vision problem. Mine is a bit more than others. Everytime >>> I get called to work on a Linux system, I have to go in and disable >>> the colors as the reds and other colors become very hard to see >>> against a dark background. The problem is the luminance value of >>> colors such a red is quite low compared to others. That's one of >>> the reasons why fire-trucks in this area are lime-green, as red >>> trucks disappear into the blackness at night. >>> >>> If you add color make sure it is a user selectable option >>> and not turned on by default. IMO everything you need to admin a >>> system needs to be able to run on something as lowly as a pure >>> serial terminal as the above poster notes. >> >> >> Ok. So I've received mass amounts of mail regarding this, and most of >> it has been positively in favor of having the option to enable the >> rc_fancy, and then an additional option to turn on coloring, with the >> default to be non-colored but still rc_fancy="YES" which should work >> ok on serial and other terminals (it did for me). >> >> >> I completely agree about all the coloring comments, and terminal >> issues. I personally think it should be an available option, easily >> enabled or disabled at will. >> >> I've put up an updated version, with many changes. This version >> includes optional coloring (with rc_fancy_color="YES" in rc.conf), >> better checking, cleaner coding, and no loops. This version is *much* >> more refined than the others - thanks for all the hints everyone! >> >> >> http://www.googlebit.com/freebsd/patches/rc_fancy.patch-5 > > Looks like this version does something strange - from an xterm, the > spacing is correct, but from console, it doesn't do anything with the > \033[71G in the echo. I've played with term types, but can't seem to > make it act the same under console as it does in an xterm. > > Anyone know the issue? Thanks to Rick Petty for pointing me in the right direction (man page!), here's the latest, and I think solid patch (for RELENG-6): http://www.googlebit.com/freebsd/patches/rc_fancy.patch-6 Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 14:46:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 062AE16A405 for ; Wed, 19 Apr 2006 14:46:14 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D51743D46 for ; Wed, 19 Apr 2006 14:46:11 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so34045nfc for ; Wed, 19 Apr 2006 07:46:10 -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:references; b=Nisj4PrWcUlYTWLMV9gntAnoWTxeTDBPHqe4AW74jdxcc1asyV3hj2GS/3aJpwe4hX6FZhU+VtcXls/hge9JBnXoUVZ25hSV3jotU/UF0TUsV+httpqsCPjnZADqilrU1yW87OSWAn5X3fMUBvI8K0w++tynmLT+qNHksOGa0EE= Received: by 10.48.162.20 with SMTP id k20mr277647nfe; Wed, 19 Apr 2006 07:46:10 -0700 (PDT) Received: by 10.48.217.6 with HTTP; Wed, 19 Apr 2006 07:46:09 -0700 (PDT) Message-ID: <346a80220604190746n69a74a67te58599f743312cab@mail.gmail.com> Date: Wed, 19 Apr 2006 10:46:09 -0400 From: "Coleman Kane" To: "Eric Anderson" In-Reply-To: <444634C1.9080206@centtech.com> MIME-Version: 1.0 References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> 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: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 14:46:14 -0000 On 4/19/06, Eric Anderson wrote: > > Eric Anderson wrote: > > Bill Vermillion wrote: > >> Somewhere around Wed, Apr 19, 2006 at 04:07 , the world stopped > >> and listened as freebsd-hackers-request@freebsd.org graced us with > >> this profound tidbit of wisdom that would fulfill the enjoyment of > >> future generations: > >> > >>> Message: 20 > >>> Date: Tue, 18 Apr 2006 15:07:31 -0700 > >>> From: Darren Pilgrim > >> > >>> Eric Anderson wrote: > >> > >>> > If I could figure out how to make sh do colors, I'd do it. :) > >> > >>> Please do not use colors in rc. Escape-sequenced colors make > >>> unacceptable assumptions about the user and syslogd strips > >>> escape sequences anyway, so it would be of no use to logged > >>> consoles. Serial consoles introduce other problems with buggy > >>> escape handling in third-party terminal programs. A good text > >>> layout and descriptive status messages do far more for clarity > >>> and readability than any use of color ever can. This point can be debated... read some literature from Edward Tufte... colors are a good way to cram more "information" into a space without actually compromising the capacity of that space. >> > >> Let me add to that. About 10% of the male population has some > >> color vision problem. Mine is a bit more than others. Everytime > >> I get called to work on a Linux system, I have to go in and disable > >> the colors as the reds and other colors become very hard to see > >> against a dark background. The problem is the luminance value of > >> colors such a red is quite low compared to others. That's one of > >> the reasons why fire-trucks in this area are lime-green, as red > >> trucks disappear into the blackness at night. > >> > >> If you add color make sure it is a user selectable option > >> and not turned on by default. IMO everything you need to admin a > >> system needs to be able to run on something as lowly as a pure > >> serial terminal as the above poster notes. > > > > > > Ok. So I've received mass amounts of mail regarding this, and most of i= t > > has been positively in favor of having the option to enable the > > rc_fancy, and then an additional option to turn on coloring, with the > > default to be non-colored but still rc_fancy=3D"YES" which should work = ok > > on serial and other terminals (it did for me). > > > > > > I completely agree about all the coloring comments, and terminal issues= . > > I personally think it should be an available option, easily enabled or > > disabled at will. > > > > I've put up an updated version, with many changes. This version > > includes optional coloring (with rc_fancy_color=3D"YES" in rc.conf), > > better checking, cleaner coding, and no loops. This version is *much* > > more refined than the others - thanks for all the hints everyone! > > > > > > http://www.googlebit.com/freebsd/patches/rc_fancy.patch-5 > > Looks like this version does something strange - from an xterm, the > spacing is correct, but from console, it doesn't do anything with the > \033[71G in the echo. I've played with term types, but can't seem to > make it act the same under console as it does in an xterm. > > Anyone know the issue? > > > Eric Try: \033[71C Hmm... I see 71 spaces.... how about we just stick to the padding... I woul= d like to not go overboard by using a lot of other escape sequences that have less experience out in the wild (and thus, less testing and are more likely to fail). Colors and attributes seem to be the overwhelming majority of reasons using the escape codes. Cursor control and other macros are probabl= y less common. You can change the \033 ---> \e if you like, or leave it. We should settle ourselves on a standard for this however... maybe make a /etc/rc.fancy that has macros for all of this stuff. Also, I second the comment regarding making this tunable. Of course the console will default to 7-bit ASCII text, printable characters only (or whatever charset you have chosen). One of the big reasons for Linux's "prettification" of its console, and support for fb console, is that there are a good number of Linux installations out there where the primary application is desktop and workstation. As for me, I primarily run FreeBSD as a desktop/workstation and therefore enjoy the opportunity to make the console more "readable". We discuss the "bare necessities for servers" and "what's necessary for administering a server", I think that my (and others') workstation needs and desires are important to the development of FreeBSD too. We should be embracing the adoption of the platform for workstation and desktop use as well, and actually take the advice of those users to heart. I would hope that if this featureset can get into the base system, then tunables get into the Console section of sysinstall (allowing this to be turned on at install time) and that the screenshots generated from that entice people who like things like "colorful error messages" to gain more interest in the platform (and yes, "FreeBSD is ugly" is a common crtique I have heard). Maybe that will finall= y push some others to get FB console working (KGI?)... My point is that we should let our purist values get in the way of others' enhanced experience using the system. -- coleman From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 15:06:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 794CF16A400 for ; Wed, 19 Apr 2006 15:06:18 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from linuxupdserver.utsp.utwente.nl (linuxupdserver.utsp.utwente.nl [130.89.1.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6623543D72 for ; Wed, 19 Apr 2006 15:06:17 +0000 (GMT) (envelope-from pieter@degoeje.nl) Received: from nox.student.utwente.nl (nox.student.utwente.nl [130.89.165.91]) by linuxupdserver.utsp.utwente.nl (8.11.7/HKD) with ESMTP id k3JF5wI10064 for ; Wed, 19 Apr 2006 17:05:58 +0200 From: Pieter de Goeje To: freebsd-hackers@freebsd.org Date: Wed, 19 Apr 2006 17:05:57 +0200 User-Agent: KMail/1.9.1 References: <20060419040716.4F26116A45F@hub.freebsd.org> <444634C1.9080206@centtech.com> <44464BBF.5040801@centtech.com> In-Reply-To: <44464BBF.5040801@centtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604191705.58027.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-MailScanner-From: pieter@degoeje.nl Subject: Re: [PATCH] Fancy rc startup style RFC - v6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 15:06:18 -0000 On Wednesday 19 April 2006 16:39, Eric Anderson wrote: > Eric Anderson wrote: > > Eric Anderson wrote: > >> Bill Vermillion wrote: > >>> Somewhere around Wed, Apr 19, 2006 at 04:07 , the world stopped > >>> and listened as freebsd-hackers-request@freebsd.org graced us with > >>> this profound tidbit of wisdom that would fulfill the enjoyment of > >>> > >>> future generations: > >>>> Message: 20 > >>>> Date: Tue, 18 Apr 2006 15:07:31 -0700 > >>>> From: Darren Pilgrim > >>>> > >>>> Eric Anderson wrote: > >>>> > If I could figure out how to make sh do colors, I'd do it. :) > >>>> > >>>> Please do not use colors in rc. Escape-sequenced colors make > >>>> unacceptable assumptions about the user and syslogd strips > >>>> escape sequences anyway, so it would be of no use to logged > >>>> consoles. Serial consoles introduce other problems with buggy > >>>> escape handling in third-party terminal programs. A good text > >>>> layout and descriptive status messages do far more for clarity > >>>> and readability than any use of color ever can. > >>> > >>> Let me add to that. About 10% of the male population has some > >>> color vision problem. Mine is a bit more than others. Everytime > >>> I get called to work on a Linux system, I have to go in and disable > >>> the colors as the reds and other colors become very hard to see > >>> against a dark background. The problem is the luminance value of > >>> colors such a red is quite low compared to others. That's one of > >>> the reasons why fire-trucks in this area are lime-green, as red > >>> trucks disappear into the blackness at night. > >>> > >>> If you add color make sure it is a user selectable option > >>> and not turned on by default. IMO everything you need to admin a > >>> system needs to be able to run on something as lowly as a pure > >>> serial terminal as the above poster notes. > >> > >> Ok. So I've received mass amounts of mail regarding this, and most of > >> it has been positively in favor of having the option to enable the > >> rc_fancy, and then an additional option to turn on coloring, with the > >> default to be non-colored but still rc_fancy="YES" which should work > >> ok on serial and other terminals (it did for me). > >> > >> > >> I completely agree about all the coloring comments, and terminal > >> issues. I personally think it should be an available option, easily > >> enabled or disabled at will. > >> > >> I've put up an updated version, with many changes. This version > >> includes optional coloring (with rc_fancy_color="YES" in rc.conf), > >> better checking, cleaner coding, and no loops. This version is *much* > >> more refined than the others - thanks for all the hints everyone! > >> > >> > >> http://www.googlebit.com/freebsd/patches/rc_fancy.patch-5 > > > > Looks like this version does something strange - from an xterm, the > > spacing is correct, but from console, it doesn't do anything with the > > \033[71G in the echo. I've played with term types, but can't seem to > > make it act the same under console as it does in an xterm. > > > > Anyone know the issue? > > Thanks to Rick Petty for pointing me in the right direction (man page!), > here's the latest, and I think solid patch (for RELENG-6): > > > http://www.googlebit.com/freebsd/patches/rc_fancy.patch-6 > > > Eric Looks really good to me :) Regards, Pieter de Goeje From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 15:37:34 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEB7316A402 for ; Wed, 19 Apr 2006 15:37:34 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: from mired.org (dsl092-153-074.wdc2.dsl.speakeasy.net [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 8383943D6E for ; Wed, 19 Apr 2006 15:37:27 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 83687 invoked by uid 1001); 19 Apr 2006 15:37:25 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Wed, 19 Apr 2006 11:37:22 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17478.22833.727876.432169@bhuda.mired.org> Date: Wed, 19 Apr 2006 11:37:21 -0400 To: cokane@cokane.org In-Reply-To: <346a80220604190746n69a74a67te58599f743312cab@mail.gmail.com> References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> <346a80220604190746n69a74a67te58599f743312cab@mail.gmail.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 15:37:34 -0000 In <346a80220604190746n69a74a67te58599f743312cab@mail.gmail.com>, Coleman Kane typed: > On 4/19/06, Eric Anderson wrote: > > >>> Please do not use colors in rc. Escape-sequenced colors make > > >>> unacceptable assumptions about the user and syslogd strips > > >>> escape sequences anyway, so it would be of no use to logged > > >>> consoles. Serial consoles introduce other problems with buggy > > >>> escape handling in third-party terminal programs. A good text > > >>> layout and descriptive status messages do far more for clarity > > >>> and readability than any use of color ever can. > This point can be debated... Only the last point, and only because it involves a quantity that's very difficult to measure. > read some literature from Edward Tufte... I've read Tufte. I've gotten him to sign my copy of some of his books at his seminars. I wish (vehemently!) that more web authors would read Tufte. > colors are a good way to cram more "information" into a space without > actually compromising the capacity of that space. True, but that's not his point. His point is that the colors aren't always visible (another thing I wish more web authors were aware of). The text layout and status messages should work well in environments where the colors aren't visible, because there are times when that's the kind of environment they'll be in. That said, colors can make checking for exceptions much easier - if you can see them. So I don't have any problem with adding colors. However, they should be off by default (at least initially), and the messages and layout should be tested that way until they work well without colors. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 16:04:25 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46ADD16A400 for ; Wed, 19 Apr 2006 16:04:25 +0000 (UTC) (envelope-from root@scienceclue.ath.cx) Received: from scienceclue.ath.cx (mic92-1-87-90-12-116.dsl.club-internet.fr [87.90.12.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FF2243D4C for ; Wed, 19 Apr 2006 16:04:23 +0000 (GMT) (envelope-from root@scienceclue.ath.cx) Received: from scienceclue.ath.cx (localhost [127.0.0.1]) by scienceclue.ath.cx (8.13.6/8.13.6) with ESMTP id k3JG4gqm006892 for ; Wed, 19 Apr 2006 18:04:43 +0200 (CEST) (envelope-from root@scienceclue.ath.cx) Received: (from root@localhost) by scienceclue.ath.cx (8.13.6/8.13.6/Submit) id k3JG4bEl006891 for freebsd-hackers@freebsd.org; Wed, 19 Apr 2006 18:04:37 +0200 (CEST) (envelope-from root) Date: Wed, 19 Apr 2006 18:04:36 +0200 From: Mathieu Prevot To: freebsd-hackers@freebsd.org Message-ID: <20060419160436.GA6835@scienceclue.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: sysctl(3) and sysctl(8) discrepancies X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mathieu Prevot List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 16:04:25 -0000 Hello, I have FreeBSD 6.1-RC #27: Wed Apr 19 02:08:00 CEST 2006 amd64 and I have 3 different outputs about hw.ncpu: `sysctl hw.ncpu` gives me: 'hw.ncpu: 2' and I have: hw.ncpu = 6 hw.ncpu = 3 with: #include #include #include main() { int ncpu[1]; size_t len; len=sizeof(int); sysctlnametomib("hw.ncpu",ncpu,&len); printf("hw.ncpu = %d\n",(*ncpu)); printf("hw.ncpu = %d\n",HW_NCPU); exit(0); } Am I doing something wrong ? Mathieu From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 16:07:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD68F16A401 for ; Wed, 19 Apr 2006 16:07:35 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id E635F43D81 for ; Wed, 19 Apr 2006 16:07:17 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so52610nfc for ; Wed, 19 Apr 2006 09:07:16 -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:references; b=pnUFN+80CX16whGeJ1Ty5K8EZFurGEUWeP25cHXFd2aG2IXADNyKRJsa9OYFndbLeB9M4bIDqTlrJI4OPyWU5gismhNf2ZiJEuAxj9VTd+C6pBKjQYnUOOzE3wlwimkDElo2rmFz5oCBwkycdzK12n2/HC/Xthb2AG/JKv2jc8E= Received: by 10.48.162.20 with SMTP id k20mr339975nfe; Wed, 19 Apr 2006 09:00:48 -0700 (PDT) Received: by 10.48.217.6 with HTTP; Wed, 19 Apr 2006 09:00:48 -0700 (PDT) Message-ID: <346a80220604190900i3bfc3b54v93a4c6c30f0dfc4f@mail.gmail.com> Date: Wed, 19 Apr 2006 12:00:48 -0400 From: "Coleman Kane" To: "Mike Meyer" In-Reply-To: <17478.22833.727876.432169@bhuda.mired.org> MIME-Version: 1.0 References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> <346a80220604190746n69a74a67te58599f743312cab@mail.gmail.com> <17478.22833.727876.432169@bhuda.mired.org> 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: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 16:07:35 -0000 On 4/19/06, Mike Meyer wrote: > > In <346a80220604190746n69a74a67te58599f743312cab@mail.gmail.com>, Coleman > Kane typed: > > On 4/19/06, Eric Anderson wrote: > > > >>> Please do not use colors in rc. Escape-sequenced colors make > > > >>> unacceptable assumptions about the user and syslogd strips > > > >>> escape sequences anyway, so it would be of no use to logged > > > >>> consoles. Serial consoles introduce other problems with buggy > > > >>> escape handling in third-party terminal programs. A good text > > > >>> layout and descriptive status messages do far more for clarity > > > >>> and readability than any use of color ever can. > > This point can be debated... > > Only the last point, and only because it involves a quantity that's > very difficult to measure. > > > read some literature from Edward Tufte... > > I've read Tufte. I've gotten him to sign my copy of some of his books > at his seminars. I wish (vehemently!) that more web authors would read > Tufte. > > > colors are a good way to cram more "information" into a space without > > actually compromising the capacity of that space. > > True, but that's not his point. His point is that the colors aren't > always visible (another thing I wish more web authors were aware > of). The text layout and status messages should work well in > environments where the colors aren't visible, because there are times > when that's the kind of environment they'll be in. > > That said, colors can make checking for exceptions much easier - if > you can see them. So I don't have any problem with adding > colors. However, they should be off by default (at least initially), > and the messages and layout should be tested that way until they work > well without colors. I want to make a nicely configurable console message system that includes colors and formatting settable by the user (with a few sane defaults). I am familiar with the trouble of using red for errors (if you've ever seen red on a B+W TV you'll know too). How about we all discuss good choices for "default" colors? And, I think I am going to assemble some sort of "framework" sh script for this after all. Either it gets ammended to rc.subr, or it sits alone as its own dedicated module (that can be sourced by rc.*). -- > Mike Meyer > http://www.mired.org/consulting.html > Independent Network/Unix/Perforce consultant, email for more information. > From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 16:39:09 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F67916A400 for ; Wed, 19 Apr 2006 16:39:09 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: from mired.org (dsl092-153-074.wdc2.dsl.speakeasy.net [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id ADD3B43D45 for ; Wed, 19 Apr 2006 16:39:07 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 86721 invoked by uid 1001); 19 Apr 2006 16:39:03 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Wed, 19 Apr 2006 12:39:00 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17478.26532.75132.709164@bhuda.mired.org> Date: Wed, 19 Apr 2006 12:39:00 -0400 To: cokane@cokane.org In-Reply-To: <346a80220604190900i3bfc3b54v93a4c6c30f0dfc4f@mail.gmail.com> References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> <346a80220604190746n69a74a67te58599f743312cab@mail.gmail.com> <17478.22833.727876.432169@bhuda.mired.org> <346a80220604190900i3bfc3b54v93a4c6c30f0dfc4f@mail.gmail.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 16:39:09 -0000 In <346a80220604190900i3bfc3b54v93a4c6c30f0dfc4f@mail.gmail.com>, Coleman Kane typed: > On 4/19/06, Mike Meyer wrote: > How about we all discuss good choices for "default" colors? Depends on the goal: do you want the default to work for everyone, or do you want the default to be prettier and/or better for most people but absolutely suck for a few? I like the former. Which means the defaults need to be black and white. Given a sufficiently flexible system for picking colors, we can use bold/underline/reversed as "colors". That might work well under that constraint. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 17:06:48 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0765E16A404 for ; Wed, 19 Apr 2006 17:06:48 +0000 (UTC) (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 0DD4243D7B for ; Wed, 19 Apr 2006 17:06:35 +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 k3JH6Sjn014487; Wed, 19 Apr 2006 10:06:28 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k3JH6Sed014486; Wed, 19 Apr 2006 10:06:28 -0700 Date: Wed, 19 Apr 2006 10:06:27 -0700 From: Brooks Davis To: Peter Jeremy Message-ID: <20060419170627.GA11251@odin.ac.hmc.edu> References: <444515C8.3030406@centtech.com> <20060418165709.GA17705@central.0xfce3.net> <44452532.40703@centtech.com> <20060418.114933.69380798.imp@bsdimp.com> <346a80220604181102v3597a1edp3e05fa663b87e15c@mail.gmail.com> <20060418193018.GB694@turion.vk2pj.dyndns.org> <444545D3.5010405@centtech.com> <20060419075721.GB704@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="G4iJoqBmSsgzjUCe" Content-Disposition: inline In-Reply-To: <20060419075721.GB704@turion.vk2pj.dyndns.org> 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 Cc: freebsd-hackers@freebsd.org, cokane@cokane.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 17:06:48 -0000 --G4iJoqBmSsgzjUCe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 19, 2006 at 05:57:21PM +1000, Peter Jeremy wrote: > On Tue, 2006-Apr-18 15:02:27 -0500, Eric Anderson wrote: > >Peter Jeremy wrote: > >>>+ padding=3D"" > >>>+ paddingsize=3D$(($columns - 15 - $2 - $namesize)) > >>>+ until [ 0 =3D ${paddingsize} ]; do > >>>+ padding=3D" $padding" > >>>+ paddingsize=3D$(($paddingsize - 1)) > >>>+ done > >> > >>This particular block of code appears unnecessary (since $padding is=20 > >>unused). > > > >I must be missing something, because I'm pretty sure it's used.. What=20 > >did I miss? >=20 > Actually, I had a closer look and I was wrong, sorry. I missed the > '[ $2 =3D 0 ]' test. The code might be more legible (and is definitely > more efficient) if the above code was moved into the else clause for > that test. >=20 > Also '[ $2 =3D 0 ]' should probably be written as '[ "0$2" -eq 0 ]', or > similar, so that it doesn't blow up if there is no $2. Or better use "${2:-0}" if that's what you mean. The idiom of prepending stuff to a variable in a string to deal with the unassigned variables has always seemed to me like it was a hold over from some truly ancent shell without modern features. The '[ "x$var" =3D "x" ]' idiom is even worse. Test has only had -z and -n for a decade or two... -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --G4iJoqBmSsgzjUCe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFERm4SXY6L6fI4GtQRAn69AJ9ZRvTJTKcVcBkQUkNA9tcgKBSYkACgoxm1 Cp+ipLnqMVO5UdsMl0I1W8A= =oEZy -----END PGP SIGNATURE----- --G4iJoqBmSsgzjUCe-- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 17:18:50 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 796B516A402 for ; Wed, 19 Apr 2006 17:18:50 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B03743D46 for ; Wed, 19 Apr 2006 17:18:50 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms063.mailsrvcs.net ([192.168.1.4]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IXZ00H6MC3DKEM0@vms042.mailsrvcs.net> for freebsd-hackers@freebsd.org; Wed, 19 Apr 2006 12:18:49 -0500 (CDT) Date: Wed, 19 Apr 2006 12:18:49 -0500 (CDT) From: Sergey Babkin To: Bill Vermillion , freebsd-hackers@freebsd.org Message-id: <32575854.2582371145467129800.JavaMail.root@vms063.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Mailman-Approved-At: Wed, 19 Apr 2006 17:21:41 +0000 Cc: Subject: Re: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 17:18:50 -0000 >From: Bill Vermillion has some >color vision problem. Mine is a bit more than others. Everytime >I get called to work on a Linux system, I have to go in and disable >the colors as the reds and other colors become very hard to see >against a dark background. The problem is the luminance value of >colors such a red is quite low compared to others. The problem with Linux colors is that they have been designed to be used on the white background which is the xterm's default (and which I hate as it's tough on my eyes). Since I usually use the black background, I disable them too. When I have time and patience to mess around, I set the LS_COLORS and such variables to the complementary bitmasks of what they've been, and that fixes the problem with contrast on the black background. -SB From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 17:32:04 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F5A316A406 for ; Wed, 19 Apr 2006 17:32:04 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBD3643D53 for ; Wed, 19 Apr 2006 17:32:01 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by nproxy.gmail.com with SMTP id p48so906983nfa for ; Wed, 19 Apr 2006 10:32:00 -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:references; b=AliyVzPWtA17XLGidHPFezVMsnPY/z7rY+8yggR6jq46icT7H564jaYB+dxN4zhLbS+OiYVrp4L6IaKwgc/rJV60SoJdvFHukkGMLwvFyLVA6li1CCyRrlz6JJuk63Yxo1R6epDtG3FAaO/aPj7Q6y6DE+0wD4wF+geZdJRTS2Y= Received: by 10.48.223.3 with SMTP id v3mr704373nfg; Wed, 19 Apr 2006 10:03:57 -0700 (PDT) Received: by 10.48.217.6 with HTTP; Wed, 19 Apr 2006 10:03:57 -0700 (PDT) Message-ID: <346a80220604191003t359258egce45cc8bfc65970f@mail.gmail.com> Date: Wed, 19 Apr 2006 13:03:57 -0400 From: "Coleman Kane" To: "Mike Meyer" In-Reply-To: <17478.26532.75132.709164@bhuda.mired.org> MIME-Version: 1.0 References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> <346a80220604190746n69a74a67te58599f743312cab@mail.gmail.com> <17478.22833.727876.432169@bhuda.mired.org> <346a80220604190900i3bfc3b54v93a4c6c30f0dfc4f@mail.gmail.com> <17478.26532.75132.709164@bhuda.mired.org> 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: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 17:32:04 -0000 On 4/19/06, Mike Meyer wrote: > > In <346a80220604190900i3bfc3b54v93a4c6c30f0dfc4f@mail.gmail.com>, Coleman > Kane typed: > > On 4/19/06, Mike Meyer > wrote: > > How about we all discuss good choices for "default" colors? > > Depends on the goal: do you want the default to work for everyone, or > do you want the default to be prettier and/or better for most people > but absolutely suck for a few? I was thinking perhaps of having a predefined set of templates (with the option and documentation to add your own). Perhaps implement one that creates the "traffic-light" style that seems to make intuitive sense to man= y americans (Bold Red: error, Bold Green: Success, Bold Yellow: warning/notice), and also have another perdefined one that uses a different color set. BTW, I know that blue and red are "bad" colors. How to the "emphasized" or "emboldened" versions of these colors match up? I like the former. Which means the defaults need to be black and > white. Given a sufficiently flexible system for picking colors, we can > use bold/underline/reversed as "colors". That might work well under > that constraint. I am merely talking about predefined color choices... of course if rc_fancy_color=3D"NO" then fancyiness will be B+W. I'd like to know if ther= e are better choices than Red/Green/Yellow. To me Red/Green/Yellow make sense to a lot of people because of their relation to our driving system here in the states. Maybe something like Error=3DYellow, Good=3DBlue, Warn/Notice= =3DGreen is a better choice across the board. -- > Mike Meyer > http://www.mired.org/consulting.html > Independent Network/Unix/Perforce consultant, email for more information. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 17:32:23 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0063116A404 for ; Wed, 19 Apr 2006 17:32:22 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: from mired.org (dsl092-153-074.wdc2.dsl.speakeasy.net [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id C516C43D6D for ; Wed, 19 Apr 2006 17:32:13 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 88016 invoked by uid 1001); 19 Apr 2006 17:32:12 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Wed, 19 Apr 2006 13:32:11 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17478.29723.209829.582135@bhuda.mired.org> Date: Wed, 19 Apr 2006 13:32:11 -0400 To: babkin@users.sourceforge.net In-Reply-To: <32575854.2582371145467129800.JavaMail.root@vms063.mailsrvcs.net> References: <32575854.2582371145467129800.JavaMail.root@vms063.mailsrvcs.net> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: Bill Vermillion , freebsd-hackers@freebsd.org Subject: Re: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 17:32:23 -0000 In <32575854.2582371145467129800.JavaMail.root@vms063.mailsrvcs.net>, Sergey Babkin typed: > >From: Bill Vermillion > > has some > >color vision problem. Mine is a bit more than others. Everytime > >I get called to work on a Linux system, I have to go in and disable > >the colors as the reds and other colors become very hard to see > >against a dark background. The problem is the luminance value of > >colors such a red is quite low compared to others. > The problem with Linux colors is that they have been > designed to be used on the white background which is > the xterm's default (and which I hate as it's tough > on my eyes). Since I usually use the black background, > I disable them too. So where do linux's blasted ls colors come from? It prints some file type as green. Green on white is simply bad news, whether or not you have vision problems. I always have to go disable them (and some linux distros make them *hard* to disable). http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 17:33:24 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2544216A4D4 for ; Wed, 19 Apr 2006 17:33:24 +0000 (UTC) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C5A643D48 for ; Wed, 19 Apr 2006 17:33:23 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.13.6/8.13.1) with ESMTP id k3JHXLxw024915; Wed, 19 Apr 2006 13:33:21 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.13.6/8.13.1/Submit) id k3JHXF15024914; Wed, 19 Apr 2006 13:33:15 -0400 (EDT) (envelope-from bv) Date: Wed, 19 Apr 2006 13:33:15 -0400 From: Bill Vermillion To: babkin@users.sourceforge.net Message-ID: <20060419173315.GD24534@wjv.com> References: <32575854.2582371145467129800.JavaMail.root@vms063.mailsrvcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <32575854.2582371145467129800.JavaMail.root@vms063.mailsrvcs.net> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on bilver.wjv.com Cc: freebsd-hackers@freebsd.org Subject: Re: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 17:33:24 -0000 "Ang utong ko ay sasabog sa sarap!" exclaimed Sergey Babkin while reading this message on Wed, Apr 19, 2006 at 12:18 and then responded with: > >From: Bill Vermillion > > has some > >color vision problem. Mine is a bit more than others. Everytime > >I get called to work on a Linux system, I have to go in and disable > >the colors as the reds and other colors become very hard to see > >against a dark background. The problem is the luminance value of > >colors such a red is quite low compared to others. > The problem with Linux colors is that they have been > designed to be used on the white background which is > the xterm's default (and which I hate as it's tough > on my eyes). Since I usually use the black background, > I disable them too. > When I have time and patience to mess around, I set the > LS_COLORS and such variables to the complementary > bitmasks of what they've been, and that fixes the > problem with contrast on the black background. Well I run in 80x24 text mode almost all the time, and when I need some graphics/web stuff I hit the KVM and move to an XP machine. I use vidcontrol to set my screen /home/bv/.profile:vidcontrol green black /home/bv/.profile:vidcontrol -b blue /home/bv/.profile:vidcontrol -c blink That gives me green on black, with a blue border defining the edge of the screen. With my vision it works very well. I got to something with white on black and I find it too bright to use, except on dying monitors :-) [I've had some clients with really bad server monitors - typically SCO. On those I'd set the white to bright white to make them readable] Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 17:46:13 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0205C16A408 for ; Wed, 19 Apr 2006 17:46:13 +0000 (UTC) (envelope-from thomas@soete.info) Received: from smtp13.wanadoo.fr (smtp13.wanadoo.fr [193.252.22.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A54443D78 for ; Wed, 19 Apr 2006 17:46:11 +0000 (GMT) (envelope-from thomas@soete.info) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1304.wanadoo.fr (SMTP Server) with ESMTP id 22CC07000082 for ; Wed, 19 Apr 2006 19:46:11 +0200 (CEST) Received: from [192.168.1.15] (ALille-252-1-26-88.w83-192.abo.wanadoo.fr [83.192.110.88]) by mwinf1304.wanadoo.fr (SMTP Server) with ESMTP id CE9AB700008A for ; Wed, 19 Apr 2006 19:46:09 +0200 (CEST) X-ME-UUID: 20060419174609846.CE9AB700008A@mwinf1304.wanadoo.fr Message-ID: <44467768.2080809@soete.info> Date: Wed, 19 Apr 2006 19:46:16 +0200 From: Thomas SOETE User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: hackers@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Wed, 19 Apr 2006 17:50:11 +0000 Cc: Subject: Kernel Fatal Trap 12 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 17:46:13 -0000 Hi everybody Since a little time I began to have some kernel fatal trap 12 I had FreeBSD 5.3 and I decided to install 6.0 to avoid this problem (thinking that the bug was patched between these versions) But after installing all, the kernel panic is still there uname -a output : FreeBSD freebsd 6.0-RELEASE-p6 FreeBSD 6.0-RELEASE-p6 #0: Mon Apr 17 19:27:35 CEST 2006 root@freebsd:/usr/src/sys/i386/compile/TOMS i386 where kgdb : #0 doadump () at pcpu.h:165 #1 0xc04b4c76 in boot (howto=260) at ../../../kern/kern_shutdown.c:399 #2 0xc04b4f0c in panic (fmt=0xc05e963d "%s") at ../../../kern/kern_shutdown.c:555 #3 0xc05cce40 in trap_fatal (frame=0xd5cf9ad8, eva=88) at ../../../i386/i386/trap.c:831 #4 0xc05ccbab in trap_pfault (frame=0xd5cf9ad8, usermode=0, eva=88) at ../../../i386/i386/trap.c:742 #5 0xc05cc7e9 in trap (frame= {tf_fs = -1067712504, tf_es = -1048772568, tf_ds = 40, tf_edi = 0, tf_esi = 0, tf_ebp = -707814604, tf_isp = -707814652, tf_ebx = -707814256, tf_edx = -707814000, tf_ecx = 0, tf_eax = 8, tf_trapno = 12, tf_err = 2, tf_eip = -1068217761, tf_cs = 32, tf_eflags = 66183, tf_esp = -707814612, tf_ss = 8}) at ../../../i386/i386/trap.c:432 #6 0xc05bbfda in calltrap () at ../../../i386/i386/exception.s:139 #7 0xc0544a5f in ip_ctloutput (so=0x8, sopt=0xd5cf9c90) at ../../../netinet/ip_output.c:1208 #8 0xc0552c03 in tcp_ctloutput (so=0xc16ca164, sopt=0xd5cf9c90) at ../../../netinet/tcp_usrreq.c:1036 #9 0xc04ee3cc in sosetopt (so=0xc16ca164, sopt=0xd5cf9c90) at ../../../kern/uipc_socket.c:1553 #10 0xc04f3629 in kern_setsockopt (td=0xc17d2d80, s=14, level=8, name=8, val=0xd5cf9d90, valseg=UIO_USERSPACE, valsize=0) at ../../../kern/uipc_syscalls.c:1331 #11 0xc04f355a in setsockopt (td=0xc17d2d80, uap=0x8) at ../../../kern/uipc_syscalls.c:1287 #12 0xc05cd157 in syscall (frame= {tf_fs = 139264059, tf_es = 59, tf_ds = -1078001605, tf_edi = 39, tf_esi = 139367520, tf_ebp = -1077941204, tf_isp = -707814044, tf_ebx = 138942556, tf_edx = 14, tf_ecx = 139367616, tf_eax = 105, tf_trapno = 22, tf_err = 2, tf_eip = 677011411, tf_cs = 51, tf_eflags = 518, tf_esp = -1077941248, tf_ss = 59}) at ../../../i386/i386/trap.c:976 #13 0xc05bc02f in Xint0x80_syscall () at ../../../i386/i386/exception.s:200 #14 0x00000033 in ?? () I tried to investigate a little and I found that : *#7 0xc0544a5f in ip_ctloutput (so=0x8, sopt=0xd5cf9c90) at ../../../netinet/ip_output.c:1208 1208 inp->inp_ip_tos = optval; *and (kgdb) p inp $12 = (struct inpcb *) 0x0 ok ... p null pointer :-/ inp is : struct inpcb *inp = sotoinpcb(so); and so is : (kgdb) p so $13 = (struct socket *) 0x8 hum strange, a pointer with value as 8 ... and so was passed as parameter : #7 0xc0544a5f in ip_ctloutput (so=0x8.... , let see where it was called : #8 0xc0552c03 in tcp_ctloutput (so=0xc16ca164, sopt=0xd5cf9c90) at ../../../netinet/tcp_usrreq.c:1036 1036 error = ip_ctloutput(so, sopt); and between the call of tcp_ctloutput and ip_ctloutput so wasn't changed, so it's value should be 0xc16ca164 (kgdb) p so $14 = (struct socket *) 0xc16ca164 So why the value passed by the caller is different with the value in the called function ? If you could help me to find why my gateway crash allmost each time the adsl connection drop it'll be nice :) Thanks, -- Thomas SOETE Etudiant Ingénieur Télécom - Enic Télécom Lille 1 Etudiant Master Recherche, Conception de Systèmes Embarqués - LIFL WWW : http://toms.netcv.org/ Mail & MSN : thomas@soete.info GTalk : toms2809@gmail.com From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 17:57:07 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99CB816A431 for ; Wed, 19 Apr 2006 17:57:07 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D5C443DA6 for ; Wed, 19 Apr 2006 17:56:52 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 6D5981A4DA7; Wed, 19 Apr 2006 10:56:52 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B4FF154E76; Wed, 19 Apr 2006 13:56:51 -0400 (EDT) Date: Wed, 19 Apr 2006 13:56:51 -0400 From: Kris Kennaway To: Thomas SOETE Message-ID: <20060419175651.GA71495@xor.obsecurity.org> References: <44467768.2080809@soete.info> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rwEMma7ioTxnRzrJ" Content-Disposition: inline In-Reply-To: <44467768.2080809@soete.info> User-Agent: Mutt/1.4.2.1i Cc: hackers@FreeBSD.org Subject: Re: Kernel Fatal Trap 12 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 17:57:08 -0000 --rwEMma7ioTxnRzrJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Apr 19, 2006 at 07:46:16PM +0200, Thomas SOETE wrote: > Hi everybody > Since a little time I began to have some kernel fatal trap 12 Kernel panics that magically start for no reason after a long time of stability are usually because your hardware has begun to fail. Kris --rwEMma7ioTxnRzrJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFERnnjWry0BWjoQKURAmz+AKD2gIMQ9k9TKEEceu4H3ffQ05sa/gCfelq5 BT0jhoBGDusWcNbyRguMB80= =L6vE -----END PGP SIGNATURE----- --rwEMma7ioTxnRzrJ-- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 17:59:04 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEBB016A40B for ; Wed, 19 Apr 2006 17:59:04 +0000 (UTC) (envelope-from thomas@soete.info) Received: from smtp13.wanadoo.fr (smtp13.wanadoo.fr [193.252.22.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32DC443D64 for ; Wed, 19 Apr 2006 17:59:04 +0000 (GMT) (envelope-from thomas@soete.info) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1304.wanadoo.fr (SMTP Server) with ESMTP id 408A47000096 for ; Wed, 19 Apr 2006 19:59:03 +0200 (CEST) Received: from [192.168.1.15] (ALille-252-1-26-88.w83-192.abo.wanadoo.fr [83.192.110.88]) by mwinf1304.wanadoo.fr (SMTP Server) with ESMTP id 82F367000090; Wed, 19 Apr 2006 19:59:02 +0200 (CEST) X-ME-UUID: 20060419175902536.82F367000090@mwinf1304.wanadoo.fr Message-ID: <44467A6C.3070401@soete.info> Date: Wed, 19 Apr 2006 19:59:08 +0200 From: Thomas SOETE User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Kris Kennaway References: <44467768.2080809@soete.info> <20060419175651.GA71495@xor.obsecurity.org> In-Reply-To: <20060419175651.GA71495@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: hackers@FreeBSD.org Subject: Re: Kernel Fatal Trap 12 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 17:59:05 -0000 Hum, is there a way to have a little idea of which hardware begun to fail ? -- Thomas SOETE Etudiant Ingénieur Télécom - Enic Télécom Lille 1 Etudiant Master Recherche, Conception de Systèmes Embarqués - LIFL WWW : http://toms.netcv.org/ Mail & MSN : thomas@soete.info GTalk : toms2809@gmail.com Kris Kennaway a écrit : > On Wed, Apr 19, 2006 at 07:46:16PM +0200, Thomas SOETE wrote: > >> Hi everybody >> Since a little time I began to have some kernel fatal trap 12 >> > > Kernel panics that magically start for no reason after a long time of > stability are usually because your hardware has begun to fail. > > Kris > From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 18:04:43 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE47816A40E for ; Wed, 19 Apr 2006 18:04:43 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6646543D66 for ; Wed, 19 Apr 2006 18:04:43 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.13.6/8.13.6) with ESMTP id k3JI4g4V047049; Wed, 19 Apr 2006 11:04:42 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.6/8.13.6/Submit) id k3JI4gAm047048; Wed, 19 Apr 2006 11:04:42 -0700 (PDT) (envelope-from sgk) Date: Wed, 19 Apr 2006 11:04:42 -0700 From: Steve Kargl To: Thomas SOETE Message-ID: <20060419180442.GA46936@troutmask.apl.washington.edu> References: <44467768.2080809@soete.info> <20060419175651.GA71495@xor.obsecurity.org> <44467A6C.3070401@soete.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44467A6C.3070401@soete.info> User-Agent: Mutt/1.4.2.1i Cc: hackers@freebsd.org, Kris Kennaway Subject: Re: Kernel Fatal Trap 12 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 18:04:43 -0000 On Wed, Apr 19, 2006 at 07:59:08PM +0200, Thomas SOETE wrote: > Kris Kennaway a ?crit : > >On Wed, Apr 19, 2006 at 07:46:16PM +0200, Thomas SOETE wrote: > > > >>Hi everybody > >>Since a little time I began to have some kernel fatal trap 12 > >> > > > >Kernel panics that magically start for no reason after a long time of > >stability are usually because your hardware has begun to fail. > > > >Kris > > > > Hum, is there a way to have a little idea of which hardware begun to fail ? > (Top post fixed!) Start by checking memory. If you have x86 hardware, then look at memtest86+. http://www.memtest.org/ -- Steve From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 18:07:43 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23F0C16A400 for ; Wed, 19 Apr 2006 18:07:43 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6429A43D6E for ; Wed, 19 Apr 2006 18:07:41 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k3JI7fKY068204 for ; Wed, 19 Apr 2006 13:07:41 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44467C60.8090708@centtech.com> Date: Wed, 19 Apr 2006 13:07:28 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <32575854.2582371145467129800.JavaMail.root@vms063.mailsrvcs.net> <20060419173315.GD24534@wjv.com> In-Reply-To: <20060419173315.GD24534@wjv.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1408/Wed Apr 19 10:13:11 2006 on mh1.centtech.com X-Virus-Status: Clean Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 18:07:43 -0000 Bill Vermillion wrote: > "Ang utong ko ay sasabog sa sarap!" exclaimed Sergey Babkin > while reading this message on Wed, Apr 19, 2006 at 12:18 > and then responded with: > >>> From: Bill Vermillion >> has some >>> color vision problem. Mine is a bit more than others. Everytime >>> I get called to work on a Linux system, I have to go in and disable >>> the colors as the reds and other colors become very hard to see >>> against a dark background. The problem is the luminance value of >>> colors such a red is quite low compared to others. > >> The problem with Linux colors is that they have been >> designed to be used on the white background which is >> the xterm's default (and which I hate as it's tough >> on my eyes). Since I usually use the black background, >> I disable them too. > >> When I have time and patience to mess around, I set the >> LS_COLORS and such variables to the complementary >> bitmasks of what they've been, and that fixes the >> problem with contrast on the black background. > > Well I run in 80x24 text mode almost all the time, and when I need > some graphics/web stuff I hit the KVM and move to an XP machine. > > I use vidcontrol to set my screen > > /home/bv/.profile:vidcontrol green black > /home/bv/.profile:vidcontrol -b blue > /home/bv/.profile:vidcontrol -c blink > > That gives me green on black, with a blue border defining the edge > of the screen. With my vision it works very well. > > I got to something with white on black and I find it too bright > to use, except on dying monitors :-) [I've had some clients > with really bad server monitors - typically SCO. On those > I'd set the white to bright white to make them readable] Ok - first, let me remind everyone that this is for startup/shutdown of scripts and such, not for ls and other things. I'd also like to remind everyone that the default for the whole thing can be OFF, so you won't even know the option exists if you don't want to know about it. If it is on, then the default is b/w like the current setup is, and currently no information is suppressed so there is no loss of helpful information on boot, only additional information (OK, FAILED, SKIP, etc). If someone doesn't like the colors, doesn't like the 'fancy' bootup, then they merely have to do nothing at all. This is a similar feature as rc_info is, and there's no issue there, because it's off by default. Same with the color daemon at the boot menu. I think it should be off by default, until enough people demand it on (if that happens at all), and then it should be b/w by default, with the option to make it color. My main goal was to implement this with as little reworking of the current system as possible, yet still reap rewards of easy readability when the system boots. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 18:08:05 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52B0116A401 for ; Wed, 19 Apr 2006 18:08:05 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9E5543D75 for ; Wed, 19 Apr 2006 18:08:04 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id D438D1A4DA8; Wed, 19 Apr 2006 11:08:04 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C9CCD54E77; Wed, 19 Apr 2006 14:08:03 -0400 (EDT) Date: Wed, 19 Apr 2006 14:08:03 -0400 From: Kris Kennaway To: Thomas SOETE Message-ID: <20060419180802.GA71717@xor.obsecurity.org> References: <44467768.2080809@soete.info> <20060419175651.GA71495@xor.obsecurity.org> <44467A6C.3070401@soete.info> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tKW2IUtsqtDRztdT" Content-Disposition: inline In-Reply-To: <44467A6C.3070401@soete.info> User-Agent: Mutt/1.4.2.1i Cc: hackers@FreeBSD.org, Kris Kennaway Subject: Re: Kernel Fatal Trap 12 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 18:08:05 -0000 --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Apr 19, 2006 at 07:59:08PM +0200, Thomas SOETE wrote: > Hum, is there a way to have a little idea of which hardware begun to fail ? Check CPU cooling, power supply, cabling, RAM, etc. Google for more - this question is asked and answered about once a week. Kris --tKW2IUtsqtDRztdT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFERnyCWry0BWjoQKURAjn2AKD4WIRXJ1Ek7DI76HS0kP+hlbDUgwCfX27C +9DjIY4fwXrffJr52eXxeM0= =9nX6 -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT-- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 18:14:26 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D057216A407 for ; Wed, 19 Apr 2006 18:14:26 +0000 (UTC) (envelope-from thomas@soete.info) Received: from smtp13.wanadoo.fr (smtp13.wanadoo.fr [193.252.22.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 408DC43D45 for ; Wed, 19 Apr 2006 18:14:26 +0000 (GMT) (envelope-from thomas@soete.info) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1304.wanadoo.fr (SMTP Server) with ESMTP id 76D9970000A1 for ; Wed, 19 Apr 2006 20:14:25 +0200 (CEST) Received: from [192.168.1.15] (ALille-252-1-26-88.w83-192.abo.wanadoo.fr [83.192.110.88]) by mwinf1304.wanadoo.fr (SMTP Server) with ESMTP id 915897000099 for ; Wed, 19 Apr 2006 20:14:24 +0200 (CEST) X-ME-UUID: 20060419181424595.915897000099@mwinf1304.wanadoo.fr Message-ID: <44467E07.8090802@soete.info> Date: Wed, 19 Apr 2006 20:14:31 +0200 From: Thomas SOETE User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 References: <44467768.2080809@soete.info> <20060419175651.GA71495@xor.obsecurity.org> <44467A6C.3070401@soete.info> <20060419180442.GA46936@troutmask.apl.washington.edu> In-Reply-To: <20060419180442.GA46936@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: hackers@freebsd.org Subject: Re: Kernel Fatal Trap 12 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 18:14:27 -0000 Hum ... first thing done before reinstalling freebsd 2 passes without errors For the little story, i don't know if it could help, My network is like that : LAN <-> FreeBSD Gateway <-> ISP Router <-> Internet Each 22 hours the isp router reboot the internet connection and usually the freebsd gateway crash when the isp router stop and restart the internet connection but it's not all the time, there could be few days without problem (max 12 days I think). So I can't say that the isp router make the freebsd crashing but when it crash it's very often when the isp router restart :-/ I'll continue to test the hardware Thanks to Kris & Steve -- Thomas SOETE Etudiant Ingénieur Télécom - Enic Télécom Lille 1 Etudiant Master Recherche, Conception de Systèmes Embarqués - LIFL WWW : http://toms.netcv.org/ Mail & MSN : thomas@soete.info GTalk : toms2809@gmail.com Steve Kargl a écrit : > On Wed, Apr 19, 2006 at 07:59:08PM +0200, Thomas SOETE wrote: > >> Kris Kennaway a ?crit : >> >>> On Wed, Apr 19, 2006 at 07:46:16PM +0200, Thomas SOETE wrote: >>> >>> >>>> Hi everybody >>>> Since a little time I began to have some kernel fatal trap 12 >>>> >>>> >>> Kernel panics that magically start for no reason after a long time of >>> stability are usually because your hardware has begun to fail. >>> >>> Kris >>> >>> >> Hum, is there a way to have a little idea of which hardware begun to fail ? >> >> > > (Top post fixed!) > > Start by checking memory. If you have x86 hardware, then > look at memtest86+. http://www.memtest.org/ > > From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 19:47:01 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AEC016A40A for ; Wed, 19 Apr 2006 19:47:01 +0000 (UTC) (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 64B8A43D45 for ; Wed, 19 Apr 2006 19:47:00 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.4) id k3JJkrit009319; Wed, 19 Apr 2006 14:46:53 -0500 (CDT) (envelope-from dan) Date: Wed, 19 Apr 2006 14:46:53 -0500 From: Dan Nelson To: Mathieu Prevot Message-ID: <20060419194653.GB18095@dan.emsphone.com> References: <20060419160436.GA6835@scienceclue.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060419160436.GA6835@scienceclue.ath.cx> X-OS: FreeBSD 5.5-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: sysctl(3) and sysctl(8) discrepancies X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 19:47:01 -0000 In the last episode (Apr 19), Mathieu Prevot said: > Hello, > > I have FreeBSD 6.1-RC #27: Wed Apr 19 02:08:00 CEST 2006 amd64 and I have 3 > different outputs about hw.ncpu: > > `sysctl hw.ncpu` gives me: > > 'hw.ncpu: 2' > > > and I have: > > hw.ncpu = 6 > hw.ncpu = 3 > > > with: > > #include > #include > #include > > main() > { > int ncpu[1]; > size_t len; > > len=sizeof(int); > sysctlnametomib("hw.ncpu",ncpu,&len); You want sysctlbyname() here instead. sysctlnametomib() returns a pointer to a mib array that you can pass to the sysctl() function later. Saves having to parse the string every time if you are looking up the same sysctl repeatedly. sysctlbyname("hw.ncpu", &ncpu, &len, NULL, 0); HW_NCPU is the mib number for hw.ncpu if you want to build the mib array manually. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 22:15:29 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C45BF16A401 for ; Wed, 19 Apr 2006 22:15:29 +0000 (UTC) (envelope-from luke@foolishgames.com) Received: from mail.foolishgames.com (mail.foolishgames.com [206.222.28.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 037A843D69 for ; Wed, 19 Apr 2006 22:15:23 +0000 (GMT) (envelope-from luke@foolishgames.com) Received: from [10.80.140.193] (pix245-188.pix.wmich.edu [141.218.245.188]) (authenticated bits=0) by mail.foolishgames.com (8.13.6/8.13.3) with ESMTP id k3JMFA6a038489 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Wed, 19 Apr 2006 18:15:12 -0400 (EDT) (envelope-from luke@foolishgames.com) Message-Id: <8CA9391D-6364-4C23-B68B-A2D6CAD383B4@foolishgames.com> X-Habeas-Swe-6: email in exchange for a license for this Habeas Content-Transfer-Encoding: 7bit X-Habeas-Swe-3: like Habeas SWE (tm) Date: Wed, 19 Apr 2006 18:15:04 -0400 X-Habeas-Swe-8: Message (HCM) and not spam. Please report use of this From: Lucas Holt X-Habeas-Swe-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-Swe-2: brightly anticipated In-Reply-To: <44467C60.8090708@centtech.com> References: <32575854.2582371145467129800.JavaMail.root@vms063.mailsrvcs.net> <20060419173315.GD24534@wjv.com> <44467C60.8090708@centtech.com> To: Eric Anderson X-Habeas-Swe-7: warrant mark warrants that this is a Habeas Compliant Mime-Version: 1.0 (Apple Message framework v749.3) X-Habeas-Swe-4: Copyright 2002 Habeas (tm) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed X-Habeas-Swe-1: winter into spring X-Habeas-Swe-9: mark in spam to . X-Mailer: Apple Mail (2.749.3) X-Virus-Scanned: ClamAV 0.88.1/1409/Wed Apr 19 17:02:41 2006 on mail.foolishgames.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 22:15:30 -0000 On Apr 19, 2006, at 2:07 PM, Eric Anderson wrote: > > Ok - first, let me remind everyone that this is for startup/ > shutdown of scripts and such, not for ls and other things. I'd > also like to remind everyone that the default for the whole thing > can be OFF, so you won't even know the option exists if you don't > want to know about it. If it is on, then the default is b/w like > the current setup is, and currently no information is suppressed so > there is no loss of helpful information on boot, only additional > information (OK, FAILED, SKIP, etc). > > If someone doesn't like the colors, doesn't like the 'fancy' > bootup, then they merely have to do nothing at all. > > This is a similar feature as rc_info is, and there's no issue > there, because it's off by default. Same with the color daemon at > the boot menu. > > I think it should be off by default, until enough people demand it > on (if that happens at all), and then it should be b/w by default, > with the option to make it color. My main goal was to implement > this with as little reworking of the current system as possible, > yet still reap rewards of easy readability when the system boots. > I hate to even suggest this, but perhaps we should add a desktop vs server option when installing freebsd. It wouldn't effect packages used, but might change a few defaults such as this new fancy startup. People using terminals and such would still get their black and white startup and everyone else would get the nice color startup. Anyone using a desktop or sys admins who have video cards in their servers and never tend to debug anything would like it. I think PC-BSD and DesktopBSD show there is a demand for FreeBSD on the desktop. It might be time we acknowledge that. Adding color doesn't minimize the "power to serve." As much as I love FreeBSD, sometimes its difficult to get others to try it simply because the project is so difficult about desktop usage. People often try out a new OS on a desktop before using it on production servers. Few people just risk it like I did a few years ago. In my case, I just didn't want linux. Lucas Holt Luke@FoolishGames.com ________________________________________________________ FoolishGames.com (Jewel Fan Site) JustJournal.com (Free blogging) FoolishGames.net (Enemy Territory site) From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 22:21:30 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A795316A407 for ; Wed, 19 Apr 2006 22:21:30 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F72443D46 for ; Wed, 19 Apr 2006 22:21:29 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (lm8f4hz32ud30v4j@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k3JMLQCc089768; Wed, 19 Apr 2006 15:21:26 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k3JMLPXT089764; Wed, 19 Apr 2006 15:21:25 -0700 (PDT) (envelope-from jmg) Date: Wed, 19 Apr 2006 15:21:25 -0700 From: John-Mark Gurney To: Kris Kennaway Message-ID: <20060419222125.GQ38619@funkthat.com> Mail-Followup-To: Kris Kennaway , Thomas SOETE , hackers@FreeBSD.org References: <44467768.2080809@soete.info> <20060419175651.GA71495@xor.obsecurity.org> <44467A6C.3070401@soete.info> <20060419180802.GA71717@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060419180802.GA71717@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: hackers@FreeBSD.org, Thomas SOETE Subject: Re: Kernel Fatal Trap 12 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 22:21:30 -0000 Kris Kennaway wrote this message on Wed, Apr 19, 2006 at 14:08 -0400: > On Wed, Apr 19, 2006 at 07:59:08PM +0200, Thomas SOETE wrote: > > Hum, is there a way to have a little idea of which hardware begun to fail ? > > Check CPU cooling, power supply, cabling, RAM, etc. Google for more - > this question is asked and answered about once a week. Just as a little bit of advice.. Make sure that there isn't dust in your cpu heat sink... and even if there isn't much dust, dust can cling to the blades of the heat sink preventing air flow and seriously limiting the ability of the heat sink to work... /me just had a computer randomly crash due to this. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 23:43:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EDDF16A400 for ; Wed, 19 Apr 2006 23:43:53 +0000 (UTC) (envelope-from bms@spc.org) Received: from mindfull.spc.org (mindfull.spc.org [83.167.185.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5820B43D55 for ; Wed, 19 Apr 2006 23:43:52 +0000 (GMT) (envelope-from bms@spc.org) Received: from arginine.spc.org ([83.167.185.2]) by mindfull.spc.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.52) id 1FWMKg-00028J-Iz; Thu, 20 Apr 2006 00:43:38 +0100 Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 2E19665499; Thu, 20 Apr 2006 00:43:44 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 79692-06-2; Thu, 20 Apr 2006 00:43:43 +0100 (BST) Received: by arginine.spc.org (Postfix, from userid 1078) id 43A8E653F9; Thu, 20 Apr 2006 00:43:43 +0100 (BST) Date: Thu, 20 Apr 2006 00:43:43 +0100 From: Bruce M Simpson To: cokane@cokane.org Message-ID: <20060419234343.GG28496@spc.org> Mail-Followup-To: Bruce M Simpson , cokane@cokane.org, Eric Anderson , freebsd-hackers@freebsd.org References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> <346a80220604190746n69a74a67te58599f743312cab@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <346a80220604190746n69a74a67te58599f743312cab@mail.gmail.com> User-Agent: Mutt/1.4.1i Organization: Incunabulum X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mindfull.spc.org X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - spc.org X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 23:43:53 -0000 On Wed, Apr 19, 2006 at 10:46:09AM -0400, Coleman Kane wrote: > My point is that we should let our purist values get in the way of others' > enhanced experience using the system. My view is: We take the patch, as long as it doesn't interfere with the internal machinations of rc too much. There are good aesthetic and functional arguments on either side. Given the excellent work on rc to date, we have clean abstractions in rc itself, so fitting colour-aesthetics in does not have a high maintenance cost. I agree strongly with the functional arguments however and think that this stuff shouldn't be turned on by default. I think that it should be available in the base system for those who wish it. I feel that this should be both for aesthetic reasons and for promoting FreeBSD to the ultimate end, that is, to potential users, who may find it easier to relate to FreeBSD if the console messages are in colour, no matter how irrational that may seem to some! Regards, BMS From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 19 23:57:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A02016A400 for ; Wed, 19 Apr 2006 23:57:57 +0000 (UTC) (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 1E55743D58 for ; Wed, 19 Apr 2006 23:57:56 +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 k3JNvqhK020580; Wed, 19 Apr 2006 16:57:52 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k3JNvq2i020573; Wed, 19 Apr 2006 16:57:52 -0700 Date: Wed, 19 Apr 2006 16:57:52 -0700 From: Brooks Davis To: Bruce M Simpson , cokane@cokane.org, Eric Anderson , freebsd-hackers@freebsd.org Message-ID: <20060419235752.GA19865@odin.ac.hmc.edu> References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> <346a80220604190746n69a74a67te58599f743312cab@mail.gmail.com> <20060419234343.GG28496@spc.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <20060419234343.GG28496@spc.org> 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 Cc: Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2006 23:57:57 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 20, 2006 at 12:43:43AM +0100, Bruce M Simpson wrote: > On Wed, Apr 19, 2006 at 10:46:09AM -0400, Coleman Kane wrote: > > My point is that we should let our purist values get in the way of othe= rs' > > enhanced experience using the system. >=20 > My view is: We take the patch, as long as it doesn't interfere with > the internal machinations of rc too much. >=20 > There are good aesthetic and functional arguments on either side. > Given the excellent work on rc to date, we have clean abstractions > in rc itself, so fitting colour-aesthetics in does not have a high > maintenance cost. I agree with this line of reasoning. So long as things are kept modular and don't cause maintance headaches when working on the internals I'd like to see this sort of work encouraged and encorporated into the tree. While there's something to be said for console output that shows everthing there's also something to be said for console output that only shows whats actually important. Giving people room to explore other options could yeild something much better than what we currently have. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFERs5/XY6L6fI4GtQRAmFJAJ4ghaAX5EL1CB9NGUwZlKQ0433PpACgh4/w 5Vu7kPtWX47/qg1wWoeBx4o= =grfs -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 00:16:46 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89F9216A401 for ; Thu, 20 Apr 2006 00:16:46 +0000 (UTC) (envelope-from gjb@gbch.net) Received: from gw.gbch.net (gw.gbch.net [203.143.238.93]) by mx1.FreeBSD.org (Postfix) with SMTP id 7D6B043D53 for ; Thu, 20 Apr 2006 00:16:40 +0000 (GMT) (envelope-from gjb@gbch.net) Received: (qmail 69470 invoked from network); 20 Apr 2006 10:16:37 +1000 Received: from iliad.gbch.net (172.16.1.9) by gw.gbch.net with SMTP; 20 Apr 2006 10:16:37 +1000 Received: (qmail 3927 invoked by uid 1001); 20 Apr 2006 10:16:34 +1000 Message-ID: Date: Thu, 20 Apr 2006 10:16:34 +1000 From: Greg Black To: Brooks Davis References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> <346a80220604190746n69a74a67te58599f743312cab@mail.gmail.com> <20060419234343.GG28496@spc.org> <20060419235752.GA19865@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060419235752.GA19865@odin.ac.hmc.edu> User-Agent: Mutt/1.4.2.1i; gjb-muttsend.sh 1.7 2004-10-05 X-Uptime: 49 days X-Operating-System: FreeBSD 6.0-RELEASE i386 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Blog: http://www.gbch.net/gjb/blog/ X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-PGP-Key-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-Request-PGP: http://www.gbch.net/keys/4B04B7D6.asc Cc: freebsd-hackers@freebsd.org, cokane@cokane.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 00:16:46 -0000 On 2006-04-19, Brooks Davis wrote: > On Thu, Apr 20, 2006 at 12:43:43AM +0100, Bruce M Simpson wrote: > > On Wed, Apr 19, 2006 at 10:46:09AM -0400, Coleman Kane wrote: > > > My point is that we should let our purist values get in the way of others' > > > enhanced experience using the system. > > > > My view is: We take the patch, as long as it doesn't interfere with > > the internal machinations of rc too much. > > > > There are good aesthetic and functional arguments on either side. > > Given the excellent work on rc to date, we have clean abstractions > > in rc itself, so fitting colour-aesthetics in does not have a high > > maintenance cost. > > I agree with this line of reasoning. So long as things are kept > modular and don't cause maintance headaches when working on the > internals I'd like to see this sort of work encouraged and encorporated > into the tree. While there's something to be said for console output > that shows everthing there's also something to be said for console > output that only shows whats actually important. Giving people room to > explore other options could yeild something much better than what we > currently have. Perhaps the default setup, while having all the pretty stuff turned off, could include one or two lines as close to the bottom of the output as possible that simply listed the new options so those who wanted them would know how to get the features and the rest of us would be gently reminded of what we were missing without damaging the output that we prefer. Greg From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 01:59:52 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FF8C16A402 for ; Thu, 20 Apr 2006 01:59:52 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from mail.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BA2F43D45 for ; Thu, 20 Apr 2006 01:59:51 +0000 (GMT) (envelope-from ota@j.email.ne.jp) Received: from dynabook-freebsd.advok.com (unknown [141.151.79.105]) by mail.asahi-net.or.jp (Postfix) with ESMTP id B5AA027EE1 for ; Thu, 20 Apr 2006 10:59:49 +0900 (JST) Date: Wed, 19 Apr 2006 21:59:48 -0500 From: Yoshihiro Ota To: freebsd-hackers@freebsd.org Message-Id: <20060419215948.8acfdf60.ota@j.email.ne.jp> X-Mailer: Sylpheed version 2.2.3 (GTK+ 2.8.16; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Is there compressed fs? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 01:59:52 -0000 Is there a compressed file system available in FreeBSD? I tried "mdconfig -ocompress" but it doesn't seem saving any spaces. Does anyone know what is the status of this, if it works, and if so, how it works? Thanks, Hiro From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 02:01:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B94816A401 for ; Thu, 20 Apr 2006 02:01:37 +0000 (UTC) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0218743D6D for ; Thu, 20 Apr 2006 02:01:31 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.13.6/8.13.1) with ESMTP id k3K21TSg028048; Wed, 19 Apr 2006 22:01:29 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.13.6/8.13.1/Submit) id k3K21NB9028047; Wed, 19 Apr 2006 22:01:23 -0400 (EDT) (envelope-from bv) Date: Wed, 19 Apr 2006 22:01:23 -0400 From: Bill Vermillion To: Mike Meyer Message-ID: <20060420020123.GC27835@wjv.com> References: <32575854.2582371145467129800.JavaMail.root@vms063.mailsrvcs.net> <17478.29723.209829.582135@bhuda.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17478.29723.209829.582135@bhuda.mired.org> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on bilver.wjv.com Cc: freebsd-hackers@freebsd.org, babkin@users.sourceforge.net Subject: Re: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 02:01:37 -0000 They all laughed on Wed, Apr 19, 2006 at 13:32 when Mike Meyer said: > In <32575854.2582371145467129800.JavaMail.root@vms063.mailsrvcs.net>, Sergey Babkin typed: > > >From: Bill Vermillion > > > > has some > > >color vision problem. Mine is a bit more than others. Everytime > > >I get called to work on a Linux system, I have to go in and disable > > >the colors as the reds and other colors become very hard to see > > >against a dark background. The problem is the luminance value of > > >colors such a red is quite low compared to others. > > The problem with Linux colors is that they have been > > designed to be used on the white background which is > > the xterm's default (and which I hate as it's tough > > on my eyes). Since I usually use the black background, > > I disable them too. > > So where do linux's blasted ls colors come from? It prints some file > type as green. Green on white is simply bad news, whether or not you > have vision problems. I always have to go disable them (and some linux > distros make them *hard* to disable). I just checked in on one Linux machine I admin - SuSE 9.2 - and the colors are set with the variable LS_OPTIONS. I've set LS_OPTIONS to '-N --color=none -T 0' And looking at the .bashrc there is also a test for the binary dircolors, and then looks for user files .dir_colors I also notice that as shipped the .bashrc has a comment line that says If LS_COLROS is set but empty the terminal has no colors. It is spelled COLROS not COLORS - but that's just cosmetic and sloppy. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 03:55:19 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85E3B16A402 for ; Thu, 20 Apr 2006 03:55:19 +0000 (UTC) (envelope-from MTaylor@bytecraft.com.au) Received: from wolf.bytecraft.au.com (wolf.bytecraft.au.com [203.39.118.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E07C443D49 for ; Thu, 20 Apr 2006 03:55:18 +0000 (GMT) (envelope-from MTaylor@bytecraft.com.au) Received: from localhost (localhost [127.0.0.1]) by wolf.bytecraft.au.com (8.12.11/8.12.11) with ESMTP id k3K3t2MB058001; Thu, 20 Apr 2006 13:55:02 +1000 (EST) (envelope-from MTaylor@bytecraft.com.au) Received: from wolf.bytecraft.au.com ([127.0.0.1]) by localhost (wolf.bytecraft.au.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 57643-02-3; Thu, 20 Apr 2006 03:55:02 +0000 (GMT) Received: from svmarshal.bytecraft.au.com ([10.0.0.4]) by wolf.bytecraft.au.com (8.12.11/8.12.11) with ESMTP id k3K3scnV057978; Thu, 20 Apr 2006 13:54:38 +1000 (EST) (envelope-from MTaylor@bytecraft.com.au) Received: from svmailmel.bytecraft.internal (Not Verified[10.0.0.24]) by svmarshal.bytecraft.au.com with MailMarshal (v5, 0, 3, 78) id ; Thu, 20 Apr 2006 13:54:37 +1000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Thu, 20 Apr 2006 13:54:40 +1000 Message-ID: <04E232FDCD9FBE43857F7066CAD3C0F111AF35@svmailmel.bytecraft.internal> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PATCH] Fancy rc startup style RFC Thread-Index: AcZkDS4ntY/YXgS/T5aJWR7FH4QOfQAARGYw From: "Murray Taylor" To: "Brooks Davis" , "Bruce M Simpson" , , "Eric Anderson" , Cc: Subject: RE: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 03:55:19 -0000 > -----Original Message----- > From: owner-freebsd-hackers@freebsd.org=20 > [mailto:owner-freebsd-hackers@freebsd.org] On Behalf Of Brooks Davis > Sent: Thursday, 20 April 2006 9:58 AM > To: Bruce M Simpson; cokane@cokane.org; Eric Anderson;=20 > freebsd-hackers@freebsd.org > Subject: Re: [PATCH] Fancy rc startup style RFC >=20 > On Thu, Apr 20, 2006 at 12:43:43AM +0100, Bruce M Simpson wrote: > > On Wed, Apr 19, 2006 at 10:46:09AM -0400, Coleman Kane wrote: > > > My point is that we should let our purist values get in=20 > the way of others' > > > enhanced experience using the system. > >=20 > > My view is: We take the patch, as long as it doesn't interfere with=20 > > the internal machinations of rc too much. > >=20 > > There are good aesthetic and functional arguments on either side. > > Given the excellent work on rc to date, we have clean=20 > abstractions in=20 > > rc itself, so fitting colour-aesthetics in does not have a high=20 > > maintenance cost. >=20 > I agree with this line of reasoning. So long as things are=20 > kept modular and don't cause maintance headaches when working=20 > on the internals I'd like to see this sort of work encouraged=20 > and encorporated into the tree. While there's something to=20 > be said for console output that shows everthing there's also=20 > something to be said for console output that only shows whats=20 > actually important. Giving people room to explore other=20 > options could yeild something much better than what we currently have. >=20 > -- Brooks My 0.02c worth - one of the Unix precepts for command line tools is silence =3D no error This is to consciously aid and abet the pipelining of programs.... Which is a major strength of Unix.. >From "The Art of Unix Programming" http://www.catb.org/~esr/writings/taoup/html/ch01s06.html#id2877684 Also http://www.catb.org/~esr/writings/taoup/html/ch11s01.html The whole site is a good read. And Albert speaks well too (see sig below) mjt -- "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein --------------------------------------------------------------- The information transmitted in this e-mail is for the exclusive use of the intended addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material.=20 E-mails may not be secure, may contain computer viruses and may be corrupted in transmission. Please carefully check this e-mail (and any attachment) accordingly. No warranties are given and no liability is accepted for any loss or damage caused by such matters. --------------------------------------------------------------- ***This Email has been scanned for Viruses by MailMarshal.*** From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 11:15:47 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A857216A403 for ; Thu, 20 Apr 2006 11:15:47 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from mail.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C9F443D45 for ; Thu, 20 Apr 2006 11:15:47 +0000 (GMT) (envelope-from ota@j.email.ne.jp) Received: from dynabook-freebsd.advok.com (pool-68-162-98-122.phil.east.verizon.net [68.162.98.122]) by mail.asahi-net.or.jp (Postfix) with ESMTP id 4523D28B03 for ; Thu, 20 Apr 2006 20:15:45 +0900 (JST) Date: Thu, 20 Apr 2006 07:15:44 -0500 From: Yoshihiro Ota To: freebsd-hackers@freebsd.org Message-Id: <20060420071544.68ff151d.ota@j.email.ne.jp> In-Reply-To: <20060419215948.8acfdf60.ota@j.email.ne.jp> References: <20060419215948.8acfdf60.ota@j.email.ne.jp> X-Mailer: Sylpheed version 2.2.3 (GTK+ 2.8.16; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Is there compressed fs? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 11:15:47 -0000 On Wed, 19 Apr 2006 21:59:48 -0500 Yoshihiro Ota wrote: > Is there a compressed file system available in FreeBSD? > > I tried "mdconfig -ocompress" but it doesn't seem saving any spaces. > Does anyone know what is the status of this, if it works, and if so, > how it works? Thanks to a couple of people who directly sent me a response. I was aware of GEOM_UZIP and mkuzip. However, the problem is it is read-only file system. I am looking for read-write compressed file system. Thanks, Hiro From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 05:12:20 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB79716A400 for ; Thu, 20 Apr 2006 05:12:20 +0000 (UTC) (envelope-from umka@sevcity.net) Received: from mail.sevcity.net (ns.sevcity.net [193.47.166.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id E129B43D46 for ; Thu, 20 Apr 2006 05:12:19 +0000 (GMT) (envelope-from umka@sevcity.net) Received: from mail.sevcity.net (service.sevcity [127.0.0.1]) by mail.sevcity.net (Postfix) with ESMTP id D0357170008; Thu, 20 Apr 2006 07:20:26 +0300 (EEST) Received: from berloga.shadowland (umka.sevcity.net [193.47.166.138]) by mail.sevcity.net (Postfix) with ESMTP id A3663170007; Thu, 20 Apr 2006 07:20:26 +0300 (EEST) Received: from berloga.shadowland (berloga.shadowland [127.0.0.1]) by berloga.shadowland (8.12.11.20060308/8.12.11) with ESMTP id k3K5CRfB003814; Thu, 20 Apr 2006 08:12:27 +0300 Received: (from root@localhost) by berloga.shadowland (8.12.11.20060308/8.12.11/Submit) id k3K5CQLV003812; Thu, 20 Apr 2006 08:12:26 +0300 From: Alex Lyashkov To: Yoshihiro Ota In-Reply-To: <20060419215948.8acfdf60.ota@j.email.ne.jp> References: <20060419215948.8acfdf60.ota@j.email.ne.jp> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Organization: SevcityNet Message-Id: <1145509946.3221.15.camel@berloga.shadowland> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-17) Date: Thu, 20 Apr 2006 08:12:26 +0300 X-Virus-Scanned: ClamAV using ClamSMTP X-Mailman-Approved-At: Thu, 20 Apr 2006 11:38:58 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Is there compressed fs? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 05:12:20 -0000 look into mkuzip and geom_uzip. =F7 =FE=D4=D7, 20.04.2006, =D7 05:59, Yoshihiro Ota =D0=C9=DB=C5=D4: > Is there a compressed file system available in FreeBSD? >=20 > I tried "mdconfig -ocompress" but it doesn't seem saving any spaces. > Does anyone know what is the status of this, if it works, and if so, > how it works? >=20 > Thanks, > Hiro > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 11:48:25 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0C4516A404 for ; Thu, 20 Apr 2006 11:48:24 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57BFF43D45 for ; Thu, 20 Apr 2006 11:48:24 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp2-g19.free.fr (Postfix) with ESMTP id 41BF2731BD for ; Thu, 20 Apr 2006 13:48:23 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 5390A9B950 for ; Thu, 20 Apr 2006 11:48:22 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 31512405B; Thu, 20 Apr 2006 13:48:22 +0200 (CEST) Date: Thu, 20 Apr 2006 13:48:22 +0200 From: Jeremie Le Hen To: freebsd-hackers@FreeBSD.org Message-ID: <20060420114822.GB35261@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Cc: Subject: Symbol weirdness with static linking X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 11:48:25 -0000 Hi hackers, I created a library (libssp) which is to be linked in the same time as libgcc (GCC's LIBGCC_SPEC [1]). This library is intended to provide the required symbols for ProPolice/SSP (Stack-Smashing Protector) which GCC references whenever it has to protect a function. This works almost perfectly but in one edge case : some programs are so "simple" (IOW have no stack-based buffer) that GCC does not feel the need to put any reference to the above symbols. For instance, bin/echo and bin/mkdir are such programs. When libssp is linked dynamically, this is not a problem. However, if I use NO_DYNAMICROOT when building world, ld(1) complains that it does not find the "syslog" symbol [2]. It happens that libssp uses syslog(3), but since libssp won't be in the resulting executable, I don't understand why ld(1) complains. OTOH, programs which do have a reference to ProPolice symbols compile without any problem. Even weirder, while there are other calls to libc functions in libssp - such as open(2), sigfillset(3) or sigprocmask(2) - if I comment out the call to syslog(3), ld(1) does not complain any longer. What is so special with libc's "syslog" symbol ? I don't understand what is the difference here between, the "syslog" symbol and, say, the "sigfilset" symbol (which is not used in echo(1) either). For the sake of completeness, I added the output of some objdump(1) outputs here : /usr/obj/usr/src/bin/echo/echo.o: http://tataz.chchile.org/~tataz/symbol_weirdness/objdump-t_echo.txt.gz /usr/obj/usr/src/tmp/usr/lib/libc.a: http://tataz.chchile.org/~tataz/symbol_weirdness/objdump-t_libc.txt.gz /usr/obj/usr/src/tmp/usr/lib/libssp.a: http://tataz.chchile.org/~tataz/symbol_weirdness/objdump-t_libssp.txt.gz Thank you. Regards, [1] #define LIBGCC_SPEC "%{shared: -lgcc_pic -lssp_pic} %{!shared: %{!pg: -lgcc -lssp} %{pg: -lgcc_p -lssp_p}}" [2] ===> bin/echo (all) cc -O2 -fno-strict-aliasing -pipe -march=pentium-m -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /usr/src/bin/echo/echo.c cc -O2 -fno-strict-aliasing -pipe -march=pentium-m -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -v -static -o echo echo.o Using built-in specs. Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 3.4.4 [FreeBSD] 20050518 /usr/obj/usr/src/tmp/usr/bin/ld -V -Bstatic -o echo /usr/obj/usr/src/tmp/usr/lib/crt1.o /usr/obj/usr/src/tmp/usr/lib/crti.o /usr/obj/usr/src/tmp/usr/lib/crtbegin.o -L/usr/obj/usr/src/tmp/usr/lib echo.o -lgcc -lssp -lc -lgcc -lssp /usr/obj/usr/src/tmp/usr/lib/crtend.o /usr/obj/usr/src/tmp/usr/lib/crtn.o GNU ld version 2.15 [FreeBSD] 2004-05-23 Supported emulations: elf_i386_fbsd /usr/obj/usr/src/tmp/usr/lib/libssp.a(ssp.o)(.text+0xe8): In function `__stack_smash_handler': : undefined reference to `syslog' *** Error code 1 -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 12:16:13 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4E6916A40E for ; Thu, 20 Apr 2006 12:16:13 +0000 (UTC) (envelope-from sico@loquefaltaba.com) Received: from mail.loquefaltaba.com (78.Red-213-96-97.staticIP.rima-tde.net [213.96.97.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B4FD43D49 for ; Thu, 20 Apr 2006 12:16:12 +0000 (GMT) (envelope-from sico@loquefaltaba.com) Received: from localhost (localhost.loquefaltaba.com [127.0.0.1]) by mail.loquefaltaba.com (Postfix) with ESMTP id CB08EC210; Thu, 20 Apr 2006 14:16:10 +0200 (CEST) Received: from mail.loquefaltaba.com ([127.0.0.1]) by localhost (sico.loquefaltaba.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60638-03; Thu, 20 Apr 2006 14:16:03 +0200 (CEST) Received: from webmail.loquefaltaba.com (localhost.loquefaltaba.com [127.0.0.1]) by mail.loquefaltaba.com (Postfix) with ESMTP id D3D83C1F4; Thu, 20 Apr 2006 14:16:02 +0200 (CEST) Received: from 194.179.68.110 (SquirrelMail authenticated user sico) by webmail.loquefaltaba.com with HTTP; Thu, 20 Apr 2006 14:16:02 +0200 (CEST) Message-ID: <32256.194.179.68.110.1145535362.squirrel@webmail.loquefaltaba.com> In-Reply-To: <44464BBF.5040801@centtech.com> References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> <44464BBF.5040801@centtech.com> Date: Thu, 20 Apr 2006 14:16:02 +0200 (CEST) From: "David Barbero" To: "Eric Anderson" User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at loquefaltaba.com Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC - v6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 12:16:13 -0000 Eric Anderson escribió: > > Thanks to Rick Petty for pointing me in the right direction (man page!), > here's the latest, and I think solid patch (for RELENG-6): > > > http://www.googlebit.com/freebsd/patches/rc_fancy.patch-6 > > > Eric > Hi all. I have found several anomalies operations in the patch. After to apply the patch, so that it works is necessary to put in rc.conf rc_fancy="YES ", when put this single entry, the system gives errors saying that correctly this entry in rc.conf is not correctly defined, adding single rc_fancy_color="YES" gives the same error. If the two entry meetings are added it don't show the error. I believe that serious advisable that these two entry did not depend the one on the other and worked separately. Another failure with which I have been is that after apply the patch and to take the normal system, without the entry rc_fancy * the system does not show such messages exactly, leave several points between the lines of the services. Ej: starting sendmail . . . starting apache and it would have to see itself of the following way: starting sendmail starting apache Another one of the failures that I have seen is that with this patch they show all the services, they are or not formed to start, I believe that single they would have to appear the services that are formed to start and not all those that can start. In addition the services that are not formed to start appear like [ OK ], in the case of appearing these, I believe that they would have to leave with another denomination that is not [ OK ]. Another failure that I have seen is that when leaving the message syslogd this sample failure, but this service starts without problems, but shows it as if it gave failure... In principle this is what I have seen at first sight on the patch. Regards. -- "Linux is for people who hate Windows, BSD is for people who love UNIX" "Social Engineer -> Because there is no patch for human stupidity" From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 12:48:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 205AA16A400 for ; Thu, 20 Apr 2006 12:48:38 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58C4943D46 for ; Thu, 20 Apr 2006 12:48:36 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k3KCmU33003464 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Apr 2006 15:48:30 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k3KCmUGY027175; Thu, 20 Apr 2006 15:48:30 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k3KCmT0G027174; Thu, 20 Apr 2006 15:48:29 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 20 Apr 2006 15:48:29 +0300 From: Kostik Belousov To: Jeremie Le Hen Message-ID: <20060420124829.GA1446@deviant.kiev.zoral.com.ua> References: <20060420114822.GB35261@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline In-Reply-To: <20060420114822.GB35261@obiwan.tataz.chchile.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on fw.zoral.com.ua Cc: freebsd-hackers@freebsd.org Subject: Re: Symbol weirdness with static linking X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 12:48:38 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 20, 2006 at 01:48:22PM +0200, Jeremie Le Hen wrote: > Hi hackers, >=20 > I created a library (libssp) which is to be linked in the same time as > libgcc (GCC's LIBGCC_SPEC [1]). This library is intended to provide the > required symbols for ProPolice/SSP (Stack-Smashing Protector) which GCC > references whenever it has to protect a function. >=20 > This works almost perfectly but in one edge case : some programs > are so "simple" (IOW have no stack-based buffer) that GCC does not > feel the need to put any reference to the above symbols. For instance, > bin/echo and bin/mkdir are such programs. >=20 > When libssp is linked dynamically, this is not a problem. However, if > I use NO_DYNAMICROOT when building world, ld(1) complains that it does not > find the "syslog" symbol [2]. It happens that libssp uses syslog(3), but > since libssp won't be in the resulting executable, I don't understand > why ld(1) complains. >=20 > OTOH, programs which do have a reference to ProPolice symbols compile > without any problem. >=20 > Even weirder, while there are other calls to libc functions in libssp > - such as open(2), sigfillset(3) or sigprocmask(2) - if I comment out > the call to syslog(3), ld(1) does not complain any longer. What is > so special with libc's "syslog" symbol ? I don't understand what is > the difference here between, the "syslog" symbol and, say, the "sigfilset" > symbol (which is not used in echo(1) either). >=20 > For the sake of completeness, I added the output of some objdump(1) > outputs here : >=20 > /usr/obj/usr/src/bin/echo/echo.o: > http://tataz.chchile.org/~tataz/symbol_weirdness/objdump-t_echo.txt.gz >=20 > /usr/obj/usr/src/tmp/usr/lib/libc.a: > http://tataz.chchile.org/~tataz/symbol_weirdness/objdump-t_libc.txt.gz >=20 > /usr/obj/usr/src/tmp/usr/lib/libssp.a: > http://tataz.chchile.org/~tataz/symbol_weirdness/objdump-t_libssp.txt.gz >=20 >=20 > Thank you. > Regards, >=20 >=20 > [1] > #define LIBGCC_SPEC "%{shared: -lgcc_pic -lssp_pic} %{!shared: %{!pg: -lg= cc -lssp} %{pg: -lgcc_p -lssp_p}}" >=20 >=20 > [2] > =3D=3D=3D> bin/echo (all) > cc -O2 -fno-strict-aliasing -pipe -march=3Dpentium-m -fstack-protector -W= system-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstr= ict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qu= al -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar= -subscripts -Winline -Wnested-externs -Wredundant-decls -c /usr/src/bin/ech= o/echo.c > cc -O2 -fno-strict-aliasing -pipe -march=3Dpentium-m -fstack-protector -W= system-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstr= ict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qu= al -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar= -subscripts -Winline -Wnested-externs -Wredundant-decls -v -static -o echo= echo.o > Using built-in specs. > Configured with: FreeBSD/i386 system compiler > Thread model: posix > gcc version 3.4.4 [FreeBSD] 20050518 > /usr/obj/usr/src/tmp/usr/bin/ld -V -Bstatic -o echo /usr/obj/usr/src/tmp= /usr/lib/crt1.o /usr/obj/usr/src/tmp/usr/lib/crti.o /usr/obj/usr/src/tmp/us= r/lib/crtbegin.o -L/usr/obj/usr/src/tmp/usr/lib echo.o -lgcc -lssp -lc -lgc= c -lssp /usr/obj/usr/src/tmp/usr/lib/crtend.o /usr/obj/usr/src/tmp/usr/lib/= crtn.o > GNU ld version 2.15 [FreeBSD] 2004-05-23 > Supported emulations: > elf_i386_fbsd > /usr/obj/usr/src/tmp/usr/lib/libssp.a(ssp.o)(.text+0xe8): In function `__= stack_smash_handler': > : undefined reference to `syslog' > *** Error code 1 >=20 > --=20 > Jeremie Le Hen > < jeremie at le-hen dot org >< ttz at chchile dot org > It seems that you rebuilt world with CFLAGS -fstack-protector, since your libc has references to the symbols like __stack_smash_handler. As result, when linking with sequence -lgcc -lssp -lc -lgcc -lssp, and no references from the main object, references from libc causes objects from _second_ instance of -lssp to be pulled into the link. Since libraries are scanned sequentially, this object from libssp has no way to get required dependencies from libc. What makes syslog(3) special is that corresponding object from libc, syslog.o, requires __stack_smash_handler, while objects for mentioned syscalls do not. Probably, another -lc after -lssp will change the situation. But I'm not sure would it be enough or not. --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFER4McC3+MBN1Mb4gRAg/VAJ977y4H+8itSlYH7oo3h+I1uS+83wCgjxvA 9EhCe+7c5mMah1+MeQynUAs= =s1qd -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l-- From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 13:17:34 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6533816A403 for ; Thu, 20 Apr 2006 13:17:34 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id F020243D45 for ; Thu, 20 Apr 2006 13:17:33 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp4-g19.free.fr (Postfix) with ESMTP id 3A2A254974; Thu, 20 Apr 2006 15:17:33 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 462919BD8D; Thu, 20 Apr 2006 13:17:32 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 2E74F405B; Thu, 20 Apr 2006 15:17:32 +0200 (CEST) Date: Thu, 20 Apr 2006 15:17:32 +0200 From: Jeremie Le Hen To: Kostik Belousov Message-ID: <20060420131732.GA68951@obiwan.tataz.chchile.org> References: <20060420114822.GB35261@obiwan.tataz.chchile.org> <20060420124829.GA1446@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060420124829.GA1446@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: [fbsd] Re: Symbol weirdness with static linking X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 13:17:34 -0000 Hi, Kostik, On Thu, Apr 20, 2006 at 03:48:29PM +0300, Kostik Belousov wrote: > It seems that you rebuilt world with CFLAGS -fstack-protector, > since your libc has references to the symbols like __stack_smash_handler. > As result, when linking with sequence -lgcc -lssp -lc -lgcc -lssp, > and no references from the main object, > references from libc causes objects from _second_ instance of -lssp to > be pulled into the link. Since libraries are scanned sequentially, > this object from libssp has no way to get required dependencies > from libc. > > What makes syslog(3) special is that corresponding object from libc, > syslog.o, requires __stack_smash_handler, while objects for mentioned > syscalls do not. > > Probably, another -lc after -lssp will change the situation. But > I'm not sure would it be enough or not. You got the point. If I add another -lc after the second -lssp, this solves the problem : /usr/bin/ld -V -Bstatic -o echo /usr/obj/usr/src/tmp/usr/lib/crt1.o /usr/obj/usr/src/tmp//usr/lib/crti.o /usr/obj/usr/src/tmp/usr/lib/crtbegin.o -L/usr/obj/usr/src/tmp/usr/lib echo.o -lgcc -lssp -lc /usr/obj/usr/src/tmp/usr/lib/crtend.o /usr/obj/usr/src/tmp/usr/lib/crtn.o Another way to solve this is to group libraries using "-(" and "-)" ld(1) options : /usr/bin/ld -V -Bstatic -o echo /usr/obj/usr/src/tmp/usr/lib/crt1.o /usr/obj/usr/src/tmp/usr/lib/crti.o /usr/obj/usr/src/tmp/usr/lib/crtbegin.o -L/usr/obj/usr/src/tmp/usr/lib echo.o -lgcc -lssp -\( -lc -lgcc -lssp -\) /usr/obj/usr/src/tmp/usr/lib/crtend.o /usr/obj/usr/src/tmp/usr/lib/crtn.o Thank you for your answer. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 13:25:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A17416A404 for ; Thu, 20 Apr 2006 13:25:57 +0000 (UTC) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2297C43D5A for ; Thu, 20 Apr 2006 13:25:55 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.13.6/8.13.1) with ESMTP id k3KDPrV8037463 for ; Thu, 20 Apr 2006 09:25:53 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.13.6/8.13.1/Submit) id k3KDPmj3037462 for freebsd-hackers@freebsd.org; Thu, 20 Apr 2006 09:25:48 -0400 (EDT) (envelope-from bv) Date: Thu, 20 Apr 2006 09:25:43 -0400 From: Bill Vermillion To: freebsd-hackers@freebsd.org Message-ID: <20060420132543.GB37150@wjv.com> References: <20060420035530.F1A5A16A4E0@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060420035530.F1A5A16A4E0@hub.freebsd.org> Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on bilver.wjv.com Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 13:25:57 -0000 While stranded on the shoulder of the Information Superhiway and trying to flag down some passing bytes freebsd-hackers-request@freebsd.org said "Bits don't fail me now", and continued with: > Date: Wed, 19 Apr 2006 13:03:57 -0400 > From: "Coleman Kane" > Subject: Re: [PATCH] Fancy rc startup style RFC > On 4/19/06, Mike Meyer wrote: > > In > > <346a80220604190900i3bfc3b54v93a4c6c30f0dfc4f@mail.gmail.com>, > > Coleman Kane typed: > > > On 4/19/06, Mike Meyer > > > > > How about we all discuss good choices for "default" colors? > > Depends on the goal: do you want the default to work for > > everyone, or do you want the default to be prettier and/or > > better for most people but absolutely suck for a few? > I was thinking perhaps of having a predefined set of templates > (with the option and documentation to add your own). Perhaps > implement one that creates the "traffic-light" style that seems > to make intuitive sense to many americans (Bold Red: error, Bold > Green: Success, Bold Yellow: warning/notice), and also have > another perdefined one that uses a different color set. "Traffic-light" style is also designed to be useable by completely color-blind people - which is rare. By that if you notice traffic lights are always in the same order, green, yellow, red so that all you have to do is be able to see the luminance value in the abscence of any chroma information.. That's the problem with web-sites which depend on chroma value, and often have colors which are easily discernable by normally sighted people, but the luminance is very close which can make things almost invisible. I have a noticed a traffic-sign problem which another person also wrote to the local newspaper - and the traffic division is looking to change the signs. In Florida bright days are indeed very bright. There are signs that use lights to spell out the message with what someone feels the most important part in 'red'. The signs have a black background. On a bright day I see "NO TURN ON " or "TO PEDS" as the word RED in the first message is invisible to me, and the YIELD in the second has the same effect. There is also a sign that I came up to that used the universal sign for turn. I started to turn and my wife had me stop because the circle with bar through it was in RED and I could not see it. On overcast days or at night these signs are easily viewable. For those of you who remember the late 1980s when IBM came out with OS/2 and MS came out with a new Windows, the complaints were the default screens on OS/2 were drab while the Windows had bright colors. IBM is very good at designing things for people with disabilites and the OS/2 default screen was designed to be readable by someone with total color-blindness - which as I said is rare. The way to check if a web-site is readable by all it to use a monochrome monitor [ exceedingly hard to find nowdays ], and at least some government sites are now required to be that way. Color can be a great way to emphasize items >IF< the chroma and luminance values are carefully chosen. If not you can take away a lot of functionality. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 14:12:58 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B27716A403 for ; Thu, 20 Apr 2006 14:12:58 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: from mired.org (dsl092-153-074.wdc2.dsl.speakeasy.net [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 8BC5C43D4C for ; Thu, 20 Apr 2006 14:12:56 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 24128 invoked by uid 1001); 20 Apr 2006 14:12:49 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Thu, 20 Apr 2006 10:12:49 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17479.38625.63752.211932@bhuda.mired.org> Date: Thu, 20 Apr 2006 10:12:49 -0400 To: bv@wjv.com In-Reply-To: <20060420132543.GB37150@wjv.com> References: <20060420035530.F1A5A16A4E0@hub.freebsd.org> <20060420132543.GB37150@wjv.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 14:12:58 -0000 In <20060420132543.GB37150@wjv.com>, Bill Vermillion typed: > The way to check if a web-site is readable by all it to use > a monochrome monitor [ exceedingly hard to find nowdays ], and > at least some government sites are now required to be that way. This is part of "section 508", and *all* web sites run by organizations that receive US government monies are supposed to comply with it. The government doesn't do a lot to enforce this, though. FWIW, the last time I checked, the question of whether or not a web site that wasn't covered by section 508 was covered by the ADA was still up in the air, hinging on whether or not a web site constituted a "public place" (but it's been a while since I checked). http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 16:36:22 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 117AA16A405 for ; Thu, 20 Apr 2006 16:36:22 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0190D43D5A for ; Thu, 20 Apr 2006 16:36:19 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k3KGaIFW025134; Thu, 20 Apr 2006 11:36:18 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4447B876.4010606@centtech.com> Date: Thu, 20 Apr 2006 11:36:06 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: David Barbero References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> <44464BBF.5040801@centtech.com> <32256.194.179.68.110.1145535362.squirrel@webmail.loquefaltaba.com> In-Reply-To: <32256.194.179.68.110.1145535362.squirrel@webmail.loquefaltaba.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.87.1/1409/Wed Apr 19 16:02:41 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC - v6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 16:36:22 -0000 David Barbero wrote: > Eric Anderson escribió: >> Thanks to Rick Petty for pointing me in the right direction (man page!), >> here's the latest, and I think solid patch (for RELENG-6): >> >> >> http://www.googlebit.com/freebsd/patches/rc_fancy.patch-6 >> >> >> Eric >> > > Hi all. > > I have found several anomalies operations in the patch. > > After to apply the patch, so that it works is necessary to put in rc.conf > rc_fancy="YES ", when put this single entry, the system gives errors > saying that correctly this entry in rc.conf is not correctly defined, > adding single rc_fancy_color="YES" gives the same error. > If the two entry meetings are added it don't show the error. > I believe that serious advisable that these two entry did not depend the > one on the other and worked separately. Well, obviously the _color option depends on the rc_fancy option being enabled, otherwise it doesn't make sense, however you can of course have rc_fancy enabled with rc_fancy_color disabled. > Another failure with which I have been is that after apply the patch and > to take the normal system, without the entry rc_fancy * the system does > not show such messages exactly, leave several points between the lines of > the services. > Ej: > starting sendmail > . > . > . > starting apache > > and it would have to see itself of the following way: > > starting sendmail > starting apache Yep, that's a bug. I think it's fixed in v7, available here: http://www.googlebit.com/freebsd/patches/rc_fancy.patch-7 along with a few other suggestions from others. > Another one of the failures that I have seen is that with this patch they > show all the services, they are or not formed to start, I believe that > single they would have to appear the services that are formed to start and > not all those that can start. If the service is run on bootup, it shows it. It was still being run before, there was just no output previously. It would be pretty easy to have an option to not print these, maybe an rc_fancy_verbose option. Is this desirable to most? > In addition the services that are not formed to start appear like [ OK ], > in the case of appearing these, I believe that they would have to leave > with another denomination that is not [ OK ]. I'm not sure what you mean here. Can you give me an example? > Another failure that I have seen is that when leaving the message syslogd > this sample failure, but this service starts without problems, but shows > it as if it gave failure... My syslogd looks clean, and doesn't give a false failure. I'm not sure how to look into this - can you confirm that it truly is passing, but giving the wrong message, or is it that the rc subsystem thinks it's failing but appears to work ok? > In principle this is what I have seen at first sight on the patch. Thanks for all the feedback and testing! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 17:49:53 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 494EC16A400 for ; Thu, 20 Apr 2006 17:49:53 +0000 (UTC) (envelope-from paul.halliday@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id D99AD43D48 for ; Thu, 20 Apr 2006 17:49:52 +0000 (GMT) (envelope-from paul.halliday@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so210950nzp for ; Thu, 20 Apr 2006 10:49:52 -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=pGwTZ8xWqB45FImLaFD3ifQuvCbV0wpqyZjtJk5NhkqRGhLPPuRBLz89QTaMRcDfBH9GarGKE0uRFNRYCz01zx5pPyV8fDZ06Nixfj6afFsbQ0EtdzZAftf0rHEyRSEdf9QmPGhNrO4iXspxHZDAwzS5dDqV/bf+arWMOOXL1nU= Received: by 10.65.75.2 with SMTP id c2mr522924qbl; Thu, 20 Apr 2006 10:49:51 -0700 (PDT) Received: by 10.65.151.18 with HTTP; Thu, 20 Apr 2006 10:49:51 -0700 (PDT) Message-ID: <2dab70a30604201049i41e409e1y8924383843c95980@mail.gmail.com> Date: Thu, 20 Apr 2006 14:49:51 -0300 From: "Paul Halliday" To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: Server choice. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 17:49:53 -0000 Hi, I am in the process of building a new database server and after pricing up 2 Dell models I thought I would throw this out just to see which choice would be better suited for FreeBSD. The demands on the system will be mostly network -> disk I/O with a hope of best performance on quickly servicing numerous reads; for example when reports are generated using the data in the database. The 2 choices (we dont have that much money and they have to be Dell) are a poweredge 1850 and a poweredge 850. 850 specs. ---------------- Procsesor: Pentium(Dual Core) 830 @ 3.0GHz/2X1MB Cache 800MHz FSB Memory: 2GB DDR2, 533MHz (2x1GB) Dual ranked DIMMs Disks: SATA 1850 specs. ------------------ Processors: 2 @ Xeon @ 3.0GHz/2MB Cache 800MHz FSB Memory: 2GB DDR2, 400MHz (4x512) Single ranked DIMMs Disks: Ultra 320 The pricing is really close. Thanks. From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 18:08:56 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 407A016A400 for ; Thu, 20 Apr 2006 18:08:56 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDBB243D46 for ; Thu, 20 Apr 2006 18:08:55 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k3KI8s7Q027898; Thu, 20 Apr 2006 13:08:54 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4447CE2A.1040603@centtech.com> Date: Thu, 20 Apr 2006 13:08:42 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Paul Halliday References: <2dab70a30604201049i41e409e1y8924383843c95980@mail.gmail.com> In-Reply-To: <2dab70a30604201049i41e409e1y8924383843c95980@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1409/Wed Apr 19 16:02:41 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: hackers@freebsd.org Subject: Re: Server choice. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 18:08:56 -0000 Paul Halliday wrote: > Hi, > > I am in the process of building a new database server and after > pricing up 2 Dell models I thought I would throw this out just to see > which choice would be better suited for FreeBSD. > > The demands on the system will be mostly network -> disk I/O with a > hope of best performance on quickly servicing numerous reads; for > example when reports are generated using the data in the database. > > The 2 choices (we dont have that much money and they have to be Dell) > are a poweredge 1850 and a poweredge 850. > > 850 specs. > ---------------- > Procsesor: Pentium(Dual Core) 830 @ 3.0GHz/2X1MB Cache 800MHz FSB > Memory: 2GB DDR2, 533MHz (2x1GB) Dual ranked DIMMs > Disks: SATA > > 1850 specs. > ------------------ > Processors: 2 @ Xeon @ 3.0GHz/2MB Cache 800MHz FSB > Memory: 2GB DDR2, 400MHz (4x512) Single ranked DIMMs > Disks: Ultra 320 > > The pricing is really close. I'm not sure the type of memory<->cpu utilization that mysql will do, however I can tell you that in a number of applications that do lots of cpu cache utilization, the 2x Xeon will knock over the dual-core. I'd go with the 1850 (we have stacks of these in house). Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 18:29:25 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B71F16A400 for ; Thu, 20 Apr 2006 18:29:25 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19F1043D4C for ; Thu, 20 Apr 2006 18:29:24 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k3KITNnn028986; Thu, 20 Apr 2006 13:29:23 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4447D2F7.1070408@centtech.com> Date: Thu, 20 Apr 2006 13:29:11 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: bv@wjv.com References: <20060420035530.F1A5A16A4E0@hub.freebsd.org> <20060420132543.GB37150@wjv.com> In-Reply-To: <20060420132543.GB37150@wjv.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1409/Wed Apr 19 16:02:41 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 18:29:25 -0000 Bill Vermillion wrote: > While stranded on the shoulder of the Information > Superhiway and trying to flag down some passing bytes > freebsd-hackers-request@freebsd.org said "Bits don't fail me now", > and continued with: > >> Date: Wed, 19 Apr 2006 13:03:57 -0400 >> From: "Coleman Kane" >> Subject: Re: [PATCH] Fancy rc startup style RFC > >> On 4/19/06, Mike Meyer wrote: > >>> In >>> <346a80220604190900i3bfc3b54v93a4c6c30f0dfc4f@mail.gmail.com>, >>> Coleman Kane typed: > >>>> On 4/19/06, Mike Meyer >>>> >>>> How about we all discuss good choices for "default" colors? > >>> Depends on the goal: do you want the default to work for >>> everyone, or do you want the default to be prettier and/or >>> better for most people but absolutely suck for a few? > >> I was thinking perhaps of having a predefined set of templates >> (with the option and documentation to add your own). Perhaps >> implement one that creates the "traffic-light" style that seems >> to make intuitive sense to many americans (Bold Red: error, Bold >> Green: Success, Bold Yellow: warning/notice), and also have >> another perdefined one that uses a different color set. > > "Traffic-light" style is also designed to be useable by completely > color-blind people - which is rare. By that if you notice traffic > lights are always in the same order, green, yellow, red so that all > you have to do is be able to see the luminance value in the > abscence of any chroma information.. > > That's the problem with web-sites which depend on chroma value, and > often have colors which are easily discernable by normally sighted > people, but the luminance is very close which can make things > almost invisible. > > I have a noticed a traffic-sign problem which another person also > wrote to the local newspaper - and the traffic division is looking > to change the signs. > > In Florida bright days are indeed very bright. There are signs > that use lights to spell out the message with what someone feels > the most important part in 'red'. The signs have a black > background. > > On a bright day I see "NO TURN ON " or "TO PEDS" as > the word RED in the first message is invisible to me, and > the YIELD in the second has the same effect. > > There is also a sign that I came up to that used the universal > sign for turn. I started to turn and my wife had me stop because > the circle with bar through it was in RED and I could not see it. > > On overcast days or at night these signs are easily viewable. > > For those of you who remember the late 1980s when IBM came out with > OS/2 and MS came out with a new Windows, the complaints were the > default screens on OS/2 were drab while the Windows had bright > colors. IBM is very good at designing things for people with > disabilites and the OS/2 default screen was designed to be readable > by someone with total color-blindness - which as I said is rare. > > The way to check if a web-site is readable by all it to use > a monochrome monitor [ exceedingly hard to find nowdays ], and > at least some government sites are now required to be that way. > > Color can be a great way to emphasize items >IF< the chroma > and luminance values are carefully chosen. If not you can take > away a lot of functionality. Bill - thanks for all the info here. I feel it's important for this to work for users with all kinds of vision differences, so can you confirm (or not) whether the b/w version (rc_fancy="YES", but rc_fancy_color="NO") looks readable to you? (please use patch 7) Thanks! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 21:42:19 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C2D316A401 for ; Thu, 20 Apr 2006 21:42:19 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from linda-5.paradise.net.nz (bm-5a.paradise.net.nz [203.96.152.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61B3B43D48 for ; Thu, 20 Apr 2006 21:42:15 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-3.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-5.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IY100BPMIYDL0@linda-5.paradise.net.nz> for hackers@freebsd.org; Fri, 21 Apr 2006 09:42:14 +1200 (NZST) Received: from [192.168.1.11] (218-101-29-147.dsl.clear.net.nz [218.101.29.147]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id 824A6101211E; Fri, 21 Apr 2006 09:42:13 +1200 (NZST) Date: Fri, 21 Apr 2006 09:42:02 +1200 From: Mark Kirkwood In-reply-to: <2dab70a30604201049i41e409e1y8924383843c95980@mail.gmail.com> To: Paul Halliday Message-id: <4448002A.50208@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit User-Agent: Thunderbird 1.5 (X11/20060417) References: <2dab70a30604201049i41e409e1y8924383843c95980@mail.gmail.com> Cc: hackers@freebsd.org Subject: Re: Server choice. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 21:42:19 -0000 Paul Halliday wrote: > Hi, > > I am in the process of building a new database server and after > pricing up 2 Dell models I thought I would throw this out just to see > which choice would be better suited for FreeBSD. > > The demands on the system will be mostly network -> disk I/O with a > hope of best performance on quickly servicing numerous reads; for > example when reports are generated using the data in the database. > > The 2 choices (we dont have that much money and they have to be Dell) > are a poweredge 1850 and a poweredge 850. > > 850 specs. > ---------------- > Procsesor: Pentium(Dual Core) 830 @ 3.0GHz/2X1MB Cache 800MHz FSB > Memory: 2GB DDR2, 533MHz (2x1GB) Dual ranked DIMMs > Disks: SATA > > 1850 specs. > ------------------ > Processors: 2 @ Xeon @ 3.0GHz/2MB Cache 800MHz FSB > Memory: 2GB DDR2, 400MHz (4x512) Single ranked DIMMs > Disks: Ultra 320 > > The pricing is really close. Typically for a database server, the IO system is the most important single component. Unfortunately this is often the component that is skimped on for budget vendor boxes. See if you can find out the details for the SATA and SCSI controllers (the SATA particularly as there are crappy controllers out there that will just be a misery if you get lumbered with them). I ran Dell servers a few years ago and liked them - but recently switched to using Supermicro, as the quality of the more modern Dell boxes seems to be ...err... shall we say, 'decreased' :-). cheers Mark From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 22:16:26 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B62116A406 for ; Thu, 20 Apr 2006 22:16:26 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F53543D48 for ; Thu, 20 Apr 2006 22:16:25 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp5-g19.free.fr (Postfix) with ESMTP id 82FCA24D65; Fri, 21 Apr 2006 00:16:24 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 4A9439BEC1; Thu, 20 Apr 2006 22:16:23 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 35CDC405D; Fri, 21 Apr 2006 00:16:23 +0200 (CEST) Date: Fri, 21 Apr 2006 00:16:23 +0200 From: Jeremie Le Hen To: Kostik Belousov Message-ID: <20060420221623.GD68951@obiwan.tataz.chchile.org> References: <20060420114822.GB35261@obiwan.tataz.chchile.org> <20060420124829.GA1446@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060420124829.GA1446@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: [fbsd] Re: Symbol weirdness with static linking X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 22:16:26 -0000 Hi, Kostik, > > For the sake of completeness, I added the output of some objdump(1) > > outputs here : > > > > /usr/obj/usr/src/bin/echo/echo.o: > > http://tataz.chchile.org/~tataz/symbol_weirdness/objdump-t_echo.txt.gz > > > > /usr/obj/usr/src/tmp/usr/lib/libc.a: > > http://tataz.chchile.org/~tataz/symbol_weirdness/objdump-t_libc.txt.gz > > > > /usr/obj/usr/src/tmp/usr/lib/libssp.a: > > http://tataz.chchile.org/~tataz/symbol_weirdness/objdump-t_libssp.txt.gz > > It seems that you rebuilt world with CFLAGS -fstack-protector, > since your libc has references to the symbols like __stack_smash_handler. > As result, when linking with sequence -lgcc -lssp -lc -lgcc -lssp, > and no references from the main object, > references from libc causes objects from _second_ instance of -lssp to > be pulled into the link. Since libraries are scanned sequentially, > this object from libssp has no way to get required dependencies > from libc. Yes, I understand that. But I can't see what's the difference between "syslog" and "sigfillset" symbols from this standpoint. The fact the former requires ProPolice/SSP doesn't interfere IMHO. > What makes syslog(3) special is that corresponding object from libc, > syslog.o, requires __stack_smash_handler, while objects for mentioned > syscalls do not. How does it prevent the "syslog" symbol from being found ? Libc undefined symbols implies the second libssp to be pulled in which in turn has undefined symbol. But since there is no more libc after this, "sigfillset" should be missing either. I would understand if echo.o needed some symbols provided by the same archive than "sigfillset" (sigsetops.o) but this is not the case. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 20 22:40:54 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CC3616A400; Thu, 20 Apr 2006 22:40:54 +0000 (UTC) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (goofy.demon.nl [83.160.134.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13CC243D46; Thu, 20 Apr 2006 22:40:53 +0000 (GMT) (envelope-from marco@goofy.tols.org) Received: from goofy.tols.org (localhost [127.0.0.1]) by goofy.tols.org (8.13.4/8.13.4) with ESMTP id k3KMenFN099465; Thu, 20 Apr 2006 22:40:49 GMT (envelope-from marco@goofy.tols.org) Received: (from marco@localhost) by goofy.tols.org (8.13.4/8.13.4/Submit) id k3KMenj6099464; Fri, 21 Apr 2006 00:40:49 +0200 (CEST) (envelope-from marco) Date: Fri, 21 Apr 2006 00:40:49 +0200 From: Marco van Tol To: freebsd-hackers@freebsd.org Message-ID: <20060420224049.GA99399@tols.org> Mail-Followup-To: freebsd-hackers@freebsd.org, John Baldwin References: <20060412215021.GB1146@tols.org> <20060417134825.GA47043@tols.org> <20060418221505.GC58081@tols.org> <200604181838.27713.jhb@freebsd.org> <20060419072627.GA66012@tols.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060419072627.GA66012@tols.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV 0.88.1/1410/Thu Apr 20 17:49:52 2006 on goofy.tols.org X-Virus-Status: Clean X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on goofy.tols.org Cc: Subject: Re: Per CPU cpu-statistics under SMP X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2006 22:40:54 -0000 On Wed, Apr 19, 2006 at 07:26:27AM +0000, Marco van Tol wrote: > On Tue, Apr 18, 2006 at 06:38:26PM -0400, John Baldwin wrote: [...] > > Ah, hmm. On 6.x we don't have per-thread stat ticks yet, which is > > probably why it is failing. It also isn't safe to move sched_lock > > down either on 6.x. You can still apply the rest of the patch by > > hand, just leave the 'mtx_lock_spin(&sched_lock)' where it is and > > change all the 'cp_time[FOO]++' to 'PCPU_LAZY_INC(cp_time[FOO])'. > > OK, thanks. > > What I will do is replace my gentoo partition with a BSD current partition > so I don't loose my workstation as it were, and use that to work on this. > > Will let you know how that goes. Thanks. Ha! It succeeded. :) For additional information: - I'm running an Athlon64 X2 4200+ in 64bit mode. (I won't start about the nvidia controller it also has ;) - I'm using the SCHED_ULE scheduler (Does that make a difference for this?) - All patching took place against todays CURRENT. - I manually patched the first hunk of kern_clock.c, as the rest of the hunks succeeded on their own. (Hadn't used .rej files much before, but they're very usefull :) Thank you very much! I think this should suffice for what I intend to do to gkrellm for now. If you want any additional information from me, or if you want me to test other patches, I'd be more then happy to supply/try it/them. Here's the result: -----< cut here >----- 1:0[marco@donald marco]sysctl hw.ncpu hw.ncpu: 2 -----< cut here >----- 1:0[marco@donald marco]for (( i = 0 ; $i < 10 ; i++ )) ; do sysctl kern.pcpu_time kern.cp_time ; sleep 1 ; echo -- ; done kern.pcpu_time: 156 0 397 225 20542 21 0 30 0 21259 kern.cp_time: 177 0 427 225 41801 -- kern.pcpu_time: 156 0 397 225 20675 21 0 30 0 21392 kern.cp_time: 177 0 427 225 42067 -- kern.pcpu_time: 157 0 398 225 20807 21 0 30 0 21526 kern.cp_time: 178 0 428 225 42333 -- kern.pcpu_time: 157 0 398 225 20940 21 0 30 0 21659 kern.cp_time: 178 0 428 225 42599 -- kern.pcpu_time: 157 0 398 225 21074 21 0 30 0 21793 kern.cp_time: 178 0 428 225 42867 -- kern.pcpu_time: 157 0 398 225 21207 21 0 30 0 21926 kern.cp_time: 178 0 428 225 43133 -- kern.pcpu_time: 157 0 398 225 21340 21 0 30 0 22059 kern.cp_time: 178 0 428 225 43399 -- kern.pcpu_time: 157 0 399 225 21473 21 0 30 0 22193 kern.cp_time: 178 0 429 225 43666 -- kern.pcpu_time: 157 0 399 225 21606 21 0 30 0 22326 kern.cp_time: 178 0 429 225 43932 -- kern.pcpu_time: 157 0 399 225 21740 21 0 30 0 22460 kern.cp_time: 178 0 429 225 44200 -- 0:0[marco@donald marco] -----< cut here >----- Marco -- The difference between theory and practice is a lot bigger in practice then in theory - Peter van der Linden in `Deep C Secrets' From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 21 03:32:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D54416A402 for ; Fri, 21 Apr 2006 03:32:49 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E899343D46 for ; Fri, 21 Apr 2006 03:32:48 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k3L3Wkxo052078; Thu, 20 Apr 2006 22:32:46 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44485251.9050303@centtech.com> Date: Thu, 20 Apr 2006 22:32:33 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: cokane@cokane.org References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> <44464BBF.5040801@centtech.com> <32256.194.179.68.110.1145535362.squirrel@webmail.loquefaltaba.com> <4447B876.4010606@centtech.com> <346a80220604202019g3e3aaea5lfe19bcabaaf65c1d@mail.gmail.com> In-Reply-To: <346a80220604202019g3e3aaea5lfe19bcabaaf65c1d@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1411/Thu Apr 20 17:23:28 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC - v6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2006 03:32:49 -0000 Coleman Kane wrote: > On 4/20/06, *Eric Anderson* > wrote: > > David Barbero wrote: > > > --- snip --- > > Yep, that's a bug. I think it's fixed in v7, available here: > > http://www.googlebit.com/freebsd/patches/rc_fancy.patch-7 > > along with a few other suggestions from others. > > > > Another one of the failures that I have seen is that with this > patch they > > show all the services, they are or not formed to start, I believe > that > > single they would have to appear the services that are formed to > start and > > not all those that can start. > > If the service is run on bootup, it shows it. It was still being run > before, there was just no output previously. It would be pretty easy to > have an option to not print these, maybe an rc_fancy_verbose option. Is > this desirable to most? > > > In addition the services that are not formed to start appear > like [ OK ], > > in the case of appearing these, I believe that they would have to > leave > > with another denomination that is not [ OK ]. > > > I'm not sure what you mean here. Can you give me an example? > > > > Another failure that I have seen is that when leaving the message > syslogd > > this sample failure, but this service starts without problems, > but shows > > it as if it gave failure... > > My syslogd looks clean, and doesn't give a false failure. I'm not sure > how to look into this - can you confirm that it truly is passing, but > giving the wrong message, or is it that the rc subsystem thinks it's > failing but appears to work ok? > > > > In principle this is what I have seen at first sight on the patch. > > > Thanks for all the feedback and testing! > > > Eric > > > I have modified the patch as follows: > > Made a bunch of the settings tunable by the user (message text and field > widths). > > It is availalbe at http://www.cokane.org/files/rc_fancy-cokane2.patch This looks good. I only wonder about two things now: - Should we also have a line for the actual colors used too? Or is that going too crazy? - Does it meet style(9)? I'm wondering about line lengths now. Other than that, do we have general consensus that these do what they claim? Any outstanding issues that haven't been addressed? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 21 03:47:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F47D16A400 for ; Fri, 21 Apr 2006 03:47:27 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70B8043D46 for ; Fri, 21 Apr 2006 03:47:26 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so64602nfc for ; Thu, 20 Apr 2006 20:47:25 -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:references; b=bsOlIfiVDaGL+PFH/jqGbxs8kgFamgRGu5PPEToXox6rJEeWG0RsWdt73LQbbBnrQtCF1AyO41nnmSVpT5ILyBjWZPaqymQM7/52jXk+w5/MXuexFM/dE9MVo7LXF0xIhWOlH9N7f2U1mtQcUy4apFkO/L2smAgaKgjBrlQseww= Received: by 10.49.54.17 with SMTP id g17mr986214nfk; Thu, 20 Apr 2006 20:41:06 -0700 (PDT) Received: by 10.48.217.6 with HTTP; Thu, 20 Apr 2006 20:41:06 -0700 (PDT) Message-ID: <346a80220604202041o7d631f43rbde4c84b5f7b16b4@mail.gmail.com> Date: Thu, 20 Apr 2006 23:41:06 -0400 From: "Coleman Kane" To: "Eric Anderson" In-Reply-To: <44485251.9050303@centtech.com> MIME-Version: 1.0 References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> <44464BBF.5040801@centtech.com> <32256.194.179.68.110.1145535362.squirrel@webmail.loquefaltaba.com> <4447B876.4010606@centtech.com> <346a80220604202019g3e3aaea5lfe19bcabaaf65c1d@mail.gmail.com> <44485251.9050303@centtech.com> 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: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC - v6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2006 03:47:27 -0000 On 4/20/06, Eric Anderson wrote: > > Coleman Kane wrote: > > > > I have modified the patch as follows: > > > > Made a bunch of the settings tunable by the user (message text and fiel= d > > widths). > > > > It is availalbe at http://www.cokane.org/files/rc_fancy-cokane2.patch > > > This looks good. I only wonder about two things now: > > - Should we also have a line for the actual colors used too? Or is that > going too crazy? Definately... I think having the ability to specify colorsets as profiles will be a must-have. Read the LSCOLORS description in ls(1). - Does it meet style(9)? I'm wondering about line lengths now. One unfortunate thing about /bin/sh: [from the sh(1) manpage] Only one of the -e and -n options may be specified. This means that we may not be able to use the -n to chain multiple echos on one line... Other than that, do we have general consensus that these do what they > claim? Any outstanding issues that haven't been addressed? > > > Eric --coleman From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 21 04:14:21 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1468116A400 for ; Fri, 21 Apr 2006 04:14:21 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BB3C43D45 for ; Fri, 21 Apr 2006 04:14:20 +0000 (GMT) (envelope-from zombyfork@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so71045nfc for ; Thu, 20 Apr 2006 21:14:19 -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:references; b=Z7U0n9X6WsAVnJGg5GSA4rV5IX1RskTJcexnb6R989eOKQuHREPJU6cZSab8M69h9F3O1Jclf/g7ztd4RRfLq/J3mNWtaObMjTDqFA6ASNmB4r5utZu/DH3Os6JMzmkrcbFNb/1m7w2jpqhj3adLX1cBoF2P7cDZyUIdDZLdR2U= Received: by 10.49.54.17 with SMTP id g17mr977517nfk; Thu, 20 Apr 2006 20:19:50 -0700 (PDT) Received: by 10.48.217.6 with HTTP; Thu, 20 Apr 2006 20:19:50 -0700 (PDT) Message-ID: <346a80220604202019g3e3aaea5lfe19bcabaaf65c1d@mail.gmail.com> Date: Thu, 20 Apr 2006 23:19:50 -0400 From: "Coleman Kane" To: "Eric Anderson" In-Reply-To: <4447B876.4010606@centtech.com> MIME-Version: 1.0 References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> <44464BBF.5040801@centtech.com> <32256.194.179.68.110.1145535362.squirrel@webmail.loquefaltaba.com> <4447B876.4010606@centtech.com> 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: freebsd-hackers@freebsd.org, David Barbero Subject: Re: [PATCH] Fancy rc startup style RFC - v6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2006 04:14:21 -0000 On 4/20/06, Eric Anderson wrote: > > David Barbero wrote: > > > --- snip --- > Yep, that's a bug. I think it's fixed in v7, available here: > > http://www.googlebit.com/freebsd/patches/rc_fancy.patch-7 > > along with a few other suggestions from others. > > > > Another one of the failures that I have seen is that with this patch > they > > show all the services, they are or not formed to start, I believe that > > single they would have to appear the services that are formed to start > and > > not all those that can start. > > If the service is run on bootup, it shows it. It was still being run > before, there was just no output previously. It would be pretty easy to > have an option to not print these, maybe an rc_fancy_verbose option. Is > this desirable to most? > > > In addition the services that are not formed to start appear like [ OK > ], > > in the case of appearing these, I believe that they would have to leave > > with another denomination that is not [ OK ]. > > > I'm not sure what you mean here. Can you give me an example? > > > > Another failure that I have seen is that when leaving the message > syslogd > > this sample failure, but this service starts without problems, but show= s > > it as if it gave failure... > > My syslogd looks clean, and doesn't give a false failure. I'm not sure > how to look into this - can you confirm that it truly is passing, but > giving the wrong message, or is it that the rc subsystem thinks it's > failing but appears to work ok? > > > > In principle this is what I have seen at first sight on the patch. > > > Thanks for all the feedback and testing! > > > Eric I have modified the patch as follows: Made a bunch of the settings tunable by the user (message text and field widths). It is availalbe at http://www.cokane.org/files/rc_fancy-cokane2.patch -- Coleman Kane From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 21 04:26:06 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9B1316A409 for ; Fri, 21 Apr 2006 04:26:06 +0000 (UTC) (envelope-from oceanare@pacific.net.sg) Received: from smtpgate4.pacific.net.sg (smtpgate4.pacific.net.sg [203.81.36.24]) by mx1.FreeBSD.org (Postfix) with SMTP id B996C43D45 for ; Fri, 21 Apr 2006 04:26:05 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 17588 invoked from network); 21 Apr 2006 04:26:03 -0000 Received: from maxwell6.pacific.net.sg (203.120.90.212) by smtpgate4.pacific.net.sg with SMTP; 21 Apr 2006 04:26:01 -0000 Received: from [192.168.0.107] ([210.24.122.33]) by maxwell6.pacific.net.sg with ESMTP id <20060421042600.KSQS1180.maxwell6.pacific.net.sg@[192.168.0.107]> for ; Fri, 21 Apr 2006 12:26:00 +0800 Message-ID: <44485E99.4090605@pacific.net.sg> Date: Fri, 21 Apr 2006 12:24:57 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Thunderbird 1.5 (X11/20060112) MIME-Version: 1.0 To: hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Build Kernels fails with X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2006 04:26:06 -0000 Hi, ist looks to me that this is still true for a 32 bit kernel. http://lists.freebsd.org/pipermail/freebsd-amd64/2005-July/005592.html This error message appears if_ural.o(.text+0x205): In function `ural_next_scan': /usr/src/sys/dev/usb/if_ural.c:699: undefined reference to `ieee80211_next_scan'*** Error code 1 as long as "device wlan" is not defined. Erich From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 21 06:55:22 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E06F16A403 for ; Fri, 21 Apr 2006 06:55:22 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E112743D4C for ; Fri, 21 Apr 2006 06:55:21 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1FWpXz-000CbX-GE; Fri, 21 Apr 2006 09:55:19 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Eric Anderson In-reply-to: Your message of Thu, 20 Apr 2006 22:32:33 -0500 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 21 Apr 2006 09:55:19 +0300 From: Danny Braniss Message-ID: Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC - v6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2006 06:55:22 -0000 > Coleman Kane wrote: > > On 4/20/06, *Eric Anderson* > > wrote: > > > > David Barbero wrote: > > > > > --- snip --- > > > > Yep, that's a bug. I think it's fixed in v7, available here: > > > > http://www.googlebit.com/freebsd/patches/rc_fancy.patch-7 > > > > along with a few other suggestions from others. > > > > > > > Another one of the failures that I have seen is that with this > > patch they > > > show all the services, they are or not formed to start, I believe > > that > > > single they would have to appear the services that are formed to > > start and > > > not all those that can start. > > > > If the service is run on bootup, it shows it. It was still being run > > before, there was just no output previously. It would be pretty easy to > > have an option to not print these, maybe an rc_fancy_verbose option. Is > > this desirable to most? > > > > > In addition the services that are not formed to start appear > > like [ OK ], > > > in the case of appearing these, I believe that they would have to > > leave > > > with another denomination that is not [ OK ]. > > > > > > I'm not sure what you mean here. Can you give me an example? > > > > > > > Another failure that I have seen is that when leaving the message > > syslogd > > > this sample failure, but this service starts without problems, > > but shows > > > it as if it gave failure... > > > > My syslogd looks clean, and doesn't give a false failure. I'm not sure > > how to look into this - can you confirm that it truly is passing, but > > giving the wrong message, or is it that the rc subsystem thinks it's > > failing but appears to work ok? > > > > > > > In principle this is what I have seen at first sight on the patch. > > > > > > Thanks for all the feedback and testing! > > > > > > Eric > > > > > > I have modified the patch as follows: > > > > Made a bunch of the settings tunable by the user (message text and field > > widths). > > > > It is availalbe at http://www.cokane.org/files/rc_fancy-cokane2.patch > > > This looks good. I only wonder about two things now: > > - Should we also have a line for the actual colors used too? Or is that > going too crazy? > > - Does it meet style(9)? I'm wondering about line lengths now. > > Other than that, do we have general consensus that these do what they > claim? Any outstanding issues that haven't been addressed? > > is the information correct? for example: Running start savecore [FAILED] Running start virecover [FAILED] the above didn't fail, they just had nothing to do. there is a danger with false negatives, it tends to confuse the uninitiated, there is a also a problem with false positives: Running start geli2 [ OK ] Running start mixer [ OK ] these do nothing, no geli2 nor mixer. The problem is one of interpretation, what does OK realy mean? one of the things i dislike with Linux is the amount of information printed when booting, it just wisks by, and when things don't work it's not clear what caused it! just to show that you are not alone: Apr 19 12:24:33 gto postgres[43823]: [2-1] FATAL: the database system is starting up danny From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 21 08:02:25 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1C8C16A402 for ; Fri, 21 Apr 2006 08:02:25 +0000 (UTC) (envelope-from sico@loquefaltaba.com) Received: from mail.loquefaltaba.com (78.Red-213-96-97.staticIP.rima-tde.net [213.96.97.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E63F43D49 for ; Fri, 21 Apr 2006 08:02:23 +0000 (GMT) (envelope-from sico@loquefaltaba.com) Received: from localhost (localhost.loquefaltaba.com [127.0.0.1]) by mail.loquefaltaba.com (Postfix) with ESMTP id 7257DC135; Fri, 21 Apr 2006 10:02:22 +0200 (CEST) Received: from mail.loquefaltaba.com ([127.0.0.1]) by localhost (sico.loquefaltaba.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22530-10; Fri, 21 Apr 2006 10:02:14 +0200 (CEST) Received: from webmail.loquefaltaba.com (localhost.loquefaltaba.com [127.0.0.1]) by mail.loquefaltaba.com (Postfix) with ESMTP id 0D689C10E; Fri, 21 Apr 2006 10:02:14 +0200 (CEST) Received: from 194.179.68.110 (SquirrelMail authenticated user sico) by webmail.loquefaltaba.com with HTTP; Fri, 21 Apr 2006 10:02:14 +0200 (CEST) Message-ID: <26839.194.179.68.110.1145606534.squirrel@webmail.loquefaltaba.com> In-Reply-To: <4447B876.4010606@centtech.com> References: <20060419040716.4F26116A45F@hub.freebsd.org> <20060419095207.GC19339@wjv.com> <44462C07.4030903@centtech.com> <444634C1.9080206@centtech.com> <44464BBF.5040801@centtech.com> <32256.194.179.68.110.1145535362.squirrel@webmail.loquefaltaba.com> <4447B876.4010606@centtech.com> Date: Fri, 21 Apr 2006 10:02:14 +0200 (CEST) From: "David Barbero" To: "Eric Anderson" User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at loquefaltaba.com Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Fancy rc startup style RFC - v6 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2006 08:02:26 -0000 Eric Anderson escribió: >> After to apply the patch, so that it works is necessary to put in >> rc.conf >> rc_fancy="YES ", when put this single entry, the system gives errors >> saying that correctly this entry in rc.conf is not correctly defined, >> adding single rc_fancy_color="YES" gives the same error. >> If the two entry meetings are added it don't show the error. >> I believe that serious advisable that these two entry did not depend the >> one on the other and worked separately. > > Well, obviously the _color option depends on the rc_fancy option being > enabled, otherwise it doesn't make sense, however you can of course have > rc_fancy enabled with rc_fancy_color disabled. yes, this is obvious, but i say rc_fancy depends on the rc_fancy_color, disabled or no, in rc.conf, if you don't put a entry for rc_fancy_color in rc.conf, the boot menssage show error. > Yep, that's a bug. I think it's fixed in v7, available here: > > http://www.googlebit.com/freebsd/patches/rc_fancy.patch-7 > > along with a few other suggestions from others. Ok, i will probe this patch in a few days and tell you for this. Probably Sunday can say something, right now I am of business trip and I do not have my PC of tests here... >> Another one of the failures that I have seen is that with this patch >> they >> show all the services, they are or not formed to start, I believe that >> single they would have to appear the services that are formed to start >> and >> not all those that can start. > > If the service is run on bootup, it shows it. It was still being run > before, there was just no output previously. It would be pretty easy to > have an option to not print these, maybe an rc_fancy_verbose option. Is > this desirable to most? I think a _verbose option don't for now, but can will be interesting. In any case I talked about that if you don't start a service (Ex: geli_enable="NO" in rc.conf) at boot time, in your patch this service it's show, and IMHO, if the service don't start at bootup, then don't show startup. >> In addition the services that are not formed to start appear like [ OK >> ], >> in the case of appearing these, I believe that they would have to leave >> with another denomination that is not [ OK ]. > > > I'm not sure what you mean here. Can you give me an example? Sorry for my English :) Yes, of course. in rc.conf: geli_enable="NO" inetd_enable="NO" And when yo reboot, the bootup menssage show: geli service [OK] inetd service [OK] And I believe that this menssage don't show on startup, or in the case of show the messange, this don't show the [OK], in that case, show [SKIP], for example. >> Another failure that I have seen is that when leaving the message >> syslogd >> this sample failure, but this service starts without problems, but shows >> it as if it gave failure... > > My syslogd looks clean, and doesn't give a false failure. I'm not sure > how to look into this - can you confirm that it truly is passing, but > giving the wrong message, or is it that the rc subsystem thinks it's > failing but appears to work ok? My syslogd work properly whitout any error, but give a false positive, I will be probe the last patch and I will try to see if I locate the failure, but will have Sunday... I see other fail in show the fancy_* when I have activated vidcontrol to 1024x764, but this is but so that it is pretty that an operation failure, IMHO is not important... > Thanks for all the feedback and testing! :) > Eric Regards -- "Linux is for people who hate Windows, BSD is for people who love UNIX" "Social Engineer -> Because there is no patch for human stupidity" From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 21 08:02:26 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFE9F16A405 for ; Fri, 21 Apr 2006 08:02:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB26A43D4C for ; Fri, 21 Apr 2006 08:02:24 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k3L82Hxg032137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Apr 2006 11:02:17 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k3L82Hk3094244; Fri, 21 Apr 2006 11:02:17 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k3L82H37094243; Fri, 21 Apr 2006 11:02:17 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 21 Apr 2006 11:02:17 +0300 From: Kostik Belousov To: Jeremie Le Hen Message-ID: <20060421080216.GB1446@deviant.kiev.zoral.com.ua> References: <20060420114822.GB35261@obiwan.tataz.chchile.org> <20060420124829.GA1446@deviant.kiev.zoral.com.ua> <20060420221623.GD68951@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NMuMz9nt05w80d4+" Content-Disposition: inline In-Reply-To: <20060420221623.GD68951@obiwan.tataz.chchile.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on fw.zoral.com.ua Cc: freebsd-hackers@freebsd.org Subject: Re: [fbsd] Re: Symbol weirdness with static linking X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2006 08:02:26 -0000 --NMuMz9nt05w80d4+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 21, 2006 at 12:16:23AM +0200, Jeremie Le Hen wrote: > Hi, Kostik, >=20 > > > For the sake of completeness, I added the output of some objdump(1) > > > outputs here : > > >=20 > > > /usr/obj/usr/src/bin/echo/echo.o: > > > http://tataz.chchile.org/~tataz/symbol_weirdness/objdump-t_echo.txt.gz > > >=20 > > > /usr/obj/usr/src/tmp/usr/lib/libc.a: > > > http://tataz.chchile.org/~tataz/symbol_weirdness/objdump-t_libc.txt.gz > > >=20 > > > /usr/obj/usr/src/tmp/usr/lib/libssp.a: > > > http://tataz.chchile.org/~tataz/symbol_weirdness/objdump-t_libssp.txt= .gz > >=20 > > It seems that you rebuilt world with CFLAGS -fstack-protector, > > since your libc has references to the symbols like __stack_smash_handle= r. > > As result, when linking with sequence -lgcc -lssp -lc -lgcc -lssp, > > and no references from the main object, > > references from libc causes objects from _second_ instance of -lssp to > > be pulled into the link. Since libraries are scanned sequentially, > > this object from libssp has no way to get required dependencies > > from libc. >=20 > Yes, I understand that. But I can't see what's the difference between > "syslog" and "sigfillset" symbols from this standpoint. The fact the > former requires ProPolice/SSP doesn't interfere IMHO. >=20 > > What makes syslog(3) special is that corresponding object from libc, > > syslog.o, requires __stack_smash_handler, while objects for mentioned > > syscalls do not. >=20 > How does it prevent the "syslog" symbol from being found ? Libc > undefined symbols implies the second libssp to be pulled in which in > turn has undefined symbol. But since there is no more libc after this, > "sigfillset" should be missing either. >=20 > I would understand if echo.o needed some symbols provided by the same > archive than "sigfillset" (sigsetops.o) but this is not the case. >=20 You are absolutely right, my error. "Explanation" with syslog dependency on stack_smash is wrong. In fact, building bin/echo on CURRENT with -DNO_SHARED gives deviant% objdump -t echo | grep sigfillset 08056dc0 g F .text 00000021 sigfillset It seems that at least the following dependency chain is present (for 6-STABLE): malloc -> abort -> sigfillset, and malloc is referenced by echo. For CURRENT, (possibly, another) dependency also pulls sig* from libc. Sorry for misinformation, I was innacurate when looking at issue. --NMuMz9nt05w80d4+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFESJGHC3+MBN1Mb4gRAgJiAJ9gxwu6Yq4CCc5ohDivBMVvWmBFsgCfdi1O 4110x28RkZ6EfhheptEOPCc= =yrs0 -----END PGP SIGNATURE----- --NMuMz9nt05w80d4+-- From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 21 08:39:06 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D97FD16A400 for ; Fri, 21 Apr 2006 08:39:06 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4744B43D46 for ; Fri, 21 Apr 2006 08:39:06 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp3-g19.free.fr (Postfix) with ESMTP id 829A648755; Fri, 21 Apr 2006 10:39:05 +0200 (CEST) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 203C79BEDC; Fri, 21 Apr 2006 08:39:04 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id DF252405B; Fri, 21 Apr 2006 10:39:03 +0200 (CEST) Date: Fri, 21 Apr 2006 10:39:03 +0200 From: Jeremie Le Hen To: Kostik Belousov Message-ID: <20060421083903.GE68951@obiwan.tataz.chchile.org> References: <20060420114822.GB35261@obiwan.tataz.chchile.org> <20060420124829.GA1446@deviant.kiev.zoral.com.ua> <20060420221623.GD68951@obiwan.tataz.chchile.org> <20060421080216.GB1446@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060421080216.GB1446@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: [fbsd] Re: [fbsd] Re: Symbol weirdness with static linking X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2006 08:39:06 -0000 Kostik, On Fri, Apr 21, 2006 at 11:02:17AM +0300, Kostik Belousov wrote: > > > It seems that you rebuilt world with CFLAGS -fstack-protector, > > > since your libc has references to the symbols like __stack_smash_handler. > > > As result, when linking with sequence -lgcc -lssp -lc -lgcc -lssp, > > > and no references from the main object, > > > references from libc causes objects from _second_ instance of -lssp to > > > be pulled into the link. Since libraries are scanned sequentially, > > > this object from libssp has no way to get required dependencies > > > from libc. > > > > Yes, I understand that. But I can't see what's the difference between > > "syslog" and "sigfillset" symbols from this standpoint. The fact the > > former requires ProPolice/SSP doesn't interfere IMHO. > > > > > What makes syslog(3) special is that corresponding object from libc, > > > syslog.o, requires __stack_smash_handler, while objects for mentioned > > > syscalls do not. > > > > How does it prevent the "syslog" symbol from being found ? Libc > > undefined symbols implies the second libssp to be pulled in which in > > turn has undefined symbol. But since there is no more libc after this, > > "sigfillset" should be missing either. > > > > I would understand if echo.o needed some symbols provided by the same > > archive than "sigfillset" (sigsetops.o) but this is not the case. > > > You are absolutely right, my error. "Explanation" with syslog dependency > on stack_smash is wrong. In fact, building bin/echo on CURRENT with > -DNO_SHARED gives > > deviant% objdump -t echo | grep sigfillset > 08056dc0 g F .text 00000021 sigfillset > > It seems that at least the following dependency > chain is present (for 6-STABLE): > > malloc -> abort -> sigfillset, > > and malloc is referenced by echo. > > For CURRENT, (possibly, another) dependency also pulls > sig* from libc. > > Sorry for misinformation, I was innacurate when looking at issue. There is no harm, don't bother. I made me think some more on linking mechanisms and I am more familiar with it now. Thank you very much for your explanation. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 21 09:55:51 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6309216A407 for ; Fri, 21 Apr 2006 09:55:51 +0000 (UTC) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from comsys.ntu-kpi.kiev.ua (comsys.ntu-kpi.kiev.ua [195.245.194.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DECA43D4C for ; Fri, 21 Apr 2006 09:55:45 +0000 (GMT) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from pm513-1.comsys.ntu-kpi.kiev.ua (pm513-1.comsys.ntu-kpi.kiev.ua [10.18.52.101]) (authenticated bits=0) by comsys.ntu-kpi.kiev.ua (8.13.6/8.13.6) with ESMTP id k3LAACSZ023462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 21 Apr 2006 13:10:13 +0300 (EEST) Received: by pm513-1.comsys.ntu-kpi.kiev.ua (Postfix, from userid 1001) id BB7CD5C024; Fri, 21 Apr 2006 12:56:11 +0300 (EEST) Date: Fri, 21 Apr 2006 12:56:11 +0300 From: Andrey Simonenko To: freebsd-hackers@freebsd.org Message-ID: <20060421095610.GA1137@pm513-1.comsys.ntu-kpi.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.3 required=5.0 tests=ALL_TRUSTED,AWL autolearn=unavailable version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on comsys.ntu-kpi.kiev.ua X-Virus-Scanned: ClamAV 0.82/1390/Tue Apr 11 10:32:32 2006 on comsys.ntu-kpi.kiev.ua X-Virus-Status: Clean Subject: Atomic updates of NFS export lists X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2006 09:55:51 -0000 Greetings, In my environment non-atomic updates of NFS export lists are not acceptable. So, I decided to correct this problem. As the result mountd, kern/vfs_export.c were completely rewritten, mount.h, vfs_mount.c and nfs_srvsubs.c also got changes. For details see kern/9619. I changed struct export_args{} and now it has two fields: a number of export specifications and a pointer to export specifications array. One export specification is a EXPC_xxx command and corresponding data for this command. I defined EXPC_ADD, UPDATE, DELETE and CLEAR commands. When mountd wants to update export list it builds an array of export specifications and passes this array to the kernel. Currently it always construct array of CLEAR, ADD, ADD... form, but support for UPDATE and DELETE commands also is ready. vfs_export.c and nfs_srvsubs.c are still Giant protected, but do not have race conditions, previously they did not protect own data correctly. I saw that there is work in progress for removing Giant from VFS, so I decided to not remove Giant from this part. vfs_export.c uses radix tree. Two memory leaks were corrected. There was memory leak if WebNFS index file were passed several times. And there was memory leak when some NFS exported filesystem was unmounted. While working on mountd I wrote simple library, which was called "Socket configuration library" or sockconf(3), which allows network servers to use getsockconf(3) function to configure network sockets and to not invite own "-h host...", "-p port...", "-t" (TCP) and "-u" (UDP) options. What do you think about this idea? Read sockconf(3), sockconf(5) and sockconf(8) manual pages. Visible changes in mountd: 1. The "-p port" option was removed. The "-s sockconf" option was added. Now it is possible to dump configuration to stdout using the -t option. 2. Now it is possible to use back-slash character in exports. Now it is possible to use several -network options in one line. 3. Several bugs with network masks were corrected: Class A, B, C... masks were created incorrectly for incomplete addresses, /xx masks were calculated incorrectly if xx % 8 != 0. 4. mountd sends better information to showmount now. 5. Now it is safe to update export lists without receiving EPERM on a client side. (I do not remember other changes.) Now mountd does not work if there is some error in exports file. I think this is correct behaviour and I'm ready to explain this. In mountd everything is organized in linked lists with small optimizations. Open questions (not complex really, without any order, I haven't implemented anything listed below, just to not make too many changes at once): 1. Is ex_root field in struct export_args{} still necessary? 2. The ex_flags field from struct export_args{} now can be removed, since check (specs != NULL) is enough. 3. Looks like that xdr_long() should should accept uint32_t argument. 4. When filesystem is unmounted, then umount(8) also should inform mountd, like mount(8) does. 5. If mount(MNT_UPDATE) is called for not VV_ROOT directory, then it should return something != EINVAL. Also see question 9. 6. Some better method should exist for communication between mount(8) and umount(8) with mountd(8). This can be sync mounting/unmounting and export lists changing using PF_LOCAL socket to communicate with mountd. It is not safe to send the HUP signal, mount/umount and update export lists. 7. Currently -public flag is not passed for address (network), but I think it should. There is XXX-comment in nfs_srvsubs.c related to this question. Is there some program for accessing WebNFS? 8. Is it necessary to check scope_id for IPv6 addresses in mountd? 9. What about passing export_args to the kernel using another syscall, for example nfssvc(2), and removing export_args fields from all filesystems xxx_args structures? It would be possible to remove some lines from VFS_MOUNT implementations. 10. What about moving MNT_DEFEXPORTED and MNT_EXPUBLIC from mp->mnt_flag to netexport structure? Are these flags very important in statfs(2) result? What about removing MNT_EXRDONLY and MNT_EXPORTANON and using EXPF_RDONLY and EXPF_ANON instead? (I aslo have another idea here.) ----------------------------------------------------------------------- I probably forgot something to say above... Everything is available for downloading and can be used on 6.1-RC, I tested everything on UP i386 system: http://comsys.ntu-kpi.kiev.ua/~simon/mountd/ SHA256 (mountd-20060421.tar.bz2) = e3f6b14468c42aeb6064a7d240955136a13f910bd12825e44096edcb8d1a6b04 Please read INSTALL before installing. From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 21 12:51:03 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E976816A401 for ; Fri, 21 Apr 2006 12:51:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41F0943D5C for ; Fri, 21 Apr 2006 12:51:03 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3LCosgK025458; Fri, 21 Apr 2006 08:50:54 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Fri, 21 Apr 2006 08:50:45 -0400 User-Agent: KMail/1.8.3 References: <44485E99.4090605@pacific.net.sg> In-Reply-To: <44485E99.4090605@pacific.net.sg> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200604210850.46126.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1411/Thu Apr 20 18:23:28 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Subject: Re: Build Kernels fails with X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2006 12:51:04 -0000 On Friday 21 April 2006 12:24 am, Erich Dollansky wrote: > Hi, > > ist looks to me that this is still true for a 32 bit kernel. > > http://lists.freebsd.org/pipermail/freebsd-amd64/2005-July/005592.html > > This error message appears > > if_ural.o(.text+0x205): In function `ural_next_scan': > /usr/src/sys/dev/usb/if_ural.c:699: undefined reference to > `ieee80211_next_scan'*** Error code 1 > > as long as "device wlan" is not defined. Well, yes. The wifi drivers (wi, ath, ral, ural, iwi, and ipw) require 'device wlan'. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 21 14:13:09 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E981416A407 for ; Fri, 21 Apr 2006 14:13:09 +0000 (UTC) (envelope-from xelah@sphinx.mythic-beasts.com) Received: from wumpus.mythic-beasts.com (wumpus.mythic-beasts.com [212.69.37.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 618BE43D45 for ; Fri, 21 Apr 2006 14:13:09 +0000 (GMT) (envelope-from xelah@sphinx.mythic-beasts.com) Received: from sphinx.mythic-beasts.com ([212.69.37.6]) by wumpus.mythic-beasts.com with esmtp (Exim 4.44) id 1FWwNg-00061H-C6; Fri, 21 Apr 2006 15:13:08 +0100 Received: from xelah (helo=localhost) by sphinx.mythic-beasts.com with local-esmtp (Exim 4.51) id 1FWwNf-00039G-Kh; Fri, 21 Apr 2006 15:13:07 +0100 Date: Fri, 21 Apr 2006 15:13:07 +0100 (BST) From: Alex Hayward X-X-Sender: xelah@sphinx.mythic-beasts.com To: Paul Halliday In-Reply-To: <2dab70a30604201049i41e409e1y8924383843c95980@mail.gmail.com> Message-ID: References: <2dab70a30604201049i41e409e1y8924383843c95980@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Alex Hayward Cc: hackers@freebsd.org Subject: Re: Server choice. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2006 14:13:10 -0000 On Thu, 20 Apr 2006, Paul Halliday wrote: > Hi, > > I am in the process of building a new database server and after > pricing up 2 Dell models I thought I would throw this out just to see > which choice would be better suited for FreeBSD. You didn't say what database you're running. Certain Poweredges (6650s at least) have a rather poor repute on the PostgreSQL mailings (for running PostgreSQL, at least). You may wish to check the archives before buying one. We used to use a 6650 for running PostgreSQL and the performance wasn't all that good for our application. Our database is much more CPU and memory-bandwidth bound than IO bound, though. For a database you probably want Opterons, not Pentiums. We've found them to perform extremely well (Athlons do well too). Your 'Dell only' restriction may well cost you a lot of performance (unless Dell have started using Opterons while I wasn't looking, or unless I'm out of date on the performance of Pentiums). > The demands on the system will be mostly network -> disk I/O with a > hope of best performance on quickly servicing numerous reads; for > example when reports are generated using the data in the database. > > The 2 choices (we dont have that much money and they have to be Dell) > are a poweredge 1850 and a poweredge 850. > > 850 specs. > ---------------- > Procsesor: Pentium(Dual Core) 830 @ 3.0GHz/2X1MB Cache 800MHz FSB > Memory: 2GB DDR2, 533MHz (2x1GB) Dual ranked DIMMs > Disks: SATA > > 1850 specs. > ------------------ > Processors: 2 @ Xeon @ 3.0GHz/2MB Cache 800MHz FSB > Memory: 2GB DDR2, 400MHz (4x512) Single ranked DIMMs > Disks: Ultra 320 > > The pricing is really close. I presume that it's some sort of decision support/data mining application, that there's no hope of fitting much of your data in to RAM and that there's no hope of beating the 'Dell only' restriction's originator in to submission. I'd go for the 1850 and lots and lots of fast disks in a RAID 10 array. AFAICS there are only two slots in a 1850. Hmm, it looks like 850s have only two, too. Do you intend to use an external disk array, or are your IO requirement just not that high? If not make sure you get the fastest disks available (it looks like the 1850 can come with 15kRPM drives, whereas the 850 SATA ones are 7.4 - which should pretty much kill that option), two disks isn't many. If you're doing any significant writes then make sure you get and enable the battery-backed cache on the RAID card to avoid having an fsync flush data all the way to disk at the end of every transaction. Does the 850 even have one? That'd be another good reason to get a 1850... From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 21 21:02:39 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C42216A406 for ; Fri, 21 Apr 2006 21:02:39 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A3A943D48 for ; Fri, 21 Apr 2006 21:02:39 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 104681A3C19; Fri, 21 Apr 2006 14:02:39 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 34F5F5526F; Fri, 21 Apr 2006 17:01:43 -0400 (EDT) Date: Fri, 21 Apr 2006 17:01:43 -0400 From: Kris Kennaway To: Andrey Simonenko Message-ID: <20060421210143.GA70701@xor.obsecurity.org> References: <20060421095610.GA1137@pm513-1.comsys.ntu-kpi.kiev.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline In-Reply-To: <20060421095610.GA1137@pm513-1.comsys.ntu-kpi.kiev.ua> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: Atomic updates of NFS export lists X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2006 21:02:39 -0000 --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 21, 2006 at 12:56:11PM +0300, Andrey Simonenko wrote: > Greetings, >=20 > In my environment non-atomic updates of NFS export lists are not > acceptable. So, I decided to correct this problem. As the result > mountd, kern/vfs_export.c were completely rewritten, mount.h, > vfs_mount.c and nfs_srvsubs.c also got changes. > 5. Now it is safe to update export lists without receiving EPERM > on a client side. I think it's fantastic that you're working on this - I had to disable the SIGHUP that is sent by mount(8) to avoid destroying my client I/O each time I remount on the server (in fact I was going to propose removing this code as a workaround). I'll test your patch soon. Kris --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFESUg3Wry0BWjoQKURAje1AJ9RXqUrGFHwuc3wbuXMrfSQ93jCZwCeMEl+ KE2Wtrax+bozd0vQN7k++Aw= =nSMQ -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs-- From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 22 02:12:04 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC84C16A405 for ; Sat, 22 Apr 2006 02:12:04 +0000 (UTC) (envelope-from oceanare@pacific.net.sg) Received: from smtpgate1.pacific.net.sg (smtpgate1.pacific.net.sg [203.120.90.31]) by mx1.FreeBSD.org (Postfix) with SMTP id 9DF6643D55 for ; Sat, 22 Apr 2006 02:12:03 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 30054 invoked from network); 22 Apr 2006 02:12:01 -0000 Received: from maxwell6.pacific.net.sg (203.120.90.212) by smtpgate1.pacific.net.sg with SMTP; 22 Apr 2006 02:11:59 -0000 Received: from [192.168.0.107] ([210.24.122.33]) by maxwell6.pacific.net.sg with ESMTP id <20060422021158.NQOV1180.maxwell6.pacific.net.sg@[192.168.0.107]>; Sat, 22 Apr 2006 10:11:58 +0800 Message-ID: <444990D7.90701@pacific.net.sg> Date: Sat, 22 Apr 2006 10:11:35 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Thunderbird 1.5 (X11/20060422) MIME-Version: 1.0 To: John Baldwin References: <44485E99.4090605@pacific.net.sg> <200604210850.46126.jhb@freebsd.org> In-Reply-To: <200604210850.46126.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Build Kernels fails with X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Apr 2006 02:12:05 -0000 Hi, John Baldwin wrote: > On Friday 21 April 2006 12:24 am, Erich Dollansky wrote: >> Hi, >> >> ist looks to me that this is still true for a 32 bit kernel. >> >> http://lists.freebsd.org/pipermail/freebsd-amd64/2005-July/005592.html >> >> This error message appears >> >> if_ural.o(.text+0x205): In function `ural_next_scan': >> /usr/src/sys/dev/usb/if_ural.c:699: undefined reference to >> `ieee80211_next_scan'*** Error code 1 >> >> as long as "device wlan" is not defined. > > Well, yes. The wifi drivers (wi, ath, ral, ural, iwi, and ipw) > require 'device wlan'. 'ural' could be the culprit. It was still defined well hidden inside the USB support. Thanks! Erich From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 22 11:26:09 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69D0D16A401 for ; Sat, 22 Apr 2006 11:26:09 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3AC343D45 for ; Sat, 22 Apr 2006 11:26:08 +0000 (GMT) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3MBQ5dh007456 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 22 Apr 2006 04:26:06 -0700 X-Auth-Received: from [192.168.0.40] (dsl254-013-145.sea1.dsl.speakeasy.net [216.254.13.145]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.6+UW06.03/8.13.6+UW06.03) with ESMTP id k3MBQ5LN008952 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Sat, 22 Apr 2006 04:26:05 -0700 Mime-Version: 1.0 (Apple Message framework v749.3) Content-Transfer-Encoding: 7bit Message-Id: <4B29E098-F409-490F-86F1-380CFE1165FC@u.washington.edu> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-hackers@freebsd.org From: Garrett Cooper Date: Sat, 22 Apr 2006 04:28:30 -0700 X-Mailer: Apple Mail (2.749.3) X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: Is showing all attributes for RS232 port possible in FreeBSD? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Apr 2006 11:26:09 -0000 Hi, I was just wondering if there was any way where I could program with C, such that I could view information regarding the extra pins on a DB9 serial port other than just TXD and RXD, ie the DTS, CD, CTS,... etc ports. I am trying to figure out how exactly Hyperterm works as part of a project with programming a PIC microprocessor. Thanks! -Garrett From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 22 11:44:22 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F05616A400 for ; Sat, 22 Apr 2006 11:44:22 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id E36DC43D45 for ; Sat, 22 Apr 2006 11:44:21 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail17.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k3MBiI6F023762 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 22 Apr 2006 21:44:19 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k3MBiIYC005721; Sat, 22 Apr 2006 21:44:18 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k3MBiICQ005720; Sat, 22 Apr 2006 21:44:18 +1000 (EST) (envelope-from peter) Date: Sat, 22 Apr 2006 21:44:18 +1000 From: Peter Jeremy To: Garrett Cooper Message-ID: <20060422114418.GD720@turion.vk2pj.dyndns.org> References: <4B29E098-F409-490F-86F1-380CFE1165FC@u.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B29E098-F409-490F-86F1-380CFE1165FC@u.washington.edu> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: Is showing all attributes for RS232 port possible in FreeBSD? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Apr 2006 11:44:22 -0000 On Sat, 2006-Apr-22 04:28:30 -0700, Garrett Cooper wrote: > I was just wondering if there was any way where I could program with >C, such that I could view information regarding the extra pins on a >DB9 serial port other than just TXD and RXD, ie the DTS, CD, CTS,... >etc ports. Look in tty(4), specifically TIOCMSET, TIOCMGET, TIOCMBIS, TIOCMBIC. -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 22 14:40:57 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD6A916A401 for ; Sat, 22 Apr 2006 14:40:57 +0000 (UTC) (envelope-from igor@doom.homeunix.org) Received: from mail.ecolines.ru (ns.ecolines.ru [81.3.181.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93D9D43D48 for ; Sat, 22 Apr 2006 14:40:54 +0000 (GMT) (envelope-from igor@doom.homeunix.org) Received: (qmail 8582 invoked from network); 22 Apr 2006 14:46:42 -0000 Received: from unknown (HELO doom.homeunix.org) (ip@212.113.114.49) by mail.ecolines.ru with ESMTPA; 22 Apr 2006 14:46:42 -0000 Received: from doom.homeunix.org (localhost [127.0.0.1]) by doom.homeunix.org (8.13.4/8.13.4) with ESMTP id k3M73cpO001193; Sat, 22 Apr 2006 11:03:39 +0400 (MSD) (envelope-from igor@doom.homeunix.org) Received: (from igor@localhost) by doom.homeunix.org (8.13.4/8.13.4/Submit) id k3L561ci006340; Fri, 21 Apr 2006 09:06:01 +0400 (MSD) (envelope-from igor) Date: Fri, 21 Apr 2006 09:05:41 +0400 From: Igor Pokrovsky To: Joe Marcus Clarke Message-ID: <20060421050541.GA3223@doom.homeunix.org> Mail-Followup-To: Joe Marcus Clarke , hackers@freebsd.org References: <1145077545.83050.15.camel@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1145077545.83050.15.camel@shumai.marcuscom.com> User-Agent: Mutt/1.4.2.1i Cc: hackers@freebsd.org Subject: Re: User mounting take 2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Apr 2006 14:40:57 -0000 On Sat, Apr 15, 2006 at 01:05:45AM -0400, Joe Marcus Clarke wrote: > Based on feedback I received on my initial diff, I took another crack at > user mounting. To address Robert's concerns, I drop the setuid > permissions until needed. Therefore, all permission checks are now done > in the kernel. The same is true for umount(8). > > silby asked for wildcard support. To handle that, I added glob support > to both the fs_file and fs_spec fstab components (via fnmatch(3)), and > also added a special %u pattern that can be used to represent the > current user (i.e. the user running mount(8)). This effectively allows > the following in /etc/fstab: > > //%u@server/homes /home/%u/smb_home smbfs rw,noauto,user 0 0 > > Then, a user could just run, for example: > > mount /home/marcus/smb_home > > And their SMB home directory would get mounted (~/.nsmbrc is also > respected). > > Additionally, something like the following is also possible: > > /dev/acd0 /home/*/cdrom cd9660 ro,noauto,user 0 0 > > Same mount command works here: > > mount /home/marcus/cdrom > > Wildcards can also be mixed and matched. > > Finally, in testing this, I found a problem with smbfs, msdosfs, and > ntfs relating to the statfs(2) f_flags field. smbfs always set this to > 0, msdosfs didn't set this at all, and ntfs set this to all flags (not > just those visible to statfs(2)). By fixing this, umount(8) works > properly on relative paths to user mount points for those three file > systems. > > http://www.marcuscom.com/downloads/usermount.diff > > Comments? Great feature! Hopefully it will hit the tree soon enough. Thanks! -ip -- A free agent is anything but. From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 22 16:34:55 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C56116A402 for ; Sat, 22 Apr 2006 16:34:55 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D53A43D49 for ; Sat, 22 Apr 2006 16:34:55 +0000 (GMT) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.13.6+UW06.03/8.13.5+UW06.03) with ESMTP id k3MGYriP024569 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 22 Apr 2006 09:34:54 -0700 X-Auth-Received: from [192.168.0.50] (dsl254-013-145.sea1.dsl.speakeasy.net [216.254.13.145]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.6+UW06.03/8.13.6+UW06.03) with ESMTP id k3MGYovO025468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 22 Apr 2006 09:34:52 -0700 Message-ID: <444A5B2E.5050307@u.washington.edu> Date: Sat, 22 Apr 2006 09:34:54 -0700 From: Garrett Cooper User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Peter Jeremy , freebsd-hackers@freebsd.org References: <4B29E098-F409-490F-86F1-380CFE1165FC@u.washington.edu> <20060422114418.GD720@turion.vk2pj.dyndns.org> In-Reply-To: <20060422114418.GD720@turion.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Cc: Subject: Re: Is showing all attributes for RS232 port possible in FreeBSD? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Apr 2006 16:34:55 -0000 Peter Jeremy wrote: > On Sat, 2006-Apr-22 04:28:30 -0700, Garrett Cooper wrote: > >> I was just wondering if there was any way where I could program with >> C, such that I could view information regarding the extra pins on a >> DB9 serial port other than just TXD and RXD, ie the DTS, CD, CTS,... >> etc ports. >> > > Look in tty(4), specifically TIOCMSET, TIOCMGET, TIOCMBIS, TIOCMBIC. Brilliant! That's exactly what I was looking for. Thanks! -Garrett From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 22 20:49:52 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38D4216A402 for ; Sat, 22 Apr 2006 20:49:52 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA39643D46 for ; Sat, 22 Apr 2006 20:49:51 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k3MKlRYl063065; Sat, 22 Apr 2006 14:47:29 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 22 Apr 2006 14:47:30 -0600 (MDT) Message-Id: <20060422.144730.38223468.imp@bsdimp.com> To: youshi10@u.washington.edu From: "M. Warner Losh" In-Reply-To: <4B29E098-F409-490F-86F1-380CFE1165FC@u.washington.edu> References: <4B29E098-F409-490F-86F1-380CFE1165FC@u.washington.edu> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Is showing all attributes for RS232 port possible in FreeBSD? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Apr 2006 20:49:52 -0000 In message: <4B29E098-F409-490F-86F1-380CFE1165FC@u.washington.edu> Garrett Cooper writes: : Hi, : I was just wondering if there was any way where I could program with : C, such that I could view information regarding the extra pins on a : DB9 serial port other than just TXD and RXD, ie the DTS, CD, CTS,... : etc ports. : I am trying to figure out how exactly Hyperterm works as part of a : project with programming a PIC microprocessor. man 4 tty Warner