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.
@GazL - Nice catch on the .xinitrc. I see the same.
Figures :P Things work fine with fvwm2 on my Slackware 14 beta 1 vm (I have yet to snapshot it and then upgrade it). I'll see what happens after I update it.
Shouldn't /etc/rc.d/rc.networkmanager be included under "Select/deselect system daemons" in the "SELECT STARTUP SERVICES TO RUN" dialog box? I would think this would be a service that most would want to enable on startup.
The option CONFIG_FB_VESA=y in the RC kernel is causing NVIDIA's blob to spill the following error.
Code:
[ 47.491112] NVRM: Your system is not currently configured to drive a VGA console
[ 47.491114] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[ 47.491116] NVRM: requires the use of a text-mode VGA console. Use of other console
[ 47.491117] NVRM: drivers including, but not limited to, vesafb, may result in
[ 47.491118] NVRM: corruption and stability problems, and is not supported.
Bug in the installer:
When installing slackware in a qemu-kvm PC using virtio drivers, all virtio devices are available ("fdisk -l" shows /dev/vdX devices) but the installer can't see /dev/vdX so I have to do that :
I install slackware without virtio drivers so I have /dev/sdX devices then I restart the cdrom with virtio enabled, chroot to my installation then modifying lilo.conf, fstab and create a initrd.gz successfully.
just as GNOME was removed. XFCE is probably the best choice for a default desktop in Slackware. Just LOOK at the bloat of KDE!
Furthermore, Perl 5.16.0 is broken in respect to CPAN. I finally avoided using CPAN by manually creating packages for modules that I'd normally install via CPAN. The latter effort could have been avoided if the Perl installation weren't broken.
Anyway, I knew in advance that the upgrade to Slackware 14 wasn't going to be clean or easy. I was right ...
Bug in curl ?
When executing "./configure" script of ncmpcpp-0.5.10, I have this message :
Code:
checking for curl-config... /usr/bin/curl-config
/usr/bin/curl-config: line 138: CPPFLAG_CURL_STATICLIB: command not found
Ok it's not an error.
I looked at "/usr/bin/curl-config" and I replace :
Code:
if test "X${prefix}/include" = "X/usr/include"; then
echo "$(CPPFLAG_CURL_STATICLIB)"
else
echo "$(CPPFLAG_CURL_STATICLIB)-I${prefix}/include"
fi
by :
Code:
if test "X${prefix}/include" = "X/usr/include"; then
echo "$CPPFLAG_CURL_STATICLIB"
else
echo "$CPPFLAG_CURL_STATICLIB-I${prefix}/include"
fi
and it works.
It seems $CPPFLAG_CURL_STATICLIB has no reason to be a command, doesn't it ?
Edit 1: I'm wrong, it doesn't work. "./configure" works but "make" failed because of curl. Edit 2: "make" failed also without modifying "/usr/bin/curl-config" on i486. "make" works perfectly on x86_64 with or without modification of curl-config. I hope I've not forgot anything and I don't lose your time. Edit 3: I just retry to compile ncmpcpp on a clean slackware-current (i486) installation and "make" works.
Last edited by Thom1b; 08-12-2012 at 07:20 AM.
Reason: Compilation works
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.