Util-Linux Archive mirror
 help / color / mirror / Atom feed
From: Stanislav Brabec <sbrabec@suse.cz>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] Mention systemd implementation of fsck
Date: Sat, 17 Feb 2024 21:01:07 +0100	[thread overview]
Message-ID: <ed954c2e-8ae4-4133-874a-682c0c1fe20c@suse.cz> (raw)
In-Reply-To: <20240215093755.557tkkvtcnshaot4@ws.net.home>

Dne 15. 02. 24 v 10:37 Karel Zak napsal(a):
> On Wed, Feb 14, 2024 at 03:23:45PM +0100, Karel Zak wrote:
>> What about:
>>
>> systemd does not invoke fsck -A to check all devices; instead, it
>> calls fsck individually for devices selected based on the logic
>> implemented in systemd-fsck.
> I had short discussion about it with Lennart, and he suggested not to
> document anywhere systemd-fsck as it's private systemd stuff. I have
> pushed to repository:
>
>    https://github.com/util-linux/util-linux/commit/9cb7b7671d903573d6c3b9d8112ec13953cdcdc6
It sound clear. I didn't want to document any details of the
implementation in the third party package and it will not need an
update in case of an systemd change.

-- 
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                         e-mail: sbrabec@suse.com
Křižíkova 148/34 (Corso IIa)                    tel: +420 284 084 060
186 00 Praha 8-Karlín                          fax:  +420 284 084 001
Czech Republic                                    http://www.suse.cz/
PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76


      reply	other threads:[~2024-02-17 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 12:17 [PATCH] Mention systemd implementation of fsck Stanislav Brabec
2024-02-14 14:23 ` Karel Zak
2024-02-15  9:37   ` Karel Zak
2024-02-17 20:01     ` Stanislav Brabec [this message]

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=ed954c2e-8ae4-4133-874a-682c0c1fe20c@suse.cz \
    --to=sbrabec@suse.cz \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).