/srv/irclogs.ubuntu.com/2019/07/12/#ubuntu-mate.txt

camelotbobGood morning  #ubuntu-mate12:43
Gossetgood morning12:44
Gossetand long life12:44
kernal_Ohayo!12:48
camelotbobHave you guys ever seen delayed movements with a wifi mouse on Ubuntu Mate?  Any mouse movements are about 1/4 seconds or more delayed.  If you spin the mouse in several circles, it takes a few second for it to repeat your action.12:50
Gossetnop12:52
camelotbobIt works fine on my windows laptop, so I was wondering if it was a driver problem.  Mouse -->  https://www.amazon.com/gp/product/B00BIFNTMC12:52
GossetI got my Ubuntu Mate a little slowlier since I installed Gnome apps12:52
sixwheeledbeastPossibly drivers are unavailable.12:58
GossetHi, how do I activate Trash on auto mounted ext4 partition?13:00
Gossetoptions are: nosuid,nodev,nofail,x-gvfs-show,x-gvfs-name=Data13:00
Gossetmaybe replacing nosuid by uid=1000 ?13:00
Gossetthe guys on ubuntu chan do not help me :(13:01
Gossetseriously?13:06
Gossetfor me it's a basic question13:06
GossetI it's strange I don't found the answer on Google13:07
camelotbobI found a few references to mouse lag when it's a wifi mouse.  So it's probably not ubuntu.13:07
sixwheeledbeastIf you check for Additional Drivers in Software and Updates it's not technically wifi just 2.4Ghz13:09
kernal_there's such a things as a wifi mouse??13:09
kernal_why?13:09
sixwheeledbeastGosset: I dont understand your question13:09
sixwheeledbeastNo idea some wireless mice use 2.4G to a USB RX for some reason13:10
Gossetmy English is poor I know13:11
kernal_adding wifi latency of course there's gonna be a delay :S13:11
Gossetthere is no trash can in my auto mounted /mnt/data partition13:11
kernal_what does trash have to do with mounting a drive?13:12
sixwheeledbeastGosset: "Trash" is only in one location on each system13:12
kernal_mount /dev/name_of_disk /where_you_want_to_mount/some_folder13:13
GossetI see13:13
Gossetso when I delete any file from my "data" partition, it's permanently  deleted13:14
Gosset:(13:14
alkisgGosset: if you have enough rights, a .Trash-(uid) folder is created for each volume13:15
kernal_rm /*13:15
alkisgIt's hidden so you need to `ls -la` or Ctrl+H to see it13:15
alkisgBut you need write access there13:15
Gossetof course I have write access13:15
Gossetit's a personal computer13:15
sixwheeledbeastGosset: I imagine you have a .Trash file within your partition13:15
Gossetnop13:16
alkisgFor example, "administrator" doesn't have write access to "/"13:16
alkisgEven on personal computers13:16
GossetI have a lost&found13:16
sixwheeledbeastDue to the drive being treated as a removable one13:16
tomreynthe same discussion is also happening in #ubuntu currently13:16
sixwheeledbeastCtrl+H may show hidden files13:16
Gossetyes tomreyn13:16
Gossetsorry13:17
GossetI focus on this chan from now on13:17
Gossetthe only hidden file on my separate partition is lost&found13:17
alkisgGosset: I didn't see the start of the discussion; what file system is this, ext4? In ext4 users don't have write access to /.13:17
alkisgSo they can't get .Trash folders there13:17
Gossetyes alkisg13:18
Gossetoh my13:18
alkisgYou'd need to create it manually13:18
Gossetevery time ?13:18
alkisgJust once13:18
Gossetok13:18
Gossetwith which name13:18
Gosset.Trash?13:18
alkisg.Trash-1000, or whatever your uid is13:18
alkisgid -u shows it13:19
alkisgRemember to chown it to your uid13:19
Gossetyes, it's 100013:19
alkisgso, chown 1000:1000 /path/to/folder/.Trash-100013:19
alkisgThen you can test with gvfs-trash; it should move a file from that volume inside trash13:20
alkisg(if it belongs to you, again; otherwise you can't delete it without using sudo)13:20
GossetNow I don't know what I've typed, I don't have permissions to write anything on the partition :(13:21
alkisgIt's normal not to have permissions to write to ext413:21
alkisgsudo mkdir /path/to/folder/username; sudo chown 1000:1000 /path/to/folder/username; ==> will give you a folder for this user13:21
sixwheeledbeastI personally have my data drives as /data0 /data1 etc not /mnt/data. Then within there a .Trash-1000 was automagically made the first time I deleted something.13:21
alkisgAutomounted folders go to /media/volume13:21
alkisgWhile /mnt/volume is wrong, FHS says /mnt shouldn't have subdirs13:21
GossetI'll restart13:22
Gossetok, it works ... partly13:25
GossetI don't have write access on /mnt/Data, but I have w access to folders inside /mnt/Data13:26
Gossetstrange!13:26
alkisgGosset: what is /mnt/Data?13:26
alkisgWhat mounts it there?13:26
alkisgDo you have an entry in fstab for that?13:26
Gossetit's my auto mounted partition13:27
Gossetof course13:27
Gossetit automounts every time13:27
alkisg /mnt/Data is the wrong path to use, that's why I'm asking13:27
alkisgAutomounted partitions go to /media/13:27
sixwheeledbeastIf the drive is internal I personally would give it a dir in root so /data0 as ext4. If removable media then I would normally format as FAT anyways and let the system mount it to /media or whereever. I feel /mnt is fairly redundant in a modern ubuntu distro.13:27
Gossetit was automatically mounted there13:28
alkisgIs this Ubuntu?13:28
GossetI used to have it on /media too13:28
alkisgUbuntu doesn't use /mnt to automount things13:28
Gossetyes13:28
alkisgYou modified it somehow13:28
alkisgDid you put it in /etc/fstab? Paste the line here13:28
Gossetnope13:28
alkisggrep /mnt /proc/mounts13:29
alkisgWhat's the output of this/13:29
alkisgAnd, grep /mnt /etc/fstab13:29
alkisgThe output of this too13:29
Gossetchown 1000:1000 /path/to/folder/.Trash-100013:29
Gossetsorry13:29
Gosset# /etc/fstab: static file system information.13:29
Gosset#13:29
Gosset# Use 'blkid' to print the universally unique identifier for a13:29
Gosset# device; this may be used with UUID= as a more robust way to name devices13:29
Gosset# that works even if disks are added and removed. See fstab(5).13:29
alkisgDon't flood13:29
alkisgNow you were muted13:29
alkisgWait a bit, then type the output that I asked for; it's one line, not all the fstab13:29
alkisgI think the bot unmutes you after 1 minute...13:30
Gossethttps://paste.ubuntu.com/p/Hk4sHQ3B98/13:30
sixwheeledbeastI'd backup fstab and re setup the drive for /data013:31
alkisgYup, you manually put it there13:31
GossetI swear I didn't put it manually there13:31
alkisgsixwheeledbeast: sorry but that's not really good advice13:31
alkisgPlease google for "FHS", file system hierarchy standard13:31
alkisgThere are valid and invalid places to mount things...13:31
sixwheeledbeastI know about FHS13:31
alkisgGosset: in any case, what you see is normal. It's an ext4 file system, you don't have access to /, and you have to subfolders13:32
alkisgYou could chown /, but using subfolders is fine too13:32
Gossetthen I'll chown /13:32
alkisgIt's like "you're not able to write to /home or to /, but you can write to /home/username"13:32
alkisgGosset: I mean /mnt/Dades of course, not / directly, right?13:32
Gossetyes13:33
GossetI've configured all my system with /mnt/Dades13:33
alkisgOK; note that you'll no longer be able to boot from that disk, if you ever install an os in this13:33
Gossetthe idea is to store my data there only13:33
alkisgAs many apps expect the root dir to be root-owned, otherwise consider it a security issue13:33
alkisgOK13:33
Gossetthanks13:33
alkisgGo on, just keep that in mind13:33
Gossetsolved13:34
Gossetthanks a lot13:34
alkisgnp13:35
GossetI must say that in my old PC I had the same partition as NTFS in /media13:35
Gossetto share files with Windows13:35
alkisgNTFS gets automounted with the ability for users to write to  /13:36
alkisgext4 is different; it's automounted without that ability, and also without the ability to execute things from there13:36
Gossetbut I discovered that ext4 files can be shared with a Windows partition too13:36
Gossetusing Virtual Machine13:37
Gossetnot a Windows partition sorry13:37
Gosseta Windows .vdi13:37
Gosset*VirtualBox13:37
alkisgWith VirtualBox you're using vboxsf, not ext4, not ntfs13:38
GossetIt was stupid having the NTFS partition13:38
alkisgThe files are accessed over vboxsf, something like "over the network"13:38
Gossetyes13:38
Gossetanyway, the NTFS filesystem would worth in a dual boot machine13:39
Gossetnot my case13:39
alkisgRight13:40
alkisgI adviced a user for that a few months ago, maybe it was you D:13:41
sixwheeledbeast?13:41
alkisg(that ntfs isn't needed when vboxfs is used)13:42
sixwheeledbeastoh13:42
Gossetit might be me xD13:42
sixwheeledbeastI thought you where still on about FHS13:43
sixwheeledbeastFHS has no comment on mounting other drives to /data or even Mac style /vol I have seen.13:45
alkisg3.11. /media : Mount point for removable media 3.12. /mnt : Mount point for a temporarily mounted filesystem14:02
alkisgThese are the standard mount points, unless of course a partition is reserved for another part of fhs, like /home, /var, whatever14:02
alkisgIf you mount it to /data0, for example, you'd need to specially configure backup software to exlcude this14:03
alkisgRationale . Placing the mount points for all removable media directly in the root directory would potentially result in a large number of extra directories in /.14:06
alkisgAlthough the use of subdirectories in /mnt as a mount point has recently been common, it conflicts with a much older tradition of using /mnt directly as a temporary mount point.14:06
sixwheeledbeastExactly neither mount point is listed by FHS for permanently mounted drives. I can't see why you would need to backup root backup would normally be for user data anyway. I am not saying for removable media I am on about a internal extra drive. FHS as no comment on where to mount them is my point, plenty of advise on where to mount specifics but not a "data" drive.14:16
sixwheeledbeastIf the drive is for a specific job listed in the FHS then it should be mounted there, that being anywhere /srv /home/user0 /opt /var/mail whatever. However, in this case /data0 is a pretty suitable place for an additional data drive and there is nothing in the FHS that explicitly forbids this.14:23
alkisgsixwheeledbeast: see the sentence above, " Placing the mount points for all removable media directly in the root directory would potentially result in a large number of extra directories in /."14:25
alkisgIt's an advice against this14:25
sixwheeledbeast"removable"14:25
alkisg(from fhs copy/paste)14:25
alkisgthe rationale is the same14:26
sixwheeledbeastinternal drives are not considered "removable" they are as removable as the system drive14:27
alkisgWe can play with words, but what's the difference between "internal drive for media" vs "external drive for media" wrt to that specific sentence?14:28
alkisgDon't they both clutter /?14:28
alkisgBackup root drive => eh, do I really need to justify why people backup their /?!14:29
alkisgSoftware that backs up / knows to exclude /media and /mnt, but not /data014:30
alkisgIn any case, I'm not someone for looong chats, I just wanted to point to what I've read/seen with experience; anyone can then follow whatever he likes best! Coffee time now . :)14:31
sixwheeledbeastYou can have all your / subdirectories on different physical drives if you wanted. They are all part of the system and not "removable"14:31
alkisgIt would be a cluttered / then14:31
alkisgThat's the point of FHS, to make things make more sense14:31
alkisgYou can have /data0 to /data100000 if you prefer it14:31
sixwheeledbeastyou would just do /data and then sub dirs14:32
alkisgIt could be /data, /mata, /pata, /fata, not specifically data0 to numberxxx14:32
alkisgDifferent names that don't belong in subfolders :D14:32
sixwheeledbeastyes it could if you wanted.14:33
alkisgIf you prefer /data with subfolders instead of /media with subfolders, sure, you can use that too14:33
alkisgI'm just saying what FHS suggests14:33
sixwheeledbeastAs I say FHS doesn't have "specific" advise for this scenario14:34
alkisgNote that they also don't mention usb sticks etc; they can't mention everything; people will need to apply their good sense in cases not explicitly mentioned14:34
alkisgThat doesn't mean that distros should use /usb and /sd-card for these14:34
sixwheeledbeastNo because they are covered under media14:34
alkisgHow about internal usb sticks? Some boards have these too14:35
sixwheeledbeastthey are "removable"14:35
alkisgNope, not more so than sata disks14:35
alkisgThey're internal usb sticks14:35
* alkisg has seen people argue about specific words in manuals and books for ages; he's not really into this :)14:35
alkisgIf you think this word removes the good sense behind that advice, you can surely ignore it14:36
sixwheeledbeastI am not arguing I am just defending the fact that there is no issue with mounting a /data drive like this as far as the FHS guidelines14:37
alkisgI don't see it that way; but I don't think we can convince each other either14:37
sixwheeledbeastAs I say if it has a specific purpose it should be mounted there above all else first.14:39
sixwheeledbeastThe point of the FHS is so there is a standard between distributions on file locations, this is why a /data would be out of scope.14:41
alkisgThis argument is the same as why /media/alkisg is out of scope14:42
alkisgOr why /mnt/alkisg isn't a good place14:42
alkisgAnyway, really, we can't convince each other14:42
alkisgLet's drop it at this point14:42
sixwheeledbeast1.1 Purpose The FHS document has a limited scope: Local placement of local files is a local issue, so FHS does not attempt to usurp system administrators.14:43
alkisgAdvice only makes sense if it makes sense; what I perceive from FHS is clearly different from what you make sense of it; so each one can apply it as he sees fit14:45
alkisgI don't think anyone of us is giving advice anymore; so...14:45
* alkisg waves14:45

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!