[SOLVED] Access to Slackware and/or to the Slackware installer through a serial line, anyone?
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.
Access to Slackware and/or to the Slackware installer through a serial line, anyone?
Does anyone access one's Slackware system through a serial line (from a "real" terminal if that still exists, a Braille display, another type of device or another computer)?
Is it enough to uncomment the lines beginning with ttyS{0,1} in /etc/inittab and (re)boot?
Same question for starting the Slackware installer (in this case unpack the initramfs, make the change and repack it, I assume).
Other question: as I do not have such hardware, how should I set one or two VMs to test and try?
Thanks in advance for reporting from your experience and for any clue or advice.
Last edited by Didier Spaier; 02-07-2016 at 04:47 PM.
Does anyone access one's Slackware system through a serial line (from a "real" terminal if that still exists, a Braille display, another type of device or another computer)?
Is it enough to uncomment the lines beginning with ttyS{0,1} in /etc/inittab and (re)boot?
Same question for starting the Slackware installer (in this case unpack the initramfs, make the change and repack it, I assume).
Other question: as I do not have such hardware, how should I set one or two VMs to test and try?
Thanks in advance for reporting from your experience and for any clue or advice.
I'll see what I can do for #3. I haven't had to deal with serial ports for communication is a while.
For #3: I use a combination of virt-manager , libvirt and qemu+KVM for virtual machines. Create a new virtual machine, add a virtual console to your domain's XML file either through command line or using the virt-manager UI, and follow the guide posted by stoa to enable it in Slackware as well. You can then do:
Code:
root@omega:~ # virsh list
Id Name State
----------------------------------------------------
1 mumble.localdomain running
2 kanboard.localdomain running
root@omega:~ # virsh console kanboard.localdomain
Connected to domain kanboard.localdomain
Escape character is ^]
Welcome to Linux 3.10.17 (ttyS0)
kanboard login:
Does anyone access one's Slackware system through a serial line (from a "real" terminal if that still exists, a Braille display, another type of device or another computer)?
Is it enough to uncomment the lines beginning with ttyS{0,1} in /etc/inittab and (re)boot?
Same question for starting the Slackware installer (in this case unpack the initramfs, make the change and repack it, I assume).
Other question: as I do not have such hardware, how should I set one or two VMs to test and try?
Thanks in advance for reporting from your experience and for any clue or advice.
Yes the Slackware installer on ARM runs via the serial console. All of the installation documents explain how it's done. I think all of the changes I made were sent back to the x86 branch, so the x86 one should also work as-is.
/etc/inittab from the 'a/etc/' package also needs to have ttyS0 uncommenting so that you can login once the OS boots:
Eventually I used a VirtualBox VM, set up as in the attached pic.
I built and installed 'socat' from http://slackbuilds.org, then started the Slackware installer in the VM appending "console=ttyS0" to the command line as suggested... by our BDFL as the first item of the installation FAQ (do I feel ashamed not to have looked there at first? Yes I do!).
Then I issued this command from an xterm:
Code:
socat UNIX-CONNECT:/tmp/myvbox STDIO,rawer
and ... Bingo! I saw the messages from the installer in the xterm.
I need to make some tuning (e.g. the dialog boxes are black and white and I do not know yet how to switch to tty{2,3,4}), but I mark this thread as [SOLVED]
Last edited by Didier Spaier; 03-01-2016 at 01:42 AM.
Reason: s/in the fisrt place/at first/
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.