On Sat, Jun 27, 2015 at 10:02 PM, Kay Sievers k...@vrfy.org wrote:
On Fri, May 22, 2015 at 3:42 PM, Bastien Nocera had...@hadess.net wrote:
It's moved to the iio-sensor-proxy D-Bus service.
---
.gitignore | 1 -
Makefile.am| 15 --
dear devel
could we please have journalctl -o cat not loose coloring
the output feature?
many thanks
P
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system
I just installed debian 8.1, on the whole my reaction is mixed, one
thing however really pisses me off more than any other
5.6.1. Stricter handling of failing mounts during boot
On 06/29/2015 02:08 PM, jon wrote:
https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system
I just installed debian 8.1, on the whole my reaction is mixed, one
thing however really pisses me off more than any other
5.6.1. Stricter
On Mon, 2015-06-29 at 14:21 +, Jóhann B. Guðmundsson wrote:
On 06/29/2015 02:08 PM, jon wrote:
https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system
I just installed debian 8.1, on the whole my reaction is mixed, one
On Jun 29, 2015 16:58, Lesley Kimmel ljkimme...@hotmail.com wrote:
Jonathan;
Thanks for the background and information. Since you clearly seem to have
a grasp of systemd please humour me with a few more questions (some of them
slightly ignorant):
a) Why are PID bad?
b) Why are lock files
В Mon, 29 Jun 2015 08:58:11 -0500
Lesley Kimmel ljkimme...@hotmail.com пишет:
Jonathan;
Thanks for the background and information. Since you clearly seem to have a
grasp of systemd please humour me with a few more questions (some of them
slightly ignorant):
a) Why are PID bad?
PID
В Mon, 29 Jun 2015 14:21:44 +
Jóhann B. Guðmundsson johan...@gmail.com пишет:
On 06/29/2015 02:08 PM, jon wrote:
https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system
I just installed debian 8.1, on the whole my
On Mon, 29.06.15 15:08, jon (j...@jonshouse.co.uk) wrote:
https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system
I just installed debian 8.1, on the whole my reaction is mixed, one
thing however really pisses me off more than any
On 06/29/2015 04:17 PM, Andrei Borzenkov wrote:
No. systemd changed interpretation of well established configurations
in incompatible way. There is no way to retain existing behavior. It is
far from recommends - it is my way or highway.
Not following which changed interpretation of well
On Mon, 2015-06-29 at 17:54 +0200, Reindl Harald wrote:
Am 29.06.2015 um 17:01 schrieb jon:
On Mon, 2015-06-29 at 14:21 +, Jóhann B. Guðmundsson wrote:
On 06/29/2015 02:08 PM, jon wrote:
On 06/29/2015 03:01 PM, jon wrote:
On Mon, 2015-06-29 at 14:21 +, Jóhann B. Guðmundsson wrote:
On 06/29/2015 02:08 PM, jon wrote:
https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system
I just installed debian 8.1, on the
On Mon, 29.06.15 16:01, jon (j...@jonshouse.co.uk) wrote:
On Mon, 2015-06-29 at 14:21 +, Jóhann B. Guðmundsson wrote:
On 06/29/2015 02:08 PM, jon wrote:
https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system
I just
On Mon, 29.06.15 19:17, Andrei Borzenkov (arvidj...@gmail.com) wrote:
The systemd community only recommends what downstream consumers of it
should do
No. systemd changed interpretation of well established configurations
in incompatible way. There is no way to retain existing behavior. It
you have a mountpoint in /etc/fstab and don't care if it don't get
mounted at boot and instead data get written into the folder instead the
correct filesystem?
You are making assumptions !
no
Not everyone uses linux in the same way. I have a number of servers that
are RAID, but
I was hoping that
getent hosts containername
would work, just like
getent hosts hostname
where hostname can be anything else in the hosts: field in nsswitch.conf. But
no such luck.
The containername does get resolved correctly in other cases, e.g. when
pinging it.
Not knowing
On Mon, 2015-06-29 at 20:18 +0200, Lennart Poettering wrote:
On Mon, 29.06.15 16:19, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:
Who writes/maintains the code that parses nofail in /etc/fstab ?
Who writes/maintains the typical system boot code (whatever has replaced
rc.sysinit) ?
On Mon, 29.06.15 18:50, jon (j...@jonshouse.co.uk) wrote:
and why don't you just add nofail
it's way shorter then write a ton of emails
Yes, this I have in fact done. I have the right to complain though
!
You don't have the right to do this on this mailing list though.
Please do it
On Mon, 29.06.15 19:20, jon (j...@jonshouse.co.uk) wrote:
Reversing the logic by adding a mustexist fstab option and keeping the
default behaviour would fix it.
At this time, systemd has been working this way for 5y now. The
behaviour it implements is also the right behaviour I am sure, and
On Mon, 29.06.15 16:19, Jóhann B. Guðmundsson (johan...@gmail.com) wrote:
Who writes/maintains the code that parses nofail in /etc/fstab ?
Who writes/maintains the typical system boot code (whatever has replaced
rc.sysinit) ?
I suspect the answer to both is the systemd maintainers, in which
On Mon, 2015-06-29 at 18:45 +0200, Lennart Poettering wrote:
On Mon, 29.06.15 19:17, Andrei Borzenkov (arvidj...@gmail.com) wrote:
The systemd community only recommends what downstream consumers of it
should do
No. systemd changed interpretation of well established configurations
On Jun 29, 2015, at 10:32, Johannes Ernst johannes.er...@gmail.com wrote:
I was hoping that
getent hosts containername
would work, just like
getent hosts hostname
where hostname can be anything else in the hosts: field in nsswitch.conf.
But no such luck.
The containername
On Mon, 29.06.15 20:36, jon (j...@jonshouse.co.uk) wrote:
What for example is the technical reason why the nofail logic could
not have been inverted ? I have not heard any technical argument that is
compelling as to why this could not have worked the other way up and
default behaviour not
A mount on /var is clearly essential, as area pretty much all mounts
below /var, though there might be exceptions. Mounts in /srv are
essential, too. Mounts which are often non-essential are external
media, USB sticks and suchlike. However, those are probably usually
handled via something
Am 29.06.2015 um 21:36 schrieb jon:
On Mon, 2015-06-29 at 20:50 +0200, Lennart Poettering wrote:
On Mon, 29.06.15 19:20, jon (j...@jonshouse.co.uk) wrote:
Reversing the logic by adding a mustexist fstab option and keeping the
default behaviour would fix it.
At this time, systemd has been
Am 29.06.2015 um 17:01 schrieb jon:
On Mon, 2015-06-29 at 14:21 +, Jóhann B. Guðmundsson wrote:
On 06/29/2015 02:08 PM, jon wrote:
https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#systemd-upgrade-default-init-system
I just installed debian 8.1, on the
Am 29.06.2015 um 18:50 schrieb jon:
On Mon, 2015-06-29 at 17:54 +0200, Reindl Harald wrote:
Am 29.06.2015 um 17:01 schrieb jon:
On Mon, 2015-06-29 at 14:21 +, Jóhann B. Guðmundsson wrote:
On 06/29/2015 02:08 PM, jon wrote:
On Mon, 29.06.15 20:36, jon (j...@jonshouse.co.uk) wrote:
On Mon, 2015-06-29 at 20:50 +0200, Lennart Poettering wrote:
On Mon, 29.06.15 19:20, jon (j...@jonshouse.co.uk) wrote:
Reversing the logic by adding a mustexist fstab option and keeping the
default behaviour would fix it.
Am 29.06.2015 um 15:58 schrieb Lesley Kimmel:
Jonathan;
Thanks for the background and information. Since you clearly seem to
have a grasp of systemd please humour me with a few more questions (some
of them slightly ignorant):
a) Why are PID bad?
what are they good for when the supervisor
Hello,
Since git 2.3, there have been a number of new fsck options added which
produce issues when I clone the repository
git://anongit.freedesktop.org/systemd/systemd
$ git fsck --full
Checking object directories: 100% (256/256), done.
warning in tag 2a440962bc639c674cef95f5dee6f184c5daf170:
On Mon, 2015-06-29 at 22:16 +0200, Reindl Harald wrote:
Am 29.06.2015 um 21:36 schrieb jon:
On Mon, 2015-06-29 at 20:50 +0200, Lennart Poettering wrote:
On Mon, 29.06.15 19:20, jon (j...@jonshouse.co.uk) wrote:
Reversing the logic by adding a mustexist fstab option and keeping the
On 06/28/2015 07:21 PM, Reindl Harald wrote:
Am 28.06.2015 um 19:02 schrieb Francis Moreau:
On 06/28/2015 01:01 PM, Reindl Harald wrote:
Am 28.06.2015 um 12:00 schrieb Francis Moreau:
Hello,
For services with Type=Forking, I'm wondering if systemd proceeds
starting follow-up units
On Mon, Jun 29, 2015 at 11:01 AM, Francis Moreau francis.m...@gmail.com wrote:
On 06/28/2015 07:21 PM, Reindl Harald wrote:
Am 28.06.2015 um 19:02 schrieb Francis Moreau:
On 06/28/2015 01:01 PM, Reindl Harald wrote:
Am 28.06.2015 um 12:00 schrieb Francis Moreau:
Hello,
For services with
Patchset imported to github.
To create a pull request, one of the main developers has to initiate one via:
https://github.com/systemd/systemd/compare/master...systemd-mailing-devs:1435563731-465-1-git-send-email-kraxel%40redhat.com
--
Generated by https://github.com/haraldh/mail2git
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
src/login/71-seat.rules.in | 6 ++
1 file changed, 6 insertions(+)
diff --git a/src/login/71-seat.rules.in b/src/login/71-seat.rules.in
index ab7b66f..270da71 100644
--- a/src/login/71-seat.rules.in
+++ b/src/login/71-seat.rules.in
@@ -17,6
On 06/28/2015 07:35 PM, Andrei Borzenkov wrote:
В Sun, 28 Jun 2015 19:02:57 +0200
Francis Moreau francis.m...@gmail.com пишет:
On 06/28/2015 01:01 PM, Reindl Harald wrote:
Am 28.06.2015 um 12:00 schrieb Francis Moreau:
Hello,
For services with Type=Forking, I'm wondering if systemd
On Mon, Jun 29, 2015 at 10:58 AM, Lesley Kimmel ljkimme...@hotmail.com wrote:
Jonathan;
Thanks for the background and information. Since you clearly seem to have a
grasp of systemd please humour me with a few more questions (some of them
slightly ignorant):
a) Why are PID bad?
Because they
On Mon, Jun 29, 2015 at 11:21 PM, Liam R. Howlett
liam.howl...@windriver.com wrote:
Hello,
Since git 2.3, there have been a number of new fsck options added which
produce issues when I clone the repository
git://anongit.freedesktop.org/systemd/systemd
$ git fsck --full
Checking object
On Mon, 2015-06-29 at 20:40 +0200, Lennart Poettering wrote:
On Mon, 29.06.15 18:50, jon (j...@jonshouse.co.uk) wrote:
and why don't you just add nofail
it's way shorter then write a ton of emails
Yes, this I have in fact done. I have the right to complain though
!
You don't
On Mon, 2015-06-29 at 20:50 +0200, Lennart Poettering wrote:
On Mon, 29.06.15 19:20, jon (j...@jonshouse.co.uk) wrote:
Reversing the logic by adding a mustexist fstab option and keeping the
default behaviour would fix it.
At this time, systemd has been working this way for 5y now. The
40 matches
Mail list logo
