Re: posix_spawn(3): explain that handling NULL envp is an extension

Having never heard of posix_spawn(3), I read the full manpage and (besides wondering "what's the point"), found that it's misspelled Ed Schouten's name: Index: posix_spawn.3 === RCS file: /cvs/src/lib/libc/gen/posix_spawn.3,v

Re: remove net.inet6.ip6.soiikey from userland

On Sat, May 20, 2023 at 05:33:11PM +0200, Florian Obser wrote: | In case this turns out to be useful for unlocking work in the kernel. | | It's a minimum diff, if we want to go this way we probably want to move | init_soiikey() to the engine process and stop bouncing through the main | process

Re: ure(4): add support for RTL8153D

Hi Kevin, This seems to work fine on my machine. The ure0 is built into my monitor: ure0 at uhub9 port 3 configuration 1 interface 0 "Realtek USB 10/100/1000 LAN" rev 3.20/33.00 addr 4 ure0: RTL8153D (0x7420), address c8:4b:d6:af:a7:8d I can get both v4 and v6 addresses over this interface

Re: Recognize Kingston KC3000 NVME SSD

ping Is this worth it? Rebased diff at the bottom for convenience On Sun, Mar 19, 2023 at 05:12:18PM +0100, Paul de Weerd wrote: | I put a Kingston KC3000 NVME SSD[1] in my new machine. This diff | recognizes that device: | | Index: pcidevs

ntpd: log hostname of constraint with IP address

While debugging some NTP weirdness, I noticed an outlier amongst the constraints (all except one had an offset less than 1s, the one outlier was over 7 hours off). Unfortunately, I couldn't tell which constraint had the outlier, because the IP's rDNS didn't correspond to one of the constraints

Recognize Kingston KC3000 NVME SSD

I put a Kingston KC3000 NVME SSD[1] in my new machine. This diff recognizes that device: Index: pcidevs === RCS file: /cvs/src/sys/dev/pci/pcidevs,v retrieving revision 1.2026 diff -u -p -r1.2026 pcidevs --- pcidevs 19 Mar 2023

add Aquantia AQC113CS to pcidevs

My new motherboard has a 10GB/s interface that doesn't work with -current. It's this thing: --- pcidump -v 7:0:0 - 7:0:0: Aquantia unknown 0x: Vendor ID: 1d6a, Product ID: 94c0 0x0004: Command: 0006, Status: 0010

Re: ACPI diff for testing

Hi Mark, On Thu, Mar 09, 2023 at 05:23:55PM +0100, Mark Kettenis wrote: | > Date: Thu, 09 Mar 2023 14:48:25 +0100 | > From: Mark Kettenis | > | > The diff below fixes an issue with the way we attach "APCI devices". | > As with all ACPI diffs, this may potentially introduce regressions, so | >

Re: refactor mbuf parsing on driver level

On Tue, Feb 07, 2023 at 01:09:25AM +0100, Christian Weisgerber wrote: | Jan Klemkow: | | > > igc(4) has very similar code, but I don't have access to a machine | > > with that hardware. | > | > Send me an ssh-key and I give you access to this machine: | | Alternatively, here's the diff, so

Re: Making wscons a bit more like xterm

On Wed, Jan 04, 2023 at 05:42:31PM -0300, Crystal Kolipe wrote: | Hopefully it'll fix the problem. Tested with tmux, the spurious ^@'s are now indeed gone. I see there's a new diff available, so I'll try that out in a bit. Paul -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+

Re: Making wscons a bit more like xterm

On Wed, Jan 04, 2023 at 02:33:57PM -0300, Crystal Kolipe wrote: | On Wed, Jan 04, 2023 at 04:42:55PM +0100, Paul de Weerd wrote: | > Hi Crystal, | > | > I tried your patch on my laptop. With it applied, and my TERM set to | > 'xterm', I do get colors in mutt and tmux. | | Gr

Re: Making wscons a bit more like xterm

Hi Crystal, I tried your patch on my laptop. With it applied, and my TERM set to 'xterm', I do get colors in mutt and tmux. The latter, however, shows '^@^@' before the PS1 prompt upon starting a new session (`tmux new`), behavior I don't see with a 'real' xterm. I like the idea, thanks for

Re: dhcpleased(8): close unneeded bpf FDs

On Thu, Jul 14, 2022 at 08:20:41AM +0200, Florian Obser wrote: | On 2022-07-12 14:35 +02, Florian Obser wrote: | > When the autoconf flag flaps around we might end up with multiple bpf | > FDs in flight. Things then get confusing. The kernel tells us we can | > read from the bpf FD but the data

