Thorsten Kukuk wrote:
On Tue, Jan 05, Ludwig Nussel wrote:
tl;dr rpms to only operate below /usr and nowhere else.
I like it, but there are some things to consider or fix:
1) Never put /home on /var, normal users can fillup their home directory> and prevent the system from working.
Never say never :-) Running out of disk space certainly is a situation the OS needs to be able to handle in a defined way. Who or what is the most likely offender or what 'working' means depends on use case though. On a MicroOS based Rpi weather station I'm certainly not worried that my .bash_history grows out of bounds for example. If I was, I'd also have to take care of /var/tmp, /var/mail etc.
[...]
4) /usr/lib/linux: so bootloader need to be able to load the kernel from a different partition than the initrd? I doubt this will work. Copying the kernel image is also problematic, with all the space free checks, cleanup, etc. normally the package manager would do for you.
IOW there's work to do, yes. Have to check bootupd.
5) No rollback for /etc needed in the final setup? This contradicts a previous comment, that /etc needs to be included in a rollback to match the configuration of the installed software. This stays still valid with the final approach, as admin made changes for updated services could break the old version of that service.
You lost me here. In general OS packages must not and can not mess with /etc directly. So it wouldn't be possible to install files there, nor mangle them in nasty %post scripts. If for whatever reason config files need to be updated, a defined mechanism is to be developed to perform the migration at the right time. That has to work forwards and backwards and has to trigger a mechanism that creates snapshots/revisions of /etc. Yes, there be dragons. Big ones. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer HRB 36809 (AG Nürnberg)