linux-kernel - Re: [PATCH] Make sysctl a separate filesystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080222012530.GD27894@ZenIV.linux.org.uk>
Date:	Fri, 22 Feb 2008 01:25:30 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Mikael Pettersson <mikpe@...uu.se>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Pavel Emelyanov <xemul@...nvz.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Alexey Dobriyan <adobriyan@...nvz.org>
Subject: Re: [PATCH] Make sysctl a separate filesystem

On Fri, Feb 15, 2008 at 12:35:23PM +0100, Mikael Pettersson wrote:
> Andi Kleen writes:
>  > Pavel Emelyanov <xemul@...nvz.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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/