vault backup: 2026-01-05 13:03:55

03_Resources/Development/Linux/filesystem-limitations.md

@@ -0,0 +1,15 @@
+Fundamental rules for for Universal Naming Convention (UNC),which enable applications to create and process valid names for files and directories, regardless of the file system:
+
+Following reserved characters:
+```
+< (less than)
+> (greater than)
+: (colon)
+" (double quote)
+/ (forward slash)
+\ (backslash)
+| (vertical bar or pipe)
+? (question mark)
+* (asterisk)
+```
+Use any character in the current code page for a name, including Unicode characters and characters in the extended character set (128–255),

03_Resources/Development/Linux/ipa-server-installation.md

@@ -0,0 +1,9 @@
+```bash
+
+sudo ipa-server-install --realm=INT.IT2000.COM.CN --domain=int.it2000.com.cn --ds-password=admingzzn --admin-password=admingzzn --hostname=ipa.int.it2000.com.cn  --ip-address=10.16.67.98 --setup-dns
+
+sudo firewall-cmd --add-service={http,https,dns,ntp,freeipa-ldap,freeipa-ldaps} --permanent
+
+sudo firewall-cmd --reload
+
+```

03_Resources/Development/Linux/sudo-command-blocking.md

@@ -0,0 +1,23 @@
+If your user is called `user` and your host is called you could add these lines to `/etc/sudoers`:
+
+```
+user = (root) NOPASSWD: /sbin/shutdown
+user = (root) NOPASSWD: /sbin/reboot
+```
+
+This will allow the user `user` to run the desired commands without entering a password. All other sudoed commands will still require a password.
+
+The commands specified in the `sudoers` file _must_ be fully qualified (i.e. using the absolute path to the command to run)
+
+If the command ends with a trailing `/` character and points to a directory, the user will be able to run any command in that directory (but not in any sub-directories therein). In the following example, the user `user` can run any command in the directory `/home/someuser/bin/`:
+
+```
+user = (root) NOPASSWD: /home/someuser/bin/
+```
+
+As an alternative to editing the `/etc/sudoers` file, you could add the two lines to a new file in `/etc/sudoers.d` e.g. `/etc/sudoers.d/shutdown`. This is an elegant way of separating different changes to the `sudo` rights and also leaves the original `sudoers` file untouched for easier upgrades.
+
+*visudo can be used to edit those files too, this prevent error that could lock you out of the system*
+```
+sudo visudo -f /etc/sudoers.d/shutdown 
+```