Clarence Verge wrote:
>
> Steven wrote:
> >
> > ---------------------------------
>
> I could find no /etc/resolv.conf.
> Do I create it?
yes
> If so, how do I create a 4char extension with my familiar editor ?
>
In Unix extensions aren't special like they are in DOS (.exe =
executable). They are just part of the name, or use 3 extensions
if you like.
> I tried elvis (even tho warned) and could not make it do ANYTHING.
> I couldn't get out of it without pushing reset.
> How do you get the processors attention ?
>
Learn some vi, you _will_ meet it again. Besides, it is a great
editor.
Vi (and all it's clones like vim, elvis, gvim, vile and many others)
has to operation modes. A command mode and an edit mode.
Upon startup vi will be in command mode. Pressing Escape a few times
will always get you back into command mode.
command mode commands
i insert text at current cursor position
a insert text after current cursor position
:q! exit without saving
:ZZ exit with saving
> There was no man info for elvis. Seems like a candidate for deletion.
>
better not, many programs (like visudo) depend on a vi clone.
> Seems to be no man info for anything.
> Says it cannot open configuration file /usr/lib/man.conf
>
It might be possible Dragon stripped all documentation.
>
> Tried pico. I approve. I can at least exit. <G>
> Likewise mcedit. Much better.
I like mcedit as well because it's so much like MS-DOS edit.com,
allthough it lacks the power of vi.
> I spent quite some time with MC but was unable to find clues to some of
> it's own characteristics.
> What are the filename conventions?
255 chars max, and pretty much anything can be in it.
Special characters like a space or an brace should be escaped (preceded)
by a backslash (" \ ")
Case does matter. Extensions have no special meaning at all, other than
to help the user identify the file. If a filename starts with a dot it
is considered hidden and will not show up on regular directory listings.
ls -a will show them.
> What do the preceding "*" or "@" mean ?
> What is the significance of the displayed colors?
Different colors are used for different file types.
eg to denote links, devices or tarballs.
> Why isn't this info builtin?
>
Probably to keep DragonLinux small.
--
Casper Gielen mailto:[EMAIL PROTECTED]
--
We do not kill enough professors. Stalin
