| 1 |
Not so long ago I was mrpropered my /home. You situation is much |
| 2 |
harder but... There is exist utility sys-fs/extundelete and if you |
| 3 |
have ~500-600mb of unparted |
| 4 |
disk space(and of course your /<removed usr> is ext fs), you can |
| 5 |
create new /usr there, unpack stage3's /usr to /<newusr>, chroot, |
| 6 |
emerge extundelete, and try to restore all your data. But for my |
| 7 |
experience it restored ~20-30%, may be you'll be more lucky. |
| 8 |
|
| 9 |
2014-08-25 18:45 GMT+03:00 hasufell <hasufell@g.o>: |
| 10 |
> behrouz khosravi: |
| 11 |
>> On Mon, Aug 25, 2014 at 3:57 AM, Volker Armin Hemmann |
| 12 |
>> <volkerarmin@××××××××××.com> wrote: |
| 13 |
>> |
| 14 |
>>> and now you know why you should have added --buildpkg to your default |
| 15 |
>>> emerge options. |
| 16 |
>> |
| 17 |
>> Yeah, I am happy that I did it. I really don't like to compile |
| 18 |
>> chromium or libreoffice again! |
| 19 |
>> |
| 20 |
> |
| 21 |
> Those methods are all not safe if you happen to randomly delete system |
| 22 |
> folders by accident. |
| 23 |
> |
| 24 |
> The only relatively safe methods are rsync to a remote (or similar) or |
| 25 |
> file system level backups like zfs has. |
| 26 |
> |
| 27 |
|
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Regards, |
| 32 |
Nikita |
Archives