Change my GID to 1000?

Hello,

Requirements:

I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata

OpenMandriva Lx version:

Rome 25.06 x86 build 4008 (Clean install)

Desktop environment (KDE, LXQT…):

KDE X11

Description of the issue (screenshots if relevant):

Changing UID & GID to match /home on an external SSD - TLDR: how do I change system GID 1000 to be “kev”?

Relevant informations (hardware involved, software version, logs or output…):

[root@Desktop kev]# groupmod -g 1007 lusers
groupmod: GID '1007' already exists
[root@Desktop kev]# groupmod -n lusers 1007
groupmod: group '1007' does not exist
[root@Desktop kev]# groupmod -n lusers vboxsf
groupmod: group 'lusers' already exists
[root@Desktop kev]# groupmod -n kev vboxsf
groupmod: group 'kev' already exists
[root@Desktop kev]# groupmod -n kev oldkev
groupmod: group 'oldkev' does not exist
[root@Desktop kev]# groups kev
kev : kev lp wheel audio video users input kvm render pipewire lpadmin network storage sambashare autologin

I’m trying to set my UID and GID to 1000:1000.

I followed this OM tutorial here → LINK

…but I obviously don’t fully know what I’m doing!

Anyway, the first part worked and I managed to change my UID from 1001 back to 1000 and am now able to login to my encrypted /home, but I am unable to change my (system) GID from 1007 (vboxsf) to be 1000 (kev). None of the commands I ran (see above) worked.

My /home is a LUKS partition on a 2nd SSD where the permissions are set as 1000:1000, but OM wants it to be 1000:1007.

I want to keep it as 1000:1000 (I have my reasons), should I just leave it as it is or should I change it to 1000?

Will it cause corruption/problems on the LUKS partition as new files are saved as 1000:1007?

So the actual question is - how do I rename group 1000 from vboxsf to kev?

Thankyou, regards.

I think I solved it myself -

[root@Desktop kev]# groupmod -n dunno vboxsf
[root@Desktop kev]# groupmod -n oldkev kev
[root@Desktop kev]# groupmod -n kev dunno
[root@Desktop kev]# groups kev
kev : oldkev lp wheel audio video users input kvm render pipewire lpadmin network storage sambashare autologin
[root@Desktop kev]# groupmod -n dunno vboxsf

Does that look OK, or have I done something stupid?

Regards.

It’s not wise to do what you are doing. Other things could break. Make sure you are backing up before you do things like this, and just restore it to a new ~ partition/mount/etc… in your new distro install.

I went through the same hassle on OMLx to go from 1001:1001 to 1000:1000 so that I could mount NFS shares. By all means, change the UID and GID to 1000:1000, the system was “broken” after you installed it so there is no concern about breaking it.

1 Like

Thanks for replying, yes backing up is always a good idea. I’ll do that now and then just run it for a while and see if anything breaks! Regards.

Hahaha, yeah there is one other issue but I’ll start a new post for that one. Regards.

You should also make sure you are doing this. I believe there is a post in Support or Resources that covers this.

I did, I linked the page I found in my OP above. It contained some info but the last part didn’t work, that’s why I posted here.

Regards.

From the How-to:

After installation boot to console mode. Login as root. (This also works on an existing system in test situation.)

# usermod -u 1000 user

# groupmod -g 1008 lusers

# groupmod -g 1000 user

# exit

$ sudo chown -R user:user $HOME

Reboot.

Where did you discover to use the -n option for groupmod?

https://man7.org/linux/man-pages/man8/groupmod.8.html

       -n, --new-name NEW_GROUP
           The name of the group will be changed from GROUP to NEW_GROUP
           name.

From experimenting with the output of groupmod --help. The line -n, --new-name NEW_GROUP didn’t make any sense to me, so I just guessed at how it worked - and got lucky!