SpaceCadet

SpaceCadet, 1 year ago

Mental note: have to migrate my gitea instance over to forgejo.

SpaceCadet, 1 year ago

For me gravity sync was too heavy and cumbersome. It always failed at copying over the gravity sqlite3 db file consistently because of my slow rpi2 and sd card, a known issue apparently.

I wrote my own script to keep the most important things for me in sync: the DHCP leases, DHCP reservations and local DNS records and CNAMES. It’s basically just rsync-ing a couple of files. As for the blocklists: I just manually keep them the same on both piholes, but that’s not a big deal because it’s mostly static information. My major concern was the pihole bringing DHCP and DNS resolution down on my network if it should fail.

Now with keepalived and my sync script that I run hourly, I can just reboot or temporarily shutdown pihole1 and then pihole2 automatically takes over DNS duties until pihole1 is back. DHCP failover still has to be done manually, but it’s just a matter of ticking the box to enable the server on pihole2, and all the leases and reservations will be carried over.

SpaceCadet, 1 year ago

That’s what I do. I do have a small VM that is linked to it in a keepalived cluster with a synchronized configuration that can takeover in case the rpi croaks or in case of a reboot, so that my network doesn’t completely die when the rpi is temporarily offline. A lot of services depend on proper DNS resolution being available.

SpaceCadet, 1 year ago

DNS-over-HTTPS

You can also do that with running cloudflared or unbound on your pihole.

SpaceCadet, 1 year ago

The official image jellyfin/jellyfin tracks unstable

Huh? That doesn’t appear to be the case. jellyfin/jellyfin:latest, which is what they tell you to use in the installation instructions. gives me 10.8.13 which appears to be the latest stable release.

There are newer and unstable versions available in dockerhub as well, but latest doesn’t give you those. After all latest is just a tag with no special meaning of itself, it doesn’t necessarly give you the most recent build.

SpaceCadet, 1 year ago

I believe there’s one in France too.

SpaceCadet, 1 year ago (edited 1 year ago)

I know wlroots exists. It’s a library that helps you implement a compositor (i.e. does some of the heavy lifting), but at the end of the day the window manager developer is still implementing a compositor and is responsible for maintaining his compositor.

The mere fact that wlroots, and other efforts like louvre, are necessary at all actually prove my point that it was an idiotic design to push everything off into “compositors”.

SpaceCadet, 1 year ago

Besides, if anyone tries to boot any other OS which is not mine, the keys are erased.

There are forensic tools that can capture the contents of RAM, and so access your decrypted LUKS encryption key.

I guess it depends on who you are protecting against, but if for example law enforcement wants evidence against you for what they think is a serious enough crime, they just may go through the trouble to do it.

SpaceCadet, 1 year ago (edited 1 year ago)

GNU grep, the most widespread implementation, does not include egrep, fgrep and rgrep for years. Distributions (not all, but many) provide shell scripts that simply run grep with corresponding option for backward compatibility. You can learn this from official documentation.

It seems you need to read the official documentation yourself. While it’s new information to me that egrep is no longer a symlink, as it used to be a couple of years ago, but a shell script wrapper to grep -E instead, the egrep command is to this day still provided by upstream GNU grep and is installed by default if you run ./configure; make; make install from source. So it is not a backward compatibility hack provided by the distribution.

You can check for yourself. Download the source from ftp.gnu.org/gnu/grep/grep-3.11.tar.gz, unpack and look for src/egrep.sh or line 1756 of src/Makefile. Apparently the change from symlink to shell script was done in 2014, and the deprecation warning was added only last year.

In any case, my larger point is that the depreciation of egrep was a pointless and arbitrary decision that does not benefit users, especially not veterans like myself who have become accustomed to its presence. I don’t mind change, but let’s be honest, most people are not in the habit of checking the minutiae of every little command line utility they use, so a change like this violates the principle of least surprise. It’s one thing if things are changed with a good reason and the users do not only suffer the inconvenience of the change but get to reap the benefits of it as well, but so far I haven’t found any justification for it yet, nor can I think of any.

So if there is a portability problem with using egrep now, it’s a self-inflicted portability problem that they caused by deprecating egrep in the first place.

Also, my scripts are not full of bashisms, gnuisms, linuxisms and other -isms, I try to keep them portable unless it is really necessary to use some unportable command or syntax.

Good for you. Do you want a cookie or something?

SpaceCadet, 1 year ago (edited 1 year ago)

You are strawmanning, and your links are not countering any point I made. I never disputed the depreciation as fact, and I never recommended that beginners should use egrep over grep -E

I disputed your claims that the egrep command has just been a distro hack all these years, when in fact GNU to this day still distributes egrep through its source tarballs and only very recently started to warn about it through the wrapper script. And again, the only “portability problem” here is the fact that they deprecated it in the first place, i.e. a self-inflicted one.

Then as a Linux and Unix veteran I gave my subjective opinion by lamenting and criticizing the fact that this depreciation happened, and how changes like this always feel like unnecessary pedantry to me. Yes it’s an expression of frustration, but I am allowed to feel frustrated about it. I don’t need people like you invalidating how I feel about breaking changes in software that I use daily.

SpaceCadet, 1 year ago (edited 1 year ago)

