Re: [maemo-users] Crashes
ext Dr. Nicholas Shaw [EMAIL PROTECTED] writes: Hmmm... I have a Linux server here I use for development - didn't think of trying to connect into the N800 using SSH. The default IT OS configurations don't have ssh installed. You first have to find it and install it. Poke me for details if you need them, but the SDK repositories should have it. ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users
Re: [maemo-users] Crashes
On Mon, Feb 12, 2007 at 02:03:44PM -0800, James Sparenberg wrote: A lot of the differences in how the OS's react to a hard shutdown center around how they view/use a file. Windows always writes back any file it opens. Even if it opens it only to read. That does not sound right. Do you have a link? Linux on the other hand writes back a file only if it changes and permissions allow writes. There are also atime updates which do write the inodes when you open files for reading. Not all filesystems store access times. I don't know whether jffs2 does, and my guess would be it doesn't. This helps prevent a lot of file corruption and fragmentation IMHO. (Yes I know this is an overly simplified explanation but I don't want to either bore or exceed my own ignorance *grin*) Marius Gedminas -- As far as we know, our computer has never had an undetected error. -- Weisert signature.asc Description: Digital signature ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users
Re: [maemo-users] Crashes
On Tuesday 13 February 2007 05:39:48 Marius Gedminas wrote: On Mon, Feb 12, 2007 at 02:03:44PM -0800, James Sparenberg wrote: A lot of the differences in how the OS's react to a hard shutdown center around how they view/use a file. Windows always writes back any file it opens. Even if it opens it only to read. That does not sound right. Do you have a link? Let me try to find one. This was part of 4 day seminar on file systems... (mostly boring.) Linux on the other hand writes back a file only if it changes and permissions allow writes. There are also atime updates which do write the inodes when you open files for reading. Not all filesystems store access times. I don't know whether jffs2 does, and my guess would be it doesn't. This is true but I'm so used to running everything noatime I forgot. Thanks This helps prevent a lot of file corruption and fragmentation IMHO. (Yes I know this is an overly simplified explanation but I don't want to either bore or exceed my own ignorance *grin*) Marius Gedminas ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users
Re: [maemo-users] Crashes
On Saturday 10 February 2007 06:54:33 Dr. Nicholas Shaw wrote: As I noted in an earlier post, occasionally some programs will fail and they are terminated. On occasion, however, some programs display very Windows-like behavior, e.g. the only way to use the system is to remove the battery and wait a bit then reboot. Specifically, I'll run a program (fmradio was one such program) and something occurs that prevents me from turning the unit off, closing the application, or doing anything with the system. In short, it's non-functional. I'm concerned that this will, at some point, corrupt the OS. Thus far, whenever this occurs, I uninstall the offending program. Thoughts? Thanks, Nick Shaw On this one. First Linux + jffs (jiffy file system used on 770/n800) is a lot less likely to be corrupted as a whole than windwos.Normally this means that the GUI is locked up rather than the system itself. On my 770 (and my laptop too sometimes) if I have an app that locks the GUI, then, SSH to the rescue. SSH into the system, from another box, then either kill the offending app or if what to kill isn't obvious, just do 'shutdown -r now' (without the quotes) or 'reboot' and the box will shut itself down cleanly, and restart. A lot of the differences in how the OS's react to a hard shutdown center around how they view/use a file. Windows always writes back any file it opens. Even if it opens it only to read. Linux on the other hand writes back a file only if it changes and permissions allow writes. This helps prevent a lot of file corruption and fragmentation IMHO. (Yes I know this is an overly simplified explanation but I don't want to either bore or exceed my own ignorance *grin*) James ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users
RE: [maemo-users] Crashes
Hmmm... I have a Linux server here I use for development - didn't think of trying to connect into the N800 using SSH. I'm going to have to give that a try. Thanks! Nick Shaw -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Sparenberg Sent: Monday, February 12, 2007 3:04 PM To: maemo-users@maemo.org Subject: Re: [maemo-users] Crashes On Saturday 10 February 2007 06:54:33 Dr. Nicholas Shaw wrote: As I noted in an earlier post, occasionally some programs will fail and they are terminated. On occasion, however, some programs display very Windows-like behavior, e.g. the only way to use the system is to remove the battery and wait a bit then reboot. Specifically, I'll run a program (fmradio was one such program) and something occurs that prevents me from turning the unit off, closing the application, or doing anything with the system. In short, it's non-functional. I'm concerned that this will, at some point, corrupt the OS. Thus far, whenever this occurs, I uninstall the offending program. Thoughts? Thanks, Nick Shaw On this one. First Linux + jffs (jiffy file system used on 770/n800) is a lot less likely to be corrupted as a whole than windwos.Normally this means that the GUI is locked up rather than the system itself. On my 770 (and my laptop too sometimes) if I have an app that locks the GUI, then, SSH to the rescue. SSH into the system, from another box, then either kill the offending app or if what to kill isn't obvious, just do 'shutdown -r now' (without the quotes) or 'reboot' and the box will shut itself down cleanly, and restart. A lot of the differences in how the OS's react to a hard shutdown center around how they view/use a file. Windows always writes back any file it opens. Even if it opens it only to read. Linux on the other hand writes back a file only if it changes and permissions allow writes. This helps prevent a lot of file corruption and fragmentation IMHO. (Yes I know this is an overly simplified explanation but I don't want to either bore or exceed my own ignorance *grin*) James ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users
