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: <Pine.LNX.4.64.0802151343330.30301@fbirervta.pbzchgretzou.qr>
Date:	Fri, 15 Feb 2008 13:44:35 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Mikael Pettersson <mikpe@...uu.se>
cc:	Andi Kleen <andi@...stfloor.org>,
	Pavel Emelyanov <xemul@...nvz.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Alexey Dobriyan <adobriyan@...nvz.org>
Subject: Re: [PATCH] Make sysctl a separate filesystem


On Feb 15 2008 12:35, 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.

For time being only.

The kernel (currently) only auto-mounts invisible filesystems.
--
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/