>Sure, we could could try to be all things to all people.
>Or we could stick with the original philosophy.
How about a compromise?
How about we create hard-coded releases that simply
ensure the majority of the masses can
1)
Boot tinyCore, piCore and/or dCore
2) Gain access to the network/
internet3a) have a
bare minimum desktop (save for (micro)Core)
3b) have SSH embedded for headless scenarios
@neonix: If the above were true, which it already is for most x86/x64 users, you can build your custom flavor somewhat easily using the extension manager. Tiny Core Linux was originally developed to act like LEGOs. We GIVE you that big flat piece (kernel/core/basic necessities) and you as the end-user build onto that foundation one brick (extension) at a time. This way, you're always assured that ONLY the things you've chosen are installed - no fluff, no bloat.
@admins: A few basic "
Meta" extensions could also come in handy in creating a
FEW starting environments. (ie: Update TC.tcz,
if necessary, to give the user a "basic" desktop
in each of the platforms, create another for a generic Xorg based desktop, etc.) For ISO files, I'd recommend the list above -- just make sure we can BOOT, get ONLINE*, have INSTALL capabilities and preferably, which would be a
huge time-saver for slightly more advanced users, allow a selection between ext/syslinux versus grub2. For users such as
@neonix possibly a single Go To Meta Extension that contains GUI files, a mid-sized browser, typical alsa items, network and hard drive utilities, etc. WITH a notice that it's intended as a starting point, but
not guaranteed to work in every possible environment.
For x86 and x86_64 ISO images - it would be very worthwhile to have an image suited with ALL firmware/driver modules that are HARDWARE related which would apply to or otherwise affect the above list. (For example, we have an Intel motherboard which has ETHERNET which
requires titan, mdadm and ipv6 drivers and STORAGE which oddly requires i2c - an install is impossible using the basic ISO files as we cannot get online to download drivers. I've created a special set of boot flash drives which contain the entire firmware/driver module set, but that's only after being faced with a lot of oddities that forced their creation. For general users... they'd be lost trying to figure out what's missing and for admins... that's hours and hours of support posts that potentially would no longer exist. (Yes, we also have USB dongles for scenarios for unforeseen install situations - but having an ISO that supports as much hardware as possible would be a God-send.)
* Isn't there a text based database of hardware IDs somewhere (at kernel.org I'm guessing) which I'm guessing we could use lspci/lsusb/etc. to get a list of detected hardware and cross reference it with kernel.org and determine which hardware modules are needed for said items? This way were're only loading module TCZ files we actually may need.
Welcome
FAQ
Downloads
Wiki
