Re: Stop using direct syscall(2) from perl(1)

On Sun, Jul 09, 2023 at 01:29:58PM -0700, Andrew Hewus Fresh wrote: > Here is a patch to replace perl(1)'s use of syscall(2) with a dispatcher > that will call the libc function instead. > > I have to do some work on style before this is ready to commit, but it > should be ready for some testing.

Re: Stop using direct syscall(2) from perl(1)

-my $sb = "\0\0\0\0"; +my $sb = "\0" x 4096; That's pretty terrible. Does this language not have types?

Re: Stop using direct syscall(2) from perl(1)

On Sun, 9 Jul 2023 13:29:58 -0700 Andrew Hewus Fresh wrote: > +syscall_emulator.h Emulator to dispatch syscalls to libc This got installed as /usr/libdata/perl5/powerpc64-openbsd/CORE/syscall_emulator.h ExtUtils::MakeMaker is using cc -DHAS_SYSCALL_EMULATOR to build my XS module; the

Re: cron -n/-s/-q whitespace and /etc/crontab

On Wed, 19 Jul 2023 16:44:23 +0100, Stuart Henderson wrote: > When /etc/crontab is used, cron only skips over a single whitespace > character between the username and -n/-s/-q flags; more than one and > the flag is taken as part of the command: > > printf '*\t*\t*\t*\t*\tnobody\t-n true 1\n' | doa

cron -n/-s/-q whitespace and /etc/crontab

When /etc/crontab is used, cron only skips over a single whitespace character between the username and -n/-s/-q flags; more than one and the flag is taken as part of the command: printf '*\t*\t*\t*\t*\tnobody\t-n true 1\n' | doas tee -a /etc/crontab printf '*\t*\t*\t*\t*\tnobody\t\t-n true 2\n' |

OpenBSD Errata: July 19, 2023 (ssh-agent)

Errata patches for ssh-agent have been released for OpenBSD 7.2 and 7.3. Binary updates for the amd64, i386 and arm64 platform are available via the syspatch utility. Source code patches can be found on the respective errata page: https://www.openbsd.org/errata72.html https://www.openbsd.org

Re: patch: partially fix interactive mode

OK florian On 2023-07-19 13:17 +02, Theo Buehler wrote: > The addition of unveil broke interactive mode since ask() assumes the > default answer if it fails to open _PATH_TTY. Questions are only asked > if neither force nor batch mode is activated, so condition on those. > > It seams cleaner to d

patch: partially fix interactive mode

The addition of unveil broke interactive mode since ask() assumes the default answer if it fails to open _PATH_TTY. Questions are only asked if neither force nor batch mode is activated, so condition on those. It seams cleaner to do unveil _PATH_TTY than to add a tty pledge since as far as I can s

Re: assign wsdisplay0 to the glass console

> Date: Wed, 19 Jul 2023 16:12:59 +0900 (JST) > From: YASUOKA Masahiko > > Hi, > > I noticed that the keyboard doesn't work for RAMDISK kernel on HP DL20 > Gen10. The kernel assigns wsdisplay0 for VGA and wsdisplay1 for > efifb. But actually the glass console is efieb but it doesn't have > any

ixl(4): protect admin queue with mutex

Hi, there is an issue with the admin queue of ixl(4) which leads into the following panic when the link state changes: uvm_fault(0x818005f8, 0x18, 0, 2) -> e kernel: page fault trap, code=0 Stopped at ixl_intr0+0xca: movq%rdx,0x18(%rax) TIDPIDUID PRFLAGS PFLAG

assign wsdisplay0 to the glass console

Hi, I noticed that the keyboard doesn't work for RAMDISK kernel on HP DL20 Gen10. The kernel assigns wsdisplay0 for VGA and wsdisplay1 for efifb. But actually the glass console is efieb but it doesn't have any keyboard assigned because the keyboard is assigned to wsdisplay0. GENERIC kernel does