| 1 |
On Wed, 13 Jan 2021 10:55:18 +0000 |
| 2 |
Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 3 |
|
| 4 |
> On Wednesday, 13 January 2021 10:38:01 GMT Michael wrote: |
| 5 |
> > On Wednesday, 13 January 2021 10:30:19 GMT Peter Humphrey wrote: |
| 6 |
> > > Hello list, |
| 7 |
> > > |
| 8 |
> > > I see that the kernel code to scroll the console has been stripped out |
| 9 |
> > > [1]. What do people use instead? |
| 10 |
> > > |
| 11 |
> > > This loss is a nuisance while installing a new system, as I am still |
| 12 |
> > > trying to do on my old laptop. |
| 13 |
> > > |
| 14 |
> > > 1. https://soylentnews.org/article.pl?sid=20/09/15/1824233&from=rss |
| 15 |
> > |
| 16 |
> > A relief to see I'm not alone in experiencing this problem - I thought I had |
| 17 |
> > misconfigured something on my systems. :-) |
| 18 |
> > |
| 19 |
> > A way around it would be to use screen or tmux and use their internal |
| 20 |
> > buffer. However, if you're already logged in a console and suddenly want to |
| 21 |
> > Shift+PageUp, then it would be too late. This suggestion won't help if you |
| 22 |
> > want to look at the rc scripts output as the system boots, but you can |
| 23 |
> > capture these separately in syslog. |
| 24 |
> |
| 25 |
> It's a pain in the neck while trying to emerge a base system and being thrown |
| 26 |
> scores of lines of reasons why it can't be done, with the prime cause long |
| 27 |
> gone. I tried using "| tee 2>&1 > /tmp/file" and then viewing the file on |
| 28 |
> another vTTY, but there ought to be a neater way. |
| 29 |
> |
| 30 |
|
| 31 |
|
| 32 |
How about this (works with bash, not sure about other shells): |
| 33 |
emerge |& less |
| 34 |
|
| 35 |
This should work with all shells: |
| 36 |
emerge 2>&1 | less |
| 37 |
|
| 38 |
Cheers |
| 39 |
Andreas |
Archives