This is a massive miss-play on Suse’s part. Essentially all the good will, and recognition I have for Suse is based on OpenSuse. It’s the reason many of the places I’ve worked at now run a Suse product instead of redhat. Seriously, when I think of OpenSuse and Suse as a whole I barely differentiate the toonunlike redhat and fedora. That’s likely the reason for the switch but I cannot see how-this does anything but benefit them.
From the article too there are some concerns. Suse is, admittedly, trying to cause opensuse to change direction ans managment to further suit it’s buisness at threat of removing support. This is sad to see.
personally i always found stow to be annoying to use and switched to a bare git-repo approach. you can read up on it over here: www.atlassian.com/git/tutorials/dotfiles. Like this your dotfiles just rest where they should and it’s rather minimal overhead.
Looks like the installer and grub is confused about the hard drive order different in instaler and different while booting, both those drives could also have the same partition/drive ID making it confused, that could happen if you cloned/copied the drive in the past
I would say as a easy and safe solution
unplug all other drives that you don’t want install linux
Install Linux (best by formatting whole drive) - it should work just fine at this point
After confirming everything works - connect the other drives back
If Linux no longer boots after adding drives then tweak disk boot order in BIOS
There’s always been the risk of confusion and openSUSE project seemed to have understood that SUSE could disallow the name at any moment. A name change does make sense for both. Especially now that even Leap might be distancing itself from SLE and whatnot.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.