What is new: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
| user | | user | ||
| No mailing list | | No mailing list | ||
| Users must be registered into the Infinity user mailing list. | | '''Users must be registered into the Infinity user mailing list.''' | ||
| In the near future, Infinity will be accessible only for registered users in Matacentrum. | | '''In the near future, Infinity will be accessible only for registered users in Matacentrum.''' | ||
|- | |- | ||
| technical, AMS | | technical, AMS | ||
| Line 22: | Line 22: | ||
| The default site is selected by the host group name, which must be provided prior to the Infinity activation | | The default site is selected by the host group name, which must be provided prior to the Infinity activation | ||
| Simpler administration | | Simpler administration | ||
|- | |||
| technical, AMS | |||
| Complex and not always working set-up of user creation mask (umask). | |||
| Simpler, well-defined set-up of user creation mask (umask). Umask is set in all new (child) shell instances. | |||
| Guaranteed data access management. | |||
|- | |- | ||
| user interface, AMS, | | user interface, AMS, | ||
Revision as of 21:40, 17 January 2024
Documentation / User Manual / What is new
| Scope | Old AMS(v8.x)/ABS(v3.x) | New AMS(v9.x)/ABS(v4.x) | Comment |
|---|---|---|---|
| user | No mailing list | Users must be registered into the Infinity user mailing list. | In the near future, Infinity will be accessible only for registered users in Matacentrum. |
| technical, AMS | One monolithic module cache per site | Several module caches are organized into module bundles, which are site-independent. | Users can define their own modules. |
| technical, AMS | The default site is selected by hostname lookup into the host group database | The default site is selected by the host group name, which must be provided prior to the Infinity activation | Simpler administration |
| technical, AMS | Complex and not always working set-up of user creation mask (umask). | Simpler, well-defined set-up of user creation mask (umask). Umask is set in all new (child) shell instances. | Guaranteed data access management. |
| user interface, AMS, | Fine-tuned colour preferences for printing into terminals can be defined by a user (ams-config). | Only predefined colour profiles can be selected now (ams-config). The administrator defines their list, which can be extended by a user. |