SFaulken

joined 2 years ago
 

Just wanted to drop there here, in case anybody finds it useful. I started doing some blogging, mostly with the intention of archiving how in the hell I've done things on Linux, in the past, so I know where to find them the next time I need to do them. There will probably be other stuff there, with time, some of it not linux related, but I'll tag the relevant stuff, so it's easier to find.

[–] SFaulken@kbin.social 7 points 2 years ago (1 children)

Yes, Printer setup on openSUSE is still a clusterfuck, for reasons. You're best off in openSUSE KDE to just point your webbrowser at http://localhost:631 and log directly into CUPS and setup your printers that way.

If you want all your web video and whatnot to work, you need to install the codecs from Packman, in their entirety, or use a flatpak'd web browser. openSUSE won't ship patent encumbered codecs from the official repositories.

Unless you really know what you're doing, with Leap, or Tumbleweed, stick with the OSS and non-OSS repos provided. They are the ones that have been through the openQA process, and are officially "supported". If you enable a bunch of home: devel: or other repositories, just assume that they're unstable, and use at your own risk. If you're looking at a repository on OBS, and don't see openSUSE_Tumbleweed as one of the build targets, then forcing the install with a Leap or SLE package, may, or may not break things.

Regarding zypper ref and autorefresh, I can't recall exactly, but there is the chance that just running zypper dup and hoping that it refreshes everything on it's own, with non-standard repositories may fail, which can lead to some weird edgecases.

Just in general, you're going to want to run zypper ref && zypper dup (not the other way round) As far as YaST being targetted more at Leap than Tumbleweed, you're exactly right. And there's a reason that we don't ship it with newer flavours of the distribution.

[–] SFaulken@kbin.social 6 points 2 years ago

Well none of that sounds like sketchy behavior on the part of the Management Company.

Not at all.

[–] SFaulken@kbin.social 1 points 2 years ago* (last edited 2 years ago)

Correct, SUSE, the corporation is no longer providing a traditional linux distribution, after the SLE-15 EOL.

openSUSE, which is a community project, and not controlled by SUSE, is currently debating as to whether we have the contributors interested in doing so, and in sufficient numbers, to continue to provide a traditional point release distribution.

Tumbleweed (the rolling release) is not going anywhere. The community has not yet decided if the interest and manpower is there to use the ALP sources provided by SUSE to create A) A traditional linux distribution, akin to what Leap currently is, B) a "Slowroll" version of Tumbleweed, that has a slower release cycle, or C) Nothing at all, because there isn't the community there to support the development of it.

SUSE != openSUSE

[–] SFaulken@kbin.social 1 points 2 years ago

That is indeed the big question, if there's nobody willing to put in the work, then there's nothing to release.

Maintaining something like Leap, with the contributor base that has historically existed, isn't sustainable, long term, especially when the upstream is going in a different direction.

 

The openSUSE Project is pleased to announce its modern lightweight host operating system Leap Micro 5.5 just entered Alpha. This release brings a host of enh...

 

The openSUSE contributor community recently completed a comprehensive survey last week aimed at determining the project’s future direction. The results were ...

[–] SFaulken@kbin.social 1 points 2 years ago

This pretty much backs up what I've been seeing. Everybody wants to use Leap, nobody wants to work on it.

[–] SFaulken@kbin.social 1 points 2 years ago

The change listed in the upstream bug has been in Tumbleweed for months, I see you're running Tumbleweed, So this is obviously a bug. Please file a bug at bugzilla.opensuse.org, as there currently isn't one existing. (I'm not encountering this bug, just saying)

[–] SFaulken@kbin.social 3 points 2 years ago* (last edited 2 years ago) (1 children)

The change shown in the upstream bug has been made in the openSUSE Tumbleweed Packages, months ago. Are you using Leap, or Tumbleweed?

edit:
I actually read the whole post. Since you're on Tumbleweed, this is indeed a bug, please file one at bugzilla.opensuse.org

 

So I've been in King and Snohomish county now for basically a decade, and even though I have a G2G account, and have had for years, has this thing ever worked?

I just got another mailed toll bill for crossing 520 from Bellevue to Seattle a couple weeks ago. So I go check my G2G account, and sure as hell, all of my vehicles license plates are registered in the system, I walked outside and looked in my pickup, and their little "tag" is right there on the windshield where it belongs, the balance available on the account is more than sufficient to cover the toll.

I don't mind paying the tolls when I use the services (this post isn't a complaint about the tolls themselves), but what use is this registration system, when it seems like I get mailed a friggin toll bill probably 50% of the time I do something that requires me to pay a toll, and manually have to go pay the bloody thing?

[–] SFaulken@kbin.social 1 points 2 years ago

I highly doubt this is ever going to happen. It's not what zypper is designed for. Its easy enough to write a bash alias, or shell script to combine the two commands.

[–] SFaulken@kbin.social 1 points 2 years ago

Bah. This is just a piece of clickbait nonsense, or somebody trying to be edgy. I'm actually mildly offended by their "review" of "On the Road". Just makes me think that they probably haven't ever read anything other than somebody elses review of it.

[–] SFaulken@kbin.social 3 points 2 years ago

Well, RIP Simon & Schuster. I give em five years, tops.

[–] SFaulken@kbin.social 10 points 2 years ago

I don't care about beeper one way or another, but that bloody image with the post, it needs to die in a fire.

 

More about Red Hat's decision to make CentOS Stream the primary repository for RHEL sources.

 

So does anybody have a walkthrough on how to set this beastie up? I'm not unfamiliar with docker and containers (I have personal Mastodon, Nextcloud, and Synapse Instances running via docker-compose)

Sort of where I'm stuck right now is what I need to change in the .env file, per the instructions here:

$ sudo apt-get install git
$ git clone https://codeberg.org/Kbin/kbin-core.git kbin
$ cd kbin
$ mkdir public/media
$ sudo chown 82:82 public/media
$ sudo chown 82:82 var
$ cp .env.example .env
$ vi .env # esc + !q + enter to exit
or
$ nano .env

Make sure you have substituted all the passwords and configured the basic services in .env file.

(yes, I know it's somewhat commented, but it's not exactly super clear) and also how to handle building it in a non-local configuration (my VPS is elsewhere, so going to kbin.localhost to do anything isn't really going to work)

So yeah, ELI5.

 

It’s been an exciting week for people who care about Linux distributions, FOSS licensing, FOSS distribution, FOSS business models, and the future of open source in general. Red Hat’s an…

view more: next ›