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.
Multi part post. Part #1 will deal with installing and setting up a basic Slackware 13/64bit multilib system. Part #2 and above will deal with additions and oddities.
First off...It's a BIG download...Burned to a DVD, and all set.
Asrock ALIVENF6G-VSTA motherboard
2GB DDR2 533 memory (2x1GB chips)
WD 160GB IDE (Yes, I have sata ports, but my sata drive died)
16xDVD +/-RW writer (ide)
Nvidia Palit 8400gs PCI-E x16 videocard 128mb DDR2
680w apower AK series PSU, w/PCI-E and SATA connectors, 40A +12v rails (2x20A)
Not a zooming system, but it does the job. Was previously running Vista Ultimate 64-bit on it, but the SATA drive took that out, along with all my data for last 4 years..
So, I started fresh. Booted the DVD, and did a full install. Used ext4 as filesystem. Installed lilo in 'expert mode', telling it to install on the MBR of /dev/hda
Ran the following as root:
xorgsetup (Basic setup of xserver, just took defaults on all)
alsamixer (Set basic sound levels)
alsaconf store (Save alsa sound levels)
adduser (Adding a regular user, with addition of being in plugdev group)
Logged into user account,Started X, went to Nvidia.com, got drivers for my video card.
Exited X, logged into root, ran the driver installer, answering Yes to all except "Do you want to look online for a kernel module", and rebooted.
Logged in as root, edited
sudoers (using visudo, to let my regular user use sudo)
lilo.conf (I hate the wait for boot, uncommented #compact)
lilo (To use the new lilo.conf)
/etc/initab (Changed to runlevel 4 for GUI logon)
Logged in GUI style (Yea!)as user, and went to Alien Bob's site to get files and instructions on making SW multilib. Downloaded needed files, installed the resulting packages, and went back to the site to get his SlackBuild of wine64, and installed that.
Rebooted once more. I now had a fully functional, 64/32 multilib FAST distro.
So far, so good...
Now, onto the unusual stuff...And why I installed wine
Because I'm a World of Warcraft addict. While I don't have a smoking games system, it does OK for WoW, as long as I don't use anything but lowest (about) settings. In Vista, was getting a average 30-40FPS in most areas, slowing down so about 20 in Dalaran. Since Vista went POOF!, I needed my fix, and WoW is SUPPOSED to work under wine. Luckily, I had all the updates on another DVD for all the patches since the Wrath of the Lich King expansion came out, so I didn't have to wait hours and hours for patches to download (again).
So, in goes the first WoW disk ,and told wine to install that. (It DOES take awhile). Then, the Burning Crusade expansion (Had to mount that DVD with a special command, look on 'net, it's everywhere. Use the same setup to install WotLK expansion DVD too.)
After those three were done, I installed the patches by copying them to the correct folder , and ran Launcher.exe. Patches only took about 20min total.
In summary, it took <15 min to install SW13, 15 min to get/install multilab/wine64, and 2 1/2 HOURS to install WoW. Yes, I'm an addict....lol
I modified the wow command to use -opengl, then I clicked the shiny new WoW icon, and away I went. Worked PERFECT! i was VERY happy.
Alot of people think that using WoW in wine/Linux gives a performance hit. Well, not here. I gained an average of 15fps..That's about a 20-30% increase in performance for free!
All was going good until: The wife wanted me to use Skype. I have a Logitech webcam for years, that worked fine in 12.1. Well, it DOESN'T work in 13. The kernel drivers for it just won't do the job. Sigh. Okay, how to get around this?
VirtualBox.I first tried the open-source version from Slackbuilds.org, but that doesn't allow USB connections...Sigh...Uninstalled, and got the binary from VirtualBox. After fiddling with Slackware mount settings in /etc/fstab, all is working now. The webcam works, and using the built-in mic on the camera, I can talk. But, there was a issue...No sound...
Part #3: Pulse Audio, and where,oh where has my printer gone?
Well, the XP32 client inside Virtual Box had no sound. So, after MUCH reading, and because Ventrilo (Voice chat program for use in WoW) uses it too, I installed Pulse Audio using the Slackbuilds from Slackbuilds.org. And, what do you know, SOUND.
Okay. Now I'm fairly happy. With the exception of the stupid old webcam, which forced me to use VirtualBox/XP, everything is running great. Then the wife asks "Why can't I print over the network?"...Sigh...
Okay..Edited inetd.conf for swat access, made sure cups.d was enabled, and away I went..
I have a HP Deskjet d1660 printer, a cheap Wal-Mart printer. hplip (the version sent with SW) does not support this printer. Sigh...
Off to HP, get the source for hplip newest version, modify the SlackBuild script in /sources, ran the script, uninstalled the hplip that came w/SW, installed new package, and after unplugging the USB cable on my printer and reinserting it, hplip-setup found the printer. I can now print locally from SW.
But, so far, no matter what I do, I cannot print over the network using cups (Something stupid, probably). So, back to VirtualBox, install it there, and BAM! Network printing.
So, to summarize so far:
Installing and configuring base system: Fast. 10-15 minutes
Setting up multilib and wine64: 10-15 minutes, plus download times
Installing WoW in wine: 2 1/2 hours. Add another 2-3 for downloading 1-2GB of patches
VirtualBox download and install using binaries: 15 min max
Configure VirtualBox to use USB: 5 min
Install XP in VirtualBox: <15min (I was amazed myself!)
Install printer and webcam in XP: <15 min including download of Win drivers for webcam
Setup new hplip: <5 min
Without WoW, total time setting up the system to where it is now took about 90 minutes (Not including download times, Google/Linuxquestions.org searches and reading).
Things to still do:
Buy a UVC camera to use in Linux, so VirtualBox/XP is no longer necessary.
Figure out my Samba/Cups issue so VirtualBox/XP is no longer necessary.
This post will be added to as things change...
Now, off to fight monsters in World of Warcraft...