You need to set the options in the fstab to no fail when the drive is not present. nofail will present no errors when the drive is not present but if you are forcing a device fscheck on mount then you may still fail at boot. Using noauto will mean that the drive only mounts when you tell it do, ie mount -a will not mount this drive ever.
Bingo
Well, @level1 beat me to it. I should have read to the end first. lol
If you have Wine/Proton installed and you have sudo setup in a very permissive way, you open yourself up to some MS Windows attacks as well as well crafted exploits.
The NTFS driver is pretty darn stable now that MS is playing nicely with F/LOSS so the disk corruption is no longer a thing like it used to be.
Foreign drives are in this context to be interpreted as drives that are physically separate from the drive with the root partition. These days your Linux desktop drive should have these partitions;
Mount point
Size
Comment
swap
4 GB
These days ātwice your RAMā is rather excessive
/
30 GB
Root partition, 30 GB should be plenty.
/home
rest of disk
Where you store your irreplacable data, such as work, family photos and pr0n stash
Though these also help for a more advanced user:
Mount point
Size
Comment
/boot
1 GB
(optional) Makes it easy to have more than one Linux install on the same drive
/mnt/second
30 GB
(optional) Your lab distro, ever wanted to try out SUSe, Arch or Debian?
/opt
100+ GB
(optional) So, I heard you like Snaps and Flatpaksā¦
Anyway, it isnāt that you cannot or should not access your windows files; you should just do so in a way that does not compromise system stability. This means that any foreign drive should be mounted from userspace instead of boot.
Hey, I moved from Arch Linux to Fedora 37 on my gaming computer (last computer to go), butI have ran into a problem with my drive situation. Fedora uses a btrfs subvolume for the home directory, but I already have a drive with my /home data on it. So I edited my fstab with the appropriate modifications. However, for some reason I get a permissions error. There is no problem with the mountpoint, and my user and group is the owner of the directory with 775 permissions. What gives?
P.S. My home directory is using LVM+LUKS and an EXT4 filesystem btw.
Whenever there is an unexplainable permission issue in Fedora it likely is SElinux. Check the context with ls -alZ /home and, if necessary, adjust with chcon. The home folders should have context unconfined_u:object_r:user_home_dir_t:s0.
E.g. chcon -R -t user_home_dir_t /home/user_a
I am assuming that you mean user_home_dir_t to be a variable? As well as /home/user_a? I tried to do that command, but I got it wrong.
I will say that SELinux has been a royal pain in my ass since I moved over to Fedora and AlmaLinux (for my server), but I thought it only affected applications.
Oh I get it now. user_home_dir_t is the context I am setting it to. Right? I got it all fixed now. Thanks, but if you wanna help me understand SELinux more Iād be grateful.
Not sure if this is truly the best place to put it but what is easier to work with making Gnome Extensions or adding stuff to Plasma widgets? I want to create something which will change backgrounds and change what apps are immediately available based on a dropdown menu with that dropdown being able to be changed based on the time of day or a dropdown.
Tried to build my own image of OpenWRT based on this fork for my Nanopi R5S, did manage to boot it up and use some stuff. However, after trying to replace Dropbear with OpenSSH, I canāt connect to it. The server does start and Iām able to kinda start the connection, but then I get a broken pipe message on the client.
On the server thatās the error I get:
I tried to disable seccomp, build the image with Openssh preinstalled (instead of downloading from the repos), messing around with some build options for SSL. Also tried building different kernel versions (6.0 and 6.2) to no avail.
The only idea I have left is to try to cross-compile a statically linked openssh server, but thatās a annoying task and I worry that I may end up facing this error in other applications in the future.