[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]
Christopher Fowler cfowler@outpostsentinel.com
Fri, 31 Mar 2006 08:47:54 -0800 (PST)
One idea is having them ssh or telnet to the console server, logging ing and then executing console directly. With a front end on the console server you can make this easy on them On Fri, 2006-03-31 at 09:13 -0700, Chris Riddoch wrote: > Bryan Stansell wrote: > > On Fri, Mar 31, 2006 at 10:49:02AM -0500, Christopher Fowler wrote: > >> available to our customers. You do not need the Cygwin environment. > >> You only need the dll. So I created a zip file that contained > >> console.exe and cygwin?.dll. It worked fine on the cmd.com prompt. > > > > and this should work with 8.x.x as well. you might need to compile > > things with '--with-port=XXX' so that an /etc/services lookup isn't > > needed, but aside from that, i don't see why dropping console.exe and > > cygwin1.dll in a directory and running it won't work. haven't tried, > > however (i have a small development cygwin environment on my laptop). > > I'll give that a try when I get a chance. I hadn't thought to build a > static binary (another suggestion I got). > > > sure would be entertaining to at least have a native console binary for > > windows...that would help ease everyone's pain. who knows how tricky > > that'll be, though (i'm no windows programmer, that's for sure). > > Yeah, neither am I. I'm trying to stay sane with SuSE on VMWare. (sigh) >