On 2/6/19 6:38 PM, suscrici...@gmail.com wrote:
> Hi,
>
> First of all apologies if this is not the correct channel to request
> for help with this issue. I've tried asking in Arch Linux forums
> without luck for the moment.
>
> Long story short, from time to time I'm dropped to a rescue shell
>
On 07/10/2017 12:14 PM, Peter Rajnoha wrote:
> On 07/10/2017 11:53 AM, Lennart Poettering wrote:
>> On Mon, 10.07.17 11:37, David Disseldorp (dd...@suse.de) wrote:
>>
>>> Thanks for the feedback, Lennart...
>>>
>>> On Mon, 10 Jul 2017 10:38:38 +0200,
On 07/10/2017 11:53 AM, Lennart Poettering wrote:
> On Mon, 10.07.17 11:37, David Disseldorp (dd...@suse.de) wrote:
>
>> Thanks for the feedback, Lennart...
>>
>> On Mon, 10 Jul 2017 10:38:38 +0200, Lennart Poettering wrote:
>>
>>> On Wed, 05.07.17 13:01, David Disseldorp (dd...@suse.de) wrote:
>>
On 05/15/2014 11:38 PM, Lennart Poettering wrote:
> On Thu, 15.05.14 23:15, Andy Kittner (andy.kitt...@gmail.com) wrote:
>
>> | May 15 22:06:47 pinky systemd[1]: Mounted Runtime Directory.
>> | May 15 22:06:47 pinky systemd[1]: Mounted Lock Directory.
>
> This looks like remains from a *really* o
Hi!
Based on SYSTEMD_READY definition, I think we should also mark loop
devices with no file attached as not ready:
rules: mark loop device as SYSTEMD_READY=0 if no file is attached
Check existence of loop/backing_file in sysfs and mark loop
devices with SYSTEMD_READY if missing. Suc
On 09/13/2012 02:28 PM, Kay Sievers wrote:
> On Thu, Sep 13, 2012 at 2:23 PM, Lennart Poettering
> wrote:
>> On Thu, 13.09.12 15:47, Alexey Shabalin (a.shaba...@gmail.com) wrote:
>>
Please check with "udevadm info
/dev/disk/by-uuid/a8ce6981-1afd-4af6-8783-784b3c7a7d64" if the device is
>
