Upgrade from 11.0 to 12.0 *without* console access - possible??
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.
Upgrade from 11.0 to 12.0 *without* console access - possible??
Greetings,
Anyone know if it's possible to upgrade from Slackware 11.0 to 12.0 remotely without having physical console access? Ie having to either be logged in via an RS232 cable or an ssh session?
I have an IBM x335 server which requires a special KVM-cable for keyboard, video and mouse which I do not have - hence the question.
Having read the UPGRADE/CHANGES_AND_HINTS/etcyadayada this is clearly slightly off mainstream... However I've come down to two possible paths:
1. Try setting Slackware up to allow login via a serial cable in single-user mode
2. Try to write a shell-script to append to the rc.S script that does all the upgrades, fixes the .new files, and then reboots back in multi-use mode. However, one little mistake, and I'm locked out of my server - ie disaster-waiting-to-happen mode :P
Has anyone come across similar bizarre problems before? And even solved them?
Why not setup one of your slack boxen as a terminal to the IBM? As long as the Slack box has a com port that is compatible with the IBM and the Slack box presents the terminal protocol that the IBM wants then no problem.
Setting up as a terminal - is that the same as setting up console login? (yeah, I'm new to this) so that I can still be in singleuser mode without trouble, and no extra/special programs loaded?
If I understand the man page correctly, is this set up in the inittab only? If so - where (else) do I specify the communications parameters (ie parity bits etc) ?
Setting up as a terminal - is that the same as setting up console login? (yeah, I'm new to this) so that I can still be in singleuser mode without trouble, and no extra/special programs loaded?
If I understand the man page correctly, is this set up in the inittab only? If so - where (else) do I specify the communications parameters (ie parity bits etc) ?
-y1
Hi,
Try;
'screen /dev/ttyS0 19200 vt100'
Do a 'man screen' to understand the command. You should change the baud rate to the IBM's port rate. Hopefully your DB connectors and cable are setup properly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.