Slashdot Mirror


Linux Standard Effort Edges Ahead

ErikPeterson writes "The Free Standards Group has released its third version of the Linux Standard Base, an effort to unify some of the workings of the open-source operating system. The LSB is designed to make it easier for those producing higher-level software to support different versions of Linux. Pledges to conform to the requirements of Version 3 are Red Hat, Novell's Suse Linux, Asianux and Debian."

138 comments

  1. Making progress... by TripMaster+Monkey · · Score: 4, Funny


    Pledges to conform to the requirements of Version 3 are Red Hat, Novell's Suse Linux, Asianux and Debian.

    Four down, only 458 to go.

    --
    ____

    ~ |rip/\/\aster /\/\onkey

    1. Re:Making progress... by tpgp · · Score: 4, Interesting
      Pledges to conform to the requirements of Version 3 are Red Hat, Novell's Suse Linux, Asianux and Debian.
      Four down, only 458 to go.


      I think you are well aware Mr Monkey, that if Debian, Suse and Red Hat commit, the rest will follow (for instance Ubuntu will pick it up naturally next time they snapshot debian unstable).

      On a different note, when I last subsribed to the debian lists (some time ago now), I remember a bit of a flame war over an earlier incarnation of LSB.

      Basically - the argument was over whether the Debian GNU/hurd and Debian GNU/*bsd projects should follow the Linux standard base or just Debian GNU/linux.

      Here's a good (mid thread) post about it.

      Does anyone know if Debian GNU/hurd and Debian GNU/*bsd will follow the LSB3? Or just Debiam GNU/Linux.
      --
      My pics.
    2. Re:Making progress... by EvilMonkeySlayer · · Score: 0

      Are you by any chance an evil monkey?

    3. Re:Making progress... by gowen · · Score: 1, Funny
      when I last subsribed to the debian lists (some time ago now), I remember a bit of a flame war over an earlier incarnation of LSB.
      A flamewar? On a Debian mailing list? Inconceivable.
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    4. Re:Making progress... by Cronopios · · Score: 4, Informative

      Despite the original post, it wasn't Debian who pledged to conform to this standard, but the Debian Common Core Alliance.

      Nor Debian nor Ubuntu are part of it.

      Btw, in a recent post on his blog, Red Hat's Ulrich Drepper makes some criticisms of the LSB and its shortcomings of the v3 certification process.

      --
      Windows users:
      Internet Explorer is obsolete. Please upgrade to Google Chrome or Mozilla Firefox.
    5. Re:Making progress... by ackthpt · · Score: 2, Funny
      Four down, only 458 to go.

      C'mon, you know the only way this stuff will standardize is when Microsoft Linux comes out ;-)

      --

      A feeling of having made the same mistake before: Deja Foobar
    6. Re:Making progress... by Arker · · Score: 1

      I think you are well aware Mr Monkey, that if Debian, Suse and Red Hat commit, the rest will follow (for instance Ubuntu will pick it up naturally next time they snapshot debian unstable).

      RTFA. Debian is not in. Neither is Slackware.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    7. Re:Making progress... by tpgp · · Score: 1

      GP: that if Debian, Suse and Red Hat....
      P: RTFA. Debian is not in.

      You may find this link interesting:
      http://dictionary.reference.com/search?q=if

      --
      My pics.
    8. Re:Making progress... by cranky_slacker · · Score: 2, Interesting

      I think you are well aware Mr Monkey, that if Debian, Suse and Red Hat commit, the rest will follow (for instance Ubuntu will pick it up naturally next time they snapshot debian unstable).

      While I agree that all the derivative distro's will follow suit (like Ubuntu), I really doubt Slackware will adopt something just because Red Hat did. I seem to recall a nice little debate here on /. last week about the necessity/relevance of Slackware when v10.2 was released. The over-riding point I tried to make was that Slack was still relevant and the reason it is, is because Pat follows his own set of standards, namely, simplicity, reliability and stability.

      Personally, I think this whole thing is waste of time until all (or an overwhelming majority) distros adopt them. Until then, it shouldn't even be called a standard. They're guidelines.

    9. Re:Making progress... by sloanster · · Score: 1

      Four down, only 458 to go.

      Since the four distros cited account for 99% of the business users of linux, as well as the majority of home users, does it really matter what the other 458 do?

    10. Re:Making progress... by Anonymous Coward · · Score: 0

      Allow me to reconstruct the context.

      Pledges to conform to the requirements of Version 3 are Red Hat, Novell's Suse Linux, Asianux and Debian.
      Four down, only 458 to go.

      I think you are well aware Mr Monkey, that if Debian, Suse and Red Hat commit, the rest will follow (for instance Ubuntu will pick it up naturally next time they snapshot debian unstable).

      Of course you knew that, since you were the poster he was referring to. Perhaps you should look up the definition of moron.

    11. Re:Making progress... by Wiwi+Jumbo · · Score: 1

      Now... I know you meant to be funny.... but...

      --
      Wiwi
      "I trust in my abilities,
      but I want more then they offer"
    12. Re:Making progress... by sheppos · · Score: 1

      A flamewar on slashdot? Inconceivable!

    13. Re:Making progress... by Anonymous Coward · · Score: 1, Interesting

      "Despite the original post, it wasn't Debian who pledged to conform to this standard, but the Debian Common Core Alliance [dccalliance.org]."

      Debian has supported the LSB in the earlier versions, what makes you think it would be any different with 3.0.

      You can go to their website now:

      http://packages.debian.org/cgi-bin/search_packages .pl?keywords=lsb&searchon=names&subword=1&version= unstable&release=all

      : and see these.

      Package lsb

              * unstable (misc): Linux Standard Base 3.0 support package
                  3.0-7: all
                  3.0-6: all

      Package lsb-base

              * unstable (misc): Linux Standard Base 3.0 init script functionality
                  3.0-7: all
                  3.0-6: all

      Package lsb-core

              * unstable (misc): Linux Standard Base 3.0 core support package
                  3.0-7: alpha arm i386 m68k mips mipsel powerpc s390
                  3.0-6: amd64 sparc
                  3.0-5: hppa hurd-i386 ia64

      Package lsb-cxx

              * unstable (misc): Linux Standard Base 3.0 C++ support package
                  3.0-7: alpha arm i386 m68k mips mipsel powerpc s390
                  3.0-6: amd64 sparc
                  3.0-5: hppa hurd-i386 ia64

      Package lsb-graphics

              * unstable (misc): Linux Standard Base 3.0 graphics support package
                  3.0-7: alpha arm i386 m68k mips mipsel powerpc s390
                  3.0-6: amd64 sparc
                  3.0-5: hppa hurd-i386 ia64

      Package lsb-release

              * unstable (misc): LSB release command
                  1.4-8: all

      Package lsb-rpm

              * unstable (devel): Red Hat package manager for LSB package building
                  4.0.4-31.1: alpha amd64 arm hppa i386 ia64 mips mipsel powerpc s390 sparc
                  4.0.4-31: m68k

      Package lsbappchk

              * unstable (misc): Linux Standard Base application compliance checking tool
                  1.3.4-1: amd64 i386 ia64 powerpc s390

      : looks like support to me. ;)

      Later, Seeker

    14. Re:Making progress... by Anarke_Incarnate · · Score: 1

      j00 keep using that word....

    15. Re:Making progress... by doubledoh · · Score: 1
      Or the more probable Google Linux.

      When Google releases their distribution, they will be setting the standards for the Linux community.

      --
      I think, therefore I doh.
  2. Dupe? by gustgr · · Score: 0, Redundant

    This was posted just 2 days ago. Isn't exactly a dupe, but was really necessary to post this news about LSB? It is implicit that LSB 3.0 was released in that one.

    1. Re:Dupe? by Anonymous Coward · · Score: 0

      Well, as the quote of the day says:

      There is only one thing in the world worse than being talked about, and that is not being talked about. -- Oscar Wilde

      Dupes are endorsed by Oscar Wilde as better than not having the story posted at all.

    2. Re:Dupe? by SumDog · · Score: 1, Redundant

      Well to be fair, the last article talked about why LSB is awful and shouldn't be implemented. This article mentions the other side of it. You're right it's not exactly a dupe, but then again, there's nothing really new here.

  3. Standards by Tomchu · · Score: 4, Insightful

    A standard is a standard when everyone is using it. Just calling it one doesn't make it so.

    --
    I used to think Linux was cool -- then I turned 14.
    1. Re:Standards by Anonymous Coward · · Score: 2, Funny

      Then, by that definition, neither metric nor imperial are standard systems of measurements. Why? Because not everyone is using it.

      You lose. Have a nice day.

    2. Re:Standards by Tomchu · · Score: 0

      I was aware of that fact while writing my comment. The truth of the matter is that there are only two countries left out there who are using the silly Imperial system, and only because they're too proud/stubborn to just suck it up and switch to metric. As for LSB ... we have what ... 8 distros using it in one form or another, and about 500 that aren't? Thanks for trying. Play again?

      --
      I used to think Linux was cool -- then I turned 14.
    3. Re:Standards by Anonymous Coward · · Score: 2, Informative

      No, that's a de facto standard. We're talking de jure, as in planned and drafted.

    4. Re:Standards by Anonymous Coward · · Score: 0, Flamebait

      Whoa whoa whoa whoa, no changing argument midstream. You said "a standard is only standard if everyone follows it". Meaning if there exists one person out there who does not follow that standard, it isn't a standard.

      You can't suddenly bring up degree and posit that in your argument - that isn't what you posited the first time. You can, of course, admit you were wrong and revise, and in which case, you'll have my complete agreement.

    5. Re:Standards by Tomchu · · Score: 0

      Alright, sure. Revision: A standard is a standard only when a great majority is using it.

      --
      I used to think Linux was cool -- then I turned 14.
    6. Re:Standards by Anonymous Coward · · Score: 0

      From the article:

      Pledges to conform to the requirements of Version 3 have come from Red Hat, Novell's Suse Linux, Asianux and Debian.

      Now, if these are on board, surely a load of derived distributions are about to "inherit" LSB compliance as a result? I think 8 distros would be an underestimate.

    7. Re:Standards by afr0byte · · Score: 5, Informative

      Yeah, and what percentage of Linux usage do these distros encompass? Based on Linux Counter, these distros (including fedora for redhat) encompass 41.31% of users. If Mandrake, for example, jumps on board then that'll be over 50%, a majority. I'm not even counting Asianux, because I couldn't find a number on that.

      --
      Bier zum Frühstück
    8. Re:Standards by rufty_tufty · · Score: 1

      /me gets nitpicky
      Greatest number of people or greatest number of factions :-)

      What about atm? More data flows over atm than over ip, (most backbones for major carriers are ATM based as are most broadband links to the home) but tcp/ip has won the mindshare regardless of the fact that most internet links are IPoATM.

      Another standards war there for you to consider; so maybe greatest number isn't always the case either, marketing mindshare has an effect too :-)

      --
      "The weirdest thing about a mind, is that every answer that you find, is the basis of a brand new cliche" -
    9. Re:Standards by gr8_phk · · Score: 1
      "A standard is a standard when everyone is using it. Just calling it one doesn't make it so."

      That's why Microsoft says .doc is a standard document format. Just because a majority use something doesn't make it a standard.

    10. Re:Standards by Anonymous Coward · · Score: 0

      Fuck you.
      Un estudiante Mexicano que trabaja en los veranos como jardinero de los gringos.

    11. Re:Standards by Mr.+Underbridge · · Score: 1
      A standard is a standard when everyone is using it. Just calling it one doesn't make it so

      Tell that to NIST and ANSI.

    12. Re:Standards by Anonymous Coward · · Score: 0

      I have mod points that I could give you...
      Shame that your sig sucks as bad as it does.

    13. Re:Standards by DarthStrydre · · Score: 1

      Just 2 countries? Then why are pin headers and chip leads spaced on .1" centers? and sometimes 2mm centers?

      The metric/imperial debate is often stated as 'well everyone else switched - it should be easy for us/uk to switch as well'. Everyone else did not switch. Officially, perhaps, and in some markets, but there are numerous standards based on Imperial that will not change any time soon.

      The problem is that there are too many international goods sold that conform to the imperial standard to get rid of it.

      I am all for the adoption of metrics here in the US, but imperial tooling pervades all countries, and without a country to champion the lesser standard, everyone would suffer. Currently you have to have 2 sets of wrenches, which is bad enough. But if the entire world switched to metric, where would you find tools to work on older equipment? ebay? museums? I need a 6.35mm wrench to work on this 1/4" bolt.

      P.S. I hear Vista is supposed to be LSB3 certified :-P

    14. Re:Standards by Tim+the+Gecko · · Score: 1

      most backbones for major carriers are ATM based

      Not true. Major carriers have OC192 (10Gbs) links in their backbones running Packet over SONET (POS). ATM cards are way more expensive and don't go up to such high speeds on Cisco and Juniper routers. Typically carriers would have swapped out their OC12 ATM for OC48 POS five years ago and have just kept augmenting since then.

    15. Re:Standards by __aajwxe560 · · Score: 2, Insightful

      Whoever flagged you as insightful should be ashamed of themselves. A standard provides a common goal for whomever is interested to work towards. Whether or not the majority work towards the goal does not make it any less of a standard. The short lived DIVX player from Circuit City was a standard, as there exists many different standards for DVDs. Whether or not the majority of devices embrace such a standard does not refute the fact that it exists. Many different types of standards start out in the minority, and many remain so, but they still serve a purpose.
      Anything that promotes some form of application commonality amongst the various Linux distributions certainly cannot be a bad thing.

    16. Re:Standards by rufty_tufty · · Score: 1

      Well when I worked at Nortel (9 months ago) That wasn't the case for most carriers we sold to.
      Yes they were OC192, and they were definitly POS, but the packet standard was ATM.

      Maybe that was just Nortel's customers as opposed to Cisco and Juniper's, but from my visability we shifted more ATM than GIGE; things were changing and new architectures were GIGE based, but we always had the existing ATM backbone in there.

      --
      "The weirdest thing about a mind, is that every answer that you find, is the basis of a brand new cliche" -
    17. Re:Standards by jeanjean83 · · Score: 1

      Maybe you will learn to enjoy Linux when you turn 15

    18. Re:Standards by Tomchu · · Score: 1

      Nah, I very much enjoy my Mini running OS X, laptop running XP, and server running Server 2003. My time has value. I can't be wasting it compiling kernels and editing config files all day long.

      --
      I used to think Linux was cool -- then I turned 14.
    19. Re:Standards by Anonymous Coward · · Score: 0

      LSB? as in Least Secure Base?

    20. Re:Standards by sloanster · · Score: 0, Redundant

      LOL, I haven't compiled a kernel in years, I've been using vendor distro, and as it turns out, they supply a kernel.

      Apparently my time has even greater value than yours. I don't use ms windoze because I can't be bothered futzing around with constant virus updates, spyware removal, "hot fixes", reboots etc. With Linux, I just get the job done, and don't have to spend any time or effort trying to keep the whole thing afloat as would be the case with ms windoze.

      Agreed, the mac mini is nice. I bought a mini a few months ago, and while it's a cool toy, there's no way it could replace suse linux as my primary platform - YMMV.

    21. Re:Standards by teknomage1 · · Score: 1

      Considering Debian isn't actually on board (Doesn't use .rpm format) you're down to 33%. And what's with the Mexican gardener thing in your sig?

      --
      Stop intellectual property from infringing on me
    22. Re:Standards by Anonymous Coward · · Score: 0

      The sig is really stupid.
      He doesn't believe in God. Wow, good for him, I guess.

      HaHa Jesus is a common Mexican name, very clever. Even funnier when paired with a shitty stereotype.

    23. Re:Standards by Anonymous Coward · · Score: 0

      So the real standard is not HTML, but IE-HTML?

    24. Re:Standards by Tomchu · · Score: 1

      Virus updates ... nope, no virus scanner Spyware removal ... nope Hot fixes ... hey, I stop by at WU once a month, it takes 5-10 minutes of my day Reboots ... not since last month's WU Yeah, so apparently I'm capable of keeping my "Windoze" PC free of spyware and viruses. That doesn't say much about your intelligence. Downloading britneyspearsnude.jpg.gif.exe is *bad*. Nice attempt at a troll, though. Go masturbate to some hot anime-style female Tux drawings.

      --
      I used to think Linux was cool -- then I turned 14.
  4. Package management by Anonymous Coward · · Score: 5, Insightful

    What the LSB should, imo, do is make autopackage the format of choice for installing applications and then have the default package manager (such as rpms and debs and stuff) to download the dependent libs and keep the base system up-to-date. That way, everyone's happy. The newbies get their easy program installers and the seasoned veterans get their apt. But, alas, it's apparently not to be.

    1. Re:Package management by Benanov · · Score: 2, Informative

      Autopackage isn't quite integrated with the default package manager yet (per their website, http://autopackage.org/) Once that happens I can see that being very likely. ;)

    2. Re:Package management by m50d · · Score: 1

      How is autopackage any better than rpm (which is what it uses)? LSB packages don't have dependencies, that's the whole point of the LSB, so what're the advantages, and do they outweigh the difficulties of switching?

      --
      I am trolling
    3. Re:Package management by Anonymous Coward · · Score: 0

      autopackage checks that the dependencies are there, unlike rpm, apt and portage that have a database. Also, autopackage is meant to give package control to the developer of the package, eliminating the need to repackage it for each and every distro. Since it's meant for the last tier (applications) mainly, that means you can use rpm for the base & libs and autopackage for apps (and also some rpm apps if you want). Commercial games would benefit GREATLY from this.

    4. Re:Package management by runderwo · · Score: 1

      Autopackage generates distribution-specific packages from generic autopackage'd sources. All you need to do is add support for your distribution/package manager to autopackage in order to be able to install any autopackage'd source on your machine as a native package - it is automatically generated by autopackage.

    5. Re:Package management by Bloater · · Score: 1

      Autopackage requires running vendor supplied binaries as root. It is a *very* *very* *bad* idea.

    6. Re:Package management by runderwo · · Score: 1

      So what? RPM and Debian packages both run their pre- and post-installation scripts as root. If you don't trust the software provider, you are in hot water no matter where you stand.

    7. Re:Package management by Bloater · · Score: 1

      > RPM and Debian packages both run their pre- and post-installation scripts as root.

      Yeah and the lsb shouldn't standardise on them either (except if they specify that pre and post installation scripts do not have to be supported).

      > If you don't trust the software provider, you are in hot water no matter where you stand.

      Not true at all. You are only in hot water if you run the software as root. Most application software *never* gets run as root, so why should the vender be trusted with RootPower for the pre/post installation scripts.

    8. Re:Package management by runderwo · · Score: 1
      Not true at all. You are only in hot water if you run the software as root.
      We'd like that to be true, but in reality there probably isn't a single version of Linux that is not vulnerable to a root exploit from an unprivileged process. Anyway, you could use trust to decide whether packages signed by this person/company should be able to execute code as root on your machine. It doesn't have to be all or nothing.
    9. Re:Package management by m50d · · Score: 1
      autopackage checks that the dependencies are there, unlike rpm, apt and portage that have a database.

      I'll bet that makes circular dependencies wonderful to handle, not to mention virtual ones. But anyway, LSB packages on LSB distros don't need dependencies, that's the whole point, so this doesn't matter.

      Also, autopackage is meant to give package control to the developer of the package, eliminating the need to repackage it for each and every distro.

      So is the LSB, you only need to make one LSB RPM and it works on all LSB-compliant distros.

      Since it's meant for the last tier (applications) mainly, that means you can use rpm for the base & libs and autopackage for apps (and also some rpm apps if you want).

      Or, you could just use RPM for everything and things would be simpler?

      Commercial games would benefit GREATLY from this.

      I fail to see how it's any easier than RPM.

      --
      I am trolling
    10. Re:Package management by m50d · · Score: 1
      We'd like that to be true, but in reality there probably isn't a single version of Linux that is not vulnerable to a root exploit from an unprivileged process.

      Do you have any evidence for this? The local root in 2.4 kernel was fixed pretty darn quick, and I haven't heard of any being discovered since then. Anyway, security is about reducing risk to an acceptable level, it's impossible to eliminate it entirely. It's a lot harder to escalate privileges and then do something nasty than just write a program that does whatever you want it to.

      --
      I am trolling
    11. Re:Package management by m50d · · Score: 1
      All you need to do is add support for your distribution/package manager to autopackage in order to be able to install any autopackage'd source on your machine as a native package - it is automatically generated by autopackage.

      And all you need to do is make your system LSB compliant and then you can install any LSB-compliant package on it. And all the big vendors seem to be moving for compliancy. How does autopackage handle things like different names and locations for libraries?

      --
      I am trolling
    12. Re:Package management by Bloater · · Score: 1

      > We'd like that to be true, but in reality there probably isn't a single version of Linux that is not vulnerable to a root exploit from an unprivileged process.

      There's a big difference between a system that's vulnerable due to a bug, and one that's vulnerable by design. Primarily, the one that's vulnerable by design has to stay vulnerable (since everyday stuff breaks if you fix it), the one with bugs can be fixed and then attackers have to find a new vector.

    13. Re:Package management by runderwo · · Score: 1
      And all you need to do is make your system LSB compliant and then you can install any LSB-compliant package on it.
      No. A package needs to be built against the same versions of shared libraries that are on the target system or breakage will occur. This is what leads to vendors having to ship 20 different RPMs for a single application.
      How does autopackage handle things like different names and locations for libraries?
      Since the distribution provides autopackage itself, I would presume that the distribution packagers would know how to configure autopackage to build packages compatible with the distribution. But I must confess I don't really understand what you are asking.
    14. Re:Package management by runderwo · · Score: 1
      There were several root exploits as late as 2.6.10. That is a hell of a lot of vulnerable kernels out there. And as soon as another one is found, it starts all over again.

      Bluetooth socket exploit
      LSM exploit
      uselib() exploit
      stack growth exploit

    15. Re:Package management by m50d · · Score: 1
      No. A package needs to be built against the same versions of shared libraries that are on the target system or breakage will occur. This is what leads to vendors having to ship 20 different RPMs for a single application.

      And that's why the LSB standardises on which shared libraries are available and where they will be located, as well as what changes can occur to them. If the distributions are LSB-compliant, vendors don't have to worry about it.

      Since the distribution provides autopackage itself, I would presume that the distribution packagers would know how to configure autopackage to build packages compatible with the distribution. But I must confess I don't really understand what you are asking.

      I'm asking how autopackage handles the problem of different names, versions and locations for shared libraries.

      --
      I am trolling
    16. Re:Package management by m50d · · Score: 1
      There were several root exploits as late as 2.6.10. That is a hell of a lot of vulnerable kernels out there.

      Only one of those you list would have affected my system, I'd forgotten about the uselib() one but that's all. I think it's far from given that a typical cracker/script kiddie/virus writer would be able to get root on a typical system, and as soon as the exploit became known it would be fixed, meaning the malware would stop affecting any patched systems which hadn't already been broken into and wouldn't spread/be used much further. Wheras there's no way to to patch to fix a script run as root having root privilidges.

      --
      I am trolling
    17. Re:Package management by runderwo · · Score: 1
      And that's why the LSB standardises on which shared libraries are available and where they will be located, as well as what changes can occur to them.
      What? Maybe for core libraries like libc (see section II and III), but it most certainly does not help you with anything further than core libraries. Example: one system has a c102 version of QT3 and another has a version compiled with an older C++ compiler. Yes, the vendor does have to worry about this and ship a separate application for the two distributions.
      Applications that are coded to the LSB Written Specification have taken the first step to becoming binary compatible among the set of LSB-branded systems. By coding to the specification, the application is limited to using only the following system libraries: libc, libdl, libm, libutil, libcrypt, libz, libpthread, libncurses, libX11, libXext, LibXt, libICE, libSM, and libGL. If an application cannot limit itself to the interfaces of the libraries previously listed, thento minimize runtime errorsthe application must either bundle the nonspecified library as part of the application, or it must statically link the library to the application. However, the libraries themselves must be LSB-compliant by using only the interfaces of the libraries listed in the previous paragraph.
      As for your last question, what exactly does autopackage have to "handle" regarding shared libraries (unless you are building a shared library package)?
    18. Re:Package management by runderwo · · Score: 1
      I agree with you regarding the likelihood of such an exploit, but my thesis still stands: the source of the software must be trusted to ensure security. So far, a Linux system secure against hostile user code does not exist because it hasn't been proven to exist, and because there is a sufficient body of evidence to show that no amount of claiming Linux is secure will make it secure. In the realm of installing software, this means you are forced to trust the program itself due to privilege escalation, just as you would have to trust maintainer scripts that are executed as root.

      Maintainer scripts are extremely useful to keeping a package in a working state, and throwing them out as a precaution when there are plenty of holes to be found elsewhere is a bad idea. Note that I do not believe maintainer scripts should be run without requiring the administrator to manually trust the signed source of the package if the source has not been trusted before. Also, there should be a way to revoke trust if the packager has had their key compromised. And hey, if you're really paranoid, extract the scripts and check them out before installing the package. Can't really do that with the binary - how do you know what the source *really* was?

    19. Re:Package management by m50d · · Score: 1
      Yes, the vendor does have to worry about this and ship a separate application for the two distributions.

      Read what you quoted just after this: "If an application cannot limit itself to the interfaces of the libraries previously listed, thento minimize runtime errorsthe application must either bundle the nonspecified library as part of the application, or it must statically link the library to the application." If they build their package the LSB way, it will work on any LSB distro. That's the whole point.

      As for your last question, what exactly does autopackage have to "handle" regarding shared libraries (unless you are building a shared library package)?

      I'm asking what autopackage does about the problems you're listing, "Example: one system has a c102 version of QT3 and another has a version compiled with an older C++ compiler."

      --
      I am trolling
    20. Re:Package management by m50d · · Score: 1
      So far, a Linux system secure against hostile user code does not exist because it hasn't been proven to exist, and because there is a sufficient body of evidence to show that no amount of claiming Linux is secure will make it secure.

      You're treating security as a binary thing here. Yes, a Linux system isn't absolutely secure when faced with hostile user code, but it is more secure than when faced with hostile root code.

      In the realm of installing software, this means you are forced to trust the program itself due to privilege escalation, just as you would have to trust maintainer scripts that are executed as root.

      Yes, you have to trust it, but you don't have to trust it absolutely. You need to trust code and scripts more to run them as root than as a user since it's easier to cause trouble when running as root. Just like I have friends I trust enough to give user accounts but not root access on my box. Yes, there's a certain amount of trust needed to grant user access, but not as much as for root.

      Maintainer scripts are extremely useful to keeping a package in a working state, and throwing them out as a precaution when there are plenty of holes to be found elsewhere is a bad idea.

      There aren't as easy holes anywhere else, or at least there shouldn't be.

      Note that I do not believe maintainer scripts should be run without requiring the administrator to manually trust the signed source of the package if the source has not been trusted before.

      Certainly, but that still doesn't mean you should trust the maintainer scripts absolutely even after verifying. Never rely on a single layer of security.

      And hey, if you're really paranoid, extract the scripts and check them out before installing the package. Can't really do that with the binary - how do you know what the source *really* was?

      Disassemble it and check the assembler. Yes, it's a bit harder, unless the scripts are written in perl, but you can hide things in any language if you're good enough. There is no way to be absolutely secure, scripts and programs can never be absolutely trustworthy, so anything which makes them less able to exploit you is a good thing, and worth doing unless the cost in terms of inconvenience etc. outweighs the security increase.

      --
      I am trolling
    21. Re:Package management by runderwo · · Score: 1
      We're just going to have to disagree on the security issue. If I know most systems running my software will have a Linux 2.6 kernel and that a vulnerability exists that has only been patched recently, I am going to be able to get root on most of them no matter who runs the script. This scenario has been constant throughout the history of Linux. Just at the time a previous exploit was finally becoming ancient history, a new vulnerability is found, so the window of opportunity for privilege escalation exploits never closes. All that changes is the exact mechanism. The author and the distribution source of the software MUST be trusted in order for security to work in any case.
      Disassemble it and check the assembler. Yes, it's a bit harder,
      Auditing a script and auditing a deadlist are not even on the same order of magnitude of difficulty.
  5. So Redhat doing it ... by oxfletch · · Score: 0

    ... apart from Ingo

    1. Re:So Redhat doing it ... by Anonymous Coward · · Score: 0

      I think you meant Ulrich.

  6. LSB Website by Grey_14 · · Score: 5, Informative

    Why doesn't he blurb link to the LSB website at all? it's here Anyway's.

    1. Re:LSB Website by Rogerborg · · Score: 0, Offtopic

      Who owns Slashdot? Who owns news.com? Who pays the wages of the Slashdot... 'editors'?

      --
      If you were blocking sigs, you wouldn't have to read this.
  7. timing issue by hey · · Score: 1

    Whats the timing issue mentioned in TFA?

    1. Re:timing issue by fimbulvetr · · Score: 3, Informative

      Check the story from a couple days ago:

      http://linux.slashdot.org/article.pl?sid=05/09/19/ 1128201&tid=156&tid=163&tid=8&tid=106

      Basically, Ulrich Drepper, maintainer of glibc was complaining about how the LSB certification is broken because it's tests are poorly coded and introduce race conditions when ran on fast (read: maybe 700Mhz+ processors) SMP machines.

      Here's a direct link to the article:
      http://www.livejournal.com/users/udrepper/8511.htm l

  8. WOW by TampaDeveloper · · Score: 3, Insightful

    Wow. I'm very happy. LSB might actually make Linux useful for those of us trying to make a living off of software development...

    1. Re:WOW by fluffywuffy · · Score: 0

      People like the The Korean virus writers!! :-)

    2. Re:WOW by Miniluv · · Score: 4, Interesting

      Don't get your hopes up. While the LSB appears like a very useful standard, as many have noted there are some real holes, and the test suite is by all accounts utterly useless. Further, there's not as tight of control of the testing so it appears at least some vendors are doing bizarre things to be compliant without waivers, despite tests that don't run in real world situations.
      One example that Ulrich Drepper of RedHat pointed out is the thread test, which won't run on an SMP box. The LSB people's response? Run it on a slow uniprocessor. What's the point of this again?

    3. Re:WOW by TampaDeveloper · · Score: 1

      That's too bad. Hopefully the vendors themselves will realize the importance, even if just to promote their own distributions, and send in additional intellectual muscle. Until then,... what? A bad standard is better than no standard? I can't decide. I think bad standard is better than none. I'm not sure why the world is getting dumber. Maybe its just the United States..... Maybe we've got a food-culprit... Time to start keeping better track of those preservatives and sugar substitutes.

    4. Re:WOW by Miniluv · · Score: 4, Interesting

      I'm torn on whether a bad standard is actually better than none. I don't think the problems lie so much in the LSBv3 standard itself, as in the poor management of the standard that such a young standards body is having.
      RedHat is really the company which needs to drive this standard, and while so far they've been doing a lot to do so, its not really in their best competitive interests. Consider that all the major "enterprise" products that folks would want on Linux (WebSphere, Oracle, WebLogic, etc) all specify RedHat as their supported distro.
      I think we need to heap scorn on the crappy test suite now, to try and force them to clean up their act before they engender too much negative press and reputation. Once we hit a certain point where the negative reputation builds up, the standard will be doomed forever.

    5. Re:WOW by TampaDeveloper · · Score: 2, Insightful

      I certainly understand why RedHat would see it as a conflict of interest. But I think they need to start thinking about the viability of the Linux community as a whole. There are two MAJOR competitors just now coming up to speed; OpenSolaris and OSX for x86. Then theirs OpenBSD. OpenBSD moves slower than Linux because nobody likes to sit around waiting for quality, but in the Unix race, quality seems to win in the long-haul. So if the leaders in the Linux community can't wrangle things together, I think theres a good chance were just going to see it diverge into obscurity.

    6. Re:WOW by TampaDeveloper · · Score: 1

      OMG, I just thought something horrible. Could you imagine the horror of having to endure Ballmer's "told you so" speech?

    7. Re:WOW by syousef · · Score: 2, Interesting

      A bad standard will ensure everyone suffers and everyone does things equally poorly.

      I'd rather no standard. People are then not pressured into doing stupid things. Eventually the software people judge to be better prevails and becomes a pseudo-standard. If nothing's significantly better than anything else out there I'd still rather we were forced to deal with the headache of incompatibility than have everyone use a system that is bad and will eventually die.

      --
      These posts express my own personal views, not those of my employer
  9. LSB by gustgr · · Score: 5, Funny

    The article gets funnier when you read LSB as Least Significant Bit.

    1. Re:LSB by plsander · · Score: 1

      My first thought was Lower Sideband.

  10. Release notes by Spy+der+Mann · · Score: 2, Informative

    Here are the LSB 3.0 Release notes. I'd appreciate it if somebody explained if there is a significant or revolution or something. Thank you.

  11. Whose standard? by anupamsr · · Score: 1

    Are these four distribution releasing this as a standard or only these four have agreed to follow it?

    Because in former case, it will never be standard in the first place. And in the latter, well, how are we going to ensure it is followed by others too?

    --
    I forgot to be anonymous.
    1. Re:Whose standard? by LnxAddct · · Score: 3, Insightful

      Well considering that Red Hat, Fedora, Novell, and Debian together hold about 3.5 million servers according to netcraft (as of last march), those are the only players that really matter. Red Hat has about 1.8 million, Fedora: 400,000 , Novell: 400,000 and Debian around 800,000. I haven't read the report in a while but at the time Fedora was expanding at 120% every few months, where as the next fastest distro (I think it was gentoo with 60,000) was growing at 40% over the same time, and all the other distros were much lower than that. I would assume that as a result of Fedora's fast growth rate that Fedora's share is closer to Debian's now. Regardless, after those 4 distros, the next largest was Mandrake (iirc) with around 70,000 active servers. As you can see, those 4 distros(Red Hat, Fedora, Novell, & Debian) are all that really matter and if they all agree on the standard, then it is the standard.
      Regards,
      Steve

    2. Re:Whose standard? by Anonymous Coward · · Score: 2, Informative

      I think this page might be of interest to you.

    3. Re:Whose standard? by jusdisgi · · Score: 1

      Not all Linux computers are webservers.

      --
      Given a choice between free speech and free beer, most people will take the beer.
  12. Like it or not ... by b3x · · Score: 4, Insightful

    This sort of thing is a necessity. With the variety of Distros and each having its own idea of where things should be, it leads to a lot of unecessary confusion. Regardless of whether the confusion is legitimate or slightly hyped by bullet points in paid research docs, it exists.

    1. Re:Like it or not ... by Skapare · · Score: 1

      Why does Linux even needs its own set of standards? Aren't the standards of UNIX in general good enough? I've developed programs by simply doing so carefully and smartly, that work fine on Linux, BSD, and several other flavors of UNIX. And in some cases, people have reported they work even on Windows (which I had made not effort to support). I think maybe the biggest area of confusion is software developers that just don't know how to write portable code.

      --
      now we need to go OSS in diesel cars
    2. Re:Like it or not ... by cybercobra · · Score: 1

      That sounds more like the FHS than the LSB.
      The FHS, unlike the LSB, is a decent standard.
      The LSB needs a major overhaul.

  13. I'm impressed by beforewisdom · · Score: 3, Insightful

    I'm impressed that Red Hat has signed on.

    Along with 2 other of the more established distros being onboard this standard has a chance.

  14. do they care? by newr00tic · · Score: 3, Interesting

    I mean, do software developers usually keep to this standard, or is it more like them cutting some slack due to numerous distros not adhering to it?

    What if those releasing the libs/support files (QT/GTK2, etc.) _only_ allowed you to use them for free, _IF_ the end product adhered to LSB specs.? --It'd force developers to be less sloppy, and some form of unity might come sooner than expected..

    Yes, an arrogant idea, but just read it as an "what-if" -kind of thing.

    --
    A horse can't be sick, you know, even if he wants to.
  15. 64bit status? by gr8_phk · · Score: 4, Interesting

    I know the debian port for AMD64 decided to make the 64bit arch a first class citizen. i.e. there is a /lib directory. Fedora OTOH uses a /lib64 directory. This is like saying there is something special about 64bit libraries on a 64bit arch. Does the new LSB specify how this should be handled? Who will have to change, debian or Red Hat? I run Fedora and am disappointed to have a /lib64 full of stuff and /lib that is almost empty. Thoughts on this?

    1. Re:64bit status? by MobyDisk · · Score: 2, Interesting

      rpm supports multiple architectures out of the box, and knows how to install them to the proper location. Apt does not. This is actually very frustrating because as a Fedora users, I prefer using apt to yum. But for Debian users, you aren't supposed to even be able to have 64-bit and 32-bit binaries co-existing on one system.

      This article on FC4 had some interesting information.

    2. Re:64bit status? by Xarius · · Score: 1

      Where libraries are on a linux system should not be handled by each individual application, just move all the /lib64 ones to /lib, and remove /lib64 from /etc/ld.so.conf. As far as I know everything should still work, unless Fedora does something queer with libraries.

      P.S. don't forget to run ldconfig ;)

      --
      C17H21NO4
    3. Re:64bit status? by hackstraw · · Score: 1

      The LSB officially supports at least ia32-64 and ia64 for 64bit architectures. Here is some info on multiple architectures: http://www.linuxbase.org.nyud.net:8090/LSBWiki/Mul tiArch.

    4. Re:64bit status? by dondelelcaro · · Score: 1
      But for Debian users, you aren't supposed to even be able to have 64-bit and 32-bit binaries co-existing on one system.
      The 64 bit Sparc port must be an example of my overactive imagination then... it's been running 32 bit userland with specific 64 bit programs for quite some time.

      --
      http://www.donarmstrong.com
    5. Re:64bit status? by MobyDisk · · Score: 1
      Debian SPARC is not a general-purpose 64-bit/32-bit mixed architecture. It is a 64-bit kernel that runs 32-bit applications. There is some limited incomplete support for 64-bit applications. You can't just install a 64-bit .package and a 32-bit package side-by-side on that system and expect it to work.

      Fedora Core supports having 32-bit applications/libraries and 64-applications/libraries running side-by-side simultaneously. The packaging system and the linker know the x86_64 packages from the i386 packages.

      From your link:

      The Debian SPARC 64 porting effort is not currently conceived as a full porting effort...In fact, there is really no point in having all applications running in 64-bit mode. Full 64-bit mode involves a significant overhead (memory and disk size) with often no benefit. Some applications really can benefit from being in 64-bit mode, and that is the purpose of this porting effort.
  16. I'm starting to wonder, too. by Anonymous Coward · · Score: 0

    This can't be the real TMM. There's only one line of unnecessary whitespace.

    ...and the post was actually pretty funny and it didn't include that f**king anime smile!

    To GP: Who are you and what have you done with the real TMM?!

  17. Excellent by miffo.swe · · Score: 1

    Since many distros is based on RedHat and Debian they too will inherit the base system and be very similar to LSB of not entierly.

    --
    HTTP/1.1 400
  18. Ubuntu by saterdaies · · Score: 2, Interesting

    It would be nice if Ubuntu committed to it seeing as though they've become the 10,000 pound gorilla of Linux distributions.

    Note: this isn't anti-Ubuntu. I run Ubuntu.

    1. Re:Ubuntu by Dan+Ost · · Score: 1

      Won't Ubuntu inherit compliance from Debian?

      --

      *sigh* back to work...
    2. Re:Ubuntu by Hosiah · · Score: 1
      Um, yeah, the 10,000 pound gorilla of Linux distributions of the year.

      I seen 'em come and go. Last year this time, if you weren't running Gentoo, you weren't "l33t".

  19. Mandates RPM by Anonymous Coward · · Score: 3, Insightful

    I don't see how a standard that uses RPM as the mandatory package format will ever gain enough consensus to be successful.

    What kind of a standard is this anyway? For example:

    Applications are also encouraged to uninstall cleanly.

    Um, that's great. Where's the definition of "cleanly"? Where's the rationale? Where's the implementation notes? This thing reads like a few people got together and jotted down a few notes on what they'd like to see. This ain't a specification. Sure, they go into great detail about the format of the RPM file - but that's already an established format that they don't need to explain.

  20. Gentoo won't as long as it still uses GCC 3.3.x by theurge14 · · Score: 1

    3.4.x still marked as an unstable ebuild last time I checked.

    1. Re:Gentoo won't as long as it still uses GCC 3.3.x by Dan+Ost · · Score: 1

      Why is 3.4.x masked on x86? I've been running it for some time now on a test
      machine and have noticed no problems at all.

      --

      *sigh* back to work...
    2. Re:Gentoo won't as long as it still uses GCC 3.3.x by theurge14 · · Score: 1

      I can't answer that, but I can say that since Gentoo is not really a distro as it is a "DIY Linux Kit", I'd just unmask 3.4 in portage.keywords and recompile everything. :)

    3. Re:Gentoo won't as long as it still uses GCC 3.3.x by manitoulinnerd · · Score: 1

      On amd64 I am using 3.4.4 as I was a month ago on my x86 system. Maybe you need to upgrade your profile.

      --
      Burn Bright or Fade Away
    4. Re:Gentoo won't as long as it still uses GCC 3.3.x by theurge14 · · Score: 1

      While 3.4.1.r1 and 3.4.3 are both stable on amd64, on x86 only 3.3.6 is marked as stable.

      I'm not about to unmask any unstable packages on my server anytime soon.

  21. GREAT MOVE by the "Penguin Crowd" imo... apk by Anonymous Coward · · Score: 1, Interesting

    Now, THIS move by the "Penguin People"? A smart one...

    Why, imo?

    WELL, it will hopefully STOP the "fragmentation @ binaries levels" that UNIX (the predecessor, inferior currently imo to Linux in many ways) encountered!

    (Which is, imo, the ONLY real reason we are not all running some form of UNIX on our PC's today instead of Windows, Mac, or Linux as OS' etc./et all).

    Kudos on such things happening to the "Penguin crowd", because it's needed imo. Linux 2.6x core is IMPRESSIVE (most impressive) & KDE rocks too imo.

    Would be a shame to see that fall apart between Linux versions!

    APK

    P.S.=> Next, is standards as much as possible between Linux & Win32 (if not MacOS X) so they interoperate on MANY levels (document formats, webpage standards, heck even binary level compatibility which tools like Delphi/Kylix, C/C++, & mostly imo, RealBasic 2005) will be of GREAT aid/help in doing...

    E.G.-> Imagine writing code ONCE, & running that same sourcecode as an executable anywhere!

    (AND, not using interpretation layers like the Java runtimes, VB runtimes, MSVC++ runtimes as intermediaries which to be blunt about it, slow things down in message-passing overheads & translations on Win32 alone)!

    Speed & binary compatibility IS possible, if everyone acts together on it imo... this is the future, & what ought to be the "thinking behind 21st century personal computing"... apk

    1. Re:GREAT MOVE by the "Penguin Crowd" imo... apk by Anonymous Coward · · Score: 0

      IMO when you're writing a comment people can expect that it represents your opinion. therefore IMO stating IMO before or after or within every single thing you say is IMO both unnecessary and annoying as hell. IMO

    2. Re:GREAT MOVE by the "Penguin Crowd" imo... apk by Anonymous Coward · · Score: 0

      "IMO when you're writing a comment people can expect that it represents your opinion. therefore IMO stating IMO before or after or within every single thing you say is IMO both unnecessary and annoying as hell. IMO"

      Who cares what you think first of all.

      Secondly, it appears you speak for all of slashdot I take it?

      Simplest point I made was this:

      Don't like what it said?? Don't read it.

      Again:

      "aaaaaaaRRRRRRGGGGGGGGGGHHHHHHHH (Score:0)
      by Anonymous Coward on Wednesday September 21, @12:24PM (#13614490)
      http://dictionary.reference.com/search?q=paragraph [reference.com]"

      4 things to say to that reply to my posting:

      1.) If you cannot draw the meaning of someone's words via the context in which they are used, YOU have the problem, not myself.

      2.) I don't need YOUR opinion, ok? Just those who have technical commentary on it!

      (& not english 101 b.s. technical issues, but on the technical issues in Comp. Sci. it may have in it... that is ALL I personally am/was interested in)

      WELL, that, or the moderators' opinions on it (which got a "+1" interesting rating).

      3.) Additionally, IF you do NOT like what I write? Don't read it - pretty simple!

      & lastly

      4.) Care to somehow PROVE you have a PhD in English since picking @ others' writing style, spelling &/or grammar is your alleged forte?

      (No, or not possible on YOUR end to produce your evidence of the possession of expertise in said areas, to the last one? I thought as much... but, my first 3 points negate that anyhow!)

      * :)

      APK

      P.S.=> Above all? Grow up! And, by the by?? Go to hell... apk

  22. Standards are good... by mmport80 · · Score: 1

    ... but they can stifle innovation. I heard somewhere that KDE had problems with freedesktop.org, cos they wanted to do some fairly sensible things - but it wasn't in the standard... Maybe someone else can fill in details...

    1. Re:Standards are good... by NineNine · · Score: 1

      But the current amount of "innovation" makes Linux unusable for many application developers and users without some kind of standards.

  23. Here's why LSB 3.0 Matters by sjvn · · Score: 4, Interesting

    And, I might mention, I think it matters A Lot.

    http://www.eweek.com/article2/0,1895,1861272,00.as p

    From where I sit, Red Hat's Drepper

    http://linux.slashdot.org/article.pl?sid=05/09/19/ 1128201

    wants to throw the baby of open standardization out with the bathwater of LSB standardization testing, which could still stand a lot of improvement.

    With open standardization, Linux could go the way of Intel Unix--shudder!

    Steven

  24. Not just standards by TheSkepticalOptimist · · Score: 0, Redundant

    How about unification? ONE linux distro to rule them all! Then Bill Gates will have to find a volcanoe to toss it into if he ever hopes Windows to compete against Linux again.

    As long as there are 20+ different distributions of Linux and multiple agencies claiming they are defining Linux standards, Linux will never compete outright against Windows.

    --
    I haven't thought of anything clever to put here, but then again most of you haven't either.
    1. Re:Not just standards by delire · · Score: 1


      Penguins always come in numbers. Get used to it.

  25. aaaaaaaRRRRRRGGGGGGGGGGHHHHHHHH by Anonymous Coward · · Score: 1, Funny
    1. Re:aaaaaaaRRRRRRGGGGGGGGGGHHHHHHHH by Anonymous Coward · · Score: 1, Funny

      "aaaaaaaRRRRRRGGGGGGGGGGHHHHHHHH (Score:0)
      by Anonymous Coward on Wednesday September 21, @12:24PM (#13614490)
      http://dictionary.reference.com/search?q=paragraph "

      4 things to say to that reply to my posting:

      1.) Go to hell first of all, if you cannot draw the meaning of someone's words via the context in which they are used, YOU have the problem, not myself.

      2.) I don't need YOUR opinion, ok? Just those who have technical commentary on it, or the moderators' opinions on it (which got a "+1" interesting rating).

      3.) Additionally, IF you do NOT like what I write? Don't read it - pretty simple!

      & lastly

      4.) Care to somehow PROVE you have a PhD in English?

      (No, or not possible on YOUR end, to the last one? I thought as much...)

      * :)

      APK

    2. Re:aaaaaaaRRRRRRGGGGGGGGGGHHHHHHHH by Anonymous Coward · · Score: 0

      Me fail English? That's un-possible!

    3. Re:aaaaaaaRRRRRRGGGGGGGGGGHHHHHHHH by Anonymous Coward · · Score: 0

      You be an a-hole? Very possible

  26. Standards. by Lux_Nova · · Score: 0

    Seems ironic that a 'open standards' site would not be W3C compliant.

    http://www.linuxbase.org/

    Let's see.. 1 error, 26 warnings! woo-

  27. Re:Standards (Definitions) by ---- · · Score: 1

    For those of us not in the latin, scientific, legal, or political professions, here's the descriptions.

    De facto: is a Latin expression that means "in fact" or "in practice".

    De jure: is a Latin expression that means "based on law".

  28. This is important for commercial apps, but... by MarkWatson · · Score: 1

    ... it seems like most expereinced Linux users prefer to get source distributions, right?

    After migrating from Slackware -> Caldera -> SuSE, I am now a happy Ubuntu user.

    Really, except for a few developer tools, just about everything that I need is in the main distribution, and can be trivially installed.

    I actually have a small point here: for developers and experienced Linux users, running ./configure ; make ; sudo make install is no problem, so the exact placement of deployed application files seems to not matter too much. ./configure gets that right for you.

    For novice users, a good distribution like Ubuntu or SuSE is likely to have what people need with OOo, Firefox, a few games, etc.

    Except for IntelliJ, it is difficult for me to imagine what other commercial software I would every want for Linux. I do buy programs for OS X and Windows, but I usually use Linux for getting work done, and for me not much is required except for development tools and a word processor. It would be interesting to hear from someone at JetBrains about how much effort it is packaging IntelliJ for various Linux distros.

    ** Healthier coding: http://cjskitchen.com/

    1. Re:This is important for commercial apps, but... by Anonymous Coward · · Score: 0

      I use Mathematica and IDL. More commercial games would be pretty nice too. You'll appreciate that Sun's JRE is commercial software.

    2. Re:This is important for commercial apps, but... by Anonymous Coward · · Score: 0

      Except for IntelliJ, it is difficult for me to imagine what other commercial software I would every want for Linux.

      For me it is Autocad, and I don't mean any old drafting package but one that has the functionality that extends to specific industries. As a Surveyor I use Autocad/Autocad Land desktop and also CivilCad.
      I've yet to find anything that matches up, and as a result am still using a dual boot setup.

      Once such an app becomes available (Wouldn't mind paying the same as it costs for the Windoze version) then it's by by MS.

  29. yes it depends by Anonymous Coward · · Score: 0

    but if you have a decent representation of the more popular distros adopting it, then it becomes a defacto standard for those people. Just in the DCCA you have a decent representation, now add in redhat and suse? You are starting to hit the bulk of what people are running. The various other hundreds of distros have relatively smaller numbers of full time adherents.

    I think the LSB is a good idea and should be followed more.

  30. Re:Standards (Definitions) by steveness · · Score: 1

    What most people mean, though is the French "d' jour" meaning "of the day". for example, "This is my random act of snarkiness d' jour."

  31. Tainted... by halleluja · · Score: 1
    After Ulrich's recent criticisms I find it hard to value this update.

    Besides, I like the Gentoo standard better.

  32. C++ Support? by bigjoeystud · · Score: 1

    I tried using LSB gcc to compile our applications and the 3.0.3-1 packages could not handle C++ code yet. I would get weird header errors on anything that included iostream. This seemed bizarre to me. Has anyone else actually tried using it? I'd be all for it if it actually worked...

  33. It doesn't matter how united it is! by hvatum · · Score: 0

    Linux united and on the desktop?
    Why?
    Why should I, a basic user with a home network, 2 children, 4 systems switch to Linux?

    I have just upgraded 2 of the 4 systems with Dell 2400 systems which are nice systems for $299.99, include a printer, Windows XP and basic necessities and as soon as you uninstall Symantec Internet Security and replace with antivir/spybot/sygate, all FREE, becomes quite a very nice system.

    So now tell me why I should move to Linux?

    Openoffice?

    I can get that FREE for Windows.
    Thanks but no thanks, and evidently I am not alone because let's face it, MSOffice cost a lot of money and one would think a free alternative would be extremely popular. The problem is Openoffice is NOT AN ALTERNATIVE. It is a wannabe that is slow, bloated (even more than MSOffice) and riddled with bugs and that is why it has not put MSOffice on the back burner.

    Gimp?

    I can get that FREE for Windows.

    Thanks but no thanks because Adobe Photoshop that came with my scanner is much better due to an interface that is easy to use.

    How about using my digital camera, a Polaroid.
    Sure it is recognized by Linux, AS A STORAGE DEVICE, which means everything I want to do takes 4 different programs and 10 steps rather
    than one simple "plug it in" which is all I do with Windows. My photo editor opens, my albums are right there, I can easily download and erase photos from the camera and so forth and it syncs perfectly.

    Speaking of syncing, how does one sync my Motorola E815 phone with Outlook, Bitpim and other tools that allow mp3/video/pda/graphics uploads and downloads with Linux?
    Can't be done.
    Can't be done with LG phones either.

    What about CD burning?

    I work for a company that does video presentations and we must send out demos and one offs to our clients. We use Plextor drives because they include Plextools which allows us to graphically query the drives to see error counts, media problems and so forth BEFORE they end up un our clients hands.

    Sorry, but this does not work with Linux.

    Linux is a mess.
    It's great if you like figuring things out and marching backwards when everyone else is going forwards. It's great if you enjoy trying to unite fifty different projects all lead by egomaniacs who refuse to sacrifice any glory or control for the sake of everyone else.

    So Sorry.
    No Linux for me, and it appears I am in the majority.

    --
    Netbooks, they come with Linux or a $3 copy of Windows. Either way, Microsoft loses.
    1. Re:It doesn't matter how united it is! by Jason+Hildebrand · · Score: 1
      So now tell me why I should move to Linux?

      You must be new here.

    2. Re:It doesn't matter how united it is! by pandrijeczko · · Score: 1
      Sounds like a troll but I'll have a little bite...

      Why should I, a basic user with a home network, 2 children, 4 systems switch to Linux?

      You shouldn't. You should use software tools that let you get the job you want to do done as quickly as possible... if that's MS Office, then so be it.

      However, you may want to just stop and consider some of the possible implications of what you are doing.

      Microsoft is rapidly coming to the conclusion that there is just *not enough* money to be made from just *selling* software. Therefore, they (and other commercial software entities) are looking at other ways of making money.

      Firstly, they'll do their damnedest to keep you in an endless upgrade cycle. So they'll "break" your old software and hardware as much as they can to force you to upgrade constantly, thus generating more money.

      Secondly, and preferably, Microsoft do not want you to *own* anything - they want you to *rent* it because then they have a nice monthly direct debit from your bank account as a nice guaranteed & regular source of income. The same is true of the music and movie companies who also want that nice rental income. Consequently, all parties want DRM badly so you end up paying more for products that ultimately give you less freedom than you enjoyed when those products were free of DRM and cheaper. They'll use the piracy argument as their excuse to implement this but the technology ultimately restricts the rights of the proper user, not the pirates. Plus the movie and music companies never seem to answer the questions as to why DVD and CD sales are *up* despite the effects of piracy.

      Thirdly, MS Office. In my experience, 90%+ of home users have pirated versions of MS Office because they borrowed CDs from work to install it. But would those same users be so vocal about using MS Office over OpenOffice if they *had* to pay several hundred dollars/Euros/pounds for it. I think not...

      Would you be so "anti" GIMP if you hadn't got Photoshop free with your printer and had to pay for it?

      Fourthly, Open Source software is *not* free. It costs you no money but it puts a lot of responsibility in *your* hands. That means, to use it effectively, you have to learn how it works, ask questions and email software developers suggesting the features you want to see. Only then will it get the ease of use and functionality you want. If you're not prepared to do that then don't swap, it's that simple.

      Linux is a mess.

      Sorry, but how do you *know* this? Quite clearly, it's not so bad a "mess, otherwise the millions of people using it currently would presumably not be doing so. Sure, it has problems - but, in the smae vein, whilst I find Windows 2000 quite stable and usable, I consider Windows XP a "mess" due to the amount of bloat it contains and a user interface designed to sacrifice CPU cycles just for eye candy.

      It's your choice whether to switch or not - in fact, Linux is *so* "willing to please", you don't actually need to "switch" - you can just sacrifice a few gigs of hard disk space and dual install it just to play with it at your leisure. And this will be an ideal opportunity for your kids to get a little more computer literate with exposure to two OSes, not just one...

      So go ahead and use what software you want - after all, that's the idea of choice... but just be aware of what you *might* be sacrificing as a result of that choice, that's all I'm trying to say.

      --
      Gentoo Linux - another day, another USE flag.
  34. Legacy Standard Base by Trejkaz · · Score: 1

    I agree that it should be the applications which have to conform, not the distros.

    For starters, applications should not assume a certain directory layout, and should just install to the appropriate places based on the distro. Yes, this means that package managers might need to be slightly smarter than they currently are. But existing source-based installation already works for the majority of packages.

    Case in point: GoboLinux. Now, those guys have introduced a more intuitive filesystem hierarchy that actually works and makes sense at the same time (which is rare.) However, Linux Standard Base, which depends on the Filesystem Hierarchy Standard, outright prohibits their directory layout.

    So... let's fast forward to when LSB is in widespread use. Application vendors start assuming that LSB is all they need to support "Linux". Distros who won't have a bar of the shitty legacy directory layout we've had to endure for decades will basically be punished for being forward-thinking.

    So yeah, LSB sounds real great.

    --
    Karma: It's all a bunch of tree-huggin' hippy crap!