From: Christoph Hellwig <hch@infradead.org>
To: "C.Y.M" <syphir@syphir.sytes.net>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Unknown symbol kill_proc_info in 2.6.10-rc1
Date: Sat, 23 Oct 2004 12:28:38 +0100 [thread overview]
Message-ID: <20041023112838.GA30910@infradead.org> (raw)
In-Reply-To: <417A3DD6.1030902@syphir.sytes.net>
On Sat, Oct 23, 2004 at 04:17:42AM -0700, C.Y.M wrote:
> >>Is there an alternative?
> >
> >
> >Maybe you could explain what you're actually trying to do at a higher
> >level first.
> >
> I have been using the lufs module in combination with autofs to be able
> to automount ftp sites on the fly. But, if lufs is broken due to the
> lack of the "kill_proc_info" symbol being available, perhaps I will just
> remove lufs and find another way (or wait until there is some kind of
> patch for lufs).
Well, that's _too_ highlevel :) The question is what lufs is trying to
archive by using the module.
prev parent reply other threads:[~2004-10-23 11:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 9:21 Unknown symbol kill_proc_info in 2.6.10-rc1 C.Y.M
2004-10-23 9:57 ` Arjan van de Ven
2004-10-23 9:57 ` Christoph Hellwig
2004-10-23 10:04 ` C.Y.M
2004-10-23 10:22 ` Christoph Hellwig
2004-10-23 11:17 ` C.Y.M
2004-10-23 11:28 ` Christoph Hellwig [this message]
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=20041023112838.GA30910@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syphir@syphir.sytes.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