On Fri, 5 Jan 2018 20:51:58 +
Jorge Almeida wrote:
> I just found out about stow. It just seems too good to be true. So:
> did I misunderstood something? Any gotchas that are not obvious?
Jorge,
I haven't used stow myself so I can't comment on how well it works.
I
On Fri, 5 Jan 2018 17:26:13 +
Ken Moffat wrote:
> Does anybody have a link for (any) updated AMD firmware? Ryzen is
> model 17h, AFAICS linux firmware has nothing for that, and the
> firmware for earlier models has not been updated in a long time.
I also sure
On Fri, Jan 05, 2018 at 02:28:04PM -0800, Paul Rogers wrote:
> I have been searching and reading intently for the past day also. I am
> disappointed by the rush to republish and dearth of solid data beyond the
> Proof of Concept.
>
Yes, it's hard finding accurate information - the whole thing
On Fri, Jan 05, 2018 at 10:09:57PM +, Ken Moffat wrote:
>
> But that is just a 'data' file and I had no idea how to use it.
> Fortunately, gentoo also use iucode_tool and their wiki shows:
>
> iucode_tool -S --write-earlyfw=/boot/early_ucode.cpio
> /lib/firmware/intel-ucode/*
>
> I'm
I have been searching and reading intently for the past day also. I am
disappointed by the rush to republish and dearth of solid data beyond the Proof
of Concept.
Apparently in theory Spectre haunts all processors back to the Pentium Pro.
There is very little solid evidence of what steppings
A poster on lkml mentioned that debian have new intel firmware.
The package is intel-microcode_3.20171215.1.tar.xz from
https://packages.debian.org/sid/intel-microcode : reading this, it
includes old firmware releases from intel which are no longer on its
site (e.g. for very old machines, but
The LFS book in "Symlink Style Package Management" (6.3.2.3) mentions that
make DESTDIR=/usr/pkg/libfoo/1.1 install
would work, except that not all packages come with a Makefile
supporting DESTDIR.
However, with GNU stow we can do something like
make install prefix=/path/to/stow/foo
and then
stow
Resent without "SPAM" in subject, sorry...
On 05/01/2018 20:24, Pierre Labastie wrote:
> On 05/01/2018 18:31, Ken Moffat wrote:
>> On Fri, Jan 05, 2018 at 11:24:45AM -0500, Baho Utot wrote:
>>> Building my first LFS-8.1, I am leaving FreeBSD ( Don't like the direction
>>> they are going in ) and
On Fri, Jan 05, 2018 at 04:30:15PM +, Hazel Russman wrote:
>
> I have just built a 4.14.11 kernel with PTI and I can't boot it. I get a
> string of acpi errors and then a panic. As far as I can see, it's the same
> problem as https://bugzilla.redhat.com/show_bug.cgi?id=1520265. That was
>
On Fri, Jan 05, 2018 at 02:58:57AM -0500, Michael Shell wrote:
>
> Most interesting, but also scary. Here's my own summary take on the info
> which I found at:
>
[ snipping - people can, and should, follow the links in your original
post, but I've got a question on one item ]
>
> There is,
Hazel Russman wrote:
I have just built a 4.14.11 kernel with PTI and I can't boot it. I get
a string of acpi errors and then a panic. As far as I can see, it's the
same problem as https://bugzilla.redhat.com/show_bug.cgi?id=1520265.
That was cured by a bios update but I wouldn't date to do a
On Thu, 4 Jan 2018 22:13:16 +
Ken Moffat wrote:
> On Thu, Jan 04, 2018 at 08:16:18PM +, Ken Moffat wrote:
> > People who follow the news will be aware that big changes have been
> > rushed into the linux kernel (and changes are/have been also rolled
> > out by
Building my first LFS-8.1, I am leaving FreeBSD ( Don't like the
direction they are going in ) and returning to LFS and picking back up
from LFS-7.5. The onlyist departure from the book is to script the
build. I am building in a VirtualBox session running LFS-7.5 as host.
Following the
On Thu, 4 Jan 2018 20:16:18 +
Ken Moffat wrote:
> There are two vulnerabilities, with the shiny names of Meltdown and
> Spectre. Both refer to ways of userspace finding where the kernel
> has been mapped, to try to do harm. Page Table Isolation addresses
> the first
14 matches
Mail list logo