On 10/31/2014 09:43 AM, Fabian Arrotin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 31/10/14 14:21, Steven Falco wrote: >> On 10/31/2014 03:44 AM, Manuel Wolfshant wrote: >>> On 10/31/2014 03:08 AM, Les Mikesell wrote: >>>> On Thu, Oct 30, 2014 at 7:06 PM, Doug >>>> Wellington<ddw at rincon.com> wrote: >>>>>> Previously: >>>>>>>> Might be simpler in the long run to make it a 2-step >>>>>>>> process. That is, do a minimal OS install, then have a >>>>>>>> 2nd DVD or USB key that they install after the base >>>>>>>> system with a script that upgrades any existing rpms >>>>>>>> and installs the rest of what you need. >>>>>> >>>>>> That adds an interesting set of questions. Do I somehow >>>>>> try to get the postinstall script to prompt for it? Do I >>>>>> try to create something similar to firstboot that would >>>>>> prompt for the second disc after the reboot? Do I just >>>>>> list it in the install docs? Right now the install docs >>>>>> are "1) Boot from DVD; 2) Choose system from menu." I'd >>>>>> like to keep it that simple. >>>>>> >>>>>> Seems like I'd still have to create an appropriate >>>>>> comps.xml file for whatever was on the second disc anyway, >>>>>> so why not just create everything on the first/only disc to >>>>>> begin with? Also, I always copy all of the RPMs into a >>>>>> local repository (e.g. /opt/repos/centos6u4) and run >>>>>> createrepo on it. Having one comps.xml file that works for >>>>>> both the installation disc and the installed repository >>>>>> keeps things clean... >>>>>> >>>> Is it really too complicated for the 'hands-on' guy to log in >>>> as root, >>> You'd be surprised. There might not exist a "hands-on guy" able >>> to do anything more advanced than "insert disc in cd-drive, boot >>> system". Been there, had to deal with that. I even had to deal >>> with the question "What does boot mean ?' >> >> This thread has taken an interesting turn, but I'd like to try to >> bring it back to my original question: >> >> How can I build a variation on the official DVD, including >> generating the embedded LiveOS image; i.e., the rootfs.img file? >> > > Well, I haven't read the whole requirements list you probably > described earlier, but have you already had a look at lorax ? It was > written for such particular case normally : > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-disk-image-installation-automatic.html Thank you! I will give that procedure a try and report my results. Can you confirm whether this is the procedure used by the official CentOS build scripts? Steve > > - -- > > Fabian Arrotin > The CentOS Project | http://www.centos.org > gpg key: 56BEC54E | twitter: @arrfab > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > > iEYEARECAAYFAlRTkgAACgkQnVkHo1a+xU7EjQCfV0vrVSDcaf0Pohuxqp8i/MOd > 1U4AnisVlXGibu2Od5d3Es4x6Efx8Q6Y > =q6tM > -----END PGP SIGNATURE----- > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > http://lists.centos.org/mailman/listinfo/centos-devel ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________