I wouldn’t compare Swartz with the AI scrapers. Aaron pulled mostly public domain documents from JSTOR and caused minor issues with the servers which is “a bit” different than pulling everything from the internet to a database over a practically global DDOS-attack. But when companies do it it’s apparently somehow different and Swartz was pretty much publicly lynched and eventually bullied to suicide.
Our previous president son is on the files. There was a news article where he explained that Epstein had contacted him for fundraising or some other legal thing and they met somewhere once for a short while but that’s all. There was also other finns, like one young woman who applied for an assistant job on some of his businesses but didn’t get hired.
So, while there’s a crapload of people who should be convicted and thrown in a jail there’s also a ton of people who don’t have anything to do with pedo-ring or anything else. Good to keep in mind that having someones name on the files alone doesn’t mean too much.
And just to avoid any confusion, if you are mentioned in the files more than Jesus is mentioned on the bible it’s not an accident or one time thing. Allegedly that applies at least to Trump and there should be a small and dark cell somewhere ready.
It’s a government thing. I’m not sure when they’ve started to consider alternatives, but that renewal process (as old systems are on EOL) has most likely been on the table for years.
That’s my use case. But my frigate-box is strictly behind firewall and I access it over wireguard when I’m away.
What errors excactly? Copy and paste what you’re getting from your terminal. Also post output of ‘df -h’.
What kind of errors you’re getting? First what you can try is to run ‘dpkg --configure -a’. If that doesnt help we need more information on what’s going on.
Get a REALLY good on-site support deal for your hardware. You also may need to adjust TTL values on your network stack.
It wasn’t for nothing, you got some learning out of the experience and a story to tell. Good luck with the new system, maybe hold upgrading that to testing for a while, there’s plenty to break and fix even without extra quirks from non-stable distribution :)
Have fun and feel free to ask for help again, I and others will be around to share what we’ve learned on our journeys.
You’re not worrying for nothing. Losing wall power will shut down the drives and as usb-cradle is generally slower than “proper” drive bus it’s more likely that some write operation is going on when power is lost and that’ll potentially cause data corruption. Obviously not every power outage will cause issues, but I’d say it’s a higher risk with USB-drives than with drives on a SATA/m.2 bus.
But no matter what your setup is, raid is not a backup. All kinds of things can happen which cause loss of data and you should plan accordingly. If all you have is two drives on usb-cradles I might choose to use one of them as a offline backup disk and one for ‘live’ data so that it’s more likely that at least one of the drives is functional even after power issues or whatever, but that approach has it’s own problems too.
There’s a walkman model which is pretty much just that which runs some flavour of android but I don’t know who they think their customer base is as the pricing is absolutely stupid. Top of the line model has gold plating and a nice 4k price tag. Also it apparently has ‘oxygen free copper’ and other audiophile bullshit, but no FM tuner.
And then there’s a ton of similar products from China but no idea which models (if any) are actually useful.
I had a two (or maybe a bit less) bitcoins on my wallet back in the day. I sold them for ~20€.
Well, the touchscreen part and maybe a bit more, had the same reaction on many directors at Nokia at the time. I don’t know if they feel like an idiot, but at least you’re not alone.
Cameras don’t stop anyone, but I still have few recording my yard. It’s more of a hobby and I’m planning to integrate person detection on those to home automation but for me it’s also a small piece of peace on my mind. Should someone steal my car trailer (or a car) I’d have some footage for the police and insurance. Also a while ago we had a decent storm around and we weren’t at home so it was nice that I could check for possible damages remotely.
But absolute majority of time I don’t even think about them. I don’t have any notifications enabled, I’m not interested about neighbors cat running across our yard or getting interruptions every time someone on the family comes or goes. And while Frigate has some AI things built in, the whole thing runs locally. There’s no way I’d install nest or some other camera which sends/stores data to anywhere which isn’t 100% in my control.
I haven’t tested lvm on arm-based systems, but if it doesn’t automatically locate them you could try pvscan/vgscan/lvscan.
Rootfs location is passed via kernel parameter, for example my grub.cfg has “set root=‘hd4,msdos1’”. That’s used by kernel and initramfs to locate the root filesystem and once ‘actual’ init process starts it already has access to rootfs and thus access to fstab. Initramfs update doesn’t affect on this case, however verifying kernel boot parameters might be a good idea.
Just in case you end up with reinstallation, I’d suggest using stable release for installation. Then, if you want, you can upgrade that to testing (and have all the fun that comes with it) pretty easily. But if you want something more like rolling release, Debian testing isn’t really it as it updates in cycles just like the stable releases, it just has a bit newer (and potentially broken) versions until the current testing is frozen and eventually released as new stable and the cycle starts again. Sid (unstable) version is more like a rolling release, but that comes even more fun quirks than testing.
I’ve used all (stable/testing/unstable) as a daily driver at some point but today I don’t care about rolling releases nor bleeding edge versions of packages, I don’t have time nor interest anymore to tinker with my computers just for the sake of it. Things just need to work and stay out of my way and thus I’m running either Debian stable or Mint Debian edition. My gaming rig has Bazzite on it and it’s been fine so far but it’s pretty fresh installation so I can’t really tell how it works in the long run.
Do you happen to have any USB (or other) drives attached? Optical drive maybe? In the first text block kernel suggests it found ‘sdc’ device which, assuming you only have ssd and hdd plugged in and you haven’t used other drives in the system, should not exist. It’s likely your fstab is broken somehow, maybe a bug in daily image, but hard to tell for sure. Other possibility is that you still have remnants of Mint on EFI/whatever and it’s causing issues, but assuming you wiped the drives during installation that’s unlikely.
Busybox is pretty limited, so it might be better to start the system with a live-image on a USB and verify your /etc/fstab -file. It should look something like this (yours will have more lines, this is from a single-drive, single-partition host in my garage):
# / was on /dev/sda1 during installation
UUID=e93ec6c1-8326-470a-956c-468565c35af9 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=19f7f728-962f-413c-a637-2929450fbb09 none swap sw 0 0
If your fstab has things like /dev/sda1 instead of UUID it’s fine, but those entries are likely pointing to wrong devices. My current drive is /dev/sde instead of comments on fstab mentioning /dev/sda. With the live-image running you can get all the drives from the system running ‘lsblk’ and from there (or running ‘fdisk -l /dev/sdX’ as root, replace sdX with actual device) you can find out which partition should be mounted to what. Then run ‘blkid /dev/sdXN’ (again, replace sdXN with sda1 or whatever you have) and you’ll get UUID of that partition. Then edit fstab accordingly and reboot.
If you’re talking about just moving the physical volumes (as in the actual hard drives) as is to another computer they’re automatically scanned and ready to go in majority of modern distributions. No need to export/import anything. This is obviously assuming your boot drive isn’t a part of volume group and you have healthy drives at your hands. You can test this with any live-distribution, just boot from USB into a new operating system and verify your physical volumes/volume groups from that.
If you want to move the volume group to a new set of disks simplest way would be to add physical drive(s) to volume group and then removing the old drive(s) from it after data has been copied. Search for pvmove and vgreduce. This obviously requires a working system, if your data drive has already failed it’s a whole another circus.
Even if your router acts as an DNS proxy it shouldn’t overload any pihole installation unless you have a crapload of devices doing millions of queries per hour. My pihole manages all my devices (20-30 individual things) without any problems and even if I hit some rate limit it’s going to be a change to default configuration, not a immovable object on your way. Based on quick glance over that reddit thread a new router might be a good option, but that’s another easy-ish task to accomplish. I use mikrotik device and I’m pretty happy with it but there’s a ton of good options.
For hiring someone to coach you I can see quite a few of potential issues. People who claim to know what they’re talking about but don’t really have the knowledge, straight up scammers obviously, mismatch in personal chemistry which will make learning unnecessarily difficult or even impossible, some people just aren’t good at teaching even if they do know their stuff and so on. By all means, use your money however you like, but I personally strongly advice against it unless you can get some courses on (preferably local) reputable vendor. You can look for online courses too, cisco has a ton of courses on networking, redhat has plenty of linux courses and other big players have their own training and even certificates if you want to go that far.
It’s not monitored for security patches as it gets all the latest stuff anyways pretty quickly, security patches (and new vulnerabilities) included. It’s just not meant to be hardened nor rock solid as it’s excactly what it claims to be: development branch of the whole project. That doesn’t mean it’s insecure by default, it just works differently from stable releases where security patches are provided for years after official release.