Re: Selection-time configuration, delayed configuration, &c
On Wed, 22 Jan 1997, Ian Jackson wrote:
ian >Why do we want selection-time configuration ?
ian >
ian >(NB: this is not a rhetorical question.)
ian >
ian >It seems to me that this has been much-touted, but isn't actually all
ian >that useful.
It would be very useful to minimize the time a package is in the
"unconfigured" state. Configuring the package prior to installation
enables the package manager to immediately configure and activate the
package thus minizing downtime.
And it gets rid of the need for "Predependencies" since all packages
are always configured.
It will greatly simplify our packagemanagement and make upgrades
of running debian servers possible.
Right now dpkg behaves in a way that causes me great concern:
One package after another is unconfigured (daemons disabled, system
functionality switches off!) until all packages are unpacked. Then dpkg
begins to configure packages. Let one package ask a question and the
whole system comes to standstill until the administrator gets back
to the console.
After experiences with this scheme of things on two of our
mission critical servers I will no longer use dselect
on mission critical systems. Instead I have written a wrapper
script around dpkg which does one by one dpkg -i for each package.
--- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---
Please always CC me when replying to posts on mailing lists.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: