Mein Linux Tagebuch - Teil 1 von 3

Vielleicht habe ich was nicht kapiert, das in XWin anders ist als in ms-dos. Die machen ja ein Heidengewese um die richtige Auswahl von Monitor und Grafikkarte.
Und bei der Einrichtung der Screen (das scheint etwas wie das Zusammenf�gen des Servers, des Monitors, der Karte und der gew�nschten Aufl�sung zu sein) wird dann Bezug genommen auf die wirren Eingaben, die ich vorher gemacht hab. Na logisch fand der Server meinen Monitor nicht, ich habe ihn schlie�lich mal meinmoni, mal userid genannt.

Schlie�lich bin ich nur ein fauler User. Ich werde meinen Monitor NICHT herumdrehen und gucken, wer ihn hergestellt hat. Und ich werde erst recht die Grafikkarte nicht ausbauen und deren Hersteller ablesen. Wozu gibt es denn VGA? Damit alles mit allem funktioniert. Und Basta.

Originellerweise gibt es keine ManPage zu vi. Zwar hatte ich irgendwo in den Tonnen Faqs, die ich wieder und wieder gelesen habe, aufgeschnappt, da� vi etwas mit ez (sprich: easy) zu tun hat. Die Synopsis hat mir aber nicht weitergeholfen.

28.04.1998

# File generated by xf86config.
Section "Files"
    RgbPath     "/usr/X11R6/lib/X11/rgb"
    FontPath    "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath    "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath    "/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath    "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath    "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection

Section "ServerFlags"
EndSection

Section "Keyboard"
    Protocol    "Standard"
    AutoRepeat  500 5
    LeftAlt     Meta
    RightAlt    ModeShift
EndSection

Section "Pointer"
    Protocol    "Microsoft"
    Device      "/dev/mouse"
    ChordMiddle
EndSection

Section "Monitor"

    Identifier  "a"
    VendorName  "b"
    ModelName   "c"
    HorizSync   31.5, 35.5
    VertRefresh 50-70
Modeline "640x400"     25.175 640  664  760  800   400  409  411  450
EndSection

# Standard VGA Device:
Section "Device"
    Identifier  "Generic VGA"
    VendorName  "Unknown"
    BoardName   "Unknown"
    Chipset     "generic"
EndSection

Section "Device"
    Identifier  "d"
    VendorName  "e"
    BoardName   "f"
    #VideoRam    1024
    Clocks  25.19  28.32  25.17  28.44
EndSection

Section "Screen"
    Driver      "svga"
    Device      "Generic VGA"
    #Device      "d"
    Monitor     "a"
    Subsection "Display"
        Depth       8
        #Modes       "640x480" "800x600" "1024x768"
        ViewPort    0 0
        Virtual     320 200
        #Virtual     1152 900
    EndSubsection
EndSection

Section "Screen"
    Driver      "vga16"
    Device      "d"
    Monitor     "a"
    Subsection "Display"
        Modes       "640x480" "800x600"
        ViewPort    0 0
        Virtual     800 600
    EndSubsection
EndSection

Mittlerweile sehe ich die Abwesenheit eines WYSYWYG-Dokumentmalprogramms auch nicht mehr so eng. Es wird zwar noch eine Weile dauern, bis ich TeX benutzen kann, aber daf�r ist es M�CHTIG.

23.06.1998

Rolf war heute in der Werkstatt und sagte, den kernel zu rekompilieren sei tats�chlich so einfach wie es im Handbuch steht. Und prompt konnte ich nicht schlafen.
Vor einer Stunde habe ich mich also wieder vor diese Kiste gesetzt, bin ins Verzeichnis /usr/src/linux gegangen und habe mich durch das Skript make config getippt. (Ja geht denn das nicht mit Fenstern? Immerhin hat es sich gemerkt, was ich bein erstenmal eingetippt hatte.)
Ich habe ihm befohlen, keine nfs mehr zu mounten und daf�r Kenntnis von allen SoundBlaster- Karten zu nehmen.

