OK, rebooting did clear out stuff and I was able to get it to install and work. 
I modified the .ks file (and this is attached).

This may be because of what I brought in (xfburn instead of gnomebaker, 
claws-mail instead of sylpheed, fetchmail and gcc* -- I personally don't think 
any linux system should come without gcc) but there is a lot of stuff which 
gets pulled in which I was surprised to see. Example: Terminal. 

I was surprised to see that it complained of including lxsesion-lite when I had 
specifically changed it to lxsession.

Btw, how does one get the F bubble instead of the burger-man while Fedora boots?

T

--- On Wed, 7/15/09, Rahul Sundaram <sunda...@fedoraproject.org> wrote:

> From: Rahul Sundaram <sunda...@fedoraproject.org>
> Subject: Re: 64-bit LXDE spin/remix
> To: "Globe Trotter" <itsme_...@yahoo.com>
> Cc: "encouragement and advice for using Fedora.Community assistance" 
> <fedora-list@redhat.com>
> Date: Wednesday, July 15, 2009, 2:36 PM
> On 07/15/2009 11:55 PM, Globe Trotter
> wrote:
> 
> > device-mapper: remove ioctl failed: Device or resource
> busy
> > Command failed
> >
> /usr/lib/python2.6/site-packages/imgcreate/errors.py:45:
> DeprecationWarning: BaseException.message has been
> deprecated as of Python 2.6
> >   return unicode(self.message)
> > Error creating Live CD : Could not remove snapshot
> device
> 
> Make sure you have run
> 
> # setenforce 0
> 
> Before running livecd-creator. Check whether you have
> enough disk space
> and run again after a reboot.
> 
> > 
> > Btw, this is not important but I was able to get
> things to "work" only after putting the .ks file in the
> /usr/share/spin-kickstarts/ directory.
> 
> The LXDE ks file inherits the base ks file. You can copy
> the base ks
> file to any location and then the path wouldn't matter.
> 
> Rahul
>


      

Attachment: Fedora-My-LXDE-remix-11.ks
Description: Binary data

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Reply via email to