On 02/26/10 05:10 PM, Kendall Tatum wrote:
>> Quotas are part of the answer (in terms of disk space consumption). How
>> /var will be handled is currently a topic of discussion, the setuid aspect is
>> one thing being considered. However, since you're new to OpenSolaris
>> and ZFS, I'd encourage
+--
| On 2010-02-26 14:10:16, Kendall Tatum wrote:
|
| Thank you for your help Dave. It has been very educational. I have been
reading the ZFS documentation to learn more about ZFS and OpenSolaris. I do
have another q
> Quotas are part of the answer (in terms of disk space consumption). How
> /var will be handled is currently a topic of discussion, the setuid aspect is
> one thing being considered. However, since you're new to OpenSolaris
> and ZFS, I'd encourage taking some time to get familiar with the sys
On 02/23/10 07:23 PM, Kendall Tatum wrote:
>> The text installer provides slice manipulation as a method for
>> coexistence with existing UFS installations (and as a way to
>> divvy up the disk on SPARC systems).
>>
>> /var and /opt can be managed via ZFS after the install
>> completes.
>> Currentl
> The text installer provides slice manipulation as a method for
> coexistence with existing UFS installations (and as a way to
> divvy up the disk on SPARC systems).
>
> /var and /opt can be managed via ZFS after the install
> completes.
> Currently, they are folders on the boot filesystem
>
> On 02/22/10 06:37 PM, Kendall Tatum wrote:
> > I have been experimenting with the text-based
> installer build textinstaller-131b. I am trying to
> create seperate /var and /opt slices, but the
> installer does not let me create them. Is this by
> design?
>
> I assume by slices you mean filesy
On 02/22/10 05:47 PM, Gary Mills wrote:
>> /var and /opt can be managed via ZFS after the
>> install completes.
>> Currently, they are folders on the boot filesystem
>> (rpool/ROOT/opensolaris at first install).
>>
> How is that possible? By copying the data from a
> directory to a filesys
On 02/22/10 06:37 PM, Kendall Tatum wrote:
> I have been experimenting with the text-based installer build
> textinstaller-131b. I am trying to create seperate /var and /opt slices, but
> the installer does not let me create them. Is this by design?
I assume by slices you mean filesystems? Th
> /var and /opt can be managed via ZFS after the
> install completes.
> Currently, they are folders on the boot filesystem
> (rpool/ROOT/opensolaris at first install).
How is that possible? By copying the data from a
directory to a filesystem? That's quite awkward.
> There's no
> need for var
The text installer provides slice manipulation as a method for
coexistence with existing UFS installations (and as a way to divvy up
the disk on SPARC systems).
/var and /opt can be managed via ZFS after the install completes.
Currently, they are folders on the boot filesystem
(rpool/ROOT/open
I have been experimenting with the text-based installer build
textinstaller-131b. I am trying to create seperate /var and /opt slices, but
the installer does not let me create them. Is this by design?
--
This message posted from opensolaris.org
11 matches
Mail list logo
