11-19-2005
Sharing ISO images over NFS
I've got a bunch of application CDs that I use here at home under Wine. They are Windows applications and as such, some of them want to see the volume label in order for the application to run. So... just copying the CD-ROM contents to a directory doesn't work. With that in mind, what I've done in the past is make ISO images of the CD-ROMs on my hard drives and mount them locally. The mounted device is then mapped to "Drive D:" in Wine. This has always worked well. But I wanted to prevent wasting HD space on my clients, so I centralized the ISOs on a server. Until now, I've been using Samba to share those ISOs but seeing that I no longer have any Windows boxes, I've been moving away from Samba and onto NFS. However, I now have a problem. If I mount 'server:/mnt/data/cdserv' on /mnt/data/cdserv on the client, I can see my ISO images. No problem. But when I try to mount one of those ISO images to /mnt/cdrom1. I get a "permission denied" error.
While testing, I tried to manually associate /dev/loop0 with /mnt/data/cdserv/abh12.iso and I got the same "permission denied" error. So it sounds like the process fails when setting up a loop device. What is odd is that iso9660 is a read only file system. I have the NFS server exporting 'ro' and the export is mounted 'ro'. So my guess is that the "permission denied" error is being caused by the loop set up and nothing else. Any ideas why? Do I need to use a special option with losetup if I set the loop device up manually? Or is it an NFS export or mount issue? Is there some aspect of the ISO image that's not getting carried over NFS? This worked very well for me under Samba, but I really don't need Samba anymore and would hate to keep it around for just this one application.
One more thing I just discovered. I created a looped ext2 filesystem image and put it in the same location that my ISOs are. I tried to mount it via nfs as a loop device and got the same "permission denied" error. So it definitely seems that losetup/loop devs don't like to be exported via NFS. I'm still not sure why though since NFS seems to act like a normal filesystem in every other regard. Still searching for an answer...
Last edited by deckard; 11-19-2005 at 04:08 AM..
7 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Whenever I try to burn an iso image on to a CD, the CD doesn't work. I use the program "CD Writing Wizard" on windows. I also tried Roxio. :confused: Can u help me.
Thank you for your replies :D :D :D :D (0 Replies)
Discussion started by: faron17
0 Replies
2. AIX
Hi Guys,
How to mount ISO images in AIX environment.
I know how to do it in Solaris.
Thanks
Manu (0 Replies)
Discussion started by: b_manu78
0 Replies
3. Linux
Hi,
I have created symlink under /.
It is /latest Pointing to /home/users/neel_prog_V1.0.
(Note: I have created this symlink so that when version get changed I will need to change only symlink instead of doing changes in /etc/exports.)
I have shared this symlink with NFS. in /etc/exports I... (0 Replies)
Discussion started by: neel.gurjar
0 Replies
4. High Performance Computing
I'm planning to load balance 2 web servers. I'm considering mounting an NFS share between the 2 servers so they can share the data. My question is: does this setup offset some of the benefits of load balancing? although there are 2 web servers, they both still access a single NFS server. Wouldn't... (2 Replies)
Discussion started by: gaspol
2 Replies
5. Solaris
Hi,
Not sure where to post this, I'm sorry and need suggestion if this is wrong section.
we are running NFS Server on Solaris 10 and client box is HP-UX 11.11 (Can't apply latest patches/upgrades as in-house appln. doesn't allow)
I am able to mount NFS shares from this Solaris box onto all... (4 Replies)
Discussion started by: prvnrk
4 Replies
6. UNIX for Dummies Questions & Answers
I am not sure is this plausible...
I have just built a NFS master server on a solaris box (secured by NIS)
And I have a dozen of virtual machines running 32 and 64 bits linux and windows, running different types of servers.
I am not sure is it possible to move most of the programs to the... (6 Replies)
Discussion started by: xstaci
6 Replies
7. UNIX for Dummies Questions & Answers
Hello,
I would like to share a 9p (Plan 9) passthrough/share to a VM via NFS (using a guest as an NFS server to share a directory from the host)
At the moment I am getting the error message: 'exportfs: /share does not support NFS export'... (2 Replies)
Discussion started by: Scratch
2 Replies
LEARN ABOUT CENTOS
wineserver
WINESERVER(1) Windows on Unix WINESERVER(1)
NAME
wineserver - the Wine server
SYNOPSIS
wineserver [options]
DESCRIPTION
wineserver is a daemon process that provides to Wine roughly the same services that the Windows kernel provides on Windows.
wineserver is normally launched automatically when starting wine(1), so you shouldn't have to worry about it. In some cases however, it can
be useful to start wineserver explicitly with different options, as explained below.
OPTIONS
-d[n], --debug[=n]
Set the debug level to n. 0 means no debugging information, 1 is the normal level, and 2 is for extra verbose debugging. If n is
not specified, the default is 1. The debug output will be sent to stderr. wine(1) will automatically set the debug level when start-
ing wineserver if the +server option is set in the WINEDEBUG variable.
-f, --foreground
Make the server remain in the foreground for easier debugging, for instance when running it under a debugger.
-h, --help
Display a help message.
-k[n], --kill[=n]
Kill the currently running wineserver, optionally by sending signal n. If no signal is specified, sends a SIGINT first and then a
SIGKILL. The instance of wineserver that is killed is selected based on the WINEPREFIX environment variable.
-p[n], --persistent[=n]
Specify the wineserver persistence delay, i.e. the amount of time that the server will keep running when all client processes have
terminated. This avoids the cost of shutting down and starting again when programs are launched in quick succession. The timeout n
is in seconds, the default value is 3 seconds. If n is not specified, the server stays around forever.
-v, --version
Display version information and exit.
-w, --wait
Wait until the currently running wineserver terminates.
ENVIRONMENT VARIABLES
WINEPREFIX
If set, the content of this variable is taken as the name of the directory where wineserver stores its data (the default is
$HOME/.wine). All wine processes using the same wineserver (i.e.: same user) share certain things like registry, shared memory and
kernel objects. By setting WINEPREFIX to different values for different Wine processes, it is possible to run a number of truly
independent Wine sessions.
WINESERVER
Specifies the path and name of the wineserver binary that will be launched automatically by wine. If not set, wine will try to load
/usr/bin/wineserver, and if this doesn't exist it will then look for a file named wineserver in the path and in a few other likely
locations.
FILES
~/.wine
Directory containing user specific data managed by wine.
/tmp/.wine-uid
The directory containing the server Unix socket and the lock file. These files are created in a subdirectory generated from the
WINEPREFIX directory device and inode numbers.
AUTHORS
The original author of wineserver is Alexandre Julliard. Many other people have contributed new features and bug fixes. Please check the
file Changelog in the Wine distribution for the complete details.
BUGS
If you find a bug, please submit a bug report at http://bugs.winehq.org. <http://bugs.winehq.org>
AVAILABILITY
wineserver is part of the Wine distribution, which is available through WineHQ, the Wine development headquarters, at
http://www.winehq.org/. <http://www.winehq.org/>
SEE ALSO
wine(1).
Wine 1.2-rc6 October 2005 WINESERVER(1)