Why make noswap and nodump ELEMENTs?
Why not just make them attributes with (true|false) values,
which default to false?
- dermot
On 01/20/11 16:13, Darren Kenny wrote:
On 20/01/2011 15:03, Drew Fisher wrote:
Matt,
- swap / dump on slices and zvols.
Since both swap and dump are considered attributes of a slice or zvol, they
should be simple boolean true|false in the schema. I would also like to
propose removing the concept of a "no_swap" and "no_dump" attribute. If a
user decides not to mark a slice or zvol as swap, the clients are responsible
for determining what is needed and will create zvols or slices as
appropriate. Same goes for zvol dump devices.
Drew, so how would a user specify they specifically don't want swap or dump
zvols created ?
If you don't mark a vdev as swap or dump, the installer will by default
attempt to create swap and dump zvols, so not specifying them does not mean
"do not create".
Would it make sense to add a simple, empty element called <noswap> or <nodump>
as a child element to <target>?
<!ELEMENT target (disk+, logical*, noswap?, nodump?)>
<!ELEMENT noswap EMPTY>
<!ELEMENT nodump EMPTY>
That way the user can control is a slice/zvol is meant for swap (is_swap) or
dump (is_dump) and if the user explicitly wants neither created, an empty
<noswap /> element can be created.
What do you think?
I think that works fine - I couldn't see why you needed to specify a zvol for
no_swap/dump anyway.
Thanks,
Darren.
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
