Ubuntu 22.04 - Nemo keeps owner and permissions unlike Ubuntu 20.04 - Undesirable behavior - file-permissions

Nemo file manager in Ubuntu 22.04 preserves owner and permissions during a copy-paste operation (GUI) from a user folder to a system folder unlike Ubuntu 20.04.
The behavior in Ubuntu 20.04 was much more comfortable than that of Ubuntu 22.04, in which from the terminal I am forced to restore the root owner and the default permissions for each file copied to a system folder.
Is there a way to tell Nemo to forget the original owner and permissions during a copy-paste operation, like it was for good old Ubuntu 20.04?

Related

Recover Windows Subsystem Root User Password for Linux

I use linux bash on my windows machine with developer mode windows subsystem setup for linux. I followed this guide to install and configure sudo: https://linuxhint.com/run-sudo-command-windows/ but I forgot my password and I don't know how to reset it. Since I don't use a GUI distribution of ubuntu I can't use the LIVE CD nor can I use the GRUP bootloader. What options do I have?

WSL file system permission mixed up with windows files

I'm using WSL2 (Windows Subsystem for linux), and I've been using it for a really long time, and I didn't have troubles with it.
Unfortunately, today, from my linux distribution (Ubuntu 20.04), I no longer have permissions to view some Windows files, to which I had previously access without trouble. I don't know what happened, I don't remember intalling any update manually.
However, interestingly, I can access them if I do sudo su and become root. Then, I can access everything, or I can use sudo cat. But I don't want anything of that, I want to be the default WSL user to do what I could before.
What I tried:
Adding my default user to admin group, root group and sudo group (no luck)
Addming username to sudoers
root ALL=(ALL:ALL) ALL
danon ALL=(ALL:ALL) ALL
Editing permissions in my Windows host machine to allow everyone to access it
Editing permissions in my Windwos host to change the owner of the file (and directories below it)
Use other WSL distros, Ubuntu 20.04 and Ubuntu 18.04
Add metadata option to /etc/wsl.conf
Restarting the distro
Restarting the wsl
Restarting the host system
I don't know what else to do. I don't want to do sudo su everytime I open my wsl, or call each method with sudo.
I would like either to access my files from WSL like I used to before, or maybe specifically make those files available to my default linux user.
Result of mount:
C:\ on /mnt/c type 9p (rw,noatime,dirsync,aname=drvfs;path=C:\;uid=1000;gid=1000;metadata;umask=22;fmask=11;symlinkroot=/mnt/,mmap,access=client,msize=65536,trans=fd,rfd=8,wfd=8)
D:\ on /mnt/d type 9p (rw,noatime,dirsync,aname=drvfs;path=D:\;uid=1000;gid=1000;metadata;umask=22;fmask=11;symlinkroot=/mnt/,mmap,access=client,msize=65536,trans=fd,rfd=8,wfd=8)

Oracle on lxc in ubuntu

I'm currently trying to install an oracle server (11g) in a linux container on ubuntu (following this tutorial (http://www2.hawaii.edu/~lipyeow/ics321/2014fall/installoracle11g.html).
When I try to change the file handler with sysctl, the modifications doesn't save into my container. Moreover, when I make the modification in the main ubuntu kernel, it propagates to the containers, so my question is as follow:
How can I modify the file handlers only in my oracle container ?
Thanks.
Try out the Orabuntu-LXC project code. It supports Ubuntu 16.04, 17.04, 17.10 and is purpose-built for running Any Oracle on Any Linux, including Ubuntu Linux. Note that as you probably already know, Oracle Corp does not formally support or certify Oracle on Ubuntu Linux.
As far as you question about the file handlers, some sysctl values can only be set at the LXC host level, and some can be set in the container.
https://sites.google.com/site/nandydandyoracle/oracle-rac-in-lxc-linux-containers/oracle-lxc-vlc#TOC-Install-the-etc-sysctl.conf-File-Required-for-Oracle
https://github.com/gstanden/orabuntu-lxc
https://sites.google.com/site/nandydandyoracle/
Please note that the step-by-step guides are quite old and that the basic LXC infrastructure together with OpenvSwitch, an LXC-containerized DNS/DHCP, and an optional SCST Linux SAN can all be installed on Ubuntu 16.04, 17.04 and 17.10 with one command:
./anylinux-services.sh
after completion of which all you would need do is download your Oracle database installtion media and install.

What is the proper way to let non-sudo users mount their windows drives to their home directories of an ubuntu machine?

We have an ubuntu machine installed with specific versions of development tools and packages that we don't want them to be upgraded accidentally.
We want to let developers mounting their windows drives to their own home directories on the ubuntu, so that they can build their own code using the build environment.
Is it possible to not making these users sudo-ers but still be able to mount their drives?

VirtualBox: mounting shared folder fails during start-up, but succeed from shell

Problem description:
When I boot my VirtualBox Guest OS, the mounting of the shared file-system - which is referenced in /etc/fstab - fails.
However, after login - mount -a succeeds.
Details:
The boot process gets stuck here ...
... and pressing s continues the boot process, which finishes.
In the shell, I verify that my shared directory is not mounted:
But now, from the shell, the mount of the shared file-system succeeds:
What should I do to make my mount succeed during start-up?
Environment:
VirtualBox: 4.3.12.r93733
Host OS: Windows 7
Guest OS: Linux ubuntu 3.13.0-32-generic #57~precise1-Ubuntu x86_64 GNU/Linux
/etc/fstab
Relevant lines in /var/log/boot.log
You don't have to mount it, VitrualBox will make it for you. For me,these steps worked on my System (VirtualBox 5.0.10 on Windows 7 and Kubuntu 14.04 guest system):
In VirtualBox, configure your shared folder for your machine under 'Shared Folder'. Pick up the directory on your host system (e.g. D:\shared) and set a name for your guest system (e.g. shared).
Boot the guest system. Now you should have a mounted folder under \media\sf_shared.
Thats all. VirtualBox manages this for you.
You need to install VirtualBox Guest Additions properly and use VirtualBox Manager to specify share folders. The issue happens because the mount point is in place with root permissions. The default mount location is in /media/sf_.
You can change mount point with VBoxControl command. To change the mount point from /media/sf_... to /home/user/sf_... use the command:
sudo VBoxControl guestproperty set /VirtualBox/GuestAdd/SharedFolders/MountDir /home/user/
To check if that's working:
sudo VBoxControl guestproperty get /VirtualBox/GuestAdd/SharedFolders/MountDir

Resources