Domain: redhat.com
Stories and comments across the archive that link to redhat.com.
Comments · 4,506
-
Red Hat
Rad Hat has some nice certification programs that seem to be versatile and respectable: RHCE
-
Re:FLTK
Unix GUI code has been written since 1984 without needing threads.
Unless the logic of my algorithms is more simply represented as threads, I shouldn't use them. If I want to toss a pretty GUI ontop of a large and ancient existing codebase that is resolutely non-threadsafe, I shouldn't have to use threads.
If my development tools (linux and gdb) don't support threads easily, it'll be aggravating to use them.
Suppose I had a thread? What would it do? Wait for stuff to come from the network, and stuff it in a buffer for the main thread to read once it's ready. Well, the operating system is already doing that exact thing for me. I shouldn't need to redundantly duplicate that same behavior in my own code. -
Just don't pick redhat for a distro.Redhat recently changed their support policy. They now will only support releases for one year with errata. Are you nervous about switching to a
.0 redhat release? Well now you have little choice.Actually, you have a choice, you can switch to their advanced server line for at least $800 per server. They will support each rev of that product with errata for up to three years. As for desktops installs...
Imagine if Microsoft only supported an OS for one year from release...
-
archives
Well, I don't know what to do in Windows, but I have a similar situation and just dual boot the machine. I use tar to make backup volumes and Windows to write. Tar has a multivolume option, -M, and tape length option, -L that I have never used because I've just kludged my way through with directories. Looks like you can use cygwin if you want. Thanks for asking, it was interesting to read about. The machine mostly stays under linux, and I mount the windows drive with an entry in
/etc/fstab. This makes it easy to move things around the local network with ftp and ssh, which might solve your problem of wanting those files on the next computer. When I'm ready to write something out, I copy it to Windose and boot over. Look, Slashdot did this a while back. -
contributed kernel improvements
There is some interesting info at the bottom of this page outlining some improvements Oracle and RedHat have made to this linux kernel regarding things such as SMP processor affinity and asynchronous I/O. Presumably these are open source changes -- the artical doesn't mention them at all.
-
Carrier Grade Linux
Aparently Linux vendors see "Phase 3 style" profit in carrier grade linux. Even Red Hat is getting into this. Lets hope it works out better than embedded linux.
-
It's all about the Benjies.
How much money are you planning on spending? If you want really excellent training, it's going to cost a fair amount of money. Usually around $1500-$2500 ish a week. And you have to decide what you want training in. If you're interested in Solaris, Sun offers a bunch of classes in several New York facilities. Here's a link to their training site: Sun Solaris Training
The couple of classes I've had from Sun have been quite good. Some hands on on equipment that I don't own myself at clean facilities with knowlegable instructors. If you want Linux training, probably the easiest/best place to get it is from Red Hat. They also have a site in NYC, in the financial district, and they provide lunch every day (very cool). Their classes also have hands on labs, but the equipment isn't anything that you wouldn't have at your own house. They teach their classes on PCs. Red Hat's site is Red Hat Leaning Services
Going to the product manufacturer is usually the best way to get top notch training, I'm just using Sun and Red Hat as examples, they have been the ones that I was most happy with. They, product manufacturers, hire instructors who are familiar with the product and who can answer a fair amount (maybe even all) of your questions. And unlike CBT, can provide alternative explanations when the one they use just doesn't get through to you.
The big problem with going to these classes is that, while good, they can be prohibitively expensive. If this is a limiting factor for you, then someone above suggested Community College. I think that this was an excellent suggestion. They are far less expensive, but it's been my experience that the instruction is not always as good.
-Runz -
Re:Redhat Patents
"RedHat granted the right to use their patents in GPL'd software, and they can't take that back."
The hell they did, and the hell they can't.
Read the actual policy, and be sure to take a copy, because it's ephemeral. I'll spell it out for you.
"Red Hat agrees to refrain from enforcing the infringed patent against such party for such [open source] exercise ("Our Promise")"
That's it. That's the whole promise. Not "licenses", not "refrain in perpetuity", not "and has accounted for this promise as a fiduciary liability and an entailment on any future sale of Red Hat".
It's merely a statement that Red Hat won't sue you today. That's all. If you want to argue that it's more than that, or that it's binding, or that it'll be binding when Microsoft buys them out, get yourself a good lawyer, because you'll need him.
-
Re:What?
Since it in Alpha right now, these are the only screenshots!
-
I heavily disagree
*sigh* There we go again.
The Slashdot opensource prejudgements must die. Now.
"The problem is as well is that there is no plausible way to get designers and similar 'soft skill' people into the OSS cycle today:"
*Ahem*
How to join the GNOME project for non-hackers FAQ
GNOME Usability Project
GNOME Documentation Project
GNOME Translation Project
And of course the KDE documentation/translation teams.
All projects for non-hackers. And they're quite busy.
"Gimp and Xfig - my two favorite whipping boys, are examples number one and two of programs that nominally have the features, but in practice are painful to use compared to their closed-source equivalents (Photoshop and Visio)."
Well course. They were made in a time when Linux GUIs were just born and developers had almost no experience in good UI design.
Compare the situation to today. GNOME 2.0? KDE 3.0? Evolution? Mozilla? All very mature software with modern and usable GUIs - because the developers have more experience now!
"* culturally, the OSS 3l337 reject anybody without super-skills. don't even pretend that this isnt true."
Oh great, the old "elitism" argument again.
I can't hack the kernel. I don't know assembly. I'm not a Unix expert. I'm not l33t. Yet if I join a GNOME mailing list, and I ask things carefully and politely, providing all the necessery details, I almost always get a good and clear answer (unless of course, nobody knows an answer). I never, I repeat, never get flamed down or told RTFM.
The elists are - what? - 5% of the entire population? The only place I've seen developers occasionally say "RTFM" is on the MPlayer developers list. On mailing lists for popular projects like GNOME and KDE, nobody tells new users to RTFM. Except sometimes as a joke (with a smilie of course). Also, on IRC channels such as #linuxhelp, people are also often friendly and helpful.
Obviously, you are brainwashed by the popular Slashdot prejudgement that OSS developers are elists. That is simply not true. Can you give me any proof that most OSS developers are elists? I don't think so.
"# Technically, there are no mechanisms in place for this. CVS is about code. The development model is essentially about continuous 'patching' of the software rather than grand rearchitecting, which design considerations often require."
Wrong.
If you say they don't design when they first started the project, then yes, I agree with you partially. Mike spent months thinking about Autopackage's design before he actually started writing code.
Most open source project design as they write the code. They learn from their mistakes and make a better design next time.
A good example is KDE 1.0 to 2.0 --> a complete rewrite. They learned from their mistake and made a new, better architecture. In fact, the design is so good, that KDE 3.0 is mostly a cleanup release with no mater architectural changes, and is mostly source compatible with 2.0.
Another good example is the Linux kernel. The new build system has been carefully designed from the ground up, and can't be applied in small continuous patches.
"economically, there's little hope of getting quality designers involved. Programmers barely get recognition in OSS (blowing to hell ESR's naive theories, btw). Who would care who designed what? How do you get street cred as a designer? I mean, it could happen, but it would take a pretty big mental shift."
GNOME Usability Project anyone? A lot of usability studies are contributed by Sun and Ximian. Sun also contributed a lot of user documentation.
"Design = customer focus. OSS too often has this not. Profit drive causes customer focus. Alas."
Commercial open source software. 'nuff said. -
not enough info
Why don't your managers want to try something new? If it's price, tell them bugzilla is free, and is used by companies from Red Hat to Netscape. If it's a political issue, that's a whole 'nother story.
Also, why is there so much overhead? Entering a bug should be as simple as filling out a single HTML form. Is your UI too big and complicated? You can probably strip it down to the essentials, without discarding it entirely. Is it on more than one page? You can probably condense them into one form. Are the bugs stored in a database? You can write your own search page.
And if you said which bug software you're currently using, you could probably have gotten more specific and relevant tips on how to make the best use of it (change the configuration, prepopulate certain fields, roll your own modified templates, etc.). -
Re:Apples vs Oranges
-
Re:Why not one of the commercial UNIXes? (Apple?)You only need one "seat". For all the rest you just install from the same copy. The "seat" is for the docs and support. Besides you manage all the servers from one "seat" anyway (or not, it still don't matter). As for overkill, you are essentially right, but there was a requirement to be easy, and the need for redundancy and clustering == AS.
Anyone can d/l AS free. It's the support & stuff(docs?) that costs.
so for PREMIUM subscription
$2500 / (70 * 2) = $17.86US
or
$799 / 140 = $5.71US
or
$costOfBandwith + $costOfCDR = SRPMS -
For those of you using RH 8.0
The rpm version that ships with RH 8.0 is pretty buggy and can lead to lockups. RH has an unsupported fixed version of rpm that fixed these problems for me (I was only impacted by one of the bugs). They haven't put out an official update yet.
Note: do *not* upgrade to the version of RPM in Rawhide or Phoebe, RH's current beta. It's a *pain* to get back -- you get moved to hash-version 8 if you --rebuilddb at any point, and db4 as packaged by RH doesn't grok hash-version 8. You'll need to grab db4 from Sleepycat and use it do dump your rpmdb and reload it with RH's db4 if you want to get back (this happened to me). -
stability
Something as important as a package manager can't be this buggy.
-
Re:RH8 CD has too many references to manuals
Totally wrong. RH is actually really good at documenting their products.
First of all, all the usual READMEs are in place:
locate README | wc -l
1392
Check /usr/share/doc for full documentation on all installed packages.
Furthermore, the complete documentation is available from their site, as usual:
http://www.redhat.com/docs/manuals/linux/ -
Re:RH8 CD has too many references to manualsYou can down the manuals in PDF, HTML or ISO format from any of the mirrors.
It's under the DOC directory.
-
Re:Well
"Score: -1, Pro-Microsoft"
Just a comment, I'm curious to hear what you think.
In my browsing of Slashdot, I've noticed a handful of posts berating Microsoft with no backing. I've questioned other posts, but couldn't make a decision because I wasn't familiar with the issue. However, most of the comments that I've seen berating Microsoft, while redundant, are deserved.
On the other side of the fence, I've seen only a handful of arguments for Microsoft (and/or against OSS/FS) that have any decent foundation. There are a few that I had to admit were very sound arguments -- and the people who made them hold my respect. However, most of these arguments are based on myths, such as a lack of good documentation, lack of easy-to-use software, lack of easy installs, etc. I have people like "Twirlip of the Mists" on my foes list simply because they insist on making arguments that they seriously know next to nothing about. And it really pisses me off because Twirlip seems to have good logic.
I understand that a lot of folks here are zealots, I understand that some posts get modded down because they support MS and not because of bad content, but I want to hear your opinion of the whole thing. Be honest, please -- bias won't get anyone anywhere. =) -
Re:SWT binaries?
"Could one, for instance, now compile a Java program using the SWT library to a native binary using GCJ, so it could be run without using a JVM?"
Yes, absolutely. Get ftp://sources.redhat.com/pub/rhug/swt-gcj-green-sn apshot.tar.gz
Run configure/make/make install, and you'll en up with lib-org-eclipse-swt.so.
People are also building for Win32 using gcj for Windows (or a cross compiler from Linux)
AG -
Re:SWT
-
Re:I was hoping they would wait.
RedHat have released updated KDE packages that include a fix for the screensaver bug.
-
Re:I was hoping they would wait.
RedHat have released updated KDE packages that include a fix for the screensaver bug.
-
Re:Change the name
You are muddying the discussion by mixing two situations. First you were talking about modifying an existing GPL'd program (Readline). Now, you seem to be talking about a hypothetical program to which you hold the copyright. In the former case, I say again: you should not expect to be able to profit from other people's work, if they choose not to allow it. In the latter case: if you desire to profit from selling your program (and you feel the GPL undermines this), then use a proprietary license. What's the problem?
But if somebody says to me, "Here, this is free," that sets a certain expectation.
You are confusing "this is Free" with "this belongs to you".
the GPL says you can't sell the software. ...
the idea of making money with your software under the GPL is completely out the window
Provably false. -
He's right!"If the open-source folks just want to copy what's already out there, why not look around more? Surely they can find something more interesting than a copy of a copy of a copy."
This is what I have been saying all along. I wish we could get a window manager more like Mac OS X and less like Windows 95.
Are there any projects out there that are really working on innovations in the GUI area? I know that RedHat 8.0 's BlueCurve is a nice start.
-
You can have both
Uh, no. Here they say "The preferred choice of independent professionals, enthusiasts, and students worldwide." (emphasis mine) Note they still have a 'personal' version. It's bad business to ignore a demographic, and how hard would it be to include some packages and add options under the "Multimedia" section of the installer? Isn't this sort of thing the reason why they developed RPM? So you can add/remove what you want from an installation? But I gripe too much, they did an awesome job.
The Red Hat Speaks on 8.0 and Multimedia page specifically mentions only mp3 audio. Even if MPEG-1 video is banned, they could still include kino and libdv.
That last link is a good one, though, they mention where to get Acrobat Reader, RealPlayer, Macromedia Flash, xine... -
You can have both
Uh, no. Here they say "The preferred choice of independent professionals, enthusiasts, and students worldwide." (emphasis mine) Note they still have a 'personal' version. It's bad business to ignore a demographic, and how hard would it be to include some packages and add options under the "Multimedia" section of the installer? Isn't this sort of thing the reason why they developed RPM? So you can add/remove what you want from an installation? But I gripe too much, they did an awesome job.
The Red Hat Speaks on 8.0 and Multimedia page specifically mentions only mp3 audio. Even if MPEG-1 video is banned, they could still include kino and libdv.
That last link is a good one, though, they mention where to get Acrobat Reader, RealPlayer, Macromedia Flash, xine... -
"Proprietary"
You keep using this word, but I do not think it means what you think it means.
Much of what you assert about the difficulty of updating Redhat is false. I will agree that apt-get install is generally easier to use, but the picture you paint of Redhat update options is far too bleak. I suggest you read the output of man up2date or man gnorpm.
Oh, and if you're sufficiently clued in to worry about POSIX standards (and I note you fail to mention that Redhat is LSB certified), why the hell are you worried about their custom kernels? -
Re:Thinning the herd
It's not sales of CDs, but of services. If you check Red Hat's Advanced Server subscription options, you'll see that the entry point for RHAS is around $800 with updates for one year, but no SLA. The $1500 and $2500 versions include SLAs for the year.
At a minimum, you're paying $600 extra for RHAS vs. the "regular" distro. If you're paying for a minimal SLA (i.e. corporate datacenter buyer), you're paying $1300 more per server as the SLA only covers one system.
In other words, over 85% of the price of a corporate purchase of RHAS with minimal SLA is for the support contract, not for the distro itself.
Mandrake's closest profit generator would be their multi-network firewall/VPN at around $2000.
Looking at the typical corporate or ISP data center, how many firewall boxen are running? How many database, application, and web servers are running? Lets assume we're dealing with a moderate company that decides to buy from both vendors:
- 1 firewall - $2000 to Mandrake
- 2 database servers - $3000/year to RedHat
- 2 app servers - $3000/year to RedHat
- 1 web server - $1500/year to RedHat
Isn't it obvious that Mandrake has targetted a niche market that cannot hope to generate the kind of revenue stream that RedHat's approach does?
The frustrating thing is I've preferred Mandrake to RedHat since I got burnt by RH 7.1 and that 2.96 compiler fiasco. I'd love to see Mandrake do well, but I just can't see any way they can even hope to survive.
-
Important Stuff:
It has come to my attention that the entire Linux community is a hotbed of so called 'alternative sexuality,' which includes anything from hedonistic orgies to homosexuality to pedophilia.
What better way of demonstrating this than by looking at the hidden messages contained within the names of some of Linux's most outspoken advocates:
- Linus Torvalds is an anagram of slit anus or VD 'L,' clearly referring to himself by the first initial.
- Richard M. Stallman, spokespervert for the Gaysex's Not Unusual 'movement' is an anagram of mans cram thrill ad.
- Alan Cox is barely an anagram of anal cox which is just so filthy and unchristian it unnerves me.
I'm sure that Eric S. Raymond, composer of the satanic homosexual propaganda diatribe The Cathedral and the Bizarre, is probably an anagram of something queer, but we don't need to look that far as we know he's always shoving a gun up some poor little boy's rectum. Update: Eric S. Raymond is actually an anagram for secondary rim and cord in my arse. It just goes to show you that he is indeed queer.
Update the Second: It is also documented that Evil Sicko Gaymond is responsible for a nauseating piece of code called Fetchmail, which is obviously sinister sodomite slang for 'Felch Male' -- a disgusting practise. For those not in the know, 'felching' is the act performed by two perverts wherein one sucks their own post-coital ejaculate out of the other's rectum. In fact, it appears that the dirty Linux faggots set out to undermine the good Republican institution of e-mail, turning it into 'e-male.'
As far as Richard 'Master' Stallman goes, that filthy fudge-packer was actually quoted on leftist commie propaganda site Salon.com as saying the following: 'I've been resistant to the pressure to conform in any circumstance,' he says. 'It's about being able to question conventional wisdom,' he asserts. 'I believe in love, but not monogamy,' he says plainly.
And this isn't a made up troll bullshit either! He actually stated this tripe, which makes it obvious that he is trying to politely say that he's a flaming homo slut!
Speaking about 'flaming,' who better to point out as a filthy chutney ferret than Slashdot's very own self-confessed pederast Jon Katz. Although an obvious deviant anagram cannot be found from his name, he has already confessed, nay boasted of the homosexual perversion of corrupting the innocence of young children. To quote from the article linked:
'I've got a rare kidney disease,' I told her. 'I have to go to the bathroom a lot. You can come with me if you want, but it takes a while. Is that okay with you? Do you want a note from my doctor?'
Is this why you were touching your penis in the cinema, Jon? And letting the other boys touch it too?
We should also point out that Jon Katz refers to himself as 'Slashdot's resident Gasbag.' Is there any more doubt? For those fortunate few who aren't aware of the list of homosexual terminology found inside the Linux 'Sauce Code,' a 'Gasbag' is a pervert who gains sexual gratification from having a thin straw inserted into his urethra (or to use the common parlance, 'piss-pipe'), then his homosexual lover blows firmly down the straw to inflate his scrotum. This is, of course, when he's not busy violating the dignity and copyright of posters to Slashdot by gathering together their postings and publishing them en masse to further his twisted and manipulative journalistic agenda.
Sick, disgusting antichristian perverts, the lot of them.
In addition, many of the Linux distributions (a 'distribution' is the most common way to spread the faggots' wares) are run by faggot groups. The Slackware distro is named after the 'Slack-wear' fags wear to allow easy access to the anus for sexual purposes. Furthermore, Slackware is a close anagram of claw arse, a reference to the homosexual practise of anal fisting. The Mandrake product is run by a group of French faggot satanists, and is named after the faggot nickname for the vibrator. It was also chosen because it is an anagram for dark amen and ram naked, which is what they do.
Another 'distro,' (abbrieviated as such because it sounds a bit like 'Disco,' which is where homosexuals preyed on young boys in the 1970s), is Debian, an anagram of in a bed, which could be considered innocent enough (after all, a bed is both where we sleep and pray), until we realise what other names Debian uses to describe their foul wares. 'Woody' is obvious enough, being a term for the erect male penis, glistening with pre-cum. But far sicker is the phrase 'Frozen Potato' that they use. This filthy term, again found in the secret homosexual 'Sauce Code,' refers to the solo homosexual practice of defecating into a clear polythene bag, shaping the turd into a crude approximation of the male phallus, then leaving it in the freezer overnight until it becomes solid. The practitioner then proceeds to push the frozen 'potato' up his own rectum, squeezing it in and out until his tight young balls erupt in a screaming orgasm.
And Red Hat is secret homo slang for the tip of a penis that is soaked in blood from a freshly violated underage ringpiece.
The fags have even invented special tools to aid their faggotry! For example, the 'supermount' tool was devised to allow deeper penetration, which is good for fags because it gives more pressure on the prostate gland. 'Automount' is used, on the other hand, because Linux users are all fat and gay, and need to mount each other automatically.
The depths of their depravity can be seen in their use of 'mount points.' These are, plainly speaking, the different points of penetration. The main one is obviously
/anus, but there are others. Militant fags even say 'there is no /opt mount point' because for these dirty perverts faggotry is not optional but a way of life.More evidence is in the fact that Linux users say how much they love `man`, even going so far as to say that all new Linux users (who are in fact just innocent heterosexuals indoctrinated by the gay propaganda) should try out `man`. In no other system do users boast of their frequent recourse to a man.
Other areas of the system also show Linux's inherit gayness. For example, people are often told of the 'FAQ,' but how many innocent heterosexual Windows users know what this actually means. The answer is shocking: Faggot Anal Quest: the voyage of discovery for newly converted fags!
Even the title 'Slashdot' originally referred to a homosexual practice. Slashdot of course refers to the popular gay practice of blood-letting. The Slashbots, of course are those super-zealous homosexuals who take this perversion to its extreme by ripping open their anuses, as seen on the site most popular with Slashdot users, the depraved work of Satan, http://www.eff.org/.
The editors of Slashdot also have homosexual names: 'Hemos' is obvious in itself, being one vowel away from 'Homos.' But even more sickening is 'Commander Taco' which sounds a bit like 'Commode in Taco,' filthy gay slang for a pair of spreadeagled buttocks that are caked with excrement. (The best form of lubrication, they insist.) Sometimes, these 'Taco Commodes' have special 'Salsa Sauce' (blood from a ruptured rectum) and 'Cheese' (rancid flakes of penis discharge) toppings. And to make it even worse, Slashdot runs on Apache!
The Apache server, whose use among fags is as prevalent as AIDS, is named after homosexual activity -- as everyone knows, popular faggot band, the Village People, featured an Apache Indian, and it is for him that this gay program is named.
And that's not forgetting the use of patches in the Linux fag world -- patches are used to make the anus accessible for repeated anal sex even after its rupture by a session of fisting.
To summarise: Linux is gay. 'Slash -- Dot' is the graphical description of the space between a young boy's scrotum and anus. And BeOS is for hermaphrodites and disabled 'stumpers.'
FEEDBACK
What worries me is how much you know about what gay people do. I'm scared I actually read this whole thing. I think this post is a good example of the negative effects of Internet usage on people. This person obviously has no social life anymore and had to result to writing something as stupid as this. And actually take the time to do it too. Although... I think it was satire.. blah.. it's early. -- Anonymous Coward, Slashdot
Well, the only reason I know all about this is because I had the misfortune to read the Linux 'Sauce code' once. Although publicised as the computer code needed to get Linux up and running on a computer (and haven't you always been worried about the phrase 'Monolithic Kernel'?), this foul document is actually a detailed and graphic description of every conceivable degrading perversion known to the human race, as well as a few of the major animal species. It has shocked and disturbed me, to the point of needing to shock and disturb the common man to warn them of the impending homo-calypse which threatens to engulf our planet.
You must work for the government. Trying to post the most obscene stuff in hopes that slashdot won't be able to continue or something, due to legal woes. If i ever see your ugly face, i'm going to stick my fireplace poker up your ass, after it's nice and hot, to weld shut that nasty gaping hole of yours. -- Anonymous Coward, Slashdot
Doesn't it give you a hard-on to imagine your thick strong poker ramming it's way up my most sacred of sphincters? You're beyond help, my friend, as the only thing you can imagine is the foul penetrative violation of another man. Are you sure you're not Eric Raymond? The government, being populated by limp-wristed liberals, could never stem the sickening tide of homosexual child molesting Linux advocacy. Hell, they've given NAMBLA free reign for years!
you really should post this logged in. i wish i could remember jebus's password, cuz i'd give it to you. -- mighty jebus, Slashdot
Thank you for your kind words of support. However, this document shall only ever be posted anonymously. This is because the 'Open Sauce' movement is a sham, proposing homoerotic cults of hero worshipping in the name of freedom. I speak for the common man. For any man who prefers the warm, enveloping velvet folds of a woman's vagina to the tight puckered ringpiece of a child. These men, being common, decent folk, don't have a say in the political hypocrisy that is Slashdot culture. I am the unknown liberator.
ROLF LAMO i hate linux FAGGOTS -- Anonymous Coward, Slashdot
We shouldn't hate them, we should pity them for the misguided fools they are... Fanatical Linux zeal-outs need to be herded into camps for re-education and subsequent rehabilitation into normal heterosexual society. This re-education shall be achieved by forcing them to watch repeats of Baywatch until the very mention of Pamela Anderson causes them to fill their pants with healthy heterosexual jism.
Actually, that's not at all how scrotal inflation works. I understand it involves injecting sterile saline solution into the scrotum. I've never tried this, but you can read how to do it safely in case you're interested. (Before you moderate this down, ask yourself honestly -- who are the real crazies -- people who do scrotal inflation, or people who pay $1000+ for a game console?) -- double_h, Slashdot
Well, it just goes to show that even the holy Linux 'sauce code' is riddled with bugs that need fixing. (The irony of Jon Katz not even being able to inflate his scrotum correctly has not been lost on me.) The Linux pervert elite already acknowledge this, with their queer slogan: 'Given enough arms, all rectums are shallow.' And anyway, the PS2 sucks major cock and isn't worth the money. Intellivision forever!
dude did u used to post on msnbc's nt bulletin board now that u are doing anti-gay posts u also need to start in with anti-black stuff too c u in church -- Anonymous Coward, Slashdot
For one thing, whilst Linux is a cavalcade of queer propaganda masquerading as the future of computing, NT is used by people who think nothing better of encasing their genitals in quick setting plaster then going to see a really dirty porno film, enjoying the restriction enforced onto them. Remember, a wasted arousal is a sin in the eyes of the Catholic church. Clearly, the only god-fearing Christian operating system in existence is CP/M -- The Christian Program Monitor. All computer users should immediately ask their local pastor to install this fine OS onto their systems. It is the only route to salvation.
Secondly, this message is for every man. Computers know no colour. Not only that, but one of the finest websites in the world is maintained by a Black Man . Now fuck off you racist donkey felcher.
And don't forget that slashdot was written in Perl, which is just too close to 'Pearl Necklace' for comfort.... oh wait; that's something all you heterosexuals do.... I can't help but wonder how much faster the trolls could do First-Posts on this site if it were redone in PHP... I could hand-type dynamic HTML pages faster than Perl can do them. -- phee, Slashdot
Although there is nothing unholy about the fine heterosexual act of ejaculating between a woman's breasts, squirting one's load up towards her neck and chin area, it should be noted that Perl (standing for Pansies Entering Rectums Locally) is also close to 'Pearl Monocle,' 'Pearl Nosering,' and the ubiquitous 'Pearl Enema.'
One scary thing about Perl is that it contains hidden homosexual messages. Take the following code: LWP::Simple -- It looks innocuous enough, doesn't it? But look at the line closely: There are two colons next to each other! As Larry 'Balls to the' Wall would openly admit in the Perl Documentation, Perl was designed from the ground up to indoctrinate it's programmers into performing unnatural sexual acts -- having two colons so closely together is clearly a reference to the perverse sickening act of 'colon kissing,' whereby two homosexual queers spread their buttocks wide, pressing their filthy torn sphincters together. They then share small round objects like marbles or golfballs by passing them from one rectum to another using muscle contraction alone. This is also referred to in programming 'circles' as 'Parameter Passing.'
And PHP stands for Perverted Homosexual Penetration. Didn't you know?
Thank you for your valuable input on this. I am sure you will be never forgotten. BTW: Did I mention that this could be useful in terraforming Mars? Mars rulaa. -- Eimernase, Slashdot
Well, I don't know about terraforming Mars, but I do know that homosexual Linux Advocates have been probing Uranus for years.
That's inspiring. Keep up the good work, AC. May God in his wisdom grant you the strength to bring the plain honest truth to this community, and make it pure again. Yours, Cerberus. -- Anonymous Coward, Slashdot
*sniff* That brings a tear to my eye. Thank you once more for your kind support. I have taken faith in the knowledge that I am doing the Good Lord's work, but it is encouraging to know that I am helping out the common man here.
However, I should be cautious about revealing your name 'Cerberus' on such a filthy den of depravity as Slashdot. It is a well known fact that the 'Kerberos' documentation from Microsoft is a detailed manual describing, in intimate, exacting detail, how to sexually penetrate a variety of unwilling canine animals; be they domesticated, wild, or mythical. Slashdot posters have taken great pleasure in illegally spreading this documentation far and wide, treating it as an 'extension' to the Linux 'Sauce Code,' for the sake of 'interoperability.' (The slang term they use for nonconsensual intercourse -- their favourite kind.)
In fact, sick twisted Linux deviants are known to have LAN parties, (Love of Anal Naughtiness, needless to say.), wherein they entice a stray dog, known as the 'Samba Mount,' into their homes. Up to four of these filth-sodden blasphemers against nature take turns to plunge their erect, throbbing, uncircumcised members, conkers-deep, into the rectum, mouth, and other fleshy orifices of the poor animal. Eventually, the 'Samba Mount' collapses due to 'overload,' and needs to be 'rebooted.' (i.e., kicked out into the street, and left to fend for itself.) Many Linux users boast about their 'uptime' in such situations.
Inspiring stuff! If only all trolls were this quality! -- Anonymous Coward, Slashdot
If only indeed. You can help our brave cause by moderating this message up as often as possible. I recommend '+1, Underrated,' as that will protect your precious Karma in Metamoderation. Only then can we break through the glass ceiling of Homosexual Slashdot Culture. Is it any wonder that the new version of Slashcode has been christened 'Bender'???
If we can get just one of these postings up to at least '+1,' then it will be archived forever! Others will learn of our struggle, and join with us in our battle for freedom!
It's pathetic you've spent so much time writing this. -- Anonymous Coward, Slashdot
I am compelled to document the foulness and carnal depravity that is Linux, in order that we may prepare ourselves for the great holy war that is to follow. It is my solemn duty to peel back the foreskin of ignorance and apply the wire brush of enlightenment.
As with any great open-source project, you need someone asking this question, so I'll do it. When the hell is version 2.0 going to be ready?!?! -- Anonymous Coward, Slashdot
I could make an arrogant, childish comment along the lines of 'Every time someone asks for 2.0, I won't release it for another 24 hours,' but the truth of the matter is that I'm quite nervous of releasing a 'number two,' as I can guarantee some filthy shit-slurping Linux pervert would want to suck it straight out of my anus before I've even had chance to wipe.
I desperately want to suck your monolithic kernel, you sexy hunk, you. -- Anonymous Coward, Slashdot
I sincerely hope you're Natalie Portman.
Dude, nothing on slashdot larger than 3 paragraphs is worth reading. Try to distill the message, whatever it was, and maybe I'll read it. As it is, I have to much open source software to write to waste even 10 seconds of precious time. 10 seconds is all its gonna take M$ to whoop Linux's ass. Vigilence is the price of Free (as in libre -- from the fine, frou frou French language) Software. Hack on fellow geeks, and remember: Friday is Bouillabaisse day except for heathens who do not believe that Jesus died for their sins. Those godless, oil drench, bearded sexist clowns can pull grits from their pantaloons (another fine, fine French word) and eat that. Anyway, try to keep your message focused and concise. For concision is the soul of derision. Way. -- Anonymous Coward, Slashdot
What the fuck?
I've read your gay conspiracy post version 1.3.0 and I must say I'm impressed. In particular, I appreciate how you have managed to squeeze in a healthy dose of the latent homosexuality you gay-bashing homos tend to be full of. Thank you again. -- Anonymous Coward, Slashdot
Well bugger me!
ooooh honey. how insecure are you!!! wann a little massage from deare bruci. love you -- Anonymous Coward, Slashdot
Fuck right off!
IMPORTANT: This message needs to be heard (Not HURD, which is an acronym for 'Huge Unclean Rectal Dilator') across the whole community, so it has been released into the Public Domain. You know, that licence that we all had before those homoerotic crypto-fascists came out with the GPL (Gay Penetration License) that is no more than an excuse to see who's got the biggest feces-encrusted cock. I would have put this up on Freshmeat, but that name is known to be a euphemism for the tight rump of a young boy.
Come to think of it, the whole concept of 'Source Control' unnerves me, because it sounds a bit like 'Sauce Control,' which is a description of the homosexual practice of holding the base of the cock shaft tightly upon the point of ejaculation, thus causing a build up of semenal fluid that is only released upon entry into an incision made into the base of the receiver's scrotum. And 'Open Sauce' is the act of ejaculating into another mans face or perhaps a biscuit to be shared later. Obviously, 'Closed Sauce' is the only Christian thing to do, as evidenced by the fact that it is what Cathedrals are all about.
Contributors: (although not to the eternal game of 'soggy biscuit' that open 'sauce' development has become) Anonymous Coward, Anonymous Coward, phee, Anonymous Coward, mighty jebus, Anonymous Coward, Anonymous Coward, double_h, Anonymous Coward, Eimernase, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward. Further contributions are welcome.
Current changes: This version sent to FreeWIPO by 'Bring BackATV' as plain text. Reformatted everything, added all links back in (that we could match from the previous version), many new ones (Slashbot bait links). Even more spelling fixed. Who wrote this thing, CmdrTaco himself?
Previous changes: Yet more changes added. Spelling fixed. Feedback added. Explanation of 'distro' system. 'Mount Point' syntax described. More filth regarding `man` and Slashdot. Yet more fucking spelling fixed. 'Fetchmail' uncovered further. More Slashbot baiting. Apache exposed. Distribution licence at foot of document.
ANUX -- A full Linux distribution... Up your ass!
-
Re:solution for one of the problems..
They make Red Hat Network Enterprise, Proxy and Satellite services just for this. https://rhn.redhat.com/purchase_info.pxt
I have no clue how much it costs. I assume if you have the need for it, then it isn't that much. -
Re:solution for one of the problems..
up2date does this for you in a couple of clicks. You then administrate all your server updates at their site.
If cost is an issue and you have an administrator to set it up, you can use Current or NRH-up2date.
With up2date, in a few clicks you can easily apply three patches to 100 servers before Close of Business
-mel -
Re:solution for one of the problems..
up2date does this for you in a couple of clicks. You then administrate all your server updates at their site.
If cost is an issue and you have an administrator to set it up, you can use Current or NRH-up2date.
With up2date, in a few clicks you can easily apply three patches to 100 servers before Close of Business
-mel -
Revenue analasis
Redhat Press idg.net has an article about SuSE Linux
-
Redhat's load balancerRedhat has it's own LVS tools with a web interface. Very easy to setup.
http://www.redhat.com/software/advancedserver/tec
h nical/piranha.html -
GNOME Armageddonthis is the sixth text revision done on 04-11-2002.
dear reader the gnome armageddon has started,
first of all i want to clarify that this text was meant to be a source of information otherwise i wouldn't have spent so much time into writing it. belive me it took me a couple of days writing this text in a foreign language. even if you don't care at all for gnome, you may find some interesting information within this text that you like to read. please try to understand my points even if it's hard sometimes, otherwise you wake up one day and feel the need to switch to a different operating system.
on the following lines i'm trying to give you a little insight of the gnome community. the things that are going on in the back, the information that could be worth talking and thinking about.
many of us like the gnome desktop and some of us were following it since the beginning. gnome is a promising project because it's mostly written in C, easy to use, configurable and therefore fits perfectly into the philosophy of u*nix. only to name some of its advantages.
unfortunately these advantages changed with the recently new released version of gnome. the core development team somehow got the idea of targeting gnome to a complete different direction of users. the so called corporate desktop user. in other words they're targeting people that aren't familiar or experienced with desktop environments. usually business oriented people who are willing to pay money for getting gnome on their computers.
having this new target in mind, the core development team mostly under contract by companies like redhat , ximian and sun decided to simplify the desktop as much as even possible by removing all its flexibility in favor of an easy clean simple interface to not confuse their new possible customers. so far the idea of a clean easy to use desktop is honourable.
some of the new ideas, features and implementations such as gconf , an evil windows registry like system, new ordering of buttons and dialogs, the removal of 90%-95% of all visible preferences from the control center and applications, the new direction that gnome leads and the attitude of the core development team made a lot of users really unhappy. these are only a couple of examples and the list can easily be expanded but for now this is enough. now let me try to get deeper into these aspects.
you may imagine that users got really frustrated because their beloved gnome desktop matured into something they didn't want. during the time, the frustration of a not less amount of people increased. more , more and more emails arrived on the gnome mailinglists where users tried to explain their concerns, frustrations and the leading target of GNOME.
but the core development team of gnome don't give a damn about what their users are thinking or wanting and most of the time they come up with their standard purl. the reply they give is mostly the same. users should either go and 'file a bug' at bugzilla or the user mails are being turned so far that at the end they sound like being trolls or the user feedback is simply not wanted. whatever happens the answers aren't really satisfying for the user. even constructive feedback isn't appreciated.
if you gonna think about this for a minute then things gonna harden that they are directing into the commercial area. the core development team actually don't care for the complaining home user. it's more important for them to reach the customers with the cash. it seems that this has been told to them by the company leaders. everything about gnome has been decided already, a way back or direct communication isn't possible. don't get trapped by sentences like 'we listen to our users'. they listen to you - yes, to make funny silly jokes about you afterwards.
i thought that everything was build up on friendship, build on programming for fun, build on understanding each other. but the reality looks like it's all for the big money. the cash is what matters everything else is a lie and a dream. time for people to wake up.
not long ago they threw one of the most important long year core developer martin baulig out of team. a guy who worked really hard on getting gnome into the right direction. a nice friendly person who put all his time into gnome. but narrow minded gnome elites such as havoc pennington were responsible that he left the gnome project. the trouble and the pressure that was put on him was to much.
with the new gnome desktop a lot of user interface changes happened such as button reordering . needless to say that this confuse people who are used to the 'right' button ordering for ages. even our fellow linux guru alan cox wasn't thrilled about this idea. but the gnome elites such as havoc pennington, seth nickell, calum benson and dave bordoley knew it better. why following the road of any other desktop that exists ? why not doing something that don't confuse their users and still stay usable ? well it seems to be too easy. gnome needs to be different than anything else so they changed the button order which was one of the reasons that users became unhappy. they said that there was a hard fight about this and the decision was made to change the buttons. but i belive they simply copied the behaviour of macos because most of the gnome developers use a macintosh as either laptop or desktop. sad that they forgot to keep in mind that users tend to mix applications and that this will lead into weird button searching and clicking.
but as if this wasn't enough the same people decided that the new gnome human interface guides were the ultima non plus ultra in human interface guides. the announcement contained informations that the kde usability people got initiated into it. unfortunately the kde people heard about it the first time when seth nickell went to the kde mailinglist which happened after the announcement. you can imagine that they got highly pissed off about this attitude. you can read more on this link . to summarize it, the kde people clarified that gnome should care for their own business.
the problem that came with the new interface guides was, that every little gnome hacker started to become an user interface expert over night. a lot of gnome programs that we like to use matured into a disaster over night. hackers that never programmed correctly for their life started to blindly follow the hype of simplification. for an example look what happened to galeon's interface (pay attention for the last paragraph). even philip langdale a long year galeon hacker got highly indignant by the target that gnome leads and wrote this email to the galeon mailinglist.
here another reason why users became angry. the elite assumes, that the user knows nothing about their system. you find a couple of heavily insulting mails on their mailing lists containing sentences like the quoted ones.
"the user don't know what a window manager is",
"the user don't know what themes are",
"the user don't know what a homedir is",
"the user can't compile a kernel",
"the user don't want to customize their desktop",
"the user shouldn't see preferences which purpose they don't know"
you may imagine that a lot of people are being offended by such lines because it's exactly these gnome users who are meant by these phrases. to read more such lines on the gnome mailinglists, simply click on this link and grep in their archives. be said that most of these sentences are coming from havoc pennington.
such evil practices shouldn't be tolerated by the users and need to be fighted. u*nix users aren't stupid people. who actually gave havoc pennington the rights to decide what the user wants and what not ? various users told him that people who use a u*nix like system are well aware of their capabilities dealing with such a complex system. there's a reason why people are switching from alternative operating systems. they want to learn, they want to use the full power of the system, they want to change everything they like.
to top all this, look at the future plans of nautilus . the current maintainers got the idea of changing the whole nautilus concepts into an object oriented user interface design. you may be highly interested in reading the exact words of alex larsson's vision for nautilus' future direction by clicking on this link .
to summarize it, it's assumed that the user don't need to deal with his homedir or his whole filesystem because it may confuse him or because he don't understand it. the new concepts of nautilus should be that the user deal with symbols in the nautilus view. e.g. you get a cdrom symbol and by clicking on it you see the directory of your cdrom, you get a photo symbol and by clicking on it you get a list of all your pr0n pictures, you get a music symbol and by clicking on it you get a list of all your mp3's. you don't know where all these files are located because you don't deal with the bottom layer of your homedir or filesystem anymore as mentioned earlier.
the question is why are people that know nothing about their users, that know nothing about correct user interface design destroying gnome ? the users don't deserve all this specially those that backed gnome for all the years. even sun threw a bunch of so called user interface experts together and have them work on gnome. don't forget that sun are the creators of the common desktop environment . we don't need another cde clone named gnome. even havoc pennington author of the good user interfaces text isn't able to get his own written software following his rules.
not long ago there was an report about the 'two captains of nautilus' where the reporter (uraeus a gnome contributor himself) reported alexander larsson and david camp. you may imagine that such a report can't be taken serious because it's done by their own people. we here have a saying that sounds like this 'one crow doesn't hack the eye of another crow out'. now you can click on this link and read more. it may be interesting to read the replies from various users all over the globe of what they think about gnome and nautilus in general (please pay attention to the listed ip's there). another nice and informative reading can be found by clicking on this link .
the fileselector problem was a long discussed issue in the gnome community. finally they came to an solution for this and have decided to go for this ugly fileselector instead going for this one which was developed by a free volunteer for a long time and in general looks and behaves better.
most users have no problems with the idea of keeping things simple and clean. removing some not needed preferences was indeed a good idea but it doesn't stop. people started to remove everything from their apps. you're forced to use dubious programs like gconf-editor which basically works like the windows registry editor, to tweak uncommented preferences. i don't think that this is an advantage. even the possibility to tweak preferences with an editor was taken away with that ugly implementation of gconf. all your preferences are stored in a directory tree with an unknown amount of *.xml files. even if you delete programs their keys are still remaining orphaned in these trees and finding them is like playing trivia. at the end it's worth a discussion if a system driven by a single home user needs such a registry like system. we didn't need such a system for over 30 years but the gnome development team got the idea copying one of the most retarded systems from windows to u*nix. not to mention that the copy is more retarded than the original.
it's a shame to see how such a nice desktop got thrown into the trash by such people. but there is a lot more behind the scenes that i don't know about. everything around gnome is a big marketing strategy. poor people are working the hell out of gnome for nothing and companies such as those mentioned above are getting the big cash. for sure you could say - go and fork gnome - but seriously how can you go and fork gnome ? such a big project which needs a bunch of people to keep the code alive and compatible. well you know it's all about open source the code is signed under the gnu/gpl or gnu/lgpl, you can't own it. even the companies are aware of this. but if you can't own the code - go and hire their developers. you can direct them like puppets in any direction that you - as company - like. exactly this is happening with gnome.
well you could easily come up and tell me to simply not use gnome and let them do whatever they like. well, you are right with that but things are more complicated nowadays. gnome is influencing a lot of third party projects such as xfree86 which recently added a lot of gnome components into their cvs repository. please know that with the next coming xfree86 version you get a lot of gnome components without even knowing it. code like, gnome-xml , pkgconfig , fontconfig , xcursor and xft2 were mainly written by people who're heavily involved into gnome development. also the gimp is maturing more and more into getting the look and feel of a native gnome application. the cvs version of the gimp has a lot of gnome pixmaps inside and they are heavily working on integrate the gimp into gnome. if not today but the direction is sure and i fear the day this gonna happen.
it's ok that these things exist and it's ok to see xfree86 and the gimp are beeing hacked on. but please think about the people that don't like or use gnome. what about them ? why force them to have gnome components installed on their systems ? why can't gnome go the same way that kde went e.g. doing their own stuff without infecting other projects like aids. seeing more and more libraries and applications that were in no way related to gnome jumping on the pkgconfig boat which's really not needed. look what will happen to solaris, the world famous operating system on u*nix used by big companies and long years experts. they really plan to replace cde with gnome. i know that cde wasn't the best invention of desktops but it rarely crashed and it fits far better into the philosophy of xfree86 with their configuration system than gnome. you know the good old way having your settings defined with
.xdefaults and all nice default configurations are going into /etc/x11/app-defaults/ and so on. understandable that the good old way may be blocking the future of applications for multiusersystems - but why must it have to be a windows registry like system that replaces future configuration ?well to come to an end i personally don't like many of this stuff. i can't stand the button reordering, i don't like the gconf system and even more i don't like the commercial outsourcing of gnome and the bad influence that gnome has on other applications. the bad attitude of some gnome developers is another story since we are all different reacting humans. luckily there are people sharing some of my thoughts otherwise i wouldn't be able to proof my text with so many links. even amongst the gnome developers there are silent voices of people that hate many of these decisions and silently use something else. right now if you checkout the gnome cvs repository every day you find out that the whole gnome development seemed to came to an halt. the contributions to their cvs are poor. while projects such as kde are reaching easily 10-20k commits per month - gnome is getting around 1-2k per month on it's best times. it really looks like the situation of gnome is unclear so it would be better to have it not influence so much other programs or at the end we deal with an disaster.
now i hope this text was informative for you. i hope that you start to think about the situation and the global direction. the situation of gnome is unclear, their target is groggy too since i can't belive that the users that they are targeting ever heard of u*nix or linux. they plan to get out of the 0.05% desktop niche but this will for sure not happen if they continue their current direction and their bad ugly attitude.
-
Re:Why doesn't RMS bother with other professions?
"The vast majority of software is not developed on a speculative basis (build it and hope they buy it), most of it is built on contract or in house, and the only risk involved is to the buyer, because the guys writing the software are on hourly wages or salaries. "
Huh? You ask me to widen my horizons, and yet you clearly don't grasp the concepts.
Whether or not software is built on contract or in house, there is still cost involved. That cost is still speculative in nature. The only difference is how that return on investment is calculated. One way is unit sales, the other way is increased business opportunities.
"In this view, rather than buying a $10 million package, a company spends a few hundred thousand enhancing an existing package to make it better suit their needs."
This is called buying off-the-shelf software. It may not literally be off a shelf, but it was developed by a third party. You pay them to customize and deliver it to you. The extent of the customization determines the cost. OSS doesn't make much of any difference to this model because it is rare to find OSS software in the specific niches companies would need. Most OSS software addresses general purpose needs, or needs specific to admins and developers because of the lack of motivation to go beyond those needs.
"I'm a programmer, and I get paid (very well, actually) to write software, yet I'm not in the least bit afraid of OSS."
I'm not the least bit afraid of OSS. I am, however, afraid of the FSF and their attempts to lobby governments into nationalizing software development.
"As long as people want software, people will get paid to write it, manage it, distribute it, fix it, improve it, etc. "
The difference is whether you work in a Bill Gates world where you receive a goodly salary and stock options, or you live in Richard Stallmans world where you receive $40k a year and 3.1% federal worker cost of living increases.
"Free software isn't socialism, it's just a different business model."
A business model which has thus far failed, resulting in it's proponents working harder and harder to lobby government agencies to outlaw commercial software and nationalize software development.
After all, that has been RMS's goal all along...
"What the facts show is that people will program for reasons other than riches; but if given a chance to make a lot of money as well, they will come to expect and demand it. Low-paying organizations do poorly in competition with high-paying ones, but they do not have to do badly if the high-paying ones are banned. "
- Richard Stallman in the GNU Manifesto
In the future I think it would be wise for you to stop confusing FSF with OSS. The two are not the same, and if you need clarification on that you need only ask Stallman. -
IMPORTANT - THE LINUX GAY CONSPIRACY
It has come to my attention that the entire Linux community is a hotbed of so called 'alternative sexuality,' which includes anything from hedonistic orgies to homosexuality to pedophilia.
What better way of demonstrating this than by looking at the hidden messages contained within the names of some of Linux's most outspoken advocates:
- Linus Torvalds is an anagram of slit anus or VD 'L,' clearly referring to himself by the first initial.
- Richard M. Stallman, spokespervert for the Gaysex's Not Unusual 'movement' is an anagram of mans cram thrill ad.
- Alan Cox is barely an anagram of anal cox which is just so filthy and unchristian it unnerves me.
I'm sure that Eric S. Raymond, composer of the satanic homosexual propaganda diatribe The Cathedral and the Bizarre, is probably an anagram of something queer, but we don't need to look that far as we know he's always shoving a gun up some poor little boy's rectum. Update: Eric S. Raymond is actually an anagram for secondary rim and cord in my arse. It just goes to show you that he is indeed queer.
Update the Second: It is also documented that Evil Sicko Gaymond is responsible for a nauseating piece of code called Fetchmail, which is obviously sinister sodomite slang for 'Felch Male' -- a disgusting practise. For those not in the know, 'felching' is the act performed by two perverts wherein one sucks their own post-coital ejaculate out of the other's rectum. In fact, it appears that the dirty Linux faggots set out to undermine the good Republican institution of e-mail, turning it into 'e-male.'
As far as Richard 'Master' Stallman goes, that filthy fudge-packer was actually quoted on leftist commie propaganda site Salon.com as saying the following: 'I've been resistant to the pressure to conform in any circumstance,' he says. 'It's about being able to question conventional wisdom,' he asserts. 'I believe in love, but not monogamy,' he says plainly.
And this isn't a made up troll bullshit either! He actually stated this tripe, which makes it obvious that he is trying to politely say that he's a flaming homo slut!
Speaking about 'flaming,' who better to point out as a filthy chutney ferret than Slashdot's very own self-confessed pederast Jon Katz. Although an obvious deviant anagram cannot be found from his name, he has already confessed, nay boasted of the homosexual perversion of corrupting the innocence of young children. To quote from the article linked:
'I've got a rare kidney disease,' I told her. 'I have to go to the bathroom a lot. You can come with me if you want, but it takes a while. Is that okay with you? Do you want a note from my doctor?'
Is this why you were touching your penis in the cinema, Jon? And letting the other boys touch it too?
We should also point out that Jon Katz refers to himself as 'Slashdot's resident Gasbag.' Is there any more doubt? For those fortunate few who aren't aware of the list of homosexual terminology found inside the Linux 'Sauce Code,' a 'Gasbag' is a pervert who gains sexual gratification from having a thin straw inserted into his urethra (or to use the common parlance, 'piss-pipe'), then his homosexual lover blows firmly down the straw to inflate his scrotum. This is, of course, when he's not busy violating the dignity and copyright of posters to Slashdot by gathering together their postings and publishing them en masse to further his twisted and manipulative journalistic agenda.
Sick, disgusting antichristian perverts, the lot of them.
In addition, many of the Linux distributions (a 'distribution' is the most common way to spread the faggots' wares) are run by faggot groups. The Slackware distro is named after the 'Slack-wear' fags wear to allow easy access to the anus for sexual purposes. Furthermore, Slackware is a close anagram of claw arse, a reference to the homosexual practise of anal fisting. The Mandrake product is run by a group of French faggot satanists, and is named after the faggot nickname for the vibrator. It was also chosen because it is an anagram for dark amen and ram naked, which is what they do.
Another 'distro,' (abbrieviated as such because it sounds a bit like 'Disco,' which is where homosexuals preyed on young boys in the 1970s), is Debian, an anagram of in a bed, which could be considered innocent enough (after all, a bed is both where we sleep and pray), until we realise what other names Debian uses to describe their foul wares. 'Woody' is obvious enough, being a term for the erect male penis, glistening with pre-cum. But far sicker is the phrase 'Frozen Potato' that they use. This filthy term, again found in the secret homosexual 'Sauce Code,' refers to the solo homosexual practice of defecating into a clear polythene bag, shaping the turd into a crude approximation of the male phallus, then leaving it in the freezer overnight until it becomes solid. The practitioner then proceeds to push the frozen 'potato' up his own rectum, squeezing it in and out until his tight young balls erupt in a screaming orgasm.
And Red Hat is secret homo slang for the tip of a penis that is soaked in blood from a freshly violated underage ringpiece.
The fags have even invented special tools to aid their faggotry! For example, the 'supermount' tool was devised to allow deeper penetration, which is good for fags because it gives more pressure on the prostate gland. 'Automount' is used, on the other hand, because Linux users are all fat and gay, and need to mount each other automatically.
The depths of their depravity can be seen in their use of 'mount points.' These are, plainly speaking, the different points of penetration. The main one is obviously
/anus, but there are others. Militant fags even say 'there is no /opt mount point' because for these dirty perverts faggotry is not optional but a way of life.More evidence is in the fact that Linux users say how much they love `man`, even going so far as to say that all new Linux users (who are in fact just innocent heterosexuals indoctrinated by the gay propaganda) should try out `man`. In no other system do users boast of their frequent recourse to a man.
Other areas of the system also show Linux's inherit gayness. For example, people are often told of the 'FAQ,' but how many innocent heterosexual Windows users know what this actually means. The answer is shocking: Faggot Anal Quest: the voyage of discovery for newly converted fags!
Even the title 'Slashdot' originally referred to a homosexual practice. Slashdot of course refers to the popular gay practice of blood-letting. The Slashbots, of course are those super-zealous homosexuals who take this perversion to its extreme by ripping open their anuses, as seen on the site most popular with Slashdot users, the depraved work of Satan, http://www.eff.org/.
The editors of Slashdot also have homosexual names: 'Hemos' is obvious in itself, being one vowel away from 'Homos.' But even more sickening is 'Commander Taco' which sounds a bit like 'Commode in Taco,' filthy gay slang for a pair of spreadeagled buttocks that are caked with excrement. (The best form of lubrication, they insist.) Sometimes, these 'Taco Commodes' have special 'Salsa Sauce' (blood from a ruptured rectum) and 'Cheese' (rancid flakes of penis discharge) toppings. And to make it even worse, Slashdot runs on Apache!
The Apache server, whose use among fags is as prevalent as AIDS, is named after homosexual activity -- as everyone knows, popular faggot band, the Village People, featured an Apache Indian, and it is for him that this gay program is named.
And that's not forgetting the use of patches in the Linux fag world -- patches are used to make the anus accessible for repeated anal sex even after its rupture by a session of fisting.
To summarise: Linux is gay. 'Slash -- Dot' is the graphical description of the space between a young boy's scrotum and anus. And BeOS is for hermaphrodites and disabled 'stumpers.'
FEEDBACK
What worries me is how much you know about what gay people do. I'm scared I actually read this whole thing. I think this post is a good example of the negative effects of Internet usage on people. This person obviously has no social life anymore and had to result to writing something as stupid as this. And actually take the time to do it too. Although... I think it was satire.. blah.. it's early. -- Anonymous Coward, Slashdot
Well, the only reason I know all about this is because I had the misfortune to read the Linux 'Sauce code' once. Although publicised as the computer code needed to get Linux up and running on a computer (and haven't you always been worried about the phrase 'Monolithic Kernel'?), this foul document is actually a detailed and graphic description of every conceivable degrading perversion known to the human race, as well as a few of the major animal species. It has shocked and disturbed me, to the point of needing to shock and disturb the common man to warn them of the impending homo-calypse which threatens to engulf our planet.
You must work for the government. Trying to post the most obscene stuff in hopes that slashdot won't be able to continue or something, due to legal woes. If i ever see your ugly face, i'm going to stick my fireplace poker up your ass, after it's nice and hot, to weld shut that nasty gaping hole of yours. -- Anonymous Coward, Slashdot
Doesn't it give you a hard-on to imagine your thick strong poker ramming it's way up my most sacred of sphincters? You're beyond help, my friend, as the only thing you can imagine is the foul penetrative violation of another man. Are you sure you're not Eric Raymond? The government, being populated by limp-wristed liberals, could never stem the sickening tide of homosexual child molesting Linux advocacy. Hell, they've given NAMBLA free reign for years!
you really should post this logged in. i wish i could remember jebus's password, cuz i'd give it to you. -- mighty jebus, Slashdot
Thank you for your kind words of support. However, this document shall only ever be posted anonymously. This is because the 'Open Sauce' movement is a sham, proposing homoerotic cults of hero worshipping in the name of freedom. I speak for the common man. For any man who prefers the warm, enveloping velvet folds of a woman's vagina to the tight puckered ringpiece of a child. These men, being common, decent folk, don't have a say in the political hypocrisy that is Slashdot culture. I am the unknown liberator.
ROLF LAMO i hate linux FAGGOTS -- Anonymous Coward, Slashdot
We shouldn't hate them, we should pity them for the misguided fools they are... Fanatical Linux zeal-outs need to be herded into camps for re-education and subsequent rehabilitation into normal heterosexual society. This re-education shall be achieved by forcing them to watch repeats of Baywatch until the very mention of Pamela Anderson causes them to fill their pants with healthy heterosexual jism.
Actually, that's not at all how scrotal inflation works. I understand it involves injecting sterile saline solution into the scrotum. I've never tried this, but you can read how to do it safely in case you're interested. (Before you moderate this down, ask yourself honestly -- who are the real crazies -- people who do scrotal inflation, or people who pay $1000+ for a game console?) -- double_h, Slashdot
Well, it just goes to show that even the holy Linux 'sauce code' is riddled with bugs that need fixing. (The irony of Jon Katz not even being able to inflate his scrotum correctly has not been lost on me.) The Linux pervert elite already acknowledge this, with their queer slogan: 'Given enough arms, all rectums are shallow.' And anyway, the PS2 sucks major cock and isn't worth the money. Intellivision forever!
dude did u used to post on msnbc's nt bulletin board now that u are doing anti-gay posts u also need to start in with anti-black stuff too c u in church -- Anonymous Coward, Slashdot
For one thing, whilst Linux is a cavalcade of queer propaganda masquerading as the future of computing, NT is used by people who think nothing better of encasing their genitals in quick setting plaster then going to see a really dirty porno film, enjoying the restriction enforced onto them. Remember, a wasted arousal is a sin in the eyes of the Catholic church. Clearly, the only god-fearing Christian operating system in existence is CP/M -- The Christian Program Monitor. All computer users should immediately ask their local pastor to install this fine OS onto their systems. It is the only route to salvation.
Secondly, this message is for every man. Computers know no colour. Not only that, but one of the finest websites in the world is maintained by a Black Man . Now fuck off you racist donkey felcher.
And don't forget that slashdot was written in Perl, which is just too close to 'Pearl Necklace' for comfort.... oh wait; that's something all you heterosexuals do.... I can't help but wonder how much faster the trolls could do First-Posts on this site if it were redone in PHP... I could hand-type dynamic HTML pages faster than Perl can do them. -- phee, Slashdot
Although there is nothing unholy about the fine heterosexual act of ejaculating between a woman's breasts, squirting one's load up towards her neck and chin area, it should be noted that Perl (standing for Pansies Entering Rectums Locally) is also close to 'Pearl Monocle,' 'Pearl Nosering,' and the ubiquitous 'Pearl Enema.'
One scary thing about Perl is that it contains hidden homosexual messages. Take the following code: LWP::Simple -- It looks innocuous enough, doesn't it? But look at the line closely: There are two colons next to each other! As Larry 'Balls to the' Wall would openly admit in the Perl Documentation, Perl was designed from the ground up to indoctrinate it's programmers into performing unnatural sexual acts -- having two colons so closely together is clearly a reference to the perverse sickening act of 'colon kissing,' whereby two homosexual queers spread their buttocks wide, pressing their filthy torn sphincters together. They then share small round objects like marbles or golfballs by passing them from one rectum to another using muscle contraction alone. This is also referred to in programming 'circles' as 'Parameter Passing.'
And PHP stands for Perverted Homosexual Penetration. Didn't you know?
Thank you for your valuable input on this. I am sure you will be never forgotten. BTW: Did I mention that this could be useful in terraforming Mars? Mars rulaa. -- Eimernase, Slashdot
Well, I don't know about terraforming Mars, but I do know that homosexual Linux Advocates have been probing Uranus for years.
That's inspiring. Keep up the good work, AC. May God in his wisdom grant you the strength to bring the plain honest truth to this community, and make it pure again. Yours, Cerberus. -- Anonymous Coward, Slashdot
*sniff* That brings a tear to my eye. Thank you once more for your kind support. I have taken faith in the knowledge that I am doing the Good Lord's work, but it is encouraging to know that I am helping out the common man here.
However, I should be cautious about revealing your name 'Cerberus' on such a filthy den of depravity as Slashdot. It is a well known fact that the 'Kerberos' documentation from Microsoft is a detailed manual describing, in intimate, exacting detail, how to sexually penetrate a variety of unwilling canine animals; be they domesticated, wild, or mythical. Slashdot posters have taken great pleasure in illegally spreading this documentation far and wide, treating it as an 'extension' to the Linux 'Sauce Code,' for the sake of 'interoperability.' (The slang term they use for nonconsensual intercourse -- their favourite kind.)
In fact, sick twisted Linux deviants are known to have LAN parties, (Love of Anal Naughtiness, needless to say.), wherein they entice a stray dog, known as the 'Samba Mount,' into their homes. Up to four of these filth-sodden blasphemers against nature take turns to plunge their erect, throbbing, uncircumcised members, conkers-deep, into the rectum, mouth, and other fleshy orifices of the poor animal. Eventually, the 'Samba Mount' collapses due to 'overload,' and needs to be 'rebooted.' (i.e., kicked out into the street, and left to fend for itself.) Many Linux users boast about their 'uptime' in such situations.
Inspiring stuff! If only all trolls were this quality! -- Anonymous Coward, Slashdot
If only indeed. You can help our brave cause by moderating this message up as often as possible. I recommend '+1, Underrated,' as that will protect your precious Karma in Metamoderation. Only then can we break through the glass ceiling of Homosexual Slashdot Culture. Is it any wonder that the new version of Slashcode has been christened 'Bender'???
If we can get just one of these postings up to at least '+1,' then it will be archived forever! Others will learn of our struggle, and join with us in our battle for freedom!
It's pathetic you've spent so much time writing this. -- Anonymous Coward, Slashdot
I am compelled to document the foulness and carnal depravity that is Linux, in order that we may prepare ourselves for the great holy war that is to follow. It is my solemn duty to peel back the foreskin of ignorance and apply the wire brush of enlightenment.
As with any great open-source project, you need someone asking this question, so I'll do it. When the hell is version 2.0 going to be ready?!?! -- Anonymous Coward, Slashdot
I could make an arrogant, childish comment along the lines of 'Every time someone asks for 2.0, I won't release it for another 24 hours,' but the truth of the matter is that I'm quite nervous of releasing a 'number two,' as I can guarantee some filthy shit-slurping Linux pervert would want to suck it straight out of my anus before I've even had chance to wipe.
I desperately want to suck your monolithic kernel, you sexy hunk, you. -- Anonymous Coward, Slashdot
I sincerely hope you're Natalie Portman.
Dude, nothing on slashdot larger than 3 paragraphs is worth reading. Try to distill the message, whatever it was, and maybe I'll read it. As it is, I have to much open source software to write to waste even 10 seconds of precious time. 10 seconds is all its gonna take M$ to whoop Linux's ass. Vigilence is the price of Free (as in libre -- from the fine, frou frou French language) Software. Hack on fellow geeks, and remember: Friday is Bouillabaisse day except for heathens who do not believe that Jesus died for their sins. Those godless, oil drench, bearded sexist clowns can pull grits from their pantaloons (another fine, fine French word) and eat that. Anyway, try to keep your message focused and concise. For concision is the soul of derision. Way. -- Anonymous Coward, Slashdot
What the fuck?
I've read your gay conspiracy post version 1.3.0 and I must say I'm impressed. In particular, I appreciate how you have managed to squeeze in a healthy dose of the latent homosexuality you gay-bashing homos tend to be full of. Thank you again. -- Anonymous Coward, Slashdot
Well bugger me!
ooooh honey. how insecure are you!!! wann a little massage from deare bruci. love you -- Anonymous Coward, Slashdot
Fuck right off!
IMPORTANT: This message needs to be heard (Not HURD, which is an acronym for 'Huge Unclean Rectal Dilator') across the whole community, so it has been released into the Public Domain. You know, that licence that we all had before those homoerotic crypto-fascists came out with the GPL (Gay Penetration License) that is no more than an excuse to see who's got the biggest feces-encrusted cock. I would have put this up on Freshmeat, but that name is known to be a euphemism for the tight rump of a young boy.
Come to think of it, the whole concept of 'Source Control' unnerves me, because it sounds a bit like 'Sauce Control,' which is a description of the homosexual practice of holding the base of the cock shaft tightly upon the point of ejaculation, thus causing a build up of semenal fluid that is only released upon entry into an incision made into the base of the receiver's scrotum. And 'Open Sauce' is the act of ejaculating into another mans face or perhaps a biscuit to be shared later. Obviously, 'Closed Sauce' is the only Christian thing to do, as evidenced by the fact that it is what Cathedrals are all about.
Contributors: (although not to the eternal game of 'soggy biscuit' that open 'sauce' development has become) Anonymous Coward, Anonymous Coward, phee, Anonymous Coward, mighty jebus, Anonymous Coward, Anonymous Coward, double_h, Anonymous Coward, Eimernase, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward. Further contributions are welcome.
Current changes: This version sent to FreeWIPO by 'Bring BackATV' as plain text. Reformatted everything, added all links back in (that we could match from the previous version), many new ones (Slashbot bait links). Even more spelling fixed. Who wrote this thing, CmdrTaco himself?
Previous changes: Yet more changes added. Spelling fixed. Feedback added. Explanation of 'distro' system. 'Mount Point' syntax described. More filth regarding `man` and Slashdot. Yet more fucking spelling fixed. 'Fetchmail' uncovered further. More Slashbot baiting. Apache exposed. Distribution licence at foot of document.
ANUX -- A full Linux distribution... Up your ass!
-
Re:2,5 year to go?"2.0 is still a supported kernel release. If you have an issue, there's a maintainer out there supporting you."
An operating system is more than just a kernel. The bulk of the errata that Redhat puts out are for things other than the kernel. Skimming the errata for 7.3 turns up security fixes for xinetd, samba, the kernel, glibc, kerberos, and so forth. Making sure your kernel is up to date isn't going to help you if you get rooted via another means.
And even though the individual maintainers for things like xinetd and samba may still be doing their job, they may no longer be maintaining the fork that was used for a given Redhat distribution. Furthermore, even if they were maintaining it, you'd have to individually watch releases for the different packages you use. In short, you'd essentially be doing the work of a distribution maintainer.
-
Re:2,5 year to go?"I don't remember seeing a 'use before' date on any linux servers. Do you?"
I haven't seen a 'use before' date, but Linux distributions get cut off just the same. I've got a box at home running Redhat 5.2 that's no longer being supported. Here's the errata archive where they recommend upgrading to a supported product.
While Linux (and open source in general) does have the advantage that someone can always support it, that doesn't mean that someone is supporting it -- especially when the package in question has been superceded by a number of later versions. There's always the option of hiring a trained individual to handle watching bug lists and backporting necessary fixes, but the pricetag on that would make Windows mandatory upgrades cheap in comparison.
-
The Final Target!this is the sixth text revision done on 04-11-2002.
dear reader the gnome armageddon has started,
first of all i want to clarify that this text was meant to be a source of information otherwise i wouldn't have spent so much time into writing it. belive me it took me a couple of days writing this text in a foreign language. even if you don't care at all for gnome, you may find some interesting information within this text that you like to read. please try to understand my points even if it's hard sometimes, otherwise you wake up one day and feel the need to switch to a different operating system.
on the following lines i'm trying to give you a little insight of the gnome community. the things that are going on in the back, the information that could be worth talking and thinking about.
many of us like the gnome desktop and some of us were following it since the beginning. gnome is a promising project because it's mostly written in C, easy to use, configurable and therefore fits perfectly into the philosophy of u*nix. only to name some of its advantages.
unfortunately these advantages changed with the recently new released version of gnome. the core development team somehow got the idea of targeting gnome to a complete different direction of users. the so called corporate desktop user. in other words they're targeting people that aren't familiar or experienced with desktop environments. usually business oriented people who are willing to pay money for getting gnome on their computers.
having this new target in mind, the core development team mostly under contract by companies like redhat , ximian and sun decided to simplify the desktop as much as even possible by removing all its flexibility in favor of an easy clean simple interface to not confuse their new possible customers. so far the idea of a clean easy to use desktop is honourable.
some of the new ideas, features and implementations such as gconf , an evil windows registry like system, new ordering of buttons and dialogs, the removal of 90%-95% of all visible preferences from the control center and applications, the new direction that gnome leads and the attitude of the core development team made a lot of users really unhappy. these are only a couple of examples and the list can easily be expanded but for now this is enough. now let me try to get deeper into these aspects.
you may imagine that users got really frustrated because their beloved gnome desktop matured into something they didn't want. during the time, the frustration of a not less amount of people increased. more , more and more emails arrived on the gnome mailinglists where users tried to explain their concerns, frustrations and the leading target of GNOME.
but the core development team of gnome don't give a damn about what their users are thinking or wanting and most of the time they come up with their standard purl. the reply they give is mostly the same. users should either go and 'file a bug' at bugzilla or the user mails are being turned so far that at the end they sound like being trolls or the user feedback is simply not wanted. whatever happens the answers aren't really satisfying for the user. even constructive feedback isn't appreciated.
if you gonna think about this for a minute then things gonna harden that they are directing into the commercial area. the core development team actually don't care for the complaining home user. it's more important for them to reach the customers with the cash. it seems that this has been told to them by the company leaders. everything about gnome has been decided already, a way back or direct communication isn't possible. don't get trapped by sentences like 'we listen to our users'. they listen to you - yes, to make funny silly jokes about you afterwards.
i thought that everything was build up on friendship, build on programming for fun, build on understanding each other. but the reality looks like it's all for the big money. the cash is what matters everything else is a lie and a dream. time for people to wake up.
not long ago they threw one of the most important long year core developer martin baulig out of team. a guy who worked really hard on getting gnome into the right direction. a nice friendly person who put all his time into gnome. but narrow minded gnome elites such as havoc pennington were responsible that he left the gnome project. the trouble and the pressure that was put on him was to much.
with the new gnome desktop a lot of user interface changes happened such as button reordering . needless to say that this confuse people who are used to the 'right' button ordering for ages. even our fellow linux guru alan cox wasn't thrilled about this idea. but the gnome elites such as havoc pennington, seth nickell, calum benson and dave bordoley knew it better. why following the road of any other desktop that exists ? why not doing something that don't confuse their users and still stay usable ? well it seems to be too easy. gnome needs to be different than anything else so they changed the button order which was one of the reasons that users became unhappy. they said that there was a hard fight about this and the decision was made to change the buttons. but i belive they simply copied the behaviour of macos because most of the gnome developers use a macintosh as either laptop or desktop. sad that they forgot to keep in mind that users tend to mix applications and that this will lead into weird button searching and clicking.
but as if this wasn't enough the same people decided that the new gnome human interface guides were the ultima non plus ultra in human interface guides. the announcement contained informations that the kde usability people got initiated into it. unfortunately the kde people heard about it the first time when seth nickell went to the kde mailinglist which happened after the announcement. you can imagine that they got highly pissed off about this attitude. you can read more on this link . to summarize it, the kde people clarified that gnome should care for their own business.
the problem that came with the new interface guides was, that every little gnome hacker started to become an user interface expert over night. a lot of gnome programs that we like to use matured into a disaster over night. hackers that never programmed correctly for their life started to blindly follow the hype of simplification. for an example look what happened to galeon's interface (pay attention for the last paragraph). even philip langdale a long year galeon hacker got highly indignant by the target that gnome leads and wrote this email to the galeon mailinglist.
here another reason why users became angry. the elite assumes, that the user knows nothing about their system. you find a couple of heavily insulting mails on their mailing lists containing sentences like the quoted ones.
"the user don't know what a window manager is",
"the user don't know what themes are",
"the user don't know what a homedir is",
"the user can't compile a kernel",
"the user don't want to customize their desktop",
"the user shouldn't see preferences which purpose they don't know"
you may imagine that a lot of people are being offended by such lines because it's exactly these gnome users who are meant by these phrases. to read more such lines on the gnome mailinglists, simply click on this link and grep in their archives. be said that most of these sentences are coming from havoc pennington.
such evil practices shouldn't be tolerated by the users and need to be fighted. u*nix users aren't stupid people. who actually gave havoc pennington the rights to decide what the user wants and what not ? various users told him that people who use a u*nix like system are well aware of their capabilities dealing with such a complex system. there's a reason why people are switching from alternative operating systems. they want to learn, they want to use the full power of the system, they want to change everything they like.
to top all this, look at the future plans of nautilus . the current maintainers got the idea of changing the whole nautilus concepts into an object oriented user interface design. you may be highly interested in reading the exact words of alex larsson's vision for nautilus' future direction by clicking on this link .
to summarize it, it's assumed that the user don't need to deal with his homedir or his whole filesystem because it may confuse him or because he don't understand it. the new concepts of nautilus should be that the user deal with symbols in the nautilus view. e.g. you get a cdrom symbol and by clicking on it you see the directory of your cdrom, you get a photo symbol and by clicking on it you get a list of all your pr0n pictures, you get a music symbol and by clicking on it you get a list of all your mp3's. you don't know where all these files are located because you don't deal with the bottom layer of your homedir or filesystem anymore as mentioned earlier.
the question is why are people that know nothing about their users, that know nothing about correct user interface design destroying gnome ? the users don't deserve all this specially those that backed gnome for all the years. even sun threw a bunch of so called user interface experts together and have them work on gnome. don't forget that sun are the creators of the common desktop environment . we don't need another cde clone named gnome. even havoc pennington author of the good user interfaces text isn't able to get his own written software following his rules.
not long ago there was an report about the 'two captains of nautilus' where the reporter (uraeus a gnome contributor himself) reported alexander larsson and david camp. you may imagine that such a report can't be taken serious because it's done by their own people. we here have a saying that sounds like this 'one crow doesn't hack the eye of another crow out'. now you can click on this link and read more. it may be interesting to read the replies from various users all over the globe of what they think about gnome and nautilus in general (please pay attention to the listed ip's there). another nice and informative reading can be found by clicking on this link .
the fileselector problem was a long discussed issue in the gnome community. finally they came to an solution for this and have decided to go for this ugly fileselector instead going for this one which was developed by a free volunteer for a long time and in general looks and behaves better.
most users have no problems with the idea of keeping things simple and clean. removing some not needed preferences was indeed a good idea but it doesn't stop. people started to remove everything from their apps. you're forced to use dubious programs like gconf-editor which basically works like the windows registry editor, to tweak uncommented preferences. i don't think that this is an advantage. even the possibility to tweak preferences with an editor was taken away with that ugly implementation of gconf. all your preferences are stored in a directory tree with an unknown amount of *.xml files. even if you delete programs their keys are still remaining orphaned in these trees and finding them is like playing trivia. at the end it's worth a discussion if a system driven by a single home user needs such a registry like system. we didn't need such a system for over 30 years but the gnome development team got the idea copying one of the most retarded systems from windows to u*nix. not to mention that the copy is more retarded than the original.
it's a shame to see how such a nice desktop got thrown into the trash by such people. but there is a lot more behind the scenes that i don't know about. everything around gnome is a big marketing strategy. poor people are working the hell out of gnome for nothing and companies such as those mentioned above are getting the big cash. for sure you could say - go and fork gnome - but seriously how can you go and fork gnome ? such a big project which needs a bunch of people to keep the code alive and compatible. well you know it's all about open source the code is signed under the gnu/gpl or gnu/lgpl, you can't own it. even the companies are aware of this. but if you can't own the code - go and hire their developers. you can direct them like puppets in any direction that you - as company - like. exactly this is happening with gnome.
well you could easily come up and tell me to simply not use gnome and let them do whatever they like. well, you are right with that but things are more complicated nowadays. gnome is influencing a lot of third party projects such as xfree86 which recently added a lot of gnome components into their cvs repository. please know that with the next coming xfree86 version you get a lot of gnome components without even knowing it. code like, gnome-xml , pkgconfig , fontconfig , xcursor and xft2 were mainly written by people who're heavily involved into gnome development. also the gimp is maturing more and more into getting the look and feel of a native gnome application. the cvs version of the gimp has a lot of gnome pixmaps inside and they are heavily working on integrate the gimp into gnome. if not today but the direction is sure and i fear the day this gonna happen.
it's ok that these things exist and it's ok to see xfree86 and the gimp are beeing hacked on. but please think about the people that don't like or use gnome. what about them ? why force them to have gnome components installed on their systems ? why can't gnome go the same way that kde went e.g. doing their own stuff without infecting other projects like aids. seeing more and more libraries and applications that were in no way related to gnome jumping on the pkgconfig boat which's really not needed. look what will happen to solaris, the world famous operating system on u*nix used by big companies and long years experts. they really plan to replace cde with gnome. i know that cde wasn't the best invention of desktops but it rarely crashed and it fits far better into the philosophy of xfree86 with their configuration system than gnome. you know the good old way having your settings defined with
.xdefaults and all nice default configurations are going into /etc/x11/app-defaults/ and so on. understandable that the good old way may be blocking the future of applications for multiusersystems - but why must it have to be a windows registry like system that replaces future configuration ?well to come to an end i personally don't like many of this stuff. i can't stand the button reordering, i don't like the gconf system and even more i don't like the commercial outsourcing of gnome and the bad influence that gnome has on other applications. the bad attitude of some gnome developers is another story since we are all different reacting humans. luckily there are people sharing some of my thoughts otherwise i wouldn't be able to proof my text with so many links. even amongst the gnome developers there are silent voices of people that hate many of these decisions and silently use something else. right now if you checkout the gnome cvs repository every day you find out that the whole gnome development seemed to came to an halt. the contributions to their cvs are poor. while projects such as kde are reaching easily 10-20k commits per month - gnome is getting around 1-2k per month on it's best times. it really looks like the situation of gnome is unclear so it would be better to have it not influence so much other programs or at the end we deal with an disaster.
now i hope this text was informative for you. i hope that you start to think about the situation and the global direction. the situation of gnome is unclear, their target is groggy too since i can't belive that the users that they are targeting ever heard of u*nix or linux. they plan to get out of the 0.05% desktop niche but this will for sure not happen if they continue their current direction and their bad ugly attitude.
-
security company?I suppose having your every move on the web tracked and monitored by some comercial company over windows is considered secure by some. Next time these folks want security and a faster connection software, might I recomend:
This would make the world a better place, even if it could not be used to forcast the next great depresion.
-
Re:MSs Place in the Market
You're right, Linux is not a company. Linux is a product that other companies like Redhat and IBM are trying to push into the Enterprise server space as well as the desktop space.
To the people here on slashdot Linux is just something that "gets adopted," because we have free time to play around with new technologies. However, when IBM / Redhat go talk to companies who are trying to decide on a platform to base their business on, such as this bank, it very much is a product that their respective marketting departments are trying to "push" into this space, just the same way Microsoft is trying to sell Windows in this space.
See Redhat's Enterprise Solutions page.
-
Re:how long will it be...
Although I am an avid supporter of linux, I have alot of trouble keeping up with the latest version of my principal programs as well as the ever-changing kernal.
Then you would be aware that Linux is the kernel and nothing more. In this instance, your service pack is patch-2.4.20.bz2, and that's it.
installing service packs in windows2000/XP, it updated the kernal and main programs like IE and media player all at once
Here's the thing: Linux doesn't have programs tied into the operating system that much. You could have a running Linux system without using a single GNU tool. As such, proposing service packs for Linux is nonsensical.
but I won't begin to start using [Linux] as my primary OS untill it has service packs.
Linux itself has service packs. Your distribution, on the other hand, is responsible for the rest of the pieces of software on your computer, and each distro has a different means of staying current. RedHat has up2date, Debian has 'apt-get update', and Gentoo has 'emerge -u'. Take your pick. -
I tell you what...
I run ClarkConnect on my firewall. Redhat, Debian, Gentoo, Lunar and Slackware on my *personal* box. Lycoris on my wife's box (no humorous responses please).
While the individual merits of each distro can be argued to no end, I do have to note that only Lycoris and ClarkConnect (Based om RH 7.2) worked perfectly out of the box. (Inasmuch as Windoze does)
Noting that, I would say that if you want to learn the differences between the distros, you should first learn how to multi-boot your machine. The greatest learning experience for me has been to have a working distro available at all times, while I'm trying to get a new (to me) distro working that I'm not familiar with. (Such as linux-from-scratch)
Anyway, I hope I haven't strayed too far from the subject, but I had to add my $.02.
In short, IMHO, if you are a complete newbie, learn how to multi-boot, install Lycoris, Mandrake and Debian. (or go to DistroWatch and pick a couple.) Graduate from one to the next while keeping your working distro intact. Then, Paraphrasing another post I read "apt-get when you finally get it together" - lol.
Happy Thanksgiving!
-
Thinking along these linesI agree that something like this is needed. I could not think of a good name but something like Community Source might work. I had even started writing a proposal for it with a view towards creating a site to extoll the idea....
The benefits of Open Source or Free software to its users are undeniable. If the software has a bug, or the software does not do something you want it to do, you can change it. There are many advantages, and they have been explained at length by various people. If you are going to be using software, you are definitely better off if you have access to the source code.
Trust
The fundamental difference between open source software and closed source software is the level of trust required. For a business to use closed source software, the level of trust required is enormous. It is not simply a question of whether the money spent purchasing the software is a good investment. The time invested using the software is far more significant. Almost inevitably your own business information becomes tied up in a format that is specific to the software you are using. In order to buy software from a closed source company, you have to take the following on trust:
- They have not left gaping security holes in the code.
- They will fix bugs in a timely manner.
- They will eventually add the features you want.
- They are not using your computing resources to do things which are not in your interest.
- They will not increase the price unreasonably once you depend on them.
- They will not go bust.
Business Models Having access to the source code makes good sense to the users. However the business case for the software vendor is far less convincing. In fact, the dangers of closed source from the user's perspective can be considered opportunities from the vendor's perspective.
The open source foundation proposes "4 ways to win" which is reproduced here: Four Ways To Win
Now for a higher-level, investor's point of view. There are at least four known business models for making money with open source:
- Support Sellers (otherwise known as "Give Away the Recipe, Open A Restaurant"): In this model, you (effectively) give away the software product, but sell distribution, branding, and after-sale service. This is what (for example) Red Hat does.
- Loss Leader: In this model, you give away open-source as a loss-leader and market positioner for closed software. This is what Netscape is doing.
- Widget Frosting : In this model, a hardware company (for which software is a necessary adjunct but strictly a cost rather than profit center) goes open-source in order to get better drivers and interface tools cheaper. Silicon Graphics, for example, supports and ships Samba.
- Accessorizing: Selling accessories books, compatible hardware, complete systems with open-source software pre-installed. It's easy to trivialize this (open-source T-shirts, coffee mugs, Linux penguin dolls) but at least the books and hardware underly some clear successes: O'Reilly Associates, SSC, and VA Research are among them.
In fact, the number of companies that have had success with any of these models is miniscule. This is hardly surprising, they are simply not very good business models for software companies.
Taking each in turn... Selling Support The better documented and more reliable the product is, the less support it needs. A business model where the more perfect your product, the less money you can make has got something fundamentally wrong with it. Loss Leader The very fact that this can be advanced as a viable business model for OpenSource shows desperation. What it comes down to is an admission that the best way to make money from software is by selling it. Widget Frosting This makes perfect sense if you are a hardware company, or when the software is a side issue. However, its no use at all for a business whose main product is software. Accessorizing Selling accessories is fine, but there is no pressing need to actually develop the software when one is in the accessories business.
There are of course other business models for Open Source. For instance, the one adopted by the Perl foundation and several others is begging. This is not a business model that many companies would find appealing though.
The basic problem is that for a business whose primary function is to make software, then the primary reward has to come from selling the software. We need a business model that actually works and we have one, it's called capitalism. It works like this: make something that people want and sell it to them. This model works for software too, and there is no reason why this model cannot work even when source code is available. Closed source vendors are relying on something a little closer to the business model of a heroin pusher. It starts off like capitalism, but there is the added feature that the user gets addicted and has to carry on buying the same thing even if he does not really want to. The more he uses the same vendor, the more reliant he is upon it.
The Solution Community software is software where the vendor can be paid a fair price for the software he creates, but where the buyer does not end up in a similar position to a junkie.
Community Source is software that guarantees the following:
- The right to see what the software is doing, ie access to unobfuscated source code.
- The right to add enhancements.
- The right to fix bugs.
- The right to sell his enhancements to other companies. This does not mean the right to the sell software without the original vendor receiving any money. The buyer still needs a license from the original vendor, but he does not have to rely on a single vendor for upgrades and enhancements.
- The right to buy enhanced versions from 3rd parties.
-
It is obvious who the leader is
It is obvious that Microsoft has been the fantastic driving force behind software innovation over the past two decades. Their uncanny ability to feel out new markets and met the needs of their customers with cost effective, friendly licensed, quality software has forced all other developers to increase the quality of their products.
-
Re:Linus' Linux is way behind...
Nope, you're wrong. Linux version refers to the Kernel version. Redhat Version number refers to their distribution. Redhat is currently using Kernel 2.4.18. (See Here)
It is Redhat that is behind not Linus. Secondly, you wouldn't expect Redhat to release the latest kernel with their package because they need to be able to test and support it before they package it. -
XML Configuration files please!
A while back I ran into a rather stupid bug in RedHat. After some debugging I figured out the problem was due to a "description" field missing from one of the config files (/boot/module-info).
At the top of this file in the "comments" was a brief note about the format that this file was supposed to follow. According to this, there should never have been an entry without a description field. The code for one of the GUI programs ASS-U-MEd this would be the case, didn't do any checking and of course crapped out when it found a malformed entry (someone obviously hadn't read the format info in the comments when the made changes).
Now of course the code should have been robust enough to handle such and error, but ideally there would have been some checking of the config file to determine whether the file actually conformed to the listed format rules before it was sent out into production.
These config files are where XML's strengths can be quite useful. If this file had a formal schema definition and was created in XML, it would be quite easy to check this config file for correctness (syntactical at least) as part of the build process. The code which reads these files could be changed to use a simple XML parser to read through it, or hell you could even write an XSLT transform to turn it into the "non-XML" format (i.e. use the XML for developing the file only) and not have to change any of the existing code that reads that file!
There's been a big push towards XML configuration files in some segments of the industry (the Java J2EE camp for example). I for one hope this trend will continue. -
Re:Hmmmm
Certainly Sun occupies a preeminent position as a certifier of Java technologies, but other companies can offer the guarantees that businesses seek - IBM and BEA, for example.
For example, this Redhat press release covers the certification of the JRockit JVM on Redhat 8 by BEA. This is targeted at the corporate audience, and makes no mention of Sun - their role was one step removed in that they certified JRockit as a J2SE implementation. -
Re:Joke if you may, Timothy
The hell?
Yes, Linux is harder than Windows at the moment. But it's not the epic quest you make it out to be. For 90% of the software I use, I don't bother with tarballs and compiling anymore. I just grab an RPM and install it and am on my way. For all of the traditional "desktop" software I use (spreadsheet, word processor, personal finance software, web browser, email client, I simply rely on what comes with Red Hat Linux and Ximian Desktop. Everyone once in a while I run Red Carpet, select all of the updates and hit "Next." Amazingly easy, freeing me up to do more interesting things (like writing new software).
You bizarrely claim that 99.1% of people who are attracted to free software and are willing to accept that is is harder to use end up giving up. If the above is "too hard", then they weren't really ready for something harder to use than Windows. (Heck, they probably aren't ready for something as exciting as installing Windows from scratch.) You're making numbers up and you know it.
The figures prove what? That an operating system and supporting software developed by people with a fraction of the budget and advertising of Apple are successfully gaining market share? That it's impossible for any operating system (even the heavily hyped MacOS X) to make serious inroads against the Microsoft monopoly? You can't prove anything with the figures other than Microsoft owns the game, Apple keeps a sizable minority, and Linux slowly grows. We can't know that if the reason Linux has such a small share is because people are trapped by the Microsoft monopoly, aren't aware of Linux due to lack of advertising, have actually tried Linux but found it too difficult, aren't interesting in exploring new options because their system shipped with Windows and works fine for now.
Your parents run Windows for a reason, and trust me -- it's not because it looks that incredible. It's just easier to use, and easier to get support for. End of story.
Bwuhuhahahahaha! Sure. Fine. Not.
My parents loath Microsoft and Windows. The "support" they've gotten is entirely "try rebooting" and "try reinstalling". My dad recently spent a weekend fighting with various drivers unsuccessfully. My dad purchases a great deal of maintenance software to try and keep his system stable. My mom struggles to keep her old games working under new Windows operating systems. (And before you complain, "but it's third party publishers that are the problem", the same is true for Linux. If you stick with your distribution's publisher (and perhaps Ximian), you'll find you get a very easy to install and use system that's stable.)
My parents don't use Windows because they like it or that they feel it's easy to use. They use Windows because it's all they've ever known.
Finally, yes, IRC is full of assholes. Duh. Big shock. It turns out that most of IRC is full of assholes, including the non-Linux channels. The Windows support channels are full of assholes. The music dicussion channels are full of assholes. The abuse support channels are full of assholes. It's the nature of anonymous communication. Fortunately, I haven't bothered looking at IRC for a long time. When I run into problems I check the mailing list archives and the FAQ. If I don't find details, then a politely phrased query to a mailing list provides useful answers. And I only ever need go to this trouble when I chose to be daring and try software that didn't come with my distribution. And only if the software has problems (less than 1% of the time). This is an exceptional case, not the general one (unless your general case involves lots of trying experimental software).