On Sat, Jun 02, 2012 at 07:36:51PM -0400, Michael Mol wrote
> The BIOS will only load a signed bootloader. The signed bootloader
> will only load a signed kernel.
OK, so I sign LILO. What code is in there that prevents LILO from
loading whatever kernel I've compiled?
> The signed kernel will.
I have been fighting with this for at least three weeks now. Most of
the conflicting packages are qt-based, between 4.8.1 (which I want) and
4.7.4 (which I don't want). I have rebuilt every package I can find
again 4.8.1, but emerge still wants to install 4.7.4, despite the fact
that I've altere
On Sun, Jun 3, 2012 at 12:08 AM, Dmitry Goncharov
wrote:
> On Sat, Jun 02, 2012 at 11:56:01PM -0400, Michael Mol wrote:
>> On Sat, Jun 2, 2012 at 11:34 PM, Dmitry Goncharov
>> wrote:
>> > On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote:
>> >> On Sat, Apr 28, 2012 at 11:07 AM, Michael
On Sat, Jun 02, 2012 at 11:56:01PM -0400, Michael Mol wrote:
> On Sat, Jun 2, 2012 at 11:34 PM, Dmitry Goncharov
> wrote:
> > On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote:
> >> On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol wrote:
> >> Wow. Just wow. This is incredible.
> >>
> >> Th
On Sat, Jun 2, 2012 at 11:34 PM, Dmitry Goncharov
wrote:
> On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote:
>> On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol wrote:
>> Wow. Just wow. This is incredible.
>>
>> This is repeatable for me.
>>
>
>> * The problem occurred while executing t
On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote:
> On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol wrote:
> Wow. Just wow. This is incredible.
>
> This is repeatable for me.
>
> * The problem occurred while executing the ebuild file named
> * 'glibc-2.14.1-r3.ebuild' located in the
On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol wrote:
> Kaylee has 10GB of RAM...if that's not enough, I'll be disabling graphite.
> (Though I haven't explicitly enabled it, either.)
>
> But, no I'm not sure, and can't check until Sunday eveningish. Currently at
> Penguicon.
Wow. Just wow. This is
On Sat, Jun 2, 2012 at 10:04 PM, BRM wrote:
>> From: Michael Mol
>
[snip]
>
> In theory that's how key signing systems are suppose to work.
> In practice, they rarely implement the blacklists as they are (i) hard to
> maintain,
> and (ii) hard to distribute in an effective manner.
Indeed. Whi
> From: Michael Mol
> On Sat, Jun 2, 2012 at 8:35 PM, Florian Philipp
> wrote:
>> Am 03.06.2012 01:36, schrieb Michael Mol:
>>> On Sat, Jun 2, 2012 at 6:50 PM, pk wrote:
On 2012-06-02 22:10, Michael Mol wrote:
>>>
>>> [snip]
>>>
>> [...]
>>>
>>> The BIOS will only load a signed b
On Sat, Jun 2, 2012 at 8:35 PM, Florian Philipp wrote:
> Am 03.06.2012 01:36, schrieb Michael Mol:
>> On Sat, Jun 2, 2012 at 6:50 PM, pk wrote:
>>> On 2012-06-02 22:10, Michael Mol wrote:
>>
>> [snip]
>>
> [...]
>>
>> The BIOS will only load a signed bootloader. The signed bootloader
>> will only
Am 03.06.2012 01:36, schrieb Michael Mol:
> On Sat, Jun 2, 2012 at 6:50 PM, pk wrote:
>> On 2012-06-02 22:10, Michael Mol wrote:
>
> [snip]
>
[...]
>
> The BIOS will only load a signed bootloader. The signed bootloader
> will only load a signed kernel. The signed kernel will...do whatever
> you
On Sat, 02 Jun 2012 14:08:39 +0800
Andrew Lowe wrote:
> Hi all,
> I've just kicked off an "emerge -NuD world" and will now head
> out for a while. My emerge has to do, amongst others, gcc,
> libreoffice, Firefox & Thunderbird. Now when I get back I'll want to
> know where the emerge is up to
On Sat, Jun 2, 2012 at 6:50 PM, pk wrote:
> On 2012-06-02 22:10, Michael Mol wrote:
[snip]
>> It's also probable that the OS kernel can tell the UEFI BIOS about new
>> keys to blacklist. I expect that'll be a recurring thing in the
>> Monthly batch of security updates Microsoft puts out. (Makes
resync
On 2012-06-02 22:10, Michael Mol wrote:
> I expect the chief mechanism is at the manufacturer's end; blacklisted
> keys get included on shipment.
Makes sense.
> It's also probable that the OS kernel can tell the UEFI BIOS about new
> keys to blacklist. I expect that'll be a recurring thing in th
c2stable ~ # emerge -fDuN @world
Calculating dependencies \ * ERROR: sys-devel/gcc-4.5.3-r2 failed
(depend phase):
* EXPORT_FUNCTIONS: toolchain_pkg_prerm is not defined
*
* Call stack:
* ebuild.sh, line 541: Called source
'/usr/portage/sys-devel/gcc/gcc-4.5.3-r2.ebuild'
* gcc
On Sat, Jun 2, 2012 at 3:51 PM, pk wrote:
> On 2012-06-02 15:12, Florian Philipp wrote:
>
>> According to [1] it is SHA-256 and RSA-2048. If I understand it
>> correctly, there are means to blacklist compromised keys. That's
>> why
>
> Just curious, how is a "compromised" key supposed to be blackl
On 2012-06-02 15:12, Florian Philipp wrote:
> According to [1] it is SHA-256 and RSA-2048. If I understand it
> correctly, there are means to blacklist compromised keys. That's
> why
Just curious, how is a "compromised" key supposed to be blacklisted?
Does the bios contact Microsoft, or is it th
On Fri, Jun 1, 2012 at 9:47 PM, Walter Dnes wrote:
> On Fri, Jun 01, 2012 at 04:17:32PM +, James wrote
>> Hello,
>>
>> Ok, so it is hurricane season here in Florida.
>> So, I'm looking for a kde4 centric weather tool
>> that show radar, forecasts and such. Full screen
>> would be keen.
>
> Th
Am 02.06.2012 15:00, schrieb Michael Mol:
> On Sat, Jun 2, 2012 at 3:43 AM, Florian Philipp wrote:
>> Am 02.06.2012 04:26, schrieb William Kenworthy:
>>> http://boingboing.net/2012/05/31/lockdown-freeopen-os-maker-p.html
>>>
>>> and something I had not considered with the whole idea was even boota
On Sat, Jun 2, 2012 at 3:43 AM, Florian Philipp wrote:
> Am 02.06.2012 04:26, schrieb William Kenworthy:
>> http://boingboing.net/2012/05/31/lockdown-freeopen-os-maker-p.html
>>
>> and something I had not considered with the whole idea was even bootable
>> cd's and usb keys for rescue will need th
Andrew Lowe writes:
> I've just kicked off an "emerge -NuD world" and will now head
> out for a while. My emerge has to do, amongst others, gcc, libreoffice,
> Firefox & Thunderbird. Now when I get back I'll want to know where the
> emerge is up to so, in my ignorance of portage/emerge in gr
On 2012-06-02 09:43, Florian Philipp wrote:
> You don't have to be "blessed". You could call your distribution
> BallmerSucks and still get a certificate. You just have to
> register, authenticate and pay the fee. Anything else would earn
> them an antitrust law suite they wouldn't forget.
...
Am 02.06.2012 04:26, schrieb William Kenworthy:
> http://boingboing.net/2012/05/31/lockdown-freeopen-os-maker-p.html
>
> and something I had not considered with the whole idea was even bootable
> cd's and usb keys for rescue will need the same privileges ...
>
> BillK
>
>
>
>
I find this art
Andrew Lowe wrote:
> Hi all,
> I've just kicked off an "emerge -NuD world" and will now head out
> for a while. My emerge has to do, amongst others, gcc, libreoffice,
> Firefox & Thunderbird. Now when I get back I'll want to know where the
> emerge is up to so, in my ignorance of portage/emerge
25 matches
Mail list logo
