WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Prepack index  (Read 4118 times)

Offline danielibarnes

  • Hero Member
  • *****
  • Posts: 542
Prepack index
« on: May 11, 2011, 01:10:12 PM »
Users need to the ability to:
1) Know they need a "prepack" to accomplish their particular goal, and
2) Know which one they need.

The tc-install prepack is documented in the readme, but a formal index file of some sort and a walk-through would be helpful for new users. For example, when someone visits the home page for the first time with the intent of installing Tiny Core, how can they determine they need this prepack and find out what to do with it?

Offline Guy

  • Hero Member
  • *****
  • Posts: 1089
Re: Prepack index
« Reply #1 on: May 12, 2011, 10:34:32 AM »
Minor changes can be made to the installation guides in the wiki to explain how to use the tc-install prepack.

However, if a person goes to the home page, and clicks on Installation, they don't go to the wiki index. I think this link should be redirected so it goes to the wiki index. Now that the installer has been improved, using it is the easiest way to install Tiny Core.

If the team wants to use information from the wiki to update the official installation guide, that is another option.


As for nettools, again, have a well documented explanation of how to use it in the wiki.
Many people see what is. Some people see what can be, and make a difference.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7343
  • Founder Emeritus
Re: Prepack index
« Reply #2 on: May 12, 2011, 11:16:03 AM »
OK. Good idea. Please post specific Wiki links here. I then will update webpage.
And many thanks for your contributions!
10+ Years Contributing to Linux Open Source Projects.

Offline Guy

  • Hero Member
  • *****
  • Posts: 1089
Re: Prepack index
« Reply #3 on: May 12, 2011, 12:13:36 PM »
It is probably best to go to the wiki index, as there are many different pages on installation, and they are at the top of the index.

http://wiki.tinycorelinux.net/

or

http://wiki.tinycorelinux.net/wiki:start

If you think it should be done differently, let me know.

There is an Installation link on all of the pages of the main website. They should all be updated.
« Last Edit: May 12, 2011, 12:22:31 PM by Guy »
Many people see what is. Some people see what can be, and make a difference.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7343
  • Founder Emeritus
Re: Prepack index
« Reply #4 on: May 12, 2011, 04:57:03 PM »
We already have a link to the Wiki on all web pages and forum.
What I would be looking for is detailed instructions on how to use the prepack as a recommended way to install Tiny Core for a new user.

Same would need to be done for configuring undetected net access devices, i.e., specifically using the prepack.

Probably best to post link here first. Get feedback and perform updates before official web pages link to them.
10+ Years Contributing to Linux Open Source Projects.

Offline beerstein

  • Sr. Member
  • ****
  • Posts: 401
Re: Prepack index
« Reply #5 on: May 13, 2011, 04:45:27 PM »
sorry for asking this question - but I do not know what a "prepack" is?

Is it something  like an extension?

What is the difference between an extension and a prepack?

Is there an example for, when do I need a prepack?

Thank you so much for help.
t(w)o be(ers) or not t(w)o be(ers) that is the question

Offline Guy

  • Hero Member
  • *****
  • Posts: 1089
Re: Prepack index
« Reply #6 on: May 13, 2011, 05:40:23 PM »
Quote
What is the difference between an extension and a prepack?

In the past, to install Tiny Core, it was necessary to install a number of extensions. To make is simple these extensions have all been combined into one prepack, so you only need to download and install one thing. The prepack may also include the script used for installation.

The same thing with wireless internet. The extensions needed for wireless internet have been included into one prepack.

At the present time, you have two options, you can install all of the extensions, like you did in the past, or you can install just the prepack. It is up to you.

If you use the prepack, it goes in the tce directory, not /tce/optional.

To load a prepack, restart the computer.
« Last Edit: May 13, 2011, 05:43:44 PM by Guy »
Many people see what is. Some people see what can be, and make a difference.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7343
  • Founder Emeritus
Re: Prepack index
« Reply #7 on: May 13, 2011, 06:17:45 PM »
One would only need a prepack if they are experiencing difficulty with inital network setup.
Because some users have such initial network issues they will be unable to perform an installation via the official Tiny Core installation program.

Therefore if you have difficulties in the initial network setup you will benefit from a prepack.
If you already have internet access then you can ignore prepacks.

Prepacks can be used with current releases of Tiny Core as stated in the announcement.
Starting with v3.7 additional options will be available.

