4 ms·
Jason is doing great work here. These aren’t fun to solve problems. Even if long term he can bootstrap a proper userspace ecosystem of using /dev/*random, will
by CyberRabbi 5y ago
Jason is doing great work here. These aren’t fun to solve problems.
Even if long term he can bootstrap a proper userspace ecosystem of using /dev/*random, will the unification ever be possible if we have to support these old systems?
I am generally in favor of maintaining 100% userspace backward compatibility but in this case I would support changing the behavior since the old shell scripts were exploiting behavior that wasn’t documented and was always incorrect.
- bhawks 5y agoIn the context of Linux on embedded and mobile breaking user space would lead to hardware manufacturers essentially freezing on the kernel version right before the break. (For both new projects or in the exceedingly rare case where they upgrade deployed devices). This would be exceedingly unwise and pushes against the vast amount of effort the kernel community is expending to secure the kernel and bring OEMs on non ancient versions of the kernel. Essentially these are not old devices, they are new and you likely have purchased some of them without even knowing.
- CyberRabbi 5y agoWouldn’t it be easier to patch their startup scripts than freezing their kernel?