[Vserver] Re: 2.6.16-rc1-vs2.1.0.9 latest test on parisc

> On Wed, Feb 01, 2006 at 07:48:25AM +0100, Joel Soete wrote: > > Hello Herbert, > > > > The latest test seems always ok (I mean no regression imho) on this > > parisc 32bit up kernel ;-) > > great! > > nitpick: let's prefix the tests with [ARCH] in the future > (for ML postings) to simplify search

Re: [Vserver] tagxid mount option

Herbert Poetzl schrieb: how did you try? (i.e. what filesystem, which partition, what options) /dev/sda1 / ext3 defaults,tagxid,errors=remount-ro 0 1 gives failures on reboot, leaving / unaccessible, I have to boot from cdrom and correct (remove the tagxid option)

Re: [Vserver] Re: 2.6.16-rc1-vs2.1.0.9 latest test on parisc

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Herbert Poetzl wrote: > On Wed, Feb 01, 2006 at 01:40:29PM -0500, Micah Anderson wrote: > > Herbert Poetzl wrote: > >>>Btw may I ask you to add this -n (i.e. no_color option) to testme. >>>That would look like: > > >>no problem, will put it into

Re: [Vserver] vhashify on Debian / CoW links not breaking on chmod/chown?

On Wed, Feb 01, 2006 at 06:29:05PM +0100, Grzegorz Nosek wrote: > Hello all, > > I started playing with vserver unification recently and I'd like to > share my two observations: > > - under Debian (sarge at least) you cannot use the supplied beecrypt2 > packages as they have a slightly different

Re: [Vserver] tagxid mount option

On Wed, Feb 01, 2006 at 03:07:56PM +0100, J.Paechnatz wrote: > got vserver working and running some different machines, debian/ubuntu > mixed. so, nice work guys! thanks! > I could not mount with the tagxid option. how did you try? (i.e. what filesystem, which partition, what options) > system

Re: [Vserver] Re: 2.6.16-rc1-vs2.1.0.9 latest test on parisc

On Wed, Feb 01, 2006 at 01:40:29PM -0500, Micah Anderson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Herbert Poetzl wrote: > >>Btw may I ask you to add this -n (i.e. no_color option) to testme. > >>That would look like: > > > > > > no problem, will put it into the next version .

Re: [Vserver] Re: 2.6.16-rc1-vs2.1.0.9 latest test on parisc

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Herbert Poetzl wrote: >>Btw may I ask you to add this -n (i.e. no_color option) to testme. >>That would look like: > > > no problem, will put it into the next version ... > > thanks, > Herbert I thought that the -n (no_color) option was added aft

[Vserver] vhashify on Debian / CoW links not breaking on chmod/chown?

Hello all, I started playing with vserver unification recently and I'd like to share my two observations: - under Debian (sarge at least) you cannot use the supplied beecrypt2 packages as they have a slightly different API (changes are subtle enough that util-vserver will compile but hashcalc wi

Re: [Vserver] Can't rename vserver's host name

Hi there, on Wednesday, February 1, 2006 at 1:28:24 PM there was posted: GH> Whitin the vserver, /etc/hostname file contains "iserv" GH> Any ideas? Palce the hostname on the host in /etc/vservers/[vserver-name]/uts/nodename - this is the file which is used to "create" the hostname on boot. -

[Vserver] tagxid mount option

got vserver working and running some different machines, debian/ubuntu mixed. so, nice work guys! I could not mount with the tagxid option. system is running on: Versions: Kernel: 2.6.12-joh VS-API: 0x00020001 util-vserver: 0.30.208; Dec 3 20

[Vserver] increased security models

I'd like some input or suggestions or combining vservers with some security related patches. I've used vservers and grsecurity (on separate machines), and have dabbed in adamantix-style RSBAC with the debian provided patch package, but I don't have a deep enough vserver knowledge to know what ar

[Vserver] Can't rename vserver's host name

Hi list, we have had a physical machine named iserv running with Suse Linux for quite a while. Now we have migrated the machine to a Debian vserver running in a Debian host (complete new install from scratch). When creating the vserver, I set vserver name=iserv but vserver *host* name=iservn

[Vserver] Re: 2.6.16-rc1-vs2.1.0.9 latest test on parisc

On Wed, Feb 01, 2006 at 07:48:25AM +0100, Joel Soete wrote: > Hello Herbert, > > The latest test seems always ok (I mean no regression imho) on this > parisc 32bit up kernel ;-) great! nitpick: let's prefix the tests with [ARCH] in the future (for ML postings) to simplify searching ... btw, we

Re: [Vserver] please avoid vs2.1.0.5-vs2.1.0.7 ...

Mike O'Connor wrote: Hi Martin http://vserver.13thfloor.at/Experimental/patch-2.6.15-vs2.1.0.5.1.diff This file seems to be missing. http://vserver.13thfloor.at/Experimental/patch-2.6.15.1-vs2.1.0.5.1.diff ___ Vserver mailing list Vserver@list.li

[Vserver] 2.6.16-rc1-vs2.1.0.9 latest test on parisc

Hello Herbert, The latest test seems always ok (I mean no regression imho) on this parisc 32bit up kernel ;-) Linux patst007 2.6.16-rc1-vs2.1.0.9-pa2-d32up #3 Tue Jan 31 08:16:56 CET 2006 parisc GNU/Linux Linux-VServer Test [V0.15] Copyright (C) 2003-2006 H.Poetzl chcontext is working. chbind is

[Vserver] postfix starttls problem in a vserver

Thanks for those /tmp suggestions, for time being I decided to stick with /tmp in RAM. Now I'm having some strange connection warning in postfix logs. Before I run over to the postfix mailing lists, has anyone ran into Feb 1 11:32:01 v64 postfix/smtp[23512]: warning: connect to private/tlsmgr: