public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Console scrollback
Date: Wed, 13 Jan 2021 10:55:18 +0000	[thread overview]
Message-ID: <7866302.T7Z3S40VBb@peak> (raw)
In-Reply-To: <4303403.LvFx2qVVIh@dell_xps>

On Wednesday, 13 January 2021 10:38:01 GMT Michael wrote:
> On Wednesday, 13 January 2021 10:30:19 GMT Peter Humphrey wrote:
> > Hello list,
> > 
> > I see that the kernel code to scroll the console has been stripped out
> > [1]. What do people use instead?
> > 
> > This loss is a nuisance while installing a new system, as I am still
> > trying to do on my old laptop.
> > 
> > 1.  https://soylentnews.org/article.pl?sid=20/09/15/1824233&from=rss
> 
> A relief to see I'm not alone in experiencing this problem - I thought I had
> misconfigured something on my systems. :-)
> 
> A way around it would be to use screen or tmux and use their internal
> buffer. However, if you're already logged in a console and suddenly want to
> Shift+PageUp, then it would be too late.  This suggestion won't help if you
> want to look at the rc scripts output as the system boots, but you can
> capture these separately in syslog.

It's a pain in the neck while trying to emerge a base system and being thrown 
scores of lines of reasons why it can't be done, with the prime cause long 
gone. I tried using "| tee 2>&1 > /tmp/file" and then viewing the file on 
another vTTY, but there ought to be a neater way.

-- 
Regards,
Peter.





  reply	other threads:[~2021-01-13 10:55 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13 10:30 [gentoo-user] Console scrollback Peter Humphrey
2021-01-13 10:38 ` Michael
2021-01-13 10:55   ` Peter Humphrey [this message]
2021-01-13 11:21     ` Andreas Fink
2021-01-13 11:46       ` Peter Humphrey
2021-01-13 18:14 ` Alan Mackenzie
2021-01-13 18:44   ` Neil Bothwick
2021-01-14 16:00     ` Alan Mackenzie
2021-01-13 19:14   ` Peter Humphrey
2021-01-13 19:32   ` Grant Taylor
2021-01-13 21:56     ` Alan Mackenzie
2021-01-13 22:14       ` Grant Taylor
2021-01-14 16:39         ` karl
2021-01-13 22:15       ` [gentoo-user] " Grant Edwards
2021-01-13 23:01         ` Neil Bothwick
2021-01-13 23:06           ` Grant Edwards
2021-01-14  0:00             ` Grant Taylor
2021-01-14  1:25               ` Grant Edwards
2021-01-14 17:10                 ` Grant Taylor
2021-01-14  0:12             ` Neil Bothwick
2021-01-14 16:06         ` Alan Mackenzie
2021-01-16 12:01           ` Alan Mackenzie
2021-01-17  5:17             ` [gentoo-user] " Thomas Mueller
     [not found]             ` <20210117051748.E3239E0869@pigeon.gentoo.org>
2021-01-17  9:16               ` Philip Webb
     [not found]             ` <20210117051748.B8178E0863@pigeon.gentoo.org>
2021-01-19 17:09               ` Laurence Perkins
2021-01-20 19:59                 ` Alan Mackenzie
2021-01-21  9:32                   ` Wols Lists
2021-01-21  8:58                     ` Jorge Almeida
2021-01-21 12:40                       ` Remco Rijnders
2021-01-21 13:00                         ` Jorge Almeida
2021-01-25 12:42                     ` Alan Mackenzie
2021-04-02 18:30                   ` Alan Mackenzie
2021-04-02 19:32                     ` karl
2021-04-02 20:49                       ` Alan Mackenzie

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=7866302.T7Z3S40VBb@peak \
    --to=peter@prh.myzen.co.uk \
    --cc=gentoo-user@lists.gentoo.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