Ugh. Again? Really? There is a search function in these forums. This debate has been beaten to death. My Slackware box does everything listed above (except I don't have a wireless card, and I don't have a second monitor -- though I know dual displays work fine).
Quote:
Originally Posted by IwannaSlack
-Able Use Multiple Moniters.(we both use 2 monitors or more)
|
Edit /etc/X11/xorg.conf. Depending on your video card, you may be able to do this more graphically as well (for example, if you use the nVidia or fglrx [ie ATI] proprietary drivers).
Quote:
Originally Posted by IwannaSlack
-Have all sound & audio drivers working
|
I have answered this question more times than I would like. It is the most frequent question I have answered, and I'm not answering it again. Search the forums. You need to make sure the correct module is loaded (and depending on your sound card, you may have to pass options to the module to get it working properly). You should also run `alsaconf` as root, followed by `alsamixer` (turn up all of the volumes and un-mute everything using the 'm' key), followed by `alsactl store`. There is more detail to this, but search the forums for more information.
Quote:
Originally Posted by IwannaSlack
-Network adapters usable Wireless & LAN
|
For ethernet cards, this is as simple as running `netconfig`. For WiFi cards, it's a little more complex. You can either take the hard (but default) route of following
this guide or take the easy way out and install wicd (a SlackBuild is available at slackbuilds.org). This is a VERY well documented procedure -- search the forums. There are rare cases with obscure network cards that may give you difficulty, and with some you may still be stuck using ndiswrapper. Search the forums.
Quote:
Originally Posted by IwannaSlack
-Able to install and uninstall programs at will
|
This is possible and easy with Slackware -- but much different than Ubuntu. They both have different philosophies. With Ubuntu, it's really an automatic process -- but you have very little control over the compile options of an app. For example, if you want the app to utilize a certain dependency that it wasn't compiled against by the person that submitted the package to the repository, you may have to recompile (or get them to include that dependency). This also results in a LOT of dependencies being absolutely required because the application was built to support as many as possible. If you know nothing about computers, this may be ideal. However, I personally don't like that much unneccessary clutter on my system, and so I use SlackBuilds and decide what I want on my system. Ubuntu is easier, but you get more control with Slackware (though you can compile applications in Ubuntu as well -- but you may have to prepare beforehand so you don't get conflicts with the dependency-resolving package manager).
The easiest methods of package installation in Slackware are using slackbuilds.org (and after finally testing sbopkg on another partition, I can say that this makes things SO much easier and faster),
rworkman's repository,
Alien Bob's repository, and slacky.eu (I trust that one less than the others, but I've never had any trouble with their SlackBuilds or packages and it is a good resource).
Again, package management in Slackware is different than most distros, and it's really a philosophical difference. It's your choice.
Quote:
Originally Posted by IwannaSlack
-Customizable
|
This one probably goes to Slackware. KUbuntu is more customizable than Ubuntu (though a little buggier, perhaps), but the level of customizability in Slackware is greater than both in my opinion. However, some of that configuration may involve editing text files. The text files in Slackware are all very well-documented, and it's a straightforward process most of the time, but if that's not your thing, there are always other distros.
Quote:
Originally Posted by IwannaSlack
-An Active memeber on the network
(we both have networks at our house's if you don't use networks then I guess this won't really matter much but it is usefull for file sharing purposes)
|
This is easy regardless of the ditribution you are using. Search the web and the forums. NFS, samba, ftp, ssh ...
Quote:
Originally Posted by IwannaSlack
-Flash and plugins for Firefox, PDF (this way you can watch youtube videos and view some other sites that have flash or videos)
|
See the SlackBuild for Flash at slackbuilds.org. They also have a SlackBuild for Adobe Reader (or Acrobat or whatever they're calling it nowadays). I *hate* Adobe Acrobat and I just get PDF files to open with KPDF, which is MUCH more lightweight. Everything is faster with KPDF. However, you can get Acrobat to act as a plugin in your browser (see the SlackBuild).
Quote:
Originally Posted by IwannaSlack
-Some sort of Open Office or Word so that we can do our school work
|
I have OpenOffice.org installed (see slackbuilds.org), and I also have Microsoft Office installed through WINE, and also in a Virtual Machine (using VirtualBox). Copying complex stuff between MS Office apps doesn't work well (or at all) through WINE, but works perfectly through a VM. I have a shared folder between Linux and the VM which allows me to use Office fairly seamlessly.
Quote:
Originally Posted by IwannaSlack
-As far as linux goes we both said we were going to get Comliz & Whine
|
See slackbuilds.org for both compiz and WINE. I'm not a fan of compiz, but whatever floats your boat. I've used it, and it works.
Quote:
Originally Posted by IwannaSlack
-Also have our music & videos up on Linux as well.
|
Slackware comes with Xine. slackbuilds.org also has SlackBuilds for mplayer, and Alien Bob's repository has a VLC SlackBuild (and package). Those three will play basically anything you can throw at it. You can also get browser plugins for either at the above-mentioned locations.
Quote:
Originally Posted by IwannaSlack
-Security
|
Both are pretty secure, and both can be made more secure using customizations. See the
Easy Firewall Generator to create some simple IPTABLES rules that should keep your box more secure. slackbuilds.org contains SlackBuilds for rkhunter and chrootkit (I would use both) to check for rootkits. Remember to always run as your normal user, and try not to start X as root (I never have and don't plan on it any time soon).
Quote:
Originally Posted by IwannaSlack
-Also keep the system up to date.
|
This is precisely why I *hate* Ubuntu. Every time I turn on my mom's Ubuntu PC, it has to install TONS of packages, some of which require a restart (WHAT!? A restart required in Linux, even if you're not upgrading the kernel!?). It takes FOREVER! It's very frustrating. This is why I hated Windows (well, one of many reasons), and why I love Slackware. Updates in Slackware are really only because of security issues, and they are relatively rare. Plus, they're easy if you use rsync to maintain a mirror of the patches/ directory. I won't get into that, but I spend very little time upgrading packages. It should be noted that you do have to keep track of applications you install yourself in Slackware, unlike in Ubuntu which does it for you.
Quote:
Originally Posted by IwannaSlack
-Able to Back up files
|
`tar` is great at this. So is rsync. There are also other tools you could install, like rsnapshot. Available in both (and all other) distros.
Quote:
Originally Posted by IwannaSlack
-Keyboard and mouse Fully function including smart buttons.
|
Search the forums. Both are explained. The extra keyboard buttons would have to be set manually, but that isn't difficult. Not all of mine are detected by `xev`, but most are (and the distro doesn't play much of a role in which keypress events are detected by the kernel, so my non-functioning buttons in Slackware would probably not function in Ubuntu either). Your mouse issue is a common question. Search the forums.
Basically, Slackware is easy, stable, and low-maintenance -- once you get used to it. Ubuntu is always relatively easy (depending on your hardware), and Slackware is always simple (but not necessarily vice versa). If you don't like Slackware, switch. Otherwise, we would be more than willing to help you fix your system.