Ironsmith Keep(LX)

Loading Linux was easy. Simply insert the CD and enter your options. The system will let you know when you need the next CD. In my case, I did not need an IP address as my RT-311 is the DCHP server. However, you will need to know the IP of your DCHP server, if you are using one. Once the load is complete, you will need to reboot the system, so that your newly compiled kernel can take effect. Unless you are doing something the directly alters the kernel, in many cases you do not reboot. You simply locate and 'kill -15' the required process and restart it.

The network potiential was immediate when the the system rebooted. I clicked on Netscape, named Mozilla in UNIX & Linux and Netscape popped right up to the Internet website for Redhat. Remember, I use a DSL connection. This means when the system came up, it was already connected. THere are some potential security issues with this. But at least this question is solved.

The issue now is to hook Linux up as a client to Merlin (NT4 Server). I know that you can set up Linux to run as a Primary Domain Controller (PDC), like Windows NT. There is plenty of reading available. However, while there is considerably less material as the idea is new, there is Winbindd. Winbindd addresses situations where it may be necessary to configure Linux workstations to be clients to an actual Windows NT PDC. One case would be that there is an encumbant NT server with many other computer already attached. What is the point of dragging down the whole network for one machine? That is the issue Winbindd addresses.

I know there are some Linux guru's out there who think I am nuts for going my route. (There were some at the last meeting I went to). But before you gets to mounting your high horse for me to switch to a Linux PDC, you need some more facts.

• This may be a family home network, but it is run like a corporate network. Stin_Net was originally set up to teach me networks in general.
  
• As Stin_Net proved to be more useful than just connecting a few computers, it has taken on more signifigance than just my hobby. It is now a line of communication, an online "local" library as well as on online "bookshelf", and etc, etc. True, it is also good for family get-togethers for a game of Age of Empires, as well.
  
• This means everyone in the family is aware of the network's status besides me. This includes the wife. Think of her as the corporate boss and the kids as the users. If the network is down for a few days, she wants to know why. (I actually had to plan for the Merlins_Rook Phase II Upgrade).
  
• The "corporate boss" (aka my wife) sets a limit on money spent and wants to know things like "bang-for-the-buck".
  
• So like the corporate boss, the wife, even with a limited technical knowledge, she knows the cost of the network, she knows what it is doing, and she definitely knows if it is up or down. ...and she will raise hell if it is down.
  
• In short, I can not just take down the whole network for one computer! Get it?
  

The only difference between a home network and a corparate network is the magnitude. Both network start out with one or two ideas in mind & a few computers. Once the network is estabilshed and it resourse potential is realized, it grows. Stin_Net started out in 1996 with two computers, Possessed (Pentium 90) and On_Faith (486DX66), and a 10BaseT cable. The purpose was an easier way to transfer files and to play games.