From owner-freebsd-arch Sun Apr 7 4: 0: 4 2002 Delivered-To: freebsd-arch@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id B20FF37B41C for ; Sun, 7 Apr 2002 03:59:41 -0700 (PDT) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g37Axf538216; Sun, 7 Apr 2002 03:59:41 -0700 (PDT) (envelope-from rizzo) Date: Sun, 7 Apr 2002 03:59:41 -0700 From: Luigi Rizzo To: arch@freebsd.org Subject: proposed code: automatic setting of hostname from MAC address Message-ID: <20020407035941.B37911@iguana.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i 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, as part of the PicoBSD "rc" scripts, there is some code which determines the hostname (and IP) of a box from the MAC address of the first ethernet interface, using /etc/hosts as a database of known machines. The relevant code is in src/release/picobsd/floppy.tree/etc/rc.conf.defaults I was wondering whether, with the necessary modifications (see NOTES), there is interest in merging this feature into the standard startup scripts. For PicoBSD the usefulness is obvious -- being images often resident on removable media, this lets you use the exact same image for different machines. I have other setups where this can be useful, e.g. I often use disks on removable frames and move them back and forth across different machines; or, for some centrally-administered configurations, this mechanism can also be very useful, as it permits to centralise the configuration to one or two files (rc.conf plus the database of MAC<->hostnames). Comments ? cheers luigi NOTES 1. Possible modifications include fetching the MAC-hostname info from /etc/ethers instead of /etc/hosts, and enabling this feature only if explicitly invoked from rc.conf (i.e. put an 'auto_set_hostname()' call in rc.conf in place of 'hostname=foo.bar' and make sure the procedure is run only once even if rc.conf is sourced multiple times). 2. This code becomes mostly useful if we use, in rc.conf, a case statement to set the configuration: # rc.conf auto_set_hostname() ... case "${hostname} in *.at.work) defaultrouter="5.6.7.8" sendmail_enable="YES" ;; *.at.home) defaultrouter="1.2.3.4" ;; esac ... 3. Another thing (again already implemented in the PicoBSD scripts) that helps a lot in managing multiple configurations is to have a mechanism to overwrite, from the rc* scripts, some basic (and short) configuration files such as resolv.conf, host.conf, and maybe fstab. Basically you set shell variables in rc.conf to provide the content for these files, and at some early point in /etc/rc these variable are used to update the corresponding files in /etc This seems to be deprecated by the current structure of rc.conf, though it can have some good uses. -------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Apr 8 1:25: 7 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by hub.freebsd.org (Postfix) with ESMTP id 91BED37B405 for ; Mon, 8 Apr 2002 01:25:04 -0700 (PDT) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id g388P4Z80340 for ; Mon, 8 Apr 2002 04:25:04 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Mon, 8 Apr 2002 04:25:03 -0400 (EDT) From: Jeff Roberson To: arch@freebsd.org Subject: Removing limits from malloc(9) Message-ID: <20020408041726.U53877-100000@mail.chesapeake.net> 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 The last bit that is missing before we can call malloc/free w/o Giant is the malloc_type statistics. Currently there is nothing really protecting them. There really is no lock that they can conveniently live under. I have a few options. The one that I'm leaning towards is only enabling malloc_type statistics if INVARIANTS is compiled in. Then I could make one lock per malloc_type. The reason this shouldn't be the default is because it creates a single point of contention which is in sharp contrast with the rest of the allocator. So, the INVARIANTS only option doesn't work if we want to keep malloc type limits. I'm wondering how useful this has been in the past? I have heard from phk that it is useful for md(4) which could be converted to use a zone. Is there any real need for these limits other than that? Any comments? Suggestions? Thanks! Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Apr 8 1:41:12 2002 Delivered-To: freebsd-arch@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 2A61B37B405 for ; Mon, 8 Apr 2002 01:41:07 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id D8D555309; Mon, 8 Apr 2002 10:41:04 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Jeff Roberson Cc: arch@freebsd.org Subject: Re: Removing limits from malloc(9) References: <20020408041726.U53877-100000@mail.chesapeake.net> From: Dag-Erling Smorgrav Date: 08 Apr 2002 10:41:04 +0200 In-Reply-To: <20020408041726.U53877-100000@mail.chesapeake.net> Message-ID: Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 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 Jeff Roberson writes: > The last bit that is missing before we can call malloc/free w/o Giant is > the malloc_type statistics. Currently there is nothing really protecting > them. There really is no lock that they can conveniently live under. I > have a few options. The one that I'm leaning towards is only enabling > malloc_type statistics if INVARIANTS is compiled in. Then I could make > one lock per malloc_type. The reason this shouldn't be the default is > because it creates a single point of contention which is in sharp contrast > with the rest of the allocator. It's still a lot better than Giant, and it's a leaf lock so there shouldn't be any worries about reversal. I'd go for it if I were you. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Apr 8 14:37:35 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 4270137B404 for ; Mon, 8 Apr 2002 14:37:32 -0700 (PDT) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g38LbRsH473066; Mon, 8 Apr 2002 17:37:27 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20020408041726.U53877-100000@mail.chesapeake.net> References: <20020408041726.U53877-100000@mail.chesapeake.net> Date: Mon, 8 Apr 2002 17:37:26 -0400 To: Jeff Roberson , arch@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Removing limits from malloc(9) Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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 At 4:25 AM -0400 4/8/02, Jeff Roberson wrote: >The last bit that is missing before we can call malloc/free w/o >Giant is the malloc_type statistics. [...] I have a few options. >The one that I'm leaning towards is only enabling malloc_type >statistics if INVARIANTS is compiled in. Then I could make one >lock per malloc_type. Why would this be tied to INVARIANTS? That option is described as "enable sanity checks". Would it make more sense to have a different kernel option, called MALLOC_STATS or something? Maybe have that as a sysctl, or at least a loader-tunable value? or maybe even an /etc/malloc.conf option... >So, the INVARIANTS only option doesn't work if we want to keep >malloc type limits. I'm wondering how useful this has been in >the past? I have heard from phk that it is useful for md(4) >which could be converted to use a zone. Is there any real need >for these limits other than that? I would like the option of malloc type limits to remain available, although it would be alright if it's only available as some option. I have a feeling that there is something about this that I'm missing, though... -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Apr 8 17:15:13 2002 Delivered-To: freebsd-arch@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 6475637B420 for ; Mon, 8 Apr 2002 17:14:38 -0700 (PDT) Received: from caddis.yogotech.com (yogotech.nokia.com [4.22.66.156]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id SAA13023; Mon, 8 Apr 2002 18:14:35 -0600 (MDT) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g390EXD01292; Mon, 8 Apr 2002 18:14:33 -0600 (MDT) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15538.12905.744914.71228@caddis.yogotech.com> Date: Mon, 8 Apr 2002 18:14:33 -0600 To: Luigi Rizzo Cc: arch@FreeBSD.ORG Subject: Re: proposed code: automatic setting of hostname from MAC address In-Reply-To: <20020407035941.B37911@iguana.icir.org> References: <20020407035941.B37911@iguana.icir.org> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) 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 > as part of the PicoBSD "rc" scripts, there is some code which > determines the hostname (and IP) of a box from the MAC address > of the first ethernet interface, using /etc/hosts > as a database of known machines. The relevant code is in > > src/release/picobsd/floppy.tree/etc/rc.conf.defaults For what it's worth, I think this code is of little value (and I use PicoBSD) code. Can you explain why you believe this code is of more value than simply configuring the interfaces based on their order? > I was wondering whether, with the necessary modifications (see > NOTES), there is interest in merging this feature into the standard > startup scripts. For PicoBSD the usefulness is obvious -- being > images often resident on removable media, this lets you use the > exact same image for different machines. How so vs. the standard way of just configuring an interface? > I have other setups where this can be useful, e.g. I often use disks > on removable frames and move them back and forth across different > machines; or, for some centrally-administered configurations, this > mechanism can also be very useful, as it permits to centralise the > configuration to one or two files (rc.conf plus the database of > MAC<->hostnames). > > Comments ? In my opinion, it's less flexible than the current scheme of ifconfig_ed0="inet 192.168.0.1/24" ifconfig_fxp0="inet 192.168.0.1/24" Or whatever in /etc/rc.conf. You're setup requires a very non-standard configuration file of /etc/hosts, which is still a custom configuration file, vs. the standard customized file in /etc/rc.conf. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Apr 8 17:45:10 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id E75D537B416 for ; Mon, 8 Apr 2002 17:45:05 -0700 (PDT) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g390j3sH493438; Mon, 8 Apr 2002 20:45:04 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <15538.12905.744914.71228@caddis.yogotech.com> References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> Date: Mon, 8 Apr 2002 20:45:02 -0400 To: nate@yogotech.com (Nate Williams), Luigi Rizzo From: Garance A Drosihn Subject: Re: proposed code: automatic setting of hostname from MAC address Cc: arch@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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 At 6:14 PM -0600 4/8/02, Nate Williams wrote: >Luigi Rizzo wrote: > > >> Comments ? > >In my opinion, it's less flexible than the current scheme of > >ifconfig_ed0="inet 192.168.0.1/24" >ifconfig_fxp0="inet 192.168.0.1/24" > >Or whatever in /etc/rc.conf. You're setup requires a very >non-standard configuration file of /etc/hosts, which is still >a custom configuration file, vs. the standard customized file >in /etc/rc.conf. Hmm. I did not understand Luigi's reference to /etc/hosts, but I had assumed that the feature was similar to how MacOS 10 works. The machine gets an IP address via DHCP (for instance), and then sets the machine's hostname based on what DNS says is the hostname for that IP address. That works out pretty well. But Now that I've read his message a little closer, I see he's talking about something else. While his code does require a custom configuration, there still is some point to it, if he's using it on a lot of machines. It's *one* custom image which can be used on a hundred different machines (if you personally are running a hundred different machines, such as in a public-lab setting). I must admit I haven't had a lot of time to think about the specific implementation he's asking about, although I have the feeling that something like it could be generally useful. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Apr 8 20: 6:19 2002 Delivered-To: freebsd-arch@freebsd.org Received: from smtp018.mail.yahoo.com (smtp018.mail.yahoo.com [216.136.174.115]) by hub.freebsd.org (Postfix) with SMTP id B67BD37B41E for ; Mon, 8 Apr 2002 20:02:29 -0700 (PDT) Received: from dialup68.net33.samart.co.th (HELO pokaeobkk) (easytoberich01@203.149.33.68 with login) by smtp.mail.vip.sc5.yahoo.com with SMTP; 9 Apr 2002 03:02:15 -0000 Message-ID: <001901c1df73$2c90ba40$442195cb@loxinfo.co.th> From: "workathome" To: Subject: turn off your tv and turn on your life Date: Tue, 9 Apr 2002 09:57:02 +0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0014_01C1DFAC.E68AA760" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 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 a multi-part message in MIME format. ------=_NextPart_000_0014_01C1DFAC.E68AA760 Content-Type: text/plain; charset="windows-874" Content-Transfer-Encoding: quoted-printable if you need a chance to make your dream come true,I will give you a = chance.take it or loose it,up to you. www.smartejob.com/siriline ------=_NextPart_000_0014_01C1DFAC.E68AA760 Content-Type: text/html; charset="windows-874" Content-Transfer-Encoding: quoted-printable
if you need a chance to make your dream = come true,I=20 will give you a chance.take it or loose it,up to you.
www.smartejob.com/siriline=
 
