Date: Thu, 25 Oct 2007 14:05:01 -0400 From: Steve Bertrand <iaccounts@ibctech.ca> To: freebsd-questions@FreeBSD.ORG Subject: Re: Booting a GELI encrypted hard disk Message-ID: <4720DACD.9040302@ibctech.ca> In-Reply-To: <200710251634.l9PGYlPV068519@lurza.secnetix.de> References: <200710251634.l9PGYlPV068519@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Oliver Fromme wrote: > Steve Bertrand wrote: > > I haven't tried it yet, but I don't think that /boot on the encrypted > > disk is necessary. I will rename the directory and reboot and see if it > > barfs. > > It shouldn't be necessary. Once the kernel is loaded, the > system never looks at /boot again. > > Unless, of course, you want to load a kernel module. Those > are located in /boot/kernel by default, but you can change > the if needed (see sysctl kern.module_path). > > Also, some system utilities that use KVM functions (vmstat, > top, ps) might require access to the kernel file. But that > can be changed, too: sysctl kern.bootfile. > > Other than that, the /boot directory isn't used at all > during normal operation. This is correct, I tested it. Also, this system (with GEOM_ELI built into kernel) successfully upgraded from 6.2 to 7.0 with ULE scheduler enabled with no problems at all. Cheers! Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4720DACD.9040302>