NT5 dual boot

[Trent Shipley]

Actually, there is little industrial need for multi-boot systems -- except
maybe in educational labs.  The main use is personal computing.
Dual-booting is actually an inelegant hack dictated by poverty.

However, heterogeneous networking is a *very* marketable skill.  The problem
is getting access to a heterogeneous network  -- you have to be an idiot to
give carte blanche access to a production network.

Would there be any interest in replacing a Thursday meeting with a
combination LAN bash and hands-on heterogeneous networking seminar?  Maybe
over a long weekend?  We could cooperate with ASLUG and maybe get some
corporate sponsorship.


I'm writing a dissertation, but there's a lull right now so I can put in a
few hours of committee time.



> > The problem with a dual boot is that it stops the learning process.
> It is
> > far more instructive to accomplish the interaction between the linux
> server
> > & the NT server(samba/smb) - setting up the various network services
> > (dns/dhcp/wins) on each and seeing how each handles clients
> differently,
> > using the Windows NT as a password server for the linux - i.e. -
> merge the
> > best of both worlds.
> >
> > Just a theory.
> >
> > Craig
> >
>
> Um... I think that is after we get the dual boot to work.........
> Actually what you say seems to be on the advanced side, and even
> though appealing, I wonder if there is much market for such.
>
> Help me out here, what would you say?
>
> Keith



> > -----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