Sometime on May 13, Satya assembled some asciibets to say:
> Some versions of (*nix) mount can mount a disk image file so it appears
> like a real disk... You can do all the usual copy/move/rm operations. Can
> windows mount an image file like that?
I don't think windows can do this. It doesn't mount disks anyway -
they're just already there.
What I want to know now - and this is something Amit and I spoke about on
Saturday - is can you mount a non disk device?
This is okay:
# mount /dev/hda3 /usr
This may also be okay:
# mount /images/mybin.img /home/philip/bin
Where mybin.img would be a file that is basically an image of an ext2
diskette containing all my bin files.
In this case, the file system is stored in the file, so it's probably
okay.
But this may not be okay:
# mount /dev/zero /some/where
Mainly because /dev/zero has no filesystem in it. Any calls that the
kernel makes to it will just return null so you'd probably just get a file
system not found error when you try to mount it.
Well, actually it would fail simply because /dev/zero is not a block
device. But what if we had a block equivalent of /dev/zero Then what?
Philip
<offtopic for satya>
> What's an asciibet?
A character from the ASCII character set. The jargon file has an entry
for ASCIIbetical order - ordered by collation sequence rather than simply
alphabetic order. The difference being - alphabetic (AaBbCc..Zz),
asciibetic (ABC..Zabc..z)
</offtopic for satya>
--
Real programs don't eat cache.
To subscribe / unsubscribe goto the site www.ilug-bom.org ., click on the mailing list
button and fill the appropriate information
and submit. For any other queries contact the ML maintener
