forked from linux/documentation
document how to set up the network drives after session startup
This commit is contained in:
1 parent
c3a41d9c51
commit
daa19bb56e
4 files changed
+6
-2
No files matched your search
@@ -51,7 +51,7 @@ Note that when using the [AD provider](../basic/ad_integration) (default with RH
|
||||
|
||||
## Eaccounts and `override_homedir`
|
||||
|
||||
By default the `override_homedir` setting (in Hiera `aaa::override_homedir` ore `base::local_homes`) is ignored for eaccounts.
|
||||
By default the `override_homedir` setting (in Hiera `aaa::override_homedir` or `base::local_homes`) is ignored for eaccounts.
|
||||
The way this has been solved causes problems with group member lookups with eaccounts enabled.
|
||||
|
||||
Without eaccounts only normal users are found as part of the group (which is correct):
|
||||
|
||||
@@ -137,7 +137,7 @@ Then on the node best run
|
||||
```
|
||||
dnf versionlock add $PACKAGE
|
||||
```
|
||||
for every package you do not wish to get updates installed any more. If there are newer packages you might test with `dnf update --assumeno` if it does not show your software any more, while other updates are still possible. Sometimes this can cause dependency resolution failures and you might need to add a version lock for one ore more packages which depend on the locked package.
|
||||
for every package you do not wish to get updates installed any more. If there are newer packages you might test with `dnf update --assumeno` if it does not show your software any more, while other updates are still possible. Sometimes this can cause dependency resolution failures and you might need to add a version lock for one or more packages which depend on the locked package.
|
||||
|
||||
After you best put the resulting `/etc/dnf/plugins/versionlock.list` in Hiera with [`files::files`](../files/distribute_files) for reproducability.
|
||||
|
||||
|
||||
@@ -2,4 +2,8 @@
|
||||
|
||||
In your home directory you find in `network-drives` the same Windows shares as on a PSI Windows system. Note that the `U:` drive is named `home`, the rest has their original share name.
|
||||
|
||||
If it is missing or they got disconnected e.g. due to network changes on laptops, you can try to bring them back by running `setup-network-drives` in the shell or start the "Setup Network Drives" tool :
|
||||
|
||||

|
||||
|
||||
If it does not work, point your admin to the [configuration guide](../admin-guide/configuration/files/windows_drives_in_home).
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 44 KiB |
Reference in new issue
Block a user