As far as I have read in this thread, the only reported problem with
upgrading from sysv to systemd concerns remote virtual machines that
won't boot.
As I said earlier: some bits of my log entries are getting discarded by
journald.
--
Salvo Tomaselli
Io non mi sento obbligato a credere
On Thu, 15 May 2014 21:51:10 +0200, Josselin Mouette j...@debian.org
wrote:
Given the fact/bullshit ratio of your recent posts, I invite you, again,
to take a step back from debian-devel.
Given the insult/information ratio of your (not only recent) posts...
Greetings
Marc
--
On Fri, May 16, 2014 at 11:01:14AM +0200, Marc Haber wrote:
On Thu, 15 May 2014 21:51:10 +0200, Josselin Mouette j...@debian.org
wrote:
Given the fact/bullshit ratio of your recent posts, I invite you, again,
to take a step back from debian-devel.
Given the insult/information ratio of your
Am 15.05.2014 01:42, schrieb Marc Haber:
On Tue, 13 May 2014 17:28:27 +0200, Vincent Bernat ber...@debian.org
wrote:
? 13 mai 2014 15:01 +0200, Marc Haber mh+debian-de...@zugschlus.de :
Thank you so much for volunteering to contribute to GNOME packaging and
to make it work on configurations
Am 13.05.2014 21:49, schrieb Cyril Brulebois:
Thibaut Paumard thib...@debian.org (2014-05-13):
Le 13/05/2014 17:36, Russ Allbery a écrit :
Right, which I've been arguing for already in this thread. I don't think
we should force this on upgrades. There should be a prompt and an
opportunity
From: Guido =?iso-8859-1?Q?G=FCnther?= a...@sigxcpu.org
GTK+3 supports themes
GTK/GNOME people have stated numerous times that they do not want them.
. This
is a perfectly fine job for a derivate or Pure Blend: to provide a
polished system that serves one use case well.
Proper integration
Hi,
Michael Biebl:
I can not confirm this behaviour Matthias describes with v204.
Sorry, my bad. Turns out that this was not done via the rescue shell.
I was using the root shell which you get on TTY9 (assuming it is enabled,
which it usually isn't for obvious reasons).
Thanks for
Thorsten Glaser t...@debian.org writes:
. This
is a perfectly fine job for a derivate or Pure Blend: to provide a
polished system that serves one use case well.
Proper integration certainly belongs into Debian or did we become a
supermarket:
Proper integration of components: yes. That is the
On Thu, 2014-05-15 at 10:55 +0200, Gergely Nagy wrote:
Thorsten Glaser t...@debian.org writes:
Integration of some components at the cost of disabling the freedom
of users to choose a different free component that also does the job,
and at the cost of removing some users' use cases: no.
Le 15/05/2014 10:55, Gergely Nagy a écrit :
You do realise we have one libc (sure, you can install *additional*
ones, but we have one libc the archive is compiled against), we have one
package manager (you can, of course, install rpm too, it is packaged!),
we have one make we use to build
Thibaut Paumard thib...@debian.org writes:
Le 15/05/2014 10:55, Gergely Nagy a écrit :
You do realise we have one libc (sure, you can install *additional*
ones, but we have one libc the archive is compiled against), we have one
package manager (you can, of course, install rpm too, it is
Hi there!
Nothing related to any init system in Debian, but...
On Tue, 13 May 2014 19:19:54 +0200, Cyril Brulebois wrote:
Thibaut Paumard thib...@debian.org (2014-05-13):
Le 13/05/2014 17:36, Russ Allbery a écrit :
Right, which I've been arguing for already in this thread. I don't think
On Thu, May 15, 2014 at 06:33:41PM +0200, Luca Capello wrote:
...despite the above, MANY THANKS to all people writing the Release
Notes (and any other official documentation), which is highly
important at least for me, as well as a pleasure to read.
Hear hear, strongly and fully ack'd.
(And
Le jeudi 15 mai 2014 à 07:51 +, Thorsten Glaser a écrit :
From: Guido =?iso-8859-1?Q?G=FCnther?= a...@sigxcpu.org
GTK+3 supports themes
GTK/GNOME people have stated numerous times that they do not want them.
Do you have a quote to back up your claims?
The fact is that themes are
On Thu, May 15, 2014 at 07:51:37AM +, Thorsten Glaser wrote:
From: Guido =?iso-8859-1?Q?G=FCnther?= a...@sigxcpu.org
GTK+3 supports themes
GTK/GNOME people have stated numerous times that they do not want
them.
There's not Debian people and not Gtk+/GNOME people, this current
Le mardi, 13 mai 2014, 17.21:45 Thorsten Glaser a écrit :
Didier 'OdyX' Raboud dixit:
Le mardi, 13 mai 2014, 16.25:31 Thorsten Glaser a écrit :
On Mon, 12 May 2014, Tollef Fog Heen wrote:
Are you aware that Joss isn't a systemd maintainer? (He's one of
the GNOME maintainers.)
On Tue, May 13, 2014 at 11:06:10AM -0700, Russ Allbery wrote:
Thorsten Glaser t...@mirbsd.de writes:
• no /etc/init.d/$foo (to tabcomplete, no less!) any more
I've been telling people to stop using this for years. You should stop
Doesn’t matter in mixed environments. Suse SLES11 has the
On Tue, May 13, 2014 at 04:31:28PM +0200, Thorsten Glaser wrote:
On Tue, 13 May 2014, Josselin Mouette wrote:
My opinion is that many users are migrating away from Debian because we
are unable to make decisions on important technical topics and leave
them with 3 different setups, none of
Hi,
Russ Allbery:
How difficult would it be, for the sake of compatibility if nothing
else, to teach su not to create a new PAM session when it doesn't
already run within one?
You don't want to do that in general since that defeats the primary
purpose of su: creating a new session as a
Hi,
Thorsten Glaser:
• no /etc/init.d/$foo (to tabcomplete, no less!) any more
Why you think these are going away? They're not, not any time soon;
and you can still use them when you're running systemd (assuming that you
include the LSB functions, like init.d/skeleton has been advising you for
Hi,
Thorsten Glaser:
OK. But who says this is to stay? The systemd developers are
hostile towards legacy stuff in a really intricate way. Take
not jornal here but something else as example: they support
running both ntpd and their own thing, to sweeten the deal
now, but plan on dropping ntpd
Hi,
Thorsten Glaser:
There’s not really a line between them, you know. (But it was
nice to have a published list of those people who maybe could
accidentally be hit by a tactical small-bus…)
I hereby apologize to the list at large for replying to your earlier emails.
*PLONK*.
--
--
* Matthias Urlichs matth...@urlichs.de, 2014-05-14, 17:30:
In fact, rescuing a system becomes way easier even without learning any
magic tools. For example, when bootup breaks you get dropped into a
rescue shell, same as before. The difference with systemd is that as
soon as you manage to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/14/2014 12:07 PM, Jakub Wilk wrote:
* Matthias Urlichs matth...@urlichs.de, 2014-05-14, 17:30:
In fact, rescuing a system becomes way easier even without learning
any magic tools. For example, when bootup breaks you get dropped
into a
Matthias Urlichs matth...@urlichs.de writes:
I see two cases here.
* I'm a logged-in user and use su to run … whatever.
In this case, whether it creates a new session or not doesn't matter
(because there already is one), so one more cannot add more blockage to
hibernation et al. than
Am 14.05.2014 18:30, schrieb The Wanderer:
On 05/14/2014 12:07 PM, Jakub Wilk wrote:
* Matthias Urlichs matth...@urlichs.de, 2014-05-14, 17:30:
In fact, rescuing a system becomes way easier even without learning
any magic tools. For example, when bootup breaks you get dropped
into a
On Tue, 13 May 2014 20:08:18 +0100, Adam D. Barratt
a...@adam-barratt.org.uk wrote:
adam@wheezy:~$ service tabtab
|[6/505]mh@swivel:~/transfer$ service tab tab
|.directorykarte4.png
|fotovoltaik.png lageplan.png
|karte1.png
On Tue, 13 May 2014 17:28:27 +0200, Vincent Bernat ber...@debian.org
wrote:
? 13 mai 2014 15:01 +0200, Marc Haber mh+debian-de...@zugschlus.de :
Thank you so much for volunteering to contribute to GNOME packaging and
to make it work on configurations nobody will actually ever use.
We are eagerly
On 13/05/14 20:30, Salvo Tomaselli wrote:
In data martedì 13 maggio 2014 19:42:32, David Goodenough ha scritto:
service foo action works across Linux distributions, with or without
systemd, and does the right thing.
The big shame with service is that tab completion does not work properly.
Roger Lynn ro...@rilynn.me.uk writes:
On 13/05/14 20:30, Salvo Tomaselli wrote:
In data martedì 13 maggio 2014 19:42:32, David Goodenough ha scritto:
service foo action works across Linux distributions, with or without
systemd, and does the right thing.
The big shame with service is that
On Wed, May 14, 2014 at 7:22 PM, Russ Allbery r...@debian.org wrote:
Roger Lynn ro...@rilynn.me.uk writes:
On 13/05/14 20:30, Salvo Tomaselli wrote:
In data martedì 13 maggio 2014 19:42:32, David Goodenough ha scritto:
service foo action works across Linux distributions, with or without
Jordan Metzmeier titan8...@gmail.com writes:
It's not loaded from /etc/profile by default (which would probably
throw errors with other shells since all login shells source
/etc/profile).
It is for me, via:
if [ -d /etc/profile.d ]; then
for i in /etc/profile.d/*.sh; do
if [ -r $i ];
On Mon, May 12, 2014 at 07:01:14PM -0700, Russ Allbery wrote:
Dependency-based boot, the change to /bin/sh, and UUID-based mounting were
all not drop-in replacements by that criteria.
Note that also none of them were forced on existing installations. The change
of /bin/sh to dash (which is
Hi,
Kevin Chadwick:
previously on this list Matthias Urlichs contributed:
I haven't yet seen a system where booting with init=/bin/bash works but
booting systemd in emergency mode does not.
Have you added me to a killfile?
* Am I under some sort of obligation to read each and every
Hi,
Steve Langasek:
As the maintainer of the pam package in Debian, I assure you: this is a bug
in dirmngr. System services should not (must not) call interfaces that
launch pam sessions as part of their init scripts. su is one of those
interfaces.
How difficult would it be, for the sake
Hi,
Bas Wijnen:
Sounds like those packages should conflict with each other. It isn't a reason
to uninstall anything.
If you've used aptitude for any length of time, its affinity towards
uninstalling half of your system in favor of *any* other way to resolve
a conflict should not be
Hi,
Cameron Norman:
Is it not possible to tell if the sysvinit or upstart packages were
installed manually, and give a prompt then (in addition to something like
you described) ?
In theory, yes you could discover whether a package was installed explicity
or has been pulled in as a
Le lundi 12 mai 2014 à 11:42 -0700, Steve Langasek a écrit :
As far as GDM is concerned, any bug reported with systemd-shim installed
will be ignored. The bug script should probably be updated to that
effect, BTW.
A better solution would be for you to step down as maintainer, since you
On Tue, 13 May 2014 11:31:19 +0200
Matthias Urlichs matth...@urlichs.de wrote:
Hi,
Cameron Norman:
Is it not possible to tell if the sysvinit or upstart packages were
installed manually, and give a prompt then (in addition to
something like you described) ?
In theory, yes you could
On Sun, 11 May 2014 22:34:47 -0700, Steve Langasek vor...@debian.org
wrote:
On Sun, May 11, 2014 at 09:10:21AM +0200, Marc Haber wrote:
The plain fact:
Using systemd breaks something that worked for probably a decade or longer
before however long that su is in that init script. So on what
On Mon, 12 May 2014 19:01:14 -0700, Russ Allbery r...@debian.org
wrote:
Dependency-based boot, the change to /bin/sh, and UUID-based mounting were
all not drop-in replacements by that criteria.
The update to the first Debian stable release running systemd will
most probably be the most painful
On Mon, 12 May 2014 13:58:31 +0200, Josselin Mouette j...@debian.org
wrote:
Le lundi 12 mai 2014 à 12:16 +0200, Andrew Shadura a écrit :
As far as GDM is concerned, any bug reported with systemd-shim installed
will be ignored. The bug script should probably be updated to that
effect, BTW.
On Mon, 12 May 2014 13:35:15 +0200, Tollef Fog Heen tfh...@err.no
wrote:
On 12 May 2014 11:54, Josselin Mouette j...@debian.org wrote:
Systemd is the default init system for jessie, and it should be listed
as the first alternative. The fact that an alternative codepath exists
for users with
2014-05-13 15:01 GMT+02:00 Marc Haber mh+debian-de...@zugschlus.de:
On Mon, 12 May 2014 13:58:31 +0200, Josselin Mouette j...@debian.org
wrote:
Le lundi 12 mai 2014 à 12:16 +0200, Andrew Shadura a écrit :
As far as GDM is concerned, any bug reported with systemd-shim installed
will be
On Mon, 12 May 2014 21:16:49 +0200, Bas Wijnen wij...@debian.org
wrote:
I, as a user, did not expect to be moved over to systemd, and given the
discussions about it and the older TC decisions about network manager getting
its dependencies right (to stop forcing all of gnome onto the user's
Le mardi 13 mai 2014 à 15:01 +0200, Marc Haber a écrit :
This sort of behavior is precisely why many users are migrating away
from Debian.
You are entitled to think that users make decisions on the alleged
behavior of people they never heard of.
My opinion is that many users are migrating
On Tue, 13 May 2014, Josselin Mouette wrote:
My opinion is that many users are migrating away from Debian because we
are unable to make decisions on important technical topics and leave
them with 3 different setups, none of which actually work, instead of
providing one that is correctly
❦ 13 mai 2014 15:01 +0200, Marc Haber mh+debian-de...@zugschlus.de :
Thank you so much for volunteering to contribute to GNOME packaging and
to make it work on configurations nobody will actually ever use.
We are eagerly waiting for your patches.
This sort of behavior is precisely why many
On Mon, May 12, 2014 at 07:01:14PM -0700, Russ Allbery wrote:
Dependency-based boot, the change to /bin/sh, and UUID-based mounting
were all not drop-in replacements by that criteria.
Note that also none of them were forced on existing installations. The
change of /bin/sh to dash (which is
How difficult would it be, for the sake of compatibility if nothing
else, to teach su not to create a new PAM session when it doesn't
already run within one?
You don't want to do that in general since that defeats the primary
purpose of su: creating a new session as a different user.
It's
Matthias Urlichs matth...@urlichs.de wrote:
In theory, yes you could discover whether a package was installed
explicity or has been pulled in as a dependency.
In practice, however, a normal Debian installation marks each and
every package as being installed explicitly.
? huh ? This has
The update to the first Debian stable release running systemd will most
probably be the most painful update Debian has ever had since switching
to glibc (which was well before I started using Linux).
I highly doubt it.
We would be wise to make the last non-systemd release an LTS one so that
On Mon, 12 May 2014, Tollef Fog Heen wrote:
]] Andrew Shadura
This sort of behaviour is precisely why so many people not only
dislike systemd, but also it's maintainers.
Are you aware that Joss isn't a systemd maintainer? (He's one of the
GNOME maintainers.)
There’s not really a line
Apologies for the last few mangled messages with bad attributions or
character sets. Emacs 24 didn't like its header and body separator
overridden (it thought my separator was a continuation line of a previous
header), which caused subtle problems with mail sending until I figured
out what was
Thorsten Glaser t...@mirbsd.org writes:
On Mon, 12 May 2014, Tollef Fog Heen wrote:
Are you aware that Joss isn't a systemd maintainer? (He's one of the
GNOME maintainers.)
There’s not really a line between them, you know. (But it was nice to
have a published list of those people who maybe
Hi,
Le 13/05/2014 17:36, Russ Allbery a écrit :
Right, which I've been arguing for already in this thread. I don't think
we should force this on upgrades. There should be a prompt and an
opportunity to not change init systems.
Instead of or in addition to such prompting, I expect this
On Tue, May 13, 2014 18:03, Russ Allbery wrote:
The update to the first Debian stable release running systemd will most
probably be the most painful update Debian has ever had since switching
to glibc (which was well before I started using Linux).
I highly doubt it.
We would be wise to
* Thorsten Glaser (t...@mirbsd.org) wrote:
(But it was
nice to have a published list of those people who maybe could
accidentally be hit by a tactical small-bus…)
These comments are not necessary nor appropriate, ever.
Thanks,
Stephen
signature.asc
Description:
On Tue, 13 May 2014, Thorsten Glaser wrote:
(But it was nice to have a published list of those people who maybe
could accidentally be hit by a tactical small-bus…)
This is absolutely inappropriate and has no place on a Debian mailing
list or anywhere else. Please retract this statement.
--
Thibaut Paumard thib...@debian.org (2014-05-13):
Le 13/05/2014 17:36, Russ Allbery a écrit :
Right, which I've been arguing for already in this thread. I don't think
we should force this on upgrades. There should be a prompt and an
opportunity to not change init systems.
Instead of or
Didier 'OdyX' Raboud dixit:
Le mardi, 13 mai 2014, 16.25:31 Thorsten Glaser a écrit :
On Mon, 12 May 2014, Tollef Fog Heen wrote:
Are you aware that Joss isn't a systemd maintainer? (He's one of
the GNOME maintainers.)
There’s not really a line between them, you know. (But it was
On
Cyril Brulebois dixit:
The sad thing is: almost nobody reads the release notes.
Many people run testing or unstable, so there are no “release”s
to have notes for, either… (but yes, even those who run stable
don’t).
bye,
//mirabilos
--
“When udev happened I wrote mdev.”
-- Rob Landley
Thijs Kinkhorst dixit:
On Tue, May 13, 2014 18:03, Russ Allbery wrote:
You're aware, right, that my primary background is with enterprise use,
and I've been doing large-site systems administration for twenty years?
systemd is a godsend with basically no downside for our enterprise use
[…]
I
Thorsten Glaser t...@mirbsd.org (2014-05-13):
(But it was nice to have a published list of those people who maybe
could accidentally be hit by a tactical small-bus…)
That's absolutely shocking and intolerable.
KiBi.
signature.asc
Description: Digital signature
Thorsten Glaser t...@mirbsd.de writes:
Yes, there were issues with e.g. grub1 to grub2, but do you honestly
think that sysadmins in a medium-sized company will cope with these?
• no /etc/init.d/$foo (to tabcomplete, no less!) any more
I've been telling people to stop using this for years.
On Tuesday 13 May 2014 11:06:10 Russ Allbery wrote:
Thorsten Glaser t...@mirbsd.de writes:
Yes, there were issues with e.g. grub1 to grub2, but do you honestly
think that sysadmins in a medium-sized company will cope with these?
• no /etc/init.d/$foo (to tabcomplete, no less!) any more
On Tue, May 13, 2014 at 07:42:32PM +0100, David Goodenough wrote:
The big shame with service is that tab completion does not work properly.
If I use /etc/init.d/ then tab tells me what is there and spells it right.
Sounds like maybe you need a better shell.
--
To UNSUBSCRIBE, email to
On Tue, 2014-05-13 at 19:42 +0100, David Goodenough wrote:
On Tuesday 13 May 2014 11:06:10 Russ Allbery wrote:
service foo action works across Linux distributions, with or without
systemd, and does the right thing.
The big shame with service is that tab completion does not work properly.
In
In data martedì 13 maggio 2014 19:42:32, David Goodenough ha scritto:
service foo action works across Linux distributions, with or without
systemd, and does the right thing.
The big shame with service is that tab completion does not work properly.
If I use /etc/init.d/ then tab tells me
Am 13.05.2014 20:42, schrieb David Goodenough:
On Tuesday 13 May 2014 11:06:10 Russ Allbery wrote:
service foo action works across Linux distributions, with or without
systemd, and does the right thing.
The big shame with service is that tab completion does not work properly.
If I use
On Tue, May 13, 2014 at 07:42:32PM +0100, David Goodenough wrote:
service foo action works across Linux distributions, with or without
systemd, and does the right thing.
The big shame with service is that tab completion does not work properly.
If I use /etc/init.d/ then tab tells me what is
Op dinsdag 13 mei 2014 19:36:35 schreef Thorsten Glaser:
Thijs Kinkhorst dixit:
I could not agree more. In our enterprise environment, I have no
expectation at all that systemd will cause us significant trouble on
upgrades. Our troubles have centered things like grub1 to grub2 or,
Yes,
* Russ Allbery r...@debian.org [140513 18:21]:
We would be wise to make the last non-systemd release an LTS one so that
enterprise users can stay on that release until the systems these
installations run are retired.
You're aware, right, that my primary background is with enterprise use,
Le 13/05/2014 19:38, Thorsten Glaser a écrit :
Cyril Brulebois dixit:
The sad thing is: almost nobody reads the release notes.
Many people run testing or unstable, so there are no “release”s
to have notes for, either… (but yes, even those who run stable
don’t).
People who run testing or
Russ Allbery dixit:
• no /etc/init.d/$foo (to tabcomplete, no less!) any more
I've been telling people to stop using this for years. You should stop
using this too, regardless of what init system you're using, since it
doesn't sanitize environment variables. You leak all kinds of crap from
Thibaut Paumard dixit:
People who run testing or unstable should be prepared to deal with
occasional breakages.
With occasional *temporary* breakages, such as packages disappearing
(in testing) or needing to be set on “hold” temporarily, yes.
With the init system suddenly be swapped out under
On Tue, May 13, 2014 at 08:23:55PM +, Thorsten Glaser wrote:
service foo action works across Linux distributions, with or without
systemd, and does the right thing.
It doesn’t work on lenny, and (unless service /etc/init.d/foo is
allowed) does not tabcomplete well (in all scenarios).
On Tue, 13 May 2014 18:57:03 +0200, Thijs Kinkhorst wrote:
I could not agree more. In our enterprise environment, I have no
expectation at all that systemd will cause us significant trouble on
upgrades. Our troubles have centered things like grub1 to grub2 or,
indeed, new PHP and Perl
Steve Langasek dixit:
On Tue, May 13, 2014 at 08:23:55PM +, Thorsten Glaser wrote:
service foo action works across Linux distributions, with or without
systemd, and does the right thing.
It doesn’t work on lenny, and (unless service /etc/init.d/foo is
allowed) does not tabcomplete well
On Tuesday 13 May 2014 21:09:14 Salvo Tomaselli wrote:
In data martedì 13 maggio 2014 19:42:32, David Goodenough ha scritto:
service foo action works across Linux distributions, with or without
systemd, and does the right thing.
The big shame with service is that tab completion does
Le mardi 13 mai 2014 à 22:46 +0100, David Goodenough a écrit :
Does bash-completion work when the command is sudo not service?
Yes.
--
.''`. Josselin Mouette
: :' :
`. `'
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Am 13.05.2014 23:46, schrieb David Goodenough:
Does bash-completion work when the command is sudo not service? Never seems
to for me. I never log in as root, I always do root things using sudo.
Sure, works fine.
--
Why is it that all of the instruments seeking intelligent life in the
]] Steve Langasek
The maintainer may disagree, in which case one is free to escalate it
to the release team precisely as Tollef has suggested. But there's
nothing inappropriate about having this discussion directly with the
maintainer first.
Right, and I didn't complain about the initial
Le 11 mai 2014 23:06, Michael Biebl bi...@debian.org a écrit :
Am 11.05.2014 19:37, schrieb Helmut Grohne:
I trust you to be technically right on this. Still the number of
packages getting this wrong is stunning[1]. Therefore I'd argue that
[1]
Le dimanche 11 mai 2014 à 15:53 +0200, Marc Haber a écrit :
On Sun, 11 May 2014 13:47:39 +0200, Laurent Bigonville
bi...@debian.org wrote:
For other distributions (and other Unix based OS) most of (all?) the
initscripts are already different anyway.
Is it right to force that?
No, this is
Le vendredi 09 mai 2014 à 21:13 +0200, Bas Wijnen a écrit :
I think it would be good for libpam-systemd to list systemd-shim first.
Certainly not.
Systemd is the default init system for jessie, and it should be listed
as the first alternative. The fact that an alternative codepath exists
for
Hello,
On 12 May 2014 11:54, Josselin Mouette j...@debian.org wrote:
Systemd is the default init system for jessie, and it should be listed
as the first alternative. The fact that an alternative codepath exists
for users with specific needs is nice for them, but it is not what we
should focus
Le Mon, May 12, 2014 at 12:16:48PM +0200, Andrew Shadura a écrit :
On 12 May 2014 11:54, Josselin Mouette j...@debian.org wrote:
Systemd is the default init system for jessie, and it should be listed
as the first alternative. The fact that an alternative codepath exists
for users with
On Sun, 11 May 2014, Marc Haber wrote:
On Sat, 10 May 2014 22:13:01 +0200, Matthias Urlichs
matth...@urlichs.de wrote:
I also would not expect an end user to add su foo -c /do/whatever to
/etc/rc.local. Your opinion may differ, that's OK.
Especially people who are not as Debian-centric as
On Fri, 9 May 2014, Steve Langasek wrote:
ii systemd 204-10
ii systemd-sysv 204-10
You can purge them. Install sysvinit-core at the same time.
This is unconstructive advice.
No, it is not, for someone who wants systemd gone
At Mon, 12 May 2014 12:16:48 +0200,
Andrew Shadura wrote:
On 12 May 2014 11:54, Josselin Mouette j...@debian.org wrote:
Systemd is the default init system for jessie, and it should be listed
as the first alternative. The fact that an alternative codepath exists
for users with specific
On Sat, 10 May 2014, Bas Wijnen wrote:
So please get dirmngr fixed instead of blaming systemd/logind.
This is the part you should _NEVER_ do. It is YOUR responsibitiliy, as a
maintainer (you are the maintainer, right?), to make sure that a bug that is
reported in the wrong place gets sent
]] Andrew Shadura
Hello,
On 12 May 2014 11:54, Josselin Mouette j...@debian.org wrote:
Systemd is the default init system for jessie, and it should be listed
as the first alternative. The fact that an alternative codepath exists
for users with specific needs is nice for them, but it is
Hello,
On 12 May 2014 13:35, Tollef Fog Heen tfh...@err.no wrote:
This sort of behaviour is precisely why so many people not only
dislike systemd, but also it's maintainers.
Are you aware that Joss isn't a systemd maintainer? (He's one of the
GNOME maintainers.)
I am. I never claimed he
Le lundi 12 mai 2014 à 13:26 +0200, Thorsten Glaser a écrit :
What *is* a “desktop seat manager”? I’d not want it on servers
(and some coworkers are even running N-M on some of them…), and
Linux desktops (and nōn-Linux ones) have not needed those until
now either. So, I (still) question this
Le lundi 12 mai 2014 à 12:16 +0200, Andrew Shadura a écrit :
As far as GDM is concerned, any bug reported with systemd-shim installed
will be ignored. The bug script should probably be updated to that
effect, BTW.
This sort of behaviour is precisely why so many people not only
dislike
[..] configurations nobody will actually ever use.
There you are plainly *wrong*... unless you on purpose make it
to not work so that nobody can use it ... which I don't hope!!!
Norbert
PREINING, Norbert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/12/2014 08:52 AM, Norbert Preining wrote:
[..] configurations nobody will actually ever use.
There you are plainly *wrong*... unless you on purpose make it to not
work so that nobody can use it ... which I don't hope!!!
Not to mention
On Mon, May 12, 2014 at 11:54:43AM +0200, Josselin Mouette wrote:
Systemd is the default init system for jessie, and it should be listed
as the first alternative.
Can you please explain what is wrong with my reasoning?
A default is only relevant at the time the functionality is first
On 2014-05-12, Bas Wijnen wij...@debian.org wrote:
A default is only relevant at the time the functionality is first installed.
After that, whatever was installed should stay until the user requests to
change it (or there is a technical reason that it can no longer be installed).
In the case
1 - 100 of 241 matches
Mail list logo
