• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • Yep, to add on as well as summarized this… Linux has historically had a design methodology of “everything is a file”. If your not familear with the implications of this, it means your command line tools just kind of work with most things, and everything is easy to find.

    For instance, there’s no “registry / regedit” on Linux… There’s just a folder with a config file that the application stores settings in. There’s no control panel application to modify your network settings… Just a text file on your OS. Your system logs and startup tasks were also (you guessed it) sinole filea on the system. Sure there might be GUI apps to make these things easier for users, but under the hood it reads and writes a file.

    This idea goes further than you might assume. Your hard drive is a file on the file system (a special file called a block device). You can do something like “mount /dev/sda1 /home/myuser/some_folder” to “attach” the drive to a folder on the system, but that special block device (dev/sda1 in this case) can be read and written to byte by byte if you want with low level tools like dd.

    Even an audio card output can show as a file in dev (this is less the case now with pipewire and pulse), but you used to be able to just echo a raw audio file (like a wav file) and redirect the output to your audio device “file” and it would play out your speaker.

    Systemd flipped this all around, and now instead of just changing files, you have to use applications to specify changes to your system. Want to stop something from starting? Well, it used to be that you just move it out of the init directory, but now you have to know to “systemctl disable something.service”, or to view logs " journalctl -idk something.service" I dont even remember the flags for specifying a service, so I have to look it up, where it used to just be looking at a file (and maybe use grep to search for something specific)



  • I run freeipa internally, which handles all internal https certs (as well as nice things like handling non sudo auth so I can just ssh to machines from an already authed machine without a PW prompt, and doing ldaps for internal things that support it)

    For external web, I have a single box running nginx as a reverse proxy thats web exposed. That nginx box has letsencrypt certs for the public web stuff. The nginx rp has the internal CA on it and will validate the internal https certs (no mullet SSL here!)

    I also do different domains for internal vs external, but thats not a requirement for a setup like this


  • A prion is just a misfolded protine that has some adverse behavior that your body can’t detect (there’s a mechanism that if your body identifies a malformed protine, it will terminate the cell making it). Anyway, prions live in this small region in a Venn diagram whereits can’t be detected, but can still replicate and cause harm.

    We mostly think of prion diseases (like mad cow) affecting the brain, but I dont think prions are isolated to the brain… Prion deseases happen to involve the brain a lot because a misbehaving protine in your brain will have a lot more apparent effects





  • Polymaker polyterra. I especially love their army blue and black filament. They print nice and matte, and the colors print almost identical between their different colors. I always thought polymaker was a more expensive brand, but polyterra hits that 20usd/kg for pla price point that hatchbox and other budget filaments used to dominate



  • Yep, as others have said, valetudo. I have a z10 pro and love it. I highly recommend one with an auto empty dust bin… Having to clean it after every run defeats the purpose of an automated vac. if you forget to empty it, it will be very ineffective the next run.

    Also, I would say make sure you can assign a room for it to clean. If you have cats, automating it to clean the litter box room after they go is soooo nice