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
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.
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart
FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd
"The scanf() function is a large and complex beast that often does
something almost but not quite entirely unlike what you desired."
-- Chris Torek
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"