Das Kompilieren dauerte etwa 7 min, ich habe derweil auf der anderen Konsole eine recht langsame Version von Sasteroids (ohne Ton) gespielt.

Mittlerweile hatte ich mir gedacht, da� das Betriebssystem nur einmal in den Rechnerspeicher geladen wird: beim Booten. Also habe ich /vmlinuz zu /vmlinuz.old umbenannt und zImage nach /vmlinuz kopiert.
Nat�rlich bootete loadlin die Schweinekiste nicht mit d:\linux\vmlinuz, sondern mit c:\loadlin\vmlinuz. Nochmal umbenannt, und siehe da: mein erster "selbstgebauter" Kernel fuhr richtig hoch. Er meckerte in der vertrauten Form �ber die Syntax des gpm.Befehls in irgendeiner /etc/init*, fand sein nfs nicht, seinen hostnamen nicht (wie denn auch), aber die CD und Xwindows liefen nach wie vor.
ich spielte dann sasteroids - immer noch ohne ton.

Immerhin sagte das Kernel beim Booten, da� er einen SoundBlaster gefunden hat. Also drehte ich an den parametern: gab in linux.par

sound=0x02220a1

Das probing von sbpcd (der supertolle treiber f�r soundblaster-Karten, die auch cd ansteuern k�nnen) soll lange dauern - mir egal, ich hatte zeit:

sbpcd=220,SoundBlaster

17.07.1998

#  echo > /etc/issue
#  echo Welcome to Linux `/bin/uname -a | /bin/cut -d\  -f3`. >> /etc/issue
#  echo >> /etc/issue
#  echo "`/bin/uname -a | /bin/cut -d\  -f1,3`. (POSIX)." > /etc/motd
#  These have been commented out by root to customize the system

 
Welcome User, to Linux 1.2.12. (POSIX).

To receive an introduction on how to work with Linux, type  

less readme

You can scroll the document with the <cursor key>s and the <Page> keys. 
If you feel bothered about my English, remember I'm a German writing Germish.  

Enjoy!

Welcome to Linux 1.2.12.

hilfe       Hilfe.
sasteroids  ein Spiel - leider ohne Ton. 
mc          Midnight-Commander
duconv      dos -> unix, duconv -d konvertiert zur�ck
joe         eine Art Wordstar, mit kleinem On-Screen-Display
less readme   introduction on how to work with Linux





Aber jetzt erstmal sch�n einloggen - Username <cr> - Passwort <cr> !

Welcome to readme.

You can quit this browser by typing 
:q <cr>      , where <cr> means the key with the word "Enter" on it.

The : will appear at the bottom of the screen, the q will terminate. 
Try this now, before you forget, and then call back this text again. 

You can browse this whole file by <CursorUp>, <CursorDn>, <PageUp>, and 
<PageDn>. 

                          *** Thank You ***

Linux is most time hacking in cryptic commands. To make User's life easier, 
you can recall your last commands by typing <CursorUp> (this is, the key
with an Arrow pointing upwards). 
Almost every command must be sent to the machine by typing <cr>.

Please leave this browser again, and then recall it by using <CursorUp>.

                          *** Thank You *** 

============================================================================

Let us see what you have learnt already:

 - logging in;
 - typing in a command (it was "less" and showed you the contents of a file);
 - submitting the command to the system by pressing <cr>;
 - browsing a file using <PageUp>, <PageDn>, <CursorUp> and <CursorDn>.

Now that you have learned how to get into the system and how to obtain some
useful info about the system, we will proceed to learn how to work with
the system. 
This documentation is held extremely short. It will only show you how to 
make something work and how to obtain further information. Please read it
thoroughly. 
There is plenty of information (that is, more than you can read in a lifetime)
on the system. But you are a user, that means you want to use the system, 
not to read long, nasty documentation. 

So let us see where you are in the system, and what you can do.

==============================================================================

