Am 15.03.2013 00:52, schrieb har...@redhat.com:
> From: Harald Hoyer
>
> First, rename root-fs.target to initrd-root-fs.target to clarify its usage.
>
> Mount units with "x-initrd-rootfs.mount" are now ordered before
> initrd-root-fs.target. As we sometimes construct /sysroot mounts in
> /etc/fs
From: Harald Hoyer
First, rename root-fs.target to initrd-root-fs.target to clarify its usage.
Mount units with "x-initrd-rootfs.mount" are now ordered before
initrd-root-fs.target. As we sometimes construct /sysroot mounts in
/etc/fstab in the initrd, we want these to be mounted before the
init
From: Harald Hoyer
First, rename root-fs.target to initrd-root-fs.target to clarify its usage.
Mount units with "x-initrd-rootfs.mount" are now ordered before
initrd-root-fs.target. As we sometimes construct /sysroot mounts in
/etc/fstab in the initrd, we want these to be mounted before the
init
From: Harald Hoyer
First, rename root-fs.target to initrd-root-fs.target to clarify its usage.
Mount units with "x-initrd-rootfs.mount" are now ordered before
initrd-root-fs.target. As we sometimes construct /sysroot mounts in
/etc/fstab in the initrd, we want these to be mounted before the
init
On Thu, Mar 14, 2013 at 01:39:15PM -0700, Lennart Poettering wrote:
> src/core/main.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> New commits:
> commit c1dae1b3c9729fb8ab749dd4e2dad07e0fad7ed8
> Author: Lennart Poettering
> Date: Thu Mar 14 21:36:38 2013 +0100
>
> main:
From: Harald Hoyer
First, rename root-fs.target to initrd-root-fs.target to clarify its usage.
Mount units with "x-initrd-rootfs.mount" are now ordered before
initrd-root-fs.target. As we sometimes construct /sysroot mounts in
/etc/fstab in the initrd, we want these to be mounted before the
init
From: Harald Hoyer
First, rename root-fs.target to initrd-root-fs.target to clarify its usage.
Mount units with "x-initrd-rootfs.mount" are now ordered before
initrd-root-fs.target. As we sometimes construct /sysroot mounts in
/etc/fstab in the initrd, we want these to be mounted before the
init
Hi Zbyszek,
- Original Message -
> Maybe just stick it in mount_setup()?
Thank you for this suggestion!
>
> It seems to be without much difference, but I'd go for /run, since
> this way there'll be less chance that somebody deletes it by mistake.
I first tried /tmp and I had issue that
All Execs within the service, will get mounted the same
/tmp and /var/tmp directories, if service is configured with
PrivateTmp=yes. Temporary directories are cleaned up by service
itself in addition to systemd-tmpfiles. Directory which is mounted
as inaccessible is created at runtime in /run/syste
---
configure.ac |9 +
units/debug-shell.service.in |4 ++--
2 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/configure.ac b/configure.ac
index 28d7286..75bda8a 100644
--- a/configure.ac
+++ b/configure.ac
@@ -742,6 +742,15 @@ AS_IF([test "x$enable_ke
On Thu, Mar 14, 2013 at 2:07 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Thu, Mar 14, 2013 at 11:43:32AM +0100, Michal Sekletár wrote:
>> Do you prefer to have it /run or in /tmp?
> It seems to be without much difference, but I'd go for /run, since this
> way there'll be less chance that somebody
On Thu, Mar 14, 2013 at 11:43:32AM +0100, Michal Sekletár wrote:
> On Thu, Mar 14, 2013 at 3:33 AM, Zbigniew Jędrzejewski-Szmek
> wrote:
> > Hi,
> >
> > Colin Walters wrote
> >>> install-directories-hook:
> >>> $(MKDIR_P) $(addprefix $(DESTDIR),$(INSTALL_DIRS))
> >>> + $(MKDIR_P) -m 000
From: Harald Hoyer
First, rename root-fs.target to initrd-root-fs.target to clarify its usage.
Mount units with "x-initrd-rootfs.mount" are now ordered before
initrd-root-fs.target. As we sometimes construct /sysroot mounts in
/etc/fstab in the initrd, we want these to be mounted before the
init
From: Harald Hoyer
Mount units with "x-rootfs.mount" are now ordered before root-fs.target.
As we sometimes construct /sysroot mounts in /etc/fstab in the initrd,
we want these to be mounted before the root-fs.target is active.
---
src/fstab-generator/fstab-generator.c | 10 ++
1 file ch
Kay Sievers píše v Čt 14. 03. 2013 v 12:40 +0100:
> On Thu, Mar 14, 2013 at 9:55 AM, Vaclav Pavlin wrote:
> > From: Václav Pavlín
> >
> > When using readonly-root systemd-random-seed.service fails because
> > /var/lib/random-seed is not writable at the time. Adding
> > fedora-readonly.service to
On Thu, Mar 14, 2013 at 9:55 AM, Vaclav Pavlin wrote:
> From: Václav Pavlín
>
> When using readonly-root systemd-random-seed.service fails because
> /var/lib/random-seed is not writable at the time. Adding
> fedora-readonly.service to
> systemd-randomd-seed's After solves this issue - mentioned
On Thu, Mar 14, 2013 at 3:33 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> Hi,
>
> Colin Walters wrote
>>> install-directories-hook:
>>> $(MKDIR_P) $(addprefix $(DESTDIR),$(INSTALL_DIRS))
>>> + $(MKDIR_P) -m 000 $(addprefix $(DESTDIR),$(INACCESSIBLE_DIR))
>> Ugh. Can you make this /run/syst
2013/3/14 Vaclav Pavlin :
> From: Václav Pavlín
>
> When using readonly-root systemd-random-seed.service fails because
> /var/lib/random-seed is not writable at the time. Adding
> fedora-readonly.service to
> systemd-randomd-seed's After solves this issue - mentioned file is bind
> mounted as rw
From: Václav Pavlín
When using readonly-root systemd-random-seed.service fails because
/var/lib/random-seed is not writable at the time. Adding
fedora-readonly.service to
systemd-randomd-seed's After solves this issue - mentioned file is bind
mounted as rw before it is used.
https://bugzilla.re
19 matches
Mail list logo
