4 ms·
I think the end-all-be-all of this obviously spiraling conversation is: the other user expected SLES to be a drop-in replacement for RHEL/CentOS, but it wasn't.
by starttoaster 3y ago
I think the end-all-be-all of this obviously spiraling conversation is: the other user expected SLES to be a drop-in replacement for RHEL/CentOS, but it wasn't. So why did they not consider Suse for their enterprise uses? Because they had existing workflows that work on RHEL-like operating systems, and Suse would require more work and time to adopt than those alternatives. All of that is completely fair and valid. And to make your point: all you have to do is learn the operating system and suddenly that's not much of a concern any more. If the free alternatives aren't as feasible in the future, I'm sure there may be more appetite for that kind of effort.
- Arnavion 3y agoI don't really have any comment on whether SLES was suitable for their RHEL shop or not. This entire subthread rabbit hole is just about their absurd assumption that packages can be transplanted between distros and their subsequent doubling-down on it.
- tiberious726 3y agoEh... It's absurd if you actually know how packages work or have ever built a package. A Linux end user, just starting out experimenting with different distros trying to install random packages they find online and not reading the right high-level documentation (like that debian link above) could very easily have the (false) experience that there are three kinds of Linuxes inside of which packages are largely interopable: RPM, DEB, and pacman . And to be fair, if they don't mind really messing up their system and bring enough different versioned dependencies in, this is kinda true, at least until they try to update. SUSE completely breaks this illusion. This thread brought me back to when I was first messing with Linux distros, I used some insane program called something like 'alien' to try to install .deb packages into Fedore Core, with no idea how wrong minded that whole enterprise was