when /flash or /storage is on non-persistent storage, it's not
yet available at the time fsck -a -p fires, so just skip
and force fsck only if ret=4
now, if /flash or /storage is non-persistent, users get
either non-recovered fs (just as it was before) or debug
shell if the fs is fubar (bad sb and so). nobody cares.
Tweak to support the newer PS3 BD (with IR) remote which identifies differently.
Version 1
[ 142.524200] input: BD Remote Control as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:43/0005:054C:0306.0001/input/i$
[ 142.533894] sony 0005:054C:0306.0001: input,hidraw0: BLUETOOTH HID v1.00 Gamepad [BD Remote Control] on 00:00:00:00:00:00
-------------
Version 2
[ 7476.763657] input: Sony Computer Entertainment Inc BD Remote Control as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.3/1-1.3.3:1.0/bluetooth/hci0/hci0:11/0005:054C:0306.000A/input/input9
[ 7476.764266] sony 0005:054C:0306.000A: input,hidraw4: BLUETOOTH HID v1.10 Gamepad [Sony Computer Entertainment Inc BD Remote Control] on 00:00:00:00:00:00
this makes no sense and may stop systemd-tmpfiles-setup,
journald-flush, sshd, irserver from starting
===
Jan 18 18:23:03 openelec systemd[1]: Found ordering cycle on systemd-tmpfiles-setup.service/start
Jan 18 18:23:03 openelec systemd[1]: Found dependency on systemd-journal-flush.service/start
Jan 18 18:23:03 openelec systemd[1]: Found dependency on var-log-debug.service/start
Jan 18 18:23:03 openelec systemd[1]: Found dependency on systemd-tmpfiles-setup.service/start
Jan 18 18:23:03 openelec systemd[1]: Breaking ordering cycle by deleting job systemd-journal-flush.service/start
===
units with DefaultDependencies=no should be always properly ordered.
