[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Proposal for --noformat handling

On 11/21/2010 05:02 PM, Bill Nottingham wrote:
Chris Lumens (clumens redhat com) said:
For a long time now, we've been telling people that anaconda/kickstart's
not going to grow an option for every single mkfs feature there is.
They need to use %pre to create the filesystems and then specify them in
kickstart with --noformat.  People seem to be happy with that as it lets
them do whatever they want.

That I understand.

On the other hand, sometimes we get bug reports from people who have
chosen to reuse their existing installation's / in a new installation,
but do not format it.  This is either through --noformat or through the
UI.  dlehman has a patch to make sure / is formatted, but that will kill
the advantages of the above paragraph.

This I don't - isn't this best treated as just user error?

The way we currently do things, yes. I think what clumens and I were discussing was shifting the --noformat option from "do not format this volume" to "do not format this volume, but if I also provide specific instructions on how that volume is to be formatted, you can run those". So we still get the traditional handling of --noformat, but also add in this capability for users to override anaconda's formatting code.

It help us with the bug reports we get from users who need bizarre format requirements or who want to specify other options to mke2fs and so on, but it also gives us a permanent workaround for letting users experiment with new filesystem types for / before we have formatting code in anaconda.

David Cantrell <dcantrell redhat com>
Red Hat / Honolulu, HI

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]