OpenBSD 6.4/amd64
System is installed without games64.tgz and x*.tgz.
When you run syspatch it dies as follows:
# syspatch
ln: /usr/X11R6/bin/X: No such file or directory
because of syspatch64-001_xserver.
Work-around is:
mkdir -p /usr/X11R6/bin
touch /usr/X11R6/bin/X
and then it works:
Get
Hi,
On 7 Dec 2018, at 16:46, Antoine Jacoutot wrote:
> It already does check the sets.
> It's not because of syspatch64-001_xserver.
> It's due to a change introduced in 002-syspatch to fix up the X link but the
> check whether it exists or not was forgotten.
> No real consequence afaik.
Well, o
On 7 Dec 2018, at 23:12, Antoine Jacoutot wrote:
>> Well, openup stops dead complaining that syspatch fails is one consequence
>> and following patches are not installed.
>>
>> Without touching a fake X in a fake /usr/X11R6/bin I cannot patch the system
>> further.
>
> You're talking about som
On 8 Dec 2018, at 08:25, Theo de Raadt wrote:
> Will you start paying attention??
>
> You have been told repeatedly that it is not an error. It is simply a
> message.
>
> Please stop assuming the worst!
Theo, thank you for your wonderful use of language.
I have taken note of your pearls of wi
On 8 Dec 2018, at 09:50, Theo de Raadt wrote:
[...]
> So please take your arrogance elsewhere.
Thank you pot!
Arrigo
P.S. “just a warning” which returns a fail return code is a bug. Contempt does
not make it magically return 0 nor does it make the behaviour correct. Neither
does doing a c&
On 8 Dec 2018, at 10:15, Theo de Raadt wrote:
> If you cannot respect the people who write the software, you probably
> shouldn't run the software.
>
> Just go away.
>
> You are acting like a gigantic dickhead.
Theo, honestly, I actually pay m:tier Platinum support for myself and my
clients,
On 8 Dec 2018, at 10:33, Theo de Raadt wrote:
> how funny. You still don't get it. Noone cares because noone believe you!
OK. Thanks.
Arrigo
On 6 Dec 2022, at 14:59, Dave Voutila wrote:
> The functional changes between releases include driving more vm exits to
> be handled by vmd and not vmm in the kernel. vmd is already quite
> chatty, so it's time to revisit which messages add value.
>
> vcpu_ext_eptviolation sounds more ominous tha
On 6 Dec 2022, at 18:20, Mike Larkin wrote:
> As dv@ pointed out in a previous mail, the eptviolation exit message can
> be ignored (and as he points out, should probably be removed or
[...]
> packets. You could experiment with raising that (it's in
> src/usr.sbin/vmd/virtio.h) to a higher power o
1) Steps to reproduce
Choose one of the following methods:
1.1) boot from install49.iso
1.2) boot from cd49.iso
1.3) boot from bsd.rd installed over a 4.8 install
2) Output (identical with all three methods above), boot always hangs after
"rd0: fixed, 4480 blocks":
boot> boot bsd.rd
booting hd0
10 matches
Mail list logo