Re: New hw.perfpolicy behavior

On Tue, Nov 02, 2021 at 12:30:56PM -0600, Theo de Raadt wrote: | Paul de Weerd wrote: | | > A recent commit by Theo changed the hw.perfpolicy behavior to always | > run at full speed when AC power is on. This means that my workstation | > (and servers, once I upgrade them) now

New hw.perfpolicy behavior

A recent commit by Theo changed the hw.perfpolicy behavior to always run at full speed when AC power is on. This means that my workstation (and servers, once I upgrade them) now consumes significantly more power, even though they usually idle. [weerd@pom] $ sysctl

Re: Unwind + NSD usage question

On Tue, Sep 28, 2021 at 12:25:30PM +0200, Paul de Weerd wrote: | Otto's answer is a good solution, but I wanted to share mine: Read Otto's answer too fast - he's basically talking about the same solution I think. Unbound has another alternative where you configure it to serve specific records

Re: Unwind + NSD usage question

Hi, Why do you set your NSD as a forwarder? How is unbound supposed to know what queires should go to your NSD versus the rest of the internet? Otto's answer is a good solution, but I wanted to share mine: If you have your NSD setup running to only serve those 'router.home.arpa' records and

Re: allow KARL with config(8)'d kernels

On Tue, Sep 07, 2021 at 07:57:55PM +0200, Robert Nagy wrote: | On 07/09/21 19:31 +0200, Paul de Weerd wrote: | > Hi all, | > | > On Tue, Sep 07, 2021 at 02:30:43PM +0200, Robert Nagy wrote: | > | /etc/reorder_kernel.conf | > | > Thank you for your suggest Robert! In the m

Re: allow KARL with config(8)'d kernels

1970 00:00:00 - +++ libexec/reorder_kernel/bsd.re-config.5 7 Sep 2021 16:16:28 - @@ -0,0 +1,46 @@ +.\"$OpenBSD$ +.\" +.\" Copyright (c) 2021 Paul de Weerd +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose

Re: allow KARL with config(8)'d kernels

t the existance of this mechanism | in the config(8) and boot_config(8) manual pages, a better name will | sneak up on us. | | Paul de Weerd wrote: | | > Hi Theo, | > | > That's a good point, but I have no better alternative. kernel.conf | > was the best I could come up with, as it is a configur

reduce debug logging from slowcgi

Hi all, On a busy-ish site, I found that slowcgi is doing quite excessive logging: every single environment variable is logged on a separate logline. There's at least 17 variables per hit, but I've seen it go up to 35. If you're writing debug logs from syslog, that adds up rather quickly. Of

Re: allow KARL with config(8)'d kernels

scoverable. | | Paul de Weerd wrote: | | > Got some more positive feedback off-list, which reminded me that | > there's a small piece missing: | > | > Index: changelist | > === | > RCS file: /home/Open

Re: allow KARL with config(8)'d kernels

1970 00:00:00 - +++ libexec/reorder_kernel/kernel.conf.524 Aug 2021 07:23:07 - @@ -0,0 +1,46 @@ +.\"$OpenBSD$ +.\" +.\" Copyright (c) 2021 Paul de Weerd +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" p

Re: allow KARL with config(8)'d kernels

Robert, Sebastien and Stuart, Thanks for your constructive and postive feedback. Combined with some off-list (positive) feedback, it suggests this is at least worth further consideration. On Tue, Aug 24, 2021 at 08:05:37PM +0200, Robert Nagy wrote: | I am happy to see this. All for it. Did you

allow KARL with config(8)'d kernels

00 - +++ kernel.conf.5 24 Aug 2021 07:23:07 - @@ -0,0 +1,46 @@ +.\"$OpenBSD$ +.\" +.\" Copyright (c) 2021 Paul de Weerd +.\" +.\" Permission to use, copy, modify, and distribute this software for any +.\" purpose with or without fee is hereby granted,

Re: ucc(4): consumer control keyboard device driver

Hi Anton, Thanks - I've applied your diff and built a kernel with it. Full dmesg (both before and after) at the end of this mail, diff is: -uhid2 at uhidev3 reportid 3: input=3, output=0, feature=0 +ucc0 at uhidev3 reportid 3 keys 24, mappings 7 +wskbd3 at ucc0 mux 1 -wskbd3 at ukbd2 mux 1

