presumably you instinctively know that you’re in a wholly safe place and there is no excuse not to do it anymore. We’re really not made to suppress elimination for a long time like that, in nature the only reason not to get the business done is because you gotta walk away from camp or because you’re chased by a lion, and neither of those tend to take a long time…
we should really be glad we’re at all able to hold it in as long as we do
it’s been multiple eternities since I’ve played 3 or NV. 4 I’ve played more recently, but that was … basically when the last dlc dropped? So… memory of those games not really the sharpest.
London is mechanically almost identical to 4 (duh? because mod, duh.). The parts of the main-story I’ve done has been great. I recall preferring side and dlc missions over main-plot in 4, but I was pretty into the main stuff (dlc or not) in NV.
some thoughts about it in no specific order:
I’m around 20 hours in, and it feels like I’ve only started. Plenty of map markers opened, but VERY little of actual land area explored.
there seems to be less emphasis on settlements, haven’t had a permanent residence (storage, bed) so far, been storing my junk in some friendly town crafting stations which don’t seem to de-spawn stored stuff (as tipped in the mod’s discord).
but settlements are apparently still a thing (not sure how I feel about it, they were the worst part in 4, imo) - haven’t aquired a settlement yet.
it’s bit more difficult than 4, ammo is a bit scarce and some enemies are ridiculously tanky, even at normal difficulty.
the early game can be a bit brutal, but eases off as you get levels (ref: at ~10-15h or so in, I was finally able to take enemies down with confidence)
The city is HUGE and dense (requires some more grunt from the computer than base-game), there’s things to do and see in every corner, a lot more buildings to enter.
“level design” is mostly great, but there have been places where the route forward/mission critical progression item was hidden by all the clutter and generally darker lighting.
the level design also contains surprisingly deep puddles here and there on the streets, and those build up radiation QUICKLY. Bodies of water in this game are dangerous.
Food and other non-stimpacks seem to be in quite a big role, at least in early game. IIRC fallout 3/nv/4 basically showered the player with stimpacks.
Voice acting is pretty good, if a bit hammy at times.
I recall enjoying all fallout games, some more than others. I mostly mod for convinience (eg. busywork, carryweight) so I’m not really playing the game(s) as intended. And this one is great… if a bit buggy here and there - but not any more so than actual Fallout games. :D
I totally recommend London, but it comes with an asterisk: the mod requires tweaking, and depending on your computer-skills it can be either “man, this is obvious” to “wtf am I doing”. Config-file editing and extra mods are required to get it actually working. Def recommending Mod Organizer 2 as well. Also, if your base fallout 4 (and dlc) are from steam, you need to downgrade from the “Next gen update”. I’m fairly sure there’s good step-by-step how-to’s to get it set up at this point.
I use syncthing to copy important files between pc, phone and proxmox server. Syncthing can be set up with version control so it keeps old versions of files.
Only the proxmox server is properly backed up though. to a proxmox backup server running in a VM on said proxmox server. the encryptred backup files are copied to backblaze using rclone
Not sure if this is what you are looking for, but it works for me.
TLDR syncthing for copies between local machines, and proxmox backup server and backblaze for proper backups
Arch is great if you want to learn the ins and outs of Linux. If you just want your computer to work, it’s probably not the best option. What’s great about Linux is that there’s an option for everybody.
That’s what’s always stopped me from running a rolling release distro like Arch: the unpredictability of life. I go on vacation for 2 weeks, don’t use my computer in that time and when I get back, I’m going to want my computer to work after an update, simple as that.
Rolling release packages tend to break as they get further and further out of sync with what’s the latest, if you haven’t updated packages in a certain period of time, I don’t know what that time period is, since I’ve never run rolling release, but my point stands. I like that I can leave a laptop sit for a while, pick it up and not break the next time I run updates.
You miss enough updates on a specific package, it may break without a proper tested upgrade path from version 1.5 from 6 months ago and version 1.76 from yesterday.
Arch breaking easily is such an over-exaggeration. I’ve run Arch so many years and the amount of tinkering I’ve had to do because of botched updaates is so minimal. Often times, they announce it on their main website even, with instructions on how to fix it. You also should have configured filesystem snapshots to easily revert after a bad update. Or have a USB installation medium ready to boot from and then repair/downgrade the affected bad package. That’s usually all there is to do, and it happens rarely.
If you have multiple problems after Arch upgrades, then I’d guess that’s a misconfiguration on your end, leading to unstable system behavior after updates. Arch doesn’t do any kind of hand-holding, you’re allowed to completely misconfigure and break your system, but then it’s also your own fault.
If you didn’t update for a while, you should probably update the archlinux-keyring package first, then do the rest of the updates. Otherwise, the other packages won’t be able to be updated when package signing keys changed in the meantime
So yeah, I wouldn’t recommend Arch for beginners, unless you really want to learn Linux the “hard way” and have a little bit of spare time and don’t mind reading on the Wiki, but still, Arch instability is kind of over-exaggeration. Arch is very stable for a rolling release distro, but you do have to do a little bit of maintenance every now and then. That’s the nature of rolling-release. I still wouldn’t call that unstable, though.
Cron + rsync is always a bulletproof solution. Simple bash script that runs every X minutes to sync to a network target. Wouldn’t need to be only when the machine starts as you mentioned.
Since you’re interested in this kind of DIY, approach, I’d seriously consider thinking the whole process through and writing a simple script for this that runs from your desktop. That will make it trivial to do an automatic backup whenever you’re active on the network.
Instead of cron, look into systemd timers and you can fire off your script after, say, one minute of being on your desktop, using a monotonic timer like OnUnitActiveSec=60.
Thinking through the script in pseudo code, it could look something like:
This would pull the back from your server to your desktop and, if the backup failed, use a service such as ntfy.sh to notify you of the problem.
I think that would pretty much take care of all of your requirements and if you ever decided to switch systems (like using zfs send/recv instead of rsync), it would be a matter of just altering that one script.
But I’m a bit sad that the French-originating Bonmot is already taken in German (meaning a witty one-liner). It would have been a nice allusion to Bonbon (candy), like words that taste nice.
kbin.life
Hot