From: Kris Van Hees <aedil@alchar.org>
To: xen-devel@lists.sourceforge.net
Subject: Re: openafs not supported?
Date: Wed, 9 Mar 2005 12:19:22 -0500 [thread overview]
Message-ID: <20050309171922.GI12141@alchar.org> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3540@liverpoolst.ad.cl.cam.ac.uk>
On Wed, Mar 09, 2005 at 04:58:26PM -0000, Ian Pratt wrote:
> > Great, that was missing piece! I'm running openafs-1.2.11
> > compiled with faked
> > linux-2.4.29-xen0 and until now everything works fine.
>
> Please can you write a good bug report for the openafs maintainers to
> get them to fix their Makefiles.
Make sure to send the bug report to openafs-bugs@openafs.org. Please also
explain the way that you are currently working around what you consider to
be a problem in the OpenAFS makefiles. That will assist everyone looking
at the bug reports to evaluate the appropriate action that is needed to make
this all work fine.
Kris
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-09 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 16:58 openafs not supported? Ian Pratt
2005-03-09 17:19 ` Kris Van Hees [this message]
2005-03-09 22:39 ` Miroslav Ruda
2005-03-09 23:06 ` Kris Van Hees
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 15:56 Ian Pratt
2005-03-09 16:54 ` Miroslav Ruda
2005-03-09 14:45 Ian Pratt
2005-03-09 15:49 ` Miroslav Ruda
2005-03-09 15:54 ` Kris Van Hees
2005-03-01 14:55 Miroslav Ruda
2005-03-02 14:35 ` Steven Hand
2005-03-02 15:52 ` Miroslav Ruda
2005-03-03 15:05 ` Miroslav Ruda
2005-03-09 13:20 ` Miroslav Ruda
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=20050309171922.GI12141@alchar.org \
--to=aedil@alchar.org \
--cc=xen-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.