Well he wrote it like he wanted to be applauded for it or something.

I also find the irony of your comment extremely funny … although that’s probably lost on you.

Later, dude.

SpaceCadet, 1 year ago

That’s just retconning/backronyming it.

/usr does historically stand for user. It’s where the user home directories were on old Unix versions.

SpaceCadet, 1 year ago (edited 1 year ago)

Binaries in the former are installed by the OS/package manager, binaries in the latter are installed manually by the user, for example by compiling from source and running make install

SpaceCadet, 1 year ago (edited 1 year ago)

100% possible with a Windows 10 guest in kvm/libvirt.

You can connect the disk to your Linux system, and then pass through the disk’s entire block device to the VM. Windows will see the device as an actual disk, and you can perform your repairs that way. I have something like this in my domain definition to pass through my game drive to my Windows 10 VM: pastebin.com/GzuvMTWP

I can even use the manufacturer’s SSD maintenance tool from my VM.

Edit: lemmy doesn’t seem to like XML in code blocks, so used pastebin instead.

SpaceCadet, 1 year ago (edited 1 year ago)

Reminds me of the time I brought down a whole AIX server with the killall command back in the 1990s.

On AIX killall really means kill every single process.

SpaceCadet, 1 year ago

And affordable education

Depends on where you where born I guess? Living in Belgium, my boomer parents never got a higher education because it was not affordable for working class families with 6 or more children. My dad had to go to work in a factory at 14, which was very common at the time. Props to him though, he got a degree through evening classes when he was already married with two children and working full time.

Higher education only became common and affordable with my generation.

On the other hand, while I make more money than my parents ever did, they were able to buy a 4 bedroom house in the 1980s on a working class income, whereas I could only afford a 2 bedroom appartment in the mid 2000s, the tail-end of affordability for housing.

SpaceCadet, 1 year ago

These days, a part time income may not even be enough to cover books, let alone room and board… forget about tuition

This is again a more American perspective I think, which doesn’t make it invalid of course. The situation over there where students typically get loans and suffer crippling debt for years after they’ve graduated is frankly outrageous. Over here though, higher education is government regulated and highly subsidized, and while it’s not free and can still be pretty expensive, it’s possible to fit it within the budget of most families without loans, and people from families with a really low income are eligible for a grant.

So I’m going to stand by my point that in Belgium at least, education has become more accessible compared to how it was for the boomer generation. It’s visible in the statistics too: the number of people with a higher education level is still increasing every year, and younger people are much more likely to be highly educated than older people.

Sources:

• statbel.fgov.be/en/…/datalab-census-education
• statbel.fgov.be/en/themes/…/level-education
• vlaanderen.be/…/scholingsgraad-bij-25-tot-64-jari…

SpaceCadet, 1 year ago

Yeah, but none of the system tools and applications follow Unix-like paradigms, so it’s really only Unix-like in name. Sure you can launch a bash or zsh shell, but there aren’t a lot of useful things you can do with that without installing a bunch of third party tools like brew, so the experience isn’t all that different from having to install Cygwin or WSL in Windows.

SpaceCadet, 1 year ago

Eh, WTF? It has normal Unix-like userland tools.

You don’t understand what I mean.

I mean that you can’t really do much with those userland tools to effectively manage and configure your system. All configuration is abstracted away in a forest of xml files (i.e. /Library/Preferences) that’s as opaque and undocumented as the Windows registry and which you’re not supposed to touch other than with the approved GUI tools.

MacOS applications never follow Unix principles either regarding file placement.

So yeah while MacOS technically still is “Unix”, it really is a giant monolithic blob of shite built on top of the skeleton of what once was a decent Unix.

SpaceCadet, 1 year ago

Woosh I guess

SpaceCadet, 1 year ago

The only downside really is RAM slot clearance when you need a beefier air cooler.

SpaceCadet, 2 years ago

you missed their flirting because you didn’t liked them enough

More likely that you missed it because you didn’t like yourself enough to believe that they were sending out clear hints.

SpaceCadet, 2 years ago

This reminds me of the time I went home with a lesbian couple after a party, and not realizing they were interested in sex with me, even after dropping hints like repeatedly telling me things like: “You know, we’ve both been with men before”, then while awkwardly watching a movie on their couch they started to undress eachother and make out, and one girl pulling me in to touch her body as the other girl moved to perform cunnilingus on her.

And all I could think was: oh wow I should probably give them some privacy now, I guess it’s time to go home.

SpaceCadet, 2 years ago

LLVM was held back for a good reason, it was breaking things left and right. Even so, if you really needed it there were always AUR packages for it, or lcarlier’s mesa-git repo if you prefer prebuilt packages, so it’s not as if you were just SOL. I got my 7900XT in december, and instructions on how to get it running were already all over the forums and subreddit at the time and it was working on the same day that I got it.

I don’t know when you got your 7900XT, but it was broken on Ubuntu too for a good while, I’m not even sure that it currently works on 22.04 without using external PPAs. In the mean time, it now works with Arch out of the box.

As for the grub thing, I’m not sure how that could have been handled differently. Upstream introduced a change that created a compatibility issue, so Arch could either not update to a newer version of grub ever, or update anyway and tell its users how to handle the compatibility issue. The latter is what they did.