Slashdot Mirror


NetBSD gets New sysctl Infrastructure

jschauma writes "NetBSD's Andrew Brown has committed a complete rewrite of the kernel's sysctl infrastructure. To test these changes, he cross compiled 150 kernels for 30 architecures to see where some problems might come up. Additional information can be found in Andrew's email to current-users."

7 of 44 comments (clear)

  1. How to develop and test: by HoldmyCauls · · Score: 3, Insightful
    To test these changes, he cross compiled 150 kernels for 30 architecures to see where some problems might come up.


    That's dedication. Kudos.
    --
    Emacs: for people who just never know when to :q!
  2. Will it be picked up by Open/Free? by Anonymous Coward · · Score: 4, Interesting

    I am sure the OpenBSD developers will check it out and add it if it makes sense to them, without affecting security. I recall they had to add sysctl variables for pf, which is what makes thing brittle to change.

    Kudus, that is a lot of dedication!

  3. An honest question by austus · · Score: 2, Insightful

    What are the benefits to having this new sysctl infrastructure?

    1. Re:An honest question by MavEtJu · · Score: 3, Informative
      From the first link on the article:
      • The kernel knows about (but does not currently use) the name to number mapping for each node. Auto-discovery of the tree is now possible.
      • Nodes can now be added to the tree by lkms, device attachment routines or at securelevel 0 from the command line via the sysctl binary.
      • Adding new nodes (or subtrees) to the sysctl tree is now much simpler.
      --
      bash$ :(){ :|:&};:
  4. Re:BSD Makes The "B" Team! by edhall · · Score: 5, Insightful

    Moderators are selected from the Slashdot community, and so have the same biases. Six months ago I would have said that the Slashdot BSD section had a trolling problem. I think it's pretty clear now that Slashdot itself is a good part of the problem.

    Slashdot has taken the attitude that the BSD community is responsible for cleaning up the problem via moderation, and failure to do so means that the community doesn't care. Since the community doesn't care enough, the reasoning goes, BSD really is, in some sense, dying and not worth saving. But this makes two assumptions that are easily shown to be false:

    1. If the BSD community (or other small community within Slashdot) cares to use it, moderation can effectively clean up the trolls, crap floods, and so forth.

      This ignores the asymmetry of the situation. A crapflooder with a dialup connection and an idle hour or two can post dozens of messages. For this, several community members have to use up all of their weekly (if they're lucky) mod points, knowing full well that the same misfit can come back and do it again minutes later.

      There aren't that many more trolls or crap flooders in the more popular sections but there are a lot more moderators, so no one has to blow their entire allotment of mod points dealing with miscreants. (And I might note that all the complaints about trolls and crapflooding here indicate a community that would deal with the situation if it had the mod points to do it.)

    2. Moderation is self-regulating.

      The fallacy of this belief was brought home to me not long ago when I was metamoderated "unfair" twice in succession for down-moderating obvious trolls in the BSD section. And, as many of us have noted lately, there are an increasing number of irrelevant postings and even blatant trolls getting positive mods. Once again, the supposed self-correcting nature of moderation fails for lower-trafficked sections.

    This is actually just the tip of an iceberg which threatens to smash Slashdot into a chaotic free-for-all; I don't think the BSD section is likely to be an isolated case for long (if this is even the case now). Just skim through the postings on nearly any technophile (i.e. geeky) subject, and see how little interest there is for true "News for Nerds" any more. At least the half the posts will be "Who the hell thinks this is interesting enough for an article?" or "Hasn't this been done before?" There is little moderation and it can take some time before the trolls and crapfloods get mopped up.

    On the other hand, each tidbit from the SCO or RIAA affairs gets many hundreds of highly-moderated "Ain't it awful" posts, and at least for the first several hours obvious trolls get squashed in minutes. (This despite the fact that very little is newly Insightful or Informative any more on thse subjects, or even much left that is Interesting.) I'm sure that Slashdot gets loads of ad impressions when they run these stories, however, and perhaps the cynics who claim that this is the reason Slashdot runs them are right. But that's irrelevant; the fact is that as a result of these stories Slashdot's content is getting softer and softer, and therefore the average Slashdotter is more likely to be only a camp follower of the technophile community, driven by peer influence rather than an actual passion for computers and technology.

    This is all grossly off-topic (except in the sense that Slashdot is a proper topic for a posting on Slashdot), and I expect some Offtopic moderations as a result. But over the years I've seen Slashdot becoming a bloated caricature of its former self, and this seemed as good a time as any to speak up.

    -Ed
  5. Moderation in BSD Section (OT) by OldMiner · · Score: 2, Interesting
    Threshold: 0: 6 Comments
    Threshold: -1: 27 comments

    Boy, that looks like moderation is working for me. But, perhaps there was some lag in this effect. Also, I give a -1 Anonymous modifier. You might try it. (Granted, it would be valuable if modifiers and thresholds could be made per section or dependent on the number of comments, but beggars can't be choosers.)

    The issue, I believe, is that troll patrol is done in large amounts by the slashdot admins who have infinite moderator points. As was shown in the early days of Slashdot, one admin with infinite mod points per 100 users spread across 10 articles is sufficient. The same works for the small sections like Developer and BSD. It just takes more lag time for admin to notice these things in small sections because they're concentrating on more highly commented stories. Once more, as you noted, there are less people with mod points reading. So, as near as I can tell, the system works, albeit maybe a little more slowly than you like.

    Now, then there's your reaction. To be honest, the grandparent post was mildly humorous. Since I don't see many troll posts, I don't know if these is a unique post, or just another unoriginal copy and paste. The reason it was made, however, in either case, is because of people -- well -- like you. You're reacting strongly to a stupid post of relatively little significance which most people won't see. The post offends you and raises your ire. But consider the lack of talent required to make such a post and how little effect it truly has. It's a dying joke that anyone who reads Slashdot has seen before in some form or another.

    If that doesn't help you, consider this strategy: give anonymous posters -6. Give foes -6. Foe logged in trolls. You won't see trolls. But, as always, please don't feed the trolls.

    2) Moderation is self-regulating.

    The fallacy of this belief was brought home to me not long ago when I was metamoderated "unfair" twice in succession for down-moderating obvious trolls in the BSD section.

    You really want to be paranoid? For EVERY time someone metamods you as unfair, even if everyone else mods you as fair, you lose karma. Don't believe me? Check out metamod.pl in the CVS. Now if that makes you uncomfortable, I think you lack perspective. If you're not a troll yourself and have useful things to say, your karma will recover. And that second part isn't wholly necessary.

    Trolls exist because some guys just plain don't have the right chemical balance in their brains, and they will always be that way. They can destroy a community if not properly regulated because to be a troll is to simply not see value in that community. But it looks to me that they are being properly regulated on Slashdot. Consider that it only takes one active non-troll moderator on average to cancel the effects of an active troll moderator. How many active troll moderators do you think there are? How about non-trolls like you and me? The bad thing is that in individual cases, someone might be poorly treated by the system, but I don't see any reason for your prediction of chaos. System works fine for me, on average.

    --
    You like splinters in your crotch? -Jon Caldara
    1. Re:Moderation in BSD Section (OT) by edhall · · Score: 2, Insightful

      Of 23 comments currently at score 0 or above, perhaps three have something relevant to say about the sysctl subsystem in NetBSD, and only one of these has any technical content. Around half of the Score 0 comments are trolls. I'd estimate that now, a full day after the article was posted, only about half of the needed mod points have been expended.

      Yes, downrating AC's eliminates much of the noise, but it also eliminates a significant fraction of any useful content. I don't consider it a solution.

      About a year and a half ago, before the trolls got the upper hand, it wouldn't have been at all surprising to have the author of something like the sysctl rework post several responses (usually as an AC), and a fruitful technical discussion would ensue. Such people now don't bother, even when someone like me bothers to tell them that there is a story on Slashdot about their project.

      Moderation is too little and too late for this situation.

      Here's another way that moderation can create a hostile environment: it is frequently used to enforce the majority view or to suppress dissent. (Just ask anyone who tries to say something even remotely positive about Microsoft.) Thus it has a lot to do with the development of a peer-pressure-based herd mentality. There are as many posts as there ever were, but in my humble opinion fewer and fewer of them have anything interesting to say. The Slashdot take on a given subject is often so one-dimensional that it is almost entirely predictable. I blame moderation for this.

      For a BSD example, consider what the accepted Slashdot wisdom is concerning the BSD license: it allows code to be "stolen" and tied up inside proprietary systems. Consider this recent post. I'll not bother to refute it here; see my response to it. My point concerns the fact that it got upmodded four times (and if you spend some time going through the rest of the discussion you'll see that it's hardly an isolated case). This kind of Slashdottiness is just another example of how moderation is broken and simply adds to the frustration of groups like BSD fans rather than helping clear the air for them.

      Well, that's enough commentary on this for this year. (And at this point I'm really not expecting there to be a next year; Slashdot has become of marginal use to me, with its BSD hostility being only a minor factor but a pretty stark example of what's broken.)

      -Ed