Non-auto ownership of HDD's

[maycne.sonahoz]

The thing is : drives and partitions have no ownership or permissions in Linux. Files, and by extension folders, have.
So it would really enlighten us to know what you mean by ownership/permissions for a drive.

[Rocherd87]

https://forum.manjaro.org/t/tutorial-understanding-and-working-with-unix-filesystems-and-permissions/65793

[maycne.sonahoz]

[HowTo] post screenshots and links

Difficulty: ★☆☆☆☆ You’ve probably been sent here by a more experienced user because you cannot post links nor screenshots so please follow the simple instructions of this tutorial below to allow you to post both screenshots and links in any post and have a short explanation of why you can’t do this easily… If you’re reading this in response to a question, please click the green link above this text to bring you to the full unabridged text of the tutorial itself. If you …

[Nachlese]

@Rocherd87

Madness is doing the same thing getting the same results knowing there has to be a better way.

… there might not be a better way - not the easy one that you’d like …
The way to go would probably be to semi-automate the chown process that just has to be done if the freshly formatted drive is to be used by anyone but root after it is first introduced to the system/mounted.

[maycne.sonahoz]

I know that tutorial. That doesn’t tell me what you mean.

[Rocherd87]

~sighs~ okay so im going to have to be super duper patantic then…

Yes, its true all drives are now repusented as files when mounted, HOWEVER when unmounted they are references that something exists

heres the problem:

@Aragorn

• The Linux kernel no longer supports (user-created) hard-links for directories, although every directory will always contain two hard-links, i.e. . (which points at itself) and .. (which points at its parent directory). In the event of the root directory, the link to the parent also points at the root directory itself. Given that these two links ─ i.e. . and .. ─ have a name that starts with a period, these two entries will not show up in a normal directory listing. Also, because directories cannot be hard-linked anymore, the link counter for a directory instead refers to the number of subdirectories it contains.

@Aragorn

• Because hard-links are simply additional links to the same inode, hard-linking cannot span across different filesystems.
• Because the permissions, owner and group of any file or directory are stored in the inode itself, you cannot set different permissions, a different owner or a different group on the individual hard-links of a single file.
• The Linux kernel no longer supports (user-created) hard-links for directories, although every directory will always contain two hard-links, i.e. . (which points at itself) and .. (which points at its parent directory). In the event of the root directory, the link to the parent also points at the root directory itself. Given that these two links ─ i.e. . and .. ─ have a name that starts with a period, these two entries will not show up in a normal directory listing. Also, because directories cannot be hard-linked anymore, the link counter for a directory instead refers to the number of subdirectories it contains.

im looking for a work around to an absolute with an absolute, i already talk to the writer, of the tutorial at the end he gave me a shrug that all i could interparte as i dunno.
and its most likly the script… not that i like it.

is there a way to give two solutions out?

[Aragorn]

@Rocherd87

HOWEVER when unmounted they are references that something exists

Please clarify. (Nothing of what you quoted appears pertinent.)

[maycne.sonahoz]

Are those focuses to… hard links? Why?
You’re losing me even more here…

I suggest we start over. Instead of describing your issue with mounting ownership, tell us what you are trying to achieve.

[dmt]

@Rocherd87

when unmounted they are references that something exists

Block device files will always be owned by root.

Try showing us the exact commands you are using.

[Rocherd87]

Im going to try my best…

Ever have wifi card, bluetooth card, thumb drive, ect ect, really hardware that your computer at first didnt know what it was… Now this information can be looked up (recently had to do it with my wifi card on a different computer). i dont remember all the commands however, i did learn 3 things kernal version matters, terminal can request details (who are you so i can assign you) directly from hardware, and both mint and manjaro do keep log file that lists hardware which can be called upon and referenced. Turns out this is true of most hardware and most OS’s.

[dmt]

Are you a troll or just crazier than I am?

[Rocherd87]

unfortunately when it comes to computers i am mostly self taught, so descriptions via annology is sometimes the only means of communcation left for complex issues.

[dmt]

I’m self taught too.

You plug the drives in, boot up and then…

Show us the exact commands you’re using to mount these drives, and any output, and ls -l the directory with your mountpoints in…

Then we can try to figure out what you’re talking about.

[Rocherd87]

@Rocherd87

