GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm no Windows expert, but isn't Windows 2000 built on NT just like XP is? Then I would think the core of the operating system would be the same and probably lot's of exploits for 2000 could work for XP.
I suggest not looking at it. It could affect any project you continue to work on afterwards and might undo ages of work.
Worst thing you could possibly do is "help" wine or a similar project with it. It would completely wreck the project by discrediting it, and by ensuring it gets sued into the ground.
If you ever plan to work on any open source projects don't read the code, or risk taining the project.
you should be more concred with what itll do to you if you do look at it, let the windows hackers take a look at it and see how every line contains a valerablilitiy(even tho i ahvent looked at it, it would make sence sence the MS themselfs are scared of people finding valnerabilitiys ) they can use to make the next big virus/worm/nuke/whatever, besides, all that bad code might be unreadale by linux hackers/programers, and n worse caase might make you code worser code
It's gonna be a while before anything abusive is ever made as a direct result of the leaked code. Quotes about being glad to have a Mac and all the profanity hints that the inside coders were given assignments that alarmed them about the quality of the OS. Does that make sense?
2 problems, MS might go after that stuff now saying its break pantents or inelectualy property, and copywrite or whatever, so like the guy said above a bit its best not to even look at teh code so MS wont have such a big case to sue you with
Distribution: Gentoo 2004.2, Slackware 10, Windows XP, Windows 2003 Server
Conspiracy theory: Maybe microsoft did this to freak out all the win2k users. Then they will all upgrade to winxp?
I feel kind of constrained because if i take one line of code from the source, i could be sued by microsoft. There are definetly heavy consequences for taking and even reading the code because microsoft is definetly going to be paranoid about this.
But wouldn't be interesting to see how they made MSpaint? hehe
we alrdy know (or at least this is what i think), they bought the basic program from somwere else, added a few features the recylced from a word processing program, and viola!, just like every other piece of code they "made"
Originally posted by tearinox Conspiracy theory: Maybe microsoft did this to freak out all the win2k users. Then they will all upgrade to winxp?
I wondered that; but I don't think so. For one thing, XP has a fairly large shared code base with Win2K and for another thing, with Open Source looming as the big bad enemy, the last thing I would have thought MS would want to do is to both scare people about security and get them looking at upgrades : that might be the spur for some companies to look at migrating to Mac or Linux rather than staying with Windows.
Originally posted by SciYro we alrdy know (or at least this is what i think), they bought the basic program from somwere else, added a few features the recylced from a word processing program, and viola!, just like every other piece of code they "made"
Imagine if hackers look at the code and it's discovered that windows contains stolen code from SCO!