Read this NOW:
Then work your way throught the following:
ubuntu help and wiki:
aysiu's page (he's a member here):
The greatest of all linux sites:
Especially read the guides there:
Start with these
Bash Guide for Beginners
GNU/Linux Command-Line Tools Summary
A couple of books:
A Practical Guide to Ubuntu Linux (Sobell)
For linux in general:
Unix Power Tools, Third Edition (Powers, Peek, O'Reilly, Loukides)
I had to practice my Bash skills (EDIT: I know practice is a good thing and I will not stop with that )
everything went fine until I played a little to much with a shredder command
Luckily for me I were not practicing in sudo mode so the only files affected where all the non-library and non-hidden files in my Home folder.
I don't know why the command shredder worked without sudo?
why it only worked on visible files?
why it only affected the files and not wandered into the directories?
why I still were able to see the files after the shredder episode (I were not able to open them just see them)?
All the files I lost were just some test scripts of no importance. But there were one file "lshw.txt", I can't remember I made a file named that. So is that an important one?
I think I have learned a lesson about playing with dangerous machinery near my home directory, I hope.
I am one page away from completing the Basher guide you found to me
wow thank you... I wil definetly look through that.
Last edited by RobbingDaHood; July 19th, 2008 at 04:45 PM.
Those are indeed excellent resources he pointed you to and exactly of the type that will get you the answers you seek. Reading and trying things out is the only way to go. To those that said linux from scratch is not something to start right away I might disagree. If you have great interest and great motivation, you can tackle tasks that would otherwise be out of reach. Now you may fail more often at trying linux from scratch than someone that has read everything there is about linux first, you'll learn a lot by failing. And indeed it may be very daunting and too difficult at first, but as long as you don't worry about that it may be fun too. Just don't forget to read as you go. The faster you iterate your read-try-fail cycle the more you'll learn.
So my advice is to either have a testing partition where you really don't worry about what commands you run because you can just wipe it out and restore it, or learn how to use virtual machines like qemu or Virtualbox and play inside those. They are really easy to wipe and restart so you can test whatever you like. That method also has less likelihood of damaging your other paritions while you are testing as well.
Oh, also as you go you may find a particular aspect you are more interested in than others, if it is the kernel you'll want a kernel internals book and you'll want to compile your own custom kernels and read the kernel source, if it is network security you'll want to get a good book on that and find the source code for the various security tools/systems, same for networking/graphics/device drivers/whatever. If you want to learn it all, start with what interests you most.
Last edited by Taxman415a; July 19th, 2008 at 05:48 PM. Reason: add a bit
One thing I have found very instructive is to install VirtualBox, install Ubuntu or another distro onto that, and just use that as a test bed for messing around with and generally doing all the things you wouldn't want to do with an actual machine. VirtualBox can take snapshots at any time so you can always revert back to these if anything goes wrong.
I've done all sorts of things in VirtualBox that I wouldn't do on an actual machine for fear of wrecking my install. For instance, I compiled my own Linux kernel in a Xubuntu install in VirtualBox, and I wouldn't dare do this yet in an actual machine for fear it might bork it. It's also good for doing a command-line only install and adding your choice of lightweight window manager, file manager etc. It's also very handy for trying new distros as you can go through the install process and if anything goes wrong you can still get online using the host machine.
Immorality: the morality of those who are having a better time. -H. L. Mencken
welcome to teh light....and the forums !!
i alsp suggest some m
linux books from anyplace that sells computer books.and even unix as well(they have much in common ).
i read somewhere there are just over 18,000 shell commands.i might know 5 LOL but i can usually get fixed what i am seeking to fix.my unstarted personal project is a barebones 'buntu for 3d gaming with nvidia and ati drivers included.i may well try it with sabayon or gentoo and see how that goes.
i also like tinkering with a minimalist live cd that runs in memory and doesnt intall(unless you want it to).puppy is one,and i think it is cool.if you want to explore and tinker try puppy and do what you can.it runs off a live cd so you cant possibly mess up your good computer settings but you also get to explore the linux way of doing things
"when you have to shoot--shoot dont talk"
Tuco Benedicto Pacifico Juan Maria Ramirez (known as the Rat)
I will try that right away (setting up a VirtualBox)
Last edited by RobbingDaHood; July 19th, 2008 at 09:46 PM.
Can someone explain to him the Power Cycle Bug with HDD's and Linux in more details please
i hear a lot of books going on here, i thought these were depreciated after the invention of the ARPA net.
google is your friend