public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Scott Taylor <security@303underground.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] multiple kernel driver emerges
Date: Fri, 02 Jan 2004 00:31:46 -0700	[thread overview]
Message-ID: <1073028705.11194.66.camel@Star.BerthoudWireless.net> (raw)
In-Reply-To: <1073027790.3678.24.camel@big_squirt.dol-sen.ca>

The wisdom that had been passed on to me to protect things like that
from being deleted *by portage* is to "touch filename" on the
appropriate modules in the lib/modules/... directory. Because if its
been modified, portage is not supposed to remove it.

The other issue that comes up is when compiling the kernel itself, the
kernel's "make modules_install" and such cleans out all the files in
/lib/modules/kernel-*/kernel/... This is a nuisance in that you may
easily forget to re-emerge the outside modules (xfree-drm for example).

It appears though that anything in a non-kernel-made directory like
/lib/modules/kernel-*/[misc,local] does not get erased when the kernel
is rebuilt. So you might try copying such modules to a different
subdirectory of your own choosing. If its not where portage put it,
portage won't yank it. If its not where the kernel's make cleans out,
that won't delete it either. Doing that means manual effort (and the
chance to overlook it) if the module itself gets re-emerged.

Perhaps there could be a way for an ebuild to mark a file as one that is
allowed to be overwritten but not backed out? That might even be able to
be done by making portage "forget" the timestamp of a kernel module
whenever its installed. Since the timestamp wouldn't match what is on
the disk, it wouldn't delete it, but the next emerge could overwrite
it...

On Fri, 2004-01-02 at 00:16, Brian wrote:
> A problem that I (and others) have is portage unmerging kernel drivers
> from an existing kernel when emerging them to a new kernel.
> ala
> 
> emerge nvidia-kernel
> emerge alsa-driver
> 
> unmerges the driver from your current kernel before you have a known
> good new kernel.
> 
> Is there a current method for doing so that I missed?  If not could an
> additional protected flag be set to prevent unmerging if the kernel
> version is different than the last emerge of the driver, similar to the
> slot #?
> 
> it would make life a lot easier for noobs & non experts to work out
> kerenel configs without messing up a working kernel.
--
Scott Taylor - <security@303underground.com> 

furbling, v.:
	Having to wander through a maze of ropes at an airport or bank
	even when you are the only person in line.
		-- Rich Hall, "Sniglets"

    


--
gentoo-portage-dev@gentoo.org mailing list


  reply	other threads:[~2004-01-02  7:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02  7:16 [gentoo-portage-dev] multiple kernel driver emerges Brian
2004-01-02  7:31 ` Scott Taylor [this message]
2004-01-02 10:23   ` [gentoo-portage-dev] kernel drivers vs. portage Drake Wyrm
2004-01-04 12:50     ` Drake Wyrm
2004-01-04 15:17       ` Marius Mauch
2004-01-04 17:30         ` Paul Varner
2004-01-06  6:41           ` Brian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1073028705.11194.66.camel@Star.BerthoudWireless.net \
    --to=security@303underground.com \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox