From: William Gunnells <gunnells@gmail.com>
To: ori@eigenstate.org
Cc: 9front@9front.org
Subject: Re: [9front] upas and gmail
Date: Mon, 20 Jul 2020 21:16:49 -0700 [thread overview]
Message-ID: <01690500-2163-43F9-8784-590F0BCFC4C9@gmail.com> (raw)
In-Reply-To: <F0EBCA391F94ECDEDE7110DCBB76703C@eigenstate.org>
so I added auth/factotum to profile and upas/fs -n
not sure I understand that script
looks like a 6 line script and the only thing I changed was the /imaps/gmail.com/gunnells box etc…
it pretty much gave me /mail/fs/ctl/ access permission denied
I feel like i’m running upas/fs wrong like mine should be that long command
> On Jul 20, 2020, at 9:00 PM, ori@eigenstate.org wrote:
>
>> wow the drawterm is a problem. I kind of thought it was the way to go. So in drawterm i’m
>> supposed to run webfs and auth/factotum
>>
>> It did ask me for a password and I guess add it to factotum
>>
>> its currently running
>>
>> I tried Mail in acme and i see the following:
>>
>> Mail: can’t open /mail/fs/ctl: ‘/mail/fs/ctl’ does not exist
>> Mail 996: can’t open %s %r
>>
>
> So, in my profile, I have something like:
>
> case cpu
> ...other stuff...
> # call from drawterm
> if(! test -e /mnt/term/dev/wsys){
> # Start the services I'd expect on a terminal
> auth/factotum
> webcookies
> webfs
> plumber
>
> # Start upas in the background so all
> # indows have access to /mail/fs; use
> # the -n option to prevent long stalls
> # when starting the window system.
> upas/fs -n
> rio -i riostart
> }
>
> Then, after login, I have a script that I run to
> mount my mailboxes:
>
> /usr/ori/bin/rc/mbox:
>
> #!/bin/rc
> if(~ $#1 0)
> echo open /imaps/eigenstate.org/ori mbox > /mail/fs/ctl
> if not
> for(m in $*)
> echo open /imaps/eigenstate.org/ori/$m $m > /mail/fs/ctl
>
> (note, $home/bin/rc is unioned with /bin)
>
>
>>> On Jul 20, 2020, at 8:16 PM, ori@eigenstate.org wrote:
>>>
>>>> upas/fs −f /imaps/imap.gmail.com/gunnells@gmail.com
>>>> cat /mnt/factotum/ctl
>>>> key proto=pass server=smtp.gmail.com service=smtp user=gunnells@gmail.com !password?
>>>> key proto=pass server=imap.gmail.com service=imap user=gunnells@gmail.com !password?
>>>>
>>>> cpu% upas/fs -f /imaps/imap.gmail.com/gunnells@gmail.com
>>>> upas/fs: imap: error is cannot find IMAP password
>>>> upas/fs: opening /imaps/imap.gmail.com/gunnells@gmail.com: cannot find IMAP password
>>>
>>> Are you using drawterm?
>>>
>>> Try running auth/factotum before this -- From what I recall, drawterm
>>> has a builtin factotum that you probably don't want to use.
>>>
>
next prev parent reply other threads:[~2020-07-21 4:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 6:56 William Gunnells
2020-07-20 8:11 ` [9front] " Joel Fridolin Meyer
2020-07-20 23:31 ` William Gunnells
2020-07-21 2:01 ` ori
2020-07-21 2:29 ` William Gunnells
2020-07-21 2:34 ` ori
2020-07-21 2:45 ` William Gunnells
2020-07-21 2:49 ` ori
2020-07-21 3:06 ` William Gunnells
2020-07-21 3:16 ` ori
2020-07-21 3:33 ` William Gunnells
2020-07-21 3:52 ` ori
2020-07-21 4:00 ` ori
2020-07-21 4:16 ` William Gunnells [this message]
2020-07-21 4:24 ` ori
2020-07-22 5:29 ` William Gunnells
2020-07-22 5:51 ` William Gunnells
[not found] <EE9D01AB4107861C7797511D56ECD0FB@eigenstate.org>
2020-07-21 2:19 ` William Gunnells
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=01690500-2163-43F9-8784-590F0BCFC4C9@gmail.com \
--to=gunnells@gmail.com \
--cc=9front@9front.org \
--cc=ori@eigenstate.org \
/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).