On Mon, Jun 27, 2005 at 11:16:04PM +0200, VSJ wrote:
> [EMAIL PROTECTED] wrote:
>
> > Why not just run sarge for everything?
> > So then why the need to run etch packages
> > for logged in users?
>
> No one knows how long it will take before etch becomes stable. I don't want
> to run old software for workstation desktop users (sarge will be ancient in
> three years...).
> But I also don't want to run testing or unstable for server tasks.
> I also don't want to enter the backporting hell, that's why I want to run
> separate sarge and etch* simultaneously, with etch possibly in a chroot.
>
>
>
> *Or possibly Ubuntu or another Debian desktop distro
Hi VSJ,
I have another suggestion:
divide the 'server' tasks between the 2 old server and use the new fast
one for the workstations. The new faster machine will be great for the
desktop user and the 2 old servers should be able to handle www, samba,
firewall, etc between them.
internet====>proxy/firewall/email/===>workstation
||
\/
www/nfs/blog
why waste good 'tested' hardware. Linux can put it do good use!
Cheers,
Kev
--
counter.li.org #238656 -- goto counter.li.org and be counted!
`$' $'
$ $ _
,d$$$g$ ,d$$$b. $,d$$$b`$' g$$$$$b $,d$$b
,$P' `$ ,$P' `Y$ $$' `$ $ "' `$ $$' `$
$$ $ $$ggggg$ $ $ $ ,$P"" $ $ $
`$g. ,$$ `$$._ _. $ _,g$P $ `$b. ,$$ $ $
`Y$$P'$. `Y$$$$P $$$P"' ,$. `Y$$P'$ $. ,$.
signature.asc
Description: Digital signature
