LABEL="UEFI Firmware Settings"
gettext_printf "Adding boot menu entry for UEFI Firmware Settings ...\n" >&2
cat << EOF
if [ "\$grub_platform" = "efi" ]; then
fwsetup --is-supported
if [ "\$?" = 0 ]; then
menuentry '$LABEL' \$menuentry_id_option 'uefi-firmware' {
fwsetup
}
fwsetup --is-supported does not apply. If it did, you would have on your Grub Menu an entry such as I show here/boot/grub/x86_64-efi/efifwsetup.mod
# and
/usr/lib/grub/x86_64-efi/efifwsetup.mod
The difference is that you obey the computer, whereas I make the computer obey ME.
Said the same guy. Thanks for providing such a good entertainment.As for the uefi-firmware file, I don't even know why that file exists
I have just deleted another, from another Member.
If I get one more, I will be sending three people on 4 weeks unpaid leave, and it will not be to The Bahamas,
Please act your age, not your shoe size.
I don't recall anyone appointing you as the arbiter of who is hypocritical and using double standards, if they did, I missed the memo.
If you find a thread or Post objectionable the Report button is available and Staff will take a look.
Thank you.
(I did not know that. Huh!)I still vastly prefer the older Grub4DOS from Puppy's earlier times. Pup's build of this is 'patched' to search for kernels TWO layers deep, and our build is still maintained; to my way of thinking, it's very flexible, and extremely easy to modify to how the user wants it.
I never did such a thing. I have never made a personal attack or called anyone names in this thread.No need for name-calling, and personal attacks. Fer Chrissakes, we just discuss things here; if ya don't like the way the thread is going, just stop posting!
Of course, I'm fully aware of the powers moderators have, which is why I've used a randomly generated nickname for my profile. I've been a moderator myself in the past. I came here to speak freely with like-minded people. If I can't do that because moderators set an overly restrictive tone and continue to mute or ban users indiscriminately, I'll move on. Forums come and go.FWIW, most people that actively argue and find fault with forum staff almost always come to a sticky end. Just sayin'.....and I, too, know what I'm talking about, 'cos I moderate on two other fora.
Admittedly, this IS one of the reasons I like coming here. They're a good bunch, and here I'm just one of the crowd (for a change)...Of course, I'm fully aware of the powers moderators have, which is why I've used a randomly generated nickname for my profile. I've been a moderator myself in the past.
Sorry for the late answer. It's summer now and I'm rarely at home, hence at the computer. Most of the time I'm out there somewhere doing stuff with other humans, anything your imagination can think of.@rado84 , can you indulge me again? Resist OS does make itself clear to me, with searches.
Is that just a customised (by you) name you placed in grub.cfg, or is there a real Arch/Arch-based distro that applies to?
I would like to take it for a spin, and shake off the rust on installing under MBR conditions.
TIA
Wizard
[rado@resist]
[rado@arch]
Well done on your setup!I love it! My own MX-Linux mixture is a "protest" form, free of everything Big Tech and their minions are trying to force on users:
- XLibre instead of Xorg / XWayland
- Runit instead of systemd
- No Rust
- No bloat
Getting there took a bit of research and time, but it's as "ideologically pure" as I can make it. I just wish I would thought of that cool name!
So it doesn't have an installer in your iso or an install script? Are you going to replace systemd as it seems you are defining your "distribution" as a protest distribution? Please just call Windows by it's proper name, as mentioned in the posting guidelines written by @KGIII. Thanks!RESIST OS is of my own making and you won't find it anywhere because it doesn't exist in the form you'd expect - ISO and everything. It started as an idea to resist against every piece of software that is being forced upon the users, regardless of whether they're Winblows or Linux users.
Eventually the changes became so many that if you ask me now what they are, I won't be able to remember them all. Suffice to say ALL of the modification are hundreds, if not thousands of files by now with a total size of 1.8 GiB. Even some services are disabled and masked in accordance to RESIST's ideals - "no forced software". Then I realized that wasn't Arch anymore, it was something else that needed a new name and a new logo.
Don't call people or things names. Instead of using a pejorative, use the proper names/abbreviations.
The only thing I still haven't found out how to change (without breaking the whole system, that is) is the host name when I open terminal. I'd very much like it to read
[rado@resist]instead of
[rado@arch]but for the moment I haven't found a safe way to change it without reinstalling.
Maybe the following works. It works with bash on debian here as shown on the command line. For persistence the PS1 code can be placed in .bashrc.The only thing I still haven't found out how to change (without breaking the whole system, that is) is the host name when I open terminal. I'd very much like it to read
instead ofCode:[rado@resist]
but for the moment I haven't found a safe way to change it without reinstalling.Code:[rado@arch]
[ben@computer ~]$ PS1="[rado@resist] $"
[rado@resist] $