exactly , that would be a great idea , ..... can u give me some help on the working of yum , i am not very well versed with the internals and functioning of YUM ....
thanks
satish.
On 4/1/08, Alastair Neil <ajneil@xxxxxxxxx> wrote:
On Tue, Apr 1, 2008 at 8:11 AM, Satish Eerpini <eerpini@xxxxxxxxx> wrote:
> hi tim ,
> well ya i agree with u ,.... i had this in mind , because once we erase the
> package, the system may become inconsistent , degrading the whole idea
> behind having the rollback functionality . so any further suggestions ?
>
> and ya Fajar, i actually was reluctant to use yum in my first
> implementations of the scripts , but didn't think of a better method given
> my low knowledge, ..... actually using storage and providing backup and
> recovery was a option i already had, .... but my point was to design it to
> be very simple to use and a very 'swift' application ........
>
> Thanks
> -Satish
>
> On Tue, Apr 1, 2008 at 4:57 PM, Tim Lauridsen <tim.lauridsen@xxxxxxxxxxxxxx>
> wrote:
> >
> > Satish Eerpini wrote:
> > > well Fajar, i didnt quite understand your point, how is storage related
> > > to the roll back functionality , ... ?
> > > can u explain a bit , or refer some resources from where i can
> > > understand this ?
> > >
> > > Thanks
> > > Satish
> > >
> >
> > The mayor problem with roleback is that you can't reverse the changes
> > done by scriptlets in RPM, so it is not posible to do downgrade in a
> > safeway.
> >
> > EX.
> >
> > rpm -ivh foo
> > rpm -e foo
> >
> > these commands add a package and remove it again.
> > the state of the system might not be the same before and after these
> > commands, so a safe rollback is not possible.
> >
> > Tim
> >
> >
> >
> >
> > _______________________________________________
> > Yum mailing list
> > Yum@xxxxxxxxxxxxxxxxxxxx
> > https://lists.dulug.duke.edu/mailman/listinfo/yum
> >
>
>
> _______________________________________________
> Yum mailing list
> Yum@xxxxxxxxxxxxxxxxxxxx
> https://lists.dulug.duke.edu/mailman/listinfo/yum
>
>
Perhaps a cogent first step would be to write a yum plugin that does
log exactly the information you need to roll back the system.
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxxxxx
https://lists.dulug.duke.edu/mailman/listinfo/yum
_______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum
