1 |
On 25 August 2014 12:19:02 CEST, Bill Kenworthy <billk@×××××××××.au> wrote: |
2 |
>On 25/08/14 17:19, Alan McKinnon wrote: |
3 |
>> On 25/08/2014 11:11, Dale wrote: |
4 |
>>> Alan McKinnon wrote: |
5 |
>>>> On 25/08/2014 08:17, Hinnerk van Bruinehsen wrote: |
6 |
>>>>> On Sun, Aug 24, 2014 at 11:58:36PM +0430, behrouz khosravi wrote: |
7 |
>>>>>> Hi. I just accidentally removed the /usr folder! |
8 |
>>>>>> And I am sure the /usr/bin and several other folders are gone! |
9 |
>>>>>> Should I go for a complete re-install or there is any other |
10 |
>solution? |
11 |
>>>>>> Thanks and I hope that I wont find that blade that I am looking |
12 |
>for! |
13 |
>>>>> You should be able to get away with an emerge @system @world -evDN |
14 |
>instead of |
15 |
>>>>> a complete re-install. |
16 |
>>>>> You should first get a copy of a minimal working /usr though (like |
17 |
>from |
18 |
>>>>> a stage3 tarball), otherwise you will run into errors as /usr/bin |
19 |
>is where |
20 |
>>>>> python and other stuff resides that you'll need for installation. |
21 |
>>>> |
22 |
>>>> gcc is also in /usr which happily guarantees that nothing can be |
23 |
>fixed |
24 |
>>>> without unpacking a stage first |
25 |
>>>> |
26 |
>>>> |
27 |
>>> |
28 |
>>> |
29 |
>>> It seems moving so much critical stuff to /usr was a really bright |
30 |
>>> move. < lots of sarcasm there > |
31 |
>> |
32 |
>> and, |
33 |
>> |
34 |
>> rm -rf /usr is not a user error one can reasonably expect to recover |
35 |
>from |
36 |
>> |
37 |
>> |
38 |
>and wasnt many of the file system changes being made because some folks |
39 |
>wanted a read only /usr but were not there yet? |
40 |
> |
41 |
>BillK |
42 |
|
43 |
Actually. Not being allowed to have /usr on a seperate filesystem as was the case for a very long time made mounting /usr read only near impossible. |
44 |
|
45 |
-- |
46 |
Joost |
47 |
-- |
48 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |