General TC > Tiny Core on Virtual Machines

Anyone succeeded with installing vmware on TC?

<< < (6/9) > >>

Ulysses_:
Probably 90% of them are superfluous or unnecessary anyway.  Maybe the vmware folks are the ones to ask about this, rather than use trial and error till hell freezes. :D

It should be like the GetFlash extension, which is only a script that you run manually in order to download flash.  

People should really be insulated from all this typing and trial and error.  I believe in computers as means to ends, it is easy to forget this is what they are.  Even extension creation should be automated somewhat as much as possible.

Is there any template for an extension like GetFlash complete with instructions how to create it?

danielibarnes:

--- Quote ---Even extension creation should be automated somewhat as much as possible.
--- End quote ---
My extensions are. This is how I calculated the 4562 figure. I rather doubt anyone else could use my highly-customized script, but I agree: automating it is helpful. My extensions would never get updated, otherwise. Here's a rough description of my script:

1) Create a temporary directory for the following steps.
2) Extract tinycore.gz.
3) Extract compiletc deps and any other extensions required to build the source.
4) Chroot into the directory, perform a few initialization steps, then build from source.
5) Remove all files extracted in steps 2 and 3, leaving only the binaries built in the previous step.

That much isn't too difficult to automate, but the next steps are real time savers:
6) Package remaining files into a base extension with -dev, -doc, and -lib extensions as appropriate.
7) Create a .list and .md5.txt file for each extension.
8) Create a .info using a T2 desc file as a template.
9) Run ldconfig recursively on every file to create a list of required libraries.
10) Search the tce directory for extensions containing those libraries and create a .dep file (not comprehensive).
11) Audit using a customized version of the extension audit script.
12) Package all of the generated files into a bcrypted tar for submission.

Bugs in my script cause Jason grief on occasion (a good reason to not distribute it), but the concepts are worth sharing. They could be discussed and refined in the scripting forum, so I might do that.

Ulysses_:
What if you create an extension that takes the current state of the filesystem and does a backup of it into a .tcz.  This would then be the user's private extension, dependent on all their chosen extensions.

danielibarnes:
An extension is read-only. You can't include the whole filesystem in an extension or else lots of things will break. Do you mean only changed files? You have a couple of methods to find changed files:
1) Use a timestamp and "find -newer"
2) Install in a chroot then subtract out the files.

The timestamp method is widely used for its simplicity. Does it work for you?

tinypoodle:
Even if doing a scatter install or creating a new initrd based on "current state of the filesystem" (which as opposed to an extension would be on a writable resp. expanded to a writable file system) certain dirs could not be included, e.g. /mnt and /proc.

Navigation

[0] Message Index

[#] Next page

[*] Previous page