From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Anand Buddhdev <anand@celtelplus.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [solved] binfmt_misc trouble with kernel 2.6.7
Date: Fri, 13 Aug 2004 23:02:51 +0100 [thread overview]
Message-ID: <1092434570.25002.21.camel@localhost.localdomain> (raw)
In-Reply-To: <1092437540.803.22.camel@mindpipe>
On Gwe, 2004-08-13 at 23:52, Lee Revell wrote:
> That is certainly a Fedora bug if they update a kernel package that
> requires userland configs to be updated and then don't update those
> configs.
We've always not had an automount for that line. If there was an
automount it would keep loading that module for every user and 99.99999%
of the users don't care about or use binfmt_misc.
That's a decision that goes back to RH8 or so when binfmt_misc first
acquired its own file system.
Alan
prev parent reply other threads:[~2004-08-13 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 17:06 binfmt_misc trouble with kernel 2.6.7 Anand Buddhdev
2004-08-13 22:11 ` Alan Cox
2004-08-13 23:51 ` Anand Buddhdev
2004-08-13 22:34 ` [solved] " Anand Buddhdev
2004-08-13 22:52 ` Lee Revell
2004-08-13 22:02 ` Alan Cox [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=1092434570.25002.21.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=anand@celtelplus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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