[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#178990: boot-floppies: more(1) or other pager for looking around



Package: boot-floppies
Version: +N/A; reported 2003-01-30
Severity: wishlist

(I'm reusing some boilerplate from a bug I just filed against anna.
Sorry if I'm boring you. Skip down to ***.)

I'm only just acquainting myself with the sarge installer CD which was
announced in this week's DWN. Sorry if I'm reporting a bug against the
wrong package; I could find no further instructions for where to
report problems with the overall layout of the installation system so
I'm hoping that boot-floppies is still more or less appropriate.
Apologies in advance if this is incorrect.

I burned the larger variant (83 meg image downloaded this morning from
http://gluck.debian.org/cdimage/testing/netinst/i386/sarge-i386-netinst.iso
which has a size of 87064576 bytes and is dated Jan 25 04:48) and
managed to boot it (which was tricky because I am using an old laptop
with only *either* a floppy or a CD drive -- but I digress :-)

***

There are obviously things which will be unfamiliar to someone who is
using the system for the first time, which is problematic especially
at this stage when you are requesting comments from new testers.
Furthermore, the lack of a more(1) or similar makes it challenging to
look at what's on the system, to just look around or to figure out why
a wedged install is not progressing.

I have been doing sed -n 1,24p etc on files that look interesting but
if I happen to look at a binary file, chances are it will shift the
console's character set into graphics mode and then I will have to
reboot in order to proceed (or drive blind, which is of course also an
alternative).

Do you think you could make room for a simple pager utility in the
bare base system? I believe it would be helpful for newcomers like
myself.

/* era */


-- System Information
Debian Release: 3.0
Kernel Version: Linux there.afraid.org 2.2.20 #1 SMP Thu Nov 7 16:15:53 EET 2002 i586 unknown



Reply to: