Mailinglist Archive: yast-devel (55 mails)

< Previous Next >
Re: [yast-devel] storage-ng and cache invalidation
On 05/30/2017 11:04 AM, Arvin Schnell wrote:
On Tue, May 30, 2017 at 10:04:33AM +0200, Josef Reidinger wrote:


Now lets get to storage-ng. I try to port this fix there. So my
first question is, what is similar equivalent in storage-ng
which allows me to see if there is change in storage, so
bootloader proposal is no longer valid?

That was discussed and even documented in
yast2-storage-ng/doc/ but unfortunately
already deleted. Have a look at

And implemented as documented here.

To check the revision number:

To update the staging devicegraph making sure revision gets updated as well:

Ancor González Sosa
YaST Team at SUSE Linux GmbH
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >