Brainstorming

Homework/research/discussion

Mindset
Don't build for $Arch build to detect and use available features

Package management and updates

• A package manager is needed, should it be shell scripted or C coded?
• In unix philosophy should it be a package suite of independent programs breaking down the jobs?
• Can it piggyback off a existing package management system or repository?
• Can a single from source package management system and repository work for multiple OS/kernels simultaneously?
• Background compile/updates?
• How can sub-distribution management be better handled for companies and other distributions wishing to address their own package database?
• Can the system detect updates and install itself without breaking? Should it?
• How can updates/new packages be best automated for least/no input or maintenance?
• Can the dependency on distribution servers/mirrors be eliminated? Reduced?

Deployment/installation

• Simplify network deployment in all environments IE corporate/soho/home_user/remote_corporate_user
• Quick configuration/installation
• Minimal booting system with network & compile tools download current build template
• Use plain txt list for files/packages and src/ref same file for install & remove to prevent file cluttering over time.

Testing and stable releases

• A test suite to ensure reliable OS releases?
• Test elftoolchain for binutils replacement.

Not yet categorized

• Built in backup solution? unix shadow copy equiv?
• Support for android packages?
• Containers / jails

[Home]