From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Disk Labels in Handbook
Date: Thu, 10 Feb 2011 15:17:47 +0000 (UTC) [thread overview]
Message-ID: <loom.20110210T160438-909@post.gmane.org> (raw)
In-Reply-To: 20110209200838.2f6efac2@digimed.co.uk
Neil Bothwick <neil <at> digimed.co.uk> writes:
> > These aren't needed to get a system up and running. Yeah, Ubuntu uses
> > them for various ID purposes, but nothing really critical. Unless
> > there's a clear need for them, for example if some package in the
> > @system set will use them in a way that our users will see, I doubt
> > the handbook needs to cover them. Adding labels using udev just seems
> > very finicky and time-consuming, and doesn't seem like it would be of
> > much utility when users are already swamped with everything else the
> > handbook asks them to do.
> Josh seems to be referring to UUID type disk labels, not filesystem
> labels. Which are you talking about?
Well, I think having this discussion, here on Gentoo-User is
our best place to sort out what we want. So far the discussion
on using labels makes it simple and straight forward.
Disk labels and file system labels are related topics, imho. My
thoughts are follow the KISS (keep it simple sonny) means that
using a scheme that is easy (like the default one currently in
the handbook) makes the most sense. Bright, skilled users,
such as those that adorn this list (cough gag snarl), surely
can use various schemes.
I like the idea of linking to another document for a robust
collection of alternatives and such, but keep the handbook
simple and straightforward. So Disk Labels would look quite
a lot like file system labels, but, that is just my
opinion.
Surely this discussion is warranted, before we all vote (Neil)
for our the best/brightest? person to complete the Bug. If it
comes from the list and a discussion occurred, like this one,
it can be reference from the bug, and the doc-devs will
have some confidence that much thought went into the suggestion.
This approach will superceed my "half-baked" ideas.....
Already we all agree that it is time to update the handbook.
So I still seek guidance....... and then consensus.....
and then we encourage one of our brighter members to
complete the bug.......
Surely Josh will like that? After all, he is still the
flux_gate.......
James
prev parent reply other threads:[~2011-02-10 16:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 13:51 [gentoo-user] Disk Labels in Handbook James
2011-02-09 14:16 ` Dale
2011-02-09 14:27 ` Mark Knecht
2011-02-09 20:58 ` Alan McKinnon
2011-02-10 10:00 ` Petri Rosenström
[not found] ` <20110210120055.6e7288c2@digimed.co.uk>
2011-02-10 12:31 ` Dale
2011-02-10 12:39 ` Joost Roeleveld
2011-02-10 12:45 ` Dale
2011-02-10 12:53 ` Joost Roeleveld
2011-02-10 12:56 ` Neil Bothwick
2011-02-10 13:14 ` Dale
2011-02-10 15:39 ` Stroller
2011-02-09 16:16 ` Jarry
2011-02-09 18:41 ` [gentoo-user] Re: Bug#354229 " James
2011-02-09 20:08 ` [gentoo-user] " Neil Bothwick
2011-02-10 15:17 ` James [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=loom.20110210T160438-909@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@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