On Fri, Dec 28, 2012 at 12:28 AM, Kevin Chadwick <ma1l1i...@yahoo.co.uk> wrote:
>
> Again you don't break the spec unless you have to and you don't change
> the spec unless it is an improvement or you have no choice. Non of
> which is the case. Just like you do not mould a mail RFC to a
> widely used technically inferior hotmail implementation.

The spec - or implementation - of / and /usr separation is broken and
has been for quite a while now. Nobody here's even bothered answering
how the modern Gentoo distro / sysad would survive /usr being out of
sync with /, for instance, or the fact that some udev programs tend to
be located in /usr, or even just a solid detailed specification on the
precise criteria for inclusion into /. Even the FHS is mum on all the
extra crap we randomly decide between / and /usr to land in. You'd
think, for instance, something as clear cut as filesystem manipulation
tools, e.g., xfs_admin, would belong in /sbin rather than /usr/sbin.
But no it's not. Or - for crying out loud, at least a text editor that
isn't ed.

Again, the broken state of the / and /usr split is a different thing
from the usefulness state of your own already installed distro.

TLDR: The spec is broken.

>
>> He's like DJB on crack.
>
> Except DJB made every Linux system on this planet more reliable simple
> and secure through better coding practices and pointing out how buggy
> sendmail was. Lennart if anything will accomplish the exact opposite
> where systemd is used.

If you have something more than FUD to back up your technical claims,
go ahead. You're directly claiming that wherever systemd is used, the
system will be less reliable and secure, and that Lennart isn't
pointing out buggy behaviors in - what's the analogue for sendmail? oh
yeah - SysVInit scripts.

To carry the analogy, DJB's main point was that the size of the code
was one of - if not the - most important factors in increasing code
quality and security, and worked to make qmail and its configuration
about as spartan as you can get. That's kind of the point of systemd
unit files, trimming the boilerplate size to reduce gotchas like init
scripts failing to detect whether a service is running or not, or if
its dependencies have been started.
--
This email is:    [ ] actionable   [ ] fyi        [x] social
Response needed:  [ ] yes          [x] up to you  [ ] no
Time-sensitive:   [ ] immediate    [ ] soon       [x] none

Reply via email to