On Fri, Dec 21, 2018 at 06:26:54PM +0100, Solene Rapenne wrote:
> Otto Moerbeek wrote:
> > On Thu, Dec 20, 2018 at 09:31:45AM +0100, Landry Breuil wrote:
> >
> > > On Thu, Dec 20, 2018 at 09:26:33AM +0100, Solene Rapenne wrote:
> > > > Hi
> > > >
> > > > fstab(5) has an example for a nfs
I just have to say that that I agree with Ingo 100%.
There are just so many ways that html could be used besides just
typical static manpage styles.
inlining could be a good case, but only for a limited set of uses.
I would really cringe at having to strip out inline CSS.
Anyone who just prefers
Ingo Schwarze wrote:
> What about making -O style= *compulsory* unless "option style" is
> defined in man.conf(5)? Just error out when no style sheet is
> configured? That can be combined with inlining the full set of
> rules when -O style=inline is explicitly specified.
This seems
Hi Raphael,
Raphael Graf wrote on Sat, Dec 22, 2018 at 03:32:45PM +0100:
> The html output contains nested anchor tags if the TABLE OF CONTENTS
> has a second level.
> For example, see http://man.openbsd.org/mdoc
>
> The diff closes the anchor tag before printing the 'ul' of the second level.
The html output contains nested anchor tags if the TABLE OF CONTENTS
has a second level.
For example, see http://man.openbsd.org/mdoc
The diff closes the anchor tag before printing the 'ul' of the second level.
Index: mdoc_html.c
Allow the mpw(4) interface to establish VPLS tunnel over an IPv6-only MPLS
core.
This is the mpw(4) bit.
It requires the kernel diff from
https://marc.info/?l=openbsd-tech=154513171617201=2 to avoid panic.
---
pe1# cat /etc/ldpd.conf
Allow the mpw(4) interface to establish VPLS tunnel over an IPv6-only MPLS core.
This is the ifconfig(8) bit providing display and configuration of IPv6
neighbor on mpw(4) interface.
pe1# ifconfig mpw0
mpw0: flags=51 mtu 1500
index 7 priority 0 llprio 3
encapsulation-type
Adjust cpsw for linux 4.20 device tree changes.
5f681f41fe17 ARM: dts: am335x: Replace remaining legacy phy_id with phy-handle
e99c4d576254 ARM: dts: dra62x-j5eco-evm: get rid of phy_id property
3a25128c02f6 ARM: dts: dm8148-t410: get rid of phy_id property
abf878ddfdf2 ARM: dts: dm8148-evm: get
Theo de Raadt wrote:
> If you are going to introduce such complicated semantics, please
> include a proposal for the manual page change so that we can see
> if this can be simply described. Being dimply described in the
> manual page is a marker for whether a change is suitable.
Stealing some
But this doesn't describe the semantics of your diff.
You have skipped details of your technical proposal. Perhaps those
details aren't needed? Or perhaps they should be documented.
> Theo de Raadt wrote:
> > If you are going to introduce such complicated semantics, please
> > include a
On Sat, Dec 22 2018, "Ted Unangst" wrote:
> Daniel Jakots wrote:
>> Hi,
>>
>> With nc(1) you can do:
>> nc -zv example.com 80
>> or
>> nc -zv example.com http
>> which does the same. This works well unless the service name has a dash:
>> $ nc -zv example.com syslog-tls
>> nc: service "tls"
On 2018/12/22 16:44, Daniel Jakots wrote:
> Hi,
>
> With nc(1) you can do:
> nc -zv example.com 80
> or
> nc -zv example.com http
> which does the same. This works well unless the service name has a dash:
> $ nc -zv example.com syslog-tls
> nc: service "tls" unknown
>
> This is because nc(1) is
On Sat, Dec 22, 2018 at 06:53:24PM -0500, Ted Unangst wrote:
> @@ -393,7 +393,7 @@ option is given).
> .Ar port
> can be a specified as a numeric port number, or as a service name.
stray ^ article that can be zapped with this diff while here.
> Ports may be specified in a range of the form
Stuart Henderson wrote:
> But I can't imagine scanning a range by name as being much used
> (tcpmux-socks or something just doesn't make sense).
>
> What I think would be least disruptive is to continue to allow - where
> the rest of the parameter is numeric. For alphabetic parameters try
>
Hi Ted,
Ted Unangst wrote on Sat, Dec 22, 2018 at 12:13:35PM -0500:
> Ingo Schwarze wrote:
>> What about making -O style= *compulsory* unless "option style" is
>> defined in man.conf(5)? Just error out when no style sheet is
>> configured? That can be combined with inlining the full set of
>>
Daniel Jakots wrote:
> Hi,
>
> With nc(1) you can do:
> nc -zv example.com 80
> or
> nc -zv example.com http
> which does the same. This works well unless the service name has a dash:
> $ nc -zv example.com syslog-tls
> nc: service "tls" unknown
>
> This is because nc(1) is able to do some port
Here is a dmesg and acpidump from another HP Stream laptop.
Running with pcidevs patch and SDMMC_DEBUG turned on.
OpenBSD 6.4-current (SDMMC_DEBUG) #280: Wed Dec 19 23:44:03 EST 2018
xxx@xxx:/usr/src/sys/arch/amd64/compile/SDMMC_DEBUG
real mem = 4102090752 (3912MB)
avail mem = 3968425984
Hi,
With nc(1) you can do:
nc -zv example.com 80
or
nc -zv example.com http
which does the same. This works well unless the service name has a dash:
$ nc -zv example.com syslog-tls
nc: service "tls" unknown
This is because nc(1) is able to do some port scanning and the
delimiter used for the
On Sat, Dec 22, 2018 at 04:44:14PM -0500, Daniel Jakots wrote:
> Here's a diff that change the delimiter to ":". This breaks existing
> scripts but it would make the syntax like pf.conf instead of using
> another symbol for a port range.
Changing it to double-colon for sanity and consistency seems
If you are going to introduce such complicated semantics, please
include a proposal for the manual page change so that we can see
if this can be simply described. Being dimply described in the
manual page is a marker for whether a change is suitable.
Ted Unangst wrote:
> Daniel Jakots wrote:
>
20 matches
Mail list logo
