| 1 |
Am 07.01.2015 um 14:44 schrieb Alan McKinnon: |
| 2 |
> On 07/01/2015 15:19, Stefan G. Weichinger wrote: |
| 3 |
>> Seems as if the biggest problems are solved right now? |
| 4 |
> |
| 5 |
> |
| 6 |
> if you ran "emerge -avuND world" and portage goes ahead and does it |
| 7 |
> without blockers, then I'd agree - the major problems are solved. |
| 8 |
> |
| 9 |
> It's a simple samba server, so not too many packages. I'd recommend you |
| 10 |
> do "emerge -e world" when done just to ensure that everything is |
| 11 |
> consistently built against the same toolchain and glibc. It's not |
| 12 |
> absolutely required, but it does give peace of mind and you can let it |
| 13 |
> run and do it's thing while you get on with something else |
| 14 |
|
| 15 |
I try "emerge -avuDN @system" for now ... this includes glibc etc and |
| 16 |
should result in a quite bootable system. |
| 17 |
|
| 18 |
The openssl-upgrade lead to some @preserved-rebuild issues ... but I |
| 19 |
have to clean up @world first. This box was based on another |
| 20 |
installation back then and has the whole LAMP stack installed which |
| 21 |
isn't used at all. If I get rid of this the whole setup and upgrade gets |
| 22 |
much much simplified. |
| 23 |
|
| 24 |
Maybe I can talk my colleague into an earlier reboot-test ... if that |
| 25 |
works we are running on a current kernel/udev/openrc ... that would be |
| 26 |
great to know. |
| 27 |
|
| 28 |
glibc-2.19-r1 emerged as well now. |
| 29 |
|
| 30 |
- |
| 31 |
|
| 32 |
But you are still right: |
| 33 |
|
| 34 |
If I had backed up /etc and copied some of my images in there I would |
| 35 |
also be up and running already. |
| 36 |
|
| 37 |
Next time! |
| 38 |
|
| 39 |
;-) |
| 40 |
|
| 41 |
S |
Archives