I hate phones for the same reason I hate instant messengers. I don't like things that demand my instant attention and interrupt what I'm doing.
If I'm working on something I can check emails when it won't affect my ability to get work done. If I'm constantly answering the phone I never get anything done.
Personally I'm not about to try and explain to my parents how to change their ssh port.. It's bad enough as it is trying to walk them through login problems. Also that server has paying customers on it and I have finally trained most of them to use winscp to transfer files.
It's important to note that the servers may not have been actually rooted. There is a large number of ssh dictionary breakin attempts on every machine I administrate on several completely different ip blocks. The worst hit is usually my personal server that tended to get hit with several thousand attempts per hour(enough that legitimate logins were a problem) before I installed countermeasures. Even now the countermeasures are locking out 5 to 8 hosts per day.
They have managed to get user accounts on a few occasions and most of the time they never even attempt to gain root. They just start scanning for new hosts.
I'm now running a python script called DenyHosts to find and lockout dictionary attacks. "apt-get install denyhosts" for debian users. Even on much more liberal settings than the default it's lowered my cpu load considerably and locks out attacks in the first minute rather than the hour it would otherwise take me to notice.
IMO there is nothing wrong with backporting new drivers (which should only affect people who use the hardware for which the new drivers are designed, not any other users of the kernel) into a stable kernel tree.
Except that in this thread people have been blaming the SATA problems on the new development method but in this case there would have been no difference.
The downside to backporting was that the differences between 2.4.x and 2.5.x were so large that the driver interfaces had a tendency to be completely different and the 2.4.x infrastructure in some cases just wasn't able to handle the newer drivers. In the case of one RAID card the 2.4.x drivers were just hopeless and I had to actually wait two weeks for 2.5.x to be stable enough and install it on my server and just hope it wouldn't crash.
"Because Linus said so" is in fact not a particularly valid answer. Yes, Linus has the right to choose the development structure the kernel is now using, but that doesn't mean it is the best way to do it for everybody. dropping the distinction between "stable" and "development" versions was a sloppy, lazy move that simply pushed the responsibility for maintaining stable released off onto the distributors. That has essentially duplicated the work a hundred-fold, because each distribution must do the work themselves. We're told that this is a "better" arrangement, but it is clearly only better for Linus and the kernel developers, because they get to do less work and be lazy when it comes to making changes: "Want to rip out the allocator and replace it with a largely untested one? Sure, why not! Making sure everything works is the distributors problem, not ours!"
Except that the old system didn't work at all. There were just too many changes to stabilize in any reasonable amount of time and while the debugging was happening the 2.4.x kernel was becoming so badly out of date that people (and distros) tried to back port changes from the 2.5.x tree.
The result was TWO unstable kernel trees and the vendor trees had a tendency to be even worse. The old system would have left those people using SATA in a worse situation then they are in now. Keep in mind that SATA came out after 2.6.x so the drivers would right now be somewhere in the 2.7.x series kernel still waiting to be debugged and the stable maintainers would be forced to try and backport the SATA drivers once again resulting in two unstable kernels
FreeDos isn't intended by Dell to be a real OS. It's just there so that Dell Can offer an OS they know they won't ever have to support so that they can tell Microsoft that they don't offer machines without an OS.
It's an end run around Microsoft. Microsoft has a hissyfit whenever vendors offer OSless boxes so they block that option but they can't object to FreeDos without having antitrust regulators breathing down their necks.
I have.. I had a co worker a few years back who never cut his hair, trimmed his beard or did laundry the stench was nasty. the company tolerated him because they thought he was good at what he did.
Turns out his installs were crap (wrong partition sizes "fixed" with symlinks) and his code was a disorganized unmaintainable mess.
I'm all for t shirts and relaxed dress code but bathing should be mandatory.
XBMC is the only reason I bought an XBOX and I spend far more time using the media functions than I do playing games so I don't care from being banned from XBOX live (which I never use anyways)
This is just not true. For every RMS or ESR we have a Linus Torvalds or an Andrew Tridgell who seem to do a very good job of making clear points and get quoted often.
That example was amusing for me considering the job ad I had in my inbox a couple of months ago from Google. If web apps will replace C then why is the hottest web company of all looking for C programmers?
Phone systems are meant to just work and often the idea is that if it's still working it should be left that way. I contract for an ISP that has it's own adsl equipment and have an access card that gets me into several Bell Canada Buildings in Montreal and one in Toronto.
The telephone world is a weird mix of the state of the art and old.
I regularly see software that comes on 9 track reels and other ancient equipment.. My biggest shock was seeing in downtown Toronto equipment that still uses vacuum tubes.
C is still a moving target.. slowly but still moving. Every Decade or so they release a new standard (C89, C99 etc).
Some tasks are still more suited to C than C++ just like some tasks still need ASM.
Generally my policy is to try things on my PC first and then the laptop. Once I'm sure a feature is stable then I try it on my server and my customer's servers.
If your worried about the feture I would suggest waiting until 2.6.22 but most of the complaints about it on the kernel mailing list involved the machine just refusing to boot during the rc cycle so it should be safe.
Except that given human nature that's not practical.
Throughout history there have been people who for whatever reason want to take advantage of others so we are stuck making laws to prevent that. Laws that are supposed to make people play nice together. For instance I'm not allowed to just walk up and punch you in the face no matter how good an idea I think that is.
My right to do what I want doesn't infringe on your right to live without being punched in the face.
Employment and housing laws are to make sure that certain people don't get relegated to slums or prevented from making a living just because we don't like them. Those laws were put in place because people did exactly that.
Or should we go back to black districts and white bathrooms? "Hey it's my bus and I think people I don't like should have to sit in the back."
That's partially true. I have all the rights in the world to dislike you for whatever reason I want but I should not and do not have any right to deny you what sould be rightfully yours.
I cannot deny you a job because I don't like your non work related lifesyle.
I cannot deny you a place to live over things that don't directly affect me.
And that is why it's only fair that certain questions cannot be asked of potential tennants.
There is. It may not mean much to you but if someone ever sent something to my ISP to have something I legitematly put up taken down it would harm my buisness dealings with my ISP since I contract with one of my ISPs adn have mutal buisness agreements with my other. The loss of reputation would cost me signifigant income and would be very actionable.
I'm sure I'm not the only person in this situation and all that needs to happen is for the RIAA to send a C&D to someone in the same position as I am.
And other religions aren't pyramid schemes and cults?
Plenty of them. Any member of the church I attend is entitled to an audited yearly finicial report stating how every last cent is spent(pastor's salary, building expenses etc). It is also followed up with an explanation and a Q&A session. I also get to vote for the board who in turn votes for the pastor.
Any church that won't offer me that is one I won't set foot in.
If the driver worked most of the time I would have less to complain about. As it sits they have a driver that is known to reintroduce bugs into the system and to make it worse won't even compile on several recent kernels while in x86_64 mode.
NVIDIA at least compiles so after buying a mid range then a top of the line ATI I've switched to NVIDA. It still annoying
Not even. Most of the phishing emails that reach my inbox don't even bother to make the URL look like the bank. They just redirect you and hope you don't bother to look at the URL at the top.
As long as a signifigant portion of the population doesn't take even basic steps to protect themselves phishing will be a prevalent problem.
AOL does this too. Somewhere on the packaging is a mention of "free internet for 3 months" but no mention of the fact that they already signed up for you and sent your credit card details to AOL.
The bank then assumes that since the card was from a large corporation you must have been the one who screwed up.
I had this happen to a friend when the PC came with an AOL install CD but it wasn't even installed on his system.
Slashdot Mirror
I hate phones for the same reason I hate instant messengers. I don't like things that demand my instant attention and interrupt what I'm doing.
If I'm working on something I can check emails when it won't affect my ability to get work done. If I'm constantly answering the phone I never get anything done.
Personally I'm not about to try and explain to my parents how to change their ssh port.. It's bad enough as it is trying to walk them through login problems. Also that server has paying customers on it and I have finally trained most of them to use winscp to transfer files.
It's important to note that the servers may not have been actually rooted. There is a large number of ssh dictionary breakin attempts on every machine I administrate on several completely different ip blocks. The worst hit is usually my personal server that tended to get hit with several thousand attempts per hour(enough that legitimate logins were a problem) before I installed countermeasures. Even now the countermeasures are locking out 5 to 8 hosts per day.
They have managed to get user accounts on a few occasions and most of the time they never even attempt to gain root. They just start scanning for new hosts.
I'm now running a python script called DenyHosts to find and lockout dictionary attacks. "apt-get install denyhosts" for debian users. Even on much more liberal settings than the default it's lowered my cpu load considerably and locks out attacks in the first minute rather than the hour it would otherwise take me to notice.
IMO there is nothing wrong with backporting new drivers (which should only affect people who use the hardware for which the new drivers are designed, not any other users of the kernel) into a stable kernel tree.
Except that in this thread people have been blaming the SATA problems on the new development method but in this case there would have been no difference.
The downside to backporting was that the differences between 2.4.x and 2.5.x were so large that the driver interfaces had a tendency to be completely different and the 2.4.x infrastructure in some cases just wasn't able to handle the newer drivers. In the case of one RAID card the 2.4.x drivers were just hopeless and I had to actually wait two weeks for 2.5.x to be stable enough and install it on my server and just hope it wouldn't crash.
"Because Linus said so" is in fact not a particularly valid answer. Yes, Linus has the right to choose the development structure the kernel is now using, but that doesn't mean it is the best way to do it for everybody. dropping the distinction between "stable" and "development" versions was a sloppy, lazy move that simply pushed the responsibility for maintaining stable released off onto the distributors. That has essentially duplicated the work a hundred-fold, because each distribution must do the work themselves. We're told that this is a "better" arrangement, but it is clearly only better for Linus and the kernel developers, because they get to do less work and be lazy when it comes to making changes: "Want to rip out the allocator and replace it with a largely untested one? Sure, why not! Making sure everything works is the distributors problem, not ours!"
Except that the old system didn't work at all. There were just too many changes to stabilize in any reasonable amount of time and while the debugging was happening the 2.4.x kernel was becoming so badly out of date that people (and distros) tried to back port changes from the 2.5.x tree.
The result was TWO unstable kernel trees and the vendor trees had a tendency to be even worse. The old system would have left those people using SATA in a worse situation then they are in now. Keep in mind that SATA came out after 2.6.x so the drivers would right now be somewhere in the 2.7.x series kernel still waiting to be debugged and the stable maintainers would be forced to try and backport the SATA drivers once again resulting in two unstable kernels
FreeDos isn't intended by Dell to be a real OS. It's just there so that Dell Can offer an OS they know they won't ever have to support so that they can tell Microsoft that they don't offer machines without an OS.
It's an end run around Microsoft. Microsoft has a hissyfit whenever vendors offer OSless boxes so they block that option but they can't object to FreeDos without having antitrust regulators breathing down their necks.
I have.. I had a co worker a few years back who never cut his hair, trimmed his beard or did laundry the stench was nasty. the company tolerated him because they thought he was good at what he did.
Turns out his installs were crap (wrong partition sizes "fixed" with symlinks) and his code was a disorganized unmaintainable mess.
I'm all for t shirts and relaxed dress code but bathing should be mandatory.
RactOS has much of the same problem Wine does: A pile of mostly undocumented internal apis that need bug for bug compatibility or random acts break.
Wine has been "almost done" for close to 10 years now.
It sounds like a somewhat exaggerated version of something Tom Mabe did here: here
XBMC is the only reason I bought an XBOX and I spend far more time using the media functions than I do playing games so I don't care from being banned from XBOX live (which I never use anyways)
This is just not true. For every RMS or ESR we have a Linus Torvalds or an Andrew Tridgell who seem to do a very good job of making clear points and get quoted often.
That example was amusing for me considering the job ad I had in my inbox a couple of months ago from Google. If web apps will replace C then why is the hottest web company of all looking for C programmers?
Phone systems are meant to just work and often the idea is that if it's still working it should be left that way. I contract for an ISP that has it's own adsl equipment and have an access card that gets me into several Bell Canada Buildings in Montreal and one in Toronto.
The telephone world is a weird mix of the state of the art and old.
I regularly see software that comes on 9 track reels and other ancient equipment.. My biggest shock was seeing in downtown Toronto equipment that still uses vacuum tubes.
C is still a moving target.. slowly but still moving. Every Decade or so they release a new standard (C89, C99 etc). Some tasks are still more suited to C than C++ just like some tasks still need ASM.
Or better yet why can't you just copy the blasted thing to your own site if your going to use it?
Is there some technical reason I'm not aware of that means it has to stay somewhere central?
Generally my policy is to try things on my PC first and then the laptop. Once I'm sure a feature is stable then I try it on my server and my customer's servers. If your worried about the feture I would suggest waiting until 2.6.22 but most of the complaints about it on the kernel mailing list involved the machine just refusing to boot during the rc cycle so it should be safe.
Except that given human nature that's not practical.
Throughout history there have been people who for whatever reason want to take advantage of others so we are stuck making laws to prevent that. Laws that are supposed to make people play nice together. For instance I'm not allowed to just walk up and punch you in the face no matter how good an idea I think that is.
My right to do what I want doesn't infringe on your right to live without being punched in the face.
Employment and housing laws are to make sure that certain people don't get relegated to slums or prevented from making a living just because we don't like them. Those laws were put in place because people did exactly that.
Or should we go back to black districts and white bathrooms? "Hey it's my bus and I think people I don't like should have to sit in the back."
That's partially true. I have all the rights in the world to dislike you for whatever reason I want but I should not and do not have any right to deny you what sould be rightfully yours.
I cannot deny you a job because I don't like your non work related lifesyle.
I cannot deny you a place to live over things that don't directly affect me.
And that is why it's only fair that certain questions cannot be asked of potential tennants.
There is. It may not mean much to you but if someone ever sent something to my ISP to have something I legitematly put up taken down it would harm my buisness dealings with my ISP since I contract with one of my ISPs adn have mutal buisness agreements with my other. The loss of reputation would cost me signifigant income and would be very actionable.
I'm sure I'm not the only person in this situation and all that needs to happen is for the RIAA to send a C&D to someone in the same position as I am.
And you take their word for it?
Rule #1: Spammers lie.
And other religions aren't pyramid schemes and cults?
Plenty of them. Any member of the church I attend is entitled to an audited yearly finicial report stating how every last cent is spent(pastor's salary, building expenses etc). It is also followed up with an explanation and a Q&A session. I also get to vote for the board who in turn votes for the pastor.
Any church that won't offer me that is one I won't set foot in.
If the driver worked most of the time I would have less to complain about. As it sits they have a driver that is known to reintroduce bugs into the system and to make it worse won't even compile on several recent kernels while in x86_64 mode. NVIDIA at least compiles so after buying a mid range then a top of the line ATI I've switched to NVIDA. It still annoying
Not even. Most of the phishing emails that reach my inbox don't even bother to make the URL look like the bank. They just redirect you and hope you don't bother to look at the URL at the top.
As long as a signifigant portion of the population doesn't take even basic steps to protect themselves phishing will be a prevalent problem.
AOL does this too. Somewhere on the packaging is a mention of "free internet for 3 months" but no mention of the fact that they already signed up for you and sent your credit card details to AOL.
The bank then assumes that since the card was from a large corporation you must have been the one who screwed up.
I had this happen to a friend when the PC came with an AOL install CD but it wasn't even installed on his system.
You don't have to put your home address and phone number there. A PO box and pager would be fine as long as it can be used to contact you.