On 22/02/2014 03:32, Joel Lopes Da Silva wrote:
I don't really know much more than that, sorry. I'm not a FreeBSD
developer either. I'm just a guy who thinks launchd is a pretty awesome
init system, and who would love to see it more widely used.
Well, our hands are pretty busy here. But if you
Hi folks,
I’m just a lambda user of Debian GNU/kFreeBSD, not a Debian Developer or
Maintainer. But if I could give you guys my 2 cts, I’d encourage you to
really consider launchd for this discussion. It’s a proven system, which
has been in use for many years in what’s arguably one of the most
On 21/02/2014 19:09, Joel Lopes Da Silva wrote:
Furthermore, if you Google some of these big names (launchd, OpenRC and
systemd), narrowing down the search results to wiki.freebsd.org, it will
be pretty clear that launchd seems to be only one that’s actually being
worked on by FreeBSD
On Friday, February 21, 2014, at 09:04 PM, Robert Millan wrote:
On 21/02/2014 19:09, Joel Lopes Da Silva wrote:
Furthermore, if you Google some of these big names (launchd, OpenRC and
systemd), narrowing down the search results to wiki.freebsd.org, it will
be pretty clear that launchd seems
Hi,
On Sat, Feb 15, 2014 at 02:47:14PM +, Robert Millan wrote:
On 14/02/2014 18:46, Steven Chamberlain wrote:
Well, we have an announcement today from Canonical - AIUI Upstart will
be discontinued after Ubuntu 14.04 LTS and they will switch to systemd:
On 14/02/2014 18:46, Steven Chamberlain wrote:
Well, we have an announcement today from Canonical - AIUI Upstart will
be discontinued after Ubuntu 14.04 LTS and they will switch to systemd:
http://www.markshuttleworth.com/archives/1316
I'm not familiar with Ubuntu politics. Is everyone in line
On 29/01/2014 09:26, Petr Salinger wrote:
1. stay with sysvinit
2. switch to OpenRC unconditionally
3. switch to Upstart unconditionally
4. switch to Upstart only if Linux uses it by default, otherwise OpenRC
5. further discussion
Please rank the above putting your preferred option first,
On 12/02/14 12:04, Svante Signell wrote:
I fear that it is currently broken since one of the latest patches. Do
you have a (scrappable) pre-installed image I can download, ala:
http://people.debian.org/~sthibault/hurd-i386/
Yes, Aurelien Jarno has kindly made these:
On 12/02/14 10:45, Robert Millan wrote:
I'm a bit afraid that even if sysvinit itself stays mostly fine, the scripts
written for
it could turn into a bunch of bitrot.
There are a few reasons to keep sysvinit scripts maintained for jessie:
1. for smoother upgrades from wheezy
2. in order to
Forwarded Message
From: Svante Signell svante.sign...@gmail.com
To: debian-h...@lists.debian.org
Subject: Re: Init system for non-Linux ports
Date: Wed, 12 Feb 2014 13:02:45 +0100
On Wed, 2014-02-12 at 10:45 +, Robert Millan wrote:
On 29/01/2014 09:26, Petr Salinger wrote
On 12/02/2014 12:09, Steven Chamberlain wrote:
There are a few reasons to keep sysvinit scripts maintained for jessie:
1. for smoother upgrades from wheezy
2. in order to backport jessie packages to wheezy
3. for non-Linux (or non-systemd) ports
So ports are not the only reason. And yet
On 12/02/14 12:23, Robert Millan wrote:
If we have to support it anyway, is it really worth spending effort on
Upstart/OpenRC for Jessie?
Right, sysvinit is a viable and easy option for jessie; having any
other init systems working is a bonus.
At least we know now that we need to concentrate
On 12/02/2014 12:40, Steven Chamberlain wrote:
Although, come jessie+1, I wonder how upgrades will be handled, if
sysvinit scripts go away.
Maybe Pre-Depends. Or maybe have written instructions to install
the new init by hand, like we often do for kernels.
Or maybe backward compat? I hear some
On 12/02/14 13:18, Robert Millan wrote:
Or maybe backward compat? I hear some of the new init implementations
support SysV.
SysV init scripts?
I thought this was obvious, or maybe I misunderstand what you mean.
*All* of the init systems that were discussed by the TC, even systemd
(for now),
On 12 February 2014 12:23, Robert Millan r...@debian.org wrote:
On 12/02/2014 12:09, Steven Chamberlain wrote:
There are a few reasons to keep sysvinit scripts maintained for jessie:
1. for smoother upgrades from wheezy
2. in order to backport jessie packages to wheezy
3. for non-Linux (or
1. stay with sysvinit
2. switch to OpenRC unconditionally
3. switch to Upstart unconditionally
4. switch to Upstart only if Linux uses it by default, otherwise OpenRC
5. further discussion
Please rank the above putting your preferred option first, as per
Debian's usual Condorcet voting system.
Hi!
Robert Millan r...@debian.org writes:
[ 3 ] 1. stay with sysvinit
[ 3 ] 2. switch to OpenRC unconditionally
[ 3 ] 3. switch to Upstart unconditionally
[ 1 ] 4. switch to Upstart only if Linux uses it by default, otherwise OpenRC
[ 2 ] 5. further discussion
Petr Salinger
I'm only a kFreeBSD user and don't have any official standing within the
Debian project, but all the same my preferences are
614253
where 6. is the proposed alternative to switch to Upstart if Linux uses
it, otherwise sysvinit.
Jeff
--
To UNSUBSCRIBE, email to
Em 2014-01-28 20:31, Steven Chamberlain escreveu:
Hi everyone,
What init system would we like to use by default on the non-Linux
ports
for jessie?
I hope this question is really as straightforward as it looks, and that
we might come to some general agreement much more quickly than the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 28/01/2014 23:31, Steven Chamberlain wrote:
Here are the options I can think of - but let me know if you want
something not represented here:
1. stay with sysvinit
2. switch to OpenRC unconditionally
3. switch to Upstart unconditionally
4.
On 28/01/14 22:31, Steven Chamberlain wrote:
1. stay with sysvinit
I know that would be the least work, but I think we should take the
opportunity to switch now to one of the modern init systems. Some
package maintainers specifically expressed that they don't want to
maintain SysV init scripts
21 matches
Mail list logo
