> -----Original Message-----
> From: plug-discuss-admin@lists.plug.phoenix.az.us
> [mailto:plug-discuss-admin@lists.plug.phoenix.az.us]On Behalf Of Todd
> Hought
> Sent: Thursday, February 15, 2001 8:30 AM
> To: plug-discuss@lists.plug.phoenix.az.us
> Subject: Re: NT5 dual boot
>
>
> Sometimes doing a install on multiple machines isnt really an option
> (resources, might be a production network, etc. etc.) and Since playing
> around with Samba's services and getting it just a little bit
> wrong can be
> catastrophic for a windows network. I did it once, it was ugly.
> But if you have th resources, play with having multiple machines
> if you can.
> It's quite fun to try out all the things that Linux can do really
> well, samba
> being one of them.
> -T
----
The process of setting up samba and authenticating against a windows NT
server is totally instructive - especially in terms of having a machine
account. Also, can be instructive on PAM, shares, etc.

Microsoft DNS is extremely clumsy, but set it up to be a 'slave' DNS server
and see what happens...it's very educational. I can tell you that I have a
number of computers around my house including some Macintosh computers and
having them all integrate - I'm using linux to host my HP LaserJet 4M and
having the Mac's and Windows computers print thru the linux box is an
entirely valuable education. All of my documents are stored on a Windows
2000 computer and the Windows computers, Macintosh computers and linux
computers access that share.

Having a dual boot computer would have prevented any of that laboratory
experimentation. When you can put together a decent enough system for $600,
use a switch to share the keyboard, monitor & mouse, a dual-boot system
seems rather trivial.

Craig