LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
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-20-2016, 11:09 PM   #31
John VV
LQ Muse
 
Registered: Aug 2005
Location: A2 area Mi.
Posts: 17,502

Rep: Reputation: 2617Reputation: 2617Reputation: 2617Reputation: 2617Reputation: 2617Reputation: 2617Reputation: 2617Reputation: 2617Reputation: 2617Reputation: 2617Reputation: 2617

-- OT --

you know this would be a good thread to point new to linux users to
the lowest post count is what 4000+

even us old timers have FUN and problems sometimes
 
1 members found this post helpful.
Old 03-22-2016, 10:49 AM   #32
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
@OP
Quote:
After reading this I'm thinking that I need to use the chmod command because I can not access the files from LM when I have Arch Linux up and running and vice versa.

http://linuxcommand.org/lc3_lts0090.php

BTW this is not my machine so I have to be careful.

Arch is installed to the 500 GB WD drive, LM KDE is installed to the 128 SSD, & LM Cinnamon to the 120 Hitachi HDD.
still struggingly along? let me get this straight.

The operator will be in one of the Linux OS and need to get access to the other two hdds? How and why? root can access them if he has password to become SU then no problems. Drop to SU then do what he got a do then get out.

if operator needs to be in user mode when accessing and maybe mounting them thus removing the auto mount it should be doing in each OS. Why is not the changing owner:user to the entire drive or at least the /home partitions so as to not mess up the rest of the system that needs to be root, not working?



one time I was having a problem setting permissions on a hdd using command line, not working for me for whatever reasons, said self, this is crazy shit, fix it. Then I replied to myself, yes self I will. Watch me.

I opened up a FileManager (pcmanfm) , under root , then clicked on the HDD selecting it, then right clicked in the hdd (right side panel) then under "folder properties" I changed owner user, then in the "permissions" tab I changed everything to.

Code:
View Content - anyone
Change content - anyone
Access content  - anyone
clicked ok, it recessively set everything (changed all of the permissions) within the entire HDD to those permissions needed to solve my problem. I was now able to read, write, and execute off of that HDD. Done deal.
but that is me.

Last edited by BW-userx; 03-22-2016 at 11:15 AM.
 
Old 03-22-2016, 11:30 AM   #33
suicidaleggroll
LQ Guru
 
Registered: Nov 2010
Location: Colorado
Distribution: OpenSUSE, CentOS
Posts: 5,573

Rep: Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138
Quote:
Originally Posted by BW-userx View Post
@OP


still struggingly along? let me get this straight.

The operator will be in one of the Linux OS and need to get access to the other two hdds? How and why? root can access them if he has password to become SU then no problems. Drop to SU then do what he got a do then get out.

if operator needs to be in user mode when accessing and maybe mounting them thus removing the auto mount it should be doing in each OS. Why is not the changing owner:user to the entire drive or at least the /home partitions so as to not mess up the rest of the system that needs to be root, not working?



one time I was having a problem setting permissions on a hdd using command line, not working for me for whatever reasons, said self, this is crazy shit, fix it. Then I replied to myself, yes self I will. Watch me.

I opened up a FileManager (pcmanfm) , under root , then clicked on the HDD selecting it, then right clicked in the hdd (right side panel) then under "folder properties" I changed owner user, then in the "permissions" tab I changed everything to.

Code:
View Content - anyone
Change content - anyone
Access content  - anyone
clicked ok, it recessively set everything (changed all of the permissions) within the entire HDD to those permissions needed to solve my problem. I was now able to read, write, and execute off of that HDD. Done deal.
but that is me.
You can't change the permissions on a drive that contains another OS without breaking said OS. If he wants to be able to access another OS stored on his drive without becoming root or breaking the other OS by screwing up the permissions and/or ownership, he needs to modify his UID on either or both systems so they match.

For a neutral "3rd-party" drive that doesn't contain an OS, but that all OSs need to access, he could change the permissions to 777 so ownership doesn't matter, but that's not exactly a great security model...

Last edited by suicidaleggroll; 03-22-2016 at 11:34 AM.
 
Old 03-22-2016, 11:48 AM   #34
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
You can't change the permissions on a drive that contains another OS without breaking said OS. If he wants to be able to access another OS stored on his drive without becoming root or breaking the other OS by screwing up the permissions and/or ownership,
that is why I said at least in the /home and not the entire system.

