On Tue, 2 Jan 2018 22:15:27 -0700, the...@sys-concept.com wrote:
> /usr/lib64/qt5/bin/lrelease res/i18n/x2goclient_de.ts
> make: /usr/lib64/qt5/bin/lrelease: Command not found
> make: *** [Makefile:537: x2goclient_de.qm] Error 127
> * ERROR: net-misc/x2goclient-4.1.0.1-r1::gentoo failed (compile
Today I noticed that x11-terms/terminator is to be deleted from the tree
and I was wondering if someone can recommend a replacement (in the
portage tree)?
The reason I use terminator is it's "multi-session" support. I use it to
open eight ssh connections to eight different hosts and then use t
On Wed, 03 Jan 2018 12:13:45 +0100, Dan Johansson wrote:
> The reason I use terminator is it's "multi-session" support. I use it
> to open eight ssh connections to eight different hosts and then use the
> "Send to all" feature to execute the same command on all hosts (and
> watch the output from
On 2018-01-03 12:46, Neil Bothwick wrote:
On Wed, 03 Jan 2018 12:13:45 +0100, Dan Johansson wrote:
The reason I use terminator is it's "multi-session" support. I use it
to open eight ssh connections to eight different hosts and then use
the
"Send to all" feature to execute the same command on
On 01/03/2018 01:39 AM, Neil Bothwick wrote:
> On Tue, 2 Jan 2018 22:15:27 -0700, the...@sys-concept.com wrote:
>
>> /usr/lib64/qt5/bin/lrelease res/i18n/x2goclient_de.ts
>> make: /usr/lib64/qt5/bin/lrelease: Command not found
>> make: *** [Makefile:537: x2goclient_de.qm] Error 127
>> * ERROR: ne
Hi,
I have the KDE plasma device notifier that shows always 1.2GB of free
space on all USB disks (HDD or flash drives). Such issue does not happen
on internals SATA HDD / SDD. This issue also prevents me to copy files
bigger then 1.2GB to any mounted USB disk using dolphin (but I can copy
the same
Hi all, I'm having a problem with my Kodi system. Unfortunately I don't use
the Kodi system very often (the system also runs as a general server on my
network so most of my work on it is done through ssh) so I don't know
exactly when this happened, but it would have been in the last couple of
month
On Wednesday, 3 January 2018 19:10:45 GMT Manuel McLure wrote:
> Hi all, I'm having a problem with my Kodi system. Unfortunately I don't use
> the Kodi system very often (the system also runs as a general server on my
> network so most of my work on it is done through ssh) so I don't know
> exactly
On 02/01/18 22:58, Adam Carter wrote:
> AMD coder's patch to disable the new code (to avoid the performance hit)
> where he states the issue doesnt exist on AMD processors;
> https://lkml.org/lkml/2017/12/27/2
Read LWN, specifically the links to the people who covered the bug.
It's a flaw in spec
On Wed, Jan 3, 2018 at 3:35 PM, Wols Lists wrote:
>
> And as I understand it the code can be disabled with either a compile
> time option or command line switch to the kernel.
I suspect the compile-time option is PAGE_TABLE_ISOLATION (which was
newly added in 4.14.11). The command line option no
> 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
> outcome is different to w
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 attack
> 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: you should buy a Mac, beca
> 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 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 know there are literally millions
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
>> fea
On Wed, 3 Jan 2018 15:53:07 -0500, Rich Freeman wrote:
> I believe the kernel went with "Page Table Isolation (PTI)" rather
> that KAISER, probably to avoid ethnic issues. Apparently this was
> deemed to have a more acceptable acronym than Forcefully Unmap
> Complete Kernel With Interrupt Trampol
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 eq
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 bangin
> On 3 Jan 2018, at 17:24, Flavio Cappelli wrote:
> …
>
> I tried with three different USB drives and the behavior is the same:
>
> ￜ- 4GB flash drive on USB2 interface, vfat formatted, 3.3GB free
> ￜ- 128GB flash drive on USB3 interface, exfat formatted, 107GB free
> ￜ- 500GB external H
> 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
> most you could have the curr
> 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 kernels are currently
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 cleaned out everything else :-)
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
>>
>> That's not a versi
On Wed, Jan 3, 2018 at 11:42 AM, Mick wrote:
>
>
> Sometime in autumn I had a similar symptom with a (non-gentoo) box running
> kodi here. I had to reprogram the IR remote control handset, but wouldn't
> know how to go about it with yours ...
> --
> Regards,
> Mick
Interesting. After checking
> 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 ever experienced that.
>
>
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 /var/lib/portage/world
> sys-kernel/gentoo-sources:4.9.34
> >
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
>>> future update, but I do
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 foo-1.0-r1
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 explain
> 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 end of ~4.9.34, I don;t quit
> 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 you have =foo-1.0 match
I'm not sure if it's been mentioned here before but there apparently is a
bug affecting all Intel CPUs manufactured in the last 10 years or so, in
which protected kernel memory is leaked to userspace. It can't be patched
in microcode and will lead to some serious overhead to patch in the OS.
See,
On Thu, Jan 4, 2018 at 2:15 PM, P Levine wrote:
> I'm not sure if it's been mentioned here before but there apparently is a
> bug affecting all Intel CPUs manufactured in the last 10 years or so, in
> which protected kernel memory is leaked to userspace. It can't be patched
> in microcode and wi
>
> Project Zero (Google) found it;
> https://googleprojectzero.blogspot.com.au/2018/01/
> reading-privileged-memory-with-side.html
>
> Phoronix has done some benchmarks on the impact of the kernel based
> workaround ([Kernel] Page Table Isolation (PSI) nee Kaiser)
> https://www.phoronix.com/scan.p
New bug resurface.
What is the command to test AMD CUP's if flag: X86_BUG_CPU_INSECURE is
enabled?
From:
https://lkml.org/lkml/2017/12/27/2
--
Joseph
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 active kernel, and
>>> didn't wi
37 matches
Mail list logo
