I am sorry if I am coming in late to the discussion, but I had a few cycles and wanted to ask a few questions.
On 9/23/09 9:50 PM, Glynn Foster wrote: > Hey all, > > Sue asked me to provide a summary of discussion. I don't think the > thread moved very far last time, but I've removed a few things from the > list that I think now are inappropriate. > > Comments, feedback still welcome but I'd probably recommend to start > with this package list as soon as the interactive install images are > ready and refine from there. > > > Glynn > > > Current Package Proposal > ===================== > Core > - Enough to get to basic console prompt > - ksh93, bash, zsh, tcsh, csh, ... > - awk, sed, gawk, gtar, less, more, rsync, screen, ssh(d), wget, gpatch... > - dialog > - /usr/gnu/bin default > - Drivers > - All included unless reason not to (IB, iSCSI, FC, ...) Does this mean that all drivers will be installed by default? Is there any way to separate these out? Virtualized platforms may not need many of the drivers that are installed by default today. I realize that there is a tradeoff here. We want things to just be able to work, but if we are putting together an absolute core set of packages that people could potentially use as the base for minimized installations, (virtual or physical) appliances, etc. - then it would be nice to have a true core set of drivers that can be supplemented as needed. With the advent of the network package repo, installing new drivers is not as painful as it used to be ;-) > - Non graphical device driver utility > - Enough to get basics working out of the box > - ZFS, CIFS, COMSTAR I would say that even CIFS/COMSTAR may be too much for a "Core" although my definition of core is closer to the Solaris 10 view of SUNWCmreq. We have a lot of customers who want to build minimal configurations and if this is not the place that is fine, but I would like to make sure that anything done would not inhibit work to put a smaller footprint in place at some point. Thoughts? > - IPS, BE > - Zones, Xen, LDOMs and other virtualization utilities Same here. > - DTrace Toolkit > - Crossbow, IPMP, NWAM (off by default), DHCP server, DNS, NFS Why would a DHCP server be a core element? I would also say that NFS is likely not a core service (using my definition of core of course) > - Volume Management, Suspend and resume (incl powertop, latencytop) Suspend / resume is interesting for physical systems but what about virtual platforms? > - Trusted It would be interesting to see how we could build multi-level appliances without a windowing system, etc. > - CUPS > - Remove graphical desktop environment and utilities > - GNOME, OpenOffice, Firefox, Thunderbird, X Again, these things would not be core for the types of use cases that I encounter - so I apologize if you are focusing your efforts on different sets of use cases. g
