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.
So far every attempt I have made to install has terminated prematurely with a “KILLED” error, usually 5-10 minutes after installation process to hdd has begun.
I have tried different computers, install media, dvd sata, dvd ide, usb stcks etc.
I will attempt to copy the text from place the last attempt halted. I have no idea what that stuff means, but I'm hoping that someone who knows can tell me what I'm doing wrong. Thanks in advance.
Killed
root@slackware:/# /usr/lib/setup/slackinstall : line 244 : 2601 Done
cat $TMP/series/series.in
2602 Killed | while read series; do
installseries $series;
done
/usr/lib/setup/installpkg : line 314 : 23479 Killed ( cd $ROOT/;
$packagecompression -dc | $TAR -xlUpvf - ) < $package >> $TMP/$shortname 2> /dev
/null
The setup program works great but can fail if the steps are not run in sequence. If you jump in and out of the setup program or jump back and forth in performing the various setup steps, it will lose track of important information supplied in previous steps that are needed for following steps.
Before you run setup the disk partitions need to be properly configured and labeled (fdisk, cfdisk, ...). Perhaps that is the common item in all of the failed attempts.
Sounds like the kernel OOM killer kicked in, but it's a mystery why this would happen on multiple machines (unless they are all short of memory). If you made it far enough to configure sufficient swap space, this shouldn't happen. If you didn't make it that far, perhaps activating swap space before running setup would help.
the stupid mistake i kept making was not formatting partitions & activating swap after making then in cfdisk. i thought leaving them as linux swap & linux was enough.
So. . I'm using the new system now . . nice so far.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.