Le dimanche 17 mars 2013 à 14:54 +0100, Kay Sievers a écrit :
Here is a chart:
http://people.freedesktop.org/~kay/bootchart-20130317-1434.svg
Rotating media and really cheap hardware looks very sad, and we take
like 5 times longer to boot than Windows 8.
Why does bootchart stop before
On Mon, Mar 18, 2013 at 5:06 AM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Sun, Mar 17, 2013 at 02:54:01PM +0100, Kay Sievers wrote:
Here is a chart:
http://people.freedesktop.org/~kay/bootchart-20130317-1434.svg
Rotating media and really cheap hardware looks very sad, and we
Am 18.03.2013 11:42, schrieb Kay Sievers:
On Mon, Mar 18, 2013 at 5:06 AM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Sun, Mar 17, 2013 at 02:54:01PM +0100, Kay Sievers wrote:
Here is a chart:
http://people.freedesktop.org/~kay/bootchart-20130317-1434.svg
Rotating media and
Am 17.03.2013 14:54, schrieb Kay Sievers:
Here is a chart:
http://people.freedesktop.org/~kay/bootchart-20130317-1434.svg
Rotating media and really cheap hardware looks very sad, and we take
like 5 times longer to boot than Windows 8.
Why does bootchart stop before all the *really* slow
'Twas brillig, and Kay Sievers at 18/03/13 10:42 did gyre and gimble:
On Mon, Mar 18, 2013 at 5:06 AM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Sun, Mar 17, 2013 at 02:54:01PM +0100, Kay Sievers wrote:
Here is a chart:
And make acceptance tests on such machines ;-)
- Original Message -
'Twas brillig, and Kay Sievers at 18/03/13 10:42 did gyre and gimble:
On Mon, Mar 18, 2013 at 5:06 AM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Sun, Mar 17, 2013 at 02:54:01PM +0100, Kay Sievers
On 16/03/13 15:10, Cedric BAIL wrote:
I think I am a little bit late about integrating systemd user
session in a desktop
Not really; as far as I can see, non-trivial systemd user sessions under
X11 need some more thought, and some more code.
Specifically, they need at least a change to
From: Harald Hoyer har...@redhat.com
Instead of typing the rather unusual:
$ journalctl _SYSTEMD_UNIT=sshd.service
one can now type
$ journalctl sshd.service
-- Logs begin at So 2013-02-24 20:54:44 CET, end at Mo 2013-03-18 14:01:01 CET.
--
Mär 18 07:48:26 lenovo sshd[400]: Server listening on
On Mon, Mar 18, 2013 at 02:04:39PM +0100, har...@redhat.com wrote:
From: Harald Hoyer har...@redhat.com
Instead of typing the rather unusual:
$ journalctl _SYSTEMD_UNIT=sshd.service
What about -u sshd.service? If anything, I think this should follow
the same rules as -u.
Zbyszek
Am 18.03.2013 14:08, schrieb Zbigniew Jędrzejewski-Szmek:
On Mon, Mar 18, 2013 at 02:04:39PM +0100, har...@redhat.com wrote:
From: Harald Hoyer har...@redhat.com
Instead of typing the rather unusual:
$ journalctl _SYSTEMD_UNIT=sshd.service
What about -u sshd.service? If anything, I think
The new IMPORT{builtin} and RUN{builtin} were not documented. Also make it
clear that RUN= is
really an alias for RUN{program}=.
---
man/udev.xml | 36 ++--
1 file changed, 30 insertions(+), 6 deletions(-)
diff --git a/man/udev.xml b/man/udev.xml
index
---
man/udev.xml | 43 ---
1 file changed, 36 insertions(+), 7 deletions(-)
diff --git a/man/udev.xml b/man/udev.xml
index 34b1e6f..fed8a5e 100644
--- a/man/udev.xml
+++ b/man/udev.xml
@@ -55,14 +55,12 @@
/refsect1
refsect1titleConfiguration/title
The properties will still be set in the udev database, but they will not be used
for setting the interface names. As for the other kernel commandline switches,
we allow it to be prefixed by 'rd.' to only apply in the initrd.
---
TODO | 2 --
man/udev.xml |
Distros that whish to support old kernels should set
--with-firmware-dirs=/usr/lib/firmware/updates:/usr/lib/firmware
to retain the old behaviour.
The hack which makes firmware events skip the dependency tracking is still
preserved, this would allow adding back firmware handling by a custom
On Sat, 16.03.13 18:45, Oleksii Shevchuk (alx...@gmail.com) wrote:
+int journal_file_sync(JournalFile *f) {
+if (! (f-writable f-fd = 0))
+return -1;
+
+if (fdatasync(f-fd))
+return -errno;
+
+return 0;
+}
I'd really prefer if
On Mon, 18.03.13 09:39, Frederic Crozat (fcro...@suse.com) wrote:
Le dimanche 17 mars 2013 à 14:54 +0100, Kay Sievers a écrit :
Here is a chart:
http://people.freedesktop.org/~kay/bootchart-20130317-1434.svg
Rotating media and really cheap hardware looks very sad, and we take
like 5
On Mon, Mar 18, 2013 at 2:17 PM, Tom Gundersen t...@jklm.no wrote:
The new IMPORT{builtin} and RUN{builtin} were not documented. Also make it
clear that RUN= is
really an alias for RUN{program}=.
Applied.
Thanks,
Kay
___
systemd-devel mailing list
On Mon, Mar 18, 2013 at 2:17 PM, Tom Gundersen t...@jklm.no wrote:
The 'kmod' and 'firmware' builtin's do not set any variables, so no need to
use
IMPORT. Use RUN as is already the case for the 'uaccess' builtin.
IMPORT is used to be called immediately and not be queued up to the
end of the
On Mon, Mar 18, 2013 at 2:17 PM, Tom Gundersen t...@jklm.no wrote:
---
man/udev.xml | 43 ---
1 file changed, 36 insertions(+), 7 deletions(-)
Hmm, they are documented in systemd-udevd, what's the right place?
Kay
On Mon, Mar 18, 2013 at 3:02 PM, Kay Sievers k...@vrfy.org wrote:
On Mon, Mar 18, 2013 at 2:17 PM, Tom Gundersen t...@jklm.no wrote:
---
man/udev.xml | 43 ---
1 file changed, 36 insertions(+), 7 deletions(-)
Hmm, they are documented in systemd-udevd,
On Mon, Mar 18, 2013 at 2:17 PM, Tom Gundersen t...@jklm.no wrote:
The properties will still be set in the udev database, but they will not be
used
for setting the interface names. As for the other kernel commandline switches,
we allow it to be prefixed by 'rd.' to only apply in the initrd.
On Mon, Mar 18, 2013 at 3:07 PM, Tom Gundersen t...@jklm.no wrote:
On Mon, Mar 18, 2013 at 3:02 PM, Kay Sievers k...@vrfy.org wrote:
On Mon, Mar 18, 2013 at 2:17 PM, Tom Gundersen t...@jklm.no wrote:
---
man/udev.xml | 43 ---
1 file changed, 36
On Mon, Mar 18, 2013 at 3:07 PM, Kay Sievers k...@vrfy.org wrote:
On Mon, Mar 18, 2013 at 2:17 PM, Tom Gundersen t...@jklm.no wrote:
The properties will still be set in the udev database, but they will not be
used
for setting the interface names. As for the other kernel commandline
On Mon, Mar 18, 2013 at 3:01 PM, Kay Sievers k...@vrfy.org wrote:
On Mon, Mar 18, 2013 at 2:17 PM, Tom Gundersen t...@jklm.no wrote:
The 'kmod' and 'firmware' builtin's do not set any variables, so no need to
use
IMPORT. Use RUN as is already the case for the 'uaccess' builtin.
IMPORT is
On Mon, Mar 18, 2013 at 3:24 PM, Tom Gundersen t...@jklm.no wrote:
On Mon, Mar 18, 2013 at 3:01 PM, Kay Sievers k...@vrfy.org wrote:
IMPORT is used to be called immediately and not be queued up to the
end of the rules handling, so that later rules could assume that this
rule has finished.
On Mon, Mar 18, 2013 at 2:58 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Mon, Mar 18, 2013 at 02:17:26PM +0100, Tom Gundersen wrote:
paraEvery line in the rules file contains at least one key-value
pair.
- There are two kinds of keys: match and assignment.
-
On Mon, Mar 18, 2013 at 3:31 PM, Kay Sievers k...@vrfy.org wrote:
On Mon, Mar 18, 2013 at 3:24 PM, Tom Gundersen t...@jklm.no wrote:
On Mon, Mar 18, 2013 at 3:01 PM, Kay Sievers k...@vrfy.org wrote:
IMPORT is used to be called immediately and not be queued up to the
end of the rules handling,
On Mon, Mar 18, 2013 at 4:04 PM, Tom Gundersen t...@jklm.no wrote:
On Mon, Mar 18, 2013 at 3:31 PM, Kay Sievers k...@vrfy.org wrote:
On Mon, Mar 18, 2013 at 3:24 PM, Tom Gundersen t...@jklm.no wrote:
On Mon, Mar 18, 2013 at 3:01 PM, Kay Sievers k...@vrfy.org wrote:
IMPORT is used to be called
Le lundi 18 mars 2013 à 14:34 +0100, Lennart Poettering a écrit :
On Mon, 18.03.13 09:39, Frederic Crozat (fcro...@suse.com) wrote:
Le dimanche 17 mars 2013 à 14:54 +0100, Kay Sievers a écrit :
Here is a chart:
http://people.freedesktop.org/~kay/bootchart-20130317-1434.svg
On Mon, Mar 18, 2013 at 5:09 PM, Kay Sievers k...@vrfy.org wrote:
On Mon, Mar 18, 2013 at 4:04 PM, Tom Gundersen t...@jklm.no wrote:
If not, I guess we could
rename it an use RUN, otherwise I suppose we'd have to stick with
IMPORT... Anyone else have an opinion?
I would not expect any real
On Mon, Mar 18, 2013 at 3:20 PM, Tom Gundersen t...@jklm.no wrote:
So perhaps net.predictable-names
Pushed this. Feel free to rename.
-t
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
Hi everyone, I just had my first encounter with systemd and all in all I'm
highly impressed.
One thing saddened me a bit though: its not obvious what to do if I just want
to start a service or do something *after* all the stuff that shipped with ths
OS has happened and the system is fully
Am 18.03.2013 18:49, schrieb Britton Kerin:
Hi everyone, I just had my first encounter with systemd and all in all I'm
highly impressed.
One thing saddened me a bit though: its not obvious what to do if I just want
to start a service or do something *after* all the stuff that shipped with
My service needs reasonably continuous mtimes on files, but at the
moment there is a big discontinuity soon after boot.
There are a number of web pages out there which tell you to put
stuff like this:
After=syslog.target network.target
WantedBy=multi-user.target
In your .service file
'Twas brillig, and Britton Kerin at 18/03/13 17:49 did gyre and gimble:
Hi everyone, I just had my first encounter with systemd and all in all I'm
highly impressed.
One thing saddened me a bit though: its not obvious what to do if I just want
to start a service or do something *after* all
This is a followup to: commit 1a37b9b9043ef83e9900e460a9a1fccced3acf89
It will fix denial messages from dbus-daemon between gdm and
systemd-logind on logging into GNOME due to this.
See the previous commit for more details.
---
src/core/dbus-job.c |4 ++--
---
src/login/inhibit.c |9 ++---
src/login/loginctl.c| 23 ---
src/login/logind-dbus.c | 29 +
src/login/logind-seat-dbus.c| 22 +-
src/login/logind-session-dbus.c | 29
On Mon, Mar 18, 2013 at 6:27 PM, Tom Gundersen t...@jklm.no wrote:
On Mon, Mar 18, 2013 at 3:20 PM, Tom Gundersen t...@jklm.no wrote:
So perhaps net.predictable-names
Pushed this. Feel free to rename.
Renamed to net.ifnames= to be more digestible for the kernel. If that
ever happens ...
I
On Sun, Mar 17, 2013 at 6:54 AM, Kay Sievers k...@vrfy.org wrote:
Here is a chart:
http://people.freedesktop.org/~kay/bootchart-20130317-1434.svg
Rotating media and really cheap hardware looks very sad, and we take
like 5 times longer to boot than Windows 8.
I've seen many charts like that
On Mon, Mar 18, 2013 at 7:40 PM, Kok, Auke-jan H
auke-jan.h@intel.com wrote:
On Sun, Mar 17, 2013 at 6:54 AM, Kay Sievers k...@vrfy.org wrote:
Here is a chart:
http://people.freedesktop.org/~kay/bootchart-20130317-1434.svg
Rotating media and really cheap hardware looks very sad, and we
Am 18.03.2013 19:45, schrieb Kay Sievers:
I put an SSD in that crappy box today; it's down from 25 to 7 sec on
the otherwise identical system. :)
So I'll not need to debug any rotating media issues, I don't have any
of them again. :)
this is nice for you
but keep in mind that for
On Sat, Mar 16, 2013 at 8:10 AM, Cedric BAIL cedric.b...@free.fr wrote:
As both of those process start visible application that should not
be killed on a restart of the initialization daemon carelessly, they
do have the same issue as Enlightenment.
Something that would be nice is if we
Sync journal with fdatasync after 10s of inactivity (by default), or
after 10 messages (by default). Intervals configured
via SyncIntervalSec and SyncIntervalMsg options at journal.conf.
Manual sync can be performed via sending SIGUSR1.
---
src/journal/journal-file.c | 25 +++-
]] Reindl Harald
but keep in mind that for professional environments for many
years SSD is no option for some TB of data and even if
the price falls down you have to calculate redundancy for
RAID10 environemnts which can not be raplced by a SSD
due lack of relieability and no real-world
Hi,
Just a quick note, Systemd is a core function on a core OS.
and a coreOS is likely to be started from flash drives. We have
i.e. ATCA devices starting from eUSB Sticks or even SD cards.
After they started the nodes could have high perfomance SSD drives
mounted for payload data, or even not
On Mon, Mar 18, 2013 at 2:30 PM, Holger Winkelmann h...@travelping.com wrote:
Hi,
Just a quick note, Systemd is a core function on a core OS.
and a coreOS is likely to be started from flash drives. We have
i.e. ATCA devices starting from eUSB Sticks or even SD cards.
After they started the
On Mon, Mar 18, 2013 at 11:57 AM, Reindl Harald h.rei...@thelounge.net wrote:
Am 18.03.2013 19:45, schrieb Kay Sievers:
I put an SSD in that crappy box today; it's down from 25 to 7 sec on
the otherwise identical system. :)
So I'll not need to debug any rotating media issues, I don't have
You are right, hopefully systemd will not turn into a direction
where only the ulra modern notebook or desktop can use it.
we see a lot of advantages to use systemd in embedded environments.
and we are talking here about_
- 180-680 MHh MIPS, ARM CPUs
- 4-32 MB Flash
- 32-128MB RAM
at the low
On Mon, Mar 18, 2013 at 10:17:25PM +0200, Oleksii Shevchuk wrote:
Sync journal with fdatasync after 10s of inactivity (by default), or
after 10 messages (by default). Intervals configured
via SyncIntervalSec and SyncIntervalMsg options at journal.conf.
Manual sync can be performed via sending
On Mon, Mar 18, 2013 at 02:38:24PM -0400, Colin Walters wrote:
This is a followup to: commit 1a37b9b9043ef83e9900e460a9a1fccced3acf89
It will fix denial messages from dbus-daemon between gdm and
systemd-logind on logging into GNOME due to this.
Applied.
Zbyszek
On Mon, Mar 18, 2013 at 02:38:48PM -0400, Colin Walters wrote:
---
src/login/inhibit.c |9 ++---
src/login/loginctl.c| 23 ---
src/login/logind-dbus.c | 29 +
src/login/logind-seat-dbus.c| 22
On Sat, 2013-03-16 at 18:45 +0200, Oleksii Shevchuk wrote:
Sync journal with fdatasync after [...] 10 messages (by default)
That's going to be kind of painful for the current GNOME userspace, we
sadly emit a lot of crap at bootup =/ (I'm slowly trying to trim it,
but...it's slow going)
And
On Tue, Mar 19, 2013 at 4:33 AM, Kok, Auke-jan H
auke-jan.h@intel.com wrote:
On Sat, Mar 16, 2013 at 8:10 AM, Cedric BAIL cedric.b...@free.fr wrote:
As both of those process start visible application that should not
be killed on a restart of the initialization daemon carelessly, they
do
---
A serie composed of three patches:
1. this one: make sd_journal_add_file available to the wide public
2. second one: allow opening of the journal in stub mode, without
any files
Explicit flag is required, since this is supposed to be used
mostly for debugging and it is better to catch the mistake
of not specyfing any files.
---
src/journal/sd-journal.c | 11 +++
src/systemd/sd-journal.h | 3 ++-
2 files changed, 9 insertions(+), 5 deletions(-)
diff --git
This is useful for debugging and feels pretty natural. For example
answering the question is this big .journal file worth keeping?
is made easier.
---
man/journalctl.xml | 31 ++-
src/journal/journalctl.c | 33 -
2 files changed,
On Tue, Mar 19, 2013 at 2:29 AM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
---
A serie composed of three patches:
1. this one: make sd_journal_add_file available to the wide public
2. second one: allow opening of the journal in stub mode, without
any files
3. third one:
57 matches
Mail list logo
