On 04/01/2018 08:40, Wols Lists wrote:
> On 03/01/18 22:09, Alan McKinnon wrote:
>> On 04/01/2018 00:02, Stroller wrote:
>>>
On 3 Jan 2018, at 21:55, Wols Lists wrote:
What would be nice, would be if "emerge --depclean" had the smarts to
recognise
On 03/01/18 22:09, Alan McKinnon wrote:
> On 04/01/2018 00:02, Stroller wrote:
>>
>>> On 3 Jan 2018, at 21:55, Wols Lists wrote:
>>>
>>> What would be nice, would be if "emerge --depclean" had the smarts to
>>> recognise that /usr/src/linux pointed to the current
> On 3 Jan 2018, at 23:41, Neil Bothwick wrote:
>
> On Wed, 3 Jan 2018 22:07:22 +, Stroller wrote:
>
>>> If you do want to use versions, I'd recommend using ~ rather than = to
>>> pick up patch-level updates.
>>
>> What do you mean by this exactly, please?
>
> If
> On 3 Jan 2018, at 22:47, Alan McKinnon wrote:
>
What do you mean by this exactly, please?
>>>
>>> =4.9.34 selects that exact version and only that specific version
>>> ~4.9.34 select that version and also 4.9.34-r1. There might need to be a
>>> * on the
On Wed, 3 Jan 2018 22:02:37 +, Stroller wrote:
> You've jogged a long-hibernating memory - the accidental removal of the
> current sources tree in an accident like this may be the exact reason
> why I refuse to allow kernel versions to be actively emerged.
It's not a big deal, as Alan
On Wed, 3 Jan 2018 22:07:22 +, Stroller wrote:
> > If you do want to use versions, I'd recommend using ~ rather than = to
> > pick up patch-level updates.
>
> What do you mean by this exactly, please?
If you have =foo-1.0 matches only foo-1.0, if a patched version is
released as
On 04/01/2018 00:41, Stroller wrote:
>
>> On 3 Jan 2018, at 22:11, Alan McKinnon wrote:
>>
>
> $ grep -e source /var/lib/portage/world
> sys-kernel/gentoo-sources:4.9.34
...
>>>
>>> I guess this risks that emerge will try to install 4.9.34-r1 during a
I found this helpful in managing kernel versions
https://www.youtube.com/watch?v=UwvV2wf-Gk0
On Wed, Jan 3, 2018 at 3:41 PM, Stroller
wrote:
>
> > On 3 Jan 2018, at 22:11, Alan McKinnon wrote:
> >
>
> $ grep -e source
> On 3 Jan 2018, at 22:11, Alan McKinnon wrote:
>
$ grep -e source /var/lib/portage/world
sys-kernel/gentoo-sources:4.9.34
>>> ...
>>
>> I guess this risks that emerge will try to install 4.9.34-r1 during a future
>> update, but I don't believe I've
On 04/01/2018 00:07, Stroller wrote:
>
>> On 3 Jan 2018, at 21:53, Neil Bothwick wrote:
>>>
>>> It installs exactly that version, and that exact version is recorded in
>>> the world file.
>>>
>>> $ grep -e source /var/lib/portage/world
>>> sys-kernel/gentoo-sources:4.9.34
>>
On 04/01/2018 00:02, Stroller wrote:
>
>> On 3 Jan 2018, at 21:55, Wols Lists wrote:
>>
>> What would be nice, would be if "emerge --depclean" had the smarts to
>> recognise that /usr/src/linux pointed to the current active kernel, and
>> didn't wipe that when it
> On 3 Jan 2018, at 21:53, Neil Bothwick wrote:
>>
>> It installs exactly that version, and that exact version is recorded in
>> the world file.
>>
>> $ grep -e source /var/lib/portage/world
>> sys-kernel/gentoo-sources:4.9.34
>
> That's not a version, it's a slot. Whilst
> On 3 Jan 2018, at 21:55, Wols Lists wrote:
>
> What would be nice, would be if "emerge --depclean" had the smarts to
> recognise that /usr/src/linux pointed to the current active kernel, and
> didn't wipe that when it cleaned out everything else :-) That way, at
>
On 03/01/18 21:39, Stroller wrote:
>> What this completely misses, is that gentoo-sources merely DOWNLOADS THE
>> > LATEST KERNEL SOURCE. So updating gentoo-sources every time does nothing
>> > to change the kernel you are running.
> I don't know why you think I missed that.
Because you're
On Wed, 3 Jan 2018 21:21:30 +, Stroller wrote:
> >> This pins your kernel version at 4.14.8-r1 and you can update when,
> >> in future, you decide it's time to update your kernel, without being
> >> nagged about it every time a new version is release or you emerge
> >> world.
> >
> > The
Wols Lists wrote:
> On 03/01/18 21:21, Stroller wrote:
>> Meanwhile, I've seen security vulnerabilities go unfixed for literally weeks
>> in the bug tracker, so I don't see the significance of a vulnerability an
>> attacker is unlikely to be able to reach. The sites I visit do not make me
>>
On Wed, Jan 3, 2018 at 4:21 PM, Stroller wrote:
>
> If the kernel devs cared to announce when they were patching exploits then we
> could take each
> one under consideration individually. But the kernel devs are secretive about
> kernel exploits, because
> they
> On 3 Jan 2018, at 21:31, Wols Lists wrote:
>
> And heaven help you if you think emerging a specific version of
> gentoo-sources will update the kernel you're running. Because Linux
> certainly won't.
Heaven help me?
Could you possibly clarify, please?
Stroller.
> On 2 Jan 2018, at 19:47, Wols Lists wrote:
>
> You should also check the CVEs every time there's a new kernel!
Who the heck's got time for that? Really?
I have a life, mate. And that means I have better things to do with my time.
Translation of what you just said:
On 03/01/18 21:21, Stroller wrote:
> Meanwhile, I've seen security vulnerabilities go unfixed for literally weeks
> in the bug tracker, so I don't see the significance of a vulnerability an
> attacker is unlikely to be able to reach. The sites I visit do not make me
> fear my kernel being
> On 2 Jan 2018, at 20:20, Kai Krakow wrote:
>
>
>> Now `emerge -n =sys-kernel/gentoo-sources-4.14.8-r1` - "This option can
>> be used to update the world file without rebuilding the packages."
>
> I don't think this is how it works. While technically correct, the
>
On 02/01/18 19:26, Stroller wrote:
>
>> On 2 Jan 2018, at 11:54, Kruglov Sergey wrote:
>>
>> Now I have gentoo-sources-4.14.8-r1 installed.
>> After "emerge --ask --update --deep --with-bdeps=y --newuse @world" command
>> emerge installs old kernel in NS (after first
On Tue, 2 Jan 2018 11:54:50 +, Kruglov Sergey wrote:
> Now I have gentoo-sources-4.14.8-r1 installed.
>
> After "emerge --ask --update --deep --with-bdeps=y --newuse @world"
> command emerge installs old kernel in NS (after first update 4.12.12,
> after second update 4.9.49-r1). How can I
> On 2 Jan 2018, at 11:54, Kruglov Sergey wrote:
>
> Now I have gentoo-sources-4.14.8-r1 installed.
> After "emerge --ask --update --deep --with-bdeps=y --newuse @world" command
> emerge installs old kernel in NS (after first update 4.12.12, after second
> update
On Tuesday, 2 January 2018 12:03:24 GMT Alexander Kapshuk wrote:
> On Tue, Jan 2, 2018 at 1:54 PM, Kruglov Sergey wrote:
> > Hello, All!
> >
> >
> > Now I have gentoo-sources-4.14.8-r1 installed.
> >
> > After "emerge --ask --update --deep --with-bdeps=y --newuse
On Tue, Jan 2, 2018 at 1:54 PM, Kruglov Sergey wrote:
> Hello, All!
>
>
> Now I have gentoo-sources-4.14.8-r1 installed.
>
> After "emerge --ask --update --deep --with-bdeps=y --newuse @world" command
> emerge installs old kernel in NS (after first update 4.12.12, after
Hello, All!
Now I have gentoo-sources-4.14.8-r1 installed.
After "emerge --ask --update --deep --with-bdeps=y --newuse @world" command
emerge installs old kernel in NS (after first update 4.12.12, after second
update 4.9.49-r1).
How can I fix it?
There is sys-kernel/gentoo-sources in my
27 matches
Mail list logo