On Saturday, July 3, 2021 1:54:13 AM CEST Dale wrote:
> Daniel Frey wrote:
> > On 6/30/21 11:59 PM, Dale wrote:
> >> Howdy,
> >>
> >> The subject line pretty much describes this. How does one manage the
> >> system.map file in /boot? Is it needed? Should it be updated with each
> >> kernel? I
Daniel Frey wrote:
> On 6/30/21 11:59 PM, Dale wrote:
>> Howdy,
>>
>> The subject line pretty much describes this. How does one manage the
>> system.map file in /boot? Is it needed? Should it be updated with each
>> kernel? I tend to keep 2 to 3 kernels installed. I tend to keep 2 that
>> I
On 6/30/21 11:59 PM, Dale wrote:
Howdy,
The subject line pretty much describes this. How does one manage the
system.map file in /boot? Is it needed? Should it be updated with each
kernel? I tend to keep 2 to 3 kernels installed. I tend to keep 2 that
I know are stable and one testing.
On 01/07/2021 15:41, Dale wrote:
I do copy mine manually. It's how it was done when I first started
using Gentoo and I just stuck with it, it works. It's just one
additional file.
I copied my kernels manually to start with. Then I discovered "make
install". (and "make modules_install").
Neil,
On Thursday, 2021-07-01 15:28:51 +0100, you wrote:
> On Thu, 1 Jul 2021 13:16:29 +0200, Dr Rainer Woitok wrote:
>
> > Same here. And whenever I configure a new kernel my kernel managing
> > script makes sure both, the kernel I'm currenty running on and the one
> > just configured
On Thu, 1 Jul 2021 09:41:27 -0500, Dale wrote:
> > grub-mkconfig only reads the files, it is the make install step of
> > kernel installation that takes care of copying the files to /boot
> > with the correct version numbers. ISTR Dale prefers to copy the
> > kernel files manually, which is why
Neil Bothwick wrote:
> On Thu, 1 Jul 2021 13:16:29 +0200, Dr Rainer Woitok wrote:
>
>> Same here. And whenever I configure a new kernel my kernel managing
>> script makes sure both, the kernel I'm currenty running on and the one
>> just configured are in "@world". That way "emerge
On Thu, 1 Jul 2021 13:16:29 +0200, Dr Rainer Woitok wrote:
> Same here. And whenever I configure a new kernel my kernel managing
> script makes sure both, the kernel I'm currenty running on and the one
> just configured are in "@world". That way "emerge --depclean" will nev-
> er remove a
tastytea wrote:
> On 2021-07-01 13:16+0200 Dr Rainer Woitok
> wrote:
>
>> Dale,
>>
>> On Thursday, 2021-07-01 01:59:57 -0500, you wrote:
>>
>>> ...
>>> Should I version the
>>> system.map file the same as kernels?
>> Not sure about that. Mine ARE
On 2021-07-01 13:16+0200 Dr Rainer Woitok
wrote:
> Dale,
>
> On Thursday, 2021-07-01 01:59:57 -0500, you wrote:
>
> > ...
> > Should I version the
> > system.map file the same as kernels?
>
> Not sure about that. Mine ARE versioned. That's
Dale,
On Thursday, 2021-07-01 01:59:57 -0500, you wrote:
> ...
>
> The subject line pretty much describes this. How does one manage the
> system.map file in /boot? Is it needed? Should it be updated with each
> kernel? I tend to keep 2 to 3 kernels installed.
Same here. And whenever I
There is a lot online - basically its optional and needed just in case
(!) and should be versioned like its matching kernel and initrd.
BillK
one of many refs:
https://stackoverflow.com/questions/28936630/what-is-the-need-of-having-both-system-map-file-and-proc-kallsyms
On 1/7/21 2:59 pm, Dale
12 matches
Mail list logo
