From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 30 11: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 7AC4F16A40F for ; Sun, 30 Apr 2006 11:25:57 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA2DF43D4C for ; Sun, 30 Apr 2006 11:25:48 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by nz-out-0102.google.com with SMTP id x3so2708478nzd for ; Sun, 30 Apr 2006 04:25:48 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YqZLlNX8X85Jpt74LadiPXMQEBSBkTdS50E3T+TXEW1IPvxHfBHbStcUeBCkWEansq+fbxnFLT2BbP3ZDMzYoZHSADPbLbMKUm7//VNimOmVYZIKA74eruaTTkWqZHtPI0UBS49szoNe/dP7va1ihxacU5jt6aKk8JYGxCS98Y4= Received: by 10.36.43.12 with SMTP id q12mr1388562nzq; Sun, 30 Apr 2006 04:25:48 -0700 (PDT) Received: by 10.37.22.74 with HTTP; Sun, 30 Apr 2006 04:25:48 -0700 (PDT) Message-ID: Date: Sun, 30 Apr 2006 15:25:48 +0400 From: "Andrew Pantyukhin" To: "Vladimir Terziev" In-Reply-To: <20060425151913.63f2463f.vlady@gbservices.biz> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060425151913.63f2463f.vlady@gbservices.biz> X-Mailman-Approved-At: Sun, 30 Apr 2006 11:46:43 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: gmirror with hot spare 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, 30 Apr 2006 11:25:57 -0000 On 4/25/06, Vladimir Terziev wrote: > > Hi hackers, > > is there a way to assign a hot spare disk/partition to a gmirror = -ed disks/partitions ? There's no sense in it, is there? When we have RAID5 hot spare is needed, because we don't know what drive will fail first. When we have gmirror, it doesn't matter! Just add another drive to gmirror and take it easy. From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 30 14: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 D3B4F16A400 for ; Sun, 30 Apr 2006 14:08:05 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1408543D48 for ; Sun, 30 Apr 2006 14:08:04 +0000 (GMT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.13.6/8.13.4) with ESMTP id k3UE831B073170 for ; Sun, 30 Apr 2006 18:08:03 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sun, 30 Apr 2006 18:08:03 +0400 (MSD) From: Dmitry Morozovsky To: hackers@FreeBSD.org Message-ID: <20060430180103.W70630@woozle.rinet.ru> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (woozle.rinet.ru [0.0.0.0]); Sun, 30 Apr 2006 18:08:04 +0400 (MSD) Cc: Subject: config(8), include, and INCLUDE_CONFIG_FILE 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, 30 Apr 2006 14:08:05 -0000 Dear colleagues, Since "include" statement has been invented in config(8), option INCLUDE_CONFIG_FILE is broken, as it's embedding only highest level config file into the kernel. I looked through the sources, but it seems fixing this is not very easy. The most natural way for me seems tracking all config while lex/yacc parsing into memory buffer, as configfile() is invoked after full config parse. Any thoughts? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 30 21:09:36 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 3476916A407 for ; Sun, 30 Apr 2006 21:09:36 +0000 (UTC) (envelope-from ianchov@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6768543D6D for ; Sun, 30 Apr 2006 21:09:29 +0000 (GMT) (envelope-from ianchov@gmail.com) Received: by uproxy.gmail.com with SMTP id m3so1832754ugc for ; Sun, 30 Apr 2006 14:09:29 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=F1Ag3XfgsZ4cYnC4PJQSWgYZ23aoKuzO+Dm4uoIZO0Nh5+EJ5oXSP/NWonz1+QWzuR86vBe+U6+1qapc5kTPCFQpaNbfCDMtr692eXQYl04vlglMAJDme2T49ihK6czbhRzRT4pWlc6tkOyBQ0Oj4pAgeHrtwLikqFjFM6NzgFg= Received: by 10.78.43.1 with SMTP id q1mr380994huq; Sun, 30 Apr 2006 14:09:29 -0700 (PDT) Received: by 10.78.16.16 with HTTP; Sun, 30 Apr 2006 14:09:29 -0700 (PDT) Message-ID: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> Date: Mon, 1 May 2006 00:09:29 +0300 From: "Iantcho Vassilev" To: freebsd-hackers@freebsd.org, "FreeBSD Questions" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 30 Apr 2006 21:09:38 -0000 Hello guys, in bsdnews.com i found this link http://kerneltrap.org/node/6506 and particulary this: "I claim that Mach people (and apparently FreeBSD) are incompetent idiots. Playing games with VM is bad. memory copies are _also_ bad, but quite frankly, memory copies often have _less_ downside than VM games, and bigger caches will only continue to drive that point home." What do you think about it? From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 30 21:15: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 95E8616A477; Sun, 30 Apr 2006 21:15:27 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr5.xs4all.nl (smtp-vbr5.xs4all.nl [194.109.24.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id C36FB43D60; Sun, 30 Apr 2006 21:15:18 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr5.xs4all.nl (8.13.6/8.13.6) with ESMTP id k3ULFHhv040052; Sun, 30 Apr 2006 23:15:18 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id k3ULFHTd011988; Sun, 30 Apr 2006 23:15:17 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id k3ULFHqA011987; Sun, 30 Apr 2006 23:15:17 +0200 (CEST) (envelope-from wb) Date: Sun, 30 Apr 2006 23:15:17 +0200 From: Wilko Bulte To: Iantcho Vassilev Message-ID: <20060430211517.GA11971@freebie.xs4all.nl> References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-hackers@freebsd.org, FreeBSD Questions Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 30 Apr 2006 21:15:33 -0000 On Mon, May 01, 2006 at 12:09:29AM +0300, Iantcho Vassilev wrote.. > Hello guys, > > > in bsdnews.com i found this link http://kerneltrap.org/node/6506 and > particulary this: > > "I claim that Mach people (and apparently FreeBSD) are incompetent idiots. > Playing games with VM is bad. memory copies are _also_ bad, but quite > frankly, memory copies often have _less_ downside than VM games, and bigger > caches will only continue to drive that point home." > > What do you think about it? That you are a bit late in discovering this one ;) Enough time has been wasted on it, at least on the project-internal lists, so please let it rest. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 30 21: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 E9E0816A406 for ; Sun, 30 Apr 2006 21:17:34 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F80F43D76 for ; Sun, 30 Apr 2006 21:17:25 +0000 (GMT) (envelope-from kip.macy@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so1632337wxc for ; Sun, 30 Apr 2006 14:17: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:content-transfer-encoding:content-disposition:references; b=fmb//SSHAEpDV9jQywK9TXBcFG8KpEU9hzZ+c/4yC0/cGEpcf5YS6eyY1E0U2P7rRLdZQZBu4N10xaphhPk/Lh1jfVEbKrBUSt7QpB8oRWOYj0HTe87tcxJ+n+QgUyS8h0yorsEjJwSWsIWoGQ6hkMpeWZ7zN0fTO5JE4aoh69w= Received: by 10.70.94.17 with SMTP id r17mr3452785wxb; Sun, 30 Apr 2006 14:17:25 -0700 (PDT) Received: by 10.70.69.7 with HTTP; Sun, 30 Apr 2006 14:17:25 -0700 (PDT) Message-ID: Date: Sun, 30 Apr 2006 14:17:25 -0700 From: "Kip Macy" To: "Iantcho Vassilev" In-Reply-To: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> Cc: freebsd-hackers@freebsd.org, FreeBSD Questions Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kmacy@fsmware.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Apr 2006 21:17:37 -0000 The implementation is > 7 years old, not used by default, and was intended for a specific application. There really isn't much to say. -Kip On 4/30/06, Iantcho Vassilev wrote: > Hello guys, > > > in bsdnews.com i found this link http://kerneltrap.org/node/6506 and > particulary this: > > "I claim that Mach people (and apparently FreeBSD) are incompetent idiots= . > Playing games with VM is bad. memory copies are _also_ bad, but quite > frankly, memory copies often have _less_ downside than VM games, and bigg= er > caches will only continue to drive that point home." > > > > > What do you think about it? > _______________________________________________ > 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 Sun Apr 30 21:32: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 2C74B16A415 for ; Sun, 30 Apr 2006 21:32:34 +0000 (UTC) (envelope-from ianchov@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id D09CF43D55 for ; Sun, 30 Apr 2006 21:32:30 +0000 (GMT) (envelope-from ianchov@gmail.com) Received: by uproxy.gmail.com with SMTP id m3so1834683ugc for ; Sun, 30 Apr 2006 14:32:29 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=uEiVJvO4/M6nmr6LtEBtcJuXW/hrzPeV74Pc/nyMyWSdjC/1RsWLizAev4+JVjnBCYQnHFttLcF0cbsIOPopYFrn6+IGhdpbd+tmKMFbu90csCkvEy0D/AOALYzqHl7WZmuqK1KwP2UoYfj/KcAg5cIn9j7yV7rxicnAAhTgl9o= Received: by 10.78.48.16 with SMTP id v16mr242115huv; Sun, 30 Apr 2006 14:32:29 -0700 (PDT) Received: by 10.78.16.16 with HTTP; Sun, 30 Apr 2006 14:32:29 -0700 (PDT) Message-ID: <18e02bd30604301432s4bf13408x7b474c7fc19840cd@mail.gmail.com> Date: Mon, 1 May 2006 00:32:29 +0300 From: "Iantcho Vassilev" To: "FreeBSD Questions" In-Reply-To: MIME-Version: 1.0 References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 30 Apr 2006 21:32:35 -0000 My first impression was as of Kip... But i think Linus attitude isn`t very perfect.... The big guy is showing muscles... On 5/1/06, Kip Macy wrote: > > The implementation is > 7 years old, not used by default, and was > intended for a specific application. There really isn't much to say. > > -Kip > > On 4/30/06, Iantcho Vassilev wrote: > > Hello guys, > > > > > > in bsdnews.com i found this link http://kerneltrap.org/node/6506 and > > particulary this: > > > > "I claim that Mach people (and apparently FreeBSD) are incompetent > idiots. > > Playing games with VM is bad. memory copies are _also_ bad, but quite > > frankly, memory copies often have _less_ downside than VM games, and > bigger > > caches will only continue to drive that point home." > > > > > > > > > > What do you think about it? > > _______________________________________________ > > 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 Sun Apr 30 23:48: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 D7F3816A401; Sun, 30 Apr 2006 23:48:46 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5006D43D46; Sun, 30 Apr 2006 23:48:43 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k3UNmgG4027178; Sun, 30 Apr 2006 17:48:42 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44554CE2.4000403@samsco.org> Date: Sun, 30 Apr 2006 17:48:50 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Iantcho Vassilev References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> In-Reply-To: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-hackers@freebsd.org, FreeBSD Questions Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 30 Apr 2006 23:48:47 -0000 Iantcho Vassilev wrote: > Hello guys, > > > in bsdnews.com i found this link http://kerneltrap.org/node/6506 and > particulary this: > > "I claim that Mach people (and apparently FreeBSD) are incompetent idiots. > Playing games with VM is bad. memory copies are _also_ bad, but quite > frankly, memory copies often have _less_ downside than VM games, and bigger > caches will only continue to drive that point home." > > > > > What do you think about it? I claim that Linus is an attention whore. How about that? Scott From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 00:33: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 A584116A401 for ; Mon, 1 May 2006 00:33:22 +0000 (UTC) (envelope-from slackwarewolf@comcast.net) Received: from rwcrmhc14.comcast.net (rwcrmhc14.comcast.net [216.148.227.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F98543D46 for ; Mon, 1 May 2006 00:33:22 +0000 (GMT) (envelope-from slackwarewolf@comcast.net) Received: from [192.168.0.100] (c-69-246-87-201.hsd1.mi.comcast.net[69.246.87.201]) by comcast.net (rwcrmhc14) with ESMTP id <20060501003321m1400s0hbme>; Mon, 1 May 2006 00:33:21 +0000 From: Allen To: freebsd-hackers@freebsd.org Date: Sun, 30 Apr 2006 20:35:50 -0400 User-Agent: KMail/1.8 References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <20060430211517.GA11971@freebie.xs4all.nl> In-Reply-To: <20060430211517.GA11971@freebie.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604302035.50870.slackwarewolf@comcast.net> Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 01 May 2006 00:33:22 -0000 On Sunday 30 April 2006 5:15 pm, Wilko Bulte wrote: > On Mon, May 01, 2006 at 12:09:29AM +0300, Iantcho Vassilev wrote.. > > > Hello guys, > > > > > > in bsdnews.com i found this link http://kerneltrap.org/node/6506 and > > particulary this: > > > > "I claim that Mach people (and apparently FreeBSD) are incompetent > > idiots. Playing games with VM is bad. memory copies are _also_ bad, but > > quite frankly, memory copies often have _less_ downside than VM games, > > and bigger caches will only continue to drive that point home." > > > > What do you think about it? I've known for quite some time that things like this are said. One thing no one points out is how Linus is actually a fan of BSD. Sometimes things he says are mis quoted though. If you watch Revolution OS, Linus points out that his main thing for doing Linux was that he wanted something like he had used at the university he was at and he says it was SunOS. Sun OS / Solaris, are straight BSD. For info on where I get this, get the movie "20 years of Berkeley UNIX". I own that and Revolution OS, Linus Loves BSD even though he's sometimes mis quoted or even joking. -Allen A Linux and BSD and BeOS user. From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 30 23:14:49 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 0CD4C16A402 for ; Sun, 30 Apr 2006 23:14:49 +0000 (UTC) (envelope-from cokane@mail.cokane.org) Received: from smtp2.fuse.net (mail-out2.fuse.net [216.68.8.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6051543D45 for ; Sun, 30 Apr 2006 23:14:47 +0000 (GMT) (envelope-from cokane@mail.cokane.org) Received: from gx5.fuse.net ([72.49.162.239]) by smtp2.fuse.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20060430231447.NNZQ26850.smtp2.fuse.net@gx5.fuse.net> for ; Sun, 30 Apr 2006 19:14:47 -0400 Received: from mail.cokane.org ([72.49.162.239]) by gx5.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with ESMTP id <20060430231447.NGUX4651.gx5.fuse.net@mail.cokane.org> for ; Sun, 30 Apr 2006 19:14:47 -0400 Received: (qmail 672 invoked by uid 1000); 30 Apr 2006 19:16:21 -0400 Date: Sun, 30 Apr 2006 19:16:21 -0400 From: Coleman Kane To: Eric Anderson Message-ID: <20060430231621.GA551@pint.candc.home> References: <20060420035530.F1A5A16A4E0@hub.freebsd.org> <20060420132543.GB37150@wjv.com> <4447D2F7.1070408@centtech.com> <346a80220604232037mb6f98a0x5fab21622de5ce3c@mail.gmail.com> <444C51BA.3020905@centtech.com> <20060424131508.GB23163@pint.candc.home> <444CD48A.4060501@centtech.com> <444CE475.30104@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <444CE475.30104@centtech.com> User-Agent: Mutt/1.5.11 X-Mailman-Approved-At: Mon, 01 May 2006 01:23:48 +0000 Cc: 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: Sun, 30 Apr 2006 23:14:49 -0000 On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: > Eric Anderson wrote: > > Actually, some other things got changed somewhere in the history, that > broke some things and assumptions I was making. This patch has them > fixed, and I've tested it with all the different options: > > http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 > > It's missing the defaults/rc.conf diffs, but you should already know those. > > > Eric > I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. This allows the use of: rc_fancy="YES" ---> Turns on fancy reporting (w/o color) rc_fancy_color="YES" ---> Turns on fancy reporting (w/ color), needs rc_fancy="YES" rc_fancy_colour="YES" ---> Same as above for you on the other side of the pond. rc_fancy_verbose="YES" --> Turn on more verbose activity messages. This will cause what appear to be "false positives", where an unused service is "OK" instead of "SKIP". You can also customize the colors, the widths of the message brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and the contents of the message (OK versus GOOD versus BUENO). Also, we have the following message combinations: OK ---> Universal good message SKIP,SKIPPED ---> Two methods for conveying the same idea? ERROR,FAILED ---> Ditto above, for failure cases Should we just have 3 different messages, rather than 5 messages in 3 categories? TODO: One thing I am trying to figure out is how to get the terminal to report its width, in columns (which is something that VT100+ supports). I just don't know how to do it from a script. TODO: Get better reporting from the rc.d/* scripts (and whatever other services we track). Right now, if verbose is on, many services respond with OK when they aren't initialized, and some respond with SKIP/SKIPPED/FAILED. E.g.: pcvt will show "SKIP", but geli2 will show "OK". Neither of these two are enabled for me though. You may get it from here: http://www.cokane.org/files/rc_fancy-cokane5.patch Further: I am very open to suggestions regarding the rc.d/* system and its reporting mechanisms. I am even thinking that it might be a good idea to offer an overhauled set of scripts that forces functionality into the following framework: rc job offers result code (from which the OK,SKIP,ERROR, etc... are picked) rc job offers short (< 20 char) status message. This could be printed in a nice fashion just after the "Running start XXX", "Running stop YYY", which we currently display. rc job (or rc itself) offers name of job (geli2, moused, etc...). Thus, the lines are nice, consistent, and fluid. The "short status message" above would most likely be truncated to 20 chars (or so.). Hopefully, some of this can then start to be put into an rc-reporter such that I could run a command that could give me a nice report of rc/init: moused FAILED "short message" Gentoo has a nice script named rc-status that does similar. Though I am not too fond of its output format (job name at left, status at right edge, hard to find out what failed in a multiline report). Try this latest version, and drop a line back with your thoughts, criticisms, etc.... -- Coleman Kane cokane@cokane.org From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 03:23:40 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 96FEC16A40A for ; Mon, 1 May 2006 03:23:40 +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 4A7E843D5E for ; Mon, 1 May 2006 03:23:36 +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 k413NW7o038474; Sun, 30 Apr 2006 22:23:33 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44557F34.3020906@centtech.com> Date: Sun, 30 Apr 2006 22:23:32 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Coleman Kane References: <20060420035530.F1A5A16A4E0@hub.freebsd.org> <20060420132543.GB37150@wjv.com> <4447D2F7.1070408@centtech.com> <346a80220604232037mb6f98a0x5fab21622de5ce3c@mail.gmail.com> <444C51BA.3020905@centtech.com> <20060424131508.GB23163@pint.candc.home> <444CD48A.4060501@centtech.com> <444CE475.30104@centtech.com> <20060430231621.GA551@pint.candc.home> In-Reply-To: <20060430231621.GA551@pint.candc.home> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1431/Sun Apr 30 12:46:15 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: 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: Mon, 01 May 2006 03:23:40 -0000 Coleman Kane wrote: > On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: >> Eric Anderson wrote: >> >> Actually, some other things got changed somewhere in the history, that >> broke some things and assumptions I was making. This patch has them >> fixed, and I've tested it with all the different options: >> >> http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 >> >> It's missing the defaults/rc.conf diffs, but you should already know those. >> >> >> Eric >> > > I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. > > This allows the use of: > rc_fancy="YES" ---> Turns on fancy reporting (w/o color) > rc_fancy_color="YES" ---> Turns on fancy reporting (w/ color), needs > rc_fancy="YES" > rc_fancy_colour="YES" ---> Same as above for you on the other side of > the pond. > rc_fancy_verbose="YES" --> Turn on more verbose activity messages. > This will cause what appear to be "false > positives", where an unused service is > "OK" instead of "SKIP". > > You can also customize the colors, the widths of the message > brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and > the contents of the message (OK versus GOOD versus BUENO). > > Also, we have the following message combinations: > OK ---> Universal good message > SKIP,SKIPPED ---> Two methods for conveying the same idea? > ERROR,FAILED ---> Ditto above, for failure cases > > Should we just have 3 different messages, rather than 5 messages > in 3 categories? Yes, that's something that started with my first patch, and never got ironed out. I think it should be: OK SKIPPED FAILED and possibly also: ERROR The difference between FAILED and ERROR would be that FAILED means the service did not start at all, and ERROR means it started but had some kind of error response. > TODO: One thing I am trying to figure out is how to get the > terminal to report its width, in columns (which is something > that VT100+ supports). I just don't know how to do it from a > script. I looked into that too, without finding a good way to do that. > TODO: Get better reporting from the rc.d/* scripts (and whatever > other services we track). Right now, if verbose is on, many > services respond with OK when they aren't initialized, and > some respond with SKIP/SKIPPED/FAILED. E.g.: pcvt will show > "SKIP", but geli2 will show "OK". Neither of these two are > enabled for me though. I agree here, and started looking into many of the scripts there now. There are a lot that need tweaking, but in the long run, I think it would be very nice and clean, and allow for some nice reporting and logging. > You may get it from here: > http://www.cokane.org/files/rc_fancy-cokane5.patch > > > Further: > > I am very open to suggestions regarding the rc.d/* system and its > reporting mechanisms. I am even thinking that it might be a good > idea to offer an overhauled set of scripts that forces functionality > into the following framework: > rc job offers result code (from which the OK,SKIP,ERROR, etc... are > picked) > rc job offers short (< 20 char) status message. This could be printed > in a nice fashion just after the "Running start XXX", "Running stop > YYY", which we currently display. > rc job (or rc itself) offers name of job (geli2, moused, etc...). > > Thus, the lines are nice, consistent, and fluid. The "short status > message" above would most likely be truncated to 20 chars (or so.). > > Hopefully, some of this can then start to be put into an rc-reporter > such that I could run a command that could give me a nice report of > rc/init: > moused FAILED "short message" > > Gentoo has a nice script named rc-status that does similar. Though > I am not too fond of its output format (job name at left, status at > right edge, hard to find out what failed in a multiline report). > > Try this latest version, and drop a line back with your thoughts, > criticisms, etc.... Thanks again for taking hold of this and driving it further! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 03: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 A8F5E16A400 for ; Mon, 1 May 2006 03:34:55 +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 458AE43D45 for ; Mon, 1 May 2006 03:34:55 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k413Ys8t046701 for ; Sun, 30 Apr 2006 22:34:54 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <445581DE.50901@centtech.com> Date: Sun, 30 Apr 2006 22:34:54 -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/1432/Sun Apr 30 21:24:21 2006 on mh1.centtech.com X-Virus-Status: Clean Subject: Boot manager beep (revisited) 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, 01 May 2006 03:34:55 -0000 This thread: http://lists.freebsd.org/pipermail/freebsd-stable/2005-December/020572.html mentions a patch to disable the boot manager beep, and also discusses having it optional. I don't have enough asm-fu to make that option happen, but I can tell you, that on laptops, that beep is really annoying, and amazingly loud. Is this just waiting for an able minded person to code up the options and submit? Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 04:44: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 2CC7416A403 for ; Mon, 1 May 2006 04:44:18 +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 E0BDD43D49 for ; Mon, 1 May 2006 04:44:17 +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 885C219F2C; Sun, 30 Apr 2006 21:44:16 -0700 (PDT) Message-ID: <4455921F.7060900@bitfreak.org> Date: Sun, 30 Apr 2006 21:44:15 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Eric Anderson References: <445581DE.50901@centtech.com> In-Reply-To: <445581DE.50901@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 04:44:18 -0000 Eric Anderson wrote: > This thread: > http://lists.freebsd.org/pipermail/freebsd-stable/2005-December/020572.html > > mentions a patch to disable the boot manager beep, and also discusses > having it optional. I don't have enough asm-fu to make that option > happen, but I can tell you, that on laptops, that beep is really > annoying, and amazingly loud. Is this just waiting for an able minded > person to code up the options and submit? Most laptops have a PC speaker volume control or on/off at boot in the BIOS. From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 05:04: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 8049016C452; Mon, 1 May 2006 05:04:26 +0000 (UTC) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6800243D5D; Mon, 1 May 2006 05:04:23 +0000 (GMT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.13.4/8.13.4) with ESMTP id k4154NFg006328; Sun, 30 Apr 2006 22:04:23 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.13.4/8.13.4) with ESMTP id k4154Nb8051900; Sun, 30 Apr 2006 22:04:23 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.13.4/8.13.4/Submit) id k4154M7N051860; Sun, 30 Apr 2006 22:04:22 -0700 (PDT) (envelope-from frank@exit.com) X-Authentication-Warning: realtime.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: Iantcho Vassilev In-Reply-To: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Sun, 30 Apr 2006 22:04:22 -0700 Message-Id: <1146459862.40842.1.camel@realtime.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV 0.88/1432/Sun Apr 30 19:24:21 2006 on tinker.exit.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, FreeBSD Questions Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 May 2006 05:04:26 -0000 On Mon, 2006-05-01 at 00:09 +0300, Iantcho Vassilev wrote: > "incompetent idiots." quote > > What do you think about it? "It is better to remain silent and be thought a fool, than to speak, and remove all doubt." -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 05:30: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 D4E2316A580 for ; Mon, 1 May 2006 05:28:23 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18E5D43D46 for ; Mon, 1 May 2006 05:28:22 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from gothmog.pc (aris.bedc.ondsl.gr [62.103.39.226]) (authenticated bits=128) by igloo.linux.gr (8.13.6/8.13.6/Debian-1) with ESMTP id k415RpHG017835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 May 2006 08:27:53 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.6/8.13.6) with ESMTP id k415RtFw089082; Mon, 1 May 2006 08:27:55 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from giorgos@localhost) by gothmog.pc (8.13.6/8.13.6/Submit) id k415Rto1089081; Mon, 1 May 2006 08:27:55 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Mon, 1 May 2006 08:27:55 +0300 From: Giorgos Keramidas To: Eric Anderson Message-ID: <20060501052755.GA88897@gothmog.pc> References: <445581DE.50901@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <445581DE.50901@centtech.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.832, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.57, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: freebsd-hackers@freebsd.org Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 05:30:30 -0000 On 2006-04-30 22:34, Eric Anderson wrote: > This thread: > http://lists.freebsd.org/pipermail/freebsd-stable/2005-December/020572.html > > mentions a patch to disable the boot manager beep, and also > discusses having it optional. I don't have enough asm-fu to make > that option happen, but I can tell you, that on laptops, that beep > is really annoying, and amazingly loud. Is this just waiting for an > able minded person to code up the options and submit? I don't like the beep either, so I usually patch my systems manually to include something very similar: # Index: boot0.S # =================================================================== # --- boot0.S (.../branches/ncvs/src/sys/boot/i386/boot0) (revision 45) # +++ boot0.S (.../trunk/src/sys/boot/i386/boot0) (revision 45) # @@ -201,9 +201,7 @@ # /* # * Start of input loop. Beep and take note of time # */ # -main.10: movb $ASCII_BEL,%al # Signal # - callw putchr # beep! # - xorb %ah,%ah # BIOS: Get # +main.10: xorb %ah,%ah # BIOS: Get # int $0x1a # system time # movw %dx,%di # Ticks when # addw _TICKS(%bp),%di # timeout Since this is asm, and it runs very very early in the boot process, we don't have the luxury of making this tunable in `/boot/loader.conf', but there's nothing wrong with making it tunable through an option in our modern `/etc/src.conf' option system. We could use something like the following: WITHOUT_BOOTEASY_BEEP= yes and then we can add the necessary Makefile-foo in `/usr/src/sys/boot' to turn this to a preprocessor #define. Does something like the following sound reasonable (I haven't had a chance to run this through a build-test, so use with care). The default behavior should be to *include* a beep, but it can be turned off by setting WITHOUT_BOOTEASY_BEEP in `/etc/src.conf'. # Index: boot0.S # =================================================================== # --- boot0.S (.../branches/ncvs/src/sys/boot/i386/boot0) (revision 47) # +++ boot0.S (.../trunk/src/sys/boot/i386/boot0) (revision 47) # @@ -201,8 +201,11 @@ # /* # * Start of input loop. Beep and take note of time # */ # -main.10: movb $ASCII_BEL,%al # Signal # +main.10: # +#ifdef BOOTEASY_BEEP # + movb $ASCII_BEL,%al # Signal # callw putchr # beep! # +#endif # xorb %ah,%ah # BIOS: Get # int $0x1a # system time # movw %dx,%di # Ticks when # Index: Makefile # =================================================================== # --- Makefile (.../branches/ncvs/src/sys/boot/i386/boot0) (revision 47) # +++ Makefile (.../trunk/src/sys/boot/i386/boot0) (revision 47) # @@ -54,6 +54,10 @@ # -DTICKS=${BOOT_BOOT0_TICKS} \ # -DCOMSPEED=${BOOT_BOOT0_COMCONSOLE_SPEED} # # +.if !defined(WITHOUT_BOOTEASY_BEEP) || (${WITHOUT_BOOTEASY_BEEP} != "no" && ${WITHOUT_BOOTEASY_BEEP} != "NO") # +CFLAGS+=-DBOOTEASY_BEEP # +.endif # + # LDFLAGS=-N -e start -Ttext ${BOOT_BOOT0_ORG} -Wl,-S,--oformat,binary # # .include From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 09:31:40 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 BAE6A16A401; Mon, 1 May 2006 09:31:40 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53FAC43D45; Mon, 1 May 2006 09:31:39 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.138] (helo=anti-virus01-09) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1FaUkk-0006Tl-Ag; Mon, 01 May 2006 10:31:38 +0100 Received: from [80.192.58.117] (helo=[192.168.0.2]) by asmtp-out6.blueyonder.co.uk with esmtp (Exim 4.52) id 1FaUkg-0006LW-L2; Mon, 01 May 2006 10:31:34 +0100 Message-ID: <4455D576.2020000@dial.pipex.com> Date: Mon, 01 May 2006 10:31:34 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: Giorgos Keramidas , freebsd-hackers@freebsd.org References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> In-Reply-To: <20060501052755.GA88897@gothmog.pc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 09:31:40 -0000 Giorgos Keramidas wrote: >On 2006-04-30 22:34, Eric Anderson wrote: > > >>This thread: >>http://lists.freebsd.org/pipermail/freebsd-stable/2005-December/020572.html >> >>mentions a patch to disable the boot manager beep, and also >>discusses having it optional. >> >Does something like the following sound reasonable (I haven't had a >chance to run this through a build-test, so use with care). The >default behavior should be to *include* a beep, but it can be turned >off by setting WITHOUT_BOOTEASY_BEEP in `/etc/src.conf'. > > I have a very similar patch which I pulled from somewhere not long after switching to 5.4. That wrapped the beep inside #ifdef SIO (which I assumed was something standard, but don't know) so that you got a beep with a serial console and not without. I can see the advantage of the beep when running headless, but for anything with a console the beep just seems like something out of the 1970s. My vote (fwiw) would be to reverse the logic and have WITH_BOOTEASY_BEEP so that it's off by default unless you turn it on with the option *or* if you have a serial console (assuming that SIO is something standard). At the same time I also patched so that NTFS filesystem was recognised as "DOS", to get rid of the ?? on standard dual-boot Win/FreeBSD machines. For me, this still comes in under 512 bytes, though I don't know by how much since the make process seems to pad to 512 bytes. The ?? has been a recurring "complaint" and the fix was easy enough and "works for me" (TM). --Alex From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 10:15: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 6503D16A405 for ; Mon, 1 May 2006 10:15:58 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DF1643D45 for ; Mon, 1 May 2006 10:15:56 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (aris.bedc.ondsl.gr [62.103.39.226]) (authenticated bits=128) by igloo.linux.gr (8.13.6/8.13.6/Debian-1) with ESMTP id k41AFew4001073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 May 2006 13:15:43 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.6/8.13.6) with ESMTP id k41AFjVG051157; Mon, 1 May 2006 13:15:45 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.6/8.13.6/Submit) id k41AFiFx051156; Mon, 1 May 2006 13:15:44 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Mon, 1 May 2006 13:15:44 +0300 From: Giorgos Keramidas To: Alex Zbyslaw Message-ID: <20060501101544.GA51137@gothmog.pc> References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> <4455D576.2020000@dial.pipex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4455D576.2020000@dial.pipex.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.395, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.80, BAYES_00 -2.60, DNS_FROM_RFC_ABUSE 0.20) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 10:15:58 -0000 On 2006-05-01 10:31, Alex Zbyslaw wrote: >Giorgos Keramidas wrote: >>On 2006-04-30 22:34, Eric Anderson wrote: >>> This thread: >>> http://lists.freebsd.org/pipermail/freebsd-stable/2005-December/020572.html >>> >>> mentions a patch to disable the boot manager beep, and also >>> discusses having it optional. >> >> Does something like the following sound reasonable (I haven't >> had a chance to run this through a build-test, so use with >> care). The default behavior should be to *include* a beep, >> but it can be turned off by setting WITHOUT_BOOTEASY_BEEP in >> `/etc/src.conf'. > > I have a very similar patch which I pulled from somewhere not > long after switching to 5.4. That wrapped the beep inside > #ifdef SIO (which I assumed was something standard, but don't > know) so that you got a beep with a serial console and not > without. > > I can see the advantage of the beep when running headless, but > for anything with a console the beep just seems like something > out of the 1970s. My vote (fwiw) would be to reverse the logic > and have WITH_BOOTEASY_BEEP so that it's off by default unless > you turn it on with the option *or* if you have a serial > console (assuming that SIO is something standard). I'd certainly prefer it if the beep was turned *off* by default, but I'm not sure if that's what everyone prefers. This is why I opted for keeping the current behavior and making my personal preference an option :) From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 10:29: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 B4C8516A406 for ; Mon, 1 May 2006 10:29:23 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 475DF43D4C for ; Mon, 1 May 2006 10:29:22 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.12.11) with ESMTP id k41ATBqB048848; Mon, 1 May 2006 03:29:11 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id k41ATBth048847; Mon, 1 May 2006 03:29:11 -0700 (PDT) (envelope-from rizzo) Date: Mon, 1 May 2006 03:29:11 -0700 From: Luigi Rizzo To: Giorgos Keramidas Message-ID: <20060501032910.B48307@xorpc.icir.org> References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> <4455D576.2020000@dial.pipex.com> <20060501101544.GA51137@gothmog.pc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20060501101544.GA51137@gothmog.pc>; from keramida@ceid.upatras.gr on Mon, May 01, 2006 at 01:15:44PM +0300 Cc: freebsd-hackers@freebsd.org, Alex Zbyslaw Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 10:29:23 -0000 On Mon, May 01, 2006 at 01:15:44PM +0300, Giorgos Keramidas wrote: ... > I'd certainly prefer it if the beep was turned *off* by default, > but I'm not sure if that's what everyone prefers. This is why I > opted for keeping the current behavior and making my personal > preference an option :) i do prefer it off. and my laptop has no volume control available at boot. many new laptops have everything in software, which means very little controls available at boot time. cheers luigi From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 10:49: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 8DD4816A405 for ; Mon, 1 May 2006 10:49:00 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1E9943D53 for ; Mon, 1 May 2006 10:48:57 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (aris.bedc.ondsl.gr [62.103.39.226]) (authenticated bits=128) by igloo.linux.gr (8.13.6/8.13.6/Debian-1) with ESMTP id k41AmaXU002320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 May 2006 13:48:39 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.6/8.13.6) with ESMTP id k41Amf5i055277; Mon, 1 May 2006 13:48:41 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.6/8.13.6/Submit) id k41Amevi055276; Mon, 1 May 2006 13:48:40 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Mon, 1 May 2006 13:48:40 +0300 From: Giorgos Keramidas To: Luigi Rizzo Message-ID: <20060501104840.GA55248@gothmog.pc> References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> <4455D576.2020000@dial.pipex.com> <20060501101544.GA51137@gothmog.pc> <20060501032910.B48307@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060501032910.B48307@xorpc.icir.org> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.395, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.80, BAYES_00 -2.60, DNS_FROM_RFC_ABUSE 0.20) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org, Alex Zbyslaw Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 10:49:00 -0000 On 2006-05-01 03:29, Luigi Rizzo wrote: > On Mon, May 01, 2006 at 01:15:44PM +0300, Giorgos Keramidas wrote: > ... > > I'd certainly prefer it if the beep was turned *off* by default, > > but I'm not sure if that's what everyone prefers. This is why I > > opted for keeping the current behavior and making my personal > > preference an option :) > > i do prefer it off. > and my laptop has no volume control available at boot. > many new laptops have everything in software, which means > very little controls available at boot time. I know the feeling. The lack of a control in my laptop was what initially prompted me to look at ways to turn it off :) From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 10:49: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 3FA5716A40A for ; Mon, 1 May 2006 10:49:38 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8336843D48 for ; Mon, 1 May 2006 10:49:37 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 8A4ED2083; Mon, 1 May 2006 12:49:32 +0200 (CEST) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -2.4/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 189AD2082; Mon, 1 May 2006 12:49:32 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id EAA4F33C31; Mon, 1 May 2006 12:49:31 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Allen References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <20060430211517.GA11971@freebie.xs4all.nl> <200604302035.50870.slackwarewolf@comcast.net> Date: Mon, 01 May 2006 12:49:31 +0200 In-Reply-To: <200604302035.50870.slackwarewolf@comcast.net> (slackwarewolf@comcast.net's message of "Sun, 30 Apr 2006 20:35:50 -0400") Message-ID: <86mze2vx38.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 01 May 2006 10:49:38 -0000 Allen writes: > If you watch Revolution OS, Linus points out that his main thing for > doing Linux was that he wanted something like he had used at the > university he was at and he says it was SunOS. Sun OS / Solaris, are > straight BSD. Wrong. Solaris is SysV with some BSD bits tacked on. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 10:55:08 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 057B616A408; Mon, 1 May 2006 10:55:07 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A0E743D76; Mon, 1 May 2006 10:55:07 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 799F52085; Mon, 1 May 2006 12:55:02 +0200 (CEST) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -2.4/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id F35902082; Mon, 1 May 2006 12:55:01 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id CBBF333C31; Mon, 1 May 2006 12:55:01 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Alex Zbyslaw References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> <4455D576.2020000@dial.pipex.com> Date: Mon, 01 May 2006 12:55:01 +0200 In-Reply-To: <4455D576.2020000@dial.pipex.com> (Alex Zbyslaw's message of "Mon, 01 May 2006 10:31:34 +0100") Message-ID: <86iroqvwu2.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, Giorgos Keramidas Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 10:55:08 -0000 Alex Zbyslaw writes: > At the same time I also patched so that NTFS filesystem was > recognised as "DOS", to get rid of the ?? on standard dual-boot > Win/FreeBSD machines. Huh? I did that more than a year ago: des@xps /usr/src% ncvs log -r1.14 sys/boot/i386/boot0/boot0.S | tail RELENG_5: 1.10.0.2 RELENG_5_BP: 1.10 keyword substitution: kv total revisions: 18; selected revisions: 1 description: ---------------------------- revision 1.14 date: 2005/02/08 20:43:04; author: des; state: Exp; lines: +2 -2 Remove type 0x4 (FAT12 <32MB) to make room for type 0x7 (NTFS). =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 12:17: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 7930A16A410 for ; Mon, 1 May 2006 12:17:13 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11BC543D45 for ; Mon, 1 May 2006 12:17:12 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.137] (helo=anti-virus01-08) by smtp-out3.blueyonder.co.uk with smtp (Exim 4.52) id 1FaXKu-0001B0-Uz; Mon, 01 May 2006 13:17:08 +0100 Received: from [80.192.58.117] (helo=[192.168.0.2]) by asmtp-out2.blueyonder.co.uk with esmtp (Exim 4.52) id 1FaXKu-00006o-CI; Mon, 01 May 2006 13:17:08 +0100 Message-ID: <4455FC43.4060001@dial.pipex.com> Date: Mon, 01 May 2006 13:17:07 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: Giorgos Keramidas References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> <4455D576.2020000@dial.pipex.com> <20060501101544.GA51137@gothmog.pc> In-Reply-To: <20060501101544.GA51137@gothmog.pc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 12:17:13 -0000 Giorgos Keramidas wrote: >I'd certainly prefer it if the beep was turned *off* by default, >but I'm not sure if that's what everyone prefers. This is why I >opted for keeping the current behavior and making my personal >preference an option :) > > The beep didn't appear until 5.X (and generated quite a few complaints), so the weight of history is behind no beep! The only argument in favour of the beep that I ever so was headless machines. I suspect this could easily turn into a bit of a bikeshed, and a way to turn off beeps without patching boot.S every time would be good regardless of what the default is. But my vote definitely goes for: headless=beep, headed=no beep. IMHO, the beep in 5.X astonished me (in a minor, but particularly irritating, way) and I bet you'd get lots of people saying "thank you for getting rid of that damn beep". The trouble I see with on-by-default is that many people won't realise they can now turn it off. I probably shouldn't suggest that it should be an option in sysinstall ;-) --Alex From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 12:22: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 C70E516A408 for ; Mon, 1 May 2006 12:22:57 +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 08B4043D72 for ; Mon, 1 May 2006 12:22:53 +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 k41CMkBO059846; Mon, 1 May 2006 07:22:46 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4455FD95.3080001@centtech.com> Date: Mon, 01 May 2006 07:22:45 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Giorgos Keramidas References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> <4455D576.2020000@dial.pipex.com> <20060501101544.GA51137@gothmog.pc> <20060501032910.B48307@xorpc.icir.org> <20060501104840.GA55248@gothmog.pc> In-Reply-To: <20060501104840.GA55248@gothmog.pc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1433/Mon May 1 03:10:05 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: Luigi Rizzo , Alex Zbyslaw , freebsd-hackers@freebsd.org Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 12:22:57 -0000 Giorgos Keramidas wrote: > On 2006-05-01 03:29, Luigi Rizzo wrote: >> On Mon, May 01, 2006 at 01:15:44PM +0300, Giorgos Keramidas wrote: >> ... >>> I'd certainly prefer it if the beep was turned *off* by default, >>> but I'm not sure if that's what everyone prefers. This is why I >>> opted for keeping the current behavior and making my personal >>> preference an option :) >> i do prefer it off. >> and my laptop has no volume control available at boot. >> many new laptops have everything in software, which means >> very little controls available at boot time. > > I know the feeling. The lack of a control in my laptop was what > initially prompted me to look at ways to turn it off :) Me too. I have no way to turn it off in the BIOS. Does having a beep at the boot prompt really help out those who are visually impaired? Seem that there are 100 other hurdles that would make that pretty much useless in the end. As far as headless booting, the beep is nice, but could be an optional loader.conf tweak that enables a kernel beep instead, right? I have lots of headless machines, and a beep is barely heard over the roar of thousands of hard drives and many tens of tons of AC rumbling. Maybe an alternate option is to compile both the beeping and a beepless boot loader, and have the boot0cfg program install the right one depending on a command line option? Hmm.. Maybe that's too cheesy.. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 12:32:15 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 0D3F016A428 for ; Mon, 1 May 2006 12:32:15 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out2.blueyonder.co.uk (smtp-out2.blueyonder.co.uk [195.188.213.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4D1C43D70 for ; Mon, 1 May 2006 12:32:10 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.140] (helo=anti-virus02-07) by smtp-out2.blueyonder.co.uk with smtp (Exim 4.52) id 1FaXZQ-0007TP-Tm; Mon, 01 May 2006 13:32:08 +0100 Received: from [80.192.58.117] (helo=[192.168.0.2]) by asmtp-out5.blueyonder.co.uk with esmtp (Exim 4.52) id 1FaXZQ-00081r-CK; Mon, 01 May 2006 13:32:08 +0100 Message-ID: <4455FFC7.7000707@dial.pipex.com> Date: Mon, 01 May 2006 13:32:07 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> <4455D576.2020000@dial.pipex.com> <86iroqvwu2.fsf@xps.des.no> In-Reply-To: <86iroqvwu2.fsf@xps.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 12:32:15 -0000 Dag-Erling Sm=F8rgrav wrote: >Alex Zbyslaw writes: > =20 > >>At the same time I also patched so that NTFS filesystem was >>recognised as "DOS", to get rid of the ?? on standard dual-boot >>Win/FreeBSD machines. >> =20 >> > >Huh? I did that more than a year ago: > > =20 > You beat me to it then ;-) =20 http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D1506483+0+archive/2005/fre= ebsd-questions/20050612.freebsd-questions Since I'm on 5.4 I guess I just haven't got your changes yet. Thanks=20 for doing it, though. Be nice not to have to remember to patch boot.S=20 every time I rebuild. --Alex From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 12:52: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 51B3B16A408 for ; Mon, 1 May 2006 12:52:39 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DD3843D75 for ; Mon, 1 May 2006 12:52:26 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (aris.bedc.ondsl.gr [62.103.39.226]) (authenticated bits=128) by igloo.linux.gr (8.13.6/8.13.6/Debian-1) with ESMTP id k41Cq5CS006802 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 May 2006 15:52:07 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.6/8.13.6) with ESMTP id k41Cq9Oa056685; Mon, 1 May 2006 15:52:09 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.6/8.13.6/Submit) id k41Cq9QP056684; Mon, 1 May 2006 15:52:09 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Mon, 1 May 2006 15:52:09 +0300 From: Giorgos Keramidas To: Alex Zbyslaw Message-ID: <20060501125209.GA56659@gothmog.pc> References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> <4455D576.2020000@dial.pipex.com> <20060501101544.GA51137@gothmog.pc> <4455FC43.4060001@dial.pipex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4455FC43.4060001@dial.pipex.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.397, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.80, BAYES_00 -2.60, DNS_FROM_RFC_ABUSE 0.20) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 12:52:39 -0000 On 2006-05-01 13:17, Alex Zbyslaw wrote: >Giorgos Keramidas wrote: >> I'd certainly prefer it if the beep was turned *off* by default, >> but I'm not sure if that's what everyone prefers. This is why I >> opted for keeping the current behavior and making my personal >> preference an option :) > > The beep didn't appear until 5.X (and generated quite a few > complaints), so the weight of history is behind no beep! Ah! Good point. From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 12:54: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 80C5116A448 for ; Mon, 1 May 2006 12:54:24 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49BB143D98 for ; Mon, 1 May 2006 12:54:03 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (aris.bedc.ondsl.gr [62.103.39.226]) (authenticated bits=128) by igloo.linux.gr (8.13.6/8.13.6/Debian-1) with ESMTP id k41CrUW2006895 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 May 2006 15:53:32 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.6/8.13.6) with ESMTP id k41CrZTn056706; Mon, 1 May 2006 15:53:35 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.6/8.13.6/Submit) id k41CrZgE056705; Mon, 1 May 2006 15:53:35 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Mon, 1 May 2006 15:53:35 +0300 From: Giorgos Keramidas To: Eric Anderson Message-ID: <20060501125334.GB56659@gothmog.pc> References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> <4455D576.2020000@dial.pipex.com> <20060501101544.GA51137@gothmog.pc> <20060501032910.B48307@xorpc.icir.org> <20060501104840.GA55248@gothmog.pc> <4455FD95.3080001@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4455FD95.3080001@centtech.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.397, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.80, BAYES_00 -2.60, DNS_FROM_RFC_ABUSE 0.20) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: Luigi Rizzo , Alex Zbyslaw , freebsd-hackers@freebsd.org Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 12:54:24 -0000 On 2006-05-01 07:22, Eric Anderson wrote: > Maybe an alternate option is to compile both the beeping and a beepless > boot loader, and have the boot0cfg program install the right one > depending on a command line option? Hmm.. Maybe that's too cheesy.. It is kind of overkill. This is a big change for such a small thing and it requires touching boot0cfg too. From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 12:55: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 2335A16A435 for ; Mon, 1 May 2006 12:55:47 +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 3A22443D53 for ; Mon, 1 May 2006 12:55:38 +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 k41CtX1B061139; Mon, 1 May 2006 07:55:33 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44560544.5030201@centtech.com> Date: Mon, 01 May 2006 07:55:32 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Giorgos Keramidas References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> <4455D576.2020000@dial.pipex.com> <20060501101544.GA51137@gothmog.pc> <20060501032910.B48307@xorpc.icir.org> <20060501104840.GA55248@gothmog.pc> <4455FD95.3080001@centtech.com> <20060501125334.GB56659@gothmog.pc> In-Reply-To: <20060501125334.GB56659@gothmog.pc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1433/Mon May 1 03:10:05 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: Luigi Rizzo , Alex Zbyslaw , freebsd-hackers@freebsd.org Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 12:55:47 -0000 Giorgos Keramidas wrote: > On 2006-05-01 07:22, Eric Anderson wrote: >> Maybe an alternate option is to compile both the beeping and a beepless >> boot loader, and have the boot0cfg program install the right one >> depending on a command line option? Hmm.. Maybe that's too cheesy.. > > It is kind of overkill. This is a big change for such a small thing > and it requires touching boot0cfg too. True. Ok, then I opt for no more beep by default unless either optionally built in or headless. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 13:03: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 AFE4C16A403; Mon, 1 May 2006 13:03:57 +0000 (UTC) (envelope-from dl@leo.org) Received: from post.leo.org (toler.leo.org [83.220.155.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 287C143D4C; Mon, 1 May 2006 13:03:56 +0000 (GMT) (envelope-from dl@leo.org) Received: by post.leo.org (Postfix, from userid 1000) id A5F171940CA; Mon, 1 May 2006 15:03:54 +0200 (CEST) Date: Mon, 1 May 2006 15:03:54 +0200 From: Daniel Lang To: Alex Zbyslaw Message-ID: <20060501130354.GA17701@toler.leo.org> References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> <4455D576.2020000@dial.pipex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4455D576.2020000@dial.pipex.com> X-Geek: GCS/CC d-- s: a C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r+++ y+++ User-Agent: Mutt/1.5.9i Cc: freebsd-hackers@freebsd.org, Giorgos Keramidas Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 13:03:57 -0000 Hi, Alex Zbyslaw wrote on Mon, May 01, 2006 at 10:31:34AM +0100: [..] > >off by setting WITHOUT_BOOTEASY_BEEP in `/etc/src.conf'. [..] > WITH_BOOTEASY_BEEP so that it's off by default unless you turn it on Regardless what you decide, if such an option is created, please call it WITH/WITHOUT_BOOTZERO_BEEP or WITH/WITHOUT_BOOT0_BEEP. The current FreeBSD bootmanager is called 'boot0'. It has replaced booteasy (which was indeed used in the past) centuries ago. Nitpicking, ;-) Daniel From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 13:07: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 1B1E716A401 for ; Mon, 1 May 2006 13:07:14 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 226DF43D45 for ; Mon, 1 May 2006 13:07:12 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (aris.bedc.ondsl.gr [62.103.39.226]) (authenticated bits=128) by igloo.linux.gr (8.13.6/8.13.6/Debian-1) with ESMTP id k41D6xlC007990 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 May 2006 16:07:00 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.6/8.13.6) with ESMTP id k41D74KE057037; Mon, 1 May 2006 16:07:04 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.6/8.13.6/Submit) id k41D74vo057036; Mon, 1 May 2006 16:07:04 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Mon, 1 May 2006 16:07:04 +0300 From: Giorgos Keramidas To: Daniel Lang Message-ID: <20060501130704.GA57024@gothmog.pc> References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> <4455D576.2020000@dial.pipex.com> <20060501130354.GA17701@toler.leo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060501130354.GA17701@toler.leo.org> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.397, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.80, BAYES_00 -2.60, DNS_FROM_RFC_ABUSE 0.20) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org, Alex Zbyslaw Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 13:07:14 -0000 On 2006-05-01 15:03, Daniel Lang wrote: > Alex Zbyslaw wrote on Mon, May 01, 2006 at 10:31:34AM +0100: > [..] > > >off by setting WITHOUT_BOOTEASY_BEEP in `/etc/src.conf'. > [..] > > WITH_BOOTEASY_BEEP so that it's off by default unless you turn it on > > Regardless what you decide, if such an option is created, please > call it WITH/WITHOUT_BOOTZERO_BEEP or WITH/WITHOUT_BOOT0_BEEP. > > The current FreeBSD bootmanager is called 'boot0'. It has replaced > booteasy (which was indeed used in the past) centuries ago. I'll do, thanks for the careful review of the diff :) From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 13:23: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 33FDA16A413 for ; Mon, 1 May 2006 13:23:41 +0000 (UTC) (envelope-from maslanbsd@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id B29B943D45 for ; Mon, 1 May 2006 13:23:40 +0000 (GMT) (envelope-from maslanbsd@gmail.com) Received: by wproxy.gmail.com with SMTP id 57so2581887wri for ; Mon, 01 May 2006 06:23:40 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RrrE911xiQfSDl4zb2bO0ZJ35yLXMbs5mnAzHwAKJKRMJ1WY1EDZc/JZXIzXxZH2Mf8/XwDEFiJwiE1P3XP6mQcv+qxA9AoOD6TT0WRuve5XjVpeI3WsJPHRzMe727ur6Cqo1J+46LjGsJAgYsMWqQXqr512PwkY1wUSptfy0m4= Received: by 10.54.113.11 with SMTP id l11mr2703143wrc; Mon, 01 May 2006 06:23:40 -0700 (PDT) Received: by 10.54.96.7 with HTTP; Mon, 1 May 2006 06:23:40 -0700 (PDT) Message-ID: <319cceca0605010623k5bb62479r1ceec72e55b5eca9@mail.gmail.com> Date: Mon, 1 May 2006 13:23:40 +0000 From: Maslan To: "=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=" In-Reply-To: <86mze2vx38.fsf@xps.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <20060430211517.GA11971@freebie.xs4all.nl> <200604302035.50870.slackwarewolf@comcast.net> <86mze2vx38.fsf@xps.des.no> Cc: freebsd-hackers@freebsd.org, Allen Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 01 May 2006 13:23:41 -0000 On 5/1/06, Dag-Erling Sm=F8rgrav wrote: > Allen writes: > > If you watch Revolution OS, Linus points out that his main thing for > > doing Linux was that he wanted something like he had used at the > > university he was at and he says it was SunOS. Sun OS / Solaris, are > > straight BSD. > > Wrong. Solaris is SysV with some BSD bits tacked on. > > DES > -- > Dag-Erling Sm=F8rgrav - des@des.no > _______________________________________________ > 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= " > That's right, but sunos (earlier than solaris) was based on bsd. www : http://en.wikipedia.org/wiki/Sunos -- I'm Searching For Perfection, So Even If U Need Portability U've To Use Assembly ;-) http://www.maslanlab.org http://libosdk.berlios.de From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 13:48:12 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 77E7316A405 for ; Mon, 1 May 2006 13:48:12 +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 E778C43D46 for ; Mon, 1 May 2006 13:48:11 +0000 (GMT) (envelope-from luke@foolishgames.com) Received: from [192.168.0.150] (24-176-58-245.dhcp.klmz.mi.charter.com [24.176.58.245]) (authenticated bits=0) by mail.foolishgames.com (8.13.6/8.13.3) with ESMTP id k41Dluml053729 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Mon, 1 May 2006 09:47:57 -0400 (EDT) (envelope-from luke@foolishgames.com) Message-Id: 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: Mon, 1 May 2006 09:47:54 -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: <319cceca0605010623k5bb62479r1ceec72e55b5eca9@mail.gmail.com> References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <20060430211517.GA11971@freebie.xs4all.nl> <200604302035.50870.slackwarewolf@comcast.net> <86mze2vx38.fsf@xps.des.no> <319cceca0605010623k5bb62479r1ceec72e55b5eca9@mail.gmail.com> To: Maslan 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/1433/Mon May 1 04:10:05 2006 on mail.foolishgames.com X-Virus-Status: Clean Cc: =?ISO-8859-1?Q? Dag-Erling_Sm=F8rgrav ?= , Allen , freebsd-hackers@freebsd.org Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 01 May 2006 13:48:12 -0000 On May 1, 2006, at 9:23 AM, Maslan wrote: > > That's right, but sunos (earlier than solaris) was based on bsd. > www : http://en.wikipedia.org/wiki/Sunos > Sun OS is how I got into BSD. My first sparc had sunos 4.21 on it. It was definitely BSD. It makes sense considering Bill Joy co- founded sun. I ended up putting NetBSD on that sparc and later found FreeBSD. 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 Mon May 1 14:09: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 4AD8416A402 for ; Mon, 1 May 2006 14:09:37 +0000 (UTC) (envelope-from jsbowden@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8B2D43D46 for ; Mon, 1 May 2006 14:09:36 +0000 (GMT) (envelope-from jsbowden@gmail.com) Received: by nz-out-0102.google.com with SMTP id 12so1323600nzp for ; Mon, 01 May 2006 07:09:36 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=n1yW127dZVz3XJwlIf6+I2n67ZlQynrzbL3BXviotlX0UwgkICkCK+/gI2vTeL3m6SiuFhUDGb0Vr2KLkigK4DNF4bhuci3vJy0OiQZ6Ybyj5hthchNkFtfbQ/yWaOVczQq3L9dk2OzFcZrxsaCD8xi6gINJieSt/VftsBFzkUc= Received: by 10.64.253.15 with SMTP id a15mr3418868qbi; Mon, 01 May 2006 07:09:36 -0700 (PDT) Received: by 10.65.216.2 with HTTP; Mon, 1 May 2006 07:09:36 -0700 (PDT) Message-ID: Date: Mon, 1 May 2006 10:09:36 -0400 From: "Jamie Bowden" Sender: jsbowden@gmail.com To: "Lucas Holt" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <20060430211517.GA11971@freebie.xs4all.nl> <200604302035.50870.slackwarewolf@comcast.net> <86mze2vx38.fsf@xps.des.no> <319cceca0605010623k5bb62479r1ceec72e55b5eca9@mail.gmail.com> X-Google-Sender-Auth: adc4fc3e46609a4c Cc: Maslan , Allen , freebsd-hackers@freebsd.org, =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 01 May 2006 14:09:37 -0000 On 5/1/06, Lucas Holt wrote: > > On May 1, 2006, at 9:23 AM, Maslan wrote: > > > > That's right, but sunos (earlier than solaris) was based on bsd. > > www : http://en.wikipedia.org/wiki/Sunos > Sun OS is how I got into BSD. My first sparc had sunos 4.21 on it. > It was definitely BSD. It makes sense considering Bill Joy co- > founded sun. I ended up putting NetBSD on that sparc and later found > FreeBSD. SunOS 4.1.4 (aka Solaris 1.1.?(1 maybe? It's been a long time now.)) was the final release of SunOS 4. It was basically 4.1.3_U1 with a couple of other minor fixes merged in. I spent a very long time porting software from SunOS 4 to Solaris 2.3|4|5 during that time as we transitioned from our older Sun4c|m based servers and hosts to Sun4u (which of course only ran Solaris 2.5 and beyond (or Solaris 4 with patches, but those weren't general release and outside of Sun and Pixar, I don't know anyone who had access to these)). Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 14:22:17 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 2DCCE16A406 for ; Mon, 1 May 2006 14:22:17 +0000 (UTC) (envelope-from slackwarewolf@comcast.net) Received: from rwcrmhc14.comcast.net (rwcrmhc14.comcast.net [216.148.227.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 495FF43D5E for ; Mon, 1 May 2006 14:22:09 +0000 (GMT) (envelope-from slackwarewolf@comcast.net) Received: from [192.168.0.100] (c-69-246-87-201.hsd1.mi.comcast.net[69.246.87.201]) by comcast.net (rwcrmhc14) with ESMTP id <20060501142208m1400ru6n1e>; Mon, 1 May 2006 14:22:08 +0000 From: Allen To: freebsd-hackers@freebsd.org Date: Mon, 1 May 2006 10:24:38 -0400 User-Agent: KMail/1.8 References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <319cceca0605010623k5bb62479r1ceec72e55b5eca9@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605011024.39126.slackwarewolf@comcast.net> Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 01 May 2006 14:22:17 -0000 On Monday 01 May 2006 9:47 am, Lucas Holt wrote: > On May 1, 2006, at 9:23 AM, Maslan wrote: > > That's right, but sunos (earlier than solaris) was based on bsd. > > www : http://en.wikipedia.org/wiki/Sunos > > Sun OS is how I got into BSD. My first sparc had sunos 4.21 on it. > It was definitely BSD. It makes sense considering Bill Joy co- > founded sun. I ended up putting NetBSD on that sparc and later found > FreeBSD. That's what I meant. I knew Bill Joy was the man who helped found it, and McKusick was actually offered a job there too as a single digit employee. This is actually in the DVD I recommended "20 Years of Berkeley UNIX" as Marshal is the man who does the speech in the movie. That's where I learned about SunOS being BSD. He said it was ;) Well, not exactly he said the idea behind Sun was "Dude we are going to sell BSD on these computers come join us". By the way if anyone here doesn't have this DVD I really say go get it. It's got some good stuff in there and even a bit on the history of Multi user OSs. -Allen From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 18:03: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 44F5616A40B for ; Mon, 1 May 2006 18:03:22 +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 ADB3F43D62 for ; Mon, 1 May 2006 18:03:20 +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 k41I360V019536; Mon, 1 May 2006 14:03:12 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 1 May 2006 13:36:13 -0400 User-Agent: KMail/1.9.1 References: <445581DE.50901@centtech.com> <20060501101544.GA51137@gothmog.pc> <4455FC43.4060001@dial.pipex.com> In-Reply-To: <4455FC43.4060001@dial.pipex.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605011336.15167.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1433/Mon May 1 04:10:05 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Giorgos Keramidas , Alex Zbyslaw Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 18:03:22 -0000 On Monday 01 May 2006 08:17, Alex Zbyslaw wrote: > Giorgos Keramidas wrote: > > >I'd certainly prefer it if the beep was turned *off* by default, > >but I'm not sure if that's what everyone prefers. This is why I > >opted for keeping the current behavior and making my personal > >preference an option :) > > > > > The beep didn't appear until 5.X (and generated quite a few complaints), No, the beep was always there, but it was only generated for invalid input until 5.x. It was changed when boot0sio was merged into boot0 in rev 1.9 of boot0.S by phk@. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 18:03: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 6AB8416A415 for ; Mon, 1 May 2006 18:03:22 +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 AD9C443D60 for ; Mon, 1 May 2006 18:03:20 +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 k41I360W019536; Mon, 1 May 2006 14:03:12 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 1 May 2006 14:02:08 -0400 User-Agent: KMail/1.9.1 References: <445581DE.50901@centtech.com> <20060501130354.GA17701@toler.leo.org> <20060501130704.GA57024@gothmog.pc> In-Reply-To: <20060501130704.GA57024@gothmog.pc> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605011402.10403.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1433/Mon May 1 04:10:05 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Giorgos Keramidas , Alex Zbyslaw Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 18:03:22 -0000 On Monday 01 May 2006 09:07, Giorgos Keramidas wrote: > On 2006-05-01 15:03, Daniel Lang wrote: > > Alex Zbyslaw wrote on Mon, May 01, 2006 at 10:31:34AM +0100: > > [..] > > > >off by setting WITHOUT_BOOTEASY_BEEP in `/etc/src.conf'. > > [..] > > > WITH_BOOTEASY_BEEP so that it's off by default unless you turn it on > > > > Regardless what you decide, if such an option is created, please > > call it WITH/WITHOUT_BOOTZERO_BEEP or WITH/WITHOUT_BOOT0_BEEP. > > > > The current FreeBSD bootmanager is called 'boot0'. It has replaced > > booteasy (which was indeed used in the past) centuries ago. > > I'll do, thanks for the careful review of the diff :) How about the patch below. It restores the behavior of the beep only happening for invalid input by axeing the BSD/OS partition type from the lookup table. Index: boot0.S =================================================================== RCS file: /usr/cvs/src/sys/boot/i386/boot0/boot0.S,v retrieving revision 1.14 diff -u -r1.14 boot0.S --- boot0.S 8 Feb 2005 20:43:04 -0000 1.14 +++ boot0.S 1 May 2006 18:00:37 -0000 @@ -29,7 +29,7 @@ .set PRT_OFF,0x1be # Partition table .set TBL0SZ,0x3 # Table 0 size - .set TBL1SZ,0xb # Table 1 size + .set TBL1SZ,0xa # Table 1 size .set MAGIC,0xaa55 # Magic: bootable .set B0MAGIC,0xbb66 # Identification @@ -198,12 +198,16 @@ movb _OPT(%bp),%dl # Display decw %si # default callw putkey # key + jmp main.7_1 # Skip beep /* - * Start of input loop. Beep and take note of time + * Users's last try was bad, beep in displeasure. */ main.10: movb $ASCII_BEL,%al # Signal callw putchr # beep! - xorb %ah,%ah # BIOS: Get +/* + * Start of input loop. Take note of time + */ +main.7_1: xorb %ah,%ah # BIOS: Get int $0x1a # system time movw %dx,%di # Ticks when addw _TICKS(%bp),%di # timeout @@ -410,7 +414,7 @@ * These values indicate bootable types we know the names of. */ .byte 0x1, 0x6, 0x7, 0xb, 0xc, 0xe, 0x83 - .byte 0x9f, 0xa5, 0xa6, 0xa9 + .byte 0xa5, 0xa6, 0xa9 /* * These are offsets that match the known names above and point to the strings * that will be printed. os_misc will be used if the search of the above table @@ -423,7 +427,6 @@ .byte os_dos-. # Windows .byte os_dos-. # Windows .byte os_linux-. # Linux - .byte os_bsd-. # BSD/OS .byte os_freebsd-. # FreeBSD .byte os_bsd-. # OpenBSD .byte os_bsd-. # NetBSD -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 18:03: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 643CD16A403 for ; Mon, 1 May 2006 18:03:26 +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 8D8DC43D68 for ; Mon, 1 May 2006 18:03:23 +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 k41I360U019536; Mon, 1 May 2006 14:03:06 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 1 May 2006 13:30:00 -0400 User-Agent: KMail/1.9.1 References: <445581DE.50901@centtech.com> <20060501104840.GA55248@gothmog.pc> <4455FD95.3080001@centtech.com> In-Reply-To: <4455FD95.3080001@centtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605011330.03301.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1433/Mon May 1 04:10:05 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: Giorgos Keramidas , Luigi Rizzo , Alex Zbyslaw Subject: Re: Boot manager beep (revisited) 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, 01 May 2006 18:03:26 -0000 On Monday 01 May 2006 08:22, Eric Anderson wrote: > Giorgos Keramidas wrote: > > On 2006-05-01 03:29, Luigi Rizzo wrote: > >> On Mon, May 01, 2006 at 01:15:44PM +0300, Giorgos Keramidas wrote: > >> ... > >>> I'd certainly prefer it if the beep was turned *off* by default, > >>> but I'm not sure if that's what everyone prefers. This is why I > >>> opted for keeping the current behavior and making my personal > >>> preference an option :) > >> i do prefer it off. > >> and my laptop has no volume control available at boot. > >> many new laptops have everything in software, which means > >> very little controls available at boot time. > > > > I know the feeling. The lack of a control in my laptop was what > > initially prompted me to look at ways to turn it off :) > > Me too. I have no way to turn it off in the BIOS. > > Does having a beep at the boot prompt really help out those who are > visually impaired? Seem that there are 100 other hurdles that would > make that pretty much useless in the end. As far as headless booting, > the beep is nice, but could be an optional loader.conf tweak that > enables a kernel beep instead, right? I have lots of headless machines, > and a beep is barely heard over the roar of thousands of hard drives and > many tens of tons of AC rumbling. > > Maybe an alternate option is to compile both the beeping and a beepless > boot loader, and have the boot0cfg program install the right one > depending on a command line option? Hmm.. Maybe that's too cheesy.. It used to only beep for invalid input, but when someone was adding some other feature a while back they had to make the beep happen on startup as well due to size constraints. I'm not a fan of it either. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 18:07: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 87B9B16A456 for ; Mon, 1 May 2006 18:07:50 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr4.xs4all.nl (smtp-vbr4.xs4all.nl [194.109.24.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5A8643D6E for ; Mon, 1 May 2006 18:07:49 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr4.xs4all.nl (8.13.6/8.13.6) with ESMTP id k41I7kQR021126; Mon, 1 May 2006 20:07:46 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id k41I7jt5019511; Mon, 1 May 2006 20:07:45 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id k41I7jcQ019510; Mon, 1 May 2006 20:07:45 +0200 (CEST) (envelope-from wb) Date: Mon, 1 May 2006 20:07:45 +0200 From: Wilko Bulte To: Maslan Message-ID: <20060501180745.GC19342@freebie.xs4all.nl> References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <20060430211517.GA11971@freebie.xs4all.nl> <200604302035.50870.slackwarewolf@comcast.net> <86mze2vx38.fsf@xps.des.no> <319cceca0605010623k5bb62479r1ceec72e55b5eca9@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <319cceca0605010623k5bb62479r1ceec72e55b5eca9@mail.gmail.com> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , Allen , freebsd-hackers@freebsd.org Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 01 May 2006 18:07:52 -0000 On Mon, May 01, 2006 at 01:23:40PM +0000, Maslan wrote.. > On 5/1/06, Dag-Erling Smørgrav wrote: > >Allen writes: > >> If you watch Revolution OS, Linus points out that his main thing for > >> doing Linux was that he wanted something like he had used at the > >> university he was at and he says it was SunOS. Sun OS / Solaris, are > >> straight BSD. > > > >Wrong. Solaris is SysV with some BSD bits tacked on. > > > >DES > >-- > >Dag-Erling Smørgrav - des@des.no > >_______________________________________________ > >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" > > > > That's right, but sunos (earlier than solaris) was based on bsd. > www : http://en.wikipedia.org/wiki/Sunos Be specific: SunOS 3.x and 4.x are BSD. The later ones are called Solaris 1.x IIRC Solaris 2.x also calls itself SunOS, just take a close look at the boot messages. It is as DES already pointed out a SysV derivative wikipedia stinks too often to be taken as gospel... -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 18:08:40 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 4B2E916A421 for ; Mon, 1 May 2006 18:08:40 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr9.xs4all.nl (smtp-vbr9.xs4all.nl [194.109.24.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52D1243D7D for ; Mon, 1 May 2006 18:08:26 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr9.xs4all.nl (8.13.6/8.13.6) with ESMTP id k41I8GIW026408; Mon, 1 May 2006 20:08:22 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id k41I8FWh019526; Mon, 1 May 2006 20:08:15 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id k41I8FkF019525; Mon, 1 May 2006 20:08:15 +0200 (CEST) (envelope-from wb) Date: Mon, 1 May 2006 20:08:15 +0200 From: Wilko Bulte To: Lucas Holt Message-ID: <20060501180815.GD19342@freebie.xs4all.nl> References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <20060430211517.GA11971@freebie.xs4all.nl> <200604302035.50870.slackwarewolf@comcast.net> <86mze2vx38.fsf@xps.des.no> <319cceca0605010623k5bb62479r1ceec72e55b5eca9@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Maslan , Allen , freebsd-hackers@freebsd.org, =?us-ascii?B?PT9JU08tODg1OS0xP1E/?= Dag-Erling_Sm=F8rgrav ?= Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 01 May 2006 18:08:40 -0000 On Mon, May 01, 2006 at 09:47:54AM -0400, Lucas Holt wrote.. > > On May 1, 2006, at 9:23 AM, Maslan wrote: > > > >That's right, but sunos (earlier than solaris) was based on bsd. > >www : http://en.wikipedia.org/wiki/Sunos > > > > Sun OS is how I got into BSD. My first sparc had sunos 4.21 on it. 4.1.2 I guess. > It was definitely BSD. It makes sense considering Bill Joy co- > founded sun. I ended up putting NetBSD on that sparc and later found > FreeBSD. > > Lucas Holt > Luke@FoolishGames.com > ________________________________________________________ > FoolishGames.com (Jewel Fan Site) > JustJournal.com (Free blogging) > FoolishGames.net (Enemy Territory site) > > > _______________________________________________ > 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" --- end of quoted text --- -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 18:10: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 C381516A448 for ; Mon, 1 May 2006 18:10:14 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr3.xs4all.nl (smtp-vbr3.xs4all.nl [194.109.24.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BA0F43D73 for ; Mon, 1 May 2006 18:10:05 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr3.xs4all.nl (8.13.6/8.13.6) with ESMTP id k41I9skL002401; Mon, 1 May 2006 20:09:55 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id k41I9reT019549; Mon, 1 May 2006 20:09:53 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id k41I9rjK019548; Mon, 1 May 2006 20:09:53 +0200 (CEST) (envelope-from wb) Date: Mon, 1 May 2006 20:09:53 +0200 From: Wilko Bulte To: Jamie Bowden Message-ID: <20060501180953.GE19342@freebie.xs4all.nl> References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <20060430211517.GA11971@freebie.xs4all.nl> <200604302035.50870.slackwarewolf@comcast.net> <86mze2vx38.fsf@xps.des.no> <319cceca0605010623k5bb62479r1ceec72e55b5eca9@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Maslan , Lucas Holt , Allen , Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , freebsd-hackers@freebsd.org Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 01 May 2006 18:10:15 -0000 On Mon, May 01, 2006 at 10:09:36AM -0400, Jamie Bowden wrote.. > On 5/1/06, Lucas Holt wrote: > > > >On May 1, 2006, at 9:23 AM, Maslan wrote: > >> > >> That's right, but sunos (earlier than solaris) was based on bsd. > >> www : http://en.wikipedia.org/wiki/Sunos > > >Sun OS is how I got into BSD. My first sparc had sunos 4.21 on it. > >It was definitely BSD. It makes sense considering Bill Joy co- > >founded sun. I ended up putting NetBSD on that sparc and later found > >FreeBSD. > > SunOS 4.1.4 (aka Solaris 1.1.?(1 maybe? It's been a long time now.)) > was the final release of SunOS 4. It was basically 4.1.3_U1 with a > couple of other minor fixes merged in. I spent a very long time > porting software from SunOS 4 to Solaris 2.3|4|5 during that time as > we transitioned from our older Sun4c|m based servers and hosts to > Sun4u (which of course only ran Solaris 2.5 and beyond (or Solaris 4 2.5 on the sun4u? Wasn't that 2.5.1 minimum? -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 18:29:45 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 9A0A616A400 for ; Mon, 1 May 2006 18:29:45 +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 4440743D82 for ; Mon, 1 May 2006 18:29:34 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers.102a7e@mired.org) Received: (qmail 44049 invoked by uid 1001); 1 May 2006 18:29:34 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Mon, 01 May 2006 14:29:32 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <17494.21387.484871.980369@bhuda.mired.org> Date: Mon, 1 May 2006 14:29:31 -0400 To: Wilko Bulte In-Reply-To: <20060501180745.GC19342@freebie.xs4all.nl> References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <20060430211517.GA11971@freebie.xs4all.nl> <200604302035.50870.slackwarewolf@comcast.net> <86mze2vx38.fsf@xps.des.no> <319cceca0605010623k5bb62479r1ceec72e55b5eca9@mail.gmail.com> <20060501180745.GC19342@freebie.xs4all.nl> 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: Maslan , Allen , freebsd-hackers@freebsd.org, Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 01 May 2006 18:29:45 -0000 In <20060501180745.GC19342@freebie.xs4all.nl>, Wilko Bulte typed: > On Mon, May 01, 2006 at 01:23:40PM +0000, Maslan wrote.. > > On 5/1/06, Dag-Erling Sm=F8rgrav wrote: > > >Allen writes: > > >> If you watch Revolution OS, Linus points out that his main thing= for > > >> doing Linux was that he wanted something like he had used at the= > > >> university he was at and he says it was SunOS. Sun OS / Solaris,= are > > >> straight BSD. > > > > > >Wrong. Solaris is SysV with some BSD bits tacked on. > > > > > >DES > > >-- > > >Dag-Erling Sm=F8rgrav - des@des.no > > >_______________________________________________ > > >freebsd-hackers@freebsd.org mailing list > > >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@free= bsd.org" > > > > >=20 > > That's right, but sunos (earlier than solaris) was based on bsd. > > www : http://en.wikipedia.org/wiki/Sunos >=20 > Be specific: SunOS 3.x and 4.x are BSD. The later ones are called > Solaris 1.x IIRC > Solaris 2.x also calls itself SunOS, just take a close look at the bo= ot > messages. It is as DES already pointed out a SysV derivative SunOS 5.x was the OS. Solaris 2.x was the OS plus the windowing system. So when you booted a system running Solaris 2.x, you were greated with SunOS 5.x banenrs. Common usage was that SunOS 5 systems were called "Solaris", and SunOS 4 systems were called SunOS, regardless of how Sun labelled the distribution media. > wikipedia stinks too often to be taken as gospel... The entry for Solaris largely agrees with my recollection of events. It's been long enough that I'm a bit hazy on the details, but there's nothing in it I know to be wrong. =09=09=09http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more informatio= n. From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 18:43:15 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 1C41316A402 for ; Mon, 1 May 2006 18:43:15 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr6.xs4all.nl (smtp-vbr6.xs4all.nl [194.109.24.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CE6043D48 for ; Mon, 1 May 2006 18:43:14 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr6.xs4all.nl (8.13.6/8.13.6) with ESMTP id k41IhAtO013990; Mon, 1 May 2006 20:43:10 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id k41Ih9BU019843; Mon, 1 May 2006 20:43:09 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id k41Ih9Vm019842; Mon, 1 May 2006 20:43:09 +0200 (CEST) (envelope-from wb) Date: Mon, 1 May 2006 20:43:09 +0200 From: Wilko Bulte To: Mike Meyer Message-ID: <20060501184309.GB19811@freebie.xs4all.nl> References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <20060430211517.GA11971@freebie.xs4all.nl> <200604302035.50870.slackwarewolf@comcast.net> <86mze2vx38.fsf@xps.des.no> <319cceca0605010623k5bb62479r1ceec72e55b5eca9@mail.gmail.com> <20060501180745.GC19342@freebie.xs4all.nl> <17494.21387.484871.980369@bhuda.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <17494.21387.484871.980369@bhuda.mired.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Maslan , Allen , freebsd-hackers@freebsd.org, Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 01 May 2006 18:43:15 -0000 On Mon, May 01, 2006 at 02:29:31PM -0400, Mike Meyer wrote.. > In <20060501180745.GC19342@freebie.xs4all.nl>, Wilko Bulte typed: > > On Mon, May 01, 2006 at 01:23:40PM +0000, Maslan wrote.. > > > On 5/1/06, Dag-Erling Smørgrav wrote: > > > >Allen writes: > > > >> If you watch Revolution OS, Linus points out that his main thing for > > > >> doing Linux was that he wanted something like he had used at the > > > >> university he was at and he says it was SunOS. Sun OS / Solaris, are > > > >> straight BSD. > > > > > > > >Wrong. Solaris is SysV with some BSD bits tacked on. > > > > > > > >DES > > > >-- > > > >Dag-Erling Smørgrav - des@des.no > > > >_______________________________________________ > > > >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" > > > > > > > > > > That's right, but sunos (earlier than solaris) was based on bsd. > > > www : http://en.wikipedia.org/wiki/Sunos > > > > Be specific: SunOS 3.x and 4.x are BSD. The later ones are called > > Solaris 1.x IIRC > > Solaris 2.x also calls itself SunOS, just take a close look at the boot > > messages. It is as DES already pointed out a SysV derivative > > SunOS 5.x was the OS. Solaris 2.x was the OS plus the windowing > system. So when you booted a system running Solaris 2.x, you were > greated with SunOS 5.x banenrs. Common usage was that SunOS 5 systems > were called "Solaris", and SunOS 4 systems were called SunOS, > regardless of how Sun labelled the distribution media. Well.. Sun at some point took 4.1.3 and 4.1.4 into the Solaris naming scheme. Just confusing to a lot of people. > > wikipedia stinks too often to be taken as gospel... > > The entry for Solaris largely agrees with my recollection of > events. It's been long enough that I'm a bit hazy on the details, but > there's nothing in it I know to be wrong. I meant wikipedia in general, not this one in particular. Its a bit like people claiming "Bill Gates invented the internet". Or Al Gore for that matter ;) -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 19:07:01 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 A57C916A409 for ; Mon, 1 May 2006 19:07:01 +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 831B743D76 for ; Mon, 1 May 2006 19:06:52 +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 k41J6jqF013423; Mon, 1 May 2006 12:06:45 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k41J6jph013421; Mon, 1 May 2006 12:06:45 -0700 Date: Mon, 1 May 2006 12:06:45 -0700 From: Brooks Davis To: Eric Anderson Message-ID: <20060501190645.GB4315@odin.ac.hmc.edu> References: <20060420035530.F1A5A16A4E0@hub.freebsd.org> <20060420132543.GB37150@wjv.com> <4447D2F7.1070408@centtech.com> <346a80220604232037mb6f98a0x5fab21622de5ce3c@mail.gmail.com> <444C51BA.3020905@centtech.com> <20060424131508.GB23163@pint.candc.home> <444CD48A.4060501@centtech.com> <444CE475.30104@centtech.com> <20060430231621.GA551@pint.candc.home> <44557F34.3020906@centtech.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3lcZGd9BuhuYXNfi" Content-Disposition: inline In-Reply-To: <44557F34.3020906@centtech.com> 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: hackers@freebsd.org, Coleman Kane 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: Mon, 01 May 2006 19:07:02 -0000 --3lcZGd9BuhuYXNfi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 30, 2006 at 10:23:32PM -0500, Eric Anderson wrote: > Coleman Kane wrote: > >On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: > >>Eric Anderson wrote: > >> > >>Actually, some other things got changed somewhere in the history, that= =20 > >>broke some things and assumptions I was making. This patch has them=20 > >>fixed, and I've tested it with all the different options: > >> > >>http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 > >> > >>It's missing the defaults/rc.conf diffs, but you should already know=20 > >>those. > >> > >> > >>Eric > >> > > > >I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. > > > >This allows the use of: > >rc_fancy=3D"YES" ---> Turns on fancy reporting (w/o color) > >rc_fancy_color=3D"YES" ---> Turns on fancy reporting (w/ color), needs > > rc_fancy=3D"YES" > >rc_fancy_colour=3D"YES" ---> Same as above for you on the other side of > > the pond. > >rc_fancy_verbose=3D"YES" --> Turn on more verbose activity messages. > > This will cause what appear to be "false > > positives", where an unused service is > > "OK" instead of "SKIP". > > > >You can also customize the colors, the widths of the message > >brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and > >the contents of the message (OK versus GOOD versus BUENO). > > > >Also, we have the following message combinations: > >OK ---> Universal good message > >SKIP,SKIPPED ---> Two methods for conveying the same idea? > >ERROR,FAILED ---> Ditto above, for failure cases > > > >Should we just have 3 different messages, rather than 5 messages > >in 3 categories? >=20 > Yes, that's something that started with my first patch, and never got=20 > ironed out. I think it should be: > OK > SKIPPED > FAILED > and possibly also: > ERROR >=20 > The difference between FAILED and ERROR would be that FAILED means the=20 > service did not start at all, and ERROR means it started but had some=20 > kind of error response. FAILED vs ERROR seems confusing. I'd be inclined toward WARNING vs FAILED or ERROR. -- 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 --3lcZGd9BuhuYXNfi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEVlxEXY6L6fI4GtQRAozqAKCcAQyNAKeQqunsFxWlv5vGKealqwCfWHR4 dUdQK1zF3taz6gBZWEfzeac= =D+bn -----END PGP SIGNATURE----- --3lcZGd9BuhuYXNfi-- From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 19:13: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 6BE0116A41B for ; Mon, 1 May 2006 19:13:30 +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 9AF8243D46 for ; Mon, 1 May 2006 19:13:29 +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 k41JDMUm085924; Mon, 1 May 2006 14:13:23 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44565DD2.1020604@centtech.com> Date: Mon, 01 May 2006 14:13:22 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Brooks Davis References: <20060420035530.F1A5A16A4E0@hub.freebsd.org> <20060420132543.GB37150@wjv.com> <4447D2F7.1070408@centtech.com> <346a80220604232037mb6f98a0x5fab21622de5ce3c@mail.gmail.com> <444C51BA.3020905@centtech.com> <20060424131508.GB23163@pint.candc.home> <444CD48A.4060501@centtech.com> <444CE475.30104@centtech.com> <20060430231621.GA551@pint.candc.home> <44557F34.3020906@centtech.com> <20060501190645.GB4315@odin.ac.hmc.edu> In-Reply-To: <20060501190645.GB4315@odin.ac.hmc.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1433/Mon May 1 03:10:05 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: hackers@freebsd.org, Coleman Kane 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: Mon, 01 May 2006 19:13:30 -0000 Brooks Davis wrote: > On Sun, Apr 30, 2006 at 10:23:32PM -0500, Eric Anderson wrote: >> Coleman Kane wrote: >>> On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: >>>> Eric Anderson wrote: >>>> >>>> Actually, some other things got changed somewhere in the history, that >>>> broke some things and assumptions I was making. This patch has them >>>> fixed, and I've tested it with all the different options: >>>> >>>> http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 >>>> >>>> It's missing the defaults/rc.conf diffs, but you should already know >>>> those. >>>> >>>> >>>> Eric >>>> >>> I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. >>> >>> This allows the use of: >>> rc_fancy="YES" ---> Turns on fancy reporting (w/o color) >>> rc_fancy_color="YES" ---> Turns on fancy reporting (w/ color), needs >>> rc_fancy="YES" >>> rc_fancy_colour="YES" ---> Same as above for you on the other side of >>> the pond. >>> rc_fancy_verbose="YES" --> Turn on more verbose activity messages. >>> This will cause what appear to be "false >>> positives", where an unused service is >>> "OK" instead of "SKIP". >>> >>> You can also customize the colors, the widths of the message >>> brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and >>> the contents of the message (OK versus GOOD versus BUENO). >>> >>> Also, we have the following message combinations: >>> OK ---> Universal good message >>> SKIP,SKIPPED ---> Two methods for conveying the same idea? >>> ERROR,FAILED ---> Ditto above, for failure cases >>> >>> Should we just have 3 different messages, rather than 5 messages >>> in 3 categories? >> Yes, that's something that started with my first patch, and never got >> ironed out. I think it should be: >> OK >> SKIPPED >> FAILED >> and possibly also: >> ERROR >> >> The difference between FAILED and ERROR would be that FAILED means the >> service did not start at all, and ERROR means it started but had some >> kind of error response. > > FAILED vs ERROR seems confusing. I'd be inclined toward WARNING vs > FAILED or ERROR. True, however I still see a difference between FAILED and WARNING. For instance, as an example: a FAILED RAID is different than a RAID with a WARNING. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 19:14:51 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 82A8916A447 for ; Mon, 1 May 2006 19:14:51 +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 E6C0143D4C for ; Mon, 1 May 2006 19:14:49 +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 k41JElMW014641; Mon, 1 May 2006 12:14:47 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k41JElIv014637; Mon, 1 May 2006 12:14:47 -0700 Date: Mon, 1 May 2006 12:14:47 -0700 From: Brooks Davis To: Eric Anderson Message-ID: <20060501191447.GD4315@odin.ac.hmc.edu> References: <4447D2F7.1070408@centtech.com> <346a80220604232037mb6f98a0x5fab21622de5ce3c@mail.gmail.com> <444C51BA.3020905@centtech.com> <20060424131508.GB23163@pint.candc.home> <444CD48A.4060501@centtech.com> <444CE475.30104@centtech.com> <20060430231621.GA551@pint.candc.home> <44557F34.3020906@centtech.com> <20060501190645.GB4315@odin.ac.hmc.edu> <44565DD2.1020604@centtech.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PHCdUe6m4AxPMzOu" Content-Disposition: inline In-Reply-To: <44565DD2.1020604@centtech.com> 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: hackers@freebsd.org, Coleman Kane 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: Mon, 01 May 2006 19:14:51 -0000 --PHCdUe6m4AxPMzOu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 01, 2006 at 02:13:22PM -0500, Eric Anderson wrote: > Brooks Davis wrote: > >On Sun, Apr 30, 2006 at 10:23:32PM -0500, Eric Anderson wrote: > >>Coleman Kane wrote: > >>>On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: > >>>>Eric Anderson wrote: > >>>> > >>>>Actually, some other things got changed somewhere in the history, tha= t=20 > >>>>broke some things and assumptions I was making. This patch has them= =20 > >>>>fixed, and I've tested it with all the different options: > >>>> > >>>>http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 > >>>> > >>>>It's missing the defaults/rc.conf diffs, but you should already know= =20 > >>>>those. > >>>> > >>>> > >>>>Eric > >>>> > >>>I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. > >>> > >>>This allows the use of: > >>>rc_fancy=3D"YES" ---> Turns on fancy reporting (w/o color) > >>>rc_fancy_color=3D"YES" ---> Turns on fancy reporting (w/ color), nee= ds > >>> rc_fancy=3D"YES" > >>>rc_fancy_colour=3D"YES" ---> Same as above for you on the other side = of > >>> the pond. > >>>rc_fancy_verbose=3D"YES" --> Turn on more verbose activity messages. > >>> This will cause what appear to be "false > >>> positives", where an unused service is > >>> "OK" instead of "SKIP". > >>> > >>>You can also customize the colors, the widths of the message > >>>brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and > >>>the contents of the message (OK versus GOOD versus BUENO). > >>> > >>>Also, we have the following message combinations: > >>>OK ---> Universal good message > >>>SKIP,SKIPPED ---> Two methods for conveying the same idea? > >>>ERROR,FAILED ---> Ditto above, for failure cases > >>> > >>>Should we just have 3 different messages, rather than 5 messages > >>>in 3 categories? > >>Yes, that's something that started with my first patch, and never got= =20 > >>ironed out. I think it should be: > >>OK > >>SKIPPED > >>FAILED > >>and possibly also: > >>ERROR > >> > >>The difference between FAILED and ERROR would be that FAILED means the= =20 > >>service did not start at all, and ERROR means it started but had some= =20 > >>kind of error response. > > > >FAILED vs ERROR seems confusing. I'd be inclined toward WARNING vs > >FAILED or ERROR. >=20 > True, however I still see a difference between FAILED and WARNING. For=20 > instance, as an example: a FAILED RAID is different than a RAID with a=20 > WARNING. For that level of detail, the ability to provide additional output seems like the appropriate solution. -- 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 --PHCdUe6m4AxPMzOu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEVl4mXY6L6fI4GtQRArPTAJ9zYMeha+AkrxP0hFn0saBGpdeGhQCfUv/s ioEBgEL8dpIT0JnnLwWh4wo= =GXqc -----END PGP SIGNATURE----- --PHCdUe6m4AxPMzOu-- From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 19:16:38 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 418C216A457 for ; Mon, 1 May 2006 19:16:38 +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 8E7BA43D62 for ; Mon, 1 May 2006 19:16:09 +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 k41JG43q086024; Mon, 1 May 2006 14:16:05 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44565E74.3060801@centtech.com> Date: Mon, 01 May 2006 14:16:04 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Brooks Davis References: <4447D2F7.1070408@centtech.com> <346a80220604232037mb6f98a0x5fab21622de5ce3c@mail.gmail.com> <444C51BA.3020905@centtech.com> <20060424131508.GB23163@pint.candc.home> <444CD48A.4060501@centtech.com> <444CE475.30104@centtech.com> <20060430231621.GA551@pint.candc.home> <44557F34.3020906@centtech.com> <20060501190645.GB4315@odin.ac.hmc.edu> <44565DD2.1020604@centtech.com> <20060501191447.GD4315@odin.ac.hmc.edu> In-Reply-To: <20060501191447.GD4315@odin.ac.hmc.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1433/Mon May 1 03:10:05 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: hackers@freebsd.org, Coleman Kane 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: Mon, 01 May 2006 19:16:38 -0000 Brooks Davis wrote: > On Mon, May 01, 2006 at 02:13:22PM -0500, Eric Anderson wrote: >> Brooks Davis wrote: >>> On Sun, Apr 30, 2006 at 10:23:32PM -0500, Eric Anderson wrote: >>>> Coleman Kane wrote: >>>>> On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: >>>>>> Eric Anderson wrote: >>>>>> >>>>>> Actually, some other things got changed somewhere in the history, that >>>>>> broke some things and assumptions I was making. This patch has them >>>>>> fixed, and I've tested it with all the different options: >>>>>> >>>>>> http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 >>>>>> >>>>>> It's missing the defaults/rc.conf diffs, but you should already know >>>>>> those. >>>>>> >>>>>> >>>>>> Eric >>>>>> >>>>> I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. >>>>> >>>>> This allows the use of: >>>>> rc_fancy="YES" ---> Turns on fancy reporting (w/o color) >>>>> rc_fancy_color="YES" ---> Turns on fancy reporting (w/ color), needs >>>>> rc_fancy="YES" >>>>> rc_fancy_colour="YES" ---> Same as above for you on the other side of >>>>> the pond. >>>>> rc_fancy_verbose="YES" --> Turn on more verbose activity messages. >>>>> This will cause what appear to be "false >>>>> positives", where an unused service is >>>>> "OK" instead of "SKIP". >>>>> >>>>> You can also customize the colors, the widths of the message >>>>> brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and >>>>> the contents of the message (OK versus GOOD versus BUENO). >>>>> >>>>> Also, we have the following message combinations: >>>>> OK ---> Universal good message >>>>> SKIP,SKIPPED ---> Two methods for conveying the same idea? >>>>> ERROR,FAILED ---> Ditto above, for failure cases >>>>> >>>>> Should we just have 3 different messages, rather than 5 messages >>>>> in 3 categories? >>>> Yes, that's something that started with my first patch, and never got >>>> ironed out. I think it should be: >>>> OK >>>> SKIPPED >>>> FAILED >>>> and possibly also: >>>> ERROR >>>> >>>> The difference between FAILED and ERROR would be that FAILED means the >>>> service did not start at all, and ERROR means it started but had some >>>> kind of error response. >>> FAILED vs ERROR seems confusing. I'd be inclined toward WARNING vs >>> FAILED or ERROR. >> True, however I still see a difference between FAILED and WARNING. For >> instance, as an example: a FAILED RAID is different than a RAID with a >> WARNING. > > For that level of detail, the ability to provide additional output seems > like the appropriate solution. Yes, true, but you'd still want to show something (I would think) in the [ ]'s to keep it consistent. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 19:29: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 2DE4A16A407 for ; Mon, 1 May 2006 19:29:25 +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 D156443D55 for ; Mon, 1 May 2006 19:29:23 +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 k41JTLwF017370; Mon, 1 May 2006 12:29:21 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k41JTLDs017369; Mon, 1 May 2006 12:29:21 -0700 Date: Mon, 1 May 2006 12:29:20 -0700 From: Brooks Davis To: Eric Anderson Message-ID: <20060501192920.GE4315@odin.ac.hmc.edu> References: <444C51BA.3020905@centtech.com> <20060424131508.GB23163@pint.candc.home> <444CD48A.4060501@centtech.com> <444CE475.30104@centtech.com> <20060430231621.GA551@pint.candc.home> <44557F34.3020906@centtech.com> <20060501190645.GB4315@odin.ac.hmc.edu> <44565DD2.1020604@centtech.com> <20060501191447.GD4315@odin.ac.hmc.edu> <44565E74.3060801@centtech.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+SfteS7bOf3dGlBC" Content-Disposition: inline In-Reply-To: <44565E74.3060801@centtech.com> 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: hackers@freebsd.org, Coleman Kane 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: Mon, 01 May 2006 19:29:25 -0000 --+SfteS7bOf3dGlBC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 01, 2006 at 02:16:04PM -0500, Eric Anderson wrote: > Brooks Davis wrote: > >On Mon, May 01, 2006 at 02:13:22PM -0500, Eric Anderson wrote: > >>Brooks Davis wrote: > >>>On Sun, Apr 30, 2006 at 10:23:32PM -0500, Eric Anderson wrote: > >>>>Coleman Kane wrote: > >>>>>On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: > >>>>>>Eric Anderson wrote: > >>>>>> > >>>>>>Actually, some other things got changed somewhere in the history,= =20 > >>>>>>that broke some things and assumptions I was making. This patch ha= s=20 > >>>>>>them fixed, and I've tested it with all the different options: > >>>>>> > >>>>>>http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 > >>>>>> > >>>>>>It's missing the defaults/rc.conf diffs, but you should already kno= w=20 > >>>>>>those. > >>>>>> > >>>>>> > >>>>>>Eric > >>>>>> > >>>>>I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. > >>>>> > >>>>>This allows the use of: > >>>>>rc_fancy=3D"YES" ---> Turns on fancy reporting (w/o color) > >>>>>rc_fancy_color=3D"YES" ---> Turns on fancy reporting (w/ color), n= eeds > >>>>> rc_fancy=3D"YES" > >>>>>rc_fancy_colour=3D"YES" ---> Same as above for you on the other sid= e of > >>>>> the pond. > >>>>>rc_fancy_verbose=3D"YES" --> Turn on more verbose activity messages. > >>>>> This will cause what appear to be "false > >>>>> positives", where an unused service is > >>>>> "OK" instead of "SKIP". > >>>>> > >>>>>You can also customize the colors, the widths of the message > >>>>>brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and > >>>>>the contents of the message (OK versus GOOD versus BUENO). > >>>>> > >>>>>Also, we have the following message combinations: > >>>>>OK ---> Universal good message > >>>>>SKIP,SKIPPED ---> Two methods for conveying the same idea? > >>>>>ERROR,FAILED ---> Ditto above, for failure cases > >>>>> > >>>>>Should we just have 3 different messages, rather than 5 messages > >>>>>in 3 categories? > >>>>Yes, that's something that started with my first patch, and never got= =20 > >>>>ironed out. I think it should be: > >>>>OK > >>>>SKIPPED > >>>>FAILED > >>>>and possibly also: > >>>>ERROR > >>>> > >>>>The difference between FAILED and ERROR would be that FAILED means th= e=20 > >>>>service did not start at all, and ERROR means it started but had some= =20 > >>>>kind of error response. > >>>FAILED vs ERROR seems confusing. I'd be inclined toward WARNING vs > >>>FAILED or ERROR. > >>True, however I still see a difference between FAILED and WARNING. For= =20 > >>instance, as an example: a FAILED RAID is different than a RAID with a= =20 > >>WARNING. > > > >For that level of detail, the ability to provide additional output seems > >like the appropriate solution. >=20 > Yes, true, but you'd still want to show something (I would think) in the= =20 > [ ]'s to keep it consistent. My feeling is that anything short of complete success should report WARNING and a message unless it actually totally failed in which case FAILED or ERROR (I slightly perfer ERROR) should be used. -- 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 --+SfteS7bOf3dGlBC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEVmGPXY6L6fI4GtQRAoRRAKDe3Jz202bcirmwS8CRRBAVyDavggCcDzrx IivIEKdZACW9zfQ+BvVUjbU= =wT+/ -----END PGP SIGNATURE----- --+SfteS7bOf3dGlBC-- From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 20:27: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 4076016A407 for ; Mon, 1 May 2006 20:27:16 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (megan.kiwi-computer.com [63.224.10.3]) by mx1.FreeBSD.org (Postfix) with SMTP id 9C3F743D48 for ; Mon, 1 May 2006 20:27:13 +0000 (GMT) (envelope-from rick@kiwi-computer.com) Received: (qmail 1357 invoked by uid 2001); 1 May 2006 20:27:12 -0000 Date: Mon, 1 May 2006 15:27:11 -0500 From: "Rick C. Petty" To: freebsd-hackers@freebsd.org Message-ID: <20060501202711.GA476@megan.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: gvinum start volume returns EBUSY 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, 01 May 2006 20:27:16 -0000 When rebuilding a degraded plex with "gvinum start volume" on a mounted filesystem, gvinum reports "errno: 16" (EBUSY). In the CVS: src/sys/geom/vinum/geom_vinum_init.c, lines 363-364 (of MAIN, added 2005-Oct-09, rev 1.10.2.1) has the check: if (gv_is_open(p->geom)) return (EBUSY); Why is this the case? The log for that change suggests this is to prevent sync operations from starting when they are already in progress, but that really refers to lines 366-367: if (p->flags & GV_PLEX_SYNCING) return (EINPROGRESS); It seems to me that lines 363-364 should be deleted. If you have a degraded volume but need to keep it mounted (such as /usr or /home, etc.), I can't see any reason why you should be forced to unmount the volume before rebuilding (if the volume is RAID5). Maybe this restriction is useful for non-RAID5 configurations, but gv_rebuild_plex is only called in the context of GV_PLEX_RAID5 on degraded plexes. Maybe I'm misunderstanding something. Feel free to enlighten me! :-) -- Rick C. Petty From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 21:26:42 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 8ED7916A400 for ; Mon, 1 May 2006 21:26:42 +0000 (UTC) (envelope-from cokane@mail.cokane.org) Received: from smtp1.fuse.net (mail-out1.fuse.net [216.68.8.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1401D43D45 for ; Mon, 1 May 2006 21:26:41 +0000 (GMT) (envelope-from cokane@mail.cokane.org) Received: from gx6.fuse.net ([72.49.162.239]) by smtp1.fuse.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20060501212641.KJCQ3018.smtp1.fuse.net@gx6.fuse.net> for ; Mon, 1 May 2006 17:26:41 -0400 Received: from mail.cokane.org ([72.49.162.239]) by gx6.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with ESMTP id <20060501212641.MEPB4722.gx6.fuse.net@mail.cokane.org> for ; Mon, 1 May 2006 17:26:41 -0400 Received: (qmail 2270 invoked by uid 1000); 1 May 2006 17:28:01 -0400 Date: Mon, 1 May 2006 17:28:01 -0400 From: Coleman Kane To: Brooks Davis Message-ID: <20060501212801.GA2254@pint.candc.home> References: <20060424131508.GB23163@pint.candc.home> <444CD48A.4060501@centtech.com> <444CE475.30104@centtech.com> <20060430231621.GA551@pint.candc.home> <44557F34.3020906@centtech.com> <20060501190645.GB4315@odin.ac.hmc.edu> <44565DD2.1020604@centtech.com> <20060501191447.GD4315@odin.ac.hmc.edu> <44565E74.3060801@centtech.com> <20060501192920.GE4315@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060501192920.GE4315@odin.ac.hmc.edu> User-Agent: Mutt/1.5.11 X-Mailman-Approved-At: Mon, 01 May 2006 21:33:22 +0000 Cc: 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: Mon, 01 May 2006 21:26:42 -0000 On Mon, May 01, 2006 at 12:29:20PM -0700, Brooks Davis wrote: > On Mon, May 01, 2006 at 02:16:04PM -0500, Eric Anderson wrote: > > Brooks Davis wrote: > > >On Mon, May 01, 2006 at 02:13:22PM -0500, Eric Anderson wrote: > > >>Brooks Davis wrote: > > >>>On Sun, Apr 30, 2006 at 10:23:32PM -0500, Eric Anderson wrote: > > >>>>Coleman Kane wrote: > > >>>>>On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: > > >>>>>>Eric Anderson wrote: > > >>>>>> > > >>>>>>Actually, some other things got changed somewhere in the history, > > >>>>>>that broke some things and assumptions I was making. This patch has > > >>>>>>them fixed, and I've tested it with all the different options: > > >>>>>> > > >>>>>>http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 > > >>>>>> > > >>>>>>It's missing the defaults/rc.conf diffs, but you should already know > > >>>>>>those. > > >>>>>> > > >>>>>> > > >>>>>>Eric > > >>>>>> > > >>>>>I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. > > >>>>> > > >>>>>This allows the use of: > > >>>>>rc_fancy="YES" ---> Turns on fancy reporting (w/o color) > > >>>>>rc_fancy_color="YES" ---> Turns on fancy reporting (w/ color), needs > > >>>>> rc_fancy="YES" > > >>>>>rc_fancy_colour="YES" ---> Same as above for you on the other side of > > >>>>> the pond. > > >>>>>rc_fancy_verbose="YES" --> Turn on more verbose activity messages. > > >>>>> This will cause what appear to be "false > > >>>>> positives", where an unused service is > > >>>>> "OK" instead of "SKIP". > > >>>>> > > >>>>>You can also customize the colors, the widths of the message > > >>>>>brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and > > >>>>>the contents of the message (OK versus GOOD versus BUENO). > > >>>>> > > >>>>>Also, we have the following message combinations: > > >>>>>OK ---> Universal good message > > >>>>>SKIP,SKIPPED ---> Two methods for conveying the same idea? > > >>>>>ERROR,FAILED ---> Ditto above, for failure cases > > >>>>> > > >>>>>Should we just have 3 different messages, rather than 5 messages > > >>>>>in 3 categories? > > >>>>Yes, that's something that started with my first patch, and never got > > >>>>ironed out. I think it should be: > > >>>>OK > > >>>>SKIPPED > > >>>>FAILED > > >>>>and possibly also: > > >>>>ERROR > > >>>> > > >>>>The difference between FAILED and ERROR would be that FAILED means the > > >>>>service did not start at all, and ERROR means it started but had some > > >>>>kind of error response. > > >>>FAILED vs ERROR seems confusing. I'd be inclined toward WARNING vs > > >>>FAILED or ERROR. > > >>True, however I still see a difference between FAILED and WARNING. For > > >>instance, as an example: a FAILED RAID is different than a RAID with a > > >>WARNING. > > > > > >For that level of detail, the ability to provide additional output seems > > >like the appropriate solution. > > > > Yes, true, but you'd still want to show something (I would think) in the > > [ ]'s to keep it consistent. > > My feeling is that anything short of complete success should report > WARNING and a message unless it actually totally failed in which case > FAILED or ERROR (I slightly perfer ERROR) should be used. > > -- Brooks What situations are we determining get flagged as ERROR versus FAILED? Is FAILED considered to be 'I was able to run the command, but it returned an error code', versus ERROR being 'I could not even run the command!' like bad path, file not found, etc... This point still kind of confuses me (and needs to be well defined). I am an advocate of having three distinct messages: OK, SKIPPED, ERROR. And not even bothering with the different types of ERROR/FAILED other than having extra reporting output. Of course, I am still willing to implement what the consensus is. -- Coleman Kane From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 21:58: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 5DA7116A440 for ; Mon, 1 May 2006 21:58:48 +0000 (UTC) (envelope-from slackwarewolf@comcast.net) Received: from rwcrmhc14.comcast.net (rwcrmhc14.comcast.net [204.127.192.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 448E843D45 for ; Mon, 1 May 2006 21:58:31 +0000 (GMT) (envelope-from slackwarewolf@comcast.net) Received: from [192.168.0.100] (c-69-246-87-201.hsd1.mi.comcast.net[69.246.87.201]) by comcast.net (rwcrmhc14) with ESMTP id <20060501215830m1400rsdmee>; Mon, 1 May 2006 21:58:30 +0000 From: Allen To: freebsd-hackers@freebsd.org Date: Mon, 1 May 2006 18:01:01 -0400 User-Agent: KMail/1.8 References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <17494.21387.484871.980369@bhuda.mired.org> <20060501184309.GB19811@freebie.xs4all.nl> In-Reply-To: <20060501184309.GB19811@freebie.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200605011801.01529.slackwarewolf@comcast.net> Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 01 May 2006 21:58:49 -0000 On Monday 01 May 2006 2:43 pm, Wilko Bulte wrote: > On Mon, May 01, 2006 at 02:29:31PM -0400, Mike Meyer wrote.. > > > In <20060501180745.GC19342@freebie.xs4all.nl>, Wilko Bulte=20 typed: > > > On Mon, May 01, 2006 at 01:23:40PM +0000, Maslan wrote.. > > > > > > > On 5/1/06, Dag-Erling Sm=F8rgrav wrote: > > > > >Allen writes: > > > > >> If you watch Revolution OS, Linus points out that his main thing > > > > >> for doing Linux was that he wanted something like he had used at > > > > >> the university he was at and he says it was SunOS. Sun OS / > > > > >> Solaris, are straight BSD. > > > > SunOS 5.x was the OS. Solaris 2.x was the OS plus the windowing > > system. So when you booted a system running Solaris 2.x, you were > > greated with SunOS 5.x banenrs. Common usage was that SunOS 5 systems > > were called "Solaris", and SunOS 4 systems were called SunOS, > > regardless of how Sun labelled the distribution media. Man I would LOVE to find a good sun box. Nothing huge, just a box I can use= to=20 toy with Solaris and oldschool stuff like early SunOS. I just don't have th= e=20 cash, all I can afford right now are PCs. And I can't even buy a new one of= =20 those for at least a few months. Just want at least one UNIX box in the=20 house. > > Well.. Sun at some point took 4.1.3 and 4.1.4 into the Solaris naming > scheme. Just confusing to a lot of people. Software naming has always been a pain ;) > I meant wikipedia in general, not this one in particular. Its a bit like > people claiming "Bill Gates invented the internet". Or Al Gore for that > matter ;) I use the handle gore on a lot of stuff. You'd be surprised how many people= =20 think I mean that guy. From owner-freebsd-hackers@FreeBSD.ORG Mon May 1 22:07: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 9279C16A603 for ; Mon, 1 May 2006 22:07:25 +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 BECDD43D53 for ; Mon, 1 May 2006 22:07:24 +0000 (GMT) (envelope-from luke@foolishgames.com) Received: from [192.168.0.4] (24-176-58-245.dhcp.klmz.mi.charter.com [24.176.58.245]) (authenticated bits=0) by mail.foolishgames.com (8.13.6/8.13.3) with ESMTP id k41M79ue058201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 May 2006 18:07:10 -0400 (EDT) (envelope-from luke@foolishgames.com) Message-ID: <44568691.2050505@foolishgames.com> Date: Mon, 01 May 2006 18:07:13 -0400 From: Lucas Holt User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Jamie Bowden References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <20060430211517.GA11971@freebie.xs4all.nl> <200604302035.50870.slackwarewolf@comcast.net> <86mze2vx38.fsf@xps.des.no> <319cceca0605010623k5bb62479r1ceec72e55b5eca9@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.1/1434/Mon May 1 15:51:00 2006 on mail.foolishgames.com X-Virus-Status: Clean Cc: Maslan , Allen , freebsd-hackers@freebsd.org, =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 01 May 2006 22:07:28 -0000 Jamie Bowden wrote: > SunOS 4.1.4 (aka Solaris 1.1.?(1 maybe? It's been a long time now.)) > was the final release of SunOS 4. It was basically 4.1.3_U1 with a > couple of other minor fixes merged in. I spent a very long time > porting software from SunOS 4 to Solaris 2.3|4|5 during that time as > we transitioned from our older Sun4c|m based servers and hosts to > Sun4u (which of course only ran Solaris 2.5 and beyond (or Solaris 4 > with patches, but those weren't general release and outside of Sun and > Pixar, I don't know anyone who had access to these)). > > Jamie Bowden > -- > "It was half way to Rivendell when the drugs began to take hold" > Hunter S Tolkien "Fear and Loathing in Barad Dur" > Iain Bowen Well I bought the system for $30 used through a company I worked for. They often bought equipment at auctions. This system came from a large pharmaceutical company with the drive still intact. I used the OS on it for several months. It was an old Sun SparcStation IPC (or ipx?). It only had a floppy drive and netbsd was installable with boot floppies and ftp. The system died on me about 2 years ago and I just bought a newer system on ebay. It was quite easy to change the root password. In sun os you just booted to single user. With solaris you can do it with a netbsd floppy :) Luke From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 00:20: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 D818416A41A for ; Tue, 2 May 2006 00:20:03 +0000 (UTC) (envelope-from aanton@spintech.ro) Received: from smtpx.spintech.ro (smtpx.spintech.ro [81.180.92.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0FBC43D53 for ; Tue, 2 May 2006 00:20:01 +0000 (GMT) (envelope-from aanton@spintech.ro) Received: from [10.0.0.2] (beastie [10.0.0.2]) by smtpx.spintech.ro (Postfix) with ESMTP id CF79B3A4A3 for ; Tue, 2 May 2006 00:53:21 +0000 (UTC) Message-ID: <4456A5B3.2010809@spintech.ro> Date: Tue, 02 May 2006 03:20:03 +0300 From: Alin-Adrian Anton Organization: Spintech Security Systems User-Agent: Mozilla Thunderbird 1.0 (X11/20041229) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: which running thread gests the external signal X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: aanton@spintech.ro List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 00:20:04 -0000 Hi Hackers, I'm working on a threaded daemon and I'm trying to make it sysadmin friendly. For this, I'm working with external signals. I noticed different behaviour between BSD and Linux for this. When I send an external SIGHUP (rehashing the config file) on BSD the thread receiving the signal seems to be "random". On Linux, if I remeber well, all the threads get the signal, sooner or later.. (the signal handler gets executed as many times as the number of running threads) The tests I've done were done some time ago, this is why I must appologise if I get the chance to mix the memories :|. So just in case anyone already knows (on BSD): which thread gets stopped and moves execution to the signal handler function, when the signal is sent by kill(1) to the pid of the daemon, which is the same for all the threads? (sorry if dizzy speaking) And also, is there a way for delegating one special thread to handle all the external signals? (on BSD) Thanks for the time guys. Yours Sincerely, -- Alin-Adrian Anton GPG keyID 0x183087BA (B129 E8F4 7B34 15A9 0785 2F7C 5823 ABA0 1830 87BA) gpg --keyserver pgp.mit.edu --recv-keys 0x183087BA "It is dangerous to be right when the government is wrong." - Voltaire From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 00:52: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 8BB9316A401 for ; Tue, 2 May 2006 00:52:04 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 229F143D45 for ; Tue, 2 May 2006 00:52:04 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k420q20f004072; Mon, 1 May 2006 20:52:02 -0400 (EDT) Date: Mon, 1 May 2006 20:52:02 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Alin-Adrian Anton In-Reply-To: <4456A5B3.2010809@spintech.ro> Message-ID: References: <4456A5B3.2010809@spintech.ro> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-hackers@freebsd.org Subject: Re: which running thread gests the external signal X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 00:52:04 -0000 On Tue, 2 May 2006, Alin-Adrian Anton wrote: > Hi Hackers, > > I'm working on a threaded daemon and I'm trying to make it sysadmin > friendly. For this, I'm working with external signals. > > I noticed different behaviour between BSD and Linux for this. When I > send an external SIGHUP (rehashing the config file) on BSD the thread > receiving the signal seems to be "random". POSIX states any thread that is in sigwait() (with the specified signal in the wait mask), or has the signal unmasked (in the threads signal mask) can receive the signal. If you want a certain thread to receive a process-wide signal, then the only sure way (POSIX) to do that is to block the signal in all the threads with the exception of the thread that is to receive the signal. > On Linux, if I remeber well, all > the threads get the signal, sooner or later.. (the signal handler gets > executed as many times as the number of running threads) Then Linux is wrong. I don't think that is the case any longer, but may have been with there older LinuxThreads model. > The tests I've done were done some time ago, this is why I must > appologise if I get the chance to mix the memories :|. > > So just in case anyone already knows (on BSD): which thread gets > stopped and moves execution to the signal handler function, when the signal > is sent by kill(1) to the pid of the daemon, which is the same for all the > threads? (sorry if dizzy speaking) See above. > And also, is there a way for delegating one special thread to handle > all the external signals? (on BSD) See above. > Thanks for the time guys. I would recommend you also visit http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html -- DE From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 05:31: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 CF13616A400; Tue, 2 May 2006 05:31:48 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5266A43D5F; Tue, 2 May 2006 05:31:41 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (aris.bedc.ondsl.gr [62.103.39.226]) (authenticated bits=128) by igloo.linux.gr (8.13.6/8.13.6/Debian-1) with ESMTP id k425VRPD008189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 2 May 2006 08:31:29 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.6/8.13.6) with ESMTP id k425VWZ9062515; Tue, 2 May 2006 08:31:32 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.6/8.13.6/Submit) id k425VVsi062514; Tue, 2 May 2006 08:31:31 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Tue, 2 May 2006 08:31:31 +0300 From: Giorgos Keramidas To: John Baldwin Message-ID: <20060502053131.GC62424@gothmog.pc> References: <445581DE.50901@centtech.com> <20060501130354.GA17701@toler.leo.org> <20060501130704.GA57024@gothmog.pc> <200605011402.10403.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200605011402.10403.jhb@freebsd.org> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.398, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.80, BAYES_00 -2.60, DNS_FROM_RFC_ABUSE 0.20) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org, Alex Zbyslaw Subject: Re: Boot manager beep (revisited) 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, 02 May 2006 05:31:48 -0000 On 2006-05-01 14:02, John Baldwin wrote: >On Monday 01 May 2006 09:07, Giorgos Keramidas wrote: >>On 2006-05-01 15:03, Daniel Lang wrote: >>> Alex Zbyslaw wrote on Mon, May 01, 2006 at 10:31:34AM +0100: >>> [..] >>> > >off by setting WITHOUT_BOOTEASY_BEEP in `/etc/src.conf'. >>> [..] >>> > WITH_BOOTEASY_BEEP so that it's off by default unless you turn it on >>> >>> Regardless what you decide, if such an option is created, please >>> call it WITH/WITHOUT_BOOTZERO_BEEP or WITH/WITHOUT_BOOT0_BEEP. >>> >>> The current FreeBSD bootmanager is called 'boot0'. It has replaced >>> booteasy (which was indeed used in the past) centuries ago. >> >> I'll do, thanks for the careful review of the diff :) > > How about the patch below. It restores the behavior of the beep > only happening for invalid input by axeing the BSD/OS partition > type from the lookup table. Much better, since this is the behavior we initially had, as you explained. Thanks :) From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 10:23: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 BA40516A400 for ; Tue, 2 May 2006 10:23:46 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail28.syd.optusnet.com.au (mail28.syd.optusnet.com.au [211.29.133.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD63843D60 for ; Tue, 2 May 2006 10:23:43 +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 mail28.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k42ANeMn004306 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 2 May 2006 20:23:40 +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 k42ANdoL001383; Tue, 2 May 2006 20:23:39 +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 k42ANdJJ001382; Tue, 2 May 2006 20:23:39 +1000 (EST) (envelope-from peter) Date: Tue, 2 May 2006 20:23:39 +1000 From: Peter Jeremy To: Allen Message-ID: <20060502102339.GB693@turion.vk2pj.dyndns.org> References: <18e02bd30604301409g2691e0cbvce0bbb8e5c5e56b2@mail.gmail.com> <17494.21387.484871.980369@bhuda.mired.org> <20060501184309.GB19811@freebie.xs4all.nl> <200605011801.01529.slackwarewolf@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200605011801.01529.slackwarewolf@comcast.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: Zero Copy, FreeBSD and Linus Torvalds opinion 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, 02 May 2006 10:23:46 -0000 On Mon, 2006-May-01 18:01:01 -0400, Allen wrote: >Man I would LOVE to find a good sun box. Nothing huge, just a box I can use to >toy with Solaris and oldschool stuff like early SunOS. This won't be one box. Sun hardware and software has undergone a lot of churn over the years and you will need to find a box to suit the SunOS or Solaris version that you want to run. > Just want at least one UNIX box in the house. *BSD is Unix in all but branding. Or you can run Solaris 10 on a PC. >> Well.. Sun at some point took 4.1.3 and 4.1.4 into the Solaris naming >> scheme. Just confusing to a lot of people. > >Software naming has always been a pain ;) Especially when the marketing people get involved... -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 11:36: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 E5FF516A402; Tue, 2 May 2006 11:36:25 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F8A943D53; Tue, 2 May 2006 11:36:24 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.140] (helo=anti-virus02-07) by smtp-out3.blueyonder.co.uk with smtp (Exim 4.52) id 1FatB1-0003Sa-UK; Tue, 02 May 2006 12:36:23 +0100 Received: from [80.192.58.117] (helo=[192.168.0.2]) by asmtp-out3.blueyonder.co.uk with esmtp (Exim 4.52) id 1FatB1-0007lb-5W; Tue, 02 May 2006 12:36:23 +0100 Message-ID: <44574436.4000105@dial.pipex.com> Date: Tue, 02 May 2006 12:36:22 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin References: <445581DE.50901@centtech.com> <20060501130354.GA17701@toler.leo.org> <20060501130704.GA57024@gothmog.pc> <200605011402.10403.jhb@freebsd.org> <20060502053131.GC62424@gothmog.pc> In-Reply-To: <20060502053131.GC62424@gothmog.pc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Boot manager beep (revisited) 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, 02 May 2006 11:36:26 -0000 Giorgos Keramidas wrote: >On 2006-05-01 14:02, John Baldwin wrote: > > >>How about the patch below. It restores the behavior of the beep >> >>only happening for invalid input by axeing the BSD/OS partition >>type from the lookup table. >> >> > >Much better, since this is the behavior we initially had, as you >explained. > >Thanks :) > > > Seconded! Thanks, --Alex From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 06:32: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 016D216A407 for ; Tue, 2 May 2006 06:32:25 +0000 (UTC) (envelope-from stijn@win.tue.nl) Received: from mailhost.tue.nl (mailhost.tue.nl [131.155.2.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F2C043D48 for ; Tue, 2 May 2006 06:32:24 +0000 (GMT) (envelope-from stijn@win.tue.nl) Received: from localhost (localhost [127.0.0.1]) by mailhost.tue.nl (Postfix) with ESMTP id 01AF75C0C0; Tue, 2 May 2006 08:32:23 +0200 (CEST) Received: from mailhost.tue.nl ([131.155.2.19]) by localhost (pastinakel.tue.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19915-07; Tue, 2 May 2006 08:32:22 +0200 (CEST) Received: from umta.win.tue.nl (umta.win.tue.nl [131.155.71.100]) by mailhost.tue.nl (Postfix) with ESMTP id B12475C092; Tue, 2 May 2006 08:32:22 +0200 (CEST) Received: from pcwin691.win.tue.nl (dyn223 [131.155.70.29]) by umta.win.tue.nl (Postfix) with ESMTP id ABB2F31401C; Tue, 2 May 2006 08:32:22 +0200 (CEST) Received: by pcwin691.win.tue.nl (Postfix, from userid 1000) id 969253C411; Tue, 2 May 2006 08:31:01 +0200 (CEST) Date: Tue, 2 May 2006 08:31:01 +0200 From: Stijn Hoop To: "Rick C. Petty" Message-ID: <20060502063101.GA32191@localhost.localdomain> References: <20060501202711.GA476@megan.kiwi-computer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060501202711.GA476@megan.kiwi-computer.com> X-Bright-Idea: Let's abolish HTML mail! User-Agent: Mutt/1.5.11+cvs20060126 X-Virus-Scanned: amavisd-new at tue.nl X-Mailman-Approved-At: Tue, 02 May 2006 11:43:59 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: gvinum start volume returns EBUSY 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, 02 May 2006 06:32:26 -0000 On Mon, May 01, 2006 at 03:27:11PM -0500, Rick C. Petty wrote: > When rebuilding a degraded plex with "gvinum start volume" on a mounted > filesystem, gvinum reports "errno: 16" (EBUSY). In the CVS: > > src/sys/geom/vinum/geom_vinum_init.c, lines 363-364 (of MAIN, added > 2005-Oct-09, rev 1.10.2.1) has the check: > > if (gv_is_open(p->geom)) > return (EBUSY); > > Why is this the case? The log for that change suggests this is to prevent > sync operations from starting when they are already in progress, but that > really refers to lines 366-367: > > if (p->flags & GV_PLEX_SYNCING) > return (EINPROGRESS); > > It seems to me that lines 363-364 should be deleted. If you have a > degraded volume but need to keep it mounted (such as /usr or /home, etc.), > I can't see any reason why you should be forced to unmount the volume > before rebuilding (if the volume is RAID5). Maybe this restriction is > useful for non-RAID5 configurations, but gv_rebuild_plex is only called > in the context of GV_PLEX_RAID5 on degraded plexes. > > Maybe I'm misunderstanding something. Feel free to enlighten me! :-) While regular vinum allowed rebuilding plexes that were mounted, I have seen resulting filesystem corruption afterwards. Unfortunately I don't know whether Lukas has implemented & tested rebuilding online plexes for gvinum yet. --Stijn From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 12: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 2206116A40D for ; Tue, 2 May 2006 12:34:55 +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 89EB543D45 for ; Tue, 2 May 2006 12:34:54 +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 k42CYleK027111; Tue, 2 May 2006 08:34:48 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Alex Zbyslaw Date: Tue, 2 May 2006 08:09:52 -0400 User-Agent: KMail/1.8.3 References: <445581DE.50901@centtech.com> <20060502053131.GC62424@gothmog.pc> <44574436.4000105@dial.pipex.com> In-Reply-To: <44574436.4000105@dial.pipex.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200605020809.52826.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1434/Mon May 1 15:51:00 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,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: Boot manager beep (revisited) 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, 02 May 2006 12:34:55 -0000 On Tuesday 02 May 2006 07:36 am, Alex Zbyslaw wrote: > Giorgos Keramidas wrote: > >On 2006-05-01 14:02, John Baldwin wrote: > >>How about the patch below. It restores the behavior of the beep > >> > >>only happening for invalid input by axeing the BSD/OS partition > >>type from the lookup table. > > > >Much better, since this is the behavior we initially had, as you > >explained. > > > >Thanks :) > > Seconded! Thanks, Does it work? :-) =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 Tue May 2 13: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 054A016A402 for ; Tue, 2 May 2006 13:39:49 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49E9043D46 for ; Tue, 2 May 2006 13:39:47 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 481042083; Tue, 2 May 2006 15:39:39 +0200 (CEST) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -2.4/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id C38402082; Tue, 2 May 2006 15:39:38 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id 9C849B818; Tue, 2 May 2006 15:39:38 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Alex Zbyslaw References: <445581DE.50901@centtech.com> <20060501052755.GA88897@gothmog.pc> <4455D576.2020000@dial.pipex.com> <86iroqvwu2.fsf@xps.des.no> <4455FFC7.7000707@dial.pipex.com> Date: Tue, 02 May 2006 15:39:38 +0200 In-Reply-To: <4455FFC7.7000707@dial.pipex.com> (Alex Zbyslaw's message of "Mon, 01 May 2006 13:32:07 +0100") Message-ID: <86slns4kbp.fsf@dwp.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Boot manager beep (revisited) 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, 02 May 2006 13:39:49 -0000 Alex Zbyslaw writes: > Since I'm on 5.4 I guess I just haven't got your changes yet. > Thanks for doing it, though. Be nice not to have to remember to > patch boot.S every time I rebuild. You don't have to, since installworld does not touch the MBR. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 15:31:37 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 3C70116A400 for ; Tue, 2 May 2006 15:31:37 +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 C1B0943D45 for ; Tue, 2 May 2006 15:31:36 +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 k42FVYrd019554; Tue, 2 May 2006 10:31:34 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <44577B56.70704@centtech.com> Date: Tue, 02 May 2006 10:31:34 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Coleman Kane References: <20060424131508.GB23163@pint.candc.home> <444CD48A.4060501@centtech.com> <444CE475.30104@centtech.com> <20060430231621.GA551@pint.candc.home> <44557F34.3020906@centtech.com> <20060501190645.GB4315@odin.ac.hmc.edu> <44565DD2.1020604@centtech.com> <20060501191447.GD4315@odin.ac.hmc.edu> <44565E74.3060801@centtech.com> <20060501192920.GE4315@odin.ac.hmc.edu> <20060501212801.GA2254@pint.candc.home> In-Reply-To: <20060501212801.GA2254@pint.candc.home> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1434/Mon May 1 14:51:00 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: 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, 02 May 2006 15:31:37 -0000 Coleman Kane wrote: > On Mon, May 01, 2006 at 12:29:20PM -0700, Brooks Davis wrote: >> On Mon, May 01, 2006 at 02:16:04PM -0500, Eric Anderson wrote: >>> Brooks Davis wrote: >>>> On Mon, May 01, 2006 at 02:13:22PM -0500, Eric Anderson wrote: >>>>> Brooks Davis wrote: >>>>>> On Sun, Apr 30, 2006 at 10:23:32PM -0500, Eric Anderson wrote: >>>>>>> Coleman Kane wrote: >>>>>>>> On Mon, Apr 24, 2006 at 09:45:09AM -0500, Eric Anderson wrote: >>>>>>>>> Eric Anderson wrote: >>>>>>>>> >>>>>>>>> Actually, some other things got changed somewhere in the history, >>>>>>>>> that broke some things and assumptions I was making. This patch has >>>>>>>>> them fixed, and I've tested it with all the different options: >>>>>>>>> >>>>>>>>> http://www.googlebit.com/freebsd/patches/rc_fancy.patch-9 >>>>>>>>> >>>>>>>>> It's missing the defaults/rc.conf diffs, but you should already know >>>>>>>>> those. >>>>>>>>> >>>>>>>>> >>>>>>>>> Eric >>>>>>>>> >>>>>>>> I have a new patch (to 7-CURRENT) of the "fancy_rc" updates. >>>>>>>> >>>>>>>> This allows the use of: >>>>>>>> rc_fancy="YES" ---> Turns on fancy reporting (w/o color) >>>>>>>> rc_fancy_color="YES" ---> Turns on fancy reporting (w/ color), needs >>>>>>>> rc_fancy="YES" >>>>>>>> rc_fancy_colour="YES" ---> Same as above for you on the other side of >>>>>>>> the pond. >>>>>>>> rc_fancy_verbose="YES" --> Turn on more verbose activity messages. >>>>>>>> This will cause what appear to be "false >>>>>>>> positives", where an unused service is >>>>>>>> "OK" instead of "SKIP". >>>>>>>> >>>>>>>> You can also customize the colors, the widths of the message >>>>>>>> brackets (e.g. [ OK ] vs. [ OK ]), the screen width, and >>>>>>>> the contents of the message (OK versus GOOD versus BUENO). >>>>>>>> >>>>>>>> Also, we have the following message combinations: >>>>>>>> OK ---> Universal good message >>>>>>>> SKIP,SKIPPED ---> Two methods for conveying the same idea? >>>>>>>> ERROR,FAILED ---> Ditto above, for failure cases >>>>>>>> >>>>>>>> Should we just have 3 different messages, rather than 5 messages >>>>>>>> in 3 categories? >>>>>>> Yes, that's something that started with my first patch, and never got >>>>>>> ironed out. I think it should be: >>>>>>> OK >>>>>>> SKIPPED >>>>>>> FAILED >>>>>>> and possibly also: >>>>>>> ERROR >>>>>>> >>>>>>> The difference between FAILED and ERROR would be that FAILED means the >>>>>>> service did not start at all, and ERROR means it started but had some >>>>>>> kind of error response. >>>>>> FAILED vs ERROR seems confusing. I'd be inclined toward WARNING vs >>>>>> FAILED or ERROR. >>>>> True, however I still see a difference between FAILED and WARNING. For >>>>> instance, as an example: a FAILED RAID is different than a RAID with a >>>>> WARNING. >>>> For that level of detail, the ability to provide additional output seems >>>> like the appropriate solution. >>> Yes, true, but you'd still want to show something (I would think) in the >>> [ ]'s to keep it consistent. >> My feeling is that anything short of complete success should report >> WARNING and a message unless it actually totally failed in which case >> FAILED or ERROR (I slightly perfer ERROR) should be used. >> >> -- Brooks > > What situations are we determining get flagged as ERROR versus FAILED? > Is FAILED considered to be 'I was able to run the command, but it > returned an error code', versus ERROR being 'I could not even run the > command!' like bad path, file not found, etc... > > This point still kind of confuses me (and needs to be well defined). I > am an advocate of having three distinct messages: OK, SKIPPED, ERROR. > And not even bothering with the different types of ERROR/FAILED other > than having extra reporting output. I'm ok with just OK, SKIPPED, ERROR.. If there's ever a need for more, it's easy to add it. 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 May 2 17:59: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 DC69616A4EA; Tue, 2 May 2006 17:59:06 +0000 (UTC) (envelope-from aanton@spintech.ro) Received: from smtpx.spintech.ro (smtpx.spintech.ro [81.180.92.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE78C43D5D; Tue, 2 May 2006 17:58:59 +0000 (GMT) (envelope-from aanton@spintech.ro) Received: from [10.0.0.2] (beastie [10.0.0.2]) by smtpx.spintech.ro (Postfix) with ESMTP id 3A4333A491; Tue, 2 May 2006 18:32:27 +0000 (UTC) Message-ID: <44579DE0.1050207@spintech.ro> Date: Tue, 02 May 2006 20:58:56 +0300 From: Alin-Adrian Anton Organization: Spintech Security Systems User-Agent: Mozilla Thunderbird 1.0 (X11/20041229) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eischen References: <4456A5B3.2010809@spintech.ro> In-Reply-To: X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: which running thread gests the external signal X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: aanton@spintech.ro List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 17:59:07 -0000 Daniel Eischen wrote: > POSIX states any thread that is in sigwait() (with the specified > signal in the wait mask), or has the signal unmasked (in the threads > signal mask) can receive the signal. If you want a certain thread > to receive a process-wide signal, then the only sure way (POSIX) to > do that is to block the signal in all the threads with the exception > of the thread that is to receive the signal. > OK, I was able to delegate a single thread for handling all the signals, by using sigprocmask to block all signals at the beggining, then using pthread_sigmask to unblock the needed signals inside the delegated thread. This seemed to be the cleanest way of doing it.. However, this is not fully clean: all the other threads should *ignore* the signals, not *block* them. Blocking a signal means the signal will be queued and the queue will eventually fill, and so on. In my scenario I get the result without running into problems (because each thread seems to have it's own signal queue), however it's not... "clean". The other threads need to simply 'drop' the signals, not cause them to be queued forever (consider an uptime of 1 year?). I don't know the impact, however I want it to be clean.. So ... would it be a way to ignore the signals from all the other threads except the delegated one for handling them? (I'm sorry, I don't notice it, even if it's obvious) Thanks for the advices and the tips, it's been really usefull. PS: Without using sigprocmask and pthread_sigmask, one random thread is stopped in order for the signal handler to execute. Doesn't this mean that the other threads are not 'seeing' the signal? In order to force a thread to receive/see the signal, I need to block the signal inside all the other threads (either with sigprocmask in main, or with pthread_sigmask). On Linux, the signal gets delivered to all the running threads, unless specifically blocked :). And I think that conformes to your mentioning of POSIX standards. Sorry if I'm wrong. [..] > > I would recommend you also visit > > > http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html > I've read it, thanks. I added it to my bookmarks. Yours Sincerely, -- Alin-Adrian Anton GPG keyID 0x183087BA (B129 E8F4 7B34 15A9 0785 2F7C 5823 ABA0 1830 87BA) gpg --keyserver pgp.mit.edu --recv-keys 0x183087BA "It is dangerous to be right when the government is wrong." - Voltaire From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 18:09: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 692C616A730 for ; Tue, 2 May 2006 18:09:41 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B9B443D81 for ; Tue, 2 May 2006 18:09:22 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (storm.stura.uni-rostock.de [139.30.252.72]) by hydra.bec.de (Postfix) with ESMTP id B45A935707 for ; Tue, 2 May 2006 20:09:20 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1000) id C8E326CC85; Tue, 2 May 2006 20:09:01 +0200 (CEST) Date: Tue, 2 May 2006 20:09:01 +0200 From: joerg@britannica.bec.de To: freebsd-hackers@freebsd.org Message-ID: <20060502180901.GA16152@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <4456A5B3.2010809@spintech.ro> <44579DE0.1050207@spintech.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44579DE0.1050207@spintech.ro> User-Agent: Mutt/1.5.11 Subject: Re: which running thread gests the external signal 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, 02 May 2006 18:09:41 -0000 On Tue, May 02, 2006 at 08:58:56PM +0300, Alin-Adrian Anton wrote: > However, this is not fully clean: all the other threads should *ignore* > the signals, not *block* them. Threads don't have signal queues. POSIX specifies that a process has a *global* list of pending signals and a *thread-local* list of currently blocked signals. A correct implementation could iterate over the list of all threads of a process, whenever either a new signal arrives or a thread mask is changed. This is not the behaviour Linux implemented for ages. Joerg From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 18:15:17 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 CDB2D16A4A5 for ; Tue, 2 May 2006 18:15:17 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B929543DDC for ; Tue, 2 May 2006 18:14:03 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k42IE2Ov029318; Tue, 2 May 2006 14:14:02 -0400 (EDT) Date: Tue, 2 May 2006 14:14:02 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Alin-Adrian Anton In-Reply-To: <44579DE0.1050207@spintech.ro> Message-ID: References: <4456A5B3.2010809@spintech.ro> <44579DE0.1050207@spintech.ro> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-hackers@freebsd.org Subject: Re: which running thread gests the external signal X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2006 18:15:18 -0000 On Tue, 2 May 2006, Alin-Adrian Anton wrote: > Daniel Eischen wrote: >> POSIX states any thread that is in sigwait() (with the specified >> signal in the wait mask), or has the signal unmasked (in the threads >> signal mask) can receive the signal. If you want a certain thread >> to receive a process-wide signal, then the only sure way (POSIX) to >> do that is to block the signal in all the threads with the exception >> of the thread that is to receive the signal. >> > > OK, I was able to delegate a single thread for handling all the signals, by > using sigprocmask to block all signals at the beggining, then using > pthread_sigmask to unblock the needed signals inside the delegated thread. > This seemed to be the cleanest way of doing it.. > > However, this is not fully clean: all the other threads should *ignore* the > signals, not *block* them. Blocking a signal means the signal will be queued > and the queue will eventually fill, and so on. In my scenario I get the > result without running into problems (because each thread seems to have it's > own signal queue), however it's not... "clean". The other threads need to > simply 'drop' the signals, not cause them to be queued forever (consider an > uptime of 1 year?). I don't know the impact, however I want it to be clean.. You are entirely confused. You should go back to the POSIX standard and get Dave Butenhof's Programming with POSIX Threads book. One and only one thread gets _a_ signal. Blocking a signal in a thread does not mean it is queued on that thread, unless the signal is sent specifically to that thread (using pthread_kill(tid, sig), not kill(pid, sig)). Read the part of the POSIX standard that talks about signals pending on the process. Signals pending on the process, stay pending (or queued if they are queued signals) until a thread either unblocks the signal, calls sigwait() selecting that signal, or ignores the signal (using sigaction()). A signal handler runs in the context of the thread that is receiving (handling) the signal. > So ... would it be a way to ignore the signals from all the other threads > except the delegated one for handling them? (I'm sorry, I don't notice it, > even if it's obvious) > > Thanks for the advices and the tips, it's been really usefull. > > PS: Without using sigprocmask and pthread_sigmask, one random thread is > stopped in order for the signal handler to execute. Doesn't this mean that > the other threads are not 'seeing' the signal? In order to force a thread to > receive/see the signal, I need to block the signal inside all the other > threads (either with sigprocmask in main, or with pthread_sigmask). On Linux, > the signal gets delivered to all the running threads, unless specifically > blocked :). And I think that conformes to your mentioning of POSIX standards. No, if Linux delivers one signal to multiple threads, then it is entirely wrong and not compliant with POSIX behavior. I think Linux' NPT threads (or whatever they are called) have correct behavior. -- DE From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 18:19: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 9881316A53A for ; Tue, 2 May 2006 18:19:26 +0000 (UTC) (envelope-from bharmaji@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45E5643D6A for ; Tue, 2 May 2006 18:19:22 +0000 (GMT) (envelope-from bharmaji@gmail.com) Received: by nz-out-0102.google.com with SMTP id 12so1618036nzp for ; Tue, 02 May 2006 11:19:21 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=HLJ/QO2SCnn5Z+iCpyJlekHP5bFt1yrVwGLdpQFzAuYZ52HRvLsGl5t8RY2xM7RyBAebpf74j5G9qy7wiGteKRken/wSlMLNdQmBGQxr0sDci0/BuzpSmn1NhuXaLHp0w6XizqRWW3uHr2JByYZYXC7kIFtG7G20MRZorwX2jYE= Received: by 10.64.53.8 with SMTP id b8mr635663qba; Tue, 02 May 2006 11:19:21 -0700 (PDT) Received: by 10.65.132.5 with HTTP; Tue, 2 May 2006 11:19:21 -0700 (PDT) Message-ID: <67beabb0605021119y5770cd3al55e2c875c84589b@mail.gmail.com> Date: Tue, 2 May 2006 11:19:21 -0700 From: "Bharma Ji" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: memory allocation / deallocation within the kernel 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, 02 May 2006 18:19:29 -0000 I am trying to understand the impact of memory allocation / deallocation within the kernel. As I understand a) Kernel memory is not pageable ie the one you get from using kernel malloc(there may be exceptions) b) Does this imply that if I have 1 GB of RAM - then I cannot reserve more than 1 GB of kernel virtual address space? The reason is that if at any point of time, the kernel has to allocate all of its virtual address space i.e. if it needs to allocate more than 1 GB of address space, there won't b= e any physical RAM memory to allocate from and thus this scenario is not allowed as a configuration? c) Another scenario is that assume that the kernel has 512 MB of virtual address space with 1 GB of RAM. Now assume that the entire 1 GB of RAM is used up by the kernel and other userland process that are running - with th= e kernel taking 256 MB and the rest allocated to the processes. Now if the kernel needs to allocate more memory, will some of the processes be swapped out to make way for the kernel(since the kernel can take upto 512 MB) Thanks for any answers. Any URL / literature that explains this will also b= e appreciated. From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 19:25:02 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 B238D16A70D for ; Tue, 2 May 2006 19:25:02 +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 2391043D6D for ; Tue, 2 May 2006 19:25:02 +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 42FA246B86; Tue, 2 May 2006 15:25:00 -0400 (EDT) Date: Tue, 2 May 2006 20:25:00 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Bharma Ji In-Reply-To: <67beabb0605021119y5770cd3al55e2c875c84589b@mail.gmail.com> Message-ID: <20060502201933.F58458@fledge.watson.org> References: <67beabb0605021119y5770cd3al55e2c875c84589b@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: memory allocation / deallocation within the kernel 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, 02 May 2006 19:25:02 -0000 On Tue, 2 May 2006, Bharma Ji wrote: > I am trying to understand the impact of memory allocation / deallocation > within the kernel. As I understand I can't answer all your questions, but can point at a few examples in current kernel code. > a) Kernel memory is not pageable ie the one you get from using kernel > malloc(there may be exceptions) In general, we guarantee that kernel memory is accessible fault-free so that locks can be held over kernel memory use. In particular, both kernel malloc and the kernel slab allocator allocate both address space and locked memory that is non-pageable. Two canonical exceptions: - Kernel thread stacks, which may be swapped out. See PS_INMEM. - Pipe buffers, which use pageable kernel memory. > b) Does this imply that if I have 1 GB of RAM - then I cannot reserve more > than 1 GB of kernel virtual address space? The reason is that if at any > point of time, the kernel has to allocate all of its virtual address space > i.e. if it needs to allocate more than 1 GB of address space, there won't be > any physical RAM memory to allocate from and thus this scenario is not > allowed as a configuration? Address space and memory are separable. The kernel memory allocators ask for memory from the VM system as other consumers do, so the kernel address space can be much larger than available memory. On the other hand, you as long as you're dealing with kernel memory allocated using standard allocators, such as malloc and UMA, you are allocating both address space and memory, so you can't use more memory than address space. Some components, such as md disk devices, allocate using swap-backed memory that is pageable, so interfaces exist to use pageable memory in kernel, and are used. You do have to be pretty careful though, as if you fault in an address in kernel, you may have to wait for it to arrive, which involves long sleeps. Holding kernel locks, especially mutexes, across faults is not a good thing, and our invariants checkers will generate errors when that happens. > c) Another scenario is that assume that the kernel has 512 MB of virtual > address space with 1 GB of RAM. Now assume that the entire 1 GB of RAM is > used up by the kernel and other userland process that are running - with the > kernel taking 256 MB and the rest allocated to the processes. Now if the > kernel needs to allocate more memory, will some of the processes be swapped > out to make way for the kernel(since the kernel can take upto 512 MB) If we're talking about non-pageable kernel memory, then user space will be operating in a memory-starved environment, and likely thrash. If we're talking about pageable kernel memory, then the kernel threads and user threads will compete for physical memory. Robert N M Watson From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 20:46:12 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 782F316A431; Tue, 2 May 2006 20:46:12 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09F3443D46; Tue, 2 May 2006 20:46:11 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k42Kk9Zr041724; Tue, 2 May 2006 14:46:10 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4457C50B.40706@samsco.org> Date: Tue, 02 May 2006 14:46:03 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org, hackers@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: re@freebsd.org Subject: FreeBSD 6.1-RC2 available 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, 02 May 2006 20:46:12 -0000 All, I'm foregoing the formal pretty announcement for 6.1-RC2 because the message needs to get out and I don't have an hour to spend on making it look nice. FreeBSD 6.1-RC2 is available for download. This is the last RC before the release. Please test it to make sure that there have been no regressions since the last RC, and to make sure that it there are no new problems with installation. Other than a few cosmetic tweaks, there will be no more changes before 6.1. The list of known issues: - Using UFS snapshots and quotas at the same time can cause system lockups. There is no work-around available at this time, so please avoid this configuration. This will be fixed in a future release. - Under rare and heavily loaded circumstances, there is a possibility to leak pty's. This can result in not being able to long into the system. The cause of this is not well understood, and it appears to be very difficult to trigger it. - DEVFS is known to have several problems with multiple processes doing directory listings at the same time, as well as with unmounting DEVFS directories at the same time. There is no known work-around for this at this time. This will be fixed in a future release. - A number of improvements and fixes for various drivers have come in at the last minute that still require much more testing and validation. This includes the 'if_nve' and 'if_bge' drivers in particular. These updates will be included in future releases. MD5 (6.1-RC1-amd64-bootonly.iso) = 93abe294e7678e00b7391f47a01074fe MD5 (6.1-RC1-amd64-disc1.iso) = c1b718b6752f0e48edb8b822ee9b0dc8 MD5 (6.1-RC1-amd64-disc2.iso) = 4a67ae8ed7a7852e08442205d6a5cd7c MD5 (6.1-RC1-i386-bootonly.iso) = b56aac9ca1a868daaf5673cd21bf78f5 MD5 (6.1-RC1-i386-disc1.iso) = 12521c3f9d40f637e4cdb40ea398d072 MD5 (6.1-RC1-i386-disc2.iso) = 53615f19889fe85c41e2bcea0b2be525 MD5 (6.1-RC2-ia64-bootonly.iso) = 481e6f1899c0ba632272e7853b8ef59e MD5 (6.1-RC2-ia64-disc1.iso) = f4601bb9089af1bcde5b751f5762f35a MD5 (6.1-RC2-ia64-disc2.iso) = b44d5a0538b784cbb5de0a8ec23e4256 MD5 (6.1-RC2-ia64-livefs.iso) = 0fe8b66a80edaa50ac353d5471930035 MD5 (6.1-RC2-pc98-disc1.iso) = 773a64a475596d586d0a1573d88310cc SHA256 (6.1-RC1-amd64-bootonly.iso) = 88e072b4898692813517aa254a33f1e7469de0e590c36bfb3e92cb120ac0ad16 SHA256 (6.1-RC1-amd64-disc1.iso) = 017e69c5461fe2c865a395830dde88c8a55e7ec83d9a195b3b619346b44f9cc6 SHA256 (6.1-RC1-amd64-disc2.iso) = 81624f3b8dfa67ceab1dc6ec0a94c4485ad85955321c39d13c9ab4a678f776ef SHA256 (6.1-RC1-i386-bootonly.iso) = ec1a3fbf53186b5bc44dbfcdc77872c847f3c55532bb62f2afb4133328e7994f SHA256 (6.1-RC1-i386-disc1.iso) = e0b83f2cbd27db20f330036d0a25b8366b9e45df4b9c09354f76e584a9eb3b83 SHA256 (6.1-RC1-i386-disc2.iso) = de1fe5009229efd44b25bb18c4e68b03027259171cd9e017fe5bffadaa3402bb SHA256 (6.1-RC2-ia64-bootonly.iso) = c044989257754fa17daa352f76c3e011dfc04b3b242c2153c7a1ec47a773d4d1 SHA256 (6.1-RC2-ia64-disc1.iso) = 60bec7c25b8f645a9d20d3240397c7a92f42d24ff5d01b4604ece5f9ee499ccc SHA256 (6.1-RC2-ia64-disc2.iso) = 854048d4ba4dcf00657501d36a5fb15a94ed4c20e646031960ebc3315c3a513e SHA256 (6.1-RC2-ia64-livefs.iso) = fb3fadb00c9ddb6233172a34a7d47ab80171b54410835954c20f50849359ee73 SHA256 (6.1-RC2-pc98-disc1.iso) = f2b5f17a3355465727613e33807964a0cf92d9c02868cd2c25440995b2c6ebfd From owner-freebsd-hackers@FreeBSD.ORG Tue May 2 22:48: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 324C416A401; Tue, 2 May 2006 22:48:07 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out3.blueyonder.co.uk (smtp-out3.blueyonder.co.uk [195.188.213.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AA3543D46; Tue, 2 May 2006 22:48:05 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.139] (helo=anti-virus01-10) by smtp-out3.blueyonder.co.uk with smtp (Exim 4.52) id 1Fb3f2-0008PD-ON; Tue, 02 May 2006 23:48:04 +0100 Received: from [80.192.58.117] (helo=[192.168.0.2]) by asmtp-out4.blueyonder.co.uk with esmtp (Exim 4.52) id 1Fb3f2-0004sy-4M; Tue, 02 May 2006 23:48:04 +0100 Message-ID: <4457E1A1.1070103@dial.pipex.com> Date: Tue, 02 May 2006 23:48:01 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin References: <445581DE.50901@centtech.com> <20060502053131.GC62424@gothmog.pc> <44574436.4000105@dial.pipex.com> <200605020809.52826.jhb@freebsd.org> In-Reply-To: <200605020809.52826.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Boot manager beep (revisited) 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, 02 May 2006 22:48:07 -0000 John Baldwin wrote: >On Tuesday 02 May 2006 07:36 am, Alex Zbyslaw wrote: > > >>Giorgos Keramidas wrote: >> >> >>>On 2006-05-01 14:02, John Baldwin wrote: >>> >>> >>>>How about the patch below. It restores the behavior of the beep >>>> >>>>only happening for invalid input by axeing the BSD/OS partition >>>>type from the lookup table. >>>> >>>> >>>Much better, since this is the behavior we initially had, as you >>>explained. >>> >>>Thanks :) >>> >>> >>Seconded! Thanks, >> >> > >Does it work? :-) > > > I downloaded the latest boot0.s from cvs, applied you patch and put it on all three disks in this box. On my tests it worked beautifully. Beeped when I selected a non-existent partition and didn't beep when I selected a legitimate one, or just let it time out to the default. (I tried both FreeBSD and WinXP/NTFS partitions for booting and auto-boot). I can't confirm what boot0sio does as I don't have anything set up with a serial console. You'll probably want some more confirmations, but I'd say this was the bees knees. --Alex From owner-freebsd-hackers@FreeBSD.ORG Wed May 3 00:51:02 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 963CA16A404; Wed, 3 May 2006 00:51:02 +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 3E26A43D45; Wed, 3 May 2006 00:51:01 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k430osNm052891; Tue, 2 May 2006 19:50:56 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4457FE6F.8030309@centtech.com> Date: Tue, 02 May 2006 19:50:55 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Alex Zbyslaw References: <445581DE.50901@centtech.com> <20060502053131.GC62424@gothmog.pc> <44574436.4000105@dial.pipex.com> <200605020809.52826.jhb@freebsd.org> <4457E1A1.1070103@dial.pipex.com> In-Reply-To: <4457E1A1.1070103@dial.pipex.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1436/Tue May 2 12:41:37 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: Boot manager beep (revisited) 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, 03 May 2006 00:51:02 -0000 Alex Zbyslaw wrote: > John Baldwin wrote: > >> On Tuesday 02 May 2006 07:36 am, Alex Zbyslaw wrote: >> >> >>> Giorgos Keramidas wrote: >>> >>>> On 2006-05-01 14:02, John Baldwin wrote: >>>> >>>>> How about the patch below. It restores the behavior of the beep >>>>> >>>>> only happening for invalid input by axeing the BSD/OS partition >>>>> type from the lookup table. >>>>> >>>> Much better, since this is the behavior we initially had, as you >>>> explained. >>>> >>>> Thanks :) >>>> >>> Seconded! Thanks, >>> >> >> Does it work? :-) >> >> >> > I downloaded the latest boot0.s from cvs, applied you patch and put it > on all three disks in this box. > > On my tests it worked beautifully. Beeped when I selected a > non-existent partition and didn't beep when I selected a legitimate one, > or just let it time out to the default. (I tried both FreeBSD and > WinXP/NTFS partitions for booting and auto-boot). I can't confirm what > boot0sio does as I don't have anything set up with a serial console. > > You'll probably want some more confirmations, but I'd say this was the > bees knees. Ditto.. My wife is very happy about the patch too. :) 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 May 3 11:56: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 53C9A16A401; Wed, 3 May 2006 11:56:42 +0000 (UTC) (envelope-from aanton@spintech.ro) Received: from smtpx.spintech.ro (smtpx.spintech.ro [81.180.92.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF8E043D46; Wed, 3 May 2006 11:56:41 +0000 (GMT) (envelope-from aanton@spintech.ro) Received: from [10.0.0.2] (beastie [10.0.0.2]) by smtpx.spintech.ro (Postfix) with ESMTP id 125133A497; Wed, 3 May 2006 12:30:18 +0000 (UTC) Message-ID: <44589A77.7070707@spintech.ro> Date: Wed, 03 May 2006 14:56:39 +0300 From: Alin-Adrian Anton Organization: Spintech Security Systems User-Agent: Mozilla Thunderbird 1.0 (X11/20041229) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eischen References: <4456A5B3.2010809@spintech.ro> <44579DE0.1050207@spintech.ro> In-Reply-To: X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: which running thread gests the external signal X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: aanton@spintech.ro List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 11:56:42 -0000 Daniel Eischen wrote: > You are entirely confused. You should go back to the POSIX standard > and get Dave Butenhof's Programming with POSIX Threads book. > [..] You are right. All is clear now, i re-read the link twice and played with sigprocmask vs. pthread_sigmask. It's clear now, also with the help of: http://www.opengroup.org/onlinepubs/009695399/functions/sigprocmask.html Thank you very much! (all involved) Regards, -- Alin-Adrian Anton GPG keyID 0x183087BA (B129 E8F4 7B34 15A9 0785 2F7C 5823 ABA0 1830 87BA) gpg --keyserver pgp.mit.edu --recv-keys 0x183087BA "It is dangerous to be right when the government is wrong." - Voltaire From owner-freebsd-hackers@FreeBSD.ORG Wed May 3 12:56: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 DC50C16A425 for ; Wed, 3 May 2006 12:56:38 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79AC943D46 for ; Wed, 3 May 2006 12:56:38 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.6/8.13.6/NETPLEX) with ESMTP id k43CubiG026329; Wed, 3 May 2006 08:56:37 -0400 (EDT) Date: Wed, 3 May 2006 08:56:37 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Alin-Adrian Anton In-Reply-To: <44589A77.7070707@spintech.ro> Message-ID: References: <4456A5B3.2010809@spintech.ro> <44579DE0.1050207@spintech.ro> <44589A77.7070707@spintech.ro> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-hackers@freebsd.org Subject: Re: which running thread gests the external signal X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 12:56:41 -0000 On Wed, 3 May 2006, Alin-Adrian Anton wrote: > Daniel Eischen wrote: >> You are entirely confused. You should go back to the POSIX standard >> and get Dave Butenhof's Programming with POSIX Threads book. >> > [..] > > You are right. All is clear now, i re-read the link twice and played with > sigprocmask vs. pthread_sigmask. It's clear now, also with the help of: > > http://www.opengroup.org/onlinepubs/009695399/functions/sigprocmask.html Note that sigprocmask() and pthread_sigprocmask() are equivalent. I don't even think pthread_sigprocmask() is in the standard any longer (it used to be in an older version of the standard). New applications should be using sigprocmask(). -- DE From owner-freebsd-hackers@FreeBSD.ORG Wed May 3 13:49:27 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 6B78E16A401; Wed, 3 May 2006 13:49:27 +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 08F6F43D48; Wed, 3 May 2006 13:49:26 +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 k43DnQJt075166; Wed, 3 May 2006 08:49:26 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4458B4E6.3070001@centtech.com> Date: Wed, 03 May 2006 08:49:26 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: John Baldwin References: <200605031343.k43Dhlox091636@repoman.freebsd.org> In-Reply-To: <200605031343.k43Dhlox091636@repoman.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1437/Wed May 3 01:54:45 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: hackers@freebsd.org Subject: Re: cvs commit: src/sys/boot/i386/boot0 boot0.S 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, 03 May 2006 13:49:27 -0000 John Baldwin wrote: > jhb 2006-05-03 13:43:46 UTC > > FreeBSD src repository > > Modified files: > sys/boot/i386/boot0 boot0.S > Log: > Restore the pre-5.x behavior of only beeping if the user makes a bad > selection and not always beeping on startup. The two bytes for the extra > 'jmp' instruction were obtained by removing recognition of BSD/OS > partitions. > > Requested by: many > Tested by: subset of many > Head nod: imp, keramida > MFC after: 2 weeks > > Revision Changes Path > 1.15 +8 -5 src/sys/boot/i386/boot0/boot0.S Hooray!! Thank you! 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 May 3 19:54: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 07B4616A43B; Wed, 3 May 2006 19:54:04 +0000 (UTC) (envelope-from aanton@spintech.ro) Received: from smtpx.spintech.ro (smtpx.spintech.ro [81.180.92.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16EE543D7C; Wed, 3 May 2006 19:54:02 +0000 (GMT) (envelope-from aanton@spintech.ro) Received: from [10.0.0.2] (beastie [10.0.0.2]) by smtpx.spintech.ro (Postfix) with ESMTP id 7C1123A4AA; Wed, 3 May 2006 20:27:43 +0000 (UTC) Message-ID: <44590A59.7000307@spintech.ro> Date: Wed, 03 May 2006 22:54:01 +0300 From: Alin-Adrian Anton Organization: Spintech Security Systems User-Agent: Mozilla Thunderbird 1.0 (X11/20041229) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eischen References: <4456A5B3.2010809@spintech.ro> <44579DE0.1050207@spintech.ro> <44589A77.7070707@spintech.ro> In-Reply-To: X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: which running thread gests the external signal X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: aanton@spintech.ro List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 19:54:04 -0000 Daniel Eischen wrote: [..] > > Note that sigprocmask() and pthread_sigprocmask() are equivalent. I > don't even think pthread_sigprocmask() is in the standard any longer > (it used to be in an older version of the standard). New applications > should be using sigprocmask(). > Yes I noticed. However, this just happens to be the implementation (probably pthread_sigmask is a wrapper to sigprocmask). This might not be the case on other OS, so for portability I'll stick to the pthread_sigmask in threads, and sigprocmask in single threaded apps. Thanks, -- Alin-Adrian Anton GPG keyID 0x183087BA (B129 E8F4 7B34 15A9 0785 2F7C 5823 ABA0 1830 87BA) gpg --keyserver pgp.mit.edu --recv-keys 0x183087BA "It is dangerous to be right when the government is wrong." - Voltaire From owner-freebsd-hackers@FreeBSD.ORG Thu May 4 05:45: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 331B816A409; Thu, 4 May 2006 05:45:34 +0000 (UTC) (envelope-from vd@datamax.bg) Received: from jengal.datamax.bg (jengal.datamax.bg [82.103.104.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6317243D6B; Thu, 4 May 2006 05:45:26 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from qlovarnika.bg.datamax (qlovarnika.bg.datamax [192.168.10.2]) by jengal.datamax.bg (Postfix) with SMTP id D8362B859; Thu, 4 May 2006 08:45:24 +0300 (EEST) Received: (nullmailer pid 5062 invoked by uid 1002); Thu, 04 May 2006 05:45:24 -0000 Date: Thu, 4 May 2006 08:45:24 +0300 From: Vasil Dimov To: Alin-Adrian Anton Message-ID: <20060504054524.GA5017@qlovarnika.bg.datamax> References: <4456A5B3.2010809@spintech.ro> <44579DE0.1050207@spintech.ro> <44589A77.7070707@spintech.ro> <44590A59.7000307@spintech.ro> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline In-Reply-To: <44590A59.7000307@spintech.ro> X-OS: FreeBSD 6.0-STABLE User-Agent: Mutt/1.5.11 Cc: Daniel Eischen , freebsd-hackers@freebsd.org Subject: Re: which running thread gests the external signal X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vd@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 05:45:34 -0000 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 03, 2006 at 10:54:01PM +0300, Alin-Adrian Anton wrote: > Daniel Eischen wrote: > [..] > > > >Note that sigprocmask() and pthread_sigprocmask() are equivalent. I > >don't even think pthread_sigprocmask() is in the standard any longer > >(it used to be in an older version of the standard). New applications > >should be using sigprocmask(). > > >=20 > Yes I noticed. However, this just happens to be the implementation=20 > (probably pthread_sigmask is a wrapper to sigprocmask). >=20 > This might not be the case on other OS, so for portability I'll stick to= =20 > the pthread_sigmask in threads, and sigprocmask in single threaded apps. >=20 For portability you should stick to the standards. Good luck! --=20 Vasil Dimov gro.DSBeerF@dv Testing can show the presence of bugs, but not their absence. -- Edsger W. Dijkstra --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFEWZT0Fw6SP/bBpCARAgzMAKCb1fHbPdNmPO/asXRzFhUrit1BgwCfeo1H 4qOUbZEBhxdib/X1u9CwK68= =LFZp -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga-- From owner-freebsd-hackers@FreeBSD.ORG Thu May 4 19:41: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 1266616A43B for ; Thu, 4 May 2006 19:41:06 +0000 (UTC) (envelope-from listas@itm.net.br) Received: from venom.itm.net.br (venom.itm.net.br [201.30.187.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F1D743D58 for ; Thu, 4 May 2006 19:41:00 +0000 (GMT) (envelope-from listas@itm.net.br) Received: (qmail 52529 invoked by uid 89); 4 May 2006 19:39:40 -0000 Received: by simscan 1.2.0 ppid: 52524, pid: 52525, t: 0.2585s scanners: attach: 1.2.0 clamav: 0.88/m:38/d:1425 spam: 3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on venom.itm.net.br X-Spam-Level: X-Spam-Status: No, score=-3.9 required=6.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from ironman.fsonline.com.br (HELO ironman) (201.30.187.70) by venom.itm.net.br with SMTP; 4 May 2006 19:39:40 -0000 Message-ID: <00fb01c66fb2$a8e157c0$0501010a@ironman> From: "Cesar" To: Date: Thu, 4 May 2006 16:40:55 -0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Antivirus: avast! (VPS 0618-2, 04/05/2006), Outbound message X-Antivirus-Status: Clean Subject: Fingerprint Authentication 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, 04 May 2006 19:41:06 -0000 Hello, I was wondering if there are any way to do ssh to a freebsd box and authenticate the user via fingerprint, and/or a module to do http autentication via fingerprint on Apache. Thanks From owner-freebsd-hackers@FreeBSD.ORG Thu May 4 20:08: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 E8B5016A402 for ; Thu, 4 May 2006 20:08:39 +0000 (UTC) (envelope-from aanton@spintech.ro) Received: from smtpx.spintech.ro (smtpx.spintech.ro [81.180.92.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 602AE43D46 for ; Thu, 4 May 2006 20:08:39 +0000 (GMT) (envelope-from aanton@spintech.ro) Received: from [10.0.0.2] (beastie [10.0.0.2]) by smtpx.spintech.ro (Postfix) with ESMTP id 08DED3A497; Thu, 4 May 2006 20:42:30 +0000 (UTC) Message-ID: <445A5F48.60303@spintech.ro> Date: Thu, 04 May 2006 23:08:40 +0300 From: Alin-Adrian Anton Organization: Spintech Security Systems User-Agent: Mozilla Thunderbird 1.0 (X11/20041229) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Cesar References: <00fb01c66fb2$a8e157c0$0501010a@ironman> In-Reply-To: <00fb01c66fb2$a8e157c0$0501010a@ironman> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Fingerprint Authentication X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: aanton@spintech.ro List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 20:08:40 -0000 Cesar wrote: > Hello, > > I was wondering if there are any way to do ssh to a freebsd box and > authenticate the user via fingerprint, and/or a module to do http > autentication via fingerprint on Apache. > Hi, I think this link will be very usefull to you (UPEK fingerprint drivers): http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader SSH can do pam authentication. Regards, -- Alin-Adrian Anton GPG keyID 0x183087BA (B129 E8F4 7B34 15A9 0785 2F7C 5823 ABA0 1830 87BA) gpg --keyserver pgp.mit.edu --recv-keys 0x183087BA "It is dangerous to be right when the government is wrong." - Voltaire From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 00:39: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 DC2BD16A401 for ; Fri, 5 May 2006 00:39:53 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E368943D49 for ; Fri, 5 May 2006 00:39:51 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.21]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k450dn8j039115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 May 2006 10:09:49 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org, aanton@spintech.ro Date: Fri, 5 May 2006 10:09:47 +0930 User-Agent: KMail/1.9.1 References: <00fb01c66fb2$a8e157c0$0501010a@ironman> <445A5F48.60303@spintech.ro> In-Reply-To: <445A5F48.60303@spintech.ro> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1185762.ZZ82dtkgi1"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200605051009.49344.doconnor@gsoft.com.au> X-Spam-Score: -1.36 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: Cesar Subject: Re: Fingerprint Authentication 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, 05 May 2006 00:39:54 -0000 --nextPart1185762.ZZ82dtkgi1 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 05 May 2006 05:38, Alin-Adrian Anton wrote: > http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader > > SSH can do pam authentication. Not sure the driver will work in FreeBSD.. There is bioapi in ports though. Oops. looks like ports wins again.. security/bsp_upektfmess This might be a more FreeBSD friendly URL.. http://shapeshifter.se/articles/upek_touchchip_freebsd/ (not that I have any of these devices :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1185762.ZZ82dtkgi1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEWp7V5ZPcIHs/zowRAtwDAKCgL/BPCBNcf//ANrPUWjEStfS10ACeOeX5 RNfMiRgrCHOkHTRcSLGpRoc= =/6/J -----END PGP SIGNATURE----- --nextPart1185762.ZZ82dtkgi1-- From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 00:59: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 AEAE816A402 for ; Fri, 5 May 2006 00:59:35 +0000 (UTC) (envelope-from andrew.chace@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF43643D64 for ; Fri, 5 May 2006 00:59:32 +0000 (GMT) (envelope-from andrew.chace@gmail.com) Received: by nz-out-0102.google.com with SMTP id l1so563144nzf for ; Thu, 04 May 2006 17:59:31 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=FxLiqSZw7LB15YOAopQeN9Q6WjRaufNg+IXrcduRAvezwV4uEicoyl/AeToYWzJjQEx1YpCpvQrHF+5tAZlXNMz8kJfzIfRXOnTZ4iHDvBCOPub7dxMtrtWvKeWGk/1VMHOIkD23Pjn2U2S+dP0O9vFnRrrIxYdH0SgKXyd40eU= Received: by 10.64.49.20 with SMTP id w20mr184973qbw; Thu, 04 May 2006 17:59:31 -0700 (PDT) Received: from ?192.168.0.6? ( [70.56.4.48]) by mx.gmail.com with ESMTP id f13sm14313qba.2006.05.04.17.59.31; Thu, 04 May 2006 17:59:31 -0700 (PDT) From: Andrew To: freebsd-hackers@freebsd.org Content-Type: text/plain Date: Thu, 04 May 2006 19:57:49 -0500 Message-Id: <1146790669.3352.38.camel@LatitudeFC5.network> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 (2.6.1-1.fc5.2) Content-Transfer-Encoding: 7bit Subject: programming question: u_char vs. uint32_t 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, 05 May 2006 00:59:35 -0000 Hello all, I'm reading through /usr/src/sys/dd/dd.h, and I noticed the following lines: 39 u_char *db; /* buffer address */ 40 u_char *dbp; /* current buffer I/O address */ Why was u_char used instead of uint32_t? Aren't pointers always 32 bits on a 32 bit machine? Thanks, Andrew From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 01:03: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 30D6E16A400 for ; Fri, 5 May 2006 01:03:38 +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 C57CA43D48 for ; Fri, 5 May 2006 01:03:37 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (lmr3ho3ynj7d50vs@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k4513aqk084019; Thu, 4 May 2006 18:03:36 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k4513a5j084018; Thu, 4 May 2006 18:03:36 -0700 (PDT) (envelope-from jmg) Date: Thu, 4 May 2006 18:03:35 -0700 From: John-Mark Gurney To: Andrew Message-ID: <20060505010335.GW728@funkthat.com> Mail-Followup-To: Andrew , freebsd-hackers@freebsd.org References: <1146790669.3352.38.camel@LatitudeFC5.network> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1146790669.3352.38.camel@LatitudeFC5.network> 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: freebsd-hackers@freebsd.org Subject: Re: programming question: u_char vs. uint32_t 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: Fri, 05 May 2006 01:03:38 -0000 Andrew wrote this message on Thu, May 04, 2006 at 19:57 -0500: > I'm reading through /usr/src/sys/dd/dd.h, and I noticed the following > lines: > > 39 u_char *db; /* buffer address */ > 40 u_char *dbp; /* current buffer I/O address */ > > Why was u_char used instead of uint32_t? Aren't pointers always 32 bits > on a 32 bit machine? You're confusing the type of the pointer w/ a pointer... These are correct, please read a basic intro to pointers in C... -- 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 Fri May 5 01:08:36 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 3F5EB16A403 for ; Fri, 5 May 2006 01:08:36 +0000 (UTC) (envelope-from andrew.chace@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC38343D48 for ; Fri, 5 May 2006 01:08:35 +0000 (GMT) (envelope-from andrew.chace@gmail.com) Received: by nz-out-0102.google.com with SMTP id l1so564192nzf for ; Thu, 04 May 2006 18:08:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=Of5SIBJYARtPwd/XGGYglqGJrF510Jl9HgW6h3QSyh2TQxHdftIwbh6DTW23pCwrtOkTcU9oU/tKmOp7cfv5hbuc10+fHbhtRrvMk9bZKCBs2sO3H+My7zHpml9a87I52ktg1pBOAAJxm5Sk+ZqnAcBaRV3FA3ULq/ptPGtxrE8= Received: by 10.65.185.13 with SMTP id m13mr219670qbp; Thu, 04 May 2006 18:08:35 -0700 (PDT) Received: from ?192.168.0.6? ( [70.56.4.48]) by mx.gmail.com with ESMTP id e16sm325763qbe.2006.05.04.18.08.34; Thu, 04 May 2006 18:08:34 -0700 (PDT) From: Andrew To: John-Mark Gurney In-Reply-To: <20060505010335.GW728@funkthat.com> References: <1146790669.3352.38.camel@LatitudeFC5.network> <20060505010335.GW728@funkthat.com> Content-Type: text/plain Date: Thu, 04 May 2006 20:06:52 -0500 Message-Id: <1146791213.3352.40.camel@LatitudeFC5.network> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 (2.6.1-1.fc5.2) Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: programming question: u_char vs. uint32_t 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, 05 May 2006 01:08:36 -0000 On Thu, 2006-05-04 at 18:03 -0700, John-Mark Gurney wrote: > Andrew wrote this message on Thu, May 04, 2006 at 19:57 -0500: > > I'm reading through /usr/src/sys/dd/dd.h, and I noticed the following > > lines: > > > > 39 u_char *db; /* buffer address */ > > 40 u_char *dbp; /* current buffer I/O address */ > > > > Why was u_char used instead of uint32_t? Aren't pointers always 32 bits > > on a 32 bit machine? > > You're confusing the type of the pointer w/ a pointer... These are > correct, please read a basic intro to pointers in C... Ahh yes, thank-you. A small case of cognitive indigestion; I think it's clearing up now. ;-) -Andrew From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 02:16: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 9537216A400 for ; Fri, 5 May 2006 02:16:16 +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 7B3AF43D45 for ; Fri, 5 May 2006 02:16:15 +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 k452GEPI066920 for ; Thu, 4 May 2006 21:16:14 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <445AB56F.8090907@centtech.com> Date: Thu, 04 May 2006 21:16:15 -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/1444/Thu May 4 16:21:06 2006 on mh2.centtech.com X-Virus-Status: Clean Subject: Core Duo - only one cpu being used 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, 05 May 2006 02:16:16 -0000 Forgive me if I've missed this on a list somewhere, but My new laptop with a Core Duo doesn't seem to use both CPU's. It sees both, but I never see anything on cpu 1. Here's a top snippet: last pid: 20852; load averages: 1.31, 1.27, 1.00 up 0+01:20:55 21:05:47 100 processes: 2 running, 98 sleeping CPU states: 47.4% user, 0.0% nice, 1.3% system, 1.3% interrupt, 50.0% idle Mem: 383M Active, 391M Inact, 154M Wired, 34M Cache, 110M Buf, 25M Free Swap: 2048M Total, 2048M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 20851 root 1 127 0 23024K 22400K RUN 0 0:03 88.66% cc1plus 861 anderson 1 96 0 108M 85384K select 0 1:22 0.98% Xorg 958 anderson 5 20 0 109M 97228K kserel 0 2:14 0.00% firefox-bin 922 anderson 1 96 0 19556K 14944K select 0 0:54 0.00% xfce4-panel 592 root 1 8 0 1348K 872K nanslp 0 0:43 0.00% powerd 932 anderson 6 20 0 75360K 60860K kserel 0 0:20 0.00% thunderbird-bin 28378 root 1 8 0 31388K 30920K wait 0 0:17 0.00% ruby18 909 anderson 1 96 0 29416K 15816K select 0 0:12 0.00% kdeinit 920 anderson 1 96 0 16412K 11228K select 0 0:03 0.00% xfdesktop 559 root 1 96 0 1448K 872K select 0 0:02 0.00% bthidd All processes are on cpu 0. Output of sysctl dev.cpu shows: dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.freq: 2005 dev.cpu.0.freq_levels: 2005/-1 1754/-1 1503/-1 1253/-1 1002/-1 751/-1 501/-1 250/-1 dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU1 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 More information (dmesg, sysctl -a, devinfo, pciconf, etc) can be found here: http://www.googlebit.com/freebsd/200605041945/ 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 Fri May 5 02:29: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 5DFC216A406 for ; Fri, 5 May 2006 02:29:24 +0000 (UTC) (envelope-from yosimoto@waishi.jp) Received: from ns.waishi.jp (ns.waishi.jp [61.199.233.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1584243DBF for ; Fri, 5 May 2006 02:28:54 +0000 (GMT) (envelope-from yosimoto@waishi.jp) Received: from darwin.waishi.jp (darwin.waishi.jp [61.199.233.196]) by ns.waishi.jp (Postfix) with ESMTP id 41CF1D8F37 for ; Fri, 5 May 2006 11:28:51 +0900 (JST) Date: Fri, 5 May 2006 11:28:50 +0900 From: Shin-ichi Yoshimoto To: freebsd-hackers@freebsd.org Message-ID: <20060505112850.667730.117329f3@waishi.jp> In-Reply-To: <445AB56F.8090907@centtech.com> References: <445AB56F.8090907@centtech.com> Mime-Version: 1.0 (GMessage framework 1.3.8) Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Organization: WAISHI.JP X-Mailer: GyazMail version 1.3.8 Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 02:29:24 -0000 On Thu, 04 May 2006 21:16:15 -0500, Eric Anderson wrote: > Forgive me if I've missed this on a list somewhere, but My new laptop > with a Core Duo doesn't seem to use both CPU's. It sees both, but I > never see anything on cpu 1. Here's a top snippet: My new desktop (M/B is ASUS N4L-VM DH) with a Core Duo is fine to use both CPU's in 6.1-RC like this: last pid: 546; load averages: 0.01, 0.11, 0.07 up 0+00:06:20 11:23:32 23 processes: 1 running, 22 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 9312K Active, 84M Inact, 81M Wired, 112M Buf, 1822M Free Swap: 4096M Total, 4096M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 533 root 1 76 0 2272K 1532K CPU0 0 0:00 0.00% top 509 root 1 4 0 6104K 3064K sbwait 1 0:00 0.00% sshd 401 root 1 76 0 2840K 1700K select 0 0:00 0.00% ntpd 520 root 1 20 0 5388K 3064K pause 1 0:00 0.00% tcsh 512 yosimoto 1 76 0 6080K 3076K select 0 0:00 0.00% sshd 513 yosimoto 1 20 0 5060K 2848K pause 1 0:00 0.00% tcsh 296 root 1 76 0 1300K 948K select 0 0:00 0.00% syslogd 519 yosimoto 1 8 0 1604K 1292K wait 1 0:00 0.00% su 432 root 1 76 0 3400K 2728K select 0 0:00 0.00% sendmail 442 root 1 8 0 1312K 1044K nanslp 0 0:00 0.00% cron 502 root 1 5 0 1268K 904K ttyin 0 0:00 0.00% getty 504 root 1 5 0 1268K 904K ttyin 1 0:00 0.00% getty 507 root 1 5 0 1268K 904K ttyin 1 0:00 0.00% getty 508 root 1 5 0 1268K 904K ttyin 1 0:00 0.00% getty 505 root 1 5 0 1268K 904K ttyin 1 0:00 0.00% getty 506 root 1 5 0 1268K 904K ttyin 1 0:00 0.00% getty 501 root 1 5 0 1268K 904K ttyin 1 0:00 0.00% getty 503 root 1 5 0 1268K 904K ttyin 1 0:00 0.00% getty 426 root 1 76 0 3356K 2540K select 0 0:00 0.00% sshd 436 smmsp 1 20 0 3300K 2704K pause 0 0:00 0.00% sendmail 262 root 1 82 0 500K 360K select 1 0:00 0.00% devd 145 root 1 20 0 1176K 680K pause 0 0:00 0.00% adjkerntz 463 root 1 139 0 1260K 768K select 0 0:00 0.00% moused > All processes are on cpu 0. Output of sysctl dev.cpu shows: In my case: # sysctl -a | grep dev.cpu dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU1 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU2 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 --- Shin-ichi YOSHIMOTO$B!!(B From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 02:47: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 BC51716A4DB for ; Fri, 5 May 2006 02:47:24 +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 7CE8C43D46 for ; Fri, 5 May 2006 02:47:24 +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 0801319F2C; Thu, 4 May 2006 19:47:22 -0700 (PDT) Message-ID: <445ABCB7.5020301@bitfreak.org> Date: Thu, 04 May 2006 19:47:19 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Eric Anderson References: <445AB56F.8090907@centtech.com> In-Reply-To: <445AB56F.8090907@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 02:47:24 -0000 Eric Anderson wrote: > Forgive me if I've missed this on a list somewhere, but My new laptop > with a Core Duo doesn't seem to use both CPU's. It sees both, but I > never see anything on cpu 1. Here's a top snippet: Your top output shows a single process eating the CPU. A single process can't span CPUs, so you're only going to see one CPU in use. You need to do something in parallel, like make -j N where N > 1. From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 02:50:56 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 D683716A40A for ; Fri, 5 May 2006 02:50: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 8363543D48 for ; Fri, 5 May 2006 02:50:56 +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 k452osS2068249; Thu, 4 May 2006 21:50:54 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <445ABD8F.4060208@centtech.com> Date: Thu, 04 May 2006 21:50:55 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Darren Pilgrim References: <445AB56F.8090907@centtech.com> <445ABCB7.5020301@bitfreak.org> In-Reply-To: <445ABCB7.5020301@bitfreak.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1444/Thu May 4 16:21:06 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 02:50:56 -0000 Darren Pilgrim wrote: > Eric Anderson wrote: >> Forgive me if I've missed this on a list somewhere, but My new laptop >> with a Core Duo doesn't seem to use both CPU's. It sees both, but I >> never see anything on cpu 1. Here's a top snippet: > > Your top output shows a single process eating the CPU. A single process > can't span CPUs, so you're only going to see one CPU in use. You need > to do something in parallel, like make -j N where N > 1. I understand that a single process won't span cpu's, but there isn't a single process on the second cpu, and running multiple: cat /dev/random | md5 Still slams one cpu. 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 May 5 03:07: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 0630816A400 for ; Fri, 5 May 2006 03:07:58 +0000 (UTC) (envelope-from oceanare@pacific.net.sg) Received: from smtpgate2.pacific.net.sg (smtpgate2.pacific.net.sg [203.120.90.32]) by mx1.FreeBSD.org (Postfix) with SMTP id BDECF43D46 for ; Fri, 5 May 2006 03:07:56 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 30345 invoked from network); 5 May 2006 03:07:54 -0000 Received: from maxwell6.pacific.net.sg (203.120.90.212) by smtpgate2.pacific.net.sg with SMTP; 5 May 2006 03:07:53 -0000 Received: from [192.168.0.107] ([210.24.122.33]) by maxwell6.pacific.net.sg with ESMTP id <20060505030751.HUPJ1180.maxwell6.pacific.net.sg@[192.168.0.107]>; Fri, 5 May 2006 11:07:51 +0800 Message-ID: <445AC174.5050102@pacific.net.sg> Date: Fri, 05 May 2006 11:07:32 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Thunderbird 1.5.0.2 (X11/20060501) MIME-Version: 1.0 To: Eric Anderson References: <445AB56F.8090907@centtech.com> In-Reply-To: <445AB56F.8090907@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 03:07:58 -0000 Hi, Eric Anderson wrote: > > All processes are on cpu 0. Output of sysctl dev.cpu shows: can you show all tasks running? Erich From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 03:20: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 EF4DA16A415 for ; Fri, 5 May 2006 03:20:16 +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 4D53343D5F for ; Fri, 5 May 2006 03:20:16 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k453KEnS078523; Thu, 4 May 2006 22:20:15 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <445AC46F.30702@centtech.com> Date: Thu, 04 May 2006 22:20:15 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Erich Dollansky References: <445AB56F.8090907@centtech.com> <445AC174.5050102@pacific.net.sg> In-Reply-To: <445AC174.5050102@pacific.net.sg> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1444/Thu May 4 16:21:06 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 03:20:18 -0000 Erich Dollansky wrote: > Hi, > > Eric Anderson wrote: >> >> All processes are on cpu 0. Output of sysctl dev.cpu shows: > > can you show all tasks running? > > Erich last pid: 33015; load averages: 1.20, 1.08, 1.08 up 0+02:35:03 22:19:55 98 processes: 4 running, 94 sleeping CPU states: 19.7% user, 0.0% nice, 28.9% system, 1.3% interrupt, 50.1% idle Mem: 388M Active, 251M Inact, 132M Wired, 11M Cache, 110M Buf, 206M Free Swap: 2048M Total, 2048M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 33010 root 1 102 0 4984K 4364K RUN 0 0:06 27.21% bzip2 33012 anderson 1 100 0 1296K 636K RUN 0 0:04 21.09% cat 33014 anderson 1 100 0 1296K 636K RUN 0 0:03 19.97% cat 33013 anderson 1 -8 0 1356K 708K piperd 0 0:01 3.72% md5 33015 anderson 1 -8 0 1356K 708K piperd 0 0:01 3.14% md5 33011 root 1 -8 0 1736K 1224K piperd 0 0:01 2.36% bsdtar 861 anderson 1 96 0 115M 89532K select 0 2:24 1.12% Xorg 592 root 1 8 0 1348K 872K nanslp 0 1:24 0.05% powerd 958 anderson 5 20 0 109M 96828K kserel 0 3:04 0.00% firefox-bin 922 anderson 1 96 0 19604K 14992K select 0 1:48 0.00% xfce4-panel 932 anderson 6 20 0 79688K 65352K kserel 0 0:45 0.00% thunderbird-bin 909 anderson 1 96 0 29416K 16044K select 0 0:24 0.00% kdeinit 28378 root 1 8 0 31388K 30912K wait 0 0:19 0.00% ruby18 920 anderson 1 96 0 16520K 11356K select 0 0:06 0.00% xfdesktop 1039 anderson 1 96 0 6388K 4752K select 0 0:04 0.00% xterm 559 root 1 96 0 1448K 872K select 0 0:03 0.00% bthidd 870 anderson 1 96 0 27000K 17472K select 0 0:03 0.00% gaim 1037 anderson 1 96 0 7916K 5824K select 0 0:02 0.00% nedit 888 anderson 1 96 0 18600K 13752K select 0 0:02 0.00% xfce4-session 916 anderson 1 96 0 14592K 10344K select 0 0:02 0.00% xfwm4 897 anderson 1 96 0 14404K 8460K select 0 0:02 0.00% xfce-mcs-manager 918 anderson 1 96 0 13116K 8968K select 0 0:01 0.00% xftaskbar4 869 anderson 1 96 0 6820K 5080K select 0 0:01 0.00% xterm 25663 anderson 1 96 0 5540K 3904K select 0 0:01 0.00% xterm 1192 anderson 1 96 0 6128K 4492K select 0 0:01 0.00% xterm 235 root 1 96 0 3056K 1684K select 0 0:00 0.00% wpa_supplicant 630 root 1 96 0 2620K 1952K select 0 0:00 0.00% httpd 68119 anderson 1 96 0 6244K 4548K select 0 0:00 0.00% xterm 92204 anderson 1 96 0 5536K 3848K select 0 0:00 0.00% xterm 901 anderson 1 97 0 25284K 11308K select 0 0:00 0.00% kdeinit 683 root 1 96 0 3712K 2404K select 0 0:00 0.00% sendmail 68120 anderson 1 96 0 3900K 2416K select 0 0:00 0.00% ssh 934 anderson 1 96 0 4360K 2880K select 0 0:00 0.00% gconfd-2 1193 anderson 1 5 0 3360K 1924K ttyin 0 0:00 0.00% bash 32933 root 1 8 0 1624K 1476K wait 0 0:00 0.00% make 25666 root 1 5 0 3276K 1824K ttyin 0 0:00 0.00% bash 30424 anderson 1 96 0 5536K 4192K select 0 0:00 0.00% xterm 889 anderson 1 8 0 3348K 1908K wait 0 0:00 0.00% bash 29892 anderson 1 96 0 2600K 1696K CPU0 0 0:00 0.00% top 480 root 1 96 0 1412K 924K select 0 0:00 0.00% syslogd 904 anderson 1 96 0 24004K 10172K select 0 0:00 0.00% kdeinit 907 anderson 1 96 0 24600K 10772K select 0 0:00 0.00% kdeinit 92205 anderson 1 5 0 3308K 1876K ttyin 0 0:00 0.00% bash 694 root 1 8 0 1428K 1028K nanslp 0 0:00 0.00% cron 924 anderson 1 8 0 1768K 1136K wait 0 0:00 0.00% sh 785 root 1 8 0 1748K 1256K wait 0 0:00 0.00% login 30453 anderson 1 5 0 3308K 1920K ttyin 0 0:00 0.00% bash 830 anderson 1 8 0 3320K 1864K wait 0 0:00 0.00% bash 1040 anderson 1 8 0 3344K 1908K wait 0 0:00 0.00% bash 25664 anderson 1 8 0 3308K 1872K wait 0 0:00 0.00% bash 1043 root 1 8 0 3304K 1852K wait 0 0:00 0.00% bash 936 anderson 1 8 0 1768K 1136K wait 0 0:00 0.00% sh 616 root 1 96 0 1320K 768K select 0 0:00 0.00% usbd 25665 anderson 1 8 0 1728K 1244K wait 0 0:00 0.00% su 1042 anderson 1 8 0 1728K 1236K wait 0 0:00 0.00% su 871 anderson 1 8 0 1764K 1060K wait 0 0:00 0.00% sh 32932 root 1 105 0 1376K 784K select 0 0:00 0.00% script 242 root 1 96 0 1500K 988K select 0 0:00 0.00% dhclient 841 anderson 1 8 0 1792K 1108K wait 0 0:00 0.00% sh 248 _dhcp 1 96 0 1500K 1040K select 0 0:00 0.00% dhclient 687 smmsp 1 20 0 3592K 2176K pause 0 0:00 0.00% sendmail 575 root 1 117 0 1384K 880K select 0 0:00 0.00% lpd 864 anderson 1 8 0 1756K 1056K wait 0 0:00 0.00% sh 954 anderson 1 8 0 1784K 1152K wait 0 0:00 0.00% sh 928 anderson 1 8 0 1784K 1152K wait 0 0:00 0.00% sh 860 anderson 1 8 0 2152K 1252K wait 0 0:00 0.00% xinit 792 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty 789 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty 787 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty 791 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty 790 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty 786 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty 788 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty 768 root 1 116 0 1504K 1052K select 0 0:00 0.00% inetd 33008 root 1 8 0 1760K 1052K wait 0 0:00 0.00% sh 840 anderson 1 8 0 3324K 1868K wait 0 0:00 0.00% bash 606 nobody 1 112 0 1384K 904K select 0 0:00 0.00% sdpd 885 anderson 1 96 0 2284K 1264K select 0 0:00 0.00% dbus-launch 677 root 1 116 0 3676K 1932K select 0 0:00 0.00% sshd 914 anderson 1 96 0 2928K 1340K select 0 0:00 0.00% gnome-keyring-daemo 555 root 1 4 0 1424K 796K sbwait 0 0:00 0.00% hcsecd 880 anderson 1 96 0 3384K 1700K select 0 0:00 0.00% ssh-agent 793 www 1 4 0 2632K 1956K accept 0 0:00 0.00% httpd 408 root 1 96 0 516K 300K select 0 0:00 0.00% devd 33009 root 1 8 0 1760K 1052K wait 0 0:00 0.00% sh 794 www 1 4 0 2632K 1956K accept 0 0:00 0.00% httpd 886 anderson 1 97 0 2704K 1020K select 0 0:00 0.00% dbus-daemon 170 root 1 20 0 1284K 660K pause 0 0:00 0.00% adjkerntz 742 root 1 111 0 1376K 720K select 0 0:00 0.00% moused -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 04:11: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 CE36D16A404 for ; Fri, 5 May 2006 04:11:11 +0000 (UTC) (envelope-from oceanare@pacific.net.sg) Received: from smtpgate2.pacific.net.sg (smtpgate2.pacific.net.sg [203.120.90.32]) by mx1.FreeBSD.org (Postfix) with SMTP id CFD4243D46 for ; Fri, 5 May 2006 04:11:10 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 32741 invoked from network); 5 May 2006 04:11:08 -0000 Received: from maxwell2.pacific.net.sg (203.120.90.192) by smtpgate2.pacific.net.sg with SMTP; 5 May 2006 04:11:07 -0000 Received: from [192.168.0.107] ([210.24.122.33]) by maxwell2.pacific.net.sg with ESMTP id <20060505041106.VMVF28656.maxwell2.pacific.net.sg@[192.168.0.107]>; Fri, 5 May 2006 12:11:06 +0800 Message-ID: <445AD048.80305@pacific.net.sg> Date: Fri, 05 May 2006 12:10:48 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Thunderbird 1.5.0.2 (X11/20060501) MIME-Version: 1.0 To: Eric Anderson References: <445AB56F.8090907@centtech.com> <445AC174.5050102@pacific.net.sg> <445AC46F.30702@centtech.com> In-Reply-To: <445AC46F.30702@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 04:11:12 -0000 Hi, this is hard to believe. Just add -S to the command line or enter S while top is running. Top should show you then on top the two idle threads. Erich Eric Anderson wrote: > Erich Dollansky wrote: >> Hi, >> >> Eric Anderson wrote: >>> >>> All processes are on cpu 0. Output of sysctl dev.cpu shows: >> >> can you show all tasks running? >> >> Erich > > > last pid: 33015; load averages: 1.20, 1.08, 1.08 > up 0+02:35:03 22:19:55 > 98 processes: 4 running, 94 sleeping > CPU states: 19.7% user, 0.0% nice, 28.9% system, 1.3% interrupt, 50.1% > idle > Mem: 388M Active, 251M Inact, 132M Wired, 11M Cache, 110M Buf, 206M Free > Swap: 2048M Total, 2048M Free > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 33010 root 1 102 0 4984K 4364K RUN 0 0:06 27.21% bzip2 > 33012 anderson 1 100 0 1296K 636K RUN 0 0:04 21.09% cat > 33014 anderson 1 100 0 1296K 636K RUN 0 0:03 19.97% cat > 33013 anderson 1 -8 0 1356K 708K piperd 0 0:01 3.72% md5 > 33015 anderson 1 -8 0 1356K 708K piperd 0 0:01 3.14% md5 > 33011 root 1 -8 0 1736K 1224K piperd 0 0:01 2.36% bsdtar > 861 anderson 1 96 0 115M 89532K select 0 2:24 1.12% Xorg > 592 root 1 8 0 1348K 872K nanslp 0 1:24 0.05% powerd > 958 anderson 5 20 0 109M 96828K kserel 0 3:04 0.00% > firefox-bin > 922 anderson 1 96 0 19604K 14992K select 0 1:48 0.00% > xfce4-panel > 932 anderson 6 20 0 79688K 65352K kserel 0 0:45 0.00% > thunderbird-bin > 909 anderson 1 96 0 29416K 16044K select 0 0:24 0.00% kdeinit > 28378 root 1 8 0 31388K 30912K wait 0 0:19 0.00% ruby18 > 920 anderson 1 96 0 16520K 11356K select 0 0:06 0.00% > xfdesktop > 1039 anderson 1 96 0 6388K 4752K select 0 0:04 0.00% xterm > 559 root 1 96 0 1448K 872K select 0 0:03 0.00% bthidd > 870 anderson 1 96 0 27000K 17472K select 0 0:03 0.00% gaim > 1037 anderson 1 96 0 7916K 5824K select 0 0:02 0.00% nedit > 888 anderson 1 96 0 18600K 13752K select 0 0:02 0.00% > xfce4-session > 916 anderson 1 96 0 14592K 10344K select 0 0:02 0.00% xfwm4 > 897 anderson 1 96 0 14404K 8460K select 0 0:02 0.00% > xfce-mcs-manager > 918 anderson 1 96 0 13116K 8968K select 0 0:01 0.00% > xftaskbar4 > 869 anderson 1 96 0 6820K 5080K select 0 0:01 0.00% xterm > 25663 anderson 1 96 0 5540K 3904K select 0 0:01 0.00% xterm > 1192 anderson 1 96 0 6128K 4492K select 0 0:01 0.00% xterm > 235 root 1 96 0 3056K 1684K select 0 0:00 0.00% > wpa_supplicant > 630 root 1 96 0 2620K 1952K select 0 0:00 0.00% httpd > 68119 anderson 1 96 0 6244K 4548K select 0 0:00 0.00% xterm > 92204 anderson 1 96 0 5536K 3848K select 0 0:00 0.00% xterm > 901 anderson 1 97 0 25284K 11308K select 0 0:00 0.00% kdeinit > 683 root 1 96 0 3712K 2404K select 0 0:00 0.00% > sendmail > 68120 anderson 1 96 0 3900K 2416K select 0 0:00 0.00% ssh > 934 anderson 1 96 0 4360K 2880K select 0 0:00 0.00% > gconfd-2 > 1193 anderson 1 5 0 3360K 1924K ttyin 0 0:00 0.00% bash > 32933 root 1 8 0 1624K 1476K wait 0 0:00 0.00% make > 25666 root 1 5 0 3276K 1824K ttyin 0 0:00 0.00% bash > 30424 anderson 1 96 0 5536K 4192K select 0 0:00 0.00% xterm > 889 anderson 1 8 0 3348K 1908K wait 0 0:00 0.00% bash > 29892 anderson 1 96 0 2600K 1696K CPU0 0 0:00 0.00% top > 480 root 1 96 0 1412K 924K select 0 0:00 0.00% syslogd > 904 anderson 1 96 0 24004K 10172K select 0 0:00 0.00% kdeinit > 907 anderson 1 96 0 24600K 10772K select 0 0:00 0.00% kdeinit > 92205 anderson 1 5 0 3308K 1876K ttyin 0 0:00 0.00% bash > 694 root 1 8 0 1428K 1028K nanslp 0 0:00 0.00% cron > 924 anderson 1 8 0 1768K 1136K wait 0 0:00 0.00% sh > 785 root 1 8 0 1748K 1256K wait 0 0:00 0.00% login > 30453 anderson 1 5 0 3308K 1920K ttyin 0 0:00 0.00% bash > 830 anderson 1 8 0 3320K 1864K wait 0 0:00 0.00% bash > 1040 anderson 1 8 0 3344K 1908K wait 0 0:00 0.00% bash > 25664 anderson 1 8 0 3308K 1872K wait 0 0:00 0.00% bash > 1043 root 1 8 0 3304K 1852K wait 0 0:00 0.00% bash > 936 anderson 1 8 0 1768K 1136K wait 0 0:00 0.00% sh > 616 root 1 96 0 1320K 768K select 0 0:00 0.00% usbd > 25665 anderson 1 8 0 1728K 1244K wait 0 0:00 0.00% su > 1042 anderson 1 8 0 1728K 1236K wait 0 0:00 0.00% su > 871 anderson 1 8 0 1764K 1060K wait 0 0:00 0.00% sh > 32932 root 1 105 0 1376K 784K select 0 0:00 0.00% script > 242 root 1 96 0 1500K 988K select 0 0:00 0.00% > dhclient > 841 anderson 1 8 0 1792K 1108K wait 0 0:00 0.00% sh > 248 _dhcp 1 96 0 1500K 1040K select 0 0:00 0.00% > dhclient > 687 smmsp 1 20 0 3592K 2176K pause 0 0:00 0.00% > sendmail > 575 root 1 117 0 1384K 880K select 0 0:00 0.00% lpd > 864 anderson 1 8 0 1756K 1056K wait 0 0:00 0.00% sh > 954 anderson 1 8 0 1784K 1152K wait 0 0:00 0.00% sh > 928 anderson 1 8 0 1784K 1152K wait 0 0:00 0.00% sh > 860 anderson 1 8 0 2152K 1252K wait 0 0:00 0.00% xinit > 792 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty > 789 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty > 787 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty > 791 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty > 790 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty > 786 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty > 788 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty > 768 root 1 116 0 1504K 1052K select 0 0:00 0.00% inetd > 33008 root 1 8 0 1760K 1052K wait 0 0:00 0.00% sh > 840 anderson 1 8 0 3324K 1868K wait 0 0:00 0.00% bash > 606 nobody 1 112 0 1384K 904K select 0 0:00 0.00% sdpd > 885 anderson 1 96 0 2284K 1264K select 0 0:00 0.00% > dbus-launch > 677 root 1 116 0 3676K 1932K select 0 0:00 0.00% sshd > 914 anderson 1 96 0 2928K 1340K select 0 0:00 0.00% > gnome-keyring-daemo > 555 root 1 4 0 1424K 796K sbwait 0 0:00 0.00% hcsecd > 880 anderson 1 96 0 3384K 1700K select 0 0:00 0.00% > ssh-agent > 793 www 1 4 0 2632K 1956K accept 0 0:00 0.00% httpd > 408 root 1 96 0 516K 300K select 0 0:00 0.00% devd > 33009 root 1 8 0 1760K 1052K wait 0 0:00 0.00% sh > 794 www 1 4 0 2632K 1956K accept 0 0:00 0.00% httpd > 886 anderson 1 97 0 2704K 1020K select 0 0:00 0.00% > dbus-daemon > 170 root 1 20 0 1284K 660K pause 0 0:00 0.00% > adjkerntz > 742 root 1 111 0 1376K 720K select 0 0:00 0.00% moused > > > > > > > From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 04:16:45 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 6ADF916A402 for ; Fri, 5 May 2006 04:16:45 +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 BB40443D49 for ; Fri, 5 May 2006 04:16:44 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k454GhSi080674; Thu, 4 May 2006 23:16:43 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <445AD1AC.1070902@centtech.com> Date: Thu, 04 May 2006 23:16:44 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Erich Dollansky References: <445AB56F.8090907@centtech.com> <445AC174.5050102@pacific.net.sg> <445AC46F.30702@centtech.com> <445AD048.80305@pacific.net.sg> In-Reply-To: <445AD048.80305@pacific.net.sg> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1444/Thu May 4 16:21:06 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 04:16:45 -0000 Erich Dollansky wrote: > Hi, > > this is hard to believe. > > Just add -S to the command line or enter S while top is running. > > Top should show you then on top the two idle threads. Here's the output: last pid: 2654; load averages: 1.10, 1.16, 1.12 up 0+03:30:41 23:15:33 159 processes: 5 running, 132 sleeping, 22 waiting CPU states: 46.5% user, 0.0% nice, 3.2% system, 0.4% interrupt, 49.9% idle Mem: 408M Active, 398M Inact, 134M Wired, 32M Cache, 110M Buf, 15M Free Swap: 2048M Total, 2048M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root 1 171 52 0K 8K CPU1 0 0:00 99.02% idle: cpu1 2653 root 1 128 0 18564K 17560K RUN 0 0:01 34.00% cc1plus 24 root 1 8 0 0K 8K - 0 4:34 1.32% ath0 taskq 23 root 1 -68 -187 0K 8K WAIT 0 2:37 0.88% irq17: ath0 861 anderson 1 96 0 112M 90744K select 0 3:27 0.10% Xorg 922 anderson 1 96 0 19672K 15060K select 0 2:54 0.05% xfce4-panel 12 root 1 171 52 0K 8K RUN 0 51:04 0.00% idle: cpu0 958 anderson 5 20 0 109M 96876K kserel 0 3:48 0.00% firefox-bin 592 root 1 8 0 1348K 872K nanslp 0 2:09 0.00% powerd 932 anderson 6 20 0 87196K 72904K kserel 0 1:02 0.00% thunderbird-bin 909 anderson 1 96 0 29416K 15964K select 0 0:39 0.00% kdeinit 46 root 1 171 52 0K 8K RUN 0 0:34 0.00% pagezero 14 root 1 -32 -151 0K 8K WAIT 0 0:33 0.00% swi4: clock sio 4 root 1 -8 0 0K 8K - 0 0:23 0.00% g_down 22 root 1 -80 -199 0K 8K WAIT 0 0:21 0.00% irq16: nvidia0 3 root 1 -8 0 0K 8K - 0 0:19 0.00% g_up 28378 root 1 8 0 31388K 30912K wait 0 0:19 0.00% ruby18 49 root 1 20 0 0K 8K syncer 0 0:09 0.00% syncer 38 root 1 -64 -183 0K 8K WAIT 0 0:08 0.00% irq14: ata0 920 anderson 1 96 0 16536K 11372K select 0 0:07 0.00% xfdesktop 40 root 1 0 0 0K 8K tzpoll 0 0:06 0.00% acpi_thermal 559 root 1 96 0 1448K 872K select 0 0:05 0.00% bthidd 870 anderson 1 96 0 26996K 17060K select 0 0:05 0.00% gaim 1039 anderson 1 96 0 6388K 4752K select 0 0:05 0.00% xterm 1037 anderson 1 96 0 7916K 5824K select 0 0:03 0.00% nedit 916 anderson 1 96 0 14592K 10340K select 0 0:02 0.00% xfwm4 13 root 1 -44 -163 0K 8K WAIT 0 0:02 0.00% swi1: net 888 anderson 1 96 0 18600K 13752K select 0 0:02 0.00% xfce4-session 897 anderson 1 96 0 14444K 8500K select 0 0:02 0.00% xfce-mcs-manager 26 root 1 -64 -183 0K 8K WAIT 0 0:02 0.00% irq20: uhci0 ehci0 918 anderson 1 96 0 13116K 8976K select 0 0:02 0.00% xftaskbar4 16 root 1 -16 0 0K 8K - 0 0:02 0.00% yarrow 869 anderson 1 96 0 6280K 4540K select 0 0:01 0.00% xterm 2 root 1 -8 0 0K 8K - 0 0:01 0.00% g_event 55 root 1 12 0 0K 8K - 0 0:01 0.00% schedcpu 1192 anderson 1 96 0 6908K 5272K select 0 0:01 0.00% xterm 18 root 1 -24 -143 0K 8K WAIT 0 0:01 0.00% swi6: + 25663 anderson 1 96 0 5540K 3904K select 0 0:01 0.00% xterm 235 root 1 96 0 3056K 1684K select 0 0:01 0.00% wpa_supplicant 19 root 1 -24 -143 0K 8K WAIT 0 0:01 0.00% swi6: task queue 41 root 1 -60 -179 0K 8K WAIT 0 0:01 0.00% irq1: atkbd0 [..snip..] > Eric Anderson wrote: >> Erich Dollansky wrote: >>> Hi, >>> >>> Eric Anderson wrote: >>>> >>>> All processes are on cpu 0. Output of sysctl dev.cpu shows: >>> >>> can you show all tasks running? >>> >>> Erich >> >> >> last pid: 33015; load averages: 1.20, 1.08, >> 1.08 up 0+02:35:03 22:19:55 >> 98 processes: 4 running, 94 sleeping >> CPU states: 19.7% user, 0.0% nice, 28.9% system, 1.3% interrupt, >> 50.1% idle >> Mem: 388M Active, 251M Inact, 132M Wired, 11M Cache, 110M Buf, 206M Free >> Swap: 2048M Total, 2048M Free >> >> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU >> COMMAND >> 33010 root 1 102 0 4984K 4364K RUN 0 0:06 27.21% bzip2 >> 33012 anderson 1 100 0 1296K 636K RUN 0 0:04 21.09% cat >> 33014 anderson 1 100 0 1296K 636K RUN 0 0:03 19.97% cat >> 33013 anderson 1 -8 0 1356K 708K piperd 0 0:01 3.72% md5 >> 33015 anderson 1 -8 0 1356K 708K piperd 0 0:01 3.14% md5 >> 33011 root 1 -8 0 1736K 1224K piperd 0 0:01 2.36% >> bsdtar >> 861 anderson 1 96 0 115M 89532K select 0 2:24 1.12% Xorg >> 592 root 1 8 0 1348K 872K nanslp 0 1:24 0.05% >> powerd >> 958 anderson 5 20 0 109M 96828K kserel 0 3:04 0.00% >> firefox-bin >> 922 anderson 1 96 0 19604K 14992K select 0 1:48 0.00% >> xfce4-panel >> 932 anderson 6 20 0 79688K 65352K kserel 0 0:45 0.00% >> thunderbird-bin >> 909 anderson 1 96 0 29416K 16044K select 0 0:24 0.00% >> kdeinit >> 28378 root 1 8 0 31388K 30912K wait 0 0:19 0.00% >> ruby18 >> 920 anderson 1 96 0 16520K 11356K select 0 0:06 0.00% >> xfdesktop >> 1039 anderson 1 96 0 6388K 4752K select 0 0:04 0.00% xterm >> 559 root 1 96 0 1448K 872K select 0 0:03 0.00% >> bthidd >> 870 anderson 1 96 0 27000K 17472K select 0 0:03 0.00% gaim >> 1037 anderson 1 96 0 7916K 5824K select 0 0:02 0.00% nedit >> 888 anderson 1 96 0 18600K 13752K select 0 0:02 0.00% >> xfce4-session >> 916 anderson 1 96 0 14592K 10344K select 0 0:02 0.00% xfwm4 >> 897 anderson 1 96 0 14404K 8460K select 0 0:02 0.00% >> xfce-mcs-manager >> 918 anderson 1 96 0 13116K 8968K select 0 0:01 0.00% >> xftaskbar4 >> 869 anderson 1 96 0 6820K 5080K select 0 0:01 0.00% xterm >> 25663 anderson 1 96 0 5540K 3904K select 0 0:01 0.00% xterm >> 1192 anderson 1 96 0 6128K 4492K select 0 0:01 0.00% xterm >> 235 root 1 96 0 3056K 1684K select 0 0:00 0.00% >> wpa_supplicant >> 630 root 1 96 0 2620K 1952K select 0 0:00 0.00% httpd >> 68119 anderson 1 96 0 6244K 4548K select 0 0:00 0.00% xterm >> 92204 anderson 1 96 0 5536K 3848K select 0 0:00 0.00% xterm >> 901 anderson 1 97 0 25284K 11308K select 0 0:00 0.00% >> kdeinit >> 683 root 1 96 0 3712K 2404K select 0 0:00 0.00% >> sendmail >> 68120 anderson 1 96 0 3900K 2416K select 0 0:00 0.00% ssh >> 934 anderson 1 96 0 4360K 2880K select 0 0:00 0.00% >> gconfd-2 >> 1193 anderson 1 5 0 3360K 1924K ttyin 0 0:00 0.00% bash >> 32933 root 1 8 0 1624K 1476K wait 0 0:00 0.00% make >> 25666 root 1 5 0 3276K 1824K ttyin 0 0:00 0.00% bash >> 30424 anderson 1 96 0 5536K 4192K select 0 0:00 0.00% xterm >> 889 anderson 1 8 0 3348K 1908K wait 0 0:00 0.00% bash >> 29892 anderson 1 96 0 2600K 1696K CPU0 0 0:00 0.00% top >> 480 root 1 96 0 1412K 924K select 0 0:00 0.00% >> syslogd >> 904 anderson 1 96 0 24004K 10172K select 0 0:00 0.00% >> kdeinit >> 907 anderson 1 96 0 24600K 10772K select 0 0:00 0.00% >> kdeinit >> 92205 anderson 1 5 0 3308K 1876K ttyin 0 0:00 0.00% bash >> 694 root 1 8 0 1428K 1028K nanslp 0 0:00 0.00% cron >> 924 anderson 1 8 0 1768K 1136K wait 0 0:00 0.00% sh >> 785 root 1 8 0 1748K 1256K wait 0 0:00 0.00% login >> 30453 anderson 1 5 0 3308K 1920K ttyin 0 0:00 0.00% bash >> 830 anderson 1 8 0 3320K 1864K wait 0 0:00 0.00% bash >> 1040 anderson 1 8 0 3344K 1908K wait 0 0:00 0.00% bash >> 25664 anderson 1 8 0 3308K 1872K wait 0 0:00 0.00% bash >> 1043 root 1 8 0 3304K 1852K wait 0 0:00 0.00% bash >> 936 anderson 1 8 0 1768K 1136K wait 0 0:00 0.00% sh >> 616 root 1 96 0 1320K 768K select 0 0:00 0.00% usbd >> 25665 anderson 1 8 0 1728K 1244K wait 0 0:00 0.00% su >> 1042 anderson 1 8 0 1728K 1236K wait 0 0:00 0.00% su >> 871 anderson 1 8 0 1764K 1060K wait 0 0:00 0.00% sh >> 32932 root 1 105 0 1376K 784K select 0 0:00 0.00% >> script >> 242 root 1 96 0 1500K 988K select 0 0:00 0.00% >> dhclient >> 841 anderson 1 8 0 1792K 1108K wait 0 0:00 0.00% sh >> 248 _dhcp 1 96 0 1500K 1040K select 0 0:00 0.00% >> dhclient >> 687 smmsp 1 20 0 3592K 2176K pause 0 0:00 0.00% >> sendmail >> 575 root 1 117 0 1384K 880K select 0 0:00 0.00% lpd >> 864 anderson 1 8 0 1756K 1056K wait 0 0:00 0.00% sh >> 954 anderson 1 8 0 1784K 1152K wait 0 0:00 0.00% sh >> 928 anderson 1 8 0 1784K 1152K wait 0 0:00 0.00% sh >> 860 anderson 1 8 0 2152K 1252K wait 0 0:00 0.00% xinit >> 792 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty >> 789 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty >> 787 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty >> 791 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty >> 790 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty >> 786 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty >> 788 root 1 5 0 1384K 852K ttyin 0 0:00 0.00% getty >> 768 root 1 116 0 1504K 1052K select 0 0:00 0.00% inetd >> 33008 root 1 8 0 1760K 1052K wait 0 0:00 0.00% sh >> 840 anderson 1 8 0 3324K 1868K wait 0 0:00 0.00% bash >> 606 nobody 1 112 0 1384K 904K select 0 0:00 0.00% sdpd >> 885 anderson 1 96 0 2284K 1264K select 0 0:00 0.00% >> dbus-launch >> 677 root 1 116 0 3676K 1932K select 0 0:00 0.00% sshd >> 914 anderson 1 96 0 2928K 1340K select 0 0:00 0.00% >> gnome-keyring-daemo >> 555 root 1 4 0 1424K 796K sbwait 0 0:00 0.00% >> hcsecd >> 880 anderson 1 96 0 3384K 1700K select 0 0:00 0.00% >> ssh-agent >> 793 www 1 4 0 2632K 1956K accept 0 0:00 0.00% httpd >> 408 root 1 96 0 516K 300K select 0 0:00 0.00% devd >> 33009 root 1 8 0 1760K 1052K wait 0 0:00 0.00% sh >> 794 www 1 4 0 2632K 1956K accept 0 0:00 0.00% httpd >> 886 anderson 1 97 0 2704K 1020K select 0 0:00 0.00% >> dbus-daemon >> 170 root 1 20 0 1284K 660K pause 0 0:00 0.00% >> adjkerntz >> 742 root 1 111 0 1376K 720K select 0 0:00 0.00% >> moused >> >> >> >> >> >> >> -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 04:22: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 E96D316A401 for ; Fri, 5 May 2006 04:22:46 +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 EACED43D46 for ; Fri, 5 May 2006 04:22:45 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 32648 invoked from network); 5 May 2006 04:22:43 -0000 Received: from maxwell2.pacific.net.sg (203.120.90.192) by smtpgate4.pacific.net.sg with SMTP; 5 May 2006 04:22:43 -0000 Received: from [192.168.0.107] ([210.24.122.33]) by maxwell2.pacific.net.sg with ESMTP id <20060505042242.VOFN28656.maxwell2.pacific.net.sg@[192.168.0.107]>; Fri, 5 May 2006 12:22:42 +0800 Message-ID: <445AD300.1020808@pacific.net.sg> Date: Fri, 05 May 2006 12:22:24 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Thunderbird 1.5.0.2 (X11/20060501) MIME-Version: 1.0 To: Eric Anderson References: <445AB56F.8090907@centtech.com> <445AC174.5050102@pacific.net.sg> <445AC46F.30702@centtech.com> <445AD048.80305@pacific.net.sg> <445AD1AC.1070902@centtech.com> In-Reply-To: <445AD1AC.1070902@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 04:22:47 -0000 Hi, Eric Anderson wrote: > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 11 root 1 171 52 0K 8K CPU1 0 0:00 99.02% > idle: cpu1 > 2653 root 1 128 0 18564K 17560K RUN 0 0:01 34.00% cc1plus could it be that it is just a problem with top itself? It cannot be that CPU1 uses 99% for the idle process and 34% for the compiler. Play with the other sort options. You might find the the idle process for CPU0. Erich From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 04:31:08 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 4279716A402 for ; Fri, 5 May 2006 04:31:08 +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 DBF3243D49 for ; Fri, 5 May 2006 04:31:07 +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 k454V6JG072208; Thu, 4 May 2006 23:31:06 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <445AD50B.2060107@centtech.com> Date: Thu, 04 May 2006 23:31:07 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Erich Dollansky References: <445AB56F.8090907@centtech.com> <445AC174.5050102@pacific.net.sg> <445AC46F.30702@centtech.com> <445AD048.80305@pacific.net.sg> <445AD1AC.1070902@centtech.com> <445AD300.1020808@pacific.net.sg> In-Reply-To: <445AD300.1020808@pacific.net.sg> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1444/Thu May 4 16:21:06 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 04:31:08 -0000 Erich Dollansky wrote: > Hi, > > Eric Anderson wrote: >> >> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU >> COMMAND >> 11 root 1 171 52 0K 8K CPU1 0 0:00 99.02% >> idle: cpu1 >> 2653 root 1 128 0 18564K 17560K RUN 0 0:01 34.00% >> cc1plus > > could it be that it is just a problem with top itself? > > It cannot be that CPU1 uses 99% for the idle process and 34% for the > compiler. > > Play with the other sort options. You might find the the idle process > for CPU0. Is this what you want: $ ps -auxw | grep idle root 11 99.0 0.0 0 8 ?? RL 7:45PM 0:00.00 [idle: cpu1] root 12 0.0 0.0 0 8 ?? RL 7:45PM 51:04.57 [idle: cpu0] I'm sure it could be a top issue, but other tools that don't use top report only 50% total cpu usage.. 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 May 5 04:38: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 02C9416A402 for ; Fri, 5 May 2006 04:38:35 +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 036B543D45 for ; Fri, 5 May 2006 04:38:33 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 12071 invoked from network); 5 May 2006 04:38:32 -0000 Received: from maxwell2.pacific.net.sg (203.120.90.192) by smtpgate4.pacific.net.sg with SMTP; 5 May 2006 04:38:31 -0000 Received: from [192.168.0.107] ([210.24.122.33]) by maxwell2.pacific.net.sg with ESMTP id <20060505043830.VQIM28656.maxwell2.pacific.net.sg@[192.168.0.107]>; Fri, 5 May 2006 12:38:30 +0800 Message-ID: <445AD6B4.7050407@pacific.net.sg> Date: Fri, 05 May 2006 12:38:12 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Thunderbird 1.5.0.2 (X11/20060501) MIME-Version: 1.0 To: Eric Anderson References: <445AB56F.8090907@centtech.com> <445AC174.5050102@pacific.net.sg> <445AC46F.30702@centtech.com> <445AD048.80305@pacific.net.sg> <445AD1AC.1070902@centtech.com> <445AD300.1020808@pacific.net.sg> <445AD50B.2060107@centtech.com> In-Reply-To: <445AD50B.2060107@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 04:38:35 -0000 Hi, Eric Anderson wrote: > Erich Dollansky wrote: >> Hi, >> >> Eric Anderson wrote: >>> >>> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU >>> COMMAND >>> 11 root 1 171 52 0K 8K CPU1 0 0:00 99.02% >>> idle: cpu1 >>> 2653 root 1 128 0 18564K 17560K RUN 0 0:01 34.00% >>> cc1plus >> >> could it be that it is just a problem with top itself? >> >> It cannot be that CPU1 uses 99% for the idle process and 34% for the >> compiler. >> >> Play with the other sort options. You might find the the idle process >> for CPU0. > > Is this what you want: > > $ ps -auxw | grep idle > root 11 99.0 0.0 0 8 ?? RL 7:45PM 0:00.00 [idle: cpu1] > root 12 0.0 0.0 0 8 ?? RL 7:45PM 51:04.57 [idle: cpu0] > something is really wrong here. CPU1 gets 99% of the time but uses then only 0 seconds while CPU0 gets 0% of the time but uses 51 hours? This is, what I get: root 11 98.2 0.0 0 8 ?? RL 21Apr06 19013:02.26 [idle: cpu1] root 12 94.9 0.0 0 8 ?? RL 21Apr06 18456:39.99 [idle: cpu0] This is a dual-Athlon system running 6.1 RC1. Erich From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 04:45: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 BC8BA16A400 for ; Fri, 5 May 2006 04:45:03 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8181243D4C for ; Fri, 5 May 2006 04:44:52 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k454igFS059446; Thu, 4 May 2006 22:44:42 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <445AD83A.7090607@samsco.org> Date: Thu, 04 May 2006 22:44:42 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Erich Dollansky References: <445AB56F.8090907@centtech.com> <445AC174.5050102@pacific.net.sg> <445AC46F.30702@centtech.com> <445AD048.80305@pacific.net.sg> <445AD1AC.1070902@centtech.com> <445AD300.1020808@pacific.net.sg> <445AD50B.2060107@centtech.com> <445AD6B4.7050407@pacific.net.sg> In-Reply-To: <445AD6B4.7050407@pacific.net.sg> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-hackers@freebsd.org Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 04:45:03 -0000 Erich Dollansky wrote: > Hi, > > Eric Anderson wrote: > >> Erich Dollansky wrote: >> >>> Hi, >>> >>> Eric Anderson wrote: >>> >>>> >>>> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU >>>> COMMAND >>>> 11 root 1 171 52 0K 8K CPU1 0 0:00 99.02% >>>> idle: cpu1 >>>> 2653 root 1 128 0 18564K 17560K RUN 0 0:01 34.00% >>>> cc1plus >>> >>> >>> could it be that it is just a problem with top itself? >>> >>> It cannot be that CPU1 uses 99% for the idle process and 34% for the >>> compiler. >>> >>> Play with the other sort options. You might find the the idle process >>> for CPU0. >> >> >> Is this what you want: >> >> $ ps -auxw | grep idle >> root 11 99.0 0.0 0 8 ?? RL 7:45PM 0:00.00 >> [idle: cpu1] >> root 12 0.0 0.0 0 8 ?? RL 7:45PM 51:04.57 >> [idle: cpu0] >> > something is really wrong here. CPU1 gets 99% of the time but uses then > only 0 seconds while CPU0 gets 0% of the time but uses 51 hours? CPU1 is being treated as a hyperthreading core instead of a real core, and is being disabled per our policy on Intel hyperthreading. By 'disabled' I mean that it is started, but it is being excluded from scheduling decisions, and thus is only running its idle proc. It's also handling any interrupts that come to it, such as timer and IPI interrupts, so it's at 99% instead of 100% for the idle proc. There is nothing broken about the number you are seeing, your system is just running under a scheduling policy that it should not be. This should have been fixed a week or so ago by a commit to HEAD, RELENG_6, and RELENG_6_1 by Colin Percival. How old is kernel? Scott From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 04:49:33 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 1244216A400 for ; Fri, 5 May 2006 04:49:33 +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 8AADD43D45 for ; Fri, 5 May 2006 04:49:32 +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 k454nVxe072926; Thu, 4 May 2006 23:49:31 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <445AD95C.7040802@centtech.com> Date: Thu, 04 May 2006 23:49:32 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Scott Long References: <445AB56F.8090907@centtech.com> <445AC174.5050102@pacific.net.sg> <445AC46F.30702@centtech.com> <445AD048.80305@pacific.net.sg> <445AD1AC.1070902@centtech.com> <445AD300.1020808@pacific.net.sg> <445AD50B.2060107@centtech.com> <445AD6B4.7050407@pacific.net.sg> <445AD83A.7090607@samsco.org> In-Reply-To: <445AD83A.7090607@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1444/Thu May 4 16:21:06 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 04:49:33 -0000 Scott Long wrote: > Erich Dollansky wrote: >> Hi, >> >> Eric Anderson wrote: >> >>> Erich Dollansky wrote: >>> >>>> Hi, >>>> >>>> Eric Anderson wrote: >>>> >>>>> >>>>> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU >>>>> COMMAND >>>>> 11 root 1 171 52 0K 8K CPU1 0 0:00 99.02% >>>>> idle: cpu1 >>>>> 2653 root 1 128 0 18564K 17560K RUN 0 0:01 34.00% >>>>> cc1plus >>>> >>>> >>>> could it be that it is just a problem with top itself? >>>> >>>> It cannot be that CPU1 uses 99% for the idle process and 34% for the >>>> compiler. >>>> >>>> Play with the other sort options. You might find the the idle >>>> process for CPU0. >>> >>> >>> Is this what you want: >>> >>> $ ps -auxw | grep idle >>> root 11 99.0 0.0 0 8 ?? RL 7:45PM 0:00.00 >>> [idle: cpu1] >>> root 12 0.0 0.0 0 8 ?? RL 7:45PM 51:04.57 >>> [idle: cpu0] >>> >> something is really wrong here. CPU1 gets 99% of the time but uses >> then only 0 seconds while CPU0 gets 0% of the time but uses 51 hours? > > CPU1 is being treated as a hyperthreading core instead of a real core, > and is being disabled per our policy on Intel hyperthreading. By > 'disabled' I mean that it is started, but it is being excluded from > scheduling decisions, and thus is only running its idle proc. It's > also handling any interrupts that come to it, such as timer and IPI > interrupts, so it's at 99% instead of 100% for the idle proc. There > is nothing broken about the number you are seeing, your system is > just running under a scheduling policy that it should not be. > > This should have been fixed a week or so ago by a commit to HEAD, > RELENG_6, and RELENG_6_1 by Colin Percival. How old is kernel? 6.1-RC FreeBSD 6.1-RC #13: Thu Apr 27 08:33:14 CDT 2006 So I probably just missed it. I'll rebuilt and try it tomorrow morning, and report back. Thanks for all the help and a good description. 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 May 5 07:03: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 90FC316A402 for ; Fri, 5 May 2006 07:03:13 +0000 (UTC) (envelope-from fli+freebsd-hackers@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AF7243D46 for ; Fri, 5 May 2006 07:03:12 +0000 (GMT) (envelope-from fli+freebsd-hackers@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id A24D01A770; Fri, 5 May 2006 09:03:07 +0200 (CEST) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 82920-08; Fri, 5 May 2006 09:03:06 +0200 (CEST) Received: from [10.0.0.50] (sto-nat.se.tangram-group.net [212.37.5.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.h3q.net (Postfix) with ESMTP id CF6381A723; Fri, 5 May 2006 09:03:05 +0200 (CEST) Message-ID: <445AF8AB.9080008@shapeshifter.se> Date: Fri, 05 May 2006 09:03:07 +0200 From: Fredrik Lindberg User-Agent: Thunderbird 1.5.0.2 (X11/20060423) MIME-Version: 1.0 To: Daniel O'Connor References: <00fb01c66fb2$a8e157c0$0501010a@ironman> <445A5F48.60303@spintech.ro> <200605051009.49344.doconnor@gsoft.com.au> In-Reply-To: <200605051009.49344.doconnor@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at h3q.net Cc: freebsd-hackers@freebsd.org, aanton@spintech.ro, Cesar Subject: Re: Fingerprint Authentication 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, 05 May 2006 07:03:13 -0000 Daniel O'Connor wrote: > On Friday 05 May 2006 05:38, Alin-Adrian Anton wrote: >> http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader >> >> SSH can do pam authentication. > > Not sure the driver will work in FreeBSD.. > There is bioapi in ports though. > > Oops. looks like ports wins again.. security/bsp_upektfmess > The driver should work fine locally. But using it remote (via ssh etc) is probably a no-go because verification of the fingerprint records are done by UPEKs driver at the hardware level. The only way as I see it (to even make it possible with UPEKs driver) is to have a reader at both the remote machine and the client machine and then capture a BioAPI record at the client machine and have the server verify it. But that involves transferring the record in a secure way to the server. Fredrik Lindberg From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 11:24: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 0F18116A403 for ; Fri, 5 May 2006 11:24:30 +0000 (UTC) (envelope-from aanton@spintech.ro) Received: from smtpx.spintech.ro (smtpx.spintech.ro [81.180.92.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id C42C243D58 for ; Fri, 5 May 2006 11:24:28 +0000 (GMT) (envelope-from aanton@spintech.ro) Received: from [10.0.0.2] (beastie [10.0.0.2]) by smtpx.spintech.ro (Postfix) with ESMTP id B55BF3A4A8; Fri, 5 May 2006 11:58:28 +0000 (UTC) Message-ID: <445B35EA.5080009@spintech.ro> Date: Fri, 05 May 2006 14:24:26 +0300 From: Alin-Adrian Anton Organization: Spintech Security Systems User-Agent: Mozilla Thunderbird 1.0 (X11/20041229) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <00fb01c66fb2$a8e157c0$0501010a@ironman> <445A5F48.60303@spintech.ro> <200605051009.49344.doconnor@gsoft.com.au> <445AF8AB.9080008@shapeshifter.se> In-Reply-To: <445AF8AB.9080008@shapeshifter.se> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Cesar Subject: Re: Fingerprint Authentication X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: aanton@spintech.ro List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 11:24:30 -0000 Fredrik Lindberg wrote: > > The driver should work fine locally. But using it remote (via ssh etc) > is probably a no-go because verification of the fingerprint records are done by UPEKs driver at the hardware level. > > The only way as I see it (to even make it possible with UPEKs driver) > is to have a reader at both the remote machine and the client machine > and then capture a BioAPI record at the client machine and have the server verify it. But that involves transferring the record in a secure > way to the server. > Or simply have a reader on client side, which if correctly authentificated will issue public-key auth with the server, or sort of.. :) Not really BioAPI auth, but it enables the user to do remote logins by putting the finger on the reader.. -- Alin-Adrian Anton GPG keyID 0x183087BA (B129 E8F4 7B34 15A9 0785 2F7C 5823 ABA0 1830 87BA) gpg --keyserver pgp.mit.edu --recv-keys 0x183087BA "It is dangerous to be right when the government is wrong." - Voltaire From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 12:45: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 F322A16A40F for ; Fri, 5 May 2006 12:45:29 +0000 (UTC) (envelope-from fli+freebsd-hackers@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAE4143D68 for ; Fri, 5 May 2006 12:45:25 +0000 (GMT) (envelope-from fli+freebsd-hackers@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id 4B8241A770; Fri, 5 May 2006 14:45:23 +0200 (CEST) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 97930-01; Fri, 5 May 2006 14:45:22 +0200 (CEST) Received: from [10.0.0.50] (sto-nat.se.tangram-group.net [212.37.5.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.h3q.net (Postfix) with ESMTP id 448911A6B2; Fri, 5 May 2006 14:45:22 +0200 (CEST) Message-ID: <445B48E6.3070000@shapeshifter.se> Date: Fri, 05 May 2006 14:45:26 +0200 From: Fredrik Lindberg User-Agent: Thunderbird 1.5.0.2 (X11/20060423) MIME-Version: 1.0 To: aanton@spintech.ro References: <00fb01c66fb2$a8e157c0$0501010a@ironman> <445A5F48.60303@spintech.ro> <200605051009.49344.doconnor@gsoft.com.au> <445AF8AB.9080008@shapeshifter.se> <445B35EA.5080009@spintech.ro> In-Reply-To: <445B35EA.5080009@spintech.ro> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at h3q.net Cc: freebsd-hackers@freebsd.org, Cesar Subject: Re: Fingerprint Authentication 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, 05 May 2006 12:45:30 -0000 Alin-Adrian Anton wrote: > Fredrik Lindberg wrote: > > > > > The only way as I see it (to even make it possible with UPEKs driver) > > is to have a reader at both the remote machine and the client machine > > and then capture a BioAPI record at the client machine and have the > server verify it. But that involves transferring the record in a secure > > way to the server. > > > > Or simply have a reader on client side, which if correctly > authentificated will issue public-key auth with the server, or sort of.. > :) Not really BioAPI auth, but it enables the user to do remote logins > by putting the finger on the reader.. > But that would sort of defeat the whole purpose of biometric authentication and you could really just use public keys instead which would be a lot faster and easier than scanning your finger at each login. :) Fredrik Lindberg From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 13:03: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 9B8A516A400 for ; Fri, 5 May 2006 13:03:51 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 208DB43D46 for ; Fri, 5 May 2006 13:03:50 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id D457284425; Fri, 5 May 2006 15:03:48 +0200 (CEST) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 90439-01; Fri, 5 May 2006 15:03:42 +0200 (CEST) Received: from [IPv6:::1] (unknown [192.168.2.3]) by people.fsn.hu (Postfix) with ESMTP id A483F8441E; Fri, 5 May 2006 15:03:41 +0200 (CEST) Message-ID: <445B4D2D.8070502@fsn.hu> Date: Fri, 05 May 2006 15:03:41 +0200 From: Attila Nagy User-Agent: Thunderbird 1.5.0.2 (X11/20060502) MIME-Version: 1.0 To: Scott Long References: <445AB56F.8090907@centtech.com> <445AC174.5050102@pacific.net.sg> <445AC46F.30702@centtech.com> <445AD048.80305@pacific.net.sg> <445AD1AC.1070902@centtech.com> <445AD300.1020808@pacific.net.sg> <445AD50B.2060107@centtech.com> <445AD6B4.7050407@pacific.net.sg> <445AD83A.7090607@samsco.org> In-Reply-To: <445AD83A.7090607@samsco.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Cc: freebsd-hackers@freebsd.org Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 13:03:51 -0000 Hello, On 05/05/06 06:44, Scott Long wrote: > CPU1 is being treated as a hyperthreading core instead of a real core, > and is being disabled per our policy on Intel hyperthreading. By > 'disabled' I mean that it is started, but it is being excluded from > scheduling decisions, and thus is only running its idle proc. It's > also handling any interrupts that come to it, such as timer and IPI > interrupts, so it's at 99% instead of 100% for the idle proc. There > is nothing broken about the number you are seeing, your system is > just running under a scheduling policy that it should not be. > > This should have been fixed a week or so ago by a commit to HEAD, > RELENG_6, and RELENG_6_1 by Colin Percival. How old is kernel? Isn't this fixed by jkim's commit? I don't have any Core Duos here, but on a Xeon LV (Sossaman) with CURRENT, everything is OK: http://www.freebsd.org/cgi/query-pr.cgi?pr=96203 BTW, just set machdep.hyperthreading_allowed=1 until the fix arrives. -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/ From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 13:10: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 8DED216A402 for ; Fri, 5 May 2006 13:10:50 +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 2BE6943D46 for ; Fri, 5 May 2006 13:10:49 +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 k45DAmag092548; Fri, 5 May 2006 08:10:48 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <445B4ED9.6020607@centtech.com> Date: Fri, 05 May 2006 08:10:49 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Attila Nagy References: <445AB56F.8090907@centtech.com> <445AC174.5050102@pacific.net.sg> <445AC46F.30702@centtech.com> <445AD048.80305@pacific.net.sg> <445AD1AC.1070902@centtech.com> <445AD300.1020808@pacific.net.sg> <445AD50B.2060107@centtech.com> <445AD6B4.7050407@pacific.net.sg> <445AD83A.7090607@samsco.org> <445B4D2D.8070502@fsn.hu> In-Reply-To: <445B4D2D.8070502@fsn.hu> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1445/Fri May 5 03:30:03 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, Scott Long Subject: Re: Core Duo - only one cpu being used 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, 05 May 2006 13:10:50 -0000 Attila Nagy wrote: > Hello, > > On 05/05/06 06:44, Scott Long wrote: >> CPU1 is being treated as a hyperthreading core instead of a real core, >> and is being disabled per our policy on Intel hyperthreading. By >> 'disabled' I mean that it is started, but it is being excluded from >> scheduling decisions, and thus is only running its idle proc. It's >> also handling any interrupts that come to it, such as timer and IPI >> interrupts, so it's at 99% instead of 100% for the idle proc. There >> is nothing broken about the number you are seeing, your system is >> just running under a scheduling policy that it should not be. >> >> This should have been fixed a week or so ago by a commit to HEAD, >> RELENG_6, and RELENG_6_1 by Colin Percival. How old is kernel? > Isn't this fixed by jkim's commit? > > I don't have any Core Duos here, but on a Xeon LV (Sossaman) with > CURRENT, everything is OK: > http://www.freebsd.org/cgi/query-pr.cgi?pr=96203 > > BTW, just set machdep.hyperthreading_allowed=1 until the fix arrives. > I can confirm now that it is fixed in todays 6-STABLE. Thanks everyone! 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 May 5 13:34: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 9AB4016A400 for ; Fri, 5 May 2006 13:34:07 +0000 (UTC) (envelope-from aanton@spintech.ro) Received: from smtpx.spintech.ro (smtpx.spintech.ro [81.180.92.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E83043D45 for ; Fri, 5 May 2006 13:34:07 +0000 (GMT) (envelope-from aanton@spintech.ro) Received: from [10.0.0.2] (beastie [10.0.0.2]) by smtpx.spintech.ro (Postfix) with ESMTP id 1E4EB3A4D2; Fri, 5 May 2006 14:08:08 +0000 (UTC) Message-ID: <445B544D.5070107@spintech.ro> Date: Fri, 05 May 2006 16:34:05 +0300 From: Alin-Adrian Anton Organization: Spintech Security Systems User-Agent: Mozilla Thunderbird 1.0 (X11/20041229) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Fredrik Lindberg References: <00fb01c66fb2$a8e157c0$0501010a@ironman> <445A5F48.60303@spintech.ro> <200605051009.49344.doconnor@gsoft.com.au> <445AF8AB.9080008@shapeshifter.se> <445B35EA.5080009@spintech.ro> <445B48E6.3070000@shapeshifter.se> In-Reply-To: <445B48E6.3070000@shapeshifter.se> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Cesar Subject: Re: Fingerprint Authentication X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: aanton@spintech.ro List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 13:34:07 -0000 Fredrik Lindberg wrote: > > But that would sort of defeat the whole purpose of biometric > authentication and you could really just use public keys instead > which would be a lot faster and easier than scanning your finger > at each login. :) > Unless you locally encrypt your private key with information gathered by the fingerprint reader, as a "password". One can scan his finger only once, at first login, or when the system boots. Passwords are still considered a bit more safe then a fingerprint reader (as far as I know). -- Alin-Adrian Anton GPG keyID 0x183087BA (B129 E8F4 7B34 15A9 0785 2F7C 5823 ABA0 1830 87BA) gpg --keyserver pgp.mit.edu --recv-keys 0x183087BA "It is dangerous to be right when the government is wrong." - Voltaire From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 13:58:02 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 37D5316A400 for ; Fri, 5 May 2006 13:58:02 +0000 (UTC) (envelope-from fli+freebsd-hackers@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA9C443D46 for ; Fri, 5 May 2006 13:58:01 +0000 (GMT) (envelope-from fli+freebsd-hackers@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id 354A71A770; Fri, 5 May 2006 15:57:59 +0200 (CEST) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 97930-09; Fri, 5 May 2006 15:57:58 +0200 (CEST) Received: from [10.0.0.50] (sto-nat.se.tangram-group.net [212.37.5.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.h3q.net (Postfix) with ESMTP id 25C1F1A6B2; Fri, 5 May 2006 15:57:57 +0200 (CEST) Message-ID: <445B59EE.6040701@shapeshifter.se> Date: Fri, 05 May 2006 15:58:06 +0200 From: Fredrik Lindberg User-Agent: Thunderbird 1.5.0.2 (X11/20060423) MIME-Version: 1.0 To: aanton@spintech.ro References: <00fb01c66fb2$a8e157c0$0501010a@ironman> <445A5F48.60303@spintech.ro> <200605051009.49344.doconnor@gsoft.com.au> <445AF8AB.9080008@shapeshifter.se> <445B35EA.5080009@spintech.ro> <445B48E6.3070000@shapeshifter.se> <445B544D.5070107@spintech.ro> In-Reply-To: <445B544D.5070107@spintech.ro> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at h3q.net Cc: freebsd-hackers@freebsd.org, Cesar Subject: Re: Fingerprint Authentication 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, 05 May 2006 13:58:02 -0000 Alin-Adrian Anton wrote: > Fredrik Lindberg wrote: >> >> But that would sort of defeat the whole purpose of biometric >> authentication and you could really just use public keys instead >> which would be a lot faster and easier than scanning your finger >> at each login. :) >> > > Unless you locally encrypt your private key with information gathered by > the fingerprint reader, as a "password". > That's exactly the problem with, at least, UPEKs driver. If you scan one of your fingers twice you'll get two "different" BioAPI records. That's "different" as in two binary data blobs which aren't equal. To match these records with each other, you hand them over to the driver which, as far as I know, hand them over to the hardware which in turn performs some black magic and then tell you if the records match or not. This is actually the way BSP (Biometric Service Providers..uhh fancy names) modules for BioAPI works. The BSP "captures" a biometric record from somewhere (could be hardware or it could be software), this opaque data is then used to construct a BIR (BioAPI Record) which you store in some database. This process is called "enrollment" in BioAPI-speak. When you want to verify/match a record you let the BSP "capture" a new record (and thus creating a new BIR), you now have two BIRs which aren't bitwise equal and as they are created by a third party module you have no idea of that they contain (except for the BIR header). Then these two BIRs are handed over to the BSP module again for the match process, which will return either a positive or negative result. In UPEKs case I was told by their representative that the matching between two BIRs are done in hardware. Fredrik Lindberg From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 16:32:17 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 91A5E16A400 for ; Fri, 5 May 2006 16:32:17 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id D713543D45 for ; Fri, 5 May 2006 16:32:16 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (hwnsps@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k45GW7fd082625; Fri, 5 May 2006 18:32:12 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k45GW2a5082588; Fri, 5 May 2006 18:32:03 +0200 (CEST) (envelope-from olli) Date: Fri, 5 May 2006 18:32:03 +0200 (CEST) Message-Id: <200605051632.k45GW2a5082588@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, cokane@cokane.org In-Reply-To: <346a80220604202041o7d631f43rbde4c84b5f7b16b4@mail.gmail.com> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 05 May 2006 18:32:13 +0200 (CEST) X-Mailman-Approved-At: Fri, 05 May 2006 16:54:48 +0000 Cc: 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: freebsd-hackers@FreeBSD.ORG, 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, 05 May 2006 16:32:17 -0000 Hi, Sorry for replying to an old message, but nobody has responded to this particular question, so I give it a try ... Coleman Kane wrote: > > 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... You can use the backslash sequence '\c' with echo -e, which has the same effect as the -n option. See sh(1). Another possibility is to use dd(1) to strip off the new- line (dd(1) lives in /bin, so it's available during boot). A shell function like this does it: echo-en() { x="$*" echo -e "$x" | dd bs=$((${#x}-1)) count=1 2>/dev/null } Although it's a bit less efficient because dd(1) is an external binary, it's more flexible since it can be used for all kinds of cutting and trimming (note that cut(1) resides in /usr/bin). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "When your hammer is C++, everything begins to look like a thumb." -- Steve Haflich, in comp.lang.c++ From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 17:07: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 E2E6016A50D for ; Fri, 5 May 2006 17:07:42 +0000 (UTC) (envelope-from bharmaji@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7035643D45 for ; Fri, 5 May 2006 17:07:42 +0000 (GMT) (envelope-from bharmaji@gmail.com) Received: by nz-out-0102.google.com with SMTP id l1so698170nzf for ; Fri, 05 May 2006 10:07:41 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=l1Ls5+aFm9k8z4Jp4gxZIUUkDodzuTUkdDvSWe83mZYN/0JD7VjwNvImtBdkG7kFoKQ4/sSB/EeFixd3dpJSXw4OrwNr8lT1GC8yqjM92FG0F6ghUqiekQgwQs+DtRL+PMcArOW/6WY5fNTQmet/eUW7DCJjhXMwarbuXwwmJxU= Received: by 10.65.110.20 with SMTP id n20mr590082qbm; Fri, 05 May 2006 10:07:41 -0700 (PDT) Received: by 10.65.133.13 with HTTP; Fri, 5 May 2006 10:07:41 -0700 (PDT) Message-ID: <67beabb0605051007q601678e6w49cf15d17604d82b@mail.gmail.com> Date: Fri, 5 May 2006 10:07:41 -0700 From: "Bharma Ji" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: how to find the physical memory allocated to the kernel 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, 05 May 2006 17:07:43 -0000 Hi Is there any way to determine the physical memory(not the virtual address space) being allocated to the kernel at any instant? The overall problem is that once I allocate say 512 MB to the kernel (virutal address space) through the config file at compile time, I want to figure out how much of that space is actually being used when the machine is under load. Thanks for any answers From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 18:10: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 088F516A416 for ; Fri, 5 May 2006 18:10:03 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F1C543D64 for ; Fri, 5 May 2006 18:10:02 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (kbczgz@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k45I9uun086717 for ; Fri, 5 May 2006 20:10:01 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k45I9uHQ086716; Fri, 5 May 2006 20:09:56 +0200 (CEST) (envelope-from olli) Date: Fri, 5 May 2006 20:09:56 +0200 (CEST) Message-Id: <200605051809.k45I9uHQ086716@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG In-Reply-To: <67beabb0605051007q601678e6w49cf15d17604d82b@mail.gmail.com> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 05 May 2006 20:10:01 +0200 (CEST) X-Mailman-Approved-At: Fri, 05 May 2006 18:10:42 +0000 Cc: Subject: Re: how to find the physical memory allocated to the kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 18:10:04 -0000 Bharma Ji wrote: > Is there any way to determine the physical memory(not the virtual address > space) being allocated to the kernel at any instant? The overall problem is > that once I allocate say 512 MB to the kernel (virutal address space) > through the config file at compile time, I want to figure out how much of > that space is actually being used when the machine is under load. > Thanks for any answers I'm not sure, but maybe you're looking for the difference between kvm_size and kvm_free? $ sysctl vm.kvm* vm.kvm_size: 1065353216 vm.kvm_free: 809500672 So, in this case the kernel is actually using 244 MB of its address space. If you're interested in physical RAM, maybe you should look at the difference between physmem and usermem: $ sysctl hw.*mem hw.physmem: 164016128 hw.usermem: 128507904 In this case the kernel is using about 34 MB of RAM. (Both output above is from the same machine.) Best regards Oliver PS: In case you're wondering, I'm using a sysctl wrapper script that allows wildcards: http://www.secnetix.de/~olli/scripts/sysctl.wrapper -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "C++ is to C as Lung Cancer is to Lung." -- Thomas Funke From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 18:15:45 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 D6E1B16A417 for ; Fri, 5 May 2006 18:15:45 +0000 (UTC) (envelope-from aanton@spintech.ro) Received: from smtpx.spintech.ro (smtpx.spintech.ro [81.180.92.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27D8943D53 for ; Fri, 5 May 2006 18:15:45 +0000 (GMT) (envelope-from aanton@spintech.ro) Received: from [10.0.0.2] (beastie [10.0.0.2]) by smtpx.spintech.ro (Postfix) with ESMTP id 612DF3A498; Fri, 5 May 2006 18:49:48 +0000 (UTC) Message-ID: <445B9650.50009@spintech.ro> Date: Fri, 05 May 2006 21:15:44 +0300 From: Alin-Adrian Anton Organization: Spintech Security Systems User-Agent: Mozilla Thunderbird 1.0 (X11/20041229) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Fredrik Lindberg References: <00fb01c66fb2$a8e157c0$0501010a@ironman> <445A5F48.60303@spintech.ro> <200605051009.49344.doconnor@gsoft.com.au> <445AF8AB.9080008@shapeshifter.se> <445B35EA.5080009@spintech.ro> <445B48E6.3070000@shapeshifter.se> <445B544D.5070107@spintech.ro> <445B59EE.6040701@shapeshifter.se> In-Reply-To: <445B59EE.6040701@shapeshifter.se> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Cesar Subject: Re: Fingerprint Authentication X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: aanton@spintech.ro List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 18:15:47 -0000 Fredrik Lindberg wrote: > Alin-Adrian Anton wrote: > >> Fredrik Lindberg wrote: >> >>> >>> But that would sort of defeat the whole purpose of biometric >>> authentication and you could really just use public keys instead >>> which would be a lot faster and easier than scanning your finger >>> at each login. :) >>> >> >> Unless you locally encrypt your private key with information gathered >> by the fingerprint reader, as a "password". >> > > That's exactly the problem with, at least, UPEKs driver. If you scan > one of your fingers twice you'll get two "different" BioAPI records. > That's "different" as in two binary data blobs which aren't equal. > To match these records with each other, you hand them over to the > driver which, as far as I know, hand them over to the hardware > which in turn performs some black magic and then tell you if > the records match or not. > > This is actually the way BSP (Biometric Service Providers..uhh fancy > names) modules for BioAPI works. > The BSP "captures" a biometric record from somewhere (could be > hardware or it could be software), this opaque data is then used to > construct a BIR (BioAPI Record) which you store in some database. > This process is called "enrollment" in BioAPI-speak. > > When you want to verify/match a record you let the BSP > "capture" a new record (and thus creating a new BIR), you now have > two BIRs which aren't bitwise equal and as they are created by a > third party module you have no idea of that they contain (except for > the BIR header). Then these two BIRs are handed over to the BSP module > again for the match process, which will return either a positive or > negative result. > In UPEKs case I was told by their representative that the matching > between two BIRs are done in hardware. > In that case, it means the "matching" is a proabilistic distance-computing algorithm. This sux, for any sort of real remote logins. -- Alin-Adrian Anton GPG keyID 0x183087BA (B129 E8F4 7B34 15A9 0785 2F7C 5823 ABA0 1830 87BA) gpg --keyserver pgp.mit.edu --recv-keys 0x183087BA "It is dangerous to be right when the government is wrong." - Voltaire From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 19:13: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 1D80A16A408 for ; Fri, 5 May 2006 19:13:19 +0000 (UTC) (envelope-from fli+freebsd-hackers@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B84243D45 for ; Fri, 5 May 2006 19:13:12 +0000 (GMT) (envelope-from fli+freebsd-hackers@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id 4F9B11A770; Fri, 5 May 2006 21:13:10 +0200 (CEST) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00634-07; Fri, 5 May 2006 21:13:09 +0200 (CEST) Received: from [192.168.0.81] (81-234-243-91-o926.tbon.telia.com [81.234.243.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.h3q.net (Postfix) with ESMTP id E9E7D1A6B2; Fri, 5 May 2006 21:13:08 +0200 (CEST) Message-ID: <445BA3CB.7000204@shapeshifter.se> Date: Fri, 05 May 2006 21:13:15 +0200 From: Fredrik Lindberg User-Agent: Thunderbird 1.5.0.2 (X11/20060423) MIME-Version: 1.0 To: aanton@spintech.ro References: <00fb01c66fb2$a8e157c0$0501010a@ironman> <445A5F48.60303@spintech.ro> <200605051009.49344.doconnor@gsoft.com.au> <445AF8AB.9080008@shapeshifter.se> <445B35EA.5080009@spintech.ro> <445B48E6.3070000@shapeshifter.se> <445B544D.5070107@spintech.ro> <445B59EE.6040701@shapeshifter.se> <445B9650.50009@spintech.ro> In-Reply-To: <445B9650.50009@spintech.ro> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at h3q.net Cc: freebsd-hackers@freebsd.org, Cesar Subject: Re: Fingerprint Authentication 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, 05 May 2006 19:13:19 -0000 Alin-Adrian Anton wrote: > > In that case, it means the "matching" is a proabilistic > distance-computing algorithm. This sux, for any sort of real remote logins. > > Yes. That's probably an accurate description. I'm by no means an expert in the biometric field, far from it. But in my most humble option, I think it would be *very* difficult to obtain an identical sample every time. When it comes to fingerprints the environment probably plays a big role in the sample, for example light conditions, skin moisture, dust on the sensor etc. Maybe there are other people on this list with better insight in this field? Fredrik Lindberg From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 19: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 08AE616A405 for ; Fri, 5 May 2006 19:26:09 +0000 (UTC) (envelope-from ahebert@pubnix.net) Received: from mail.pubnix.net (Mail.pubnix.net [192.172.250.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 560FC43D55 for ; Fri, 5 May 2006 19:26:08 +0000 (GMT) (envelope-from ahebert@pubnix.net) Received: from [10.0.1.2] (aal.pubnix.net [64.235.216.13]) (authenticated bits=0) by mail.pubnix.net (8.13.6/8.13.6) with ESMTP id k45JQ58B091241; Fri, 5 May 2006 15:26:05 -0400 (EDT) (envelope-from ahebert@pubnix.net) Message-ID: <445BA6CD.4090304@pubnix.net> Date: Fri, 05 May 2006 15:26:05 -0400 From: Alain Hebert Organization: PubNIX, Inc. User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060130 X-Accept-Language: en-us, en MIME-Version: 1.0 References: <00fb01c66fb2$a8e157c0$0501010a@ironman> <445A5F48.60303@spintech.ro> <200605051009.49344.doconnor@gsoft.com.au> <445AF8AB.9080008@shapeshifter.se> <445B35EA.5080009@spintech.ro> <445B48E6.3070000@shapeshifter.se> <445B544D.5070107@spintech.ro> <445B59EE.6040701@shapeshifter.se> <445B9650.50009@spintech.ro> <445BA3CB.7000204@shapeshifter.se> In-Reply-To: <445BA3CB.7000204@shapeshifter.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Cesar Subject: Re: Fingerprint Authentication X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ahebert@pubnix.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 May 2006 19:26:09 -0000 In most implementation I saw it was coupled with a rfid card (short distance < 1inch (2.5cm)) And for usage at entrance of datacenter -> a network of camera. Its not spy proof... but good enought for your average lamer. Fredrik Lindberg wrote: > Alin-Adrian Anton wrote: > >> >> In that case, it means the "matching" is a proabilistic >> distance-computing algorithm. This sux, for any sort of real remote >> logins. >> >> > > Yes. That's probably an accurate description. > > I'm by no means an expert in the biometric field, far from it. > But in my most humble option, I think it would be *very* difficult > to obtain an identical sample every time. > When it comes to fingerprints the environment probably plays a big role > in the sample, for example light conditions, skin moisture, dust on the > sensor etc. > > Maybe there are other people on this list with better insight in this > field? > > Fredrik Lindberg > _______________________________________________ > 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" > -- Alain Hebert ahebert@pubnix.net PubNIX Inc. P.O. Box 175 Beaconsfield, Quebec H9W 5T7 tel 514-990-5911 http://www.pubnix.net fax 514-990-9443 From owner-freebsd-hackers@FreeBSD.ORG Fri May 5 23:57: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 9D02316A40E for ; Fri, 5 May 2006 23:57:43 +0000 (UTC) (envelope-from cokane@ramen.cokane.org) Received: from smtp2.fuse.net (mail-out2.fuse.net [216.68.8.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB80B43D6B for ; Fri, 5 May 2006 23:57:37 +0000 (GMT) (envelope-from cokane@ramen.cokane.org) Received: from gx4.fuse.net ([72.49.162.239]) by smtp2.fuse.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20060505235737.KMSZ2107.smtp2.fuse.net@gx4.fuse.net> for ; Fri, 5 May 2006 19:57:37 -0400 Received: from ramen.cokane.org ([72.49.162.239]) by gx4.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with SMTP id <20060505235736.PAIB14894.gx4.fuse.net@ramen.cokane.org> for ; Fri, 5 May 2006 19:57:36 -0400 Received: (qmail 85028 invoked by uid 1001); 6 May 2006 07:58:48 -0000 Date: Sat, 6 May 2006 07:58:48 +0000 From: Coleman Kane To: hackers@freebsd.org Message-ID: <20060506075848.GA85008@ramen.coleyandcheryl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Cc: 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, 05 May 2006 23:57:43 -0000 Hey all, My webserver went down earlier this week, and I have moved my mail. I am in the arduous process of getting a new replacement. I apologize for the delay however, on the rc.subr colorization project, and hope to have the newest updates available again soon. -- Coleman Kane From owner-freebsd-hackers@FreeBSD.ORG Sat May 6 07:46: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 3A78316A40B for ; Sat, 6 May 2006 07:46:18 +0000 (UTC) (envelope-from avalonwallace@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9004343D75 for ; Sat, 6 May 2006 07:46:07 +0000 (GMT) (envelope-from avalonwallace@gmail.com) Received: by py-out-1112.google.com with SMTP id e30so972690pya for ; Sat, 06 May 2006 00:46:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=CEfvIv+/bCD0wYg4Upu3o8WfW3bwseU7f0+4EtK6XObjBpq3kjISV1GoxSgGQbRk4qtuHxWh8YOc9lC1UAEd7Ht5kWEKB+K6cYi2hXRTu3V2pJjGc6Y1FCHq4Q0FSsD2ePwH5/YG/dA0mKu4JxXiQs23d5lNTT22q0A/LVlcgkg= Received: by 10.35.88.17 with SMTP id q17mr193532pyl; Sat, 06 May 2006 00:46:06 -0700 (PDT) Received: by 10.35.105.6 with HTTP; Sat, 6 May 2006 00:46:06 -0700 (PDT) Message-ID: <3a60de0b0605060046l134240det7a900d556a74527f@mail.gmail.com> Date: Sat, 6 May 2006 15:46:06 +0800 From: "Wallace William" To: freebsd-hackers@freebsd.org, jhb@freebsd.org, imp@bsdimp.com MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: misc questions about the device&driver arch 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, 06 May 2006 07:46:18 -0000 I have seen this in the freebsd 5 road map,have the hotplug of pci already merged into the RELENG_5 branch? PCI resource allocation: PC2003 compliance requires that x86 systems no longer configure PCI devices from the system BIOS, leaving this task solely to the OS. FreeBSD must gain the ability to manage and allocate PCI memory resources on its own. Implementing this should take into account cardbus, PCI-HotPlug, and laptop dock station requirements. This feature will become increasingly critical through the lifetime of RELENG_5, and therefore is a requirement for the RELENG_5 branch. On Thursday 10 November 2005 05:48 am, kylin wrote: > Sir ,i am still puzzled by the windows and freebsd arch similar. > 1 > the window TPS say that windwo allocate the resource window in default > size of 1M or 2M,so there may be hole ,does that happen in freebsd 5 > or 6? No. > 2 > in my view i believe that freebsd us the "just enough "tactics,so > the nexus level of resource view is =3D=3D=3Dcontinuous=3D=3D=3D=3Dwith N= O hole in > a boot up system, IF hot remove do not happen .am i right? Sorta. We actually will use whatever the BIOS uses by default. We only try to alloc resources if the BIOS doesn't, and I'm not sure how we handle a bridge running out of resources. I think we might just fail the allocation. From owner-freebsd-hackers@FreeBSD.ORG Sat May 6 11:21: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 47A0F16A402 for ; Sat, 6 May 2006 11:21:37 +0000 (UTC) (envelope-from avalonwallace@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1878343D46 for ; Sat, 6 May 2006 11:21:36 +0000 (GMT) (envelope-from avalonwallace@gmail.com) Received: by py-out-1112.google.com with SMTP id e30so993925pya for ; Sat, 06 May 2006 04:21:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=j7KbTruVa18FYHkMfCFfb8gr2PbvJ5IyReRQc72AACLdSkTIhOucc6NUv9T7jm8mkn3i2kSeNmbN2kMkomBYedfJXu8Pi2He5GusilpmtnSviQ529WEWn+EVwtiiFq/X6Q2WnzXeefL27kFsGy7MxFG4tv8xY9rN4ec9lndDTAI= Received: by 10.35.36.13 with SMTP id o13mr92115pyj; Sat, 06 May 2006 04:21:35 -0700 (PDT) Received: by 10.35.105.6 with HTTP; Sat, 6 May 2006 04:21:35 -0700 (PDT) Message-ID: <3a60de0b0605060421l708d8c06y29006c2c3cd75519@mail.gmail.com> Date: Sat, 6 May 2006 19:21:35 +0800 From: "Wallace William" To: freebsd-arch@freebsd.org, freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: fakedevice hotplug Demo with sourcecode 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, 06 May 2006 11:21:37 -0000 hello ,everyone . i have write a demo module to demostrate the hotplug of a pci device under freeBSD 5.3 . when kldload the module ,the fakedevice will be "plug "into the pci architechure,when kldunload ,the device will be removed= . pciconf -l ,and devinfo -v will be the tool to show this change : a new device called wallace is added ,this device comes from the info in LINE97 o= f the fakeBSC.c: *dinfo=3D* ((struct pci_devinfo *) device_get_ivars(devlist[6]) ); maybe u need to change the '6' according to ur need . there r 4 file in this package :pci_hotplug_core.c fakeBSD.c pci_hotplug.h and the Makefile . way to RUN: 1 unzip the package 2 make 3 kldload ./fakeBSD.ko 4 pciconf -l ,and devinfo -v to see the change 5 kldunload fakeBSD.ko welcome for ur feedback,next i will do my best to write the driver for rea= l pci device hotplug, as what cardbus has done ////////////////pci_hotplug_core.c////////////////////////////////// /////////////from PCIexample//////////////// #include /* defines used in kernel.h */ #include #include #include #include /* types used in module initialization */ #include /* cdevsw struct */ #include /* uio struct */ #include #include /* structs, prototypes for pci bus stuff */ #include #include #include #include /* For get_pci macros! */ #include //////////////////////////////////// #include #include "pci_hotplug.h" //WB// #define MY_NAME "pci_hotplug" //simplified//WB// #define dbg(fmt, arg...) do { if (debug) printf( fmt , ## arg); } while (0) #define err(format, arg...) printf( format, MY_NAME , ## arg) #define info(format, arg...) printf(format, MY_NAME , ## arg) #define warn(format, arg...) printf(format , MY_NAME, ## arg) /* local variables */ static int debug; ////////////////////////////////////////////////////////////////// static LIST_HEAD(pci_hotplug_slot_list); /* these strings match up with the values in pci_bus_speed */ static char *pci_bus_speed_strings[] =3D { "33 MHz PCI", /* 0x00 */ "66 MHz PCI", /* 0x01 */ "66 MHz PCIX", /* 0x02 */ "100 MHz PCIX", /* 0x03 */ "133 MHz PCIX", /* 0x04 */ NULL, /* 0x05 */ NULL, /* 0x06 */ NULL, /* 0x07 */ NULL, /* 0x08 */ "66 MHz PCIX 266", /* 0x09 */ "100 MHz PCIX 266", /* 0x0a */ "133 MHz PCIX 266", /* 0x0b */ NULL, /* 0x0c */ NULL, /* 0x0d */ NULL, /* 0x0e */ NULL, /* 0x0f */ NULL, /* 0x10 */ "66 MHz PCIX 533", /* 0x11 */ "100 MHz PCIX 533", /* 0x12 */ "133 MHz PCIX 533", /* 0x13 */ "25 GBps PCI-E", /* 0x14 */ }; ///////////////////fakeBSD.c ///////////////////////////////////////////////// ////////change of the header///////////// /////////////from PCIexample//////////////// #include /* defines used in kernel.h */ #include #include #include #include /* types used in module initialization */ #include /* cdevsw struct */ #include /* uio struct */ #include #include /* structs, prototypes for pci bus stuff */ //for TAILQ_FOREACH //#include // #include //1129 #include #include #include #include //1129 sizeof #include /* For get_pci macros! */ #include #include //1129 //////////////////////////////////// #include //for list_head //#include "pci_hotplug.h" put the unrealated functions out //#include "../pci.h" //this is created on compiling.so leave it to makefile //#include "pcib_if.h" //#include "pci_if.h" /* //COMMENT //devinfo struct for devinfo //addtodevice_list for pciconf COPY the NIC device content to the wallace0 fake device */ #define MY_NAME "fakephp" #define dbg(fmt, arg...) do { if (debug) printf( fmt , ## arg); } while (0) #define err(format, arg...) printf( format, MY_NAME , ## arg) #define info(format, arg...) printf(format, MY_NAME , ## arg) #define DRIVER_AUTHOR "Wallace " #define DRIVER_DESC "Fake PCI Hot Plug Controller Driver" /* * This function is called by the kld[un]load(2) system calls to * determine what actions to take when a module is loaded or unloaded. */ /* vars */ static struct pci_devinfo *dinfo; static device_t bus; //refer to pci bus size_t dinfo_size; static int fake_loader(struct module *m, int what, void *arg) { int erro=3D0; device_t *devlist; int count=3D0; int numdevs; devclass_t class1; char * Dtarget=3D"pci",Dname=3D"wallace"; struct devlist *devlist_head; devlist_head =3D &pci_devq; switch (what) { case MOD_LOAD: /* kldload */ printf("Module loaded.\n,with bootverbose=3D%i",bootverbose); //find pci devclass and device if ((class1 =3D devclass_find(Dtarget)) =3D=3D NULL) { printf("unable to get the class"); return ENXIO; } printf("\n//////////////my name is %s////////////\n",devclass_get_name(class1)); // show the nameof the device,or store them into another TAILQ printf("maxunit under class pci is%i\n",devclass_get_maxunit(class1)); //WB does unit =3D=3D count if((bus =3D devclass_get_device(class1,count))!=3DNULL)//WB why not use t= he loop over count? { printf("my device name is %s,my unit is %i, DESC: %s,with number:%i\n", device_get_name(bus),device_get_unit(bus),device_get_desc(bus),pcib_get_= bus(bus)); } //else? return (NULL) dinfo_size=3Dsizeof(struct pci_devinfo); dinfo=3DNULL; //initialized dinfo=3D malloc(dinfo_size, M_DEVBUF, M_WAITOK | M_ZERO); if (dinfo =3D=3D NULL) return (NULL); if (device_get_children(bus, &devlist, &numdevs)=3D=3D0) //get ivar from de0,thus 6 of devlist ,hardcoded ,this need specific platform characteristic , waiting for modification *dinfo=3D* ((struct pci_devinfo *) device_get_ivars(devlist[6]) ); if ((dinfo->cfg.dev =3D device_add_child(bus, "wallace", -1)) =3D= =3D NULL) {//change the name device_printf(device_get_parent(bus), "couldn't attach pci bus\n"); } device_sysctl_init(dinfo->cfg.dev); strncpy ((dinfo->conf.pd_name),device_get_name(dinfo->cfg.dev ),8);//sizeof(device_get_name(dinfo->cfg.dev))); STAILQ_INSERT_TAIL(devlist_head, dinfo, pci_links); pci_numdevs++; pci_generation++; device_set_ivars(dinfo->cfg.dev, dinfo); //show result if (device_get_children(bus, &devlist, &numdevs)=3D=3D0) while (numdevs--){ printf("%i",numdevs); device_print_prettyname(devlist[numdevs]); if (device_get_devclass(devlist[numdevs])!=3DNULL ) printf("devclass=3D%s\n",devclass_get_name(device_get_devclass(devlist[numd= evs]) )); } break; case MOD_UNLOAD: printf("Module unloaded.\n"); //still dinfo point to the fake device i point to . it is static !!!:) if (dinfo->cfg.dev !=3D NULL) { printf("dinfo->cfg.dev exist,deleting it.\n"); device_delete_child(device_get_parent(dinfo->cfg.dev), dinfo->cfg.dev); printf("dinfo->cfg.dev exist,deleted .\n"); }else printf("dinfo->cfg.dev=3DNULL\n"); if (device_get_children(bus, &devlist, &numdevs)=3D=3D0) //demostrating the result while (numdevs--){ printf("%i",numdevs); device_print_prettyname(devlist[numdevs]); if (device_get_devclass(devlist[numdevs])!=3DNULL ) printf("devclass=3D%s\n",devclass_get_name(device_get_devclass(devlist[numd= evs]) )); } printf("freeing(dinfo,M_DEVBUF)\n"); //1 device_sysctl_fini(dinfo->cfg.dev);//WB finish sysctl structure devlist_head =3D &pci_devq; STAILQ_REMOVE(devlist_head, dinfo, pci_devinfo, pci_links); free(dinfo, M_DEVBUF); /* increment the generation count */ //WB inrease or decreas? pci_generation++; /* we're losing one device */ pci_numdevs--; dinfo=3DNULL; //2 printf("freed dinfo,\n"); //WB ,n->,/n //erro=3D0; break; default: printf("Module default.\n"); erro =3D EINVAL; break; } return(erro); } //DEV_MODULE(echo,echo_loader,NULL); //#define DEV_MODULE(name, evh, arg) static moduledata_t fake_mod =3D { "fakeBSD", fake_loader, NULL }; DECLARE_MODULE(fake, fake_mod, SI_SUB_DRIVERS, SI_ORDER_MIDDLE); //////////////////////pci_hotplug.h /////////////////////// #include //WB// #ifndef _PCI_HOTPLUG_H #define _PCI_HOTPLUG_H /* These values come from the PCI Hotplug Spec */ enum pci_bus_speed { PCI_SPEED_33MHz =3D 0x00, PCI_SPEED_66MHz =3D 0x01, PCI_SPEED_66MHz_PCIX =3D 0x02, PCI_SPEED_100MHz_PCIX =3D 0x03, PCI_SPEED_133MHz_PCIX =3D 0x04, PCI_SPEED_66MHz_PCIX_ECC =3D 0x05, PCI_SPEED_100MHz_PCIX_ECC =3D 0x06, PCI_SPEED_133MHz_PCIX_ECC =3D 0x07, PCI_SPEED_66MHz_PCIX_266 =3D 0x09, PCI_SPEED_100MHz_PCIX_266 =3D 0x0a, PCI_SPEED_133MHz_PCIX_266 =3D 0x0b, PCI_SPEED_66MHz_PCIX_533 =3D 0x11, PCI_SPEED_100MHz_PCIX_533 =3D 0x12, PCI_SPEED_133MHz_PCIX_533 =3D 0x13, PCI_SPEED_UNKNOWN =3D 0xff, }; /* These values come from the PCI Express Spec */ enum pcie_link_width { PCIE_LNK_WIDTH_RESRV =3D 0x00, PCIE_LNK_X1 =3D 0x01, PCIE_LNK_X2 =3D 0x02, PCIE_LNK_X4 =3D 0x04, PCIE_LNK_X8 =3D 0x08, PCIE_LNK_X12 =3D 0x0C, PCIE_LNK_X16 =3D 0x10, PCIE_LNK_X32 =3D 0x20, PCIE_LNK_WIDTH_UNKNOWN =3D 0xFF, }; enum pcie_link_speed { PCIE_2PT5GB =3D 0x14, PCIE_LNK_SPEED_UNKNOWN =3D 0xFF, }; struct hotplug_slot; /*//WB// struct hotplug_slot_attribute { struct attribute attr; ssize_t (*show)(struct hotplug_slot *, char *); ssize_t (*store)(struct hotplug_slot *, const char *, size_t); }; //WB// #define to_hotplug_attr(n) container_of(n, struct hotplug_slot_attribute, attr); * struct hotplug_slot_ops -the callbacks that the hotplug pci core can use * @owner: The module owner of this structure * @enable_slot: Called when the user wants to enable a specific pci slot * @disable_slot: Called when the user wants to disable a specific pci slot * @set_attention_status: Called to set the specific slot's attention LED t= o * the specified value * @hardware_test: Called to run a specified hardware test on the specified * slot. * @get_power_status: Called to get the current power status of a slot. * If this field is NULL, the value passed in the struct hotplug_slot_info * will be used when this value is requested by a user. * @get_attention_status: Called to get the current attention status of a slot. * If this field is NULL, the value passed in the struct hotplug_slot_info * will be used when this value is requested by a user. * @get_latch_status: Called to get the current latch status of a slot. * If this field is NULL, the value passed in the struct hotplug_slot_info * will be used when this value is requested by a user. * @get_adapter_status: Called to get see if an adapter is present in the slot or not. * If this field is NULL, the value passed in the struct hotplug_slot_info * will be used when this value is requested by a user. * @get_address: Called to get pci address of a slot. * If this field is NULL, the value passed in the struct hotplug_slot_info * will be used when this value is requested by a user. * @get_max_bus_speed: Called to get the max bus speed for a slot. * If this field is NULL, the value passed in the struct hotplug_slot_info * will be used when this value is requested by a user. * @get_cur_bus_speed: Called to get the current bus speed for a slot. * If this field is NULL, the value passed in the struct hotplug_slot_info * will be used when this value is requested by a user. * * The table of function pointers that is passed to the hotplug pci core by a * hotplug pci driver. These functions are called by the hotplug pci core when * the user wants to do something to a specific slot (query it for information, * set an LED, enable / disable power, etc.) */ //the freebsd WAY of function call back typedef int enable_slot_t (struct hotplug_slot *slot); typedef int disable_slot_t (struct hotplug_slot *slot); typedef int set_attention_status_t (struct hotplug_slot *slot, u_int8_t value); typedef int hardware_test_t (struct hotplug_slot *slot, u_int32_t value); typedef int get_power_status_t (struct hotplug_slot *slot, u_int8_t *value); typedef int get_attention_status_t (struct hotplug_slot *slot, u_int8_t *value); typedef int get_latch_status_t (struct hotplug_slot *slot, u_int8_t *value); typedef int get_adapter_status_t (struct hotplug_slot *slot, u_int8_t *value); typedef int get_address_t (struct hotplug_slot *slot, u_int32_t *value); typedef int get_max_bus_speed_t (struct hotplug_slot *slot, enum pci_bus_speed *value); typedef int get_cur_bus_speed_t (struct hotplug_slot *slot, enum pci_bus_speed *value); struct hotplug_slot_ops { //struct module *owner; enable_slot_t * enable_slot; disable_slot_t *disable_slot; set_attention_status_t *set_attention_status; hardware_test_t *hardware_test; get_power_status_t *get_power_status; get_attention_status_t *get_attention_status; get_latch_status_t *get_latch_status; get_adapter_status_t *get_adapter_status; get_address_t *get_address; get_max_bus_speed_t *get_max_bus_speed; get_cur_bus_speed_t *get_cur_bus_speed; }; /** * struct hotplug_slot_info - used to notify the hotplug pci core of the state of the slot * @power: if power is enabled or not (1/0) * @attention_status: if the attention light is enabled or not (1/0) * @latch_status: if the latch (if any) is open or closed (1/0) * @adapter_present: if there is a pci board present in the slot or not (1/0) * @address: (domain << 16 | bus << 8 | dev) * * Used to notify the hotplug pci core of the status of a specific slot. */ struct hotplug_slot_info { u_int8_t power_status; u_int8_t attention_status; u_int8_t latch_status; u_int8_t adapter_status; u_int32_t address; enum pci_bus_speed max_bus_speed; enum pci_bus_speed cur_bus_speed; }; /** * struct hotplug_slot - used to register a physical slot with the hotplug pci core * @name: the name of the slot being registered. This string must * be unique amoung slots registered on this system. * @ops: pointer to the &struct hotplug_slot_ops to be used for this slot * @info: pointer to the &struct hotplug_slot_info for the inital values fo= r * this slot. * @private: used by the hotplug pci controller driver to store whatever it * needs. */ typedef void release_t (struct hotplug_slot *slot); struct hotplug_slot { char *name; int unit; struct hotplug_slot_ops *ops; struct hotplug_slot_info *info; release_t * release; void *private; /* Variables below this are for use only by the hotplug pci core. for example :pci_hotplug_slot_list */ struct list_head slot_list; //WB//struct kobject kobj; }; //WB//#define to_hotplug_slot(n) container_of(n, struct hotplug_slot, kobj) #define LIST_HEAD_INIT(name) { &(name), &(name) } #define LIST_HEAD(name) \ struct list_head name =3D LIST_HEAD_INIT(name) /* list_entry - get the struct for this entry * @ptr: the &struct list_head pointer. * @type: the type of the struct this is embedded in. * @member: the name of the list_struct within the struct. entry2 inorder to differ from the vm one */ #define list_entry2(ptr, type, member) \ ((type *)((char *)(ptr)-(unsigned long)(&((type *)0)->member))) /** * list_for_each_safe - iterate over a list safe against removal of list entry * @pos: the &struct list_head to use as a loop counter. * @n: another &struct list_head to use as temporary storage * @head: the head for your list. */ #define list_for_each_safe2(pos, n, head) \ for (pos =3D (head)->next, n =3D pos->next; pos !=3D (head); \ pos =3D n, n =3D pos->next) extern int pci_hp_register (struct hotplug_slot *slot); extern int pci_hp_deregister (struct hotplug_slot *slot); extern int pci_hp_change_slot_info (struct hotplug_slot *slot, struct hotplug_slot_info *info); //WB//extern struct subsystem pci_hotplug_slots_subsys; #endif ///////////////////Makefile///////////////////////////// .PATH: /usr/src/devdrv/ KMOD=3D fakeBSD SRCS=3D fakeBSD.c pci_hotplug_core.c SRCS+=3D device_if.h bus_if.h pci_if.h .include From owner-freebsd-hackers@FreeBSD.ORG Sat May 6 11:39: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 82E3B16A409 for ; Sat, 6 May 2006 11:39:39 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from marvin.harmless.hu (marvin.harmless.hu [195.56.55.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id A626243D49 for ; Sat, 6 May 2006 11:39:38 +0000 (GMT) (envelope-from phoemix@harmless.hu) Received: from localhost (localhost [127.0.0.1]) by marvin (Postfix) with ESMTP id BBB3620001CA for ; Sat, 6 May 2006 13:39:37 +0200 (CEST) Received: from marvin.harmless.hu ([127.0.0.1]) by localhost (marvin [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03947-09 for ; Sat, 6 May 2006 13:39:36 +0200 (CEST) Received: by marvin (Postfix, from userid 1000) id 3CC1E20001C9; Sat, 6 May 2006 13:39:36 +0200 (CEST) Date: Sat, 6 May 2006 13:39:36 +0200 To: freebsd-hackers@freebsd.org Message-ID: <20060506113936.GA13287@marvin.harmless.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline User-Agent: Mutt/1.5.9i From: phoemix@harmless.hu (Gergely CZUCZY) X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at harmless.hu Subject: syscall calling question 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, 06 May 2006 11:39:54 -0000 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=utf-8 Content-Disposition: inline hello, There's an issue on jails i've decided to look into (jails keep on stucking into the system). Yet, i examining the 6-STABLE tree, and there is a point i don't understands in libc.so.6 there is jail_attach (i've picked a call) defined, while i was unable to find any jail-related functions defined in lib/libc. The only place they are defined is under kern/kern_jail.c, which has a different prototype than the one in the libc (according to the manual page and the source of jexec(8)). my question is, from a userland libcall, how does a kernel-functions be invoked? i couldn't figure it out by looking at the source, and also the developers handbook hadn't told this to me. Bye, Gergely Czuczy mailto: gergely.czuczy@harmless.hu PGP: http://phoemix.harmless.hu/phoemix.pgp Weenies test. Geniuses solve problems that arise. --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEXIr4bBsEN0U7BV0RAi+ZAKCsZ2bnLRU67crzWrEwuDBPjOLd2QCfb21X 3rNhcT0HMGG7WFP2x727d9w= =hBAi -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- From owner-freebsd-hackers@FreeBSD.ORG Sat May 6 16:35: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 EB68B16A400 for ; Sat, 6 May 2006 16:35:48 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E01C43D46 for ; Sat, 6 May 2006 16:35:48 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: by wx-out-0102.google.com with SMTP id t13so644284wxc for ; Sat, 06 May 2006 09:35:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=g/8Yw2Ho4ilLpP3wmzeEr2sRtwcH9vGPXsCqSkahKvEqT64s3a3OBTKRYaUm/erG5z9b9umywtmdI1yMvgopH60pxn2gbdVmRbKQWz6/IqSj9y/4dpZNIhPhkQrZVpedoUHlKlgiN/bfe5dURQBgIaxO7A0aIixqAPlHx6CYuKQ= Received: by 10.70.44.20 with SMTP id r20mr429402wxr; Sat, 06 May 2006 09:35:47 -0700 (PDT) Received: by 10.70.37.11 with HTTP; Sat, 6 May 2006 09:35:47 -0700 (PDT) Message-ID: <3bbf2fe10605060935l280183e9ifb0355970d01c2b8@mail.gmail.com> Date: Sat, 6 May 2006 18:35:47 +0200 From: "Attilio Rao" To: "Gergely CZUCZY" In-Reply-To: <20060506113936.GA13287@marvin.harmless.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline References: <20060506113936.GA13287@marvin.harmless.hu> Cc: freebsd-hackers@freebsd.org Subject: Re: syscall calling question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rookie@gufi.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 16:35:49 -0000 VGhlIG9ubHkgZnVuY3Rpb25zIGNhbiBiZSBjYWxsZWQgYXQgdXNlcnNwYWNlIGFyZSBzeXNjYWxs cyB0aHJvdWdoCnNvZnR3YXJlIGludGVycnVwdC4KCkF0dGlsaW8KCjIwMDYvNS82LCBHZXJnZWx5 IENaVUNaWSA8cGhvZW1peEBoYXJtbGVzcy5odT46Cj4gaGVsbG8sCj4KPiBUaGVyZSdzIGFuIGlz c3VlIG9uIGphaWxzIGkndmUgZGVjaWRlZCB0byBsb29rIGludG8KPiAoamFpbHMga2VlcCBvbiBz dHVja2luZyBpbnRvIHRoZSBzeXN0ZW0pLiBZZXQsIGkgZXhhbWluaW5nCj4gdGhlIDYtU1RBQkxF IHRyZWUsIGFuZCB0aGVyZSBpcyBhIHBvaW50IGkgZG9uJ3QgdW5kZXJzdGFuZHMKPgo+IGluIGxp YmMuc28uNiB0aGVyZSBpcyBqYWlsX2F0dGFjaCAoaSd2ZSBwaWNrZWQgYSBjYWxsKSBkZWZpbmVk LAo+IHdoaWxlIGkgd2FzIHVuYWJsZSB0byBmaW5kIGFueSBqYWlsLXJlbGF0ZWQgZnVuY3Rpb25z IGRlZmluZWQgaW4KPiBsaWIvbGliYy4gVGhlIG9ubHkgcGxhY2UgdGhleSBhcmUgZGVmaW5lZCBp cyB1bmRlciBrZXJuL2tlcm5famFpbC5jLAo+IHdoaWNoIGhhcyBhIGRpZmZlcmVudCBwcm90b3R5 cGUgdGhhbiB0aGUgb25lIGluIHRoZSBsaWJjIChhY2NvcmRpbmcKPiB0byB0aGUgbWFudWFsIHBh Z2UgYW5kIHRoZSBzb3VyY2Ugb2YgamV4ZWMoOCkpLgo+Cj4gbXkgcXVlc3Rpb24gaXMsIGZyb20g YSB1c2VybGFuZCBsaWJjYWxsLCBob3cgZG9lcyBhIGtlcm5lbC1mdW5jdGlvbnMKPiBiZSBpbnZv a2VkPyBpIGNvdWxkbid0IGZpZ3VyZSBpdCBvdXQgYnkgbG9va2luZyBhdCB0aGUgc291cmNlLCBh bmQKPiBhbHNvIHRoZSBkZXZlbG9wZXJzIGhhbmRib29rIGhhZG4ndCB0b2xkIHRoaXMgdG8gbWUu Cj4KPiBCeWUsCj4KPiBHZXJnZWx5IEN6dWN6eQo+IG1haWx0bzogZ2VyZ2VseS5jenVjenlAaGFy bWxlc3MuaHUKPiBQR1A6IGh0dHA6Ly9waG9lbWl4Lmhhcm1sZXNzLmh1L3Bob2VtaXgucGdwCj4K PiBXZWVuaWVzIHRlc3QuIEdlbml1c2VzIHNvbHZlIHByb2JsZW1zIHRoYXQgYXJpc2UuCj4KPgo+ IC0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tCj4gVmVyc2lvbjogR251UEcgdjEuNC4xIChH TlUvTGludXgpCj4KPiBpRDhEQlFGRVhJcjRiQnNFTjBVN0JWMFJBaStaQUtDc1oyYm5MUlU2N2Ny eldyRXd1REJQak9MZDJRQ2ZiMjFYCj4gM3JOaGNUMEhNR0c3V0ZQMng3MjdkOXc9Cj4gPWhCQWkK PiAtLS0tLUVORCBQR1AgU0lHTkFUVVJFLS0tLS0KPgo+Cj4KCgotLQpQZWFjZSBjYW4gb25seSBi ZSBhY2hpZXZlZCBieSB1bmRlcnN0YW5kaW5nIC0gQS4gRWluc3RlaW4K From owner-freebsd-hackers@FreeBSD.ORG Sat May 6 16:37: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 5CF8E16A438 for ; Sat, 6 May 2006 16:37:49 +0000 (UTC) (envelope-from phoemix@harmless.hu) Received: from marvin.harmless.hu (marvin.harmless.hu [195.56.55.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02BC143D46 for ; Sat, 6 May 2006 16:37:48 +0000 (GMT) (envelope-from phoemix@harmless.hu) Received: from localhost (localhost [127.0.0.1]) by marvin (Postfix) with ESMTP id C4F3420001CA; Sat, 6 May 2006 18:37:46 +0200 (CEST) Received: from marvin.harmless.hu ([127.0.0.1]) by localhost (marvin [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10630-06; Sat, 6 May 2006 18:37:46 +0200 (CEST) Received: by marvin (Postfix, from userid 1000) id 479EA20001C9; Sat, 6 May 2006 18:37:46 +0200 (CEST) Date: Sat, 6 May 2006 18:37:46 +0200 To: rookie@gufi.org Message-ID: <20060506163746.GA24724@marvin.harmless.hu> References: <20060506113936.GA13287@marvin.harmless.hu> <3bbf2fe10605060935l280183e9ifb0355970d01c2b8@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3MwIy2ne0vdjdPXF" Content-Disposition: inline In-Reply-To: <3bbf2fe10605060935l280183e9ifb0355970d01c2b8@mail.gmail.com> User-Agent: Mutt/1.5.9i From: phoemix@harmless.hu (Gergely CZUCZY) X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at harmless.hu Cc: Gergely CZUCZY , freebsd-hackers@freebsd.org Subject: Re: syscall calling question 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, 06 May 2006 16:37:50 -0000 --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=utf-8 Content-Disposition: inline On Sat, May 06, 2006 at 06:35:47PM +0200, Attilio Rao wrote: > The only functions can be called at userspace are syscalls through > software interrupt. where can I read about this more? how does it exactly works, where can i find the bits, if i want to experience, how can i add a syscall and call it, how goes the symbol into the compiled libc shared object, and so... ? Bye, Gergely Czuczy mailto: gergely.czuczy@harmless.hu PGP: http://phoemix.harmless.hu/phoemix.pgp Weenies test. Geniuses solve problems that arise. --3MwIy2ne0vdjdPXF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEXNDabBsEN0U7BV0RAhNNAJ4rI0lrZ4kRaBv1UqQFaH/8EYtdsQCeOPSp OhGqBczjyEU2Izort0oL73M= =yXri -----END PGP SIGNATURE----- --3MwIy2ne0vdjdPXF-- From owner-freebsd-hackers@FreeBSD.ORG Sat May 6 16:40:45 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 B1F3616A413 for ; Sat, 6 May 2006 16:40:45 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C3CD43D6E for ; Sat, 6 May 2006 16:40:37 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: by wx-out-0102.google.com with SMTP id t13so644724wxc for ; Sat, 06 May 2006 09:40:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=l/1w2lh38QicMBuCnXpsoUEaUC3AEyBCO2ykynaPvGxrA/AzZVtwnhtfOyASmr1MEF1v4IsDnL5aoAE+4SyttmBFvxHaIQkQLVd6Dum8eWM38K6AQzfHHuvkqmyUP/694PjhPjVJnkpaa5DhQo7e+3kHqhTho87RfYweLhiNsAo= Received: by 10.70.47.3 with SMTP id u3mr437410wxu; Sat, 06 May 2006 09:40:37 -0700 (PDT) Received: by 10.70.37.11 with HTTP; Sat, 6 May 2006 09:40:37 -0700 (PDT) Message-ID: <3bbf2fe10605060940v3a9888f6icc05dd3df543979@mail.gmail.com> Date: Sat, 6 May 2006 18:40:37 +0200 From: "Attilio Rao" To: "Gergely CZUCZY" In-Reply-To: <20060506163746.GA24724@marvin.harmless.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline References: <20060506113936.GA13287@marvin.harmless.hu> <3bbf2fe10605060935l280183e9ifb0355970d01c2b8@mail.gmail.com> <20060506163746.GA24724@marvin.harmless.hu> Cc: freebsd-hackers@freebsd.org Subject: Re: syscall calling question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rookie@gufi.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2006 16:40:48 -0000 ZGV2ZWxvcGVycyBoYW5kYm9vayAocmVhZCBhc3NlbWJseSBzZWN0aW9uKSBleHBsYWluIGV4YWN0 bHkgaG93IHRoZQpzeXNjYWxsIGhhbmRsaW5nIGhhcHBlbnMgb24gaTM4NiBhcmNoaXRlY3R1cmUu CgpBdHRpbGlvCgoyMDA2LzUvNiwgR2VyZ2VseSBDWlVDWlkgPHBob2VtaXhAaGFybWxlc3MuaHU+ Ogo+IE9uIFNhdCwgTWF5IDA2LCAyMDA2IGF0IDA2OjM1OjQ3UE0gKzAyMDAsIEF0dGlsaW8gUmFv IHdyb3RlOgo+ID4gVGhlIG9ubHkgZnVuY3Rpb25zIGNhbiBiZSBjYWxsZWQgYXQgdXNlcnNwYWNl IGFyZSBzeXNjYWxscyB0aHJvdWdoCj4gPiBzb2Z0d2FyZSBpbnRlcnJ1cHQuCj4gd2hlcmUgY2Fu IEkgcmVhZCBhYm91dCB0aGlzIG1vcmU/IGhvdyBkb2VzIGl0IGV4YWN0bHkgd29ya3MsIHdoZXJl IGNhbiBpIGZpbmQKPiB0aGUgYml0cywgaWYgaSB3YW50IHRvIGV4cGVyaWVuY2UsIGhvdyBjYW4g aSBhZGQgYSBzeXNjYWxsIGFuZCBjYWxsIGl0LCBob3cKPiBnb2VzIHRoZSBzeW1ib2wgaW50byB0 aGUgY29tcGlsZWQgbGliYyBzaGFyZWQgb2JqZWN0LCBhbmQgc28uLi4gPwo+Cj4gQnllLAo+Cj4g R2VyZ2VseSBDenVjenkKPiBtYWlsdG86IGdlcmdlbHkuY3p1Y3p5QGhhcm1sZXNzLmh1Cj4gUEdQ OiBodHRwOi8vcGhvZW1peC5oYXJtbGVzcy5odS9waG9lbWl4LnBncAo+Cj4gV2VlbmllcyB0ZXN0 LiBHZW5pdXNlcyBzb2x2ZSBwcm9ibGVtcyB0aGF0IGFyaXNlLgo+Cj4KPiAtLS0tLUJFR0lOIFBH UCBTSUdOQVRVUkUtLS0tLQo+IFZlcnNpb246IEdudVBHIHYxLjQuMSAoR05VL0xpbnV4KQo+Cj4g aUQ4REJRRkVYTkRhYkJzRU4wVTdCVjBSQWhOTkFKNHJJMGxyWjRrUmFCdjFVcVFGYUgvOEVZdGRz UUNlT1BTcAo+IE9oR3FCY3pqeUVVMkl6b3J0MG9MNzNNPQo+ID15WHJpCj4gLS0tLS1FTkQgUEdQ IFNJR05BVFVSRS0tLS0tCj4KPgo+CgoKLS0KUGVhY2UgY2FuIG9ubHkgYmUgYWNoaWV2ZWQgYnkg dW5kZXJzdGFuZGluZyAtIEEuIEVpbnN0ZWluCg== From owner-freebsd-hackers@FreeBSD.ORG Sat May 6 17:12: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 B9CC916A402 for ; Sat, 6 May 2006 17:12:06 +0000 (UTC) (envelope-from marcel245@mweb.co.za) Received: from anemone.mweb.co.za (anemone.mweb.co.za [196.2.50.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D85F43D45 for ; Sat, 6 May 2006 17:12:05 +0000 (GMT) (envelope-from marcel245@mweb.co.za) Received: from anemone.mweb.co.za (localhost.localdomain [127.0.0.1]) by pwfilter01.mweb.co.za (Postfix) with ESMTP id 2858428483 for ; Sat, 6 May 2006 19:12:04 +0200 (SAST) Received: from mws38 (unknown [196.2.63.102]) by anemone.mweb.co.za (Postfix) with ESMTP id 0FD3528482 for ; Sat, 6 May 2006 19:12:04 +0200 (SAST) From: "marcel245@mweb.co.za" To: freebsd-hackers@freebsd.org Message-ID: <926f294bee3f4d3caf20a4257ccded9b@mweb.co.za> Date: Sat, 06 May 2006 19:12:03 +0200 X-Priority: 3 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: ClamAV using ClamSMTP X-Mailman-Approved-At: Sat, 06 May 2006 17:25:50 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: NATD & IPFW 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, 06 May 2006 17:12:06 -0000 I cant seem to get something working and would really appreciate some h= elp=2E I use IPFW and have used NAT in the past through the ipfw= "divert" rules=2E But what i need to get right is simply nat for a = particular host internally to a external mail server=2E Now i ca= n nat all traffic or nothing not control a particular host=2E Also i= have tried all resources and methods including trying the "rediect por= t" function of natd seperatlly of ipfw=2E this to didnt seem to work=2E= Examples i copied didnt=2E Im using freebsd6