Humbly want to state that if you or anyone can run a alpine-linux 64bit vm on
current for 30 minutes, then this bug can be trashed. Maybe its my computer or
my installation.
My responses Inline.
Due apologies, will do my best to get these reports right.
Thanks,
; Long
‐‐‐ Original Message ‐‐‐
On Friday, February 15, 2019 9:48 PM, Mike Larkin wrote:
> On Fri, Feb 15, 2019 at 05:53:11PM +, longwuyuan wrote:
>
> > I started vmd with -d -vv in foreground b
On Sat, 16 Feb 2019 01:48:11 +0100, Christian Weisgerber wrote:
> I think tod() already has the required logic, but it doesn't handle
> the case where the time is only past by minutes.
Even better. OK millert@
- todd
That looks like the correct fix.
ok deraadt
> > The manual is correct. Below is one way to fix this, though the
> > logic probably belongs in tod() itself.
>
> I think tod() already has the required logic, but it doesn't handle
> the case where the time is only past by minutes.
>
> Index: pars
Todd C. Miller:
> The manual is correct. Below is one way to fix this, though the
> logic probably belongs in tod() itself.
I think tod() already has the required logic, but it doesn't handle
the case where the time is only past by minutes.
Index: parsetime.c
===
On Fri, 15 Feb 2019 22:36:08 +0100, Christian Weisgerber wrote:
> The at(1) man page says:
> at allows some moderately complex timespec specifications. It accepts
> times of the form HHMM or HH:MM to run a job at a specific time of day.
> (If that time is already past, the next day i
On Fri, Feb 15, 2019 at 05:53:11PM +, longwuyuan wrote:
> I started vmd with -d -vv in foreground but there is not a single message
> related to the locked up alpine linux VM
>
You really need to work on these reports. I'll give it one more try.
1. How did you install this VM? Did you use t
OpenBSD 6.4-current (GENERIC.MP) #2: Thu Feb 14 21:19:17 CET 2019
na...@ariolc.mips.inka.de:/sys/arch/amd64/compile/GENERIC.MP
The at(1) man page says:
at allows some moderately complex timespec specifications. It accepts
times of the form HHMM or HH:MM to run a job at a specific time
On Fri, Feb 15, 2019 at 06:06:05PM +0100, mb...@mbuhl.me wrote:
>
> Hello,
>
> the following change lead to a kernerl panic after running
> /usr/src/regress/usr.sbin/bgpd/integrationtests/network_statement.sh
>
> https://cvsweb.openbsd.org/src/sys/net/route.c?rev=1.381&content-type=text/x-cvswe
> I started vmd with -d -vv in foreground but there is no message related to a
> locked up alpine linux VM. Uuntu works
>
> System : OpenBSD 6.4
> Details : OpenBSD 6.4-current (GENERIC.MP) #724: Thu Feb 14 23:08:31
> MST 2019
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compi
> le/GENERIC
I started vmd with -d -vv in foreground but there is not a single message
related to the locked up alpine linux VM
System : OpenBSD 6.4
Details : OpenBSD 6.4-current (GENERIC.MP) #724: Thu Feb 14 23:08:31
MST 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd6
Hello,
the following change lead to a kernerl panic after running
/usr/src/regress/usr.sbin/bgpd/integrationtests/network_statement.sh
https://cvsweb.openbsd.org/src/sys/net/route.c?rev=1.381&content-type=text/x-cvsweb-markup
> CVSROOT: /cvs
> Module name: src
> Changes by: d...@cvs.o
On 11/02/19(Mon) 18:58, Artturi Alm wrote:
> On Mon, Feb 11, 2019 at 02:15:43PM -0200, Martin Pieuchot wrote:
> > On 10/02/19(Sun) 20:46, Artturi Alm wrote:
> > > Hi,
> > >
> > > rather than patching uhub(4), i figured this would be less not-ok,
> > > if not ok as-is, given its way more limited sco
13 matches
Mail list logo