Slashdot Mirror


User: Billygoat+Gruff

Billygoat+Gruff's activity in the archive.

Stories
0
Comments
5
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 5

  1. Re:Bring Back /usr/doc! on Updates from the Free Standards Group · · Score: 1
    Unfortunately, annoyances (hopefully temporary) are to be expected if people want to bring slightly-varying standards together to match a unified standard.

    At least you can use symlinks to get around the multiple file locations for now. it'll be annoying for awhile, but hopefully, eventually, as future distributions become more standards compliant the old symlinks can be phased out over time.

    Other problems might be encountered that simple links can't fix, that'll be a harder problem to solve in the meantime. Such as varying formats for etc files, for instance. Any lists of known problems/inconsistencies of this type?

  2. Re:IIRC on Windows 2000 Source Code Gets (A Few) More Eyes · · Score: 1
    Hello Fellow Billygoater!

    I see you, too, are helping clear the bridges of those pesky trolls.

    let's hang out in the pub tonite and drink some Troll Sweat brew.

  3. Re:Go away darpa on DARPA to Fund Open Source Security Research · · Score: 1
    Your sig is pretty ironic, considering this is the second obvious troll that you've bitten on in this story alone.

    that's the point, anon!

  4. Re:Go away darpa on DARPA to Fund Open Source Security Research · · Score: 3
    Darpa should keep it's nose out of the internet business. The internet is a creation of the free market and they are trying to coopt it for the gumint.

    Too bad that DARPA INVENTED the Internet! Back when they were still ARPA (Advanced Research Projects Agency). Now they've become DARPA by throwing a Defense in front of the ARPA.

    So as Mr. T would say, "Cut that jibba-jabba, fool! Internet wuzn't no creation of the free-market!"

  5. Re:Security on DARPA to Fund Open Source Security Research · · Score: 1
    But what happens when some malicious person decides to screw with the code? That's right. Disaster. It's on the horizon.

    And this is different from closed-source HOW? You seem to imply that it is because you also say this:

    Open Source has the most vulnerable model available, yes. Anybody who knows how to code can put anything they want into the code.

    That's why you don't compile random modules into the kernel. And it's also why you don't execute randomly-compiled code as root. This is in NO WAY different than me taking a closed-source kernel, doing some modifications to the binaries, and you running them on your own.