Here's the revised diff that removes $FreeBSD$ IDs from my previous diff.
Index: lib/libc/arch/amd64/sys/tfork_thread.S
===
RCS file: /cvs/src/lib/libc/arch/amd64/sys/tfork_thread.S,v
retrieving revision 1.6
diff -u -p -u -p -r1.6
On Thu, Mar 14, 2019 at 09:06:12PM +0100, Sebastian Benoit wrote:
> Claudio Jeker(cje...@diehard.n-r-g.com) on 2019.03.14 11:53:29 +0100:
> > On Thu, Mar 14, 2019 at 11:46:10AM +0100, Otto Moerbeek wrote:
> > > On Thu, Mar 14, 2019 at 10:43:03AM +0100, Claudio Jeker wrote:
> > >
> > > > On Thu,
Hi,
all tools dealing with X font server have been already removed, and
don't seem to be missed since no one asked to re-add them in ports.
Now, libFS, the font server client library can be removed.
I've checked in sqlports and with a bulk build on amd64 that nothing
in ports in depending on it
Claudio Jeker(cje...@diehard.n-r-g.com) on 2019.03.14 11:53:29 +0100:
> On Thu, Mar 14, 2019 at 11:46:10AM +0100, Otto Moerbeek wrote:
> > On Thu, Mar 14, 2019 at 10:43:03AM +0100, Claudio Jeker wrote:
> >
> > > On Thu, Mar 14, 2019 at 10:36:58AM +0100, Otto Moerbeek wrote:
> > > > Hi,
> > > >
>
Hi Stefan,
Stefan Sperling wrote on Thu, Mar 14, 2019 at 04:11:00PM +0100:
> Yes, OK.
Thanks for checking.
Here is the next step outside line.c, completely cleaning up the file
less/filename.c with respect to UTF-8 handling. The loop needed is very
similar to the one in search.c except that
On Thu, Mar 14, 2019 at 04:04:20PM +0100, Ingo Schwarze wrote:
> Hi,
>
> the following is a very simple patch to completely clean up the
> file less/search.c with respect to UTF-8 handling. It also fixes
> an outright bug: Searching for uppercase UTF-8 characters currently
> doesn't work because
Hi,
the following is a very simple patch to completely clean up the
file less/search.c with respect to UTF-8 handling. It also fixes
an outright bug: Searching for uppercase UTF-8 characters currently
doesn't work because passing a Unicode codepoint (in this case, the
"ch" retrieved with
On Thu, Mar 14, 2019 at 11:46:10AM +0100, Otto Moerbeek wrote:
> On Thu, Mar 14, 2019 at 10:43:03AM +0100, Claudio Jeker wrote:
>
> > On Thu, Mar 14, 2019 at 10:36:58AM +0100, Otto Moerbeek wrote:
> > > Hi,
> > >
> > > So i have a little IPv6 problem.
> > >
> > > I have a machine in colocation
> Date: Thu, 14 Mar 2019 19:17:42 +1100
> From: Jonathan Gray
>
> A large number of machines ship uefi firmware which does not have
> the serial io protcol. When using shell.efi 'dh -p serialio' and
> 'sermode' indicate it is not present.
>
> To handle this fallback to pio access with code
On Thu, Mar 14, 2019 at 10:43:03AM +0100, Claudio Jeker wrote:
> On Thu, Mar 14, 2019 at 10:36:58AM +0100, Otto Moerbeek wrote:
> > Hi,
> >
> > So i have a little IPv6 problem.
> >
> > I have a machine in colocation that has IPv6. I have my home cable
> > modem connection that does not have
Thanks, comments inline.
> diff --git a/usr.bin/cu/command.c b/usr.bin/cu/command.c
> index c07fe73aeca..e225fb544be 100644
> --- a/usr.bin/cu/command.c
> +++ b/usr.bin/cu/command.c
> @@ -30,6 +30,7 @@
> #include
> #include
> #include
> +#include
>
> #include "cu.h"
>
> @@ -223,6
Den tors 14 mars 2019 kl 10:48 skrev Claudio Jeker :
> On Thu, Mar 14, 2019 at 10:36:58AM +0100, Otto Moerbeek wrote:
> > How does one solve the default route problem? I never really
> > understood how routing works in the presense of IPSEC flows.
>
> IPSec flows steal the traffic away before it
On Thu, Mar 14, 2019 at 10:36:58AM +0100, Otto Moerbeek wrote:
> Hi,
>
> So i have a little IPv6 problem.
>
> I have a machine in colocation that has IPv6. I have my home cable
> modem connection that does not have it.
>
> So I thought: I make my own tunnel. First I tried gif(4), that worked,
Hi,
So i have a little IPv6 problem.
I have a machine in colocation that has IPv6. I have my home cable
modem connection that does not have it.
So I thought: I make my own tunnel. First I tried gif(4), that worked,
but only after some fighting with mtu settings on all hosts on my home
net via
A large number of machines ship uefi firmware which does not have
the serial io protcol. When using shell.efi 'dh -p serialio' and
'sermode' indicate it is not present.
To handle this fallback to pio access with code derived from
amd64/stand/libsa/bioscons.c minus the init code which resulted in
On Thu, Mar 14, 2019 at 01:40:55AM +0100, Ulf Brosziewski wrote:
> Anyway, first we should make sure that the mechanism
> is sound; I'm a bit puzzled by Joshua's report and hope there will be
> more tests.
Your change works well on my x250 and x201.
Compared to my x220, which currently runs the
16 matches
Mail list logo