From: Dennis Schridde <devurandom-hi6Y0CQ0nG0@public.gmane.org>
To: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/2] [99fs-lib] Create generic mount framework
Date: Thu, 11 Apr 2013 18:10:54 +0200 [thread overview]
Message-ID: <1645019.IW4GTDGkzb@ernie> (raw)
In-Reply-To: <5166DB40.7040108-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
Am Donnerstag, 11. April 2013, 17:48:16 schrieb Harald Hoyer:
> Am 11.04.2013 17:39, schrieb Dennis Schridde:
> > * Utilises fstab.{early,late} files in /etc
> > * Provides fs_add_mount function to mount in pre-mount (early) and
> > pre-pivot (late) phases * Code to mount a fstab file is moved over from
> > 95fstab-sys
> > ---
>
> Why not make use of fstab and fstab of the real root?
>
> /etc/fstab in the initramfs == fstab.early
> $NEWROOT/etc/fstab == fstab.late
I want to mount depending on the cmdline arguments of the kernel.
Basically, what I need is a way to guarantee certain devices/directories to be
mounted before dracut tries to mount the rootfs.
Also, the mountpoints are inside the initramfs, not inside the rootfs. So
having them in the rootfs' fstab (when the mountpoints do not exist there),
seems wrong.
For testing it was extremely helpful that I could provide these devices on the
cmdline, because the initramfs takes quite a while to build on my machines, so
replacing a file inside them each time I tried to get the path right would
have been cumbersome.
> In systemd we introduced "x-initrd.mount" as a mount option, to mark those
> mount entries from $NEWROOT/etc/fstab to be mounted in pre-pivot.
I assume there is nothing (yet) that mounts entries before the rootfs gets
mounted?
--Dennis
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-04-11 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 15:39 [PATCH 1/2] [99fs-lib] Create generic mount framework Dennis Schridde
[not found] ` <1365694762-7806-1-git-send-email-devurandom-hi6Y0CQ0nG0@public.gmane.org>
2013-04-11 15:39 ` [PATCH 2/2] [99fs-lib] Provide fs_mount_to_var utility function to parse /path:type:/dev,options style mountspecs Dennis Schridde
[not found] ` <1365694762-7806-2-git-send-email-devurandom-hi6Y0CQ0nG0@public.gmane.org>
2013-04-11 15:48 ` Dennis Schridde
2013-04-11 15:48 ` [PATCH 1/2] [99fs-lib] Create generic mount framework Harald Hoyer
[not found] ` <5166DB40.7040108-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-04-11 16:10 ` Dennis Schridde [this message]
2013-05-17 16:22 ` Dennis Schridde
2013-05-17 16:17 ` [PATCH 1/2] [40network] Add variable parsing framework for network related variables Dennis Schridde
[not found] ` <1368807440-9207-1-git-send-email-devurandom-hi6Y0CQ0nG0@public.gmane.org>
2013-05-17 16:17 ` [PATCH 2/2] [40network] Provide a hostname fallback function, in case there is no executable of this name Dennis Schridde
2013-05-17 16:22 ` [PATCH 1/2] [40network] Add variable parsing framework for network related variables Dennis Schridde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1645019.IW4GTDGkzb@ernie \
--to=devurandom-hi6y0cq0ng0@public.gmane.org \
--cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.