>> 2. what's your requirement for the GUI DDU? >> >> For instance, how will the GUI DDU be called in background during the >> livecd startup? And how and where to show the notification for the >> missing driver? > The DDU will be called via the Gnome desktop autostart. See my blog > (just written today!) for an intro. blogs.sun.com/jaschwartz > > I am wondering if the scan during silent mode can be made more > light-weight by doing only the scan for devices with missing drivers > (accomplished using "prtconf -D" and looking for devices without a > driver for example) rather than checking packages and the other things > which are done during a standard DDU device scan today. > > When one or more devices are missing drivers, a popup notification > appears on the screen to say that there is at least one device missing > its driver. The popup notification is similar to what NWAM uses when it > finds a new interface to attach to. > > The add-drivers mode will display a window similar to what exists today, > accept it will allow installation of a specific IPS package, SVR4 > package or package from a DU image, and will allow the user to specify > the location (repo, directory). Please see sections 3.1 and 5.4.1 for > more details on the GUI DDU. > > The spec proposes an "unmount" button for unmounting selected removable > media. This is useful if, say, a user has two drivers to add, each on > its own USB stick. After the user finishes with the first USB stick, > the "unmount" button is pushed to umount it, and the user can then > insert the second USB stick to get the second driver. > > Please feel free to ask specific questions. >
This seems like a feature that could be deferred, perhaps indefinitely. It's relatively unlikely that multiple drivers actually need to be handled here, and even so, the average driver is far smaller than any commonly available medium these days, so telling users to put multiple drivers on one device doesn't seem unreasonable. Is there some case I'm missing here? Dave
