Hide Forgot
Description of problem: Installing the FC development tree from today, on bootup /sbin/dmraid -a y is started on a read-only / partition and "mkdir /var/lock/dmraid" fails. Packaging this directory into the rpm package is probably best (???). Looking into the changelog, seems there is also a "--ignorelocking" option which could be used? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Changing assignment to notting to be addressed in initscripts: dmraid needs to be called with the '--ignorelocking' option there in order to avoid a root readonly issue (ie, 'dmraid -i -ay').
--ignorelocking added in CVS, will be in 8.15-1. Popping back over to dmraid to own the directory.
Bill, owning /var/lock/dmraid in a readonly environment won't help. dmraid must be run with the -i option in early boot avoiding access to /var completely. Any later dmraid runs w/o -i after boot are ok with readwrite access to /var. Did I miss something with your recommendation ?
If it requires the lock directory, it should be created as part of the RPMs build process and shipped with the package, as opposed to created at runtime, regardless of whether or not rc.sysinit calls it with --ignorelocking.
Fixed in devel: /var/lock/dmraid included in rpm from version dmraid-1.0.0.rc10-FC5_6.2.