I hope that SUSE saved the staff of Rancher from the previous assholes who ran the place. God that was an absolutely awful company to work for. I'm glad they started their own stupid acorn or whatever service nobody will ever use. Rancher had a lot of incredibly intelligent people who were treated like absolute shit.
SUSE to go private
141–150 of 245 posts
Re: SUSE to go private
#142Earlier quoted context omitted.
Open Build System and OpenQA, for automated building and testing of packages. This is what gets updates to their rolling release Tumbleweed faster than Arch, but with no instability ever. I can't emphasize enough how rock solid Tumbleweed is. OBS also doubles as their own AUR equivalent - you can make your own repo and do your own builds and install from the command line, or browse and install what other people have…
> faster than Arch that's a thing I haven't heard in a long time
Re: SUSE to go private
#143Earlier quoted context omitted.
Many could argue that Dell improved substantially after its 2013 transition to private ownership. At least, from the consumer perspective, things improved drastically. Linux support, a wider variety of competitive lines with much needed improvements to legacy lines, adoption of AMD for CPUs/GPUs, etc. I can't speak of their server/enterprise business, however.
I think Dell went downhill after the acquisition, their hardware quality is junk all across their line: servers, workstations, laptops, monitors, etc. Every device from them that I had my hands on recently have, at best, terrible build quality, and at worst, multiple failures. And their support is a bad joke.
Re: SUSE to go private
#144I am cautiously optimistic. From the article: > Both SUSE’s Management and Supervisory Boards have expressed support for the strategic opportunity presented by this delisting. They believe that it will enable SUSE to concentrate on its operational priorities and the execution of its long-term strategy without the pressure of public markets. Lets hope their incentives more strongly align with their customers, now. I a…
Can you elaborate please?
Re: SUSE to go private
#145Earlier quoted context omitted.
I ran SUSE around the same time (2001-2002ish), because it was the only major distro (between RH and Mandrake, primarily) that would install on my archaic 128MB PII. Debian worked but my grade school brain had no capacity for setting up Xfree86 manually. I stuck to SUSE for about 1.5 years before switching to Mandrake (and, eventually, Fedora Core) on my new Athlon XP desktop. My nostalgia for them will probably alwa…
Sounds like we pretty much had the same Linux story! I started with SuSE 7 (purchased it!), then Mandrake, then Fedora, then Ubuntu, then Arch and now reluctantly back on Xubuntu because I can't get my laptop to sleep properly on Arch... Do you remember why you switched from SuSE? I only have vague memories but I feel like the package manager might have been a bit clunky? Maybe I should give openSUSE another go, I re…
The other half was that whenever I searched for an RPM for something I needed, it was almost always a Mandrake or RH package. RH was a pain with things like MP3s and proprietary drivers, so Mandrake seemed obvious. And yeah, SaX/YaST was a little clunkier than Drak.
I went to Fedora Core in their first version because the third party repositories became seamless enough and they were easily the best supported, especially for on-the-edge software.
Went through some Arch, Gentoo, Ubuntu, Pop_OS! etc days in-between there but have mostly settled on Fedora KDE, these days.
Re: SUSE to go private
#146Earlier quoted context omitted.
Open Build System and OpenQA, for automated building and testing of packages. This is what gets updates to their rolling release Tumbleweed faster than Arch, but with no instability ever. I can't emphasize enough how rock solid Tumbleweed is. OBS also doubles as their own AUR equivalent - you can make your own repo and do your own builds and install from the command line, or browse and install what other people have…
+1 for zypper. The GUI feels very "enterprise-y" but in a good way. You just pick the software you want and it gets the job done quickly and with a minimum of fuss.
Re: SUSE to go private
#147I am cautiously optimistic. From the article: > Both SUSE’s Management and Supervisory Boards have expressed support for the strategic opportunity presented by this delisting. They believe that it will enable SUSE to concentrate on its operational priorities and the execution of its long-term strategy without the pressure of public markets. Lets hope their incentives more strongly align with their customers, now. I a…
Re: SUSE to go private
#148I am cautiously optimistic. From the article: > Both SUSE’s Management and Supervisory Boards have expressed support for the strategic opportunity presented by this delisting. They believe that it will enable SUSE to concentrate on its operational priorities and the execution of its long-term strategy without the pressure of public markets. Lets hope their incentives more strongly align with their customers, now. I a…
Re: SUSE to go private
#149Earlier quoted context omitted.
I used to run SUSE about 20 years ago and have always thought it was cool but haven't kept up with it much since then. What are some of the things they do that make them unparalleled?
[flagged]
Re: SUSE to go private
#150Earlier quoted context omitted.
Open Build System and OpenQA, for automated building and testing of packages. This is what gets updates to their rolling release Tumbleweed faster than Arch, but with no instability ever. I can't emphasize enough how rock solid Tumbleweed is. OBS also doubles as their own AUR equivalent - you can make your own repo and do your own builds and install from the command line, or browse and install what other people have…
I have been using Tumbleweed for a few years now, but while it seems like a stable rolling release distribution, I am not quite sure about the "rolling release" part. Each month, a new snapshot comes out, which upgrades every single package you have installed, regardless of whether there were actual upstream updates. With a full Texlive installation and just a few more suites this amount to roughly 10,000 packages an…
A) Snapshots come out far more regularly then once a month. Going from the mailing list we've actually had a snapshot released every day since the 4th. I'd say the average is one every three days but that's just from the top of my head.
B) they do not cover every package you have installed: They don't even know what packages you have installed, snapshots are cut on the repo side. It's true that packages get rebuilt a lot but that's because either the package updated or a dependency of the package updated that caused the package to be rebuilt.