Op 28 apr. 2014, om 17:48 heeft Lennart Poettering het
volgende geschreven:
> On Mon, 28.04.14 12:22, Manuel Reimer (manuel.s...@nurfuerspam.de) wrote:
>
>>
>> Lukasz Skalski samsung.com> writes:
>>> You can define which RTC (/dev/rtcX) should be read -
>>> "(rtc1) RTC used to set the system
On Fri, Apr 25, 2014 at 08:30:36PM +0200, Tom Gundersen wrote:
> On Fri, Apr 11, 2014 at 2:45 AM, Djalal Harouni wrote:
> > Currently if nspawn was called with --link-journal=host or
> > --link-journal=auto and the right /var/log/journal/machine-id/ exists
> > then the bind mount the subdirectory
On Fri, Apr 25, 2014 at 08:07:29PM +0200, Tom Gundersen wrote:
> On Fri, Apr 11, 2014 at 2:45 AM, Djalal Harouni wrote:
> > Move the container wait logic into its own wait_for_container() function
> > and add two status codes: CONTAINER_TERMINATED or CONTAINER_REBOOTED
> >
> > These status codes a
Lennart Poettering poettering.net> writes:
>
> On Mon, 28.04.14 00:44, Mantas Mikulėnas (grawity gmail.com) wrote:
>
> > With proprietary graphics drivers, there won't be any 'drm' devices in
> > sysfs, so logind will never suspend the system upon closing the lid,
> > even if only one (interna
On Mon, Apr 28, 2014 at 6:12 PM, Lennart Poettering
wrote:
> Oh yuck, this looks like a bug in systemd.
>
> Currently if /etc/machine-id is missing we will try to initialize it
> from the UUID that KVM maintaines for each machine. However, this is a
> bad idea if we are actually running inside a c
This is a completed version of the patch Lennart and I worked on at
the hackfest. The version we worked on had separate string arguments
for each type of state. This patch harmonizes it more with the way
systemctl --state already works, which is an array of possible states
to match across all state
From: David Strauss
---
src/core/dbus-manager.c| 24 +++-
src/core/org.freedesktop.systemd1.conf | 4
src/systemctl/systemctl.c | 24 +---
3 files changed, 40 insertions(+), 12 deletions(-)
diff --git a/src/core/dbus-man
On Fri, 2014-04-25 at 18:26 -0400, Will Woods wrote:
> Currently, systemd refuses to load SELinux policy more than once.
>
> Normal systems don't care, because they either:
> a) have initramfs without policy, then load policy after switch-root, or
> b) load policy in initramfs, and never switch-ro
On Fri, Apr 25, 2014 at 6:26 PM, Will Woods wrote:
But if SELinux was already initialized, selinux_setup() skips loading
policy and returns 0. So if you load policy normally, and then you
switch-root to a new root that has new policy, selinux_setup() never
loads the new policy. What gives?
I
On Fri, 25.04.14 15:39, Brandon Philips (bran...@ifup.co) wrote:
> On Wed, Apr 23, 2014 at 2:36 PM, Lennart Poettering
> wrote:
> > This looks correct, but could you move this into job_coldplug()?
>
> I rewrote the patch to be in job_coldplug() and tested. Patch attached.
This has been applied
Hi Lennart,
inline...
On 04/28/2014 04:31 PM, Lennart Poettering wrote:
> On Sun, 27.04.14 23:46, Przemek Rudy (pru...@o2.pl) wrote:
>
>>
>> This patch is a proposal for a problem with not falling back to password
>> request
>> if the device with unlocking key for crypt volumes is not mounted fo
On Mon, 28.04.14 17:45, Ruben Kerkhof (ru...@rubenkerkhof.com) wrote:
> > Alternatively, remove the file in the container, as it will then create
> > a new machine id on boot automatically, and store in the file.
>
> Tried that, it does generate a machine-id, but the same one as on the host.
>
>
On 04/28/2014 05:47 PM, Lennart Poettering wrote:
Why do you have two RTCs even enabled? What's the logic there? And why
isn't rtc0 just fine? If it doesn't work, why have it enabled at all?
"rtc0" is part of the CPU (iMX233) and only works if a LiPo battery is
connected. I prefer a RTC chip w
On Mon, Apr 28, 2014 at 5:53 PM, Lennart Poettering
wrote:
>
> This is solely about whether Local= and Remote= belong in .netdev?
That's my take.
> I am
> pretty sure they do, after all this is a weird setup: a tunnel is
> something where the link level is actually the network level of the
> und
On Fri, 25.04.14 19:36, Tom Gundersen (t...@jklm.no) wrote:
> [sorry for breaking the quoting, hopefully it is clear who said what]
>
> I actually think this is the correct way to do it, as the addresses
> (which I assume is what Jóhann is objecting to?) are properties of the
> link (similar to m
On Mon, 28.04.14 12:22, Manuel Reimer (manuel.s...@nurfuerspam.de) wrote:
>
> Lukasz Skalski samsung.com> writes:
> > You can define which RTC (/dev/rtcX) should be read -
> > "(rtc1) RTC used to set the system time" option in kernel menuconfig.
>
> Yes, this is possible. But my RTC does not ex
On Mon, 28.04.14 11:36, Manuel Reimer (manuel.s...@nurfuerspam.de) wrote:
> Mantas Mikulėnas gmail.com> writes:
> > Doesn't the kernel already do the same via CONFIG_RTC_HCTOSYS_DEVICE?
>
> The kernel reads from "/dev/rtc0" which is the CPU built-in RTC (iMX233). My
> added RTC has to be registe
On Mon, Apr 28, 2014 at 5:07 PM, Lennart Poettering
wrote:
> On Sat, 26.04.14 15:35, Ruben Kerkhof (ru...@rubenkerkhof.com) wrote:
>
>> Hi list,
>>
>> I was just playing with systemd-nspawn, and noticed that when I start a
>> container in a virtual machine running on KVM,
>> it gets the same mach
On Mon, 28.04.14 07:48, Manuel Reimer (manuel.s...@nurfuerspam.de) wrote:
> Hello,
>
> I want to run systemd on a embedded linux board. I have connected a RTC
> module via I2C.
>
> What I want to do is to set the time via "hwclock --hctosys" during
> boot.
I can only recommend to make sure tha
On Sun, 27.04.14 23:46, Przemek Rudy (pru...@o2.pl) wrote:
>
> This patch is a proposal for a problem with not falling back to password
> request
> if the device with unlocking key for crypt volumes is not mounted for
> defined time.
Can you elaborate on the usecase? I mean, this would still re
On Mon, 28.04.14 00:44, Mantas Mikulėnas (graw...@gmail.com) wrote:
> With proprietary graphics drivers, there won't be any 'drm' devices in
> sysfs, so logind will never suspend the system upon closing the lid,
> even if only one (internal) display is connected. This has been reported
> by multip
On Sat, 26.04.14 15:35, Ruben Kerkhof (ru...@rubenkerkhof.com) wrote:
> Hi list,
>
> I was just playing with systemd-nspawn, and noticed that when I start a
> container in a virtual machine running on KVM,
> it gets the same machine-id as the vm itself, resulting in:
> Host and machine ids are e
I am trying to access the journal using the HTTP interface, as described
here:
http://www.freedesktop.org/software/systemd/man/systemd-journal-gatewayd.service.html
I want to filter journal entries by starting date/time or until a specific
date/time and by number of lines. These are similar to jou
On 04/28/2014 02:22 PM, Manuel Reimer wrote:
Lukasz Skalski samsung.com> writes:
You can define which RTC (/dev/rtcX) should be read -
"(rtc1) RTC used to set the system time" option in kernel menuconfig.
Yes, this is possible. But my RTC does not exist until I do the following on
shell:
ech
Hi Tom,
Sure, I'll get rid of this signed-off soon and re-send.
It has been tested with fedora 20 for all three options:
- with device inserted
- with device removed during startup but inserted before the mount timeout
- with device removed
Thanks
Przemek
On 04/28/2014 10:15 AM, Tom Gundersen wro
Lukasz Skalski samsung.com> writes:
> You can define which RTC (/dev/rtcX) should be read -
> "(rtc1) RTC used to set the system time" option in kernel menuconfig.
Yes, this is possible. But my RTC does not exist until I do the following on
shell:
echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-1/
On 04/28/2014 01:36 PM, Manuel Reimer wrote:
Mantas Mikulėnas gmail.com> writes:
Doesn't the kernel already do the same via CONFIG_RTC_HCTOSYS_DEVICE?
The kernel reads from "/dev/rtc0" which is the CPU built-in RTC (iMX233). My
added RTC has to be registered first and then appears as /dev/rtc
Hi,
We stumbled upon a freeze/block in systemd.
The problem occurs when a rshd (socket activated) execution is completed, the
network connection is down and systemd is closing the socket.
This causes a long (60 seconds) freeze where it's not possible to communicate
with systemd.
Do you have any
Mantas Mikulėnas gmail.com> writes:
> Doesn't the kernel already do the same via CONFIG_RTC_HCTOSYS_DEVICE?
The kernel reads from "/dev/rtc0" which is the CPU built-in RTC (iMX233). My
added RTC has to be registered first and then appears as /dev/rtc1.
Greetings,
Manuel
Hi Damir,
Thanks for the report. Umut just pointed out this problem the other
day and how to fix it, so we should have it fixed by the next release.
Cheers,
Tom
On Mon, Apr 28, 2014 at 11:40 AM, Damir Simunic
wrote:
> I installed CoreOS 298 (with systemd 212) on a multi-homed machine with a
>
On Mon, Apr 28, 2014 at 10:48 AM, Manuel Reimer
wrote:
>
> Hello,
>
> I want to run systemd on a embedded linux board. I have connected a RTC
> module via I2C.
>
> What I want to do is to set the time via "hwclock --hctosys" during boot. I
> have to do this before the first systemd-timer is trigge
Hey Kay,
Kay Sievers [2014-04-28 12:16 +0200]:
> http://cgit.freedesktop.org/systemd/systemd/commit/?id=bf7f800f2b3e93ccd1229d4717166f3a4d3af72f
Ah, cool, thanks! Will replace our patch with that.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.c
Hey Kay,
Kay Sievers [2014-04-26 19:55 +0200]:
> SUBSYSTEM=="module" is not so much about *loadable* modules, but about
> module *parameters*, which also apply to built-in modules. "block" is
> never a module.
Ah! That misled me then, thanks for clarifying.
> Is the value not applied at all, can
On Mon, Apr 28, 2014 at 12:09 PM, Martin Pitt wrote:
> Hello all,
>
> a while ago we got a report (https://launchpad.net/bugs/1207705) that
> with kernel >= 3.11 the kvm modules (in particular, kvm_intel) don't
> get autoloaded any more. Andy (CC'ed) fixed that back then with the
> attached patch
Hello all,
a while ago we got a report (https://launchpad.net/bugs/1207705) that
with kernel >= 3.11 the kvm modules (in particular, kvm_intel) don't
get autoloaded any more. Andy (CC'ed) fixed that back then with the
attached patch to 80-drivers.rules. Yesterday on the Debian systemd
sprint this
Hi,
I installed CoreOS 298 (with systemd 212) on a multi-homed machine with a
public and a private interface. It’s a data-center machine, and the provider
assigns both interfaces through DHCP. Stock CoreOS defaults to DHCP settings
for all network interfaces.
When I boot the machine, the publi
On Mon, Apr 28, 2014 at 12:46 AM, Przemek Rudy wrote:
> This patch is a proposal for a problem with not falling back to password
> request
> if the device with unlocking key for crypt volumes is not mounted for defined
> time.
Looks good to me (but I didn't test it). Only one minor nit below.
Hello,
I want to run systemd on a embedded linux board. I have connected a RTC
module via I2C.
What I want to do is to set the time via "hwclock --hctosys" during boot. I
have to do this before the first systemd-timer is triggered.
How do I have to create my service-file to set the time as early
38 matches
Mail list logo
