Re: Hard to believe but...
- From: Claus Dragon <claus@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 19 Mar 2007 23:53:55 +0100
Words to the wise, Ashikaga <citizenashi@xxxxxxxxx> wrote:
On 95khz Claus Dragon <claus@xxxxxxxxxxxxxxxxxx> shrieked:
Words to the wise, Ashikaga <citizenashi@xxxxxxxxx> wrote:
And other options that I could not understand a thing. And it says after
the config file is written, I need to run some update routine or something,
except I don't even know where that update executable is located....
find . -filename
That's nice, except I don't even know the filename I am suppose to search
That is normally listed in the help you read. Or should be.
Another possibility is just to look for the directory.
LOL, that's exactly what the problem is. Ubuntu's help told me it's my job
to find them out....
Well, how should Ubunty know about some app you are using?
And now you told me the same thing. LOL!
Well, normally you should know where that software got installed, you
didnt pay attention then (due to simply not knowing that paying
attention is important for this), so you have to look now.
I guess technical people all think alike.
Well, there is a problem, you know the tools now, you should be able
to find it.
Obviously we don't even have a clue, that's why it's not easy for us (i.e., I can run the procedure just fine,
but I need to have the lead first), and the reason we consulted a help file
(or asked you guys for help).
Well, you said:
And other options that I could not understand a thing. And it says
after the config file is written, I need to run some update routine or
something, except I don't even know where that update executable is
So, I take it there was some info about what to do next which is what
you have to do next.
Anyways, thanks for the good gesture. This is already too much
coming from you. ;-p I really wish the search would be as easy as dir/w/s
That is the same as ls - artlR
ls stands for list, right? I think I read that.
Of course, you can also use ls -artlR <filename>, but that is less
Of course you can also do: ls -artlR | egrep -i
That sounds a little technical, but I'll try them out and see the
differences myself. That should enhance the understanding.
It is not technical at all: ls == list directory you are currently in.
-artlR are a few parameters, well-documented in the man page.
That just means you have the contents of the current directory and all
sub directories, the group of those files is being sent to grep which
just goes through them filename by filename and looks for the
expression you specified in the ''.
I wonder if there is a help command on individual command (i.e., help
[command] under DOS 6.0 or later). I typed help in terminal and it gave me
a list of command, but not much explanation (the kind that's suppose to
refresh your memory rather than tutoring a newbie like me). I'll try that
out and see if it works.
Help should give you a list of commands. You can look at each man page
then, which contains the command and all options, a desription, an
explanation of all parameters, an example or two and a few other
things not of big interest to a user.
And the command to read a help file on a command is:
For some reason, the command pwd reminds me of pawned.... (random thought)
Print Working Directory.
BTW, I noticed some Unix commands there are some extra spaces as
oppose to DOS. For example, is cd/ or find .-filename acceptable under
No it isnt. And it is a bloody Dos hack that it is.
I have no idea the layout of Linux's system files, unlike the very familiar
Windows platform which I've been using for decades. That should be among
the first things I need to learn.
easy: user stuff is found on /home/<username>
binaries are at /usr/local:/user/bin/ ....
optional software is at /opt/ ...
Ah. I figured out the user part. That's like Program Files under Windows.
But the last two, that totally makes sense now. :-) What kind of software
is optional software? Is it like drivers?
No, /usr/* is not like program files, that is /opt, more or less.
More or less because most executables are in /usr/ (or linked to usr/
from /opt/), but not all.
That depends on the software you are installing.
Oh, and if you are looking for a certain command/program/application:
It seems knowing these computer terms give me an understanding of Windows
Registry too... (though syntaxes are different, but the idea is the same,
Erm, no, the idea of registry does not exist anywhere else. Instead of
a centralised registry file, you have executables, which are linked to
/usr/* (/usr/bin:usr/sbin:/usr/local/bin) which normally have a .conf
file somewhere next to itself.
Having said that I realize that the Solaris 10/11 system works a bit
like a registry. Instead of a mass of config files, you have a
centralised "services" system now. Makes sense on huge server
help document is still too technical for everyday user (though I must say
the document is very comprehensive and I've been able to find every subject
I asked for, except I don't understand most of the stuff written there).
I tried to write a simple config file (actually I copied the codes from the
Internet...), except I was blocked from writing to the root directories. I
thought I am the administrator.... I made sure all the read, write,
executive rights were checked, but still no avail....
chmod 777 <filename> is your friend.
OR, better: su - root <enter password> then try to edit the config
iAshi is having a bad case of information overload....
What does chmod stands for?
Just type man chmod and read, everything will become clear.
You know why I asked the definition, right? I hope I don't sound annoying.
No, I am just helping you the Unix way :>
It's super hard for me to remember anything if they don't stand for
something. Like dir stands for directory, so that's how I remember it.
The first lines of the help file:
CHMOD(1) User Commands
chmod - change file access permissions
What does su stands for?
That is like the run as thing in Windows, only that you get a whole
root shell instead of one command only.
Ah. Windows's Run or DOS prompt.
In a way. Though more like the other way round.
Is space between - and root necessary?
As a rule of thumb, if someone posts a shell command, it is normally
typed the way you are supposed to do it.
Okay. I thought it can be lenient. I noticed Unix likes strict rule over
flexibility for well-formness.
Well-formness is *not* flexible. A well-formed command is anything but
flexible, it is very strict.
Why enter a password (which I assume there must be something that prompts the OS it's an admin thing).
Because it says: 'Hello, I would like to get a root shell, that is if
I remember the password'.
Actually this one needs no explanation now. Knowing what su stands for
explains everything. Thanks.
Another rule: You have to read a lot. Really, a lot.
Claus Dragon <clauskick@xxxxxxxxxxxxxxx>
d++ e++ T--
"Coffee is a mocker. So, I am going to mock."
- Me, lately.
- Prev by Date: Re: Ultima 5 on Windows: any way to hack my characters?
- Next by Date: Re: Sometimes it looks easier than it is
- Previous by thread: Re: Hard to believe but...
- Next by thread: Re: There goes yet another optical drive...