Quote:
|
Hello all, thank you for your replies. I was busy at work and honestly forgot about the thread. After some more mucking about I was able to finally get it to at least create a mount point with a UID of my user (GID for whatever reason is being assigned '500' which doesn't exist on this system). umount/eject from the terminal still say Operation not permitted. Thunar fails to eject however Dolphin can eject it. ¯\_(ツ)_/¯
I may have no choice but to disable that udev rule. @Richard Cranium It is now showing: Code:
$ ls -lh The 1023:1023 came from the mount point itself. The contents have the usual baorr:users ownership. As far as changes scaring people...nah. The reason for wanting it mount inside /media directly and not inside another directory is purely laziness. This is a single user system so for all intents and purposes having mount points 2 levels shallower just makes sense. If garbage collection for unused mount points ever become an issue then a crontab can be used to prune. @abga Thanks for those links, I can see why it was included in FHS-2.3. Slackware 14.1 (at least that I remember) didn't make use of /run/media/{user}/{mountpoint} and I didn't see anything about it in the 14.2 changelog or 'CHANGES AND HINTS.TXT' file. I don't think I need to recompile it as I believe that flag was already set when the udisks2 maintainer compiled it. @philanc,rworkman: Nope, Hasn't touched Android at all. Fresh partition table and ext4 filesystem. @GazL: Right on the nose. More out of laziness (erm, 'efficiency') than refusal to change...unless your are talking about systemd...then I'm stubborn on that one. I like my BSD-style init...it's simple and elegant for what I need. |
Quote:
https://mirror.de.leaseweb.net/slack...ks2.SlackBuild |
Quote:
|
All times are GMT -5. The time now is 03:30 AM. |