Another question I have is, when I mount the URL with ISO, it gets listed in a folder first.
For example
# ./httpfs2-ssl -a /etc/pki/tls/cert.crt https://user:password@10.10.1.1/ISO/file.iso /home/tempmount
# ls /home/tempmount
file.iso.
Then I have to manually mount this a loop device as follows
# mount -o loop file.iso /home/actualmount
Then I can see the actually contents of the ISO.
# ls /home/actualmount `
1.txt 2.txt 3.txt
why can't the httpfs2 mount the ISO directly and show the contents ? Why to mount two times.
The number of loop devices in my system are limited. I can't effort to loose my loop devices for a temporary folders.
Is there a solution for this ?
Thanks
Murali
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Then I have to manually mount this a loop device as follows
mount -o loop file.iso /home/actualmount
Then I can see the actually contents of the ISO.
ls /home/actualmount `
1.txt 2.txt 3.txt
why can't the httpfs2 mount the ISO directly and show the contents ? Why to
mount two times.
This is because httpfs mounts the http location which may be ISO,
squashfs, tar, or anything whatsoever. So it cannot automagically show
its content
The number of loop devices in my system are limited. I can't effort to loose
my loop devices for a temporary folders.
Is there a solution for this ?
You can
- write a script that automagically mounts ISO images for you
- you can release loop devices once done with them so you can also
write a script that does that for you automagically on unmount of your
ISO image
- you can increase the number of loop devices by a parameter (not
sure if only at compile time or at module load time
HTH
Michal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm trying execute the following command to mount the iso from https web server
./httpfs2-ssl -a /etc/pki/tls/cert.crt https://user:password@10.10.1.1/ISO/file.iso /home/tempmount
However, I'm getting the following error.
............
.............
..............
- Key Exchange: RSA
- Protocol: TLS1.2
- Certificate Type: X.509
- Compression: NULL
- Cipher: AES-128-CBC
- MAC: SHA256
Note: SSL paramaters may change as new connections are established to the server.
../httpfs2-ssl: main: closing socket.
./httpfs2-ssl: main: closing SSL socket.
./httpfs2-ssl: main: initializing SSL socket.
./httpfs2-ssl: HEAD: failed with status: 404 Not Found.
HTTP/1.1 404 Not Found
Date: Fri, 15 Jul 2016 22:49:29 GMT
Connection: close
Content-Type: text; charset=plain
Content-Length: 0
./httpfs2-ssl: main: HEAD: exchange: server error
HTTP/1.1 404 Not Found
Date: Fri, 15 Jul 2016 22:49:29 GMT
Connection: close
Content-Type: text; charset=plain
Content-Length: 0
I'm trying with the latest httpfs.c available in repository.
Any help will be appriciated.
Thanks
Murali
Sorry... I got it working, My bad, that I didnt check whether the port 443 is open or not.
Now it works .. Sorry for false alram.
Another question I have is, when I mount the URL with ISO, it gets listed in a folder first.
For example
# ./httpfs2-ssl -a /etc/pki/tls/cert.crt https://user:password@10.10.1.1/ISO/file.iso /home/tempmountThen I have to manually mount this a loop device as follows
# mount -o loop file.iso /home/actualmountThen I can see the actually contents of the ISO.
why can't the httpfs2 mount the ISO directly and show the contents ? Why to mount two times.
The number of loop devices in my system are limited. I can't effort to loose my loop devices for a temporary folders.
Is there a solution for this ?
Thanks
Murali
Hello,
This is because httpfs mounts the http location which may be ISO,
squashfs, tar, or anything whatsoever. So it cannot automagically show
its content
You can
- write a script that automagically mounts ISO images for you
- you can release loop devices once done with them so you can also
write a script that does that for you automagically on unmount of your
ISO image
- you can increase the number of loop devices by a parameter (not
sure if only at compile time or at module load time
HTH
Michal
Understood, Thanks a lot. httpfs2 is very useful.
Last edit: Murali 2016-07-19
One more question, When is the fix for mounting ISO more than 2GB is going to get submitted into the main stream ?
Is this still a problem?
It should work 0.1.5 and later.