On 10/21/2012 02:25 PM, Michael H. Warfield wrote:
How do we work around this problem in systemd where it has hard
coded
mounts in the binary that we can't override or configure? Or is it
there and I'm just missing it trying to examine the sources? That's how
I found where the problem lay.
Why would anybody in their right mind do such a thing? It's just as bad
as when people hard-coded timing loops under the assumption that the PC
would always and forever run at 4.77 Mhz.