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.

Multiplatform Theoretical Network - Some information before I try this out, please?

I've knocked up this small diagram in Inkscape of what I want my home network to be like. Basically, I want a box running Linux (preferably Slack) to do all the server-y type stuff, and I want to be able to access the connection, shared files and printers etc on any one machine on the network, so Samba is on my mind right now.

Anyway, please take a look at my diagram and tell me how possible this is, without causing me too much of a headache. I have Googled around and seen nothing specific to my tastes or desires. If you have any advice or comments, I'd be interested. Especially if regarding what the best way around this would be, common pitfalls to avoid, definite things to do first, reading material to swallow beforehand, etc.

Note that I may also add a Mac machine to the mix later on - so I'd like to know if this is possible (I assume it's mostly click and go/plug and play, since it's technically Unix to Unix here).

I also wouldn't mind tips for really cool things I can do with such a powerful home network (Like hooking up a widescreen TV to a TV out to have the network play mplayer videos living on the file shares, straight to the TV via a SCART/TV out (if SCART out even exists for x86!) from any of my machines - I had that idea for a while, and it seems really cool, if almost impossible).

And on the wireless issue - unless I'm going to have it forced down my throat by the majority of ISPs, I want to avoid WiFi. I don't trust it at this moment in time. There's the security issue, and also the issue of it just not working due to interference from cellphones/microwaves/opera singers. It's also too damned expensive for an individual wireless NIC at the moment.

PS: I know it probably seems like too much of a Utopian dream, but if I can get file and broadband sharing setup across Linux->Windows, I'll be happy. I don't think there are Linux drivers for my ancient printer anyway.

Not knowing the kind of network equipment you have, it's hard to advise any specific LAN configuration.
You show a seperate router and modem. Most ISP's provide a combination moden/router/firewall, is this what you have? If not, get one, they are cheap and simple to set-up. Next lose the direct connection from the laptop to the modem. Your Slack machine will have two network cards installed. eth0 connected to the modem and eth1 connected to a switch which will provide you with ports for your inside LAN. Printer sharing under CUPS is fairly easy to set-up but you mentioned that you have an older printer and you want to be sure it is supported (and do NOT buy a Lexmark).
Experts recommend not using a firewall machine as a server, but I am not an expert so I've run this way for years. This means that if you are thinking of putting up iptables on the Slackware machine, in addition to server duties, you are walking on thinly supported ice. Get the combo modem.
Samba is a great program but you will have to configure both TCP/IP and Windows sharing. This is still not a task for the faint of heart especially if you want to share that printer from both environments.
The answer to your whole post would take up several pages and just scratch the surface of the possibilities you envision. Keep reading, planning, and archiving.