From owner-freebsd-arch Mon Jul 2 1:33:32 2001 Delivered-To: freebsd-arch@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id 621B337B403; Mon, 2 Jul 2001 01:33:27 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f612PAq00351; Sun, 1 Jul 2001 03:25:10 +0100 (BST) (envelope-from nik) Date: Sun, 1 Jul 2001 03:25:10 +0100 From: Nik Clayton To: Mike Pritchard Cc: Nik Clayton , arch@FreeBSD.ORG Subject: Re: [PATCH] Show login(1) how to execute programs at start up Message-ID: <20010701032510.B274@canyon.nothing-going-on.org> References: <20010619195223.E68877@clan.nothing-going-on.org> <20010630081550.B4689@mppsystems.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="H+4ONPRPur6+Ovig" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010630081550.B4689@mppsystems.com>; from mpp@mppsystems.com on Sat, Jun 30, 2001 at 08:15:50AM -0500 Organization: FreeBSD Project Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --H+4ONPRPur6+Ovig Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 30, 2001 at 08:15:50AM -0500, Mike Pritchard wrote: > On Tue, Jun 19, 2001 at 07:52:23PM +0100, Nik Clayton wrote: > > I want to make the new 'tips' fortunes the default for new users at > > system startup. >=20 > Where is the little "click this box to not see this again" box? None > of the fortunes mention how to opt-out of seeing these messages. I got bored of trying to come up with a nice fancy technical solution that would please everybody, so I went with the easy option. At the moment, the functionality is in the share/skel files, so if you use those when you add new users then your users get fortunes (in -current, I haven't MFC'd this yet). Turning it off is as simple as editing .login/.profile. I'm prepared to make this a FAQ. There's been some talk about keying this off the =2Ehushlogin file, which might be a good idea. =20 > Many of the tips are very shell specific. What if the user isn't running > tsch, but running sh instead? =20 They get a few lines of not particularly useful output. It's no big deal. > I think the tips need to be more generic, > or for shell specific tips, tell the user how to determine what shell > they are currently running. Might be a good idea. Commit new tips (or replacements) as necessary. > How non-UNIX are we going on these tips. =20 My criteria has been "Does this provide useful information in a bitesize format that's relevant to a FreeBSD user?". I'm pretty happy that the=20 existing ones do. That's not to say they're perfect, or that they cover every eventuality, but they're not intended to. As I say, feel free to commit replacements as you feel necessary (I know others have). > And that we tell them how to opt-out of our advice. FAQ entry? N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --H+4ONPRPur6+Ovig Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjs+igUACgkQk6gHZCw343UxmwCfdz3GCqi13IRbyUf4XAZscbu4 Lh4AoIzJo3bhSFjUXdCbAw15t6WZGsNA =5u7p -----END PGP SIGNATURE----- --H+4ONPRPur6+Ovig-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Jul 2 7:47: 5 2001 Delivered-To: freebsd-arch@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 198E537B403; Mon, 2 Jul 2001 07:47:03 -0700 (PDT) (envelope-from keichii@iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id CB8B559229; Mon, 2 Jul 2001 09:46:51 -0500 (CDT) Date: Mon, 2 Jul 2001 09:46:51 -0500 From: "Michael C . Wu" To: Mike Pritchard Cc: Nik Clayton , arch@FreeBSD.ORG Subject: Re: [PATCH] Show login(1) how to execute programs at start up Message-ID: <20010702094651.C96996@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20010619195223.E68877@clan.nothing-going-on.org> <20010630081550.B4689@mppsystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010630081550.B4689@mppsystems.com>; from mpp@mppsystems.com on Sat, Jun 30, 2001 at 08:15:50AM -0500 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Jun 30, 2001 at 08:15:50AM -0500, Mike Pritchard scribbled: Can we please stop this bikeshed? Thank you very much, Michael -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Jul 2 7:59:30 2001 Delivered-To: freebsd-arch@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 01CE337B405; Mon, 2 Jul 2001 07:59:17 -0700 (PDT) (envelope-from keichii@iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id 469BD59229; Mon, 2 Jul 2001 09:59:15 -0500 (CDT) Date: Mon, 2 Jul 2001 09:59:15 -0500 From: "Michael C . Wu" To: Mitsuru IWASAKI Cc: dfr@nlsystems.com, arch@freebsd.org, audit@freebsd.org, athlete@kta.att.ne.jp Subject: Re: CFR: Crusoe LongRun Support Message-ID: <20010702095913.A98201@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20010630041951I.iwasaki@jp.FreeBSD.org> <20010701031447S.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="OXfL5xGRrasGEqWY" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010701031447S.iwasaki@jp.FreeBSD.org>; from iwasaki@jp.FreeBSD.org on Sun, Jul 01, 2001 at 03:14:47AM +0900 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Jul 01, 2001 at 03:14:47AM +0900, Mitsuru IWASAKI scribbled: | > I would like to see something like longrun(4) which described the sysctls | > and indicated what each longrun level actually means. | | OK, understood. I've written longrun(4) manpage. As always my English | is poor, any feedback is welcome :-) Here is your original file and the diff I made. Hope you will like this better. :) Just a friendly reminder, do you mind using attachments next time? It is quite a hassle to save the email and then edit it. -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="longrun.4" .\" Copyright (c) 2001 Tamotsu HATTORI .\" Copyright (c) 2001 Mitsuru IWASAKI .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" SUCH DAMAGE. .\" .\" $FreeBSD$ .Dd Jun 30, 2001 .Dt LONGRUN 4 i386 .Os .Sh NAME .Nm longrun .Nd Transmeta(TM) Crusoe(TM) LongRun(TM) support .Sh SYNOPSIS The following .Xr sysctl 8 MIBs are available: .Bl -tag -width "hw.crusoe.percentage integer no " -compact .It Sy "Name Type Changeable Description .It "hw.crusoe.longrun integer yes LongRun mode. .Bl -tag -width "0: minimum frequency mode" -compact .It "0: minimum frequency mode .It "1: power-saving mode .It "2: performance mode .It "3: maximum frequency mode .El .It "hw.crusoe.frequency integer no Current frequency (MHz). .It "hw.crusoe.voltage integer no Current voltage (mV). .It "hw.crusoe.percentage integer no Processing performance (%). .El .Pp .Sh EXAMPLES To get current status: .Bd -literal -offset indent % sysctl hw.crusoe .Ed .Pp To set LongRun mode to performance oriented variable frequency mode: .Bd -literal -offset indent # sysctl -w hw.crusoe.longrun=2 .Ed .Pp .Sh AUTHORS .An -nosplit LongRun support and this manual page were written by .An Tamotsu HATTORI Aq athlete@kta.att.ne.jp and .An Mitsuru IWASAKI Aq iwasaki@FreeBSD.org . .Sh HISTORY Transmeta(TM) Crusoe(TM) LongRun(TM) support first appeared in .Fx 5.0 . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="longrun.4.diff" --- longrun.4 Mon Jul 2 09:50:37 2001 +++ longrun.4.new Mon Jul 2 09:56:10 2001 @@ -31,9 +31,11 @@ .Nm longrun .Nd Transmeta(TM) Crusoe(TM) LongRun(TM) support .Sh SYNOPSIS +The LongRun(TM) support is a collection of power saving mode +for the Transmeta(TM) Crusoe(TM), similiar to Intel(TM)'s SpeedStep(TM). The following .Xr sysctl 8 -MIBs are available: +MIBs set the different modes that the CPU runs in: .Bl -tag -width "hw.crusoe.percentage integer no " -compact .It Sy "Name Type Changeable Description .It "hw.crusoe.longrun integer yes LongRun mode. @@ -49,12 +51,12 @@ .El .Pp .Sh EXAMPLES -To get current status: +Print the current status: .Bd -literal -offset indent % sysctl hw.crusoe .Ed .Pp -To set LongRun mode to performance oriented variable frequency mode: +To set the LongRun mode to performance oriented variable frequency mode (no power saving): .Bd -literal -offset indent # sysctl -w hw.crusoe.longrun=2 .Ed @@ -66,9 +68,6 @@ and .An Mitsuru IWASAKI Aq iwasaki@FreeBSD.org . .Sh HISTORY -Transmeta(TM) Crusoe(TM) LongRun(TM) support first appeared in +The Transmeta(TM) Crusoe(TM) LongRun(TM) support first appeared in .Fx 5.0 . - -To Unsubscribe: send mail to majordomo@FreeBSD.org -with "unsubscribe freebsd-arch" in the body of the message --OXfL5xGRrasGEqWY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Jul 2 11: 6:31 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kta.att.ne.jp (kta.att.ne.jp [165.76.242.5]) by hub.freebsd.org (Postfix) with SMTP id C17C037B407 for ; Mon, 2 Jul 2001 11:06:25 -0700 (PDT) (envelope-from athlete@kta.att.ne.jp) Received: (qmail 22404 invoked from network); 2 Jul 2001 18:06:17 -0000 Received: from unknown (HELO krishna.kta.att.ne.jp) (165.76.242.122) by kta.att.ne.jp with SMTP; 2 Jul 2001 18:06:17 -0000 X-My-Real-Login-Name: athlete; kta.att.ne.jp MIME-Version: 1.0 X-Mailer: Denshin 8 Go V32.1.3.0 025 Date: Tue, 03 Jul 2001 03:06:09 +0900 From: Tamotsu HATTORI To: "Michael C . Wu" Cc: dfr@nlsystems.com, arch@freebsd.org, audit@freebsd.org, iwasaki@jp.freebsd.org In-Reply-To: Your message of "Mon, 2 Jul 2001 09:59:15 -0500" <20010702095913.A98201@peorth.iteration.net> References: <20010702095913.A98201@peorth.iteration.net> Subject: Re: CFR: Crusoe LongRun Support Message-Id: <20010702180625.C17C037B407@hub.freebsd.org> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi. Mon, 2 Jul 2001 09:59:15 -0500 "Michael C . Wu" wrote: Michael> On Sun, Jul 01, 2001 at 03:14:47AM +0900, Mitsuru IWASAKI scribbled: Michael> | > I would like to see something like longrun(4) which described the sysctls Michael> | > and indicated what each longrun level actually means. Michael> | Michael> | OK, understood. I've written longrun(4) manpage. As always my English Michael> | is poor, any feedback is welcome :-) Michael> Michael> Here is your original file and the diff I made. Hope you will like Michael> this better. :) Michael> I think we had better remove the expression of "no power saving" from the following line: To set the LongRun mode to performance oriented variable frequency mode (no power saving). Because processor will spend many time with lower frequency when it works in variable frequency mode, power dissipation will be reduced. How do you think? --------------------------------------------------------- Tamotsu Hattori URL: http://home.att.ne.jp/delta/athlete/index.html e-mail: athlete@kta.att.ne.jp --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Jul 2 16:20:51 2001 Delivered-To: freebsd-arch@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 4D36737B401; Mon, 2 Jul 2001 16:20:43 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f62NJhK38382; Mon, 2 Jul 2001 17:19:43 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107022319.f62NJhK38382@harmony.village.org> To: "Michael C . Wu" Subject: Re: CFR: Crusoe LongRun Support Cc: Mitsuru IWASAKI , dfr@nlsystems.com, arch@FreeBSD.ORG, audit@FreeBSD.ORG, athlete@kta.att.ne.jp In-reply-to: Your message of "Mon, 02 Jul 2001 09:59:15 CDT." <20010702095913.A98201@peorth.iteration.net> References: <20010702095913.A98201@peorth.iteration.net> <20010630041951I.iwasaki@jp.FreeBSD.org> <20010701031447S.iwasaki@jp.FreeBSD.org> Date: Mon, 02 Jul 2001 17:19:43 -0600 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010702095913.A98201@peorth.iteration.net> "Michael C . Wu" writes: : .Sh SYNOPSIS : +The LongRun(TM) support is a collection of power saving mode : +for the Transmeta(TM) Crusoe(TM), similiar to Intel(TM)'s SpeedStep(TM). I'd say this as LongRun support is a collection of power saving modes for the Transmeta Crusoe chips, similar in scope to Intel's SpeedStep. : The following : .Xr sysctl 8 : -MIBs are available: : +MIBs set the different modes that the CPU runs in: MIBs control the different CPU modes: : -To set LongRun mode to performance oriented variable frequency mode: : +To set the LongRun mode to performance oriented variable frequency mode (no power saving): To set LongRun mode to performance oriented variable frequency mode (less power savings): Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Jul 2 16:24:34 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mass.dis.org (dhcp44-21.dis.org [216.240.44.21]) by hub.freebsd.org (Postfix) with ESMTP id 0110A37B403; Mon, 2 Jul 2001 16:24:27 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f62NZCU02939; Mon, 2 Jul 2001 16:35:13 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200107022335.f62NZCU02939@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: "Michael C . Wu" , Mitsuru IWASAKI , dfr@nlsystems.com, arch@FreeBSD.ORG, audit@FreeBSD.ORG, athlete@kta.att.ne.jp Subject: Re: CFR: Crusoe LongRun Support In-reply-to: Your message of "Mon, 02 Jul 2001 17:19:43 MDT." <200107022319.f62NJhK38382@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Jul 2001 16:35:12 -0700 From: Mike Smith Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I would *very* much like to see an ACPI dump from one of these systems. > In message <20010702095913.A98201@peorth.iteration.net> "Michael C . Wu" writ > es: > : .Sh SYNOPSIS > : +The LongRun(TM) support is a collection of power saving mode > : +for the Transmeta(TM) Crusoe(TM), similiar to Intel(TM)'s SpeedStep(TM). > > I'd say this as > > LongRun support is a collection of power saving modes for the > Transmeta Crusoe chips, similar in scope to Intel's SpeedStep. > > : The following > : .Xr sysctl 8 > : -MIBs are available: > : +MIBs set the different modes that the CPU runs in: > > MIBs control the different CPU modes: > > : -To set LongRun mode to performance oriented variable frequency mode: > : +To set the LongRun mode to performance oriented variable frequency mode (n > o power saving): > > To set LongRun mode to performance oriented variable frequency mode > (less power savings): > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Jul 2 19:57: 2 2001 Delivered-To: freebsd-arch@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 8D2F537B406 for ; Mon, 2 Jul 2001 19:56:57 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.11.3+3.4W/8.11.3/tasogare) with ESMTP/inet id f632ujI99536; Tue, 3 Jul 2001 11:56:46 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: arch@FreeBSD.ORG Cc: athlete@kta.att.ne.jp Subject: Re: CFR: Crusoe LongRun Support In-Reply-To: <200107022319.f62NJhK38382@harmony.village.org> References: <20010701031447S.iwasaki@jp.FreeBSD.org> <200107022319.f62NJhK38382@harmony.village.org> <200107022335.f62NZCU02939@mass.dis.org> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010703115640L.iwasaki@jp.FreeBSD.org> Date: Tue, 03 Jul 2001 11:56:40 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 41 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG # Cc trimed Hi, Warner Losh wrote: > In message <20010702095913.A98201@peorth.iteration.net> "Michael C . Wu" writes: > : .Sh SYNOPSIS > : +The LongRun(TM) support is a collection of power saving mode > : +for the Transmeta(TM) Crusoe(TM), similiar to Intel(TM)'s SpeedStep(TM). > > I'd say this as > > LongRun support is a collection of power saving modes for the > Transmeta Crusoe chips, similar in scope to Intel's SpeedStep. > > : The following > : .Xr sysctl 8 > : -MIBs are available: > : +MIBs set the different modes that the CPU runs in: > > MIBs control the different CPU modes: > > : -To set LongRun mode to performance oriented variable frequency mode: > : +To set the LongRun mode to performance oriented variable frequency mode (no power saving): > > To set LongRun mode to performance oriented variable frequency mode > (less power savings): I'll take this correction. Thanks guys! Mike Smith wrote: > I would *very* much like to see an ACPI dump from one of these systems. Yes, I think we have: http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/fiva-MPC-260.asl?cvsroot=freebsd-jp http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/vaioc1.asl?cvsroot=freebsd-jp First one is also available in US: http://www.casio.com/personalpcs/product.cfm?section=17&market=0&product=3917 Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Jul 2 23:59:58 2001 Delivered-To: freebsd-arch@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 106A737B405; Mon, 2 Jul 2001 23:59:50 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.3/8.9.3) with ESMTP id f636xhF30841; Mon, 2 Jul 2001 23:59:43 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.1) id f636xfY06559; Mon, 2 Jul 2001 23:59:41 -0700 (PDT) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 02 Jul 2001 23:59:41 -0700 (PDT) From: John Baldwin To: arch@FreeBSD.org, developers@FreeBSD.org Subject: Kernel Meeting Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is just a heads up to let you all know that once I've gathered in the various IRC logs and notes from the kernel meeting (Matt Dillon took some excellent notes that he's forwarded already, thanks Matt!) I'll write up a summary and forward it all out (along with whatever method we come up with for viewing the videotape Jordan took (thanks Jordan!)) to these lists. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Jul 3 1:13:29 2001 Delivered-To: freebsd-arch@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id B646637B406; Tue, 3 Jul 2001 01:13:08 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.4/8.11.3) with ESMTP id f638Cxt61310; Tue, 3 Jul 2001 01:13:00 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: jhb@FreeBSD.org Cc: arch@FreeBSD.org, developers@FreeBSD.org Subject: Re: Kernel Meeting In-Reply-To: References: X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010703011259R.jkh@osd.bsdi.com> Date: Tue, 03 Jul 2001 01:12:59 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 22 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: John Baldwin Subject: Kernel Meeting Date: Mon, 02 Jul 2001 23:59:41 -0700 (PDT) > This is just a heads up to let you all know that once I've gathered in the > various IRC logs and notes from the kernel meeting (Matt Dillon took some > excellent notes that he's forwarded already, thanks Matt!) I'll write up a > summary and forward it all out (along with whatever method we come up with for > viewing the videotape Jordan took (thanks Jordan!)) to these lists. And, erm, it may be in need of some editing. I have over 4.5 hours of recorded tape here. Trust me, sitting through the entire "showing" of what I have unedited would be so mind-numbing as to constitute a form of capital punishment. :) You're going to have to give me about a week and a very large hard drive partition to pull this into some semblance of shape - there are some large content-free sections of this archive and you're talking about well over 10GB just to transfer the whole thing, if anyone were that masochistic. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Jul 3 1:26:34 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kalaid.f2f.com.ua (kalaid.f2f.com.ua [62.149.0.33]) by hub.freebsd.org (Postfix) with ESMTP id DAE1437B401; Tue, 3 Jul 2001 01:26:22 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from mail.uic-in.net (root@[212.35.189.4]) by kalaid.f2f.com.ua (8.11.3/8.11.1) with ESMTP id f638SNC43267; Tue, 3 Jul 2001 11:28:25 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (das0-l99.uic-in.net [212.35.189.226]) by mail.uic-in.net (8.11.3/8.11.3) with ESMTP id f638Q4m48124; Tue, 3 Jul 2001 11:26:05 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.4/8.11.3) with ESMTP id f638Psq26861; Tue, 3 Jul 2001 11:25:54 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3B418195.6E9D3A6C@FreeBSD.org> Date: Tue, 03 Jul 2001 11:25:57 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Jordan Hubbard Cc: jhb@FreeBSD.org, arch@FreeBSD.org, developers@FreeBSD.org Subject: Re: Kernel Meeting References: <20010703011259R.jkh@osd.bsdi.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > From: John Baldwin > Subject: Kernel Meeting > Date: Mon, 02 Jul 2001 23:59:41 -0700 (PDT) > > > This is just a heads up to let you all know that once I've gathered in the > > various IRC logs and notes from the kernel meeting (Matt Dillon took some > > excellent notes that he's forwarded already, thanks Matt!) I'll write up a > > summary and forward it all out (along with whatever method we come up with for > > viewing the videotape Jordan took (thanks Jordan!)) to these lists. > > And, erm, it may be in need of some editing. I have over 4.5 hours of > recorded tape here. Trust me, sitting through the entire "showing" of > what I have unedited would be so mind-numbing as to constitute a form > of capital punishment. :) > > You're going to have to give me about a week and a very large hard > drive partition to pull this into some semblance of shape - there are > some large content-free sections of this archive and you're talking > about well over 10GB just to transfer the whole thing, if anyone were > that masochistic. You may compress it using divx codec (sorta MPEG-4). For example I have a 3 hour movie here packed into ordinary CD (690MB) and quality is quite bearable. See http://www.divx.com/ for details. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Jul 3 12:25:37 2001 Delivered-To: freebsd-arch@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 55A6937B406 for ; Tue, 3 Jul 2001 12:25:34 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 3 Jul 2001 20:25:33 +0100 (BST) To: Dima Dorfman Cc: arch@freebsd.org, dwmalone@maths.tcd.ie Subject: Re: Peer credentials on a Unix domain socket In-reply-to: Your message of "Wed, 27 Jun 2001 00:06:28 PDT." <20010627070628.AB5F13E2F@bazooka.unixfreak.org> X-Request-Do: Date: Tue, 03 Jul 2001 20:25:29 +0100 From: David Malone Message-ID: <200107032025.aa14647@salmon.maths.tcd.ie> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I would like to propose implementing such a facility as a socket > option, LOCAL_PEERCRED. The payload would be am xucred structure with > the effective credentials of the connect(2) caller. Granted these may > not be the credentials of the process using the socket (think > descriptor passing), but it doesn't matter; if a process hands a > descriptor off to something else, it should be trusting it not to > abuse it (this is a feature: think of opening a privileged port and > dropping privileges). BSDI already has an option like this called (I think) LOCAL_CREDS, it would be probably best to impliment what they do. The option is discussed in the second edition of Steven's network programming book. I have some patches which clean up the Unix Domain control message passing code, so I could have a look at implimenting it. > This has been discussed at least twice before, and nobody has a better > idea. Again, I would like to stress the two requirements: (1) the > accept(2) caller must be able to reliably obtain the effective > credentials of the connect(2) caller, and (2) the accept(2) caller > must be able to do (1) without relying on the connect(2) caller to > send data (SCM_CREDS doesn't meet (2)). If you want to do things like this without waiting, then maybe it would be better coded using unix domain datagram sockets, not stream sockets? That way they can't use up file discriptors on the serving process. They can still send junk datagrams, but you could tell they were junk easily 'cos they'd have no credentials attached. (If you impliment things this way you can also get the creds of the process sending messages, as opposed to the credentials of the process which bound the socket.) David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Jul 3 14: 6:34 2001 Delivered-To: freebsd-arch@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id AEBF437B401 for ; Tue, 3 Jul 2001 14:06:30 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id B09E53E28; Tue, 3 Jul 2001 14:06:25 -0700 (PDT) To: David Malone Cc: arch@freebsd.org Subject: Re: Peer credentials on a Unix domain socket In-Reply-To: <200107032025.aa14647@salmon.maths.tcd.ie>; from dwmalone@maths.tcd.ie on "Tue, 03 Jul 2001 20:25:29 +0100" Date: Tue, 03 Jul 2001 14:06:25 -0700 From: Dima Dorfman Message-Id: <20010703210625.B09E53E28@bazooka.unixfreak.org> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Malone writes: > > I would like to propose implementing such a facility as a socket > > option, LOCAL_PEERCRED. The payload would be am xucred structure with > > the effective credentials of the connect(2) caller. Granted these may > > not be the credentials of the process using the socket (think > > descriptor passing), but it doesn't matter; if a process hands a > > descriptor off to something else, it should be trusting it not to > > abuse it (this is a feature: think of opening a privileged port and > > dropping privileges). > > BSDI already has an option like this called (I think) LOCAL_CREDS, > it would be probably best to impliment what they do. I think we already have this, although it isn't called LOCAL_CREDS. At least there's code to implement it in uipc_usrreq.c (unp_internalize() routine, circa line 991). If I'm seeing things, then LOCAL_CREDS would certainly be a welcome addition, although it would compliment, not contradict, what's being discussed here. > The option is > discussed in the second edition of Steven's network programming > book. I have some patches which clean up the Unix Domain control > message passing code, so I could have a look at implimenting it. > > > This has been discussed at least twice before, and nobody has a better > > idea. Again, I would like to stress the two requirements: (1) the > > accept(2) caller must be able to reliably obtain the effective > > credentials of the connect(2) caller, and (2) the accept(2) caller > > must be able to do (1) without relying on the connect(2) caller to > > send data (SCM_CREDS doesn't meet (2)). > > If you want to do things like this without waiting, then maybe it > would be better coded using unix domain datagram sockets, not stream > sockets? That way they can't use up file discriptors on the serving > process. They can still send junk datagrams, but you could tell > they were junk easily 'cos they'd have no credentials attached. But it may still be desireable to use a stream socket for other reasons. > (If you impliment things this way you can also get the creds of > the process sending messages, as opposed to the credentials of the > process which bound the socket.) With my implementation, the credentials are stored at connect(2) time. In some bizzare cases, this may even be preferred to the credentials at write(2) time. Of course, having both would be nice :-). Dima Dorfman dima@unixfreak.org P.S. I just caught up on my OpenBSD commit mail, and it seems they've implemented something like what I'm proposing, but as a system call, getpeereid(). The net result is the same, although I think a socket option is more appropriate than a syscall. If desired, we/I can implement getpeereid() as a library function in terms of getsockopt(2). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Jul 4 2: 2:40 2001 Delivered-To: freebsd-arch@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 31A7337B405 for ; Wed, 4 Jul 2001 02:02:37 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 4 Jul 2001 10:02:36 +0100 (BST) To: Dima Dorfman Cc: David Malone , arch@freebsd.org Subject: Re: Peer credentials on a Unix domain socket In-reply-to: Your message of "Tue, 03 Jul 2001 14:06:25 PDT." <20010703210625.B09E53E28@bazooka.unixfreak.org> X-Request-Do: Date: Wed, 04 Jul 2001 10:02:35 +0100 From: David Malone Message-ID: <200107041002.aa78002@salmon.maths.tcd.ie> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I think we already have this, although it isn't called LOCAL_CREDS. > At least there's code to implement it in uipc_usrreq.c > (unp_internalize() routine, circa line 991). If I'm seeing things, > then LOCAL_CREDS would certainly be a welcome addition, although it > would compliment, not contradict, what's being discussed here. What we have is slightly different. In BSDI's version you set a socket option on the receiving end and then cerds are added as a control message when someone writes data to the sending end. With our version the sender must add a control message of type SCM_CREDS. > > If you want to do things like this without waiting, then maybe it > > would be better coded using unix domain datagram sockets, not stream > > sockets? That way they can't use up file discriptors on the serving > > process. They can still send junk datagrams, but you could tell > > they were junk easily 'cos they'd have no credentials attached. > But it may still be desireable to use a stream socket for other reasons. If you need to communicate after authenticating then you can always send a datagram back with one end of a pipe, a socketpair or whatever type of file discriptor you need. Mind you, I may just be making excuses... > > (If you impliment things this way you can also get the creds of > > the process sending messages, as opposed to the credentials of the > > process which bound the socket.) > With my implementation, the credentials are stored at connect(2) time. > In some bizzare cases, this may even be preferred to the credentials > at write(2) time. Of course, having both would be nice :-). If we wanted to be consistant with the tcp/udp getcred code we should be getting the creds of the person who did the socket(2) call ;-) I guess it's a matter if figuring out what the likely uses are and what the most sensible semantics are based on those. I was working on making a non-suid version of crontab[*] which used SCM_CREDS and SCM_RIGHTS. I was using a datagram socket 'cos it avoided the problem of having to listen and accept. In this case, having the credentials attached to the data you recieve means that there was less doubt about who made the request. I wonder how OpenBSD are using getpeerid and what it's semantics are? Do we know the intended uses of any of other options which people have implimented? (Maybe we should just impliment a way of getting the creds of the caller of socket, connect or write and let application writers choose). David. [*] I got stuck implimenting this version of crontab 'cos currently you can only attach one control message at a time. I've fixed this and found three reasonably serious bugs in the control message passing code (two only show up on FreeBSD-alpha, I think all the BSDs get bitten by the other). Patches soon, hopefully. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Jul 4 2:35:47 2001 Delivered-To: freebsd-arch@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 0CDEE37B401 for ; Wed, 4 Jul 2001 02:35:40 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id 7E2E53E31; Wed, 4 Jul 2001 02:35:36 -0700 (PDT) To: David Malone Cc: arch@freebsd.org Subject: Re: Peer credentials on a Unix domain socket In-Reply-To: <200107041002.aa78002@salmon.maths.tcd.ie>; from dwmalone@maths.tcd.ie on "Wed, 04 Jul 2001 10:02:35 +0100" Date: Wed, 04 Jul 2001 02:35:36 -0700 From: Dima Dorfman Message-Id: <20010704093536.7E2E53E31@bazooka.unixfreak.org> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Malone writes: > > With my implementation, the credentials are stored at connect(2) time. > > In some bizzare cases, this may even be preferred to the credentials > > at write(2) time. Of course, having both would be nice :-). > > If we wanted to be consistant with the tcp/udp getcred code we should > be getting the creds of the person who did the socket(2) call ;-) > > I guess it's a matter if figuring out what the likely uses are and > what the most sensible semantics are based on those. Here's one example use: http://www.superscript.com/ucspi-ipc/intro.html. This author actually provides patches for *BSD to implement getpeereid(), and I believe--although I haven't checked--that OpenBSD just took his patch. (And as I said before, I really think a system call is overdoing it for something like this, esp. when there's already a nice socket option interface.) > I was working > on making a non-suid version of crontab[*] which used SCM_CREDS > and SCM_RIGHTS. I was using a datagram socket 'cos it avoided the > problem of having to listen and accept. In this case, having the > credentials attached to the data you recieve means that there was > less doubt about who made the request. > > I wonder how OpenBSD are using getpeerid and what it's semantics > are? The semantics are very similar to my patch. > Do we know the intended uses of any of other options which > people have implimented? AFAIK, they aren't using it (read: I haven't seen any commit logs that suggest they're using it, although OpenBSD's commit logs are notoriously terse), and I don't know what their intented uses are. > (Maybe we should just impliment a way of getting the creds of the > caller of socket, connect or write and let application writers > choose). If we do this it would be nice if it were consistent, although I don't know how useful it would be to know who called socket(2). Dima Dorfman dima@unixfreak.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Jul 4 2:39:13 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 4DCAD37B406 for ; Wed, 4 Jul 2001 02:39:04 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 3972 invoked by uid 1000); 4 Jul 2001 09:43:34 -0000 Date: Wed, 4 Jul 2001 12:43:34 +0300 From: Peter Pentchev To: arch@FreeBSD.org Cc: audit@FreeBSD.org Subject: A slight improvement of the rc system Message-ID: <20010704124334.F653@ringworld.oblivion.bg> Mail-Followup-To: arch@FreeBSD.org, audit@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, (And yes, I know that there is work in progress of importing the NetBSD rc system; still, I don't think it is going to happen very soon, and I don't think it is going to be MFC'd soon, if ever, so here goes..) Attached is a patch that does two things for the startup/shutdown scripts. First, a new rc.conf variable is introduced - script_name_sep. By default, this is a space, but it should be changed if your startup/shutdown scripts contain spaces. This is not a common occurrence, but it might prove useful, e.g. for people coming from Seattle-OS-based environments, who are prone to generating long, descriptive file names. Second, the rc.shutdown logic is changed a little, so shutdown scripts are executed in reverse alphabetical order. Thus, dependent services are shutdown before the ones they depend upon. G'luck, Peter -- .siht ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI Index: src/etc/rc =================================================================== RCS file: /home/ncvs/src/etc/rc,v retrieving revision 1.271 diff -u -r1.271 rc --- src/etc/rc 2001/06/28 06:43:47 1.271 +++ src/etc/rc 2001/07/04 07:45:15 @@ -793,17 +793,24 @@ ;; *) echo -n 'Local package initialization:' + slist="" for dir in ${local_startup}; do if [ -d "${dir}" ]; then for script in ${dir}/*.sh; do - if [ -x "${script}" ]; then - (set -T - trap 'exit 1' 2 - ${script} start) - fi + slist="${slist}${script_name_sep}${script}" done fi done + script_save_sep="$IFS" + IFS="${script_name_sep}" + for script in ${slist}; do + if [ -x "${script}" ]; then + (set -T + trap 'exit 1' 2 + ${script} start) + fi + done + IFS="${script_save_sep}" echo '.' ;; esac Index: src/etc/rc.shutdown =================================================================== RCS file: /home/ncvs/src/etc/rc.shutdown,v retrieving revision 1.16 diff -u -r1.16 rc.shutdown --- src/etc/rc.shutdown 2000/12/17 08:15:57 1.16 +++ src/etc/rc.shutdown 2001/07/04 07:45:15 @@ -102,17 +102,24 @@ [Nn][Oo] | '') ;; *) + slist="" for dir in ${local_startup}; do if [ -d "${dir}" ]; then for script in ${dir}/*.sh; do - if [ -x "${script}" ]; then - (set -T - trap 'exit 1' 2 - ${script} stop) - fi + slist="${script}${script_name_sep}${slist}" done fi done + script_save_sep="$IFS" + IFS="${script_name_sep}" + for script in ${slist}; do + if [ -x "${script}" ]; then + (set -T + trap 'exit 1' 2 + ${script} stop) + fi + done + IFS="${script_save_sep}" echo '.' ;; esac Index: src/etc/defaults/rc.conf =================================================================== RCS file: /home/ncvs/src/etc/defaults/rc.conf,v retrieving revision 1.116 diff -u -r1.116 rc.conf --- src/etc/defaults/rc.conf 2001/06/28 21:45:47 1.116 +++ src/etc/defaults/rc.conf 2001/07/04 07:45:15 @@ -31,6 +31,7 @@ pccard_conf="/etc/defaults/pccard.conf" # pccardd(8) config file removable_interfaces="" # Removable network interfaces for /etc/pccard_ether. local_startup="/usr/local/etc/rc.d /usr/X11R6/etc/rc.d" # startup script dirs. +script_name_sep=" " # Change if your startup scripts' names contain spaces rc_conf_files="/etc/rc.conf /etc/rc.conf.local" fsck_y_enable="NO" # Set to YES to do fsck -y if the initial preen fails. background_fsck="YES" # Attempt to run fsck in the background where possible. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Jul 4 2:56: 6 2001 Delivered-To: freebsd-arch@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id CAFA137B401 for ; Wed, 4 Jul 2001 02:56:03 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 4 Jul 2001 10:56:03 +0100 (BST) To: Dima Dorfman Cc: David Malone , arch@freebsd.org Subject: Re: Peer credentials on a Unix domain socket In-reply-to: Your message of "Wed, 04 Jul 2001 02:35:36 PDT." <20010704093536.7E2E53E31@bazooka.unixfreak.org> X-Request-Do: Date: Wed, 04 Jul 2001 10:56:02 +0100 From: David Malone Message-ID: <200107041056.aa84171@salmon.maths.tcd.ie> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Here's one example use: http://www.superscript.com/ucspi-ipc/intro.html. > This author actually provides patches for *BSD to implement getpeereid(), > and I believe--although I haven't checked--that OpenBSD just took his > patch. (And as I said before, I really think a system call is overdoing it > for something like this, esp. when there's already a nice socket option > interface.) Interesting - I guess this is a little like the inetd unix domain socket stuff, only it sets some extra environment variables. I guess it would make sense to have inetd set these variables too. I see some mention of SO_PEERCRED for Linux - we should probably find out what was done here and impliment something compatable? (Least we be accused of suffering from NIH). We could then also impliment getpeercred in terms of this and impliment the BSDI socket option. That should cover most bases. > > Do we know the intended uses of any of other options which > > people have implimented? > AFAIK, they aren't using it (read: I haven't seen any commit logs that > suggest they're using it, although OpenBSD's commit logs are > notoriously terse), and I don't know what their intented uses are. I'll try grepping for it in the OpenBSD CVS tree and see. > > (Maybe we should just impliment a way of getting the creds of the > > caller of socket, connect or write and let application writers > > choose). > If we do this it would be nice if it were consistent, although I don't > know how useful it would be to know who called socket(2). The person who called socket is usually the person who called connect (maybe in more cases than the connecting and writing user match?) I guess the advantage is that someone always calls socket, but not always does someone call connect. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Jul 4 9:48:13 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail12.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with SMTP id 7765D37B401 for ; Wed, 4 Jul 2001 09:48:04 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 44563 invoked from network); 4 Jul 2001 16:48:03 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 4 Jul 2001 16:48:03 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010703011259R.jkh@osd.bsdi.com> Date: Wed, 04 Jul 2001 09:48:02 -0700 (PDT) From: John Baldwin To: Jordan Hubbard Subject: Re: Kernel Meeting Cc: developers@FreeBSD.org, arch@FreeBSD.org Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 03-Jul-01 Jordan Hubbard wrote: > From: John Baldwin > Subject: Kernel Meeting > Date: Mon, 02 Jul 2001 23:59:41 -0700 (PDT) > >> This is just a heads up to let you all know that once I've gathered in the >> various IRC logs and notes from the kernel meeting (Matt Dillon took some >> excellent notes that he's forwarded already, thanks Matt!) I'll write up a >> summary and forward it all out (along with whatever method we come up with >> for >> viewing the videotape Jordan took (thanks Jordan!)) to these lists. > > And, erm, it may be in need of some editing. I have over 4.5 hours of > recorded tape here. Trust me, sitting through the entire "showing" of > what I have unedited would be so mind-numbing as to constitute a form > of capital punishment. :) > > You're going to have to give me about a week and a very large hard > drive partition to pull this into some semblance of shape - there are > some large content-free sections of this archive and you're talking > about well over 10GB just to transfer the whole thing, if anyone were > that masochistic. That's fine by me. Thanks. > - Jordan -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Jul 5 14:26:37 2001 Delivered-To: freebsd-arch@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-93.dsl.lsan03.pacbell.net [63.207.60.93]) by hub.freebsd.org (Postfix) with ESMTP id 25AC337B401 for ; Thu, 5 Jul 2001 14:26:33 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 31FA166C4D; Thu, 5 Jul 2001 14:26:28 -0700 (PDT) Date: Thu, 5 Jul 2001 14:26:27 -0700 From: Kris Kennaway To: Chris Wasser Cc: arch@FreeBSD.org Subject: Re: netbsd rc system diff Message-ID: <20010705142627.A38780@xor.obsecurity.org> References: <20010617150050.F582@skunkworks.arpa.mil> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010617150050.F582@skunkworks.arpa.mil>; from cwasser@v-wave.com on Sun, Jun 17, 2001 at 03:00:50PM -0600 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Jun 17, 2001 at 03:00:50PM -0600, Chris Wasser wrote: > Attached is a diff to rc.subr which applies the aforementioned > implementation. Ofcourse this isn't a end-all-be-all solution, ideally a > specialized tool would be used to differentiate which is an actual > parent process and which are children/threads. I haven't been following this thread too closely, but if the goal is to identify the parent PID of some service, then surely the best thing to do is to record the PID in /var/run/*.pid at the time it is started, so there is no ambiguity later on. Kris --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7RNuCWry0BWjoQKURAl6HAJ484ETmTIbo+KdU782lDlaLIzBYAACgg2t9 5W5zgaM83kiMCZFsE9Ih6W4= =WgyC -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Jul 5 17:44:17 2001 Delivered-To: freebsd-arch@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id AB13837B406; Thu, 5 Jul 2001 17:44:12 -0700 (PDT) (envelope-from obrien@nuxi.ucdavis.edu) Received: from dragon.nuxi.com (root@trang.muxi.com [206.40.252.115] (may be forged)) by relay.nuxi.com (8.11.2/8.11.2) with ESMTP id f660iBR06663; Thu, 5 Jul 2001 17:44:11 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f660iAB15217; Thu, 5 Jul 2001 17:44:10 -0700 (PDT) (envelope-from obrien) Date: Thu, 5 Jul 2001 17:44:10 -0700 From: "David O'Brien" To: Peter Pentchev Cc: arch@FreeBSD.org, audit@FreeBSD.org Subject: Re: A slight improvement of the rc system Message-ID: <20010705174409.A15136@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <20010704124334.F653@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010704124334.F653@ringworld.oblivion.bg>; from roam@orbitel.bg on Wed, Jul 04, 2001 at 12:43:34PM +0300 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jul 04, 2001 at 12:43:34PM +0300, Peter Pentchev wrote: > +script_name_sep=" " # Change if your startup scripts' names contain spaces Uh... ever heard of "over engineering"? I think we can assume scripts don't have spaces in their names. Anyone trying and has the ability to change this knob knows enought to just not use spaces in a script's name. This is UNIX. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Jul 5 17:51:14 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mass.dis.org (dhcp44-21.dis.org [216.240.44.21]) by hub.freebsd.org (Postfix) with ESMTP id 80BA337B406; Thu, 5 Jul 2001 17:51:10 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f6614Y903847; Thu, 5 Jul 2001 18:04:34 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200107060104.f6614Y903847@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: obrien@FreeBSD.org Cc: Peter Pentchev , arch@FreeBSD.org, audit@FreeBSD.org Subject: Re: A slight improvement of the rc system In-reply-to: Your message of "Thu, 05 Jul 2001 17:44:10 PDT." <20010705174409.A15136@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Jul 2001 18:04:34 -0700 From: Mike Smith Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > On Wed, Jul 04, 2001 at 12:43:34PM +0300, Peter Pentchev wrote: > > +script_name_sep=" " # Change if your startup scripts' names contain > spaces > > Uh... ever heard of "over engineering"? I think we can assume scripts > don't have spaces in their names. Anyone trying and has the ability to > change this knob knows enought to just not use spaces in a script's name. > This is UNIX. Actually, anyone writing code to parse a set of filenames knows better than to assume that filenames don't contain spaces. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Jul 5 23:22: 3 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 9AC8037B407 for ; Thu, 5 Jul 2001 23:21:57 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 3838 invoked by uid 1000); 6 Jul 2001 06:26:24 -0000 Date: Fri, 6 Jul 2001 09:26:24 +0300 From: Peter Pentchev To: David O'Brien Cc: arch@FreeBSD.org, audit@FreeBSD.org Subject: Re: A slight improvement of the rc system Message-ID: <20010706092624.A3782@ringworld.oblivion.bg> Mail-Followup-To: David O'Brien , arch@FreeBSD.org, audit@FreeBSD.org References: <20010704124334.F653@ringworld.oblivion.bg> <20010705174409.A15136@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010705174409.A15136@dragon.nuxi.com>; from obrien@FreeBSD.org on Thu, Jul 05, 2001 at 05:44:10PM -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jul 05, 2001 at 05:44:10PM -0700, David O'Brien wrote: > On Wed, Jul 04, 2001 at 12:43:34PM +0300, Peter Pentchev wrote: > > +script_name_sep=" " # Change if your startup scripts' names contain spaces > > Uh... ever heard of "over engineering"? I think we can assume scripts > don't have spaces in their names. Anyone trying and has the ability to > change this knob knows enought to just not use spaces in a script's name. > This is UNIX. Yep, this is Unix, and Unix has no arbitrary restrictions on filenames. It does not have a 8.3 restriction, or a caps-only restriction; so why should a *part* of the system place a no-spaces restriction on filenames? Just about all the filesystems supported by FreeBSD allow filenames to contain spaces; it's only logical to give the user the ability to use them, if she so desires. It's not overcomplicating the code, either - the IFS shell variable is standardized and used, which means that the shell was written with this in mind; not allowing it is just that - not using the shell's capabilities the way they were meant to be used. G'luck, Peter -- I am jealous of the first word in this sentence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Jul 6 1:56:33 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ringworld.nanolink.com (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id 8163137B407 for ; Fri, 6 Jul 2001 01:56:23 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 1052 invoked by uid 1000); 6 Jul 2001 09:00:49 -0000 Date: Fri, 6 Jul 2001 12:00:49 +0300 From: Peter Pentchev To: arch@FreeBSD.org Cc: audit@FreeBSD.org Subject: [Fwd: Re: kern/26317: /modules not created by make installkernel] Message-ID: <20010706120049.A590@ringworld.oblivion.bg> Mail-Followup-To: arch@FreeBSD.org, audit@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Anybody see how much harm can come if this patch is committed? It does really solve a possible problem - a removed /modules dir - by interrupting the installworld process instead of happily installing the last module into a file named /modules. G'luck, Peter -- Nostalgia ain't what it used to be. ----- Forwarded message from Gregory Bond ----- Date: Sun, 8 Apr 2001 17:10:02 -0700 (PDT) To: freebsd-bugs@FreeBSD.org Cc: From: Gregory Bond Subject: Re: kern/26317: /modules not created by make installkernel Reply-To: Gregory Bond The following reply was made to PR kern/26317; it has been noted by GNATS. From: Gregory Bond To: David Taylor Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/26317: /modules not created by make installkernel Date: Mon, 09 Apr 2001 10:03:24 +1000 This is a multipart MIME message. --==_Exmh_8133331360 Content-Type: text/plain; charset=us-ascii > It should at least bomb out with an error message, instead of pretending it > succesfully installed your kernel and modules, even though what it > _actually_ did was install one module as '/modules'... A simple patch to achieve this is attached. (I.e. install into /modules/ rather than /modules to force the error to be trapped.) --==_Exmh_8133331360 Content-Type: text/plain ; name="patch"; charset=us-ascii Content-Description: patch Content-Disposition: attachment; filename="patch" Index: kmod.mk =================================================================== RCS file: /usr/ncvs/src/sys/conf/kmod.mk,v retrieving revision 1.82.2.5 diff -u -r1.82.2.5 kmod.mk --- kmod.mk 2001/03/05 06:14:21 1.82.2.5 +++ kmod.mk 2001/04/08 23:59:26 @@ -217,7 +217,7 @@ realinstall: _SUBDIR ${INSTALL} ${COPY} -o ${KMODOWN} -g ${KMODGRP} -m ${KMODMODE} \ - ${_INSTALLFLAGS} ${PROG} ${DESTDIR}${KMODDIR} + ${_INSTALLFLAGS} ${PROG} ${DESTDIR}${KMODDIR}/ .if defined(LINKS) && !empty(LINKS) @set ${LINKS}; \ while test $$# -ge 2; do \ --==_Exmh_8133331360-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Jul 6 2:34:41 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ringworld.nanolink.com (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id 4B30137B401 for ; Fri, 6 Jul 2001 02:34:34 -0700 (PDT) (envelope-from roam@ringworld.nanolink.com) Received: (qmail 656 invoked by uid 1000); 6 Jul 2001 09:38:40 -0000 Date: Fri, 6 Jul 2001 12:38:40 +0300 From: Peter Pentchev To: arch@FreeBSD.org Cc: hardware@FreeBSD.org Subject: New hw.cpuhz sysctl as per PR i386/27627 Message-ID: <20010706123840.A598@ringworld.oblivion.bg> Mail-Followup-To: arch@FreeBSD.org, hardware@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Attached is a slight modification of the patch in PR i386/27627. Are there any downsides to implementing this? If not, how should it be extended to allow probing non-TSC/non-i386 timecounters? G'luck, Peter -- "yields falsehood, when appended to its quotation." yields falsehood, when appended to its quotation. Index: src/sys/i386/isa/clock.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v retrieving revision 1.174 diff -u -r1.174 clock.c --- src/sys/i386/isa/clock.c 2001/05/15 23:22:21 1.174 +++ src/sys/i386/isa/clock.c 2001/07/06 09:11:52 @@ -146,6 +146,10 @@ static u_int32_t i8254_lastcount; static u_int32_t i8254_offset; static int i8254_ticked; +static u_int cpuhz; + +SYSCTL_INT(_hw, OID_AUTO, cpuhz, CTLFLAG_RD, &cpuhz, 0, "CPU speed in Hz."); + /* * XXX new_function and timer_func should not handle clockframes, but * timer_func currently needs to hold hardclock to handle the @@ -664,7 +668,7 @@ * similar to those for the i8254 clock. */ if (tsc_present) - tsc_freq = rdtsc() - old_tsc; + cpuhz = tsc_freq = rdtsc() - old_tsc; if (bootverbose) { if (tsc_present) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Jul 6 5:44:58 2001 Delivered-To: freebsd-arch@freebsd.org Received: from relay.wplus.net (relay.wplus.net [195.131.52.179]) by hub.freebsd.org (Postfix) with ESMTP id 1E2E137B413 for ; Fri, 6 Jul 2001 05:44:50 -0700 (PDT) (envelope-from ricsLtd@hotmail.com) Received: from relay1.wplus.net (smtp.wplus.net [195.131.52.143]) by relay.wplus.net (8.9.1/8.9.1/wplus.2) with ESMTP id QAA41485 for ; Fri, 6 Jul 2001 16:44:48 +0400 (MSD) From: ricsLtd@hotmail.com X-Real-To: Received: from Olga (ip94-78.dialup.wplus.net [195.131.94.78]) by relay1.wplus.net (8.9.1/8.9.1/wplus.2) with SMTP id QAA72257 for ; Fri, 6 Jul 2001 16:44:47 +0400 (MSD) Date: Fri, 6 Jul 2001 16:44:47 +0400 (MSD) Message-Id: <200107061244.QAA72257@relay1.wplus.net> To: X-Mailer: PersMail 3.1 Mime-Version: 1.0 Content-Type: text/plain; charset=Windows-1251 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Looking for the contract or permanent IT staff? We can recruit Russian IT professionals for you? Have a look at www.ricsltd.co.uk. We have a lot to offer! You will be impressed with our services, low fees as well as quality of programmers. If you have any questions please do not hesitate to contact us: info@ricsltd.co.uk Regards, Andrei Nikonorov ________________________________ Sent by "PersMail 3.1" (freeware) ЗАО "АСУ-Импульс": Бизнес-справочники и базы данных "Электронная библиотека художественной литературы" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Jul 6 11:10:56 2001 Delivered-To: freebsd-arch@freebsd.org Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by hub.freebsd.org (Postfix) with ESMTP id 0BA7037B406; Fri, 6 Jul 2001 11:10:52 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: by sharmas.dhs.org (Postfix, from userid 500) id A2AAD5DD93; Fri, 6 Jul 2001 11:11:00 -0700 (PDT) Date: Fri, 6 Jul 2001 11:11:00 -0700 From: Arun Sharma To: Peter Pentchev Cc: arch@FreeBSD.org, hardware@FreeBSD.org Subject: Re: New hw.cpuhz sysctl as per PR i386/27627 Message-ID: <20010706111100.A10405@sharmas.dhs.org> References: <20010706123840.A598@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <20010706123840.A598@ringworld.oblivion.bg>; from roam@orbitel.bg on Fri, Jul 06, 2001 at 12:38:40PM +0300 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jul 06, 2001 at 12:38:40PM +0300, Peter Pentchev wrote: > Hi, > > Attached is a slight modification of the patch in PR i386/27627. > Are there any downsides to implementing this? If not, how should > it be extended to allow probing non-TSC/non-i386 timecounters? > Does this sysctl adjust itself on machines with Intel SpeedStep technology ? Based on my web searches, the MSRs which contain that info don't seem to be documented. I've read about efforts to reverse engineer the windows utility PRCPU.EXE, but haven't seen any results. It'd be great if this sysctl is adjusted. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Jul 6 13:47:20 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mass.dis.org (dhcp44-21.dis.org [216.240.44.21]) by hub.freebsd.org (Postfix) with ESMTP id 0E4C537B401; Fri, 6 Jul 2001 13:47:12 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f66L0fa01267; Fri, 6 Jul 2001 14:00:41 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200107062100.f66L0fa01267@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Peter Pentchev Cc: arch@FreeBSD.org, hardware@FreeBSD.org Subject: Re: New hw.cpuhz sysctl as per PR i386/27627 In-reply-to: Your message of "Fri, 06 Jul 2001 12:38:40 +0300." <20010706123840.A598@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Jul 2001 14:00:41 -0700 From: Mike Smith Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG CPU speeds aren't constants; this is probably not the right place to put it. It also assumes there's only one CPU, which isn't acceptable. It would be better to have a per-cpu "cupuinfo" struct, and populate it from a variety of sources. > Attached is a slight modification of the patch in PR i386/27627. > Are there any downsides to implementing this? If not, how should > it be extended to allow probing non-TSC/non-i386 timecounters? > > G'luck, > Peter > > -- > "yields falsehood, when appended to its quotation." yields falsehood, when ap > pended to its quotation. > > Index: src/sys/i386/isa/clock.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v > retrieving revision 1.174 > diff -u -r1.174 clock.c > --- src/sys/i386/isa/clock.c 2001/05/15 23:22:21 1.174 > +++ src/sys/i386/isa/clock.c 2001/07/06 09:11:52 > @@ -146,6 +146,10 @@ > static u_int32_t i8254_lastcount; > static u_int32_t i8254_offset; > static int i8254_ticked; > +static u_int cpuhz; > + > +SYSCTL_INT(_hw, OID_AUTO, cpuhz, CTLFLAG_RD, &cpuhz, 0, "CPU speed in Hz."); > + > /* > * XXX new_function and timer_func should not handle clockframes, but > * timer_func currently needs to hold hardclock to handle the > @@ -664,7 +668,7 @@ > * similar to those for the i8254 clock. > */ > if (tsc_present) > - tsc_freq = rdtsc() - old_tsc; > + cpuhz = tsc_freq = rdtsc() - old_tsc; > > if (bootverbose) { > if (tsc_present) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Jul 6 14:22:31 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mass.dis.org (dhcp44-21.dis.org [216.240.44.21]) by hub.freebsd.org (Postfix) with ESMTP id 0264437B403; Fri, 6 Jul 2001 14:22:24 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f66LZja01616; Fri, 6 Jul 2001 14:35:46 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200107062135.f66LZja01616@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Arun Sharma Cc: Peter Pentchev , arch@FreeBSD.org, hardware@FreeBSD.org Subject: Re: New hw.cpuhz sysctl as per PR i386/27627 In-reply-to: Your message of "Fri, 06 Jul 2001 11:11:00 PDT." <20010706111100.A10405@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Jul 2001 14:35:45 -0700 From: Mike Smith Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Does this sysctl adjust itself on machines with Intel SpeedStep > technology ? Based on my web searches, the MSRs which contain that > info don't seem to be documented. I've read about efforts to reverse > engineer the windows utility PRCPU.EXE, but haven't seen any results. This will come with the ACPI processor support; a little further down my list. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Jul 6 15: 9:59 2001 Delivered-To: freebsd-arch@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 39B1637B406; Fri, 6 Jul 2001 15:09:55 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f66M9rG01256; Fri, 6 Jul 2001 15:09:53 -0700 (PDT) Message-ID: <3B463731.2090001@isi.edu> Date: Fri, 06 Jul 2001 15:09:53 -0700 From: Lars Eggert User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.2-RELEASE i386; en-US; rv:0.9) Gecko/20010529 X-Accept-Language: en, de MIME-Version: 1.0 To: Mike Smith Cc: Peter Pentchev , arch@FreeBSD.org, hardware@FreeBSD.org Subject: Re: New hw.cpuhz sysctl as per PR i386/27627 References: <200107062100.f66L0fa01267@mass.dis.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Smith wrote: > CPU speeds aren't constants; this is probably not the right place to put > it. It also assumes there's only one CPU, which isn't acceptable. Being the author of the original patch, I agree that its a hack - but it's better than nothing :-) Plus, it doesn't necessarily assume only one CPU - it does assume they all have the same fixed speed though. > It would be better to have a per-cpu "cupuinfo" struct, and populate it > from a variety of sources. All for it. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Jul 6 15:13:31 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mass.dis.org (dhcp44-21.dis.org [216.240.44.21]) by hub.freebsd.org (Postfix) with ESMTP id 94ACE37B403; Fri, 6 Jul 2001 15:13:26 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f66MQra02267; Fri, 6 Jul 2001 15:26:58 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200107062226.f66MQra02267@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Lars Eggert Cc: Mike Smith , Peter Pentchev , arch@freebsd.org, hardware@freebsd.org Subject: Re: New hw.cpuhz sysctl as per PR i386/27627 In-reply-to: Your message of "Fri, 06 Jul 2001 15:09:53 PDT." <3B463731.2090001@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Jul 2001 15:26:52 -0700 From: Mike Smith Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > CPU speeds aren't constants; this is probably not the right place to put > > it. It also assumes there's only one CPU, which isn't acceptable. > > Being the author of the original patch, I agree that its a hack - but > it's better than nothing :-) Plus, it doesn't necessarily assume only > one CPU - it does assume they all have the same fixed speed though. It doesn't seem to serve much useful purpose; the information is already available to the user in the boot-time message buffer, and it's not useful as a number to a running process. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Jul 7 4:22:30 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1D9CB37B401; Sat, 7 Jul 2001 04:22:23 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA02645; Sat, 7 Jul 2001 21:22:19 +1000 Date: Sat, 7 Jul 2001 21:20:15 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Mike Smith Cc: Lars Eggert , Peter Pentchev , arch@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: New hw.cpuhz sysctl as per PR i386/27627 In-Reply-To: <200107062226.f66MQra02267@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 6 Jul 2001, Mike Smith wrote: > > Mike Smith wrote: > > > > > CPU speeds aren't constants; this is probably not the right place to put > > > it. It also assumes there's only one CPU, which isn't acceptable. > > > > Being the author of the original patch, I agree that its a hack - but > > it's better than nothing :-) Plus, it doesn't necessarily assume only > > one CPU - it does assume they all have the same fixed speed though. > > It doesn't seem to serve much useful purpose; the information is already > available to the user in the boot-time message buffer, and it's not > useful as a number to a running process. The same information is already available to the user via the machdep.tsc_freq sysctl if there is a tsc, modulo bugs in the timecounter code (this sysctl is actually only available if there is a tsc AND the tsc timecounter was initialized at boot time). If there is no tsc, then machdep.tsc_freq fails properly but hw.cpuhz bogusly says that the frequency is 0. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message