Hey,
Use the monotonic clock when logging progress in cdio(1) and ftp(1).
This keeps the progress log from blipping or stalling if the system
time is changed, e.g., in the midst of a transfer or rip.
ok?
--
Scott Cheloha
Index: usr.bin/cdio/mmc.c
Hey,
None of these programs make use of anything but the .tv_sec field
in the timeval initialized by gettimeofday(2), so we can simplify
the code some and just use time(3).
While here, in date(1) we ought to use err(3) instead of errx(3)
if adjtime(2) fails. This:
date: adjtime:
$ diff -u fc-list.1.orig fc-list.1
--- fc-list.1.orig Fri Dec 22 18:47:19 2017
+++ fc-list.1 Fri Dec 22 18:54:24 2017
@@ -69,7 +69,7 @@
\fBfc-scan\fR(1)
.PP
The fontconfig user's guide, in HTML format:
Hi Theo,
Theo Buehler wrote on Thu, Dec 21, 2017 at 11:57:12PM +0100:
> Ingo Schwarze wrote:
>> So i really don't feel like adding a BUGS section, but instead i
>> think documenting that -i is intended as an ASCII-only feature is
>> the way to go.
> Yes, sounds reasonable.
Thanks for checking!
> Date: Fri, 22 Dec 2017 23:35:47 +0100
> From: Frederic Cambus
>
> Hi tech@,
>
> Now that we call rasops_putchar_rotated(), we don't need ri anymore.
>
> Comments? OK?
ok kettenis@
> Index: sys/dev/rasops/rasops.c
>
On 2017/12/22 22:12, Anton Lindqvist wrote:
> Hi,
> Since export accepts several variables, put them on a single line.
>
> Comments? OK?
>
> Index: release.8
> ===
> RCS file: /cvs/src/share/man/man8/release.8,v
> retrieving
Hi tech@,
Now that we call rasops_putchar_rotated(), we don't need ri anymore.
Comments? OK?
Index: sys/dev/rasops/rasops.c
===
RCS file: /cvs/src/sys/dev/rasops/rasops.c,v
retrieving revision 1.48
diff -u -p -r1.48 rasops.c
---
On 2017/12/22 19:47, Nicholas Marriott wrote:
> I don't think we should bring ! back.
>
> I wanted to remove v and | (and some other stuff) shortly afterwards, but
> several people objected.
>
> I did suggest having a lightweight less in base for most people and adding
> the full upstream less
> Date: Fri, 22 Dec 2017 22:12:19 +0100
> From: Anton Lindqvist
>
> Hi,
> Since export accepts several variables, put them on a single line.
>
> Comments? OK?
Feels like unnecessary chrun to me. The exports are already on a
single line, so there is no benefit for copy and
Hi,
Since export accepts several variables, put them on a single line.
Comments? OK?
Index: release.8
===
RCS file: /cvs/src/share/man/man8/release.8,v
retrieving revision 1.89
diff -u -p -r1.89 release.8
--- release.8 5 Jun 2017
I don't think we should bring ! back.
I wanted to remove v and | (and some other stuff) shortly afterwards, but
several people objected.
I did suggest having a lightweight less in base for most people and adding
the full upstream less to ports for the stuff we don't want to maintain
(like we do
On Fri, 22 Dec 2017 12:08:58 +0100, =?UTF-8?Q?Jan_Kokem=c3=bcller?= wrote:
> I've found some buffer overflows in realpath(3). They are limited to
> just two bytes though (one after the 'left' buffer and one before
> 'symlink'), so the impact is minimal.
>
> Similar bugs in FreeBSD:
>
On Mon, Sep 18, 2017 at 08:53:43PM +0300, Artturi Alm wrote:
> On Mon, Sep 18, 2017 at 03:41:56PM +0300, Artturi Alm wrote:
> > On Mon, Sep 18, 2017 at 11:19:09AM +0100, Stuart Henderson wrote:
> > > On 2017/09/18 04:28, Artturi Alm wrote:
> > > > Do i really need to reference datasheets, or would
On Sun, Dec 10, 2017 at 07:05:11PM +0100, Mark Kettenis wrote:
> > Date: Sun, 10 Dec 2017 19:03:41 +0200
> > From: Artturi Alm
> >
> > On Wed, Nov 29, 2017 at 11:45:51AM +0200, Artturi Alm wrote:
> > > Hi,
> > >
> > >
> > > there's more work to be done for fec, but this
On Fri, Dec 15, 2017 at 03:10:49PM +0100, Alexander Bluhm wrote:
> Hi,
>
> With pf divert raw sockets behave differently than TCP or UDP.
>
> TCP and UDP first make an exact match without divert in_pcbhashlookup().
> Then they do the divert-to match in in_pcblookup_listen().
>
> This diff makes
Hi,
There is a corner case where linking the inp to the state key does
not work in pf. The function pf_inp_link() takes the state key
from the mbuf and not the one we have just found. Introduce a new
function pf_state_key_link_inpcb() that does exactly that together
with some sanity checks.
I
Hi,
I would like to update LLVM, including clang, lld and lldb, to the
patch release version 5.0.1. They typically only do bugfixing, which
means that the diff to 5.0.0 is "only" about 3500 lines.
I don't expect any big fallout, but I would appreciate if someone
could do a ports run with this
Hi,
I've found some buffer overflows in realpath(3). They are limited to
just two bytes though (one after the 'left' buffer and one before
'symlink'), so the impact is minimal.
Similar bugs in FreeBSD:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219154
Here is a list of issues:
- The
18 matches
Mail list logo