![](https://feddit.de/pictrs/image/7d050835-a5a4-4358-bde1-78c5c4a607e9.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
one of the main reasons the linux kernel is where it is today: “never break userspace”
unfortunately not every project keeps to this principle.
one of the main reasons the linux kernel is where it is today: “never break userspace”
unfortunately not every project keeps to this principle.
no package manager should put stuff into /usr/local, thats why its /usr/local. package manager should only put stuff into /usr/… not /usr/local. In the past some mainframes mounted these directory via nfs to do some kind of software management. It contains global stuff that is not managed by the package manager. install some software via “tarball and make” and it most likely puts everything into /usr/local/…
It’s the best location for your needs. /home/shared is a bad idea. /home is reserved for home directories not some shared stuff.
/usr/local is specifically what you are asking for. i would put themes to /usr/local/share/themes for example. chances are gtk will already look there. You can manage permissions inside /usr/local as you like. since the package manager doesn’t care for that directory there is no problem. giving write permissions only to root still is a good idea. it suggest to learn to use sudo when you are working on your system.
Why are you so angry? I never meant or even said what you are implying i did. Quiet the contrary: read the wikipage again, its about when it is justified to act like the side you want to ban.
People are intolerant. Let’s not tolerate them. Now we are intolerant:
Does it only happen with these two drives? i would try with some other HDD/SSDs or two usb sticks. that way you can test if its some weird hardware incompatibility that sometimes happen between specific devices or if the board wont support more then one connected usb drive in general.
if it’s to cheap, the market wont be able to profit enough, so I’m pretty sure they will find a way to squeeze us dry anyway
Me too. Stable packages, unlike everyone thinks, doesn’t mean it is bug free, it means that the software versions don’t change. And that exactly lets me enable unattended-upgrades and forget about the server for years, without risking to fubar the system because of some config changes or new options
we had a paper with a bunch of Ys and Ns, so we could go through the autoexec.bat and config.sys step by step and decide which library to load into highmem or lowmem
most of the time it works every time. :)
I’m using debian unstable as a desktop OS on all of my 3 regularly used systems: 2 notebooks and 1 desktop. And debian 11 on citrix virtual desktop at work. debian stable on around 200 servers.
I rarely have bigger issues in my day to day usage of unstable which includes surfing, gaming and coding. at the moment my bluetooth headset microphone doesn’t work, which i guess is due to some changes to pipewire but only on my desktop. both my work and private notebook seem to not have issues.
this is one of the worst problems i had in the last 8 years. other then that, if you use apt-listbugs to exclude any updates with serious bugs by pinning them until a bugfree version gets released, you wont have any more issues then you get with arch for example.
Thanks but no thanks. I’ll stay with my debian unstable: less snap bullshit, no advertising in motd and newer packages (systemd 254 for example)
who said debian uses old packages again?
As will have debian unstable. That’s the way it goes, for a few months every few years it slows down until the new stable gets released. Testing is just 10 days after unstable to avoid the biggest bugs.
Never had big problems with debian unstable in 15 years though, as long as you use apt-listbugs
Your own nextcloud instance. Then move everything that is saved at Google over to your own server.
Calenders, Filesync, Contacts sync with android works really nice.
Knowing my data is stored only on my own devices and google doesn’t know more about me than I do is a nice feeling.
Linus would like to have a word with you