On 12/04/2016 07:38, Dale wrote:
> Howdy,
>
> Well, I went and did it. On one hand, it's sort of nice. Seems to be
> faster in a way. On the other hand, I want to wring its neck. I used to
> have 10 virtual desktop thingys. I was organized like a OCD King here.
> Well, that seems to have
Howdy,
Well, I went and did it. On one hand, it's sort of nice. Seems to be
faster in a way. On the other hand, I want to wring its neck. I used to
have 10 virtual desktop thingys. I was organized like a OCD King here.
Well, that seems to have left the building. Google informed me that
J. Roeleveld wrote:
> On April 11, 2016 11:04:59 AM GMT+02:00, Dale wrote:
>> Howdy,
>>
>> I did a google search and it had zero results. Long time since I seen
>> that happen. Anyone else run into this? Basically, portage says it is
>> about to clobber some files it
None of this is grub's fault, it's users are just petulant children.
It's bloated but pick a real argument.
On Mon, Apr 11, 2016 at 10:31:42PM -0400, Poison BL. wrote:
> The file 'bootx64.efi' is the default that uefi looks for when booting
> a 'disk' in a quasi-bios-style fallback (if there's not a real 'boot
> this particular thing' like the windows boot manager adds), which also
> makes the
On Mon, Apr 11, 2016 at 8:56 PM, Adam Carter wrote:
>
>> The problem was sys-boot/grub-2.02_beta2-r9, which UEFI never ran.
>>
>> The fix was to get rid of grub altogether and instead use
>> sys-boot/gummiboot.
>> Not only was it fully functional, it was a welcome relief
On 11 Apr 2016 16:16, Gwendal Grignou wrote:
> Sedutil (https://github.com/Drive-Trust-Alliance/sedutil) is a tool to
> enable encryption of TCG Opal capable devices (SATA drives, NVMe SSD).
> Any objections to add it to gentoo?
if you want it in CrOS, that's all you really need ;).
just send
> The problem was sys-boot/grub-2.02_beta2-r9, which UEFI never ran.
>
> The fix was to get rid of grub altogether and instead use
> sys-boot/gummiboot.
> Not only was it fully functional, it was a welcome relief not to have to
> grapple with grub's baroque complexity and to be able to return to
On Monday 11 Apr 2016 22:34:04 Alan McKinnon wrote:
> On 11/04/2016 20:15, Mick wrote:
> > On Monday 11 Apr 2016 13:17:05 J. Roeleveld wrote:
> >> On Monday, April 11, 2016 11:34:03 AM Peter Humphrey wrote:
> >>> On Saturday 09 April 2016 11:12:51 Mick wrote:
> I noticed today that Plasma 5
On 11/04/2016 20:15, Mick wrote:
> On Monday 11 Apr 2016 13:17:05 J. Roeleveld wrote:
>> On Monday, April 11, 2016 11:34:03 AM Peter Humphrey wrote:
>>> On Saturday 09 April 2016 11:12:51 Mick wrote:
I noticed today that Plasma 5 is now stable, which means I will soon
have
to deal
On 11/04/16 13:34, Peter Humphrey wrote:
I saw that too, and it cast a gloom over the rest of my day. I intend to stick
with KDE-4 until some more sensible themes become available in Plasma 5
The KDE 4 themes are still included. (Oxygen and Air.) Breeze is the
default though.
On Monday 11 Apr 2016 13:17:05 J. Roeleveld wrote:
> On Monday, April 11, 2016 11:34:03 AM Peter Humphrey wrote:
> > On Saturday 09 April 2016 11:12:51 Mick wrote:
> > > I noticed today that Plasma 5 is now stable, which means I will soon
> > > have
> > > to deal with it.
> >
> > I saw that too,
11.04.2016 17:09, Alan McKinnon wrote:
On 11/04/2016 15:15, Yuri K. Shatroff wrote:
Hi gentoo users,
Got a strange problem. While emerging kde-plasma/kscreenlocker (as part
of upgrading to the brand new plasma desktop), the build fails with the
following error:
* Applying
On 11/04/2016 15:15, Yuri K. Shatroff wrote:
> Hi gentoo users,
>
> Got a strange problem. While emerging kde-plasma/kscreenlocker (as part
> of upgrading to the brand new plasma desktop), the build fails with the
> following error:
>
> * Applying kscreenlocker-5.4.90-no-SUID-no-GUID.patch ...
>
Hi gentoo users,
Got a strange problem. While emerging kde-plasma/kscreenlocker (as part
of upgrading to the brand new plasma desktop), the build fails with the
following error:
* Applying kscreenlocker-5.4.90-no-SUID-no-GUID.patch ...
On Monday, April 11, 2016 11:34:03 AM Peter Humphrey wrote:
> On Saturday 09 April 2016 11:12:51 Mick wrote:
> > I noticed today that Plasma 5 is now stable, which means I will soon have
> > to deal with it.
>
> I saw that too, and it cast a gloom over the rest of my day. I intend to
> stick with
On Saturday 09 April 2016 11:12:51 Mick wrote:
> I noticed today that Plasma 5 is now stable, which means I will soon have
> to deal with it.
I saw that too, and it cast a gloom over the rest of my day. I intend to stick
with KDE-4 until some more sensible themes become available in Plasma 5, so
On Thursday 7th April 2016 I wrote:
> I have a new box with an NVMe SSD drive attached to the PCI bus via an
> M.2 interface. The drive shows up as /dev/nvme0n1, with partitions
> /dev/nvme0n1p1, /dev/nvme0n1p2, ...
> After following the instructions in the handbook for a UEFI system, I get
>
On April 11, 2016 11:04:59 AM GMT+02:00, Dale wrote:
>Howdy,
>
>I did a google search and it had zero results. Long time since I seen
>that happen. Anyone else run into this? Basically, portage says it is
>about to clobber some files it shouldn't so it puked out all this
Howdy,
I did a google search and it had zero results. Long time since I seen
that happen. Anyone else run into this? Basically, portage says it is
about to clobber some files it shouldn't so it puked out all this
mess.:/
>>> Verifying ebuild manifests
>>> Emerging (1 of 1)
20 matches
Mail list logo