Hi all,
[...]
I really understand, why setup-storage prefers the safe way, but for us the
old implementation was much better.
Could it be possible to extend setup-storage with an preserve-lazy-unsafe
option, that destroys data? Or does anyone already have a solution for this?
I
On Thu, 24 Feb 2011 09:56:20 +, Michael Tautschnig m...@debian.org
said:
setup-storage: the problem is the very very small differences in the
semantics
of the various preserve* options, which make it prone to both subtle
implementation errors and misunderstandings on the
I include separate options for fresh installs in my pxe configs that
boot FAI with the initial flag or whatever it is.
I filed a wishlist bug (#614914) for adding a new option to
fai-chboot for setting this flag. Shouldn't be that hard to
implement.
--
regards Thomas
Hi,
I'm not sure whether Manuel actually wants a lazy preserve, or indeed the
reinstall one
in fact, we currently use the reinstall preserve-option together with two
different fai-chboot configs.
And even if lazy is the desired way: there
must be some way to tell whether you will want to
I filed a wishlist bug (#614914) for adding a new option to
fai-chboot for setting this flag.
For us this feature won't be necessary, perhaps for other users?!
We use two configs, one with initial, one without.
So fai-chboot -c [install|install-initial] hostname works pretty well.
Hello everyone,
disk_config and setup-storage both have the option to preserve lazy, but the
implementation differs. (My explanation is simplified.)
disk_config:
You want to preserve a partition then the logic is:
- partition has the same size, preserve it (don't run mkfs)
or
- partition
Manuel Hachtkemper hac...@math.uni-bonn.de 2011-02-23 18:32:
Hello everyone,
disk_config and setup-storage both have the option to preserve lazy, but
the implementation differs. (My explanation is simplified.)
disk_config:
You want to preserve a partition then the logic is:
- partition
