On Tue, Sep 06, 2022 at 09:38:37PM +, Klemens Nanni wrote:
> Noticed when seeing both on
> https://cdn.openbsd.org/pub/OpenBSD/snapshots/riscv64/
> but not in the file.
>
> Feedback? Objection? OK?
ok jsg@
>
> Index: distrib/notes/riscv64/contents
> =
Noticed when seeing both on
https://cdn.openbsd.org/pub/OpenBSD/snapshots/riscv64/
but not in the file.
Feedback? Objection? OK?
Index: distrib/notes/riscv64/contents
===
RCS file: /cvs/src/distrib/notes/riscv64/contents,v
retrieving
On Tue, Sep 06, 2022 at 09:06:41PM +, Klemens Nanni wrote:
> On Sun, Sep 04, 2022 at 07:08:51PM +, Mikolaj Kucharski wrote:
> > Hi,
> >
> > I have strange setup on some of my machines, when I want to encrypt disk
> > where OpenBSD is installed, but still be able to boot them up without
> >
On Sun, Sep 04, 2022 at 07:08:51PM +, Mikolaj Kucharski wrote:
> Hi,
>
> I have strange setup on some of my machines, when I want to encrypt disk
> where OpenBSD is installed, but still be able to boot them up without
> any user interaction, like passphrase entry for CRYPTO softraid(4). I
> ha
On Fri, Aug 19, 2022 at 10:54:42PM +0200, Alexander Bluhm wrote:
> This diff allows to run udp_input() in parallel.
Parts have been commited, below is the diff for -current.
With this diff UDP socket splicing does not work yet as udp_output()
is not MP safe. Also calls from udp_input() to anywhe
Klemens Nanni wrote:
> On Tue, Sep 06, 2022 at 05:50:31PM +, Lucas wrote:
> > Sorry for the noise. I wasn't aware that `set -e` only takes into
> > consideration the last command in an AND-OR list and not the exit status
> > of the AND-OR list itself.
>
> What is the status of the list itself
On Tue, Sep 06, 2022 at 06:00:25PM +, Klemens Nanni wrote:
> On Tue, Sep 06, 2022 at 05:50:31PM +, Lucas wrote:
> > Sorry for the noise. I wasn't aware that `set -e` only takes into
> > consideration the last command in an AND-OR list and not the exit status
> > of the AND-OR list itself.
>
On Tue, Sep 06, 2022 at 05:50:31PM +, Lucas wrote:
> Klemens Nanni wrote:
> > Yes I want it to fail, just like reorder_kernel.sh using `set -o errexit'
> > does with
> > [ -f /etc/bsd.re-config ] && config -e -c /etc/bsd.re-config -f bsd
> >
> > If the config file exists but is invalid, I
Klemens Nanni wrote:
> Yes I want it to fail, just like reorder_kernel.sh using `set -o errexit'
> does with
> [ -f /etc/bsd.re-config ] && config -e -c /etc/bsd.re-config -f bsd
>
> If the config file exists but is invalid, I expect programs using it to fail.
Sorry for the noise. I wasn't
On Tue, Sep 06, 2022 at 05:12:33PM +, Lucas wrote:
> Klemens Nanni wrote:
> > On rare occasions, I need 'disable xxx' in /etc/bsd.re-config to be able to
> > boot a system, e.g. to ignore quirky devices crashing drivers during attach.
> >
> > bsd.re-config(5) currently applies to GENERIC(.MP)
Klemens Nanni wrote:
> On rare occasions, I need 'disable xxx' in /etc/bsd.re-config to be able to
> boot a system, e.g. to ignore quirky devices crashing drivers during attach.
>
> bsd.re-config(5) currently applies to GENERIC(.MP) /bsd alone, but /bsd.rd
> and /bsd.upgrade RAMDISK kernels will
On Sat, Sep 03, 2022 at 01:50:28PM +0300, Pavel Korovin wrote:
> After these changes, OpenBSD VMware guest's clock is galloping into the
> future like this:
> Aug 31 02:42:18 build ntpd[55904]: adjusting local clock by -27.085360s
> Aug 31 02:44:26 build ntpd[55904]: adjusting local clock by -116.2
On rare occasions, I need 'disable xxx' in /etc/bsd.re-config to be able to
boot a system, e.g. to ignore quirky devices crashing drivers during attach.
bsd.re-config(5) currently applies to GENERIC(.MP) /bsd alone, but /bsd.rd
and /bsd.upgrade RAMDISK kernels will require the same quirks to avoid
On Tue, Sep 06, 2022 at 04:00:39PM +0200, Moritz Buhl wrote:
> Hi,
> here is the most recent diff for the libc part of send and recvmmsg.
> This requires a libc minor bump and therefore should be coordinated
> after snapshots are building normally again.
>
> To my understanding the minor bump itse
Hi,
here is the most recent diff for the libc part of send and recvmmsg.
This requires a libc minor bump and therefore should be coordinated
after snapshots are building normally again.
To my understanding the minor bump itself should not cause problems
in ports anymore.
mbuhl
Index: lib/libc/Sy
On 28.08.22 14:22, Klemens Nanni wrote:
Every platform ought to set `stages', `stage1' and optionally `stage2'
in md_init(), otherwise passing explicit files results won't work as
`stages' is zero-initialised and no default path is set:
# installboot -v sd0 /root/BOOTAA64.EFI
usa
On Tue, Sep 06, 2022 at 10:14:02AM +0200, Mark Kettenis wrote:
> > Date: Tue, 6 Sep 2022 01:16:47 +
> > From: Klemens Nanni
> >
> > The installer considers a disk a root disk if 'a' is FFS and contains
> > expected files.
> >
> > Furthermore, unattended upgrades will always install to the f
On Sun, Sep 04, 2022 at 02:50:10PM +1000, Jonathan Gray wrote:
> On Sat, Sep 03, 2022 at 05:33:01PM -0500, Scott Cheloha wrote:
> > On Sat, Sep 03, 2022 at 10:37:31PM +1000, Jonathan Gray wrote:
> > > On Sat, Sep 03, 2022 at 06:52:20AM -0500, Scott Cheloha wrote:
> > > > > On Sep 3, 2022, at 02:22,
> Date: Tue, 6 Sep 2022 01:16:47 +
> From: Klemens Nanni
>
> The installer considers a disk a root disk if 'a' is FFS and contains
> expected files.
>
> Furthermore, unattended upgrades will always install to the first root
> disk that is found.
>
> This works fine on machines with only on
19 matches
Mail list logo
