public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
	"[ext] Q. Gylstorff" <Quirin.Gylstorff@siemens.com>
Cc: isar-users@googlegroups.com,
	"[ext] Claudius Heine" <claudius.heine.ext@siemens.com>
Subject: Re: [PATCH] recipes-support: add fsck to initramfs
Date: Tue, 13 Aug 2019 17:01:16 +0200	[thread overview]
Message-ID: <389814ef-bbb9-32f7-e7b6-d5dba934bcaa@siemens.com> (raw)
In-Reply-To: <20190813163615.0edcfa7c@md1za8fc.ad001.siemens.net>

On 13.08.19 16:36, [ext] Henning Schild wrote:
> Well it looks like the problem is the missing fstab
> line. /usr/share/initramfs-tools/hooks/fsck is looking for that to
> decide which fsck to include.
> 
> There also seems to be /etc/fstab.d/*.fstab that can be used if we do
> not like touching the original fstab. I think Claudius once removed /
> from fstab claiming that it was not required.
> 
> The package you get from that changes content based on an image
> variable. That must not be done. The fstypes would have to become part
> of PN or PV ...
> 
> I think we should get that fstab line back.

/ is in fstab, but in a generic form. If you add a specific one, you easily 
start duplicating wic. It's a chicken-egg thing: You need the information during 
package installation, but you only have it after imaging.

BTW, there is enable-fsck for partially the same reason (there other is that you 
do want to control whether fsck is run in embedded scenarios).

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2019-08-13 15:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07  7:59 Q. Gylstorff
2019-08-13 14:36 ` Henning Schild
2019-08-13 15:01   ` Jan Kiszka [this message]
2019-08-14 16:31     ` Henning Schild
2019-08-19  7:00       ` Quirin Gylstorff
2019-08-22 13:07         ` [PATCH v2] " Q. Gylstorff
2019-09-04 12:32           ` Baurzhan Ismagulov
2019-08-13 15:31   ` [PATCH] " 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=389814ef-bbb9-32f7-e7b6-d5dba934bcaa@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Quirin.Gylstorff@siemens.com \
    --cc=claudius.heine.ext@siemens.com \
    --cc=henning.schild@siemens.com \
    --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