If this is your first visit, be sure to
check out the FAQ. You will have to register
before you can post. To start viewing messages,
select the forum that you want to visit from the selection below.
Please do not use the CODE tag when pasting content that contains formatting (colored, bold, underline, italic, etc) Use the QUOTE tag instead.
The CODE tag displays all content as plain text, including the formatting tags, making it difficult to read.
The following Topic Prefixes are designated for use in Community Cafe:
DS (Distribution Showdown)
GN (Geek News)
KLD (Kubuntu or Linux Discussion)
TWC (The Water Cooler)
KUT (Kubuntu User Testimony)
NRD (Next Release Discussion)
While use is not required, doing so allows for efficient Filtering.
I've been running opensuse tw and on another machine opensuse leap for best part of a year and not had any problems on either. I don't know whether I have a "production system" though
That is what I call a system one uses e.g. between 9:00 and 18.00, Monday to Friday, to earn one's livelihood or that is used in an industrial setting.
I don't know if it is the right English term for this, sorry.
PS: openSUSE Leap I would use for such a purpose, like Kubuntu LTS or Debian stable.
Last edited by Schwarzer Kater; Apr 10, 2024, 08:11 AM.
Reason: added PS
Debian KDE & LXQt • Kubuntu & Lubuntu • openSUSE KDE • Windows • macOS X Desktop: Lenovo ThinkCentre M75s • Laptop: Apple MacBook Pro 13" • and others
Basically, a PC you use and depend on, as opposed to a PC you just tinker with.
Windows no longer obstructs my view.
Using Kubuntu Linux since March 23, 2007.
"It is a capital mistake to theorize before one has data." - Sherlock Holmes
Am I correct in thinking that the recent liblzma compromise indicates a weakness in the rolling release approach? Those on supported *buntu releases were not affected.
Am I correct in thinking that the recent liblzma compromise indicates a weakness in the rolling release approach? Those on supported *buntu releases were not affected.
As I take it, the tarball was compromised, not the source git repository, and Arch (and Nix, Gentoo, and others) pull it directly from there. The malware is apparently only built from that tarball when using cmake (which isn't used for this on Arch), and only when building rpm/deb packages.
OT: Why would it be in Debianstable? Debian testing/unstable/experimental OK, but stable?
Officially the others are not meant for the "normal" user or "normal" usage at all AFAIK.
And at least unstable and experimental are rolling releases (and testing, too), or am I wrong?
Last edited by Schwarzer Kater; Apr 10, 2024, 04:46 PM.
Reason: typos et al.
Debian KDE & LXQt • Kubuntu & Lubuntu • openSUSE KDE • Windows • macOS X Desktop: Lenovo ThinkCentre M75s • Laptop: Apple MacBook Pro 13" • and others
Comment