Page MenuHomeFreeBSD

Offer all efi/uefi programs under both names since we've been inconsistent about what we call efi/uefi as have others in the industry.
AbandonedPublic

Authored by imp on Jan 24 2018, 5:30 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jan 3, 9:12 PM
Unknown Object (File)
Nov 30 2024, 7:49 PM
Unknown Object (File)
Nov 29 2024, 12:43 AM
Unknown Object (File)
Nov 29 2024, 12:42 AM
Unknown Object (File)
Nov 29 2024, 12:24 AM
Unknown Object (File)
Sep 25 2024, 11:06 PM
Unknown Object (File)
Sep 25 2024, 8:24 AM
Unknown Object (File)
Sep 25 2024, 3:19 AM
Subscribers

Details

Reviewers
manu
emaste

Diff Detail

Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 14557
Build 14694: arc lint + arc unit

Event Timeline

This revision is now accepted and ready to land.Jan 24 2018, 5:58 PM

Probably would be nice to link efi.8 to uefi.8 too?

I don't think it's reasonable to offer uefi* things under efi* names where they don't already exist and we're not emulating a tool that exists on other systems.

emaste requested changes to this revision.Jan 24 2018, 6:13 PM

I disagree with making these all available under both names. I'm fine with standardizing on efi* going forward, but then let's make efi* compat links only for the uefi* names, not uefi* compat links.

This revision now requires changes to proceed.Jan 24 2018, 6:13 PM

As @jhb pointed out we should also add MLINKS=uefi.8 efi.8.

We should later update uefi.8 - .Xr the tools added after uefi.8, likely change the uefisign .Xr to efisign, and perhaps explain the ambiguity.

I took the first trivial step towards uefi.8 update in D14033.

linimon retitled this revision from Offser all efi/uefi programs under both names since we've been inconsistent about what we call efi/uefi as have others in the industry. to Offer all efi/uefi programs under both names since we've been inconsistent about what we call efi/uefi as have others in the industry..Jul 19 2018, 2:45 AM