• hirihit640@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    2
    ·
    19 hours ago

    They could have been two commands that call a single parent command with different options. For example, imagine if cat had an option -N to restrict the number of lines that was printed, and also an option -t to start from the end. head would just proxy to cat -N and tail would proxy to cat -N -t. Combining the three into a single implementation reduces total LoC and opportunity for bugs. Also reduces total maintenance burden.

    I believe busybox is like this actually - a ton of Unix commands in a single package. It’s used by Alpine Linux, a tiny and performance linux distro commonly used by docker containers.

    • Kairos@lemmy.today
      link
      fedilink
      arrow-up
      3
      arrow-down
      3
      ·
      17 hours ago

      Busybox is literally just a bundle. That’s its whole purpose. It doesn’t reimplement anything.

      • hirihit640@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        1
        ·
        edit-2
        10 hours ago

        Some quick research says that it is indeed a re-implementation. The first line of the wikipedia, says:

        BusyBox is an implementation of many Unix commands in a single executable file.

        You can download the source code yourself to verify. And if you’ve actually used Alpine Linux before you would have also noticed that the commands provided by busybox have only a subset of the options provided by their GNU coreutils counterparts.

        Please do your research before so confidently correcting other people.