>> > Please test the version in unstable as it might fix your problem. >> Tested the version from unstable, think it was 0.30.204-1. > That is the latest version. The package page also lists 0.30.204-2 but it doesn't seem to be available yet. The changelog also doesn't suggest it will be any different.
Should I report this upstream then? >> > It would be nice for me to know if it fix the problem or not. >> It didn't seem to, but it's possible I didn't get the very latest >> version (I used the one from the UK mirror) - I'll try again later. > Ok. It may be that you use too long names, or actually I quite > sure that it is the problem. Longer names are supported but not > if they have the same start name. How long is too long? I don't recall finding any limits in any of the documentation. Given the device is 'eth0:mjb-' I guess that it will be a problem if the first four letters of the name are the same. I created another vserver called test which didn't seem to clash or cause problems so I think that's the problem. BTW what's the difference between kernel-patch-vserver and kernel-patch-ctx - they appear to be the same. Also what's the status of vserver / util-vserver on SPARC, I suspect I'll need to use it on a large SMP sun4u machine so if you need any help debugging it I'm happy to help. Cheers, - Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
