unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian" <pelzflorian@pelzflorian.de>
To: "Zheng Junjie" <zhengjunjie@iscas.ac.cn>
Cc: 71940-done@debbugs.gnu.org
Subject: bug#71940: [PATCH] system: images: Add comment how to enlarge visionfive2 root partition.
Date: Sun, 07 Jul 2024 11:03:24 +0200	[thread overview]
Message-ID: <47ea-668a5a00-95-4b04d800@255064684> (raw)
In-Reply-To: <47ea-66871e00-7f-4b04d800@255028912>

[-- Attachment #1: Type: text/plain, Size: 905 bytes --]


Hello Zheng, you are right: growpart indeed can properly enlarge my again newly bought, identical microSD card.  However this time, fdisk works too as described in upstream’s Quick Start Guide.  It appears the newly bought first microSD and the old microSD cards were somehow faulty as well.

Perhaps we could add a warning of faulty microSD cards, but actually this is not just about visionfive2.

We could add a comment to visionfive2.scm to use growpart, but I believe fdisk is not at fault, fdisk could be used just as well.  parted worked better than fdisk by chance.

We could remove unused modules from visionfive2.scm like in the patch, as reported by

$ guix shell guile-next
[env]$ guild compile -Wunused-module gnu/system/images/visionfive2.scm

but visionfive2.scm is not the only file in images with unused modules.

I just close this patch now.

Regards,
Florian
 

[-- Attachment #2: Type: text/html, Size: 1000 bytes --]

      reply	other threads:[~2024-07-07  9:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04 14:22 [bug#71940] [PATCH] system: images: Add comment how to enlarge visionfive2 root partition Florian Pelz
2024-07-04 15:11 ` pelzflorian
2024-07-04 15:43 ` Zheng Junjie
2024-07-04 22:10   ` pelzflorian
2024-07-07  9:03     ` pelzflorian [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

  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=47ea-668a5a00-95-4b04d800@255064684 \
    --to=pelzflorian@pelzflorian.de \
    --cc=71940-done@debbugs.gnu.org \
    --cc=zhengjunjie@iscas.ac.cn \
    /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).