Skip to contentSkip to conversation

loopback on block device

DISCUSSION Lei Yang 4 participants 6 messages Oct 27, 2004 – Oct 28, 2004

lore
Share & tools
lore

Lei Yang

author
#0 lore raw

Hello,

Here is a question for loopback device. As far as I understand, the loopback device is used to mount files as if they were block devices.

Then Why I could do "losetup -e XOR /dev/loop0 /dev/ram0" ? Notice that ram0 is not mounted anywhere and does not have a filesystem on it. I've tried that command and there seems to be no error. I got confused and looked into loop.c, it seems to me that a loopback device should be associated with a "backing file", why would it work on a block device anyway?

I'd appreciate your comments greatly!

TIA,
Lei

author
#1 lore raw

Please cc me if you have answers to this, I am not on the list. Thanks a lot!

Quoted 11 lines · Lei Yang

Hello,

Here is a question for loopback device. As far as I understand, the loopback device is used to mount files as if they were block devices.

Then Why I could do "losetup -e XOR /dev/loop0 /dev/ram0" ? Notice that ram0 is not mounted anywhere and does not have a filesystem on it. I've tried that command and there seems to be no error. I got confused and looked into loop.c, it seems to me that a loopback device should be associated with a "backing file", why would it work on a block device anyway?

I'd appreciate your comments greatly!

TIA,
Lei

#2 lore raw
Quoted 9 lines · Lei Yang
Quoted 9 lines

Here is a question for loopback device. As far as I understand, the loopback device is used to mount files as if they were block devices.

Then Why I could do "losetup -e XOR /dev/loop0 /dev/ram0" ? Notice that ram0 is not mounted anywhere and does not have a filesystem on it. I've tried that command and there seems to be no error. I got confused and looked into loop.c, it seems to me that a loopback device should be associated with a "backing file", why would it work on a block device anyway?

Because block device is a file.

#3 lore raw
In reply to Lei Yang
Quoted 11 lines · Lei Yang

Hello,

Here is a question for loopback device. As far as I understand, the loopback device is used to mount files as if they were block devices.

Then Why I could do "losetup -e XOR /dev/loop0 /dev/ram0" ? Notice that ram0 is not mounted anywhere and does not have a filesystem on it. I've tried that command and there seems to be no error. I got confused and looked into loop.c, it seems to me that a loopback device should be associated with a "backing file", why would it work on a block device anyway?

I'd appreciate your comments greatly!

TIA,
Lei

man losetup
You just set up the loop device to enable encryption on /dev/ram0. /dev/ram0 is a "file". It's a special-file, but a file nevertheless. It can contain a file-system, therefore act as a RAM disk, but it doesn't have to.

In principle, you could make an encrypted file-system in which you couldn't even know what kind of file- system it was, without an encryption key.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.9 on an i686 machine (5537.79 BogoMips).
Notice : All mail here is now cached and reviewed by John Ashcroft.
98.36% of all statistics are fiction.

author
#4 lore raw

Why /dev/ram0 is a file? Can you get into more details? For example, if I want to do some system level programming and write to a /dev/ram0, how do I do it?

Thanks very much for your reply!

Lei

Quoted 32 lines · linux-os
Quoted 11 lines · Lei Yang

Hello,

Here is a question for loopback device. As far as I understand, the loopback device is used to mount files as if they were block devices.

Then Why I could do "losetup -e XOR /dev/loop0 /dev/ram0" ? Notice that ram0 is not mounted anywhere and does not have a filesystem on it. I've tried that command and there seems to be no error. I got confused and looked into loop.c, it seems to me that a loopback device should be associated with a "backing file", why would it work on a block device anyway?

I'd appreciate your comments greatly!

TIA,
Lei

man losetup
You just set up the loop device to enable encryption on /dev/ram0. /dev/ram0 is a "file". It's a special-file, but a file nevertheless. It can contain a file-system, therefore act as a RAM disk, but it doesn't have to.

In principle, you could make an encrypted file-system in which you couldn't even know what kind of file- system it was, without an encryption key.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.9 on an i686 machine (5537.79 BogoMips).
Notice : All mail here is now cached and reviewed by John Ashcroft.
98.36% of all statistics are fiction.

#5 lore raw
Quoted 4 lines · Lei Yang

Why /dev/ram0 is a file? Can you get into more details? For example, if I want to do some system level programming and write to a /dev/ram0, how do I do it?

I don't think you need an example. You can open it in exactly the same way as you open regular files like /etc/resolv.conf.

ie.
FILE *f = fopen("/dev/ram0", "rw");
Then use fseek, fwrite and fread as usual.

Helge Hafting