similar to: patch for openssh/contrib/solaris/buildpkg.sh

I've made some changes to buildpkg.sh to make it easier for package builders to add their local changes. I'd like people that use buildpkg.sh to test and comment on these changes before I commit them to CVS. None of the defaults have changed. Some of the patch is is just moving chunks of code to a different location to make some of the enhancements work. Some things you may find

Hi. Solaris packages created by buildpkg.sh don't create privsep user or group and sshd won't start until they are created (or privsep is disabled): ## Executing postinstall script. starting /usr/local/sbin/sshd... Privilege separation user sshd does not exist /etc/init.d/opensshd: Error 255 starting /usr/local/sbin/sshd... bailing. The attached patch (against -cvs) ports the relevant

I've attached a patch for contrib/solaris package builder to bring it up to date with OpenSSH 2.9p1. The changes are: build-pkg - add libexec/ directory creation (to house sftp-server) cp sftp-server to libexec/ cp sftp.1 to man/man1 cp sftp to bin/ postinstall.in - add RSA key generation and installation/update prototype - add sftp, sftp.1 and sftp-server Btw, 2.9p1 is

I've just commited the patch below to buildpkg.sh.in to HEAD Just in case anyone is using "make package" to build a SVR4 style package, I thought I'd give a heads the default name for $POST_MAKE_INSTALL_FIXES has changed. --- buildpkg.sh.in.old 2005-12-28 14:24:55.856729016 -0800 +++ buildpkg.sh.in 2006-02-12 10:04:06.383475017 -0800 @@ -35,7 +35,7 @@ SYSVINITSTART=S98

Can someone else from the Solaris realm that uses our package system verify that this should be done? It looks right, but I want another opinion before commiting. - Ben > On Wed, 27 Feb 2002, Antonio Navarro wrote: > >> Hi Ben, >> >> I have made some modifications to the buildpkg.sh script that is >> distributed with openssh. >> >> I am sending it to

SecureComputing's PAM library doesn't pass back the correct context to the pam_conversation function, i.e. it passes back NULL. So this patch works around this fact. likely you'll only want this hack if you expect to use pam_safeword.so in your authentication check, and only if you run sshd in privilege separation (separate process) mode so that the PAM conversation is single

Ben, I am trying to create a package for Openssh.3-1p1, but the /contrib/solaris/buildpkg.sh script failes with the following errors: ./mkinstalldirs /tools/OpenSSH/openssh-3.1p1/contrib/solaris/package/usr/local/b in mkdir /tools/OpenSSH/openssh-3.1p1/contrib/solaris/package/usr/local/bin ./mkinstalldirs /tools/OpenSSH/openssh-3.1p1/contrib/solaris/package/usr/local/s bin mkdir

Hi, The line grabbing the version out of version.h is slightly broken in 3.1p1: VERSION=`tail -1 ../../version.h | sed [.....] because there's an extra blank line at the end of version.h. It would be more robust if the script did something like this instead: VERSION=`grep SSH_VERSION ../../version.h | sed [....] Cheers, Chris

Hi, thanks for this great work. Just a minor point - maybe you should mention the rm -rf $FAKE_ROOT command within your README file: It caught me unexpected and I was looking a couple of minutes for the package artifact before I actually read the last line. Regards, Burkhard Kohl Lead Engineer Content Management burkhard.kohl at intershop.de INTERSHOP? http://www.intershop.de INTERSHOP

Hello, I don't know how off the wall this question will be, but first let me say that I've found your buildpkg.sh script very useful in creating an OpenSSH package for use on my Solaris systems. Currently I'm trying to set up a fully automated JumpStart system at my workplace, and I'm realizing that the 'postinstall' script (and possibly some of the other install scripts)

(Shame on me: wrong filename in last posting, now here are correct diffs) in contrib/solaris/ (openssh-SNAP-20011017.tar.gz) 1) buildpkg.sh makes wrong link for /etc/init.d/opensshd 2) /etc/init.d/opensshd has not-working killproc here my version tested on Solaris 2.4 and 8 (no pgrep with solaris 2.4, XARGS was undefined, simpler syntax) J?rg --- contrib/solaris/buildpkg.sh Fri Oct 12

Greetings all, See below for postinstall and remove scripts for the above release for those who may have wondered why they didn't work. Minor changes, but those below work. Find these scripts in ../samba-1.9.18p10/packaging/Solaris/pkg-specs. Regards Anthnoy :::::::::::::: postinstall :::::::::::::: #!/bin/sh # install samba nawk '/^netbios-[ns]*[ ]/ {next} {print} END { print

Hello Ben Lindstrom, I tried your package creation scripts for Solaris which are contributed with the new OpenSSH Version 3.0.0p1. Nice that you develop these scripts but I run into a major problem installing the package which was created by the script. On our Solaris hosts /usr/local is only a symbolic link to /opt/local. After installing the OpenSSH package the symbolic link was removed and a

Not that I''m much of a Solaris guy, and definitely not a Solaris 10 guy, but since nobody else had posted anything yet: http://reductivelabs.com/trac/puppet/wiki/PuppetSolaris#Solaris10 The good news is that it appears to be a completely hands-off puppetd installation. Just sign the client key afterwards on the puppetmaster and you''re set. The bad news is that it''s

On 26/10/2015 10:56, Andrey Smetanin wrote: > Hyper-V SynIC is a Hyper-V synthetic interrupt controller. > > The test runs on every vCPU and performs the following steps: > * read from all Hyper-V SynIC MSR's > * setup Hyper-V SynIC evt/msg pages > * setup SINT's routing > * inject SINT's into destination vCPU by 'hyperv-synic-test-device' > * wait for

This testscript creates reflinks to files on different subvolumes, overwrites the original files and reflinks, and moves reflinked files between subvolumes. Originally submitted as testcase 302, changes are made based on comments from Eric: http://oss.sgi.com/archives/xfs/2013-03/msg00231.html Two new common/rc functions used in this script (_require_cp_reflink and _verify_reflink) have been

Hyper-V SynIC is a Hyper-V synthetic interrupt controller. The test runs on every vCPU and performs the following steps: * read from all Hyper-V SynIC MSR's * setup Hyper-V SynIC evt/msg pages * setup SINT's routing * inject SINT's into destination vCPU by 'hyperv-synic-test-device' * wait for SINT's isr's completion * clear Hyper-V SynIC evt/msg pages and destroy

Hyper-V SynIC is a Hyper-V synthetic interrupt controller. The test runs on every vCPU and performs the following steps: * read from all Hyper-V SynIC MSR's * setup Hyper-V SynIC evt/msg pages * setup SINT's routing * inject SINT's into destination vCPU by 'hyperv-synic-test-device' * wait for SINT's isr's completion * clear Hyper-V SynIC evt/msg pages and destroy

This testscript creates reflinks to files on different subvolumes, overwrites the original files and reflinks, and moves reflinked files between subvolumes. Originally submitted as testcase 302, changes are made based on comments from Eric: http://oss.sgi.com/archives/xfs/2013-03/msg00231.html Two new common/rc functions used in this script (_require_cp_reflink and _verify_reflink) have been

Hi all, Following an upgrade from samba 2.2.8a to 3.0.22 we have been unable to delete files on a samba share using an XP client. We were previously able to delete these files when using 2.2.8a. The problem occurs when we have a particular sub-set of permissions. Directory permissions on UNIX are set to 775 and ownerhips to usera : group1. This should mean that either usera or anyone who