Re: Re: [Vserver] is there any getting started with vserver documentation anywhere?

2003-11-30 Thread Simon Garner
On Saturday, November 29, 2003 11:02 PM NZT,
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

 Hello Simon,

 Is there a list of things to remove prior to building the skel, and
 after?
 If so where can I get it, I continue to have problem with thing trying
 to start, like the can't initalize iptable - can't find etc/fstab,
after
 I edited it in the skel...?


/etc/rc.d stuff all needs to be modified quite a bit to work with
vservers. I could look at adding some of the needed changes to the
build-skel functionality in Vskel, only trouble is it tends to be a
little distribution specific.

I suggest you look in /etc/rc.d/init.d (in the skel) and delete all init
scripts for things you don't need - including iptables. Then look in
/etc/rc.d/rc3.d and remove the links to those same scripts (or you can
use chkconfig to do this the 'tidy' way).

Let me know if you still have trouble...

-Simon

___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: Re: [Vserver] is there any getting started with vserver documentation anywhere?

2003-11-28 Thread mile1
Hello Simon, 

The vskel is a very good tool, nice job. I have but one question
about creating the vservers, is there a way allocate disk, memory space for each 
vserver? I understand the ulimit to be the number of limited processes within the 
vserver. I ask this because, if your in webhosting customers would want to see some 
type of accounting for service level agreements, is this possible?
 
 From: Simon Garner [EMAIL PROTECTED]
 Date: 2003/11/05 Wed PM 05:04:18 EST
 To: [EMAIL PROTECTED]
 Subject: Re: [Vserver] is there any getting started with vserver   documentation 
 anywhere?
 
 On Thursday, November 06, 2003 10:28 AM NZT,
 Jan-Hendrik Heuing [EMAIL PROTECTED] wrote:
 
 
  Just to get this right:
 
  - vanilla kernel should not be used on redhat
  - vserver does not patch redhat kernel yet
 
  ?
  It looks a bit like there is no straight way using redhat9 with
  vserver, am I right with this conclusion ?
 
 
 Correct... that's assuming redhat9 uses NPTL, I'm pretty sure it does
 but somebody correct me if I'm wrong...
 
 
  Anyway, if you still know the place of the kernel sources, I'd still
  like to know, as I can't find them. And I guess at some point there
  will be patches for the redhat kernel.
 
 
 up2date --download kernel-source
 
 The redhat9+ kernels also use the O(1) scheduler which I think is the
 main sticking point for vserver, but there has been work on O(1) vserver
 patches... somebody else can tell you more about that.
 
 
 
  What would be the way to go ?
 
  Use debian as the host, and maybe use rh vservers ? I'd like to use
  redhat for some things as I know about it. Just looking into debian...
 
 
 At Herbert's suggestion I'm now using Mandrake 9.2 and have found it
 quite nice. It's a redhat-based/redhat-style distribution, so most
 things are quite similar to redhat (i.e. it uses rpms and the system
 layout is much the same). But it doesn't use NPTL or O(1), so a vanilla
 kernel with vserver patches works just fine on Mandrake.
 
 -Simon
 
 ___
 Vserver mailing list
 [EMAIL PROTECTED]
 http://list.linux-vserver.org/mailman/listinfo/vserver
 

___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] is there any getting started with vserver documentation anywhere?

2003-11-05 Thread Alexander Goeres
I once tried to make the vservers run on a SuSE disto but after serveral 
weekends gave up. That's basically due to my lack of ability to compile a 
vanilla kernel on SuSE so that all the modules it has with its standard 
kernel work. 
We run vservers under Debian 3.0 (Woody) without any problems. The normal 
vservers (without setting disk-space limits and without setting the context 
number :-)) are simple: I started with the introduction by Jacques (in 
april, I think) and worked up my way through the other docs in mentioned 
http://linux-vserver.org. Astonishingly there's not really much to do to run 
vservers: patching, compiling and installing the kernel, getting the tools of 
choice (either from the Debian distro or Enrico's util-vserver), setting up a 
vserver, do a vserver xxx start and that's it... As a kernel I use whatever 
is currently regarded as stable (on the long running system 2.4.18, on the 
systems to-be-set-up 2.4.22) and where the developers provide a patch.

I found it to be very stable, relatively easy to install and extremely useful!

Alexander


Am Mittwoch, 5. November 2003 05:31 schrieb ian douglas:
 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
  [EMAIL PROTECTED]
  http://list.linux-vserver.org/mailman/listinfo/vserver

 ___
 Vserver mailing list
 [EMAIL PROTECTED]
 http://list.linux-vserver.org/mailman/listinfo/vserver

-- 
---
[EMAIL PROTECTED]
tel.: +49 (0)30 / 61 20 26 87
fax: +49 (0)30 / 61 20 26 89
---
lieblinxNET
 we do software
a Marwood  Thiele GbR
---
reichenberger straße 125
10999 Berlin

http://lieblinx.net
---

___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] is there any getting started with vserver documentation anywhere?

2003-11-05 Thread Jan-Hendrik Heuing
At 13:53 05.11.2003, you wrote:
Charles Dale wrote:
Re: compiliing a kernel on SuSE, they should provide a .config file that has
all the configuration options used for compiling the stock kernel.
With RedHat this is in the config/ directory inside the kernel tree. Looking
at a SuSE source RPM I can't see anything similar. Hmm.
On redhat, if the config is in that directory, what is the config file in 
/boot ?

The other thing: I might be wrong with this, but: Isn't it the case that 
redhat provides a patched kernel ? I could not fine the whole source 
kernel. Finally I used a standard vanilla kernel (which I still have little 
problems with).

I could only find some kernel-xxx.src.rpm, but which only installs some 
other directory structure, not like it would be with a vanilla kernel.

Ages ago I searched for the same for rh7.3, that days it was seperated, I 
also had to install kernel-headers etc..., but I can't find these things 
for rh9.

Hints are appreaciated !

JH

___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver


Re: [Vserver] is there any getting started with vserver documentation anywhere?

2003-11-05 Thread Jan-Hendrik Heuing

 Ages ago I searched for the same for rh7.3, that days it was
 seperated, I also had to install kernel-headers etc..., but I can't
 find these things for rh9.

I think running a vanilla kernel on rh9/rhel3 is not a good idea (this
was what I found with taroon at least) - the red hat kernel has NPTL
(native posix thread library) support patched in, and a lot of userspace
things expect this kernel support to be there. If you run a vanilla
kernel (which won't have NPTL) then you will see problems with threaded
apps.
Unfortunately the vserver patches won't patch (yet) against the red hat
patched kernels.
Just to get this right:

- vanilla kernel should not be used on redhat
- vserver does not patch redhat kernel yet
?
It looks a bit like there is no straight way using redhat9 with vserver, am 
I right with this conclusion ?

Anyway, if you still know the place of the kernel sources, I'd still like 
to know, as I can't find them. And I guess at some point there will be 
patches for the redhat kernel.

What would be the way to go ?

Use debian as the host, and maybe use rh vservers ? I'd like to use redhat 
for some things as I know about it. Just looking into debian...

thanks, JH 

___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver


RE: [Vserver] is there any getting started with vserver documentation anywhere?

2003-11-04 Thread ian douglas
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
 [EMAIL PROTECTED]
 http://list.linux-vserver.org/mailman/listinfo/vserver



___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver