>You're going to put application data file formats in the kernel?
>YOU'RE GOING TO PUT APPLICATION DATA FILE FORMATS IN THE KERNEL?
% ^DATA FILE^NETWORK PROTOCOL
[henning@babsi ipv4]% ls *masq*
ip_masq.c ip_masq_cuseeme.c ip_masq_irc.c ip_masq_raudio.c
ip_masq_app.c ip_masq_ftp.c ip_masq_quake.c ip_masq_vdolive.c
[henning@babsi ipv4]% pwd
/usr/src/linux-2.0.37/net/ipv4
Yes. Where is the problem? We already do this. As I understood, you
don't put the data file formats in the kernel but a loadable
abstraction layer which allows one application to use resource forks
and another one a representation as dot-files, subdirectories, you
name it. I would consider this a "cool thing (TM)".
Kind regards
Henning
-- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- hps@tanstaafl.de TANSTAAFL! Consulting - Unix, Internet, SecurityHutweide 15 Fon.: 09131 / 50654-0 "There ain't no such D-91054 Buckenhof Fax.: 09131 / 50654-20 thing as a free Linux"
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/