Skip to main content

su: Sorry on FreeBSD

When running su on FreeBSD and you are getting su: Sorry that could mean that the user is not part of the wheel group. To fix this, do:

  1. Login as root, this can be rebooting the machine or open another TTY terminal (Alt+F2 might help).
  2. Re-mount root filesystem for read/write operation
  3. #: mount -u -w /
    
  4. Add user to the wheel group. Assume below that u1 is the user that will be added to the group
  5. #: pw usermod u1 -G wheel
    
  6. Remount root filesystem back to read-only
  7. #: mount -u -r /
    
If you go back to the psuedo terminal of the u1 user, you should be able to run su this time.

Reference:
https://graspingtech.com/freebsd-fix-su-sorry-message/

Comments

Popular posts from this blog

The following add-ins could not be started MonoDevelop.GnomePlatform

Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re