Tiny Core Linux 3.5
الترجمة الالية للوصف
- مرات التنزيل: 236
- متطلبات التشغيل:
- الاصدار : 3.5
- اضيف في: 0000-00-00 00:00:00
- اخر تحديث: 15/02/2011
- الموقع علي الانترنت:
Descriptionabove.In Copy Mode: * Application Extensions are copied into RAM instead of mounted. * Applications can be RAM-loaded in bulk (copy2fs.flg), selectively loaded into RAM (copy2fs.lst), or mounted. * The Appsaudit program tracks installation/loading options (bulk copy, selective copy, etc). * Boot times are longer, since copying to RAM takes more time than mounting.Copy Mode briefly extends the boot time to gain some of the RAM-run speed of Default Mode and the persistence of a pure Mount Mode.In Copy Mode, it is important to note that extensions can be either mounted or copied into RAM. The Appsaudit program makes this flexibility possible by keeping track of user selections.The Hybrid Mode of Operation: Local/InstallIn Hybrid Mode: * Tiny Core System Files are copied into RAM as normal. * Application extensions are installed to disk using "Install", and mounted as a tree at /usr/local. * RAM is saved for other uses (as in Mount Mode). * Boot times are very low. * Tiny Core loses a pristine renew-on-reboot. * Tiny Core ignores downloaded extensions and the Personal Persistent Repository (PPR) of application extensions.Hybrid Mode installs applications to a partition or loop back file in a traditional "one file tree" way. This copy of /usr/local, a Personal Persistent Installation (PPI), is mounted into the main file system on reboot using the boot code local=.As with most typical environments, installing applications can lead to corruption over time. Applications gradually write over each other's libraries, partial upgrades occur, user and system errors happen, and minute changes may be unnoticeable and difficult to fix. Because of this inevitable "system rot," the Mount and Copy Modes are strongly preferred to Hybrid Mode.Early in Tiny Core history (around 2.4 and before), not all applications supported PPI installation because some of their dependencies might not have been in the /usr/local tree. Individual extension .info files still hold those details.To set up a PPI of /usr/local, see the wiki and forum topics on the local= boot code, the "Create Loop Back File" menu option, and the tclocal dirctory or loop back.Backup/Restore and Other Persistence Options:Aside from the PPR (Personal Persistent Repository of application extension) and PPI (Personal Persistent Installation of application extensions), Tiny Core supports persistent/permanent:Backup and Restore of personal settings, andPersistent /home and /opt directories.Backup/RestoreTiny Core includes filetool for saving personal settings and data. The text file /opt/.filetool.lst lists files and directories to be backed up at power down and restored at reboot. The list may be changed manually (using vi, nano, etc) or via the scripts in the Tools menu; note that the entry for /opt/filetool.lst should never be removed from the list itself. filetool also supports exclusion of particular files via /opt/xfiletool.lst.By default, filetool.lst includes the entire home/tc directory, and xfiletool.lst excludes some unnecessary caches and temporary directories.filetool writes backup mydata.tgz. The location of mydata.tgz can be initially set using the boot option restore=hdXY, restore=hdXY/directory, or, after boot, by selecting Backup/Restore from the Control Panel. If the restore code is no used, Tiny Core will search for mydata.tgz in available root directories at boot. Conversely, the boot option norestore ignores any existing backup files, a useful tool for trouble-shooting and upgrading.Further settings and configurations are stored or executed using /home/tc/.xsession, /home/tc/.profile, /opt/bootlocal.sh, and /opt. Search the forum and wiki for information on these and other custom settings files.Persistent HomeJust as Tiny Core offers persistence options for downloaded application extensions, so does it for your home directory. These are set using boot codes/options.home=hdXY will automatically setup /home/tc to "bind" to /mnt/hdXY/tchome. When using the home boot code, mydata.tgz is not created - personal data backups must occur in a more traditional way. The home boot code lets Tiny Core coexist with other Linux installations by inserting the tc user directory under a pre-existing /home directory. Be careful, as the initial use of the boot code will creat this directory and its content. Also, Tiny Core cannot auto-detect a persistent home directory, so the home boot option is always required. What's New in This Release: [ read full changelog ]
· Updated busybox 1.18.3 plus patches.
· Updated zsync to 0.6.2.
· Updated fluff file manager to 0.8.9
· New autoscan-devices compiled to improve boot speed.
· Updated tc-functions for call to autoscan-devices.
· New rotdash compiled to improve boot speed.
· Updated tce-audit builddb to not force fetch of all .dep files when no tce.db exists.
· Updated appsaudit to support removing ondemand uninstalled extensions without rebooting.
· Clean up of tce-audit 'delete' spurious messages.
· New tce-remove support for tce-audit/appsaudit.
· Update wbar_rm_icon to support tce-remove.
· Updated appsaudit, added highlight on FAILED md5 checking.
· Updated wbarconf added many more bar position options.
· Updated services to support nested daemon starting.
· Updated appbrowser Mirror Selection to support mirror.tcz extension.
· Updated tc-config crond call and removed duplicate crond script.
· Scripts adjusted to remove extra spaces to reduce size.
· fsck replaced with busybox fsck
· Moved thinkpad_acpi.ko from base to extension.
· Corrected typo in .desktop item for fluff file manager.
· Corrected permission on protect option bfe file.
· New logo tag line. Fast. Easy. Modular. Extendable.
Moshax.com only provide legal software, please help us keeping pur site legal, if you think this page is violating copyrights please let us know by clicking here Here