* Re: [gentoo-user] Re: systemd? [ Was: The End Is Near ... ]
@ 2012-03-18 2:52 99% ` Pandu Poluan
0 siblings, 0 replies; 1+ results
From: Pandu Poluan @ 2012-03-18 2:52 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 2237 bytes --]
On Mar 18, 2012 9:44 AM, "Joshua Murphy" <poisonbl@gmail.com> wrote:
>
> On Sat, Mar 17, 2012 at 10:12 PM, Nikos Chantziaras <realnc@gmail.com>
wrote:
> > On 18/03/12 03:45, Canek Peláez Valdés wrote:
> >>
> <snip>
> >> [...]
> >>
> >> * It tries to unify Linux behaviour among distros (some can argue that
> >> this is a bad thing): Using systemd, the same
> >> configurations/techniques work the same in every distribution. No more
> >> need to learn /etc/conf.d, /etc/sysconfig, /etc/default hacks by
> >> different distros.
> >
> >
> > Out of the things you listed, this strikes me as the most important.
Linux
> > really needs standards. When I install software on Windows, it knows
how to
> > add its startup services. On Linux, this is all manual work if your
distro
> > isn't supported, especially on Gentoo. If there's no ebuild for it, you
> > spend your whole day trying to make it work.
> >
> >
>
> My day job's on the windows side of things... and as true as it is
> that the application developer knows the approach they're going to use
> today to get their piece of software to start when windows does (as
> often as not, doing so without the knowledge of the user), there's a
> *massive* range of ways to do just that, and they *do* vary as you
> move from one version of windows to the next... and tracking down
> what's actually starting at boot (and why) without tools explicitly
> created to give that information is an incredible amount of work on
> the side of the user and even the usual admin. I'm not sure I'd cite
> that as a positive benefit on the windows side of things...
>
True, that.
Case in point : a couple of months back, I had great trouble trying to
start the server service *after* the iSCSI service. Finally have to resort
on a script starting using Windows Scheduler (post-boot event)
On Linux, I *know* where services are started. The locations might be
different from one distro to another, but within one distro, there's
(usually) only 2 ways a service get started.
Plus, as a server guy, I don't really care if the boot up process is
faster; I need deterministic boot process, with as succinct instrumentation
as possible.
Rgds,
[-- Attachment #2: Type: text/html, Size: 2734 bytes --]
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2012-03-17 4:11 [gentoo-user] The End Is Near ... or, get the vaseline, they're on the way! Bruce Hill, Jr.
2012-03-17 6:25 ` [gentoo-user] " Nikos Chantziaras
2012-03-17 11:53 ` [gentoo-user] systemd? [ Was: The End Is Near ... ] Alan Mackenzie
2012-03-18 0:48 ` [gentoo-user] " Nikos Chantziaras
2012-03-18 1:45 ` Canek Peláez Valdés
2012-03-18 2:12 ` Nikos Chantziaras
2012-03-18 2:41 ` Joshua Murphy
2012-03-18 2:52 99% ` Pandu Poluan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox