On 10/3/19 9:05 PM, Eric Faurot wrote:
> On Thu, Sep 19, 2019 at 05:48:17PM +, gil...@poolp.org wrote:
>
>>> To me, the only real problem with '\r' is at the end of lines. It's
>>> confusing
>>> since you never really know whether it's part of the content or the
>>> protocol.
>>>
>>> So I
so we can remove it, starting with taking it out of sys/conf/files.
ok?
Index: files
===
RCS file: /cvs/src/sys/conf/files,v
retrieving revision 1.674
diff -u -p -r1.674 files
--- files 29 Sep 2019 13:04:03 - 1.674
On Thu, Oct 03, 2019 at 04:22:47PM +1000, Jonathan Gray wrote:
> On Wed, Oct 02, 2019 at 03:48:27PM +0200, Jan Klemkow wrote:
> > On Tue, Oct 01, 2019 at 11:34:09AM +1000, Jonathan Gray wrote:
> > > On Tue, Oct 01, 2019 at 12:27:48AM +0200, Jan Klemkow wrote:
> > > > After updating my router to
On Thu, Sep 19, 2019 at 05:48:17PM +, gil...@poolp.org wrote:
> > To me, the only real problem with '\r' is at the end of lines. It's
> > confusing
> > since you never really know whether it's part of the content or the
> > protocol.
> >
> > So I suggest that we strip all '\r' found at the
On Thu, Oct 03, 2019 at 12:43:20PM -0400, sven falempin wrote:
> On Thu, Oct 3, 2019 at 12:15 PM Jason McIntyre wrote:
> >
> > On Thu, Oct 03, 2019 at 11:56:26AM -0400, sven falempin wrote:
> > > Dear reader,
> > >
> > > If you look an option, the options section does not tell you how to set it
>
On Thu, Oct 3, 2019 at 12:15 PM Jason McIntyre wrote:
>
> On Thu, Oct 03, 2019 at 11:56:26AM -0400, sven falempin wrote:
> > Dear reader,
> >
> > If you look an option, the options section does not tell you how to set it
> > ( nor where )
> > at least this creates a searchable ref between the set
So looking closer at Claudio's remark from this morning I found that 'e'
basically *must* be the last element in the sequence (or weird *beep*
happens). Also, 'e' never fails, since ber_link_elements doesn't have a
fail-case. So combining this information, if we end a
ber_printf_elements on 'e'
On Thu, Oct 03, 2019 at 11:56:26AM -0400, sven falempin wrote:
> Dear reader,
>
> If you look an option, the options section does not tell you how to set it
> ( nor where )
> at least this creates a searchable ref between the set ( which you cannot
> find looking for set
> because of the [t] ).
>
As discussed this morning with Claudio ber_printf_elements might give
the impression that it cleans up everything on failure, while it only
removes the last element before '.', which is (from a quick scan) not
used in our tree.
Since 'e' is the only parameter that gets linked in instead of copied
Dear reader,
If you look an option, the options section does not tell you how to set it
( nor where )
at least this creates a searchable ref between the set ( which you cannot
find looking for set
because of the [t] ).
Index: docs/USD.doc/vi.man/vi.1
On 3 Oct 2019, at 17:28, Stuart Henderson wrote:
> On 2019/10/03 17:25, Oliver Marugg wrote:
>> Hi
>>
>> Found another a small addition to www 66.html, pls. change platform name
>> from aarch64 to arm64 . -oliver
>
> This entry lists cpu architectures: aarch64, powerpc, mips64el,
> not machine
As discussed with semarie@ this morning: We're a bit too loose when it
comes to accessing indexes based directly from the pdu.
Diff below allows only indexes within the range of the pdu.
If user supplied oid and returned oid on index match the user supplied
input is shown (for easier reference).
On 2019/10/03 17:25, Oliver Marugg wrote:
> Hi
>
> Found another a small addition to www 66.html, pls. change platform name
> from aarch64 to arm64 . -oliver
This entry lists cpu architectures: aarch64, powerpc, mips64el,
not machine architectures: arm64, macppc, loongson (and if you think
about
Hi
Found another a small addition to www 66.html, pls. change platform name
from aarch64 to arm64 . -oliver
as the base system compiler.
The powerpc architecture is now provided with
https://man.openbsd.org/clang.1;>clang(1), in
- addition to aarch64, amd64, armv7, i386, mips64el, sparc64.
+
Hi Claudio,
thanks for answering promptly, much appreciated.
Kind regards,
Alexandre Hamada
On 02/10/2019 17:17, Claudio Jeker wrote:
On Wed, Oct 02, 2019 at 03:41:06PM -0300, Alexandre Hamada wrote:
Hi Tech,
I've found a missing initialization at ip.c (rpki-client project), and I
would like
On 10/3/19 10:56 AM, Claudio Jeker wrote:
> On Thu, Oct 03, 2019 at 10:42:42AM +0200, Martijn van Duren wrote:
>> On 10/3/19 10:19 AM, Claudio Jeker wrote:
>>> On Thu, Oct 03, 2019 at 10:01:06AM +0200, Martijn van Duren wrote:
On 10/3/19 9:21 AM, Sebastien Marie wrote:
> On Thu, Sep 26,
On Thu, Oct 03, 2019 at 10:55:51AM +0200, Martijn van Duren wrote:
> >
> > But even if the agent is wrong, I think it is dangerous to bindly trust the
> > other
> > side of accessing a memory chunk. Before using the value, it should be
> > checked
> > against the valid range to avoid
On 03.10.2019 02:13, Mike Belopuhov wrote:
> And what about OpenBSD-current or an attached patch as opposed
> to the linked one?
>
> Please don't go half the way if you're willing to help us out,
> we'd like to make OpenBSD 6.6-release work in these setups
> especially since we believe that all
On Thu, Oct 03, 2019 at 10:42:42AM +0200, Martijn van Duren wrote:
> On 10/3/19 10:19 AM, Claudio Jeker wrote:
> > On Thu, Oct 03, 2019 at 10:01:06AM +0200, Martijn van Duren wrote:
> >> On 10/3/19 9:21 AM, Sebastien Marie wrote:
> >>> On Thu, Sep 26, 2019 at 02:33:11PM +0200, Martijn van Duren
On 10/3/19 10:33 AM, Sebastien Marie wrote:
> On Thu, Oct 03, 2019 at 10:01:06AM +0200, Martijn van Duren wrote:
Index: snmpc.c
===
RCS file: /cvs/src/usr.bin/snmp/snmpc.c,v
retrieving revision 1.11
diff -u -p
On Thu, Oct 03, 2019 at 08:28:02AM +0200, Martijn van Duren wrote:
> Any feedback on the relayd part?
>
> On 9/25/19 8:58 AM, Martijn van Duren wrote:
> > On 9/25/19 8:55 AM, Martijn van Duren wrote:
> >> Hello,
> >>
> >> Mischa found that relayd's agentx support is pretty much unusable for
> >>
On 10/3/19 10:19 AM, Claudio Jeker wrote:
> On Thu, Oct 03, 2019 at 10:01:06AM +0200, Martijn van Duren wrote:
>> On 10/3/19 9:21 AM, Sebastien Marie wrote:
>>> On Thu, Sep 26, 2019 at 02:33:11PM +0200, Martijn van Duren wrote:
On 9/26/19 9:54 AM, Martijn van Duren wrote:
> Hello,
>
On Thu, Oct 03, 2019 at 10:01:06AM +0200, Martijn van Duren wrote:
> >> Index: snmpc.c
> >> ===
> >> RCS file: /cvs/src/usr.bin/snmp/snmpc.c,v
> >> retrieving revision 1.11
> >> diff -u -p -r1.11 snmpc.c
> >> --- snmpc.c18 Sep
On Thu, Oct 03, 2019 at 10:01:06AM +0200, Martijn van Duren wrote:
> On 10/3/19 9:21 AM, Sebastien Marie wrote:
> > On Thu, Sep 26, 2019 at 02:33:11PM +0200, Martijn van Duren wrote:
> >> On 9/26/19 9:54 AM, Martijn van Duren wrote:
> >>> Hello,
> >>>
> >>> I reckon this will be on of the last
On 10/3/19 9:21 AM, Sebastien Marie wrote:
> On Thu, Sep 26, 2019 at 02:33:11PM +0200, Martijn van Duren wrote:
>> On 9/26/19 9:54 AM, Martijn van Duren wrote:
>>> Hello,
>>>
>>> I reckon this will be on of the last major additions.
>>> Adding "snmp set" allows us to run snmpd's regress without
On Thu, Sep 26, 2019 at 02:33:11PM +0200, Martijn van Duren wrote:
> On 9/26/19 9:54 AM, Martijn van Duren wrote:
> > Hello,
> >
> > I reckon this will be on of the last major additions.
> > Adding "snmp set" allows us to run snmpd's regress without installing
> > netsnmp. :-)
> >
> > Tested
Hi,
While testing snmp(1), I found the following weird behaviour regarding error
message:
$ snmp get 192.168.1.5 sysDescr.0 sysUpTime.0
sysDescr.0 = STRING: TOSHIBA e-STUDIO3505AC
sysUpTime.0 = Timeticks: (55587200) 6 day 10:24:32.00
$ snmp get 192.168.1.5 sysDescr.0 sysUpTime.0 xxx
snmp:
Any feedback on the relayd part?
On 9/25/19 8:58 AM, Martijn van Duren wrote:
> On 9/25/19 8:55 AM, Martijn van Duren wrote:
>> Hello,
>>
>> Mischa found that relayd's agentx support is pretty much unusable for
>> the uninitiated, because you have to know the tables beforehand.
>>
>> I managed
On Wed, Oct 02, 2019 at 03:48:27PM +0200, Jan Klemkow wrote:
> On Tue, Oct 01, 2019 at 11:34:09AM +1000, Jonathan Gray wrote:
> > On Tue, Oct 01, 2019 at 12:27:48AM +0200, Jan Klemkow wrote:
> > > After updating my router to current, the systems hangs during the boot.
> > > Maybe its caused by the
29 matches
Mail list logo
