> Slackware packages are actually called <whatever>.tgz,
> and they are tarballs; you can untar them and do whatever
> you want.

The files will untar to the correct directories if you cd
to the / directory or use the -C/ parameter.

> I think they can contain special scripts to do post-expansion
> installation stuff

When the package untars, it creates an install directory.  In
that directory you will find doinst.sh.  Execute this script
to complete the installation.

> They probably depend on Slackware's directory structure,

Indeed.  There are some differences in directory structure
between distributions.  It may be safer to untar the package
in the /tmp directory and move the files by hand to make sure
they end up where your distribution expects.

BTW, the pkg script (from BasicLinux) untars to /, executes
doinst.sh and cleans up the remains.  Since it is just a
bash script, it could be used with other distributions.

> system startup scripts to be in Slackware's traditional Unix
> layout as opposed to a lot of Linux distros that use a more
> Linux-specific design.

I think most experienced DOS-users will probably be more
comfortable with Slackware's startup scripts.  rc.S and
rc.M run linearly (just like config.sys and autoexec.bat).
and a DOS user should be right at home (once he figures how
the conditional branching works).

Cheers,
Steven

To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with 
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
More info can be found at;
http://www.softcon.com/archives/SURVPC.html

Reply via email to