How can I convince systemd-nspawn to let me create loop devices inside a
container?
I just learned that docker apparently has a —privileged=true, which allows
this. man docker says:
> The --privileged flag gives all capabilities to the container, and it also
> lifts all the limitations enforce
On Wed, 24.06.15 08:55, Ernast Sevo (ers...@gmail.com) wrote:
> Hello!
>
>
> I have a small issue that I am facing on my system when journal files
> aren't cleanly closed. I have seen online that many other people have
> encountered this online but haven't actually come close to finding a
> sol
Hi Lennart,
sorry, this took a bit longer than expected, but I took the time to
upgrade to systemd 221, so the results should be a bit closer to the
current state than before (which was still using systemd 219).
Inside container (broken shell/fish):
speed 38400 baud; rows 60; columns 184; line =
Hello!
I have a small issue that I am facing on my system when journal files
aren't cleanly closed. I have seen online that many other people have
encountered this online but haven't actually come close to finding a
solution or figuring out what the issue is. Essentially on my system
journal fil
On 06/24/2015 12:20 PM, Thomas Schmidt wrote:
> Hello, many thanks for your replies!
>
> Is there an advise what should be used instead ? SDBus/DBus is too
> late activated, private socket looks like a short term solution. Is
> there anything already there which would be the optimal way ?
No. Tha
Thomas Schmidt wrote on 24/06/15 11:20:
> Hello, many thanks for your replies!
>
> Is there an advise what should be used instead ? SDBus/DBus is too
> late activated, private socket looks like a short term solution. Is
> there anything already there which would be the optimal way ? or will
> some
Hello,
many thanks for your replies!
Is there an advise what should be used instead ? SDBus/DBus is too late
activated, private socket looks like a short term solution.
Is there anything already there which would be the optimal way ? or will
something be introduced once the code handling priva
On 06/24/2015 11:57 AM, Umut Tezduyar Lindskog wrote:
> On Wed, Jun 24, 2015 at 11:53 AM, Daniel Mack wrote:
>> On 06/24/2015 11:30 AM, Umut Tezduyar Lindskog wrote:
>>> IMPORTANT: Man page says "This interface is private to systemd and
>>> should not be used in external projects." for /run/system
On Wed, Jun 24, 2015 at 11:53 AM, Daniel Mack wrote:
> On 06/24/2015 11:30 AM, Umut Tezduyar Lindskog wrote:
>> IMPORTANT: Man page says "This interface is private to systemd and
>> should not be used in external projects." for /run/systemd/private. I
>> am not sure if this is still the case.
>
>
On 06/24/2015 11:30 AM, Umut Tezduyar Lindskog wrote:
> IMPORTANT: Man page says "This interface is private to systemd and
> should not be used in external projects." for /run/systemd/private. I
> am not sure if this is still the case.
Yes it is. The private socket is a hack that will go away mid-
Hello,
I’ll check this (it was already in my mind but as you said manuals claim that
it should not be used for external projects so i didn’t touch it yet...)
I’m very thankful for your fast reply
Kind Regards
Thomas Schmidt
>
> Am 24.06.2015 um 11:30 schrieb Umut Tezduyar Lindskog :
>
> You
You can use PID 1's DBUS API -
http://www.freedesktop.org/wiki/Software/systemd/dbus/. Particularly
you should be interested in NJobs and Progress property.
Since it is too late to wait for DBus to come up you need to connect
to systemd directly (instead of going through dbus-daemon). The socket
y
Hello,
for embedded system I’m writing small boot splash/progress bar daemon
(unfortunately plymouth doesn’t fit). Even after study of especially sd_.*(3)
manuals, mail archives, and source code it is not clear for me what could be
the best way to obtain the boot messages and boot proceed from a
On Wed, Jun 24, 2015 at 8:53 AM, Chad wrote:
> Killermoehre,
> Thank you for your time and reply.
>
> I intend to do exactly that when I start using systemd (I am still using
> init.d at the moment). In fact I have already suggested that very thing on
> the fail2ban mailing list so that can add it
14 matches
Mail list logo