From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] p9p factotum available for plan 9
Date: Tue, 9 Nov 2010 19:37:25 -0500 [thread overview]
Message-ID: <1e4bfd86eef85bbf4434f8ef22b6fed7@plug.quanstro.net> (raw)
In-Reply-To: <d8838076af10656ad31056e8704f034b@chula.quanstro.net>
On Tue Nov 9 13:01:17 EST 2010, quanstro@quanstro.net wrote:
> > This is tangential to the topic, but has anyone written up a "how I use p9p"
> > configuration style document? I've not really tried to use factotum from
> > p9p, because I was not even sure if it worked.
>
> "recently", that is within the past 2 years, p9p factotum has stopped
> working with drawterm. it might be that porting back some of the
> fixes to p9p factotum in nfactotum would fix that.
no dice. still hangs on startup:
where
#0 0x00007fb507c8440d in read () from /lib/libpthread.so.0
#1 0x0000000000410c77 in lfdread (c=0x6e0b60, buf=0x6e4e60, n=8192, off=0) at devlfd.c:86
#2 0x000000000040be90 in devbread (c=0x6e0b60, n=8192, offset=0) at dev.c:414
#3 0x00000000004128c6 in doread (m=0x6e0850, len=7) at devmnt.c:852
#4 0x000000000041296a in mntrpcread (m=0x6e0850, r=0x6e0dc0) at devmnt.c:874
#5 0x000000000041282c in mountio (m=0x6e0850, r=0x6e0dc0) at devmnt.c:837
#6 0x00000000004124ce in mountrpc (m=0x6e0850, r=0x6e0dc0) at devmnt.c:764
#7 0x0000000000411702 in mntattach (muxattach=0x7fff8a3da990 "`\vn") at devmnt.c:349
#8 0x0000000000415b23 in bindmount (ismount=1, fd=3, afd=-1, arg0=0x0, arg1=0x45be6e "/mnt/factotum", flag=0,
spec=0x45bdf0 "") at sysfile.c:682
#9 0x0000000000415cba in _sysmount (fd=3, afd=-1, new=0x45be6e "/mnt/factotum", flag=0, spec=0x45bdf0 "") at sysfile.c:727
#10 0x0000000000416380 in sysmount (fd=3, afd=-1, new=0x45be6e "/mnt/factotum", flag=0, spec=0x45bdf0 "") at sysfile.c:988
#11 0x00000000004037a1 in mountfactotum () at cpu.c:87
#12 0x0000000000403ef9 in cpumain (argc=0, argv=0x7fff8a3dae70) at cpu.c:165
#13 0x0000000000403313 in main (argc=3, argv=0x7fff8a3dae58) at main.c:68
- erik
next prev parent reply other threads:[~2010-11-10 0:37 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 21:13 erik quanstrom
2010-11-09 3:37 ` erik quanstrom
2010-11-09 17:41 ` David Leimbach
2010-11-09 17:51 ` erik quanstrom
2010-11-10 0:37 ` erik quanstrom [this message]
2010-11-10 1:49 ` Russ Cox
2010-11-10 6:46 ` erik quanstrom
2010-11-10 14:31 ` Russ Cox
2010-11-12 3:35 ` Noah Evans
2010-11-12 5:34 ` erik quanstrom
2010-11-12 5:46 ` Noah Evans
2010-11-12 6:03 ` Noah Evans
2010-11-12 6:19 ` Russ Cox
2010-11-12 6:25 ` Noah Evans
2010-11-12 9:07 ` EBo
2010-11-12 15:12 ` David Leimbach
2010-11-12 15:19 ` Eric Van Hensbergen
2010-11-12 15:35 ` erik quanstrom
2010-11-12 15:55 ` Russ Cox
2010-11-12 16:22 ` Eric Van Hensbergen
2010-11-12 19:55 ` ron minnich
2010-11-12 20:23 ` erik quanstrom
2010-11-12 20:31 ` Eric Van Hensbergen
2010-11-12 20:37 ` ron minnich
2010-11-12 20:30 ` Eric Van Hensbergen
2010-11-12 20:41 ` ron minnich
2010-11-12 22:15 ` Eric Van Hensbergen
2010-11-12 22:20 ` ron minnich
2010-11-12 22:36 ` Russ Cox
2010-11-13 8:31 ` tlaronde
2010-11-13 23:42 ` Dave Eckhardt
2010-11-14 22:49 ` Nathaniel W Filardo
2010-11-15 16:22 ` erik quanstrom
2010-11-15 17:40 ` Nathaniel W Filardo
2010-11-15 17:50 ` John Floren
2010-11-12 21:12 ` Russ Cox
2010-11-09 18:08 ` yy
2010-11-09 19:17 ` Bakul Shah
2010-11-09 19:27 ` Russ Cox
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=1e4bfd86eef85bbf4434f8ef22b6fed7@plug.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).