chenga2 wrote on Wed, Sep 23, 2015 at 05:49:44PM -0400:
> This fixes a typo in the faq13.html page. Specifically in section 13.7 of
> the page. 'handly' should be either 'handy', or 'handily'.
Committed, thanks.
Ingo
> Index: faq13.html
> =
On Wed, Sep 23, 2015 at 07:42:54PM -0400, Michael Reed wrote:
> banner(1) without arguments works fine, so denote it as such
> in the manual.
>
in the context of banner(1), define "works fine". i mean, technically
maybe it does but, practically, why try to show this to the reader? is
there a use
Good day,
Please see diffs (below) to add a user defined "constraint margin" to ntpd.
I also included a basic regress test report (and script).
This may be a misguided endeavour, but I am enjoying myself!
Comments are more than welcome.
Regards,
Rob
Index: client.c
==
In dired mode, I noticed that if the cursor is on a file marked for
deletion when dired-do-flagged-delete (x) is called, the cursor is
placed on the left hand side of the window. This diff makes d_expunge
behave like other delete functions and calls d_warpdot to() place the
cursor on the first char
This fixes a typo in the faq13.html page. Specifically in section 13.7
of the page. 'handly' should be either 'handy', or 'handily'.
Index: faq13.html
===
RCS file: /cvs/www/faq/faq13.html,v
retrieving revision 1.155
diff -u -p -
banner(1) without arguments works fine, so denote it as such
in the manual.
Index: src/usr.bin/banner/banner.1
===
RCS file: /cvs/src/usr.bin/banner/banner.1,v
retrieving revision 1.8
diff -u -p -r1.8 banner.1
--- src/usr.bin/banner
Hi all,
I test it out as both `arch' and `machine' and didn't observe
any differences. Also, I figured I might as well convert exit(3)
to return while touching this code, as was done in [1].
Regard,
Michael
[1]: https://marc.info/?l=openbsd-tech&m=144095769912804&w=2
Index: src/usr.bin/arch/
Am I interpreting this correctly?
This is the least invasive fix, but it's unfortunate that this function
allows the supplied buffer to be NULL. If we made it unconditionally
allocate a new buffer, we would have to change some program logic
because uses pass stack-allocated statically-sized buffer
On Wed, Sep 23, 2015 at 12:12:01PM -0400, Ted Unangst wrote:
> Dimitris Papastamos wrote:
> > I did some very crude benchmarking on my machine and I could push
> > about 100k messages per second through a single message queue.
> >
> > At this point, I can start working on manpages + the necessary
Jason McIntyre wrote:
> On Mon, Sep 21, 2015 at 10:40:29PM -0400, Michael McConville wrote:
> > Could also say "Use the err(3) and warn(3) family of functions." That's
> > what the err(3) man page intro refers to it as.
> >
>
> please some developer commit or reject this. thanks,
> jmc
Ingo gave
Jason McIntyre wrote:
> On Mon, Sep 21, 2015 at 10:40:29PM -0400, Michael McConville wrote:
> > Could also say "Use the err(3) and warn(3) family of functions." That's
> > what the err(3) man page intro refers to it as.
> >
>
> please some developer commit or reject this. thanks,
i liked the wor
On Mon, Sep 21, 2015 at 10:40:29PM -0400, Michael McConville wrote:
> Could also say "Use the err(3) and warn(3) family of functions." That's
> what the err(3) man page intro refers to it as.
>
please some developer commit or reject this. thanks,
jmc
> Index: share/man/man9/style.9
> ===
On Sat, Sep 19, 2015 at 10:46:23PM -0400, Rob Pierce wrote:
> Mention that collisions are theorizied for SHA-1 in the caveat.
>
> Regards,
>
> Index: md5.1
> ===
> RCS file: /cvs/src/bin/md5/md5.1,v
> retrieving revision 1.44
> diff
Dimitris Papastamos wrote:
> I did some very crude benchmarking on my machine and I could push
> about 100k messages per second through a single message queue.
>
> At this point, I can start working on manpages + the necessary
> userspace glue.
>
> Is this patch going in the right direction?
I d
Hi,
I'll test your diff on an x86 multiprocessor now. Will let you know if
there are any issues. My server is not a router, though
On Wed, Sep 23, 2015 at 11:21 AM, Martin Pieuchot wrote:
> Here's an alternative path towards putting rtisvalid(9) checks in the
> tree. The end goal is to stop usi
On 22/09/15(Tue) 19:55, Stefan Sperling wrote:
> On Tue, Sep 22, 2015 at 01:23:17PM -0400, Ted Unangst wrote:
> > Stefan Sperling wrote:
> > > Properly reset the RX ring by clearing RX buffer status exposed to
> > > hardware.
> > > Found by Matthew Dillon while porting FreeBSD's iwm(4) to Dragonfl
On Sun, Sep 20, 2015 at 04:00:56PM +0059, Jason McIntyre wrote:
> >
> > there is a "d" missing at the end.
> >
> > And "In a tamed program, systrace(4) is disabled" sounds better to me, but
> > jmc might have an opinion on that.
no problem, I am not too confident in my english wording :)
> > Th
Here's an alternative path towards putting rtisvalid(9) checks in the
tree. The end goal is to stop using !RTF_UP routes, so simply bail if
such route is passed to ARP or NDP instead of trying to fetch a
compatible one.
I hope this will help me find some bugs, I'd appreciate tests and oks.
Inde
18 matches
Mail list logo