Quote:
he needs to modify his UID on either or both systems so they match.
I know also, that I was gaining access to another drive with an Linux OS installed on it via external hdd. I did not do anything with the User ID but never checked it either, so I have no idea if they matched or not, and I actually forget the steps I took to gain access to the /home directory as well.

I'd have to install a system on one of my external HDDs to figure it out again. But your Logic sounds sound.

if the user name is the same in each hdd as was mine, I still did not have that much of a problem as it seems this one here is giving OP in gaining access to other hdds, as mine was via USB Port (not that it would matter) same user name, IUD may have just been the same as well I never checked.

then to each HDD separately he would need matching UID to all three HDD's and do this in each system separately one at a time obviously syncing all three hdd to the same IUD. but that too would limit the usage to just what that one owner IUD is attached to while roaming around in the other HDD's. If only One User to each HDD /OS then that should theologically work.

but for user land only /home directory that is. Permissions (should) only need to be the same giving that same user permissions to access each drive it should not matter if he is the only one using this system, one OS at a time with him being the only user given to each OS.

in other words, their is only one user to each OS, and he is it and he can only be in one system at a time, because they are all attached to the same PC/Laptop?

then it would be the permissions that are attached to each home dir in each hdd that are now in sync and attached to the /home/user instead of the IUD being synced to all three drives. 6 one way, a half a dozen the other. is that too not theologically sound thinking?

say something like 775 or 755 across the board (all three drives in the /home/user) perhaps
to answer this
Quote:
For a neutral "3rd-party" drive that doesn't contain an OS, but that all OSs need to access, he could change the permissions to 777 so ownership doesn't matter, but that's not exactly a great security model...
finding out myself. going into test mode. installing LM Cinnamon on external, it will only give me two HDD but the theory is the same so the solution is the same.

MOD:
Ok I stand corrected (myself) I created two users in LM KDE to get two different UIDs one matching my other user in the other system UID 1000 I had no problems accessing each others accounts going though the file manager. The other one that has a different UID 1001 no go, had to change permissions to 777.

I must have had the same UID for both users in each OS. though then again, if he is the ONLY person using this system, one OS at a time, then the 777 might be not that big a deal thought syncing IUDs is deff the best idea/answer.

Last edited by BW-userx; 03-22-2016 at 01:58 PM.
 
Old 03-22-2016, 02:17 PM   #35
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:
If he wants to be able to access another OS stored on his drive without becoming root or breaking the other OS by screwing up the permissions and/or ownership, he needs to modify his UID on either or both systems so they match.
-::-I made it so that they (all uid's) matched and it broke the Apricity OS anyway.-::-

I joined the Arpricity OS Forum and I have found that I am not the only one that this has happened to.
A handful of folks have installed this distro and had the same result as mine ie) either couldn't access other os on other drives and changing permissions and or ownership broke/crashed the gui.

Linux Mint 17.3 Mate is now running stable on that drive.

I'd like to re-install Apricity OS in place of Linux Mint 17 Cinnamon when I have time but first I have to find out if the result with the uid and the gid is going to be the same. I suspect that it will be.

The username was the same of the Western Digital, the SSD and the Hitachi perhaps that was part of the conflict and reason for the crash after making the uid's the same- I don't know at this point.

If anything I'm testing a new distribution and seeing what it does and what I can and can't do with it.

If it breaks again I'll delete the old .Xaurthority file and create a new one as it's suggested in the Arch documentation and install the gdm again.
 
Old 03-22-2016, 02:22 PM   #36
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
The username was the same of the Western Digital, the SSD and the Hitachi perhaps that was part of the conflict and reason for the crash after making the uid's the same- I don't know at this point.
When I just installed LM KDE my first user UID was 1000 the same as my other OS. it worked, then created another user in LM KDE UID 1001, did not work.

the first user UID is mostly 1000 or 1001, but mostly 1000. if you could do a preemptive strike on your UID's so that they'd match what ever Apricity OS would use as its first UID then you'd NOT have to change Apricity OS UID it'd already match the others. then it'd just might work.
 
1 members found this post helpful.
Old 03-22-2016, 02:36 PM   #37
suicidaleggroll
LQ Guru
 
Registered: Nov 2010
Location: Colorado
Distribution: OpenSUSE, CentOS
Posts: 5,573

