X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Subject: Fw: 1.5.25-11 Bash? Problem installing unattended on Server 2008 To: cygwin AT cygwin DOT com X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006 Message-ID: From: Christoph Herdeg Date: Fri, 4 Apr 2008 15:00:26 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m34D16LN025199 Hello Mailing List, regarding my problem below in the meantime I was able to find an approach: The Nullsoft-Installer (made by one of my predecessors) was until now -anyway why- scripted to build a directory skeleton for "/home" and "/home/Administrator". When removing the corresponding lines from the ".nsi"-file one of the post-setup.exe errors vanished: the skeleton files are being copied now. But the Nullsoft-Installer also copies our shellscript to "/etc/profile.d" - okay, so far so good. But on analysis the script file strangely did not inherit the folder's ACLs as did the other files copied there by "setup.exe" (e.g. "00bash.sh"). So my result for the moment would be that my problem is not Cygwin- but Windows Server 2008- or Nullsoft-related. Never the less I was glad if someone here had a clue what the reason for our problem could be. Mit freundlichen Grüßen / with kind regards Christoph Herdeg p.s.: Last I woul like to let you know that I could not reply correctly (missing quotes etc.) to the mailing-list because my original mail can be seen at "http://cygwin.com/ml/cygwin/2008-04/msg00108.html" but has not yet been delivered to my mailbox. Hello Mailing List! at the moment we're trying to upgrade our Cygwin unattended installation package to render it usable on Windows Server 2008 / Windows Vista SP1. The main problems are fixed, as well are the cosmetic issues (changes in batch syntax, as always undocumented of course). We're using Cygwin to run certain 'x shellscripts on our Windows systems to gather certain information (needed for our systems management application) over SSH using passwordless logins. 1st an outline how we approach the unattended installation: We use a Nullsoft-Installer started by the local Administrator to extract all needed files on the target system. Then we use a modified version of the batch file Henrik Bengtsson adopted from Seth de l'Isle's instructions to call setup.exe providing the "-q" and "-R" switches. The setup.ini file is modified so setup.exe believes that all packages we need would belong to "category: base". The Nullsoft-Installer also copies a shellscript to /etc/profile.d and executes cygwin.bat as penultimate step so cygwin automagically runs it - last step ist to delete this among other files not needed after installation. On all Windows Versions from Windows 2000 this procedure works absolutely smooth. When it comes to Windows Server 2008, also everything works...until cygwin.bat is called: Cygwin starts but does not create the usual "skeleton files for the user to personalise their cygwin experience": Copying skeleton files. These files are for the user to personalise their cygwin experience. These will never be overwritten. `./.bashrc' -> `/home/cherdeg//.bashrc' `./.bash_profile' -> `/home/cherdeg//.bash_profile' `./.inputrc' -> `/home/cherdeg//.inputrc' Instead we are shown the message: bash: cannot create temp file for here document: Bad address bash: /home/Administrator/.bash_profile: Bad address If we now parallely start a second instance of Cygwin, e.g. by clicking its desktop icon, solely our shellscript is executed; no skeleton files are copied. When finished the script exits its instance of Cygwin and leaves us with the 1st one which we end as well so the Nullsoft installer can do its cleanups. We now have a fully working version of Cygwin doing everything we want...but: what about the skeleton / personalisation? The main problem for us is that the installer is no longer "unattended" which renders it unusable for our purpose. If we install cygwin attended by using setup.exe and the patched .ini file, everything works...but we need our script be run and an unattended installation. How could we fix this situation - are there any preinstall-requisites required on the target system, e.g. setting special ACLs? BTW: We only use the US versions of all windows releases so the symbolic links topic of international version won't bother. Mit freundlichen Grüßen / with kind regards Christoph Herdeg -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/