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 see the store is located in California. That means high shipping rates to Europe for example. Maybe a store on each continent will make it much more affordable; buying a t-shirt will almost double its value (wasted money instead of a donation). So, for the moment I have just donated. God bless you guys!
About the Slackware documentation project I don't know what to say: you can find almost anything on the internet. Still, I think the project aim is to make Slackware more user friendly and attract more individuals if there is a central documentation source. With this in mind I was thinking to write an article about installing nvidia gpu-driver but see it is already done. Maybe I will just register on the project email list and discuss more there.
It's getting close to a New Year! Just a reminder for new users, please look at: Security Advisories. Once you are aware of the Security needs then be sure to look at: Mailing Lists
Slackware Linux Project Mailing Lists
We have several mailing lists, check the instructions for how to subscribe. To subscribe to a mailing list, email:
with the phrase "subscribe [name of list]" in the body of the email. The list choices are described below (use one the names below for the name of the list).
You as a Slackware user should sign up for the desired mailing list so that you can be aware of necessary changes to be made for your version of Slackware. PV & Team provide this so we can keep things stable & secure.
Plus you can watch a changelog via a favorite mirror (mine) or at home changelog. Please use a mirror whenever possible so we can be sure not to load Slackware Home, mirrors are updated on a regular cycle.
xap/mozilla-firefox-18.0-x86_64-1.txz: Upgraded. This release contains security fixes and improvements. For more information, see: http://www.mozilla.org/security/know...s/firefox.html (* Security fix *) In addition, the build script has been moved from using ./configure back to .mozconfig in order to build with profile-guided optimization by default. The script itself parses ./configure like syntax for ease of hacking. Better icons in more resolutions are installed as well. Thanks much to Matteo Bernardini for the improvements!
xap/mozilla-thunderbird-17.0.2-x86_64-1.txz: Upgraded. This release contains security fixes and improvements. For more information, see: http://www.mozilla.org/security/know...underbird.html (* Security fix *) xap/seamonkey-2.15-x86_64-1.txz: Upgraded. This release contains security fixes and improvements. For more information, see: http://www.mozilla.org/security/know...seamonkey.html (* Security fix *)
Gentoo's lcdfilter repository hasn't been updated in months, and I see that infinality patches are now part of Gentoo's main portage tree. Therefore, I strongly suspect that the lcdfilter ebuilds have reached their end of life. If they have, then my lcdfilter SlackBuilds, which are ports of them, will need to be retired.
Fortunately, Kabamaru's packages, which you can get at someslack, are still being updated and have a FreeType 2.4.11 package available.
The features are all likely to work fine. If you have Windows 8 and want to keep it, start by hitting (windows key) + X, select the disk management program, and resize the windows drive to make some free space for the Slackware installation. Boot the x86_64 Slackware install disc under the legacy boot mode and with Secure Boot turned off (probably you'll want to leave it off anyway). The installer handles GPT fine, so make your partitions using cgdisk. If you made a swap partition, run mkswap on it before running setup, and then proceed to install as usual. Skip the LILO installation.
Last step is probably the tricky one, but not too bad. It might be easier to do from the installed system than from the installer since you'll have network access there. Leave the machine in legacy boot mode for now, reboot the install disc, and use it to boot the installed system. Then, find the EFI boot partition. This is a smallish FAT partition with an EFI directory that contains a Boot and Microsoft directory. Make a slackware directory in there, and put your kernel (and initrd if you use one) in it. Download the elilo sources, and install the prebuilt 64 bit EFI elilo binary in /efi/slackware/. elilo.efi is a good name to give it. Last, you need an elilo.conf config file. The syntax is similar to lilo.conf. Here's an example I'm using here (still giving a few errors yet, but it works):
Now you can put the machine back in UEFI mode (without Secure Boot). To boot Linux, you'll need to use UEFI to add a menu selection that runs elilo.efi. Alternately, most UEFI implementations will allow you to boot from a file, in which case just browse the EFI partition to find elilo.efi and run it. When elilo boots, you might need to hit tab and type slackware to get it to go.
Really? I didn't think any UEFI implementations could boot an ISO9660 or UDF disc (at least not by accessing those filesystems). I'm using Tianocore booted from a USB stick to emulate UEFI though (so far, anyway... hoping to see prices on machines that don't suck come down a little). Discs I've seen that can boot on either BIOS or UEFI are crazy hacks that have a hidden FAT EFI partition on them and both MBR and GPT partition tables. I'm still not sure that we'll go to that extreme. I'd be happy to get a working USB installer image, but I'm not sure how well that's going to work without some other kind of trick. GPT expects a secondary table at the end of the drive, but probably a bootable USB image isn't going to be the same size as whatever stick it is written to.
Funny story. On the UEFI I'm testing with, until the kernel loads the KMS video driver and initializes the framebuffer console, there's no video. So when my tests began, I was running blind. I spent a couple of days trying to boot an installation from a GPT stick with an EFI partition, the huge kernel, and elilo. Every time it would hang, and since there wasn't any video yet I was left to guess why. First I thought the elilo.conf had a bug somewhere, then considered that maybe the huge kernel was too big (ran into that with LILO a few years back). I could get the huge kernel to boot the installer, and could get generic+initrd to boot the installation. I booted the installer (which still doesn't have the video support) and typing with no video tried to mount the root partition on /mnt, and run "touch /mnt/tmp/kilroy" just to prove I'd been there. When I checked on the system, it wasn't there.
That's when it occured to me that the huge kernel was probably giving /dev/sda to the USB stick. I booted the installed system again with the huge kernel but this time pulled the stick out as soon as the kernel loaded, and the system booted fine that time. Probably time to move the USB modules out of the huge kernel... or maybe even get rid of that thing, finally.
Packages can be downloaded from one of the mirrors, and keep in mind that they were built on Slackware 14, which will make them unfit for Slackware 13.37 or earlier (but of course the packages will work on slackware-current):
I have been real busy of late. For members that are not following ChangeLog.txt;
Wed Apr 3 06:58:59 UTC 2013
d/binutils-184.108.40.206.1-x86_64-2.txz: Rebuilt. Export/install demangle.h. Thanks to Jim Diamond. Patched addr2line to use dynamic symbol table if needed. Reverted an upstream change that broke linking dynamic libraries through weak symbols, requiring additions like -lpthread to the link line. Fixed texinfo files to be compatible with newer texinfo versions. Patched system headers to not complain about missing "config.h".
l/gtk+2-2.24.17-x86_64-2.txz: Rebuilt. Restored the missing /etc/gtk-2.0/$ARCH-slackware-linux/ directory. Thanks to Tim Thomas.
xap/mozilla-firefox-20.0-x86_64-1.txz: Upgraded. This release contains security fixes and improvements. For more information, see: http://www.mozilla.org/security/know...s/firefox.html (* Security fix *)
xap/mozilla-thunderbird-17.0.5-x86_64-1.txz: Upgraded. This release contains security fixes and improvements. For more information, see: http://www.mozilla.org/security/know...underbird.html (* Security fix *)
Please notice that Mozilla Firefox is now at 20.0 and Thunderbird is at 17.0.5 for security fixes.
In case you are using Slackware64 14.0 then look at patches/ or just link from here;
Just got my new Asus M5A97 R2.0 motherboard and a new AMD FX6100 to build another tower(Antec 300) to replace a few older bench systems. The reason to choose this Motherboard was to get the newer 'ASUS UEFI BIOS' features to allow debug and system states at any time with 'DirectKey'. Allows you to enter the BIOS at any time to get snapshots, make changes or list states. System is now built and burning in for test period. Probably load systems over the weekend.