fuel-dev team mailing list archive

[Mike Scherbakov <mscherbakov@xxxxxxxxxxxx>]

> "off" for disks with no allocations.
This will potentially lead to failure in booting. I would suggest to keep
it still "on", even if it's unallocated. If user certainly knows what he is
doing, he will switch it to off, accepting a risk of not booting into the
system.

I believe we should keep it dump simple as for blond girl, still giving the
abilities for an expert to change defaults and details, with the
flexibility he wants...


On Thu, Apr 3, 2014 at 9:01 PM, Dmitry Borodaenko
<dborodaenko@xxxxxxxxxxxx>wrote:

> On Wed, Apr 2, 2014 at 10:33 PM, Mike Scherbakov
> <mscherbakov@xxxxxxxxxxxx> wrote:
> >> > As for ability not to partition chosen disks and write boot sector on
> >> > them
> >> > there were 2 ideas:
> >> >
> >> > Don't touch disk at all if user left all disk space unallocated. Every
> >> > partitioned drive will have boot sector. No UI modifications required.
> >>
> >> +1
> >>
> >> > Return "make bootable" checkbox for every disk so user can manually
> mark
> >> > disks which he wants to make bootable.
> >>
> >> Eventually we'll need this option, too.
> >
> > Only if it's enabled by default. Otherwise users won't be enabling it,
> and
> > thus failing to boot a node.
>
> Yes, it should set the default enabled state in line with the first
> option: "on" for all disks with partition allocations, "off" for disks
> with no allocations.
>
> --
> Dmitry Borodaenko
>



-- 
Mike Scherbakov
#mihgen