My main server is named Postulate (an idea that you assume for the sake of argument), my desktop is named Axiom (a proved postulate), and my backup server is named Corollary (an idea that follows from an axiom).

What are your computers named, and why?

  • OrangeCorvus@lemmy.world
    link
    fedilink
    English
    arrow-up
    17
    ·
    edit-2
    1 year ago

    Calculon - Workstation

    Flexo - Gaming laptop

    Bender - Intel Nuc/HTPC

    Hmm my Synology NAS is called Syn, I need to find a more appropriate name for it.

  • DaPorkchop_@lemmy.ml
    link
    fedilink
    arrow-up
    12
    ·
    1 year ago
    • poweredge-t620-0
    • poweredge-t620-1
    • poweredge-r520-0
    • macbook-2011
    • pi-0 through pi-3

    having read all these other comments, i’m now feeling like i should come up with a more creative naming scheme… for what it’s worth, my phone is named bob.

  • b9chomps@beehaw.org
    link
    fedilink
    arrow-up
    11
    ·
    1 year ago

    I don’t name my computers, but usually name my OS drive Brain and the media drive Pinky.

  • nik282000@lemmy.ml
    link
    fedilink
    arrow-up
    8
    ·
    1 year ago

    Damnit, I’m boring af. Machines are named by their model for laptops/consumer devices and buy their CPU for home built stuff.

    Except for Crimson-Binome.local 🏴‍☠️

  • paradox2011@lemmy.ml
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    1 year ago

    Desktop - thebox
    Server - thecloud
    Phone - thewand
    Tablet - theportal
    Home assistant - theoracle

    Not too creative, but it works.

  • gerdesj@lemmy.ml
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    1 year ago

    I once named a load of servers for a helicopter company in the UK with elements. The cluster nodes were copper, silicon, etc. The cluster itself was called iron. The volumes were labelled fe_function.

    It worked - it was easy to read and the bits that implied “cluster” were grouped appropriately. All the other servers had random elemental names unless they were associated in some way, in which case the group would be used. The engineers (real engineers with oil or distressingly nasty lubricants in their veins) loved it - it made sense, without being too quirky. It was very legible.

    When those systems were hoicked out and replaced, the usual nonsense was applied: 2 char country code + 2 char site code etc etc ad nauseam. Followed by my absolute pet hate: 01. Oh so you might need 99 domain controllers? Yes you might, but not on one site.

    Let’s face it, it is mostly AD admins who don’t get hostnames. I blame MS - their docs and blogs strive to be … authoritative or at least look so. An entire generation (possibly two) of sysadmins have been sold up the river by MS and their wankery.

    • D. Moonfire@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      I completely agree with the “01” problem, it should be “001”.

      Single digit is great but then one service needs more than ten, or you keep rolling them over into new ones (one of our production server is 13 because it’s the thirteen generation). But then I want all the numbers of have consistent patterns, so if one has two digits, they all have to have it.

      But I’m not allowed to name servers anymore.