On Fri, Apr 29, 2022 at 11:58:52AM +0200, Claudio Jeker wrote:
> The callback currently uses struct rttimer as an argument but the code
> only needs the rtt_tableid element from there. Change the callbacks to
> be of the form void (*rtt_callback)(struct rtentry *r, u_int rtableid)
>
> Also change
On Thu, Apr 28, 2022 at 08:54:02PM -0500, Scott Cheloha wrote:
> On Thu, Sep 17, 2020 at 06:29:48PM -0500, Scott Cheloha wrote:
> > [...]
> >
> > Using nanosleep(2) to print the stats periodically causes the period
> > to drift. If you use setitimer(2) it won't drift.
> >
> > ok?
>
> 19 month b
Angelo writes:
> > > > If that's the case, then it would be good if we can keep speaker(4).
> > > > I have multiple headless systems at home which start to beep under
> > > > certain conditions, to alert me.
Just as an aside, in the mid-90s I hacked FreeBSD's morse(6) to
send the real thing out /
On Fri, Apr 29, 2022 at 06:33:04PM +0200, Mark Kettenis wrote:
> > From: Scott Cheloha
> > Date: Fri, 29 Apr 2022 11:13:19 -0500
> >
> > > On Apr 29, 2022, at 09:33, Angelo wrote:
> > >
> > > Hello
> > >
> > >> On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
> > >> speaker(4) i
On Fri, Apr 29, 2022 at 04:46:23PM +0200, Florian Obser wrote:
> So I got a yubikey and I wanted to try fido2 with ssh. I was a bit
> unsure on how to generate a key (hint: it's just ssh-keygen -t
> ed25519-sk). So I went and ask the Internet. I ran into some page that
> suggested that you need to
> From: Scott Cheloha
> Date: Fri, 29 Apr 2022 11:13:19 -0500
>
> > On Apr 29, 2022, at 09:33, Angelo wrote:
> >
> > Hello
> >
> >> On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
> >> speaker(4) is a whimsical thing, but I don't think we should have a
> >> dedicated chiptune i
> On Apr 29, 2022, at 10:40, Jeremie Courreges-Anglas wrote:
>
> On Thu, Apr 28 2022, Scott Cheloha wrote:
>> speaker(4) is a whimsical thing, but I don't think we should have a
>> dedicated chiptune interpreter in the kernel.
>
>> This patch unhooks the driver and the manpage from the build.
> On Apr 29, 2022, at 09:33, Angelo wrote:
>
> Hello
>
>> On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
>> speaker(4) is a whimsical thing, but I don't think we should have a
>> dedicated chiptune interpreter in the kernel.
>>
>> This patch unhooks the driver and the manpage f
> On Apr 29, 2022, at 10:06, j...@entropicblur.com wrote:
>
> On 2022-04-29 08:31, Angelo wrote:
>> Hello
>>> On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
>>> speaker(4) is a whimsical thing, but I don't think we should have a
>>> dedicated chiptune interpreter in the kernel.
>>
On Thu, 28 Apr 2022 20:54:02 -0500, Scott Cheloha wrote:
> Once again, using nanosleep(2) here to print the stats periodically is
> flawed. The period will drift. Using setitimer(2)/sigsuspend(2) is
> better.
Yes, I agree that an interval timer is a better fit.
> While here:
>
> - We don't nee
On Thu, Apr 28 2022, Scott Cheloha wrote:
> speaker(4) is a whimsical thing, but I don't think we should have a
> dedicated chiptune interpreter in the kernel.
> This patch unhooks the driver and the manpage from the build. The
> driver is built for alpha, amd64, and i386.
>
> A subsequent patch
On 2022-04-29 08:31, Angelo wrote:
Hello
On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
speaker(4) is a whimsical thing, but I don't think we should have a
dedicated chiptune interpreter in the kernel.
This patch unhooks the driver and the manpage from the build. The
driver is
Scott Cheloha wrote:
> speaker(4) is a whimsical thing, but I don't think we should have a
> dedicated chiptune interpreter in the kernel.
>
> This patch unhooks the driver and the manpage from the build. The
> driver is built for alpha, amd64, and i386.
>
> A subsequent patch will move all rel
So I got a yubikey and I wanted to try fido2 with ssh. I was a bit
unsure on how to generate a key (hint: it's just ssh-keygen -t
ed25519-sk). So I went and ask the Internet. I ran into some page that
suggested that you need to give a ton of options to ssh-keygen,
including -o resident without expl
Hello
On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
> speaker(4) is a whimsical thing, but I don't think we should have a
> dedicated chiptune interpreter in the kernel.
>
> This patch unhooks the driver and the manpage from the build. The
> driver is built for alpha, amd64, and
On Thu, Oct 14, 2021 at 04:13:18PM -0500, Scott Cheloha wrote:
>
> [...]
>
> When we compute high resolution time, both in the kernel and in libc,
> we get a 32-bit (or smaller) value from the active timecounter and
> scale it up into a 128-bit bintime.
>
> The scaling math currently looks like t
On Thu, Apr 28, 2022 at 12:28:45PM +0200, Martin Pieuchot wrote:
> rw_enter(9) can sleep. When the lock is finally acquired by the
> pagedaemon the previous check might no longer be true and the page
> could be busy. In this case we shouldn't touch it.
>
> Diff below recheck for PG_BUSY after ac
The callback currently uses struct rttimer as an argument but the code
only needs the rtt_tableid element from there. Change the callbacks to
be of the form void (*rtt_callback)(struct rtentry *r, u_int rtableid)
Also change the default rttimer callback (in case the function is NULL)
to only handl
On Thu, Apr 28, 2022 at 06:34:00AM -0500, Scott Cheloha wrote:
> speaker(4) is a whimsical thing, but I don't think we should have a
> dedicated chiptune interpreter in the kernel.
>
> This patch unhooks the driver and the manpage from the build. The
> driver is built for alpha, amd64, and i386.
19 matches
Mail list logo
