One of the reasons that Mandrake is so popular is because you can find boxed sets in EVERY Walmart (one of the most popular stores in the US). If RedHat drops it's boxed sets (which can normally be found in Staples, Office Depot, and other places that people with money shop), then the percentage of of RedHat users will drop.
I teach an Intro to Linux course at a community college (using RedHat, mostly because of it's popularity). Even though one of the first things I mention is that Linux is free and show the students how to get it, most of then go out and buy a boxed set (my guess is because it's out of habbit or they want the documentation in the dead tree form). If RedHat stops selling boxed sets, then it's only going to hurt themselves. And I may have to change the distribution I use in the class.
No shit! If someone was hitting on me that much, I'd start asking them to buy me things. i.e - I really could use some new cloths to go out on the town, or I really am looking forward to the next release of [insert name of game here], etc. If she doens't buy you anything, then she'll stop hitting on you. If you get what you want, then what are you complaining about. Yeah her crotch may not look as nice or smell as sweet as a 20 year olds, but so what. Get drunk before hand if you have too....
It happens all of the time when more than one company/group/organiztion have access to the same satellite. When one of them are having problems with the uplink (excessive cloud cover, etc), it's common that a tech for that company would go out to the satcom modem and boost the signal a couple of decibels. This would usually drown out another companies siganl who would than boost their own. Eventually you would get to a situation where everyone has boosted their output signal way above what is normal and everyone is getting drowned out. The company in charge of the satellite would have to call all of the offending parties, have them cut their signal, and bring them up one by one. It wasn't uncommon for this to happen at least once every six months.
I wonder how the HAMs will take this. They've been using Push To Talk switches for at least 50 years (being generous for Nextel). I hope Nextel is smart when it goes after people over TM infringement. It would be really easy for a court to rule that term is generic. If Nextel does go after HAMs or those that make amatuer radios, Nextel may be surprised when they realize that HAMs can have deep pockets and are great at pooling resourses. Shit, HAMs have been building their own satellites for some time now....
As of January of this year I have finally accepted the fact I will likely never be able to develop LRP into the operating system it could have been. A full 6 months later I'm forcing myself to update this page to reflect this.
LRP has pretty much been dead for the last couple of years. For a while, the only thing of interest on the main website was the forum where people could get help. The main website was never updated. A few of the more active developers wanted to take over the project and the main website, but the original developer refused to hand it over (for whatever reason). It was obvious then he didn't have any interest or time for the project.
Most of the information and development was on the unofficial c0wz website (those involved with LRP know which site I'm talking about). But that site went down around the time LEAF started. Every once in a while I run accross an old mirror of the c0wz website, which still has the best collection of networking links and information IMHO.
One thing people don't realize is that if they don't have the time or energy for a project, they need to hand it off to someone else. Otherwise everyone will jump ship and start a new project (see LEAF) and leave the original developer with nothing more than a dead project and a few memories. When something a popular as LRP dies, it's not because of a lack of interest from the community, it's because of a lack of interest, direction, and leadership from the original developer. The LRP would continue on if the original developer would learn to just let go...
THE GOVERNMENT IS STILL HIDING THE TRUTH!!
on
Roswell Declassified
·
· Score: 2, Funny
/me puts his tinfoil hat on so that everyone will know I'm telling the truth...
The "Morning Reports" indicate that nothing happened. Of course no staff duty log or "Morning Report" would contain any classified information. If something was accidently added, that log would have been rewritten within a day. The governement change their story the next day. What would keep them from changing any daily logs?!?
/me goes to check the supplies in the fallout shelter
These documents only prove the the government is still trying to hide something!!
/me sees black helicopters flying around
Everyone else is nuts for believing EVERYTHING the government tells them!!
Read-Copy Update - http://lse.sourceforge.net/locking/rcupdate.html
"Read-Copy Update was originally designed for DYNIX/ptx, a UNIX operating system from Sequent Computer Systems Inc., now a part of IBM."
If there is any SCO code that IBM submitted to the Linux kernel, then it should be in those patches. That's if the statements by the analyst is true that SCO is claiming their code is specifically in the NUMA and RCU sections of the kernel.
Oh, and something SCO/Caldera seems to have missed totally is who the contributing IBM people actually are; most (all?) of them are the people from the NUMA-Q section, which is a very recent purchase on IBM's part. No SCO code involved there, afaict.
An article that talks about IBM's purchase of Sequent and NUMA.
http://news.com.com/2100-1001-228275.html
And another article about IBM and NUMA. http://news.com.com/2100-1001-233626.html?legacy=c net
The last article makes it sound like IBM bought NUMA and worked with SCO to include it in Monterey. IBM also bought RCU from Sequent and may have possible worked with SCO to include it into Monterey. It's possible that SCO can claim some ownership because they worked with IBM on the technologies. But if IBM was the one that bought NUMA and RCU, then SCO is going to have a tough time claiming any rights to it. But there is not enough details available to be sure what really happened.
Are the claims limited to any one area of the O/S (kernel)? For example, UNIX SysV's implementation of shared memory or similar.
The claims are not limited to just one area of the Unix System V kernel. SCO claims there are multiple instances of copyright violations. SCO said these include: NUMA (Non Uniform Memory access) a mechanism for enabling large multiprocessing systems, RCU (Read Copy Update) (and) SMP. All of the aforementioned functions represent high end enterprise performance and scalability functionality portions of the code.
Regarding the claim of looking at old UNIX code to prove SCO's point, I have a feeling that whole issue will turn out to be a red herring.
But mentions of RCU, NUMA, and SMP would mean that those areas of the kernel would be a REALLY good place to start looking.
Isn't IBM the primary contributor of the NUMA code?
"Close this book and burn it. Go buy O'Reilly's elephant book, and learn PERL instead.":P
Elephant book? The only elephants I've seen on O'Reilly books is on the MCSE in a Nutshell books. Perhaps you are refering to the Camel book (Perl Programming). Or the Llama book (Learning Perl).
Refering to the elephant book shows how much you use/know Perl.
I remember the first show they started that didn't show videos, "120 Minutes". All I could think about was, "OMG!! Two whole hours without music videos!! What are they thinking!!!"
And the only commercial they showed advertised themselves, "I want my MTV!" Which was kind of funny, if you could see the commercial, you already HAD MTV!
"Restricted Cash and Royalty Payable to Novell, Inc.
The Company has an arrangement with Novell, Inc. ("Novell") in which it acts as an administrative agent in the collection of royalties for customers who deploy SVRx technology. Under the agency agreement, the Company collects all customer payments and remits 95 percent of the collected funds to Novell and retains 5 percent as an administrative fee. The Company records the 5 percent administrative fee as revenue in its consolidated statements of operations. The accompanying October 31, 2002 and 2001 consolidated balance sheets reflect the amounts collected related to this agency agreement but not yet remitted to Novell of $1,428,000 and $1,894,000, respectively, as restricted cash and royalty payable to Novell. The October 31, 2001 balances were reclassified from cash and equivalents and other royalties payable to conform to the current year presentation."
Correct me if my understanding of the above is a little off, but it sounds like SCO made $71,400 and $94,700 in 2002 and 2001 off of royalty payments.
While everyone's attention is on the circus being created by SCO, someone needs to keep an eye on MS. I can see them using this whole affair to backdoor the Linux community while noone is watching. (If MS is not already playing SCO like a puppet...)
Using a honeypot to detect and surveil computer intruders might put you on the working end of federal wiretapping beef, or even get you sued by the next hacker that sticks his nose in the trap,
There is an easy fix for this. Stop calling them honeypots and start calling them what they really are, an intrusion detection system. Saying that your IDS was broken into will also go over better with the judge and jury.
So far the Columbia Accident board has said that before resuming shuttle missions NASA must do a better job inspecting the leading edge of the spaceplanes' wings and ensure that the nation's spy satellites capture detailed images of the orbiter during each flight.
Now correct me if my logic is a little faulty, but if a large piece of insulation fell off of the fuel tank, and from what I hear this is a fairly common occurance, shouldn't they be looking at making sure the insulation on the fuel tank doesn't fall off? Looking at the wings for corrosion is a good idea, but it seems that they are ignoring the possibility that the insulation hitting the leading edge of the wing was the primary cause of the accident.
The board is starting to sound like a NTSB investigation. Represenatives from all of the concerned parties get involved and do there best to blame the cause of the accident on someone else. This is why the primary cause of most accidents are blamed on pilot error (they are usually not around to defend themselves). Instead of taking the fact that insulation regularly falls off of the fuel tank as a serious problem, more inspections of the wings is being presented as the solution.
I've got a stupid question. Instead of asking my friends what they think or doing a little research online, I'll post the question on Slashdot and see what the largest collection of wannabe geeks on the Internet think. When you flush the toilet in the Southern Hemisphere, which way does the water spin?
HP4's are built like tanks!! And they are easy to fix too. The technical manual for them make troubleshooting easy. Parts are easy to find but I tend to buy parts from www.printerworks.com. The only problems I have with the HP4's is the refurbished toner cartridges sometimes cause problems and the old rollers on the printers tend to gum up when it gets humid. Fixing HP4's will spoil you though.
The printer I like working on next are the old HP II's and III's (yes, there are some still floating around). Yes, they weight about as much as tanks, but the two most common problems (fusers burning up and gear assemblies chipping teeth) are easy to replace.
InkJets are simply a pain in the ass to fix (if you can find parts for them!!). It's usually not cost effective to even try to fix them (the repair parts tend to cost more than a new printer!!). If you can find repair parts for them and insist on trying to fix them, it usually doens't work anyways. The technical manuals are a joke so you are left to guessing what is wrong. And you have a large chance of breaking the printer even more trying to open it up because of all the cheap plastic parts.
As much as I like the HP4's, HP's new laserjets are going down hill a little. They are not as easy to fix and the technical manuals are not as good. The first large color laserjet that I worked on had a toner cartridge explode inside of it (that was a mess!!). Well, something else was taken out in the process. The troubleshooting steps in the manual went along the lines of, replace this several hundred dollar part first, and if that doesn't work, replace a different several hundred dollar part next, and if that didn't work, replace this thousand dollar controller card. Needless to say, the newer HP printers can be expensive to fix.
The military has been working on desensitizing for some time now. It was noticed that during both WWI and WWII only a small percentage of soldiers would actually fire their weapons in combat. I saw a show on the Discovery Channel a few years ago that talked about this. One of the ways to desensitize soldiers is by using a conditioned response. The Army's weapons qualification (a yearly requirement at minimum) currently does this by using human shaped pop-up targets. The condition, a target pops up. The response, the soldier pulls the trigger and the target goes down. One of the people being interviewed during the show mentioned that conditioned response is the same technique that is used to train dolphins to respond to sounds and rabbits to respond to lights.
Web Server.
Windows, go to add/remove software, add IIS. Run the microsoft management console, and tweak it to your delight, if you get stuck the help file is right there, or burn a call on the credit card to MS support.
This is the sort of attitude that gives MCSE's and Window's SysAdmins a bad name. Most people's approach to administrating Windows is from the GUI. They seem to feel everything is point and click and that there is a check box or scroll down menu for every possible option. Wrong. The few Window's admins that I've met that I had a LOT of respect for all had the same attitude, Windows is much more powerful from the command line. Have you installed the Support Tools on the Server CD? Do you use them? Why not? Do you have the Server Resource Kit? Do you use those tools? Why not? Run `netdiag -v > netdiag.yyyymmdd.txt` and look at the output. Now show me where in the GUI I can get all of that information in one place. Do you feel uncomfortable about digging through the registry? Why? There are some things that can only be setup be adding or changing entries in the registry. Want to optimize your system? How many options does that GUI give you? Optimize for File Sharing, Optimize for Network Applications, etc. Yeah, you're really optimizing your system there. Most system optimizations can only be set in the registry. It tends to help the Unix crowd to thing of the registry as the/etc directory condensed into a couple of files. Yes they can get corrupted. But you know how to recover from that right? If not, you shouldn't be touching a Windows server.
Do you have a Technet subscription? Why not? Most of money you're wasting on support calls can easily be answered by searching through Technet. What do you think the person on the other end of the line is reading back to you? Yes it's possible that you found some obscure bug in your unique setup that you're running. But with the millions of MS users out there do you honestly think that you are that special? Yes, Knowledge Base articles tend to not go into detail or really explain what's going on, but there are a large number of man pages in linux that do nothing more than list all of the options.
One of the biggest complaints I here from the Unix crowd is that you can't do scripting on Windows. Bullshit. You have your choice from vbscript, javascript, Windows Scripting Host, Perl, etc. They are not any harder to learn than trying to teach someone shell scripting, awk, sed, (insert 50 other commands), and regular expresions.
One of the things (out of many) that I don't like about Windows is that the GUI tends to make people lazy. Why learn scripting when people think they can point and click everything. After setting up DNS on a 2000 Server, I noticed the DNS entries looked almost identical to the ones you'd create in Bind. In Unix, you have to know how to create zone files by hand. But since Windows sets those up for you, I don't see too many people without Unix experience digging around in zone files and figuring out how they work.
I started administrating Windows machines after becoming proficient with Unix. At first I had no intentions of every wanting to learn Windows administration, but I became interested after someone showed me how much more powerful Windows actually is from the command line. So I approached Windows from the Unix point of view, using the command line, digging around in the registry, trying to understand what is really going on (this sometimes seems impossible), etc. Maybe my experience just carried over and helped me understand how things work. But I don't see too many people who approach Windows as nothing more than a GUI really taking the time to understand what's going on. Most of the so called Windows admins I see are not really admins from the Unix point of view. They are the office geek who spends most of their spare time playing video games and just become the unofficial admin for the office. Or they jumped on the band wagon a few years ago thinking they'd become rich after getting their MCSE. Of course taking care of more than 10 desktop machines is going to be more than they can handle...
This is nothing more than a red herring. If somebody has physical access to your box, then your security has been breached. Passwords aren't going to protect you from having your hard drive removed. An encrypted filesystem, however, will.
The old Slackware.com forums have been available on Userlocal for well over 6 months. The only thing that has changed recently is that Userlocal has a new hosting provider and that the forums are no longer read only.
But this may be a bad time for the forums to become active again, alt.os.linux.slackware has been getting hit fairly hard by a troll(s) in the last few days.
Slashdot Mirror
I teach an Intro to Linux course at a community college (using RedHat, mostly because of it's popularity). Even though one of the first things I mention is that Linux is free and show the students how to get it, most of then go out and buy a boxed set (my guess is because it's out of habbit or they want the documentation in the dead tree form). If RedHat stops selling boxed sets, then it's only going to hurt themselves. And I may have to change the distribution I use in the class.
Some people are just too picky...
It happens all of the time when more than one company/group/organiztion have access to the same satellite. When one of them are having problems with the uplink (excessive cloud cover, etc), it's common that a tech for that company would go out to the satcom modem and boost the signal a couple of decibels. This would usually drown out another companies siganl who would than boost their own. Eventually you would get to a situation where everyone has boosted their output signal way above what is normal and everyone is getting drowned out. The company in charge of the satellite would have to call all of the offending parties, have them cut their signal, and bring them up one by one. It wasn't uncommon for this to happen at least once every six months.
I wonder how the HAMs will take this. They've been using Push To Talk switches for at least 50 years (being generous for Nextel). I hope Nextel is smart when it goes after people over TM infringement. It would be really easy for a court to rule that term is generic. If Nextel does go after HAMs or those that make amatuer radios, Nextel may be surprised when they realize that HAMs can have deep pockets and are great at pooling resourses. Shit, HAMs have been building their own satellites for some time now....
Most of the information and development was on the unofficial c0wz website (those involved with LRP know which site I'm talking about). But that site went down around the time LEAF started. Every once in a while I run accross an old mirror of the c0wz website, which still has the best collection of networking links and information IMHO.
One thing people don't realize is that if they don't have the time or energy for a project, they need to hand it off to someone else. Otherwise everyone will jump ship and start a new project (see LEAF) and leave the original developer with nothing more than a dead project and a few memories. When something a popular as LRP dies, it's not because of a lack of interest from the community, it's because of a lack of interest, direction, and leadership from the original developer. The LRP would continue on if the original developer would learn to just let go...
The "Morning Reports" indicate that nothing happened. Of course no staff duty log or "Morning Report" would contain any classified information. If something was accidently added, that log would have been rewritten within a day. The governement change their story the next day. What would keep them from changing any daily logs?!?
These documents only prove the the government is still trying to hide something!!
Everyone else is nuts for believing EVERYTHING the government tells them!!
Oh no!! They've come for me....
IBM Patches for NUMA - http://www-124.ibm.com/linux/patches/?project_id=5 6
Read-Copy Update - http://lse.sourceforge.net/locking/rcupdate.html "Read-Copy Update was originally designed for DYNIX/ptx, a UNIX operating system from Sequent Computer Systems Inc., now a part of IBM."
IBM's original RCU Patch - http://lse.sourceforge.net/locking/rcu/patches/rcl ock-2.4.1-01.patch
Other kernel patches from IBM - http://www-124.ibm.com/linux/patches/?project_id=5 2
If there is any SCO code that IBM submitted to the Linux kernel, then it should be in those patches. That's if the statements by the analyst is true that SCO is claiming their code is specifically in the NUMA and RCU sections of the kernel.
There is an interesting quote in this interview from MozillaQuest Magazine back in March. http://mozillaquest.com/Linux03/ScoSource-07_Story 02.html
An article that talks about IBM's purchase of Sequent and NUMA. http://news.com.com/2100-1001-228275.html And another article about IBM and NUMA. http://news.com.com/2100-1001-233626.html?legacy=But mentions of RCU, NUMA, and SMP would mean that those areas of the kernel would be a REALLY good place to start looking.
Isn't IBM the primary contributor of the NUMA code?
http://oss.software.ibm.com/linux/news/?project_id =56
Refering to the elephant book shows how much you use/know Perl.
And the only commercial they showed advertised themselves, "I want my MTV!" Which was kind of funny, if you could see the commercial, you already HAD MTV!
While everyone's attention is on the circus being created by SCO, someone needs to keep an eye on MS. I can see them using this whole affair to backdoor the Linux community while noone is watching. (If MS is not already playing SCO like a puppet...)
The board is starting to sound like a NTSB investigation. Represenatives from all of the concerned parties get involved and do there best to blame the cause of the accident on someone else. This is why the primary cause of most accidents are blamed on pilot error (they are usually not around to defend themselves). Instead of taking the fact that insulation regularly falls off of the fuel tank as a serious problem, more inspections of the wings is being presented as the solution.
What ever....
I've got a stupid question. Instead of asking my friends what they think or doing a little research online, I'll post the question on Slashdot and see what the largest collection of wannabe geeks on the Internet think. When you flush the toilet in the Southern Hemisphere, which way does the water spin?
HP4's are built like tanks!! And they are easy to fix too. The technical manual for them make troubleshooting easy. Parts are easy to find but I tend to buy parts from www.printerworks.com. The only problems I have with the HP4's is the refurbished toner cartridges sometimes cause problems and the old rollers on the printers tend to gum up when it gets humid. Fixing HP4's will spoil you though.
The printer I like working on next are the old HP II's and III's (yes, there are some still floating around). Yes, they weight about as much as tanks, but the two most common problems (fusers burning up and gear assemblies chipping teeth) are easy to replace.
InkJets are simply a pain in the ass to fix (if you can find parts for them!!). It's usually not cost effective to even try to fix them (the repair parts tend to cost more than a new printer!!). If you can find repair parts for them and insist on trying to fix them, it usually doens't work anyways. The technical manuals are a joke so you are left to guessing what is wrong. And you have a large chance of breaking the printer even more trying to open it up because of all the cheap plastic parts.
As much as I like the HP4's, HP's new laserjets are going down hill a little. They are not as easy to fix and the technical manuals are not as good. The first large color laserjet that I worked on had a toner cartridge explode inside of it (that was a mess!!). Well, something else was taken out in the process. The troubleshooting steps in the manual went along the lines of, replace this several hundred dollar part first, and if that doesn't work, replace a different several hundred dollar part next, and if that didn't work, replace this thousand dollar controller card. Needless to say, the newer HP printers can be expensive to fix.
Let's not give anyone any ideas now... It wouldn't surprise me if there are a dozen different worms running around the internet tomorrow.
/. is almost as bad as how CNN was during the Rodney King Riots...
MS has been releasing rootkits for it's servers for years. Haven't you ever used MS's {NT|2000} Server h@x0r^H^H^H^H^HResource Kit?
The military has been working on desensitizing for some time now. It was noticed that during both WWI and WWII only a small percentage of soldiers would actually fire their weapons in combat. I saw a show on the Discovery Channel a few years ago that talked about this. One of the ways to desensitize soldiers is by using a conditioned response. The Army's weapons qualification (a yearly requirement at minimum) currently does this by using human shaped pop-up targets. The condition, a target pops up. The response, the soldier pulls the trigger and the target goes down. One of the people being interviewed during the show mentioned that conditioned response is the same technique that is used to train dolphins to respond to sounds and rabbits to respond to lights.
Do you have a Technet subscription? Why not? Most of money you're wasting on support calls can easily be answered by searching through Technet. What do you think the person on the other end of the line is reading back to you? Yes it's possible that you found some obscure bug in your unique setup that you're running. But with the millions of MS users out there do you honestly think that you are that special? Yes, Knowledge Base articles tend to not go into detail or really explain what's going on, but there are a large number of man pages in linux that do nothing more than list all of the options.
One of the biggest complaints I here from the Unix crowd is that you can't do scripting on Windows. Bullshit. You have your choice from vbscript, javascript, Windows Scripting Host, Perl, etc. They are not any harder to learn than trying to teach someone shell scripting, awk, sed, (insert 50 other commands), and regular expresions.
One of the things (out of many) that I don't like about Windows is that the GUI tends to make people lazy. Why learn scripting when people think they can point and click everything. After setting up DNS on a 2000 Server, I noticed the DNS entries looked almost identical to the ones you'd create in Bind. In Unix, you have to know how to create zone files by hand. But since Windows sets those up for you, I don't see too many people without Unix experience digging around in zone files and figuring out how they work.
I started administrating Windows machines after becoming proficient with Unix. At first I had no intentions of every wanting to learn Windows administration, but I became interested after someone showed me how much more powerful Windows actually is from the command line. So I approached Windows from the Unix point of view, using the command line, digging around in the registry, trying to understand what is really going on (this sometimes seems impossible), etc. Maybe my experience just carried over and helped me understand how things work. But I don't see too many people who approach Windows as nothing more than a GUI really taking the time to understand what's going on. Most of the so called Windows admins I see are not really admins from the Unix point of view. They are the office geek who spends most of their spare time playing video games and just become the unofficial admin for the office. Or they jumped on the band wagon a few years ago thinking they'd become rich after getting their MCSE. Of course taking care of more than 10 desktop machines is going to be more than they can handle...
y00 k33p 7h1Nk1N6 7hA7, 3y3 0wN j00...
Last post before forums were shut down: 12-14-01 13:24
/.
First post after forums became active again: 01-20-03 21:07
Means "2 years of hibernation" on
The old Slackware.com forums have been available on Userlocal for well over 6 months. The only thing that has changed recently is that Userlocal has a new hosting provider and that the forums are no longer read only.
But this may be a bad time for the forums to become active again, alt.os.linux.slackware has been getting hit fairly hard by a troll(s) in the last few days.