On Wed, 28 Aug 2002, Pic Dude wrote:

>Okay, just tried that and it failed too.  I CD'ed into the
>directory with the disk sets, ran pkgtool and hit the first
>option (install from current directory).  All I got was a
>command prompt again.  Did this about 50 times to read the
>message that flashed across:
>    //var/log/packages: no such file or directory
>
>Apparently this is linked to an adm directory somewhere that
>does not exist.  Odd.
>
>I see the .tgz packages under the a, ap, d, etc directories.
>I've never had to uncompress the tgz's.  That should be one
>of the functions of pkgtool.

I did not say to uncompress them. Sometimes the DISKS are compressed.
That's how you dl them. Do you see several .tgz files inside each
directory ?

>I'm going to wget the full installation, re-create the boot
>and root disks and try again.

Wait a sec. I gather that you do not have anything in the system yet. This
means that the base structure of the installation is not in place.
/var/log/packages contains a list of installed packages (one file per
package). It does not exist if you did not boot off of the right disk and
started install from there.

There are options to run pkgtool w/o this of course. I do not have it
here so I can't say.

Normally setup (slackware setup) expects to run off a boot+rootdsk floppy.
Is this how you boot ? By the time you run setup or pkgtool it is
necessary for this framework to exist. If you fudged it by hand you need
to generate it yourself. An easy way is to install aaa_base.tgz by hand.
Here are the steps:

1. cd /mounted/root_partition
2. rm -f install/doinst.sh # do not skip this step
3. tar -xzvf /somewhere/a??/aaa_base.tgz
4. if [ -x install/doinst.sh ]; then . install/doinst.sh; done

After this you should be able to run pkgtool and setup. pkgtool is
peculiar about the paths you give it (what isn't ?), trailing slashes and
other such things. Type carefully or your ass will be laminated ;-)

pkgtool does this when installing packages. pkgtool is a shell script, you
can read it or run it in debug mode to find out what it tries to do and
fix it. So is setup. Both should be run while in the directory
/mounted/root_partition, although there are ways to do it elsewhere.

Peter

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu