Re: printf(3): extra parameters, %b token, and cpp antics

On Sun, Apr 23, 2017 at 06:01:18PM +1000, Damian McGuckin wrote: > On Sun, 23 Apr 2017, Jonathan Gray wrote: > > > http://man.openbsd.org/printf.9 > > Is the use of '%b' an addressing-out-of-bounds bug waiting to happen or is > there some sort of inbuilt protection that I cannot see? > >

nvi(1)

Dear, I started to use nvi(1) OpenBSD base editor, the manpage isn't clean about: 1- How copy and paste between xterms? Should I use Marks? is it possible or not? 2- On thinkpad and I usually select the text and paste with middle button, but I noticed the original text format isn't preserved, eg

Re: Bad kernel for OpenBSD 6.1 sparc64 ?

On Sat, Apr 22, 2017 at 04:31:02PM -0600, Jeff wrote: > Booting from sr0a seemed to do the trick to get my system upgraded to > 6.1. Unfortunately, it's now panicing frequently with, "panic: > psycho0: uncorrectable DMA error" but on different commands each time. Please follow the steps in

Re: BeagleBone Black GPIO

> Hello Misc, This is probably a discussion for tech@; anyway: > I'm trying to get a BeagleBone Black talking onewire and i2c via GPIO to > several off-board ICs through gpioow(4) and gpioiic(4) respectively. As a warning, let me say that tinkering with hardware like this isn't very high on the

Re: nvi(1)

Am 23. April 2017 15:30:02 MESZ schrieb Unixway1 : >Dear, > >I started to use nvi(1) OpenBSD base editor, the manpage isn't clean >about: >1- How copy and paste between xterms? > Should I use Marks? is it possible or not? Use one terminal with tmux, split it into

HP StorageWorks Ultrium 960 "misprobed" by mpi(4)

Dear misc readers, Recently I upgraded the SCSI card and the tape drive in my home server to the following: mpi0 at pci1 dev 2 function 0 "Symbios Logic 53c1030" rev 0x08: apic 3 int 7 mpi0: 0, firmware 1.3.39.0 scsibus2 at mpi0: 16 targets, initiator 7 st0 at scsibus2 targ 3 lun 0:

multi-USB flash did not work with bsd.rd but manual install fine

I have everything split apart into two flash drives to get enough diskspace. I couldn't get bsd.rd to work since not all of the partitions were mounted. Any reasonable fix good for this problem? I was doing upgrade to 6.1 from an older 6.1 -current. Since everything is mounted when system is

Re: flaky network connection after 6.1 upgrade

On Sun, Apr 23, 2017 at 10:46:56PM +0200, Stefan Sperling wrote: > Your other option is to stop reading now, forget about athn for now, > and use some other AP. I got mixed up between problem reports in my inbox. You have an athn client, not an athn AP. Sorry about that. A pcap file showing your

hotplugd attach script

I'm working on a gui tool for mounting usb sticks. I want it to launch from hotplugd, but so far I am unsuccessful. #/etc/hotplug/attach #!/bin/sh DEVCLASS=$1 DEVNAME=$2 case $DEVCLASS in 2) /usr/local/bin/xmount.py /dev/"$DEVNAME"a ;; esac The script is

Re: flaky network connection after 6.1 upgrade

On Sat, Apr 22, 2017 at 03:49:35PM -0500, Colton Lewis wrote: > I applied the patch and compiled a new kernel using the stable branch. > 11n and 11g both work now, > but with significantly worse performance than 11b. Downloads are about > 40% slower. > > $ curl

Re: understanding ldapd log error messages

Robert Klein wrote: > Hi, > > On Sat, 22 Apr 2017 21:55:58 -0400 > Predrag Punosevac wrote: > > > Predrag Punosevac write: > > > Hi misc, > > > > > > ldapd on one of my two ldap servers stop working overnight > > > > > > > ldapd died again

Re: understanding ldapd log error messages

> Use the options "-dv" at first. If you need to see th BER messages > use "-dvv" (see also "man ldapd"). Do you see anything in this snipped b,dc=org by any, in namespace dc=autonlab,dc=org Apr 23 23:19:09.481 [18682] found dn uid=rrabbany,ou=users,dc=autonlab,dc=org Apr 23 23:19:09.481

hotplugd attach script

Hi, i am not sure that the hotplug scripts are executed by the system user of the person that is sitting in front of the Computer. So, no rights to files or no display can be a Problem. How can the Computer know how inserted that device ?

Re: understanding ldapd log error messages

Hi, On Sat, 22 Apr 2017 21:55:58 -0400 Predrag Punosevac wrote: > Predrag Punosevac write: > > Hi misc, > > > > ldapd on one of my two ldap servers stop working overnight > > > > ldapd died again overnight. I noticed that this started happening not > right after the

printf(3): extra parameters, %b token, and cpp antics

I noticed some strange code in src/sys/arch/armv7/omap/ommmc.c This preprocessor define seems to map intr. state bit positions with strings describing them: 149 #define MMCHS_STAT_FMT "\20" \ 150 "\x09d_BADA" \ 151 "\x09c_CERR" \ 152 "\x098_ACE" \ 153 "\x096_DEB" \ 154

Re: printf(3): extra parameters, %b token, and cpp antics

On Sun, Apr 23, 2017 at 03:39:22AM -0400, Ian Sutton wrote: > I noticed some strange code in src/sys/arch/armv7/omap/ommmc.c > > This preprocessor define seems to map intr. state bit positions with > strings describing them: > > 149 #define MMCHS_STAT_FMT "\20" \ > 150 "\x09d_BADA" \ > 151

Re: printf(3): extra parameters, %b token, and cpp antics

On Sun, Apr 23, 2017 at 03:39:22AM -0400, Ian Sutton wrote: > > So through some combination of: > * CPP multi-string define with unclear hex escapes prepended > * printf() call with one too many parameters > * undocumented %b printf() token you didn't look at the right printf

Re: printf(3): extra parameters, %b token, and cpp antics

On Sun, 23 Apr 2017, Jonathan Gray wrote: http://man.openbsd.org/printf.9 Is the use of '%b' an addressing-out-of-bounds bug waiting to happen or is there some sort of inbuilt protection that I cannot see? Regards - Damian Pacific Engineering Systems International, 277-279 Broadway, Glebe