From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: util-linux@vger.kernel.org
Subject: Re: LUKS partition types, redux
Date: Tue, 25 Nov 2014 09:36:29 -0600 [thread overview]
Message-ID: <5474A1FD.1060607@gmail.com> (raw)
In-Reply-To: <20141125112615.GC2610@x2.net.home>
Karel Zak wrote:
> On Mon, Nov 24, 2014 at 01:56:51PM -0600, Bruce Dubbs wrote:
>> Karel Zak wrote:
>>> On Mon, Nov 24, 2014 at 09:42:50AM -0500, Phillip Susi wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> On 11/24/2014 6:37 AM, Karel Zak wrote:
>>>>> The current trend is to use partition type to define for what
>>>>> purpose we want to use the partition (for example "this is /home")
>>>>> independently on partition format.
>>>>
>>>> I wouldn't call this bone headed idea of redhat's a trend. Using
>>>> partition table type codes to decide to auto mount in particular parts
>>>> of the filesystem is such a brain damaged idea, those who thought it
>>>> up need beaten with a clue-by-four and its use needs to be *strongly*
>>>> discouraged.
>>>
>>> well, it's designed for auto-generated fstab-less systems like
>>> containers/virt images, etc. I'm not big fan of this feature, but for
>>> some use cases it makes sense. (And it's systemd upstream decision.)
>>>
>>> Anyway, use partition type for "usage" makes more sense than for "fs-type".
>>
>> Since when is systemd upstream of util-linux?
>
> Ah.. freedesktop guys introduced some new GUID and util-linux project
> has accepted these identifiers (rather than interpret these IDs as
> "unknown") ... as well as we accepted partition IDs for Apple stuff,
> as well as we accepted Hurd patches, ports to freebsd, uClibc,
> not-perfect zram stuff from kernel, stuff from SysVinit, and many
> many many other things.
>
> I don't plan to be censor for another projects and apply any
> emotional criteria. The reason why this project still alive is that
> we are very friendly to arbitrary distributions and another projects.
I have not problem with that. I just don't want to see a hard
dependency on systemd like other projects have done. There are a lot of
projects that are mutually dependent, but the term upstream sounded some
alarm bells for me.
I do think util-linux is managed in an excellent way.
-- Bruce
next prev parent reply other threads:[~2014-11-25 15:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 20:59 LUKS partition types, redux Drake Wilson
2014-11-19 22:24 ` Dale R. Worley
2014-11-19 22:37 ` Drake Wilson
2014-11-20 21:33 ` Dale R. Worley
2014-11-21 7:47 ` Milan Broz
2014-11-21 7:54 ` LUKS partition types, redux (wandering into the weeds) Drake Wilson
2014-11-20 16:43 ` Bug#770211: LUKS partition types, redux Phillip Susi
2014-11-24 4:45 ` Drake Wilson
2014-11-24 14:33 ` Phillip Susi
2014-11-24 14:37 ` Drake Wilson
2014-11-24 14:45 ` Phillip Susi
2014-11-24 14:48 ` Drake Wilson
2014-11-24 14:58 ` Phillip Susi
2014-11-24 15:04 ` Drake Wilson
2014-11-24 15:09 ` Phillip Susi
2014-11-24 16:10 ` Karel Zak
2014-11-24 16:27 ` Phillip Susi
2014-11-25 15:18 ` Dale R. Worley
2014-11-24 11:37 ` Karel Zak
2014-11-24 12:09 ` Drake Wilson
2014-11-24 14:42 ` Phillip Susi
2014-11-24 15:46 ` Karel Zak
2014-11-24 19:56 ` Bruce Dubbs
2014-11-25 11:26 ` Karel Zak
2014-11-25 15:36 ` Bruce Dubbs [this message]
2014-11-25 15:20 ` Dale R. Worley
2014-11-24 15:48 ` Dale R. Worley
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=5474A1FD.1060607@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=util-linux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.