Sanjay G. Nadkarni wrote: >> <div id="jive-html-wrapper-div"> >> >> Hi everyone.<br> >> <br> >> Sorry for the late response. I just saw >> this...<br> >> <br> >> Live CD isn't always a throw-away environment, as the >> booted >> environment is cpio-ed onto a target hard drive when >> installed. Driver >> Update is a project which takes advantage of this, >> using the DDU to >> install missing drivers in the booted environment, >> before the booted >> environment is cpio-ed to the hard drive.<br> >> <br> >> DDU (Device Driver Utility) will be enhanced to >> install SVR4 packages >> to get drivers. The contents file will need to >> be accurate on the hard >> drive w.r.t. these SVR4 packages.<br> >> <br> > Even with DDU, LiveCD by definition is a throw away environment. > If for instance the system reboots the user will have to redo all the > pkgadds. So there's no need for the contents file to consistent across > reboots.
Hi Sanjay, I agree that we don't need to keep contents file consistent across reboots (and thus pkgserv SMF service can be disabled), but as Jack pointed out, since contents file on target is the one copied from LiveCD, I think we need to keep it consistent for the installation. I concur with Jack that it could be done by calling 'pkgadm sync -q' before CPIO transfer phase begins - it would force pkgserv daemon to flush the log file into contents file making sure that contents file is accurate. Jan
