Comment # 7 on bug 1228854 from Glass Su
(In reply to Fabian Vogt from comment #6)
> (In reply to Glass Su from comment #5)
> > (In reply to Fabian Vogt from comment #4)
> > > (In reply to Glass Su from comment #3)
> > > > 2) The other method is to create /etc/lvm/devices when lvm package installs
> > > > just like what fedora/centos does:
> > > > https://src.fedoraproject.org/rpms/lvm2/blob/rawhide/f/lvm2.spec#_374
> > > > 
> > > > 
> > > > The issue may occur again in the long future if we move /etc/ to /usr/etc
> > > > and /usr is a mountpoint. But for now, I think it's simple for method 2.
> > > 
> > > Please don't, we need less packages messing with /etc, not more.
> > > /etc/lvm/devices/ will not move to /usr/etc/ as it's for system
> > > configuration.
> > > 
> > Sorry. Could you elaborate? If /etc/lvm/devices/ will not move to /usr/etc/,
> > the directory created by installation can be seen by lvm2-monitor before
> > systemd-remount-fs.service. So the issue won't happen, right?
> 
> Packages must only own files within /usr/ and the system must be able to boot
> with empty /etc/.
> 
> https://en.opensuse.org/openSUSE:Packaging_UsrEtc#What_do_we_want_to_do?

I see. I will submitted a change as comment 4 suggested. lvm2-monitor service
used to start after local-fs.target before 2015. Also I've checked so it should
be okay.


You are receiving this mail because: