Hi. I became new maintainer for s-c-netboot and I have found this interesting mailing list. It seems we are doing same thing but in different way. S-c-netboot is quite old now and needs some serious work and the question is develop it alone or use some parts of your work. And seems same for Stateless Fedora project. The best way I think is to use what is already done, work together, s-c-netboot can act as (G)UI for Stateless Fedora/RHEL project. With beginning of system configuration management project (PolicyKit etc.) we can have independent backend for users to access stateless configuration etc. I've already read old thread "s-c-netboot vs..." but it's quite old now...
So what do you think? ;-) --- Jaroslav Reznik <[EMAIL PROTECTED]> Software Engineer - Base OS Core Services Brno Red Hat, Inc. +420 532 294 275 _______________________________________________ Stateless-list mailing list [email protected] http://www.redhat.com/mailman/listinfo/stateless-list
