I know it can be made to work, but most business users prefer something that can be enabled in a standard distribution, not some patch that can be pulled from a mailing list. Especially because there are so many of these loose ends.
Umm...most business users don't admin a server at all. I've had to download patches for everything I admin, from the NT boxes to the Linux boxes to the Cisco routers. The PHB's just want it to work, and usually don't care how you do it.
Actually, coders abandoning the community so they could write code for money sparked the formation of gnu and the fsf. Read the gnu manifesto for the details.
It's happened before, and will happen again, except this time, on a much larger scale.
This is not accurate at all. I went to Geocities to remove my site, and I cannot even access it unless I agree to their new usage terms. Do Not Accept these terms. You will no longer have a legal foot to stand on.
I have material on Geocities that has been Copyrighted (got my Library of Congress forms and everything). I am in the process of contacting a lawyer. I will keep the community updated.
Yahoo can do what they want with their site...just not with my work.
Re:are you sure about smb in the NT kernel?
on
NT vs. Linux: Again
·
· Score: 1
Been working with NT (unfortunately) for five years now. SMB is integrated with the Server Service, which is in kernel-land. This explains the speed.
It's very possible. Check out "Windows NT User Administration" by O'Reilly Press. The book is all about managing an NT network using ActiveState's Win32 port of PERL.
NT is one of the things I have to admin at work. I have no choice. At least the PERL makes it more interesting (and flexable)
To some, this may not be "worthy science". If you don't agree with the project, don't participate.
What it does have is what we used to call "hack value". The joy of the attempt at finding alien signals justifies the attempt itself. Who cares if it's not successful? Seems to me that all scientific discoveries are lead up to by mistakes and failure. No one has ever gotten it right the first time.
As for the little script kiddies who tamper with the client and the data...I believe that a real hacker has an ethical responsibility to find the loopholes, and instead of exploiting them, present his findings to the SETI people. This would benifit the project as a whole.
Only children with no ethics would distroy something simply for the sake of distruction.
In my company, the NT servers that we use do decent file/print services. NT Terminal Server is the biggest headache I have to face. UGGGHHH! I hate that thing!!
Fortunately...all the web/intranet/sql stuff is Linux...muhahaha
Incorrect usage of "hacker" and "cracker"
on
"Hackers" are Dumb
·
· Score: 1
ahem...(cough) (cough)
I mean really...who gives a shit?
People...spend a little less time whining over a word and a little more time coding....
Here's the "BRAIN" reference...
on
Hyperbolic Trees
·
· Score: 1
Great to hear. Post the code, and maybe it will be developed faster.
I work as the SysAdmin for a medium sized company that utilizes NT/Novell/Linux. While there have been some wonderful technical suggestions in the above posts, there are skills that I have found necessary that are above and beyond being a Systems geek
1. THIS IS THE MOST IMPORTANT! Being able to effectively communicate with non-technical people. I spend much of my time planning new implementations (hardware, software, etc..etc..etc) with department managers, who range widely in their knowledge of computers. You need to have a great command of the English language, and be able to translate non-technical requests into technical reality.
2. A great deal of flexibility. A SysAdmin wears many hats. You will be asked to solve many interesting problems, particularly if the company you work for is small or medium sized.
3. You must be emotionally stable. You are the train conductor, and nobody notices the trains unless they are late (or crashed). Being a SysAdmin can be a thankless job at times.
4. Accept the fact that you will be in a continual state of learning. If you don't have a passion for this type of work, DON'T DO IT.
5. Go to www.usenix.org and check out the ethical code of the SysAdmin. Live it.
Slashdot Mirror
So.......you're saying that you keep a record of all your passwords on a Windows box?
....hmmmm....what's your ip address?
I know it can be made to work, but most business users prefer something that can be enabled in a standard distribution, not some patch that can be pulled from a mailing list. Especially because there are so many of these loose ends.
Umm...most business users don't admin a server at all. I've had to download patches for everything I admin, from the NT boxes to the Linux boxes to the Cisco routers. The PHB's just want it to work, and usually don't care how you do it.
Leave the system admin to root, baby....
Actually, coders abandoning the community so they could write code for money sparked the formation of gnu and the fsf. Read the gnu manifesto for the details.
It's happened before, and will happen again, except this time, on a much larger scale.
trog
(Sticking to Debian GNU/Linux)
This is not accurate at all. I went to Geocities to remove my site, and I cannot even access it unless I agree to their new usage terms. Do Not Accept these terms. You will no longer have a legal foot to stand on.
I have material on Geocities that has been Copyrighted (got my Library of Congress forms and everything). I am in the process of contacting a lawyer. I will keep the community updated.
Yahoo can do what they want with their site...just not with my work.
Been working with NT (unfortunately) for five years now. SMB is integrated with the Server Service, which is in kernel-land. This explains the speed.
Some nerds (like myself) are forced to support NT boxen at work. All well. I'm posting this with M7, and I like it :)
Gonna abuse the browser and see if I can contribute something back to Mozilla.
When the final is released, it will become my companies standard. Muhahaha!
I go to the gym. Five days a week. That's WHY I need a XXXL.
muhaha.
It's very possible. Check out "Windows NT User Administration" by O'Reilly Press. The book is all about managing an NT network using ActiveState's Win32 port of PERL.
NT is one of the things I have to admin at work. I have no choice. At least the PERL makes it more interesting (and flexable)
grow up....if you didn't cheat, then you shouldn't take offence.
Do you feel guilty? Is there something we should know about?
To some, this may not be "worthy science". If you don't agree with the project, don't participate.
What it does have is what we used to call "hack value". The joy of the attempt at finding alien signals justifies the attempt itself. Who cares if it's not successful? Seems to me that all scientific discoveries are lead up to by mistakes and failure. No one has ever gotten it right the first time.
As for the little script kiddies who tamper with the client and the data...I believe that a real hacker has an ethical responsibility to find the loopholes, and instead of exploiting them, present his findings to the SETI people. This would benifit the project as a whole.
Only children with no ethics would distroy something simply for the sake of distruction.
No...the answer is 47
In my company, the NT servers that we use do decent file/print services. NT Terminal Server is the biggest headache I have to face. UGGGHHH! I hate that thing!!
Fortunately...all the web/intranet/sql stuff is Linux...muhahaha
ahem...(cough) (cough)
I mean really...who gives a shit?
People...spend a little less time whining over a word and a little more time coding....
Great to hear. Post the code, and maybe it will be developed faster.
I work as the SysAdmin for a medium sized company that utilizes NT/Novell/Linux. While there have been some wonderful technical suggestions in the above posts, there are skills that I have found necessary that are above and beyond being a Systems geek
1. THIS IS THE MOST IMPORTANT! Being able to effectively communicate with non-technical people. I spend much of my time planning new implementations (hardware, software, etc..etc..etc) with department managers, who range widely in their knowledge of computers. You need to have a great command of the English language, and be able to translate non-technical requests into technical reality.
2. A great deal of flexibility. A SysAdmin wears many hats. You will be asked to solve many interesting problems, particularly if the company you work for is small or medium sized.
3. You must be emotionally stable. You are the train conductor, and nobody notices the trains unless they are late (or crashed). Being a SysAdmin can be a thankless job at times.
4. Accept the fact that you will be in a continual state of learning. If you don't have a passion for this type of work, DON'T DO IT.
5. Go to www.usenix.org and check out the ethical code of the SysAdmin. Live it.
Hope this helps.