/mnt/something has root as Owner. So When I try to move something to Trash, it’s not allowing me to do
You have to change permissions or owner of that folder (not /mnt itself but the subfolder “something”).
If I’m not wrong changing permissions is enough to use gui “move to trash”, you can use chmod thru cli (man chmod
) o your gui file manager with root privileges.
If you want only your user be able to read/write to that disk, then change the owner using chown thru cli (man chown
) or again your gui file manager.
The Linux FHS does not address this, so it’s up to you where to mount it. There is no correct choice, but if you want to follow standards just mount it inside /mnt which is the nearest use-case (/media could be automatically used by your DE, so avoid it). Otherwise you can just create a custom folder in root like someone else suggested.
Take a look at FHS spec.
Edit:
On arch forum someone suggests /mnt/data
/srv
contains site-specific data which is served by this system.
https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#srvDataForServicesProvidedBySystem
Sony patents a lot of fancy undoable things.
Why is it blue?
From video description:
Reason 1: Gaming
Reason 2: Creative Apps
Reason 3: Foobar2000 (my music player)
Reason 4 (bonus) Fussing, fussing, fussing!
How does this actually works? Can you point me to technical documentation about this?
I’ve only found info about SSAI, not about SSAP. Is it the same?
Seems too much, really. Even if they do such a terrible thing, would they not expose a “report ad” or “see the product” buttons? Video buffer is still locally downloaded.
I don’t see any technical specification in the article, but if they inject the ad at the start of the video, making it part of the video itself, would make possible to just skip it using video controls. To avoid user skippin ad thru video controls there should be client-side script blocking it, so an ad-blocker can use this to tell apart an ad from the video itself.
Can anyone correct me on this?
Also, would this affect piped and invidious too?
Different protocols? Like android’s mtp? Never had an apple device, what do they use?
I still don’t get why GNOME moved to RDP instead of sticking with VNC.
Embracing Microsoft technologies to better fit offices?
Alaska kings are open-minded.
Alaska kings sleep with 3 women.
Politics is endangering the whole Lemmy, with instances defederated because of their political views and a lot of censorship.
Calm down folks! This is a web forum, people should be free to share what they think (without harassing anyone) without being censored, creating a biased platform.
I’m not into non-free-speech instances (like lemmy.world), but I do understand and respect their decision because it MAY decrease harassment between users. But please don’t defederate with everyone otherwise it would still be a biased platform. Let people choose what to see and just ban spam and real harassment (I’ve used too much this word).
I’m not into politics myself and it drives me crazy that we can’t rely on fine communities because they are on instances defederated by big instances because of their political views.
Seems to be based mostly on Fedora by reading the Readme.
I would like to know if it does use systemd and/or other redhat technologies.
In the readme they mention Qt, does anyone know what DE do they use?
Is there a list of impacted roms?
On Linux files and folders have permissions info for owner, group and everyone else. So you can set individual permissions for these.
By setting the owner to root, if you want to make your user able to read/write that folder, you must either give permissions to everyone to read/write OR assign a group to the folder, give the group permissions to read/write and add your user to that group.
If you instead set your user as the owner of the folder, you can make only your user able to read/write without other fuss.
If you are a newbie, stick to gui file manager. Can you please tell me what file manager are you using? Most of the time you can change permissions thru right click > propriety > permissions.