[–] 3 points 8 months ago (2 children)

I not sure what you are trying to argue.

Even if you audit the code yourself, you still need to trust your OS, you need to trust the hardware the OS is running on, and you need to trust the proprietary drivers of each component in that hardware. Then at that point you gotta trust the person who sold you the hardware hasn't modified it.

Ok and?

  • source
  • parent
  • context
  • [–] 20 points 8 months ago (3 children)

    First take a deep breath, there are infinitely more ways to fuck up a system beyond repair and you are not even in the yellow zone.

    1. Plug in the old usb stick
    2. Go into BIOS and change boot order to usb
    3. boot into live mode, there is usually an option to 'try the os' instead of installing it, do that
    4. There download a new image, maybe mint or correct version of pop!
    5. put in a new usb stick
    6. use 'dd' to write the image to the new usb stick
    7. reboot into the new usb stick and install the image
  • source
  • [–] 13 points 9 months ago (2 children)

    For large networks with over 20 devices, I find them acceptable not because they are good but because other options are more expensive.

    For small networks? I despise them

    1. The UI keeps changing and moving around settings for no good reason after each update
    2. You can't setup devices directly if you have a device or two, you are required to setup a control center
    3. The control center is already slow and sluggish, but the real nightmare starts when you start having 100 or more devices
    4. Last couple of years they have been releasing batches with serious issues, software and hardware. The way they accepted recall for unfixable devices was so limited that many people are left with broken APs that will kill their network occasionally and the poor consumer has no idea why.
    5. Honestly fuck 'em. there's more but I don't wanna give them any more rent space in my head on a Sunday lol
  • source
  • view more: ‹ prev next ›