WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: [SOLVED]how to create right click menu entry  (Read 6808 times)

Offline manit123

  • Sr. Member
  • ****
  • Posts: 315
Re: how to create right click menu entry
« Reply #15 on: April 03, 2013, 06:45:53 AM »
you mean that loop mounts are read only so usb stick would not deteriorate . Also access to RAM is fast , my computer has 4GB of it . So copy2fs will help me in faster access ?

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 6888
Re: how to create right click menu entry
« Reply #16 on: April 03, 2013, 06:55:55 AM »
Hi manit123
Actually, the extensions are packaged in a read only file system so they can't be messed up. If you use copy2js, your
boot time will take longer, but applications will start faster.

Offline manit123

  • Sr. Member
  • ****
  • Posts: 315
Re: how to create right click menu entry
« Reply #17 on: April 05, 2013, 09:19:01 AM »
Won't they run fast too considering that they are loaded into RAM whose access time is much faster than USB ?
Also , can you tell me way to have copy2fs flag in boot (I have grub 0.97 ) ?

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: how to create right click menu entry
« Reply #18 on: April 05, 2013, 09:28:17 AM »
All programs run from RAM.  The copy2fs.flg is a file in your tce directory

Offline manit123

  • Sr. Member
  • ****
  • Posts: 315
Re: how to create right click menu entry
« Reply #19 on: April 06, 2013, 07:07:43 AM »
i do not want to pester you .
Can you point me to link explaining copy2fs mode ?

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11063
Re: how to create right click menu entry
« Reply #20 on: April 06, 2013, 07:19:09 AM »
you can use the apps gui to set the copy2fs flag:

installation options -> toggle default install to file system flag

This will put a file named copy2fs.flg in your /tce folder and extensions will then be copied to ram

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 6888
Re: how to create right click menu entry
« Reply #21 on: April 06, 2013, 07:45:45 AM »
Hi manit123
Quote
Can you point me to link explaining copy2fs mode ?
Check out the diagrams for mount mode and copy mode found here:
http://wiki.tinycorelinux.net/wiki:tiny_core_file_architecture_diagrams

Offline manit123

  • Sr. Member
  • ****
  • Posts: 315
Re: how to create right click menu entry
« Reply #22 on: April 06, 2013, 09:02:18 AM »
That was wonderful .
As i thought - copy2fs will help my applications like dictionary , word-letter-combination-search-software-for-scrabble to run faster at the expense of longer startup time .
I think if I create an empty copy2fs.flg file in tce folder my usb stick  . I will get copy2fs mode . Is that right (why should I bother systemtool>apps for that) ?

The difference I think among the tcz & copy2fs is that - in tcz mode one can see  what has been loaded as there will be many loop mounts . In copy2fs mode I won't get so many mountpoints . Isn't it ?

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 6888
Re: how to create right click menu entry
« Reply #23 on: April 06, 2013, 09:24:47 AM »
Hi manit123
Quote
I think if I create an empty copy2fs.flg file in tce folder my usb stick  . I will get copy2fs mode . Is that right (why should I bother systemtool>apps for that) ?
Yes, that will work. The tool is suggested because that is one of the functions it provides.
The applications will run just as fast as mount mode. The time from when you start the application until you see
results on the screen will be a lot less (startup time).

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: how to create right click menu entry
« Reply #24 on: April 06, 2013, 09:33:35 AM »
The applications will run just as fast as mount mode.

Hmm, isn't there a possibility where a mounted app would access squashfs while running (and therefore might be a bit slower, depending on storage medium throughput)?
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 6888
Re: how to create right click menu entry
« Reply #25 on: April 06, 2013, 09:44:38 AM »
Hi tinypoodle
The executables and libraries will be loaded into and running from RAM. If the application includes a data file in the
squashfs that it routinely opens and reads, that could slow things down a bit, though caching would probably serve
to reduce that.

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: how to create right click menu entry
« Reply #26 on: April 06, 2013, 12:10:01 PM »
The executables and libraries will be loaded into and running from RAM. If the application includes a data file in the
squashfs that it routinely opens and reads, that could slow things down a bit

Request for clarification please:
1. Is statement referring to squashfs in particular or generally applicable (incl. e.g. uncompressed scatter files)?
2. Is statement referring to compiled code exclusively or generally applicable (incl. e.g. interpreted code)?

Quote
though caching would probably serve
to reduce that.

True, but OTOH even in copy2fs mode swapping to disk could lead to decrease speed.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 6888
Re: how to create right click menu entry
« Reply #27 on: April 06, 2013, 02:05:42 PM »
Hi tinypoodle
1. The program will be loaded into RAM regardless of how/where it is stored.
2. Compiled code. I don't know how for example ash or a basic interpreter would handle it.
Quote
True, but OTOH even in copy2fs mode swapping to disk could lead to decrease speed.
I was referring to if the program routinely read from a data file, those reads would wind up being cached in RAM. If
the program went to read from that file again, it may already have been cached since reads are done in blocks of
4K in think.