> On Oct 20, 2015, at 8:55 PM, Benjamin Kaduk wrote:
>
> On Tue, 20 Oct 2015, John wrote:
>
>> Hi,
>>
>> as subject - is building kernel in /sys/amd64/conf depreciated?
>>
>> I can get a modified kernel to build and install in /usr/src but not
>> in /sys/amd64/conf. I always used to be able t
On Tue, 20 Oct 2015, John wrote:
> Hi,
>
> as subject - is building kernel in /sys/amd64/conf depreciated?
>
> I can get a modified kernel to build and install in /usr/src but not
> in /sys/amd64/conf. I always used to be able to do this in there, then
> again I either used -RELEASE or -STABLE. I
from Jeffrey Bouquet:
> I'd installworld in single user mode... sorry for no backstory. Worked here.
Sure, I used single user mode, as advised in UPDATING file.
from Sergey Kandauro:
> This looks like if you would try to installworld on newer sources and older
> objs without doing buildworld f
Hi,
as subject - is building kernel in /sys/amd64/conf depreciated?
I can get a modified kernel to build and install in /usr/src but not
in /sys/amd64/conf. I always used to be able to do this in there, then
again I either used -RELEASE or -STABLE. I used to do it like this:
1. cd /sys/amd64/co
Le 20/10/2015 17:50, Freddie Cash a écrit :
On Tue, Oct 20, 2015 at 6:32 AM, Juan Ramón Molina Menor mailto:lis...@club.fr>>wrote:
Hi!
I’m certainly doing it wrong, because CCACHE does not kick in after
applying the patch and modifying make.conf. CCACHE stats ('ccache
-z' follow
On Tue, Oct 20, 2015 at 6:32 AM, Juan Ramón Molina Menor
wrote:
> Hi!
>
> I’m certainly doing it wrong, because CCACHE does not kick in after
> applying the patch and modifying make.conf. CCACHE stats ('ccache -z'
> followed by 'ccache -s') remain at zero during buildworld while they used
> to re
Hi!
I’m certainly doing it wrong, because CCACHE does not kick in after
applying the patch and modifying make.conf. CCACHE stats ('ccache -z'
followed by 'ccache -s') remain at zero during buildworld while they
used to reflect the cache miss/hits before.
# cat /etc/make.conf
WITH_CCACHE_BUIL
On 20 October 2015 at 11:07, Thomas Mueller wrote:
> I was trying to test the new i915 graphics driver but got stuck in building
> and installing the userland:
>
> /usr/share/man/man2/mknodat.2 -> /usr/share/man/man2/mknod.2
> /usr/share/man/man2/munlock.2 -> /usr/share/man/man2/mlock.2
> /usr/sh
On 10/20/2015 01:27, Poul-Henning Kamp wrote:
In message
, NGie
Cooper writes:
1. Why are there 2 competing technologies?
They are not competing, they support two very different threat models.
We need to make this a lot more clear in the Handbook. John-Mark is
taking the charge h
>From p...@phk.freebsd.dk Tue Oct 20 10:08:55 2015
>
>>Am I correct that the papers are from 2003 and 2004
>>respectively. Has much changed in gbde since then?
>
>Nope.
One thing that puzzled me about the way gbde
is integrated with the FreeBSD boot sequence is
that it's not possible to boot witho
In message <201510200841.t9k8fngy005...@mech-as222.men.bris.ac.uk>, Anton
Shterenlikht writes:
>Am I correct that the papers are from 2003 and 2004
>respectively. Has much changed in gbde since then?
Nope.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org
>> In message <201510200645.t9k6jaam004...@mech-as222.men.bris.ac.uk>, Anton
>> Shterenlikht writes:
GBDE is for when the user is in danger.
>>>
>>> In danger of what?
>>> Please elaborate.
>>
>> Read the paper:
>>
>> http://phk.freebsd.dk/pubs/bsdcon-03.gbde.paper.pdf
>>
>> Or use t
I was trying to test the new i915 graphics driver but got stuck in building and
installing the userland:
/usr/share/man/man2/mknodat.2 -> /usr/share/man/man2/mknod.2
/usr/share/man/man2/munlock.2 -> /usr/share/man/man2/mlock.2
/usr/share/man/man2/munlockall.2 -> /usr/share/man/man2/mlockall.2
/us
In message <5625d422.4040...@fizk.net>, Yonas Yanfa writes:
>> Think human rights activists for instance.
>
>Couldn't they use a fake email address and Tor to communicate
>anonymously? I'd be surprised if they aren't already.
If you think being a human rights activist is that simple, yo
> On Oct 20, 2015, at 00:29, Poul-Henning Kamp wrote:
>
>
> In message <201510200645.t9k6jaam004...@mech-as222.men.bris.ac.uk>, Anton
> Shterenlikht writes:
>>> GBDE is for when the user is in danger.
>>
>> In danger of what?
>> Please elaborate.
>
> Read the paper:
>
> http:/
>GBDE is for when the user is in danger.
In danger of what?
Please elaborate.
>From the handbook, it is not clear at all
that the two encryption methods are designed
to defend against different threats.
Maybe I'm using the wrong one...
Thank you
Anton
__
In message <201510200645.t9k6jaam004...@mech-as222.men.bris.ac.uk>, Anton
Shterenlikht writes:
>>GBDE is for when the user is in danger.
>
>In danger of what?
>Please elaborate.
Read the paper:
http://phk.freebsd.dk/pubs/bsdcon-03.gbde.paper.pdf
Or use the TL;DR version in the
17 matches
Mail list logo
