Re: Help/problems with blktap on xen-unstable

[Roland Paterson-Jones <roland@rolandpj.com>]

Roland Paterson-Jones wrote:

>  So, I guess I need to recompile with an alternate device major number.

I can find the following refs to 254 in the source (some are dups):

./linux-2.6.16.13-xen0/drivers/xen/blktap/blktap.c:              
major=254, minor numbers begin at 0            */
./linux-2.6.16.13-xen0/drivers/xen/blktap/blktap.c:#define 
BLKTAP_DEV_MAJOR 254         /* TODO: Make major number dynamic  *
./linux-2.6-xen-sparse/drivers/xen/blktap/blktap.c:              
major=254, minor numbers begin at 0            */
./linux-2.6-xen-sparse/drivers/xen/blktap/blktap.c:#define 
BLKTAP_DEV_MAJOR 254         /* TODO: Make major number dynamic  *
./tools/blktap/lib/blktaplib.h:#define BLKTAP_DEV_MAJOR 254
./tools/blktap/drivers/blktapctrl.c:    make_blktap_dev(devname,254,0);
./tools/blktap_user/aiotools/blktapctrl.c:    
make_blktap_dev(devname,254,0);
./tools/blktap_user/blktaplib.h:#define BLKTAP_DEV_MAJOR 254

I'm guessing it would be good to have one definition, but I'm not too 
familiar with the code structure. Can a .h file span kernel and user 
source? Also, any idea what is meant by making major number 'dynamic' - 
are they proposing walking the major numbers in code until successful, 
or just a config option somewhere (where?).

Regards
Roland