Again, if you already have net access you will not need a prepack.
10+ Years Contributing to Linux Open Source Projects.

Offline Guy

  • Hero Member
  • *****
  • Posts: 1089
Re: Prepack index
« Reply #8 on: May 13, 2011, 06:35:29 PM »
Quote
Please post specific Wiki links here. I then will update webpage.

There are a number of different pages about installation. I suggest putting a link to this page.

http://wiki.tinycorelinux.net/wiki:install

Where relevant, these pages have info about the prepacks. I have included both options - prepacks or extensions. Some pages don't have info about the prepacks.

It seems when 3.7 comes out, these pages will need updating again.
« Last Edit: May 13, 2011, 06:37:35 PM by Guy »
Many people see what is. Some people see what can be, and make a difference.

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Prepack index
« Reply #9 on: May 13, 2011, 10:02:26 PM »
The same thing with wireless internet. The extensions needed for wireless internet have been included into one prepack.

Same for wired ethernet (firmware).
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline floppy

  • Hero Member
  • *****
  • Posts: 577
Re: Prepack index
« Reply #10 on: May 14, 2011, 12:24:42 AM »
from my small installing history (still not finish with ALSA..), I think following Prepacks would have helped few months ago:
- wired
- wireless (ndiswrapper, wicd..)
- communication and exchanges (opera, links, midhight commander for ftp)
- hardware audit and setup (lspci, lshw, hdparm, gparted,..)
- office tiny (flume, gnumeric, leafpad, epdfview)
After the knowledge is growing and most of things works, I would keep only the extensions I know and which are good to me..
AMD K6-IIIATZ 550MHz MB DFI K6xv3/+66
P4 HP DC7100 3GB 3GHz
Samsung NC10 boot from SD card port (via USB reader)
.. all TinyCore proofed

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7343
  • Founder Emeritus
Re: Prepack index
« Reply #11 on: May 14, 2011, 10:31:12 AM »
Once net access is achieved it is much more efficient to use existing tczs.
Don't expect a plethora of permutations and combinations to be offered.
We have a specific goal.
10+ Years Contributing to Linux Open Source Projects.

Offline floppy

  • Hero Member
  • *****
  • Posts: 577
Re: Prepack index
« Reply #12 on: May 14, 2011, 12:52:17 PM »
Once net access is achieved it is much more efficient to use existing tczs.
Don't expect a plethora of permutations and combinations to be offered.
We have a specific goal.
yes.
I was just thinking how to make a bigger "HHHUURRAAHH" effect on consumers.
I can make fire with a fire-stone.. but making fire with a BIC-lighter is quicker.
AMD K6-IIIATZ 550MHz MB DFI K6xv3/+66
P4 HP DC7100 3GB 3GHz
Samsung NC10 boot from SD card port (via USB reader)
.. all TinyCore proofed

Offline beerstein

  • Sr. Member
  • ****
  • Posts: 401
Re: Prepack index
« Reply #13 on: May 14, 2011, 05:48:48 PM »
Thank yo for this - now I know more.

I remember that there is a c-language package also in the repo. Needed to compile source code.
Is this a "prepack" too?

So when I download a prepack it sits in my /tce on sda1 for instance. Can I just copy it over
to another TC system on another machine and use it there?

Will it automatically be installed during reboot?

Would it make sense to make a prepack for "php, mysql and lightpd" for instance?

Are there instructions some where on how to do something like this?

t(w)o be(ers) or not t(w)o be(ers) that is the question

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 8032
Re: Prepack index
« Reply #14 on: May 14, 2011, 11:42:40 PM »
Thank yo for this - now I know more.

I remember that there is a c-language package also in the repo. Needed to compile source code.
Is this a "prepack" too?

compiletc is a meta-extension - it depends on all the necessary extensions. A prepack would be a combined extension instead, like compiletc was in the TC 1.x days.

Quote
So when I download a prepack it sits in my /tce on sda1 for instance. Can I just copy it over
to another TC system on another machine and use it there?

Will it automatically be installed during reboot?

Yes and yes.

Quote
Would it make sense to make a prepack for "php, mysql and lightpd" for instance?

Are there instructions some where on how to do something like this?

Not really, as Robert said, once you have initial internet access, you can just "tce-load -wi php mysql lighttpd" (untested command, extension names may differ).

For combining extensions, I think there is some info on the wiki and forum, but I don't think there has been a specific howto for that yet.
The only barriers that can stop you are the ones you create yourself.