sudo man mount /dev/sdxN -path

x is for standard drive lettering, N for numbers

but we are now back tracking to something that has a solution even if i dont like it, however it is what it is:

@Tomek

Did you thought about writing script? This script should have at least those tasks:

1. list all partitions (for example with ls /dev/sd[a-z][0-9]
2. test if partition is mounted
3. if not then mount to your desired location (standardized names should be ok for example ~/mounts/sdxN - directory should be created if not exist)
4. chmod/chown on mounted partitions

Since i already have too format and partition everything i was hoping i could make things faster if the default policy that all new hard drives where automatically user controll (me) instead of root.

[dmt]

Ok, I just though we could maybe get something better worked out for you.

@Rocherd87

sudo man mount /dev/sdxN -path

No wonder you’re having trouble.

It’s not a proper command, first of all it’s a combination of two commands man mount and sudo mount /dev/sdxN and do you have a dir called -path in the current directory. You’re running man with root for no reason and adding a block device for no reason.

Don’t put mountpoints in /run or /tmp since they’re temporary filesystems. No idea if you do this, since you won’t show the path.

[Nachlese]

for the sake of clarity:
I guess no one really knows what you are doing/trying to achieve quicker than you currently do.

I’m quite sure I don’t.

You have a lot of different drives regularly?
And you reformat and re-partition them?
And you then also want to use them?
But not as root but as a regular user?

That is where the chown step comes in …

But they are not in use for long.
Because then you change them again?
And the whole process starts again?

Or is it just the reformatting/repartitioning - possibly erasing/overwriting the previous content?

All these steps except the using them as a regular user require root access anyway, so … ?

[papajoke]

as @Nachlese

• format 300 disk with gparted ! bad: can use script

• partition(s?) - only data ? if yes, you can force ID (1000) or GID (users) in same script and use also mask and acl

• you want copy datas from manjaro to this 300 disk ? copy with ???

• same disk content or not ?

• …

[Rocherd87]

1. yes lots
2. yes often
3. they have to be returned usable so yes i have to be able to use them in (obviously since there so much patantic nature going on, not all 300 at once, like i said 5 at a time)
4. when the drive is installed the machine is running, this new drive i do not want it too automatically make it root upon existing in connection to the machine as that would speed things up (well, what could be reasonably sped up), how i know root is in effect reguardless of the state of data on the drive or kind of data, or format. ALL require root to just deal with in any facit, until root is dealt with the whole way until the end where chown can finally be allowed to be used. I just dont want to keep fighting with root the entire time.
5. if i could get rid of chown or other repeate per drive permissions and ownership method that would also needs to go (well disabled)
   6-8. this is because i most of these drives are going back to non profit, friends, family, ect. like anything in life there is always stuff to be done.

using the script method would save me about the same time i wanted to avoid scripting because its too foreign to me (computer faster than human fingers lol, so i guess im just going to have to get over it and script it)

im not really asking for anything to be done about the (re)formating/(re)partitioning, ect that takes time to do that stuff and require sudo regardless this part takes time anyhow… no complaints here cant really shave much time out this spot due to varied requests its why im trying to avoid giving much detail about this section because its irrelvant beyond story/context.

[maycne.sonahoz]

@Rocherd87

• they have to be returned usable so yes i have to be able to use them in (obviously since there so much patantic nature going on, not all 300 at once, like i said 5 at a time)
• when the drive is installed the machine is running, this new drive i do not want it too automatically make it root upon existing in connection to the machine as that would speed things up (well, what could be reasonably sped up), how i know root is in effect reguardless of the state of data on the drive or kind of data, or format. ALL require root to just deal with in any facit, until root is dealt with the whole way until the end where chown can finally be allowed to be used. I just dont want to keep fighting with root the entire time.
• if i could get rid of chown or other repeate per drive permissions and ownership method that would also needs to go (well disabled)
• this is because i most of these drives are going back to non profit, friends, family, ect. like anything in life there is always stuff to be done.

Putting aside ownership/permissions, is your objective here just to mount them and write something on them to check they work?

[Nachlese]

My questions where to elicit information on what you are actually trying to do, what the objective is that you are trying to achieve.
What is the overall goal?

Lots of disks - reformat and somehow test them? Then send them on their way?