ntpd constraints and caching proxies (CDNs)

Hi all, I was investigating some 'unsupported date format' messages that ntpd was logging and found that one constraint server served a time that was quite a ways off from actual time. Turns out that the website in question is fronted by some CDN that caches the page, including the date:-header.

Re: httpd(8): fastcgi & Content-Length: 0

For the record: I tested this on a WordPress instance and it fixed the problem for me. It was also visible in roundcubemail and wikimedia (firefox and safari showed the issue, chrome on the company laptop did not). Thanks Florian! Paul On Wed, May 19, 2021 at 08:44:47PM +0200, Florian Obser

Re: setitimer(2): don't round up it_value

Hi Scott, Thanks for this work! I see significant improvement with my test code (see below; obviously focussing quite specificially on one thing). Before your diff (snapshot from a few days ago; OpenBSD 6.9-current (GENERIC.MP) #1: Mon May 3 11:04:25 MDT 2021) I got: [weerd@pom] $ ./measure

Re: find -exec util {} arg + confusion

On Tue, Nov 17, 2020 at 01:06:05AM +0100, Alexander Hall wrote: | On Mon, Nov 16, 2020 at 09:04:53AM +0100, Paul de Weerd wrote: | > Hi Alexander, | > | > On Sun, Nov 15, 2020 at 10:22:32PM +0100, Alexander Hall wrote: | > | I googled for "POSIX find", and hit th

Re: find -exec util {} arg + confusion

Hi Andreas, On Mon, Nov 16, 2020 at 08:53:36AM +0100, Andreas Kusalananda Kähäri wrote: | On Thu, Nov 12, 2020 at 08:51:22PM +0100, Paul de Weerd wrote: | > Hi all, | > | > I misread find(1) and did: | > | > [weerdpom] $ find path/to/cam -name \*.JPG -exec cp {} path/to/store +

Re: find -exec util {} arg + confusion

Hi Alexander, On Sun, Nov 15, 2020 at 10:22:32PM +0100, Alexander Hall wrote: | I googled for "POSIX find", and hit this: | | https://pubs.opengroup.org/onlinepubs/009695399/utilities/find.html | | => "Only a plus sign that follows an argument containing the two | characters "{}" shall

Re: find -exec util {} arg + confusion

ot; should follow {}", + isok ? "-ok" : "-exec"); + } } } On Thu, Nov 12, 2020 at 08:51:22PM +0100, Paul de Weerd wrote: | Hi all, | | I misread find(1) and did: | | [weerdpom] $ find path/to/cam

find -exec util {} arg + confusion

Hi all, I misread find(1) and did: [weerdpom] $ find path/to/cam -name \*.JPG -exec cp {} path/to/store + find: -exec no terminating ";" or "+" That was somewhat surprising - there is a terminating "+". The error really is that the "+" doesn't follow immediately after the "{}" (which the

missing support for OHMS and ENERGY sensors in sensorsd

Hi all, While browsing sensorsd.c for inspiration for a small project I'm working on, I noticed that both src/usr.sbin/sensorsd/sensorsd.c and src/sbin/sysctl/sysctl.c have a 'print_sensor' function that returns/prints the value of the given sensor, including unit. However, sensorsd doesn't

Re: sensor value last change time not updated?

On Tue, Aug 25, 2020 at 01:38:20PM -0600, Theo de Raadt wrote: | What you are doing wasn't the purpose of the time field. It was added | only for time sensors, and it looks like someone added it to other | sensors. And now it must suddenly be for all of them?? Sorry - I may have introduced some

Re: sensor value last change time not updated?

Hi Theo, On Tue, Aug 25, 2020 at 01:33:28PM -0600, Theo de Raadt wrote: | > I don't understand the point. None of the sensor drivers set that | > member except the timedelta sensors. I don't think adding code to do | > so to all sensor drivers makes sense. | | That is correct. Non-time

Re: sensor value last change time not updated?

Hi Mark, Thanks for your reply. On Tue, Aug 25, 2020 at 09:27:20PM +0200, Mark Kettenis wrote: | > I've dug out my stash of weird usb devices and found another sensor (a | > uthum(4), with only temperature support). I have a few other sensors | > in live machines too (acpitz(4), cpu(4),

Re: sensor value last change time not updated?

truct uthum_sof temp += sc->sc_sensor[sensor].cal_offset * 1; sc->sc_sensor[sensor].sensor.value = temp; sc->sc_sensor[sensor].sensor.flags &= ~SENSOR_FINVALID; + microtime(>sc_sensor[sensor].sensor.tv);

Typo fix in comment sys/dev/usb/ugold.c

While looking at ugold.c I noticed a typo in a comment. Diff below. Cheers, Paul Index: ugold.c === RCS file: /home/OpenBSD/cvs/src/sys/dev/usb/ugold.c,v retrieving revision 1.14 diff -u -p -r1.14 ugold.c --- ugold.c 5 Oct

Re: sensor value last change time not updated?

14, 2020 at 02:50:39PM +0200, Hiltjo Posthuma wrote: | On Fri, Aug 14, 2020 at 01:46:57PM +0200, Paul de Weerd wrote: | > Hi all, | > | > I'm trying to read temperature sensor values from my ugold(4) device. | > Seems to work alright (I get the same temperature reading as sysc

Re: acme-client config grammar improvements

On Thu, Jul 16, 2020 at 07:40:35AM +0200, Daniel Eisele wrote: | Also it would be nice to have a feature to update all domains of the | config file. I currently do that in a shell script by parsing the output | of acme-client -nv with sed and then calling acme-client multiple times. What I have

Re: [PATCH] fast conditional console scrolling

the "Optimized rasops32 putchar" patch I just posted, you | should see another significant speedup. | | | Original Message | Subject: Re: [PATCH] fast conditional console scrolling | From: Paul de Weerd | Date: Fri, June 26, 2020 1:23 am | To: jo...@armadilloaerospace.com |

Re: [PATCH] fast conditional console scrolling

Hi John, I tried your diff. I don't quite see the same 3x improvement that you report, more like 2x. I timed 7 runs of ls -R /usr/ports: Before diff, time ls -R /usr/ports | wc -l 2.897s on average After diff, time ls -R /usr/ports | wc -l 2.707s on average Before diff, time ls -R

randomize daily/weekly/monthly crons

Really like the ~ feature in cron. I'm moving every machine that gets updated to -current to use this for the daily/weekly/monthly crons, so they are randomized in the 30 minute window after the original start time. Especially useful on machines running a few (or more) VMs. Something (or

Re: Opportunistic DoT for unwind(8)

On Thu, Oct 24, 2019 at 11:27:24AM +0100, Kevin Chadwick wrote: | | > The purpose of unwind is to provide secure DNS services even when | > the available nameservers are broken or filtered like in many hotels. | > To do that, it prefers DNSSEC whenever possible and changes to do | > resolving by

Re: [PATCH] Add swich to enable/disable re-link the kernel at startup

Hi Stefan, On Tue, May 21, 2019 at 09:10:51PM +0200, Stefan Sperling wrote: | > Reminds me that I should find some bigger CF to stick in there; 2GB | > really doesn't cut it anymore these days. | | My alix survives reorder_kernel just fine with 2GB of swap space, | though 1GB would probably be

Re: grep ".one\|.two" doesn't work on OpenBSD. Is it expected?

On Mon, May 20, 2019 at 08:01:12PM +0200, Juan Francisco Cantero Hurtado wrote: | I've a test in one of my ports similar to this: | | $ cat test.txt | $TESTTMP/hgcache/master/packs/7bcd2d90b99395ca43172a0dd24e18860b2902f9.histpack |

Re: [PATCH] Add swich to enable/disable re-link the kernel at startup

Hi Stuart, On Mon, May 20, 2019 at 12:14:56PM +0100, Stuart Henderson wrote: | On 2019/05/20 10:46, Paul de Weerd wrote: | > However, library_aslr delays the boot sequence (because libraries must | > be completed before the system can boot up) while kernel_aslr does not | > - it only i

Re: [PATCH] Add swich to enable/disable re-link the kernel at startup

On Sun, May 19, 2019 at 01:04:53PM +0200, Ricardo Fraile wrote: | Hi all, | | As exists the variable "library_aslr" to disable library randomization on | rc, it would be helpful to have the same option for the kernel. Here is the | patch to add the "kernel_aslr" swich. If you must do this: `doas

Re: [3/4] Re: Add support for Meinberg DCF600USB to umbg(4)

the Thanks, Paul On Fri, Mar 22, 2019 at 04:00:06PM +0100, Paul de Weerd wrote: | Whoops. I had missed one change to the manpage that's still needed: | the DESCRIPTION section also mentions the supported devices. This now | supports two models, but I don't think it makes sense to turn this | into a list

Re: usb drivers & arches (Re: [4/4] Re: Add support for Meinberg DCF600USB to umbg(4))

On Fri, Mar 22, 2019 at 11:53:20AM +, Stuart Henderson wrote: | This is a more general thing actually, the list of USB drivers is rather | haphazard at the moment. List below (to fit <80 cols I've snipped i386 | which has all drivers present in any other GENERIC config, amd64 which | is only

Re: [3/4] Re: Add support for Meinberg DCF600USB to umbg(4)

sensor and the delta (in nanoseconds) between the received time information and the local time can be accessed through the On Fri, Mar 22, 2019 at 10:04:19AM +0100, Paul de Weerd wrote: | | Index: share/man/man4/umbg.4 | === | RCS file

Re: [4/4] Re: Add support for Meinberg DCF600USB to umbg(4)

On Fri, Mar 22, 2019 at 10:22:15AM +, Stuart Henderson wrote: | $ for i in */conf/GENERIC; do grep -q ^udcf $i && grep -q ^umbg $i || echo ${i%%/*}; done Did you want to only find archs which DO have udcf(4) but not umbg(4)? Because not all of those in your list have udcf. This adds ubmg

Re: [4/4] Re: Add support for Meinberg DCF600USB to umbg(4)

On Fri, Mar 22, 2019 at 10:22:15AM +, Stuart Henderson wrote: | it's missing on some others too; | | $ for i in */conf/GENERIC; do grep -q ^udcf $i && grep -q ^umbg $i || echo ${i%%/*}; done | alpha | amd64 | arm64 | armv7 | hppa | landisk | loongson | luna88k | socppc Yes. I have some of

[5/4] Re: Add support for Meinberg DCF600USB to umbg(4)

Bonus diff - make explicit in the GENERIC configs that already have umbg(4), that this driver now supports DCF600USB too Index: i386/conf/GENERIC === RCS file: /home/OpenBSD/cvs/src/sys/arch/i386/conf/GENERIC,v retrieving revision

[2/4] Re: Add support for Meinberg DCF600USB to umbg(4)

Index: usbdevs.h === RCS file: /home/OpenBSD/cvs/src/sys/dev/usb/usbdevs.h,v retrieving revision 1.707 diff -u -p -r1.707 usbdevs.h --- usbdevs.h 24 Feb 2019 17:35:44 - 1.707 +++ usbdevs.h 22 Mar 2019 07:48:28 - @@

[4/4] Re: Add support for Meinberg DCF600USB to umbg(4)

Index: GENERIC === RCS file: /home/OpenBSD/cvs/src/sys/arch/amd64/conf/GENERIC,v retrieving revision 1.466 diff -u -p -r1.466 GENERIC --- GENERIC 19 Jan 2019 03:24:18 - 1.466 +++ GENERIC 22 Mar 2019 08:10:33 - @@

[3/4] Re: Add support for Meinberg DCF600USB to umbg(4)

Index: share/man/man4/umbg.4 === RCS file: /home/OpenBSD/cvs/src/share/man/man4/umbg.4,v retrieving revision 1.4 diff -u -p -r1.4 umbg.4 --- share/man/man4/umbg.4 16 Jul 2013 16:05:49 - 1.4 +++ share/man/man4/umbg.4

[1/4] Re: Add support for Meinberg DCF600USB to umbg(4)

Index: usbdevs === RCS file: /home/OpenBSD/cvs/src/sys/dev/usb/usbdevs,v retrieving revision 1.695 diff -u -p -r1.695 usbdevs --- usbdevs 24 Feb 2019 17:35:29 - 1.695 +++ usbdevs 20 Mar 2019 11:55:44 - @@

Add support for Meinberg DCF600USB to umbg(4)

Hi all, After Peter J. Philipp asked about Meinberg DCF clock support on misc@ in https://marc.info/?l=openbsd-misc=155205024420585=2 I was also interested in the question he asked. After some consideration, I decided to try, so I bought a Meinberg DCF600USB which was delivered yesterday. I

Re: what.1: remove BUGS section

Hi Ingo, On Sun, Jan 20, 2019 at 03:11:55PM +0100, Ingo Schwarze wrote: | > Talking about BSD not being able to distribute SCCS doesn't help | > anyone; | > not behaving like the original SCCS is obvious considering the | > STANDARDS section specifically notes OpenBSD extensions and | >

Re: sbin/wsconsctl: show more data

Lots of negativity here, so I just wanted to chime in - really love the new console font! Crisp and easily readable letters, big enough to be readable, with a reasonable number of letters per line (${COLUMNS}) en lines per screen (${LINES}). It does mean pretty big characters on big screens when

Re: Add acpipci(4) on amd64

Hi Mark, On Mon, Oct 22, 2018 at 09:45:06PM +0200, Mark Kettenis wrote: | I'd like to see this tested on a wide range of amd64 hardware, but | especially on laptops. Please reply with a diff of your dmesg before | and after. Make sure you run make config before building a new kernel. Thanks

Re: nsd 4.1.24

On Wed, Aug 15, 2018 at 03:12:19PM +0200, Florian Obser wrote: | When this goes in I think we should switch the default control socket | and stop listening on localhost. This makes a lot of sense to me, please make the UDS the default control socket. Thanks Florian! Paul | OK? | | diff --git

Re: call for testing: rad(8) - a rtadvd(8) replacement

On Wed, Jul 18, 2018 at 08:54:51AM +0200, Florian Obser wrote: | During g2k18 I commited rad(8). | | The latest amd64 and i386 snapshots should contain it with enough | features to replace rtadvd(8). If you are using rtadvd(8) I'd | appreciate if you could switch to rad(8) and report back if any

Re: 6.3 and Prolific PL-2303 USB serial adapter

Updated diff included below. I've set the product name to LD220. This diff lacks the updates to usbdevs{,_data}.h, whoever commits should update those too. Any takers to commit this? Tested by an owner of the actual device, so that's good. Jan-Piet, maybe you can share a dmesg of the machine

Re: 6.3 and Prolific PL-2303 USB serial adapter

Hi Jan-Piet! On Mon, Jun 18, 2018 at 04:16:34PM +0200, Jan-Piet Mens wrote: | > Only one way to find out :) | | I spare you a lot of details by pointing you at a photo I just took of the | working display: if you'd please scroll to the bottom of [1] .. ? | | A final (hah!) question: will your

Re: 6.3 and Prolific PL-2303 USB serial adapter

On Sun, Jun 17, 2018 at 07:30:34PM +0200, Jan-Piet Mens wrote: | Hi Paul, | | > Is there any specific marking on the device to suggest it's from HP? | | oh, indeed. The photo at [1] shows the display with a prominent "HP" logo. | | [1] https://mastodon.social/@jpmens/100220482259778231 Oh,

Re: 6.3 and Prolific PL-2303 USB serial adapter

Hi Jan-Piet, This seems to be a USB to serial adapter made by HP, given the output from Fedora's lsusb: > idVendor 0x03f0 Hewlett-Packard > idProduct 0x3524 > bcdDevice3.10 > iManufacturer 1 Prolific Technology Inc. > iProduct2

Re: ping.c minor bug discrepancy between reported size of icmp packet

Hi Tom, This is documented in ping(8): -s packetsize Specify the number of data bytes to be sent. The default is 56, which translates into 64 ICMP data bytes when combined with the 8 bytes of ICMP header data. The maximum packet size is

Re: ifconfig(8): pltime and vltime are measured in seconds

Hi Jason, Thanks for your reply. Yes, that's better. Here you go: Index: ifconfig.8 === RCS file: /home/OpenBSD/cvs/src/sbin/ifconfig/ifconfig.8,v retrieving revision 1.305 diff -u -p -r1.305 ifconfig.8 --- ifconfig.8 16 Mar

ifconfig(8): pltime and vltime are measured in seconds

During a discussion on IPv6 with Undeadly editor Ross Richardson, he pointed out that ifconfig(8) doesn't mention the unit of the arguments to the pltime and vltime options. Here's a diff to fix that: Index: ifconfig.8 === RCS

Re: Add "-c command" option to script(1)

ping Anyone? Buehler? :) Paul On Mon, Dec 25, 2017 at 12:23:44PM +0100, Paul de Weerd wrote: | Hi all, | | Sorry to keep harping on this script stuff, but I'd really like to see | this committed. I've just upgraded my laptop while doing some | vlan-bridging debugging and suddenly script(1

Re: Add "-c command" option to script(1)

. Is anyone willing to commit it with those? Thanks, Paul On Sat, Dec 16, 2017 at 09:45:02AM +0100, Paul de Weerd wrote: | On Fri, Dec 15, 2017 at 12:24:45PM +0100, Paul de Weerd wrote: | | I've updated the diff to add this example as per jmc's suggestion. It | | now has: | | | | - add the `-c

cross ref ocspcheck in httpd.conf(5)

I've been playing a bit with OCSP stapling in httpd and found the documentation a bit lacking / confusing. httpd says: ocsp file Specify an OCSP response to be stapled during TLS handshakes with this server. The file should contain a DER-format

Re: Add "-c command" option to script(1)

On Fri, Dec 15, 2017 at 12:24:45PM +0100, Paul de Weerd wrote: | I've updated the diff to add this example as per jmc's suggestion. It | now has: | | - add the `-c command` feature | - updates usage | - removes /* ARGSUSED */ lint comments | - documents the -c feature

Re: Add "-c command" option to script(1)

On Thu, Dec 14, 2017 at 08:49:18AM +, Jason McIntyre wrote: | On Thu, Dec 14, 2017 at 09:23:29AM +0100, Paul de Weerd wrote: | > Another use I personally find very convenient is this: | > | > [weerd@pom] $ script -c "vmctl start test -c" | | you could add this as an EXAM

Re: Add "-c command" option to script(1)

Another use I personally find very convenient is this: [weerd@pom] $ script -c "vmctl start test -c" Hope others see value here too :) Paul On Thu, Dec 14, 2017 at 08:45:19AM +0100, Paul de Weerd wrote: | Hi Jason, | | Thank you for your quick feedback! I've incorporated yours and

