LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 03-30-2016, 09:03 PM   #46
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163

Quote:
So no matter which OS you are in you can access any of the other Linux Installs without incident of an error. Correct?
I can access the other files on the other 2 installs while Apricity OS is up and running but I can not copy and paste certain files with an X on them that do throw an error: coping; permission denied.

Quote:
by Live user you are referring to that being you starting up a Linux Live Session resting on a USB Stick and NOT an actual installed system?
The Live User should of went away after the installation. It did not and is holding the id of 1000.

Quote:
Where your other two Systems already installed UID 1000?
Than yes.
Today no. I installed Apricity OS in place of LM Cinnamon so now the system looks like this:
Code:
/dev/sda 128 GB HDD Mint KDE
/dev/sdb 500 GB HDD LM Mate
/dev/sdc 120 GB SSD Apricity OS
Quote:
who is live User, and who is Sifu?
Live user is what the Installer put on the system and gave it the id of 1000.
The fresh install made Sifu which is the regular user of the system and gave him an id of 1001.

-::-The installer assigned the live user the id of 1000 which should have been given to Sifu.-::-

It looks like the Live User file is a back door.-
 
Old 04-01-2016, 08:07 PM   #47
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163
BW-userx:
When you have time tell me what your take is on this situation.
I answered your questions in the previous post the best way I could.-
 
Old 04-02-2016, 08:53 AM   #48
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (current), FreeBSD, Win10, It varies
Posts: 9,951

Rep: Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146
Quote:
The Live User should of went away after the installation. It did not and is holding the id of 1000.
did you remove that USBStick and still getting that LiveUser and UID 1000? if yes or no.

this is what I'd being trying to do.

find out that first bit first and if you are still getting this UID 1001 with that one OS, without the USBStick still plugged in.

the main objective
is to get all three systems to have all three users , one user for each system to have that same UID.


now all you have to so is have nothing plugged into your USB Ports to interfere. You boot up using just your internal HDD. Grub kicks in you pick this Apricity OS boot into it check your users UID if t is 1001. Whereas the other two is 1000.

then just log out, change ttys. Ctrl+Alt+F(1-9) log in root user. You don't have to even try to startx, just try changing that users UID to 1000. if it will not let you. then slap it to get the frustration out of you, or yell at your sister and just blame her for anything, even if she is not there. hehe just because she is your sister. if no sisters then just yell. Reclaiming your posture.

then try the same thing on the other two systems. Go to tty and log in as root user and try to change your users UID to 1001. remembering that for sake of argument with the systems, use that very same user name for all three of your systems, along with the very same UID.

if it does not take 1001, then let trial and error mode kick in until you get all three to take the same UID number. what ever range that system allows for user UID's. Remember that number does not actually matter what it is, in a long run (per sa) only that all three match.

remember as well the "normal" user cannot be logged in the system while you are working on changing that users UID only the administrator being the ROOT user account can be logged in to change it. you have to be in that ROOT user account while chaining it, and that user account cannot be logged into the system while doing so.

yes, it is going to be a lot of rebooting and logging into systems to see if it is working yet work. So prepare your mind to deal with that stress before proceeding.

MOD:
what I think is going on with your install of Apricity OS is that the way they that created it have the USB-Live user within that OS already has UID 1000, so when you're installing it that system it uses the next available UID which is 1001. This is why it is not working out as easily as it should for you. Whereas mine does not do that, it is created different. It just copies the contents over onto the hard drive so I get UID 1000 when I install off of it.

that is just my logical deduction of the situation with no research to back it up.

Last edited by BW-userx; 04-02-2016 at 09:13 AM.
 
Old 04-02-2016, 08:58 AM   #49
suicidaleggroll
LQ Guru
 
Registered: Nov 2010
Location: Colorado
Distribution: OpenSUSE, CentOS
Posts: 5,573

Rep: Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137
There is absolutely no need for any trial and error or guesswork.

As I explained before, there are three possible scenarios, each with different actions.
1) Your system(s) with UID 1000 do not currently have a 1001, so change UID 1000 to 1001
2) Your system(s) with UID 1001 do not currently have a 1000, so change UID 1001 to 1000
3) If neither of the above applies, then choose a new UID that's free on all of them, probably UID 1002 but all you have to do is just LOOK at /etc/passwd on the three systems to find one, then change all of them to that

