On Sat, 10 Jul 2021 11:22:38 +0300, Nikos Chantziaras wrote:
> Right. However, it's obvious I've hit a portage inconsistency here. For
> example, when I use:
>
>CONFIG_PROTECT="blah"
>
> in make.conf, "blah" is appended to CONFIG_PROTECT. But for whatever
> reason, this is not the case
On 08/07/2021 02:09, Nikos Chantziaras wrote:
So I just noticed that when I run:
emerge @module-rebuild
after having installed a kernel update, the kernel modules of the
previous kernel version are being deleted. I am sure this didn't use to
be the case.
Found the issue. On my new system, I
On Thu, 8 Jul 2021 02:46:32 +0300, Nikos Chantziaras wrote:
> > Hasn't this always been the case. emerging a package removes files
> > installed by the previous merge.
> >
> > I think adding /lib/modules to CONFIG_PROTECT will prevent their
> > deletion.
>
> I just tried that after "eselect
Nikos Chantziaras wrote:
> On 08/07/2021 02:18, Neil Bothwick wrote:
>> On Thu, 8 Jul 2021 02:09:17 +0300, Nikos Chantziaras wrote:
>>
>>> So far, so good. But when I ran "emerge @module-rebuild", which
>>> rebuilds these two packages:
>>>
>>> app-emulation/vmware-modules
>>>
On 08/07/2021 02:18, Neil Bothwick wrote:
On Thu, 8 Jul 2021 02:09:17 +0300, Nikos Chantziaras wrote:
So far, so good. But when I ran "emerge @module-rebuild", which
rebuilds these two packages:
app-emulation/vmware-modules
x11-drivers/nvidia-drivers
The vmwware and nvidia kernel
5 matches
Mail list logo
