Once you get it to work, you'll find that you can't log in to the minimal livecd.

That's just the way it's designed. So, I'd suggest switching to another one. It probably has a bunch of SELinux packages specified.

I've found that (if I don't want SELinux), I have to do this to the kickstart.

available: sed, getent, etc. Make sure they're installed. Then make sure your PATH variable includes their directories.

that livecd-creator uses needs to be on a local drive or you run the risk of strange build failures.

Until you get it to build without these errors it's not going to boot under qemu.

Fulko Hew wrote: I'm failing at my first attempt at creating (or recreating) a live CD - I'm using Fedora 8 (because I don't find KDE in F9 usable yet) - I have SELinux disabled. Following the process described in the LiveCDHowTo, well, actually the step: livecd-creator --config=/usr/share/livecd-tools/livecd-fedora-minimal.ks resulted in a complaint about SELinux not being enabled on the host system... Right, so I edited the '.ks' file and set selinux=--disabled This let it proceed through the build stage with the following errors: Installing: info ##################### [ 29/129] /var/tmp/rpm-tmp.42253: line 2: sed: command not found error: %post(info-4.12-1.fc10.i386) scriptlet failed, exit status 127 ... Installing: cracklib ##################### [ 45/129] /var/tmp/rpm-tmp.50225: line 2: getent: command not found /var/tmp/rpm-tmp.50225: line 3: getent: command not found ... Installing: kernel ##################### [124/129] device-mapper: table ioctl failed: No such device or address Command failed ... Installing: selinux-policy-targeted ##################### [129/129] libsemanage.dbase_llist_query: could not query record value libsepol.sepol_user_modify: MLS is enabled, but no MLS default level was defined for user guest_u libsepol.sepol_user_modify: could not load (null) into policy libsemanage.dbase_policydb_modify: could not modify record value libsemanage.semanage_base_merge_components: could not merge local modifications into policy /usr/sbin/semanage: Could not add SELinux user guest_u libsepol.sepol_user_modify: MLS is enabled, but no MLS default level was defined for user xguest_u libsepol.sepol_user_modify: could not load (null) into policy libsemanage.dbase_policydb_modify: could not modify record value libsemanage.semanage_base_merge_components: could not merge local modifications into policy /usr/sbin/semanage: Could not add SELinux user xguest_u Removing password for user root. passwd: Success Then I used the specified command to execute the ISO image: qemu -m 512 -cdrom livecd-fulko-200805241043.iso The first time I followed the procedure (a few days ago) to build the ISO and execute it, it wouldn't even boot. Today I retried the same procedure, and today it boots, but after it get to the point of starting udev, something flashes by on the screen (qemu window) and then the window goes black, and I can't see anything after that. I seems hung. So then I tried recreating the 'livecd-fedora-desktop.ks' version as per instructions and it dies with: Installing: tzdata ################### [ 21/1019] umount: /var/tmp/livecd-creator-PxlU8W/install_root: device is busy umount: /var/tmp/livecd-creator-PxlU8W/install_root: device is busy ioctl: LOOP_CLR_FD: Device or resource busy Traceback (most recent call last): File "/usr/bin/livecd-creator", line 1603, in <module> sys.exit(main()) File "/usr/bin/livecd-creator", line 1575, in main target.install() File "/usr/bin/livecd-creator", line 948, in install self.installPackages() File "/usr/bin/livecd-creator", line 591, in installPackages self.ayum.runInstall() File "/usr/bin/livecd-creator", line 330, in runInstall return self.runTransaction(cb) File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 591, in runTransaction errors = self.ts.run(cb.callback, '') File "/usr/share/yum-cli/callback.py", line 124, in callback fd = os.open(rpmloc, os.O_RDONLY) OSError: [Errno 2] No such file or directory: '/var/tmp/livecd-creator-PxlU8W/install_root/var/cache/yum/development/packages/texlive-texmf-errata-fonts-2007-4.fc9.noarch.rpm' So I'm at a loss as to how to proceed to start testing this process even before I add my own customizations. Any help would be appreciated. TIA Fulko ------------------------------ -- Fedora-livecd-list mailing listFedora-livecd-list@redhat.comhttps://www.redhat.com/mailman/listinfo/fedora-livecd-list -- _________________________________ Tim Wood, CLP, RHCT 719.338.7484 (tel) The Data Wranglers Web, Database & more since since 1994 www.datawranglers.com -- Fedora-livecd-list mailing list Fedora-livecd-list(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list

> > I do have those things available... at least to me. > I don't know about the environment that livecd-creator makes for > itself though. > Same things goes for PATH. I can execute those utilities. Strange... I believe livecd-creator uses your PATH.

I'm failing at my first attempt at creating (or recreating) a live CD - I'm using Fedora 8 (because I don't find KDE in F9 usable yet) - I have SELinux disabled. Following the process described in the LiveCDHowTo, well, actually the step: livecd-creator --config=/usr/share/livecd-tools/livecd-fedora-minimal.ks

On Sat, May 24, 2008 at 11:21 AM, Fulko Hew <fulko.hew(a)gmail.com&gt; wrote: > I'm failing at my first attempt at creating (or recreating) a live CD > > - I'm using Fedora 8 (because I don't find KDE in F9 usable yet) > - I have SELinux disabled. > > Following the process described in the LiveCDHowTo, well, actually > the step: > > livecd-creator --config=/usr/share/livecd-tools/livecd-fedora-minimal.ks ... snip ... Following up on my own email... I am making progress, but not because I changed anything... I now have success in creating a live CD, just by running _exactly_ the same thing again. Now its basically working (without changing a thing... Yeah, I have a hard time believing that myself.) Now that I can basically create a bootable media... I want to customize it. But if I use the standard approach of always downloading the RPMs across the net, it takes a long time, so therefore I'd like to have a local repository to suck from. I haven't been able to find a 'good/working' set if instructions to follow that a) creates a local repo, and b) changes required to the kickstart file so it _successfully_ uses that local repo. Surely there must be a definitive set of instructions/docs for this _whole_ downloading/setup/building/customizing a liveCD process? (I haven't found any 'complete' instructions yet.) Pointers anyone?

Jerry Vonau wrote: You could also use the --cachedir= setting in livecd-creator to keep the > cache from being deleted in between runs. > > Make that --cache=

Fulko Hew wrote: > On Sat, May 31, 2008 at 1:25 PM, Jerry Vonau <jvonau(a)shaw.ca&gt; wrote: > >> Jerry Vonau wrote: >> >> You could also use the --cachedir= setting in livecd-creator to keep the >> >>> cache from being deleted in between runs. >>> >>> Make that --cache= >>> >> > > OK... I tried that, and after a few false attempts I figured out that I > had > to pre-create a cache directory specifically named 'yum-cache' > and to pass into the -cache option the name of the directory > that _contained_ 'yum-cache' instead. > > I've been using rawhide and now F9, I didn't have that problem with recent versions, what version are you using?

Might be the behavior of what was released with F8, sorry I don't recall.

After running livecd-creator, that cache directory was indeed populated, so I decided to run the build again to watch it now take all the rpms from the cache, but it still went out to the net for everything. There should be contact with the internet, to gather the repo's metadata to resolve dependences for the rpms. However when it comes time to download the rpms, if the rpm is in the cache the download should be skipped.