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.
Hi,
I'm on the verge of buying this book, but, as far as i can see, nearly all of the articles within it use debian and fedora as examples. I have no knowledge of these distro's.
So I guess my question goes out to slackers who also have deb and fedora experience: Would these networking examples be easy to "translate" so I can work through them on a slackware box?
I don't know this particular book. All parts of the book treating about 'network in general' will be of use. Examples rather not as they are based on Debian/Fedora packages. The information how to set up applications provided by this packages won't help for building a network with Slackware.
@onebuck
I don't agree this time with you. The site is well suited for Debianists and Fedoraists. Eg. in Slackware a small dhcp server is called .. dnsmasq (I found this recently ). It is not a good idea to learn by examples which cannot be verified - or at least someone will have to install Debian or Fedora.
@onebuck
I don't agree this time with you. The site is well suited for Debianists and Fedoraists. Eg. in Slackware a small dhcp server is called .. dnsmasq (I found this recently ). It is not a good idea to learn by examples which cannot be verified - or at least someone will have to install Debian or Fedora.
Your rights to that opinion!
I believe the site has a lot of useful information. Your not going to have a lot to select from out there for Slackware. I can discern what is applicable and useful to my needs. If you need step by step for Slackware then either wait for the new Slackbook or use the old SlackwareŽ Essentials or SlackwareŽ Basics. Do a Search here on Slackware LQ which will gain loads of information on particular subjects.
You can garner information from Linux Documentation Project or even Rute Tutorial & Exposition which most certainly are not Slackware specific. Syntax & Semantics will always be an issue when using any material that is to be used to learn!
Simple command support from Linux Command Guide will a aid anyone not just a Slackware user.
I could continue with links that are helpful to everyone that are not Slackware specific but usable by a Slackware user. I've got several books/guides on my bookshelf that are general and are used all the time for reference for Slackware issues: Sybex series, Linux Complete & Security Complete are two that come to mind. Sure these are mostly 'man command' extensions but still detailed thus useful.
So if you cannot discern or read for understanding then translate or transfer information to a useful form then a hold your hand distribution may be the best choice not Slackware.
Slackware assumptions are that your smart enough to use it!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.