General TC > Programming & Scripting - Unofficial

NFS storage base scripts mod for PXE booting [split]

<< < (4/6) > >>

curaga:
As gutmensch, I see no use for the separation in cases other than thin clients with low ram. The ram savings would be negligible if the libs.tczl would be in ram, or worse by 3mb with lib.tcel (of course lib.tcel could be deleted after extraction, to get absolutely the same ram usage as current microcore). It would also bring some overhead, and with a tcz use one loop.

Also, what libraries one's setup considers needed and what are considered extra vary by the setup. For example if one client shows pics, it needs libpng; if another runs a webserver, it needs other libs. There's no general solution.

Being able to do this kind of customization is the forte of TC/MC. However I don't see some separation like this ready-done being useful to very many.

gerald_clark:
With NFS, it loopmounts over NFS, so it does not copy to RAM at all.
Only the TFTP loaded extensions get copied to RAM.

curaga:
Indeed, I forgot to take that into account in my post. What I meant was "....ram savings in normal cases would be...".

alu:
nevertheless: starting with a microcore at 3.5 mb (or less) would deserve from thin client up to other machines (i did not know that while loading tc/mc from server, you only load the tftp extension in ram, since i ever did it, but want to move to this kind of boot methode; so thanks, i have learnt smthg); curaga, you'r certainly right while saying that it is just little ram saving, but my point is rather: as we have microcore with 7.* mb, why shouldn't we make it smaller (if it is not too much workload; obviously, i don't want to complicate the existing concept)? i did not think to make for each kind of library (or group of libraries) a special extension, rather to package all libraries at the moment in microcore which we could remove into one tcz extension. if you want, it would be a sorte of what gutmensch says, i.e. radicalization of the tcz approach while at the same time a step nearer to a kind of turn key machine. as a result, you have a minimal setting with bzImage and the kernel, and everything else come as a tcz extensions. that way, you would also have an alternative to a tftp/pxe approach for those user wanting to stay with their system on a physicall support. by the way, as we are there, another suggestion (useless these are only personal thoughs in order to share ideas and stimulate the reflection on tc/mc): would it be possible for the TC-Team to provide a kind of NFS-server access in order for us to remote install tc/mc?

curaga:

--- Quote from: alu on September 01, 2009, 02:34:48 PM ---by the way, as we are there, another suggestion (useless these are only personal thoughs in order to share ideas and stimulate the reflection on tc/mc): would it be possible for the TC-Team to provide a kind of NFS-server access in order for us to remote install tc/mc?

--- End quote ---
There is already such a service: netboot.me (that's the URL as well). It isn't ours, but they offer TC and MC as netbootable images.

Navigation

[0] Message Index

[#] Next page

[*] Previous page