OnDemand problem ?

[labeas]

See TheBook re. "On demand" installation?

"20.4. Ondemand scripts.
If you install an extension as OnDemand, a script will be generated
for it under the ondemand/ directory...............
Example ondemand script:
#!/bin/sh
ondemand -e nano.tcz  "
-----------
So, if the files-of-an-extention have been fetched other than by
the <Apps panel>, how will the "loading script" be generated, to
load-on-demand said extention.
-----------
Apps > Maintenance.
8.5. Onboot/ondemand maintenance.
These two modes allow you to add and remove extensions from the
onboot or ondemand lists..
Onboot.lst is a plain text file, so you can edit it with an editor of
your choice in addition to the GUI method listed. Ondemand items
are generated scripts, so managing them manually is discouraged..
!! <OnDemand GUI list> is empty ?? How to add items ??

[Misalf]

"Apps" -> "Maintenance" -> "OnDemand Meintenance" ...
select an item from the list on the left, click on "Add Item" at the bottom.
This is how OnDemand scripts are generated for you.

[labeas]

  "Apps" -> "Maintenance" -> "OnDemand Meintenance" ...
   select an item from the list on the left, click on "Add Item" at the bottom.
   This is how OnDemand scripts are generated for you.
------------
NO!!  apparently "list on the left" would only contain items which where
<fetched by APPS GUI in OnDemand mode>.
My "list on the left" is empty.
Wasn't that clear from my OP ?
How will privately fetched & installed *.tcz get into "list on the left"
when fetched by M$, before TC's WiFi is working ?

[coreplayer2]

  "Apps" -> "Maintenance" -> "OnDemand Meintenance" ...
   select an item from the list on the left, click on "Add Item" at the bottom.
   This is how OnDemand scripts are generated for you.
------------
NO!!  apparently "list on the left" would only contain items which where
<fetched by APPS GUI in OnDemand mode>.

I'm not sure where that idea came from.  Perhaps a better way to understand how this works is:  The list in the left window pane under the heading "Select" indicates all extensions found in the tce/optional directory which are not yet installed "OnDemand".  From this point follow the guide already given by Mysalf.

!! <OnDemand GUI list> is empty ?? How to add items ??

Expect this list on the right window pane of APPS

How will privately fetched & installed *.tcz get into "list on the left"
when fetched by M$, before TC's WiFi is working ?

How any extension arrived within the tce/optional directory is of no consequence, as long as file permissions are set correctly.

To help get an idea of what to expect in each of APPS menu's and window contents I recommend this short video.  Note the part from 3 min 55 seconds into the movie regarding ondemand
http://tinycorelinux.net/videos/apps.html

Also see Chapter 20 of the CoreBook

FYI:  If installed to a HDD or USB drive then tce/optional directory as specified in the boot config file is where all extensions are stored, regardless of whether they were installed onboot, ondemand, or simply downloaded.

The very last line within the APPS main window indicates the current location of the tce/optional directory.

 

[Misalf]

Dude, these movies are great! Especially for those who don't want to read the book. :p
Didn't they used to be in the wiki?

[coreplayer2]

I thought you'd like those,  that's how I learned..

[labeas]

> How any extension arrived within the tce/optional directory is of no
> consequence, as long as file permissions are set correctly.
Correct. *Provided*  the "extension arrived within the tce/optional directory".
But since the extensions are DESIGNED to arrive via the <APP Browser>, my ones
tht come by horse-back won't get to the critical directory.
But if you clowns would specify the full path of the directory, I could put the
*.tce there myself.
---------
Let's analyse some of the inacurate text of <CoreBook>:---------

>Tiny Core includes the filetool utility for saving personal settings
>and data.
OK: /usr/local/bin/filetool <- runs <Backup\Restore:GUI>

>The text file /opt/.filetool.lst lists files and directories
>to be backed up at power down and restored at reboot.
TC writers REFUSE to acknowledge the difference between files and
directories. My /opt/.filetool.lst contains 2 entries: one-per-line,
apparently both signifying directories. How would a non-dir-FILE
be indicated? eg. /mnt/sdb1/CRG/TestBakupRestore.
Can files belonging to eg. /mnt/sdb2, not yet manually mounted, be
accessed at restore time ?

>The list may be changed manually (using vi, nano, etc) or via the
> scripts in the Tools menu;
Where\How is the <Tools menu> accessible in TC64ver7 ?

> Filetool also supports exclusion of particular files via
> /opt/.xfiletool.lst
There is a fault:
grep opera /opt/.xfiletool.lst  == .opera/opcache .opera/cache4
find /home/tc -name "*cache*" == /home/tc/.opera-12/opcache.....
===> Your absurd suggestion of explaining via movies, explains the
reluctance to get the basic first principles right.

[Misalf]

But if you clowns would specify the full path of the directory, I could put the
*.tce there myself.

You refuse to learn things that are not exactly as you expect and even attack those people who are still willing to help you.
Get out of here, please!

[coreplayer2]

> How any extension arrived within the tce/optional directory is of no
> consequence, as long as file permissions are set correctly.
Correct. *Provided*  the "extension arrived within the tce/optional directory".
But since the extensions are DESIGNED to arrive via the <APP Browser>, my ones
tht come by horse-back won't get to the critical directory.
But if you clowns would specify the full path of the directory, I could put the
*.tce there myself.

Hilarious...

that explains why your APPS > Ondemand select window is empty!
Please read up on persistence,  only then will you come to the realization that tce directory is most likely located wherever designated in your boot config file.     
To know the path of tce directory please show output of this command

Code: [Select]

showbootcodes

[polikuo]

/etc/sysconfig/tcedir is a symbolic link that points to your TCEDIR.

To know the path of tce directory please show output of this command as well

Code: [Select]

realpath /etc/sysconfig/tcedir