Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Distribution: SOLARIS/BSD-like, some Debian-like, some Arch-like, some GENTO-like, some RH-like, some slacky-like
Posts: 386
Rep:
slackware 14.2 repair installation
Hi everyone,
5.10.17
is there a way to fix a bad installation? I probably removed some packages or I did not installed properly or both and I have a next to nothing system, no ping/dhclient/slackpkg/wget/curl and so on. There are lots of packages in /var/log/packages mostly for X (X broken obviously)
installpkg and pkgtool works btw.
Tried upgradepkg --reinstall
no output
can not raise up network
I can fix it with a live media but I am wondering if this can be repaired as is. Thanks a lot!
Given the number of issues you mention, it's probably best to back up any crucial data to external media and reinstall, especially as you report that you cannot connect to your network. You might be able to repair it manually, but it's likely to be more effort than it's worth.
Just my two cents.
Last edited by frankbell; 07-18-2021 at 09:32 PM.
Reason: grammar
Distribution: SOLARIS/BSD-like, some Debian-like, some Arch-like, some GENTO-like, some RH-like, some slacky-like
Posts: 386
Original Poster
Rep:
I agree with you but I have another good standing slack on VM. I would like to spend some resources to try fixing this broken one as a learning experience. I am relatively new in BSD-like world therefore anything will be much appreciated. Thanks so much!
If you have a working Slackware, you can install missing packages in the crippled one by using installpkg with an alternative root. Either set $ROOT to the root directory of your shot system or use the --root option to set it.
Of course, and it is a lot simpler if the user has an idea of what the problem is but you list a number of possibilities. Since there are a number of possibilities, where would you start. Seems like this would result in frustration possibly w/o a solution.
Is your working Slackware on VM on the same computer on another OS?
Simplest solution would be a data backup and reinstall, select to not format the / partition during the install which should retain functioning software and personal data.
There is no learning experience here. Crashes time to time happen. But usually for different reasons. If you fix this now - it will not give you benefit in next crash. Learning experience is only in repetitive tasks. So save yourself time gaining worthless knowledge and reinstall system.
There is no learning experience here. Crashes time to time happen. But usually for different reasons. If you fix this now - it will not give you benefit in next crash. Learning experience is only in repetitive tasks. So save yourself time gaining worthless knowledge and reinstall system.
That is a rather negative attitude. Every experience is a learning experience. Every one of us learns from everything we do, whether it is one-off or repeated. Troubleshooting is a key part of learning and the OP has a "what not to do" and "how to fix" opportunity.
While I agree that the reinstall would be quickest and easiest, that is the lazy mans way of avoiding a challenge. The man already said he did things that broke the system so let him learn how to fix what was done instead of throwing water on his eagerness to learn.
Last edited by computersavvy; 07-19-2021 at 09:45 AM.
From your first post it looks like your missing packages from n and ap and maybe l. If you insist on attempting to fix without reinstalling the whole system, reinstall all of n and ap and maybe l using the install medium.
Last edited by colorpurple21859; 07-19-2021 at 09:38 AM.
That is a rather negative attitude. Every experience is a learning experience.
It is about gaining skills which can be used in solving some tasks. No skills here to learn. Because next crash will be for completely different reasons. So knowledge gained here will be useless. Even worse. It can misguide. Just accept things time to time happen.
Distribution: SOLARIS/BSD-like, some Debian-like, some Arch-like, some GENTO-like, some RH-like, some slacky-like
Posts: 386
Original Poster
Rep:
installpkg command is available but I can not connect to a mirror. I said ping command not found, the same dhclient.
The ultimate question: Is slackpkg upgrade-all safe? Is anything that can prevent to break the slack?
I wanted to perform a
Full system upgrade
To perform a full system upgrade, please follow these steps (as root user):
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.