Slashdot Mirror

← Back to Stories (view on slashdot.org)

LSB & Posix Conflicts

Posted by Hemos on from the understand-it-better dept.

An anonymous reader writes "The OpenGroup has published a detailed list of the conflicts between the Linux Standards Base and Posix ? that is accessible through their website. "

4 of 354 comments (clear)

  1. POSIX LSB by Gorny · · Score: 5, Insightful

    IMHO it's better for GNU/Linux (never know if rms is watching ;) to comply to the older POSIX standards than a nice utopian LSB. I doubt if it will ever get of the ground since the whole Linux distro's are so scattered and divided (let alone the commmercialization of certain products).

    btw. check the following for more information on POSIX
    http://www.posix.com/
    http://standards.iee e.org/regauth/posix/

    --
    Alan Perlis once said: "A language that doesn't affect the way you think about programming, is not worth knowing"
  2. Re:Oh yeah? POSIX can be DUMB! by __past__ · · Score: 5, Insightful
    Doesn't matter a bit. If anything, issue a warning if someone uses a potentially dangerous function (like FreeBSD does for stuff like mktemp, the linker will print "Warning: Potentially unsafe use of mktemp, consider using mkstemp instead" or some such), but don't break apps that adhere to the standard. It has "portable" in its name for a reason.

    Even the bash approach where you have to explicitly ask for POSIX-conforming behaviour is better than nothing, even if I think that it should be the default.

    There are only two sane ways to deal with POSIX brain-damage: Fix POSIX, or don't use that stuff in your programs. OSes that are "mostly" POSIX-compatible are worse for portability that those who just say that they don't implement POSIX at all.

    --
    Programming can be fun again. Film at 11.
  3. Re:Oh yeah? POSIX can be DUMB! by Anonymous Coward · · Score: 5, Insightful

    Errr, no, we need to actually eliminate these functions that are unsafe by design, and if a program uses gets(), then too bad, it needs rewritten by an actual programmer and it can't be ported until it is rewritten.

    This is on the same scale as your mother asking, "If all your friends jumped off a bridge, would you jump."

    Them even bringing up gets() makes me doubt their whole report. If the rest of their comments are on the same scale as this, I'd say go with the LSB everytime.

    The LSB overrides and superceeds all previous standards with a single common way of doing things that actually halfway makes sense.

  4. Re:POSIX is required! by pmsyyz · · Score: 5, Insightful

    Ask yourself this: can you read a copy of the POSIX standards online?

    No, that's why Linus couldn't implement it fully.

    --
    Phillip