From: Isaac Dunham <ibid.ag@gmail.com>
To: Bruce Dubbs <bruce.dubbs@gmail.com>
Cc: Bernhard Voelker <mail@bernhard-voelker.de>, util-linux@vger.kernel.org
Subject: Re: fdisk
Date: Tue, 1 Sep 2015 18:29:51 -0700 [thread overview]
Message-ID: <20150902012950.GA1910@newbook> (raw)
In-Reply-To: <55E47EC8.1030904@gmail.com>
On Mon, Aug 31, 2015 at 11:20:24AM -0500, Bruce Dubbs wrote:
> Bernhard Voelker wrote:
> >On 08/31/2015 04:04 AM, Bruce Dubbs wrote:
> >>I have a question about (or a enhancement request) running fdisk. When
> >>asking to list known partition types, I get about 70 lines of output.
> >>Generally that would not be a problem, but I was running in a Debian
> >>install/rescue iso that uses busybox in a 25 line terminal. I do not
> >>have a way to scroll up and thus cannot see the first 40 or so partition
> >>types.
> >>
> >>Is there a way to use a pager for this? In this situation 'more' is
> >>available but 'less' is not. Otherwise I think an automatic pause every
> >>20 lines or so would be appropriate to build into the partition type
> >>listing.
> >
> >hmm, I'm getting 27 lines (at a maximum line length of 79 characters) as
> >output of the 'l' command here - even if I resize the xterm to 20x80
> >characters.
> >OTOH, the main help output via the 'm' command uses 38 lines. Shouldn't
> >you also have issues with that one in your environment?
>
> In a konsole terminal resized to
>
> # echo $LINES
> 25
> # fdisk --version
> fdisk from util-linux 2.26.2
>
> Yes, the main menu scrolls off the top do the topmost line is:
>
> n add a new partition
>
> but that is not a big problem in konsole because I can scroll back the
> buffer. The l command lists the partition types and the topmost line of the
> screen is entry number 44.
>
> The difficult problem is in busybox where there is no scroll back
> capability.
If you do not switch VTs, the Linux kernel has a limited "scroll back"
capability:
use <Shift>+<PgUp> or <Shift>+<PgDn>.
There are serious enough limitations to this that it's not really viable
except as a workaround:
-only things that have been on-screen after you last switched to the
current VT will be visible
-switch VTs, and you lose history
But it may be useful to you.
HTH,
Isaac Dunham
next prev parent reply other threads:[~2015-09-02 1:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 2:04 fdisk Bruce Dubbs
2015-08-31 6:56 ` fdisk Bernhard Voelker
2015-08-31 16:20 ` fdisk Bruce Dubbs
2015-09-02 1:29 ` Isaac Dunham [this message]
2015-08-31 10:06 ` fdisk Karel Zak
2015-09-02 2:07 ` fdisk Isaac Dunham
2015-09-02 8:01 ` fdisk Karel Zak
-- strict thread matches above, loose matches on Subject: below --
2011-06-24 18:25 fdisk Bruce Dubbs
2011-06-27 14:21 ` fdisk Karel Zak
2011-06-27 19:27 ` fdisk Mike Frysinger
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=20150902012950.GA1910@newbook \
--to=ibid.ag@gmail.com \
--cc=bruce.dubbs@gmail.com \
--cc=mail@bernhard-voelker.de \
--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