Date: Mon, 11 Dec 2017 21:29:31 +0100 From: Harry Schmalzbauer <freebsd@omnilan.de> To: byrnejb@harte-lyne.ca Cc: "James B. Byrne via freebsd-questions" <freebsd-questions@freebsd.org> Subject: Re: IPMITool questions: Message-ID: <5A2EEAAB.8060702@omnilan.de> In-Reply-To: <93d4d4f96a4766fd76478371bee8f2d8.squirrel@webmail.harte-lyne.ca> References: <0357d8aee93fb02cd39af11f6476487b.squirrel@webmail.harte-lyne.ca> <5A2EC94A.9000000@omnilan.de> <93d4d4f96a4766fd76478371bee8f2d8.squirrel@webmail.harte-lyne.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Bezüglich James B. Byrne's Nachricht vom 11.12.2017 20:57 (localtime): > > On Mon, December 11, 2017 13:07, Harry Schmalzbauer wrote: >> >> Hello, >> >> do you want to establish pre-boot sessions via SoL or a login session >> to FreeBSD? >> > > I only need access to the pre-boot console. The remote system is set > up with an encrypted zfs file system and configured to boot from zfs. > The boot process needs the encryption key pass phrase to start. That's what I would neither call pre-boot nor post-boot, but during-boot ;-) Similar solution: You have to tell the boot loader to use serial console. Out of memory I don't know which stage asks for GELI... If /boot/loader.conf (3rd stage) is too late (which I don't think, so it's worth trying boot_multicons="YES" in /boot/loader.conf), you can pass "-nDS115200" to the 2nd boot stage, by putting it into /boot.config. Hope that helps, -harry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5A2EEAAB.8060702>