From owner-freebsd-arch@FreeBSD.ORG Sun Mar 27 04:20:54 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6054D106566B for ; Sun, 27 Mar 2011 04:20:54 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [65.120.238.197]) by mx1.freebsd.org (Postfix) with ESMTP id 3C9F68FC08 for ; Sun, 27 Mar 2011 04:20:53 +0000 (UTC) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.4/8.14.1) with ESMTP id p2R49hq5081052 for ; Sat, 26 Mar 2011 21:09:43 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.14.4/8.13.4/Submit) id p2R49h9e081051; Sat, 26 Mar 2011 21:09:43 -0700 (PDT) Date: Sat, 26 Mar 2011 21:09:43 -0700 (PDT) From: Matthew Dillon Message-Id: <201103270409.p2R49h9e081051@apollo.backplane.com> To: freebsd-arch@freebsd.org References: <20110323200200.GA85810@freebsd.org> <201103232050.p2NKov4g017463@lurza.secnetix.de> <4D8A7976.5090103@freebsd.org> <20110323232209.GA15486@freebsd.org> <20110324083048.60862a0f@ernst.jennejohn.org> <20110324214320.K1149@besplex.bde.org> Subject: Re: kernel memory checks on boot vs. boot time X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2011 04:20:54 -0000 In DFly I just changed to code to check one word per 64KB instead of one word per 4KB, which cuts the time down by a factor of 16. At least some basic 'is this actually memory' test should probably still be done. Probing 64G of ram was really annoying before I made that change. Another solution would be to use a much larger mmu mapping, like a DMAP style mapping. Iterating the dram isn't going to be fast no matter what since each test requires a full RAS cycle anyway. I didn't try this approach but it would be easier to code (treating the page directory entry as a mapping cache for multiple tests). Adding programmable bells and whistles would be overkill, and high-end machines shouldn't require a tunable bypass to boot reasonably anyhow. -Matt From owner-freebsd-arch@FreeBSD.ORG Sun Mar 27 08:27:46 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9DEA106564A for ; Sun, 27 Mar 2011 08:27:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 7C1478FC16 for ; Sun, 27 Mar 2011 08:27:46 +0000 (UTC) Received: by wwc33 with SMTP id 33so2712496wwc.31 for ; Sun, 27 Mar 2011 01:27:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=pQzvexMvz/kfTx78tIfqetZ9MkrX7mbz1gdwbt3qgAs=; b=udKIKaYo6kuVifGxHd00j9S3M8XYkJibeADFI8vTLyTK49pOvEw2Aawk8Qz0Yp0zUG esNcxwWlN98/o4YUdrSmjJIJS+YDz7E8akO8f22IBmYH2GM5tCAi6A3iQtOVqCYc8eBn JTXkHUGLXN7dPkFXOe+7Qh0cMOizoi7g8e2k0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=PdLBkUv8VrcXVag0EmuI5nC7jI+dCwVdinzmR1V1uFTQwsC4M87vgRfIw4S6BokSyE QF6X5vG/1q5MGpbP1uJ+NWLb2wsBKHL1RN1La62l+7wgAA68pAuxHkCNm2Mq4kOcDjqC 22dan4etxHREzY8V/BoumBSmMjiS5l+JwEbZI= MIME-Version: 1.0 Received: by 10.227.196.10 with SMTP id ee10mr2672187wbb.209.1301213129074; Sun, 27 Mar 2011 01:05:29 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.227.135.137 with HTTP; Sun, 27 Mar 2011 01:05:29 -0700 (PDT) In-Reply-To: <20110324214320.K1149@besplex.bde.org> References: <20110323200200.GA85810@freebsd.org> <201103232050.p2NKov4g017463@lurza.secnetix.de> <4D8A7976.5090103@freebsd.org> <20110323232209.GA15486@freebsd.org> <20110324083048.60862a0f@ernst.jennejohn.org> <20110324214320.K1149@besplex.bde.org> Date: Sun, 27 Mar 2011 16:05:29 +0800 X-Google-Sender-Auth: piOPvdwDMRGt8BMgZHpVXZGBKtg Message-ID: From: Adrian Chadd To: Bruce Evans Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-arch@freebsd.org Subject: Re: kernel memory checks on boot vs. boot time X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2011 08:27:47 -0000 On 24 March 2011 19:26, Bruce Evans wrote: > Me too. However, I liked userconfig and even the semi-graphical visual > userconfig in FreeBSD-[2-4]. These were correctly placed from my point > of view (in the kernel), and were optional so not using them was > supported. I actually miss this. I know you dislike bootloaders, but has anyone written up something like this for FreeBSD in loader FICL? Adrian From owner-freebsd-arch@FreeBSD.ORG Sun Mar 27 12:43:31 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 607DE106567A for ; Sun, 27 Mar 2011 12:43:31 +0000 (UTC) (envelope-from pr@infopress.spb.ru) Received: from de1.webtraffic.ru (de1.playnext.net [91.194.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id E579E8FC21 for ; Sun, 27 Mar 2011 12:43:30 +0000 (UTC) Received: from KaplijaLudmila (unknown [178.89.128.27]) by de1.webtraffic.ru (Postfix) with ESMTP id 18C24AB8295 for ; Sun, 27 Mar 2011 15:59:18 +0400 (MSD) From: "Kaplija Ludmila" To: freebsd-arch@freebsd.org Content-Type: text/plain; charset="UTF-8" Date: Sun, 27 Mar 2011 15:19:45 +0300 Message-Id: <20110327115919.18C24AB8295@de1.webtraffic.ru> Subject: Nopelni saveejo daavanu karti jau driz!... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kaplija Ludmila List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2011 12:43:31 -0000 Virtualais edienu gatavotaajs ienak ari juusu majaas (dzivokli) - pagatavo burgerus savaa datora , bet notiesaa tos realaa kafejniicaa! http://www.deliver-guaanty.ca.pn/xks5.html - tur uzzinaasi siikaak! From owner-freebsd-arch@FreeBSD.ORG Mon Mar 28 07:51:07 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E37DF1065673 for ; Mon, 28 Mar 2011 07:51:07 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 79DD48FC0A for ; Mon, 28 Mar 2011 07:51:07 +0000 (UTC) Received: by wyf23 with SMTP id 23so3048092wyf.13 for ; Mon, 28 Mar 2011 00:51:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=LK66q2mTMqJ+5MUeh1eDTF/q2SsLmRPk8J/BsYniy4o=; b=hXU3E6Os0ccXLbr61FuWasOApDNJM6F1OdAGsB5rKmzOO8m2faGpdRaBDf1DmQf8a9 U9GBNq93hixYwsc0HDUge1mfk99Q79MoHG2iYOH3wAT4VVo9QLrADgL2AJN5FcCbFENF lxFQe2hXX6CkxQUFd5CmypLv8owY9/+KqhIxw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=gIvRTf11Xyj4+UYAr2HV2PMOgbE3izSMwRcw8Dr4Eu0iyQQ7U4c9ZWybT0nh9kjk2L zrClOuSZBxcO5IYbPwzoRW7YoQ2AqdPUncx6LKTeT7L4D/EYzu0oPEL3b/NtrsVEeQ1F fsExEQ4DzOkY8+ebJgoF/ASltAgxTSjuohMm4= MIME-Version: 1.0 Received: by 10.227.131.9 with SMTP id v9mr3568749wbs.6.1301298666183; Mon, 28 Mar 2011 00:51:06 -0700 (PDT) Received: by 10.227.135.137 with HTTP; Mon, 28 Mar 2011 00:51:06 -0700 (PDT) In-Reply-To: References: Date: Mon, 28 Mar 2011 15:51:06 +0800 Message-ID: From: Adrian Chadd To: freebsd-arch@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Fwd: heads-up: breaking up ath (back) into sub-devices X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2011 07:51:08 -0000 Forwarded here in case -arch wants to comment. Adrian ---------- Forwarded message ---------- From: Adrian Chadd Date: 28 March 2011 15:48 Subject: heads-up: breaking up ath (back) into sub-devices To: freebsd-current Hi all, I'd like to split the ath driver back up into some of its sub-components in -HEAD before 9.0-RELEASE is done. Those components are: * ath (the BSD/net80211 facing interface itself) * ath_hal (hardware layer) * ath_rate_* (the rate control modules) * ath_pci (the ath<->PCI glue) Since I'm planning on supporting embedded devices as well as PCI/PCIe devices, I'm going to split out ath_pci from ath. I'll then introduce an ath_ahb device for embedded atheros radios hanging off the AHB bus. I'd also like to split out the HAL and rate control modules too in preparation for some later work. Since there's likely going to be some alternative rate control modules when 11n pops up, I'd like to make it easy for people to test the various ones out without having to continually recompile the whole ath driver itself. It also makes doing some current and legacy embedded systems development quite a bit easier. This will change kernel config files in -HEAD and thus 9.0-RELEASE. Please let me know if you have any issues with this. Thanks, Adrian From owner-freebsd-arch@FreeBSD.ORG Mon Mar 28 20:30:29 2011 Return-Path: Delivered-To: FreeBSD-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E5E71065672 for ; Mon, 28 Mar 2011 20:30:29 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from hapkido.dreamhost.com (hapkido.dreamhost.com [66.33.216.122]) by mx1.freebsd.org (Postfix) with ESMTP id 34B1D8FC12 for ; Mon, 28 Mar 2011 20:30:29 +0000 (UTC) Received: from homiemail-a36.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by hapkido.dreamhost.com (Postfix) with ESMTP id A143A17AB61 for ; Mon, 28 Mar 2011 13:01:10 -0700 (PDT) Received: from homiemail-a36.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a36.g.dreamhost.com (Postfix) with ESMTP id 00736778057 for ; Mon, 28 Mar 2011 13:01:02 -0700 (PDT) Received: from fbsdlab.fbsdsecure.org (ip72-219-240-45.dc.dc.cox.net [72.219.240.45]) (Authenticated sender: trhodes@fbsdsecure.org) by homiemail-a36.g.dreamhost.com (Postfix) with ESMTPA id 91D3B77806E for ; Mon, 28 Mar 2011 13:01:01 -0700 (PDT) Date: Mon, 28 Mar 2011 16:01:01 -0400 From: Tom Rhodes To: FreeBSD-arch@FreeBSD.org Message-Id: <20110328160101.11a439c9.trhodes@FreeBSD.org> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd8.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Bringing service monitoring into base X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2011 20:30:29 -0000 Hi, So a handful of people have reviewed, used, are using, and seem to like my services monitoring stuff found here: http://people.FreeBSD.org/~trhodes/fsc Up there I have a port (may or not be written correctly); A tarball of the files; some patches against FreeBSD's rc to add support for startup and shutdown; and even a Makefile you can use to install the software. I've been running it at home on both CURRENT and STABLE for awhile and it appears pretty solid. Now I'd like to bring it into base and let everyone else make use of/modify/improve it. Unless there are any serious objectionss, I'll pull it in this coming weekend; perhaps Saturday or Sunday after an update and yet another build test. Thanks, -- Tom Rhodes From owner-freebsd-arch@FreeBSD.ORG Mon Mar 28 23:00:24 2011 Return-Path: Delivered-To: FreeBSD-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C3E710656B3; Mon, 28 Mar 2011 23:00:24 +0000 (UTC) (envelope-from gordon@tetlows.org) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 532E48FC1A; Mon, 28 Mar 2011 23:00:16 +0000 (UTC) Received: by qwc9 with SMTP id 9so2600336qwc.13 for ; Mon, 28 Mar 2011 16:00:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.40.198 with SMTP id l6mr4038582qae.47.1301351696907; Mon, 28 Mar 2011 15:34:56 -0700 (PDT) Received: by 10.229.27.6 with HTTP; Mon, 28 Mar 2011 15:34:56 -0700 (PDT) In-Reply-To: <20110328160101.11a439c9.trhodes@FreeBSD.org> References: <20110328160101.11a439c9.trhodes@FreeBSD.org> Date: Mon, 28 Mar 2011 15:34:56 -0700 Message-ID: From: Gordon Tetlow To: Tom Rhodes Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD-arch@freebsd.org Subject: Re: Bringing service monitoring into base X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Mar 2011 23:00:24 -0000 On Mon, Mar 28, 2011 at 1:01 PM, Tom Rhodes wrote: > Hi, > > So a handful of people have reviewed, used, are using, and seem > to like my services monitoring stuff found here: > > http://people.FreeBSD.org/~trhodes/fsc > > Up there I have a port (may or not be written correctly); > A tarball of the files; some patches against FreeBSD's rc > to add support for startup and shutdown; and even a Makefile > you can use to install the software. > > I've been running it at home on both CURRENT and STABLE for > awhile and it appears pretty solid. =A0Now I'd like to bring it > into base and let everyone else make use of/modify/improve it. > > Unless there are any serious objectionss, I'll pull it in this > coming weekend; perhaps Saturday or Sunday after an update > and yet another build test. =A0Thanks, I would think that fscadm should go into /usr/sbin since you have to be root to run it. Correspondingly, the manpage should be in section 8. The Makefile infrastructure looks to hardcode paths which I assume would be fixed up by importing it into the tree. I'll see if I can take a closer look at it tonight or tomorrow. Gordon From owner-freebsd-arch@FreeBSD.ORG Fri Apr 1 14:29:58 2011 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D448E106564A; Fri, 1 Apr 2011 14:29:58 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9BE198FC08; Fri, 1 Apr 2011 14:29:57 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA26851; Fri, 01 Apr 2011 17:29:55 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4D95E162.40605@FreeBSD.org> Date: Fri, 01 Apr 2011 17:29:54 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: FreeBSD Arch , FreeBSD Hackers X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: looking for error codes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2011 14:29:58 -0000 I am looking for error codes that would unambiguously signal that a disk drive has readonly or write-protected media and that disk drive has no media at the moment. I foresee these error codes being used mostly between disk peripheral drivers and filesystem drivers. I will appreciate your suggestions. P.S. I see that Linux uses EROFS and ENOMEDIUM for these purposes. I am not sure about EROFS in this role. And we don't have ENOMEDIUM (nor EMEDIUMTYPE). -- Andriy Gapon From owner-freebsd-arch@FreeBSD.ORG Fri Apr 1 14:58:33 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A6E81065672; Fri, 1 Apr 2011 14:58:33 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 383018FC14; Fri, 1 Apr 2011 14:58:33 +0000 (UTC) Received: from 63.imp.bsdimp.com (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p31EpPiD040268 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Fri, 1 Apr 2011 08:51:25 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <4D95E162.40605@FreeBSD.org> Date: Fri, 1 Apr 2011 08:51:25 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4D95E162.40605@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Fri, 01 Apr 2011 08:51:25 -0600 (MDT) Cc: FreeBSD Hackers , FreeBSD Arch Subject: Re: looking for error codes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2011 14:58:33 -0000 On Apr 1, 2011, at 8:29 AM, Andriy Gapon wrote: >=20 > I am looking for error codes that would unambiguously signal that a = disk drive has > readonly or write-protected media and that disk drive has no media at = the moment. > I foresee these error codes being used mostly between disk peripheral = drivers and > filesystem drivers. >=20 > I will appreciate your suggestions. >=20 > P.S. > I see that Linux uses EROFS and ENOMEDIUM for these purposes. > I am not sure about EROFS in this role. > And we don't have ENOMEDIUM (nor EMEDIUMTYPE). Maybe we could add ENOMEDIA for that (spelled however Linux spells it) = after EDAVE. Warner From owner-freebsd-arch@FreeBSD.ORG Fri Apr 1 15:19:03 2011 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A91A106566C; Fri, 1 Apr 2011 15:19:03 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8E8608FC13; Fri, 1 Apr 2011 15:19:02 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA27456; Fri, 01 Apr 2011 18:18:55 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4D95ECDE.1020504@FreeBSD.org> Date: Fri, 01 Apr 2011 18:18:54 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: Andrew Duane References: <4D95E162.40605@FreeBSD.org>, In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers , FreeBSD Arch Subject: Re: looking for error codes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2011 15:19:03 -0000 on 01/04/2011 18:04 Andrew Duane said the following: > AFAIK, FreeBSD does not really detect read-only media. This was something I had to add as a small project here at work, and was considering cleaning up to try to get into CURRENT. If there's a real need for it, I could speed that up. > Yes, that's exactly the problem that I am looking at. So if you have anything to share it will be greatly appreciated at least by me. But I think many more people could benefit from it (e.g. those having SD/SDHC/etc cards). Thanks! > ________________________________________ > From: owner-freebsd-hackers@freebsd.org [owner-freebsd-hackers@freebsd.org] On Behalf Of Warner Losh [imp@bsdimp.com] > Sent: Friday, April 01, 2011 10:51 AM > To: Andriy Gapon > Cc: FreeBSD Hackers; FreeBSD Arch > Subject: Re: looking for error codes > > On Apr 1, 2011, at 8:29 AM, Andriy Gapon wrote: > >> >> I am looking for error codes that would unambiguously signal that a disk drive has >> readonly or write-protected media and that disk drive has no media at the moment. >> I foresee these error codes being used mostly between disk peripheral drivers and >> filesystem drivers. >> >> I will appreciate your suggestions. >> >> P.S. >> I see that Linux uses EROFS and ENOMEDIUM for these purposes. >> I am not sure about EROFS in this role. >> And we don't have ENOMEDIUM (nor EMEDIUMTYPE). > > Maybe we could add ENOMEDIA for that (spelled however Linux spells it) after EDAVE. -- Andriy Gapon From owner-freebsd-arch@FreeBSD.ORG Fri Apr 1 15:20:27 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 596861065691 for ; Fri, 1 Apr 2011 15:20:27 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by mx1.freebsd.org (Postfix) with ESMTP id B1BD28FC15 for ; Fri, 1 Apr 2011 15:20:25 +0000 (UTC) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKTZXtOM9t4CtvXu6aQWHJR50nUBYTR95R@postini.com; Fri, 01 Apr 2011 08:20:27 PDT Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 1 Apr 2011 08:04:06 -0700 Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Fri, 1 Apr 2011 11:05:40 -0400 From: Andrew Duane To: Warner Losh , Andriy Gapon Date: Fri, 1 Apr 2011 11:04:38 -0400 Thread-Topic: looking for error codes Thread-Index: AcvwfWvgdu2RiXRbQqKNabRJHzfR4wAALLZh Message-ID: References: <4D95E162.40605@FreeBSD.org>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: FreeBSD Hackers , FreeBSD Arch Subject: RE: looking for error codes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2011 15:20:27 -0000 AFAIK, FreeBSD does not really detect read-only media. This was something I= had to add as a small project here at work, and was considering cleaning u= p to try to get into CURRENT. If there's a real need for it, I could speed = that up. -- Andrew Duane Juniper Networks 978-589-0551 10 Technology Park Dr aduane@juniper.net Westford, MA 01886-3418 ________________________________________ From: owner-freebsd-hackers@freebsd.org [owner-freebsd-hackers@freebsd.org]= On Behalf Of Warner Losh [imp@bsdimp.com] Sent: Friday, April 01, 2011 10:51 AM To: Andriy Gapon Cc: FreeBSD Hackers; FreeBSD Arch Subject: Re: looking for error codes On Apr 1, 2011, at 8:29 AM, Andriy Gapon wrote: > > I am looking for error codes that would unambiguously signal that a disk = drive has > readonly or write-protected media and that disk drive has no media at the= moment. > I foresee these error codes being used mostly between disk peripheral dri= vers and > filesystem drivers. > > I will appreciate your suggestions. > > P.S. > I see that Linux uses EROFS and ENOMEDIUM for these purposes. > I am not sure about EROFS in this role. > And we don't have ENOMEDIUM (nor EMEDIUMTYPE). Maybe we could add ENOMEDIA for that (spelled however Linux spells it) afte= r EDAVE. Warner _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-arch@FreeBSD.ORG Fri Apr 1 15:39:39 2011 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFC1B106564A; Fri, 1 Apr 2011 15:39:38 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by mx1.freebsd.org (Postfix) with ESMTP id CBA838FC13; Fri, 1 Apr 2011 15:39:36 +0000 (UTC) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKTZXxt7W9xLalW4+DGQycLcWDhn2v8aFT@postini.com; Fri, 01 Apr 2011 08:39:38 PDT Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 1 Apr 2011 08:37:00 -0700 Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Fri, 1 Apr 2011 11:38:34 -0400 From: Andrew Duane To: Andriy Gapon Date: Fri, 1 Apr 2011 11:35:50 -0400 Thread-Topic: looking for error codes Thread-Index: AcvwgCAChEFAfkU1TQqYtmTB61u6+AAAlrTk Message-ID: References: <4D95E162.40605@FreeBSD.org>, , <4D95ECDE.1020504@FreeBSD.org> In-Reply-To: <4D95ECDE.1020504@FreeBSD.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: FreeBSD Hackers , FreeBSD Arch Subject: RE: looking for error codes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2011 15:39:39 -0000 My work is absolutely NOT in any shape at all to even consider, it's a real= ly tailored point solution to a specific platform issue. I've been working = with another engineer to expand it and make it more generic, but that effor= t is stalled at the moment. My plan was to add something like an ioctl to a device that would query it = for read/write status, and percolate that up through the geom layer to capt= ure it for mount requests. The correct place to stop it is at mount time. E= ven mounting a read-only device as read-write will eventually panic the sys= tem as super-block flag updates will not be able to complete. Once that is = done, any attempt to open a file for writing fails. -- Andrew Duane Juniper Networks 978-589-0551 10 Technology Park Dr aduane@juniper.net Westford, MA 01886-3418 ________________________________________ From: Andriy Gapon [avg@FreeBSD.org] Sent: Friday, April 01, 2011 11:18 AM To: Andrew Duane Cc: Warner Losh; FreeBSD Hackers; FreeBSD Arch Subject: Re: looking for error codes on 01/04/2011 18:04 Andrew Duane said the following: > AFAIK, FreeBSD does not really detect read-only media. This was something= I had to add as a small project here at work, and was considering cleaning= up to try to get into CURRENT. If there's a real need for it, I could spee= d that up. > Yes, that's exactly the problem that I am looking at. So if you have anything to share it will be greatly appreciated at least by= me. But I think many more people could benefit from it (e.g. those having SD/SD= HC/etc cards). Thanks! > ________________________________________ > From: owner-freebsd-hackers@freebsd.org [owner-freebsd-hackers@freebsd.or= g] On Behalf Of Warner Losh [imp@bsdimp.com] > Sent: Friday, April 01, 2011 10:51 AM > To: Andriy Gapon > Cc: FreeBSD Hackers; FreeBSD Arch > Subject: Re: looking for error codes > > On Apr 1, 2011, at 8:29 AM, Andriy Gapon wrote: > >> >> I am looking for error codes that would unambiguously signal that a disk= drive has >> readonly or write-protected media and that disk drive has no media at th= e moment. >> I foresee these error codes being used mostly between disk peripheral dr= ivers and >> filesystem drivers. >> >> I will appreciate your suggestions. >> >> P.S. >> I see that Linux uses EROFS and ENOMEDIUM for these purposes. >> I am not sure about EROFS in this role. >> And we don't have ENOMEDIUM (nor EMEDIUMTYPE). > > Maybe we could add ENOMEDIA for that (spelled however Linux spells it) af= ter EDAVE. -- Andriy Gapon From owner-freebsd-arch@FreeBSD.ORG Fri Apr 1 17:23:52 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37534106566B; Fri, 1 Apr 2011 17:23:52 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id B900F8FC14; Fri, 1 Apr 2011 17:23:51 +0000 (UTC) Received: by qwc9 with SMTP id 9so2679731qwc.13 for ; Fri, 01 Apr 2011 10:23:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=N00NaMS2DTvJJ67YayaYKNHD5pXVNs0q43d+duo9Z4Y=; b=V6UimiUmIOOs+eszdVVf4fRiul6zBybsSGAwOlGQQ92c9Wa2G/FEqAInW/AX9vYOAf +Z1zlpALY+/g3P7bGUqfFAbP6tW6kzSMvrYyexKiltStJV1uC835HnRsXU/kKqDCA/w3 eV7o51JtJPkxwqRpl/fMSMAttQ35J+1KNG9bQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=in8jepGaAGEk7d8ks584O8NVEmbdhfhTclYPnYX7+55lqmaCEceNNDpE3S+WGEa7HI kc2cey9gizEGAWts4pkiPfChqE6E4ewGEfv9VacsLMVROpaG0fuaz25RGDzBc6DLXu3o u4/tJRAp33Li4EGp4E16yWxIufTqC82WF2n6M= MIME-Version: 1.0 Received: by 10.224.9.197 with SMTP id m5mr3730052qam.367.1301676940854; Fri, 01 Apr 2011 09:55:40 -0700 (PDT) Received: by 10.224.67.21 with HTTP; Fri, 1 Apr 2011 09:55:40 -0700 (PDT) In-Reply-To: <4D95ECDE.1020504@FreeBSD.org> References: <4D95E162.40605@FreeBSD.org> <4D95ECDE.1020504@FreeBSD.org> Date: Fri, 1 Apr 2011 12:55:40 -0400 Message-ID: From: Mehmet Erol Sanliturk To: Andriy Gapon Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Hackers , Andrew Duane , FreeBSD Arch Subject: Re: looking for error codes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2011 17:23:52 -0000 On Fri, Apr 1, 2011 at 11:18 AM, Andriy Gapon wrote: > on 01/04/2011 18:04 Andrew Duane said the following: > > AFAIK, FreeBSD does not really detect read-only media. This was something > I had to add as a small project here at work, and was considering cleaning > up to try to get into CURRENT. If there's a real need for it, I could speed > that up. > > > > Yes, that's exactly the problem that I am looking at. > So if you have anything to share it will be greatly appreciated at least by > me. > But I think many more people could benefit from it (e.g. those having > SD/SDHC/etc > cards). > Thanks! > > > ________________________________________ > > From: owner-freebsd-hackers@freebsd.org [ > owner-freebsd-hackers@freebsd.org] On Behalf Of Warner Losh [ > imp@bsdimp.com] > > Sent: Friday, April 01, 2011 10:51 AM > > To: Andriy Gapon > > Cc: FreeBSD Hackers; FreeBSD Arch > > Subject: Re: looking for error codes > > > > On Apr 1, 2011, at 8:29 AM, Andriy Gapon wrote: > > > >> > >> I am looking for error codes that would unambiguously signal that a disk > drive has > >> readonly or write-protected media and that disk drive has no media at > the moment. > >> I foresee these error codes being used mostly between disk peripheral > drivers and > >> filesystem drivers. > >> > >> I will appreciate your suggestions. > >> > >> P.S. > >> I see that Linux uses EROFS and ENOMEDIUM for these purposes. > >> I am not sure about EROFS in this role. > >> And we don't have ENOMEDIUM (nor EMEDIUMTYPE). > > > > Maybe we could add ENOMEDIA for that (spelled however Linux spells it) > after EDAVE. > > -- > Andriy Gapon > For a long time I am thinking to obtain a physically ( not only software ) based FreeBSD edition by re-arranging some parts of it , but I do not know how to do it . Such an approach requires separation of FreeBSD into two parts : Read-Only parts and modifiable parts . The core software will be in the read-only part and data files will be in modifiable parts . This will require a new directory structure and partition scheme . At that point , I want to mention my a previously applied approach to such a problem . During 1990 years I was managing computer laboratories of a university department having *DOS systems . Maintenance of software on these computers was impossible due to malicious software . In those days , there were MFM hard disks : Their controllers were separate from their disks as add-on cards , and its cables have two lines among others : One is READ from disk , another WRITE to disk . I have attached rocker switches to WRITE lines of the controller cables . After installations of software , I was disconnecting WRITE line rocker switch and supply the computer for usage . The students were required to boot the computer to eliminate possibility of malicious software invasion of the memory before beginning to study and to use diskettes for data read-write . The main usage was to connect to the main frame of the university . After application of the above protection scheme , the students and others were able to use the computers safely and continuously without any interruption or harm due to malicious software . Data storage into the local personal computers were not important because of usability of main frame of the university . After some years , MFM hard disks abandoned in favor of IDE ( Integrated Drive Electronics ) hard disks by moving controller to hard disk and eliminating use of add-on cards with a very unfortunate design decision as ( a write protect mechanism by a switch on the hard disks are not implemented ) . With respect to my knowledge , no one of the operating systems has a facility to separate read-only and modifiable parts . This feature is making operating systems a very vulnerable targets for wicked persons for malicious attacks . Software protections are not able to prevent this problem because it is impossible to design an error-free software system , especially a very complex system such as an operating system . Up to a few months before , I could not be able to obtain a physical security policy when I accidentally study SDHC cards . Reason of my study was a wish to obtain a more cheaper medium for my frequent operating system installations on USB sticks because USB sticks are much more expensive from hard disks with respective to per giga byte cost . SDHC cards have WRITE-PROTECT mechanism which may be used to protect an operating system physically , IF we can obtain an operating system divisible into two parts as read-only ( software and configuration files , user definitions , etc. ) and modifiable ( data files ) . There are Live DVD/CD operating systems but I do not know that any one of them has a facility to allow to use an external file system usage for continuous usability . I have learned the presence of Puppy Linux from mails : http://puppylinux.org/main/Overview%20and%20Getting%20Started.htm The Puppy Linux has a WONDERFUL Live CD facility : It uses a ram disk during its working . At the end of the session , when a shutdown is requested it is asking to user whether the session will be saved or not . If the Puppy Linux is recorded onto a DVD and writing to DVD is NOT closed , it is possible to burn session data incrementally onto DVD up to a closing of writing . In that way , it is possible to customize working of the Live DVD/CD incrementally . By using such a facility , it is possible to rearrange a physically secure operating system : (1) Install the operating system . Boot it and set its parameters . Write those parameters to its configuration files and close it . Use a DVD-ROM ( not DVD Re-Write ) drive for absolute protection . If speed is important and there is no DVD-ROM , use a SDHC card : (2) Protect it by its write protect switch in SDHC cards after installation and setting parameters . For subsequent usages , use other external drives for data processing ( read - write ) only without any possibility of loading any executable from them . When it is necessary to perform a secure operation , just boot the computer to clean the possible memory invasion of malicious software . For the upgrades : Use a sterile computer ( as not connected to external sources to prevent from possible pollution ) , prepare an upgraded version , write-protect it , insert it into production computer which is exposed to external world by replacing the older version part. By separating directories into distinct drives , it is possible to upgrade only a required part as write protected : .../user_definitions : Important for installations which have a large number of users such as schools , and companies with a large number of employees or users of the computer ( server ) . .../packages : .../configurations : .../operating_system : .../boot_manager : The following parts may be assigned to modifiable drives : /home /var /tmp /swap and possible others . As a summary : It is necessary to have - A new partition structure with ability to assigning parts to distinct drives referenced by names , - Distinction between read-only and modifiable parts where they are assignable to physically different drives referenced by names , ( not by physically encoded drive numbers with respect to attached slot of the computer ) - and other related modifications not mentioned here or not recognized at present by me . I am sorry to present an off-topic subject into this thread , but to obtain such a facility , it is necessary to be able to detect structure of drives and use that structure appropriately . Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-arch@FreeBSD.ORG Sat Apr 2 08:00:34 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B8AA1065678; Sat, 2 Apr 2011 08:00:34 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 3C7418FC1C; Sat, 2 Apr 2011 08:00:34 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p3280XYW036537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 2 Apr 2011 01:00:33 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p3280X74036536; Sat, 2 Apr 2011 01:00:33 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA14774; Fri, 1 Apr 11 23:50:49 PST Date: Sat, 02 Apr 2011 00:50:29 -0700 From: perryh@pluto.rain.com To: m.e.sanliturk@gmail.com Message-Id: <4d96d545.e/wWTIUATgk2CGjt%perryh@pluto.rain.com> References: <4D95E162.40605@FreeBSD.org> <4D95ECDE.1020504@FreeBSD.org> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, avg@freebsd.org, freebsd-arch@freebsd.org Subject: Re: looking for error codes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2011 08:00:34 -0000 Mehmet Erol Sanliturk wrote: > For a long time I am thinking to obtain a physically ( not only > software ) based [read-only] FreeBSD edition by re-arranging some > parts of it , but I do not know how to do it ... > After some years , MFM hard disks abandoned in favor of IDE > ( Integrated Drive Electronics ) hard disks by moving controller > to hard disk and eliminating use of add-on cards with a very > unfortunate design decision as ( a write protect mechanism by > a switch on the hard disks are not implemented ) . At least some IDE drives have write-protect jumpers, which could presumably be replaced with connections to switches. > With respect to my knowledge , no one of the operating systems > has a facility to separate read-only and modifiable parts ... SunOS 4 had a partial solution to this, by rearranging the FS layout so that /usr could be mounted read-only (and often, from a server -- IIRC a single /usr could be shared among multiple diskless clients). They used quite a few symlinks so that things could be found in their accustomed places although actually located elsewhere. The scheme was fairly well described in the SunOS 4 manual set; granted _finding_ a SunOS 4 manual set these days may be a challenge :) From owner-freebsd-arch@FreeBSD.ORG Sat Apr 2 09:56:33 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A55C106566C; Sat, 2 Apr 2011 09:56:33 +0000 (UTC) (envelope-from freebsd@psconsult.nl) Received: from mx1.psconsult.nl (unknown [IPv6:2001:7b8:30f:e0::5059:ee8a]) by mx1.freebsd.org (Postfix) with ESMTP id 031AE8FC0C; Sat, 2 Apr 2011 09:56:32 +0000 (UTC) Received: from mx1.psconsult.nl (psc11.adsl.iaf.nl [80.89.238.138]) by mx1.psconsult.nl (8.14.4/8.14.4) with ESMTP id p329uQxf029423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 2 Apr 2011 11:56:31 +0200 (CEST) (envelope-from freebsd@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.4/8.14.4/Submit) id p329uQZK029422; Sat, 2 Apr 2011 11:56:26 +0200 (CEST) (envelope-from freebsd@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to freebsd@psconsult.nl using -f Date: Sat, 2 Apr 2011 11:56:26 +0200 From: Paul Schenkeveld To: freebsd-arch@freebsd.org, freebsd-hackers@freebsd.org Message-ID: <20110402095626.GA29060@psconsult.nl> References: <4D95E162.40605@FreeBSD.org> <4D95ECDE.1020504@FreeBSD.org> <4d96d545.e/wWTIUATgk2CGjt%perryh@pluto.rain.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4d96d545.e/wWTIUATgk2CGjt%perryh@pluto.rain.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Subject: Re: looking for error codes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2011 09:56:33 -0000 On Sat, Apr 02, 2011 at 12:50:29AM -0700, perryh@pluto.rain.com wrote: > Mehmet Erol Sanliturk wrote: > > > For a long time I am thinking to obtain a physically ( not only > > software ) based [read-only] FreeBSD edition by re-arranging some > > parts of it , but I do not know how to do it ... > > > After some years , MFM hard disks abandoned in favor of IDE > > ( Integrated Drive Electronics ) hard disks by moving controller > > to hard disk and eliminating use of add-on cards with a very > > unfortunate design decision as ( a write protect mechanism by > > a switch on the hard disks are not implemented ) . > > At least some IDE drives have write-protect jumpers, which could > presumably be replaced with connections to switches. > > > With respect to my knowledge , no one of the operating systems > > has a facility to separate read-only and modifiable parts ... > > SunOS 4 had a partial solution to this, by rearranging the FS layout > so that /usr could be mounted read-only (and often, from a server -- > IIRC a single /usr could be shared among multiple diskless clients). > They used quite a few symlinks so that things could be found in > their accustomed places although actually located elsewhere. The > scheme was fairly well described in the SunOS 4 manual set; granted > _finding_ a SunOS 4 manual set these days may be a challenge :) In fact, FreeBSD is very similar, /etc and /usr/local/etc may be written to for configuration purposes after building your system, /tmp and /var should really be writable (temp files, log files, sockets etc.) /home other application directories of course depend on the particular application and the rest can be r/o. Embedded systems (please read the freebsd-embedded mailing list) deal with similar issues and that's what nanobsd(8) was written for. Read http://www.psconsult.nl/talks/AsiaBSDcon2010-Servers if you want to see that similar techniques can also be applied to servers. Regards, Paul Schenkeveld From owner-freebsd-arch@FreeBSD.ORG Sat Apr 2 15:57:53 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2437F106566C; Sat, 2 Apr 2011 15:57:53 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id B2F538FC0C; Sat, 2 Apr 2011 15:57:52 +0000 (UTC) Received: from [10.0.0.63] (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p32FsGmv054175 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Sat, 2 Apr 2011 09:54:19 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1082) From: Warner Losh In-Reply-To: <4d96d545.e/wWTIUATgk2CGjt%perryh@pluto.rain.com> Date: Sat, 2 Apr 2011 09:54:16 -0600 Message-Id: References: <4D95E162.40605@FreeBSD.org> <4D95ECDE.1020504@FreeBSD.org> <4d96d545.e/wWTIUATgk2CGjt%perryh@pluto.rain.com> To: perryh@pluto.rain.com X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Sat, 02 Apr 2011 09:54:19 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, m.e.sanliturk@gmail.com, avg@freebsd.org, freebsd-arch@freebsd.org Subject: Re: looking for error codes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2011 15:57:53 -0000 On Apr 2, 2011, at 1:50 AM, perryh@pluto.rain.com wrote: >=20 >> With respect to my knowledge , no one of the operating systems >> has a facility to separate read-only and modifiable parts ... >=20 > SunOS 4 had a partial solution to this, by rearranging the FS layout > so that /usr could be mounted read-only (and often, from a server -- > IIRC a single /usr could be shared among multiple diskless clients). > They used quite a few symlinks so that things could be found in > their accustomed places although actually located elsewhere. The > scheme was fairly well described in the SunOS 4 manual set; granted > _finding_ a SunOS 4 manual set these days may be a challenge :) FreeBSD can do this too. In fact, NanoBSD relies heavily on having most = of the system mounted read-only, and has MFS partitions for /etc and = /var. Warner From owner-freebsd-arch@FreeBSD.ORG Sat Apr 2 16:38:20 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8E27106564A; Sat, 2 Apr 2011 16:38:20 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by mx1.freebsd.org (Postfix) with ESMTP id 2BE258FC15; Sat, 2 Apr 2011 16:38:11 +0000 (UTC) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKTZdQ8tbE01LX7Xq25w+nuf5dYneLWapi@postini.com; Sat, 02 Apr 2011 09:38:20 PDT Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sat, 2 Apr 2011 09:36:16 -0700 Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Sat, 2 Apr 2011 12:37:52 -0400 From: Andrew Duane To: Warner Losh , "perryh@pluto.rain.com" Date: Sat, 2 Apr 2011 12:36:16 -0400 Thread-Topic: looking for error codes Thread-Index: AcvxTvHauLj/p3NoQGWKX8kFJ5nmLgABSPv5 Message-ID: References: <4D95E162.40605@FreeBSD.org> <4D95ECDE.1020504@FreeBSD.org> <4d96d545.e/wWTIUATgk2CGjt%perryh@pluto.rain.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-hackers@freebsd.org" , "m.e.sanliturk@gmail.com" , "avg@freebsd.org" , "freebsd-arch@freebsd.org" Subject: RE: looking for error codes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2011 16:38:20 -0000 My work around read-only systems extended this, to allow a general FreeBSD = system to come up with "main media" write locked. In the RC files, MFS part= itions were made for /tmp, /var, and other places we needed to write. Now t= hat we're upgrading to a later BSD, I hope to refit these with union filesy= stems instead, to save space and complexity. -- Andrew Duane Juniper Networks 978-589-0551 10 Technology Park Dr aduane@juniper.net Westford, MA 01886-3418 ________________________________________ From: owner-freebsd-hackers@freebsd.org [owner-freebsd-hackers@freebsd.org]= On Behalf Of Warner Losh [imp@bsdimp.com] Sent: Saturday, April 02, 2011 11:54 AM To: perryh@pluto.rain.com Cc: freebsd-hackers@freebsd.org; m.e.sanliturk@gmail.com; avg@freebsd.org; = freebsd-arch@freebsd.org Subject: Re: looking for error codes On Apr 2, 2011, at 1:50 AM, perryh@pluto.rain.com wrote: > >> With respect to my knowledge , no one of the operating systems >> has a facility to separate read-only and modifiable parts ... > > SunOS 4 had a partial solution to this, by rearranging the FS layout > so that /usr could be mounted read-only (and often, from a server -- > IIRC a single /usr could be shared among multiple diskless clients). > They used quite a few symlinks so that things could be found in > their accustomed places although actually located elsewhere. The > scheme was fairly well described in the SunOS 4 manual set; granted > _finding_ a SunOS 4 manual set these days may be a challenge :) FreeBSD can do this too. In fact, NanoBSD relies heavily on having most of= the system mounted read-only, and has MFS partitions for /etc and /var. Warner _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"