This is a Linux system, which processes files. A file is like a block of data,
and it can be more or less readable to humans. 
The file sizes vary a lot: from 0 to millions of bytes. For now, you may
think of a byte as one single letter. Or a space between letters. 
As you can see, you can understand this file. Be sure the system cannot, 
this file is only of use for you, the user, and does not more to the system
than employ disk space. 
There are other files, that tell the system what to do next. These are called
"programs" or "shell scripts". They are installed here to fulfill your needs.

Every file has a name. As there are many files on the system, they are 
arranged like the leaves on branches on a tree. 
A tree has a root. In Linux, the root is called / (Slash). 
Out of the root, there grow some branches, which are called directories. 
The also have names, like bin, home, temp or something else.
Each branch may have files (you may think of leaves) and more branches on it.

As you work on files, each file must be in a special directory. In fact, 
at this moment you ARE in some special directory: You are in your home. 

Your directory is something like

/home/username     where username is just your username. 

You did not see this directory after you logged in. Instead, you saw 
something like 

darkstar:~$   (and a blinking cursor, of course.)

The ~ (Tilde) means that you are in your home directory. After you have
logged in, the system knew your username and put you right at the position
to start your work.  

If the file tree is the world (and for the system, it is), the your home
is one of the tree's branches. This is where you will live and work, and 
where you'll be while the system works for you. 
It is the only place where you are allowed to work, for there are other users
on the system, and they need protection for their works. Working means
creating, editing, and deleting files and achieve some readable output from
the system. 

In linux, the world needs a god. On linux systems, God is called "superuser"
or "sysop", which is short from "system operator". 
As any other god, DO NOT BOTHER HIM WITH NASTY QUESTIONS, 
because he has got a lot to do to keep the system going and make it run 
faster and smoother every day - so you, the user, can work on it more 
efficiently. 
As no other god, you need not to pray to him. That means, he'll like you 
most if he is not aware that you are there. 

Sometimes you may get stuck in your work. PLEASE check out the documentation
and ask other users before attempting to disturb the sysop in his work. 

============================================================================

Now you may want to explore the system, that is ask the system to tell you 
something about itself. 

ls      shows the files and directories in the current directory.

ls -l   shows the same, with somewhat more detail. 
        
"ls" is the command, that is the name of the program you want the system to 
perform. ls reads whitch files and directories are there, and displays them
on the screen. 
"-l" is an option. All options start with a "-".
You may think of a switch that is switched on the command. 
(In fact, a command is no electrical device but a binary device, but the
effect is the same.)
On Linux systems, most commands use to have bazillions of options. 

ls -a   shows all files and directories, including the hidden ones. 

The names of hidden files and directories start with a ".". For the moment, 
it is good to know they are there, but you should not change them until you 
know what you are doing. 

These two options, "a" and "l", can be combined by

ls -al               or       ls -la

You see, the order is not important (there are few commands where it is), 
and they are typed simply in a row. 

After performing this, you may look at the end of a long table that does not 
fit onto the screen. With S-<PageUp> (that is, holding the <Shift> key down 
and pressing <PageUp> once) you can scroll back to see what is at the 
beginning of the table. You even can scroll back more "pages", the sysop
has told the system how many. 

============================================================================

On the directory tree, you can hop one directory up with 

cd directory             where  cd is short for change_directory, and 
                         directory is the upper directory's name. 

You hop one directory down with

cd ..

You need not tell the system the name of the lower directory, for this can
be only one, and the system knows its name. 

Of course, you can change to the current directory:

cd .

but this will take you just where you are, so what's the use of it. 

This is called relative cd'ing, as you get there relatively to the directory
you are already in. 

You may type in the whole tree to get to some new directory:

cd /sbin

takes you first to the root of the directory tree, and then to directory sbin. 

As your home directory is abbreviated by ~, you may do 

cd ~ 

at any time to go back to your home directory, or 

cd ~/goodies

if a directory called "goodies" happens to exist in your home directory. 

You may want to explore the system now - do it, and then come back and read
on.