pure (non-GUI) terminals after recent years' changes?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I, too, had wondered what happened to scrollback in a non-GUI console. I always boot to a console and start a GUI with startx - but I sometimes to upgrades and stuff as root from the console.
Of course it was useful. And if you've ever built an LFS system, you'll know just how useful. You can do most of LFS in an xterm, but at the end, you have to boot your new system. And since it has a hand-built kernel, there's a lot that can go wrong with the boot, especially if it's your first time. How are you supposed to diagnose the problem if you can't scroll back?
Then you go on to BLFS. If you use a booted system to add all the stuff you need, the lack of scrolling could be a real problem when builds go wrong. You can get round that by working entirely in chroot from your old system using an xterm, but that seems to me rather a weird and artificial thing to have to do.
What I find strangest is that it was Linus himself who decided to sabotage the console.
Probably Fedora fault, they do not even have boot messages anymore on TTY1, only a logo screen between grub2 and gdm.
There's no use for scrollback on that kind of setup when TTY is hidden and it boots straight to X or wayland.
Since I've always liked to see the messages on boot, I miss the scrollback feature now too.
What I do now is dmesg > /tmp/output && mcedit /tmp/output so I can scroll, search or whatever.
That's very nice but where's the patch? All those links show, as far as I can see, is a lot of talk about it. I would be quite happy to try it out if someone here provided it, assuming that it works for the 5.15 kernel, which is what Slackware-15 uses. There's no real risk, Jan. It's just a matter of rebuilding the kernel from source using that patch and Patrick's config file, and putting it into an alternative stanza in your boot manager.
Edit: Found it. Now I need to get the kernel source. I prefer to do this in the early morning when it doesn't get in the way of my peak band allowance. I'll let this thread know when I've done it.
first time I noticed the scroll back not working, I thought there was suddenly something wrong with my computer. I really can't fathom what was going through Torvalds mind -- despite having read what he had to say about it.
New month, new download allowance, so I downloaded source for 5.15.19 (the official Slackware-15 kernel), patched it and built it using Patrick's config file. The patch ran without comment but the build took all day. And that's with 4 cores! I'd forgotten just how big a standard distro kernel is. When I build on LFS, I include only the drivers I need and it all completes in 3 hours, but I assume Pat's kernel is expertly tuned to Slackware so I felt safer using that.
I used "make oldconfig" and got asked just two questions, both about the console. That looks hopeful.
It's all on the ESP now and I shall try using it for tomorrow's boot.
It boots! No problem. As soon as I got to the login prompt, I scrolled back. The display is a bit odd; it sometimes jumps to a second column and then back again. In some places, you get two parallel columns. But it's all there, right back to the first line about the partitions on sda.
Actually 5.15.27 is now the official Slackware kernel, but I would like to get this working for Slackware-current: 5.17.3 (though I'm on 5.17.2 and haven't rebooted yet) and new kernels come regularly.
You're right. 5.15.27 is the one I normally use. I found 5.15.19 in the main Slack-15 repo but I realise now that I should have downloaded the one from patches.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.