[SOLVED] setup fails on most current Slackware-current March 26, 2012
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.
setup fails on most current Slackware-current March 26, 2012
I used Alien's mirror script to download and burn a current DVD for Slackware. The burn failed because the iso was > 4.7G.
Easy fix delete kdei/. Everything OK so far.
Reboot from DVD and log in as root. run 'setup' no messages, after a few seconds, newline and bash prompt return. Repeated attempts produce the same result.
my system:
uname -a returns
Linux Linux 3.3.0 #2 SMP Mon Mar 19 08:13:15 EDT 2012 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ AuthenticAMD GNU/Linux
8GB memory
Lots of space on drives.
Any suggestions would be greatly appreciated
Thanks
John
Click here to see the post LQ members have rated as the most helpful post in this thread.
I used Alien's mirror script to download and burn a current DVD for Slackware. The burn failed because the iso was > 4.7G.
Easy fix delete kdei/. Everything OK so far.
Reboot from DVD and log in as root. run 'setup' no messages, after a few seconds, newline and bash prompt return. Repeated attempts produce the same result.
my system:
uname -a returns
Linux Linux 3.3.0 #2 SMP Mon Mar 19 08:13:15 EDT 2012 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 5000+ AuthenticAMD GNU/Linux
8GB memory
Lots of space on drives.
Any suggestions would be greatly appreciated
Thanks
John
The same here: as I see the dialog do not start - "Error opening terminal: unknown", seems like ncurses/termcap problem in the current build.
P.S. The further investigation shows the problem with sh (busybox) that do not propagates the TERM env var to child scripts.
P.P.S. Uploading the bash static binary and linking it to /bin/sh solved the issue completely - I've managed to install the distro.
--- installer/busybox-dot-config.orig 2012-01-09 19:51:11.000000000 +0100
+++ installer/busybox-dot-config 2012-03-28 10:05:57.705013774 +0200
@@ -54,7 +54,7 @@
#
# Build Options
#
-# CONFIG_STATIC is not set
+CONFIG_STATIC=y
# CONFIG_PIE is not set
# CONFIG_NOMMU is not set
# CONFIG_BUILD_LIBBUSYBOX is not set
@@ -89,7 +89,7 @@
#
# Busybox Library Tuning
#
-CONFIG_FEATURE_SYSTEMD=y
+# CONFIG_FEATURE_SYSTEMD is not set
CONFIG_FEATURE_RTMINMAX=y
CONFIG_PASSWORD_MINLEN=6
CONFIG_MD5_SIZE_VS_SPEED=2
Thanks for the replies, but no success
patched busybox-dot-config as described
ran busybox.Slackbuild
archived the output from the slackbuild with cpio > initrd.img
copied the initrd.img to slackware64/isolinux/initrd.img
rebuilt the DVD
did I do something wrong or miss something?
the boot from the install disk hangs at the same place
setup will not run
looking for any other suggestions
thanks
john
PS using the March 28th changelog
Last edited by AlleyTrotter; 03-30-2012 at 08:04 PM.
Reason: Mixed up two initrd.img's
There is a work around I have used for temporary install of current.
Boot with your 13.37 disk, after you log in as root remove the 13.37 DVD
and replace it with current DVD. enter 'setup' and you should be able to install current.
Of course this is only a temporary fix as I would expect Pat to fix this before the next release.
Credit for the workaround goes to PV as he taught me that in one of my 'guru wannbe' lessons
There is a work around I have used for temporary install of current.
Boot with your 13.37 disk, after you log in as root remove the 13.37 DVD
and replace it with current DVD. enter 'setup' and you should be able to install current.
Or boot your 13.37 CD/DVD, do a network install and set the network path to be a current directory on your favoured mirror
or, if you like, you can also try these mini-isos, where I built busybox statically and replaced it in the initrd (more info on how to extract the initrd here).
P.S. you can also:
- rebuild busybox (/source/installer) modifying busybox-dot-config as above: resulting binary will be in /tmp/busybox-*/_install/bin/busybox;
- extract the initrd.img that you find on slackware's mirrors;
- replace busybox (in extracted_initrd_folder/bin) with the just built one;
- reassemble the initrd.img;
- put it in the isolinux folder of your slackware*-current mirror;
- create the full iso with Eric's script
or, if you like, you can also try these mini-isos, where I built busybox statically and replaced it in the initrd (more info on how to extract the initrd here).
P.S. you can also:
- rebuild busybox (/source/installer) modifying busybox-dot-config as above: resulting binary will be in /tmp/busybox-*/_install/bin/busybox;
- extract the initrd.img that you find on slackware's mirrors;
- replace busybox (in extracted_initrd_folder/bin) with the just built one;
- reassemble the initrd.img;
- put it in the isolinux folder of your slackware*-current mirror;
- create the full iso with Eric's script
Code:
mirror-slackware-current.sh -i
Thanks again Ponce
Even after much time googling I did not find the page http://www.flaterco.com/kb/slackware.html here
It would have helped much
Anyway fixing it was a good learning experience for me.
try to update your -Current ISO using the latest update. Pat has updated the initrd to use Genuine Bash instead of Busybox Ash
Quote:
Sat Apr 7 21:48:42 UTC 2012
l/libtiff-3.9.6-i486-1.txz: Upgraded.
Patched overflows that could lead to arbitrary code execution when parsing
a malformed image file.
For more information, see: http://cve.mitre.org/cgi-bin/cvename...=CVE-2012-1173
(* Security fix *)
isolinux/initrd.img: Rebuilt.
Use genuine GNU bash instead of busybox ash. This fixes installer failure
caused by exported variables such as TERM failing to propogate to subshells.
I'm still not sure what's causing that issue (perhaps a change in glibc?),
but using real bash might be better in the long run, as we won't need to
avoid bashisms in the scripts. The original reason bash was avoided was to
keep things small for installer floppies, and we're well past that era.
usb-and-pxe-installers/usbboot.img: Rebuilt.
Thanks, Willysr.
Looks like the x86_64 is a couple days behind ( at least the change log on Slackware.org). As soon as the change shows up I'll test it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.