Rom transfer

mitu

The above looks to be more so my answer. Anyone disagree?

Disagree with what ? Do you actually have an error message that you received when booting the system ?

korn16ftl3

@mitu haven't gotten as far as trying to boot anything as of yet but ud imagine I'd have to set the permissions back to the way they were

mitu

@korn16ftl3 Just try and boot first.

korn16ftl3

@mitu ok will do and if there are issues I suppose I found the answer lol

korn16ftl3

Well I'm going to chown that folder again I guess I got some errors when I tried shutting down retropie.

alt text

Clyde

@korn16ftl3 Please post the output of the command, run on Retropie on the screen you posted:

ls -l /usr/lib/sudo/sudoers.so

On my Retropie, the output is

-rw-r--r-- 1 root root 308944 Dec  9 18:57 /usr/lib/sudo/sudoers.so

The first three-digit set rw- says that the owner has read/write permissions (rw), but no (-) execution permissions. The second set r-- says that the owning group can read (r), but not write or execute (--). The third set says the same for others (i.e. non-owners). The owner is root and the owning group is also root (output: root root).

Normally, you could set the right permissions by these commands in Retropie:

sudo chown root:root /usr/lib/sudo/sudoers.so
sudo chmod 644 /usr/lib/sudo/sudoers.so

The 644is the octal equivalent of rw-r--r--, each number representing one three-digit set (see Octal modes). BUT with your messed-up permissions, it may be that sudo won't be working in your Retropie system. Then, you'd have to do it on Lubuntu:

sudo chown 0:0 /media/lubuntu/retropie/usr/lib/sudo/sudoers.so
sudo chmod 644 /media/lubuntu/retropie/usr/lib/sudo/sudoers.so

Here, I'm using Retropie's root user id 0 in case that your Lubuntu has a different user id for root (which shouldn't be the case).

korn16ftl3

I just wiped the whole sd card again sudo was refusing to work.....lesson learned I suppose glad I didn't have anything more than rom transfers on the card. It's ok I decided I wanted to take the time to pull the Japanese roms and put them in their own folder anyways

I was able to get rid of 2 of the 3 errors by crating a user on my lubuntu live usb called pi however I couldn't get the sudo set back to 0 and from some googling it was better to perform a fresh install after the error I was getting that broke sudo

Clyde

@korn16ftl3 Although I usually prefer fixing a problem to a complete wipe + reinstallation (infamous as "the Windows way" among many Linux users), in your case it may've been the best choice, as a messed-up root tree / probably would've been prone to more errors.

Just another crumb of Linux knowledge: Linux differentiates users not by their names but by their user id (uid). The -n option of ls shows the uids and group ids (gids) instead of names:

ls -l -n /path  # shorter: ls -ln /path

You can show a user's uid and gid by using the id command:

id     # uid + gid of current user
id pi
id root

korn16ftl3

@clyde thanks for sharing that, normally when it comes to linux I also prefer fixing the problem at hand as it forces me to go further in depth with the OS and learn more about it or at least how to resolve problems and what I did, in this case....I already figured out my screw up before even realizing what I did after I did it so that on its own (and because this is my first build for this kind of thing) was worth the loss of maybe a couple hours of work that can easily be made up

korn16ftl3

Well I guess I got this figured out and on the way learned WHAT NOT TO DO lol.

Now to figure out this mausberry bit so I can get the switches to behave how I would like.....

Power = Power on and proper shutdown when powered on

Reset = when in emulation reset back to retropie gui/main screen, when at retropie main screen and reset is hit a proper reset is performed

Keep your eyes peeled for another noon post, because I've read a lot about these mausberry switches and am quite lost how to get the performance I would like.

I will make another thread for that tho as its completely off topic for this one.