Dick Davies wrote:
On 15/08/06, Lori Alt <[EMAIL PROTECTED]> wrote:
Brian Hechinger wrote:
> On Fri, Jul 28, 2006 at 02:26:24PM -0600, Lori Alt wrote:
>
>>>What about Express?
>>
>>Probably not any time soon. If it makes U4,
>>I think that would make it available in Express late
>>this year.
>
>
> Is there a specific Nevada build you are going to target? I'd love to
> start testing this as soon as possible. I have both SPARC and x86
here
> to play with.
You need more than a Nevada build. You also need the
installation code. We're working on an OpenSolaris
community web page for zfs-boot. On that web page
will be links to files that can be downloaded for
putting together a netinstall image or a DVD for
installing a system with a zfs root file system.
We hope to have that available in the next few weeks.
That's excellent news Lori, thanks to everyone who's working
on this. Are you planning to use a single pool,
or an 'os pool/application pool' split?
I'm not quite sure what you mean by an "os pool/application pool"
split. I would have thought that the *executables* for an application
would normally be installed somewhere in the Solaris namespace
(i.e., the name space established by a Solaris installation: root, /usr,
/opt, /var, and so ) and would thus be part of the "personality"
of a system. Data, on the other hand, is typically NOT part of that
namespace. So your databases, etc. would often be installed somewhere
else. Thus I think of the most important split as the "os pool/data pool"
split. Maybe that's what you meant. If so, then the answer to your
question is:
The plan right now is to encourage (though not mandate) separate
pools for the Solaris name space and for data. There are three reasons
for this:
1. There will be some restrictions on root pools, at least initially
and perhaps permanently, that you would probably not want to place
on pools used for data. For example, no RAID-Z or concatenation of
vdevs. These might be relaxed at some time, but right now, limitations
in the boot PROMs cause us to place restrictions on the devices
you can place in a root pool. (root mirroring WILL be supported,
however).
2. Data is theoretically shareable and transferable among different
instruction set architectures. System software is not.
3. There are advantages to separating the "personality" of a machine
from its data. If they are separated, one can be modified (i.e., patched,
upgraded, moved from one kind of storage to another, etc) without having
to affect the other.
As an aside, is there a general method to generate bootable
opensolaris DVDs? The only way I know of getting opensolaris on
is installing sxcr and then BFUing on top.
I actually don't know much about that right now. Someone else might have to
answer that question for you.
Lori
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
