I love the hogwash that comes from the airline industry. They tell you that you cannot use your cellphone in the plane because it can interfere with their navigation equipment. I doubt that can actually happen, by the way. They probably tell you that so you'll use that phone built into the seat in front of you, that costs Lord only knows how much per minute, instead of your own phone, because you'll be afraid to get killed by screwing up their nav stuff.
And now, at the same time, they say OK to WiFi, which in my opinion is much more dangerous.
For those geeks who think a computer needs eight dual-core processors, 64 gigs of RAM, and 10 gigs of OS and software code to read email, I'd like to tell you a bit about the good ol' days.
Amazing things can be done with a few measly logic gates and a few machine code instructions. Heck, you think a webserver made of 200 TTL chips is crazy? Check this out. About halfway down the page is a description of the R-741 computer, a minicomputer built in the early '70's to run robotic machinery. I doubt it even contains half as many as 200 TTL chips, and running at 4 MHz on a custom instruction set, this thing's operating system, coming in at a whopping 21k, runs all the functions of digital and analog I/O for robotic machinery--under a complete language interpreter! And it's faster at some functions than many modern computers, given that its electronics, instruction set, and software were all designed so tightly that not a single chip or wire was used unnecessarily, and not a single clock cycle was wasted. Today's general purpose machines, with their zillions of logic gates and gigabytes of memory, are weighed down by layers upon layers of stuff.
It is truly refreshing (and a priviledge, I suppose) to work with this R-741 machine. And it's quite refreshing to see someone build a webserver in a similar style. We need more of this type of ingenuity, and less mountains of bloated code that work too hard to do things that are basically very simple.
All of the most amazing things are invented in Israel. It's almost cliche now! Just like launches to space. Used to be a spectacle for the whole world. Now, who cares? Same for Israel and technology. Nobody pays attention when some new whiz-bang thing like this comes from the land of Jesus.
Maybe because the biggest miracle of all is that this tiny democracy can even exist when literally surrounded by so many enemies that wish for its destruction. Drives me nuts how people can be so shortsighted.
First, Apple switches to Intel, and now, equally shocking: Debian Sarge is released! Hell has officially frozen over!
Oh my Lord! Two miracles come to pass in the same day. This means the Second Coming is upon us! But watch out, because Jesus said, "Another will come in my name and him you will receive."
By the way, I'd like to introduce myself. I'm Jesus H. Christ.
This is a very smart system. The Samba team uses something very similar. The key to finding regressions with this method is to create tests for every piece of functionality, and to integrate it with the rest of the testing suite, so that each function of the kernel will be continuously tested. For new features, it is preferable to create these tests as the features are being coded. For existing millions of lines of code, it is necessary for some brave souls to go in and create these tests.
I hope they are using code from the Linux testing suite. That piece of work has already formed a nice set of tests. Also, I hope that the kernel is automatically built with many different combinations of options. And with time, I hope this will become better. The more tests, with the more hardware configurations, with the more kernel configurations, with the more types of input data (including many imaginative forms of incorrect input data to test that the kernel handles it gracefully and thwarts attacks based on such methods), the better quality we will have in the kernel, and it is likely that Linux will be unmatched in quality, stability, efficiency (well, maybe not efficiency necessarily), and long uptimes.
I can't blame Microsoft for phasing out Windows 2000. After all, synergies between killer applications empower emerging stewards to architect ubiquitous initiatives, harness revolutionary convergence, and engineer bleeding-edge solutions to recontextualize turn-key markets.
Growing open-source deliverables harness global interfaces to unleash holistic partnerships. Strategic content drives leading-edge web services to deliver efficient networks while syndicating one-to-one mindshare. When bleeding-edge content architects maximize seamless schemas to deliver robust web services, extensible infrastructures cultivate mission-critical functionalities. Best-of-breed communities target proactive enterprise paradigms while 24/7 methodologies reintermediate visionary content. By leveraging vertical synergies, content providers syndicate one-to-one cross-platform convergence.
Microsoft's plans include optimizing their internal operations to speed up delivery of Longtooth. Sources whom I consider accurate have told me that despite Microsoft's claims that Longtooth will be released by 2006 or 2007, the planned release date is actually late in 2019. Microsoft's secret goals for this version are:
To reduce the user's perception of the complexity of Windows.
To gain increased security from emerging threats, such as viruses, worms, spam, spyware, adware, malware, hackers, and phreakers, among others.
Microsoft will accomplish these goals through a variety of changes. First, Longtooth will no longer be based on the Windows NT design philosophy, as were Windows 2000 and XP. Instead, Microsoft will release MS-DOS 9.0 2003, a 64-bit multithreaded DOS written in VisualBASIC.Net, and Windows Longtooth will run on top of that. Also, Longtooth will contain more code changes than any previous version of Windows, both in the number of changed source lines of code (SLOCs) and in the percentage of the total Windows codebase changed. Tremendous numbers of new features are being implemented in completely new code.
More importantly, Microsoft employees are combing through the codebase, in a relentless search for code that is mature, stabilized, and proven. This search has proved difficult, but when found, such code will be marked for reimplementation. I'm told that most of this code will be reimplemented in VisualBASIC.NET, even if the prior version was written in another language, such as C or C++. Programmers making the new VisualBasic.NET code are not allowed to look at the code that already exists, so that fixes to known issues will not be known until well after the software is deployed to millions of users.
The reason for these changes is simple: Study after study conducted by Microsoft has proven that security through obscurity is the only way to go, especially in an operating system deployed to millions of users, with many instances running mission critical applications in finance, industry, government, and other sectors. Microsoft has identified that viruses, worms, spam, spyware, adware, malware, hackers, and phreakers are able to compromise Windows security because vulnerabilities in the code are known. By changing much of the codebase, especially the stablest and most proven parts, Microsoft will thwart the efforts of malicious programmers, as it will take time for them to find the new vulnerabilities in the unknown code.
To meet Microsoft's first goal of reducing the user's perception of the complexity of Windows, Microsoft will integrate a new technology, dubbed Microsoft Windows User Simplicity And Security Manager 2003, into Longtooth. This technology will hide all configuration settings from the user. All settings will be completely automatic, and the user will have no need to know or care what is under the hood. In reality, Longtooth will be the most complex version of Windows yet, with thousands of configuration settings controlling nearly every function of the operating system. The settings will be produced by discove
Simply write me a check for the entire amount, and I will see to it that it will be put to good use. You can rest assured that many a free software project will benefit greatly if a check is written to me and mailed right away.
Please make payable and mail to:
Rice Burners Suck 12345 South Rodder Street Chevy Rocks, Florida 54321 USA
So many millions of dollars are being invested in locating water on Mars. Instead of wasting this money in this fashion, why don't they simply devise a system to transport massive amounts of water over there?
In fact, this is what they should do: Build a gigantic ship with a hull large enough to contain billions and billions of gallons of water. Then, pump water from the oceans through a desalination plant and right into this ship. The water would be transported to Mars this way. Another ship would carry seeds, plants, and soil. All of this would be taken to the most opportune spot and placed there. Perhaps a crater could be filled with the water and then the soil and plants could be planted around it. After several hundred missions like this, there could be quite a number of lakes on Mars, with lots of plant life around them, which would create more oxygen in the air and allow a working natural cycle to begin.
This would have added benefits. There are some (misinformed) scientists on this planet who believe that global warming will cause ice caps to melt, which will raise the level of the oceans and cover the entire earth. Kind of like what's on the third page of Genesis, but then no Slashdotter reads the Holy Bible. Anyway, by removing a lot of water from Earth and using it to create lakes on Mars, we would eliminate the risk of drowning in the waters (which won't happen), the result of an overheating world (which also won't happen), and we would also create many square miles of land rich in nutrients previously untapped, which could be used to grow healthy foods for those who are starving (which is more a result of political problems in third world countries than a result of lack of land space to grow food).
This would be worth millions of dollars in investment.
That way I can sneak the appropriate code onto every web site I build, until people get so sick of IE running slow and swapping like mad that they switch to Firefox.
You are a good and righteous person.
By leveraging innovative technologies, content providers streamline compelling enterprise solutions.
As part of the transition, the Fedora open source project will transfer development work and copyright ownership of contributed code to the foundation but Red Hat will continue to provide substantial financial and engineering support.
Reminds me of the time that Wind River Systems "spun off" the support they initially gave to the FreeBSD project after buying out Walnut Creek CD-ROM. The community had sent them a number of questions, and their answer was something along the lines of, "We will continue to encourage emerging stewards of the FreeBSD project," along with paragraph after paragraph of additional meaningless duckspeak, in the same form as, "By leveraging innovative technologies, content providers streamline compelling enterprise solutions."
What I'm essentially trying to say, then, is that Red Hat will, for a short time, continue to give equal amounts of support to the Fedora project. But this will slowly wane, as I believe has been Red Hat's plan all along. That is why the name was changed from Red Hat Linux to Fedora Core. They will eventually turn as many components of their so-called Enterprise version of Linux into closed source, proprietary software, in the same style as most of the UNIX OSes out there. The kernel will continue to adhere to the GPL, as will other major components (think Samba, Apache, etc.) with their respective licenses. But I think that nearly all Red Hat development will be in the closed source arena.
This way, Red Hat will have achieved the following interesting goal: They are widely known as the de facto Linux standard, because they were open source for years and provided a lot to the community. But on the other hand, they will be able to make a lot of money on their Enterprise stuff, because most of it will be proprietary and the technologies therein will be unavailable in Fedora or in any other Linux for that matter. Think Mac OS X. Red Hat Enterprise Linux will be about as open source as Apple's software... Sure, hundreds of thousands of lines of code are open source. But the really good stuff, the really innovative stuff, the new stuff that no other OS has is proprietary, closed source, binary, and locked out of view.
This, I believe, is Red Hat's plan. I don't know about you, but I'm putting on my tin-foil hat.
I don't understand why we need these newfangled transistor thingies anyway. Why, when I was your age, logic was handled using relays. Why, it took only eleven minutes for our computer, here at Building B, to add two numbers, and that includes the time it took to enter the numbers. All these newfangled transistor contraptions don't do a darn thing, I tell ya. Yes sir, I swear it, they're unnecessary.
I have a better idea. There should be a worldwide law that states that all websites must make every effort possible to crash MSIE, but run well on all other browsers. The reasoning is that by eliminating MSIE, much of the risk associated with cybercrime will disappear with it.
Europe should put all of its resources into the production and installation of open source software in all areas of government, industry, and commerce. Europe must also take active measures to ensure that closed source software will be illegal throughout the continent. People should not be allowed to make, use, sell, or otherwise traffic in closed source software.
This is the most important issue in the entire continent, and must be addressed immediately. If Europe fails to properly embrace open source software, it will surely spell disaster for the entire continent, all the countries thereof, and all people living in Europe.
Open source software is the solution to all of the world's problems.
The US Department of Health and Human Services (HHS)...
No, no, no, you've got it all wrong. It's the GNU/US Department of Health and Human Services (GNU/HHS). I'm going to report this to the Free Software Foundation's Department of Making Sure GNU Appears Anywhere GNU/Linux is Used (GNU/RMS).
I almost thought the title of this article was, "Longtooth Drops My Panties." That would have been a much better and more informative article.
For immediate release: Mikrosoft Corporation (NASDAQ: M5FT) today announced new technology, dubbed Pantydropper 2003 Professional Server. By leveraging innovative technologies, content providers streamline compelling enterprise solutions. The software is touted as being the only solution on the enterprise market currently that can drop one's panties.
Gill Bates, Chief Software Architect at Mikrosoft, stated, "This is one I've been trying to figure out ever since my days as a pimply-faced teenaged geek. Now, at the age of 51, I finally have the solution to all of my problems."
OH NO!!! I voted for BUSH, TWICE, once in 2000, one in 2004. He is a great president, despite what that idiot that you said I sound like would have you believe. The war in Iraq is a just and righteous war. Go Bush!
There was another article I read somewhere... it was a system designed to increase convenience, decrease the chance of theft or credit card fraud...
Basically, it was a system to use giant limestone wheels from the island of Yap as credit cards. The giant wheels are difficult to counterfeit, and therefore will prevent theft through credit card fraud. These will be called credit rocks, rather than credit cards, and will take a crane to move, but many retailers believe that it will provide consumers with the added convenience that because the stones will be so difficult to move, they won't charge as much on their credit rocks as they do on their credit cards, and therefore we will have fewer people in debt.
...the importance, significance, and obviousness of Microsoft's ongoing evil ploy, funded by "They" who wish to take over the world. This is what you'll see in Blacktooth, Microsoft's codename for Longtooth's successor: It won't just say "Computer" anymore... it will say, "Komputer", because in Soviet Microsoft, the computer is the master and the user is called "My User".
The computer will answer, "I'm sorry my user, I'm afraid I can't do that."
User interface features, such as mouse movement and clicks, use of the scroll wheel, keys pressed, menu selections, and other events pass through a special filter when they occur in any part of the interface not controlled by safe Microsoft code. Any time such an event occurs, Windows will display a dialog, asking the user if he is sure he wants to perform that action. The user will have to select "Yes" and enter the administrator password to proceed. This process will be known in Longtooth as "Authenticating an OS event to the user," or simply, as "authentication."
The network layer will be heavily protected. Each network packet received or sent over any interface will require authentication, unless focus is in a Microsoft program at the time, in which case all security checks, including the Microsoft Personal Firewall, if activated, will be completely bypassed. Users will also have to authenticate the loading of any program, unless it is a Microsoft program. Any APIs called will have to be authenticated, unless they are called from a Microsoft program. Any assembly instruction executed in a non-Microsoft program will also have to be authenticated.
By the way, to make sure that a "bot" or some other automated system isn't automatically clicking "yes" and entering the password, and to foil password cracking programs, Microsoft will implement several innovative new technologies. Sometimes, the user will be asked to enter his password backwards. Other times, the password form will request every other character of the password, or every third character, or an ASCII sum of characters located in prime number locations (e.g., the 1st, 2nd, 3rd, 5th, 7th, 11th, etc., characters of the password) in BCD notation, or characters located in Fibonacci number locations (e.g., the 0th, 1st, 1st, 2nd, 3rd, 5th, 8th, etc., characters of the password). In the case of Fibonacci numbers, 0 will refer to the first character, 1 to the second, etc. Longtooth will provide a reference guide and a programmer's calculator to assist the user during this process. Additionally, Windows will sometimes display an image of text that is slightly warped (to foil OCR algorithms that might be present in password crackers) that the user must enter correctly before typing the password.
Again, these authentication checks take place only when running non-Microsoft code. Microsoft understands that so much authentication will make any non-Microsoft program totally unusable for all practical purposes. Instead of getting any work done, the user will spend all of his time entering passwords. Therefore, Microsoft will release what it internally calls a PoK, or "patchwork of kludges," known for marketing purposes as Microsoft Longtooth Password Accelerator 2003. This accelerator will function by capturing authentication events and entering the Administrator password automatically each time, preventing the window from appearing and bothering the user. Since this means the security gained through authentication will be lost, Microsoft Longtooth Password Accelerator 2003 will, at random intervals, disregard authentication events, causing the window to appear. This means that you could be playing Doom III, and suddenly a window appears asking you if you really want to execute MOV EAX,EBX. Or you might have Nero burning a DVD while you're watching TV in the other room, and the burning process will get screwed up in the middle because some window will wait for your password before continuing. These programs will be frozen until you enter the Administrator password. But since Microsoft understands
This is what I think needs to be done: Take all the crews of The Original Series, The Next Generation, Deep Space Nine, Voyager, and Enterprise. Put them all on a single ship, called the Enterprise XP. There would be five captains, to begin with. This would result in much political bickering within the ship. In the meantime, while they're arguing over whether to engage the sensor array or go into maximum warp, a Klingon vessel will uncloak and launch photon torpedos at the Enterprise XP. While this is going on, one of the captains will beat the crap out of the others in an attempt to run over to the maximum warp button and push it. Before he manages to do that, Longtooth XP, the operating system in the ship's computer, will crash with a blue screen of death, showing a cute animation of Clippy the talking paperclip undergoing a death by drive-by-shooting with phasers set to kill. While the captain attempts to restart the ship's computer in order to facilitate jumping to maximum warp, a process which takes approximately two days when including the fsck that must take place, the Klingons continue to fire photon torpedos, and then a Romulan ship shows up and starts firing at the Enterprise XP as well. Finally, the ship is destroyed, taking with it all five crews, and that is called the last episode of Star Trek.
And then, in five years, when they decide that funds are low and it's time to capitalize on yet another Star Trek film, they'll make another episode with the same actors, as if nothing ever happened. And we're supposed to pretend that it didn't. That episode will be called Star Trek Wars, and it will include Yoda, Darth Vadar, and the whole Star Wars crew, in addition to the Star Trek crew. The purpose of this yet-another final episode will be to throw additional fuel on the fire of people who confuse Star Wars and Star Trek, as if there isn't a clear difference between the two. (One happened a long time ago in a galaxy far far away, and the other is happening in the home galaxy in a distant future time setting.)
Ok, so they went ahead and made a nice looking little computer. (Personally, I have a Mac Mini and am quite happy with it in many respects.) But then they had to go ahead and cripple the box by running some version of Microsoft Windows on it. In case you are not familiar with this Microsoft Windows that I am discussing, it is a software package designed to facilitate the unauthorized use of a personal computer while preventing authorized use. Or, at least that's what I gathered based on my experience with this software. Microsoft's purpose may have been quite different, but I don't see how that could be.
The long awaited 3.1 release of the Debian GNU/Linux distribution - codenamed Sarge - is due out next week on the 6th of June
Jesus RMS Christ! And here I had long expected the second coming to happen years before the release of Sarge. But watch out, because Jesus said, "Another will come in my name and him you will receive."
Nah, Harrison Ford won't do Jack Schitt. His agent's agent's agent will do all the work to make sure that Ford won't turn himself into a stinking pile of anything. Once all the arguing and legal problems are out of the way, Ford will just do the acting, get a huge check, and go home.
Slashdot Mirror
And now, at the same time, they say OK to WiFi, which in my opinion is much more dangerous.
From on now, I'm driving.
I'm jumping for joy--This puts my team one step away from winning, and on top of that, it's all over Slashdot!!!
Amazing things can be done with a few measly logic gates and a few machine code instructions. Heck, you think a webserver made of 200 TTL chips is crazy? Check this out. About halfway down the page is a description of the R-741 computer, a minicomputer built in the early '70's to run robotic machinery. I doubt it even contains half as many as 200 TTL chips, and running at 4 MHz on a custom instruction set, this thing's operating system, coming in at a whopping 21k, runs all the functions of digital and analog I/O for robotic machinery--under a complete language interpreter! And it's faster at some functions than many modern computers, given that its electronics, instruction set, and software were all designed so tightly that not a single chip or wire was used unnecessarily, and not a single clock cycle was wasted. Today's general purpose machines, with their zillions of logic gates and gigabytes of memory, are weighed down by layers upon layers of stuff.
It is truly refreshing (and a priviledge, I suppose) to work with this R-741 machine. And it's quite refreshing to see someone build a webserver in a similar style. We need more of this type of ingenuity, and less mountains of bloated code that work too hard to do things that are basically very simple.
Maybe because the biggest miracle of all is that this tiny democracy can even exist when literally surrounded by so many enemies that wish for its destruction. Drives me nuts how people can be so shortsighted.
Oh my Lord! Two miracles come to pass in the same day. This means the Second Coming is upon us! But watch out, because Jesus said, "Another will come in my name and him you will receive."
By the way, I'd like to introduce myself. I'm Jesus H. Christ.
I hope they are using code from the Linux testing suite. That piece of work has already formed a nice set of tests. Also, I hope that the kernel is automatically built with many different combinations of options. And with time, I hope this will become better. The more tests, with the more hardware configurations, with the more kernel configurations, with the more types of input data (including many imaginative forms of incorrect input data to test that the kernel handles it gracefully and thwarts attacks based on such methods), the better quality we will have in the kernel, and it is likely that Linux will be unmatched in quality, stability, efficiency (well, maybe not efficiency necessarily), and long uptimes.
I can't blame Microsoft for phasing out Windows 2000. After all, synergies between killer applications empower emerging stewards to architect ubiquitous initiatives, harness revolutionary convergence, and engineer bleeding-edge solutions to recontextualize turn-key markets.
Growing open-source deliverables harness global interfaces to unleash holistic partnerships. Strategic content drives leading-edge web services to deliver efficient networks while syndicating one-to-one mindshare. When bleeding-edge content architects maximize seamless schemas to deliver robust web services, extensible infrastructures cultivate mission-critical functionalities. Best-of-breed communities target proactive enterprise paradigms while 24/7 methodologies reintermediate visionary content. By leveraging vertical synergies, content providers syndicate one-to-one cross-platform convergence.
Microsoft's plans include optimizing their internal operations to speed up delivery of Longtooth. Sources whom I consider accurate have told me that despite Microsoft's claims that Longtooth will be released by 2006 or 2007, the planned release date is actually late in 2019. Microsoft's secret goals for this version are:
Microsoft will accomplish these goals through a variety of changes. First, Longtooth will no longer be based on the Windows NT design philosophy, as were Windows 2000 and XP. Instead, Microsoft will release MS-DOS 9.0 2003, a 64-bit multithreaded DOS written in VisualBASIC.Net, and Windows Longtooth will run on top of that. Also, Longtooth will contain more code changes than any previous version of Windows, both in the number of changed source lines of code (SLOCs) and in the percentage of the total Windows codebase changed. Tremendous numbers of new features are being implemented in completely new code.
More importantly, Microsoft employees are combing through the codebase, in a relentless search for code that is mature, stabilized, and proven. This search has proved difficult, but when found, such code will be marked for reimplementation. I'm told that most of this code will be reimplemented in VisualBASIC.NET, even if the prior version was written in another language, such as C or C++. Programmers making the new VisualBasic.NET code are not allowed to look at the code that already exists, so that fixes to known issues will not be known until well after the software is deployed to millions of users.
The reason for these changes is simple: Study after study conducted by Microsoft has proven that security through obscurity is the only way to go, especially in an operating system deployed to millions of users, with many instances running mission critical applications in finance, industry, government, and other sectors. Microsoft has identified that viruses, worms, spam, spyware, adware, malware, hackers, and phreakers are able to compromise Windows security because vulnerabilities in the code are known. By changing much of the codebase, especially the stablest and most proven parts, Microsoft will thwart the efforts of malicious programmers, as it will take time for them to find the new vulnerabilities in the unknown code.
To meet Microsoft's first goal of reducing the user's perception of the complexity of Windows, Microsoft will integrate a new technology, dubbed Microsoft Windows User Simplicity And Security Manager 2003, into Longtooth. This technology will hide all configuration settings from the user. All settings will be completely automatic, and the user will have no need to know or care what is under the hood. In reality, Longtooth will be the most complex version of Windows yet, with thousands of configuration settings controlling nearly every function of the operating system. The settings will be produced by discove
Please make payable and mail to:
Rice Burners Suck
12345 South Rodder Street
Chevy Rocks, Florida 54321
USA
Thanks.
In fact, this is what they should do: Build a gigantic ship with a hull large enough to contain billions and billions of gallons of water. Then, pump water from the oceans through a desalination plant and right into this ship. The water would be transported to Mars this way. Another ship would carry seeds, plants, and soil. All of this would be taken to the most opportune spot and placed there. Perhaps a crater could be filled with the water and then the soil and plants could be planted around it. After several hundred missions like this, there could be quite a number of lakes on Mars, with lots of plant life around them, which would create more oxygen in the air and allow a working natural cycle to begin.
This would have added benefits. There are some (misinformed) scientists on this planet who believe that global warming will cause ice caps to melt, which will raise the level of the oceans and cover the entire earth. Kind of like what's on the third page of Genesis, but then no Slashdotter reads the Holy Bible. Anyway, by removing a lot of water from Earth and using it to create lakes on Mars, we would eliminate the risk of drowning in the waters (which won't happen), the result of an overheating world (which also won't happen), and we would also create many square miles of land rich in nutrients previously untapped, which could be used to grow healthy foods for those who are starving (which is more a result of political problems in third world countries than a result of lack of land space to grow food).
This would be worth millions of dollars in investment.
I do not think you understand the definition of freedom. Ask RMS. He'll explain the proper meaning of that word.
You are a good and righteous person.
Keep up the good work.Reminds me of the time that Wind River Systems "spun off" the support they initially gave to the FreeBSD project after buying out Walnut Creek CD-ROM. The community had sent them a number of questions, and their answer was something along the lines of, "We will continue to encourage emerging stewards of the FreeBSD project," along with paragraph after paragraph of additional meaningless duckspeak, in the same form as, "By leveraging innovative technologies, content providers streamline compelling enterprise solutions."
What I'm essentially trying to say, then, is that Red Hat will, for a short time, continue to give equal amounts of support to the Fedora project. But this will slowly wane, as I believe has been Red Hat's plan all along. That is why the name was changed from Red Hat Linux to Fedora Core. They will eventually turn as many components of their so-called Enterprise version of Linux into closed source, proprietary software, in the same style as most of the UNIX OSes out there. The kernel will continue to adhere to the GPL, as will other major components (think Samba, Apache, etc.) with their respective licenses. But I think that nearly all Red Hat development will be in the closed source arena.
This way, Red Hat will have achieved the following interesting goal: They are widely known as the de facto Linux standard, because they were open source for years and provided a lot to the community. But on the other hand, they will be able to make a lot of money on their Enterprise stuff, because most of it will be proprietary and the technologies therein will be unavailable in Fedora or in any other Linux for that matter. Think Mac OS X. Red Hat Enterprise Linux will be about as open source as Apple's software... Sure, hundreds of thousands of lines of code are open source. But the really good stuff, the really innovative stuff, the new stuff that no other OS has is proprietary, closed source, binary, and locked out of view.
This, I believe, is Red Hat's plan. I don't know about you, but I'm putting on my tin-foil hat.
I don't understand why we need these newfangled transistor thingies anyway. Why, when I was your age, logic was handled using relays. Why, it took only eleven minutes for our computer, here at Building B, to add two numbers, and that includes the time it took to enter the numbers. All these newfangled transistor contraptions don't do a darn thing, I tell ya. Yes sir, I swear it, they're unnecessary.
I have a better idea. There should be a worldwide law that states that all websites must make every effort possible to crash MSIE, but run well on all other browsers. The reasoning is that by eliminating MSIE, much of the risk associated with cybercrime will disappear with it.
This is the most important issue in the entire continent, and must be addressed immediately. If Europe fails to properly embrace open source software, it will surely spell disaster for the entire continent, all the countries thereof, and all people living in Europe.
Open source software is the solution to all of the world's problems.
No, no, no, you've got it all wrong. It's the GNU/US Department of Health and Human Services (GNU/HHS). I'm going to report this to the Free Software Foundation's Department of Making Sure GNU Appears Anywhere GNU/Linux is Used (GNU/RMS).
I almost thought the title of this article was, "Longtooth Drops My Panties." That would have been a much better and more informative article.
For immediate release: Mikrosoft Corporation (NASDAQ: M5FT) today announced new technology, dubbed Pantydropper 2003 Professional Server. By leveraging innovative technologies, content providers streamline compelling enterprise solutions. The software is touted as being the only solution on the enterprise market currently that can drop one's panties.
Gill Bates, Chief Software Architect at Mikrosoft, stated, "This is one I've been trying to figure out ever since my days as a pimply-faced teenaged geek. Now, at the age of 51, I finally have the solution to all of my problems."
With a jackhammer.
OH NO!!! I voted for BUSH, TWICE, once in 2000, one in 2004. He is a great president, despite what that idiot that you said I sound like would have you believe. The war in Iraq is a just and righteous war. Go Bush!
Bush rocks. Moore sucks.
Basically, it was a system to use giant limestone wheels from the island of Yap as credit cards. The giant wheels are difficult to counterfeit, and therefore will prevent theft through credit card fraud. These will be called credit rocks, rather than credit cards, and will take a crane to move, but many retailers believe that it will provide consumers with the added convenience that because the stones will be so difficult to move, they won't charge as much on their credit rocks as they do on their credit cards, and therefore we will have fewer people in debt.
The computer will answer, "I'm sorry my user, I'm afraid I can't do that."
User interface features, such as mouse movement and clicks, use of the scroll wheel, keys pressed, menu selections, and other events pass through a special filter when they occur in any part of the interface not controlled by safe Microsoft code. Any time such an event occurs, Windows will display a dialog, asking the user if he is sure he wants to perform that action. The user will have to select "Yes" and enter the administrator password to proceed. This process will be known in Longtooth as "Authenticating an OS event to the user," or simply, as "authentication."
The network layer will be heavily protected. Each network packet received or sent over any interface will require authentication, unless focus is in a Microsoft program at the time, in which case all security checks, including the Microsoft Personal Firewall, if activated, will be completely bypassed. Users will also have to authenticate the loading of any program, unless it is a Microsoft program. Any APIs called will have to be authenticated, unless they are called from a Microsoft program. Any assembly instruction executed in a non-Microsoft program will also have to be authenticated.
By the way, to make sure that a "bot" or some other automated system isn't automatically clicking "yes" and entering the password, and to foil password cracking programs, Microsoft will implement several innovative new technologies. Sometimes, the user will be asked to enter his password backwards. Other times, the password form will request every other character of the password, or every third character, or an ASCII sum of characters located in prime number locations (e.g., the 1st, 2nd, 3rd, 5th, 7th, 11th, etc., characters of the password) in BCD notation, or characters located in Fibonacci number locations (e.g., the 0th, 1st, 1st, 2nd, 3rd, 5th, 8th, etc., characters of the password). In the case of Fibonacci numbers, 0 will refer to the first character, 1 to the second, etc. Longtooth will provide a reference guide and a programmer's calculator to assist the user during this process. Additionally, Windows will sometimes display an image of text that is slightly warped (to foil OCR algorithms that might be present in password crackers) that the user must enter correctly before typing the password.
Again, these authentication checks take place only when running non-Microsoft code. Microsoft understands that so much authentication will make any non-Microsoft program totally unusable for all practical purposes. Instead of getting any work done, the user will spend all of his time entering passwords. Therefore, Microsoft will release what it internally calls a PoK, or "patchwork of kludges," known for marketing purposes as Microsoft Longtooth Password Accelerator 2003. This accelerator will function by capturing authentication events and entering the Administrator password automatically each time, preventing the window from appearing and bothering the user. Since this means the security gained through authentication will be lost, Microsoft Longtooth Password Accelerator 2003 will, at random intervals, disregard authentication events, causing the window to appear. This means that you could be playing Doom III, and suddenly a window appears asking you if you really want to execute MOV EAX,EBX. Or you might have Nero burning a DVD while you're watching TV in the other room, and the burning process will get screwed up in the middle because some window will wait for your password before continuing. These programs will be frozen until you enter the Administrator password. But since Microsoft understands
And then, in five years, when they decide that funds are low and it's time to capitalize on yet another Star Trek film, they'll make another episode with the same actors, as if nothing ever happened. And we're supposed to pretend that it didn't. That episode will be called Star Trek Wars, and it will include Yoda, Darth Vadar, and the whole Star Wars crew, in addition to the Star Trek crew. The purpose of this yet-another final episode will be to throw additional fuel on the fire of people who confuse Star Wars and Star Trek, as if there isn't a clear difference between the two. (One happened a long time ago in a galaxy far far away, and the other is happening in the home galaxy in a distant future time setting.)
Ok, so they went ahead and made a nice looking little computer. (Personally, I have a Mac Mini and am quite happy with it in many respects.) But then they had to go ahead and cripple the box by running some version of Microsoft Windows on it. In case you are not familiar with this Microsoft Windows that I am discussing, it is a software package designed to facilitate the unauthorized use of a personal computer while preventing authorized use. Or, at least that's what I gathered based on my experience with this software. Microsoft's purpose may have been quite different, but I don't see how that could be.
Jesus RMS Christ! And here I had long expected the second coming to happen years before the release of Sarge. But watch out, because Jesus said, "Another will come in my name and him you will receive."
Nah, Harrison Ford won't do Jack Schitt. His agent's agent's agent will do all the work to make sure that Ford won't turn himself into a stinking pile of anything. Once all the arguing and legal problems are out of the way, Ford will just do the acting, get a huge check, and go home.