Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Red Hat Software Businesses

Red Hat to ignore LSB? 55

warpeightbot writes "CNN.com is carrying an IDG article expressing concern that Red Hat may not support the Linux Standards Base for various reasons. Sounds like FUD to me, but if it's on CNN, it has to be dealt with one way or the other... " The article itself is like the 90th Red Hat conspiracy piece I've seen in the mainstream now. Its crossed the line into amusing now for me anyway.
This discussion has been archived. No new comments can be posted.

Red Hat to ignore LSB?

Comments Filter:
  • "Its crossed the line into amusing now for me anyway"....and as such, does it merit a slashdot posting? I think probably not, but feel free people, thrash out the same old material - just for the heck of it.

    --Remove SPAM from my address to mail me
  • This is the new direction of FUD for Linux. Microsoft is not bad, RedHat is. Ugh. The bad thing is that with CNN running it, people will buy into it. Seems like the worst thing we can do about this is to inflate it and lend it creedence. What's needed, seems to me, is a killer response to this such as the Petreley response to Muth's piece.

    What is not needed is a lot of flame or ESR silliness on this one. At least, that's what I think anyway.

  • by Praxxus ( 19048 ) on Saturday March 27, 1999 @09:29AM (#1960172) Homepage
    THAT was different, anyway. Of course, the article was still along the lines of of:

    RH: Yes. We support the LSB. We dig it. We're down with it. Go Linux!!

    IDG: BUT...they might not! And if they don't, thisandthisandthis could happen, and then Linux would suck! Be scared!!!

    Wow. That was stunning journalism, a-yup.

    --
  • In repeated press releases and articles, RedHat has made their LSB position clear. They like the idea, they will support the process (Note that they are LSB members [linuxbase.org]), but they won't commit to complying with the standard until they actually can read a final standard.

    While I would be happier if they committed to complying, I understand their reluctance, and I don't see the big deal. Once the LSB is actually out, we can lambast them if they don't comply. Until then, I think it's safe to assume that they will do the sane thing, and follow standards.
  • He doesn't seem to be. Read the interview at http://www.linuxworld.com
  • I think this article is a reprint from a ZDNET article that ran last week. It might have even been posted on /. before. Anyway, I think we should give Red Hat the benefit of the doubt until they actually do something "bad" -- being quoted out of context by ZDNET isn't a crime.

    TedC

  • by drwiii ( 434 )
    The good thing about Red Hat is that you can make changes and redistribute them as your own distribution. The thing to do would be to make Redhat LSB compliant and redistribute it to the masses. If it's really a popular idea, it'll take off and Redhat will probably take notice.

    Note for people in the Baltimore/Washington area -- Hamboree/Computerfest is this weekend at the Timonium Fairgrounds.. Lots of computer hobbyists there, so there's bound to be some Linux persons wandering around or selling stuff. Plus they have that cool food. LINK [gbhc.org]

  • This article is a good representation of the early stages of the media getting to know the inside scoop on any niche. Things, in general, are all too happy in the Linux community (compared to other players on the field) so when something that smacks even remotely of dissent or conflict, the press prints it and hypes it, thereby making it news.

    They are still working their way into the field and inside scoops are still coming from press releases and strange interpretations of facts. Once the press figures out who's who, and what they are capable of, then the coverage will even out to resemble that of other industry players like Sun and IBM.

    Of course, that's just my opinion...
  • is RH becoming the next M$....who cares anyway, we'll still have another linux distro to choose from and all them are open source, just the way we like.....
  • I was thinking the same idea. Just repackage the GPL stuff to make it LSB compliant.

    Yawn. The FUD is getting thick....

  • by Pudding Yeti ( 9773 ) on Saturday March 27, 1999 @10:08AM (#1960180)
    This is what I said last time this story came up:

    They've figured out that Linux stories attract eyes, so they're going to write about Linux. Enter the other factor, which is what to write about once they've decided that they're going to write. Well, conflict sells. Heck, conflict has been the primary basis of Western (and I mean that in the classic sense) narrative for millenia. We've run through the cycle of "GNOME storms the MS desktop stronghold" and "Big Name Adopters Prove Microsoft is doomed," so the next best thing to do is troll (and I use that in the "gill net fishing" sense) for some other conflict.

    I still maintain that as accurate.

    That doesn't make this FUD. It just makes it sloppy, lazy, reporting from people who believe what they read from anyone who posts a suitably inflammatory comment on Slashdot.

    Heck, just to get nasty about it, I'd submit that if reporters reading this site decided to set their filters up to "2," they'd probably report about this much less.

    How can something be FUD when it's probably plucked in all of its repetitive, paranoid, strident glory straight from the pages of one of the standard bearers of the Linux revolution?

    Don't by the way, try to claim agents of Bill are seeding this story. A quick look back at any story here that's ever reported on a new Red Hat, Debian, or other distro release will indicate that even Microsoft probably doesn't have the cash to pay that many agent provocateurs. Nope. it comes from in the fold, and now we get to wallow in the media-mediated tripe we created.


    ----------
    mphall@cstone.nospam.net

  • by Anonymous Coward
    I don't see how RedHat, or any company, could take over a piece of software that is required by its license to remain available free of charge with source code. I would not be the least bit surprised is Red Hat become the dominant company in the field of selling Linux, but I think that's a far stretch from a takeover.

    All the more power to them. At the moment, what's good for them seems to be good for us and that's what is of primary importance in my opinion.
  • Yes! For now, RedHat puts out a fairly good software product and has done nothing, yet, to bring on so many conspiracy stories. Sure, the RedHat ditro's not FreeBSD (sorry), but it is one of the better general purpose, easier-to-use distros, which accounts for its popularity (which is to say that it fundamentally doesn't resemble MS windows, which is ugly, not fun to use, and, yet, market-dominating). As long as they have a reason to be the market leader, Red Hat shouldn't be blamed for, well, leading the market. It would be a very different story if their distro was inferior to that of their competitors.

    Additionally, RedHat has several viable competitors who have significant market-share themselves. If RedHat drops the ball (on standards, drivers, ease-of-use, etc) SUSE and Caldera (and maybe debian but not really) are right behind them to pick it up and run with it. A stretched analogy to be sure, but, for now, RedHat is still Linux and switching to a distro that meets ones needs better isn't that difficult.


    --Andrew Grossman
    grossdog@dartmouth.edu
  • by Master Switch ( 15115 ) on Saturday March 27, 1999 @10:20AM (#1960184) Homepage
    Red Hat's unwavering support of the GPL, and their strict insistance on applying it to all that they do, leads me to believe that they are not, nor will they ever, try to take "ownership" of the Linux movement. Red Hat has done a fine job, and whether you like to admit it or not, if it wasn't for them, Linux awareness would be two or three years behind where it is today. Red Hat was one of the first vendors to support multiple platforms. They put up the money to help with GNOME, and now also KDE. They fund the development of graphics card drivers, and they are partially responsible for much of the recent Kernel development(Alan Cox). I don't see the other vendors stepping to the plate like this. Don't get me wrong, I like SuSE, SlackWare, Debian, etc... But I am somewhat dissapointed with other vendors willingness to give back to Linux.
  • I had lunch with Debian and Red Hat folks just before the last LSB meeting. The Red Hat person had flown out for the meeting.

    Bruce

  • Take a look at all the discussion about the LSB from inside at http://www.debian.org/Lists-Archives/ [debian.org] down at the bottom of the page. All the LSB work is done open, and in the public eye. I don't see it there.

    Looking at the LSB web site [linuxbase.org] and I see no news of Red Hat falling off the supporters list. I don't see it there.

    So, what is CNN's source? Off to the CNN artical [cnn.com] and I read Red Hat's PRO LSB statements and quotes. I don't see it there.... Oh wait "And other Red Hat officials in recent weeks have referred to standards groups as "overhead." " Ahhh... This is the bad news? Wait a minute.

    Let's see, most Buisnesses call things they have to spend money on "overhead." Not a bad thing, it's simply something needed to function. So, in a sence, it's even like saying Red Hat sees that it NEEDS the LSB to keep it's product (LINUX) alive. Without it, Red Hat would die out because of the lack of community support, and it's users would flock to any of the other dozen Linux choices (and vendors would soon follow).

    So, where is the leaked internal Red Hat memo, where is the source? Where is this comming from? I don't see it. Take ONE WORD, "overhead", out of context, and do a complete "why Red Hat Sucks" spin on one out of context word from a Red Hat statement?

    Bad CNN, Bad Bad Bad..... No table scraps for you tonight, go back to the dog house...

  • by Anonymous Coward
    I think Red Hat should be free to ignore the LSB. I'd rather have a bit more divergence and innovation that constraining all GNU/Linux vendors to follow the same model. I trust Red Hat; they've released everything they wrote under the GPL. If they try to become the next Microsoft, we'll just stop buying their product, and even maintain it seperate of Red Hat (try and say that for SuSE or Caldera). I also don't see any reason why Red Hat would want to diverge from the LSB unless they had a really good reason for doing so.

    I say we leave them alone and see what happens. I don't see how they can reasonably do something wrong.
  • The benifit of what doubt? The whole story read to me like an interview where they asked a bunch of people " What If Red Hat did this?" and they got the answers they wanted to publish.

    I don't doubt for a second that Red Hat will do the Right Thing(tm).

  • FUD = Spreading Fear Uncertianty and Doubt.

    Let's see... To me, I see this whole story as a series of "What if Red Hat Did X?" questions asked to any big names in Linux they could get at in a time frame to write the story.

    Then, they get it ran on CNN?

    I loose respect for CNN in this case. Sorry. I see no REAL evidance at all that Red Hat is doing this, or going to do this. Therefore, it's FUD in my eyes. Something I thought CNN was above.

    I agree that "conflict sells." But to do something that is an overview of the negitive "what if's" that they picked up from places like SlashDot which is (Dare I say this) and insider discussion about Linux, and very casual, is just plain lame.

    All the negitives I have about Slashdot aside, I still respect the fact that it's an OPEN FORUM where a Senior Programer with 30 years of experiance under his belt can get into a flame war about a technical detail with a 14 year old who just bought Red Hat at Best Buy after saving up his lunch money! That is a good thing. It opens eyes, and keeps Linux alive. It's an open window to keep seeing things from a "fresh" point of view.

    But to take this as "a crediable source" for something like a CNN artical, that's FUD, and something I use to thing CNN was above publishing.

  • slackware has always been like that. especially with glibc 2.0.x etc. slow to move, oh well, anyway, it IS SLACKware... patrick v.... has a very nice position: he doesn't really care all THAT much about market share etc. :P
  • (conjecture, and probably won't happen) by using red hat's ever increasing market share and power with the suits' big companies, they may be able to use their new found powers to try to take the standards, implement them, and steer them into their strategy. (that was from the article paraphrased) the problem with this is that red hat's "strategy" doesn't differ from SuSe's stance, Debian's stance, or any other stance. (maybe slight differences like Debian's commitment to GNU/Linux or something like that) their goal is all the same (disconnect your flame throwers before proceeding): create a high-quality, compatible distribution that might be easier to use/powerful/server-focused/desktop-focused. etc.

    this was probably disjointed and discursive, ignore it

  • I'm sure that there are at least several Red Hat employees who read /. What chance of an official word direct from them to us, the masses?

  • I certainly appreciate all the development dollars that Red Hat has put into Linux, and thats one reason I use their distribution. I would like to point out that SuSE has done a lot of work with XFree86 and that the first SMP work done by Alan Cox was funded by Caldera.
  • Slackware is still around? I mean glibc5 is dead... Slackware is aptedly named, I switched off slack long ago. ;)
  • My definition of FUD is just off from yours enough as to make us speak to the same issue on different, but not mutually exclusive, tracks.

    You define FUD as FUD = Spreading Fear Uncertianty and Doubt, I tend to think of "FUD" as going a little further and having a motivational component. Since I'm still relatively new to Slashdot (one year) and Linux culture in general (two years), I did a quick Google search to see where I might have come up with that idea, since I know I didn't come up with it on my own, and came up with this page, [linux-hw.com] which was featured here on Slashdot some time ago. It garnered a lot of comment, some negative. As much as I don't like the rash of attempts to write "scholarly sounding" documents that broke out after The Cathedral & The Bazaar got so much notice, I felt like FUD was pretty clearly summed up, especially since the author went so far as to attribute a source for the term.

    Given that paper, I still maintain that this article is not FUD. It's ignorant, and it spreads the components of FUD by its mere publication, but it lacks a motivational element. Call it manslaughter instead of premeditated murder, I guess.

    I will also continue to maintain that because in some ways Linux represents as much a cultural as technical phenomenon, and to the extent that the democratic, anarchic nature of the phenomenon's base will never settle on having a "ministry of truth" to issue press releases, reporters will tend to catch as catch can when it comes to reporting on this phenomenon.

    You may also choose to note the headline of that item: Linux fans fear Red Hat takeover.

    That's true. And again, I stand by my assertion based on cursory observation of virtually every story about Red Hat that runs here on Slashdot.

    I don't think the openness of Slashdot is bad, either, by the way. But I've been around long enough to know that things that are "good" (free speech) don't always confer goodness in their use (libel, slander, FUD). This story by CNN is most likely an example.
    ----------
    mphall@cstone.nospam.net

  • by BlackHawk ( 15529 ) on Saturday March 27, 1999 @02:37PM (#1960198) Journal
    In reading many of the other comments, I see that there is a decidedly supportive tone directed at both Red Hat and LSB. While this may be the "correct" course of action, let's look at it again, from a fresh perspective, one free from past experience. I can provide that, since I just became acquainted with Linux in the middle of last year, and have not yet been in a position to implement either at home or at work. (All of that changing by June, however. ) As something of a disclaimer, I will state up front that when I type "Linux", I mean the OS which is also referred to as "GNU/Linux" by some. But just Linux is shorter, I'm not such a great typist.

    I've been following the idea of a "standard Linux" with some interest. I don't have the hacking skills that many here have, and while the idea of hacking at the kernel or creating drivers, or apps for Linux is one I hold dear, the reality is that I won't be doing that for a bit yet. No, I'll be using Linux as a user first, and there's where the idea of a standard is appealing. I want apps to work with the distro I choose, without requiring me to restructure parts of the source code first. OK, yeah, that's the user in me talking, but it's also the IS Manager in me. Deploying desktops is tedious enough without contemplating the current state of Linux desktop deployment.

    So the LSB sounds good. It's good in theory, and I feel it'll be good in practice. But for a moment, let's give the benefit of the doubt not to Red Hat nor the LSB, but to "conspiracy", as Taco put it. For the record, no I'm not a believer in the conspiracy, but I like to cover all the angles I can see. I play chess; it's no different.

    Is Red Hat as supportive of the LSB as they seem? Well, it appears so. We've heard from any number of people that they are. But what do they stand to gain or lose with the LSB? There are quotes on record where Red Hat personnel have claimed that standards groups slow down innovation. And Red Hat likes to innovate, to be sure. Referring to standards groups as "overhead" is extremely revealing of the true sentiments of the speaker. After all, with Red Hat being only one member of the LSB, what are the odds that the standard will end up looking exactly like Red Hat? Minimal, at best, meaning that Red Hat will have to rework at least some of its distro to match the new standard. "Rework" always means non-profitable labor, hours spent that are not "billable". And Red Hat is a business. And all for-profit businesses exist to turn a profit, that's a given. Right now, Red Hat (argueably) has the majority market share. Adhering to an LSB created by a committee whose members include some of their competitors will likely result in those competitors making market gains. After all, if you no longer need to have Red Hat to ensure compatibility with certain applications, then why buy it? Support? Well, yes, but with the advent of LinuxCare, that may not be such a selling point. And there will be other "LinuxCare"'s on the horizon. So is it Red Hat's best interest to support the LSB? From a purely business perspective, while the tempo of the game belongs to them, perhaps not. Mind you, out-and-out rejection of the LSB will work against Red Hat as well. So perhaps outer support of the standard is a good idea, while the committee takes alot of time to arrive at that standard. Time for Red Hat to consolidate market position.

    So now, let's flip to the other side. Who stands to gain the most from having the LSB? Well, us, really, since a standard Linux will be easier to write to, add to, etc. But in the short term, having that standard will benefit companies whose distribution is not Red Hat. And I'm going to squarely point a finger at Caldera. I have tested Caldera, back when I was going to run a NetWare class and showcase the OS to my students. I have to say, I chose not to do it, because of the problems I had during the installation and the fact that several very cool apps I wanted to show wouldn't work with the older version of libc OpenLinux 1.3 had. So would Caldera stand to gain from an LSB? Yes, and not just because of the same reasons we would. The LSB will almost certainly incorporate pieces from Caldera. Or at the very least, it will require some pieces to be written from scratch. Either way, those pieces will place Caldera on equal if not superior footing to Red Hat, at least in those areas. This will give them leverage to use in the marketplace, leverage that they would not have had without that standard.

    So is Machiavelli the author of the LSB? No, I don't think so. I like the standard idea. I wish I knew more about Linux, because I'd love to help. but for those of us watching the coming LSB battles... and there will be some, there's no doubt of that... we need to make sure we watch the moves closely. But also watch the players. Sometimes a chance comment will reveal motives they'd prefer were kept hidden.

  • Why would CNN have any interest in FUD'ing Linux. The wants to "sell" news. If you do not think we can just ignore articles like this come up with something more "News" worthy. Second, I think most /. folks know the issues and are not afraid of RH morphing into MS. If the rest of the world thinks so, maybe its not so bad. To some extend it would strengthen Linux mindshare.
  • Isn't the standards movement entirely about commercial software? You don't configure and make Oracle or WordPerfect.

    Without standards, the fear is you'd start to see commercial vendors releasing "tested and supported on RedHat 5.2 or greater only" statements, just because it's the only baseline they can aim for. It would be better if that read "supported on LSB 1.1 or greater", or whatever. Call it braindead, but that's how commercial sofware works.

    (One idea that Linux should steal from the MacOS is something like the "desktop database", which allows you move programs around the directory structure and have them still run. It's the one huge reason the MacOS is more unbreakable (from a regular user perpsective) than either Windows or unix.)


    --
  • This is not official word, since I'm not an officer of Red Hat Software. That said, almost everything I say here, Red Hat Software has said officially in several contexts, and regular /. readers will see little new here. I'm not sure that this statement is needed, frankly; the majority of the comments I have seen so far are right on the money.

    Red Hat Software is supporting the LSB project both practically, by participation, and philosophically, by agreeing that the LSB is a good idea and expressing our expectation that it will produce a useful and workable standard).

    By now, most /. readers will have heard Red Hat Software's general policy, rarely broken, of not preannouncing software releases. We stick to this policy for many reasons, but two really good reasons are our absolute disgust for vaporware and murphy's law. Things will go wrong and change our delivery dates from time to time. That does not keep us from working on software, obviously -- it just keeps us from preannouncing.

    The same is true for our support of the LSB. We will not preannounce that we will make Red Hat Linux LSB-compliant when the LSB does not exist. That does not keep us from expressing our expectation (it's stronger than simple hope) that the LSB will be a good standard that we will want to implement because it will make our users' lives (and our own work) simpler and easier. We contribute publically to the effort to build the LSB standard, reserving our judgment for the completed standard.

    To the folks who think that Red Hat Software is trying to corner the market in black helicopters, I'll only say that a good enough LSB standard would be very good for all of Linux, abolutely and most definitely including Red Hat Software. But if you think that Red Hat has bought the black helicopters, you aren't going to believe a word I say anyway. ;-)

  • LSB fixes standard features which distros will have to have to be "Linux". What if the file executable type had been "standardized" earlier? We'd still be using inferior a.out binaries. What if the C libraries were "standardized" earlier? We glibc users would be trying to thread with libc5. That would suck. These changes are not a terribly big deal if you have the source code for all your programs. You just recompile!

    LSB will stifle Linux advancement for the benefit of fat-ass companies who don't want to release their code. These companies want to write a program, then sit on their hands and rake in the dough from selling the binaries. Pay someone to compile on another platform or release the source?! Goodness no! Screw them I say.
  • I vote for Yellow Hat. We could make Curious George the unofficial mascot =)

    But yeah, I love how they are talking about Redhat adopting an 'embrace and extend' strategy.. how the fvck can you embrace and extend GPL software?

    "We added fourteen new features to 'ls' to make it incompatible with other linux distros"

    "We recompiled the source that redhat released yesterday, and now have their fourteen new features"

  • Generally Slackware user are those DIY types or sysadmins who prefer their own ways or system hackers. LSB doesn't mean a big deal to them. Patrick said that diversity is preferred.......

    Maddog
  • by slk ( 2510 ) on Saturday March 27, 1999 @07:15PM (#1960206)
    From what the article says, Redhat is waiting for at least a draft version of the standard before saying they will support it. They feel that standards are overhead (they are, to a degree).


    There are two separate issues here: the value of standards, and when to adopt a standard.


    Standards are what the internet (as we know it) is built on. The Web would not have happened without a standardized http, nor compatability between so many e-mail systems without SMTP. Standards like HTTP, FTP, Telnet, TCP/IP, and DNS are what have made the internet possible. What happens if an application decides to handle DNS differently than everybody else? It won't work. What about a web browser that sends nonstandard HTTP queris? It won't work, at least not consistently. Having said that, standards can be overhead. I'm sure there are flaws in all of the accepted internet standards, but they work, and they work well.


    On the other hand, there are bad standards. It seems that most of these are produced by groups that don't regularly handle standardization (you don't see too many bad ones from IEEE, IETF, etc). The LSB is a committee, and might or might not do a good job. Redhat's wait-and-see attitude towards the standard is quite reasonable.

  • by Anonymous Coward

    Hmm. CNN has an email address for feedback...


    To: cnn.feedback@cnn.com
    Subject: Re: Linux fans fear Red Hat takeover

    Dear Sir or Madam,

    Excuse me. Usually you appear to have well-written, seemingly accurate stories. But your recent story entitled 'Linux fans fear Red Hat takeover' has more holes than a colander. And that reflects very poorly on you.

    You stated:

    Szulik also said Red Hat, based in Research Triangle Park, N.C., wouldn't want to see the LSB be used by other Linux vendors with less market share to catch up to Red Hat.

    That just does not make any sense to me. Red Hat makes a point of giving away their software. To the point where competing companies have started taking Red Hat's version of linux, making minor tweaks, and selling it as their own competing flavor of linux.

    Red Hat, and the whole linux community, are well aware of the dangers of linux fragmentation. Considerable effort is being expended to avoid such fragmentation. And by and large, everyone (Red Hat and their competition) is shipping the same software programs. The only major differences are package installation procedures and systems administration.

    The LSB, for all its hype, has more potential to hurt linux compatibility than to help it. When software tools are improving from month to month, and sometimes from day to day, an LSB agreement that prohibited newer releases could stifle linux. And, in the gift-culture that makes up linux, this would in turn lead to everyone buying a competing flavor of linux that did not suffer from the LSB constraints. Quite possibly even one based off Red Hat...


    You also stated:

    Steve Kleynhans, an analyst at Meta Group Inc. in Stamford, Conn., said Red Hat may end up treating Linux standards the way Microsoft Corp. has treated standards such as the Web programming language, HTML: by embracing them, extending them and steering them to match the company's strategy. Red Hat does realize that Linux will fail if it fragments, he said.

    This is misleading. It's so easy to misread the start of the final sentence as "Red Hat doesn't" instead of "does".

    It also completely overlooks all the support Red Hat is giving to the free software community. Red Hat is actually PAYING people to write software on both the GNOME and KDE projects! This is free software. It is GPL'ed. Everyone, including Red Hat's competitors, will be able to distribute not only the binaries that are produced, but also the source code!


    To actually know what is going on in the world of linux, and then to read a story like this... It just makes me sick. Don't you people ever check your facts?

    Or did you just repeat that recent story on zdnet? (http://www.zdnet.com/zdnn/stories/news/0,4586,222 9091,00.html) If so, you should know that I tried to reply to that story in the 'talkback' section. Only, despite several attempts, I was unable to do so. It seems that Zdnet is censoring! They only seem to appreciate pro-linux discussion when it's poorly written, coming from children, or from cranks. I found far more accurate discussion over on slashdot.org. (http://slashdot.org/article.pl?sid=99/03/22/13425 9)

    By the way, your article is being discussed on slashdot.org too. (http://slashdot.org/articles/99/03/27/1518214.sht ml) If you do read the slashdot discussion, I suggest that you "be tolerant". For many of us, watching yet another instance of the microsoft propaganda machine at work has crossed the line from "outraging" to "amusing pathetic". But you might not be as entertained as I was by the comment: "Bad CNN, Bad Bad Bad..... No table scraps for you tonight, go back to the dog house..."

    Sincerely...

  • by Ozric ( 30691 )
    It is important from a support stand point as well. Not that there is that much of a problem now . I think this(LSB)is more to make people see that Linux is Linux no matter how you wrap it.

    Forking Hurt unix.

    Commerical Vendors will not release source code, and a LSB binary better work on all LSB Linux systems.
  • To the best of my knowledge, it is SuSE that does most of the contributions to XFree86 from the Linux distributions.
  • ..but that does not mean it is there.

    RedHat usurped Slackware because users (albeit newcomers) chose RedHat over Slackware despite the fact that most documentation focuses on Slackware. This was because RH is easier to use than Slackware, a similar shift can happen away from RedHat especially over this type a shit.

    Also it makes little sense to try an corner the Linux market, most of whom compile their own programs from source. How long will they wait after any Machiavellian moves by Mr. Young, or anyone else, before they burn RH in effigy.

    LSB is supposed to make developing easier, if it does so they will be more software for Linux. This would remove M$' last leg. LSB can lead to a increase in the size of the Linux market and 10% of what M$ now has is more than 100% of the current Linux market. Desktop wise atleast, and when I say desktop I mean desktop only.

    In which case it is in RH (and all other distros) to grow the pie, thus given everyone more. That way the only people hurting are...
  • The LSB's main thrust is a good one: collaboration between developers and packagers of Linux distributions in order to prevent needless divergence (i.e. keeping apache in /www instead of all over the filesystem, putting smb.conf in /etc, and so forth).

    Where the good intentions go a little awry is in trying to make the certification side an all-or-nothing prospect. Such a thing sounds good at first glance, but it works against some of Linux's strengths.

    Rearranging things to allow use of an innovative configuation management toolset. Moving, removing or replacing components for security. This should be encouraged. Doing these things doesn't change Linux's openness, though it can create islands of incompatibility. The point is that this kind of differentiation is one of the sources of the good ideas that find their way into all the distribs sooner or later.

    Stop this and things stagnate. And then the LSB will implode and you'll have the kind of fragmentation you see in Unix.

    There's undeniable value to a label that indicates broad inter-distribution interoperability and common configuration consistency. But under the current model, it's too constricting. What the LSB needs to do is find a mission that balances consensus and standardization without ever being stifling.
  • A standard will generally list what you need to have to comply... so if a.out files were standardized earlier, it would only mean you have to support them to be complient... not that you can't support any other type of file. So you can continue to enhance things as long as you support the "standard" version as well. The standard could later be changed to reflect those improvements...
  • It's been a few months already and they have nothing to show for it. Just a long list of members. How can LSB provide a standard that adapts fast enough to the changing world of Linux if it can't even provide ONE quickly for starter?

    I love Linux with passion, it's my only OS at home and I try to get people to use it at work, but I'm so angry right now with it!

    I had the most frustrating time lately trying to compile even the simplest program on my S.u.S.E. 5.3. And forget about using pre-compiled packages: I just can't believe how many different kind of RPM are sprouting up! Just check out http://rufus.w3.org/linux/RPM/ for proof...

    I'm sure general software quality and ease of install would increase if software could be build on a standard base.

    LSB NOW!
  • united we stand. divided we fall.

    which way are we headed does it seem?
  • glibc5 isn't dead. It hasn't been born so it can't have died! We're currently at glibc2.1 (or something close to that figure)
    --
  • You write as if the goal of LSB is to create a uniform system, where no progress or differentiation can happen. This is not the case.

    The principal benefit of LSB is that third party software vendors can just target "LSB 1.0" and hence support all distributions. This is a good idea, wouldn't you say?

    In no way does this imply that any distribution needs to be hobbled by the LSB. I'm sure that if glibc 2.1 or 2.2 ends up as the library component of the LSB, and glibc 3 comes out, then distributions will move to it rapidly, while retaining support for LSB in exactly the way that a.out support is provided now.

    If LSB also emerges as a useful development target for ISVs, then I assume that some distributions will provide GCC configurations that link against the "old" libraries as well as a GCC configuration which links against the latest stable glibc etc.

  • Well first RedHat is the one that seems to be setting the standards.. glibc2, rpm, etc.. they are helping the community progress, which is good.. most other distros can run RedHat rpm's or at least the source code can be compiled fairly easily on another platform (supposedly)

    I'd worry about RedHat being a real threat when they start threatening other companies like IBM, Oracle, and such in things like you can only port your stuff to us and everyone else has to suffer...

    M$ threatens other companies that is what makes them such a big threat in the market..

    I am waiting for M$ to threaten RH....

  • CNN had little or nothing to do with this story.. they just post up whatever schlock IDG gives them, whether its from ComputerWorld or LinuxWorld, etc. (Nick Petreley of LinuxWorld fame had a CNN article recently..)

    The problem is that while CNN usually has good reporting quality, they don't seem to display a great sense of judgement with regards to republishing technical articles...


  • Yes, thats a perception problem that indeed exists. Many people new to Open Source, or even commercial variants of basic core products, see what we call distributions as different OSes entirely. I had an admitted newcomer who was contemplating trying Linux ask me if he could run Red Hat and Debian in multi-boot on the same machine as both had been recommended to him and he wanted to compare and see which Operating System was best for him.

    Besides touting just the benefits of the Linux (and other Open Source OSes) we also need to educate as to just what an OS is and what different distributions have to offer.

    I know some people that are otherwise comfortable with computers and use them daily would be horrified if faced with having to compile their software before they could use it to say nothing of patch it as needed. It's going to be a long time before that sort of thing is easily accepted by the greater number of users out there.

  • I loose respect for CNN in this case. Sorry. I see no REAL evidance at all that Red Hat is doing this, or going to do this. Therefore, it's FUD in my eyes. Something I thought CNN was above.


    HAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA!

    Hooooboy, that's a good one.

    But seriously, I think there's a difference between FUD that is intentionally flung around, and stuff that looks like FUD but is accidentally stepped in as the result of one's incompetence or ignorance.
  • Gees, a it's typo. Slackware libc5... don't be so literal minded.

Single tasking: Just Say No.

Working...