From: Anand Buddhdev <anand@celtelplus.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [solved] binfmt_misc trouble with kernel 2.6.7
Date: Sat, 14 Aug 2004 00:34:05 +0200 [thread overview]
Message-ID: <411D41DD.1080005@celtelplus.com> (raw)
In-Reply-To: <411CF503.40202@celtelplus.com>
Anand Buddhdev wrote:
> Hi,
>
> A few days ago I upgraded to fedora kernel 2.6.7-1.494.2.2. Before that,
> I had kernels in which binfmt_misc was compiled as a module. The wine
> init script modprobe'd the module and then registered /usr/bin/wine as a
> handler for windows executables. However, in the new 2.6.7 kernel,
> binfmt_misc is compiled into the kernel, so the modprobe in the wine
> init script fails. I can fix that, but main problem I am having is that
> now, the permissions on the /proc/sys/fs/binfmt_misc directory are 0555:
>
> dr-xr-xr-x 2 root root 0 Aug 13 19:04 /proc/sys/fs/binfmt_misc
>
> I cannot create a file called register under /proc/sys/fs/binfmt_misc.
>
> I created a Fedora bugzilla entry for this but I was told that this is a
> problem in the kernel upstream. Is this indeed a known problem, and is
> there a fix?
Geoffrey Leach from the Fedora list provided a hint to the solution.
There's no bug. I just have to add:
none /proc/sys/fs/binfmt_misc binfmt_misc defaults 0 0
to my /etc/fstab, and then the /proc/sys/fs/binfmt_misc directory
becomes writable, with a register and a status file in it. Sorry to have
bothered you all.
next prev parent reply other threads:[~2004-08-13 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 17:06 Anand Buddhdev
2004-08-13 22:11 ` Alan Cox
2004-08-13 23:51 ` Anand Buddhdev
2004-08-13 22:34 ` Anand Buddhdev [this message]
2004-08-13 22:52 ` [solved] " Lee Revell
2004-08-13 22:02 ` Alan Cox
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=411D41DD.1080005@celtelplus.com \
--to=anand@celtelplus.com \
--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®