Date: Thu, 29 May 1997 15:06:38 +0100 From: Brian Somers <brian@utell.co.uk> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Brian Somers <brian@awfulhak.org>, freebsd-hackers@freebsd.org Subject: Re: rstartd on freefall Message-ID: <199705291406.PAA03949@utell.co.uk> In-Reply-To: Your message of "Wed, 28 May 1997 21:39:59 PDT." <25691.864880799@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > So rstart is broken by design. Let me guess. This has been argued > > before, and the xfree86 guys won't allow an absolute path to rstartd > > (via say a flag to rstart).... :| > > I don't recall that it was ever discussed. I've certainly never heard > of anyone actually using it, at least not until just now. :-) Heh. This is a good example of me wandering around and trying to figure out how something works. I come up with a solution and *assume* it's the one everyone else uses 'cos it works. How do other people exec remote X programs ? Doing a "rsh ....." doesn't send your DISPLAY over, so you end up with some nasty lines like: rsh freefall xterm -display $HOSTDISPLAY -T freefall -n freefall -e bash --login rather than rstart -g freefall xterm (although I suppose you could hide the -T & -n in .Xdefaults). The rstart idea is nice 'cos you can just dump your .rstart.* directories on a machine and kill all the long lines :) > Jordan -- Brian <brian@awfulhak.org> <brian@freebsd.org> <http://www.awfulhak.org> Don't _EVER_ lose your sense of humour !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705291406.PAA03949>