On Fri, Nov 29, 2019 at 07:02:27AM +0100, Björn Ketelaars wrote:
> On Thu 28/11/2019 16:16, Otto Moerbeek wrote:
> > On Thu, Nov 28, 2019 at 03:26:34PM +0100, Otto Moerbeek wrote:
> >
> > > Hi,
> > >
> > > In many offices, split horizon DNS is used. This means that if you are
> > > in the office
On Thu 28/11/2019 16:16, Otto Moerbeek wrote:
> On Thu, Nov 28, 2019 at 03:26:34PM +0100, Otto Moerbeek wrote:
>
> > Hi,
> >
> > In many offices, split horizon DNS is used. This means that if you are
> > in the office you are supposed to use a specific resolver that will
> > hand out different re
spotted when reading code..
--
cvs diff: Diffing .
Index: file.c
===
RCS file: /home/nayden/cvsync/src/bin/csh/file.c,v
retrieving revision 1.38
diff -u -p -r1.38 file.c
--- file.c 28 Jun 2019 13:34:58 - 1.38
+++ file.c
OK millert@
- todd
ok?
Index: at.c
===
RCS file: /cvs/src/usr.bin/at/at.c,v
retrieving revision 1.82
diff -u -p -r1.82 at.c
--- at.c28 Jun 2019 13:35:00 - 1.82
+++ at.c29 Nov 2019 02:50:28 -
@@ -378,7 +378,7 @@ byctime(const
Hello,
A mostly mechanical diff that makes use of __func__ in place of
hardcoded function names in panic() and printf() calls.
If someone is working in netinet6 and this change will trample
your work please let me know and I'll hold off.
ok?
Index: icmp6.c
===
Miod Vallat wrote:
> > For dynamic binaries, valid regions are ld.so's text segment, the signal
> > trampoline, and libc.so's text segment... AND the main program's text.
> >
> > Unfortunately our current go build model hasn't followed solaris/macos
> > approach yet of calling libc stubs, and use
> For dynamic binaries, valid regions are ld.so's text segment, the signal
> trampoline, and libc.so's text segment... AND the main program's text.
>
> Unfortunately our current go build model hasn't followed solaris/macos
> approach yet of calling libc stubs, and uses the inappropriate "embed
>
Alexander Nasonov wrote:
> Theo de Raadt wrote:
> > The following change only permits system calls from address-ranges
> > in the process which system calls are expected from.
>
> Just curious if some approximation of pledge can be reimplemented
> in userspace with more granular libc.so's text s
Theo de Raadt wrote:
> The following change only permits system calls from address-ranges
> in the process which system calls are expected from.
Just curious if some approximation of pledge can be reimplemented
in userspace with more granular libc.so's text segments?
--
Alex
On Thu, Nov 28, 2019 at 06:12:11PM +0100, Mark Kettenis wrote:
> The man page change is not an improvement.
How so? Does it lack concrete examples? I'd rather leave a reference
to the manual that describes formatas in detail instead of repeating
suffices and/or examples.
Perhaps add one small ex
> Date: Thu, 28 Nov 2019 03:48:04 +0100
> From: Klemens Nanni
>
> On Thu, Nov 28, 2019 at 01:05:43AM +0100, Klemens Nanni wrote:
> > With that, the next step is to implement `ldomctl console guest01' in
> > analogy to vmctl(8).
> Here's a complete diff for updating the status output and implement
> Date: Thu, 28 Nov 2019 17:12:28 +0100
> From: Klemens Nanni
>
> Replace the hand-written routing with a proper library allowing even
> more formats. vmctl(8) does the same, which is also where I took the
> manual wording from.
>
> ldomctl has a local "util.h" which is included by parse.y, so
Replace the hand-written routing with a proper library allowing even
more formats. vmctl(8) does the same, which is also where I took the
manual wording from.
ldomctl has a local "util.h" which is included by parse.y, so
compilation would fail to find scan_scaled after including due
the include
On Thu, Nov 28, 2019 at 03:48:04AM +0100, Klemens Nanni wrote:
> I've tested this diff on a T4-2 machine with all possible invocations
> of `ldomctl status [domain]' and `ldomctl console [domain]': it always
> prints and attaches to the correct serial console respectively, whether
> I pass an expl
On Thu, Nov 28, 2019 at 09:53:20AM +0100, Tobias Heider wrote:
> > voidcopy_satoipa(struct ipsec_addr_wrap *,
>
> One minor nit: sa in iked usually refers to IPsec security associations,
> maybe it would make sense to use "saddr" here?
Good point, I'll rename it.
> > More
On Thu, Nov 28, 2019 at 03:26:34PM +0100, Otto Moerbeek wrote:
> Hi,
>
> In many offices, split horizon DNS is used. This means that if you are
> in the office you are supposed to use a specific resolver that will
> hand out different results than when asking for the same name on the
> rest of th
Hi,
In many offices, split horizon DNS is used. This means that if you are
in the office you are supposed to use a specific resolver that will
hand out different results than when asking for the same name on the
rest of the internet.
Until now unwind could not really handle that, e.g. in recursin
On Wed, Nov 27, 2019 at 05:18:32PM +0100, Mark Kettenis wrote:
> The inteldrm(4) driver keeps a cache of graphics objects, allegedly to
> make things faster by avoiding cache flushes. But those graphics
> objects consume memory that we want to free if we need it for
> something else.
>
> The diff
> void copy_satoipa(struct ipsec_addr_wrap *,
One minor nit: sa in iked usually refers to IPsec security associations,
maybe it would make sense to use "saddr" here?
> More tests appreciated.
> Feedback? OK?
Works for me. ok tobhe@, with or without name change.
20 matches
Mail list logo
