Hi Folks,
OK, simple problem (except for a Solaris newbie like me!). I am installing OpenSSH on a pair of servers. The first server went fine. Now I'm trying to do it on the second one: it won't add the packages.
FTP'd the packages from freeware.sun.com (it has a number of different packages which are required, but the behavior's the same on all of them so here's a representative sample):
get openssh-4.3p2-sol8-sparc-local.gz
Unzipped it:
# gunzip openssh-4.3p2-sol8-sparc-local.gz
I only got one file and I thought I would get a directory tree, but maybe I just saw that stuff going by during the pkgadd process on the prior server, so I'm unconcerned. Then when I do the pkgadd command it complains strangely:
# pkgadd -d openssh-4.3p2-sol8-sparc-local
pkgadd: ERROR: no packages were found in </var/tmp/dstreAAAXBaObN>
Is this a way of saying the the file is corrupted somehow so that the tmp file it tried to use in the process didn't work right or what? I tried redoing the download in a different way and the byte counts are identical to the original. gzip doesn't complain about the zip file being bad or anything. What should I try next?
Any suggestions welcomed most heartily!
John
John Craig
Alpha-G Consulting, LLC
OK, simple problem (except for a Solaris newbie like me!). I am installing OpenSSH on a pair of servers. The first server went fine. Now I'm trying to do it on the second one: it won't add the packages.
FTP'd the packages from freeware.sun.com (it has a number of different packages which are required, but the behavior's the same on all of them so here's a representative sample):
get openssh-4.3p2-sol8-sparc-local.gz
Unzipped it:
# gunzip openssh-4.3p2-sol8-sparc-local.gz
I only got one file and I thought I would get a directory tree, but maybe I just saw that stuff going by during the pkgadd process on the prior server, so I'm unconcerned. Then when I do the pkgadd command it complains strangely:
# pkgadd -d openssh-4.3p2-sol8-sparc-local
pkgadd: ERROR: no packages were found in </var/tmp/dstreAAAXBaObN>
Is this a way of saying the the file is corrupted somehow so that the tmp file it tried to use in the process didn't work right or what? I tried redoing the download in a different way and the byte counts are identical to the original. gzip doesn't complain about the zip file being bad or anything. What should I try next?
Any suggestions welcomed most heartily!
John
John Craig
Alpha-G Consulting, LLC