Rep: Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138
Most installers let you manually set the UID when you create the first user.
 
1 members found this post helpful.
Old 03-22-2016, 02:39 PM   #38
suicidaleggroll
LQ Guru
 
Registered: Nov 2010
Location: Colorado
Distribution: OpenSUSE, CentOS
Posts: 5,573

Rep: Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138
Quote:
Originally Posted by Ztcoracat View Post
-::-I made it so that they (all uid's) matched and it broke the Apricity OS anyway.-::-
Your previous post indicated that you changed the user's ID while that user was logged in and running things (permission errors on /proc). That will of course break things on any distro. As I said originally, you need to make sure the user is not running ANYTHING before you do this. Run "ps -ef" and look through the output, there should not be a single process belonging to the user for whom you intend to change the UID. This is why you have to do it in a TTY (or while logged in as a separate, unrelated user), you cannot be logged in as the user, anywhere on the system, while making this change.

Last edited by suicidaleggroll; 03-22-2016 at 02:41 PM.
 
Old 03-23-2016, 06:09 PM   #39
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
When I just installed LM KDE my first user UID was 1000 the same as my other OS. it worked, then created another user in LM KDE UID 1001, did not work.

the first user UID is mostly 1000 or 1001, but mostly 1000. if you could do a preemptive strike on your UID's so that they'd match what ever Apricity OS would use as its first UID then you'd NOT have to change Apricity OS UID it'd already match the others. then it'd just might work.
I think that the problem is that the Live User is the actual user.

Before the crash there was a folder in the root directory above root marked "Live User".
I think that file is creating conflict.
 
Old 03-23-2016, 06:17 PM   #40
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 suicidaleggroll View Post
Your previous post indicated that you changed the user's ID while that user was logged in and running things (permission errors on /proc). That will of course break things on any distro. As I said originally, you need to make sure the user is not running ANYTHING before you do this. Run "ps -ef" and look through the output, there should not be a single process belonging to the user for whom you intend to change the UID. This is why you have to do it in a TTY (or while logged in as a separate, unrelated user), you cannot be logged in as the user, anywhere on the system, while making this change.
Got it that's clear now.
I accidently changed the uid while logged in as the regular user.

Should I create a seperate user to make the uid match?

I'll reinstall Apricity when I have more time.

I'm wondering if removing that Live User file will stop the uid issue?

Last edited by Ztcoracat; 03-27-2016 at 03:54 PM.
 
Old 03-23-2016, 06:42 PM   #41
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
Looks like Elementary OS
http://www.apricityos.com/
https://elementary.io/
 
Old 03-23-2016, 08:31 PM   #42
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
Yes it does in many ways.

Apricity OS looks almost identical to Elementary with a newer version of the kernel and a different cmd-line utility.
 
Old 03-28-2016, 05:09 PM   #43
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 suicidaleggroll View Post
Most installers let you manually set the UID when you create the first user.
I hope the Anaconda installer will allow me to do that.
I'll look for a way to set the UID during the install this evening.
 
Old 03-30-2016, 08:18 PM   #44
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
A fresh installation went well. The installer was foreign to me and it didn't have the option to manually change the id after I created the first user.

The Live User's id is 1000.
Sifu (the owner of the system) id is 1001. It looks like that Live User file is creating havoc because Sifu should be 1000 not 1001. You agree?

Here's pic's to show you what I mean by the Live User.
http://i1052.photobucket.com/albums/...2014-14-58.png

http://i1052.photobucket.com/albums/.../id%20user.png

Any thoughts or idea's on this guys?
 
Old 03-30-2016, 08:34 PM   #45
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
help me refresh my brain. You need to get the same UID on three separate installs of Linux all on separate Hard Drives all attached to each other via the motherboard. So no matter which OS you are in you can access any of the other Linux Installs without incident of an error. Correct?

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?

Where your other two Systems already installed UID 1000? flashback to Post #1 "Arch is installed to the 500 GB WD drive, LM KDE is installed to the 128 SSD, & LM Cinnamon to the 120 Hitachi HDD."

the LM KDE is installed to the 128 SSD, & LM Cinnamon to the 120 Hitachi HDD UID are 1000 yes?

who is live User, and who is Sifu?

are these two separate actual user names within the same system?
 
  


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 03:57 AM.

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