• 0 Posts
  • 18 Comments
Joined 11 months ago
cake
Cake day: December 25th, 2023

help-circle


  • I don’t hate that much but I don’t watch him because of the shady selling business hr often does and apparent sponsored content which is not always disclosed (been a while but his channel misrepresented graphics cards benchmarks for example).

    It’s like the British yellow press for me: his face alone is enough to discredit the quality of the source. Could it be good? Sure! Will I ever find out? Not anymore.



  • User perspective:

    If you want something big I’d pitch nixos. As in the core distribution. It’s a documentation nightmare and as a user I had to go over options search and then trying to figure out what they mean more often than I found a comprehensive documentation.

    That would be half writing and half coordinating writers though I suspect.

    Another great project with mixed quality documentation is openhab. It fits the bill of more backend heavy side and the devs are very open in my experience. I see it actually as superior in its core concepts to the way more popular home assistant in every aspect except documentation!

    That said: thanks for putting the effort in! ♥






  • Edit: I missed some complexity as suspected! I’m not sure how this process would handle hard and symlinks. Would add an experiment for that before going with the nix and root folders (it shouldn’t harm log at all).

    Original text: Perhaps I’m missing some complexity in your setup but from my understanding it’s really straight forward:

    The main caveat is that you need twice the space of your largest future sub volume. A garbage collect - d and any manual cleanup can help you there. I’d gets that approach with /var/log and when that works move over to the more critical systems.

    • You create the subvolumes within the partition you want to keep.
    • Mount them at a temp location and copy the files over.
    • alter your hardware.nix or whereever you’ve set your mount points to use the subvolume.
    • rebuild switch and reboot.

    If everything is working as expected, write a run book for every step and repeat with /home (i.e. have every step written up). Home is the second least critical folder for this.

    Once you have your runbook repeat the process and when you run out of space resize as needed. (e.g. https://btrfs.readthedocs.io/en/latest/btrfs-filesystem.html#man-filesystem-resize)

    That said: as you aim for the fully ephemeral root I personally would actually go the reibstwllwtion/reinstall route and write up everything I needed to do by hand. But that needs even more spare space (I’d prefer even a second disk for stuff like that to have a fallback).

    Good luck!



  • Hey friend,

    I want to be very straight forward here in the hope that it’ll give you an additional perspective:

    The scenario you’re describing I’d describe as “make the life of my surrounding as easy as possible when I bite the bullet”.

    . That does not include making my system or even the home server easy to use or maintain. My interests don’t matter in that case only what those people need and would want. In my case: my non tech savvy wife would want to get rid of a big desktop PC but would most likely struggle because I enjoyed using it.

    This means:

    • For all data there are encrypted files with passwords and/or instructions.
    • For all things no one would want there is a “this is how you get rid of it most easily” guide, including "call an electrician for the following recabling to pull out the shellies.
    • for the one thing not easily ripped out there is a maintenance guide and a replacement guide (a bus system monster" temporarily" installed due to good reasons).

    To be clear: no non tech savvy person I know would want to use my (and I guess your) custom systems. Not one. They’d rather have a “this is the ebay description” or a “this is how you install windows”.

    Your legacy will find other ways to life on - it won’t be your tools and toys though.


  • You have several long and comprehensive answers so please allow me to add an emotional one:

    Fucking compile error in hour six of what you estimated to be a four hour compile job because of a mistake you made that you found within 5 seconds after the error!!

    Fucking why doesn’t this compilation start I can’t find my mistake for hours?!

    Where does this module come from?! What do you mean “root kit”? Learning was fun!

    It all was fun! :)


  • Is there anything to support this? I couldn’t find anything that really has this intend documented and Intel weren’t the only on pushing for usb as the most simple protocol possible ( I recall a lot of excitement about the “u” part… How naive at least I was back then!).

    I’m not knowledgeable enough to really argue against it, looking simply from an Okham point of view as “they wanted everything to connect” - the printer in the same way as that PDA… Plus Intels de facto (IT) world domination at the time it just seems unlikely.

    Edit: some sentences didn’t make even less sense, fixed.



  • (not OP but same boat) Doesn’t really matter to me because google knows my servers external IP which is a non-issue: I don’t expect google to try to attack me individually but crawl data about me. There is no automatic link between my server and my personal browsing habits.

    In terms of attack vector vs ease of use , self hosting searxng is a nobrainer for me - but I do have an external server available for things like that anyway so no additional overhead needed.


  • Two more things to add: you get downvoted not for the content but for the tone. People tend to not respond well to abuse, even if verbal - and at least I read a “make this shit work for me” in between your lines.

    And more important: what you are asking is not easy. Wouldn’t be on windows, wouldn’t be on macos (disclaimer: I’ve never set up the arr stack on either but docker runtimes) . You are diving into server software no matter if you’re the only user or not. Either you accept this and the learning curve ahead of you or you give up on it.