Tiny Core Linux
Tiny Core Base => TCB News => Release Candidate Testing => Topic started by: roberts on June 21, 2009, 02:18:40 AM
-
The Second Release Candidate of v2.1 is now posted and ready for testing.
http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/2.x/release/
Change log for tinycore_2.1rc2.iso:
* Updated aterm for better interaction with appbrowser (less hangs).
* Updated tce-wget, the command line tool for fetching extensions.
* Updated tc-config, crond & sshd moved to after restore for better support of user selected options.
* Updated tc-functions. Added space to end of searched devices for better mountpoint detection.
* Updated screenshot to remove extra delimiters in date section of filename.
* New usbinstall, a command line tool to install to pendrive, usbhdd, usbzip, or usbext. Needs extensions dosfstools, syslinux, and for usbzip, perl5
* Moved virtual hard drive to support persistent home on a virtual hard drive.
* Deleted memdisk and mbr.bin as they are avilable in extensions.
-
You are the Man!
Tinycore gets better everyday:)
-
Oh yes, although Roberts didn't mention...simply open a terminal and type in "usbinstall"
For those who will ask. ;)
-
If I use the new "Install to Pendrive," is there a way (such as Linux command) to make the Pendrive TinyCore installation WITH INSTALLED APPLICATIONS into an ISO?
I need this to complete my recently announced project, "TinyCore Magic DILLOcious Browser Anywhere."
"Small is beautiful; Tiny is exquisite."
Hooray for Robert Shingledecker and TinyCore Linux!
-
See the wiki:
http://wiki.tinycorelinux.com/tiki-index.php?page=Remastering
Basically, you put the apps in /tce (or /tcz) on the iso image.
-
See the wiki:
http://wiki.tinycorelinux.com/tiki-index.php?page=Remastering
Basically, you put the apps in /tce (or /tcz) on the iso image.
The Remastering documentation is excellent EXCEPT for explaining exactly HOW to put the new apps in /tce: that's where I fail. Perhaps this will be explained in more detail in the next revision of "Remastering."
"Small is beautiful; Tiny is exquisite"
-
It would appear that /tmp/extract is being used as the "root' environment for the new iso.
So to add or remove would be relative from that, e.g,
To unpack app_to_be_added.tce into /tmp/extract one could use:
tar -C /tmp/extract -zxvf app_to_be_added.tce
-
It would appear that /tmp/extract is being used as the "root' environment for the new iso.
So to add or remove would be relative from that, e.g,
To unpack app_to_be_added.tce into /tmp/extract one could use:
tar -C /tmp/extract -zxvf app_to_be_added.tce
Thank you, RobertS. I'll try this when I get home.
-
I tried the rc2 and found I've still got the problem with the creation of the Apps-Menu when the development tools are installed. Please take a look at my suggestion for a workaround:
http://forum.tinycorelinux.net/index.php?topic=2012.msg10948#msg10948
-
I only test base norestore nolocal. I do not preface every invocation of every util with busybox.
What extension specifically are you using that is breaking things? If it is gawk, shouldn't be called gawk?
-
The extension that breaks things is gawk.tce from the 2.x repository. It contains a link awk->gawk, so removing this link from the .tce-package should fix this problem, but I'm not sure if it might breaks other things. I'll change the package and give the system some test runs on building packages.
-
IMHO gawk in not awk. However, I agree that there is no harm in what you suggested. It is in 2.1 final.
-
Thanks. Anyway, after changing the gawk package, I could not trigger any bug or glitch.
-
Compiling gawk automatically installs the symlink awk -> gawk.
Does it make sense to remove this symlink in light of what you mention above?
-
Both, either removing the symlink awk->gawk or prefixing awk in the script with either "busybox awk" or "/usr/bin/awk", fix the issue. I'm no expert in awk, let alone the different dialects, so it's hard for me to tell which is the "right" awk...
But to put it short: since the script /usr/bin/jwm_makemenu has been adjusted, there's no need for the removal of the symlink awk->gawk any more.
-
Typically gawk specific scripts specify gawk in their shebang or invocation.
This would indicate, that since TC is providing a basic awk, that the extra link to provide of it could be removed. This would be much like perl5 needing to indicate that a specific level of perl is needed, e..g, perl5 and not just perl.