uspend-listener could busy-poll
ListInhibitors DBus method until all predefined services have successfully
re-acquired sleep delay inhibitor locks.
Thank you,
Eric
block device via UUID, LABEL, PARTUUID, PARTLABEL, etc.? Because the
current implementations don't scale well when you have many block
devices.
I suspect we may not be the first to encounter this, so just probing
to see if anyone had ideas on how to solve this in the past.
Is mise le meas/Regards,
Eric Curtin
Yes, your understanding is correct. I'm off at the moment, we will try and
open a PR sometime to explain it better.
By the way I'd also happily review your PR also if you think you could
explain it better.
At the moment it's a loopback mounted file from /boot, mounted as an erofs
with transient o
On Tue, 12 Dec 2023 at 20:35, Nils Kattenbeck wrote:
>
> Hi, while I have been following this thread passively for now I also
> wanted to chime in.
>
> > (The main reason why sd-stub doesn't actually support erofs-initrds,
> > is that sd-stub also generates initrd cpios on the fly, to pass
> > cre
t; > On Mon, 11 Dec 2023 at 17:30, Demi Marie Obenour
> > > wrote:
> > > >
> > > > On Mon, Dec 11, 2023 at 10:57:58AM +0100, Lennart Poettering wrote:
> > > > > On Fr, 08.12.23 17:59, Eric Curtin (ecur...@redhat.com) wrote:
> > > > >
&g
On Mon, 11 Dec 2023 at 16:36, Demi Marie Obenour
wrote:
>
> On Mon, Dec 11, 2023 at 10:57:58AM +0100, Lennart Poettering wrote:
> > On Fr, 08.12.23 17:59, Eric Curtin (ecur...@redhat.com) wrote:
> >
> > > Here is the boot sequence with initoverlayfs integrated, the
&g
On Mon, 11 Dec 2023 at 12:48, Eric Curtin wrote:
>
> On Mon, 11 Dec 2023 at 11:51, Lennart Poettering
> wrote:
> >
> > On Mo, 11.12.23 11:28, Eric Curtin (ecur...@redhat.com) wrote:
> >
> > > > > For the items listed above I think you can find
On Mon, 11 Dec 2023 at 11:51, Lennart Poettering wrote:
>
> On Mo, 11.12.23 11:28, Eric Curtin (ecur...@redhat.com) wrote:
>
> > > > For the items listed above I think you can find different solutions
> > > > which do not necessarily compromise security as much
I am also thinking, what is the difference between "make the
bootloader load the erofs into contiguous memory" part and doing
something like storage-init.
They are similar approaches, introduce something in the middle to
handle the erofs.
Is mise le meas/Regards,
Eric Curtin
On M
On Mon, 11 Dec 2023 at 11:20, Eric Curtin wrote:
>
> On Mon, 11 Dec 2023 at 10:06, Lennart Poettering wrote:
> >
> > On Fr, 08.12.23 17:59, Eric Curtin (ecur...@redhat.com) wrote:
> >
> > > Here is the boot sequence with initoverlayfs integrated, the
> > &
On Mon, 11 Dec 2023 at 10:06, Lennart Poettering wrote:
>
> On Fr, 08.12.23 17:59, Eric Curtin (ecur...@redhat.com) wrote:
>
> > Here is the boot sequence with initoverlayfs integrated, the
> > mini-initramfs contains just enough to get storage drivers loaded and
> >
On Sat, 9 Dec 2023 at 18:12, Luca Boccassi wrote:
>
> On Sat, 9 Dec 2023 at 17:58, Eric Curtin wrote:
> >
> > On Sat, 9 Dec 2023 at 17:46, Luca Boccassi wrote:
> > >
> > > On Sat, 9 Dec 2023 at 17:25, Eric Curtin wrote:
> > > >
> >
On Sat, 9 Dec 2023 at 17:46, Luca Boccassi wrote:
>
> On Sat, 9 Dec 2023 at 17:25, Eric Curtin wrote:
> >
> > On Sat, 9 Dec 2023 at 17:19, Luca Boccassi wrote:
> > >
> > > On Sat, 9 Dec 2023 at 15:08, Eric Curtin wrote:
> > > >
>
On Sat, 9 Dec 2023 at 17:19, Luca Boccassi wrote:
>
> On Sat, 9 Dec 2023 at 15:08, Eric Curtin wrote:
> >
> > On Sat, 9 Dec 2023 at 14:56, Andrei Borzenkov wrote:
> > >
> > > On 09.12.2023 17:42, Eric Curtin wrote:
> > > > On Sat, 9 Dec 2023 at 1
nting
erofs with transient overlay is really fast. Of course if people want
to do that it's fine :)
>
> Before adopting anything like this I believe there should be a serious
> effort to get
> this implemented within Linux itself. Only if that turns out to be
> impossible sho
On Sat, 9 Dec 2023 at 14:56, Andrei Borzenkov wrote:
>
> On 09.12.2023 17:42, Eric Curtin wrote:
> > On Sat, 9 Dec 2023 at 12:46, Luca Boccassi wrote:
> >>
> >> On Fri, 8 Dec 2023 at 19:00, Eric Curtin wrote:
> >>>
> >>> We have been wo
On Sat, 9 Dec 2023 at 12:46, Luca Boccassi wrote:
>
> On Fri, 8 Dec 2023 at 19:00, Eric Curtin wrote:
> >
> > We have been working on a new initial filesystem called initoverlayfs.
> > It is a new filesystem that provides a more scalable approach to
> > initial
motive-sig/next
dnf install initoverlayfs
initoverlayfs-install
Is mise le meas/Regards,
Eric Curtin
eport it there (done by adding in cc here). They did
not specify LISTEN_FDNAMES at the time LISTEN_PID was first
documented, so the likelihood of libnbd not being the only application
that happens to leak inherited LISTEN_FDNAMES through to the child
process is non-zero, where this sort of bug will bite more than one
client of systemd socket activation. And it is this sort of
backwards-incompatibility caused by the systemd extension that they
will need to be more careful of avoiding if they ever add any future
LISTEN_* environment variables.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
sword, this is also a bad situation.
Is it possible to add more than one password ?
/eric
Thanks for your answer.
After some research, it seems that issue is already registered and fixed :
https://github.com/systemd/systemd/issues/23410
BR,
Eric
-Message d'origine-
De : systemd-devel De la part de
Colin Guthrie
Envoyé : mercredi 28 septembre 2022 18:18
À : systemd-
x
2d1.device
Jun 17 09:21:33 b-0021 systemd[1]: tank.service: tank.service lost
dependency
ReferencedBy=sys-devices-platform-soc-210.bus-2184000.usb-ci_hdrc.0-usb1
-1\x2d1.device
Best regards
---
Eric-Olivier Perrin
<mailto:eric-olivier.per...@sysnav.fr> eric-olivier.per...@sy
Hi, thought I would try again...
eric
On 3/11/20 2:37 PM, Eric DeVolder wrote:
Systemd-devel,
Below is a proposal for adding a couple of settings to the systemd pstore
service so that it can enable the kernel parameters that allow the
kernel to write into the pstore.
Regards,
eric
From
Systemd-devel,
Below is a proposal for adding a couple of settings to the systemd pstore
service so that it can enable the kernel parameters that allow the
kernel to write into the pstore.
Regards,
eric
From 837d716c6e7ed02518a399356df95bf7c47e1772 Mon Sep 17 00:00:00 2001
From: Eric DeVolder
Hi Lennart,
I've applied the coding style guidelines, and created a pull request
#12768 via GitHub. Let me know what I may have done wrong, my first
attempt via GitHub.
Thanks,
eric
On 5/16/19 9:34 AM, Lennart Poettering wrote:
On Do, 16.05.19 09:28, Eric DeVolder (eric.devol...@oracl
OK, will do!
eric
On 5/16/19 9:34 AM, Lennart Poettering wrote:
On Do, 16.05.19 09:28, Eric DeVolder (eric.devol...@oracle.com) wrote:
Could you please submit this via github as PR? Review is so much nicer
there, in particular for complex patch sets, and this qualifies as
complex I think. This
time
- This intended to be an early look/review to ensure I'm headed down
the desired path per maintainers.
---
v1 16may2019
- sent to systemd-devel@lists.freedesktop.org for early/initial review
Eric DeVolder (6):
pstore: Add new pstore tool/service to the build
pstore: Add new pstore
ts. The default
is "/var/lib/systemd/pstore".
- AllowUnlink : is one of "yes" or "no". When "yes", the default, then
files in the pstore are removed once processed. When "no", processing
of the pstore occurs normally, but the pstor
determine which dmesg it is a part
- the file is either moved to archive storage or recorded in the journal
- the file is appended to the reconstructed dmesg
Signed-off-by: Eric DeVolder
---
src/pstore/pstore.c | 736
1 file changed, 736
This new file is invoked by the build system to build pstore.
Signed-off-by: Eric DeVolder
---
src/pstore/meson.build | 21 +
1 file changed, 21 insertions(+)
create mode 100644 src/pstore/meson.build
diff --git a/src/pstore/meson.build b/src/pstore/meson.build
new file
The xml file for the systemd pstore tool configuration file.
Signed-off-by: Eric DeVolder
---
man/pstore.conf.xml | 100
1 file changed, 100 insertions(+)
create mode 100644 man/pstore.conf.xml
diff --git a/man/pstore.conf.xml b/man
The necessary systemd service file which invokes the pstore
archival tool upon boot as well as shutdown (poweroff, reboot).
Signed-off-by: Eric DeVolder
---
units/systemd-pstore.service.in | 32
1 file changed, 32 insertions(+)
create mode 100644 units/systemd
This change adds the src/pstore directory to the build files.
Signed-off-by: Eric DeVolder
---
meson.build | 29 +
meson_options.txt | 2 ++
units/meson.build | 1 +
3 files changed, 32 insertions(+)
diff --git a/meson.build b/meson.build
index eaf0edd
s, I apologize. If there is
a recommended developer reading (my google searches turned up mostly
user-perspective hits), I'd greatly appreciate a pointer.
Also, I have other tasks on my plate, so I am working on this but not as
my sole priority.
Lennart,
I've some homework to do based on your feedback and will report back. As
I understand it, I need to do this in C as well.
Regards,
eric
On 1/15/19 12:49 PM, Lennart Poettering wrote:
On Di, 15.01.19 11:23, Eric DeVolder (eric.devol...@oracle.com) wrote:
Systemd-devel,
Below
your time,
Eric
Oracle ERST usage
The BIOS ACPI error record serialization table, ERST, is an API for
storing data into non-volatile storage, such as hardware errors [1,
Section 18.5 Error Serialization]. The ERST non-volatile storage on
Oracle servers tends to be small, on the orde
sing hardware crypto accelerators, there is no need to call
into the kernel just to compute hashes. Or at the very least, make the
dependency optional.
Thanks!
- Eric
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.fre
o be dropped).
Certainly it has been that way for quite a while now.
Except for the negative acl aspect there are no issues with dropping
groups, as setgroups will limit you to the groups allowed in your user
namespace.
Eric
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
---
src/basic/util.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/basic/util.c b/src/basic/util.c
index 727be56..906e4ab 100644
--- a/src/basic/util.c
+++ b/src/basic/util.c
@@ -3627,7 +3627,7 @@ bool string_is_safe(const char *p) {
if (*t > 0 && *t < '
On 06/17/2015 12:34 PM, Lennart Poettering wrote:
> On Mon, 18.05.15 18:45, Eric Cook (l...@gmx.com) wrote:
>
>> By the time __systemctl is called, --user/--system are shifted out of
>> `words' by _arguments. This patch queries the array sooner.
>>
>> In the
Thomasz,
Really appreciate your helps. It works perfectly now after taking your
instructions.
--Regards,Eric Lu
On Sunday, June 14, 2015 2:39 AM, Tomasz Torcz
wrote:
On Sat, Jun 13, 2015 at 10:39:24PM -0700, Eric Lu wrote:
> Hi,
>
>
>
> I tested the f
/tst.path
-/usr/sbin/tst.sh
Any help is greatly appreciated.
--
Regards,
Eric Lu
[ylu@f21 ~]$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.17.4-301.fc21.x86_64 root=/dev/mapper/fedora-root ro
rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
using _wanted instead of calling compadd directly. this allows the user to
customize
possible matches.
An example being, grouping units by type:
autoload -Uz compinit; compinit
zstyle ':completion:*' menu select
zstyle ':completion:*' group-name ''
zstyle ':completion:*' format 'Completing %d'
zs
By the time __systemctl is called, --user/--system are shifted out of
`words' by _arguments. This patch queries the array sooner.
In the case that both --user and --system are on the line when compsys runs,
_sys_service_mgr is set to the latter. Which is seemingly how systemctl behaves.
If neith
I seem to have forgot about _systemctl_active_units().
---
shell-completion/zsh/_systemctl.in | 30 ++
1 file changed, 14 insertions(+), 16 deletions(-)
diff --git a/shell-completion/zsh/_systemctl.in
b/shell-completion/zsh/_systemctl.in
index a4db563..d3e7ee2 100644
---
shell-completion/zsh/_systemctl.in | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/shell-completion/zsh/_systemctl.in
b/shell-completion/zsh/_systemctl.in
index cce9dea..8764e07 100644
--- a/shell-completion/zsh/_systemctl.in
+++ b/shell-completion/zsh/_systemctl.
---
shell-completion/zsh/_systemctl.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/shell-completion/zsh/_systemctl.in
b/shell-completion/zsh/_systemctl.in
index f30fb84..5a39cfb 100644
--- a/shell-completion/zsh/_systemctl.in
+++ b/shell-completion/zsh/_systemctl.in
@@ -14
---
shell-completion/zsh/_systemctl.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/shell-completion/zsh/_systemctl.in
b/shell-completion/zsh/_systemctl.in
index 5a39cfb..a4db563 100644
--- a/shell-completion/zsh/_systemctl.in
+++ b/shell-completion/zsh/_systemctl.in
@@
compadd's -a option treats non-option arguments as arrays. So
$(_systemctl_get_template_names) expands to some words that aren't
legal array names. Even if there were, they would be empty; thus adding
nothing.
deduplicated a few functions too.
---
shell-completion/zsh/_systemctl.in | 21 +
---
shell-completion/zsh/_systemctl.in | 28 +---
1 file changed, 13 insertions(+), 15 deletions(-)
diff --git a/shell-completion/zsh/_systemctl.in
b/shell-completion/zsh/_systemctl.in
index a4db563..d2ebab0 100644
--- a/shell-completion/zsh/_systemctl.in
+++ b/shell-comp
---
shell-completion/zsh/_systemctl.in | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/shell-completion/zsh/_systemctl.in
b/shell-completion/zsh/_systemctl.in
index d2ebab0..9b7f962 100644
--- a/shell-completion/zsh/_systemctl.in
+++ b/shell-completion/zsh/_systemctl.i
Hi, I'm trying to sync my vps log to laptop. They are connected with
openvpn.
Both laptop and vps are,
- Arch Linux
- systemd 219-5
- vps: 10.8.0.1
- laptop: 10.8.0.6
It is already secured by openvpn tunnel. So I tried with normal http
settings. Services are launched successfully. There is noth
lity system
things wind up being more maintainable.
Eric
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
removed pointless index sort of bootids.
use `compadd -a' to add each array, instead of expanding possibly hundreds of
words needlessly.
optional completion of -b
---
shell-completion/zsh/_journalctl | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/shell-completion/zsh
This fixes the issue noted by Zbigniew in most cases.
if a unit's name is enclosed in single quotes completion still
will not happen after the first `\'.
---
shell-completion/bash/systemctl.in | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/shell-completion/bash/s
On 07/26/2014 07:52 PM, Zbigniew Jędrzejewski-Szmek wrote:
> Unfortunately it works only partially. It seems that completions are generated
> properly, but bash doesn't seem to be able to continue after a backslash,
> so one has to copy in the remaining part by hand.
>
> Zbyszek
Hm... (I think)Once
This looks seems like it should work. I would appreciate it if you could trail
run it.
My use of bash is limited and knowledge of it's completion system even more so.
---
shell-completion/bash/systemctl.in | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/shell-
Units with literal hex '\xFF' in their names has to be read
and printed properly.
dev-disk-byx2dlabel-root.device != dev-disk-by\x2dlabel-root.device
---
shell-completion/zsh/_systemctl.in | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/shell-completion/z
I think the idea was
if we are not in the initrd - try to load policy
if we are in the initrd and we find selinux_path() - try to load policy
Thus embeded/thin who put everything inside the initrd will work (and
the kernel enforce=1 will mean what is should)
And where we don't put anything inside
I like it, if it's reasonable/possible
On Thu, Feb 20, 2014 at 2:26 PM, Lennart Poettering
wrote:
> On Thu, 20.02.14 13:50, Eric Paris (epa...@parisplace.org) wrote:
>
>> Not really. If it doesn't exist on the final root fs and I put
>> enforcing=1 on the comma
Not really. If it doesn't exist on the final root fs and I put
enforcing=1 on the command line, I expect the box to
panic/fail/die/whatever
On Thu, Feb 20, 2014 at 1:36 PM, Lennart Poettering
wrote:
> On Thu, 20.02.14 18:17, Colin Walters (walt...@verbum.org) wrote:
>
> Hmm, maybe a simple c
have been the same.
The network namespace are all about communicating between network
namespaces and that is what was allowed here.
If you don't want a socket or a fifo or any other file to be used by a
container don't give it access to it. It really is
Gao feng writes:
> cc libvirt-list
>
> On 08/21/2013 01:30 PM, Eric W. Biederman wrote:
>> Gao feng writes:
>>
>>> Unix sockets are private resources of net namespace,
>>> allowing one net namespace to access to other netns's unix
>>> sock
own -h now
There are more compelling uses and there is no cost in supporting this
in the kernel.
What kind of misconfiguration caused someone to complain about this?
> We should make sure unix sockets are per net namespace to
> avoid this problem.
Nacked-by: "Eric W. Biederm
Zbigniew Jędrzejewski-Szmek writes:
> On Sun, Apr 21, 2013 at 09:18:34AM -0700, Eric W. Biederman wrote:
>> Zbigniew Jędrzejewski-Szmek writes:
>>
>> > On Sat, Apr 20, 2013 at 03:27:46PM -0700, Eric W. Biederman wrote:
>> >> Zbigniew Jędrzejewski-Szmek wri
Zbigniew Jędrzejewski-Szmek writes:
> On Sat, Apr 20, 2013 at 03:27:46PM -0700, Eric W. Biederman wrote:
>> Zbigniew Jędrzejewski-Szmek writes:
>>
>> > Hi,
>> > I've hit a bit of a problem with nsenter and systemd-nspawn.
>> > When nsenter
recommend not typing "reboot & exit" instead
of "reboot" from a shell started with nsenter, and otherwise not leaving
processes with parents outside the pid namespace around.
Of course that seding SIGSTOP before sending SIGTERM seems mighty fishy
as well.
Eric
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Linus Torvalds writes:
> On Tue, Jan 31, 2012 at 4:44 AM, Eric W. Biederman
> wrote:
>>
>> The sensors update with the fix is scheduled for about a week out, well
>> before 3.3 ships.
>
> That's almost certainly *not* going to help.
>
> Guys, people d
ease. That seems like plenty of time for distros to get an update
package for sensors together.
Eric
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
by many quite
> mundane tools as an optimisation.
Those tools for a decade or better all know to treat nlink == 1 as the
case where the optimization does not apply.
On a traditional unix filesytem the most common place you will see nlink
== 1 is when the link count overflows. extN with >
ount indicating
>> number of subdirectories is a standard Unix thing and used by many quite
>> mundane tools as an optimisation.
>
> Ah, yeah, that is easier.
>
> Eric, care to fix this or want me to revert it?
With respect to sensors the conversation has already been had
On Wed, May 11, 2011 at 4:22 PM, Greg KH wrote:
> On Wed, May 11, 2011 at 04:14:32PM -0400, Eric Paris wrote:
>> On Wed, May 11, 2011 at 3:56 PM, Greg KH wrote:
>> > On Wed, May 11, 2011 at 10:14:40AM -0700, Casey Schaufler wrote:
>> >> I would prefer /sys/securit
ew one, I'd be glad to work with you to
> add anything you might need to securityfs first, but if that doesn't
> work out, then yes, you could use /sys/fs/ for your new one.
Pretty sure we already have a securty/smack/smackfs.c .
-Eric
_
On Wed, May 11, 2011 at 12:35 PM, Eric Paris wrote:
> On Tue, May 10, 2011 at 6:34 PM, Greg KH wrote:
>>
>> From: Greg Kroah-Hartman
>>
>> In the interest of keeping userspace from having to create new root
>> filesystems all the time, let's follow the lead
or it in sysfs.
>
> For selinuxfs, this mount point should be in /sys/fs/selinux/
>
> Cc: Stephen Smalley
> Cc: James Morris
> Cc: Eric Paris
> Cc: Lennart Poettering
> Cc: Daniel J Walsh
> Signed-off-by: Greg Kroah-Hartman
security/selinux/selinuxfs.c: In functio
On Wed, May 11, 2011 at 11:13 AM, Stephen Smalley wrote:
> On Wed, 2011-05-11 at 10:58 -0400, Eric Paris wrote:
>> On Wed, May 11, 2011 at 10:54 AM, John Johansen
>> > AppArmor, Tomoyo and IMA all create their own subdirectoy under securityfs
>> > so this should not
ectory? They have their own subdirs in
>>>> there, or both just use the securityfs infrastructure and not their
>>>> own filesystem on top?
>>>
>>> Only one security module is allowed to be loaded/active at any one point
>>> in time, so they can
space from having to create new root
> > > filesystems all the time, let's follow the lead of the other in-kernel
> > > filesystems and provide a proper mount point for it in sysfs.
> > >
> > > For selinuxfs, this mount point should be in /sys/fs/selinux/
> > &
s. I see that it used a u64
for a3 and a4 when these are only going to be 32 values. Does that
matter? I also see that some prototype such as sys32_readahead()
explicitly added a pad into the 32 helper. Should we be doing that? I
also notice that the naming of arguments seems wrong (although it
shouldn't matter)
SYSCALL_DEFINE6(32_fanotify_mark, int, fanotify_fd, unsigned int, flags,
u64, a3, u64, a4, int, dfd, const char __user *, pathname)
I would have thought equivalently:
fanotify_fd == a0
flags == a1
'a3' == a2
'a4' == a3
dfd == a4
etc.
Anyway, no idea if it is related, but I thought I designed the
systemcall with this padding in mind.
-Eric
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
79 matches
Mail list logo