X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Received-SPF: pass (mail3.jubileegroup.co.uk: domain of ged AT jubileegroup DOT co DOT uk designates 127.0.0.1 as permitted sender) receiver=mail3.jubileegroup.co.uk; client-ip=127.0.0.1; helo=mail3.jubileegroup.co.uk; envelope-from=ged AT jubileegroup DOT co DOT uk; x-software=spfmilter 0.97 http://www.acme.com/software/spfmilter/ with libspf2-1.0.0; Date: Wed, 9 Jul 2008 09:01:53 +0100 (BST) From: "G.W. Haywood" To: cygwin AT cygwin DOT com Subject: Re: Updating cygwin from a remote shell? In-Reply-To: <1215563345.10132.ezmlm@cygwin.com> Message-ID: References: <1215563345 DOT 10132 DOT ezmlm AT cygwin DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (mail3.jubileegroup.co.uk [0.0.0.0]); Wed, 09 Jul 2008 09:01:54 +0100 (BST) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Hi there, On Tue, 8 Jul 2008 Andrew DeFaria wrote: > Thomas Walker wrote: > > > ... I did a decent amount of looking through mailing lists but > > couldn't find anything relevant. Been there too. :) > > ... want to be able to add new features ... and would like to be > > able to easily update cygwin and/or install new packages onto the > > Windows/Cygwin boxes from a remote shell. Ditto. > > I know I can setup VNC and all that fun stuff and run setup.exe but is > > there an easier way? The usual yum, apt, up2date, etc. don't seem to > > be options... > > There is no yum, apt, up2date, etc. You don't need VNC. RDP is already > on XP machines. Use rdesktop(1). I've been struggling with these same issues for some years. I manage a network for a business which is located a few hundred metres away from mine, and we use a radio link for the connection between us which means there are no connectivity problems. Even so, however, if I use rdesktop to connect to their Windows 2000 server and I'm not _very_ careful how I close down the rdesktop session then the server crashes. This is really inconvenient because the server does relatively mundane things like recording production information and the times when people clock on and off as they arrive for work and leave. Sometimes they take it personally... Of course I've suggested upgrading to a later OS but that's a very expensive exercise. So I use ssh for everything that I can do with ssh, and avoid logging in with rdesktop except in dire emergency. If there's something that I can't do with ssh then I schedule the work to be done on site when I can physically go there and not be in the way too much. That sucks, especially as they plan to move the server to another site two miles away in a few months. If there are any tips for a safer way of connecting to a Windows 2000 server to do routine upgrades of Cygwin and other remote admin that I can't do using ssh, I'd be very happy to hear them. -- 73, Ged. -- 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/