util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonny Grant <jg@jguk.org>
To: util-linux@vger.kernel.org
Cc: Karel Zak <kzak@redhat.com>
Subject: fdisk Ctrl+C
Date: Wed, 9 Jan 2019 18:01:18 +0000	[thread overview]
Message-ID: <9bf2cc25-1b6a-88ae-c293-7a613b1255d8@jguk.org> (raw)

Hello!

A few questions, ideas

1. Could Ctrl+C be added to get out of changing a partition type?

2 Could the partition code check that it is hex. At the moment if I type 
'q' I get partition type 0.

3.
For partition type 0, which is called "Empty" probably this message 
should say "Empty" and not 'unknown' ?

=======
Changed type of partition 'W95 FAT32 (LBA)' to 'unknown'.
=======

Would a patch be accepted for this?


NB. See log below for more info.

Regards, Jonny




$ fdisk --version
fdisk from util-linux 2.31.1


# fdisk /dev/sdb

Welcome to fdisk (util-linux 2.31.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/sdb: 114.6 GiB, 123010547712 bytes, 240254976 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdb1          32 240254975 240254944 114.6G  c W95 FAT32 (LBA)

Command (m for help): t
Selected partition 1
Hex code (type L to list all codes): ^CHex code (type L to list all codes):


Hex code (type L to list all codes): q
Type 0 means free space to many systems. Having partitions of type 0 is 
probably unwise.

Changed type of partition 'W95 FAT32 (LBA)' to 'unknown'.

Command (m for help):


             reply	other threads:[~2019-01-09 18:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 18:01 Jonny Grant [this message]
2019-01-10 11:22 ` fdisk Ctrl+C Karel Zak
2019-01-10 12:22   ` Jonny Grant

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=9bf2cc25-1b6a-88ae-c293-7a613b1255d8@jguk.org \
    --to=jg@jguk.org \
    --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 NNTP newsgroup(s).