From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] use.desc: add global USE flag 'split-sbin'
Date: Wed, 16 Oct 2019 11:06:27 -0500 [thread overview]
Message-ID: <20191016160627.GA29093@whubbs1.dev.av1.gaikai.org> (raw)
In-Reply-To: <2b4de5d1-e5f3-1c9d-792f-0e64002d04e3@uls.co.za>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
Hi Jaco,
On Wed, Oct 16, 2019 at 11:18:38AM +0200, Jaco Kroon wrote:
> Hi,
*snip*
> For what it's worth. All of my systems are installed with a fixed-size
> 512MB / with everything else (including /usr) on separate LVs.
>
> Whilst sbin vs bin is just a matter of what's available, to me it makes
> sense to keep these split. To me it's always been logical to keep
> administrative type (root) tools under sbin, and stuff that's generally
> useful for users under bin.
As I said in my previous message, sbin and /usr/sbin are supposed to
have statically linked binaries in them, "s" means static not
superuser.
> Keeping / and /usr split (or the ability to keep it split) is rather
> crucial for me. It's for historic installations a matter of space
> constraints on /. For new installations it's a matter of keeping / as
> small as possible in order to have a smallish bootable system which can
> be used for recovering the rest of the system, ideally without an initrd
> (which also works to an extent).
Having / and /usr on separate filesystems is not what split-usr is
about. split-usr just means that /bin /lib* and /sbin are directories
not symlinks.
Splitting / and /usr to separate filesystems without an initramfs is
not officially supported.
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2019-10-16 16:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 11:00 [gentoo-dev] [PATCH] use.desc: add global USE flag 'split-sbin' David Seifert
2019-10-12 11:11 ` Michał Górny
2019-10-12 16:02 ` William Hubbs
2019-10-12 17:01 ` Dennis Schridde
2019-10-12 17:52 ` David Seifert
2019-10-13 16:33 ` Mike Gilbert
2019-10-13 16:43 ` Mike Gilbert
2019-10-13 17:38 ` Michał Górny
2019-10-15 12:00 ` David Seifert
2019-10-15 16:02 ` Mike Gilbert
2019-10-15 16:04 ` Mike Gilbert
2019-10-15 17:34 ` David Seifert
2019-10-16 3:08 ` Joshua Kinard
2019-10-16 15:39 ` William Hubbs
2019-10-16 17:17 ` Ulrich Mueller
2019-10-16 18:19 ` William Hubbs
2019-10-17 6:59 ` Ulrich Mueller
2019-10-19 23:36 ` Joshua Kinard
2019-10-16 9:18 ` Jaco Kroon
2019-10-16 9:48 ` David Seifert
2019-10-16 10:03 ` Jaco Kroon
2019-10-16 10:38 ` Michał Górny
2019-10-16 16:06 ` William Hubbs [this message]
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=20191016160627.GA29093@whubbs1.dev.av1.gaikai.org \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox