latta46
Group: Members
Posts: 8
Joined: Nov. 2006 |
 |
Posted: Dec. 02 2006,20:33 |
 |
Howdy;
After reading the Kernel Module HowTo, and the recommendations on the DSL Wiki, I think that the best method is to KISS it (Keep It Simple Stupid) and utilize the bootlocal.sh and .xinirtrc methods therein outlined for my application. I should also be able to place additional wrapper files in the /mydsl subdirectory, to get things fired up.
Since DSL is intrisicly small, and therefore suitable for dedicated application usage (my intent), some compromises are in order. System adminitration should be kept as simple and as straightforward as possible, as the user will be the person doing the maintenance.
For my application, I only have two or three *.o device drivers to load, that I could put in subdirectories off of /myfiles (which is located on hda2 (my persistent storage)), along with their docs, sources, etc. I do not plan to be unmounting the modules once installed, as I have half a gig of ram on the target system. Once I have the application fully functional, this might be downsized. It will depend on the size of the database files generated by the application.
Most of the application frontend is planned to be Dillo, Monkey, PHP, SQLite, some bash files, and possibly some perl or TCL/TK. I intend to issue the application with a book and accompanying CD-ROM.
The only real question that I now have is, how to package up the *.o, *.c, and the usage docs (txt or PDF), including schematics for the IO module hardware (where required), for each of the new device drivers, that I wish to share on the DSL repository. As you can see, some tailoring of a standard *.dsl, (etc.) install is required.
Mitch
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
