Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
you might be able to view them but can you edit them? and how about going to the root home directory /root . you should get permission denied.
you could set the permissions of everything on the drive to be only accessible the owner of that file
that would look like this
chmod go-rw / -R
**READ ON BEFORE DOING THIS***
personally i wouldn't do this cos i don't think its a bright thing to do. the reason its not mentioned anywhere in tutorials is because its not the done thing. if you think about a windows pc you can still access the windows directory even though you aren't administrator.
i think the above command would seriously harm your installation though. what it should do is make it so you can go through every directory but not read or write to them.the only problem with this being that if any program you run requires read access to a config file then it'll be a bit screwed.
its not being able to view files that poses a threat but being able to modify and execute them that does.
for example try doing /sbin/reboot as your test user.
it shouldn't work because your not root.
another example should be the /etc/shadow file.
if you try a 'cat /etc/shadow' as a normal user you'll be told to take a hike.
nothing to it really. it just sets where the / directory is
very handy if you boot of a cd and mount your hard drive linux install. you can then chroot to the base dir of the hard drive install and away you go
pretty un responsible for this 'help' .. i was looking for help on lighthttpd and came across this.. now why would anyone recommend to change en masse the root perms :s .. now hes gonna have fun wqith this vps... everythings borked if hes done this the wrong way.. y
you should clarified at start, what exactly you are doing.. your minor warning, does not really say "DONT DO THIS ON YOUR VPS' .. hell, you have just made it a one usert box basically.. very unresponsible help i would ignore..and maybe use man abit, and look into usergroups andusing your conf files for the usergroup wich would have taken the same time anyhow.. or same amount of writing.. so why give dodgy help.. give proper help or let someone else do it properly :s
oh sheeshus lol.. did not even notice that date when i answered.. ok.. new to forum 'ing so il learn from it lol.. my bad...
on another note..il get to posting something wich can actually stimulate.. sorry for r opening this, just iognore it.. lol..sheesh.