From: Marius Bakke <mbakke@fastmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 3/6] file-systems: Suppress fsck status completion bar.
Date: Mon, 07 Nov 2016 09:29:08 +0000 [thread overview]
Message-ID: <87mvhb8wpn.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <8760nzy8bj.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Hey!
>
> Marius Bakke <mbakke@fastmail.com> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> Marius Bakke <mbakke@fastmail.com> skribis:
>>>
>>>> * gnu/build/file-systems.scm (check-file-system): Drop "-C" argument
>>>> from fsck for compatibility with other fscks.
>>>
>>> Oh so fsck.ext2 would no longer show any kind of progress report?
>>> That’s annoying.
>>>
>>> Could we address it differently? Not sure how, though.
>>
>> We would have to provide a custom check-file-system procedure for each
>> detected file-system. That might be needed in the long run anyway, but I
>> think this is a worthwhile compromise for now.
>
> What about adding a one-argument procedure as the ‘check-procedure’
> field of <file-system>, with a sane default, like:
>
> (define (default-file-system-check file-system)
> #~(system* (string-append "fsck." #$(file-system-type file-system))
> …))
>
> ?
>
> In fact, that would also remove the need for the special case to add
> dosfstools to the initrd because we could simply write:
>
> (define (fat-file-system-check file-system)
> #~(system* #$(file-append vfatfsck/static "/bin/fsck.vfat")
> …))
>
> and that would automatically bring vfatfsck/static to the initrd when
> it’s needed, and only then.
>
> WDYT?
>
> (Same design pattern as ‘open’ in <device-mapping>.)
This looks very promising. Will try to make it work -- new patches
hopefully later this week! :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]
next prev parent reply other threads:[~2016-11-07 9:29 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 12:55 Initial vfat support Marius Bakke
2016-11-05 12:55 ` [PATCH 1/6] gnu: Add fatfsck-static Marius Bakke
2016-11-05 16:01 ` Hartmut Goebel
2016-11-05 16:11 ` Marius Bakke
2016-11-06 21:42 ` Ludovic Courtès
2016-11-05 12:55 ` [PATCH 2/6] linux-initrd: Support FAT filesystems Marius Bakke
2016-11-06 21:44 ` Ludovic Courtès
2016-11-05 12:55 ` [PATCH 3/6] file-systems: Suppress fsck status completion bar Marius Bakke
2016-11-06 21:47 ` Ludovic Courtès
2016-11-07 0:00 ` Marius Bakke
2016-11-07 8:59 ` Ludovic Courtès
2016-11-07 9:29 ` Marius Bakke [this message]
2016-11-07 10:15 ` Danny Milosavljevic
2016-12-17 9:40 ` Marius Bakke
2016-12-18 10:57 ` Ludovic Courtès
2016-11-05 12:55 ` [PATCH 4/6] gnu: Add efivar Marius Bakke
2016-11-06 21:51 ` Ludovic Courtès
2016-11-05 12:55 ` [PATCH 5/6] gnu: Add efibootmgr Marius Bakke
2016-11-06 21:52 ` Ludovic Courtès
2016-11-05 12:55 ` [PATCH 6/6] gnu: Add grub-efi Marius Bakke
2016-11-05 18:58 ` Leo Famulari
2016-11-05 19:38 ` Marius Bakke
2016-11-06 22:00 ` Ludovic Courtès
2016-11-07 0:19 ` Marius Bakke
2016-11-07 9:00 ` Ludovic Courtès
2016-11-07 9:23 ` Marius Bakke
2016-12-16 17:09 ` Ludovic Courtès
2016-12-16 17:16 ` Danny Milosavljevic
2016-12-16 17:33 ` Marius Bakke
2016-12-18 10:54 ` Ludovic Courtès
2016-12-18 14:36 ` Marius Bakke
2016-12-19 10:48 ` Ludovic Courtès
2016-12-19 15:49 ` Marius Bakke
2016-12-19 21:16 ` Ludovic Courtès
2016-12-19 22:48 ` Marius Bakke
2016-12-20 13:53 ` Ludovic Courtès
2016-12-20 14:42 ` Marius Bakke
2016-12-20 16:53 ` Ludovic Courtès
2016-12-20 18:43 ` Marius Bakke
2016-12-21 9:12 ` Ludovic Courtès
2016-12-21 18:55 ` Danny Milosavljevic
2017-01-03 16:06 ` Ludovic Courtès
2017-01-03 16:16 ` Chris Marusich
2017-01-04 22:18 ` Ludovic Courtès
2016-12-17 9:38 ` Marius Bakke
2016-12-17 10:15 ` Marius Bakke
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvhb8wpn.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).