Date: Thu, 04 Jun 2026 06:38:46 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 295812] stand: stand/efi/loader/main.c: allow backup loader.env to be used Message-ID: <bug-295812-227-HTvUJRLw9n@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-295812-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295812 --- Comment #3 from Sulev-Madis Silber <bugs-freebsd-org916@ketas.si.pri.ee> --- sure, but i wasn't sure about naming should it be 8.3? maybe loader.prv / loader.nxt files? also was next file ever used, apart from if user patches it in manually in their build also i don't fully get what first argument of read_loader_env() is, is it just a name, not used for anything else? thats's why i was not even sure how to do this. let alone documenting it but i know if anything enters the tree, that's how it stays forever. people read it, learn to use it, and you can't take it back. well, easily that is. everyone would be pissed hence behaviour has no documentation because i have no idea what behaviour would end up like in the first place not the first time a feature would be source-only-documented. eg hw.userspace_allow_phys_counter so yeah you're right, documention is good to be honest, i was digging around a lot before i even found that /efi/freebsd/loader.env is a thing at all i also have https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283457 which also is kind of booty, still have no idea how to do that, nevermind how to document -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-295812-227-HTvUJRLw9n>