| 1 |
Am 13.02.2013 21:05, schrieb Stefan G. Weichinger: |
| 2 |
> Am 2013-02-13 21:01, schrieb Canek Peláez Valdés: |
| 3 |
> |
| 4 |
>> LVM2 will be pulled again by udisks2; it's a mandatory dependency. I |
| 5 |
>> don't think the problem is related to LVM, but I don't really know. |
| 6 |
> |
| 7 |
> I already found out, yes. Maybe it's just some systemd race condition. |
| 8 |
> It's not that important to me right now ... I will check back with later |
| 9 |
> releases and google bug-reports now and then. |
| 10 |
|
| 11 |
Another update: |
| 12 |
|
| 13 |
posted to systemd-devel and got pointed to LVM/DM-people ... I don't know: |
| 14 |
|
| 15 |
http://lists.freedesktop.org/archives/systemd-devel/2013-March/009323.html |
| 16 |
|
| 17 |
- |
| 18 |
|
| 19 |
Next systemd-issue (yes, I know ... openrc is there as well ...): |
| 20 |
|
| 21 |
I get warnings like "superblock date is in the future --- REPAIRED" for |
| 22 |
filesystems at boot-time. |
| 23 |
|
| 24 |
Canek, (how) do you handle time and hwclock with systemd? |
| 25 |
|
| 26 |
I *had* a hwclock.service and removed it now ... no change. |
| 27 |
|
| 28 |
Greets, thanks, Stefan |
Archives