Hi all,
A "dist-upgrade" is in my todo list for some time now. I see it like a
"pre-reboot full upgrade" with merging of conffiles in a temp location.
What do you think of it ?
Regards, Cedric
2006/8/23, KP Kirchdoerfer <[EMAIL PROTECTED]>:
>
> Hi EricS;
>
> Am Mittwoch, 23. August 2006 19:49 schrieb Eric Spakman:
> > Hi Paul,
> >
> > >1: In case of a large upgrade (e.g. a new B-U is released), it would
> be
> > >nice if one could simply scp all the new packages over to the MSDOS
> > >filesystem, and then type "apkg -u -a" to have apkg check *EVERY*
> > >package currently loaded on the system.
> >
> > In that case it's better to just scp all new packages to the MSDOS fs
> > and reboot. This has the same function as an 'apkg -u -a' but clears
> > possible old unused files, reboot all daemons and updates initrd.
>
> But it does not provide the extra checks apkg -u does for configuration
> files
> and the possible changes.
> I see your points, but some users want to be safe while updating and have
> a
> look into every changed config...
>
> I think the "-a" option should have a path option, where to find the
> files.
>
>
>
> > >> - During backup the sha1sums of the files in memory are compared with
> > >> the saved *.sha1 sums, new files are detected and duplicates are
> > >> filtered out. For example: when one package has an etc/ppp directory
> in
> > >> <package>.local and another one an etc/ppp/dsl-providers file
> listed,
> > >> the dsl-provider file would be find twice and also stored twice in
> the
> > >> configdb.
> > >
> > >3: Stored twice in the configdb? Isn't this a bug?
> >
> > Nope, see the sentence above the example: "duplicates are filtered out.
> > "
>
> Well, looks like a native english speaker should clean this paragraph.
>
>
> > >> Changed files are saved in "configdb".lrp with a "full" backup, this
> is
> > >> dynamic so installing (or removing) a package will also be taken into
> > >> account.
> > >
> > >What does a "non-full" backup do now? Or is that option gone?
> >
> > That option is gone, the configdb is more or less a "non-full" backup.
> > With full backup in this context is meant: when you press save, the
> > configdb is recreated from scratch ("full"), removing old stale files.
>
> That's a "full" backup of the configuration.
> Backing up individual packages won't work any more.
>
> But I agree, it's similar to the old partial backup - where only the
> configuration files are saved instead of the whole package.
>
> So speaking about packages - yes, it's a partial backup of the
> files/directories named in <package>.local, speaking about a box - it's
> full
> backup of every changed configuration file/directory.
>
> kp
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> ------------------------------------------------------------------------
> leaf-user mailing list: [email protected]
> https://lists.sourceforge.net/lists/listinfo/leaf-user
> Support Request -- http://leaf-project.org/
>
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
