SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I ran out of disk space on my eeepc 2G surf while upgrading to RC3 and wasn't able to get the kernel source, qt or samba.
There were some earlier suggestions to do a clean install. I have done something quite similar to what you describe once or twice. If you have slackpkg, you can re-install package groups; if not, try booting with the installer, mount your file systems, and (re-)install away. You may be able to do this with pkgtool, you may be able to do this with setup.
14.0RC4 is running on a double-boot box here in 32-bit and 64-bit mode, with Xfce. When inserting a CD-Rom or a DVD and mounting it in Thunar, the automagic mountpoint is /run/media/<disk_label>. Did I miss some evolution here?
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Well, if you try hardly enough, you always will find something to fix.
For instance in the installer, isolinux.cfg includes three entries for kernels with respective labels huge.s, hugesmp.s and speakup.s
The last two are somehow duplicates, as both launch the same kernel (hugesmp.s), but at the same time the help text that you see if you hit the F2 key (f2.txt) says:
The default kernel is hugesmp.s, which requires at least a
Pentium Pro processor. If this kernel doesn't work for you, you may try
the regular "huge.s" kernel, which supports i486 and better single CPU
machines. Both kernels now contain Speakup support.
This is somehow slightly inconsistent - and possibly a reminiscence of an older version.
I guess that this doesn't deserve an RC5, though
Last edited by Didier Spaier; 09-02-2012 at 04:10 PM.
If possible, make a clean install of Slackware 14 RC4, to be sure that your problems don't come from your successive upgrades.
That sounds a lot like the old generic advice in the early days of Windows: "Oh, you just need to reinstall Windows!" ... but it worked!
That new xfce4 default setup is pretty!
This fresh install apparently cleared out a lot of assorted cruft and freed up more of my limited disc space.
NetworkManager doesn't want to voluntarily find my wireless router yet, but automounting of USB flash drives is now working again after several months of not working.
I'll reinstall wicd, chrome, flash-player-plugin, and those (less than a dozen) SBo, alien and slacky packages. Oh, and I'll be wanting to upgrade guile again from the version 1.8.8 installed by default (I think they're at 2.0.6 now).
BTW, I remember there was an answer here (in LQ) to how to view utf8 man pages properly. It was helpful but I failed to find it just now.
AKAIK, there is no magic solution, as the manuals are bundled without any mechanism allowing to each of them to declare the charset it uses. Here I think you look at an UTF-8 manual with an UTF-8 locale, so groff converts it to UTF-8 because it knows your local charset but ignores the page is already suitable for it. Try this to inform groff there's no need to convert:
GROFF_ENCODING=utf-8 man chsh
Originally Posted by kingbeowulf
same here. man shutdown, last and halt do spit out "Error parsing *roff command from file ..."
manpage troff syntax error? utf8? There seem be a few bug reports scattered about that the line
'\" -*- coding: UTF-8 -*-
It's a typo, I think. The leading single quote should be a dot.
Not sure if this is wrong or correct, but the netatalk package includes two configuration files in /etc/netatalk atalkd.conf.new and papd.conf.new which are not handled by the doinst.sh script and therefore stay as *.new files even if there is no existing configuration file during install.
I'm using Fluxbox and haven't decided how to handle the loss of HAL,
so I haven't run across this issue yet.
I'm running Fluxbox without HAL, but udev + udisks (not udisks2) + udiskie script works like a charm. And it even mounts devices to /media
And by the way, I did new install (accidentally partially erased my /etc, so new-install was fastest way how to fix this and it also cleaned few once-compiled-now-completely-forgotten programs) and Slackware 14 RC4 runs just fine. Well, I'm experiencing one problem with ipw2200 kernel module*, but that's nothing Slackware can fix. And I would also like to resolve rc.dhcpd issue, but I can live without it. Slackware 14 RC4 is flawless from my point of view.
* due to change in udev, ipw2200 fails to load at first, timeout after 60 seconds and then it's successfully loaded again. Nothing actually broken, only you have to wait for 60 more seconds. If anyone wants details, feel free to ask.
Last edited by yenn; 09-03-2012 at 11:28 AM.
Reason: link fix