[arch-general] [arch-dev-public] Migration to systemd

[Jayesh Badwaik]

On Thursday 16 Aug 2012 22:37:25 Felipe Contreras wrote:
> On Thu, Aug 16, 2012 at 4:15 PM, Brandon Watkins <bwat47 at gmail.com> 
wrote:
> > Doing it later does not necessarily "minimize" problems, in fact it
> > can sometimes exacerbate problems.
> 
> No it doesn't, quite the opposite actually.
> 
> Here, I'm going to do something that you are not doing, not just make
> an unsupported statement, but actually show an argument: the more
> mature a piece of software is, the less likely it is you are going to
> hit a bug.
> 
> Can you do the same? Not just say "X is true", but "X is true because
> Y", if you don't, then there's no value in your statements.

@Felipe
Brandon is saying from a developers perspective and you are saying from 
a user perspective. But, in case of ArchLinux and other distributions, 
its all the same. 

In commercial software which people are using and testing, adopting 
later is a good move because most of the bugs would have been ironed 
about by either the testing team or by the team of early testers. 

In a community like ArchLinux when compared to the bigger ecosystem of 
linux, the complete archcommunity is a tester. Earlier they test, 
earlier the problem can be found.

Of course, you are free to adopt as late as possible, especially on your 
production system, and hence Tom has shown his intent to maintain 
initscripts as long as udev works with it. So, while you may not want to 
shift completely. you can try testing systemd everytime you have 
maintainance on your servers. Or if you have a desktop, you can try 
testing systemd once in a while and report errors, which can then be 
resolved.

With the variety of computers existing, it is possible that every case 
reported here will be unique. 

-- 
Cheers and Regards
Jayesh Badwaik
stop html mail      | always bottom-post
www.asciiribbon.org | www.netmeister.org/news/learn2quote.html