| 20:02:10 | | Russ was last seen on #blob 1 days, 3 hours, 34 minutes and 32 seconds ago, saying: nm, there it is [Fri Mar 22 16:27:38 2002] |
| 20:02:10 | prpplague | ibot: seen Russ |
| 21:11:03 | Russ | I'm here |
| 21:56:34 | | russ was last seen on #blob 45 minutes and 21 seconds ago, saying: <private message> [Sat Mar 23 21:11:13 2002] |
| 21:56:34 | prpplague | ibot: seen russ |
| 21:57:05 | Russ | yes? |
| 21:58:57 | prpplague | Russ: hey you mind looking at an abstract? |
| 21:59:14 | Russ | send it along |
| 22:00:43 | Russ | ...or not |
| 22:00:47 | Russ | try spam@asu.edu |
| 22:01:07 | prpplague | oops |
| 22:01:56 | prpplague | sorry bout that |
| 22:02:01 | prpplague | how much did you get? |
| 22:02:26 | Russ | none |
| 22:02:55 | prpplague | Russ: ok, lets try that again with a non-flood mode |
| 22:03:08 | prpplague | Embedded Linux Systems: Creating End-User Proof Devices |
| 22:03:08 | prpplague | Linux has proven to be powerful and flexible in many areas. This has lead to its use in many embbedded applications such as thin clients(Point-of-Sale Terminal), mobile devices (inventory control on a handheld), and traditional embedded systems(network Printserver). The needs of most Linux installations, including desktops, can be catogrized into the groups of configuration, file system considerations, interfacing, display management, and operatio |
| 22:03:08 | prpplague | ns. However there are strong differences between embedded and desktop installations. |
| 22:03:25 | prpplague | Embedded platforms, unlike desktops, have very specific technology and user interface needs, such as limitations on display space, user input methods, storage capacity, and battery life. As a result special care and forthought is needed to develop Linux based devices that will be operated by the average end user. Which leads to the basic question , "What do i need to consider if i want my embedded Linux device to be successful in an end-user envir |
| 22:03:25 | prpplague | oment?" If you have asked yourself that question, then you will need to start consideration things like end-users don't care when they power off a device ( read only or journaling file systems ), they have no idea what an ip adress is ( message window "My Workstation ID is 192.168.1.2" ), and generaly they don't relate to phrases like "child window" or "daemon process" ( 1,2,3... - A,B,C... - Red, Green, Blue... ). All of these can make an embedde |
| 22:03:25 | prpplague | d Linux unsuable in the end-user enviroment. |
| 22:03:32 | prpplague | ok thats it |
| 22:04:52 | Russ | "you will need to start consideration things like" |
| 22:05:52 | prpplague | ya its a little rough |
| 22:06:11 | Russ | what do you want me to look at? grammer, spelling, flow, ideas? |
| 22:06:38 | Russ | brb |
| 22:06:42 | prpplague | content, this is suppose to be an abstract for a conference |
| 22:07:08 | prpplague | needs sleep |
| 22:07:40 | prpplague | Russ: forgive my in-eptitude today, i need some sleep |
| 22:12:46 | Russ | the first two parts are very in-depth, and descriptive, but the third part trails off in a big way |
| 22:13:07 | prpplague | Russ: thats what i thought |
| 22:13:11 | Russ | the third part seems like it should be more of the focus |
| 22:13:45 | Russ | I think you can assume that the audience has a good understanding of what is in the first parts |
| 22:14:05 | Russ | but would need more info about specific issues and what to think about |
| 22:15:42 | prpplague | Russ: ok thanks, think i'll sleep on it and revise it tomorrow |
| 22:15:45 | Russ | btw, the way I did it, is with a boot loader block, a static config block (mac addresses, serial number, etc), 2 "journal blocks", a cramfs backup partition (kernel, and ftpd, allows firmware flashing to occur), and the full cramfs partition (includes kernel) |
| 22:16:08 | Russ | the 2 journal blocks are handled in user space |
| 22:16:38 | prpplague | Russ: nice |
| 22:17:29 | Russ | I have a unpolished cramfs thing that does what andersee's patch to jffs2 does |
| 22:17:45 | Russ | (devices, permissions, etc, in a config file) |
| 22:17:59 | Russ | has a problem or two, but seems to work |
| 22:20:10 | prpplague | Russ: nice, thanks for the input |
| 22:20:43 | Russ | do you have the paper layed out at all yet? |
| 22:21:28 | prpplague | Russ: i've pretty much got the outline fixed up and about 75% of the content, just not put it all together yet |
| 22:21:53 | Russ | you have to get the abstract done now though? |
| 22:22:28 | prpplague | Russ: ya, just got to get something turned in so they make selections |