To me, no. However it angers me that FUD can be spread like this to a large degree, and people just soak it up.
Just reading through some of the 'comments' on OSS. Raymond Keating calls OSS 'the borg'! What the hell? Microsoft is more the borg than OSS. Since when did freedom become a restriction?
Sonia Arrison suggests that OSS is just full of a lot of pimply teenagers is so far from the truth, I just don't get it. Searching for the 'online' comment she mentions in google comes up with nothing, (that may mean nothing though).
Wayne T. Brough mentions that there are more incompatibilities with OSS than commercial software. When are these people going to get it, that most of the people who write OSS are the same people who write for commercial companies!
There are so many more statments like this. Grrrrrr. I don't think we should just ignore it like this. This is the problem. People actually listen to FUD. The more FUD people get, the more brainwashed they get. You'll be amazed at what people can believe once they are brainwashed.
But you don't need to upgrade the kernel, unless that security leak occurs. If I had a choice between updating the kernel on Windows vs Linux, I know which I'd prefer.
I still think it's a real media throw-away line that will get quoted by at least one person. It's an annoyingly inaccurate non-statement.
much more frequent in Linux than in proprietary systems from Microsoft or Sun
Huh? Does it!? Since when? I like these throw-away lines the media people dish out. What is their basis for this statement? Even when they see Linux obviously succeeding, they dish out a statement like this.
I certainly don't have to patch my Linux boxes as frequently as my Windows boxes. Actually... no... wait, they're right! I only need to patch Windows once. Ctrl-Alt-Del -> Boot Debian CD.
The good thing with coding in Java, is that now it doesn't JUST support PCs, I could run this on our 90 odd HPUX/Solaris/Linux servers at work. By coding in Java you instantly broaden your server base. Heck run it on a Cray, (if it has a JIT). That alone surely makes up for any slowness that may be apparent in Java.
Why go to Gigabit? A 100BaseT LAN on a switch can easily handle several video loads. Several of my PCs can pump out 6Mbit/s, (DVD quality). But there is still 94Mbit/s left! Surely you're not going to want to watch 16 videos at once, (100 6/)?
Also, I don't know of many PCs that will be able to make use of the GigaBit speeds to it's full extent.
I agree with Dr. Schwartz to some extent. Australia is seeing a huge amount of privitization throughout all industries. We are having to make a huge amount of choices for everything. I know the US have had it for years, but I get annoyed having to make too many choices every step of the way. I see it as a waste of time and energy that can be better spent elsewhere.
The other side of the coin is, though, that we need to have choices to avoid a monopoly/dictatorship. Whichever way you look at it - Microsoft is a dictator. They tell us to jump and we say 'how high?'.
This is unsatisfactory. So for this reason alone I prefer to have choices. Even if I do get annoyed, I would much prefer that I get annoyed than have some monopoly dictating my life.
The other thing to note is: Microsoft is treating the OSS movement as a THREAT to it's existance. Therefore, they are going all out to get at OSS in anyway possible. I see this study as FUD by Microsoft, (whether initially intentional or not).
Re:I'm not sure how accurate this statement is.
on
MRAM in 2004?
·
· Score: 1
I have 5 systems running 24/7. I leave them on to reduce wear and tear. Surge currents do horrible things to electronics. But, then again - if you use a stable O/S why shutdown? Really?
It's a funny situation. But the usual reasons for management not wanting to use open src is: 1. Have the ability to finger point when things go belly-up. 2. Have the ability to 'call' a named party for assistance, (usually complete with SLA).
The stupid reality of it all is that: 1. You can't really finger point these days because of EULAs. 2. If you have a good SysAdmin team, you very rarely get to use any support provided.
We have around 80 systems, (HP, Sun, Linux, Windows). All running varying development/test environments. We use open src very heavily. This mainly is due to the fact that we're a development house, (yes - they still do exist!), and also we've managed to convince management that it actually saves money. But, of course, it depends on your environment.
We also use some third party software, (we really can't get away from ALL of it). We use Oracle, ClearCase, Rose, JBuilder, plus others. We pay close to $1m per annum for support costs, and we haven't called up once in the last year!! For that you could add another handfull of developers and SysAdmins to your team. But....
The other problem that I've come across is that you can argue till you are blue in the face. But you might find the bean counters say that there's no money in the budget for extra people, yet the budget clearly says you can spend $1m on software costs! Doh! Different money buckets you see. Head count/assets versus software costs.
Sometimes you just have to think like 'them' sometimes to be able to put your argument.
Mmmm. I don't agree with this. For one M$ has managed to overcome a lot in the past years. It's managed to kill off a lot of opponents that stood in it's way.
I can't stand M$ just as much as the next Linux geek, however, that said good things, (ha - yeah right!), don't last, and M$ will fall down, but because none of us here have 20/20 visions of the future we really can't speculate accurately the when/how/why.
You never know, the OS technology landscape of the future may be
* M$, Open Source, IBM. * Open Source, IBM, HP, Sun * IBM, M$, Open Source, HP * etc, etc, etc, etc
Basically we don't know, we can hazard a guess, but it still remains a guess. One thing for certain though. SCO won't be there in it's present form. These lawsuits are the convulsive habits of a dying company.
Sun: The house structure would be strong and stable, but bits would occasionally fall off, like doorhandles and drawers. You would also need great gobs of cupboard space for all that coffee.
HP: Foundations would be a bit unstable, but the walls would be 10 inches thick, doors 4 inches thick. You would have to rip up the foundations every time you wanted to add another room.
Linux: You would have so many rooms with so many decour choices that you'd get lost. You'd have the chance, though, to really DIY. Of course this would mean that the house would never get finished.
AIX: Would need extensive modifications to kitchen cupboards just to install a toaster. Would require you to press the garage door opener to be able to have a shower.
DOS: Would be a one room house with a ceiling height of 6' 40". (Why would you need it to be taller?)
Windows: Would have to keep going out to the power board and turning the power off and on. You could only use M-rated applicances in the house. The house voltage would be 189V, (reguardless of country). And you wouldn't be able to look out of the windows half the time because of a blue haze.
I use this method as well. However the problem I have with the system is interrupt latency. Quite often interrupt response times could be as high as 1 minute. Even after repeated 'yell' commands, (especially when their faces are glued to the TV).
Sometimes the 'demand' and 'ultimatum' commands don't even get through.
Actually the problem could also be due to packet filtering. It is possible that they have a rather neat packet filter that filters out all those commands.
wife: "Stop that damn clicking and come to bed!" husband(skating on thin ice): "But I bought you some earplugs. Why aren't you using them?" wife: "I'm not going to wear those !@%!$#%@#^ earplugs just so you can click all night!" husband(now in the dog house): "But you'll be able to go to sleep then!" wife: "I can't go to sleep with !@$%#%^^ earplugs in my ears and you clicking all night."
One way of getting the audible keypress feedback and have a quiet keyboard is to use audible key clicks. Some PC BIOSes support this, also every OS supports it as well. You could then find an ultra quiet keyboard and then don a set of headphones. Granted there would be a delay between keypress and sound, (depending on the OS and speed of your poota). But if you use the BIOS to provide the keyclick there shouldn't be much noticable delay. If you don't like headphones then you can just pipe it to a speaker and adjust the volume.
I suffer from exactly the same problem. My office is directly opposite the main bedroom. I've had to dampen the sound from the fans and disks, by doing the old trick of adding a diode inline to the fan power, and putting in foam baffles.
However, keyboard click is a problem. I find myself attempting to type quietly which tends to slow me down somewhat. As a matter of fact mouse clicks are a problem too. When I'm coding I very rarely use mouse clicks, (if at all), however surfing the web is something else. The somewhat sparodic mouse click noise tends to wake my wife up more.
controlling four different compilers (gcc 3.1, Sun Forte, Irix MIPSpro and Visual C++ 7)
Couldn't you just use gcc across all systems? There are also plenty of opensource IDEs around. We use Eclipse along with ClearCase. Very good for cross platform.
Every company/ISP/system should enforce password changes/passwd restrictions I'm all in favour of it.
However, it IS possible to go the other way, and provide less security. My company is a multi-national and we have a huge network. Forced password changes were implemented around a year ago, because of a hacker wandering around. That's fine to do that, but then we have around 5-9 accounts, (depending on what you're doing), and that's INDIVIDUAL accounts. That's INDIVIDUAL passwords. It's made slightly easier, by not having passwd restrictions.
I can tell you that the passwords that are going to be used by users will be something along the lines of 'abcdefgh', then 'bcdefghi'. The forced passwd changes is a monthly grief for everyone. Everyone HATES it. And so they should.
Some of you seem to be missing the point that coding is very similar to book writing.
There are several similarities:
Creativity - if you don't have this, then neither coding nor writing will succeed.
Finding the zone - most, (if not all), book writers PREFER to NOT be disturbed. This disturbes their train of thought. Writers, (like coders), like to envelop themselves in their story so that they can write better. Similarly, if a coder is on a train of thought they don't want to be disturbed either.
Style - whether you're writing a novel, or cutting code your opinion and style will ALWAYS surface. Whatever you write will always be an extension of yourself.
Debugging - You debug code, you proof read books. Same thing!
The only differences I can readily think of, (correct me), is the fact that on big projects you have several coders, as opposed to writing books you always, (almost always), have one.
Of course this highlights the question, "Are you talking about novels or other books?". Well, I think both apply.
Also, all this doesn't mean to say that a good book writer will be a good coder - it's a different thing. Coders need to have both sides of the brain well developed, (technical AND creative).
My firewall has an uptime of 317 days, my vmware PC has 195, (all running Linux), but oh yeah my games pc, (windows 98), has to be rebooted every day.- OK it would be an advantage to those uptime challenged OS.
Slashdot Mirror
To me, no. However it angers me that FUD can be spread like this to a large degree, and people just soak it up.
Just reading through some of the 'comments' on OSS. Raymond Keating calls OSS 'the borg'! What the hell? Microsoft is more the borg than OSS. Since when did freedom become a restriction?
Sonia Arrison suggests that OSS is just full of a lot of pimply teenagers is so far from the truth, I just don't get it. Searching for the 'online' comment she mentions in google comes up with nothing, (that may mean nothing though).
Wayne T. Brough mentions that there are more incompatibilities with OSS than commercial software. When are these people going to get it, that most of the people who write OSS are the same people who write for commercial companies!
There are so many more statments like this. Grrrrrr. I don't think we should just ignore it like this. This is the problem. People actually listen to FUD. The more FUD people get, the more brainwashed they get. You'll be amazed at what people can believe once they are brainwashed.
But you don't need to upgrade the kernel, unless that security leak occurs. If I had a choice between updating the kernel on Windows vs Linux, I know which I'd prefer.
I still think it's a real media throw-away line that will get quoted by at least one person. It's an annoyingly inaccurate non-statement.
much more frequent in Linux than in proprietary systems from Microsoft or Sun
Huh? Does it!? Since when? I like these throw-away lines the media people dish out. What is their basis for this statement? Even when they see Linux obviously succeeding, they dish out a statement like this.
I certainly don't have to patch my Linux boxes as frequently as my Windows boxes. Actually... no... wait, they're right! I only need to patch Windows once. Ctrl-Alt-Del -> Boot Debian CD.
The good thing with coding in Java, is that now it doesn't JUST support PCs, I could run this on our 90 odd HPUX/Solaris/Linux servers at work. By coding in Java you instantly broaden your server base. Heck run it on a Cray, (if it has a JIT). That alone surely makes up for any slowness that may be apparent in Java.
Why go to Gigabit? A 100BaseT LAN on a switch can easily handle several video loads. Several of my PCs can pump out 6Mbit/s, (DVD quality). But there is still 94Mbit/s left! Surely you're not going to want to watch 16 videos at once, (100 6 /)?
Also, I don't know of many PCs that will be able to make use of the GigaBit speeds to it's full extent.
I have to say several things:
I agree with Dr. Schwartz to some extent. Australia is seeing a huge amount of privitization throughout all industries. We are having to make a huge amount of choices for everything. I know the US have had it for years, but I get annoyed having to make too many choices every step of the way. I see it as a waste of time and energy that can be better spent elsewhere.
The other side of the coin is, though, that we need to have choices to avoid a monopoly/dictatorship. Whichever way you look at it - Microsoft is a dictator. They tell us to jump and we say 'how high?'.
This is unsatisfactory. So for this reason alone I prefer to have choices. Even if I do get annoyed, I would much prefer that I get annoyed than have some monopoly dictating my life.
The other thing to note is: Microsoft is treating the OSS movement as a THREAT to it's existance. Therefore, they are going all out to get at OSS in anyway possible. I see this study as FUD by Microsoft, (whether initially intentional or not).
I have 5 systems running 24/7. I leave them on to reduce wear and tear. Surge currents do horrible things to electronics.
But, then again - if you use a stable O/S why shutdown? Really?
It's a funny situation. But the usual reasons for management not wanting to use open src is:
1. Have the ability to finger point when things go belly-up.
2. Have the ability to 'call' a named party for assistance, (usually complete with SLA).
The stupid reality of it all is that:
1. You can't really finger point these days because of EULAs.
2. If you have a good SysAdmin team, you very rarely get to use any support provided.
We have around 80 systems, (HP, Sun, Linux, Windows). All running varying development/test environments. We use open src very heavily. This mainly is due to the fact that we're a development house, (yes - they still do exist!), and also we've managed to convince management that it actually saves money. But, of course, it depends on your environment.
We also use some third party software, (we really can't get away from ALL of it). We use Oracle, ClearCase, Rose, JBuilder, plus others. We pay close to $1m per annum for support costs, and we haven't called up once in the last year!! For that you could add another handfull of developers and SysAdmins to your team. But....
The other problem that I've come across is that you can argue till you are blue in the face. But you might find the bean counters say that there's no money in the budget for extra people, yet the budget clearly says you can spend $1m on software costs! Doh! Different money buckets you see. Head count/assets versus software costs.
Sometimes you just have to think like 'them' sometimes to be able to put your argument.
Mmmm. I don't agree with this. For one M$ has managed to overcome a lot in the past years. It's managed to kill off a lot of opponents that stood in it's way.
I can't stand M$ just as much as the next Linux geek, however, that said good things, (ha - yeah right!), don't last, and M$ will fall down, but because none of us here have 20/20 visions of the future we really can't speculate accurately the when/how/why.
You never know, the OS technology landscape of the future may be
* M$, Open Source, IBM.
* Open Source, IBM, HP, Sun
* IBM, M$, Open Source, HP
* etc, etc, etc, etc
Basically we don't know, we can hazard a guess, but it still remains a guess. One thing for certain though. SCO won't be there in it's present form. These lawsuits are the convulsive habits of a dying company.
The designation 'System Templar' has a certain 'The saint' ring to it. Not many SysAdmins are reguarded as saints.
Actually, you are assuming that that is the speed per wire which isn't right.
320Mbps = 320 / 16 = 20Mbytes/s
320Mbps = 320 / 32 = 10Mbytes/s
SCSI1 is 8bits wide, SCSI2 is 16bit wide, and SCSI3 is 32bit wide.
Anyway all these figures are wrong because the SCSI3 standard is a LOT faster than 10Mbytes/s.
You can buy the hardware from here
Actually more likely to be:
Sun: The house structure would be strong and stable, but bits would occasionally fall off, like doorhandles and drawers. You would also need great gobs of cupboard space for all that coffee.
HP: Foundations would be a bit unstable, but the walls would be 10 inches thick, doors 4 inches thick. You would have to rip up the foundations every time you wanted to add another room.
Linux: You would have so many rooms with so many decour choices that you'd get lost. You'd have the chance, though, to really DIY. Of course this would mean that the house would never get finished.
AIX: Would need extensive modifications to kitchen cupboards just to install a toaster. Would require you to press the garage door opener to be able to have a shower.
DOS: Would be a one room house with a ceiling height of 6' 40". (Why would you need it to be taller?)
Windows: Would have to keep going out to the power board and turning the power off and on. You could only use M-rated applicances in the house. The house voltage would be 189V, (reguardless of country). And you wouldn't be able to look out of the windows half the time because of a blue haze.
Can't readily think of any others.
I am Duranos.
Errrr, nope, sorry doesn't help. Can you give us any more clues?
One of the joys of the Internet is that our memory of history is as long as our connection.
I use this method as well. However the problem I have with the system is interrupt latency. Quite often interrupt response times could be as high as 1 minute. Even after repeated 'yell' commands, (especially when their faces are glued to the TV).
Sometimes the 'demand' and 'ultimatum' commands don't even get through.
Actually the problem could also be due to packet filtering. It is possible that they have a rather neat packet filter that filters out all those commands.
Oh well...
Yeah right - I can just imagine it.
wife: "Stop that damn clicking and come to bed!"
husband(skating on thin ice): "But I bought you some earplugs. Why aren't you using them?"
wife: "I'm not going to wear those !@%!$#%@#^ earplugs just so you can click all night!"
husband(now in the dog house): "But you'll be able to go to sleep then!"
wife: "I can't go to sleep with !@$%#%^^ earplugs in my ears and you clicking all night."
One way of getting the audible keypress feedback and have a quiet keyboard is to use audible key clicks. Some PC BIOSes support this, also every OS supports it as well. You could then find an ultra quiet keyboard and then don a set of headphones.
Granted there would be a delay between keypress and sound, (depending on the OS and speed of your poota). But if you use the BIOS to provide the keyclick there shouldn't be much noticable delay.
If you don't like headphones then you can just pipe it to a speaker and adjust the volume.
I suffer from exactly the same problem. My office is directly opposite the main bedroom. I've had to dampen the sound from the fans and disks, by doing the old trick of adding a diode inline to the fan power, and putting in foam baffles.
However, keyboard click is a problem. I find myself attempting to type quietly which tends to slow me down somewhat. As a matter of fact mouse clicks are a problem too. When I'm coding I very rarely use mouse clicks, (if at all), however surfing the web is something else. The somewhat sparodic mouse click noise tends to wake my wife up more.
So what about quiet mice as well?
I notice that in the posted image Bill is wearing a tux. Looks like it's affecting him more than he thinks.
controlling four different compilers (gcc 3.1, Sun Forte, Irix MIPSpro and Visual C++ 7)
Couldn't you just use gcc across all systems? There are also plenty of opensource IDEs around. We use
Eclipse along with ClearCase. Very good for cross platform.
I prefer librarians that are orange and go 'OOK".
Every company/ISP/system should enforce password changes/passwd restrictions I'm all in favour of it. However, it IS possible to go the other way, and provide less security. My company is a multi-national and we have a huge network. Forced password changes were implemented around a year ago, because of a hacker wandering around. That's fine to do that, but then we have around 5-9 accounts, (depending on what you're doing), and that's INDIVIDUAL accounts. That's INDIVIDUAL passwords. It's made slightly easier, by not having passwd restrictions. I can tell you that the passwords that are going to be used by users will be something along the lines of 'abcdefgh', then 'bcdefghi'. The forced passwd changes is a monthly grief for everyone. Everyone HATES it. And so they should.
Some of you seem to be missing the point that coding is very similar to book writing.
There are several similarities:
Creativity - if you don't have this, then neither coding nor writing will succeed.
Finding the zone - most, (if not all), book writers PREFER to NOT be disturbed. This disturbes their train of thought. Writers, (like coders), like to envelop themselves in their story so that they can write better. Similarly, if a coder is on a train of thought they don't want to be disturbed either.
Style - whether you're writing a novel, or cutting code your opinion and style will ALWAYS surface. Whatever you write will always be an extension of yourself.
Debugging - You debug code, you proof read books. Same thing!
The only differences I can readily think of, (correct me), is the fact that on big projects you have several coders, as opposed to writing books you always, (almost always), have one.
Of course this highlights the question, "Are you talking about novels or other books?". Well, I think both apply.
Also, all this doesn't mean to say that a good book writer will be a good coder - it's a different thing. Coders need to have both sides of the brain well developed, (technical AND creative).
You must be bored.
What's a reboot? :-)
My firewall has an uptime of 317 days, my vmware PC has 195, (all running Linux), but oh yeah my games pc, (windows 98), has to be rebooted every day.- OK it would be an advantage to those uptime challenged OS.