Re: Add "-c command" option to script(1)

Hi Jason, Thank you for your quick feedback! I've incorporated yours and off-list feedback from ian@ into a new diff included below. The diff now also includes the removal of /* ARGSUSED */ lint comments. On Wed, Dec 13, 2017 at 09:34:03PM +, Jason McIntyre wrote: | > +To run a | | i'd

Add "-c command" option to script(1)

Hi all, As seen in NetBSD, FreeBSD and Linux, script(1) could do with a way to tell it what command to run instead of your $SHELL. This implements the "-c command" option. I've taken the logic to start the command (and its arguments, if any) from crontab(1), execv'ing `sh -c `. I wrote this

Re: Have installboot default to the device carrying /

On Tue, Nov 07, 2017 at 12:38:17AM -0700, Theo de Raadt wrote: | >On Mon, Nov 06, 2017 at 03:24:30PM -0700, Theo de Raadt wrote: | >| > Here's a diff that will make it default to the device carrying the | >| > root filesystem. Result this: | >| | >| I disagree strongly with this. installboot is

Re: Have installboot default to the device carrying /

On Mon, Nov 06, 2017 at 03:24:30PM -0700, Theo de Raadt wrote: | > Here's a diff that will make it default to the device carrying the | > root filesystem. Result this: | | I disagree strongly with this. installboot is a disruptive operation, | and you should specify the device. Fair enough. I

