Hi Peter, Thanks for looking at this. Comments inline..
> On 1/31/07, Sarah Jelinek <Sarah.Jelinek at sun.com> wrote: >> Hi Everyone, >> >> I have posted details for the Dwarf Caiman project, including planned >> feature set, and preliminary schedule, >> http://opensolaris.org/os/project/caiman/ > > OK, some comments based on the feature set: > >> Graphical installation interface for initial installation based on >> Caiman mockups >> which replaces Solaris Express, Developer Release path introduced in >> build 55. > > Must have a look at that sometime... > >> Runs within current miniroot + any required libraries for look & feel > > How close is it to a LiveCD/DVD? > It isn't. It is our existing miniroot, and it runs off of the CD/DVD that we provide with this distribution. There is no Live running Solaris, except for the miniroot during this. We are working on the LiveDVD project, but haven't had a chance to integrate that experience in with the install experience. It is in our plans. >> Network configured for DHCP always > > With no choice? What if that's the wrong choice? How does > a user who can't use that change it? > You can choose the non Solaris Express, Developer Edition path on the grub menu. This project only replaces that installation experience. The idea is to try to provide a streamlined path to getting Solaris installed. Also, after installation using the Solaris Express, Developer Edition path, you can of course reconfigure your network settings. Kind of a pain though. >> Install to pre-configured UFS layout within Solaris2 FDISK partition > > What is the layout? (See later.) > >> Installs SUNWCxall metacluster, no customization, plus developer tools > > Ugh. Now, who is the target audience here? I can't think of anybody > for whom SUNWCxall is a suitable starting point. > The target is developers. I can see where SUNWCxall might be a bit heavyweight. It includes stuff from OEM's which might not be appropriate for developers. >> User prompted for: >> date/time/timezone >> language/locale >> root password >> initial user account >> x86 and sparc platform support > > In an FDISK partition? Fdisk for x86, vtoc for sparc. There will be a choice to modify the fdisk layout, but the sparc vtoc layout is based on the default filesystem layout we provide. > >> Will provide for preservation of existing data > > How? Is this an upgrade, leaving the data in place, or > is there some other means? > No, it means leaving data in place, like data in your /export. Not OS specific data, but other data you want to preserve. We won't overwrite that. >> Will not provide customization of filesystem layout > > OK, so what is the default filesystem layout going to look like? > Like this, sizes dependent on disk size [x] / [ ] /opt [ ] /usr [ ] /usr/openwin [ ] /var [X] swap Everything under / fs except swap and we create an /export/home filesystem as well. >> Upgrade from Solaris Express, Developer Release, build 55 > > If you upgrade a system with a customized software installation, > will those customizations be preserved? Yes, they should be preserved. > > I think the one thing I don't understand is what the target > audience is. The simplicity seems aimed at home users, > but then the developer tools might add considerable weight > and SUNWCxall isn't appropriate. Certain aspects of this > wouldn't work in a business context - where networks and > systems are tightly controlled (in my case, the dhcp > requirement might be a problem, as the way to make most > of my Solaris machines work is to keep them out of dhcp > entirely, and I wouldn't be happy with an unhardened > SUNWCxall machine on my network). And a standalone > developer might want more control. The target audience is supposed to be developers. The idea is the lower the barriers to installing Solaris for laptop/x86 users, and get them up and running with the development tools they need. Your point about SUNWCxall being too heavyweight is valid. What would you suggest as the default cluster we should install for this target audience? And, what type of default network settings should be consider for developers? Keep in mind that that user can choose the traditional installation path and configure their filesystem layout and network settings if they choose. They just won't get the developer tools. These can be installed later however. Thanks again for taking the time to review and comment. sarah
