similar to: OpenSSH Contrib/solaris buildpkg.sh

(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

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

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, 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

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)

Here is a small patch for OpenSSH 3.2.3p1.. When the package postinstall script runs, it presumes that the package will be installed relative to the current / directory.. If this package is installed as part of a Solaris Jumpstart installation, this will not be the case. Consequentially, the /etc/ssh/sshd_config.default will never get copied to /etc/ssh/sshd_config on the new operating system.

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

Hello, I have compiled and installed (almost) wine 0.9.24 within Mac OS X tiger 4.8 with X11 etc installed. The wine configure and compile steps complete without a warning/hitch etc. However, when I run wine <prog> I receive the following warning message -- Wine cannot find the FreeType font library. To enable Wine to use True Type fonts please install a version of FreeType greater

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

Hello everybody, I have written a shell script that makes the building of a Solaris package of rsync easier. Because I think it is useful for other Solaris user, I wold be very happy, if somebody would include it to the source tree. There is one little things to do: - include it in the auto-configuration process, so that the version number will be set correctly. So far, Jens ----- Script

I've been trying to figure this out for a while, but my knowledge of R is obviously still too limited. The context is as follows: I have some time series, and I would like to estimate their densities, and then use the actual densities in a monte carlo simulation. Now, I can easily estimate the density using density(); I can write a random number generator to fit an arbitrary density

I am attempting to successfully run the buildpkg.sh script which is located in the contrib/solaris directory. I am receiving the following error: Building pkginfo file... Building prototype file... Building package.. ## Building pkgmap from package prototype file. ## Processing pkginfo file. pkgmk: ERROR: parameter <VERSION> cannot be null ## Packaging was not successful. pkgtrans: ERROR:

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

http://bugzilla.mindrot.org/show_bug.cgi?id=1038 Summary: buildpkg.sh postinstall script does not install RC links using installroot and non-symlinks. Product: Portable OpenSSH Version: 4.0p1 Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component:

Hello, For an internal project we were looking for a solution which extends ActiveRecord by an iterator function. Using find(:all) is no fun if you have to process some 10.000 records. Until now there have been two ways of dealing with that scenario: - write your logic a second times (e.g. use stored procedure) - bet on AR plugins which work around that limitation by fetching IDs and

Hi, version.h in OpenSSH_3.1p1 has an Newline after #define SSH_VERSION "OpenSSH_3.1p1" so tail -1 ../../version.h | sed -e 's/.*_\([0-9]\)/\1/g' | sed 's/\"$//' does give back a version number regards Oliver -- Oliver F?nger - Phone +49 201 8501 319 Cityweb Network GmbH & Co. KG Friedrichstr. 12 - Fax +49 201 8501 104 45128 Essen - email

Hello all, I was finally able to create the OpenSSH package for Solaris 8 10/01. The problem I have now is that I will still need to have entropy ready prior to openssh-3.1p1 package installation. Otherwise there is no entropy pool available (with the new servers) and key generation fails. With the previous versions of openssh, I used SUN's "makeOpenSSHPackage.ksh" script and was

I have a minor issue with the 'buildpkg.sh' script in the contrib/solaris directory for OpenSSH (3.4p1 in my case) that I'm hoping might be solvable. First off, I'd like to say that I've been quite happy with the script; for interactive installs, it's worked great. My problem is occurring due to my attempts to make it work non-interac- tively, however, within an init

Hi all, Lustre 1.8.3 is available on the Sun Download Center Site. http://www.sun.com/software/products/lustre/get.jsp Our forwarding link has not yet been updated but should be shortly, so you can either find your way in through: http://www.sun.com/downloads/index.jsp?tab=2#L and look for Lustre 1.8.3 near the bottom of the "L" section. or

Hi all, Lustre 1.8.3 is available on the Sun Download Center Site. http://www.sun.com/software/products/lustre/get.jsp Our forwarding link has not yet been updated but should be shortly, so you can either find your way in through: http://www.sun.com/downloads/index.jsp?tab=2#L and look for Lustre 1.8.3 near the bottom of the "L" section. or