LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-12-2007, 03:32 PM   #1
WoodLark
LQ Newbie
 
Registered: Feb 2004
Location: South Carolina
Distribution: Slackware et. al.
Posts: 29

Rep: Reputation: 15
Setup being KILLED -- Slackware 12.0


A couple days ago, I installed Slackware 12.0 on an older computer. At the time, I thought I did not want/need x-windows since it was to be a server. Since then, I have decided to install x-windows (but I don't want to lose the other software I have installed/configured in the meantime).

Now comes the stupid part. I figured the best way was to boot from the CD and rerun setup, but only the select and install packages portion, selecting only those packages needed for the x-windows (so far so good). Due to brain failure, I interrupted the install process in the middle of installing glibc.

I have tried several times to rerun setup, but each time, in the middle of the installation of glibc setup exits with multiple console messages of "Killed". I have run removepkg glibc, and that appears to run ok but has no effect on the problem.

Luckily, the system still boots and runs ok, although I suspect I would have a serious problem if I tried to compile anything.

Does anyone have a suggestion as to how to fix this without dumping everything and starting over?
 
Old 11-12-2007, 04:26 PM   #2
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,639

Rep: Reputation: Disabled
You don't need to boot from cd. Just boot normally.

Slackware packages are installed using the commands "installpkg" and "upgradepkg". What you should have done was simply mount the cd with the /x (and maybe /xap and /kde) directories and typed (as root)"installpkg /path_to_cd/slackware/x/*tgz" to install all the x stuff (do this with /xap to install X applications and guess what /kde has ;-).

You can fix a borked glibc install with "upgradepkg --reinstall --install-new path_to_cd/slackware/l/glibc_package_name.tgz". And if you really think some of the other libraries are affected you can reinstall all the libraries with "upgradepkg --reinstall --install-new /path_to_cd/slackware/l/*tgz".

You get the idea.

Brian
 
Old 11-12-2007, 08:01 PM   #3
WoodLark
LQ Newbie
 
Registered: Feb 2004
Location: South Carolina
Distribution: Slackware et. al.
Posts: 29

Original Poster
Rep: Reputation: 15
BCarey,

You have helped me save what little hair I have left! Thank you, your instructions worked perfectly (and I learned something new).
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
find history of a job killed by "kernel: Out of Memory: Killed process" poulacou Linux - Server 3 09-20-2007 04:24 PM
Slackware - Eth1 Setup and Port Setup help girlsmakegraves Linux - Networking 3 12-16-2005 11:11 AM
Swaret KILLED sound for Slackware 10.1 NetRAVEN5000 Slackware 35 08-13-2005 06:32 PM
Slackware 10.1 kernel upgrade killed my network - help! clowntoe Slackware 13 06-10-2005 11:52 AM
Help! I've killed Slackware 9! usernamed Slackware 7 06-08-2003 02:13 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:20 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration