similar to: contrib/solaris/buildpkg.sh - use within JumpStart as well?

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

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.

(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

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

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

Hi Ben, Just a few things on openssh 3.4p1 Solaris package. 1) Solaris naming convention would be OPENssh for package 2) Need to add the "sed" edit of X11Forwarding for ssh_config also 3) I prefer sym links as default (I suppose thats personal) 4) Need to provide "response" file so that dont need interaction to install!! - I do all install via jumpstart scripts etc.

Anyone have idea how to create ZFS pool and volumes during jumstart instalation ? (I''m using JumpStart Enterprise Toolkit) kloczek

Hi everybody, Today I tried the latest Solaris on Xen build. I downlaoded all files and created the iso. Then I wanted to run setup_install_server , but this failed: bash-3.00# ./setup_install_server /export/sol_xen/ -bash: ./setup_install_server: cannot execute binary file -bash-3.00# So I create a tar file to copy over all files to export/sol_xen/ Then I tried to start and install via

Hi all, I'm trying to use mboot.c32 to build our Solaris machines but the problem we are getting is the network interface doesn't get configured. It would boot in to the miniroot and then drops in to a shell. At the shell, if I configure the interface via dhcp it would continue on with the jumpstart. This is the first time we are using syslinux (version 4.04) and looking at the

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:

I have zfs on my base T5210 box installed with LDOMS (v.1.0.3). Every time I try to jumpstart my Guest machine, I get the following error. ERROR: One or more disks are found, but one of the following problems exists: - Hardware failure - The disk(s) available on this system cannot be used to install Solaris Software. They do not have a valid label. If you want to use the

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

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:

Warning: WINE Newbie Alert. Proceed with caution.... Background: I don't want to fork up $$$ for a separate Windows machine for my kid so I've decided to see if I can run any of the popular brain-rot software under WINE (Is it "WINE" or "Wine" or "wine"?) on a Linux 2.4.18 kernel. My first project is a vintage 1995 version of JumpStart Kindergarten. Seeing

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

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

I understand that currently, at least under Solaris 10u6, it is not possible to jumpstart a new system with a zfs root using a flash archive as a source. Can anyone comment as to whether this restriction will pass in the near term, or if this is a while out (6+ months) before this will be possible? Thanks, Jerry

This patch adds the seatbelts which _only_ kill parent sshd procs... -RMallory (eg: when you ssh into a machine and pkgadd the new openssh, it will not kill your current (or anyone else's sshd session) onanother_note: the buildpkg.sh could use some exec_prefix functionality... to deal with ./configure --prefix= --exec_prefix=/usr *** bak/opensshd.in Fri Oct 19 13:36:24 2001 ---