from the quill of Roger <[EMAIL PROTECTED]> on scroll
<00022621140100.02988@cx640487-b>
> no-offense, but i've known this.
You just seemed so "amazed" by it all.
> thing is, i can't find "any" direct how-to's.
"Direct" how-to's on what though?
> this i should be pressumabley listed within a "local lans" section.
Huh?
> btw: i've picked up the o'reilly book on x. scanned thru it.
Maybe you need to read it rather than scan thru it.
> not
> too much on veiwing remote computer by "x".
What do you mean by "viewing remote computer"? X is a display protocol,
nothing more.
> maybe i didn't get/find the right
> one.
I don't think I am grasping what you want to do. Doing such is probably
outside the scope of this list however so perhaps we should just drop
it.
> i've been ruthlessly searching for some type of how-to on this
> x/remote stuff.
What how-to? There is nothing to write a how-to about. You tell X
where you want to display the gui for the app, set up the permission to
do it and that is it. I gave you the how-to for the most part in the
last message here.
> your the first that has said anything.
I guess it all seems pretty mindless to those of us who have been
working with X for as many years rather than getting lulled into the
"single display" world of MS-Windows.
> Guess once people get their stuff up and running, they forget to
> document their
> techniques.
But this is the point, there is nothing to document. The document would
not be much larger than what I gave you. What more do you need to know?
> Thanx for your info on setting it up.
You are welcome. Very.
> i already new about the "built into the
> roots" deal,
You just seemed so amazed by it all is all.
> but after searching 2 mos. for the routing,
Routing? What routing?
> was rediculous in my
> opinion.. the farthest i've gotten with this thang, is the remote
> command line
> logins/rlogins. <bummer>
You sound like you need to do some reading rather than scanning. Try
reading some books. Start with the simple stuff, work up to the more
complicated stuff. Draw yourself a "learning line" and keep to the
scheduled line. It's so easy to get sidetracked. And the most
important thing is to play and use logic and be resourceful to figure
out what you need to figure out.
Good luck
b.
--
Brian J. Murrell InterLinx Support Services, Inc.
North Vancouver, B.C. 604 983 UNIX
Platform and Brand Independent UNIX Support - R3.2 - R4 - BSD
