Re: [PATCH/RFC] Have sane default values for cpusets

[Peter Zijlstra]

On Thu, 2010-05-13 at 16:03 +0200, Lennart Poettering wrote:
> > On Wed, 2010-05-12 at 21:07 +0200, Lennart Poettering wrote:
> > > See Dhaval's patch on the background of systemd
> > > (http://0pointer.de/blog/projects/systemd.html). When a service is
> > > started in systemd, we create a cgroup for it, when it ends, we remove
> > > it. 
> > 
> > I seriously hope that's optional, because I for one would really hate a
> > system that does that. I still mostly build kernels with only cpuset in
> > and really don't want anybody but me creating groups in there.
> 
> By default systemd will create its groups in the "debug" hierarchy, (at
> least for now, in the long run i'd like to see "noop" hierarchy or so,
> that doesn't sound so temporary), since that controller is not useful
> for anything but keeping track of processes. So it shouldn't bother you
> at all. 

Will it still work with a CONFIG_CGROUP=n kernel? I see distributions
deteriorate, you cannot even boot a raw bzImage kernel without initrd on
most distros (sure, its not too hard to fix, but still).

Also, I get all kinds of dumb-ass init-script failures for not having
modules but stuff built-in. A prime example is NFS failing on start on
both fedora and ubuntu with a built-in nfs server (for different but
both retarded reasons).

Requiring CONFIG_CGROUP=y to even get init running seems like a final
straw to ensure nobody will ever get anything to boot these days.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/