Tiny Core Base > Release Candidate Testing
tinycore_v2.8rc3
roberts:
--- Quote from: bigpcman on January 17, 2010, 01:58:45 PM ---Regarding tce-load usage:
--- Code: ---# Example usage:
# tce-load -i /mnt/hda1/tce/optional/nano.tcz Loads local extension
# tce-load -w -i nano.tcz Download into tce/optional directory, links for OnBoot and installs
# tce-load -w nano.tcz Download only into tce/optional directory
--- End code ---
I'm a little confused just what options cause the "boot link" to be created in /tce ? Are both -w and -i required?
Could a little more explanation be provided.
--- End quote ---
Operationally the same combination of flags.
-w only = download only
-i only = loads local from specified path
-w -i = downloads and sets up link for on boot.
bigpcman:
--- Quote from: roberts on January 17, 2010, 02:19:44 PM ---
--- Quote from: bigpcman on January 17, 2010, 01:52:52 PM ---I noticed there's still an ftp indicator in the tool panel. Is this correct? I thought ftp was dropped from the base.
Also, any progress on the dropbear extension?
--- End quote ---
ftp was dropped. Where is ftp shown? AFAIK, not shown when booted base norestore. What window manager are you using?
--- End quote ---
I booted from cd iso. I'll try again with base norestore.
If you are talking about control panel tftp server, that is still available.
roberts:
--- Quote from: bigpcman on January 17, 2010, 02:07:30 PM ---Could a little more explanation be provided for tce-update easy mode and inplace batch mode.
--- Code: ---# If not interactive then check for easy mode or inplace batch update
--- End code ---
--- End quote ---
easy mode and inplace mode are not new in this RC. Both are batch updates.
easy mode checks disk space available for update of all extensions, if so, creates an upgrade folder and updates download into upgrade folder, upon boot upgrade is completed before loading of extensions.
In place mode, is for smaller devices, e.g., a small pendrive, here each extension to be updated is downloaded into /tmp, md5 checked, then moved to replace existing extension.
Interactive mode is intended solely for calls from appsaudit.
roberts:
--- Quote from: bigpcman on January 17, 2010, 02:03:28 PM ---Could a few of the more complicated usage examples be provided for the tce-audit command.
--- Code: ---Usage tce-audit: {builddb|dependson|requiredby|nodepends|audit|auditall|delete|marked} extname
--- End code ---
--- End quote ---
To build the database of dependices you need to specify dir, e.g.:
tce-audit builddb /mnt/hda2/tce/optional
To check for missing denpendencies on all extensions you need to specify a dir, e.g.:
tce-audit auditall /mnt/hda2/tce/optional
To display all extensions that have no dependencies you need to specify a dir, e.g.:
tce-audit nodepends /mnt/hda2/tce/optional
For all other reports use the full path, e.g.:
tce-audit requiredby /mnt/hda2/tce/optional/webkit.tcz
tce-audit dependson /mnt/hda2/tce/optional/midori.tcz
It is much easier to use appsaudit which loads up the path and makes selecting and reporting via the GUI very nice.
Of course using shell's edit capability of 'up arrorw' and 'tab completion' makes the cli easy as well.
roberts:
--- Quote from: bigpcman on January 17, 2010, 01:55:10 PM ---Just out of curiosity does "tce2tcz.sh" still work?
--- End quote ---
I will remove it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version