On Tue, Oct 24, 2023 at 09:09:21AM +0200, Peter N. M. Hansteen wrote:
> On Tue, Oct 24, 2023 at 06:54:30AM +0000, Klemens Nanni wrote:
> > - parse.y still accepting undocumented "ssl" with a warning since 2014
> > - more "SSL/TLS" instead of "TLS" in m
10/24/23 14:03, Crystal Kolipe пишет:
> On Tue, Oct 24, 2023 at 01:44:08AM +0000, Klemens Nanni wrote:
>> Rereading the code, I now question why it checks the 'a' label type at all.
>>
>> Taking your sd0d example through devboot():
>>
>> |#ifdef S
Wanted to learn about TLS usage in relayd(8) and thought these SSL history
bits in the TLS RELAYS section read out of place.
Index: relayd.conf.5
===
RCS file: /cvs/src/usr.sbin/relayd/relayd.conf.5,v
retrieving revision 1.206
diff -u
On Mon, Oct 23, 2023 at 06:36:21PM -0300, Crystal Kolipe wrote:
> On Mon, Oct 23, 2023 at 11:04:07AM +0000, Klemens Nanni wrote:
> > 10/16/23 04:02, Klemens Nanni ??:
> > > The current check implies one could use, e.g. SWAP or MSDOS partitions
> > > as soft
10/16/23 04:02, Klemens Nanni пишет:
> The current check implies one could use, e.g. SWAP or MSDOS partitions
> as softraid(4) chunks, but sys/dev/softraid.c always expects FS_RAID,
> thus using chunks with different partition types is not possible:
>
> # vmctl create
On Mon, Sep 04, 2023 at 09:57:40PM +, Klemens Nanni wrote:
> Extend the yes/no question to no/passphrase/keydisk and have users pick an
> existing, preformated RAID partition; no support (yet) for creating one.
>
> Thanks to how ask_which() works, users can always say 'd
On Mon, Oct 16, 2023 at 01:02:07AM +, Klemens Nanni wrote:
> The current check implies one could use, e.g. SWAP or MSDOS partitions
> as softraid(4) chunks, but sys/dev/softraid.c always expects FS_RAID,
> thus using chunks with different partition types is not possible:
>
>
The current check implies one could use, e.g. SWAP or MSDOS partitions
as softraid(4) chunks, but sys/dev/softraid.c always expects FS_RAID,
thus using chunks with different partition types is not possible:
# vmctl create -s100M disk.img
# vnd=`vnconfig disk.img`
# echo 'sw
On Sun, Oct 15, 2023 at 07:51:00AM -0400, Dave Voutila wrote:
>
> Dave Voutila writes:
>
> > Looking for folks that use the serial console connection in vmd(8) and
> > experience the host CPU spikes & delays associated with things like
> > hitting the up key (to cycle shell command history) or c
9/23/23 14:11, Mark Kettenis пишет:
>> Date: Thu, 21 Sep 2023 22:30:01 +
>> From: Klemens Nanni
>>
>> In comparison to MI boot which only cares about /bsd.upgrade's x bit,
>> powerpc64 rdboot just wants a regular file.
>>
>> Require and strip u+x
On Sun, Oct 08, 2023 at 12:18:34AM -0400, George Koehler wrote:
> On Fri, 8 Jul 2022 16:04:47 +
> Guilherme Janczak wrote:
>
> > gzip violates wpath if you tell it to extract stdin and restore the
> > original filename.
>
> More than a year ago, Guilherme Janczak reported that OpenBSD's
> "g
[this change was lost between others and private mails...]
Passphrases must not be empty or else volume creation/unlock fails:
# bioctl -cC -lvnd0a softraid0
New passphrase:
Re-type passphrase:
bioctl: bcrypt_pbkdf failed
[-p passfile] already says "invalid pass
On Mon, Sep 25, 2023 at 01:33:31PM +, Klemens Nanni wrote:
> On Tue, Jul 25, 2023 at 01:30:43PM +0300, Slava Voronzoff wrote:
> > Hi, pinging and refreshing this patch
> >
> > What it does:
> > allow arm64 cpus to break from the loop of waiting to start cor
On Fri, Sep 29, 2023 at 05:28:46PM +0200, Florian Obser wrote:
> On 2023-09-29 14:41 UTC, Klemens Nanni wrote:
> > The response file contains only to non-defaults, except for
> > Set name(s)? (or 'abort' or 'done') [done] done
> >
>
The response file contains only to non-defaults, except for
Set name(s)? (or 'abort' or 'done') [done] done
which is the hardcoded default since 2009:
ask "Set name(s)? (or 'abort' or 'done')" done
We pass it since r1.23 in 2019
Let sysupgrade(8) create auto_upgrade.co
On Tue, Jul 25, 2023 at 01:30:43PM +0300, Slava Voronzoff wrote:
> Hi, pinging and refreshing this patch
>
> What it does:
> allow arm64 cpus to break from the loop of waiting to start core and
> drop to DDB or OS.
>
> Patch based on same concept in amd64 cpu.c
>
> Any suggestions? Good to go?
On Mon, Sep 25, 2023 at 05:35:40AM +, Visa Hankala wrote:
> On Sat, Sep 23, 2023 at 02:26:18PM +0000, Klemens Nanni wrote:
> > On Sat, Sep 23, 2023 at 01:11:32PM +0200, Mark Kettenis wrote:
> > > > Date: Thu, 21 Sep 2023 22:30:01 +
> > > > From: K
On Sat, Sep 23, 2023 at 09:55:03AM -0600, Theo de Raadt wrote:
> Mark Kettenis wrote:
>
> > > Date: Fri, 22 Sep 2023 23:19:30 +0000
> > > From: Klemens Nanni
> > >
> > > Does the tiny kexec kernel actually need network, bio(4) or HID devices?
&
On Sat, Sep 23, 2023 at 01:11:32PM +0200, Mark Kettenis wrote:
> > Date: Thu, 21 Sep 2023 22:30:01 +
> > From: Klemens Nanni
> >
> > In comparison to MI boot which only cares about /bsd.upgrade's x bit,
> > powerpc64 rdboot just wants a regular file.
&g
Does the tiny kexec kernel actually need network, bio(4) or HID devices?
octeon/BOOT does not have any of this.
Looks like too much of powerpc64/RAMDISK remained, but I might be missing
some obvious difference between these platforms.
The Raptor CS Blackbird used for the re-upgrade prevention dif
On Thu, Sep 21, 2023 at 10:30:01PM +, Klemens Nanni wrote:
> In comparison to MI boot which only cares about /bsd.upgrade's x bit,
> powerpc64 rdboot just wants a regular file.
>
> Require and strip u+x before execution to prevent sysupgrade(8) loop.
> I'm new to pow
In comparison to MI boot which only cares about /bsd.upgrade's x bit,
powerpc64 rdboot just wants a regular file.
Require and strip u+x before execution to prevent sysupgrade(8) loop.
I'm new to powerpc64 and can't think of a reason to be different.
Feedback? Objection? OK?
Regular boot and sysu
powerpc64 already has bio(4) and bioctl(8) like macppc, but lacks
softriad(4), which looks like an oversight.
Neither architecture has boot support, but they still ought to be able
to access softraid volumes during install/upgrade.
distrib/powerpc64/ramdisk builds and fits; I did not have a free
On Wed, Sep 06, 2023 at 12:23:33PM -0500, Scott Cheloha wrote:
> On Wed, Sep 06, 2023 at 01:04:19PM +0100, Martin Pieuchot wrote:
> > Debugging OOM is hard. UVM uses per-CPU counters and sadly
> > counters_read(9) needs to allocate memory. This is not acceptable in
> > ddb(4). As a result I cann
Extend the yes/no question to no/passphrase/keydisk and have users pick an
existing, preformated RAID partition; no support (yet) for creating one.
Thanks to how ask_which() works, users can always say 'done' to land back
at question to either skip crypto or use a passphrase instead.
All code re
On Fri, Aug 11, 2023 at 03:51:38PM +0100, Stuart Henderson wrote:
> On 2023/08/11 16:43, Mark Kettenis wrote:
> > See the recent discussion about _bcrypt_autorounds() in libc.
> >
> > System performance varies, and even on modern hardware it can provide
> > varying results. The ramdisk environmen
On Fri, Aug 18, 2023 at 04:20:13PM +, Klemens Nanni wrote:
> Messages from the driver always land on standard output, but they may
> contain errors, which ought to land on standard error.
>
> Seen when scripted creation silently failed:
>
> # bioctl -Cforce -cC -lvnd0
Messages from the driver always land on standard output, but they may
contain errors, which ought to land on standard error.
Seen when scripted creation silently failed:
# bioctl -Cforce -cC -lvnd0a softraid0 1>/dev/null ; echo $?
1
# ./obj/bioctl -Cforce -cC -lvnd0a softr
On Fri, Aug 18, 2023 at 10:35:37AM +0200, Omar Polo wrote:
> sorry for the noise, noticed just now re-reading the diff.
>
> On 2023/08/17 09:32:43 +, Klemens Nanni wrote:
> > --- bioctl.86 Jul 2023 21:08:50 - 1.111
> > +++ bioctl.817 Au
On Thu, Aug 17, 2023 at 06:43:36PM +1000, Joel Sing wrote:
> I agree with the intent, however the man page should probably reflect this
> change (i.e. -s makes it non-interactive and you will not get confirmation).
Done.
>
> > Index: bioctl.c
> > =
On Fri, Aug 11, 2023 at 03:44:46PM +, Klemens Nanni wrote:
> On Wed, Aug 02, 2023 at 10:37:36AM +0000, Klemens Nanni wrote:
> > Creating new volumes prompts
> > Passphrase:
> > Re-type passphrase:
> > which is sane for interative usage, but -s (which omit
Consistent with other options and our manuals in general.
Index: cksum.1
===
RCS file: /cvs/src/bin/md5/cksum.1,v
retrieving revision 1.40
diff -u -p -r1.40 cksum.1
--- cksum.1 4 Aug 2022 06:20:24 - 1.40
+++ cksum.1
On Wed, Aug 02, 2023 at 11:51:09AM +, Klemens Nanni wrote:
> An alternative approach could be a new bioctl(8)) flag
> -K Keep prompting until new and re-typed passphrases match.
> to repeat the prompt (during interactive creation only) until match or ^C:
>
> #
On Mon, Aug 14, 2023 at 05:47:35PM +, Lucas wrote:
> Klemens Nanni wrote:
> > @@ -1117,13 +1117,6 @@ bio_changepass(char *dev)
> >
> > /* Current passphrase. */
> > bio_kdf_derive(&kdfinfo1, &kdfhint, "Old passphrase: ", 0);
> >
On Fri, Aug 11, 2023 at 05:38:41PM +0200, Mark Kettenis wrote:
> > From: "Theo de Raadt"
> > I think this case is different, because the ramdisk has no process
> > contention.
> >
> > The code still sticks to minimum 16:
> >
> > if (r < 16)
> > r = 16;
> >
> > On faster
13.08.2023 12:13, Omar Polo пишет:
> [moving to tech@, there's a diff for the manpage below]
>
> On 2023/08/13 01:04:11 -0700, Alfred Morgan wrote:
>> I was surprised that `server "default"` didn't act like I expected. In this
>> example I expected `test1` to get 200 and everything else to get 40
On Wed, Aug 02, 2023 at 10:37:36AM +, Klemens Nanni wrote:
> Creating new volumes prompts
> Passphrase:
> Re-type passphrase:
> which is sane for interative usage, but -s (which omits prompts) to read
> from stdin also prompts twice.
>
> I think that&#x
On Fri, Aug 11, 2023 at 03:51:38PM +0100, Stuart Henderson wrote:
> Agreed. (Re bcrypt, I usually completely ignore auto rounds, I had just
> forgotten to set that up on the machine where I noticed the problem..)
>
> Also, am I right in thinking that this only affects the time when
> entering the
Joel encouraged me to switch to '-r auto' by default sooner than later.
The alternative installer diff on tech@ would thus be obsolete/a NOOP.
If you do encrypted disk installs on one machine, but use them on another,
or you want a specific number of rounds, just use '-r N' during creation
or pass
On Mon, May 08, 2023 at 11:00:27AM +, Klemens Nanni wrote:
> On Sun, Apr 23, 2023 at 05:07:30PM +0000, Klemens Nanni wrote:
> > For new installs, it seems adequate to base the number on the actual
> > hardware,
> > assuming the CRYPTO volume will stay in that
On Wed, Aug 02, 2023 at 11:38:57AM +, Klemens Nanni wrote:
> This needs "bioctl: do not confirm new passphrases on stdin" on tech@.
>
> Current code tries thrice to get matching passphrases before aborting;
> simple enough to get the feature going, but also due to code
On Fri, Aug 04, 2023 at 11:45:00AM +, Klemens Nanni wrote:
> If the root disk contains a valid CRYPTO volume, bioctl(8) by default
> unlocks that instead of creating a new one.
>
> Use `-C force' to prevent reuse of old volumes, which happens if you, e.g.
> restart an en
On Sat, Apr 22, 2023 at 12:00:44AM +, Klemens Nanni wrote:
> On Fri, Apr 21, 2023 at 11:29:11PM +, Koakuma wrote:
> > I noticed that when using `ldomctl status` the utilization value of
> > stopped ldoms is always a copy of the previous entry's value,
> > w
If the root disk contains a valid CRYPTO volume, bioctl(8) by default
unlocks that instead of creating a new one.
Use `-C force' to prevent reuse of old volumes, which happens if you, e.g.
restart an encrypted installation past this point or install onto an old
disk without wiping it first:
I had a few important changes in there and drm related crashes whilst
editing/testing /etc/X11/xorg.conf did result in that file being empty afer
reset and fsck, so a backup would be valuable.
xorg.conf(5) lists a various .../xorg.conf and .../conf.d/*.conf files,
but the single (default?) path se
On Wed, Aug 02, 2023 at 02:38:57PM +0300, Klemens Nanni wrote:
> This needs "bioctl: do not confirm new passphrases on stdin" on tech@.
>
> Current code tries thrice to get matching passphrases before aborting;
> simple enough to get the feature going, but also due to code
This needs "bioctl: do not confirm new passphrases on stdin" on tech@.
Current code tries thrice to get matching passphrases before aborting;
simple enough to get the feature going, but also due to code limitations.
One possible fix is to let the installer (not bioctl) prompt the passphrase
like
Creating new volumes prompts
Passphrase:
Re-type passphrase:
which is sane for interative usage, but -s (which omits prompts) to read
from stdin also prompts twice.
I think that's neither intuitive nor ergonomical and as intended for
non-interactive scripts, -s should take a new pa
On Wed, Jul 05, 2023 at 11:15:41AM +0200, Alexandr Nedvedicky wrote:
> Hello,
>
>
> On Wed, Jul 05, 2023 at 11:10:11AM +0200, Alexandr Nedvedicky wrote:
>
> >
> > thanks for your help to put my update to pf(4) to shape.
> > updated diff is below.
> >
>
> diff in my earlier email was wrong
On Tue, Jun 27, 2023 at 03:27:55PM +0200, Claudio Jeker wrote:
> On Mon, Jun 26, 2023 at 08:58:47PM +0000, Klemens Nanni wrote:
> > On Mon, Jun 26, 2023 at 10:52:20PM +0200, Claudio Jeker wrote:
> > > count() is strange since it only works on maps (at least from what I
> >
On Tue, Jun 27, 2023 at 01:32:37PM +0300, Vitaliy Makkoveev wrote:
> M_TEMP seems unreasonable for interface groups data allocations.
After claudio pointed out the wrong type, I thought of the same name,
no other malloc(9) type fits.
FWIW OK kn, but please wait for other to chime in.
>
> Don't
On Mon, Jun 26, 2023 at 10:52:20PM +0200, Claudio Jeker wrote:
> count() is strange since it only works on maps (at least from what I
> figured out). I need to double check how min() and max() work. Since the
> usage also seems non-intuitive.
>
> I find the documentation of bt(5) rather weak. So m
On Mon, Jun 26, 2023 at 05:24:53PM +0200, Claudio Jeker wrote:
> I created this simple btrace script to help find malloc(9) leaks but
> it did not work. First step was adding kstack support to the map
> implementation. But then it still did not work because btrace did not
> enable the kstack report
On Fri, May 26, 2023 at 04:18:45PM +, Klemens Nanni wrote:
> On Fri, May 26, 2023 at 05:28:01PM +0300, Vitaliy Makkoveev wrote:
> > On Fri, May 26, 2023 at 01:03:13PM +, Klemens Nanni wrote:
> > > snmpd(8) and 'pfctl -s Interfaces' dump pf&#
On Wed, May 31, 2023 at 10:27:13AM +0200, Claudio Jeker wrote:
> On Tue, May 30, 2023 at 11:56:01PM +0000, Klemens Nanni wrote:
> > On Tue, May 23, 2023 at 07:13:28PM +, Klemens Nanni wrote:
> > > On Sat, Jan 14, 2023 at 02:28:27PM +, Stuart Henderson wrote:
> >
On Tue, May 23, 2023 at 07:13:28PM +, Klemens Nanni wrote:
> On Sat, Jan 14, 2023 at 02:28:27PM +, Stuart Henderson wrote:
> > On 2023/01/12 04:49, Mikolaj Kucharski wrote:
> > > Hi,
> > >
> > > Is there anything else which I can do, to help this diff r
On Fri, May 26, 2023 at 05:28:01PM +0300, Vitaliy Makkoveev wrote:
> On Fri, May 26, 2023 at 01:03:13PM +0000, Klemens Nanni wrote:
> > snmpd(8) and 'pfctl -s Interfaces' dump pf's internal list of interfaces.
> >
> > pf.conf's 'set skip on ifN
snmpd(8) and 'pfctl -s Interfaces' dump pf's internal list of interfaces.
pf.conf's 'set skip on ifN' and 'pfctl -F all|Reset' set and clear flags,
PFI_IFLAG_SKIP being the only flag.
(There's no other usage of these ioctls in base.)
pf's internal interface list is completely protected by the pf
On Wed, May 24, 2023 at 08:50:26PM +0200, Stefan Fritsch wrote:
> I forgot to mention that no stress test is necessary. If it boots and the
> virtio devices work at all, that should be enough.
amd64 bsd.mp keeps working with disks and network interfaces behind
VirtIO, no dmesg or behaviour change
ask_yn() returns 0/1 for no/yes, so almost all users in install.sub use
the same 'ask_yn && do-it', 'ask_yn || skip' idioms.
Adjust two MD calls accordingly.
OK?
Index: amd64/common/install.md
===
RCS file: /cvs/src/distrib/amd64/co
On Thu, May 25, 2023 at 03:28:45AM +, Klemens Nanni wrote:
> On Thu, May 25, 2023 at 03:20:04AM +0000, Klemens Nanni wrote:
> > pfsync_in_bus() looks like the only place where the static array
> > pf_pool_limits[] is accessed without the pf lock, so grab it there.
> >
On Thu, May 25, 2023 at 03:20:04AM +, Klemens Nanni wrote:
> pfsync_in_bus() looks like the only place where the static array
> pf_pool_limits[] is accessed without the pf lock, so grab it there.
>
> Limits themselves are protected by the pf lock and pool(9)s are never
> des
pfsync_in_bus() looks like the only place where the static array
pf_pool_limits[] is accessed without the pf lock, so grab it there.
Limits themselves are protected by the pf lock and pool(9)s are never
destroyed and have builtint per-pool locks, so the net lock is not
needed.
(pf_pool_limits[] a
24 мая 2023 г. 18:05:29 Todd C. Miller :
> On Tue, 23 May 2023 22:22:04 -0000, Klemens Nanni wrote:
>
>> I'm pointing this out because the error message we'd get provides less
>> information with your diff:
>>
>> $ echo $(cat /nope) 2>/dev/null
&
On Tue, May 23, 2023 at 11:41:32PM +0200, Christian Weisgerber wrote:
> This replaces "$(cat file)" with the ksh construct "$( Admittedly cosmetic.
Functional behaviour won't change, but stderr handling is subtly
different, as you're gladly aware of.
> I have left the line
>
> local _sec
On Sat, Jan 14, 2023 at 02:28:27PM +, Stuart Henderson wrote:
> On 2023/01/12 04:49, Mikolaj Kucharski wrote:
> > Hi,
> >
> > Is there anything else which I can do, to help this diff reviwed and
> > increase the chance of getting in?
> >
> > Thread at https://marc.info/?t=16347829861&r=1&
On Sat, May 20, 2023 at 07:47:46PM +0200, Florian Obser wrote:
> On 2023-05-20 19:37 +02, Paul de Weerd wrote:
> > 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
On Tue, May 16, 2023 at 10:07:20AM -0700, Chris Cappuccio wrote:
> I don't quite understand the case this patch solves, because my installs to
> fresh media always get EFI/GPT. It doesn't default to MBR. However, if
> there is a case where it tries to use MBR, that isn't going to work so well.
If
On Mon, May 15, 2023 at 09:42:47AM -0400, Bryan Steele wrote:
> On Mon, May 15, 2023 at 09:17:00AM -0400, Okan Demirmen wrote:
> > On Mon 2023.05.15 at 10:41 +0200, Matthieu Herrb wrote:
> > > On Mon, May 15, 2023 at 06:26:41AM +0000, Klemens Nanni wrote:
> > > >
Both fvwm(1) and twm(1) have a restart menu that contains other window
managers by default, which is useful if you want to switch around
without restarting X and/or custom window manager config.
cwm(1) only offers to restart into itself by deafult.
Add the other two we ship by default so users can
On Fri, May 12, 2023 at 12:18:12AM +0200, Alexander Bluhm wrote:
> Hi,
>
> I would like to remove the kernel lock from nd6 resolve and use nd6
> mutex instead.
>
> Access rt_llinfo and check for NULL without checking RTF_LLINFO
> flag before. They are changed togehter with the arp or nd6 mutex.
Came here after reading /etc/rc wrt. the shutdown sequence.
Feedback?
Index: rc.shutdown.8
===
RCS file: /cvs/src/share/man/man8/rc.shutdown.8,v
retrieving revision 1.16
diff -u -p -r1.16 rc.shutdown.8
--- rc.shutdown.8 16 May
On Sun, Apr 23, 2023 at 05:07:30PM +, Klemens Nanni wrote:
> For new installs, it seems adequate to base the number on the actual hardware,
> assuming the CRYPTO volume will stay in that hardware for a while.
>
> The current default of 16 is from old PKCS5 PBKDF2 times and ch
On Thu, May 04, 2023 at 08:43:19AM +0200, Alexander Bluhm wrote:
> To make ND6 mp-safe, I have to guarantee the life time of ln =
> rt->rt_llinfo. This call to nd6_llinfo_settimer(ln) looks strange.
It reads like two distinct cases folded into one overly clever block.
> The complicated logic can
On Sun, May 07, 2023 at 06:22:55PM +0200, Mark Kettenis wrote:
> > Date: Sat, 6 May 2023 22:47:55 +
> > From: Klemens Nanni
> >
> > On Sat, Apr 29, 2023 at 06:47:48PM +, Klemens Nanni wrote:
> > > Installing to a wiped disk on EFI machines suggest
On Sat, Apr 29, 2023 at 06:47:48PM +, Klemens Nanni wrote:
> Installing to a wiped disk on EFI machines suggests MBR not GPT when chosing
> (E)dit because MBR vs. GPT in this manual case is picked based on existing
> data on the disk, not whether it has EFI.
>
> Fix that so us
On Sat, May 06, 2023 at 09:33:05PM +0200, Alexander Bluhm wrote:
> On Sat, May 06, 2023 at 11:11:25AM +0000, Klemens Nanni wrote:
> > pf_osfp.c contains all the locking for these three ioctls, this removes
> > the net lock from it.
> >
> > All data is protected by the
pf_osfp.c contains all the locking for these three ioctls, this removes
the net lock from it.
All data is protected by the pf lock, new asserts verify that.
Beside the pf ioctl handler, pf_match_rule()'s call to pf_osfp_match()
is the only hook into it.
tcpbump still compiles pf_osfp.c without o
On Thu, May 04, 2023 at 05:40:10PM -0600, Todd C. Miller wrote:
> I'm fairly certain that doesn't do what you think it does. When I
> tested it "~/10" behaved the same as "~". The step value is not
> even parsed.
Oh I see, it is actually picking a random minute and ignores steps,
so entries run
On Thu, May 04, 2023 at 03:30:30PM -0600, Todd C. Miller wrote:
> This fixes two issues with the parsing of random values:
>
> 1) A random value with a step is now rejected. For example:
>
> ~/10* * * * echo invalid
I've ben using ~/10 to randomly distribute four similar tasks so that
t
On Wed, May 03, 2023 at 12:22:16AM +0200, Alexander Bluhm wrote:
> Hi,
>
> Some checks in nd6_resolve() do not require kernel lock. The analog
> code for ARP has been unlocked in if_ether.c revision 1.250 since
> 2022/06/27 20:47:10.
Same diff here, thought I sent/committed that already.
OK kn i
Installing to a wiped disk on EFI machines suggests MBR not GPT when chosing
(E)dit because MBR vs. GPT in this manual case is picked based on existing
data on the disk, not whether it has EFI.
Fix that so users get correct instructions and don't end up with legacy
partitioning in fresh installs o
Both walk the list of rulesets aka. anchors, first one yields a count,
second yields a specific's anchor name.
Same data access pattern, different copy out, basically.
pf_anchor_global are contained within pf_ioctl.c and pf_ruleset.c and
fully protected by the pf lock.
Same for pf_main_ruleset a
Same logic and argument as for the parent *S ioctl, might as well have
committed them together:
---
Remove net lock from DIOCGETQUEUES
Both ticket and number of queues stem from the pf_queues_active list which
is effectively static to pf_ioctl.c and fully protected by the pf lock.
On Thu, Apr 27, 2023 at 03:22:10PM +0300, Vitaliy Makkoveev wrote:
> > On 27 Apr 2023, at 15:16, Alexander Bluhm wrote:
> >
> > On Wed, Apr 26, 2023 at 11:17:37PM +0300, Vitaliy Makkoveev wrote:
> >> Route timers and route labels protected by corresponding mutexes. `ifa'
> >> uses references coun
Another approach would be to make installboot(8) -p to retain existing
EFI Sys partitions instead of always recreating them.
This way, it was nothing to do with softraid, but installing on machines
like Apple arm64 depends on existing non-OpenBSD partitions and files on
them.
We hacked 'installbo
On Thu, Apr 27, 2023 at 10:53:03AM +, Klemens Nanni wrote:
> Would be nice to record changes to critical scripts run on state changes
> and have modifications recorded through security(8).
>
> Feedback? Objection? OK?
This gets ugly if you use binary files instead of scripts, so
Would be nice to record changes to critical scripts run on state changes
and have modifications recorded through security(8).
Feedback? Objection? OK?
Index: changelist
===
RCS file: /cvs/src/etc/changelist,v
retrieving revision 1.13
#if 0 since import, APM_CANCEL does not appear anywhere else.
OK?
Index: apmd.c
===
RCS file: /cvs/src/usr.sbin/apmd/apmd.c,v
retrieving revision 1.111
diff -u -p -r1.111 apmd.c
--- apmd.c 8 Mar 2023 04:43:13 - 1.111
+
On Mon, Apr 24, 2023 at 02:07:11PM +, Miod Vallat wrote:
> After suspending a machine with acpithinkpad(4) and resuming, the fan
> senors report a value of 65535 (i.e. 0x) for a few seconds, and
> then start reporting correct values.
I don't see these bogus values on an intel t14 gen3 when
On Tue, Apr 25, 2023 at 04:15:49PM +, Klemens Nanni wrote:
> A clearer version of this diff would use two new bools `expired' and `reject'
> rather than a ternary `reject', but that can be polished and retested later.
Or simpler even, use new `expired' and exist
On Tue, Apr 25, 2023 at 11:44:34AM +0200, Alexander Bluhm wrote:
> Hi,
>
> Mutex arp_mtx protects the llinfo_arp la_... fields. So kernel
> lock is only needed for changing the route rt_flags.
>
> Of course there is a race between checking and setting rt_flags.
> But the other checks of the RTF
(Thought I already committed this months ago, noticed now looking into
bootloaders again...)
GENERIC, efiboot and installboot(8) all have softraid support already,
softraid(4) documents boot support for riscv64,
"just" the ramdisk kernel lacks it.
Still boots fine on the SiFive HiFive Unmatched A
Would be nice to have a backup of it and track changes.
OK? No?
Index: changelist
===
RCS file: /cvs/src/etc/changelist,v
retrieving revision 1.135
diff -u -p -r1.135 changelist
--- changelist 18 Apr 2023 08:50:37 - 1.135
+
On Mon, Apr 24, 2023 at 01:46:17PM +, Klemens Nanni wrote:
> I have on vm.conf, vmd does not need it, but complains:
> Apr 23 17:12:50 atar vmd[79320]: failed to open /etc/vm.conf: No such file or
> directory
>
> We've fixed the same for dhcpleased a year ago, port
I have on vm.conf, vmd does not need it, but complains:
Apr 23 17:12:50 atar vmd[79320]: failed to open /etc/vm.conf: No such file or
directory
We've fixed the same for dhcpleased a year ago, port the diff from there.
Works for me with good, with bad and without /etc/vm.conf.
Feedback? OK?
Ind
On Sun, Apr 16, 2023 at 01:37:30AM +, Klemens Nanni wrote:
> ps(1) -U expects names, top(1) and pgrep(1) -U take numbers as well.
>
> With the new tree view, I start using 'ps -fU55' more often instead of
> 'top -U55' to watch ports builds, but keep doing
>
On Tue, Apr 18, 2023 at 10:44:36PM +, Klemens Nanni wrote:
> On Sat, Apr 15, 2023 at 01:48:02PM +0000, Klemens Nanni wrote:
> > On Fri, Apr 14, 2023 at 11:33:18PM +, Klemens Nanni wrote:
> > > All cases do the same check up first, so merge it before the switch.
>
>
For new installs, it seems adequate to base the number on the actual hardware,
assuming the CRYPTO volume will stay in that hardware for a while.
The current default of 16 is from old PKCS5 PBKDF2 times and changing it in
bioctl(8) is a more invasive change (for later, perhaps).
Thoughts? Feedba
On Fri, Apr 21, 2023 at 11:29:11PM +, Koakuma wrote:
> I noticed that when using `ldomctl status` the utilization value of
> stopped ldoms is always a copy of the previous entry's value,
> which is probably incorrect?
>
> Zeroing utilization value in `ldomctl status` at the start of the loop
>
1 - 100 of 1143 matches
Mail list logo
