1 |
On 02/03/2018 04:11:33 PM, Marc Joliet wrote: |
2 |
> Am Samstag, 3. Februar 2018, 10:50:53 CET schrieb Helmut Jarausch: |
3 |
> > On 02/03/2018 06:54:06 AM, Dale wrote: |
4 |
> > > While on this topic, I have a question about glibc. I have it |
5 |
> set in |
6 |
> > > make.conf to save the binary packages. Generally I use it when I |
7 |
> need |
8 |
> > > to go back shortly after a upgrade, usually Firefox or something. |
9 |
> > > However, this package is different since going back a version |
10 |
> isn't a |
11 |
> > > good idea. My question tho, what if one does go back a version |
12 |
> using |
13 |
> > > those saved binary packages? Has anyone ever did it and it work |
14 |
> or |
15 |
> > > did |
16 |
> > > it and it fail miserably? |
17 |
> > |
18 |
> > I've tried to binary emerge my previous version. This didn't succeed |
19 |
> > since |
20 |
> > the ebuild disallows downgrading glibc. |
21 |
> > |
22 |
> > Luckily I had backuped my system just 20 hours ago. |
23 |
> |
24 |
> Having up-to-date backups is always good :) . |
25 |
> |
26 |
> > Does anybody know how to restore ONLY those files which are |
27 |
> > more recent on the target file system. |
28 |
> > (My whole back is 124 Gb large which is a lot to copy back) |
29 |
> |
30 |
> If you can access the backups like a normal file system, then using |
31 |
> rsync with |
32 |
> the --update option looks to me like what you want: |
33 |
> |
34 |
> "-u, --update skip files that are newer on the |
35 |
> receiver". |
36 |
> |
37 |
|
38 |
High Marc, |
39 |
I think I need the opposite : |
40 |
only update files which are newer on the receiver |
41 |
|
42 |
Thanks, |
43 |
Helmut |