Including the virtualbox port maintainer in the loop. Any thoughts? Ronald. On Sun, 04 Mar 2018 22:04:05 +0100, Ronald Klop <ronald-lists_at_klop.ws> wrote: > Hi, > > I'm trying to use vboxfs on # uname -a > FreeBSD sjakie 12.0-CURRENT FreeBSD 12.0-CURRENT #4 r329516M: Sun Feb 18 > 12:37:36 CET 2018 > ronald_at_sjakie:/data/ronald/obj-freebsd-current/data/ronald/freebsd-current/amd64.amd64/sys/GENERIC-NODEBUG > amd64 > > I run VirtualBox on Windows 10 using FreeBSD 12 as a guest. > virtualbox-ose-additions-5.2.8 is installed by pkg. > I configured C:\Temp as 'win' in VirtualBox. > > Modules are loaded: > kldstat | grep vbox > 5 2 0xffffffff82e26000 2d9e0 vboxguest.ko > 13 1 0xffffffff82e7e000 1f320 vboxvfs.ko > > [root_at_sjakie ~]# mount_vboxvfs win /mnt/win > [root_at_sjakie ~]# ls /mnt/win/ > ls: /mnt/win/: Not a directory > > I tried different Windows directories and different users/rights on the > /mnt/win directory. > Am I doing something wrong? > I can't find a lot documentation about vboxvfs. > > Regards, > Ronald. > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe_at_freebsd.org"Received on Thu Mar 08 2018 - 09:49:11 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:15 UTC