I should clarify: I didn't mean actual expansion of the law. What I meant in regard to item "F" was: since when does difficulty of enforcement, even if they did prove it, justify loosening the standards of evidence? I did not think that was allowable.
Well I knew exactly what you meant Jane, even before you 'clarified' it.
Hi, NYCL! I haven't noticed you around here much lately. Is item F even a thing? Since when does the difficulty of enforcing a law allow judicial expansion of the law? I thought that idea had been thoroughly buried a long time ago.
I have to agree with you Jane Q. For 10 years I've been trying to wake the courts up to the fact that they're not supposed to bend the law to help content owners just because the content owners don't know who committed the infringement. Glad to see them coming around.
I think that if this troll can prove they have a copyright on the material and the right to enforce it, they will have a good case to appeal this decision and it will likely be overturned.
You also have to prove that the person you're suing actually committed the infringement. It's not enough that they paid the bill for an internet service account that somebody used to commit an infringement.
Please read on what POSIX is first. It is what guarantees that your software will be portable, which is a foundation upon which UNIX is built.
Yes, POSIX is important. But as with any standard it defines the least common denominator. Couple that with the fact that POSIX was not updated in years and you have to address the least common denominator from more that 5 years ago (I think even longer...). That is an eternity in IT. A standard is fine, but it should not stop you from playing to your strength.
Systemd argues that an init system is closely related to the Kernel and should make all the fancy kernel features available to user space. There is enough precedence for this in commercial unix variants by the way: Many come with init systems tailored to their specific strength of their kernels. I do not see that as a bad thing. So far I am not aware of anybody in the BSD camp even wanting to port systemd. At least the FreeBSD developers said they wanted a modern init system, too, but they are going for something that plays to the strength of their own kernel. So why should systemd bother about being portable to OSes that want to come up with their own solution?
That BSDs require some compatibility layer is nothing new, either. There is support for Linux style
There are projects on the BSDs as well, that are non-portable: LibreSSL and openSSH from openBSD spring to mind here. Those use interfaces from the BSD kernel. There a separate porting projects that bring those code bases over to Linux. They actually introduced a new kernel API due to libreSSL into the Linux kernel.
I see nothing bad in targetting specific platforms whatsoever. Yes, I do think POSIX is important: If you can do something with POSIX, then use that. If not, then use something else. And when in doubt target one platform and let people that care for other platforms port the stuff if they care.
It was not possible with consolekit, great that there was progress with consolekit2.
There is no way to refute conspiration theorists. It is a self-contained believe system, that functions outside of the real world. I won't bother to argue with that.
What got vdev/udev to do with running xorg as non-root? Yes, that does initial setup of device nodes, but all the rest is handled by systemd-logind.
You are brandishing the wing stick:-)
That person is bitching that everybody and their dog start to depends on systemd. That is your evidence right there.
Of course you have to do the dating assumption that devs do whatever they like... It kind of crumples if you assume that there are systemd hitmen traveling the world, forcing developers to depend on systemd.
That consultation mongering in that link is indeed laughable.
The absense of CVEs can mean the absense of people looking, and with the x11 being a quagmire of protocols, often contradicting each other as new stuff gets added over the decades, there are very few people that can even understand the code. One guy started to look last a while back and he is finding appalling bugs, check the recent CVEs and his presentation at last years chaos communication congress (30C3).
Making this swamp a bit dryer by not having it have root priviledgea is something that was work in progress ever since xfree started to run on Linux.
Now you come here and tell me that this sour spot for the last thirty years is better to keep around than having a much smaller, much cleaner codebase where almost all parts run in their own security context -- usually with privileges way lower than those you have as a user. Right.
Mid term devuan has just one chance: Make it easy for developers to provide solutions that work with multiple int systems. Systemd does bring quite a few improvements for developers. That is the reason why systemd becomes entrenched: Developers like it and start to depend on it since it makes their live easier.
If devuan wants to keep a manageable distribution they need to make it similarly easy to tackle issues in a convenient and reliable way when using multiple init systems. If they manage that, then I am pretty sure developers will support their interfaces in favor of systemd. No developer wants needless ties.
Unfortunately it is much harder to provide generic solutions than it is to provide a specific one. So devuan is in a very challenging position to make things easier for developers.
Is they blow this, then they will have more and more software that depends on systemd-only interfaces and more and more work to remove those dependencies.
One of the chief duties of the mathematician in acting as an advisor... is to discourage... from expecting too much from mathematics. -- N. Wiener
