From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcel Holtmann Date: Tue, 11 Aug 2009 22:22:44 +0000 Subject: Re: [PATCH 2/2] hid2hci: when recovering from S3 use parent devpath Message-Id: <1250029364.30166.38.camel@localhost.localdomain> List-Id: References: <4A6E19FF.5070207@dell.com> In-Reply-To: <4A6E19FF.5070207@dell.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Hi Karl, > > Honestly the entire split of / and /usr, like we usually do, is just > > plain stupid in the first place. It might be ok if we would put the > > desktop stuff in /usr, but spreading random commandline tools and > > libraries around causes nothing but trouble for no good reason. > > Theory says that /usr can be mounted read-only, which could > improve system security for those binaries that live there > or have other advantages regarding media used, storage sharing, etc. > http://www.pathname.com/fhs/pub/fhs-2.3.html#THEUSRHIERARCHY the security argument is non-sense. Only SELinux can really protect you here. Once you are root, you just re-mount it read-write. > The other side of the argument is that / is supposed to be > able to be kept small. > http://www.pathname.com/fhs/pub/fhs-2.3.html#THEROOTFILESYSTEM As Kay mentioned, that is fine for the UI components, but mostly all system components (even that are not needed for boot) should be just be living in /bin and /sbin. And so even the separation between bin and sbin is kinda pointless nowadays. It is Unix legacy and at some point Linux has to cut some of its roots to get ready for the future. Similar to what MacOS X did. Regards Marcel