On Mon, 2005-11-28 at 19:31 -0500, Gain Paolo Mureddu wrote: > This brings a question... If (for instance) avoiding the run of first > boot (from a chrooted sysrescue session) the system is put up2date on a > default install, would taht be considered modification? Most probably it > would... I thought of the first boot post-install method as it seems to > be the intended way for Fedora, only what would be the best way to > ensable a disk to work in this way? Difficult to say. In fact what I made use of was init's .unconfigured plugin. If init finds a /.unconfigured file it will call some TUI tools such as setting the root password, configuring the auth method, setting what services start, etc... some of the things that are outside the scope of firstboot. Honestly you probably should have your clients do some of firstboot if not all of it. I'd like to get a policy in place that allows you to ship a system with all the updates installed and even some extra software so we can avoid some of the trouble of trying to do this last mile stuff at the customer location. Customers have a way of forgetting to do it or messing it up. -- Jesse Keating RHCE (http://geek.j2solutions.net) Fedora Legacy Team (http://www.fedoralegacy.org) GPG Public Key (http://geek.j2solutions.net/jkeating.j2solutions.pub) Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating -- Fedora-marketing-list mailing list Fedora-marketing-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-marketing-list
