> We have the following need:
>   - We have a directory with all the rpms that a machine should have
>     installed.  Nothing more, nothing less.  We therefore need a way
>     of _removing_ rpms that are not in the directory we are 'syncing'
>     with.  AFAIK, autorpm doesn't support this.
>   - We need a command-line interface.

        An added CRC and timestamp check database could be a nice idea for
checking for modified files - something that after the rpm is installed
- it parses through the file list ( -ql ) and updates the CRC/timestamp
database.  Then you can add a program to cron ( daily for SOHO type
systems, hourly for larger trafic systems ) this database could be
stored offsite, or copies sent offsite via the same program.  This could
then be akin to the anti-virus programs in win/mac that monitor for
modifed files.  So even if someone got root and put in a linux rootkit
with modified programs - you could have the database compare itself
against the offsite copy if you suspect a problem.  This would get
around a rpm aware hackers who might modify the local rpm database.  If
it finds altered files, the module could present a menu of altered files
- look up what rpm they came from - and allow you to pluck it from a
secure copy ( say from the redhat ftp site, or via a local read only
media like a distribution CD or a site custom burnt archive. )

> 
> Wrt. installing rpms, it is sometimes a bit tricky.
>   - If you install many rpms and one is bad, it barfs on you.
>     Consequently, you want to install one rpm at a time if possible.
>   - However, to handle cyclic dependencies you _must_ install all the
>     rpms in the cycle simultaneously.
> 
>   A way to solve this is to repeatedly iterate through the list of
>   rpms that should be installed/updated, installing/updating one rpm
>   at a time.  If you have a complete iteration through the list
>   without a successful installation/update, the last rpms might have
>   cyclic dependencies.  The last rpms should therefore be installed in
>   one command.


        Or, parse out the deps from the rpm file, create a list of the rpms
that depend on each other and can then do a single rpm call for them all
like you suggested.


> 
> astor
> 
> --
>  Alexander Kjeldaas, Guardian Networks AS, Trondheim, Norway
>  http://www.guardian.no/
> 
> ---
> You are currently subscribed to linuxconf as: [EMAIL PROTECTED]
> To unsubscribe, forward this message to [EMAIL PROTECTED]

-- 
===========================================================
        James Michael Keller | [EMAIL PROTECTED]
              http://www.radix.net/~jmkeller
-----------------------------------------------------------
Contents (c)1998 James Michael Keller.  All rights reserved
===========================================================

---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]

Reply via email to