11:56 a.m.
I was able to create a CentOS 5 Live CD with livecd-tools 009. However,
before launching the livecd-creator, I had to increase the maximum
number of open files:
# ulimit -n 65535
I added a script in the kickstart configuration file to automatically
mount hard drive and logical volume partitions via
/etc/rc.d/init.d/centos-live. If anyone is interested, I could post the
script.
I would like to thank the livecd-tools coders for such a powerfull tool.
--
Patrice Guay
1:34 p.m.
On 6/12/07, Patrice Guay <patrice.guay(a)nanotechnologies.qc.ca> wrote:
I was able to create a CentOS 5 Live CD with livecd-tools 009.
However,
before launching the livecd-creator, I had to increase the maximum
number of open files:
# ulimit -n 65535
I added a script in the kickstart configuration file to automatically
mount hard drive and logical volume partitions via
/etc/rc.d/init.d/centos-live. If anyone is interested, I could post the
script.
I would like to thank the livecd-tools coders for such a powerfull tool.
That's great news. One of the goals of the live-cd tools is to enable
other distros to create live CDs.
I personally would be interested in seeing your script. Can you post a
link?
John Babich
Volunteer, Fedora Project
1:28 a.m.
I would be definitely interested. I'm putting together a test system which
will need CentOS5 to which I add some test software and a couple of 3rd
party drivers. Please post your script.
thanks,
John
On 6/12/07, John Babich <jmbabich(a)gmail.com> wrote:
On 6/12/07, Patrice Guay <patrice.guay(a)nanotechnologies.qc.ca> wrote:
> I was able to create a CentOS 5 Live CD with livecd-tools 009. However,
> before launching the livecd-creator, I had to increase the maximum
> number of open files:
>
> # ulimit -n 65535
>
> I added a script in the kickstart configuration file to automatically
> mount hard drive and logical volume partitions via
> /etc/rc.d/init.d/centos-live. If anyone is interested, I could post the
> script.
>
> I would like to thank the livecd-tools coders for such a powerfull tool.
>
That's great news. One of the goals of the live-cd tools is to enable
other distros to create live CDs.
I personally would be interested in seeing your script. Can you post a
link?
John Babich
Volunteer, Fedora Project
--
Fedora-livecd-list mailing list
Fedora-livecd-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-livecd-list
8:12 a.m.
John Pleines wrote:
On 6/12/07, John Babich <jmbabich(a)gmail.com> wrote:
>
> On 6/12/07, Patrice Guay <patrice.guay(a)nanotechnologies.qc.ca> wrote:
> > I was able to create a CentOS 5 Live CD with livecd-tools 009.
> However,
> > before launching the livecd-creator, I had to increase the maximum
> > number of open files:
> >
> > # ulimit -n 65535
> >
> > I added a script in the kickstart configuration file to automatically
> > mount hard drive and logical volume partitions via
> > /etc/rc.d/init.d/centos-live. If anyone is interested, I could post
> the
> > script.
> >
> > I would like to thank the livecd-tools coders for such a powerfull
> tool.
> >
> That's great news. One of the goals of the live-cd tools is to enable
> other distros to create live CDs.
>
> I personally would be interested in seeing your script. Can you post a
> link?
>
> John Babich
> Volunteer, Fedora Project
I would be definitely interested. I'm putting together a test system
which
will need CentOS5 to which I add some test software and a couple of 3rd
party drivers. Please post your script.
thanks,
John
You can find information about the live CD creation procedure and the
CentOS 5 Live CD script on this post:
http://lists.centos.org/pipermail/centos-devel/2007-June/003660.html
Regards,
--
Patrice Guay
3:45 p.m.
New subject: Revisor is looking for busybox
I've (finally) been trying to build a live cd. I've been trying to use
Revisor. After I sorted out some issues so that Fedora played nice with
my repository, Revisor runs and gets to the point where it's trying to
build the cd. And it complains that busybox is a required package. My
repository has busybox-anaconda. I look at the os and all portions of one
of the official Fedora 7 repositories and I see the same thing:
busybox-anaconda and no busybox. Does anyone know how to resolve this?
4:24 p.m.
New subject: Revisor is looking for busybox
Tim Wood wrote:
I've (finally) been trying to build a live cd. I've been
trying to use
Revisor. After I sorted out some issues so that Fedora played nice with
my repository, Revisor runs and gets to the point where it's trying to
build the cd. And it complains that busybox is a required package. My
repository has busybox-anaconda. I look at the os and all portions of one
of the official Fedora 7 repositories and I see the same thing:
busybox-anaconda and no busybox. Does anyone know how to resolve this?
Hi Tim,
busybox is in the Everything repository. The default configs of the
version of Revisor you run may be pointing to the Fedora repository,
holding just the packages that came with the released DVD.
Later versions of Revisor have this fixed.
Kind regards,
Jeroen van Meeuwen
-kanarip
5:17 p.m.
New subject: Revisor is looking for busybox
When I ran yum update revisor, no luck, but I was able to download the
latest off of download.fedora.redhat.com/.../development/... and it seems
to be happily working.
Once I can generate one via the defaults I'm going to (scary) try one off
of the repository I'm running here. Should I add some or all of the
development rpms to my repository?
Tim Wood wrote:
> I've (finally) been trying to build a live cd. I've been trying to use
> Revisor. After I sorted out some issues so that Fedora played nice with
> my repository, Revisor runs and gets to the point where it's trying to
> build the cd. And it complains that busybox is a required package. My
> repository has busybox-anaconda. I look at the os and all portions of
> one
> of the official Fedora 7 repositories and I see the same thing:
> busybox-anaconda and no busybox. Does anyone know how to resolve this?
>
Hi Tim,
busybox is in the Everything repository. The default configs of the
version of Revisor you run may be pointing to the Fedora repository,
holding just the packages that came with the released DVD.
Later versions of Revisor have this fixed.
Kind regards,
Jeroen van Meeuwen
-kanarip
7:57 p.m.
New subject: Revisor is looking for busybox
On Sun, 2007-07-01 at 16:17 -0600, Tim Wood wrote:
When I ran yum update revisor, no luck,
This is due to the update sitting in the signing que. It should be
signed and pushed out to the mirrors sometime here soon.
For future reference, you can download Revisor builds directly from Koji
(if you don't want to wait for us to approve the builds for public
consumption):
http://koji.fedoraproject.org/koji/packageinfo?packageID=4446
but I was able to download the
latest off of download.fedora.redhat.com/.../development/... and it seems
to be happily working.
Once I can generate one via the defaults I'm going to (scary) try one off
of the repository I'm running here. Should I add some or all of the
development rpms to my repository?
No. The issue is that we were shipping default configs that only pointed
at the "Fedora" repo, which only has the bits that were shipped on the
DVD. We currently list "busybox" as a required package. Make sure you
have busybox in the repo you point Revisor to.
> Tim Wood wrote:
>> I've (finally) been trying to build a live cd. I've been trying to use
>> Revisor.
;-)
After I sorted out some issues so that Fedora played nice with
>> my repository, Revisor runs and gets to the point where it's trying to
>> build the cd. And it complains that busybox is a required package. My
>> repository has busybox-anaconda. I look at the os and all portions of
>> one
>> of the official Fedora 7 repositories and I see the same thing:
>> busybox-anaconda and no busybox. Does anyone know how to resolve this?
>>
>
> Hi Tim,
>
> busybox is in the Everything repository. The default configs of the
> version of Revisor you run may be pointing to the Fedora repository,
> holding just the packages that came with the released DVD.
>
> Later versions of Revisor have this fixed.
What version are you using? (rpm -q revisor) 2.0.4.0 is the latest.
Jonathan Steffan
daMaestro
2:58 a.m.
New subject: Revisor is looking for busybox
Tim Wood wrote:
When I ran yum update revisor, no luck, but I was able to download
the
latest off of download.fedora.redhat.com/.../development/... and it seems
to be happily working.
Once I can generate one via the defaults I'm going to (scary) try one off
of the repository I'm running here. Should I add some or all of the
development rpms to my repository?
Revisor doesn't really depend on what is in the repositories other then
with the lists of required packages it has for installation and live
media. Given that the latest version of Revisor is released to rawhide
you would need to do the occasional
# yum --enablerepo=development update revisor
to see if there is a more up-to-date version. Other then that, you don't
need to enable the latest and greatest of software for Revisor to use
composing your media. In fact, on my own development workstation I've
been able to do FC5, FC6 and CentOS 5 respins. These obviously don't
have the same software as F7 or development ;-)
Kind regards,
Jeroen van Meeuwen
-kanarip
7:35 a.m.
New subject: Revisor is looking for busybox
For future reference, you can download Revisor builds directly from
Koji
Thanks. I've added that to my notes
DVD. We currently list "busybox" as a required package.
Make sure you
have busybox in the repo you point Revisor to.
Thanks. Will do.
What version are you using? (rpm -q revisor) 2.0.4.0 is the latest.
Hehehe conveniently rpm -qa | grep revisor was the last thing in the open
terminal window. 2.0.4.0 it is.
thanks again for the help - Tim
7:42 a.m.
New subject: Revisor is looking for busybox
been able to do FC5, FC6 and CentOS 5 respins. These obviously
don't
have the same software as F7 or development ;-)
Right now I'm doing a respin for an actual project. I'm looking forward
to doing one with CentOS 5 just to see what happens. It would be fun to
eventually retire most of the LiveCDs I carry around because they have
this tool or that tool that's useful once every 4 months...
regards,
Tim Wood
11:46 a.m.
New subject: config file question/suggestion
I added a section to one of the Revisor configs with the short name
development (e.g. [development]). No matter what I did, it was ignored
until I changed that to something else (e.g. [extras]). Is there a config
file that governs what short names are sanctioned or is there a
suggestion/bug reporting tool for Revisor?
12:42 p.m.
New subject: config file question/suggestion
Tim Wood wrote:
I added a section to one of the Revisor configs with the short name
development (e.g. [development]). No matter what I did, it was ignored
until I changed that to something else (e.g. [extras]). Is there a config
file that governs what short names are sanctioned or is there a
suggestion/bug reporting tool for Revisor?
Hi Tim,
to enable development (same with testing, debug and source) repositories
in the Revisor configuration, you'll need to set
repos_enabledevelopment=1 because we prevent these repositories from
being displayed in the GUI on purpose. Check the rawhide models for
examples.
Bugs and suggestions you can just sent to our mailing list:
http://lists.fedoraunity.org/mailman/listinfo/revisor-users
Kind regards,
Jeroen van Meeuwen
-kanarip
8:35 a.m.
New subject: Revisor stalls while downloading packages
Last night I started running Revisor. I thought I'd finally gotten all
the config files convinced to play nice. I'm using a repository that
existing on another machine on the same network. I haven't tested this
repository extensively (it's a replacement for a machine that died), but
have used it to do a couple of recent installs/updates on 1 machine and
everything seems to work properly.
It got to the "Building your media" screen, went through checking
dependencies and then sat there on downloading packages. I check it with
ps and it was taking 10+% CPU and 23% Memory. This morning, it's still in
the same stage (downloading media) and the task progress bar has not
moved. CPU usage has dropped to 1%. What I'm assuming is the cache log
(/var/tmp/revisorrevisor-yum.log) is empty. The cache directory
(/var/tmp/revisor-yumcache) has been created and there's a subdirectory
for each of the entries that were on the repo screen (development, fedora,
updates) and each has various items including an empty packages directory.
The log (/var/log/revisor.log) ends with a copy of the warning I received
about /srv/revisor already existing (from a previous failed run).
Any suggestions on troubleshooting this? Maybe rip Revisor out and beat
it with a baseball bat?
3:55 p.m.
New subject: Revisor stalls while downloading packages
On Wed, 2007-07-04 at 07:35 -0600, Tim Wood wrote:
Last night I started running Revisor.
What type of media are you creating?
I thought I'd finally gotten all
the config files convinced to play nice.
May we see?
I'm using a repository that
existing on another machine on the same network. I haven't tested this
repository extensively (it's a replacement for a machine that died), but
have used it to do a couple of recent installs/updates on 1 machine and
everything seems to work properly.
It got to the "Building your media" screen, went through checking
dependencies and then sat there on downloading packages. I check it with
ps and it was taking 10+% CPU and 23% Memory. This morning, it's still in
the same stage (downloading media) and the task progress bar has not
moved. CPU usage has dropped to 1%.
It sounds like you hit a bug. If you're willing, run Revisor from a
terminal so you can get the traceback.
What I'm assuming is the cache log
(/var/tmp/revisorrevisor-yum.log) is empty. The cache directory
(/var/tmp/revisor-yumcache) has been created and there's a subdirectory
for each of the entries that were on the repo screen (development, fedora,
updates) and each has various items including an empty packages directory.
The log (/var/log/revisor.log) ends with a copy of the warning I received
about /srv/revisor already existing (from a previous failed run).
Any suggestions on troubleshooting this?
What version of Revisor are you using? (rpm -q revisor)
Maybe rip Revisor out and beat it with a baseball bat?
Sure. Just not the face ;-)
Jonathan Steffan
daMaestro
8:47 a.m.
New subject: Revisor stalls while downloading packages
On Wed, 2007-07-04 at 07:35 -0600, Tim Wood wrote:
> Last night I started running Revisor.
What type of media are you creating?
A live cd.
> I thought I'd finally gotten all
> the config files convinced to play nice.
May we see?
I've attached the three I've modified. sw-gateway-ks-0.0.1.cfg is my
kickstart. The 192.168... address is my local repository
> I'm using a repository that
> existing on another machine on the same network. I haven't tested this
> repository extensively (it's a replacement for a machine that died), but
> have used it to do a couple of recent installs/updates on 1 machine and
> everything seems to work properly.
>
> It got to the "Building your media" screen, went through checking
> dependencies and then sat there on downloading packages. I check it
> with
> ps and it was taking 10+% CPU and 23% Memory. This morning, it's still
> in
> the same stage (downloading media) and the task progress bar has not
> moved. CPU usage has dropped to 1%.
It sounds like you hit a bug. If you're willing, run Revisor from a
terminal so you can get the traceback.
I'd be happy to. After doing the command (revisor), how do I do a traceback?
> What I'm assuming is the cache log
> (/var/tmp/revisorrevisor-yum.log) is empty. The cache directory
> (/var/tmp/revisor-yumcache) has been created and there's a subdirectory
> for each of the entries that were on the repo screen (development,
> fedora,
> updates) and each has various items including an empty packages
> directory.
> The log (/var/log/revisor.log) ends with a copy of the warning I
> received
> about /srv/revisor already existing (from a previous failed run).
>
> Any suggestions on troubleshooting this?
What version of Revisor are you using? (rpm -q revisor)
2.0.4
> Maybe rip Revisor out and beat it with a baseball bat?
Sure. Just not the face ;-)
Hehehe. Yeah. (Almost) anything to avoid going back to customizing knoppix.
5:07 p.m.
New subject: Revisor stalls while downloading packages
[snip]
>> What type of media are you creating?
>
> A live cd.
>
[snip]
> I've attached the three I've modified.
sw-gateway-ks-0.0.1.cfg is my
> kickstart. The 192.168... address is my local repository
>
>
>>> I'm using a repository that
>>> existing on another machine on the same network. I haven't tested
[snip]
I'm concerned with that, as Revisor (or actually the yum object Revisor
creates for doing dependency resolving and downloading packages),
really, really depends on good repositories. I see there's a disc1/
directory which I can only hope is not the DVD of what the Fedora
Project released, rather then the Everything tree.
I repointed that to RPMS.os. All of a sudden I'm getting a 'no groups'
error right before resolving dependencies. But, it's downloading
packages. What's the problem with the install DVD?
If you run from a gnome-terminal -like prompt, you can run:
revisor --debug > ~/revisor.log
I didn't realize that's all that term means... Interesting.
>>> Maybe rip Revisor out and beat it with a baseball bat?
>> Sure. Just not the face ;-)
>
> Hehehe. Yeah. (Almost) anything to avoid going back to customizing
> knoppix.
Gheghe, you know revisor started beating /some-other-application/ with a
baseball bat, and *in* the face, right? ;-)
Jeroen, it feels like that ;-) I suspect I'm missing an inside joke
here... 42, fully ladden swallows and Gheghe perhaps... Ah well, 2 out
of 3 ain't bad...
thanks and regards, Tim
5:09 p.m.
New subject: Revisor stalls while downloading packages
Tim Wood wrote:
> On Wed, 2007-07-04 at 07:35 -0600, Tim Wood wrote:
>> Last night I started running Revisor.
> What type of media are you creating?
A live cd.
>> I thought I'd finally gotten all
>> the config files convinced to play nice.
> May we see?
I've attached the three I've modified. sw-gateway-ks-0.0.1.cfg is my
kickstart. The 192.168... address is my local repository
>> I'm using a repository that
>> existing on another machine on the same network. I haven't tested this
>> repository extensively (it's a replacement for a machine that died), but
>> have used it to do a couple of recent installs/updates on 1 machine and
>> everything seems to work properly.
>>
I'm concerned with that, as Revisor (or actually the yum object Revisor
creates for doing dependency resolving and downloading packages),
really, really depends on good repositories. I see there's a disc1/
directory which I can only hope is not the DVD of what the Fedora
Project released, rather then the Everything tree.
>> It got to the "Building your media" screen, went
through checking
>> dependencies and then sat there on downloading packages. I check it
>> with
>> ps and it was taking 10+% CPU and 23% Memory. This morning, it's still
>> in
>> the same stage (downloading media) and the task progress bar has not
>> moved. CPU usage has dropped to 1%.
> It sounds like you hit a bug. If you're willing, run Revisor from a
> terminal so you can get the traceback.
I'd be happy to. After doing the command (revisor), how do I do a traceback?
If you run from a gnome-terminal -like prompt, you can run:
revisor --debug > ~/revisor.log
That'd ensure everything is in /a/ logfile, that we can use to track
down the issue here. Mind that our logging facility is... erhm...
b0rked. Hence the original revisor logfile not showing as much as we'd
want it to.
>> Maybe rip Revisor out and beat it with a baseball bat?
> Sure. Just not the face ;-)
Hehehe. Yeah. (Almost) anything to avoid going back to customizing knoppix.
Gheghe, you know revisor started beating /some-other-application/ with a
baseball bat, and *in* the face, right? ;-)
Kind regards,
Jeroen van Meeuwen
-kanarip
5:35 p.m.
New subject: Revisor stalls while downloading packages
--- Jeroen van Meeuwen <kanarip(a)kanarip.com> wrote:
>>> Maybe rip Revisor out and beat it with a baseball bat?
>> Sure. Just not the face ;-)
>
> Hehehe. Yeah. (Almost) anything to avoid going back to
customizing knoppix.
>
Gheghe, you know revisor started beating /some-other-application/
with a
baseball bat, and *in* the face, right? ;-)
What are you talking about?
-dmc/jdog
____________________________________________________________________________________
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for
today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
5:40 p.m.
New subject: Revisor stalls while downloading packages
Jane Dogalt wrote:
--- Jeroen van Meeuwen <kanarip(a)kanarip.com> wrote:
>>>> Maybe rip Revisor out and beat it with a baseball bat?
>>> Sure. Just not the face ;-)
>> Hehehe. Yeah. (Almost) anything to avoid going back to
> customizing knoppix.
> Gheghe, you know revisor started beating /some-other-application/
> with a
> baseball bat, and *in* the face, right? ;-)
What are you talking about?
-dmc/jdog
Inside joke, never mind.
Kind regards,
Jeroen van Meeuwen
-kanarip
5:56 p.m.
New subject: Revisor stalls while downloading packages
Tim Wood wrote:
[snip]
>>> What type of media are you creating?
>> A live cd.
>>
[snip]
>> I've attached the three I've modified. sw-gateway-ks-0.0.1.cfg is my
>> kickstart. The 192.168... address is my local repository
>>
>>
>>>> I'm using a repository that
>>>> existing on another machine on the same network. I haven't tested
[snip]
> I'm concerned with that, as Revisor (or actually the yum object Revisor
> creates for doing dependency resolving and downloading packages),
> really, really depends on good repositories. I see there's a disc1/
> directory which I can only hope is not the DVD of what the Fedora
> Project released, rather then the Everything tree.
I repointed that to RPMS.os. All of a sudden I'm getting a 'no groups'
error right before resolving dependencies. But, it's downloading
packages. What's the problem with the install DVD?
Nothing in particular actually. But as it showed 'disc1' and no other
discs being released I was confused with what exactly was in that
repository ;-).
The no groups error usually comes from lacking comps.xml in the
repository metadata. Revisor uses that comps to create the list of
Categories and Groups during package selection.
Kind regards,
Jeroen van Meeuwen
-kanarip
9:42 p.m.
New subject: How to fix Resolver not seeing your comps.xml file
The no groups error usually comes from lacking comps.xml in the
repository metadata. Revisor uses that comps to create the list of
Categories and Groups during package selection.
Grumble. I'm using mrepo to build my repository. It's great except that
it seems to ignore the comps.xml file on the source repository. In
futzing around, I found out (FWIW) that Resolver (or anything else hitting
your repo) finds the comps.xml file by looking in the repomd.xml file. I
was able to solve the problem by copying the comparable section out of the
repomd.xml on the official fedora repository into my repomd.xml. Then, it
was just a matter of making sure the path, etc., in that section were
correct for my repo.
regards, Tim
4:07 a.m.
New subject: How to fix Resolver not seeing your comps.xml file
Tim Wood wrote:
> The no groups error usually comes from lacking comps.xml in the
> repository metadata. Revisor uses that comps to create the list of
> Categories and Groups during package selection.
Grumble. I'm using mrepo to build my repository. It's great except that
it seems to ignore the comps.xml file on the source repository.
You should report this issue to Dag then.
Rahul
12:26 p.m.
New subject: How to fix Resolver not seeing your comps.xml file
> Grumble. I'm using mrepo to build my repository. It's
great except
> that
> it seems to ignore the comps.xml file on the source repository.
You should report this issue to Dag then.
Yes... haven't had time to locate his bug reporting page/tool/whatever...
regards, Tim
1:11 p.m.
New subject: How to fix Resolver not seeing your comps.xml file
When I create a traditional kickstart, I'm able to preface a package name
with a dash to not install it. For instance:
@base-x
-linuxwacom
-synaptics
I can't seem to make the same thing work when Revisor is using a kickstart
file. Is there a way to make this work or is the only solution to copy
each package name I want (from say the comps.xml file)?
thanks, Tim
6148
days inactive
6173
days old
livecd@lists.fedoraproject.org
26 comments
8 participants
participants (8)
-
Jane Dogalt -
Jeroen van Meeuwen -
John Babich -
john pleines -
Jonathan Steffan -
Patrice Guay -
Rahul Sundaram -
Tim Wood