LS,
I'm trying to create a backup with PinguyBuilder-v5.1.3 but am running into some unexpected behavior. After installing the backup ISO in a VirtualBox VM it appears ok out-of-the-box, but the sudo command no longer functions as-is because it seems to be owned by the user (uid=1000) i.s.o. by root (uid=0). For example:
<start>
$ sudo
sudo: /etc/sudoers is owned by uid 1000, should be 0
sudo: no valid sudoers sources found, quitting
sudo: unable to initialize policy plugin
<end>
In some blogs the following is suggested: "pkexec chown root:root /etc/sudoers /etc/sudoers.d -R", but all this does is change the first line of the error message to "sudo: /etc/sudoers is world writable". Some background in case it is relevant:
* Hardware = 64-bit Intel Xeon E3-1505M v5 @ 2.80GHz.
* PinguyBuilder version = 1.5.3.
* Base distro = Ubuntu 18.04 installed in a VirtualBox VM (VDI file located on an NTFS filesystem).
Since installing the backup ISO on a VM creates a Live session I'm actually not even sure if the sudo ownership described above is indeed an issue or actually normal behavior (I'm assuming the former because a LiveCD created directly from the Ubuntu18.04 Desktop ISO does not have this 'feature' and sudo can be called without problems). Does anyone know how to fix it? I sure hope that it is possible, because with this problem solved it seems like PinguyBuilder is the perfect application for me!
In case of reply: please keep it simple. I'm not very bright and my knowledge of linux architecture is nearly non-existent![Wink]( "Wink")
I'm trying to create a backup with PinguyBuilder-v5.1.3 but am running into some unexpected behavior. After installing the backup ISO in a VirtualBox VM it appears ok out-of-the-box, but the sudo command no longer functions as-is because it seems to be owned by the user (uid=1000) i.s.o. by root (uid=0). For example:
<start>
$ sudo
sudo: /etc/sudoers is owned by uid 1000, should be 0
sudo: no valid sudoers sources found, quitting
sudo: unable to initialize policy plugin
<end>
In some blogs the following is suggested: "pkexec chown root:root /etc/sudoers /etc/sudoers.d -R", but all this does is change the first line of the error message to "sudo: /etc/sudoers is world writable". Some background in case it is relevant:
* Hardware = 64-bit Intel Xeon E3-1505M v5 @ 2.80GHz.
* PinguyBuilder version = 1.5.3.
* Base distro = Ubuntu 18.04 installed in a VirtualBox VM (VDI file located on an NTFS filesystem).
Since installing the backup ISO on a VM creates a Live session I'm actually not even sure if the sudo ownership described above is indeed an issue or actually normal behavior (I'm assuming the former because a LiveCD created directly from the Ubuntu18.04 Desktop ISO does not have this 'feature' and sudo can be called without problems). Does anyone know how to fix it? I sure hope that it is possible, because with this problem solved it seems like PinguyBuilder is the perfect application for me!
In case of reply: please keep it simple. I'm not very bright and my knowledge of linux architecture is nearly non-existent
