You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Digging into initial SR creation, I find a couple of inconsistencies, not all of which are obvious to get straight:
default-storage.conf gets written both XSPARTITIONS/XSTYPE and PARTITIONS/TYPE, with backend.py saying the latter are legacy names. It would appear that scripts on a newly installed system will use non-legacy names and have no need for legacy ones, so probably we could remove legacy names. However storage-init does use PARTITIONS/TYPE. Something looks wrong :)
backend.py points to prepare-storage as user of this file, while the user is clearly storage-init
@rosslagerwall, those XS names were introduced in 2008, is this some transition that did not make it into sm ?
The text was updated successfully, but these errors were encountered:
Digging into initial SR creation, I find a couple of inconsistencies, not all of which are obvious to get straight:
default-storage.confgets written bothXSPARTITIONS/XSTYPEandPARTITIONS/TYPE, withbackend.pysaying the latter are legacy names. It would appear that scripts on a newly installed system will use non-legacy names and have no need for legacy ones, so probably we could remove legacy names. Howeverstorage-initdoes usePARTITIONS/TYPE. Something looks wrong :)backend.pypoints toprepare-storageas user of this file, while the user is clearlystorage-init@rosslagerwall, those
XSnames were introduced in 2008, is this some transition that did not make it intosm?The text was updated successfully, but these errors were encountered: