>Nonsense. If you're doing without a filesystem, you can't do userland >_at all_. it might be nonsense (in most cases) to do everything in kernelspace, but that wasn't what i'd like. it's not hard to imagine a kernel that creates proceses out of ROM, or the network, or a serial port; and these processes could ran in userland, and talk to each other via IPC > >> but a unix-like system (like linux) doesn't seem the best way... > >A UNIX-like system is a perfectly valid way, but you'll have to >understand the design philosophy: mechanism belongs to kernel, policy >should be done in userland. i have no problem with the policy/mechanism separation! but in UNIX, the mantra "everything is a file" presupones a filesystem. in QNX, "everything is a message" doesn't. you can see a working example, the PalmPilot doesn't have a filesystem! ------ Javier -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ IRC Channel: irc.openprojects.net / #kernelnewbies Web Page: http://www.kernelnewbies.org/
