_dl_gettimeofday() was used by the prebind code, which was recently
removed.
_dl_lstat() was only used by _dl_realpath(), which no longer needs it.
ok?
Index: alpha/ldasm.S
===
RCS file: /cvs/src/libexec/ld.so/alpha/ldasm.S,v
ret
Sigh, stupid control-enter keybinding in gmail
What I meant to say was:
BTW, this chunk in fusefs_setattr():
On Sat, Aug 27, 2016 at 8:50 PM, Philip Guenther wrote:
> if (io->fi_flags & FUSE_FATTR_SIZE && vp->v_type == VDIR) {
> error = EISDIR;
> goto
if (io->fi_flags & FUSE_FATTR_SIZE && vp->v_type == VDIR) {
error = EISDIR;
goto out;
}
On Sat, Aug 27, 2016 at 4:42 AM, Martin Natano wrote:
> In struct fusebuf the attributes (used for getattr/setattr and to return
> the ino/mode of a newly created file) are stored in a struct vattr. The
> problem with this is, that using struct vattr in userspace is suboptimal
> as some related he
I have no objections.. If I hear none by monday I can commit it for you
On Sat, Aug 27, 2016 at 11:53:14PM -0300, Henrique N. Lengler wrote:
> > Hi,
> >
> > This is a tiny patch to enable the use of numpad Enter key on cwm menus.
> >
> > Regards,
> >
> > Henrique N. Lengler
>
> No intention t
> Hi,
>
> This is a tiny patch to enable the use of numpad Enter key on cwm menus.
>
> Regards,
>
> Henrique N. Lengler
No intention to apply this?
Numpad enter key is is recognized by every program on openbsd base and xenocara,
so this would keep consistency. Anyway it is only one line.
Index
Well you've failed to justify removing it.
Does it hurt anyone to leave it?
> Xserver no longer listen on tcp 6000:6010 by default. I wonder if that pf
> rule is still necessary.
>
>
> Index: pf.conf
> ===
> RCS file: /cvs/src/etc/
Xserver no longer listen on tcp 6000:6010 by default. I wonder if that pf
rule is still necessary.
Index: pf.conf
===
RCS file: /cvs/src/etc/pf.conf,v
retrieving revision 1.54
diff -u -p -r1.54 pf.conf
--- pf.conf 23 Aug 2014 05:
Currently, realpath() calls lstat() on each component and -- if it's a
symlink -- then call readlink() on it. All it uses the lstat() for is "is
this a symlink".
Umm, readlink() will tell you that, more cheaply! Just call readlink()
directly and if it returns EINVAL then its not a symlink.
On Sat, Aug 27, 2016 at 08:31:02PM +0200, Ingo Schwarze wrote:
> Hi Chris,
>
> i'm not sure that i understand all your questions, but i'm trying
> to answer as best i can.
>
> Chris Bennett wrote on Sat, Aug 27, 2016 at 12:00:29PM -0500:
>
> > I'd like some help understanding how the policy work
Hi Chris,
i'm not sure that i understand all your questions, but i'm trying
to answer as best i can.
Chris Bennett wrote on Sat, Aug 27, 2016 at 12:00:29PM -0500:
> I'd like some help understanding how the policy works with actually
> having something acceptable to being included into base vs. n
On Sat, Aug 27, 2016 at 07:34:53PM +0200, Ingo Schwarze wrote:
> Hi Todd,
>
> Todd C. Miller wrote on Sat, Aug 27, 2016 at 10:28:14AM -0600:
>
> > Now that we have a handy size_t scratch variable,
> > we can use it to store the return value of mbrtowc()
> > instead of storing it in an int. Worth
Hi Todd,
Todd C. Miller wrote on Sat, Aug 27, 2016 at 10:28:14AM -0600:
> Now that we have a handy size_t scratch variable,
> we can use it to store the return value of mbrtowc()
> instead of storing it in an int. Worth it or overkill?
Some interfaces are specifically designed to trap the unwar
I'd like some help understanding how the policy works with actually
having something acceptable to being included into base vs. needing to
be a port.
Some code essentially has only one way to write it and I see it all over
the place. Calling a variable with another name doesn't seem at all like
ori
On Sat, 27 Aug 2016 12:12:02 +0200, Ingo Schwarze wrote:
> However, in the case at hand, it really helps readability
> in a function (unavoidably) already longer than comfortable
> for reading it.
Now that we have a handy size_t scratch variable, we can use it to
store the return value of mbrtowc
> in 2014, Theo scolded me when i tried to use strnlen(3) at some
> place in mandoc where it wasn't really important, pointing out that
> some systems still didn't have it, and saying: "Let me say simply:
> Yuck." And indeed, i promptly got reports about compile failures
> on Solaris.
Right.
> H
Illegal fragmentation block sizes can trigger division by zero in the
disklabel and fsck_ffs tools.
See this sequence of commands to reproduce:
# dd if=/dev/zero of=nofrag.iso bs=1M count=1
# vnconfig vnd0 nofrag.iso
# disklabel -e vnd0 # create 'a' and set fsize = bsize = 1
# fsck_ff
Hi Sevan,
Sevan Janiyan Solaris wrote on Wed, Aug 24, 2016 at 01:35:38AM +0100:
> Index: bin/expr/expr.1
> ===
> RCS file: /cvs/src/bin/expr/expr.1,v
> retrieving revision 1.23
> diff -u -p -u -r1.23 expr.1
> --- bin/expr/expr.1 16
On 08/27/16 12:32, Guenther Niess wrote:
...
Or do you think we should change
+ .algo_strength = SSL_HIGH,
to
+ .algo_strength = SSL_MEDIUM,
this matter seems to be highly subjective. I personally don't like and
don't make use of the LOW/MEDIUM/HIGH keywords for c
In struct fusebuf the attributes (used for getattr/setattr and to return
the ino/mode of a newly created file) are stored in a struct vattr. The
problem with this is, that using struct vattr in userspace is suboptimal
as some related helpers are not available, e.g. VATTR_NULL() and IFTOVT().
What
On 08/26/2016 12:44 AM, Bob Beck wrote:
> On Thursday, 25 August 2016, Ted Unangst wrote:
>> Andreas Bartelt wrote:
>>> On 08/25/16 15:58, Brent Cook wrote:
No objection here. Anyone else?
>>>
>>> in general, I personally would only add further cryptographic primitives
>>> to a TLS confi
Would this be ok for inclusion in the next release?
On Sat, Aug 27, 2016 at 7:27 AM, Mart Tõnso wrote:
> Updated Estonian keymap patch for current. Original from 2005 at
> http://marc.info/?l=openbsd-tech&m=112873075504474
>
>
> Index: sys/dev/pckbc/wskbdmap_mfii.c
> =
Hi Todd,
in 2014, Theo scolded me when i tried to use strnlen(3) at some
place in mandoc where it wasn't really important, pointing out that
some systems still didn't have it, and saying: "Let me say simply:
Yuck." And indeed, i promptly got reports about compile failures
on Solaris.
However, in
Ok, thank you so much Raf,
I'll take note for the next devices.
Cheers,
Guille
2016-08-27 10:28 GMT+02:00 Raf Czlonka :
> On Sat, Aug 27, 2016 at 08:53:57AM BST, Guillermo Bernaldo de Quiros
> Maraver wrote:
> > Hi, good morning,
> >
> > Please, could anyone add this patch?
> >
> > Thanks anywa
On Sat, Aug 27, 2016 at 08:53:57AM BST, Guillermo Bernaldo de Quiros Maraver
wrote:
> Hi, good morning,
>
> Please, could anyone add this patch?
>
> Thanks anyway
>
> Index: pcidevs
> ===
> RCS file: /cvs/src/sys/dev/pci/pcidevs,v
Hi, good morning,
Please, could anyone add this patch?
Thanks anyway
Index: pcidevs
===
RCS file: /cvs/src/sys/dev/pci/pcidevs,v
retrieving revision 1.1802
diff -u -p -r1.1802 pcidevs
--- pcidevs 31 Jul 2016 07:36:16 - 1.1802
++
26 matches
Mail list logo
