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.
youd think id know better than to ask slackers for help with slackware by now
every system is going to have not only different hardware but different setups as far as filesystem and partitions goes, its not like these people trying to help you are sitting beside you at your desk, most of it is educated guesses based on their personal experiences,
i been using slackware a good long while and know it is a very stable and trustworthy system, and if i have problems i know it is either my hardware being wonky or my ignorance about something getting in the way and after a little bit of investigating and studying the problem i usually figure it out for myself with the help of google search which sometimes sends me right back here to linuxquestions.org to an old post where someone was having the same problem i was having
point being is that i know how to do it and im getting crap commands from the generator.
im over it. i can get a valid command from the interactive generator. youd think id know better than to ask slackers for help with slackware by now
Goddamn, dude. I'm not running -current, but I've used the generator non-interactive for years without a hassle on laptops with LUKS and LVM. I've also made stupid effing errors in my setups that I would have bet my life I didn't do until I finally figured out that I actually did do it.
My rep points were gained on this forum by helping (or trying to, anyways) other Slackers.
it's odd, as GazL & Alien Bob pointed out:
what you define as interactive spits out a -m option
what you define as non-interactive doesn't spit out a -m option
reading the documentation README_CRYPT.TXT you can actually run the command interactively
You can even run
the script in full interactive mode by using the "-i" parameter, and it will
guide you through the process of generating a mkinitrd commandline.
would be worthwhile to go deeper and get to the bottom of this issue of yours
This case might be related to earlier posts in this thread.
I just did try to install the latest slackware64current version (burned today).
I did burnt it on a slackware64 14.2 systems exactly as I did at earlier occasions.
But now I got problems with ramdisk generation, just after all packages were installed.
The messages I got was repeated in some loop:
mkinitrd_command_generator.sh Line 345: shift: 2 : shift count out of range.
This type of error was not present in the 18 december 2018 version I burned earlier and which installed
smoothly.
Has there been a change in the mkinitrd procedures?
The test system 8Mb memory.
This case might be related to earlier posts in this thread.
I just did try to install the latest slackware64current version (burned today).
I did burnt it on a slackware64 14.2 systems exactly as I did at earlier occasions.
But now I got problems with ramdisk generation, just after all packages were installed.
The messages I got was repeated in some loop:
mkinitrd_command_generator.sh Line 345: shift: 2 : shift count out of range.
This type of error was not present in the 18 december 2018 version I burned earlier and which installed
smoothly.
Has there been a change in the mkinitrd procedures?
The test system 8Mb memory.
Best regards,
talo
linux talo is online now Report This Post
Please stick to ONE SINGLE THREAD with your questions. I answered in your other thread. This is just annoyiong.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.