From: serge@euler.Berkeley.EDU serge@euler.Berkeley.EDU
Subject: remote device access
Date: Fri, 28 Apr 1995 17:39:13 -0400 [thread overview]
Message-ID: <19950428213913.-TYYlKqVg6LJ23c1-eKokeWNQsAryMOaq2fJEmxGbm8@z> (raw)
>the machine architectures are often not the same, so in general a
>precompiled driver isn't much use off its own machine.
You mean the whole world isn't a VAX ... er, I mean a PeeCee? :-)
This wouldn't be any different from, e.g. a PC client/terminal getting
its (PC) binaries from a, say, SGI server (c.f. /386/bin/rc), etc.
Wouldn't it?
next reply other threads:[~1995-04-28 21:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-04-28 21:39 serge [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-04-29 6:54 David
1995-04-29 6:51 David
1995-04-29 6:09 serge
1995-04-28 16:04 rob
1995-04-28 8:26 forsyth
1995-04-28 6:52 Boyd
1995-04-28 0:18 serge
1995-04-27 8:29 forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19950428213913.-TYYlKqVg6LJ23c1-eKokeWNQsAryMOaq2fJEmxGbm8@z \
--to=serge@euler.berkeley.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).