9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: 9nut@9netics.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cryptographic signatures & factotum
Date: Thu, 11 Mar 2004 15:57:55 -0800	[thread overview]
Message-ID: <e7ecad64a375772c8358ff1719810200@9netics.com> (raw)
In-Reply-To: <559b5ec89e2cfd991a8152e0ceddc88c@snellwilcox.com>

> I want to be able to send an email from home to work
> which will cause my work machine to cpu(1) back to me.

I've not tried this, but I think it should work.

Why not run a cron job on the cpu at work (on your behalf and your
factotum), that dials home, and once it authenticated itself, runs
exportfs.  On the home system you'd run a service that authenticates
the incoming call and then posts the fd on /srv later you mount
/srv/incoming to /n/someplace.

The part i'm not sure of is the cron/factotum interaction.



  parent reply	other threads:[~2004-03-11 23:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11 23:03 steve-simon
2004-03-11 23:41 ` andrey mirtchovski
2004-03-11 23:57 ` 9nut [this message]
2004-03-12  0:03   ` George Michaelson
2004-03-12  0:09     ` boyd, rounin
2004-03-12  0:30       ` George Michaelson
2004-03-12  9:07         ` Bruce Ellis
2004-03-12 11:49           ` boyd, rounin
2004-03-12 12:14             ` boyd, rounin
2004-03-12  1:18     ` bs
2004-03-12  0:27 ` matt
2004-03-12  0:49 ` a
2004-03-12 19:52   ` rog
2004-03-12  1:02 ` Geoff Collyer
2004-03-12  9:23   ` Steve Simon
2004-03-12 13:03     ` David Presotto
2004-03-12 13:14       ` boyd, rounin
2004-03-12 13:35         ` David Presotto
2004-03-12 14:02           ` boyd, rounin
2004-03-12 16:23             ` John Kodis
2004-03-12 19:08               ` boyd, rounin
2004-03-14  3:39     ` Nick Jamieson
2004-03-14  3:53       ` boyd, rounin
2004-03-14  5:31         ` Nick Jamieson
2004-03-14  5:37           ` boyd, rounin

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=e7ecad64a375772c8358ff1719810200@9netics.com \
    --to=9nut@9netics.com \
    --cc=9fans@cse.psu.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).