Linux is not Windows, advise them to get new hardware (probably a good thing performance wise, or maybe only lack of TPM 2.0?), or use the new Rufus version to create a Windows 11 iso image and upgrade…
Suggest Aeon or Kalpa and use flatpaks? I’ve found in my simple tests for a few Windows apps that Bottles works fine.
Setup a VM or maybe WSL to test things out in Windows?
Else get a Mac system…
Tumbleweed is a development platform, users should expect issues and some expectation that they can at least resolve the simple ones? We post the snapshot release details, check that out to see what is being updated, read the changelog summaries.
Likewise the plethora of new hardware with no linux support (eg wifi) or newer Intel ARC and NPU support.
Sorry for this late question - I’ve only read this thread today, linked from the Summary Forums Newsletter.
Is this change also planned for Leap 16.0 and Leap 15.6 (until EOL in April)?
Asked because the EFI partitions on my notebook (fresh installed 16.0) and Desktop-PC have both 100 MB size.
If yes, is anybody knows approximately when
Thanks in advance for answer!
Such changes never affect a released Leap or SLES distribution, so no, it won’t affect Leap 15.6 or 16.0.
I am not sure about Leap 16.1, though; but since Leap is very near to the corresponding SLES, I doubt that within a major SLES release (16) there will be such a change.
Right now for Leap 15.6, you can always switch the bootloader type in a YaST installation to grub2-efi and keep your existing ESP partition.
For an Agama installation (16.x), I am very sure that the bootloader type will be configurable if there is more than one to choose from. Right there are only few parameters to configure.
Thanks a lot for the information!
It is comforting to know, it is not needed to change the disk partition for the next time.
… and I really hope, the openSUSE developers team will implement the grub-option in Agama on a future Leap version. As I am not a programmer nor an OS admin, I would be not able to configure Agama myself.
BTW: I appreciate a lot of your comments about the changes in SUSE environment. I don’t want to degenerate the purpose of this thread, but I see in the SUSE changes a - maybe indirect - dependency to social and economy changes in the States.
Adding my two cents, following with @shundhammer comments . . . yes, “change is inevitable,” but that doesn’t always mean “all change is good” . . . specifically in reference to grub-efi changing to grub-bls. The folks who do multi-boot such as myself, find that grub-efi actually works . . . but from discussion on the Factory list, it seems that grub-bls does not do multi-boot?
I have a Pop_OS system installed on a laptop and they also put the kernel in the bootloader partition, which hogs up space and, like the OP’s 44M /boot partition, that can be filled quickly. I get that grub boots the kernel, but does that mean it has to be storing kernels there??
Obviously for the common end user, running one distro, and running one kernel it might be moot. But for those who might want to expand their “universe” of distros or kernels, having the option of selecting grub-efi should be provided . . . especially considering that TW is a “development” distribution, having it flexible for those who like options rather than “one size fits all that a few devs have selected for you” . . . doesn’t sound like the “mission vision” of openSUSE???
It’s only the default, not like it can’t be changed. That’s the thing though, as you alluded too, it’s the development product, so things do change. Users should following the relevant mailing list to see what is happening… In a past time, folks called it reading… a skill that seems to be declining these days…
Likewise with today’s modern hardware, users can use the likes of virtualization to run environments, distrobox to test/use applications provided by other distributions etc.
Alrighty, “default” that could be changed is good. In the quick read through this post it seemed like it was implied that “this is what will be happening and best be prepared for the consequences of it.”
Others also mentioned “development” here, but as I referred, that should be a “two way” street, in that, those using it can “develop” it as they wish, not get locked into a one way street, etc. Other distros such as ubuntu, also seem to be doing stuff with grub such that they are the only system that it will boot . . . making it harder to do multi-boot . . . so that seems to be the trend . . . in linux, which should be for exploration and development, rather than channelizing everything to system control . . . that would be like Apple and Windows???
Thanks for the band width, please resume with normal programming . . . .
So I have a Tumbleweed setup using grub-bls dual booting with Windows 11, I just hit the BIOS boot key (F12) and select Windows Boot Manager if want to use, seems like grub-efi which still requires keyboard interaction? If want to boot next to Windows 11 from Tumbleweed, I just use the efibootmgr -n option…
OK, good to know those details . . . although dual-boot isn’t too complicated to run . . . . I try to stay out of the BIOS keystroke on booting, which is an extra step . . . in my recent home built “KISS” inspired machine I now have 8 linux distros running on two drives, when I boot the machine the grub window loads and it shows my options, which I can arrow down to and select. TW handles the os-prober duties right now, grub was removed from as many of the other systems as would allow, Lubuntu would not allow that, but os-prober is turned off. No Windows options on that machine.
On my older '12 cMP that I was using for much of my previous interactions on the TW forum that machine has 5 or 6 versions of OSX && 7 linux distros sharing 4 drives. If I cold boot, the grub-EFI window loads and shows me the linux options . . . I never had the time or capacity to rig up the OSX installs, but largely wasn’t using them. If I wanted OSX I hit the option key and the OSX bootloader would load the OSX options . . . sort of like the BIOS bootloader. Since the OSX systems would not share or recognize data or docs from linux, had no reason to switch back and forth while booted in one; the twain shall never meet. Might be different with Windows, but then I was a “Mac guy” . . . never had any use for Windows.
From a post from one of the other, the few, the proud, multi-booters . . . who was running a high number of distros via grub, there is/was a limitation to the grub-bls capacity vis “multi-booting.”
I am hoping there isn’t a need to run a fresh install of anything for awhile, but I would be hoping/looking for a grub-efi option on the bootloader. I like a tidy /boot/efi directory . . . don’t like a bunch of kernel data adding weight to it, etc. Max space used 500MB. : - )))
Ah . . . thanks for the clarification . . . I was scanning fast, trying to “have a life” and yet get a “vote” in for keeping grub2 as an available option in the openSUSE world.
