Open zorbathegreek opened 2 years ago
Your title is confusing. So for me, reading implies that vboxusers:*:920: is missing /etc/group.
While reading your Explanation, that is not the case.
So this is not a bug. It is working has been intended by the FreeBSD port's maintainer.
It is a feature request, not a bug, but that could become problematic.
What happens if there are multiple users and they are all added, but we want to restrict the access from some users.
This request is not that simple.
Sorry for that, I was confused myself.
AFAIR,
On Wed, Mar 23, 2022 at 10:53 AM Eric Turgeon @.***> wrote:
Your title is confusing. So for me reading it implying that vboxusers:*:920: is missing /etc/group.
While reading your Explanation, that is not the case.
So this is not a bug. It is working has been intended by the FreeBSD port's maintainer.
It is a feature request, not a bug, but that could become problematic.
What happens if there are multiple users and they are all added, but we want to restrict the access from some users.
This request is not that simple.
— Reply to this email directly, view it on GitHub https://github.com/ghostbsd/issues/issues/54, or unsubscribe https://github.com/notifications/unsubscribe-auth/AETTVDJP4ZMUHXTZ6GGHKO3VBLZ2PANCNFSM5RLSHMKA . You are receiving this because you authored the thread.Message ID: @.***>
-- mobile +49 17676524576 "Artificial intelligence will never match natural stupidity."
I will not close it yet in case I come up with an idea to have users added to the VirtualBox group.
issue moved from ghostbsd/ghostbsd-src to ghostbsd/issues
Version
22-03-20
Explain the issue and what happens
I installed VirtualBox from Software Station, then set up a virtual machine. Went through the routine steps; starting with "New" - selected all the obvious choices. It reported an error when I fired it up:
Googled the issue and found that probably the .iso file was corrupted. But the checksum was ok.
The Telegram group proposed that my username was probably missing in /etc/group and voilá Added my username.Still the same error.Rebootet and now the VM works.
Explain how to reproduce the bug?
I guess the real issue is that the VirtualBox installer didn't include the in the /etc/group but I did not try to replicate that.
The issue for me was that I could not get a VM running and that happened every time I fired up the VM within VirtualBox though all the setup choices I had made were reasonable and the .iso file was ok.
What is the Expected behavior (if applicable)
Start a VM after setting it up with it's name, OS, RAM, hard drive, etc, and the (sha256sum verified) .iso file
Additional context (if applicable)
Adding in /etc/group is not sufficient; the error is reported until after reboot.