Bug 168050 - It would be nice to be able to easily bootstrap fedora in a chroot
It would be nice to be able to easily bootstrap fedora in a chroot
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2005-09-11 13:25 EDT by Guido Trotter
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-19 14:06:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Guido Trotter 2005-09-11 13:25:50 EDT
Fedora already supports bootstrapping itself in a chroot, for example as
described in http://www.fedoraproject.org/wiki/FedoraXenQuickstart .
Unfortunately to use the procedure you need a MAKEDEV compatible with the one
shipped by fedora, and yum. It would be nice to have an easier method to
bootstrap it from inside a different linux distribution, for use with xen and
other virtualization tecniques (eg: uml, linux-vserver).

Other distribution already do this (eg, gentoo with the stage tarballs, debian
and ubuntu with "debootstrap") and I think it would be a nice enhancement for
fedora too...
Comment 1 Jeremy Katz 2005-09-19 14:06:09 EDT
The real answre here isn't going to be bootstrapping in a chroot but full
support for Xen.  In the works for FC5
Comment 2 Guido Trotter 2005-09-20 03:25:57 EDT
Not completely true... Other other distributions (eg. suse) support xen but only
have a possibility to install a new version of themselves starting from their
cotrol panel, which doesn't help if the host system is a different one.

What I'm recommending is that it should be kept simple to install Fedora even
starting from something which is not Fedora!

Note You need to log in before you can comment on or make changes to this bug.