Assuming your efi partition is sda1:

mkfs.vfat /dev/sda1

1 members found this post helpful.

According to slackware.com, 14.2 came out in July of 2016, just over three years ago. Still, this is a valid question.

While I am aware that Patrick is a single person doing an entire distro (having maintained a BLFS system for a while, I can understand some of what that feels like), three years is overlong without (a) a release nor (b) an Official Announcement. What is wrong?

p.s. In the meantime, the last two Slackware installs I've done have been snapshots of Current. If Patrick is switching to a rolling release model, should he just make it official and announce it?

Slackware is not moving towards a rolling release moving, just taking its time for the next stable release.

Why would you assume that? It's not up-to-the-minute being an i5 on a Z77 Extreme chipset but it isn't ancient let alone 32 bit. For me it's all about Cost/Benefit. With UEFI it is required to jump through several additional hoops including special partitioning and creation and all for exactly what benefit?

3 members found this post helpful.

Why do you imagine something is wrong? Is there something you cannot do on 14.2?

This may possibly answer both questions above. Do you even have a 14.2 install or only Current? If you have only Current it may well mean that you prefer a rolling release for some reason completely beyond me. I've tried several rolling releases and to me they are a PITA. I end up spending more time in maintenance mode than getting anything actually productive done.

1 members found this post helpful.

Build adriconf.
Build dxvk.
Build libreoffice-6.3.0.4...

This list can go on for a while if you wish.

2 members found this post helpful.

And that's it? Dang... so I do this before the install, then when I install everything should work?? That is so simple....

That's my position exactly, too.

I keep being told that I should use UEFI boot, because, for instance, "Legacy BIOS mode is buggy." Even if it is, then:

• I, for one, don't seem to run into these bugs;
• Can't the same be said about UEFI mode?

In any case, the only computer that I left in UEFI mode, is my dad's laptop, because he wanted to keep Windows 10 installed. It is also the only computer on which the boot order of the installed operating systems is unstable, and I've given up trying to figure out if there's anything I can do about it. Now, I have no idea if this is a Windows, Ubuntu, or UEFI issue, or some combination of the above, but I do know that on the computers that run Legacy BIOS mode (and on which Windows is not installed), this issue does not occur.

An additional advantage of Legacy BIOS mode, with GPT-partitioned disks, is that Windows won't even run. Good riddance!

1 members found this post helpful.

Interesting rumour. I have three laptops that run Slackware in legacy, and they have had no problems whatsoever.

The only computer I've had issues with [hard lockups etc] is my converted Chromebook, but that's not really a surprise. It runs Xubuntu anyway, not Slackware.

1 members found this post helpful.

Same. I have three laptops and three desktops running Slackware64-current.

2 members found this post helpful.

My experience with UEFI was that it was a pretty simple transition from lilo to elilo. The reason I switched was because I had a new motherboard and I know at some point, legacy booting won't be available anymore (although, I believe that is still many years away) and I wanted to be prepared for UEFI when I no longer had the option for legacy. I was fully prepared to throw my hands up in exasperation after expecting to struggle getting it setup, but I never ran into any snags, so I just stuck with it. I've now installed 3-4 systems using UEFI and it's all been pretty easy.

I can't really say that one is easier than the other because both have benefits and drawbacks, but I was expecting a headache and it was actually pretty easy. And from my understanding, most of my issues with elilo (the biggest being it's more difficult to switch between multiple boot stanzas) are solved when using rEFInd (and probably grub, but I've never had the desire to learn grub), but I've been too lazy to try it out.

1 members found this post helpful.

Well, one example is that 14.2 is not good on HiDPI screens (like my laptop), which makes using the system difficult. As far as I know, something like Xfce 4.14 or Plasma 5 would be an improvement (or Cinnamon, perhaps MATE), but none of these are even in -current let alone 14.2, and they require some effort to add with additional uncertainty for things like Plasma 5 if they will even continue to be around in the future (say if the Plasma 5 dependencies aren't added to -current and Eric decides to drop it). The version of Zathura (minimalist PDF reader) that supports HiDPI won't compile on 14.2 because of old libraries, and I get quite a few crashes on Okular 0.20.3 when recompiling stuff in LaTeX with the document open in Okular. Is it fixed in newer releases? Maybe so, but trying that is fairly intrusive on -current, and not possible on 14.2 with the latest releases. From looking at the release page, Okular 0.20.x must be of 2014 vintage. I'm not saying that Pat is obliged to do anything, but as the years pass then it becomes more true that yes, there are things you cannot do that you might like/need to.

3 members found this post helpful.

I see there were some posts about UEFI installations.

This post helped me with that. A lot.

https://www.linuxquestions.org/quest...6/#post5409238

It's not that difficult to learn. As you can see from my post above, it is really quite easy. EFI booting is simply about having the right files in the right place.
Well, for one there's future-proofing. MBR partitioning doesn't work on disks larger than 2Tb.
Then there's flexibility and ease of use. EFI booting is easier, safer and more flexible, especially if you use Linux and like to experiment with different kernels, distributions, etc.
You've got a 64 bit machine, but you've hamstrung it with 32 bit ways... This is free software. It's not going to cost you anything to learn, other than a few minutes of your time.

1 members found this post helpful.

ok, so like what slackdoc did you use?

same here

Thanks!