Announcement

Collapse
No announcement yet.

Systemd 217 Will Introduce Its New "Consoled" User Console Daemon

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Originally posted by Naib View Post
    A software system is called "monolithic" if it has a monolithic architecture, in which functionally distinguishable aspects (for example data input and output, data processing, error handling, and the user interface), are not architecturally separate components but are all interwoven


    ALL aspects of SystemD is interwoven. It is monolithic, it is modular...
    sort out your defnition
    you missed word 'interfaces' in my reply, didn't you ?

    Comment


    • #32
      Interwoven one way does not mean it is monolithic. SystemD is more like a tree, not interwoven
      Monolithic means one piece. While I would agree separate binaries that cannot be separated PERIOD would classify as monolithic. This is not the case with SystemD.

      You do not have to use all the flags in SystemD You are free to use only the components your build needs.

      Comment


      • #33
        Originally posted by grndzro View Post
        Interwoven one way does not mean it is monolithic. SystemD is more like a tree, not interwoven
        Monolithic means one piece. While I would agree separate binaries that cannot be separated PERIOD would classify as monolithic. This is not the case with SystemD.

        You do not have to use all the flags in SystemD You are free to use only the components your build needs.
        which is why it is modular. It is still monolithic, like the kernel, like Xorg

        Comment


        • #34
          Originally posted by Naib View Post
          A software system is called "monolithic" if it has a monolithic architecture, in which functionally distinguishable aspects (for example data input and output, data processing, error handling, and the user interface), are not architecturally separate components but are all interwoven


          ALL aspects of SystemD is interwoven. It is monolithic, it is modular...
          sort out your defnition
          Nearly all your programs depend on glibc. By your definition its an evil monolithic glibc conspiracy!

          The detail you are missing is that you can replace the glibc part with a compatible replacement (thats where the "Interface" comes into play).

          Comment


          • #35
            Originally posted by Naib View Post
            which is why it is modular. It is still monolithic, like the kernel, like Xorg
            You need a lesson in English....
            Modular and Monolithic are mutually exclusive.

            From Webster
            Monolithic = consisting of or constituting a single unit
            Modular = having parts that can be connected or combined in different ways.

            Your comprehension skills are such that I find it impossible that you can adequately understand anything of complexity.

            Linux Kernel is one file.
            Xorg is a package of completely dependent files. All are required
            SystemD is a package that can be divided up as you see fit.

            See the difference?
            Last edited by grndzro; 08 October 2014, 06:36 AM.

            Comment


            • #36
              Originally posted by grndzro View Post
              You need a lesson in English....
              Modular and Monolithic are mutually exclusive.

              From Webster
              Monolithic = consisting of or constituting a single unit
              Modular = having parts that can be connected or combined in different ways.

              Your comprehension skills are such that I find it impossible that you can adequately understand anything of complexity.

              Linux Kernel is one file.
              Xorg is a package of completely dependent files. All are required
              SystemD is a package that can be divided up as you see fit.

              See the difference?
              wrong, go look up the software engineering definition.
              Being monolithic isn't bad, but saying it isn't when it is stretches reality.

              Comment


              • #37
                Naib = Gentoo Forum Troll.

                Before Naib wastes any more of your time people, you should know he is a gentoo forum user here to troll and spread poison.
                Yesterday he even posted in this thread: http://forums.gentoo.org/viewtopic-t...start-375.html : stating that Lennart needed someone to take their "dick" and put put it in his ass (like anal rape of lennart) his post got cleaned away by mod but maybe a google cache or something still exists.

                Comment


                • #38
                  Naib = Gentoo Forum Troll.

                  Before Naib wastes any more of your time people, you should know he is a gentoo forum user here to troll and spread poison and confusion.
                  Yesterday he even posted in this thread: http://forums.gentoo.org/viewtopic-t...start-375.html : stating that Lennart needed someone to take their "dick" and put put it in his ass (like anal rape of lennart) his post got cleaned away by mod but maybe a google cache or something still exists.

                  Comment


                  • #39
                    Originally posted by Naib View Post
                    wrong, go look up the software engineering definition.
                    You are the one making the claim, why don't you look it up and post a source here? A reliable source, not some random blog or anti-systemd website or something.

                    Comment


                    • #40
                      Originally posted by Naib View Post
                      wrong, go look up the software engineering definition.
                      Being monolithic isn't bad, but saying it isn't when it is stretches reality.
                      Nice try.

                      From Wikipedia
                      In software engineering, a monolithic application describes a software application which is designed without modularity. Modularity is desirable, in general, as it supports reuse of parts of the application logic and also facilitates maintenance by allowing repair or replacement of parts of the application without requiring wholesale replacement.

                      Just admit you are wrong. It's easier that way.

                      Comment

                      Working...
                      X