This is not a complicated problem, just stop hammering away at the keyboard, take a step back, and look at the situation. If you can choose a UID that a couple of systems already use, that makes your life a little easier, but if not, so what? Just pick a new UID and move on with your life.

A long time ago I got fed up with the different rules on all systems, so I made my UID 3000 across the board. That's never in use on ANY distro (at least not yet), so I never have this problem. I could have chosen any number, it really doesn't matter, you can use any UID up to 65535.

Just open up /etc/passwd on all three systems and see what's in use, by who, and what isn't...then go from there.

Last edited by suicidaleggroll; 04-02-2016 at 09:11 AM.
 
Old 04-02-2016, 09:18 AM   #50
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (current), FreeBSD, Win10, It varies
Posts: 9,951

Rep: Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146
Quote:
Originally Posted by suicidaleggroll View Post
There is absolutely no need for any trial and error or guesswork.

As I explained before, there are three possible scenarios, each with different actions.
1) Your system(s) with UID 1000 do not currently have a 1001, so change UID 1000 to 1001
2) Your system(s) with UID 1001 do not currently have a 1000, so change UID 1001 to 1000
3) If neither of the above applies, then choose a new UID that's free on all of them, probably UID 1002 but all you have to do is just LOOK at /etc/passwd on the three systems to find one, then change all of them to that
is all trial and error work. if one does not work then it is an error so try the next one. now you are guessing (hoping) it will work so yes it is trail and error work that is involved.

I said the same thing you did. I just worked it different. if 1000 does not work then try 1001 for all of them if that don't work then try what ever number will.

three steps just like you told him too. so we are just telling him to do the same thing only differently.

Like I told him that number does not matter as long as they all match. you did just that by using 3000 for IUD.

Quote:
A long time ago I got fed up with the different rules on all systems, so I made my UID 3000 across the board. That's never in use on ANY distro (at least not yet), so I never have this problem. I could have chosen any number, it really doesn't matter, you can use any UID up to 65535.
again, we are just telling him to do the same thing only differently.

Last edited by BW-userx; 04-02-2016 at 09:24 AM.
 
Old 04-02-2016, 09:59 AM   #51
suicidaleggroll
LQ Guru
 
Registered: Nov 2010
Location: Colorado
Distribution: OpenSUSE, CentOS
Posts: 5,573

Rep: Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137Reputation: 2137
Quote:
Originally Posted by BW-userx View Post
is all trial and error work. if one does not work then it is an error so try the next one. now you are guessing (hoping) it will work so yes it is trail and error work that is involved.

I said the same thing you did. I just worked it different. if 1000 does not work then try 1001 for all of them if that don't work then try what ever number will.

three steps just like you told him too. so we are just telling him to do the same thing only differently.
That's a waste of time. It will only fail if that UID is already in use. There is no reason to go through the hassle of booting into three different systems over and over again and repeatedly trying multiple UIDs until you finally find a combination that works. That is trial and error, and it's pointless in this case.

He can see ahead of time, on all three systems simultaneously, which UIDs will work and which will fail. Then he just needs to boot into each system ONCE and set the UID appropriately. This is not trial and error, this is looking at the situation as a whole and picking the right answer from the start.

The three numbers I listed were not three steps, they were three options. You look at /etc/passwd on all three systems first, then choose ONE option depending on what the UID situation looks like, and implement it. That's the opposite of trial and error.
 
Old 04-02-2016, 10:20 AM   #52
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (current), FreeBSD, Win10, It varies
Posts: 9,951

Rep: Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146
Quote:
Originally Posted by suicidaleggroll View Post
That's a waste of time. It will only fail if that UID is already in use. There is no reason to go through the hassle of booting into three different systems over and over again and repeatedly trying multiple UIDs until you finally find a combination that works. That is trial and error, and it's pointless in this case.

He can see ahead of time, on all three systems simultaneously, which UIDs will work and which will fail. Then he just needs to boot into each system ONCE and set the UID appropriately. This is not trial and error, this is looking at the situation as a whole and picking the right answer from the start.
MOD:
it is still having to do what? reboot three times at least to see what numbers will work. it is all trial and error. you're telling him what I did not know is only cutting it down to try and eliminate it. GOOD for you thank you for filling in the blanks ... go have a coffee and know that you knew more then I did. Because I didn't feeel like looking all of that up first, I just took from what I already knew. and it'd still have worked either way. picking 3000 is a good guess to eleminte that looking into the /etc/passwd too. makes me wonder if you looked before you leaped. not that I really care. the only thing I care about in this post is getting that persons problem solved. be it by any means whatsoever.

