From: Eric Dorman <edorman@san.rr.com>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] (idefs)
Date: Fri, 24 Aug 2001 22:27:44 -0700 [thread overview]
Message-ID: <3B873750.C726A078@san.rr.com> (raw)
In article <3B7B316A.DED8096F@san.rr.com> you write:
>>what's stupid is that now that i sit here typing this i realize
>>that i had not factored all the variables. maybe my _build_
>>environment is bad. ugh.
>
>Hadn't Nemo put some effort into merging the IDE patches into the current
>file server code? I thought, for a time, that he was going to become the
>keeper of the idefs code.... I'm not questioning your doing it Eric, of
>course, but I'd hate to see a lot of duplication of effort.
>
> - Dan C.
sorry been so long getting back.
yes, you're correct. the link i posted shouldn't be construed
as 'mostest currentest'. oddly now that i look at it i'm not sure
how it ever worked (what? no Devide type in devream?? drek.) and i've
still been unable to build one that doesn't scramble the freelist.
i'm pushing forward but also waiting with bated breath when
http://plan9.escet.urjc.es/export/idefs.rc comes back up to see
where I've done wrong :)
-eld
reply other threads:[~2001-08-25 5:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B873750.C726A078@san.rr.com \
--to=edorman@san.rr.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).