• @[email protected]
    link
    fedilink
    English
    41 year ago

    Why billboard system would have sane installed? I don’t think Debian or derivatives install it by default. Vnstat is also a bit odd, but maybe that’s just me. I assume they have multiple of these displays around and for them it would make more sense to use something more centralized, like zabbix, to monitor the whole network (obviously they could do that too).

    • @[email protected]
      link
      fedilink
      51 year ago

      assume they have multiple of these displays around and for them it would make more sense to use something more centralized, like zabbix

      The one I saw a decade ago yielded SNMP to solarwinds (I know I know) rather well, but they mainly used PING on it to see when the radio link died.

      Fancy that – when the parks n rec sites were converted to e-billboards, they had power but no net line, and “radio’s fine”. Show me an old linux billboard host and I’ll show you a canvas my inner child can’t wait to e-graffiti.

      • @[email protected]
        link
        fedilink
        English
        21 year ago

        Wait a second. They used AMPRNet to manage these things? In here this kind of things are either hardwired to the internet or they use 3/4/5G uplink and while of course techinally possible either way to breach the system it’s a bit more difficult to find out proper IP’s and everything.

        Once upon a time I had a task to plan a scalable system to display stuff on billboards and even replace printed ads on stores with monitors. The whole thing fell down as we couldn’t secure a funding for it, but I made a POC setup where individual displays had a linux host running and managing the display with (if memory serves) plain X.org session with mplayer (or something similar, it was about 20 years ago) running on full screen and a torrent network to deliver new content to them with a web-based frontend to manage what’s shown on which site. Back then it would’ve been stupidly expensive to have the hardware and bandwidth on a single point to service potentially few thousand clients, so distributing the load was the sensible solution. I think that even today it would be a neat solution for the task, but no one has put up the money to actually make it happen.

    • @[email protected]
      link
      fedilink
      English
      11 year ago

      The blue stuff is insulation/vapor barrier on new construction, so it’s not even completely built yet.

    • lurch (he/him)
      link
      fedilink
      791 year ago

      that is the exact opposite of systemd: sysvinit

      you can recognize it by the iconic makefile line in the output, which indicates the setting CONCURRENCY=makefile has been chosen.

      • @[email protected]
        link
        fedilink
        81 year ago

        Ah, back in the days before Lennart and RHEL killed linux.

        Having only run debian for a job interview - where I had to learn systemd and I fucking crushed it, woo - I would never have picked out that makefile line. Kudos.

        Having run automation in 2002 based on package triggers, makefile, cron and awk, I completely approve of using makefiles to orchestrate startup. That’s actually genius.

        • @[email protected]
          link
          fedilink
          41 year ago

          I’m still furious they intentionally broke CentOS. And then had the audacity to emulate SmallFloppy Glasspane and bake some spyware into Fedora.

            • @[email protected]
              link
              fedilink
              31 year ago

              Probably telemetry software. Basically mandated for any publicly traded software company these days.

              • @[email protected]
                link
                fedilink
                31 year ago

                The thing is that telemetry can be useful… bug reports let the developer know which bugs occur the most, feature logging lets the developer know which features are used the most (and thus what they might want to focus on adding new functionality to), etc. It’s become a dirty word since a lot of companies have telemetry that’s way too intrusive.

                • @[email protected]
                  link
                  fedilink
                  11 year ago

                  Yep! I understand, which is why I was clarifying for the previous commenter. As for if telemetry is morally justified, or if we should go back to old fashioned bug reports and some sort of upload system that requires direct user buy-in as the payment for privacy at the cost of reliability, mobility, and scalability is a discussion for someone else haha.

  • KillingTimeItself
    link
    fedilink
    English
    101 year ago

    looks like it’s starting cron? I’m assuming that’s debian/ubuntu then.

    Could be anything else, but if i had to posit a likely guess that would be mine.

    • @[email protected]
      link
      fedilink
      11 year ago

      The makefile style concurrency shows that it’s probably running sysvinit. The last version of Ubuntu to do that by default was 9.04.

      Either it’s a very old distro (Ubuntu 9.04 or earlier, Debian 7 or earlier, RHEL/CentOS 5 or earlier) or it’s a non systemd distro like slackware.

  • Lunya \ she/it
    link
    fedilink
    51 year ago

    No way, Debian uses systemd, and systemd uses systemd-journald for logging, and doesn’t need cron, because it has timers.

  • visnudeva
    link
    fedilink
    11 year ago

    Not Debian, it is how the arch Linux distros boot after the grub menu.

  • Cabbage
    link
    fedilink
    91 year ago

    Reminds me of the garbage can that keeps crashing at the Tim Horton’s downtown