>On 12/25/17, Otto Moerbeek wrote:
>> On Tue, Dec 26, 2017 at 12:31:02AM +0100, Klemens Nanni wrote:
>>
>>> On Mon, Dec 25, 2017 at 03:57:00PM -0700, Theo de Raadt wrote:
>>> > I think this is a silly solution, and the documentation is clear
>>> > enough.
>>> The manual page
>On Mon, Dec 25, 2017 at 03:57:00PM -0700, Theo de Raadt wrote:
>> I think this is a silly solution, and the documentation is clear
>> enough.
>The manual page certainly is clear enough but the current error message
>is logically wrong, as there are sufficient Xs *in* `XXs' but just
>not at
On 12/25/17, Otto Moerbeek wrote:
> On Tue, Dec 26, 2017 at 12:31:02AM +0100, Klemens Nanni wrote:
>
>> On Mon, Dec 25, 2017 at 03:57:00PM -0700, Theo de Raadt wrote:
>> > I think this is a silly solution, and the documentation is clear
>> > enough.
>> The manual page certainly is
On Tue, Dec 26, 2017 at 12:31:02AM +0100, Klemens Nanni wrote:
> On Mon, Dec 25, 2017 at 03:57:00PM -0700, Theo de Raadt wrote:
> > I think this is a silly solution, and the documentation is clear
> > enough.
> The manual page certainly is clear enough but the current error message
> is logically
On Tue, Dec 26, 2017 at 01:15:35PM +0800, Kevin Lo wrote:
> The diff below adds support for the "next-generation" clock and pinctrl
> bindings for the Allwinner A33.
>
> Tested on my Banana Pi M2 Magic. dmesg: http://ix.io/DoB
> ok?
>
> Index: sys/dev/fdt/ehci_fdt.c
>
The diff below adds support for the "next-generation" clock and pinctrl
bindings for the Allwinner A33.
Tested on my Banana Pi M2 Magic. dmesg: http://ix.io/DoB
ok?
Index: sys/dev/fdt/ehci_fdt.c
===
RCS file:
On Mon, Dec 25, 2017 at 03:57:00PM -0700, Theo de Raadt wrote:
> I think this is a silly solution, and the documentation is clear
> enough.
The manual page certainly is clear enough but the current error message
is logically wrong, as there are sufficient Xs *in* `XXs' but just
not at the end
I think this is a silly solution, and the documentation is clear
enough.
How did this happen to you? Show the place where it happened to you.
Would the text you propose actually have saved you 1 second of time
to help you realize what was wrong? I don't think so. If you
weren't familiar that
Hi,
in my use-case urndis is likely never there at boot, and while i've
been aware of ifstated(8) all the time, the relevant man pages have
felt dry w/regards giving something trivial/!carp, to make me skip
setting this up again for far too long:)
/etc/examples/ifstated.conf also supported my
On Mon, Dec 25, 2017 at 08:36:07PM +, Stuart Henderson wrote:
> On 2017/12/25 20:52, Klemens Nanni wrote:
> > from mktemp(1):
> >
> > The template may be any filename with at least six ‘Xs’ appended
> > to it, for example /tmp/tfile.XX.
> >
> > Now when a template contains
On 2017/12/25 20:52, Klemens Nanni wrote:
> from mktemp(1):
>
> The template may be any filename with at least six ‘Xs’ appended
> to it, for example /tmp/tfile.XX.
>
> Now when a template contains but does not end in six Xs, the error
> message may imply errornous behaviour
from mktemp(1):
The template may be any filename with at least six ‘Xs’ appended
to it, for example /tmp/tfile.XX.
Now when a template contains but does not end in six Xs, the error
message may imply errornous behaviour instead of bad usage:
$ mktemp XX
Hi all,
Sorry to keep harping on this script stuff, but I'd really like to see
this committed. I've just upgraded my laptop while doing some
vlan-bridging debugging and suddenly script(1) lost my new favorite
feature.
The manpage bits are OK jmc@; job@ and ian@ (off-list) OK'd the diff.
Is
13 matches
Mail list logo