systemd-journalctl and systemd-systemctl were also renamed to get more
convenient ...
(But hey, I don't really know what external stuff uses "-.slice" and
"-.mount" ...)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.free
On Thu, Jan 16, 2014 at 8:59 AM, Holger Schurig wrote:
> systemd-journalctl and systemd-systemctl were also renamed to get more
> convenient ...
Symlinks are cheap to create, if compat for these rather exotic things
is needed.
systemctl was always systemctl, but loginctl we also have renamed.
>
On Thu, Jan 16, 2014 at 06:01:58AM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Sun, Jan 12, 2014 at 02:07:32AM +0100, Djalal Harouni wrote:
> > On Sat, Jan 11, 2014 at 10:26:13PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> > > On Fri, Jan 03, 2014 at 02:19:19PM +0100, Djalal Harouni wrote:
> > >
Oh, I confused that with the old /etc/systemd/systemd-journald.conf
file, which was renamed.
Kay, I only meant to special case the "/", e.g. let
home-kay-data.mount be it like it is, but rename "-" to "root", so
that it is "root.mount" and "root.slice".
On Thu, Jan 16, 2014 at 11:27:42AM +0100, Holger Schurig wrote:
> Oh, I confused that with the old /etc/systemd/systemd-journald.conf
> file, which was renamed.
>
> Kay, I only meant to special case the "/", e.g. let
> home-kay-data.mount be it like it is, but rename "-" to "root", so
> that it is
'Twas brillig, and Holger Schurig at 16/01/14 10:27 did gyre and gimble:
> Oh, I confused that with the old /etc/systemd/systemd-journald.conf
> file, which was renamed.
>
> Kay, I only meant to special case the "/", e.g. let
> home-kay-data.mount be it like it is, but rename "-" to "root", so
> t
On Jan 16, 2014 9:34 AM, "Holger Schurig" wrote:
>
> Please consider renamign "-.slice", because this sucks:
>
> # cd /lib/systemd/system
> # grep -r user@ *
> grep: invalid option -- '.'
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
>
>
> Yes, I know that I
On Sat, Jan 11, 2014 at 7:04 PM, Kay Sievers wrote:
> We got systemd git working to be able to run a full GNOME (Fedora 20)
> user session with kdbus now. Instead of dbus-daemon running and
> activating applications, they are directly started by the systemd
> --user instance now.
>
> Here is the o
'Twas brillig, and Colin Guthrie at 14/01/14 13:28 did gyre and gimble:
> 3. Some sort of kernel trigger for me today led it to run two reexecs
> quite quickly and triggered this problem randomly during runtime. This
> *might* have come in via "telinit u" instead. It doesn't appear that the
> kerne
2014/1/16 Holger Schurig :
> Chengwai,
>
>> given that kmod may not available in some distro version
>
> I'm on Debian and use my self-compiled systemd v208 with a self-made
> kmod_15.deb file. Packaging kmod is dead easy, it's a very
Fwiw, sid/jessie have a recent version of kmod:
$ apt-cache po
On Thu, 16.01.14 11:27, Holger Schurig (holgerschu...@gmail.com) wrote:
>
> Oh, I confused that with the old /etc/systemd/systemd-journald.conf
> file, which was renamed.
>
> Kay, I only meant to special case the "/", e.g. let
> home-kay-data.mount be it like it is, but rename "-" to "root", so
On Thu, 16.01.14 08:33, Holger Schurig (holgerschu...@gmail.com) wrote:
> Please consider renamign "-.slice", because this sucks:
>
> # cd /lib/systemd/system
> # grep -r user@ *
> grep: invalid option -- '.'
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
>
11.12.2013 at 15:15 Lennart Poettering wrote:
On Wed, 11.12.13 14:24, Maciej Wereski (m.were...@partner.samsung.com)
wrote:
>>+xattr = new0(char, strlen(i->argument)+1);
>>+if (!xattr)
>>+return log_oom();
>>+
>>+tmp = strv_split(i->argument, WHITESPA
On Wed, 15.01.14 20:20, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> I was a bit surprised that for mount points the dependency
> Before=local-fs.target is only added when nofail is not used.
> This seems to be a concious decision (added by Lennart in
> 155da457, and then survived all
On Thu, Jan 16, 2014 at 03:51:02PM +0100, Lennart Poettering wrote:
> On Wed, 15.01.14 20:20, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> > I was a bit surprised that for mount points the dependency
> > Before=local-fs.target is only added when nofail is not used.
> > This seems to
On Thu, 16.01.14 16:14, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> On Thu, Jan 16, 2014 at 03:51:02PM +0100, Lennart Poettering wrote:
> > On Wed, 15.01.14 20:20, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl)
> > wrote:
> >
> > > I was a bit surprised that for mount points the
On Jan 16, 2014, at 7:51 AM, Lennart Poettering wrote:
> On Wed, 15.01.14 20:20, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
>> I was a bit surprised that for mount points the dependency
>> Before=local-fs.target is only added when nofail is not used.
>> This seems to be a concious
Hi,
On 14.01.2014 16:13, Tom Gundersen wrote:
On Tue, Jan 14, 2014 at 2:15 PM, Joonas Lahtinen
wrote:
I've implemented very basic BMP support and commited it.
The custom format was there for best possible speed to be achieved when
displaying the splash, as the original use case is extremely
Hi Joonas,
On Thu, Jan 16, 2014 at 4:13 PM, Joonas Lahtinen
wrote:
> By our measurements, the original BGRX code only adds some 5 milliseconds to
> the boot time compared to no logo at all, where the BMP code adds almost 70
> milliseconds.
>
> I think the most difference comes from the fact that
On Thu, Jan 16, 2014 at 4:19 PM, Lennart Poettering
wrote:
> On Thu, 16.01.14 16:14, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
>>
>> On Thu, Jan 16, 2014 at 03:51:02PM +0100, Lennart Poettering wrote:
>> > On Wed, 15.01.14 20:20, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl)
>> >
On Mon, 13.01.14 22:58, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> Eeeh, why? This new name suggests that this libary is for systemd
> functionality. But so far it is a generic. Also, we have
> libsystemd-daemon, libsystemd-id128, etc. As a consumer of the library,
> I'd much prefer
'Twas brillig, and Chris Murphy at 16/01/14 15:34 did gyre and gimble:
>
> On Jan 16, 2014, at 8:25 AM, Kay Sievers wrote:
>
>> On Thu, Jan 16, 2014 at 4:19 PM, Lennart Poettering
>> wrote:
>>> On Thu, 16.01.14 16:14, Zbigniew Jędrzejewski-Szmek
>>> (zbys...@in.waw.pl) wrote:
>>>
O
On Jan 16, 2014, at 8:25 AM, Kay Sievers wrote:
> On Thu, Jan 16, 2014 at 4:19 PM, Lennart Poettering
> wrote:
>> On Thu, 16.01.14 16:14, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl)
>> wrote:
>>
>>>
>>> On Thu, Jan 16, 2014 at 03:51:02PM +0100, Lennart Poettering wrote:
On Wed, 15.0
В Thu, 16 Jan 2014 16:04:34 +
Colin Guthrie пишет:
> >
> > Although with faster boot times, a device in fstab not existing is
> > probably increasingly common. What about splitting the scheduling of
> > .mount jobs such that /sysroot happens early, and everything else
> > listed in fstab hap
On Tue, 14.01.14 15:26, Umut Tezduyar Lindskog (umut.tezdu...@axis.com) wrote:
> From: Umut Tezduyar Lindskog
>
> ---
> README |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/README b/README
> index a1058c5..6fcab4f 100644
> --- a/README
> +++ b/README
> @@ -63,7
On Thu, Jan 16, 2014 at 04:41:48PM +0100, Lennart Poettering wrote:
> On Mon, 13.01.14 22:58, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> > Eeeh, why? This new name suggests that this libary is for systemd
> > functionality. But so far it is a generic. Also, we have
> > libsystemd-d
On Thu, Jan 16, 2014 at 5:31 PM, Michael Biebl wrote:
> 2014/1/16 Lennart Poettering :
>> So I am pretty sure libsystemd-id128, libsystemd-login,
>> libsystemd-journal should just end up in a single libsystemd.so together
>> with the event loop, the bus, the asyncns stuff and more. All this
>> fun
2014/1/16 Lennart Poettering :
> So I am pretty sure libsystemd-id128, libsystemd-login,
> libsystemd-journal should just end up in a single libsystemd.so together
> with the event loop, the bus, the asyncns stuff and more. All this
> functinality requires each other, and should nto pull in its own
2014/1/16 Zbigniew Jędrzejewski-Szmek :
> I am also a bit worried about so-bumps: currently we have very nice backwards
> compatibility, without any API removals. -daemon, -id128, -journal, -login
> are all still .so.0. But libsystemd-bus (libsystemd now) is much harder to
> keep this way, among ot
On Thu, 16.01.14 17:31, Michael Biebl (mbi...@gmail.com) wrote:
> 2014/1/16 Lennart Poettering :
> > So I am pretty sure libsystemd-id128, libsystemd-login,
> > libsystemd-journal should just end up in a single libsystemd.so together
> > with the event loop, the bus, the asyncns stuff and more. Al
On Mon, 06.01.14 03:35, Tom Gundersen (tome...@kemper.freedesktop.org) wrote:
> +lease->dns = new0(struct in_addr*, len / 4 + 1);
> +if (!lease->dns)
> +return -ENOMEM;
> +
> +for (i = 0; i < le
On Thu, 16.01.14 17:24, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> > There are some exceptions to this though. For example, I am unsure about
> > libsystemd-daemon: it's relatively easy to maintain this in its own lib,
> > sicne so far it actually doesn't use any of the shared code,
On Thu, 16.01.14 17:33, Michael Biebl (mbi...@gmail.com) wrote:
>
> 2014/1/16 Zbigniew Jędrzejewski-Szmek :
> > I am also a bit worried about so-bumps: currently we have very nice
> > backwards
> > compatibility, without any API removals. -daemon, -id128, -journal, -login
> > are all still .so.0
On Sun, 12.01.14 06:32, Tom Gundersen (tome...@kemper.freedesktop.org) wrote:
> +r = mkdir_safe_label("/run/systemd/network", 0755, 0, 0);
> +if (r < 0)
> +return r;
> +
> +r = fopen_temporary("/run/systemd/network/resolv.conf", &f,
> &temp_path);
> +
On 16/01/14 15:41, Lennart Poettering wrote:
> There are some exceptions to this though. For example, I am unsure about
> libsystemd-daemon: it's relatively easy to maintain this in its own lib,
> sicne so far it actually doesn't use any of the shared code, because
> its' embeddable. But then agaiu
On Thu, 16.01.14 18:27, Michael Biebl (mbi...@gmail.com) wrote:
>
> 2014/1/16 Lennart Poettering :
> > On Thu, 16.01.14 17:33, Michael Biebl (mbi...@gmail.com) wrote:
> >
> >>
> >> 2014/1/16 Zbigniew Jędrzejewski-Szmek :
> >> > I am also a bit worried about so-bumps: currently we have very nice
2014/1/16 Lennart Poettering :
> On Thu, 16.01.14 17:33, Michael Biebl (mbi...@gmail.com) wrote:
>
>>
>> 2014/1/16 Zbigniew Jędrzejewski-Szmek :
>> > I am also a bit worried about so-bumps: currently we have very nice
>> > backwards
>> > compatibility, without any API removals. -daemon, -id128, -j
On Thu, 16.01.14 17:19, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote:
>
> On 16/01/14 15:41, Lennart Poettering wrote:
> > There are some exceptions to this though. For example, I am unsure about
> > libsystemd-daemon: it's relatively easy to maintain this in its own lib,
> > sicne so fa
2014/1/16 Lennart Poettering :
> On Thu, 16.01.14 18:27, Michael Biebl (mbi...@gmail.com) wrote:
>
>>
>> 2014/1/16 Lennart Poettering :
>> > On Thu, 16.01.14 17:33, Michael Biebl (mbi...@gmail.com) wrote:
>> >
>> >>
>> >> 2014/1/16 Zbigniew Jędrzejewski-Szmek :
>> >> > I am also a bit worried about
On Thu, Jan 16, 2014 at 7:00 PM, Michael Biebl wrote:
> 2014/1/16 Lennart Poettering :
>> Well, it can certainly continue to use and build against the old version
>> for a while, no?
>
> We'd have to make pre-systemd-209 and systemd-209 packages
> co-installable (different source package names et
2014/1/16 Kay Sievers :
> On Thu, Jan 16, 2014 at 7:00 PM, Michael Biebl wrote:
>> 2014/1/16 Lennart Poettering :
>
>>> Well, it can certainly continue to use and build against the old version
>>> for a while, no?
>>
>> We'd have to make pre-systemd-209 and systemd-209 packages
>> co-installable (
On Thu, Jan 16, 2014 at 5:35 PM, Lennart Poettering
wrote:
> On Mon, 06.01.14 03:35, Tom Gundersen (tome...@kemper.freedesktop.org) wrote:
>
>> +lease->dns = new0(struct in_addr*, len / 4 + 1);
>> +if (!lease->dns)
>> +
On Thu, Jan 16, 2014 at 6:13 PM, Lennart Poettering
wrote:
> On Sun, 12.01.14 06:32, Tom Gundersen (tome...@kemper.freedesktop.org) wrote:
>
>> +r = mkdir_safe_label("/run/systemd/network", 0755, 0, 0);
>> +if (r < 0)
>> +return r;
>> +
>> +r = fopen_tempora
Due to anti-magic, a recent update horribly broke the system's ability to do
further updates. This is resolved by regression to a prior Btrfs snapshot, once
updated it works fine. But that's a two week old snapshot. I don't need the
broken rootfs but I want to keep the journal for those two wee
Chris Murphy schrieb:
> Due to anti-magic, a recent update horribly broke the system's ability to
> do further updates. This is resolved by regression to a prior Btrfs
> snapshot, once updated it works fine. But that's a two week old snapshot.
> I don't need the broken rootfs but I want to keep
On Jan 16, 2014, at 1:58 PM, Kai Krakow wrote:
> Chris Murphy schrieb:
>
>> Due to anti-magic, a recent update horribly broke the system's ability to
>> do further updates. This is resolved by regression to a prior Btrfs
>> snapshot, once updated it works fine. But that's a two week old snapsh
'Twas brillig, and Michael Biebl at 16/01/14 18:22 did gyre and gimble:
> 2014/1/16 Kay Sievers :
>> On Thu, Jan 16, 2014 at 7:00 PM, Michael Biebl wrote:
>>> 2014/1/16 Lennart Poettering :
>>
Well, it can certainly continue to use and build against the old version
for a while, no?
>>>
>
Chris Murphy schrieb:
>>> Due to anti-magic, a recent update horribly broke the system's ability
>>> to do further updates. This is resolved by regression to a prior Btrfs
>>> snapshot, once updated it works fine. But that's a two week old
>>> snapshot. I don't need the broken rootfs but I want t
Am 16.01.2014 22:15 schrieb "Chris Murphy" :
>
>
> On Jan 16, 2014, at 1:58 PM, Kai Krakow wrote:
>
> > Chris Murphy schrieb:
> >
> >> Due to anti-magic, a recent update horribly broke the system's ability
to
> >> do further updates. This is resolved by regression to a prior Btrfs
> >> snapshot,
On Jan 16, 2014, at 2:48 PM, Mirco Tischler wrote:
>
> Afair, you don't need to mount subvolumes.
>
>
I do in this case in order to make sure there's an fstab in subsequent
snapshots, that mounts the /var/log/journal subvolume. Otherwise, the booted
snapshot will end up with a new /var/log/j
Mirco Tischler schrieb:
> Am 16.01.2014 22:15 schrieb "Chris Murphy" :
>>
>>
>> On Jan 16, 2014, at 1:58 PM, Kai Krakow wrote:
>>
>> > Chris Murphy schrieb:
>> >
>> >> Due to anti-magic, a recent update horribly broke the system's ability
> to
>> >> do further updates. This is resolved by regre
Chris Murphy schrieb:
>
> On Jan 16, 2014, at 2:48 PM, Mirco Tischler wrote:
>>
>> Afair, you don't need to mount subvolumes.
>>
>>
> I do in this case in order to make sure there's an fstab in subsequent
> snapshots, that mounts the /var/log/journal subvolume. Otherwise, the
> booted snapsh
On Jan 16, 2014, at 3:44 PM, Kai Krakow wrote:
> Chris Murphy schrieb:
>
>>
>> On Jan 16, 2014, at 2:48 PM, Mirco Tischler wrote:
>>>
>>> Afair, you don't need to mount subvolumes.
>>>
>>>
>> I do in this case in order to make sure there's an fstab in subsequent
>> snapshots, that mounts
On Thu, Jan 16, 2014 at 09:36:47PM +, Colin Guthrie wrote:
> 'Twas brillig, and Michael Biebl at 16/01/14 18:22 did gyre and gimble:
> > 2014/1/16 Kay Sievers :
> >> On Thu, Jan 16, 2014 at 7:00 PM, Michael Biebl wrote:
> >>> 2014/1/16 Lennart Poettering :
> >>
> Well, it can certainly co
---
Makefile.am | 73 +--
src/libsystemd/libsystemd.sym| 87 +++--
src/login/libsystemd-login.pc.in | 2 +-
src/login/libsystemd-login.sym | 94
4 files changed, 97 inse
55 matches
Mail list logo
