"vitmau...@gmail.com":
> My /var/log/daemon regarding the issue:
> mountd[91001]: Refused mount RPC from host 192.168.1.4 port 57264
The client's mount request didn't come from a reserved port, i.e. <1024.
OpenBSD's mountd(8) does not accept this.
--
Christian "naddy" Weisgerber
W dniu 29.12.2022 o 17:29, vitmau...@gmail.com pisze:
I have a NFS share on OpenBSD with a Windows 10 and a FireOS clients
(through VLC and Kodi). Windows 10 mounts the NFS share without issue,
but the Fire OS can't mount it either through VLC or Kodi. Before
moving to OpenBSD I had a NFS share
I have a NFS share on OpenBSD with a Windows 10 and a FireOS clients
(through VLC and Kodi). Windows 10 mounts the NFS share without issue,
but the Fire OS can't mount it either through VLC or Kodi. Before
moving to OpenBSD I had a NFS share on Fedora 34 and all my systems
could mount it.
I've
On Thu, Dec 29, 2022 at 04:05:44PM +0100, Jurjen Oskam wrote:
> > It has been this way since day-1 of -B -- unclear if you want to call
> > it expected, feature or bug :-)
>
> Ah, thanks! No need to dive into it then, and hopefully this thread
> will pop up in searches for others running into the
> It has been this way since day-1 of -B -- unclear if you want to call
> it expected, feature or bug :-)
Ah, thanks! No need to dive into it then, and hopefully this thread
will pop up in searches for others running into the same phenomenon.
:)
Regards,
Jurjen
Op do 29 dec. 2022 om 16:01
Am 29.12.2022 15:40 schrieb Jurjen Oskam:
From the host dmesg I noticed the following line:
It has been this way since day-1 of -B -- unclear if you want to call
it expected, feature or bug :-)
Noticed this early on the vagrant+packer works.. -B is adhoc and
thus vmd is not aware of it after
Hi,
Today I first started to use vmm(4) virtual machines (on amd64 7.2 with all
syspatches applied, dmesg of the host is below). From what I've seen so far
I'm quite happy with it, it's very elegant and straightforward how all the
components work together.
One thing I noticed is that when a VM
I fixed it by booting into snapshots install72.img (-stable kernel turns out to
not boot -current) and going thorugh the upgrade process. installboot must've
been what I needed to do.
For the sake of the archive: Initially I couldn't upgrade because I exited to
shell from the installer to
On Wed, Dec 28, 2022 at 09:01:26PM +, Chris wrote:
> After that however, the bootloader no longer prompts me for the full disk
> encryption passphrase. Previously it was prompting me for the FDE passphrase
> before it tried to boot the broken kernel.
I'm assuming that you only have a single
9 matches
Mail list logo
