Tiny Core Base > Raspberry Pi
Towards Core (microcore) on Raspberry Pi
bmarkus:
Hm..... There is nothing against to do the same on x86 platform, introduce debCore86 with the great Debian repository. This would position Core as one of the many Debian clones, loosing its original idea and unique ground, depending on a Big Brother giving up independency.
And half year later if someone asks what is Tiny Core Linux the answer is 'Just a strange Debian or Ubuntu something using uncommond approach, forget it.' And in one year time it is gone.
Back to RPI I understand lack of resources, but if TC on x86 is fine with current repository, RPI version can survive with less than 40,000 extensions. Current build scripts can be easily reused to have piCore offering similar functionality as TC today.
It is good to speed up the startup, to have a bootstrap toolchain, but thats all. If it is officially a .deb converter, no way back. Making this move would mean to give up Tiny Core philosophy.
I'm sure it is possible to build a community keeping the original idea. Maybe it is slow, for sure different than existing, but can work. You need marketing. You can touch many RPI funs, both professionals and hobbist who do not know TC yet. To be 10th of RPI is different than to be 500th on x86.
Make available a minimal system with a development toolchain and introduce as an ideal platform for small systems for both hw and QEMU in the RPI community. They will like it. There is a great momentum. Use it.
But please, do not piggiback on the Debian repository and do not kill Tiny Core!
P.S. Read this http://forum.tinycorelinux.net/index.php/topic,13864.0.html
roberts:
I thought I was quite clear when I said I was not going to change in any way the support for user contributed extensions.
That I stated that this tool, a deb2tcz on steriods, would be evaluated. We have had Jason's basic deb2tcz for quite a while and there was no such outrage over its announcement or use!
I am expanding the concept of deb2tcz to process debian dependencies and with selection via a package browser ala ab/tce/tce-ab. It is an option just at the current x86 deb2tcz. YOU don't have to use it!
I am NOT giving up on the concepts that I have developed over the many years of doing Linux distributions.
There is not going to be .deb files in your extension directory. There is no call for such a harsh reaction on an optional tool.
vinnie:
if it is possible for us to have compatibility with .deb packages as additional features without alter the normal operation of the .tcz system, this seems very positive, otherwise I agree with bmarkus, it is best to keep the spirit that has made Core distro really different.
I hazard a proposal, if we had a script system repository like Aur of archlinux this could automate the compilation by architecture from which you start the script, thus making the creation of packages multiplatform.
I do not understand crosscompilation, so forgive me if I'm saying stupid things :P.
roberts:
--- Quote from: bmarkus on September 09, 2012, 07:09:46 AM ---No loop module in QEMU kernels >:(
--- End quote ---
Qemu kernels are not production kernels.
I don't mind to build and test a qemu kernel if on TinyCore. I have not Windows.
Does your present qemu kernel with piCore.gz load using Core's qemu-extra.tcz
or does that extension need an update?
bmarkus:
--- Quote from: roberts on September 11, 2012, 04:42:16 PM ---
--- Quote from: bmarkus on September 09, 2012, 07:09:46 AM ---No loop module in QEMU kernels >:(
--- End quote ---
Qemu kernels are not production kernels.
I don't mind to build and test a qemu kernel if on TinyCore. I have not Windows.
Does your present qemu kernel with piCore.gz load using Core's qemu-extra.tcz
or does that extension need an update?
--- End quote ---
Result is kernel panic. TC repo version is 1.0 what I'm using is 1.1
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version