[SOLVED] Mess Up On Installation. What Can I Do Right Now?
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.
Back to your last sentence "READ UP ON THE SUBJECT FIRST". For people who have some basic computer knowledge, a Linux installation process shall be intuitive. I didn't read any document other than the dual boot portion prior to install Linux Mint.
And if you want to install with some storage device, or from some media, or in some unique configuration like into a container image, or maybe onto x86 but not exactly PC hardware, etc the MINT installer is probably entirely unusable for you where large parts of Slackware's installer would still be helpful.
Nobody here is saying EVERYONE should use Slackware, and few here would say Slackware is the best option in ALL situations. Its like wood working sometimes a circular saw is all you need, other times a radial arm is very useful, but yes it requires more time to setup a cut and you should probably read the instructions first so you don't hurt yourself..Both things have their place.
While there are no doubt exceptions as general rule: The more flexible a tool is the more you need to know to use it, the more capable a tool is the great the harm mistakes can result in.
I guess that Slackware is for different people. For some, I can think of a statement something like "Linux is free as long as you don't value your time". Some people make videos on the topic published on youtube.
For some of us, it is actually more time consuming using other distros. Yes, Slackware is not a distro that will hold your hand and provide you fancy custom GUIs to help manage installation or packages. That is a turn off for some people and there's nothing wrong with not liking Slackware because of that.
But for many of us, it is nice to use the upstream tools to manage our systems rather than some custom GUI that the distro developed to manage everything. We're in charge of everything on our computers and Slackware doesn't try to shield us from shooting ourselves in the foot. That has led to some broken systems or lost data for some of us (me included), but many of us turned it into a learning experience to learn that thing better to prevent it from happening in the future.
If you feel that Slackware is not the right distro for you, there's nothing wrong with that. There are a lot of flavors of Linux and if another one suits you better, then that is the better option for you.
If you are interested in learning more about Slackware and to learn the installer and partitioning better so you don't make a similar mistake again, we'd be happy to help you out with it.
For some of us, it is actually more time consuming using other distros. Yes, Slackware is not a distro that will hold your hand and provide you fancy custom GUIs to help manage installation or packages. That is a turn off for some people and there's nothing wrong with not liking Slackware because of that.
But for many of us, it is nice to use the upstream tools to manage our systems rather than some custom GUI that the distro developed to manage everything. We're in charge of everything on our computers and Slackware doesn't try to shield us from shooting ourselves in the foot. That has led to some broken systems or lost data for some of us (me included), but many of us turned it into a learning experience to learn that thing better to prevent it from happening in the future.
If you feel that Slackware is not the right distro for you, there's nothing wrong with that. There are a lot of flavors of Linux and if another one suits you better, then that is the better option for you.
If you are interested in learning more about Slackware and to learn the installer and partitioning better so you don't make a similar mistake again, we'd be happy to help you out with it.
Thanks for your advice.
There are few options for a 32-bit Linux distro. I don't say which distro is right or wrong for me, but in a matter of time, I need to spend in getting it up and making it run smoothly. Here is my other experience shows a difference between Slackware and other distros I have used. I connect a laptop hard drive with a USB adapter to my dual boot box. After booting up from the external hard drive with Deeepin, all three OS boot options are shown in the Deepin boot screen without any human intervention. Although that is a rare use case, the plug-n-play is a joyful use experience.
After booting up from the external hard drive with Deeepin, all three OS boot options are shown in the Deepin boot screen without any human intervention. Although that is a rare use case, the plug-n-play is a joyful use experience.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.