AMD Ryzen product errata
https://www.amd.com/system/files/TechDocs/55449_Fam_17h_M_00h-0Fh_Rev_Guide.pdf
On 11/2/2018 11:03 AM, Denis wrote:
> OpenBSD6.4amd64 first install on latest AMD Ryzen7 2700 +Asrock B450
> chipset based mainboard.
>
> Hardware is relatively new. Can test any
Hi,
dhclient(8)'s privileged process cannot be pledged yet due to some route
related sysctl(2)'s, but it seems it only needs to access two files. One is
/etc/resolv.conf with write/create permissions and saved_argv[0] (usually
/sbin/dhclient) with execute since we may receive a SIGHUP and it will
On Mon, Nov 05, 2018 at 08:43:56AM -0500, Daniel Dickman wrote:
>
>
> > On Nov 5, 2018, at 8:30 AM, Marc Espie wrote:
> >
> > Or we could just finally remove brk and sbrk from the libc ?
> >
> >
>
> you won’t get very far. they are still needed in base (gcc, clang, mkhybrid).
The big
On Mon, Nov 05, 2018 at 09:15:28AM -0500, Daniel Dickman wrote:
>gcc uses them for precompiled headers (PCH) which is a local diff added
>by kurt@ in 2009. its likely nothing in base uses PCH but i don't know
>what in ports needs this:
This has always been a mess. I suspect it's not
On Mon, Nov 05, 2018 at 11:31:53AM +, Stuart Henderson wrote:
> On 2018/11/04 10:29, Daniel Dickman wrote:
> > The below overrides the cached autoconf value that says that we have
> > sbrk(2) on our system and pretends like we don't have it.
> >
> > With this we can build tcsh without a need
>> On Nov 5, 2018, at 8:30 AM, Marc Espie wrote:
>>
>> Or we could just finally remove brk and sbrk from the libc ?
>>
>>
>
>you won???t get very far. they are still needed in base (gcc, clang, mkhybrid).
The goal isn't to remove it.
Rather, we want to neuter one semantic component, such
> On Nov 5, 2018, at 8:47 AM, Marc Espie wrote:
>
>> On Mon, Nov 05, 2018 at 08:43:56AM -0500, Daniel Dickman wrote:
>>
>>
>>> On Nov 5, 2018, at 8:30 AM, Marc Espie wrote:
>>>
>>> Or we could just finally remove brk and sbrk from the libc ?
>>>
>>>
>>
>> you won’t get very far. they
As per krw@ I probably should add a #define to /sbin/dhclient and use
that instead of saved_argv and you wouldn't have that error but you'd still
have to make install.
On 22:53 Mon 05 Nov , Remi Locherer wrote:
> On Mon, Nov 05, 2018 at 12:30:08PM +, Ricardo Mestre wrote:
> > Hi,
> >
>
On Mon, Nov 05, 2018 at 08:49:08PM +0100, Denis Fondras wrote:
> I wanted to run bgpd in a specific rdomain.
> First routes could not be selected then I patched rde.c and routes magically
> appeared in the right routing table.
>
> Is this as simple as the provided diff or am I overlooking
On Mon, Nov 05, 2018 at 12:30:08PM +, Ricardo Mestre wrote:
> Hi,
>
> dhclient(8)'s privileged process cannot be pledged yet due to some route
> related sysctl(2)'s, but it seems it only needs to access two files. One is
> /etc/resolv.conf with write/create permissions and saved_argv[0]
I wanted to run bgpd in a specific rdomain.
First routes could not be selected then I patched rde.c and routes magically
appeared in the right routing table.
Is this as simple as the provided diff or am I overlooking something ?
Denis
Index: rde.c
Hi,
As someone with interests in kernel development and a lot of spare
time, I want to work on OS patches. I just installed OpenBSD 6.4 in a
clean development VM and started building the -current branch from CVS
to get up to date with the latest commits.
I noticed that the build was failing with
On Tuesday 06 November 2018 00:39:11 Luigi30 wrote:
> Hi,
>
> As someone with interests in kernel development and a lot of spare
> time, I want to work on OS patches. I just installed OpenBSD 6.4 in a
> clean development VM and started building the -current branch from CVS
> to get up to date
something like the below? I added a new define for /etc/resolv.conf since it's
now used on 2 different places and hardcoded the executable path to avoid
strange errors if running from a symlink directory as pointed out by remi@
Index: dhclient.c
On Tue, Nov 06, 2018 at 08:21:57AM +0100, Martijn van Duren wrote:
> ping
>
> On 10/24/18 10:27 AM, Martijn van Duren wrote:
> > In my previous ldap mail I proclaimed that we should encode whitespace.
> > Reading rfc2849 a bit further, encoding a string with leading space is
> > mandatory by
ping
On 10/24/18 11:34 AM, Martijn van Duren wrote:
> This adds UTF-8 support for join(1). Since we don't support collation we
> can skip that part of POSIX. This patch does add support for splitting
> columns on UTF-8 characters.
>
> Using schwarze@'s favorite UTF-8 character:
> $ cat /tmp/z1
ping
On 10/24/18 10:27 AM, Martijn van Duren wrote:
> In my previous ldap mail I proclaimed that we should encode whitespace.
> Reading rfc2849 a bit further, encoding a string with leading space is
> mandatory by SAFE-INIT-CHAR. This is needed because of the definition
> of value-spec, which
17 matches
Mail list logo
