All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
	Pavel Emelyanov <xemul@openvz.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Alexey Dobriyan <adobriyan@openvz.org>
Subject: Re: [PATCH] Make sysctl a separate filesystem
Date: Fri, 22 Feb 2008 10:40:02 +0100	[thread overview]
Message-ID: <47BE9872.5090706@firstfloor.org> (raw)
In-Reply-To: <20080222012530.GD27894@ZenIV.linux.org.uk>

Al Viro wrote:
> On Fri, Feb 15, 2008 at 12:35:23PM +0100, Mikael Pettersson wrote:
>> Andi Kleen writes:
>>  > Pavel Emelyanov <xemul@openvz.org> writes:
>>  > >    this subdir;
>>  > > 3. sysctl inodes are now smaller than the procfs ones.
>>  > 
>>  > That's always a good thing.
>>  > 
>>  > > Note: update your initscripts to mount sysctl filesystem 
>>  > > right after the proc is mounted in order not to lose your
>>  > > /etc/sysctl.conf configuration (and optionally fstab).
>>  > 
>>  > That will break about everybody's init scripts I suspect.
>>  > 
>>  > I think you would need to go through some deprecation
>>  > period for this at least, with printks warning people
>>  > to fix their init scripts.
>>  > 
>>  > Or better find some way to do the mount automatically.
>>
>> Doing it automatically is the only acceptable way, IMO.
> 
> When and where?

Al, how would you solve the problem?

-Andi



  reply	other threads:[~2008-02-22  9:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 10:39 [PATCH] Make sysctl a separate filesystem Pavel Emelyanov
2008-02-15 10:47 ` Andi Kleen
2008-02-15 11:35   ` Mikael Pettersson
2008-02-15 12:44     ` Jan Engelhardt
2008-02-15 16:34       ` Randy Dunlap
2008-02-15 17:18         ` Jan Engelhardt
2008-02-15 16:57       ` Oliver Pinter
2008-02-15 18:27         ` Jan Engelhardt
2008-02-22  1:25     ` Al Viro
2008-02-22  9:40       ` Andi Kleen [this message]
2008-02-22  9:52       ` Mikael Pettersson
2008-02-19 14:24 ` Stephen Smalley

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=47BE9872.5090706@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=adobriyan@openvz.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=viro@ZenIV.linux.org.uk \
    --cc=xemul@openvz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.