Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen Revision Vorhergehende Überarbeitung | |||
content:serverbasics [2024/04/20 11:33] – [Raided EFI-BOOT] Daniel | content:serverbasics [2024/04/20 13:02] (aktuell) – [UMask- Approach] Daniel | ||
---|---|---|---|
Zeile 42: | Zeile 42: | ||
==== Raided EFI-BOOT ==== | ==== Raided EFI-BOOT ==== | ||
- | Nowadays, UEFI is always the best choice to boot. UEFI- Boot is quite straight forward: You first take some device, make it gpt- partitioned, | + | Nowadays, UEFI is always the best choice to boot. UEFI- Boot is quite straight forward: You first take some device, make it gpt- partitioned, |
- | Unfortunatelly, | + | But: Unfortunatelly, |
Fortunatelly the designers of OSS software- raid were smarter: They found a way to work around that: They made a special Version of MD Metadata called V1.0 which will store its Metadata at the end of the partition - so it will not interfere with FAT32. For FAT32 it can work as usual and for MD-Tools it will be able to detect the devices as Raid1. | Fortunatelly the designers of OSS software- raid were smarter: They found a way to work around that: They made a special Version of MD Metadata called V1.0 which will store its Metadata at the end of the partition - so it will not interfere with FAT32. For FAT32 it can work as usual and for MD-Tools it will be able to detect the devices as Raid1. | ||
Zeile 170: | Zeile 170: | ||
==== Filesystem ==== | ==== Filesystem ==== | ||
- | Brtfs is the way to go everywhere. There are some disadvanteges while it is still in developement and sometime | + | Brtfs is the way to go everywhere |
+ | |||
+ | And there is one Reason: Docker - at the current time of writing this (20.04.2024) you should NOT USE BTRFS with Docker. More is explained later. | ||
==== Mountoptions ==== | ==== Mountoptions ==== | ||
Zeile 301: | Zeile 304: | ||
By default the umask is 0002 or 0022. Those values are substracted from 0777, which would mean full access for everyone. You can check out the docs in the net how they work. I won't explain here, cause there is a big problem with umask: The value can only be changed on process level or user or systemwide. This means you cannot set them per directory - which would be intentional to the user. | By default the umask is 0002 or 0022. Those values are substracted from 0777, which would mean full access for everyone. You can check out the docs in the net how they work. I won't explain here, cause there is a big problem with umask: The value can only be changed on process level or user or systemwide. This means you cannot set them per directory - which would be intentional to the user. | ||
- | So forget about umask. | + | So you should maybe think of setting a better umask than 022 - which would make all users of you group have read access to you files to lets say 077. Or - even better don't use the group " |
+ | |||
+ | On my system the umask can be defined in the file ''/ | ||
+ | |||
+ | But to go on directory- permissions: | ||
==== FACLs ==== | ==== FACLs ==== |