have a laptop with the e100 eth0 driver. The driver is in your firmware extension. So I need to either remaster or put the extension on a usb stick. BUT I can't get the extension without the app browser...
Your assertion fails at the beginning of the second sentence. There is nothing preventing you from using any web browser, or cli tool to fetch extensions from the web page hosting the repository using the same method you did for Tiny Core itself.
Your second idea, of tarballs and scripts, would then make this topic thread invalid as it has to do with extensions and not the base.
Regarding Windows NTFS, ntfs-3g.tcz is a trivial single file download and any standard means to download does indeed work. It would only need to be in the base if one demands to host all of Tiny Core on NTFS.
The idea of offering a turnkey system is not very practical by the base design of Tiny Core. Recall the base initial ram disk, e.g., tinycore.gz is loaded entirely into ram. Having every ethernet, wireless, firmware can become quite expensive in terms of ram usage for those not wanting or even needing wireless, firmware, and Windows specific drivers. And even expensive for those who have such, as you typically have only one wifi and therefore no need for a myriad of other files taking up ram.
Even installing Tiny Core is typically, a one time event. Why should the base, e.g., dedicated ram wasted for one time or rarely used events. Hint. I have been looking into this very area.
The design of Tiny Core is not a "conceptual bug" it is by design. Many before you get it.
Trying to make Tiny Core like the hundreds of other distros is not in the works. Providing the bare minimum is.
I am not totally dismissing you. Tiny Core's 10.6MB packs many attributes. Extension offering, packaging, and documentation is where this should be handled.
I am also not against the efforts of "The Full Core" for those that wish to choose such.
Welcome
FAQ
Downloads
Wiki
