[ale] Debian fork thoughts?

[Jim Kinney]

It's really not about faster boot times. It's about a better managed init
process. By having all the stuff that starts at boot run by a single
process that does all the start and stops, plus providing insight into
failures, the idea is to make the system more robust.

Granted, my first custom systemd script is not yet working. But then my
first custom initd scripts also didn't work.

Side note: some centos7 systems don't run journalctl and some do. No
pattern stands out yet. Weird.
On Dec 3, 2014 9:17 AM, "Wolf Halton" <wolf.halton at gmail.com> wrote:

> Does this systemd vs init controversy actually lead out to anything
> useful?  I reboot my laptop a lot and I have never pined away for a faster
> boot time.  Ubuntu Studio 14.04LTS  seems to be running both daemons, but
> starting with init.
>
> me at telcontar-2:~$ pgrep init
> 1
> 2606
> 3780
> me at telcontar-2:~$ pgrep systemd
> 373
> 1047
> me at telcontar-2:~$ uname -a
> Linux telcontar-2 3.13.0-41-lowlatency #70-Ubuntu SMP PREEMPT Tue Nov 25
> 15:07:35 UTC 2014 i686 i686 i686 GNU/Linux
>
> When I was running a lot of Debian systems, I hardly ever rebooted any of
> them, except lab environment hosts.  I have never seen a kernel panic,
> except on my laptop, where I beta test stuff.  I am running Fedora VMs and
> have not felt that the systemd initialization was much faster than any
> other initiation system.
>
>
> Wolf Halton
> Mobile 678-687-6104
> --
> Expand Your Vision = Enhance Your Impact
> Marketing and Security in the Cloud - http://AtlantaCloudTech.com
> <http://atlantaCloudTech.com>
>
>
> On Mon, Dec 1, 2014 at 7:22 PM, Solomon Peachy <pizza at shaftnet.org> wrote:
>
>> On Mon, Dec 01, 2014 at 06:51:26PM -0500, James Sumners wrote:
>> > Really? I'll let the comments on [1] do most of the talking. I wanted to
>> > link the article that post is about, but the article author changed the
>> > content. It originally detailed how you'd have to install systemd to
>> > install Jessie, and then jump through some hoops to get it removed
>> after OS
>> > install.
>>
>> Systemd is *default* in Jessie, so of course it's installed and running
>> unless you say otherwise; but it's not intended to be automatically
>> enabled if you're upgrading an older system -- if it happens, file a
>> bug, that's what release freezes are for!
>>
>> So, if you don't like systemd to be running, turn it off and uninstall
>> (most of) it -- It's a simple apt-get command.
>>
>> Continuing on, If you are objecting to libraries remaining on the hard
>> disk, you might as well be complaining that you need e2fsprogs installed
>> when you don't have any ext2/3/4 filesystems -- because the libaries are
>> used by other tools and it had to be enabled at compile time or not at
>> all.
>>
>> Sure, one could mangle everything to load every potential feature and
>> dependency at runtime, but that's a lot of work to save a couple hunded
>> kilobytes of disk space at a time.  You're welcome to do it if it means
>> that much to you; I'm sure deb package maintainers will happily accept
>> patches.  Otherwise everyone has much has better things to do.  Like
>> knocking out actual bugs in Jessie.
>>
>>  - Solomon
>> --
>> Solomon Peachy                         pizza at shaftnet dot org
>> Delray Beach, FL                          ^^ (email/xmpp) ^^
>> Quidquid latine dictum sit, altum viditur.
>>
>> _______________________________________________
>> Ale mailing list
>> Ale at ale.org
>> http://mail.ale.org/mailman/listinfo/ale
>> See JOBS, ANNOUNCE and SCHOOLS lists at
>> http://mail.ale.org/mailman/listinfo
>>
>>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20141203/d74633e7/attachment.html>