Will I ever get this message in Linux?

[slvadcjelli42]

Out of all the annoying, illogical, frustrating things that are driving me away from Windows (and currently towards Linux), the one that seems to get to me the most is when i get flat-out "Access Denied" messages for stuff on my own computer. Granted, most of those come when you try to do something with system files and folders, but why shouldn't I have the right to do that (after all, it is MY computer, for crying out loud!)? Besides, it isn't only those files (I found a few of those "content.ie5" type files mentioned on this site myself a few years ago...)

Now, to the question: Does Linux ever give you one of these types of messages (I mean, of course, when you SHOULD have full access, such as when logged in as root)? I remember reading that it is possible to wipe out your entire file system with a single command when root. Not that I would do that, but I tend to believe that I should have the right to act how I want to on my computer, even if that happens to consist of acting like an idiot. It's the principle of the matter  

I feel like the answer couldn't possibly be anything but "no, of course not" but I think I'll rest a little easier when I've heard someone say it themselves  

[Faust]

Not as root.  As normal users you get "are you sure?" messages, or "fuck off you can't do that, you don't have sufficient priviledges" messages.  You can get "are you sures?" as root too but its configurable.  rm -i i believe for are you sures...
if you wanna screw your partitions while running and youre root, you get to go the hell ahead.  

[slvadcjelli42]

Alright! Thanks, that DOES make me feel better.  I'm glad it won't get in my way, whether I'm doing something good, bad or just plain weird. It's good to know that I won't have to spend any more time shaking my fist at one of those damned "Access Denied" windows once I switch.   :rolleyes:

P.S. "Are you sure?" messages are fine, I don't usually mind those things at all  

[ July 21, 2003: Message edited by: Dirk Gently ]

[Faust]

Just remember not to rm -rf that massive /mnt directory.  

[Meshuggener]

It's true, I shot myself in the foot with that command while reading a book as a noob.  I thought I was removing a not-empty directory, but if I read the next paragraph I would have realized that it was the command to erase everything on your HD.

[slvadcjelli42]

ouch!

[preacher]

http://hackthiscomputer.cjb.net/rootdenied.png

[slvadcjelli42]

What? no!! how??   :confused:

[flap]

quote:Originally posted by Dirk Gently:
What? no!! how??    :confused:  

Because the file isn't executable.

[slvadcjelli42]

oooh haha of course! And I was just reading about the file permission settings and that sort of thing a little while ago, too. I should have realized that. But, something I still don't get... If you simply enter the name of a file with no command, it assumes you are trying to execute it (as opposed to open/read it, i guess)?

[flap]

yes

[Stryker]

quote:Originally posted by Dirk Gently:
If you simply enter the name of a file with no command, it assumes you are trying to execute it (as opposed to open/read it, i guess)?

it depends on if the file is in $PATH or not. If not, it won't do a thing with it unless u tell it to execute (./myfile) simply typing "myfile" won't do anything. and if u do ./myfile it won't execute unless the execute permissions are set. If you want to open/read a file, you need to use a program to do it. The most basic way, use cat. (cat myfile)

[slvadcjelli42]

Oh, ok. I think I've got it now, thanks.