[Pkg-bluetooth-maintainers] Bug#755274: bluez: BT adapter isn't powered on at boot

[Andriy Martynets]

On Tue, 22 Jul 2014 15:39:36 +0200
Michael Biebl <biebl at debian.org> wrote:

> Instead of having each udev rule having to work around this issue, it
> would be much better to simply mount /usr via the initramfs and
> discourage the use of a separate /usr partition.
> dracut can already do that, for initramfs-tools there is [1].
> 
> As a reality check you might be interested in the attached list.
> 
> Cheers,
> Michael
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652459

Dear Michael,
Many thanks for the info provided and one more idea on how to work
around this bug. But this is not the solution. The solution is a change
to the package after which end-user, once installed it on to the
standard Debian system, will have to take zero steps to get it working.

As the root cause of the issue is the policy violation I see the
simplest and straight forward solution as to move file in question to
standard location to comply with standards.

From your message I can conclude that you are going to make the package
dependent on new versions of initramfs-tools, sysvinit and util-linux
packages which seem to be not available yet. Is this correct?

Reading all these threads (bug #652459 and related) I thought that
guys must have good reason to make simple things so complicated. I share
believe that initramfs is to provide the kernel with the module to
mount real rootfs. All the rest can be done by real init. Thanks to
Robert Tracy I realized what is the reason. It's all about systemd!
This answered all my questions...

Best regards,
Andriy