[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [PATCH] fsset.py tweaks for ext4dev & xfs
- From: Jeremy Katz <katzj redhat com>
- To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list redhat com>
- Subject: Re: [PATCH] fsset.py tweaks for ext4dev & xfs
- Date: Thu, 31 Jan 2008 14:22:48 -0500
On Thu, 2008-01-31 at 12:49 -0600, Eric Sandeen wrote:
> Jeremy Katz wrote:
> > On Thu, 2008-01-31 at 11:19 -0600, Eric Sandeen wrote:
> >> ext4dev just got a "test_fs" flag which soon must be set in order for
> >> the kernel to mount it; this will prevent ext3 from accidentally getting
> >> mounted as ext4, and making it hard to go back. (when ext4 goes prime-time,
> >> the need for this flag will be removed).
> >
> > Seems reasonable, only one question -- what happens once the need for
> > test_fs goes away if people's ext4 filesystems have the test_fs flag
> > set?
>
> Well, those people who got there via anaconda also had to type
> "iamanext4developer" and can use debugfs to unset the flag, if need be.
>
> Although I think the patch Ted has in store for the kernel will mount a
> "test_fs" with "production" code; just not vice versa.
>
> In any case, I think we should lift the "iamanext4developer" requirement
> and the "test_fs" mkfs option at the same time, so that the only people
> who wind up with the flag set at least *claimed* to know what they are
> doing.
Sounds reasonable. Applied the patch. Thanks!
Jeremy
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]