Re: Bootadm: managing a diskless client

>
>> I am sponsoring this case for myself.  I believe it
qualifies
>> for self-review with automatic approval and I've
marked it as
>> such, but if anyone disagrees, it can be promoted
to a fast-track.
>> I am requesting minor/patch binding for this
change.
>
>Quick question - why can't bootadm figure this out for
itself and do
>the right thing?
>
>- Bart
>

We can't yet communicate with the machine, of course, and
there's
nothing about the root filesystem layout that tells us the
platform
implementation (sun4u or sun4v).  Bootadm builds
per-platform archives
as we've found otherwise boot time suffers.  The diskless
admin tools
already know the client's implementation so it's just a
matter of
communicating that to bootadm during the process of
configuring
the client.


-jg

_______________________________________________
opensolaris-arc mailing list
opensolaris-arcopensolaris.org

>
> We can't yet communicate with the machine, of course,
and there's
> nothing about the root filesystem layout that tells us
the platform
> implementation (sun4u or sun4v).  Bootadm builds
per-platform archives
> as we've found otherwise boot time suffers.  
Side note: I've noticed that the time you save in boot time
you (seem 
to, at least for OpenSolaris) pay back later in reboot
time.
_______________________________________________
opensolaris-arc mailing list
opensolaris-arcopensolaris.org