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.
Hey, I was helping a friend of mine install Slackware 10.0 a few days ago, and I ran into a problem I'd never seen before. The discs burned fine (we burned an additional copy since at first we thought this was the problem) and everything booted up A-OK. We partitioned and went to do a full install. But it complained that the packages couldn't be installed, some error to do with pkgtool (sorry I can't recall the specific message). EVERY package refuses to install, and I honestly have no clue.
I'm pretty sure it isn't a disk space issue. / was given 10 GB and /home was given like 45 GB or something. Regardless if it was a space issue, it should've installed some of the packages, rather than complaining at the first. I'll ask my friend if he can recall the error message, I'm still drawing a blank.
It does sound like a space issue, as that is wha tit looked like when I messed up my partitioning scheme before. Try just using a swap and a /. If that works, you can laways go back and do it again with a proper partitioning scheme.
I have this problem also. I just did a manual install
1. Install Packages manually
2. Create /etc/fstab
3. Create /etc/lilo.conf
3. Chroot into the new install, mount proc, run lilo, umount proc, exit the chroot environment
Originally posted by shilo It does sound like a space issue, as that is wha tit looked like when I messed up my partitioning scheme before. Try just using a swap and a /. If that works, you can laways go back and do it again with a proper partitioning scheme.
Trust me, it isn't a space issue.
Quote:
Originally posted by Artimus I have this problem also. I just did a manual install
1. Install Packages manually
2. Create /etc/fstab
3. Create /etc/lilo.conf
3. Chroot into the new install, mount proc, run lilo, umount proc, exit the chroot environment
Note that this is from memory.
I wouldn't mind doing that, although, my friend is rather new to *nix (he's used OS X, so he's fairly competent around the terminal) so I wouldn't want to just do it for him, and I'm afraid that process could overwhelm him. I might just have him install 9.1, as the only difference is packages, which will give him plenty of incentive to learn to compile from source quickly .
Thanks for you help/suggestions though, I'll get back to you when I hear from him again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
.