Re: Have installboot default to the device carrying /

Now with manpage diff, fixed usage and less magic numbers (thanks to florian@ again for the last two). Paul On Mon, Nov 06, 2017 at 03:58:50PM +0100, Paul de Weerd wrote: | installboot(8) will error out when not given a device to install to: | | [weerd@pom] $ doas installboot | usage

Have installboot default to the device carrying /

installboot(8) will error out when not given a device to install to: [weerd@pom] $ doas installboot usage: installboot [-nv] [-r root] disk [stage1 [stage2]] Here's a diff that will make it default to the device carrying the root filesystem. Result this: [weerd@pom] $ doas obj/installboot -v

Re: inteldrm(4) diff needs review and testing

Hi Mark, On Sun, Jul 16, 2017 at 03:19:41PM +0200, Mark Kettenis wrote: | Can somebody test the following diff on Ivy Bridge or Haswell (Intel | HD Graphics 2500/4000/4600/4700/5000/5100/5200)? | | When I added support for the command parser, I took a bit of a | shortcut and implemented the hash

Re: [PATCH] cp(1): add -v option for verbosity

On Sun, Jun 25, 2017 at 10:49:04PM +0200, Landry Breuil wrote: | > | Alternatively one can use rsync(1), but that is not part of the base. | > | > That may work for cp(1), but it's hard to replicate mv(1) behavior | > with rsync (only metadata changes when on the same fs) or even | > impossible

Re: [PATCH] rm(1): add -v option for verbosity

Hi Ingo, On Sun, Jun 25, 2017 at 03:12:26PM +0200, Ingo Schwarze wrote: | Hi, | | Job Snijders wrote on Sun, Jun 25, 2017 at 02:06:16PM +0200: | | > This patch adds a '-v' option to rm(1) for more verbose output. | | Do not add new options to standard utilities, unless you can show | that they

Re: [PATCH] cp(1): add -v option for verbosity

On Sun, Jun 25, 2017 at 06:22:05PM +0200, Job Snijders wrote: | Dear Alexander, | | On Sun, Jun 25, 2017 at 06:13:40PM +0200, Alexander Hall wrote: | > On June 25, 2017 2:06:20 PM GMT+02:00, Job Snijders wrote: | > >This patch adds a -v option to cp(1) for more verbose

Re: Finish the link-kit job

On Fri, Jun 23, 2017 at 07:53:35AM -0600, Theo de Raadt wrote: | > Perhaps we'll come up with a simpler way down the road, but it isn't | > *that* hard for manual upgrades. once you've installed the kernels, make | > sure you've got the correct hash: | > | > sha256 -h /var/db/kernel.SHA256

Re: Finish the link-kit job

On Fri, Jun 23, 2017 at 04:28:15AM -0600, Theo de Raadt wrote: | > /mnt/usr/sbin/chroot /mnt /usr/local/libexec/reorder_kernel | > | > ... | > | > + mail -Es "$(hostname) Kernel relink info" root >/dev/null | | No, that isn't cool. | | Yes, we are going to link in the

