🚀 go-pugleaf

mbk@octarine.adfa.oz.au (Martin Kuchlmayer) writes:

>   I have installed slackware but have run into some trouble. I was
> installing some packages when I ran out of disk space. So I decided to
> remove some packages and re-install them on another partition. I would
> also need to remove the package set that the install died on.

If you run out of disk space as the superuser (root), you are *really*
out of space and the install software will probably not have had a
chance to save the true state of the package it choked on.

>   I used pkgtool to remove emacs, which it seemed to do - the next
> time I ran pkgtool, emacs was not available - and emacs is listed in
> file /var/adm/removed_packages. However there are still some files in
> the emacs dir tree. Some of these are listed in files in dir
> /var/adm/packages (which I assume is where pkgtool and the install
> prog keep their info). ...

Correct.
>                    ... However there numerous files in dir
> /usr/share/emacs/19.34/etc/lisp that are not listed in any file in the
> packages dir. Nor are they listed in the removed_packages file. All
> these files have extension ".elc".
>   So did something go wrong here?

No. It is possible to have more than one version of emacs installed
which all share the ``.elc'' files.  (elc = Emacs Lisp Compiled)
Third party Lisp packages may also end up in those directory
branches.  The installer just plays it safe.

>   Should I just delete these files?

Your's is a new installation.  If you had two or more versions of
emacs you would know it.  If you had any investment in third party
Emacs Lisp packages you would know that too.

Before you re-install Emacs:
    cd /usr/share
    rm -rf emacs

>   Will I have trouble removing packages that the install died on (I
> don't think it was emacs)?

Possibly.  The difficulty is in recognizing which package the
individual files belong to.  However, if a few stale configuration
files hang around that won't hurt much.  If you re-install the same
files, the old ones should simply be over-written.  If the
installation succeeds, a consequent un-install should clean everything
up.

>   I am using slackware 3.3.0 with kernal 2.0.30.
> 
>   I think I had trouble seeing any way of telling the slackware
> install prog (I think its name is setup) to install a package to a
> different dir. How do I do this? ...

As a new user, you probably should accept the defaults.  Once you know
what you are doing you can change things.

You can utilize symlinks to re-locate files or whole directory
branches, see below.
>                              ... Or is it best to just put /usr on a
> different partition?
>   Any advice on how to divide the linux directory tree across 2
> partitions would also be appreciated.

I don't know your partition sizes and what you indend to install.

The ``/usr'' branch often is by far the biggest directory branch.  
If you want to install X11 (which is *big*), that will go there too.

So maybe you want to create a directory ``X11R6'' on another
partition.  Lets assume your other partition is ``/dev/hda2'' and you
are mounting it under ``/hda2''.  Refer to your ``/etc/fstab'', also
do a ``man fstab''.
    cd /hda2
    mkdir X11R6

Then you create a symbolic link to it:
    cd /usr
    ln -s /hda2/X11R6 X11R6

Check it with
    ls -l X*

As long as the partition is mounted, it will now appear as an integral
part of your root file system.  Install X11 as normal.

>   2 more beginner questions - these are do really fall under this
> subject but are not important enough to warrant a seperate posting:
> 
>   I have found that not all the information displayed at boot time is
> in /var/adm/syslog (or messages). Does it appear somewhere else?

On my system the log files are actually in ``/var/log'', but you can
also "see" them under ``/var/adm'' and ``/usr/adm'' courtesy of 
sym-links.  Links can be recognized by the ``@'' which is appended to
the filename when you use ``ls''.  This does not take up extra disk
space except for the symlinks' directory enties.

>   I am getting a message at boot time:
> modeprobe: Can't locate module char-major-10-135
> Should I worry about this?

That is ``/dev/rtc'' (Real Time Clock).  You would know if you really
needed it for something, just ignore that for now.  Your system time
and date do not rely on it.  Eventually you probably will compile your
own, customized kernel.  You can take care of it then. 

Cheers, viele Gr��e,
-- 
Manfred Bartz <mbartz@werple.net.au>
  --- LINUX, live free or die ---