>>* Currently, a protocol prefix is only defined to end with a colon, not*
>>* with ":/" or "://". There are already protocol block drivers which do*
>*> not require a slash after the colon such as blkdebug or blkverify and I*
>* >deem it rather impossible to redefine their filename format now (in*
On 03.03.2014 19:03, Eric Blake wrote:
On 03/03/2014 10:47 AM, Max Reitz wrote:
Currently, a protocol prefix is only defined to end with a colon, not
with ":/" or "://". There are already protocol block drivers which do
not require a slash after the colon such as blkdebug or blkverify and I
dee
On 03/03/2014 10:47 AM, Max Reitz wrote:
>
> Currently, a protocol prefix is only defined to end with a colon, not
> with ":/" or "://". There are already protocol block drivers which do
> not require a slash after the colon such as blkdebug or blkverify and I
> deem it rather impossible to redef
On 03.03.2014 15:02, Jun Li wrote:
Such as how to visit glusterfs:
file=gluster://1.2.3.4/testvol/a.img
file=gluster+tcp://1.2.3.4/testvol/a.img
file=gluster+tcp://1.2.3.4:24007/testvol/dir/a.img
file=gluster+tcp://[1:2:3:4:5:6:7:8]/testvol/dir/a.img
file=gluster+tcp://[1:2:3:4:5:6:7:8]:24007/tes
Such as how to visit glusterfs:
file=gluster://1.2.3.4/testvol/a.img
file=gluster+tcp://1.2.3.4/testvol/a.img
file=gluster+tcp://1.2.3.4:24007/testvol/dir/a.img
file=gluster+tcp://[1:2:3:4:5:6:7:8]/testvol/dir/a.img
file=gluster+tcp://[1:2:3:4:5:6:7:8]:24007/testvol/dir/a.img
file=gluster+tcp://ser
