| 1 |
> I am not saying prelink isn't buggy BTW. |
| 2 |
> |
| 3 |
> The -f flag is needed if you have prelinked binaries already on the |
| 4 |
> system, otherwise it will abort, that is another matter..... |
| 5 |
> |
| 6 |
> If you use -f you get around that problem, but you then encounter the |
| 7 |
> other one, you are between a rock and a hard place it seems. |
| 8 |
|
| 9 |
I've found that the only way around the problem seems to be: prelink -ua, |
| 10 |
followed by a reboot and prelink -a. reboot. (with an occasional tendency to |
| 11 |
break things.) |
| 12 |
|
| 13 |
I've been wondering about the impact on portage however. Will portage know to |
| 14 |
unmerge these prelinked binaries still? My guess would be no. |
| 15 |
|
| 16 |
General remark: Prelinking definitely promises to be great but unless your |
| 17 |
willing to deal with some 'early adoption' quirks it isn't for you yet. I've |
| 18 |
broken my system once or twice severely trying to gauge it's state. I would |
| 19 |
say that some challenges remain before it is ready for the masses. |
| 20 |
|
| 21 |
|
| 22 |
-- |
| 23 |
gentoo-dev@g.o mailing list |
Archives