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.
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.
in the past it usually took a few days for someone to get it working again, but this time it might be some kind of cheat detection.
fortunately dota works as a substitude drug for me
I have played lol for 10 years. Last week, due to some updates lol doesn’t run on Linux at the moment, I switched to dota. I know exactly what you are talking about.
This works but I’d just create a function and use that instead of creating an alias that creates a function and then calls itself.
if your containers are created with a docker compose file you can use docker-compose to target them all
I’m using a HP spectre x360 since 2020-12 and I love it so much. I don’t use the tablet functionality often. The touch works pretty well as far as I can say. The notebook, even if it’s 13" ultra portable, is a little heavy for constant tablet usage. Everything else rocks aside of the thumbprint thingy. I use howdy instead.
Im most interested in encrypted homedirs for servers. Since all my collegues are to lazy to use encrypted ssh keys, i hoped that systemd-homed makes it possible to secure them from the root user.
Is systemd-homed already useable for such usecase? If gnome will do the same for desktops, that would be a big plus, thinking about firefox profiles and such. Hopefully also using pam or kerberos for decryption.
I’ll look into fuse though, thanks for the hint
My comment wasn’t meant as a jab against systemd or gnome, I was just curious if there are different solutions for an encrypted homedir.
I really like the direction linux, systemd and gnome are going! Big thank you to all the developers! <3
Congrats GNOME!
Does anyone know if homedir encryption will utilize systemd-homed?
things like “vim file.txt”, which is obviously not usually how files are edited
You what mate? Don’t assume my workflow. “vi file.txt” is obviously superior to clicking inside some texteditor or file browser
catching a car fire in the parking lot […] notifying […] employees so they could move their cars, preventing the loss of hundreds of cars.
sounds like a really bad idea. there is a reason everyone needs to leave the office when a fire alarm happens.
Funnily enough, I like nix. The concept is way ahead of silverblue and the likes. With nix nothing is hidden behind a compatibility layer. I feel like if we really need immutability, nix is the way to go.
its an easy: sudo apt install task-kde-desktop; sudo apt purge task-gnome-desktop; sudo apt autopurge
In testing or unstable this can be a problem though.
I feel like, many people just don’t understand exactly how a distro and package managers work. immutable os feels like it allows priotizing only on on a small core part of the distribution which is immutable and slapping everything else on via flatpak or snap.
i don’t like it and i sometimes wonder if we are not going backwards with that approach.
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?
Linus would like to have a word with you