(Maybe to be moved to misc@)
Dear OpenBSD tech@,
Thunderbolt support would be awesome. Especially it would allow the use
of additional M.2 NVMe SSD:s on a laptop at full performance.
Thunderbolt support would also allow the use of an AMDGPU via a PCIe
chassi, as well as enable the use of 10gbps
Hi Klemens,
Klemens Nanni wrote on Sat, Mar 21, 2020 at 12:49:20AM +0100:
> On Fri, Mar 20, 2020 at 04:53:19PM +0100, Ingo Schwarze wrote:
>> I don't feel very strongly about that, but i think .Cm does make
>> slightly more sense for primaries than .Fl (and .Ic is probably
>> acceptable, too,
On Fri, Mar 20, 2020 at 04:53:19PM +0100, Ingo Schwarze wrote:
> Not really. In the POSIX sense, options are indeed options while
> primaries are arguments. That has implications, for example that
> all options must precede all primaries.
Fair point.
> I don't feel very strongly about that, but
Hi Klemens,
Klemens Nanni wrote on Fri, Mar 20, 2020 at 12:12:39AM +0100:
> In both command line usage and manual output format, find's options
> and primaries behave the same,
Not really. In the POSIX sense, options are indeed options while
primaries are arguments. That has implications, for
You could do:
expr `date +%s` - `sysctl -n kern.boottime`
On Fri, 20 Mar 2020 at 12:54, Alex Naumov wrote:
>
> Hi,
>
> this patch adds a new option to uptime(1) that allows to see the length of
> time the system has been up in seconds.
> Patch includes documentation (man-page) update.
>
>
On Fri, Mar 20, 2020 at 01:44:22PM +0100, Alex Naumov wrote:
> this patch adds a new option to uptime(1) that allows to see the length of
> time the system has been up in seconds.
Please don't. Both uptime(1) and w(1) has had several options removed
over the past - cleaning, simplyfying and
Hi,
this patch adds a new option to uptime(1) that allows to see the length of
time the system has been up in seconds.
Patch includes documentation (man-page) update.
Example:
$ uptime
1:26PM up 1:28, 1 user, load averages: 0.00, 0.00, 0.00
$ uptime -S
1:26PM 5308 secs, 1 user, load
On Tue 2020.01.28 at 13:44 -0500, Okan Demirmen wrote:
> Hi,
>
> The below refactors client cycling to be available from a client context
> instead of limiting to a screen context; this allows bindings for the 4
> related functions (window-{,r}cycle,window-{,r}cycle-ingroup) for either
> key or
> Date: Fri, 20 Mar 2020 12:50:58 +0100
> From: Martin Pieuchot
>
> On 20/03/20(Fri) 12:01, Mark Kettenis wrote:
> > > Date: Fri, 20 Mar 2020 11:54:59 +0100
> > > From: Martin Pieuchot
> > >
> > > As explained in my recent ix(4) diff, using a define when an arch
> > > doesn't support a given
On 20/03/20(Fri) 12:01, Mark Kettenis wrote:
> > Date: Fri, 20 Mar 2020 11:54:59 +0100
> > From: Martin Pieuchot
> >
> > As explained in my recent ix(4) diff, using a define when an arch
> > doesn't support a given function makes the compiler complain that
> > the arguments are unused:
> >
> >
> Date: Fri, 20 Mar 2020 11:54:59 +0100
> From: Martin Pieuchot
>
> As explained in my recent ix(4) diff, using a define when an arch
> doesn't support a given function makes the compiler complain that
> the arguments are unused:
>
> /sys/dev/pci/if_ix.c:1789:21: error: unused variable
As explained in my recent ix(4) diff, using a define when an arch
doesn't support a given function makes the compiler complain that
the arguments are unused:
/sys/dev/pci/if_ix.c:1789:21: error: unused variable 'dummy'
[-Werror,-Wunused-variable]
pci_intr_handle_t
On 19/03/20(Thu) 20:53, Klemens Nanni wrote:
> Changing file permissions on /dev/dt to allow non-root access and a
> simple `btrace -l' as non-root user already dt(4)'s KASSERT()s.
Would you mind sharing traces?
> Instead of panicing the machine I think we can return early just like
> in other
On 19/03/20(Thu) 19:58, Klemens Nanni wrote:
> On Thu, Mar 19, 2020 at 07:25:05PM +0100, Martin Pieuchot wrote:
> > > +.It Fn exit
> > > +Terminate with exit code 0
> >
> > I don't see the value of mentioning the exit code. What about:
> >
> > Terminate the execution.
> "Terminate" is already
On Fri, Mar 20, 2020 at 12:12:39AM +0100, Klemens Nanni wrote:
morning.
> In both command line usage and manual output format, find's options
> and primaries behave the same, but their mdoc(7) markup is different and
> therefore causes different tag names:
>
i'm not sure what you mean by
15 matches
Mail list logo