On 11/9/2016 1:30 PM, Louis Lagendijk wrote:
On Wed, 2016-11-09 at 12:58 -0500, Przemek Klosowski wrote:
> On 11/09/2016 08:02 AM, Simo Sorce wrote:
>> Although this is true, one thing we could do is set a default hostname
>> that is static ("fedora" or similar is fine), and teach the utilities
>> used to join an AD/IPA/etc.. domain to generate a new random hostname if
>> they detect the hostname is the generic "static" one.
> The hostname is used in the install-time-generated disk volume names
> (/dev/mapper/fedora_myhostname-home), so changing it is confusing.
> Would it make sense to leave the old names? or rename the volumes?
> _______________________________________________
> devel mailing list --devel(a)lists.fedoraproject.org
<mailto:devel@lists.fedoraproject.org>
> To unsubscribe send an email todevel-leave(a)lists.fedoraproject.org
> <devel-leave(a)lists.fedoraproject.org%0A>
Is using a unique volume group name not actually preferable.
If one needs to add a disk from one machine to another it avoids the
problem of having 2 volume groups with the same name and therefore
overlapping LV names.
I got bitten by that once.
/Louis
The problem is that those VG/LV names are distinct from the host they're
a part of.... The only thing worse than a generic label for something is
an incorrect or misleading one, as happens occasionally with clones,
host renames or imaging a VM on top of that.
If we really don't have a better, persistent, local name for a system at
install time, then I don't see why reverting to /dev/VolGroup00/LogVol00
is horrible here. VG names should be human-readable and exist in a
namespace; shouldn't uniqueness should be from VG/LV UUIDs when we need it?
-jc