1. 39

When submitting the Quest OS, I couldn’t find a tag that fit it past CompSci. I noticed more than once we don’t have a tag to say something is about developing or releasing an operating system even though that’s the category for many examples of research, FOSS projects, and commercial products. We do have specific tags for some popular UNIX’s, Mac OS, and Windows as precedent for an OS-centric tag. This tag can merely be called “OS - Operating Systems.”

  1.  

  2. 35

    I suggest ‘osdev’. I believe a tag named just ‘Operating Systems’ or ‘OS’ would be too happily applied along any other system qualifier (ie. openbsd + os).

    +1 for adding a general ‘osdev’ tag.

    1. 6

      Yes, I had suggested a tag for general OS, kernels, drivers, and low-level embedded before. Rob Pike can’t claim it’s dead now!

      1. 3

        I have two goals with the tag:

        1. Cover obscure OS’s, old or new, people havent heard of. Preferrably that are in a state where the features they claim are implemented versus the hundreds of toy projects unfinished.

        2. Writeups on OS development.

        Your tag covers 2 obviously. Maybe not 1.

        1. 2

          Can you find some examples that would not cover 1? I think they should be pretty well covered by using another tag for the specifier of the niche (security, ocaml, erlang, whatever).

          With similar reasoning, your tag ‘os’ would both apply to toy projects & finished niche systems so it would not help in filtering out toy projects at all.

          1. 3

            Any link with detailed info on an OS that’s not about building it that’s also not already a specific tag. That includes MCP, Stratus, NonStop, VMS, Amigas (esp Morphos), BeOS, Haiku, Sanos for Java, any fielded RTOS’s (esp QNX), usable microkernels like OKL4, network OS’s, lamguage-specific OS’s like JX or COSMOS, and so on.

            There’s piles of OS’s out there with features people can learn from without seeing source itself. Far as incomplete or pure toys, I say we discourage all of those from Lobsters submitted stories as a general rule. Only exception would be toy examples used in otherwise great writeups that teach important concepts or techniques where simplicity of the example is a learning aid. Compiler designers and formal verification do that a lot.

            1. 2
              • MCP - osdev, historical
              • Stratus - osdev, historical, perhaps would be nice to have a critical systems/realtime tag.
              • NonStop - osdev, historical, critical systems?
              • VMS - osdev, historical
              • Amiga - osdev, historical
              • Morphos - osdev, critical/realtime
              • BeOS - osdev, historical
              • Haiku - osdev or deserving it’s own haiku tag
              • Sanos - osdev, java
              • QNX (and other RTOS) - osdev + I think rtos or realtime would be a nice tag in it’s own

              We might differ in how we treat tags. I treat tags for the following purposes:

              1. narrow down stories to things that interest me
              2. filter out stories that don’t interest me

              I might not care on osdev but be interested in a java operating system. I can not care about osdev in general but like historical operating systems - both approaches allow me to filter in/out the above list.

              1. 1

                How do the BSD’s get labelled in your categorization? Most on them would fit under OSdev. Plus, many you describe as historical are existing products still updated running on modern hardware. UNIX or Windows might be historical if you’re going that far.

                1. 1

                  Depends on the article. If you look at the OpenBSD tag right now it has various content.

                  • security
                  • networking
                  • ruby
                  • historical
                  • release
                  • freebsd,netbsd (common history article)
                  • as above but for testing
                  • hardware

                  so already we have topics that fit not only OpenBSD (testing operating systems), or fit OpenBSD but are not strictly osdev (switching from 1 password to bitwarden, hackathon reports, libressl release).

                  Hence I think we are ambiguous already and depend on people using the secondary tags to specify the topic.

                  Now why I am pushing on osdev is strictly on the filtering purpose. There are a lot of OpenBSD tagged articles that would benefit with the osdev tag (specifically talking about operating system development) versus articles about an operating system (everything under the openbsd tag would be fitting). That is the case I raise.

                  1. 2

                    I wouldnt object to such a compromise if we were already having to double tag such things. So long as we have some kind of tag for generic OS’s. It’s a common category in schools, IT directories, and so on. It’s absence here is more an exception than the rule.

                    1. 1

                      Now why I am pushing on osdev is strictly on the filtering purpose. There are a lot of OpenBSD tagged articles that would benefit with the osdev tag (specifically talking about operating system development) versus articles about an operating system (everything under the openbsd tag would be fitting). That is the case I raise.

                      programming and compsci already exist as the “overflow” tags - another I don’t think is too beneficial.

          2. 3

            +1 for osdev.

            I wonder if a ‘research’ tag would be more general (might be applied to new programming languages too, for example) without being too vague.

            1. 8

              I think the existing plt tag covers programming language research pretty well. Research feels too broad.