public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wayne.Brown@altec.com
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to mount /proc/sys/fs/binfmt_misc ?
Date: Fri, 16 Mar 2001 10:12:42 -0600	[thread overview]
Message-ID: <86256A11.00590FF8.00@smtpnotes.altec.com> (raw)



Thanks for the quick response.  I took your suggestion (a) and created
/etc/binfmt_misc, and set up a test in my rc.local to mount it and register my
usual entries there if /proc/sys/fs/binfmt_misc doesn't exist.  So now it works
with both 2.4.3-pre4 and 2.4.2-ac20.

Wayne




Alexander Viro <viro@math.psu.edu> on 03/16/2001 09:37:49 AM

To:   Wayne Brown/Corporate/Altec@Altec
cc:   linux-kernel@vger.kernel.org

Subject:  Re: How to mount /proc/sys/fs/binfmt_misc ?





On Fri, 16 Mar 2001 Wayne.Brown@altec.com wrote:

>   The release notes specify this:
>
>      mount -t binfmt_misc none /proc/sys/fs/binfmt_misc
>
> but this doesn't work because
>
>      mount: mount point /proc/sys/fs/binfmt_misc does not exist

Grr... OK, I've been an overoptimistic idiot and missed that ugliness.

Solutions:
     a) mount it on some real place. And write there to register
entries instead of the bogus /proc/sys/fs/binfmt_misc
     b) add a couple of proc_mkdir() into fs/proc/root.c
That is, add
     proc_mkdir("sys/fs", 0):
     proc_mkdir("sys/fs/binfmt_misc", 0);
after the line that says
     proc_mkdir("sys", 0);

I would strongly recommend (a). In the long run we'll need to go that
way.




             reply	other threads:[~2001-03-16 16:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-16 16:12 Wayne.Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-16 15:23 How to mount /proc/sys/fs/binfmt_misc ? Wayne.Brown
2001-03-16 15:37 ` Alexander Viro
2001-03-16 17:49   ` Richard Guenther
2001-03-16 17:58     ` Alexander Viro
2001-03-16 18:07       ` Alexander Viro
2001-03-16 18:32         ` David Weinehall
2001-03-16 18:48           ` Alexander Viro
2001-03-19 19:29             ` Colin Watson
2001-03-20 10:12               ` Richard Guenther
2001-03-22 18:28                 ` Colin Watson
2001-03-22 19:07                   ` Alexander Viro
2001-03-23  9:34                     ` Richard Guenther
2001-03-21 19:18     ` Alan Cox
2001-03-16 16:02 ` Thomas Dodd

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=86256A11.00590FF8.00@smtpnotes.altec.com \
    --to=wayne.brown@altec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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