23.03.2026 12:47, Jan Stary пишет:
> On Mar 23 10:24:47, kasak@kasakoff.net wrote:
>>> You can spawn a login prompt on com0 through /etc/ttys and avoid changing boot.conf. Enable tty00 in /etc/ttys.
>>>
>>> That's the best dual support you'll get.
>>>
>> i'm afraid, this will not help me to fix filesystem errors, which i get time
>> to time because of power outage.
> How would two consoles help you fix FS errors after a reboot
> (as opposed to having one console after a reboot)?
very easy :) i won't have to go to work on the weekend, because i have
another machine near, which i've could use to connect to console.
Unfortunately, i do not have any kvm or ipmi on my OpenBSD machine, and
cannot afford it.
>> it's the main reason i wanted second console.
> It is way easier to help
> if you make you main reason clear
> at the very start of your post.
I already seen those posts about patching rc to make fsck be more
automatically, i think this is terrible solution.
So, i thought, maybe there is another way.
>
> Jan
>
>
>>>> On Mar 22, 2026, at 3:48 PM, Stuart Henderson <stu.lists@spacehopper.org> wrote:
>>>>
>>>> On 2026-03-22, Andrew Daugherity <andrew.daugherity@gmail.com> wrote:
>>>>>> I use
>>>>>>
>>>>>> ~ $ cat /etc/boot.conf
>>>>>> stty com0 115200
>>>>>> set tty com0
>>>>>> ~ $
>>>>> You can configure a serial console in boot.conf, and switch back to
>>>>> the default local console by holding the Ctrl during bootup to skip
>>>>> loading the conf file (on i386 & amd64 at least, not sure about other
>>>>> arches). From boot(8):
>>>>>
>>>>> boot.conf processing can be skipped, and the automatic boot
>>>>> cancelled, by holding down either Control key as boot starts.
>>>> You've got to be very lucky with timing on some machines.
>>>>
>>>>
>>>> --
>>>> Please keep replies on the mailing list.
>>>>
>>
No comments:
Post a Comment