Tiny Core Extensions > TCE Talk

User mirroring of the repo.

<< < (9/11) > >>

mbainrot:
Ok awesome, Once I finish my assignments (gotta love end of semester) I might write up some better documentation as it appears that the wiki formatting has munched the docs and its kinda unclear how to do it.

hiro:
Yes, it's insane, why do you need all these extensions anyway?

mbainrot:
I am setting up a complete local mirror as the other mirrors are really painful to get to from the land of oz.

Also I plan on using tiny core linux for pxe booting and have worked out that a local mirror and a slightly modified initrd (adding some scripts into /opt/bootlocal.sh to make it load stuff) should do the trick WAY better than slax.

Reason I need all packages is because I dont know exactly what my pxe booting setup is actually going to do yet.

In time when money permits I will prolly setup a high speed Australian mirror to make life a little more pleasant for us aussies.

My experience with mirroring is. Basing this on a linux web host
Assuming your www root resides in /var/www create the following directory structure.
/var/www/tc
/var/www/tc/3.x
/var/www/tc/3.x/tcz

use the tree command to verify the structure (noting my present working dir is /var/www)

--- Code: ---[root@jupiter www]# tree -d tc
tc
`-- 3.x
    `-- tcz

2 directories
[root@jupiter www]#

--- End code ---

1) Pick a mirror other than distro.ibbilio.org (i used ftp.vim.org) to get most of your stuff
2) Navigate to your version (e.g. 3.x)
4) Navigate to the tcz folder (note, this could take some time as generating a directory listing is pretty labourious)
5) For a full dump, copy all files inside of the tcz dir but avoid downloading the sources/src directory as they are quite large arn't needed for a local mirror.
6) When completed you'll probabally find that there are files missing, to rectify this connect to the main ftp server and then tell your client to only overwrite existing files if the source is newer. Whilst in theory it causes a load spike its short lived and its enough to get you going.
7) Check your folder permissions and then remaster your tiny core linux build so it uses your local repo.
8) Enjoy :)

Thats pretty much a detailed tl;dr of how to do it in easy to digest form.

Pentium44:
Mind if I make a mirror of distro.ibiblio.org/tinycorelinux at vps.cddo.us/pub/tinycorelinux/ ?

CentralWare:
@Jason / roberts / curaga / etc.: Would it be too much of an imposition to have the scripts currently run on the 3.x and newer TCZ directories to also be launched on the 2.x/tcz directory for sizelist and md5.db (and their gz counterparts?)  I know 2.x is likely a rare (if ever) recipient of updates due to its age, but considering there's otherwise no way I know of (without downloading every .info file for every .tcz) to determine if/when a file changes thus the above two items (md5 bare minimum) would be a terrific addition since 2x is still on the repo servers.

I'm currently writing up a system intended for downloading and maintaining a repository structure (I've recently noticed some odd things with WGET's mirroring capabilities and as such figured it's easier to draw it up from scratch as opposed to bug reporting and waiting) whereas the entire repo is going to be broken down between VERSION and PLATFORM where one or more combination of each can be selected and only those items are monitored for updates.  (ie: 9.x/armv6 and armv7 as well as 8.x/armv6 and 7 for someone who was solely focused on something like a RasPi, skipping over all of the unnecessary items - especially other platforms they'd otherwise have no use for.)  The 2.x, though, has no tracking (again, that I'm aware of) and I've read posts here and there with peeps still using 2x...)  The logic for these two files is simple: If MD5 and/or SIZE are different than what's on the user-based repo, update something.tcz and its associated files.

TCZ submission will be sent once she's completed.

Navigation

[0] Message Index

[#] Next page

[*] Previous page