OpenSUSE Leap 15.2 Release Notes: Difference between revisions
Page created |
m Added coloured boxes |
||
| Line 21: | Line 21: | ||
The installer supports the system role ''Transactional Server''. This system role features an update system that applies updates atomically (as a single operation) and makes them easy to revert should that become necessary. These features are based on the package management tools that all other SUSE and openSUSE distributions also rely on. This means that the vast majority of RPM packages that work with other system roles of openSUSE Leap 15.2 also work with the system role ''Transactional Server''. | The installer supports the system role ''Transactional Server''. This system role features an update system that applies updates atomically (as a single operation) and makes them easy to revert should that become necessary. These features are based on the package management tools that all other SUSE and openSUSE distributions also rely on. This means that the vast majority of RPM packages that work with other system roles of openSUSE Leap 15.2 also work with the system role ''Transactional Server''. | ||
<div style="background:#C0C0C0;border:1px solid #666666;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;"> | |||
'''Note: Incompatible Packages''' | '''Note: Incompatible Packages''' | ||
Some packages modify the contents of <code>/var</code> or <code>/srv</code> in their RPM <code>%post</code> scripts. These packages are incompatible. If you find such a package, file a bug report. | Some packages modify the contents of <code>/var</code> or <code>/srv</code> in their RPM <code>%post</code> scripts. These packages are incompatible. If you find such a package, file a bug report. | ||
</div> | |||
To provide these features, this update system relies on: | To provide these features, this update system relies on: | ||
| Line 34: | Line 34: | ||
: To make this setup work, two additional changes to the file system needed to be made: To allow writing user configuration in <code>/etc</code>, this directory is automatically configured to use OverlayFS. <code>/var</code> is now a separate subvolume which can be written to by processes. | : To make this setup work, two additional changes to the file system needed to be made: To allow writing user configuration in <code>/etc</code>, this directory is automatically configured to use OverlayFS. <code>/var</code> is now a separate subvolume which can be written to by processes. | ||
<div style="background:#FDDFA6;border:1px solid #BB7B03;padding-left:5px;padding-right:5px;padding-bottom:15px;padding-top:5px;"> | |||
'''Important: ''Transactional Server'' Needs At Least 12 GB Disk Space''' | '''Important: ''Transactional Server'' Needs At Least 12 GB Disk Space''' | ||
The system role ''Transactional Server'' needs a disk size of at least 12 GB to accommodate Btrfs snapshots. | The system role ''Transactional Server'' needs a disk size of at least 12 GB to accommodate Btrfs snapshots. | ||
</div> | |||
To work with transactional updates, always use the command transactional-update instead of YaST and Zypper for all software management: | To work with transactional updates, always use the command transactional-update instead of YaST and Zypper for all software management: | ||