On 25Jun2013 09:37, highskywhy@yahoo.de <highskywhy@yahoo.de> wrote:
| Di Jun 25 09:33:00 2013
| Good morning
| Thank You for help.
Please configure your mail reader to indent the quoted material.
Picking your reply text out of mine or others' is very difficult.
Observe that in this message the quite text is indented with a
marker character down the side, making it easy to distinguish the
new text.
| On 20Jun2013 14:30, highskywhy@yahoo.de <highskywhy@yahoo.de> wrote:
| | I start terminal:
| | name@nameM57p:~$
| | Is this the root?
|
| No. It is your home directory, probably something like /home/name.
| The command "pwd" will tell you ("print working directory").
| *
| What is the difference between root and home?
The root, "/", is the top of the filesystem tree. Everything can be found
from there by descending into subdirectories.
Your "home" directory is the working directory you start with when
you log in, and is a special area set aside in the system for _your_
files. It is owned by you, and you can do what you like inside it.
Other areas of the system are not owned by you; they contain system
files like executables and libraries, and of course the home
directories for other users, owned by them.
| Is root where the program files are?
Root is where you start.
Of you look at your $PATH variable by going:
echo $PATH
you will see a list of directories, separated by colons.
Program files like in those directories.
Normally there will be a "bin" directory in your own home directory,
eg "/home/name/bin", at the start of your $PATH. This lets you write
your own commands and have somewhere to put them.
| Ist home where the data files are?
Your home directory is where your files live, be they data or
program. "/home" is a common convention for where the user home
directories are stored. So in there is probably "/home/name"
containing your files, and "/home/some-other-name" containing the
files of another user.
| | A better command for your example might be:
| |
| | grep -r "thisismyAIM" . > resu.txt
| |
| | *
| | grep -r "thisismyAIM" . > resu.txt
| | Is this better then
| | grep -r "thisismyAIM" * > resu.txt
|
| Slightly. "*" will not match files/directories starting with a dot ("."),
| like .ssh. That is a convention to "hide" configuration files as a
| matter of convenience.
| It may be what you want, or it may not.
|
| *
| So if I am searching for my data files like
| text.txt
| pic.gif
| movie.avi
|
| then it is the same and I can use both like:
| grep -r "thisismyAIM" . > resu.txt
| grep -r "thisismyAIM" * > resu.txt
| ?
Pretty much, yes.
| Searching * will missing the "dot" names.
This is becuase then you type:
grep thisismyAIM *
the shell expands the "*" into a list of your files in the current
directory, so the actual command that is _run_ looks like this:
grep thisismyAIM movie.avi pic.gif text.txt
(whatever the real files are, of course). The expansion of "*" will
not include any "dot" files like ".bash_profile". This is a
convenience.
Cheers,
--
Cameron Simpson <cs@zip.com.au>
Clymer's photographs of this procedure show a very clean head. This is a lie.
There is oil in here, and lots of it. - Mike Mitten, rec.moto, 29sep1993
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (16) |
No comments:
Post a Comment