[12:43] Good morning #ubuntu-mate [12:44] good morning [12:44] and long life [12:48] Ohayo! [12:50] Have 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:52] nop [12:52] It works fine on my windows laptop, so I was wondering if it was a driver problem. Mouse --> https://www.amazon.com/gp/product/B00BIFNTMC [12:52] I got my Ubuntu Mate a little slowlier since I installed Gnome apps [12:58] Possibly drivers are unavailable. [13:00] Hi, how do I activate Trash on auto mounted ext4 partition? [13:00] options are: nosuid,nodev,nofail,x-gvfs-show,x-gvfs-name=Data [13:00] maybe replacing nosuid by uid=1000 ? [13:01] the guys on ubuntu chan do not help me :( [13:06] seriously? [13:06] for me it's a basic question [13:07] I it's strange I don't found the answer on Google [13:07] I found a few references to mouse lag when it's a wifi mouse. So it's probably not ubuntu. [13:09] If you check for Additional Drivers in Software and Updates it's not technically wifi just 2.4Ghz [13:09] there's such a things as a wifi mouse?? [13:09] why? [13:09] Gosset: I dont understand your question [13:10] No idea some wireless mice use 2.4G to a USB RX for some reason [13:11] my English is poor I know [13:11] adding wifi latency of course there's gonna be a delay :S [13:11] there is no trash can in my auto mounted /mnt/data partition [13:12] what does trash have to do with mounting a drive? [13:12] Gosset: "Trash" is only in one location on each system [13:13] mount /dev/name_of_disk /where_you_want_to_mount/some_folder [13:13] I see [13:14] so when I delete any file from my "data" partition, it's permanently deleted [13:14] :( [13:15] Gosset: if you have enough rights, a .Trash-(uid) folder is created for each volume [13:15] rm /* [13:15] It's hidden so you need to `ls -la` or Ctrl+H to see it [13:15] But you need write access there [13:15] of course I have write access [13:15] it's a personal computer [13:15] Gosset: I imagine you have a .Trash file within your partition [13:16] nop [13:16] For example, "administrator" doesn't have write access to "/" [13:16] Even on personal computers [13:16] I have a lost&found [13:16] Due to the drive being treated as a removable one [13:16] the same discussion is also happening in #ubuntu currently [13:16] Ctrl+H may show hidden files [13:16] yes tomreyn [13:17] sorry [13:17] I focus on this chan from now on [13:17] the only hidden file on my separate partition is lost&found [13:17] Gosset: 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] So they can't get .Trash folders there [13:18] yes alkisg [13:18] oh my [13:18] You'd need to create it manually [13:18] every time ? [13:18] Just once [13:18] ok [13:18] with which name [13:18] .Trash? [13:18] .Trash-1000, or whatever your uid is [13:19] id -u shows it [13:19] Remember to chown it to your uid [13:19] yes, it's 1000 [13:19] so, chown 1000:1000 /path/to/folder/.Trash-1000 [13:20] Then you can test with gvfs-trash; it should move a file from that volume inside trash [13:20] (if it belongs to you, again; otherwise you can't delete it without using sudo) [13:21] Now I don't know what I've typed, I don't have permissions to write anything on the partition :( [13:21] It's normal not to have permissions to write to ext4 [13:21] sudo mkdir /path/to/folder/username; sudo chown 1000:1000 /path/to/folder/username; ==> will give you a folder for this user [13:21] I 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] Automounted folders go to /media/volume [13:21] While /mnt/volume is wrong, FHS says /mnt shouldn't have subdirs [13:22] I'll restart [13:25] ok, it works ... partly [13:26] I don't have write access on /mnt/Data, but I have w access to folders inside /mnt/Data [13:26] strange! [13:26] Gosset: what is /mnt/Data? [13:26] What mounts it there? [13:26] Do you have an entry in fstab for that? [13:27] it's my auto mounted partition [13:27] of course [13:27] it automounts every time [13:27] /mnt/Data is the wrong path to use, that's why I'm asking [13:27] Automounted partitions go to /media/ [13:27] If 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:28] it was automatically mounted there [13:28] Is this Ubuntu? [13:28] I used to have it on /media too [13:28] Ubuntu doesn't use /mnt to automount things [13:28] yes [13:28] You modified it somehow [13:28] Did you put it in /etc/fstab? Paste the line here [13:28] nope [13:29] grep /mnt /proc/mounts [13:29] What's the output of this/ [13:29] And, grep /mnt /etc/fstab [13:29] The output of this too [13:29] chown 1000:1000 /path/to/folder/.Trash-1000 [13:29] sorry [13:29] # /etc/fstab: static file system information. [13:29] # [13:29] # Use 'blkid' to print the universally unique identifier for a [13:29] # device; this may be used with UUID= as a more robust way to name devices [13:29] # that works even if disks are added and removed. See fstab(5). [13:29] Don't flood [13:29] Now you were muted [13:29] Wait a bit, then type the output that I asked for; it's one line, not all the fstab [13:30] I think the bot unmutes you after 1 minute... [13:30] https://paste.ubuntu.com/p/Hk4sHQ3B98/ [13:31] I'd backup fstab and re setup the drive for /data0 [13:31] Yup, you manually put it there [13:31] I swear I didn't put it manually there [13:31] sixwheeledbeast: sorry but that's not really good advice [13:31] Please google for "FHS", file system hierarchy standard [13:31] There are valid and invalid places to mount things... [13:31] I know about FHS [13:32] Gosset: in any case, what you see is normal. It's an ext4 file system, you don't have access to /, and you have to subfolders [13:32] You could chown /, but using subfolders is fine too [13:32] then I'll chown / [13:32] It's like "you're not able to write to /home or to /, but you can write to /home/username" [13:32] Gosset: I mean /mnt/Dades of course, not / directly, right? [13:33] yes [13:33] I've configured all my system with /mnt/Dades [13:33] OK; note that you'll no longer be able to boot from that disk, if you ever install an os in this [13:33] the idea is to store my data there only [13:33] As many apps expect the root dir to be root-owned, otherwise consider it a security issue [13:33] OK [13:33] thanks [13:33] Go on, just keep that in mind [13:34] solved [13:34] thanks a lot [13:35] np [13:35] I must say that in my old PC I had the same partition as NTFS in /media [13:35] to share files with Windows [13:36] NTFS gets automounted with the ability for users to write to / [13:36] ext4 is different; it's automounted without that ability, and also without the ability to execute things from there [13:36] but I discovered that ext4 files can be shared with a Windows partition too [13:37] using Virtual Machine [13:37] not a Windows partition sorry [13:37] a Windows .vdi [13:37] *VirtualBox [13:38] With VirtualBox you're using vboxsf, not ext4, not ntfs [13:38] It was stupid having the NTFS partition [13:38] The files are accessed over vboxsf, something like "over the network" [13:38] yes [13:39] anyway, the NTFS filesystem would worth in a dual boot machine [13:39] not my case [13:40] Right [13:41] I adviced a user for that a few months ago, maybe it was you D: [13:41] ? [13:42] (that ntfs isn't needed when vboxfs is used) [13:42] oh [13:42] it might be me xD [13:43] I thought you where still on about FHS [13:45] FHS has no comment on mounting other drives to /data or even Mac style /vol I have seen. [14:02] 3.11. /media : Mount point for removable media 3.12. /mnt : Mount point for a temporarily mounted filesystem [14:02] These are the standard mount points, unless of course a partition is reserved for another part of fhs, like /home, /var, whatever [14:03] If you mount it to /data0, for example, you'd need to specially configure backup software to exlcude this [14:06] Rationale . 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] Although 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:16] Exactly 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:23] If 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:25] sixwheeledbeast: 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] It's an advice against this [14:25] "removable" [14:25] (from fhs copy/paste) [14:26] the rationale is the same [14:27] internal drives are not considered "removable" they are as removable as the system drive [14:28] We 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] Don't they both clutter /? [14:29] Backup root drive => eh, do I really need to justify why people backup their /?! [14:30] Software that backs up / knows to exclude /media and /mnt, but not /data0 [14:31] In 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] You can have all your / subdirectories on different physical drives if you wanted. They are all part of the system and not "removable" [14:31] It would be a cluttered / then [14:31] That's the point of FHS, to make things make more sense [14:31] You can have /data0 to /data100000 if you prefer it [14:32] you would just do /data and then sub dirs [14:32] It could be /data, /mata, /pata, /fata, not specifically data0 to numberxxx [14:32] Different names that don't belong in subfolders :D [14:33] yes it could if you wanted. [14:33] If you prefer /data with subfolders instead of /media with subfolders, sure, you can use that too [14:33] I'm just saying what FHS suggests [14:34] As I say FHS doesn't have "specific" advise for this scenario [14:34] Note 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 mentioned [14:34] That doesn't mean that distros should use /usb and /sd-card for these [14:34] No because they are covered under media [14:35] How about internal usb sticks? Some boards have these too [14:35] they are "removable" [14:35] Nope, not more so than sata disks [14:35] They're internal usb sticks [14:35] * alkisg has seen people argue about specific words in manuals and books for ages; he's not really into this :) [14:36] If you think this word removes the good sense behind that advice, you can surely ignore it [14:37] I 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 guidelines [14:37] I don't see it that way; but I don't think we can convince each other either [14:39] As I say if it has a specific purpose it should be mounted there above all else first. [14:41] The 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:42] This argument is the same as why /media/alkisg is out of scope [14:42] Or why /mnt/alkisg isn't a good place [14:42] Anyway, really, we can't convince each other [14:42] Let's drop it at this point [14:43] 1.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:45] Advice 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 fit [14:45] I don't think anyone of us is giving advice anymore; so... [14:45] * alkisg waves