Re: Finish the link-kit job

On Wed, Jun 21, 2017 at 01:13:31PM -0600, Theo de Raadt wrote: | Future work should be to see if we can build a fresh kernel at | install/upgrade time, for that "every computer is unique" feel. How about we move the rc bits out from rc and into a small script that we call from rc. Now we can

Re: mcast-proxy daemon

On Sat, May 27, 2017 at 11:05:13PM +0200, Paul de Weerd wrote: | - lacks an rc.d init script Here's a diff that adds an rc.d script 'mcastproxy' (other daemons that have a '-' in their name also drop it in their rc.d script, so I followed that example) I stuck it in /etc/rc around

Re: [PATCH] ntpd: allow to specify a source IP address for outgoing queries

Works for me, verified both v4 and v6 selection actually uses that address. Suggested a small improvement for ntpd.conf(5) to Job privately. Would love to see this feature get imported :) Thanks Job! Paul On Tue, May 30, 2017 at 06:10:03PM +0200, Job Snijders wrote: | On Sun, May 28, 2017 at

Re: mcast-proxy daemon

Hi tech@, I've been talking to Rafael about this piece of code over the last week a bit, and have tried it on my home TV setup. My ISP has a multicast setup for watching television, with their set-top-box connected to my TV. Up until now, I was using net/igmpproxy on my OpenBSD gateway to get

