public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: claudius.heine.ext@siemens.com
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [PATCH 0/3] Filesystem mounting and machine-id fix
Date: Tue, 28 May 2019 10:58:11 +0200	[thread overview]
Message-ID: <20190528085814.12967-1-claudius.heine.ext@siemens.com> (raw)

From: Claudius Heine <ch@denx.de>

Hi,

here is a small patchset that removes the fstab and the machine-id file.

The fstab generation is much to inflexible and in its current form unnecessary.
If it comes back in the future, then we should think about a good user API.

As a result of the removal, I added a few 'rw' kernel arguments to the meta-isar
wks files. I haven't touched the wks files from `scripts` yet, because I don't
really know how/if those scripts are used downstream and would like an input
from the community about this. When I use wic, I tend to write custom wks files.

The machine-id removal is pretty simple and systemd will recreate it on first
boot, but that requires a rw /etc directory. (Some exceptions possible, see
systemd-machine-id-commit.service(8).)

The machine-id patch can be applied without the first two patches.

regards,
Claudius

Claudius Heine (3):
  wks: added 'rw' to kernel arguments
  image.bbclass: remove fstab generation
  image-postproc-extension: add removal of machine-id

 .../scripts/lib/wic/canned-wks/bananapi.wks      |  2 +-
 .../lib/wic/canned-wks/directdisk-isar.wks       |  2 +-
 .../scripts/lib/wic/canned-wks/sdimage-efi.wks   |  2 +-
 meta/classes/image-postproc-extension.bbclass    | 11 +++++++++--
 meta/classes/image.bbclass                       | 16 ----------------
 5 files changed, 12 insertions(+), 21 deletions(-)

-- 
2.20.1


             reply	other threads:[~2019-05-28  8:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28  8:58 claudius.heine.ext [this message]
2019-05-28  8:58 ` [PATCH 1/3] wks: added 'rw' to kernel arguments claudius.heine.ext
2019-05-28 17:29   ` Henning Schild
2019-05-29  6:38     ` Claudius Heine
2019-05-28  8:58 ` [PATCH 2/3] image.bbclass: remove fstab generation claudius.heine.ext
2019-05-28 17:34   ` Henning Schild
2019-05-29  6:47     ` Claudius Heine
2019-05-29 11:11       ` Henning Schild
2019-05-28  8:58 ` [PATCH 3/3] image-postproc-extension: add removal of machine-id claudius.heine.ext
2019-05-28 17:44   ` Henning Schild
2019-05-29  7:00     ` Claudius Heine
2019-05-29 11:06       ` Henning Schild
2019-05-28 19:51   ` Henning Schild
2019-05-29  7:00     ` Matthias Luescher
2019-05-29  7:06       ` Claudius Heine
2019-06-06 17:18   ` Maxim Yu. Osipov
2019-06-04 20:09 ` [PATCH 0/3] Filesystem mounting and machine-id fix Maxim Yu. Osipov
2019-06-05  6:45   ` Claudius Heine

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=20190528085814.12967-1-claudius.heine.ext@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=ch@denx.de \
    --cc=isar-users@googlegroups.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox