From: ian douglas (id_at_w98.us)
Date: Wed 05 Nov 2003 - 04:31:25 GMT
Considering RedHat's recent press release about discontinuing the "RedHat
Linux" line in favor of the more expensive enterprise version, I'd really
like a few answers from others (only had one off-list reply) regarding which
operating system is going to be my best bet since I'm going to have to
convert my server to another Linux distro now.
I'll be starting a whole new server to manage everything but curious,
obviously, which distro people have had the most success with other than
RedHat.
Thanks for any help on that, as well as my other unanswered questions.
-id
> I searched the site's documentation and found the multi-page
> "this is what it's
> capable of" documentation, but didn't see any offhand that answered the
> following questions. I sent them to Jacques, but I'd like to pose
> it to the list
> in general for the 1.0 release so I can get started on vserver in
> the coming
> weeks.
>
> ---
> Hi Jacques,
>
> I've been daydreaming about a vserver setup for my system.
>
> A few things that perhaps would be handy to have in the FAQ:
>
> - what OS works 'best'? Kernel version is obviously important,
> but it would be
> neat to see some sort of volunteered information from various
> users as to the OS
> and version of that OS, that they have the most success with
>
> - how does one get started? is it best to start with a totally
> fresh machine and
> build from there, or could I start from a medium-sized virtual
> hosting setup
> using Linuxconf and build a vserver and go from there? I guess
> I'm looking for
> guidance on what should/should not get copied over when building the first
> vserver - once I build the first one, I can just use the vserver
> software to
> duplicate it, but I'm worried about disk space and how to
> actually mount/share
> file system areas...
>
> - any patched versions of up2date out there? or would I have to
> tell up2date to
> save a copy of the RPM's on the disk somewhere and run the
> vserver rpm utility
> to patch all vservers? If I have 100 vservers, is there a quicker
> way to tell it
> to patch all vservers, or would I have to literally type "rpm
> server1 server2
> server3 ... server99 server100 -Uvh *rpm" ?
>
> ---
>
> Thanks for any additional feedback.
> -id
>
>
> _______________________________________________
> Vserver mailing list
> Vserver_at_list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
>
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver