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.
Distribution: Slackware 14 (Server),OpenSuse 13.2 (Laptop & Desktop),, OpenSuse 13.2 on the wifes lappy
Only issue I have come across so far, (and it's been the same for every major upgrade I've ever tried) is the fonts never seem to remain the same across upgrades which is a bit of a nuisance. Not sure if this is a Slackware thing or a general Linux thing as I have no other distros installed to compare.
Distribution: Slackware 14.1 64 bit MLED with XFCE 4.12, KDE 4.14.3 and currently using Fluxbox
Should I just click on the patch file after removing the .txt - to patch the broadcom driver - or is there another step that I'm missing? I tried the following in terminal as root: patch -p0 src/wl/sys/wl_linux.c < bc_wl_abiupdate.patch
and received the error below:
Hunk #1 FAILED at 332.
1 out of 1 hunk FAILED -- saving rejects to file src/wl/sys/wl_linux.c.rej
just open the wl_linux.c & patch file with your text editor,navigate to the line that you must change and copy/paste.If you update your kernel to 3.3.1 then you must use " make API=CFG80211 " (without quotes) and have cfg80211 option (under Wireless) enable in kernel.At least that's what i did to be able to compile the module.WIRELESS_EXT API is no longer compile the wl module.I'm using BCM 4313 14e4:4727
1. uncomment a mirror for your upgrade source in /etc/slackpkg/mirrors
2. do $slackpkg update #dl's file lists from the mirror
3. do #slackpkg install-new #installs the latest slack goodness
4. do #slackpkg upgrade-all #upgrades all files on your machine including kernel
5. you may be prompted to run /sbin/lilo #y is the correct answer
6. you may be prompted to K/O/R/P the new files #O for overwrite config files is the brave answer
Do not ressurrect a years-old thread. It is considered to go against LinuxQuestions etiquette.
Second, you do not ask an actual question here. What is your context? What are you trying to achive?
Third, your question (if this is indeed a question about how to upgrade a system) has no relevance to the topic of this thread. You should have opened a new thread or asked this question in the thread where your quote comes from.
Fourth, read the fine manual before asking: http://docs.slackware.com/howtos:sla...considerations