Re: Vi backspace key problem

[Dag Wieers <dag wieers com>]

On Wed, 20 Jul 2005, Chester R. Hosey wrote:

> On Wed, 2005-07-20 at 02:34 +0200, Dag Wieers wrote:
> 
> > PS I've once written a tool in bash to help in cleaning up leftover files 
> > like .rpmnew, .rpmsave and .rpmorig and I desperately need to rewrite that 
> > in python (allowing to diff available files, verifying with rpmdb and 
> > being smart about it in general :))
>
> >From the wishlist-entries-I-don't-care-enough-to-code-myself dept:
> 
> When run interactively and faced with modified configuration files, dpkg
> prompts the user and allows them to choose whether to keep the original,
> install the upstream version, run a shell to examine the situation, or
> examine a diff between the versions.

Well, RPM is designed to be used unattended. And there's no reason to sort 
out the config-file differences afterwards. That of course does not handle 
all of the complexity when doing upgrades, but upgrading to the latest 
Debian stable is no easy task either.

Besides if you do a major upgrade (especially in production) it's fairly 
important you understand the situation. Chance is that the complexity of 
your environment is not taken care of in all details anyway.


> It's a nice feature. It would be nice if up2date-with-rpm did something
> similar, or if RHN noted that an upgrade didn't include a configuration
> file update due to user changes. I'd be really impressed if RHN went to
> far as to provide a diff of the configuration files so the administrator
> could evaluate the importance without having to log in and search
> for .rpm{new|save|orig} files manually.

I don't think it belongs as part of RHN, besides I don't think you can 
implement all the complexity correctly, which would only become a 
liability to Red Hat if they have to support it.

And since you're interested. Here is the script I was refering to and 
hope to implement in python one day (with extra features like diffs and 
more intelligence).

	clup.sh		cleans up left-over config files
	bup.sh		makes a poor man's backup (partly replaced/rewritten with dconf)

Use at own risk :) Preferably with cloop if you're unsure.

clup.sh [-f] [-h] [-q] [-t] [-v] [-x] [paths...]

	-f	force-mode, perform changes
	-h	help (apparently not updated)
	-t	test-mode, only report changes (default)
	-q	quiet
	-v	verbose
	-x	don't leave mount-point

bup.sh [-f] [-i] [-h] [-l] [-t] [-u] [-x] [paths...]

	-f	full backup
	-i	incremental backup
	-h	help (also not updated)
	-l	list files (no backup made)
	-t	test-mode
	-u	include user directories
	-x	don't leave mount-point

Kind regards,
--   dag wieers,  dag wieers com,  http://dag.wieers.com/   --
[all I want is a warm bed and a kind word and unlimited power]