Messages in this thread | | | From | Holger Schurig <> | Subject | Re: State of devfs in 2.6? | Date | Tue, 09 Dec 2003 11:08:39 +0100 |
| |
>> * space. devfs doesn't eat space like the MAKEDEV approach. > > Um, devfs does actually use a non-zero amount of code...
Yeh, it uses code. But if you look into a MAKEDEV bases file system, you see hundreds of device files. Which uses inode and directory space on the medium, may it be e2fs or jffs2.
I did not measure if the code for devfs is smaller as the code+config files for udev. But I didn't make a statement about this.
> For a typical embedded device with about 5 entries in /dev I wouldn't > be surprised if devfs used a lot _more_ space...
# find /dev | wc -l 326
"Embedded" is not automatically a washing maschine with only 5 entries, it can be a full blown Linux computer with 400 MHz, Framebuffer, USB Host, USB Client, 7 serial ports for GSM, Barcode Scanner, Whatever, and so on. Like our device.
However, even on such hardware-rich devices you usually have a constraint on Flash Memory size. So having things small & simple is nice. That makes room for the user applications & data.
-- Try Linux 2.6 from BitKeeper for PXA2x0 CPUs at http://www.mn-logistik.de/unsupported/linux-2.6/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |