> > I always had the idea that there could be a whole raft of virtual files > that don't actually exist but that could be used to issue commands or > return data like RTC time etc, like /proc /sys etc. They could even be in > their own virtual sub dir. The dir could even be invisible where it isn't > listed in the root directory listing, but never the less works if you > request the right dir and filenames. > I like the idea that, at least for some things, you might be able go use > them by just opening the "file" in TEXT. Or sched or addr for that matter. > You could have a 2 MB address book for real, but a virtual addr.do that > only sees a 5k window of it at any given time. > I don't actually know what all the useful uses might be but it just seems > obvious to provide the facility simply because you can, and maybe someone > else comes up with functions that are made possible by using the facility.
The virtual files would be very useful, if not found in current dir - look to the magic directory and serve up the file. Would be great for SARDINE and DOS and I don't think would cost too much memory/program wise. I could just never get past the whole, do I search the "magic" directory for specific files defined somewhere or if it doesn't exist I just check for predefined files? I thought about a config file that would be read on boot/insertion that would set these hints but with the limited memory I didn't want that to get too big. Maybe read the file each time? Maybe just one directory where you put things and they always show, but then how do you treat duplicates? Fun stuff to play with. I really like the /proc file system idea, that's pretty smart to use the file system to transmit the data. One thing I would also like to see though is serial communication that does something similar. IE: a serial command that can pull real time clock info as well as the /proc/. That would give me the best of both worlds for doing things. I really do miss the CLI interface the NADs has when using this device. -Brian
