Opened 7 years ago
Last modified 7 years ago
#262 new enhancement
Require a reboot upon CONFIG.SYS or driver update
| Reported by: | dmik | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | rpm | Version: | |
| Severity: | medium | Keywords: | |
| Cc: | dave.r.yeo@… |
Description (last modified by )
Updating some components of the system requires a reboot in order for the changes to be picked up by the system or by the applications. These components include CONFIG.SYS and driver updates. RPM should require a reboot after such updates and prevent any further operation including installation, update or removal of packages. This ticket complements #261.
Change History (2)
comment:1 by , 7 years ago
| Cc: | added |
|---|
comment:2 by , 7 years ago
| Description: | modified (diff) |
|---|
You mean to cause proper paths in CONFIG.SYS with a new drive letter? Okay but this already doable with some script magic: all CONFIG.SYS changes are done from RPM install/uninstall scriptlets using a cube macro, so one can query scriptlets of all installed RPMs via the rpm -q interface and reinstall those that use cube. Won't be fast perhaps, but fully automated.
Of course, the cube macro may be tweaked to additionally main a file containing a list of all packages that change CONFIG.SYS to speed up the reinstall operation. This is something to think on.
It would be nice if this is implemented in such a way that RPM's that require a reboot are easy to flag for reinstall in the case where @UNIXROOT is shared between partitions, versions of OS/2 etc. Even something as simple as prefixing with OS2.