Without any judgement: why are your servers running X11? Just because you dislike SSH’ing to them?
Without any judgement: why are your servers running X11? Just because you dislike SSH’ing to them?
And yes, word is the word.
It seems like you are one of the twelve Americans who is unaware that the bird is the word.
The hell happened to the feet in the second panel?
If all of those servers are yours (which they likely are, since you get ssh access), you can use one key for all. Using different keys would make one compromised key less problematic. But if someone was able to copy one file of your system, they can copy multiple files.
That resolves keeping track of things as well 😄
absolute galaxy brain moment
The stalebot is most times useless. The only scenario where I can see use of it is a maintainer waiting for the reporter to add information. But closing issues because no maintainer checked on them? That’s garbage and discourages bug reports.
You forgot the package hollywood.
I think they come with ublock itself and are called “annoyance filters” or something like that.
If you have the iso image, you can write it with the command dd to your stick / sdcard
I like how it is cheaper to buy it upfront. Like they can load an extra bag or two full of internet if they know you need it.
Do we have a Beetlejuicing community already?
I would recommend key based authentication for SSH connections. For the normal connection, the key pair is enough, if you want admin (root) access, you would use the command sudo which in turn requires a password. For creating a default admin account: Linux does this for you, it’s called root. You should create a personal user to work with in daily business and add it to the sudoers group (permits using the sudo command)
Gardening with Maurice was nice. Actually all the shows on WCTR.
That’s the garbage in part of the GIGO process.
I’m a sucker for jetbrains Mono when I need a monospaced font. It just looks nice to me.
If the package comes from the repo, you can uninstall it by the same name you used to install it. If it came from a .deb file (in case of debian), you can find out how the package calls itself and use that name to uninstall. Usually the package name is quite identical to the file name. And dpkg -L
shows you which files came from the package and where they were installed.
I’m fine with config files, as long as they are where you expect them (~/.config/tool or ~/.tool). What I dislike is yet another funny config syntax because the dev couldn’t settle on an established standard. Command line syntax is ok, if you give me sensible completions.
Not a recommendation per se, but you can use any backup software as long as you can edit your live iso. For example puting the restic binary into /opt
sad Kenya noises
Hmm, I see. The perfectionist in me would want to shed that processor load though ^^