From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 16 18:58:46 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 113AD1065670 for ; Sat, 16 Jun 2012 18:58:46 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id D0C878FC08 for ; Sat, 16 Jun 2012 18:58:44 +0000 (UTC) Received: from [89.204.137.49] (helo=tiny.Sisis.de) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1SfyCX-000609-5c; Sat, 16 Jun 2012 20:58:26 +0200 Received: from tiny.Sisis.de (localhost [127.0.0.1]) by tiny.Sisis.de (8.14.5/8.14.3) with ESMTP id q5GIwOAB001300; Sat, 16 Jun 2012 20:58:25 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by tiny.Sisis.de (8.14.5/8.14.3/Submit) id q5GIwNsl001299; Sat, 16 Jun 2012 20:58:23 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: tiny.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Sat, 16 Jun 2012 20:58:23 +0200 From: Matthias Apitz To: Wojciech Puchar Message-ID: <20120616185822.GA1253@tiny.Sisis.de> References: <4fb7dfd6.736a980a.186d.ffff902f@mx.google.com> <20120519180901.GA1264@tiny> <20120525183006.GA1259@tiny> <20120525225839.GA7347@server.rulingia.com> <20120527082745.GA2591@tinyCurrent> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 10.0-CURRENT r226986 (i386) User-Agent: Mutt/1.5.21 (2010-09-15) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.137.49 Cc: freebsd-hackers@freebsd.org, rozhuk.im@gmail.com Subject: Re: proper newfs options for SSD disk X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jun 2012 18:58:46 -0000 El día Wednesday, May 30, 2012 a las 07:44:37PM +0200, Wojciech Puchar escribió: > > from; one has to go (by pressing ESC) to the boot menu to pick it up as > > current boot device; any idea how this could be changed? > > boot from 4GB. just put /boot here and add > > vfs.root.mountfrom="ufs:XXX" > > where XXX is your root filesystem device name with "/dev/" stripped > > do not forget to bsdlabel -B your.4GB.SSD > > WARNING: you must have proper disklabel with a: partition containing UFS > with /boot. > > But you may have a partition equal to whole disk > > a: 117231408 0 4.2BSD 0 0 0 > c: 117231408 0 unused 0 0 # "raw" part, don't edit > > > and it is absolutely OK, UFS do not overwrite first few sectors as it is > reserved for it. > > And PLEASE DO NOT make this stupid MSDOS style slices. It is not just > unneeded but introduces mess and only mess. > > just have /dev/ad0a not /dev/ad0s1a OK, but I wanted to have most of the space of the 4 GB SSD encrypted with geli(8); so I should make there some slice containing /boot (unencrypted) and a second slice which later will contain my HOME and encrypted; wrong? matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5