| 1 |
The wisdom that had been passed on to me to protect things like that |
| 2 |
from being deleted *by portage* is to "touch filename" on the |
| 3 |
appropriate modules in the lib/modules/... directory. Because if its |
| 4 |
been modified, portage is not supposed to remove it. |
| 5 |
|
| 6 |
The other issue that comes up is when compiling the kernel itself, the |
| 7 |
kernel's "make modules_install" and such cleans out all the files in |
| 8 |
/lib/modules/kernel-*/kernel/... This is a nuisance in that you may |
| 9 |
easily forget to re-emerge the outside modules (xfree-drm for example). |
| 10 |
|
| 11 |
It appears though that anything in a non-kernel-made directory like |
| 12 |
/lib/modules/kernel-*/[misc,local] does not get erased when the kernel |
| 13 |
is rebuilt. So you might try copying such modules to a different |
| 14 |
subdirectory of your own choosing. If its not where portage put it, |
| 15 |
portage won't yank it. If its not where the kernel's make cleans out, |
| 16 |
that won't delete it either. Doing that means manual effort (and the |
| 17 |
chance to overlook it) if the module itself gets re-emerged. |
| 18 |
|
| 19 |
Perhaps there could be a way for an ebuild to mark a file as one that is |
| 20 |
allowed to be overwritten but not backed out? That might even be able to |
| 21 |
be done by making portage "forget" the timestamp of a kernel module |
| 22 |
whenever its installed. Since the timestamp wouldn't match what is on |
| 23 |
the disk, it wouldn't delete it, but the next emerge could overwrite |
| 24 |
it... |
| 25 |
|
| 26 |
On Fri, 2004-01-02 at 00:16, Brian wrote: |
| 27 |
> A problem that I (and others) have is portage unmerging kernel drivers |
| 28 |
> from an existing kernel when emerging them to a new kernel. |
| 29 |
> ala |
| 30 |
> |
| 31 |
> emerge nvidia-kernel |
| 32 |
> emerge alsa-driver |
| 33 |
> |
| 34 |
> unmerges the driver from your current kernel before you have a known |
| 35 |
> good new kernel. |
| 36 |
> |
| 37 |
> Is there a current method for doing so that I missed? If not could an |
| 38 |
> additional protected flag be set to prevent unmerging if the kernel |
| 39 |
> version is different than the last emerge of the driver, similar to the |
| 40 |
> slot #? |
| 41 |
> |
| 42 |
> it would make life a lot easier for noobs & non experts to work out |
| 43 |
> kerenel configs without messing up a working kernel. |
| 44 |
-- |
| 45 |
Scott Taylor - <security@××××××××××××××.com> |
| 46 |
|
| 47 |
furbling, v.: |
| 48 |
Having to wander through a maze of ropes at an airport or bank |
| 49 |
even when you are the only person in line. |
| 50 |
-- Rich Hall, "Sniglets" |
| 51 |
|
| 52 |
|
| 53 |
|
| 54 |
|
| 55 |
-- |
| 56 |
gentoo-portage-dev@g.o mailing list |
Archives