Red Hat Bugzilla – Bug 217945
FC6 LiveCD tracker bug
Last modified: 2014-03-16 23:04:29 EDT
Tracker bug for FC6 live cd.
Adding link to LiveCD Wiki page for reference:
I guess I should add this bug to this tracker.
system-config-network is missing.
user can't configure network for static ip easily without it.
alternate method: use ifconfig or edit ifcfg-eth0
See Personal Note for FC6 LiveCD at:
I would like to file some "Feature Requests" for pilgrim, I don't know where to
do this, but this is where I was linked to from FedoraForum
1. I would like for there to be a GUI for generating a live-cd using pilgrim.
2. More Importantly I would like for easy re-branding of a live-cd using
pilgrim, it's kind of hard to look for all the right pictures to replace, if
part of the tool would allow users to choose the particular logos to replace it
would make forks much easier especially given the likelihood that people will
fork fedora and add non-oss apps to it, it would be good to make it easier for
fedora to distance itself from this. This second request can probably be
implemented more easily if the first one goes through.
I can't seem to download the livecd using the torrent it time's out connecting
to the tracker. This was mentioned in a previous post but I'd like to reiterate
that its occuring for me as of this date.
(In reply to comment #4)
> I can't seem to download the livecd using the torrent it time's out connecting
> to the tracker. This was mentioned in a previous post but I'd like to reiterate
> that its occuring for me as of this date.
[marc@strikeforce Zod-livecd-1-i386]$ traceroute torrent.linux.duke.edu
traceroute to torrent.linux.duke.edu (18.104.22.168), 30 hops max, 40 byte packets
1 fcserver.mwiriadi.id.au (192.168.1.1) 0.206 ms 0.210 ms 0.224 ms
2 nexthop.wa.ii.net (22.214.171.124) 15.787 ms 17.145 ms 17.610 ms
3 gi2-4.per-qv1-bdr1.ii.net (126.96.36.199) 19.620 ms 21.033 ms 21.965 ms
4 gi0-14-0-0.syd-ult-core1.ii.net (188.8.131.52) 83.349 ms 83.998 ms
gi0-14-0-1.syd-ult-core1.ii.net (184.108.40.206) 85.213 ms
5 220.127.116.11 (18.104.22.168) 86.911 ms 88.618 ms 90.581 ms
6 22.214.171.124 (126.96.36.199) 247.350 ms 247.543 ms 248.992 ms
7 pax-brdr-02.inet.qwest.net (188.8.131.52) 249.953 ms 230.341 ms 231.641 ms
8 svl-core-01.inet.qwest.net (184.108.40.206) 233.601 ms 234.533 ms 236.003 ms
9 dca-core-02.inet.qwest.net (220.127.116.11) 304.342 ms 296.565 ms 297.929 ms
10 dca-edge-02.inet.qwest.net (18.104.22.168) 305.159 ms 306.035 ms 307.034 ms
11 gw-dc-mcnc.ncren.net (22.214.171.124) 321.040 ms 322.221 ms 323.666 ms
12 rlgh7600-2-gw-to-rlgh1-2-gw.ncren.net (126.96.36.199) 321.433 ms 322.394
ms 309.764 ms
13 roti-gw-to-rlgh7600-gw.ncren.net (188.8.131.52) 306.061 ms 307.443 ms
14 trinity-v400.netcom.duke.edu (184.108.40.206) 320.473 ms 321.420 ms 315.600 ms
15 * * *
It carries on with the *** to 30 hops.
Thank you for this work!
Is there a particular location at which we can look for the source code that
the FC6LiveCDTracker is based on?
(In reply to comment #6)
> Thank you for this work!
> Is there a particular location at which we can look for the source code that
> the FC6LiveCDTracker is based on?
I believe you're refering to following location:
In future, please use fedora-livecd-list for support question:
In livecd-installer, line 71 and line 74 are the same, I think line 74 should be
I just burn the live CD iso but when i try to boot it it hangs on first mouse
I am attempting to run the Fedora Core LiveCD received with Fedora 6 and RHEL
Bible book by wiley. I am assuming it is the same build although there is not
much on the content of the CD to indicate which build or version.
The problem I am having (tested on 2 different intel desktops, older Dell 4100
dimension and newer Lenovo 3000J) is that after the initial boot my monitor
displays "Mode not supported H:68.8KHZ V:85.1HZ" and the display never comes
back. I used the same monitor on both machines. The monitor is a MAG innovision
Model #900P flatscreen.
Apologies if I am posting this in the wrong place.
Adding Tracking keyword
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.