i was wrong. i misread the article thinking that opensuse was going to turn into an analogue similar to centos stream ending up with suse eventually sun setting opensuse like red hat is doing with centos; but no, they’re ARE doing a centos stream like model but it’s going to be back and forth between opensuse leap and opensuse tumbleweed.
opensuse is back on the recommended list. lol
then i feel sorry for you too. lol
if your session is still running you can use env to help reconstruct it
i take back what i said; i just discovered that suse isn’t going to support opensuse anymore.
i always felt that the old dell powerconnect line of switches’ operating system was a knockoff of cisco’s; so i can say with confidence that, that sticker was probably more useful than the old powerconnects. lol
i used to have a 2013 macbook air from the electronics disposal bin and used it for five years as my daily driver. i don’t know how well it would do considering all your audio related constraints; but in your shoes i would do some quick and dirty testing with a live linux distribution on usb drive.
i would go with elive because it comes preinstalled with proprietary software; including things for multimedia, like codecs. you could also do it w any other distro, but why not save yourself the extra steps; since we’re only looking for breadcrumbs to follow anyways.
i used to use a headset w a usb audio dongle circa 2002 on red hat linux and the breadcrumbs i found back then led me to discover that getting it to work required the proprietary software that the distros wouldn’t carry because of the licensing. so i spent days tearing apart my new installation trying to get it to work with the help of strangers on internet linux forums and ultimately failed; i later succeeded with mandrake linux and ran with that for about 3ish years before switching to debian and later elive.
elive has already figured out all the intricate details necessary to get that software to work and i’m inclined to believe that they made significant improvements over the last 20ish years. you can use the fruits of their labor for a quick and non-invasive test that can be the first breadcrumb that leads you to whatever you end up using for your two machines while ensuring your audio requirements will be met; maybe elive can also help with other proprietary software or maybe it’s people on the software that they use that are like yours.
also: you lost me on Focusrite Audio-Interface paragraph so i don’t understand how it fits into any of this.
do you have any intel related packages in your system? you can search with something like apt-cache search intel
if it turns out you don’t and you’re certain that it’s okay for you then you can probably add a repository for it.
i can’t stress enough the part where you need to be certain that you need it.
i use xfce, but entirely because it worked well when 16 megabytes of ram was considered average and it literally took almost a half hour to log in and start using a browser on both gnome and kde.
is mate as lightweight as xfce?
androids can’t do base distro’s anymore?
the touch screen support was TERRIBLE, but it was helped a lot by the physical slide-out keyboard and i never got the phone capabilities to work correctly, but i heard from my colleagues at the time that some of them had figured it out.
Well duh, a comparatively tiny amount of minorities changing how they vote or not voting doesn’t matter if A MAJORITY of all white people can’t be counted on to vote for racism.
fixed it for you.
in case you didn’t know: democrats haven’t had the majority white vote since the 1960’s
… nowadays it’s in my top 3 list when I’m suggesting distros to people
same here; but only because of the support like red hat’s and canonical’s
fwiw: it was viable when i had the first android released to the public; it was an HTC and with debian.
With imperative style, you have a lot of implicit state that you need to know to figure out what actually happened. So, you end up having to go through the steps of building that state up before you can start figuring out what went wrong.
i think i struggle with this part the most since i’m entirely self taught and relied on very old methods for writing my source since the educational material i used was the most common and freely available at the time i starting doing development work. i’ve learned that it was acceptably sufficient for the IT-based problems that i was trying to solve at the time i learned it and that legacy style has been keeping me at a disadvantage.
if seen some of the newer style of debugging like the one you’re shared from the young fresh graduate developers who are lucky enough to be spared the slog of a over decade within “customer service” oriented side of the tech industry umbrella and it’s painfully evident to me how vastly superior it is compared to the old methods that i taught myself and it’s encouraged me to seek a degree to help me master them and my new job will make that degree free for me; which matters A LOT as an american considering the price tag it entails.
opensuse was my shortest experiment when i used to distro hop because of how old their software seemed to be. (ie old like debian stable).
this was almost 20 years; has it gotten better?
but it’s so much easier to put in echo "if you can see this it worked" 100 times in your source. lol
clearing my head is why i’m doing it too
it might as well be since they’re all black pizza boxes with holes. lol
I bought a nifty blue Netgear 24-port one mostly because I’m more willing to buy junk from the Humane Society shop, but then decided it was too loud (40mm fans) and went to 2.5G (with smaller fanless switches) instead.
i used to marvel at people at people who setup racks in their own home with those LOUD blades because my time racking & stacking in all the data centers have lead to permanent hearing damage so seeing these people bring that into their home is wild to me.
Haha I’m guessing that was meant to say ActivityPub
yes, that’s what i get for going fast; thanks for the correction and the history lesson.
if you can find the source deb package for it, you can use that to try to construct a version that’s appropriate for your release.
or at least it’s true to for rpm packages from the last time i encountered a barrier like this on centos.