From: Niall O Broin (niall at domain linux.ie)
Date: Mon 20 Aug 2001 - 13:43:11 IST
On Fri, Aug 17, 2001 at 08:14:29PM +0100, John Gay wrote:
> After several sugestions that I needed to file system modules as well, on the
> Advice of the original instigator of using nbd for local floppy access, I
> added the msdos and fat modules to the floppy module the workstation loads on
> boot-up. Now I can mount the floppy from a root shell on the workstation! YEA
As previously mentioned, I very much doubt if you require the file system
modules on the server at all. What you eventually want is for the client to
be able to mount filesystems from floppies - then the client needs the
appropriate filesystem modules. As the name suggests, the server is
exporting a block device and this is below the filesystem. Yes, you require
them to test the floppy if you want to see if you can mount a DOS formatted
disk, but you can test the floppy in other ways e.g. create a tar file on it
tar cvf /dev/fd0 somefiles
Try that with the floppy module loaded but WITHOUT loading the msdos or fat
modules - it should work fine.
> Now I tried the nbd client from the terminal server and it connected! Even
> Better! The only problem now is, I can't seem to do anything else with it.
> The nbd-client connects to the nbd-server and I even get a brief light on the
> floppy drive on the workstation, but nothing else seems to happen. I can't
> mount /home/jgay/.dev/fd0, this command just hangs. Also, there is still the
> problem with the ioctl lock-up mentioned by Jason, who has also been working
> on this.
On the client you won't be able to mount filesystems UNLESS you have the
appropriate modules loaded (or compiled into the kernel, of course). The
fact that you get a brief light on the floppy drive on the workstation
sounds good because this means that the server has looked at the floppy (it
does this to make sure that there is a floppy there, and that it can write
to it, unless you specify the appropriate option for read only operation.
Having successfully created the tar file on the floppy as above, then run
nbd-client and see what happens when you do
tar tf /home/jgay/.dev/fd0
You should get a list of the files in the tar file (somefiles as above).
If that all works, and I believe it should, then your problems with mounting
floppies are filesystem related. Using tar for tests cuts out the filesystem
layer - when you're trying to get something new working, the simpler you can
make it, the better.
> The end result I'm looking for is to put icon's on the KDE desktop for floppy
> and CD and have them automagically mount and umount the devices on demand.
I'm not sure that you'll ever be able to make this as transparent as you'd
like. For CDs, yes, I'd imagine it should be possible. However, floppies are
a different issue. If you can live with the restriction that you must only
insert writable floppies, then it might fly, but as the server has to be
started with a special option for read-only media, and as the server will be
started when the terminal boots, what do you do ? I imagine the only option
is to explain to the users that write-protected floppies won't work. AFAIR
if you try to use a write-protected floppy without using the switch you run
into the server hanging problem and even if you kill it, you have to use a
different port when you try again.
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:11:44 GMT