On Wed, 2008-10-22 at 00:42 +0100, Phillip Lougher wrote: > David P. Quigley wrote: > > > > > Looking through the code I noticed that you give certain object types > > the same inode number for all instances of it (devices, fifo/sockets). > > How is this done internally? Do these types of objects occupy the same > > position on the inode table? If so how do you differentiate between a > > device and a socket? > > > > No, devices and fifo/sockets get their own unique inode numbers: > > root@slackware:/mnt# mount -t squashfs test.sqsh /mnt2 -o loop > root@slackware:/mnt# ls -li /mnt2 > total 0 > 2 crw-r--r-- 1 root root 1, 1 2008-10-22 00:31 device > 4 prw-r--r-- 1 root root 0 2008-10-22 00:31 fifo > 3 srwxr-xr-x 1 root root 0 2008-10-17 16:25 socket [Snip] My mistake I misread your statement in email 0. You said that squashfs has real inode numbers and that cramfs didn't. Good luck with your mainlining attempt. Once you get xattr support this would definitely make life better for people who want to make SELinux enabled LiveCDs and other small devices. Dave -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
