• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: August 12th, 2023

help-circle
  • from a diagramming pov, remember to document the link speed at each end as well as the ethernet cable type. if your cable modem supports 10GB I would really really look at 10GB network devices pretty closely, budget allowing. I would steer cleared of managed, it’s just a PIA for your setup.

    You might want to experiment with modem <-> switch <-> wifi vs (modem <-> wifi <-> switch). remember wifi is just ethernet. so the order may or may not matter as much (vendor gets a vote). there does not appear to be a reason to march ethernet cable traffic thru the wifi router, but maybe there is???

    def agree an 8 port switch might be better for you, use a 5 to split a single cable at a single location (say, tv + game console + speaker combo)

    Remember if you need a WiFi mesh (multi access-point) to connect your devices, if possible, link the mesh backplane together via ethernet cable so that you don’t chew half the speed with wi-fi backplane chatter.






  • Whoops

    Excel is def the mkt leader for a reason

    I loathe Ms Access but have to admit there is no peer that even comes close.

    Vs code is relatively reliable, cross platform and gets the job done. When there are a lot of people “one way that works for all” is a quality as well.

    That said, I wish open offices were better. Even Apple numbers isn’t a realistic excel alt yet (though it is super decent). And I agree there are plenty of editors that work in many situations.







  • how many devices do you need to update?

    ansible wants to have a home base and an inventory of devices to manage. for example, if you have a flock of Rasberry Pi’s and a server stashed under a desk somewhere, yes, ansible is 100% going to simplify your life.

    ansible mgmt from a device to that same device… It might be just as easy to make backups and track your file deltas. the temptation is to use ansible so you remember what changes you made, but it can be a pia when you need to do a quick shift and have to go thru the playbook (unless you have playbooks on the ready).


  • PuppyOSAndCoffee@lemmy.mltoSelfhosted@lemmy.worldHomeServer main storage upgrade
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    1 year ago

    what you are attempting is called high availability; it might not be worth it; usually would need three different physical devices (in a homelab situation)…a load balancer to route traffic, and two nodes to handle said traffic. to perform your storage upgrade, you pull one device out of the load balancer, do your upgrade, and then add it back in. then, you do the same for the other load balancer. this would have 100% service availability…but this is a lot of work for a one-person show!

    do that for fun - you do you. however, if you can handle a few hours of downtime and don’t want to burden yourself with the long time care+feeding the above setup will require…

    remember you can use USB boot, mount both your drives, and then if you are lucky, your distro (on USB) will have a disk management/cloning utility.

    click click click, boom…you have bit perfect copy of small M2 on to large M2.

    Do not change your small M2! power down, swap 'em, and power on! if it doesn’t work, you still have your OG M2 to boot from.

    there are backup/restore utilities and other ways, each taking more and more time…but M2 is pretty quick.


  • lol - gotta keep the man sharp

    btw - who downvotes ppl (you + me ) praising a guy for battling cancer, because that’s what it is … Cancer strips us of our humanity - doesn’t matter who you are, it reduces you. And the only way to live is to keep a positive attitude, do everything medicine has to beat it into submission and see that next sunrise.

    I have always liked RMS because he praised solutions to problems, hope there is someone else to carry his torch.



  • Leave ‘em behind.

    What should be and why it is, two diff questions…

    A terminal renders a single glyph in a grid. That’s it. This stems from the days from before - when there was no graphics instruction to render anything different, and link speeds could be, on bad days, slower than typing speeds.

    Terminal rendering evolved to include ANSI instruction to manipulate the rendering-color, grid position, etc.

    However, at its core, is this limitation…a glyph in a grid…and this limitation is due to how slow terminals are.

    Terminals originally operated at a serial baud rate where one could nearly type faster than the transmission speed.

    X windows…was designed…to not have these limits.

    Terminal emulation is handy, but … it is limited. By definition retro. If a terminal doesn’t work…move on…and make something that does :)





  • Puppy Linux - the OS is spooled into RAM from a single signed compressed image. by default there is no write back to physical data store; this can include user folders etc. each boot can be a clean slate.

    Since the OS itself is in a single compressed & signed package, if someone alters it via a sidecar boot to an alt OS, it and you would know.

    When there are chain of custody issues it is pretty secure when added with the usual bevy of other securing options.