[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Remote login to a Mac
- To: info-mcl@digitool.com
- Subject: Remote login to a Mac
- From: Shannon V Spires <svspire@somnet.sandia.gov>
- Date: Thu, 8 Jun 1995 08:52:58 -0600 (MDT)
- Cc: svspire@somnet.sandia.gov (Shannon V Spires)
- In-reply-to: <199506080500.BAA19668@digitool.com> from "info-mcl-digest-request@digitool.com" at Jun 8, 95 01:00:24 am
- Sender: owner-info-mcl@digitool.com
> A few weeks ago I was at an interview and got into a discussion about
> Macintosh vs. UNIX. The interviewer said that there was no way to log into
> a mac from home and start a build. That way when you got to work the build
> would be done. I made the usual references to Timbuktu and ARA but those
> require another Mac. She has linux running on a PC. So I thought for a
> couple of minutes and suggested using MCL to build a telnet server to send
> commands to toolserver. She said I was the only person to give an answer
> besides, "You can't do that."
Sounds like you came up with a good solution. But here are some other
options:
1) Timbuktu does require a copy of itself in both locations, but it now
works cross-platform, at least. You can control a Mac with a Windows
machine, or vice versa, and it communicates with either Appletalk or IP.
2) Use MacHTTP in conjunction with MCL and control things with web forms.
MacHTTP (or WebSTAR) handles the IP stuff, MCL takes care of the
Appleevents.
3) Get MachTen (Unix for the Mac). Runs as just another Mac application,
unlike the old A/UX.
--
Shannon Spires
svspire@sandia.gov