Bart Smaalders wrote: > Kyle McDonald wrote: >> Bart Smaalders wrote: >>> Benjamin Brumaire wrote: >>> >>>> Hi, >>>> >>>> I experienced the new installation process while setting a new >>>> system. >>>> It feels very easy to install Solaris Express Community Edition b87 >>>> and >>>> I think it 's a good thing to simplify the process. But making thing >>>> easier shouldn't make the process inflexible. In Unix-style there >>>> should >>>> be room for modification. Especialy disk layout. Maybe I missed >>>> something but I wasn't able to find a way to modify the default >>>> layout. >>>> In that case I think the simplification process of installing >>>> opensolaris went too far. >>>> >>> >>> Is the problem that you wish to repartition the disk? Note that ZFS >>> doesn't >>> use fixed boundaries for filesystems, so space allocation should not >>> be an issue >>> inside the disk/partition chosen for OpenSolaris. >>> >>> >> Even with ZFS, the installer should let you define which sub trees >> (/, /usr, /var) are separate ZFS filesystems, and set fixed sizes >> (Quotas? Reservations?) on them. > > Why do you feel this is necessary? The current layout is obviously > not yet > finished, but once /var/mail. /var/log etc are properly separated, > what user > benefit is derived by setting quotas before installation. Setting quota's before? None I guess. Maybe I'm mistaken, but I was under the impression that only XFS filesystem root's could have quota's and reservations. Is that wrong?
If not, then the thing that *is* needed before installation is defining which branches are separate FS's, and which aren't. Once you provide that, it seems convienent to allow setting size at the same place. > > If desired (which makes little sense for disks containing OS files), such > quotas can be added later on, or removed > > Any work done to ease administration tasks in a not yet installed image > is basically useless for any other purpose. Only those items that > _cannot_ > be done after install should be done before hand. > I guess. At a minimum allowing the user to define where a new ZFS starts in the tree seems like something that can't be done later. (zfs split anyone?) I understand the idea to simplify the install experience for users by not asking questions they may not understand, or know how to answer. At the same time, it seems like there's an oportunity (maybe for a later release) to allow users who know what they want to specify it, and end up with a complete usableystem after install, with out any manual work needed from them. Personally, I've only used the interactive installer when trying out the Indiana previews. When all is said and done I'll be doing 99% of my installs through JumpStart or it's replacement. In that environment I'd hope to be able to specify all of this info in one place, and have a system that is fully ready to go after the install completes. -Kyle > - Bart > > >