------=_NextPart_000_0014_01C1DFAC.E68AA760-- _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Apr 8 21:24:48 2002 Delivered-To: freebsd-arch@freebsd.org Received: from smtp.web.de (smtp02.web.de [217.72.192.151]) by hub.freebsd.org (Postfix) with ESMTP id 206C637B41D for ; Mon, 8 Apr 2002 21:24:40 -0700 (PDT) Received: from [213.7.61.144] (helo=q5c0d3) by smtp.web.de with smtp (WEB.DE(Exim) 4.43 #48) id 16unBJ-0006wb-00 for freebsd-arch@FreeBSD.org; Tue, 09 Apr 2002 06:24:33 +0200 Message-ID: <000901c1df7e$d6a9a540$903d07d5@q5c0d3> From: "Peter Rader Alias Nocturne" To: Subject: witch platform i have Date: Tue, 9 Apr 2002 06:27:18 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C1DF8F.991E4620" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 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 a multi-part message in MIME format. ------=_NextPart_000_0006_01C1DF8F.991E4620 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable i dont know, if i need i386 or Alpha i have an Cyrix; meen Alpha the old 100Mhz Processor of AMD? ------=_NextPart_000_0006_01C1DF8F.991E4620 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
i dont know, if i need = i386 or=20 Alpha
i have an Cyrix; meen = Alpha the old=20 100Mhz Processor of AMD?
 
------=_NextPart_000_0006_01C1DF8F.991E4620-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Apr 8 23:52:34 2002 Delivered-To: freebsd-arch@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 5C99B37B419 for ; Mon, 8 Apr 2002 23:52:28 -0700 (PDT) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g396qQN57953; Mon, 8 Apr 2002 23:52:26 -0700 (PDT) (envelope-from rizzo) Date: Mon, 8 Apr 2002 23:52:26 -0700 From: Luigi Rizzo To: Nate Williams Cc: arch@FreeBSD.ORG Subject: Re: proposed code: automatic setting of hostname from MAC address Message-ID: <20020408235226.B57765@iguana.icir.org> References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15538.12905.744914.71228@caddis.yogotech.com> User-Agent: Mutt/1.3.23i 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 Nate, probably i did not explain it clearly. s Garance says, the code i am proposing lets you use the same configuration file (/etc/rc.conf) on multiple machines, instead of having to customise it for each one. The call to auto_set_hostname() in rc.conf will fetch the MAC address from the first ethernet card, look it up in a database of MAC<->hostname pairs (/etc/ethers, or /etc/hosts), and sets the "hostname" and "ifconfig_foo0" shell variables accordingly. From there on, rc.conf is absolutely the same as usual. Obviously, now that hostname is not constant, you can also find it convenient to have a " case ${hostname} in ... esac" statement in rc.conf to customise the configuration for the different hosts. This is not replacing the current scheme -- you can still choose to put hostname="foo.bar" ifconfig_ed0="inet 1.2.3.4 netmask 0xffffff00" in your rc.conf. But since this is often the only significant difference among different rc.conf, having this sorted out automatically can be very convenient. Examples: + in a site that I know, the sysadmin manages a number of FreeBSD boxes, and whenever an OS upgrade needs to be made, he has to push around a number of configuration files. For the most part, they are all the same except for rc.conf (where the difference in most cases is limited to the setting of "hostname" and "ifconfig_foo0", and possibly /etc/fstab. + for things such as PicoBSD images, or "rescue" floppy/CDs, having this code lets you use the same exact media to come up with the correct configuration on different boxes + (a bit less common, though still someone might do this) for some time I used to carry my hard disk in a removable frame and move it between my home and office machine. Again this code would let the OS use the correct configuration in the different places. Does it make more sense now ? cheers luigi > For what it's worth, I think this code is of little value (and I use > PicoBSD) code. Can you explain why you believe this code is of more > value than simply configuring the interfaces based on their order? ... > In my opinion, it's less flexible than the current scheme of > > ifconfig_ed0="inet 192.168.0.1/24" > ifconfig_fxp0="inet 192.168.0.1/24" > > Or whatever in /etc/rc.conf. You're setup requires a very non-standard > configuration file of /etc/hosts, which is still a custom configuration > file, vs. the standard customized file in /etc/rc.conf. > > > > Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 1:43:29 2002 Delivered-To: freebsd-arch@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 802FD37B41A for ; Tue, 9 Apr 2002 01:43:22 -0700 (PDT) Received: from pool0072.cvx40-bradley.dialup.earthlink.net ([216.244.42.72] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16urDf-0000vZ-00; Tue, 09 Apr 2002 01:43:15 -0700 Message-ID: <3CB2A989.6E09236C@mindspring.com> Date: Tue, 09 Apr 2002 01:42:49 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Luigi Rizzo Cc: Nate Williams , arch@FreeBSD.ORG Subject: Re: proposed code: automatic setting of hostname from MAC address References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> <20020408235226.B57765@iguana.icir.org> Content-Type: text/plain; charset=us-ascii 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 Luigi Rizzo wrote: > The call to auto_set_hostname() in rc.conf will fetch the MAC address > from the first ethernet card, I like the idea, except which etherent card is "first"? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 3:34:50 2002 Delivered-To: freebsd-arch@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 3568437B419 for ; Tue, 9 Apr 2002 03:34:47 -0700 (PDT) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g39AYiA59670; Tue, 9 Apr 2002 03:34:44 -0700 (PDT) (envelope-from rizzo) Date: Tue, 9 Apr 2002 03:34:44 -0700 From: Luigi Rizzo To: Terry Lambert Cc: Nate Williams , arch@FreeBSD.ORG Subject: Re: proposed code: automatic setting of hostname from MAC address Message-ID: <20020409033444.B59548@iguana.icir.org> References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> <20020408235226.B57765@iguana.icir.org> <3CB2A989.6E09236C@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CB2A989.6E09236C@mindspring.com> User-Agent: Mutt/1.3.23i 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 Tue, Apr 09, 2002 at 01:42:49AM -0700, Terry Lambert wrote: > Luigi Rizzo wrote: > > The call to auto_set_hostname() in rc.conf will fetch the MAC address > > from the first ethernet card, > > I like the idea, except which etherent card is "first"? the first one listed by "ifconfig -l" :) In practice, in my databases i tend to put the MAC addresses of all cards installed, so the process is reasonably safe even if the probe order changes. Think only broke briefly when ifconfig stopped printing leading zeros in the MAC addresses, but this has been fixed now. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 4:53:21 2002 Delivered-To: freebsd-arch@freebsd.org Received: from pikachu.sys.atl.earthlink.net (pikachu.sys.atl.earthlink.net [199.174.117.37]) by hub.freebsd.org (Postfix) with ESMTP id B476137B416 for ; Tue, 9 Apr 2002 04:53:17 -0700 (PDT) Received: (from poirierg@localhost) by pikachu.sys.atl.earthlink.net (8.11.1/8.11.1) id g39BrHo33131 for freebsd-arch@freebsd.org; Tue, 9 Apr 2002 07:53:17 -0400 (EDT) (envelope-from poirierg) Date: Tue, 9 Apr 2002 07:53:17 -0400 (EDT) From: Greg Poirier Message-Id: <200204091153.g39BrHo33131@pikachu.sys.atl.earthlink.net> To: freebsd-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 subscribe freebsd-arch poirierg@corp.earthlink.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 8:50:26 2002 Delivered-To: freebsd-arch@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 156FF37B405 for ; Tue, 9 Apr 2002 08:50:12 -0700 (PDT) Received: from caddis.yogotech.com (yogotech.nokia.com [4.22.66.156]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id JAA22248; Tue, 9 Apr 2002 09:50:08 -0600 (MDT) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g39Fo4o03920; Tue, 9 Apr 2002 09:50:04 -0600 (MDT) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15539.3500.712066.51894@caddis.yogotech.com> Date: Tue, 9 Apr 2002 09:50:04 -0600 To: Luigi Rizzo Cc: Nate Williams , arch@FreeBSD.ORG Subject: Re: proposed code: automatic setting of hostname from MAC address In-Reply-To: <20020408235226.B57765@iguana.icir.org> References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> <20020408235226.B57765@iguana.icir.org> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) 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 > Nate, probably i did not explain it clearly. I used the stuff in PicoBSD, so I'm fairly comfortable with it. > As Garance says, the code i am proposing lets you use the same > configuration file (/etc/rc.conf) on multiple machines, instead of > having to customise it for each one. Right. It allows you to use the a custom configuration file that will allow you to configure multiple machines with the same configuration file, right? I don't like it because it's non-standard, and uses a completely non-standard configuration file. However, I don't have a better solution. What I did was rip out all of the code in my PicoBSD builds to use the stock 'rc.conf' stuff, and then I add a customized rc.conf for each different machine I build (by hand) that contains that machine's configuration. However, in my case, each machine has a slightly different configuration, so I need something more than a different ifconfig line, so my situation is obviously different than yours. (Replacing rc.conf is trivial by doing the copy && gunzip over top of the MFS version by sticking a compresses copy of the customized rc.conf on the floppy in a special directory as the examples in the past have done.) > The call to auto_set_hostname() in rc.conf will fetch the MAC address > from the first ethernet card, look it up in a database of > MAC<->hostname pairs (/etc/ethers, or /etc/hosts), and sets the > "hostname" and "ifconfig_foo0" shell variables accordingly. From > there on, rc.conf is absolutely the same as usual. Unless the box needs a different configuration. Basically, you're trying to batch configure the hosts using the exact same configuration files, but differentiating them by MAC address. This only works if you know the MAC addresses ahead of time, and in my case, this can change when a piece of hardware fails, etc... > This is not replacing the current scheme -- you can still choose > to put > > hostname="foo.bar" > ifconfig_ed0="inet 1.2.3.4 netmask 0xffffff00" > > in your rc.conf. But since this is often the only significant > difference among different rc.conf, having this sorted out > automatically can be very convenient. I wish this worked with PicoBSD, but it didn't. :( > + in a site that I know, the sysadmin manages a number of > FreeBSD boxes, and whenever an OS upgrade needs to be made, > he has to push around a number of configuration files. For > the most part, they are all the same except for rc.conf > (where the difference in most cases is limited to the setting > of "hostname" and "ifconfig_foo0", and possibly /etc/fstab. > > + for things such as PicoBSD images, or "rescue" floppy/CDs, > having this code lets you use the same exact media to > come up with the correct configuration on different boxes > > + (a bit less common, though still someone might do this) > for some time I used to carry my hard disk in a removable > frame and move it between my home and office machine. > Again this code would let the OS use the correct configuration in > the different places. > > Does it make more sense now ? Yes, but it's not quite as bullet-proof as you let on, since you still need to do all the MAC addresses ahead of time. So, if you replace an ethernet card, you have to build a new customized floppy anyways. It works well for fairly static configurations you know about ahead of time. However, in those cases, you still need N different floppies, so it's almost just as easy to create customized rc.conf files for each floppy. Just my .02 worth.... nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 9:27:17 2002 Delivered-To: freebsd-arch@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id DA09737B400 for ; Tue, 9 Apr 2002 09:27:13 -0700 (PDT) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g39GR8O63318; Tue, 9 Apr 2002 09:27:08 -0700 (PDT) (envelope-from rizzo) Date: Tue, 9 Apr 2002 09:27:08 -0700 From: Luigi Rizzo To: Nate Williams Cc: arch@FreeBSD.ORG Subject: Re: proposed code: automatic setting of hostname from MAC address Message-ID: <20020409092708.A63224@iguana.icir.org> References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> <20020408235226.B57765@iguana.icir.org> <15539.3500.712066.51894@caddis.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15539.3500.712066.51894@caddis.yogotech.com> User-Agent: Mutt/1.3.23i 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 Tue, Apr 09, 2002 at 09:50:04AM -0600, Nate Williams wrote: ... > Right. It allows you to use the a custom configuration file that will > allow you to configure multiple machines with the same configuration > file, right? > > I don't like it because it's non-standard, and uses a completely > non-standard configuration file. I frankly don't understand your objection. I am just proposing to add a few shell functions in the default scripts that users may decide to use if they like to, or just stick to the existing code. Why do you define it "non standard", and call "not standard" the config files ? + yes, in the picobsd version the MAC<->hostname mapping was in /etc/hosts, but this will be moved to /etc/ethers which is the standard place for this stuff; + the use of a "case ${hostname} .." in rc.conf is, yes, "non standard", but you don't have to use it, and as a matter of fact it is what lets you handle the "slightly different configuration" for each machine in a centralised place. > However, I don't have a better solution. What I did was rip out all of > the code in my PicoBSD builds to use the stock 'rc.conf' stuff, and then > I add a customized rc.conf for each different machine I build (by hand) > that contains that machine's configuration. However, in my case, each > machine has a slightly different configuration, so I need something more > than a different ifconfig line, so my situation is obviously different > than yours. ... cheers luigi -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 9:31:15 2002 Delivered-To: freebsd-arch@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id E3D3F37B417 for ; Tue, 9 Apr 2002 09:31:07 -0700 (PDT) Received: from caddis.yogotech.com (yogotech.nokia.com [4.22.66.156]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id KAA22657; Tue, 9 Apr 2002 10:31:05 -0600 (MDT) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g39GV2q04282; Tue, 9 Apr 2002 10:31:02 -0600 (MDT) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15539.5958.66973.551501@caddis.yogotech.com> Date: Tue, 9 Apr 2002 10:31:02 -0600 To: Luigi Rizzo Cc: Nate Williams , arch@FreeBSD.ORG Subject: Re: proposed code: automatic setting of hostname from MAC address In-Reply-To: <20020409092708.A63224@iguana.icir.org> References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> <20020408235226.B57765@iguana.icir.org> <15539.3500.712066.51894@caddis.yogotech.com> <20020409092708.A63224@iguana.icir.org> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) 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 > > Right. It allows you to use the a custom configuration file that will > > allow you to configure multiple machines with the same configuration > > file, right? > > > > I don't like it because it's non-standard, and uses a completely > > non-standard configuration file. > > I frankly don't understand your objection. I am just proposing to > add a few shell functions in the default scripts that users may > decide to use if they like to, or just stick to the existing > code. > > Why do you define it "non standard", and call "not standard" > the config files ? > + yes, in the picobsd version the MAC<->hostname mapping was in > /etc/hosts, but this will be moved to /etc/ethers which is the > standard place for this stuff; /etc/ethers is for determining a network mask, not for determining a host's IP address. Using it otherwise is non-standard. > + the use of a "case ${hostname} .." in rc.conf is, yes, "non standard", > but you don't have to use it, and as a matter of fact it is what lets > you handle the "slightly different configuration" for each machine > in a centralised place. /etc/rc.conf *is* the method for configuring each machine. You're changing what was previously a machine-specific file into a machine-independant file, totally changing the way things are done. (In a more confusing/less flexible way I might add.) > > However, I don't have a better solution. What I did was rip out all of > > the code in my PicoBSD builds to use the stock 'rc.conf' stuff, and then > > I add a customized rc.conf for each different machine I build (by hand) > > that contains that machine's configuration. However, in my case, each > > machine has a slightly different configuration, so I need something more > > than a different ifconfig line, so my situation is obviously different > > than yours. > ... Just because something is useful doesn't mean it should be added to FreeBSD. I believe your solution has very limited usefulness beyond your particular situation, and as such, shouldn't be added to FreeBSD. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 9:37:26 2002 Delivered-To: freebsd-arch@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 68DAC37B417 for ; Tue, 9 Apr 2002 09:37:22 -0700 (PDT) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g39GbHP63436; Tue, 9 Apr 2002 09:37:17 -0700 (PDT) (envelope-from rizzo) Date: Tue, 9 Apr 2002 09:37:17 -0700 From: Luigi Rizzo To: Nate Williams Cc: arch@FreeBSD.ORG Subject: Re: proposed code: automatic setting of hostname from MAC address Message-ID: <20020409093717.B63338@iguana.icir.org> References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> <20020408235226.B57765@iguana.icir.org> <15539.3500.712066.51894@caddis.yogotech.com> <20020409092708.A63224@iguana.icir.org> <15539.5958.66973.551501@caddis.yogotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15539.5958.66973.551501@caddis.yogotech.com> User-Agent: Mutt/1.3.23i 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 Tue, Apr 09, 2002 at 10:31:02AM -0600, Nate Williams wrote: ... > > Why do you define it "non standard", and call "not standard" > > the config files ? > > + yes, in the picobsd version the MAC<->hostname mapping was in > > /etc/hosts, but this will be moved to /etc/ethers which is the > > standard place for this stuff; > > /etc/ethers is for determining a network mask, not for determining a > host's IP address. Using it otherwise is non-standard. aren't you mistaking it for /etc/networks ? > man 5 ethers Formatting page, please wait...Done. ETHERS(5) FreeBSD File Formats Manual ETHERS(5) NAME ethers - ethernet address database DESCRIPTION The ethers database contains information regarding known 48-bit ethernet addresses of hosts on an Internetwork. The data is stored in a file called /etc/ethers in the following format: ethernet-address fully-qualified-host-name Items are separated by any number of blanks and/or tab characters. A ``#'' at the start of a line indicates the beginning of a comment that extends to the end of the line. A ``+'' at the start of a line will cause the ethers(3) library functions to use data stored in the NIS(4) ethers.byname and ethers.byaddr maps in addition to the data in the /etc/ethers file. An ethernet address is expressed in ASCII form as "x:x:x:x:x:x" where x is a hexadecimal value between 0x00 and 0xFF. The address values should be in network order. Hostnames specified in the /etc/ethers database should correspond to entries in the hosts(5) file. > /etc/rc.conf *is* the method for configuring each machine. You're > changing what was previously a machine-specific file into a > machine-independant file, totally changing the way things are done. (In > a more confusing/less flexible way I might add.) > > > > However, I don't have a better solution. What I did was rip out all of point taken. We disagree, but that's the beauty of diversity :) cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 9:38:51 2002 Delivered-To: freebsd-arch@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 12DA937B405 for ; Tue, 9 Apr 2002 09:38:42 -0700 (PDT) Received: from caddis.yogotech.com (yogotech.nokia.com [4.22.66.156]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id KAA22750; Tue, 9 Apr 2002 10:38:39 -0600 (MDT) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g39Gcbf04335; Tue, 9 Apr 2002 10:38:37 -0600 (MDT) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15539.6413.325758.698515@caddis.yogotech.com> Date: Tue, 9 Apr 2002 10:38:37 -0600 To: Luigi Rizzo Cc: Nate Williams , arch@FreeBSD.ORG Subject: Re: proposed code: automatic setting of hostname from MAC address In-Reply-To: <20020409093717.B63338@iguana.icir.org> References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> <20020408235226.B57765@iguana.icir.org> <15539.3500.712066.51894@caddis.yogotech.com> <20020409092708.A63224@iguana.icir.org> <15539.5958.66973.551501@caddis.yogotech.com> <20020409093717.B63338@iguana.icir.org> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) 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 > > > Why do you define it "non standard", and call "not standard" > > > the config files ? > > > + yes, in the picobsd version the MAC<->hostname mapping was in > > > /etc/hosts, but this will be moved to /etc/ethers which is the > > > standard place for this stuff; > > > > /etc/ethers is for determining a network mask, not for determining a > > host's IP address. Using it otherwise is non-standard. > > aren't you mistaking it for /etc/networks ? You are indeed correct. /etc/ethers does do what you've asked. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 9:44:56 2002 Delivered-To: freebsd-arch@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id A28F037B417 for ; Tue, 9 Apr 2002 09:44:52 -0700 (PDT) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020409164452.KQLE1143.rwcrmhc51.attbi.com@bmah.dyndns.org>; Tue, 9 Apr 2002 16:44:52 +0000 Received: from intruder.bmah.org (localhost [IPv6:::1]) by bmah.dyndns.org (8.12.2/8.12.2) with ESMTP id g39Gipt2032319; Tue, 9 Apr 2002 09:44:51 -0700 (PDT) (envelope-from bmah@intruder.bmah.org) Received: (from bmah@localhost) by intruder.bmah.org (8.12.2/8.12.2/Submit) id g39GilBw032318; Tue, 9 Apr 2002 09:44:47 -0700 (PDT) Message-Id: <200204091644.g39GilBw032318@intruder.bmah.org> X-Mailer: exmh version 2.5+ 20020404 with nmh-1.0.4 To: "Peter Rader Alias Nocturne" Subject: Re: witch platform i have In-reply-to: <000901c1df7e$d6a9a540$903d07d5@q5c0d3> References: <000901c1df7e$d6a9a540$903d07d5@q5c0d3> Comments: In-reply-to "Peter Rader Alias Nocturne" message dated "Tue, 09 Apr 2002 06:27:18 +0200." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.org X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Apr 2002 09:44:47 -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 If memory serves me right, "Peter Rader Alias Nocturne" wrote: > i dont know, if i need i386 or Alpha > i have an Cyrix; meen Alpha the old 100Mhz Processor of AMD? [This question doesn't belong on arch@, which is for architectural discussions. You probably want to send questions like this to questions@freebsd.org.] Alpha refers to a line of processors that are most notably seen in workstations/servers from Digital Equipment Corporation (now Compaq). Your Cyrix processor should be supported by the i386 port of FreeBSD. Good luck, Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 13: 6:48 2002 Delivered-To: freebsd-arch@freebsd.org Received: from grant.org (grant.org [206.190.164.98]) by hub.freebsd.org (Postfix) with ESMTP id 3F35737B404 for ; Tue, 9 Apr 2002 13:06:37 -0700 (PDT) Received: (from devon@localhost) by grant.org (8.11.6/8.11.6) id g39K6Vc83785; Tue, 9 Apr 2002 16:06:31 -0400 (EDT) (envelope-from devon) Date: Tue, 9 Apr 2002 16:06:31 -0400 (EDT) Message-Id: <200204092006.g39K6Vc83785@grant.org> From: FreeBSD@Jovi.Net To: freebsd-arch@FreeBSD.ORG In-reply-to: <200204091802.g39I2tk39958@freefall.freebsd.org> (nsayer@FreeBSD.org) Subject: Re: kern/33904: secure mode bug References: <200204091802.g39I2tk39958@freefall.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 Bug is in the code. Perpetuated by policy error. Silent DWIM/failure is never acceptable policy in any API. Suggest this kludge be documented as a temporary security measure with a specific termination date, e.g. Monday 6 February 2006 to give app writers four years to fix their code after which the emergency broken kernel can be restored to normal. Cheers --Devon /"\ \ / ASCII Ribbon Campaign X Help Cure HTML Mail / \ PS: I do not advocate any specific solution to the current defect, there are many choices and I'm sure I haven't thought of them all, here's one: Accept small changes, reject large ones. Giving the caller half a time change is like giving the mom half a baby. Apps can learn to ask for small time changes. Some guiding principles: * API quality is paramount * Silent failure is never ok * Silent DWIM is even worse * necessity is not divinity (repent for we are all kludgers) Most C coders ignore error status anyway, maybe a clean UNIX system is a lost cause, still no excuse for the current DWIM hack, pure poison to allow UI kludges in the API, blurring the concept of success or failure. Date: Tue, 9 Apr 2002 11:02:55 -0700 (PDT) From: Synopsis: secure mode bug State-Changed-From-To: analyzed->feedback State-Changed-By: nsayer State-Changed-When: Tue Apr 9 11:01:58 PDT 2002 State-Changed-Why: This is not a problem with the code, but rather the documentation. I've asked for help in getting the man page fixed, but not heard anything back. http://www.freebsd.org/cgi/query-pr.cgi?pr=33904 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 18:53:20 2002 Delivered-To: freebsd-arch@freebsd.org Received: from softweyr.com (softweyr.com [65.88.244.127]) by hub.freebsd.org (Postfix) with ESMTP id 86DFB37B416 for ; Tue, 9 Apr 2002 18:53:10 -0700 (PDT) Received: from nextgig-5.customer.nethere.net ([209.132.102.165] helo=softweyr.com) by softweyr.com with esmtp (Exim 3.35 #1) id 16v7I3-000EqU-00; Tue, 09 Apr 2002 19:52:51 -0600 Message-ID: <3CB37FAF.DE67363E@softweyr.com> Date: Tue, 09 Apr 2002 17:56:31 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: Jeff Roberson , arch@freebsd.org Subject: Re: Removing limits from malloc(9) References: <20020408041726.U53877-100000@mail.chesapeake.net> Content-Type: text/plain; charset=us-ascii 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 Dag-Erling Smorgrav wrote: > > Jeff Roberson writes: > > The last bit that is missing before we can call malloc/free w/o Giant is > > the malloc_type statistics. Currently there is nothing really protecting > > them. There really is no lock that they can conveniently live under. I > > have a few options. The one that I'm leaning towards is only enabling > > malloc_type statistics if INVARIANTS is compiled in. Then I could make > > one lock per malloc_type. The reason this shouldn't be the default is > > because it creates a single point of contention which is in sharp contrast > > with the rest of the allocator. > > It's still a lot better than Giant, and it's a leaf lock so there > shouldn't be any worries about reversal. I'd go for it if I were you. Can they be updated with an atomic increment? For statistics like this, being off by 1 or 2 on read isn't so important as long as you don't miss a bunch of counts. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 19:18: 3 2002 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 E1D9637B404 for ; Tue, 9 Apr 2002 19:17:58 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id g39JY3018631; Tue, 9 Apr 2002 20:34:03 +0100 (BST) (envelope-from nik) Date: Tue, 9 Apr 2002 20:34:03 +0100 From: Nik Clayton To: Luigi Rizzo Cc: Nate Williams , arch@FreeBSD.ORG Subject: Re: proposed code: automatic setting of hostname from MAC address Message-ID: <20020409203403.U30474@canyon.nothing-going-on.org> References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> <20020408235226.B57765@iguana.icir.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5Dr6Wqe9hdyl7LAI" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020408235226.B57765@iguana.icir.org>; from rizzo@icir.org on Mon, Apr 08, 2002 at 11:52:26PM -0700 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 --5Dr6Wqe9hdyl7LAI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 08, 2002 at 11:52:26PM -0700, Luigi Rizzo wrote: > Nate, probably i did not explain it clearly. > s Garance says, the code i am proposing lets you use the same > configuration file (/etc/rc.conf) on multiple machines, instead > of having to customise it for each one. >=20 > The call to auto_set_hostname() in rc.conf will fetch the MAC address > from the first ethernet card, look it up in a database of > MAC<->hostname pairs (/etc/ethers, or /etc/hosts), and sets the > "hostname" and "ifconfig_foo0" shell variables accordingly. From > there on, rc.conf is absolutely the same as usual. Why not do this in /etc/rc.conf.local, which can be local to each=20 machine, with /etc/rc.conf being sitewide? I've done that before and it works well. 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 --- .\._/= _) --5Dr6Wqe9hdyl7LAI 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 iEYEARECAAYFAjyzQioACgkQk6gHZCw343VWzACdHKsk4YcSzxypGITpWz6WMxCP /IgAni8mVcw3pFgnFutDc5arMX9tduhH =VF6c -----END PGP SIGNATURE----- --5Dr6Wqe9hdyl7LAI-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 19:18:27 2002 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 6ADFC37B41B for ; Tue, 9 Apr 2002 19:18:21 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id g39JWlZ18621; Tue, 9 Apr 2002 20:32:47 +0100 (BST) (envelope-from nik) Date: Tue, 9 Apr 2002 20:32:46 +0100 From: Nik Clayton To: Garance A Drosihn Cc: Nate Williams , Luigi Rizzo , arch@FreeBSD.ORG Subject: Re: proposed code: automatic setting of hostname from MAC address Message-ID: <20020409203246.T30474@canyon.nothing-going-on.org> References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="qUsYCxAE223BCwdt" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from drosih@rpi.edu on Mon, Apr 08, 2002 at 08:45:02PM -0400 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 --qUsYCxAE223BCwdt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 08, 2002 at 08:45:02PM -0400, Garance A Drosihn wrote: > Hmm. I did not understand Luigi's reference to /etc/hosts, but > I had assumed that the feature was similar to how MacOS 10 works. > The machine gets an IP address via DHCP (for instance), and > then sets the machine's hostname based on what DNS says is the > hostname for that IP address. That works out pretty well. Not directly relevant to the topic at hand, but FreeBSD does this too. Just make sure that you that you don't have a 'hostname' line in=20 /etc/rc.conf and dhclient will pick up whatever hostname is offered by the DHCP server. 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 --- .\._/= _) --qUsYCxAE223BCwdt 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 iEYEARECAAYFAjyzQd0ACgkQk6gHZCw343XFqwCghQbZu4TXoRva8XiFsp4hK2Qd +hsAn1SkrvoFb9iqmKlILKFqZb9WvCVr =86gY -----END PGP SIGNATURE----- --qUsYCxAE223BCwdt-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Apr 9 22:51:50 2002 Delivered-To: freebsd-arch@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 6832437B419; Tue, 9 Apr 2002 22:51:48 -0700 (PDT) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g3A5pmF68438; Tue, 9 Apr 2002 22:51:48 -0700 (PDT) (envelope-from rizzo) Date: Tue, 9 Apr 2002 22:51:48 -0700 From: Luigi Rizzo To: Nik Clayton Cc: Nate Williams , arch@FreeBSD.ORG Subject: Re: proposed code: automatic setting of hostname from MAC address Message-ID: <20020409225148.A68389@iguana.icir.org> References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> <20020408235226.B57765@iguana.icir.org> <20020409203403.U30474@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020409203403.U30474@canyon.nothing-going-on.org> User-Agent: Mutt/1.3.23i 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 Tue, Apr 09, 2002 at 08:34:03PM +0100, Nik Clayton wrote: ... > > The call to auto_set_hostname() in rc.conf will fetch the MAC address > > from the first ethernet card, look it up in a database of > > MAC<->hostname pairs (/etc/ethers, or /etc/hosts), and sets the > > "hostname" and "ifconfig_foo0" shell variables accordingly. From > > there on, rc.conf is absolutely the same as usual. > > Why not do this in /etc/rc.conf.local, which can be local to each > machine, with /etc/rc.conf being sitewide? rc.conf can be local as well. My whole point is try to have a single config file as opposed to 100 of them! cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Apr 10 2:15:26 2002 Delivered-To: freebsd-arch@freebsd.org Received: from infinitive.futureperfectcorporation.com (infinitive.futureperfectcorporation.com [196.25.137.68]) by hub.freebsd.org (Postfix) with SMTP id D5BA637B41B for ; Wed, 10 Apr 2002 02:15:18 -0700 (PDT) Received: (qmail 66615 invoked by uid 0); 10 Apr 2002 09:15:15 -0000 Received: from unknown (HELO gerund.futureperfectcorporation.com) (196.25.137.65) by infinitive.futureperfectcorporation.com with DES-CBC3-SHA encrypted SMTP; 10 Apr 2002 09:15:14 -0000 Received: (qmail 48075 invoked by uid 1001); 10 Apr 2002 09:17:03 -0000 Date: Wed, 10 Apr 2002 11:17:03 +0200 From: Neil Blakey-Milner To: Luigi Rizzo Cc: Nik Clayton , Nate Williams , arch@FreeBSD.ORG Subject: non-variables in rc.conf (Re: proposed code: automatic setting of hostname from MAC address) Message-ID: <20020410091703.GA47576@mithrandr.moria.org> References: <20020407035941.B37911@iguana.icir.org> <15538.12905.744914.71228@caddis.yogotech.com> <20020408235226.B57765@iguana.icir.org> <20020409203403.U30474@canyon.nothing-going-on.org> <20020409225148.A68389@iguana.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020409225148.A68389@iguana.icir.org> User-Agent: Mutt/1.3.27i Organization: iTouch Labs X-Operating-System: FreeBSD 4.3-RELEASE i386 X-URL: http://mithrandr.moria.org/nbm/ 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 Tue 2002-04-09 (22:51), Luigi Rizzo wrote: > On Tue, Apr 09, 2002 at 08:34:03PM +0100, Nik Clayton wrote: > ... > > > The call to auto_set_hostname() in rc.conf will fetch the MAC address > > > from the first ethernet card, look it up in a database of > > > MAC<->hostname pairs (/etc/ethers, or /etc/hosts), and sets the > > > "hostname" and "ifconfig_foo0" shell variables accordingly. From > > > there on, rc.conf is absolutely the same as usual. > > > > Why not do this in /etc/rc.conf.local, which can be local to each > > machine, with /etc/rc.conf being sitewide? > > rc.conf can be local as well. My whole point is try to have > a single config file as opposed to 100 of them! Maybe I'm being silly, but I was hoping the whole rc.conf system could move from being "sh" and become just variables in preparation for some as-yet-undefined changes to configuration that may be required in future. In fact, I wrote the first step to do this and posted it a while back (can't find it at the moment. The file name was rc.sourceconf or something). This move would make sysinstall and potential future configuration tools much easier to maintain and write, since the entire "rc configuration" can be handled by a C library (these exist already, iirc). The alternative is to make the configuration tool include sh's functionality, or call it externally. Future changes (the as-yet-undefined bit) might be per-hostname/ip configuration at around 6.0 era (or even 5.0, but I'm not in a hurry). Abstracting the configuration away from "shell scripts and functions" would allow us to pull the configuration in from other locations in the "backend". The one basic example I did perform was in the order of (replace \ns with real enters): eval `echo 'g/^[:space:]*$/d\ng/^#/d\ng/$/s//;/\ng/./' | ed -s \!'cat /etc/rc.alternate.conf'` Anyway, assume that we can get our network configured beforehand, and we can then use ldap, NIS, or whatever (netinfo?) to get our configuration. In Luigi's case, he would write a new backend that does some magic to set (or overwrite) variables based on hostname or ip. Something that grabs all variables prefixed with the hostname, and removes the prefix, and then sets the variables. It could even be written in C. Or maybe I'm thinking in entirely the wrong direction? Neil -- Neil Blakey-Milner nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Apr 10 2:18:57 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by hub.freebsd.org (Postfix) with ESMTP id F19B437B41C for ; Wed, 10 Apr 2002 02:18:51 -0700 (PDT) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id g3A9Iio01898; Wed, 10 Apr 2002 05:18:44 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Wed, 10 Apr 2002 05:18:44 -0400 (EDT) From: Jeff Roberson To: Wes Peters Cc: Dag-Erling Smorgrav , Subject: Re: Removing limits from malloc(9) In-Reply-To: <3CB37FAF.DE67363E@softweyr.com> Message-ID: <20020410051245.A87494-100000@mail.chesapeake.net> 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 Tue, 9 Apr 2002, Wes Peters wrote: > Dag-Erling Smorgrav wrote: > > > > It's still a lot better than Giant, and it's a leaf lock so there > > shouldn't be any worries about reversal. I'd go for it if I were you. > > Can they be updated with an atomic increment? For statistics like this, > being off by 1 or 2 on read isn't so important as long as you don't miss > a bunch of counts. > An atomic increment would still cause cache thrashing. I considered doing per cpu queues for the statistics and then aggregating them when someone wants to report them. This doesn't work if you want to do limits though, since you'd need to check all of the statistics caches at each call. I suppose that this is really good enough at this point. Maybe when we're running on 64 or 128 CPU systems the cache thrashing will hurt enough to get rid of limits. :-) Until then I'll just leave them the way they are and wrap the whole thing in a per malloc_type mutex. This should sufficiently reduce contention and make malloc(9) totally mp safe. Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Apr 11 4: 2:36 2002 Delivered-To: freebsd-arch@freebsd.org Received: from fw.wemm.org (12-232-135-171.client.attbi.com [12.232.135.171]) by hub.freebsd.org (Postfix) with ESMTP id 2FC3C37B400 for ; Thu, 11 Apr 2002 04:02:33 -0700 (PDT) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (8.11.6/8.11.6) with ESMTP id g3BB2WQ28154 for ; Thu, 11 Apr 2002 04:02:33 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (Postfix) with ESMTP id D25C739EA; Thu, 11 Apr 2002 04:02:33 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Wes Peters Cc: Dag-Erling Smorgrav , Jeff Roberson , arch@FreeBSD.ORG Subject: Re: Removing limits from malloc(9) In-Reply-To: <3CB37FAF.DE67363E@softweyr.com> Date: Thu, 11 Apr 2002 04:02:33 -0700 From: Peter Wemm Message-Id: <20020411110233.D25C739EA@overcee.wemm.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 Wes Peters wrote: > Dag-Erling Smorgrav wrote: > > > > Jeff Roberson writes: > > > The last bit that is missing before we can call malloc/free w/o Giant is > > > the malloc_type statistics. Currently there is nothing really protecting > > > them. There really is no lock that they can conveniently live under. I > > > have a few options. The one that I'm leaning towards is only enabling > > > malloc_type statistics if INVARIANTS is compiled in. Then I could make > > > one lock per malloc_type. The reason this shouldn't be the default is > > > because it creates a single point of contention which is in sharp contras t > > > with the rest of the allocator. > > > > It's still a lot better than Giant, and it's a leaf lock so there > > shouldn't be any worries about reversal. I'd go for it if I were you. > > Can they be updated with an atomic increment? For statistics like this, > being off by 1 or 2 on read isn't so important as long as you don't miss > a bunch of counts. You know, at work the one and only time we ever check malloc limits is when we discover that a transient load spike caused it to hit some limit and it crashed or locked up as a result. When the machine crashes or deadlocks automatically as a result of hitting the limits, one has to wonder what the point is? It is crashing in order to protect us from what? crashing? Personally, I'd be happy with counts being done per-cpu (to avoid contention) and aggregated periodically (eg: at vmstat -m time). And to hell with the limits. But that's just me. :-) Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Apr 11 22:58:41 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by hub.freebsd.org (Postfix) with ESMTP id 510D037B416 for ; Thu, 11 Apr 2002 22:58:39 -0700 (PDT) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id g3C5wAN67249; Fri, 12 Apr 2002 01:58:11 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Fri, 12 Apr 2002 01:58:10 -0400 (EDT) From: Jeff Roberson To: Peter Wemm Cc: Wes Peters , Dag-Erling Smorgrav , Subject: Re: Removing limits from malloc(9) In-Reply-To: <20020411110233.D25C739EA@overcee.wemm.org> Message-ID: <20020412015551.M42805-100000@mail.chesapeake.net> 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 Thu, 11 Apr 2002, Peter Wemm wrote: > Personally, I'd be happy with counts being done per-cpu (to avoid > contention) and aggregated periodically (eg: at vmstat -m time). And to > hell with the limits. But that's just me. :-) > This is more along the lines of what I was looking for. I don't like the limits but I wasn't sure if anyone found them to be useful. So far I have heard 2 votes for getting rid of limits, and no votes for keeping them. Would anyone else care to vote? Thanks, Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Apr 12 10:20:15 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 418AE37B416 for ; Fri, 12 Apr 2002 10:20:12 -0700 (PDT) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g3CHK013410930; Fri, 12 Apr 2002 13:20:00 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20020412015551.M42805-100000@mail.chesapeake.net> References: <20020412015551.M42805-100000@mail.chesapeake.net> Date: Fri, 12 Apr 2002 13:19:59 -0400 To: Jeff Roberson From: Garance A Drosihn Subject: Re: Removing limits from malloc(9) Cc: arch@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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 At 1:58 AM -0400 4/12/02, Jeff Roberson wrote: >This is more along the lines of what I was looking for. I >don't like the limits but I wasn't sure if anyone found them >to be useful. So far I have heard 2 votes for getting rid >of limits, and no votes for keeping them. My earlier comment was meant to be a weak vote for the limits. "weak" in the sense that I would like to keep them, but that I do not feel very strongly about it. Consider it more like half-a-vote for them. Even with that, I wouldn't mind if limits were only available as a malloc option (set via /etc/malloc.conf) and not done by default. Perhaps just file these comments under "nice ideas to do someday", and just ignore them for now... -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Apr 12 10:30:58 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by hub.freebsd.org (Postfix) with ESMTP id 0955A37B427 for ; Fri, 12 Apr 2002 10:30:38 -0700 (PDT) Received: (qmail 10736 invoked from network); 12 Apr 2002 17:30:36 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail16.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 12 Apr 2002 17:30:36 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g3CHVRv61407; Fri, 12 Apr 2002 13:31:27 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 12 Apr 2002 13:29:50 -0400 (EDT) From: John Baldwin To: Garance A Drosihn Subject: Re: Removing limits from malloc(9) Cc: arch@FreeBSD.ORG, Jeff Roberson 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 12-Apr-2002 Garance A Drosihn wrote: > At 1:58 AM -0400 4/12/02, Jeff Roberson wrote: >>This is more along the lines of what I was looking for. I >>don't like the limits but I wasn't sure if anyone found them >>to be useful. So far I have heard 2 votes for getting rid >>of limits, and no votes for keeping them. > > My earlier comment was meant to be a weak vote for the limits. > "weak" in the sense that I would like to keep them, but that > I do not feel very strongly about it. Consider it more like > half-a-vote for them. Even with that, I wouldn't mind if limits > were only available as a malloc option (set via /etc/malloc.conf) > and not done by default. These are limits for kernel malloc(9), not userland malloc(3). These two malloc's are entirely unrelated. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "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 Fri Apr 12 11:19: 9 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id B7A4737B400; Fri, 12 Apr 2002 11:19:04 -0700 (PDT) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g3CIJ213431960; Fri, 12 Apr 2002 14:19:03 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Fri, 12 Apr 2002 14:19:01 -0400 To: John Baldwin From: Garance A Drosihn Subject: Re: Removing limits from malloc(9) Cc: arch@FreeBSD.org, Jeff Roberson Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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 At 1:29 PM -0400 4/12/02, John Baldwin wrote: >On 12-Apr-2002 Garance A Drosihn wrote: >> At 1:58 AM -0400 4/12/02, Jeff Roberson wrote: >>>This is more along the lines of what I was looking for. I >>>don't like the limits but I wasn't sure if anyone found them >>>to be useful. So far I have heard 2 votes for getting rid >>>of limits, and no votes for keeping them. >> >> My earlier comment was meant to be a weak vote for the limits. >> "weak" in the sense that I would like to keep them, but that >> I do not feel very strongly about it. Consider it more like >> half-a-vote for them. Even with that, I wouldn't mind if limits >> were only available as a malloc option (set via /etc/malloc.conf) >> and not done by default. > >These are limits for kernel malloc(9), not userland malloc(3). >These two malloc's are entirely unrelated. Ah. Okay, reduce my vote to 1/10th of a vote for limits... :-) -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Apr 13 20:48: 6 2002 Delivered-To: freebsd-arch@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6D76237B405; Sat, 13 Apr 2002 20:48:00 -0700 (PDT) Received: (from scottl@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g3E3m0767698; Sat, 13 Apr 2002 20:48:00 -0700 (PDT) (envelope-from scottl) Date: Sat, 13 Apr 2002 20:48:00 -0700 (PDT) From: Message-Id: <200204140348.g3E3m0767698@freefall.freebsd.org> To: freebsd-arch@freebsd.org, freebsd-fs@freebsd.org Subject: Universal Disk Format (UDF) filesystem for FreeBSD 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 All, Available from http://people.freebsd.org/~scottl/udf are patches for a UDF filesystem driver for FreeBSD. UDF is the filesystem used for packet-written CD-RW's, and is found on most commercial DVD-Video disks. These patches allow a FreeBSD 5-CURRENT system to mount read-only a disk formatted with this filesystem. Although the UDF standard also supports packet-written CD-R, these patches do not implement this functionality yet. Read-write support is also not implemented yet, but work will begin shortly on it. Patches for FreeBSD 4-STABLE are maintained by Jeroen Ruigrok and can be found at http://www.softweyr.com/asmodai/projects/udf. I encourage anyone to try these patches out and provide feedback. They are the product of a year of free-time develpment and have been tested against disks created with Roxio's DirectCD and Nero's InCD packages. I also plan to commit these patches to the FreeBSD CVS repository soon. Scott Long To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message