On Wed, 2011-10-26 at 18:44 -0700, John Reiser wrote: > On 10/26/2011 05:25 PM, David Lehman wrote: > > > It sounds like the basic reason you have this problem of knowing which > > filesystems are which stems from that fact that you create the > > partitions outside of anaconda. Do you have some requirements for > > partitioning that anaconda cannot satisfy? > > Absolute control over where it goes (down to the sector). If you just feel the need to have total control, have at it. I do just about everything I can on the command line so I can control things, too. > An option to label the filesystem. > > I'll take suggestions, but I require the capability to override everything. > Also, from time to time a new system will overwrite an old one. > The last customer for the old partition finally upgraded, and > new users of systems of that vintage are deemed unlikely. > Locating the old filesystem+partition by label is the easiest method. > I also take screenshots of gparted. > > > This is certainly something we will consider. We do want to discourage > > the use of labels as the primary (/etc/fstab, /etc/crypttab, &c) means > > of identifying filesystems since they are not guaranteed to be unique, > > Filesystem UUIDs are not guaranteed to be unique, either, and duplicates > _do_ happen. The obvious method of cloning a filesystem (/bin/dd) > duplicates the "UUID", too. I've done it once by accident, and a > few times on purpose :-) Sure, but the only way to do that is to do a dd or similar. With labels, there are plenty of ways to end up with duplicates, many of which are nowhere near as unreasonable as copying a filesystem without updating the UUID of one of the copies. > > > > but that does not necessarily preclude an interface for specifying > > and/or viewing labels as a convenience. > > > > FWIW kickstart already allows both arbitrary identifiers for existing > > devices/filesystems (include LABEL=) and an option to specify a label > > when creating a filesystem (--label=). > > In general I don't understand why the graphical parts of the installer > aren't just an app whose output is a kickstart file, and the actual > install is just an execve() with the kickstart file as its only input. > You are not the only one. _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
