From owner-freebsd-geom@FreeBSD.ORG Wed Feb 1 00:51:48 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB7B716A420 for ; Wed, 1 Feb 2006 00:51:48 +0000 (GMT) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCCB443D49 for ; Wed, 1 Feb 2006 00:51:47 +0000 (GMT) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1F46Di-0005gP-9I for freebsd-geom@freebsd.org; Wed, 01 Feb 2006 01:51:38 +0100 Received: from p508c1b93.dip0.t-ipconnect.de ([80.140.27.147]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Feb 2006 01:51:38 +0100 Received: from christian.baer by p508c1b93.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Feb 2006 01:51:38 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-geom@freebsd.org From: Christian Baer Date: Tue, 31 Jan 2006 11:48:58 +0100 (CET) Organization: Convenimus Projekt Lines: 22 Message-ID: References: <000901c625b8$68954120$0201a8c0@oxy> <20060130192626.GA928@garage.freebsd.pl> <001001c6264a$f391eca0$0201a8c0@oxy> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p508c1b93.dip0.t-ipconnect.de User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: geli bugreport? fdisk error with non default sector size X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2006 00:51:48 -0000 On Tue, 31 Jan 2006 10:44:37 +0100 OxY wrote: > i've got one question: > is it neccesary to leave the /boot unencrypted or it has no effect > that i get non system disk message during boot after encrypted the > whole system disk.. I'm not sure what you are getting at, so I'll just put this in a general statement: You cannot boot the kernel from an encrypted file system. This would be a little like the "chicken or the egg problem". Encrypted filesystems cannot be read unless attached to the kernel. But without reading from your encrypted file system, you can't boot the kernel - because it's on there. If you really want to encrypt *all* of your disk space, boot the kernel from something else (CD-ROM, USB-Stick etc.). Regards Chris