[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Merging workstation and server systems



On Mon, Jun 27, 2005 at 08:09:13AM -0700, michael@etalon.net wrote:
> Quoting VSJ <debian@terabytemusic.cjb.net>:
> 
> >Hi,
> >I've a small home network, with an old server system, running Woody and
> >WWW/mail/proxy/NFS/Samba/NIS services. This system is up 24/7.
> >I also have another old system, acting as a workstation, currently running
> >Etch and physically located next to the server system. This system is also
> >up 24/7.
> >I'm planning to replace both systems by a new computer, which should also be
> >running 24/7. The problem is that I don't want to merge a workstation and a
> >server configuration.
> >I'd like know if it is possible to keep both configurations completely
> >separated: ie, run sarge as server and run etch inside a chroot.
> >The problem is that the users should not be able to access the sarge
> >configuration, ie they should not be able to break out of the chroot and it
> >should not be visible they are in a chroot.
> >For example, if the computer boots up, the terminals (including kdm at vt7)
> >should give access to the etch system, not the the sarge system.
> >Is it possible to have two completely separate configurations/distros
> >running simultaneously on the same system? And how should I set things up?
> >Thanks in advance,
> >Stan.
> 
> That sounds like alot of work.  :)
> Why not just run sarge for everything?
> I can guess that you want to keep your server up with sarge packages as
> its the latest stable release. So then why the need to run etch packages
> for logged in users? 

The better solution is probably UserMode Linux or Xen.  AIUI, both are
well supported in Debian.  The advantage of UserMode Linux is that one
OS is the host and has direct access to the hardware (you probably want
that for the workstation).  The advantage of Xen is that is has better
performance.

-Roberto

-- 
Roberto C. Sanchez
http://familiasanchez.net/~sanchezr

Attachment: pgpQpPtIZofLq.pgp
Description: PGP signature


Reply to: