Section 4 : Troubleshooting

Q442: Problems after Un-taring a binary distributions?

? Got something to say about this answer? Hit the question mark to invoke the mailer and send your comments to the HylaFAQ maintainers.

Problems after Un-taring a binary distributions?

Date: Wed, 31 Jul 1996 08:13:31 +0200 (MST)
From: Matthias Apitz < >
Subject: Re: Starting up the server...

Sam Leffler wrote:
    It sounds like you might have un-tar'd the binary distribution as yourself
    and not root.  This would have caused many files to be owned by the wrong
    user and since of them are setuid this would have caused numerous problems
    when the programs were started.  In this case the best thing to do is to
    purge everything and start again.  Problems such as this are the reason for
    having "real distribution mechanisms" like the SGI inst software or (maybe)
    the SVR4 pkg tools.

Yes; the SVR4 pkg tools are able to create and install packages in
a very very robust form. The "package" consist of a tree of all
application files and some info files describing these files

- pkgmap(4), describing these files (where the files
  should be placed and who should own them ...)
- pkginfo(4), describing the package itself
- copyright(4)
- postinstall(4) and preremove(4) ...
  scripts which are executed during postinstall phase or
  preremove phase if one is installing the package or removing it.

The package is created by pkgmk(1), can be tar(1)'ed for transport
and can be installed with pkgadd(1M).  Below is
a short snipp of the pkgmap-file. As you can see it's
also easy to distribute FIFO's (they are just created by pkgmak(1M):
1 p none /usr/local/lib/HylaFAX-v4.0/spool/FIFO 0600 uucp uucp
1 d none /usr/local/lib/HylaFAX-v4.0/spool/archive 0700 uucp uucp
1 d none /usr/local/lib/HylaFAX-v4.0/spool/bin 0755 uucp uucp


 Back to FAQ Index FAQ Index  Next question in List Q443: Bad exit status 0400 for bin/faxrcvd? Last updated $Date: 2000/02/01 01:23:08 $.