On Mon, Mar 19, 2001 at 02:42:10PM -0800, did [EMAIL PROTECTED] write:
> On Mon, 19 March 2001, Sudhakar Chandra wrote:
> > you run to configure various software. For example, to configure sendmail,
> > you'd run /usr/sbin/sendmailconfig.
> is this the same thing that dpkg --configure runs?
Yes. Typically, when you are in the post install configuration phase,
dpkg --configure is run. This, in many cases, will run
/var/lib/dpkg/info/packagename.postinst which will, in turn, run
/usr/sbin/packagenameconfig
> > IMO, knowing how to edit config files by hand is also a great skill to
> > acquire.
> I know some and am learning more. But it's not pleasant to have the types
> of Linuxconf (on RedHat) wipe out your hard work while you're sleeping.
> YaST (on SuSE) doesn't do that (it creates a separate .Suseconfig file
> instead) and I'm hoping that Debian won't do either.
Think of /usr/sbin/*config as tools that are run to generate a base config.
The smartness of these config script varies widely. It is entirely left
upto the maintainer of a package to make their config script smart.
As a rule of thumb, run /usr/sbin/packagenameconfig the first time to
generate a basic config and edit it by hand.
> I've installed potato and upgraded to woody and there's some problem with
> libpaperg. removing that (and hitting enter instead of X) wiped out my
> base packages. Is this a problem with libpaperg or debconf perl modules
> or should I not updrade potato to woody?
woody is still unstable and things like these happen. Best thing is to
install the last stable version (potato) and install individual packages
from potato for which you need newer versions.
Thaths
--
pub 1024R/9B7FE6BD 1998-03-25 Sudhakar Chandrasekharan <[EMAIL PROTECTED]>
Key fingerprint = 8A 84 2E 67 10 9A 64 03 24 38 B6 AB 1B 6E 8C E4
uid Sudhakar Chandrasekharan <[EMAIL PROTECTED]>
----------------------------------------------
The mailing list archives are available at
http://lists.linux-india.org/cgi-bin/wilma/linux-india-help
