Date: Sat, 20 Mar 2021 09:54:19 -0500 From: Valeri Galtsev <galtsev@kicp.uchicago.edu> To: Steve O'Hara-Smith <steve@sohara.org> Cc: freebsd-questions@freebsd.org Subject: Re: Call to delay EOL of 11.x -> Re: OS to replace FreeBSD Message-ID: <7270A6A8-4514-4B61-80AD-7812CC0AEFD7@kicp.uchicago.edu> In-Reply-To: <20210320135740.c10f4d671d34ce6590527eb6@sohara.org> References: <NGCSlp5NzhdwJNGCUlpzqu@videotron.ca> <5743CB5D-338C-4609-8E89-396440926CEC@videotron.ca> <20210319110001.00000bf8@seibercom.net> <4602cbad-bf26-18d1-83e6-cba9627787d8@johnea.net> <90FEC704-1764-43E7-BEFA-C9481CF14714@kreme.com> <CAAQ96DyS5HOxkE77eoCNPo6O4mEWahhg-PWY=y8M_vdU_kpuMQ@mail.gmail.com> <20210320083808.00000cb1@seibercom.net> <CAAQ96DwosgKxnbU=itPRWfmAjhzHcoSbRonq8_B24=xAo9MrxA@mail.gmail.com> <20210320093304.00001e37@seibercom.net> <20210320135740.c10f4d671d34ce6590527eb6@sohara.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Mar 20, 2021, at 8:57 AM, Steve O'Hara-Smith <steve@sohara.org> = wrote: >=20 > On Sat, 20 Mar 2021 09:33:04 -0400 > Jerry <jerry@seibercom.net> wrote: >=20 >> I CANNOT install it,=20 >=20 > Perhaps I am misunderstanding the situation. AIUI the install > completes it is just that the default console is spammed by error = messages > so you can't see the login prompt (it is actually possible to log in = and > work under these conditions but it is hideous to do). Fortunately = there is > a better option, there are several active virtual consoles available = by > hitting Alt-F<n> simply switch to one of those, log in and proceed as > normal. >=20 I had to install FreeBSD not in GUI but in text menu mode once on the = machine producing constant stream of messages (USB related on console). = In my case I was booting off USB medium. That effectively obliterated my = ability to interact with menu. The solution to that was to suppress console messages: when boot menu appears do "ESCape to loader prompt=E2=80=9D. Then in in boot prompt: set boot_mute=3D=E2=80=9CYES=E2=80=9D boot After that there were no console messages, and I was able to = successfully do installation. In general, to suppress console messages on already installed system, = you can add to /boot/loader.conf: boot_mute=3D"YES" I hope, this helps. Valeri >> so I am unsure of how to build a custom kernel. >> Then, assuming I could build a custom kernel, I would not be able to >> use the "freebsd update" utility. >=20 > Of course you can use freebsd-update with a custom kernel, I do = it > all the time. It just adds the extra step of compiling your custom = kernel > before rebooting after the update. My usual sequence for this is: >=20 > freebsd-update fetch > freebsd-update install > cd /usr/src > make kernel > reboot >=20 > NB: make kernel works because I have kernconf set in = /etc/make.conf > to the name of my custom kernel config. >=20 >> So, to put it in the vernacular, >> "I am fucked if I do, and fucked if I don't". >=20 > Nope, you just have to understand how to get yourself out of the > hole. >=20 > --=20 > Steve O'Hara-Smith <steve@sohara.org> > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to = "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7270A6A8-4514-4B61-80AD-7812CC0AEFD7>