On Thu, Mar 22, 2001 at 02:22:43PM -0800, Sudhakar Chandra wrote:
> 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
>
> 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.
>
Yeah, and I found out that Debian package maintainers are smart enough. Eg
I installed and uninstalled apache a few times trying to resolve a problem
in the httpd.conf and my /var/www is still intact. Debian issues a notice
that /var/www in untouched. Guess that's really great foresight!
> As a rule of thumb, run /usr/sbin/packagenameconfig the first time to
> generate a basic config and edit it by hand.
>
> 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.
Thanks for the advice but in my bid to resolve conflicts one after the other,
the machine now runs the latest version of Sid, flawlessly (or so I hope). I
have yet to patch up with reiserfs though, since the screen sometimes freezes
while switching consoles and X and the hotkey is the only way left to go.
Seems things are mostly stable if you're a bit careful in reading the error
messages before hitting enter.
Thanks,
Indraneel
----------------------------------------------
LIH is all for free speech. But it was created
for a purpose. Violations of the rules of
this list will result in stern action.
