On Sun, Nov 23, 2003 at 05:39:23PM -0800, Greg KH wrote:
> On Mon, Nov 24, 2003 at 02:33:42AM +0100, Kay Sievers wrote:
> > On Sat, Nov 22, 2003 at 09:49:18PM -0800, Greg KH wrote:
> > > On Sun, Nov 23, 2003 at 04:54:09AM +0100, Kay Sievers wrote:
> > > > On Sat, Nov 22, 2003 at 03:41:10PM +0100, Kay Sievers wrote:
> > > > > here is a automatic udev test script. To test place it in the test/
> > > > > directory of the current tree to find the sysfs tree copy and run it.
> > > > > 
> > > > > The whole test is self contained, it only needs a matching sysfs tree.
> > > > > To extend the test add a hash to the @tests array inside the script.
> > > > > The script checks the created node and prints a summary of all tests.
> > > > > 
> > > > > Please don't change $udev_root to something useful, its a temorary
> > > > > directory and will be removed after the test run.
> > > > 
> > > > Here is a slightly better version that runs 'tree' on error
> > > > and prints a description for every test.
> > > 
> > > Sweet, this blows away my mess of shell scripts.  I've added this script
> > > to the test/ directory, thanks a lot for this.
> > 
> > We don't want to test the "remove" if "add" fails.
> 
> Why not?  We should remove the same device, right?  That way we end up
> with a clean directory :)

Yes, you are right. If we have two errors we don't want to list
at the second error the node from the first.

But I found two missing characters and optimized $PWD.
You see my queue is empty now :)

thanks,
Kay