Open liyu1981 opened 10 years ago
I feel not good about that idea, it would increse the size of the boot image by over a gigabyte. Having base64 should be enough to get people started, from there on only the FiFo zone needs internet access to import datasets so the hypervisors can stay nice and isolated.
yes, you are right. But there are some reasons ...
- Minimal version, no default datasets at all.
- Medium version, with only a smartmachine base as default datasets.
- Full version, with all I have mentioned (and even with some Windows versions).
Multiple versions will give the users choices. When some intranet admin want to try DogeOS (as well as FiFo), and he have no intend to break any intranet network policies, he can use either medium or full version (just like CentOS, there is a full DVD image). The medium or full version will enable him to experience DogeOS without any pain to configure more network. With that smooth installation and experience, he should build some trust against our OS, and then he can be a long-term user.
I think in next milestone, after I finish the auto-build scripts for DogeOS, the above goals can be achieved.
I like the idea of having multiple versions, for a long run something like 'build your own dodge' could be fun, i.e. when downloading users can decide which datasets they want.
My main concern is PXE, since I think for PXE booting a image it is required to load the entire thing in the memory not only the active part (but I could be mistaken here), so a 2G image PXE booted would mean 2G of memory lost on each hypervisor which would hurt.
For memo:
for nginx, the default client_max_body_size is too small.
to enable uploading, nginx setting should adjust to
client_max_body_size 10240M;
Currently DogeOS relies on network importing the guest datasets for using.
To provide ability to import some initial guest datasets: