From: Troy Benjegerdes <hozer@hozed.org>
To: Christoph Hellwig <hch@infradead.org>,
Arjan van de Ven <arjan@infradead.org>,
David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: PATCH: Change in-kernel afs client filesystem name to 'kafs'
Date: Sat, 24 Jun 2006 13:27:37 -0500 [thread overview]
Message-ID: <20060624182737.GQ5040@narn.hozed.org> (raw)
In-Reply-To: <20060624180953.GA4145@infradead.org>
On Sat, Jun 24, 2006 at 07:09:53PM +0100, Christoph Hellwig wrote:
> On Sat, Jun 24, 2006 at 01:01:41PM -0500, Troy Benjegerdes wrote:
> > Now, if you could suggest another way to have both the *experimental*
> > in-kernel AFS client and OpenAFS client with mounted filesystems, please
> > let me know.
>
> Don't do that. Or at least stay far away from the vger lists with any
> bugreports or suggestions that come up when running OpenAFS. It's some
> of the worst code around, and it has a license that doesn't event permit
> the blatantly stupid poking into kernel internals it does.
I'm going to do it, but I know who to flame when OpenAFS breaks, and
it's not the kernel list. Believe me I've done it enough already.
Besides the syscall table modification, which is just plain stupid, is
there any other poking around in kernel internals the openafs code does
that shouldn't be there?
next prev parent reply other threads:[~2006-06-24 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 0:41 Troy Benjegerdes
2006-06-24 12:16 ` Arjan van de Ven
2006-06-24 18:01 ` Troy Benjegerdes
2006-06-24 18:09 ` Christoph Hellwig
2006-06-24 18:27 ` Troy Benjegerdes [this message]
2006-06-24 21:23 ` Alan Cox
2006-06-26 6:24 ` Troy Benjegerdes
2006-06-24 13:37 ` Christoph Hellwig
2006-06-24 18:19 ` Troy Benjegerdes
2006-06-25 3:19 ` Josh Boyer
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=20060624182737.GQ5040@narn.hozed.org \
--to=hozer@hozed.org \
--cc=arjan@infradead.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®