HP C8000 workstations

Hi all, I have a couple of HP C8000 workstations collecting dust at home. Now that the hppa64 port has been cancelled, my chances of ever running OpenBSD on one of them have gone from slim to none. They're not supported, something with the chipset (ZX1?) that is undocumented, I believe. So no

Simtec USB Entropy Key

Hi all, While cleaning out my closet I found a Simtec USB Entropy Key (hidden under those HP C8000 workstations :) It attaches as: May 31 13:09:26 pom /bsd: umodem0 at uhub3 May 31 13:09:26 pom /bsd: port 5 configuration 1 interface 0 "Simtec Electronics Entropy Key" rev 2.00/2.00 addr 6 May

Re: Journal Implementation

On Tue, Jun 02, 2015 at 07:33:58PM +, Stefan wrote: | http://www.openbsd.org/faq/faq8.html#Journaling Right, that doesn't help, it's not a tip for someone interested in *developing a journaling system for UFS*... You can rest assured they're already aware that OpenBSD doesn't support

Re: Small ifconfig output tweak for inet6?

On Thu, Mar 26, 2015 at 01:48:03PM +0100, Martin Pieuchot wrote: | How do people feel about printing the prefixlen in CIDR notation? I'm | annoyed about outputs not fitting in 80 chars when using autoconf magic: | | -inet6 fd00::f2de:f1ff:fe6a:15d1 prefixlen 64 autoconf pltime 3594 vltime 7194 |

Re: changing ffs mount between rw and ro while preserving softdep

On Thu, Aug 28, 2014 at 06:27:48PM +, Miod Vallat wrote: | Which is why the current way to remove softdep from a filesystem is a | rw+softdep - ro - rw transition, which would no longer work with your | diff. | | It would work, but you'd have to explicitly disable softdep, as one might |

  1   2   >