SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
So my installation had been working great, and then this morning I had the brilliant idea to do an upgrade to current using slackpkg, well, I installed a series of packages like seamonkeysolibs and xf86 drivers and stuff, and I also checked off to upgrade bash. I believe that's where my problem is, after things started upgrading, slackpkg abruptly stopped with an upgradepkg error, and now whenever I try to do anything I get the:
Error: cannot execute /bin/sh executable not found
or something similar to that. But if you look /bin/sh is not there, and now that I've turned off my system I'm not going to be able to log back on. I also tried to chroot it from an install disk and it didn't work. Anyone have any ideas on how to help me out of this?
Distribution: Slint64-14.2rc on Lenovo Thinkpad W520
Well, as there is not so much difference between -13.0 and -current for now, my guess is you didn't choose the good mirror in /etc/slackpkg/mirrors, i.e. you chose a slackware64-current mirror instead of a slackware-current (or reverse if you started from a slackware64-13.0).
Not sure you can do better than save your important files using a rescue disk or live cd, then reinstall. If your /home directory is in its own partition you won't have to save its content, provided you do not format it during reinstall.
Last edited by Didier Spaier; 10-03-2009 at 07:27 AM.
I'll paraphrase a statement I made on IRC a moment ago:
You can break a system with slackroll, with swaret, with slapt-get, with slackpkg, and yes, even doing it "by hand" or "manually" or whatever you want to call it. In all but a small minority of cases, the tool is not to blame - it's user error, even if that error was failing to read and/or understand the documentation on how to use the tool properly.
Ultimately, shit will happen. It also happens to fly farther when using tools.
rworkman was right when he said that. Anyway, back to the point, you should make sure /bin/sh is a link to bash, and that bash exists and can be executed. You can recreate the link using a rescue disk and mounting your partitions, and you can chroot to the system to verify everything is in place and works normally. If not, you can use a USB disk to take packages from there and try to fix the problems and do the upgrade properly. Be sure to check the CHANGES_AND_HINTS.TXT file of every Slackware version you jump over to -current.