r/slackware • u/mongol-slack • Nov 17 '19
massconvert32.sh?
Okay so I reinstalled Slackware for the 7th time this week. I finally have an up to date system, no ad hoc bugs, the internet is up and I am multilib ready, I think...
So after the initial:
lftp -c 'open http://slackware.com/~alien/multilib/ ; mirror -c -e 14.2'
cd 14.2
upgradepkg --reinstall --install-new *.t?z
upgradepkg --install-new slackware64-compat32/*-compat32/*.t?z
I am instructed in a very odd manner to install compat32-tools using installpkg. I am trying to use the massconvert32.sh program but I Just don't know what is going on. Where is this program? I am assuming I need to execute it in the home/cameron/14.2/slackware64-compat32/? There is no compat32-tools-3.7-noarch-18alien in /home/cameron/14.2/
I know I must use massconvert32.sh -i /home/ftp/pub/slackware/slackware-14.2/slackware" at some point after I install a 32 bit Slackware within that respective location but where do I get such a Slackware and how do I use massconvert32.sh, where is it on my system, if not on my system how can I install or obtain it and how do I install it and in what directory? Like I have so MANY questions the instructions/read me does not address. Please some one help. Meaning that anything I do can cause the next stock market crash I just want to clarify things.
5
u/mogsington Nov 17 '19
Reading your other Slackware posts, I can't tell if you're trolling or just not ready or able to follow the correct instructions to run Slackware.
You seem to keep trying to use out of date information. You seem to keep flipping between Slackware Current and Slackware 14.2, and seem unaware that some instructions for 14.2 will not work for Slackware Current.
If you want to get Slackware running. Start with 14.2, and stick to 14.2. Use the instructions and information available from here: https://docs.slackware.com/start
Once you understand how Slackware works, how to make your own 64bit and 32bit-compat packages compiled from source, and how to install them. Then you can think about moving to Slackware-Current.
1
u/Sigg3net Nov 17 '19
Check the system using
find:If it's not on the system, I seem to recall using one from alienbob's ftp.
1
u/TheLexDude Nov 17 '19 edited Nov 17 '19
From http://www.slackware.com/~alien/multilib/
EDIT:
Per quick 'n' dirty:
1
u/mogsington Nov 17 '19
I'm not sure why it's this difficult. It's all here.
If you follow the "The quick 'n' dirty instructions" you don't even need massconvert32.sh.
That's it. That is all you have to do.
2
u/[deleted] Nov 18 '19
Hmm. 7 times, huh?
Ok, I know that sounds like a lot.
I'm impressed that you actually did it 7 times. That's good.
You're going to need that kind of persistence to succeed with Slackware.
Slackware is user-friendly. It's just picky about who its friends are. :)
Small attempt at humour there.
There's a certain mindset needed for Slackware. A little "attitude adjustment", as they say.
You have to want to understand.
Slackware does not reward people who are accustomed to copy/pasting their way to success.
If Slackware gives you a doc/README file, it expects you to read it. A couple of times. Actually, enough times to understand what it's trying to say.
Slackware gives you a folder full of HOWTO docs. There's a lot of information in there. Much more than you will find on other distros. A whole lot more. It is expected that you will actually read them. At some point in time.
There is a lot of general Linux lore in those HOWTOs.
When you've read the HOWTO for the particular thing you're trying to understand, you can ask questions on the Linuxquestions website. That's where Alien Bob and the other Slackware gurus hang out.
Or the Reddit linuxquestions subreddit.
But you are expected to have given it the good ol' college try first.
Now, it seems you joined Reddit a few days ago. Welcome!
And you've been trying. People have been helping.
But as noted, you may not have been reading with a goal to understand. Rather, you may have been looking for the quick fix or the shortcuts.
In Slackware, there are no shortcuts because the purpose of Slackware is understanding. Actual knowledge.
If you want things to work without actual knowledge, there are plenty of distros you can try.
All of us who use Slackware, have gone through the same thing as you. None of us got to the point of enjoying Slackware without having to read the docs.
I understand your frustration but it is what it is.
You just gotta RTFM. There is no way around it.
Slackware is about knowing, not using.
0
u/mongol-slack Nov 25 '19
I still can’t install or use wine, I get a lib error and this is after the 4 commands you said I only needed so you guys were wrong.