On Fri, 2 Sep 2016 02:33:12 +0200, Kai Krakow wrote:
> Am Thu, 1 Sep 2016 22:56:31 +0100
> schrieb Neil Bothwick :
>
> > > - so my next upgrade would "force" me into deciding going way down
> > > (probably a bad idea) or up into unknown territory (and this showed:
> > > can also be a problem). Or
On Thu, 1 Sep 2016 22:08:19 +0200, Kai Krakow wrote:
> > No one forced you to do anything. You 4.6 kernel was still in boot,
> > your 4.6 sources were still installed. The ebuild was only removed
> > fro the portage tree, nothing was uninstalled from your system unless
> > you did it. Even the ebu
On 01/09/2016 22:08, Kai Krakow wrote:
Am Tue, 30 Aug 2016 08:47:22 +0100
schrieb Neil Bothwick :
On Tue, 30 Aug 2016 08:34:55 +0200, Kai Krakow wrote:
Surprise surprise, 4.7 has this (still not fully fixed) oom-killer
bug. When I'm running virtual machines, it still kicks in. I wanted
to sta
On Tue, 30 Aug 2016 08:34:55 +0200, Kai Krakow wrote:
> Surprise surprise, 4.7 has this (still not fully fixed) oom-killer bug.
> When I'm running virtual machines, it still kicks in. I wanted to stay
> on 4.6.x until 4.8 is released, and only then switch to 4.7. Now I was
> forced early (I'm usin
4 matches
Mail list logo
