I asked:
>> I've been using Qemu to cross-compile packages and root filesystems
>> for a while and thought I'd try nspawn instead. [ . . . ]
>> Here's the base sequence:
>> Install
>> ==
[ . . . ]
>> Boot as Qemu
>> ===
[ . . . ]
>> Login with nspawn
>> ===
>> moun
В Fri, 3 Apr 2015 14:14:18 -0700
Alison Chaiken пишет:
> I've been using Qemu to cross-compile packages and root filesystems
> for a while and thought I'd try nspawn instead.While I sometimes
> want a full GUI desktop in the walled-off environment, mostly console
> is enough, and for that nsp
В Fri, 3 Apr 2015 21:19:24 +0300
Mantas Mikulėnas пишет:
> Previously udev used to undo mounts when a device *disappeared;* when
> systemd took over the task, it started unmounting things as soon as it
> noticed that the device *doesn't exist right now.* While similar, the new
> behavior can be a
В Fri, 3 Apr 2015 19:16:59 +0200
Lennart Poettering пишет:
> On Fri, 03.04.15 19:38, Andrei Borzenkov (arvidj...@gmail.com) wrote:
>
> > В Fri, 3 Apr 2015 13:17:05 +0200
> > Lennart Poettering пишет:
> >
> > > On Thu, 02.04.15 11:49, Al Lau (laua...@gmail.com) wrote:
> > >
> > > > As a test,
On Sun, Mar 29, 2015 at 12:43 PM, Goffredo Baroncelli
wrote:
> Hi,
> did you find the time to give a look a these patches ? Do you have any
> suggestions ?
>
I do not know about anyone else, but this message was in my spam box.
The reason was: "It has a from address in libero.it but has failed
l
I've been using Qemu to cross-compile packages and root filesystems
for a while and thought I'd try nspawn instead.While I sometimes
want a full GUI desktop in the walled-off environment, mostly console
is enough, and for that nspawn sounds more efficient.
Here's the base sequence:
Install
==
On Fri, 3 Apr 2015, Lennart Poettering wrote:
On Thu, 02.04.15 21:24, Dimitrios Apostolou (ji...@gmx.net) wrote:
Usually if one wants to do that one is just working around some
problems that are better solved in a different way.
Why precisely do you need this feature?
I need to properly ter
Hi,
On 03-04-15 20:21, Benjamin Tissoires wrote:
On Apr 03 2015 or thereabouts, David Herrmann wrote:
Hi
On Fri, Apr 3, 2015 at 5:30 PM, Benjamin Tissoires wrote:
On Apr 03 2015 or thereabouts, David Herrmann wrote:
Hi
On Fri, Apr 3, 2015 at 4:38 PM, Benjamin Tissoires wrote:
On Apr 03 2
Previously udev used to undo mounts when a device *disappeared;* when
systemd took over the task, it started unmounting things as soon as it
noticed that the device *doesn't exist right now.* While similar, the new
behavior can be annoying, since it also triggers if the device never
existed in the
On Apr 03 2015 or thereabouts, David Herrmann wrote:
> Hi
>
> On Fri, Apr 3, 2015 at 5:30 PM, Benjamin Tissoires
> wrote:
> > On Apr 03 2015 or thereabouts, David Herrmann wrote:
> >> Hi
> >>
> >> On Fri, Apr 3, 2015 at 4:38 PM, Benjamin Tissoires
> >> wrote:
> >> > On Apr 03 2015 or thereabou
Hi
On Fri, Apr 3, 2015 at 5:30 PM, Benjamin Tissoires wrote:
> On Apr 03 2015 or thereabouts, David Herrmann wrote:
>> Hi
>>
>> On Fri, Apr 3, 2015 at 4:38 PM, Benjamin Tissoires
>> wrote:
>> > On Apr 03 2015 or thereabouts, Hans de Goede wrote:
>> >> Hi,
>> >>
>> >> On 03-04-15 15:51, David He
2015-04-03 12:49 GMT-03:00 Lennart Poettering :
> On Sun, 29.03.15 19:33, Marcos Mello (marcos...@gmail.com) wrote:
>
>> Mar 29 15:21:16 xxx.localdomain systemd[1]: squid.service: Supervising
>> process 1491 which is not our child. We'll most likely not notice when it
>> exits.
>
> This is probabl
On Fri, 03.04.15 19:38, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> В Fri, 3 Apr 2015 13:17:05 +0200
> Lennart Poettering пишет:
>
> > On Thu, 02.04.15 11:49, Al Lau (laua...@gmail.com) wrote:
> >
> > > As a test, the "/usr/sbin/smartd $smartd_opts" is invoked from the command
> > > line an
В Fri, 3 Apr 2015 13:17:05 +0200
Lennart Poettering пишет:
> On Thu, 02.04.15 11:49, Al Lau (laua...@gmail.com) wrote:
>
> > As a test, the "/usr/sbin/smartd $smartd_opts" is invoked from the command
> > line and the daemon is forked and stayed up as expected. By default, the
> > /usr/sbin/smar
В Fri, 3 Apr 2015 14:04:10 +0200
Lennart Poettering пишет:
> On Thu, 02.04.15 16:28, Martin Pitt (martin.p...@ubuntu.com) wrote:
>
> > Lennart Poettering [2015-04-02 13:03 +0200]:
> > > Yeah, and rightfully so. I mean, a service really should be able to
> > > shutdown if dbus is dead. In fact, i
On Fri, 27.03.15 10:32, Kai Hendry (hen...@webconverger.com) wrote:
> First, thanks for trying to help me Kai. Awesome name btw.
>
> On Fri, 27 Mar 2015, at 03:26 AM, Kai Krakow wrote:
> > Try Type=simple to not let it wait. That is telling systemd, that the
> > binary
> > will not daemonize - a
On Thu, 26.03.15 20:26, Kai Krakow (hurikha...@gmail.com) wrote:
> Kai Hendry schrieb:
>
> > Hi there,
> >
> > How do I figure out why or where something is stuck?
> > http://s.natalian.org/2015-03-25/systemd-start-issue.png
> >
> > `journalctl -u surf -f` prints nothing.
> >
> > Binary surf
---
Changes in v4:
- better logind API naming
- don't write to efi vars if they don't change
man/systemctl.xml | 10 +++
shell-completion/bash/systemctl.in | 2 +-
shell-completion/zsh/_systemctl.in | 1 +
src/login/logind-dbus.c| 9
On Sun, 29.03.15 19:33, Marcos Mello (marcos...@gmail.com) wrote:
> Mar 29 15:21:16 xxx.localdomain systemd[1]: squid.service: Supervising
> process 1491 which is not our child. We'll most likely not notice when it
> exits.
This is probably the source of your problems: squid's main process (or
w
On Apr 03 2015 or thereabouts, David Herrmann wrote:
> Hi
>
> On Fri, Apr 3, 2015 at 4:38 PM, Benjamin Tissoires
> wrote:
> > On Apr 03 2015 or thereabouts, Hans de Goede wrote:
> >> Hi,
> >>
> >> On 03-04-15 15:51, David Herrmann wrote:
> >> >Hi
> >> >
> >> >On Fri, Apr 3, 2015 at 12:07 PM, Han
On Fri, Apr 3, 2015 at 4:47 PM, Lennart Poettering
wrote:
> On Thu, 02.04.15 13:11, Paul Menzel (paulepan...@users.sourceforge.net) wrote:
>
>> Dear systemd folks,
>>
>>
>> some network cards with certain cables and devices take up to five
>> seconds so that the link is up [1].
>>
>> $ sud
On Sat, 28.03.15 10:49, Alberto Bertogli (albert...@blitiri.com.ar) wrote:
>
> Hi!
>
> I noticed by chance that systemd was using ~15% of a CPU in my laptop,
> according to top.
>
> This is on Debian testing, systemd 215-12.
>
> The machine has been up since January, but this started to happen
Hi
On Fri, Apr 3, 2015 at 4:38 PM, Benjamin Tissoires wrote:
> On Apr 03 2015 or thereabouts, Hans de Goede wrote:
>> Hi,
>>
>> On 03-04-15 15:51, David Herrmann wrote:
>> >Hi
>> >
>> >On Fri, Apr 3, 2015 at 12:07 PM, Hans de Goede wrote:
>> >>input_id already (tries to) tag accelerometers as su
On Wed, 01.04.15 23:04, Tobias Hunger (tobias.hun...@gmail.com) wrote:
> A stateless system has a tmpfs as root file system. That obviously
> does not have any block device associated with it. So try falling back
> to the device of the /usr filesystem if the root filesystem fails.
> ---
> src/gpt
On Wed, 01.04.15 22:53, Tobias Hunger (tobias.hun...@gmail.com) wrote:
> /boot does not exist on a stateless system, so do not get
> confused by that.
> ---
> src/efi-boot-generator/efi-boot-generator.c | 23 +++
> 1 file changed, 19 insertions(+), 4 deletions(-)
>
> diff --g
On Thu, 02.04.15 13:11, Paul Menzel (paulepan...@users.sourceforge.net) wrote:
> Dear systemd folks,
>
>
> some network cards with certain cables and devices take up to five
> seconds so that the link is up [1].
>
> $ sudo journalctl -u systemd-networkd
> -- Logs begin at Fr 201
On Apr 03 2015 or thereabouts, Hans de Goede wrote:
> Hi,
>
> On 03-04-15 15:51, David Herrmann wrote:
> >Hi
> >
> >On Fri, Apr 3, 2015 at 12:07 PM, Hans de Goede wrote:
> >>input_id already (tries to) tag accelerometers as such, but this only works
> >>for absolute accelerometers. Recent kernels
B1;3802;0cOn Fri, 03.04.15 15:17, Didier Roche (didro...@ubuntu.com) wrote:
> >To start with, the code is really wrong, it should never have been
> >merged in its current state, the read/write logic for the sockets is
> >completely borked (I cannot even boot my own machine reliably with
> >it!). A
Hi,
On 03-04-15 15:51, David Herrmann wrote:
Hi
On Fri, Apr 3, 2015 at 12:07 PM, Hans de Goede wrote:
input_id already (tries to) tag accelerometers as such, but this only works
for absolute accelerometers. Recent kernels mark accelerometers through an
input prop. Trust that prop and always t
The pointingstick of the Dell Latitude E6400 is somewhat slow by default,
where as the pointingstick of the Dell Latitude D620 is much too fast by
default, set POINTINGSTICK_CONST_ACCEL for both of them to adjust for this.
---
hwdb/70-pointingstick.hwdb | 12
1 file changed, 12 insert
Lenovo has changed the sensitity of the trackpoint on the x240 / T440s / T540
generation of Thinkpads, making them somewhat unsensitive by default, add a
hwdb entry to tweak the sensitivity setting.
The ThinkPad X200s is way way too slow by default and unless you push the
trackpoint quite hard onl
There is quite a wide spread in the delta events generated by pointingsticks,
some generate deltas of 1-2 under normal use, while others generate deltas
from 1-20.
This commit adds a set of rules + a hwdb file which allows specifying a
per model POINTINGSTICK_CONST_ACCEL value which can be used by
The IBM / Lenovo trackpoints are special, they allow specifying a sensitivity
setting through a ps/2 command, which changes the range of the deltas send when
using the trackpoint. One some models with normal usage one only deltas
of 1 or 2 are send, resulting in there only being 2 mouse cursor move
Hi All,
Here is v2 of my pointstick set.
Changes since v1:
-Drop the patch to set ID_INPUT_TRACKPOINT, Peter already send almost the
same patch to set ID_INPUT_POINTINGSTICK
-s/trackpoint/pointingstick/ unlike trackpoint pointingstick is a vendor
neutral name, and pointingstick is also what the
Hi
On Fri, Apr 3, 2015 at 12:07 PM, Hans de Goede wrote:
> input_id already (tries to) tag accelerometers as such, but this only works
> for absolute accelerometers. Recent kernels mark accelerometers through an
> input prop. Trust that prop and always tag devices with it with
> ID_INPUT_ACCELERO
Hi,
On 03-04-15 13:13, Lennart Poettering wrote:
On Fri, 03.04.15 12:07, Hans de Goede (hdego...@redhat.com) wrote:
input_id already (tries to) tag accelerometers as such, but this only works
for absolute accelerometers. Recent kernels mark accelerometers through an
input prop. Trust that prop
Hi,
With the help of Lennart and Alexander Sverdlin, I reworked major parts
of the bootchart code to make it more readable and maintainable. Most
importantly, I got rid a number of global variables that were used all
over the place, fixed tons of coding style issues and dead code. The
patches for
Le 03/04/2015 14:58, Lennart Poettering a écrit :
Heya,
Hey Lennart,
so we discussed the whole fsckd situation a bit more here in Berlin,
and we came to the conclusion that fsckd really should not exist the
way it does in systemd.
To start with, the code is really wrong, it should never have
On Fri, 03.04.15 12:45, Mantas Mikulėnas (graw...@gmail.com) wrote:
> Actually why does it need a pidfile in the first place? Systemd is usually
> good at guessing the mainpid.
Yeah, if there's only one process remaining after the parent process
exited, then the PID file logic is unnecessary. Tha
Heya,
so we discussed the whole fsckd situation a bit more here in Berlin,
and we came to the conclusion that fsckd really should not exist the
way it does in systemd.
To start with, the code is really wrong, it should never have been
merged in its current state, the read/write logic for the sock
On Fri, Apr 3, 2015, 14:17 Lennart Poettering
wrote:
On Thu, 02.04.15 11:49, Al Lau (laua...@gmail.com) wrote:
> As a test, the "/usr/sbin/smartd $smartd_opts" is invoked from the command
> line and the daemon is forked and stayed up as expected. By default, the
> /usr/sbin/smartd daemonize.
On Thu, 02.04.15 09:39, Martin Pitt (martin.p...@ubuntu.com) wrote:
> Hello all,
>
> The recent commit
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=d99ce933 (which
> also made it into v219-stable at
> http://cgit.freedesktop.org/systemd/systemd-stable/commit/?h=v219-stable&id=b238b0ea
On Thu, 02.04.15 12:01, Merten Sach (mer...@tabinin.eu) wrote:
> Hi,
>
> I have a problem with a timer that trigges a service that has a condition set.
> The timer defines the following properties:
>
> [Timer]
> OnBootSec=1h
> OnUnitInactiveSec=1h
> Unit=autobackup@%i.service
>
> The se
On Thu, 02.04.15 20:55, Kurt von Laven (k...@endlessm.com) wrote:
> On a separate note, how long does systemd wait after sending a SIGTERM to a
> service before sending it a SIGKILL?
90s. This may be configured per-service in TimeoutStopSec= and
globally with DefaultTimeoutStopSec= in system.con
On Thu, 02.04.15 22:28, Martin Pitt (martin.p...@ubuntu.com) wrote:
> Hello,
>
> Dan Williams [2015-04-02 9:51 -0500]:
> > On Thu, 2015-04-02 at 16:31 +0200, Martin Pitt wrote:
> > > wpa_supplicant and NM already have Before=network.target which is even
> > > stronger. But that doesn't help -- i
On Thu, 02.04.15 16:31, Martin Pitt (martin.p...@ubuntu.com) wrote:
> Lennart Poettering [2015-04-02 15:31 +0200]:
> > You need to order wpa_supplicant and NM Before=remote-fs-pre.target
> > and pull it it via Wants=remote-fs-pre.target. With that in place
> > during shutdown the mounts will be un
On Thu, 02.04.15 16:28, Martin Pitt (martin.p...@ubuntu.com) wrote:
> Lennart Poettering [2015-04-02 13:03 +0200]:
> > Yeah, and rightfully so. I mean, a service really should be able to
> > shutdown if dbus is dead. In fact, it should be able to shutdown in
> > pretty much any situation...
>
> T
On Thu, 02.04.15 15:04, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote:
> On 02/04/15 14:31, Lennart Poettering wrote:
> > Hmm? I really don't see how the NFS vs wpa_supplicant issue has
> > anything to do with dbus? NFS doesn't care about dbus at all...
>
> It does inasmuch as it requires
2015-04-03 14:38 GMT+03:00 Lennart Poettering :
> On Fri, 03.04.15 14:31, Alexey Shabalin (a.shaba...@gmail.com) wrote:
> My plan is to add a concept of .nspawn files that may accompany
> machine directories and contain additional settings that may then be
> omitted on the command line. It has been
On Fri, 03.04.15 14:31, Alexey Shabalin (a.shaba...@gmail.com) wrote:
> Hi.
>
> I have several containers with different setting.
> For example:
> systemd-nspawn@server1.service:
> ExecStart=/usr/bin/systemd-nspawn --quiet --keep-unit --boot
> --link-journal=try-guest --network-bridge=br140
> --b
Hi.
I have several containers with different setting.
For example:
systemd-nspawn@server1.service:
ExecStart=/usr/bin/systemd-nspawn --quiet --keep-unit --boot
--link-journal=try-guest --network-bridge=br140
--bind=/srv/node:/srv/node --machine=%i
systemd-nspawn@server2.service:
ExecStart=/usr/bi
On Fri, Apr 3, 2015 at 11:14 AM, Jan Synáček wrote:
> From the following commit onward, systemd doesn't boot properly in
> Rawhide. Some device units time out and I'm then dropped into an
> emergency shell.
>
> commit f4ac4d1a82e2c468761fffa23841ad886221
> Author: Tom Gundersen
> Date: Wed
On Thu, 02.04.15 21:24, Dimitrios Apostolou (ji...@gmx.net) wrote:
> >Usually if one wants to do that one is just working around some
> >problems that are better solved in a different way.
> >
> >Why precisely do you need this feature?
>
> I need to properly terminate system accounting, in the sa
On Thu, 02.04.15 11:49, Al Lau (laua...@gmail.com) wrote:
> As a test, the "/usr/sbin/smartd $smartd_opts" is invoked from the command
> line and the daemon is forked and stayed up as expected. By default, the
> /usr/sbin/smartd daemonize.
Well, but does it do that correctly? i.e. does it *doubl
On Fri, 03.04.15 12:07, Hans de Goede (hdego...@redhat.com) wrote:
> input_id already (tries to) tag accelerometers as such, but this only works
> for absolute accelerometers. Recent kernels mark accelerometers through an
> input prop. Trust that prop and always tag devices with it with
> ID_INPUT
On Fri, 03.04.15 12:40, Jan Janssen (medhe...@web.de) wrote:
> Changes in v3:
> - call the feature reboot to firmware everywhere
> - make the login interface a property and methods to change it and
>don't couple it with a reboot action
> - changed/added policykit action defaulting to auth_a
---
Hi,
Changes in v3:
- call the feature reboot to firmware everywhere
- make the login interface a property and methods to change it and
don't couple it with a reboot action
- changed/added policykit action defaulting to auth_admin_keep. Please
change this if something else is desired.
input_id already (tries to) tag accelerometers as such, but this only works
for absolute accelerometers. Recent kernels mark accelerometers through an
input prop. Trust that prop and always tag devices with it with
ID_INPUT_ACCELEROMETER.
Note that detection by the prop bit works the same as the e
Hi All,
Note this patch depends on Peter Hutterer's recent patch titled:
"udev: input_id: tag pointing sticks as ID_INPUT_POINTINGSTICK"
Regards,
Hans
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailm
Hi,
On 02-04-15 12:27, Lennart Poettering wrote:
On Thu, 02.04.15 12:21, Lennart Poettering (lenn...@poettering.net) wrote:
On Thu, 02.04.15 11:48, Hans de Goede (hdego...@redhat.com) wrote:
The kernel has been setting the INPUT_PROP_POINTING_STICK property bit
on trackpoints for a while now
Hello,
From the following commit onward, systemd doesn't boot properly in
Rawhide. Some device units time out and I'm then dropped into an
emergency shell.
commit f4ac4d1a82e2c468761fffa23841ad886221
Author: Tom Gundersen
Date: Wed Apr 1 13:55:20 2015 +0200
libudev: device - replace b
Hello,
Dan Williams [2015-04-02 9:51 -0500]:
> On Thu, 2015-04-02 at 16:31 +0200, Martin Pitt wrote:
> > wpa_supplicant and NM already have Before=network.target which is even
> > stronger. But that doesn't help -- it's D-Bus which we need to leave
> > running longer, as dbus going down early tea
62 matches
Mail list logo