the same objective is getting all three to have the same UID.


that is why it is allowed to have more then one person in here helping taking the knowledge pool and making it bigger so that everyone benefits from it. not just one person.


enjoy your coffee.
END MOD:
Quote:
The three numbers I listed were not three steps, they were three options. You look at /etc/passwd on all three systems first, then choose ONE option depending on what the UID situation looks like, and implement it. That's the opposite of trial and error.
how else are you going to change them to get them numbers to all match if 1001 or 1000 does not work?


then he could just do what you did and get fed up and use IUD 3000 then he still has to go into each system separately to change them, and why not check to be sure it works how else will he know. so Yes it may have to be done, as I implied.

you just gave him a more informed how to, whereas I was just using the basic knowledge of how things work in Linux. Knowing only about UID's but not the range or /etc/passwd file and what it can tell someone.

so regardless we are still telling him the same thing. if one does not work 1001 then try 1000 if that does not work use something other then 1000 or 1001. where you have him the next probable number and how to find out I did not, only knowing that there is a range of numbers one can use, what they are I did not know, I did not need to know. nor did he really.

using logic and basic understanding of Linux. it has to have a range of numbers because it keeps signing UID numbers to everything that gets a group. therefore logic states that their has to be a range of numbers being used.

why are you looking for fault in me and what I have said? when you have done that very same thing, you had to have booted into all of your systems to change them all to UID 3000 so that they'd all matched.

Last edited by BW-userx; 04-02-2016 at 10:32 AM.
 
Old 04-02-2016, 08:26 PM   #53
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163
I've been sick the last 2 days in a row so I'll work on this tomorrow and let you know how things go.
 
Old 04-05-2016, 04:18 PM   #54
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163
Success

I logged in to tty as 'root' and ran these cmd's and had complete success at the next fresh boot.

Code:
usermod -u 1000 sifu
groupmod -g 1000 group

find / -user 1001 -exec chown 1000 {} +
find / -group 1001 -exec chgrp 1000 {} +
For some reason running the last string returned:
Code:
run/user/120/gufs : permission denied
The owner of the machine can now mnt any HDD he wants and cp and paste anything. He says: "Thank You"

suicidaleggroll & BW-userx thank you for staying with me and helping me understand and fix this uid issue.
 
Old 04-05-2016, 04:24 PM   #55
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (current), FreeBSD, Win10, It varies
Posts: 9,951

Rep: Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146Reputation: 2146
Quote:
Originally Posted by Ztcoracat View Post
I logged in to tty as 'root' and ran these cmd's and had complete success at the next fresh boot.

Code:
usermod -u 1000 sifu
groupmod -g 1000 group

find / -user 1001 -exec chown 1000 {} +
find / -group 1001 -exec chgrp 1000 {} +
For some reason running the last string returned:
Code:
run/user/120/gufs : permission denied
The owner of the machine can now mnt any HDD he wants and cp and paste anything. He says: "Thank You"

suicidaleggroll & BW-userx thank you for staying with me and helping me understand and fix this uid issue.
that warning is no big deal, and I'd been wondering about you and that problem. I am so happy you finally got that head ache out of the way. !!!!!
.
 
Old 04-05-2016, 04:47 PM   #56
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163Reputation: 1163
Quote:
Originally Posted by BW-userx View Post
that warning is no big deal, and I'd been wondering about you and that problem. I am so happy you finally got that head ache out of the way. !!!!!
.
I'm happy too that headache is gone.
It's nice to have things run properly.

Thanks again-
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Error opening /dev/sdb:Permission denied Neo@Matrix Linux - Newbie 20 09-20-2011 09:39 PM
excuting file resuls in permission denied error Panceisto Linux - Newbie 3 04-22-2010 03:12 AM
Acrobat Reader "error opening document - permission denied" Robhogg Linux - Software 5 04-25-2008 08:44 AM
Error opening type hash map aliases.db : permission denied Tazzmanian Linux - Software 2 08-24-2004 11:56 AM
permission denied when opening directory pilot1 Linux - General 1 10-23-2002 08:27 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 04:57 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration