Slashdot Mirror
SUSE Linux Sold For $2.5 Billion (reuters.com)
Archangel Michael writes: Reuters is reporting that Britain's Micro Focus has agreed to sell its SUSE open-source enterprise software business to Swedish buyout group EQT Partners for $2.535 billion, lifting its shares 6 percent. Micro Focus, a serial acquirer that has been struggling to get to grips with a $8.8 billion Hewlett Packard Enterprise deal, said on Monday it would use some of the proceeds to reduce debt and could return some of the rest to shareholders. SUSE is used by banks, universities and government agencies around the world and is a pioneer in enterprise-grade Linux software serving companies such as Air India, Daimler and Total.
If SuSE is worth $2.5B, then what is Slackware worth?
All the main distros use it because it is good, a huge improvement.
If it is causing you problems, my advice is to look for some kind of "linux for dummies" type of book. Or better, stop pretending you're a sysadmin and breaking your web terminal; try sticking to the stuff in the GUI menu.
Will be interesting on how this works out with 'big banks', COBOL, SUSE and IBM Mainframes
Hey buddy, Slackware still has up-to-date libs and apps. Not that any poseurs would know.
Wrong. All the professional systems admins I know curse it, it is bad. I admin hundreds of systems and am sorry I'm being forced to upgrade them into the bloated, unstable, needlessly complicated garbage that is systemd.
It does not belong on enterprise servers, it is bad enginering.
All the main distros use it because it is good, a huge improvement.
SystemD is 2010s version of Microsoft wizards of the 1990s.
... wait, what ARE you doing? What IS that? Never mind, I'll just ignore it." And it gets confused or out of sync. And on any breakage, even better, now YOU'RE confused as well, and even worse YOU literally don't know what's going on.
;-) you begin to wonder.
They're great. They really are. They're easy to use, helpful, and just work.
That is until they don't. And then you're screwed
"Domain interpreters", if you will, are superb at what they do. They make all of the hard stuff "go away", kinda like programming libraries. That is, as long as you stay WITHIN their domain and do things as expected.
The moment you take one minor baby step outside what they expect or control, it all goes to Hell. It's confused because: "You're doing
SystemD hasn't broken on me yet, but I've heard horror stores of non-standard or even not-quite-mainstream configs that work and then they suddenly won't. And if you look at some of the bugs Pottering has declared WONTFIX (referred to by that random ignored bastion of unworthyness
The best thing about domain interpreters is that in a must-work complex situation is that you have to call for help. And who better than your distro maintainer? And then no reason at all, guess who SystemD's main author, Pottering, is employed by?
Oh, Debian is the literal base for a bunch of distros, including Ubuntu. RedHat also supports a few you might have heard of. You might be interested in the Debian vote for SystemD.
I'm a RHCE, SuSE something, Microsoft something, Novell CNE, and what-all else, or at least was -- retired, so guess I don't count anymore. Once I get my storage usage under control, I'm beginning a move to FreeBSD.
If you've "broken your web terminal" you should run "reset". And your homepage seems to be currently down, BTW.
If the universe is someone's simulation -- does that mean the stars are just stuck pixels?
Blog post: https://www.suse.com/c/further...
Yes. https://www.microfocus.com/pro...
Post says SuSE is used by banks, etc., but many companies also use it. I know the servers at local Wal-marts are using it, for example.
on a headless debian system, I had the joy of systemd dropping out to an emergency shell
Trouble was SSH wasn't up and running at this point so it was impossible to access this emergency shell.
The reason for the emergency, an external data drive wasn't present.
Blarney Quality Restaurant, Plants
This. I've yet to meet a full time unix admin (and that doesn't mean a basement dweller who managed to install ubuntu on their laptop) who actually liked it or could make a good case for it.
It's usually something along the lines of "well, yes, can't deny that our service (non-)management could use some improvement so I can see the original drive behind systemd, but it's a complete dumpster fire at this point"
Now if you'll excuse me, I have to figure out why rc.local is run before half the other services; what actually causes it to run and with what environment. Too bad this is not a matter of debugging shell scripts anymore. Because recompiling systemd with debug symbols and then hooking up a debugger to it is so much better.
Except not.
CLI paste? paste.pr0.tips!
The reason for the emergency, an external data drive wasn't present.
So admin did something incredibly stupid requiring the automounting of an external device at boot time and is upset that his misconfiguration caused his system to boot.
Got it.
All the main distros use it because it is good, a huge improvement.
If it is causing you problems, my advice is to look for some kind of "linux for dummies" type of book. Or better, stop pretending you're a sysadmin and breaking your web terminal; try sticking to the stuff in the GUI menu.
you are kidding right?
systemd is bringing MS and Apple grade development to Linux.
do you remember this https://github.com/systemd/sys... ?
this one https://github.com/systemd/sys... ?
and there's another ridiculous one with the usernames allowed or forbidden by logind.
The problem with systemd is not systemd, but its dev team.
The worst part of pettering's(I know he hates it when his name is mi-spelled) development is the fact that he chooses sometimes to have systemd taking decisions because systemd take into consideration that targets users but other times systemd doesn't have to take decisions because systemd is supposed to be configured by maintainers and not by users.
I know that some other smaller init might not have the sources or the influence and funding that systemd has by redhat, but when you complain to those devs that their s/w is causing rm to brick motherboards, they prevent it and they add to their documentation that if you want to write to some special block that affects your motherboard's firmware, you should, as a dev, remount it with w+. Peotterring otoh, says that's not a bug and you shouldn't rm -rf / .
A guy walk into a doctors office.
-Doctor, when I do this my arm hurts.
-Then don't do it. [not a bug][closed]
Nobody wakes up one day and decides to shit on peotterring via github tickets. The guy is just a code monkey, yeah those exist in C dev too, and is unable to steer or manage projects.
I'd suggest you read a "logic for dummies" type of book.
I use a CentOS 7 as a development workstation and multiple test, staging and production servers. All with systemd. It is reliable and gives me no trouble at all.
Hmm, I dual boot with windows - and this is the main issue I've had with systemd
pre-systemd, windows would sometimes leave its FS in an "unclean" state, and upstart(?) would happily boot providing a warning about failing to mount the FS.
post-systemd, In the same situation, I get dropped into a limited shell, with no reason given, and a note to look at the log.
It's not a big issue for me, fixable, I can just remove those items from fstab (Note - I did not add them, the *buntu installer did!) - but still, this kind of things are a bigger problem for new users, make linux look bad, and can be a much more serious problem in a server environment.
I'd accept it failing to boot if it could not mount a partition it _needed_ to boot... but the way it is setup right now just seems silly.
Seems you don't get it. Running sysv-rc init doesn't have the issue. On both my laptop and the one of my wife, I had configured the USB device to be mounted where I wanted to (I didn't really enjoy the /media stuff). On both, upgrade performed perfectly, only systemd refused to continue to boot because it didn't like the entry in fstab.
... it couldn't see the 2nd HDD of a RAID1 array. I saw it multiple times, as the 2nd SSD was going away of its socket in the Thinkpad ultrabay (fixed after a few of these failures with ... a piece of paper to prevent it to move!). Now, explain to me what the point is to have redundancy, if it is just to double the chances of failure to boot? And then what happens when the HDD is really dead?
This is *NOT* a problem by the sysadmin, this is a problem of change of behavior of the operating system caused by systemd. You will have a hard time convincing anyone that it's best to just stay stuck on an emergency shell rather than continuing to boot up to a point where the admin can do something with the compute.
I also had some very exasperating situation where systemd would refuse to boot because
Systemd has some good point. But it goes too far in many area, and has many troubles, nobody can deny that. To me, it's still a PoC. Maybe it will be reliable in 5 to 10 years from now...
Why are you systemd haters still thinking that systemd is exact replica of sysvinit, but newer code?
Thinking that this what systemd haters think is next level stupid. Nobody thinks this since it is obvious that systemd is a huge crapton of stuff beyond that. Hell even the init program consists of dozens of kilolines worth of source (cue you demonstrating your lack of understanding by telling me the source file isn't that much bigger than sysvinit's).
It is not. It is a completely different, new system, with new paradigms.
Yeah. And both the system and the paradigms are a pile of crap. It's confused people like you who think "newer is better" in the software world, because it's generally like this for material things that are subject to wear over time.
You don't do rc.local under systemd
Yet enough systemd based distros offer rc.local.
you write a proper service and get the FULL advantage of the entire process management API.
Oh nice! I can't wait for the "FULL advantage of the entire process management API" (seriously you sound like an advertiser) when spinning down hard disks at after system bootup, and setting my keyboard layout. Incredibly helpful to have this run through a huge blob so what it fails (and it does), instead of debugging a shell script I have to rebuild systemd with debugging symbols and attach a debugger or trace it. Great value.
nobody is taking them away from you.
Except they are, by more and more stuff indirectly depending on systemd. Personally I run BSDs where I can, but I still feel the systemd breakage at work and on computers I maintain for others, like my parents. The other day I could no longer run Xfce on my parent's computer, because some dependencies of its dependencies of its dependencies now depend on systemd. Great value. This is where I migrated them to Devuan.
And don't even get me started on the "clean up behind us" arrogance of the systemd developers and fanboys (like you)
CLI paste? paste.pr0.tips!