RE: Accessibility of files in FileSystemDriver
Lorne Smith <Lorne.Smith-6tN4nzCoH/[email protected]>
| Newsgroups | gmane.comp.hardware.microcontrollers.tini |
|---|---|
| Message-ID | <[email protected]> |
This applies to the file system only. This is the reason for requirement #2 below. The new process does not (cannot) inherit the class, just the mount point. TINIOS automatically makes the call to DSFile.mount. The parameters to this method are all that are passed from the parent to the child. --Lorne > -----Original Message----- > From: tini-admin-6tN4nzCoH/[email protected] > [mailto:tini-admin-6tN4nzCoH/[email protected]]On Behalf Of > Shawn Silverman > Sent: Wednesday, February 25, 2004 11:16 PM > To: Lorne Smith > Cc: tini-6tN4nzCoH/[email protected] > Subject: Re: [TINI]Accessibility of files in FileSystemDriver > > > Does this apply to the filesystem only, or to all static classes and > fields that are used from a parent process? I thought all processes > are supposed to behave like a separate JVM? How does this fit in? > > Thanks, > -Shawn > > On 25-Feb-04, at 9:36 AM, Lorne Smith wrote: > > > The mount point will exist in a new process if both of the following > > conditions are met: > > > > 1) The new process is spawned from a process that has already > > performed the > > mount. > > 2) The new process has access to the driver class (i.e. the > driver is > > in the > > classpath or built into the tini file of the new process). > > > > In your example, if you added the driver class to the > slush.tbin file > > when > > you rebuilt it, you will also need to build it into any > programs you > > want to > > access the mounted file system. An alternative is to store > the driver > > class > > file in TINI's tiniext directory. > > > > --Lorne > > > >> -----Original Message----- > >> From: tini-admin-6tN4nzCoH/[email protected] > >> [mailto:tini-admin-6tN4nzCoH/[email protected]]On Behalf Of > >> Shawn Silverman > >> Sent: Tuesday, February 24, 2004 7:50 PM > >> To: tini-6tN4nzCoH/[email protected] > >> Subject: [TINI]Accessibility of files in FileSystemDriver > >> > >> > >> I have implemented a FileSystemDriver that mounts itself when Slush > >> starts -- I've replaced the main() method. > >> > >> My question is, say I've mounted it in "/mnt", and there's a > >> file named > >> "data.txt". I know that from the Slush shell I can access > >> "/mnt/data.txt". What about from separate processes? How > does 'new > >> File("/mnt/data.txt")' work if the DSFile static instance > >> used to mount > >> is in the Slush process? What goes on internally with the > filesystem? > >> > >> My guess is that I still need to mount the filesystem another > >> time from > >> all processes that aren't Slush, with a new instance of my > >> FileSystemDriver. > >> > >> Is this correct? I'm off to try this theory... > >> > >> -Shawn > > _______________________________________________ > TINI mailing list > TINI-6tN4nzCoH/[email protected] > To UNSUBSCRIBE, edit your profile, or see list archives: > http://lists.dalsemi.com/mailman/listinfo/tini > _______________________________________________ TINI mailing list TINI-6tN4nzCoH/[email protected] To UNSUBSCRIBE, edit your profile, or see list archives: http://lists.dalsemi.com/mailman/listinfo/tini