Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 01 Jun 2021 16:42:24 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 256343] Proposal for a generic boot/loader.conf, mainly for hints (in addition to defaults/loader.conf)
Message-ID:  <bug-256343-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256343

            Bug ID: 256343
           Summary: Proposal for a generic boot/loader.conf, mainly for
                    hints (in addition to defaults/loader.conf)
           Product: Base System
           Version: 13.0-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: conf
          Assignee: bugs@FreeBSD.org
          Reporter: bugzilla.freebsd@omnilan.de

Created attachment 225465
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D225465&action=
=3Dedit
Template/draft for a generic boot/loader.conf

Hello,

over the years, console has undergone massive changes in FreeBSD.
When we haven't had EFI, and sc(4) was the only video console available,
options were much simpler than today.
With the advent of vt(4), zfsloader, loader.efi - just to name a view - I l=
ost
overview.
And there's serial console of course too.  Still one of the most important
things to be aware about, imho.
Over the years, comments/hints in my various loader.conf versions grew and
differed significantly enough, that I started to confuse things myself.

So I merged all hints into some text for my personal, generic boot/loader.c=
onf
(template).

I'd like to share that and would like to know what you think about includin=
g a
generic boot/loader.conf by default - more or less like the one attached he=
re.
Of course in addition to boot/defaults/loader.conf.

Please note that the lines below ##platform/machine specifics# are not mean=
t to
be part of a possibly generic loader.conf- I left them intentionally for the
curious ones and in case there's something others frequently copy of that r=
eal
world example.

And please note, that I propose to set "vbe_max_resolution" by default - I =
see
no reason why we don't want the VESA switch to enable higher resolutions th=
an
640x480; the statement about the default switch to 800x600, if no EDID data
could be read, never worked for any of my (i386 resp. non-UEFI) setups.

-harry

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256343-227>