loop back broken in 2.2.14
I thought that the -pre would be the developer kernels, and that an actual release (2.4.14) would have been somewhat tested. I fully understand that a 'runtime' bug in the vm or some other system could arrise and that is one thing. I also understand when a 'less used' driver like NTFS or VFAT breaks, but to see bugs in the loop device in a 'stabilizing' kernel is something that I thought I'd never see.
Hmm anyone working on a regression testing tool for the kernel compilation options??
Also new features DO go into stable trees, there are many times when 2.3.x was open that stuff was backported to 2.2.x. I also heard that ext3 might end up in 2.4.15, which I'd love to see happen (that and lm_sensors)
I DO think that there needs to be a better way of handling some of these small bugs. Like maybe where the kernel is posted (in my case obtaining from ftp.kernel.org) there should be a readme.first.2.4.14 for every version of the kernel and in there things like this could be stated. Simple one line in loop.c commment out the two lines or remove the two lines with deactivate_page.
I don't mind 'testing', but how can you test what wont compile or what compiles but does not run?
Joe
Quoted 1 line · John Alvord
In developer-speak, stable == stablizing, which means that fixes go in
but no new features. That can include monstrous fixes like the VM cleanup.
When you are running developer kernels, you are on the kernel test team whether you know it or not, whether you think thats OK or hate it.
For "stable" kernels, wait for the distributors like red hat/suse/etc. There is no way around serious testing which they perform.
john
Quoted 29 lines · On Mon, 12 Nov 2001 12:40:43 -0500, [email protected] wrote:
Okay, I can delete out those two lines to get loop working.
Is 2.4.x really a stable tree? Or should I wait for 2.4.25 before I consider it really stable?
Quoted 10 lines
Quoted 7 lines
Quoted 2 lines · François Cami
yes, see 2.4.15pre1
warning, the iptables code in 2.4.15pre1 and pre2 seems broken.and further it is likely that pre3 fixes iptables code :) (it looks like the patch got reverted)
Actually it doesn't seem to be reverted,
just reworked -hmm, spoke too soon -
looks like they were reverted after all...
cu
jjs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)
Something definitely should be done to help "stabilize" the tree; it's not really a big deal for most of us if something is broken, as you know there will be a fix posted very soon after the release, _but_ bugs like these don't exactly make Linux "look good" to the rest of the UNIX community. A FreeBSD advocate might say "well, FreeBSD never does _that_". My suggestion to help fix the problem would be to do what SGI does; have two seperate trees that strive to stay as close to each other as possible, but one becomes part of the "maintaince stream", where only bug fixes and the such are added, and a "features stream", where actual new features are added in. Take a look at some of the IRIX web pages at http://www.sgi.com/ for a better idea of how that works, but believe me, it works. This would be in addition to some sort of testing suite that each official kernel must pass before it is released. With the growing number of (important/big) Linux users, we must make sure each kernel is rock-solid before being released. This is definitely more of a political topic than a technical one, but it has to be addressed nonetheless.
-----------------------------------------------
Sean P. Elble
Editor, Writer, Co-Webmaster
ReactiveLinux.com (Formerly MaximumLinux.org)
http://www.reactivelinux.com/
[email protected]
-----------------------------------------------
----- Original Message -----
From: <[email protected]>
To: "John Alvord" <[email protected]>
Cc: <[email protected]>
Sent: Monday, November 12, 2001 3:27 PM
Subject: Re: Re: loop back broken in 2.2.14
Quoted 1 line
I thought that the -pre would be the developer kernels, and that an actual
release (2.4.14) would have been somewhat tested. I fully understand that a 'runtime' bug in the vm or some other system could arrise and that is one thing. I also understand when a 'less used' driver like NTFS or VFAT breaks, but to see bugs in the loop device in a 'stabilizing' kernel is something that I thought I'd never see.
Quoted 2 lines
Hmm anyone working on a regression testing tool for the kernel compilation
options??
Quoted 2 lines
Also new features DO go into stable trees, there are many times when 2.3.x
was open that stuff was backported to 2.2.x. I also heard that ext3 might end up in 2.4.15, which I'd love to see happen (that and lm_sensors)
Quoted 2 lines
I DO think that there needs to be a better way of handling some of these
small bugs. Like maybe where the kernel is posted (in my case obtaining from ftp.kernel.org) there should be a readme.first.2.4.14 for every version of the kernel and in there things like this could be stated. Simple one line in loop.c commment out the two lines or remove the two lines with deactivate_page.
Quoted 2 lines
I don't mind 'testing', but how can you test what wont compile or what
compiles but does not run?
Quoted 11 lines
Joe
Quoted 1 line · John Alvord
In developer-speak, stable == stablizing, which means that fixes go in
but no new features. That can include monstrous fixes like the VM cleanup.
When you are running developer kernels, you are on the kernel test team whether you know it or not, whether you think thats OK or hate it.
Quoted 11 lines
For "stable" kernels, wait for the distributors like red hat/suse/etc. There is no way around serious testing which they perform.
john
Quoted 3 lines · On Mon, 12 Nov 2001 12:40:43 -0500, [email protected] wrote:
Okay, I can delete out those two lines to get loop working.
Is 2.4.x really a stable tree? Or should I wait for 2.4.25 before I
consider it really stable?
Quoted 16 lines
Quoted 16 lines
Quoted 11 lines
Quoted 8 lines
Quoted 2 lines · François Cami
yes, see 2.4.15pre1
warning, the iptables code in 2.4.15pre1 and pre2 seems broken.and further it is likely that pre3 fixes iptables code :) (it looks like the patch got reverted)
Actually it doesn't seem to be reverted,
just reworked -hmm, spoke too soon -
looks like they were reverted after all...
Quoted 7 lines
Quoted 7 lines
cu
jjs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
in
Quoted 10 lines
Quoted 3 lines
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)
In reply to [email protected]I guess the way I'd do it would be to actually freeze [in which I mean no more 'testing' patch are applied] a pre something, say 2.4.XpreY for example, see if there are any obvious bugs in it (like the loopback in 2.4.14), correct them, test again, and if it's okay, release 2.4.X.
Of course, I've never done much kernel work except testing, so I'm not exactly the one who should talk about it.
Still, I think that from the user point of view (and there was a post in LKML yesterday, about Linux being used by UN*X experienced sysadmins only... or going mainstream instead) the releases should be tested a bit more thoroughly and actually *frozen* for some time (a day or two should suffice I guess) before being labelled 2.4.X.
Just the two cents from a newbie - I hope/mean to offense noone with that
François Cami
Quoted 112 lines · Sean Elble
Something definitely should be done to help "stabilize" the tree; it's not really a big deal for most of us if something is broken, as you know there will be a fix posted very soon after the release, _but_ bugs like these don't exactly make Linux "look good" to the rest of the UNIX community. A FreeBSD advocate might say "well, FreeBSD never does _that_". My suggestion to help fix the problem would be to do what SGI does; have two seperate trees that strive to stay as close to each other as possible, but one becomes part of the "maintaince stream", where only bug fixes and the such are added, and a "features stream", where actual new features are added in. Take a look at some of the IRIX web pages at http://www.sgi.com/ for a better idea of how that works, but believe me, it works. This would be in addition to some sort of testing suite that each official kernel must pass before it is released. With the growing number of (important/big) Linux users, we must make sure each kernel is rock-solid before being released. This is definitely more of a political topic than a technical one, but it has to be addressed nonetheless.
-----------------------------------------------
Sean P. Elble
Editor, Writer, Co-Webmaster
ReactiveLinux.com (Formerly MaximumLinux.org)
http://www.reactivelinux.com/
[email protected]
---------------------------------------------------- Original Message -----
From: <[email protected]>
To: "John Alvord" <[email protected]>
Cc: <[email protected]>
Sent: Monday, November 12, 2001 3:27 PM
Subject: Re: Re: loop back broken in 2.2.14Quoted 2 lines
I thought that the -pre would be the developer kernels, and that an actual
release (2.4.14) would have been somewhat tested. I fully understand that a 'runtime' bug in the vm or some other system could arrise and that is one thing. I also understand when a 'less used' driver like NTFS or VFAT breaks, but to see bugs in the loop device in a 'stabilizing' kernel is something that I thought I'd never see.
Quoted 2 lines
Hmm anyone working on a regression testing tool for the kernel compilation
options??
Quoted 2 lines
Also new features DO go into stable trees, there are many times when 2.3.x
was open that stuff was backported to 2.2.x. I also heard that ext3 might end up in 2.4.15, which I'd love to see happen (that and
lm_sensors)Quoted 2 lines
I DO think that there needs to be a better way of handling some of these
small bugs. Like maybe where the kernel is posted (in my case obtaining from ftp.kernel.org) there should be a readme.first.2.4.14 for every version of the kernel and in there things like this could be stated. Simple one line in
loop.ccommment out the two lines or remove the two lines withdeactivate_page.Quoted 2 lines
I don't mind 'testing', but how can you test what wont compile or what
compiles but does not run?
Quoted 12 lines
Joe
Quoted 2 lines · John Alvord
In developer-speak, stable == stablizing, which means that fixes go in
but no new features. That can include monstrous fixes like the VM cleanup.
When you are running developer kernels, you are on the kernel test team whether you know it or not, whether you think thats OK or hate it.
Quoted 13 lines
For "stable" kernels, wait for the distributors like red hat/suse/etc. There is no way around serious testing which they perform.
john
Quoted 4 lines · On Mon, 12 Nov 2001 12:40:43 -0500, [email protected] wrote:
Okay, I can delete out those two lines to get loop working.
Is 2.4.x really a stable tree? Or should I wait for 2.4.25 before I
consider it really stable?
Quoted 22 lines
Quoted 22 lines
Quoted 12 lines
Quoted 9 lines
Quoted 3 lines · François Cami
yes, see 2.4.15pre1
warning, the iptables code in 2.4.15pre1 and pre2 seems broken.and further it is likely that pre3 fixes iptables code :) (it looks like the patch got reverted)
Actually it doesn't seem to be reverted,
just reworked -hmm, spoke too soon -
looks like they were reverted after all...
cu
jjs
-
Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)
In reply to [email protected]Can't argue with you on the respect that kernels should be tested, but I _can_ argue with you on your method. :-) The main problem that I see there is that you are then limiting yourself (well not you, but just making things hypothetical) to a certain number of test kernels. What if another problem is found after the freeze? Testing should be done any time Linus gets ready to release a kernel, though a feature freeze wouldn't be a bad idea. I'm still wondering what the best solution is though . . .
-----------------------------------------------
Sean P. Elble
Editor, Writer, Co-Webmaster
ReactiveLinux.com (Formerly MaximumLinux.org)
http://www.reactivelinux.com/
[email protected]
-----------------------------------------------
----- Original Message -----
From: "François Cami" <[email protected]>
To: "Sean Elble" <[email protected]>
Cc: <[email protected]>; "John Alvord" <[email protected]>; <[email protected]>
Sent: Monday, November 12, 2001 7:37 PM
Subject: Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)
I guess the way I'd do it would be to actually freeze [in which I mean no more 'testing' patch are applied] a pre something, say 2.4.XpreY for example, see if there are any obvious bugs in it (like the loopback in 2.4.14), correct them, test again, and if it's okay,
release 2.4.X.
Of course, I've never done much kernel work except testing, so I'm not exactly the one who should talk about it.
Still, I think that from the user point of view (and there was a post in LKML yesterday, about Linux being used by UN*X experienced sysadmins only... or going mainstream instead) the releases should be tested a bit more thoroughly and actually *frozen* for some time (a day or two should suffice I guess) before being labelled 2.4.X.
Just the two cents from a newbie - I hope/mean to offense noone with that
François Cami
Quoted 5 lines · Sean Elble
Something definitely should be done to help "stabilize" the tree; it's not really a big deal for most of us if something is broken, as you know there will be a fix posted very soon after the release, _but_ bugs like these don't exactly make Linux "look good" to the rest of the UNIX community. A FreeBSD advocate might say "well, FreeBSD never does _that_". My
suggestion
Quoted 4 lines
to help fix the problem would be to do what SGI does; have two seperate trees that strive to stay as close to each other as possible, but one becomes part of the "maintaince stream", where only bug fixes and the such are added, and a "features stream", where actual new features are added
in.
Quoted 25 lines
Take a look at some of the IRIX web pages at http://www.sgi.com/ for a better idea of how that works, but believe me, it works. This would be in addition to some sort of testing suite that each official kernel must pass before it is released. With the growing number of (important/big) Linux users, we must make sure each kernel is rock-solid before being released. This is definitely more of a political topic than a technical one, but it has to be addressed nonetheless.
-----------------------------------------------
Sean P. Elble
Editor, Writer, Co-Webmaster
ReactiveLinux.com (Formerly MaximumLinux.org)
http://www.reactivelinux.com/
[email protected]
---------------------------------------------------- Original Message -----
From: <[email protected]>
To: "John Alvord" <[email protected]>
Cc: <[email protected]>
Sent: Monday, November 12, 2001 3:27 PM
Subject: Re: Re: loop back broken in 2.2.14
Quoted 3 lines
Quoted 2 lines
I thought that the -pre would be the developer kernels, and that an actual
release (2.4.14) would have been somewhat tested. I fully understand that
a
Quoted 2 lines
'runtime' bug in the vm or some other system could arrise and that is one thing. I also understand when a 'less used' driver like NTFS or VFAT
breaks,
Quoted 9 lines
but to see bugs in the loop device in a 'stabilizing' kernel is something that I thought I'd never see.
Quoted 2 lines
Hmm anyone working on a regression testing tool for the kernel compilation
options??
Quoted 2 lines
Also new features DO go into stable trees, there are many times when 2.3.x
Quoted 7 lines
was open that stuff was backported to 2.2.x. I also heard that ext3 might end up in 2.4.15, which I'd love to see happen (that and
lm_sensors)Quoted 2 lines
I DO think that there needs to be a better way of handling some of these
small bugs. Like maybe where the kernel is posted (in my case obtaining from ftp.kernel.org) there should be a readme.first.2.4.14 for every
version
Quoted 57 lines
of the kernel and in there things like this could be stated. Simple one line in
loop.ccommment out the two lines or remove the two lines withdeactivate_page.Quoted 2 lines
I don't mind 'testing', but how can you test what wont compile or what
compiles but does not run?
Quoted 12 lines
Joe
Quoted 2 lines · John Alvord
In developer-speak, stable == stablizing, which means that fixes go in
but no new features. That can include monstrous fixes like the VM cleanup.
When you are running developer kernels, you are on the kernel test team whether you know it or not, whether you think thats OK or hate it.
Quoted 13 lines
For "stable" kernels, wait for the distributors like red hat/suse/etc. There is no way around serious testing which they perform.
john
Quoted 4 lines · On Mon, 12 Nov 2001 12:40:43 -0500, [email protected] wrote:
Okay, I can delete out those two lines to get loop working.
Is 2.4.x really a stable tree? Or should I wait for 2.4.25 before I
consider it really stable?
Quoted 22 lines
Quoted 22 lines
Quoted 12 lines
Quoted 9 lines
Quoted 3 lines · François Cami
yes, see 2.4.15pre1
warning, the iptables code in 2.4.15pre1 and pre2 seems broken.and further it is likely that pre3 fixes iptables code :) (it looks like the patch got reverted)
Actually it doesn't seem to be reverted,
just reworked -hmm, spoke too soon -
looks like they were reverted after all...
cu
jjs
-
Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)
In reply to [email protected]I am wondering too... Anyone got ideas on this ?
I would like to avoid some specific problems... especially bugs that show up when compiling a certain module / feature of the kernel, like the loopback in 2.4.14.
Those should be very easy to get rid of
[it only takes some kernel testers to debug that early, if only there actually were a feature freeze that last for one day...].
François
Quoted 82 lines · Sean Elble
Can't argue with you on the respect that kernels should be tested, but I _can_ argue with you on your method. :-) The main problem that I see there is that you are then limiting yourself (well not you, but just making things hypothetical) to a certain number of test kernels. What if another problem is found after the freeze? Testing should be done any time Linus gets ready to release a kernel, though a feature freeze wouldn't be a bad idea. I'm still wondering what the best solution is though . . .
-----------------------------------------------
Sean P. Elble
Editor, Writer, Co-Webmaster
ReactiveLinux.com (Formerly MaximumLinux.org)
http://www.reactivelinux.com/
[email protected]
---------------------------------------------------- Original Message -----
From: "François Cami" <[email protected]>
To: "Sean Elble" <[email protected]>
Cc: <[email protected]>; "John Alvord" <[email protected]>; <[email protected]>
Sent: Monday, November 12, 2001 7:37 PM
Subject: Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)I guess the way I'd do it would be to actually freeze [in which I mean no more 'testing' patch are applied] a pre something, say 2.4.XpreY for example, see if there are any obvious bugs in it (like the loopback in 2.4.14), correct them, test again, and if it's okay,
release 2.4.X.Of course, I've never done much kernel work except testing, so I'm not exactly the one who should talk about it.
Still, I think that from the user point of view (and there was a post in LKML yesterday, about Linux being used by UN*X experienced sysadmins only... or going mainstream instead) the releases should be tested a bit more thoroughly and actually *frozen* for some time (a day or two should suffice I guess) before being labelled 2.4.X.
Just the two cents from a newbie - I hope/mean to offense noone with that
François Cami
Quoted 6 lines · Sean Elble
Something definitely should be done to help "stabilize" the tree; it's not really a big deal for most of us if something is broken, as you know there will be a fix posted very soon after the release, _but_ bugs like these don't exactly make Linux "look good" to the rest of the UNIX community. A FreeBSD advocate might say "well, FreeBSD never does _that_". My
suggestion
Quoted 5 lines
to help fix the problem would be to do what SGI does; have two seperate trees that strive to stay as close to each other as possible, but one becomes part of the "maintaince stream", where only bug fixes and the such are added, and a "features stream", where actual new features are added
in.
Quoted 16 lines
Take a look at some of the IRIX web pages at http://www.sgi.com/ for a better idea of how that works, but believe me, it works. This would be in addition to some sort of testing suite that each official kernel must pass before it is released. With the growing number of (important/big) Linux users, we must make sure each kernel is rock-solid before being released. This is definitely more of a political topic than a technical one, but it has to be addressed nonetheless.
-----------------------------------------------
Sean P. Elble
Editor, Writer, Co-Webmaster
ReactiveLinux.com (Formerly MaximumLinux.org)
http://www.reactivelinux.com/
[email protected]
-----------------------------------------------
Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)
In reply to [email protected]Umm... Linus, when are you going to open the 2.5.x development cycle? That is how we used to catch this kind of thing.
Matthew D. Pitts
Pitts Computer Services
[email protected]
----- Original Message -----
From: "François Cami" <[email protected]>
To: "Sean Elble" <[email protected]>
Cc: <[email protected]>; "John Alvord" <[email protected]>; <[email protected]>
Sent: Monday, November 12, 2001 8:03 PM
Subject: Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)
Quoted 12 lines
I am wondering too... Anyone got ideas on this ?
I would like to avoid some specific problems... especially bugs that show up when compiling a certain module / feature of the kernel, like the loopback in 2.4.14.
Those should be very easy to get rid of
[it only takes some kernel testers to debug that early, if only there actually were a feature freeze that last for one day...].François
Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)
In reply to [email protected]Quoted 2 lines · Matthew D. Pitts
Umm... Linus, when are you going to open the 2.5.x development cycle? That is how we used to catch this kind of thing.
*eager to test 2.5* I guess that's one good idea, yes... less 'beta' in the current 'stable' tree means that there actually is a dev tree.
And we're back at what Sean Elble wrote about SGI having two trees for IRIX.
François
Quoted 35 lines
Matthew D. Pitts
Pitts Computer Services
[email protected]
----- Original Message -----
From: "François Cami" <[email protected]>
To: "Sean Elble" <[email protected]>
Cc: <[email protected]>; "John Alvord" <[email protected]>; <[email protected]>
Sent: Monday, November 12, 2001 8:03 PM
Subject: Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)Quoted 6 lines
I am wondering too... Anyone got ideas on this ?
I would like to avoid some specific problems... especially bugs that show up when compiling a certain module / feature of the kernel, like the loopback in 2.4.14.
Quoted 6 lines
Those should be very easy to get rid of
[it only takes some kernel testers to debug that early, if only there actually were a feature freeze that last for one day...].François
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)
In reply to [email protected]The feature freeze certainly seems to be an important part of things . . . now we just need to determine what we want to happen during and after the feature freeze. :-) I certainly think Linus' Linux should be in a CVS tree, and he should patch to that; in addition, other developers, like Alan Cox, should have commit access to the tree, but Linus has already shown that he doesn't want that. Either way, I say "testing, testing, testing!". :-)
-----------------------------------------------
Sean P. Elble
Editor, Writer, Co-Webmaster
ReactiveLinux.com (Formerly MaximumLinux.org)
http://www.reactivelinux.com/
[email protected]
-----------------------------------------------
----- Original Message -----
From: "François Cami" <[email protected]>
To: "Sean Elble" <[email protected]>
Cc: <[email protected]>; "John Alvord" <[email protected]>; <[email protected]>
Sent: Monday, November 12, 2001 8:03 PM
Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)
In reply to [email protected]Quoted 5 lines
I am wondering too... Anyone got ideas on this ?
I would like to avoid some specific problems... especially bugs that show up when compiling a certain module / feature of the kernel, like the loopback in 2.4.14.
Why not introduce a linux-2.4.xx-rc?
If there is no compile error or huge problem it will become linux-2.4.xx __without__ any change after 1 day.
If there is a problem, only a patch for this problem is applied. Just an idea
greetings
Christian
Well, the loopback bug is a pain.. but we have had these pains on quite a few releases in the 2.4.x series...
I wonder if maybe a new method of distributing kernels should happen.. 2.4.14 should become 2.4.14-stable meaning that it never ever changes after release, and 2.4.14-fixed means that these tiny typos, gotchas, and backport driver fixes can get into 2.4.14-fixed which may change from day to day, but not get any enhancements, only minor fixes..
People could try 2.4.14-stable, and if they have a problem, they could just try the 2.4.14-fixed to see if their problem is already addressed...
The idea is that at least every major release kernel should compile, and it would reduce the noise levels from people trying out *stable* kernel versions..
Just a thought..
Quoted 2 lines · On Mon, 2001-11-12 at 12:27, [email protected] wrote:
I thought that the -pre would be the developer kernels, and that an actual release (2.4.14) would have been somewhat tested. I fully understand that a 'runtime' bug in the vm or some other system could arrise and that is one thing. I also understand when a 'less used' driver like NTFS or VFAT breaks, but to see bugs in the loop device in a 'stabilizing' kernel is something that I thought I'd never see.
Signature · 9 lines
"Catch the Magic of Linux..." -------------------------------------------------------- Michael Peddemors - Senior Consultant LinuxAdministration - Internet Services NetworkServices - Programming - Security Wizard IT Services http://www.wizard.ca Linux Support Specialist - http://www.linuxmagic.com -------------------------------------------------------- (604)589-0037 Beautiful British Columbia, Canada