From 2d830697a3a73675ae59baa0a28fe529149b859b Mon Sep 17 00:00:00 2001 From: "Brian C. Lane" Date: Thu, 29 Jan 2015 12:20:34 -0800 Subject: [PATCH] Moved livecd-tools to github --- API | 78 --- AUTHORS | 3 - COPYING | 342 --------- HACKING | 28 - Makefile | 56 -- README | 167 ----- config/livecd-fedora-minimal.ks | 15 - dead.repo | 3 + docs/livecd-creator.pod | 117 ---- docs/livecd-iso-to-disk.pod | 164 ----- docs/mkbiarch.8 | 89 --- imgcreate/__init__.py | 68 -- imgcreate/creator.py | 947 ------------------------- imgcreate/debug.py | 92 --- imgcreate/errors.py | 58 -- imgcreate/fs.py | 659 ------------------ imgcreate/kickstart.py | 612 ---------------- imgcreate/live.py | 1040 ---------------------------- imgcreate/util.py | 39 -- imgcreate/yuminst.py | 236 ------- tools/edit-livecd | 738 -------------------- tools/livecd-creator | 236 ------- tools/livecd-iso-to-disk.sh | 1456 --------------------------------------- tools/livecd-iso-to-pxeboot.sh | 144 ---- tools/liveimage-mount | 298 -------- tools/mkbackup.py | 99 --- tools/mkbiarch.py | 303 -------- 27 files changed, 3 insertions(+), 8084 deletions(-) delete mode 100644 API delete mode 100644 AUTHORS delete mode 100644 COPYING delete mode 100644 HACKING delete mode 100644 Makefile delete mode 100644 README delete mode 100644 config/livecd-fedora-minimal.ks create mode 100644 dead.repo delete mode 100644 docs/livecd-creator.pod delete mode 100644 docs/livecd-iso-to-disk.pod delete mode 100644 docs/mkbiarch.8 delete mode 100644 imgcreate/__init__.py delete mode 100644 imgcreate/creator.py delete mode 100644 imgcreate/debug.py delete mode 100644 imgcreate/errors.py delete mode 100644 imgcreate/fs.py delete mode 100644 imgcreate/kickstart.py delete mode 100755 imgcreate/live.py delete mode 100644 imgcreate/util.py delete mode 100644 imgcreate/yuminst.py delete mode 100755 tools/edit-livecd delete mode 100755 tools/livecd-creator delete mode 100755 tools/livecd-iso-to-disk.sh delete mode 100755 tools/livecd-iso-to-pxeboot.sh delete mode 100755 tools/liveimage-mount delete mode 100644 tools/mkbackup.py delete mode 100644 tools/mkbiarch.py diff --git a/API b/API deleted file mode 100644 index 9783c74..0000000 --- a/API +++ /dev/null @@ -1,78 +0,0 @@ -In addition to livecd-creator itself, the livecd-creator package -provides a python API for building your own, other types of images. -This API could also be used to build on top of the live image -functionality. - -== Image Creation Frontends == - -livecd-creator and image-creator are both frontends for creating -images. But really, it's straight-forward to build your own which -deals with your own specific needs. To do so, you'll want to do -the following: - -* Create a pykickstart handler object. All of the image creators are -driven by data stored in pykickstart handlers. -* Then, instantiate a creator - creator = ImageCreator(ks, name) - where ks is your pykickstart object and name is the label/name you - want for the image. -* With the image, you can either do everything in one-shot with - creator.create() - or call the steps of creator.create() itself. The latter lets you add - an interactive shell step if you want as well as a few other - options. The order, though, is - creator.mount() - creator.install() - creator.configure() - creator.unmount() - creator.package() - - Other available methods are - * creator.launch_shell(): This launches a root shell within the - install root - * creator.cleanup(): Tear down the image. Note that this also - occurs when the image object is deleted - - -== Image Creator Backends == - -The basic idea is that there are (presently) 3 main classes used to -implement different types of images. No matter which you use, the -interface should be largely the same. This means that, eg, -livecd-creator _could_ generate other types of outputs just by -switching from the LiveImageCreator to another ImageCreator object. - -* ImageCreator: This is the guts of what most image creators will - need to use. It provides all of the bits to handle a kickstart - config, install packages into an install root, etc. It leaves - a number of hook methods which maybe be implemented by more specific - creators: - i) _mount_instroot(self): This method is where your filesystems - should get mounted. The root of your filesystem tree should be - located at self._instroot - ii) _unmount_instroot(self): This method is called to undo - _mount_instroot() basically. - iii) _create_bootconfig(self): Set up anything needed for your - image to boot. This could involve creating an initramfs, writing a - bootloader configuration, etc. The filesystem is still mounted at - self._instroot at this point. Note that this could be a no-op. - iv) _stage_final_image(self): Do whatever is needed to make your - image "consumable" and copy it to self._outdir. eg, for live CDs, - this is where we generate the iso images. Note that this could be - a no-op. - - Other hooks are available to subclasses, as well as a number of - helper methods which can be used in implementing the hooks. See - the inline docstrings for more details. - - Overriding other methods is not supported or guaranteed to continue - to give consistent results over time. - -* LoopImageCreator: This generates ext3 images in a loopback file - which could then later be booted in a virtual machine environment. - NOTE: this does nothing to set up booting - -* LiveImageCreator: This builds on top of the LoopImageCreator to - build live images which use dm-snapshot, etc. This is what is used - by livecd-creator. - diff --git a/AUTHORS b/AUTHORS deleted file mode 100644 index 6f70bcc..0000000 --- a/AUTHORS +++ /dev/null @@ -1,3 +0,0 @@ -David Zeuthen -Jeremy Katz -Douglas McClendon diff --git a/COPYING b/COPYING deleted file mode 100644 index 9115ee6..0000000 --- a/COPYING +++ /dev/null @@ -1,342 +0,0 @@ - - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 - - Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA - - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -License is intended to guarantee your freedom to share and change free -software--to make sure the software is free for all its users. This -General Public License applies to most of the Free Software -Foundation's software and to any other program whose authors commit to -using it. (Some other Free Software Foundation software is covered by -the GNU Library General Public License instead.) You can apply it to -your programs, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -this service if you wish), that you receive source code or can get it -if you want it, that you can change the software or use pieces of it -in new free programs; and that you know you can do these things. - - To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the rights. -These restrictions translate to certain responsibilities for you if you -distribute copies of the software, or if you modify it. - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must give the recipients all the rights that -you have. You must make sure that they, too, receive or can get the -source code. And you must show them these terms so they know their -rights. - - We protect your rights with two steps: (1) copyright the software, and -(2) offer you this license which gives you legal permission to copy, -distribute and/or modify the software. - - Also, for each author's protection and ours, we want to make certain -that everyone understands that there is no warranty for this free -software. If the software is modified by someone else and passed on, we -want its recipients to know that what they have is not the original, so -that any problems introduced by others will not reflect on the original -authors' reputations. - - Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that redistributors of a free -program will individually obtain patent licenses, in effect making the -program proprietary. To prevent this, we have made it clear that any -patent must be licensed for everyone's free use or not licensed at all. - - The precise terms and conditions for copying, distribution and -modification follow. - - GNU GENERAL PUBLIC LICENSE - TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. This License applies to any program or other work which contains -a notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". - -Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running the Program is not restricted, and the output from the Program -is covered only if its contents constitute a work based on the -Program (independent of having been made by running the Program). -Whether that is true depends on what the Program does. - - 1. You may copy and distribute verbatim copies of the Program's -source code as you receive it, in any medium, provided that you -conspicuously and appropriately publish on each copy an appropriate -copyright notice and disclaimer of warranty; keep intact all the -notices that refer to this License and to the absence of any warranty; -and give any other recipients of the Program a copy of this License -along with the Program. - -You may charge a fee for the physical act of transferring a copy, and -you may at your option offer warranty protection in exchange for a fee. - - 2. You may modify your copy or copies of the Program or any portion -of it, thus forming a work based on the Program, and copy and -distribute such modifications or work under the terms of Section 1 -above, provided that you also meet all of these conditions: - - a) You must cause the modified files to carry prominent notices - stating that you changed the files and the date of any change. - - b) You must cause any work that you distribute or publish, that in - whole or in part contains or is derived from the Program or any - part thereof, to be licensed as a whole at no charge to all third - parties under the terms of this License. - - c) If the modified program normally reads commands interactively - when run, you must cause it, when started running for such - interactive use in the most ordinary way, to print or display an - announcement including an appropriate copyright notice and a - notice that there is no warranty (or else, saying that you provide - a warranty) and that users may redistribute the program under - these conditions, and telling the user how to view a copy of this - License. (Exception: if the Program itself is interactive but - does not normally print such an announcement, your work based on - the Program is not required to print an announcement.) - -These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Program, -and can be reasonably considered independent and separate works in -themselves, then this License, and its terms, do not apply to those -sections when you distribute them as separate works. But when you -distribute the same sections as part of a whole which is a work based -on the Program, the distribution of the whole must be on the terms of -this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote it. - -Thus, it is not the intent of this section to claim rights or contest -your rights to work written entirely by you; rather, the intent is to -exercise the right to control the distribution of derivative or -collective works based on the Program. - -In addition, mere aggregation of another work not based on the Program -with the Program (or with a work based on the Program) on a volume of -a storage or distribution medium does not bring the other work under -the scope of this License. - - 3. You may copy and distribute the Program (or a work based on it, -under Section 2) in object code or executable form under the terms of -Sections 1 and 2 above provided that you also do one of the following: - - a) Accompany it with the complete corresponding machine-readable - source code, which must be distributed under the terms of Sections - 1 and 2 above on a medium customarily used for software interchange; or, - - b) Accompany it with a written offer, valid for at least three - years, to give any third party, for a charge no more than your - cost of physically performing source distribution, a complete - machine-readable copy of the corresponding source code, to be - distributed under the terms of Sections 1 and 2 above on a medium - customarily used for software interchange; or, - - c) Accompany it with the information you received as to the offer - to distribute corresponding source code. (This alternative is - allowed only for noncommercial distribution and only if you - received the program in object code or executable form with such - an offer, in accord with Subsection b above.) - -The source code for a work means the preferred form of the work for -making modifications to it. For an executable work, complete source -code means all the source code for all modules it contains, plus any -associated interface definition files, plus the scripts used to -control compilation and installation of the executable. However, as a -special exception, the source code distributed need not include -anything that is normally distributed (in either source or binary -form) with the major components (compiler, kernel, and so on) of the -operating system on which the executable runs, unless that component -itself accompanies the executable. - -If distribution of executable or object code is made by offering -access to copy from a designated place, then offering equivalent -access to copy the source code from the same place counts as -distribution of the source code, even though third parties are not -compelled to copy the source along with the object code. - - 4. You may not copy, modify, sublicense, or distribute the Program -except as expressly provided under this License. Any attempt -otherwise to copy, modify, sublicense or distribute the Program is -void, and will automatically terminate your rights under this License. -However, parties who have received copies, or rights, from you under -this License will not have their licenses terminated so long as such -parties remain in full compliance. - - 5. You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Program or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Program (or any work based on the -Program), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying -the Program or works based on it. - - 6. Each time you redistribute the Program (or any work based on the -Program), the recipient automatically receives a license from the -original licensor to copy, distribute or modify the Program subject to -these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties to -this License. - - 7. If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you -may not distribute the Program at all. For example, if a patent -license would not permit royalty-free redistribution of the Program by -all those who receive copies directly or indirectly through you, then -the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Program. - -If any portion of this section is held invalid or unenforceable under -any particular circumstance, the balance of the section is intended to -apply and the section as a whole is intended to apply in other -circumstances. - -It is not the purpose of this section to induce you to infringe any -patents or other property right claims or to contest validity of any -such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system, which is -implemented by public license practices. Many people have made -generous contributions to the wide range of software distributed -through that system in reliance on consistent application of that -system; it is up to the author/donor to decide if he or she is willing -to distribute software through any other system and a licensee cannot -impose that choice. - -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. - - 8. If the distribution and/or use of the Program is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Program under this License -may add an explicit geographical distribution limitation excluding -those countries, so that distribution is permitted only in or among -countries not thus excluded. In such case, this License incorporates -the limitation as if written in the body of this License. - - 9. The Free Software Foundation may publish revised and/or new versions -of the General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - -Each version is given a distinguishing version number. If the Program -specifies a version number of this License which applies to it and "any -later version", you have the option of following the terms and conditions -either of that version or of any later version published by the Free -Software Foundation. If the Program does not specify a version number of -this License, you may choose any version ever published by the Free Software -Foundation. - - 10. If you wish to incorporate parts of the Program into other free -programs whose distribution conditions are different, write to the author -to ask for permission. For software which is copyrighted by the Free -Software Foundation, write to the Free Software Foundation; we sometimes -make exceptions for this. Our decision will be guided by the two goals -of preserving the free status of all derivatives of our free software and -of promoting the sharing and reuse of software generally. - - NO WARRANTY - - 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY -FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN -OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES -PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED -OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF -MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS -TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE -PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, -REPAIR OR CORRECTION. - - 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR -REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, -INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING -OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED -TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY -YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER -PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE -POSSIBILITY OF SUCH DAMAGES. - - END OF TERMS AND CONDITIONS - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - - Copyright (C) - - This program is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; either version 2 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this program; if not, write to the Free Software - Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA - - -Also add information on how to contact you by electronic and paper mail. - -If the program is interactive, make it output a short notice like this -when it starts in an interactive mode: - - Gnomovision version 69, Copyright (C) year name of author - Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, the commands you use may -be called something other than `show w' and `show c'; they could even be -mouse-clicks or menu items--whatever suits your program. - -You should also get your employer (if you work as a programmer) or your -school, if any, to sign a "copyright disclaimer" for the program, if -necessary. Here is a sample; alter the names: - - Yoyodyne, Inc., hereby disclaims all copyright interest in the program - `Gnomovision' (which makes passes at compilers) written by James Hacker. - - , 1 April 1989 - Ty Coon, President of Vice - -This General Public License does not permit incorporating your program into -proprietary programs. If your program is a subroutine library, you may -consider it more useful to permit linking proprietary applications with the -library. If this is what you want to do, use the GNU Library General -Public License instead of this License. diff --git a/HACKING b/HACKING deleted file mode 100644 index 00fbe3c..0000000 --- a/HACKING +++ /dev/null @@ -1,28 +0,0 @@ - -SOURCE CONTROL MANAGEMENT -========================= - -This project is stored in git and can be checked out using - - git clone git://git.fedorahosted.org/git/livecd - -or if you have write access you might want to use - - git clone ssh://git.fedorahosted.org/git/livecd - -Change history etc. can be obtained from the web interface - - http://git.fedoraproject.org/?p=hosted/livecd - -PATCHES -======= - -Send patches to the livecd@lists.fedoraproject.org mailing list - - https://lists.fedoraproject.org/mailman/listinfo/livecd - -If you have a number of patches and want to have them pulled from a -public git repository, please post a pointer to it as well as sending -each of the patches individually to the list. Note that the -combination of git-format-patch and git-send-email works well for -sending a series of patches which you have in a local repository. diff --git a/Makefile b/Makefile deleted file mode 100644 index 7227ea4..0000000 --- a/Makefile +++ /dev/null @@ -1,56 +0,0 @@ - -VERSION = 21.4 - -INSTALL = /usr/bin/install -c -INSTALL_PROGRAM = ${INSTALL} -INSTALL_DATA = ${INSTALL} -m 644 -INSTALL_SCRIPT = ${INSTALL_PROGRAM} - -INSTALL_PYTHON = ${INSTALL} -m 644 -define COMPILE_PYTHON - python -c "import compileall as c; c.compile_dir('$(1)', force=1)" - python -O -c "import compileall as c; c.compile_dir('$(1)', force=1)" -endef -PYTHONDIR := $(shell python -c "import distutils.sysconfig as d; print d.get_python_lib()") - -all: - -man: - pod2man --section=8 --release="livecd-tools $(VERSION)" --center "LiveCD Tools" docs/livecd-creator.pod > docs/livecd-creator.8 - pod2man --section=8 --release="livecd-tools $(VERSION)" --center "LiveCD Tools" docs/livecd-iso-to-disk.pod > docs/livecd-iso-to-disk.8 - - -install: man - $(INSTALL_PROGRAM) -D tools/livecd-creator $(DESTDIR)/usr/bin/livecd-creator - ln -s ./livecd-creator $(DESTDIR)/usr/bin/image-creator - $(INSTALL_PROGRAM) -D tools/liveimage-mount $(DESTDIR)/usr/bin/liveimage-mount - $(INSTALL_PROGRAM) -D tools/livecd-iso-to-disk.sh $(DESTDIR)/usr/bin/livecd-iso-to-disk - $(INSTALL_PROGRAM) -D tools/livecd-iso-to-pxeboot.sh $(DESTDIR)/usr/bin/livecd-iso-to-pxeboot - $(INSTALL_PROGRAM) -D tools/edit-livecd $(DESTDIR)/usr/bin/edit-livecd - $(INSTALL_PROGRAM) -D tools/mkbiarch.py $(DESTDIR)/usr/bin/mkbiarch - $(INSTALL_DATA) -D AUTHORS $(DESTDIR)/usr/share/doc/livecd-tools/AUTHORS - $(INSTALL_DATA) -D COPYING $(DESTDIR)/usr/share/doc/livecd-tools/COPYING - $(INSTALL_DATA) -D README $(DESTDIR)/usr/share/doc/livecd-tools/README - $(INSTALL_DATA) -D HACKING $(DESTDIR)/usr/share/doc/livecd-tools/HACKING - mkdir -p $(DESTDIR)/usr/share/livecd-tools/ - mkdir -p $(DESTDIR)/$(PYTHONDIR)/imgcreate - $(INSTALL_PYTHON) -D imgcreate/*.py $(DESTDIR)/$(PYTHONDIR)/imgcreate/ - $(call COMPILE_PYTHON,$(DESTDIR)/$(PYTHONDIR)/imgcreate) - mkdir -p $(DESTDIR)/usr/share/man/man8 - $(INSTALL_DATA) -D docs/*.8 $(DESTDIR)/usr/share/man/man8 - -uninstall: - rm -f $(DESTDIR)/usr/bin/livecd-creator - rm -rf $(DESTDIR)/usr/lib/livecd-creator - rm -rf $(DESTDIR)/usr/share/doc/livecd-tools-$(VERSION) - rm -f $(DESTDIR)/usr/bin/mkbiarch - -dist : all - git archive --format=tar --prefix=livecd-tools-$(VERSION)/ HEAD | bzip2 -9v > livecd-tools-$(VERSION).tar.bz2 - -release: dist - git tag -s -a -m "Tag as livecd-tools-$(VERSION)" livecd-tools-$(VERSION) - scp livecd-tools-$(VERSION).tar.bz2 fedorahosted.org:livecd - -clean: - rm -f *~ creator/*~ installer/*~ config/*~ docs/*.8 diff --git a/README b/README deleted file mode 100644 index a31d6d3..0000000 --- a/README +++ /dev/null @@ -1,167 +0,0 @@ - - The Fedora live CD tools - David Zeuthen - Jeremy Katz - - Last updated: March 10, 2014 (v20.5) - -This project concerns tools to generate live CD's on Fedora based -systems including derived distributions such as RHEL, CentOS and -others. See the project Wiki at - - http://fedoraproject.org/wiki/FedoraLiveCD - -for more details. Discussion of this project takes places at the -fedora-livecd@redhat.com mailing list - - http://www.redhat.com/mailman/listinfo/fedora-livecd-list - -This project and it's source files is licensed under the GPLv2 -license. See the file COPYING for details. - -1. LIVE CD DESIGN GOALS - -The live CD is designed in such a way that the when running from a -live CD, the system should appear as much as possible as a standard -system with all that entails; e.g. read-write rootfs (achieved using -dm-snapshot), standard ext3 file system (for extended attributes) and -so on. - -Another design goal is that the live CD should be ''installable'', -ie. an user should be able to install the bits from the live CD onto -his hard disk without this process requiring network access or -additional media. - -Finally, another design goal is that the tool set itself should be -separate from configuration; the same unmodified tool should be usable -for building various live CD flavors with vastly different -configurations, e.g. a GNOME live CD, a KDE live CD, a live cd with -music programs and so on. - -2. CREATING A LIVE CD - -To create a live cd, the livecd-creator tool is used. Super user -privileges are needed. The tool is more or less self-documenting, use -the --help option to see options. - -2.1 HOW THE LIVE CD CREATOR WORKS - -In a nutshell, the livecd-creator program - - o Sets up a file for the ext3 file system that will contain all the - data comprising the live CD - - o Loopback mounts that file into the file system so there is an - installation root - - o Bind mounts certain kernel file systems (/dev, /dev/pts, /proc, - /sys, /selinux) inside the installation root - - o Uses a configuration file to define the requested packages and - default configuration options. The format of this file is the same - as is used for installing a system via kickstart. - - o Installs, using yum, the requested packages into the installation - using the given repositories - - o Optionally runs scripts as specified by the live CD configuration file. - - o Relabels the entire installation root (for SELinux) - - o Creates a live CD specific initramfs that matches the installed kernel - - o Unmounts the kernel file systems mounted inside the installation root - - o Unmounts the installation root - - o Runs resize2fs to minimize and unminimize the ext3 file to remove data - from deleted files - - o Runs resize2fs to minimize on a devicemapper snapshot, to generate a - small minimized delta image file which can be used by anaconda to - reduce installation time by not copying unused data to disk - - o Creates a squashfs file system containing only the ext3 file (compression) - - o Configures the boot loader - - o Creates an iso9660 bootable CD - - -2.2 EXAMPLE: A BAREBONES LIVE CD - -The command - -# livecd-creator \ - --config=/usr/share/doc/livecd-tools/livecd-fedora-minimal.ks - -will create a live CD that will boot to a login prompt. Not that since -no configuration is done the user will not be able to login to the -system as the root password is not set / cleared. - -2.3 LIVE CD CONFIGURATION FILES - -The configuration of the live CD is defined by a file that uses the -same format as installing a system via kickstart. They can include -some basic system configuration items, the package manifest and a -script to be run at the end of the build process. - -For the Fedora project, there are currently a variety of different live CD -configuration files. The spin-kickstarts package includes all of the -kickstarts used to create the various spins. These include a minimal live image -(livecd-fedora-minimal.ks), a complete desktop image (livecd-fedora-desktop.ks) -and others. - -2.4 EXAMPLE: SPINNING THE FEDORA DESKTOP LIVE CD - -Assuming that you use the livecd-fedora-desktop.ks configuration file, -then the following command - -# livecd-creator \ - --config=/usr/share/spin-kickstarts/fedora-livecd-desktop.ks \ - --fslabel=Fedora-20-LiveCD-1-foo - -will create a live CD called "Fedora-7-LiveCD-1-foo". The name -given by --fslabel is used. - - o as a file system label on the ext3 and iso960 file systems - (as such it's visible on the desktop as the CD name) - - o in the isolinux boot loader - -If you have the repositories available locally and don't want to wait -for the download of packages, just substitute the URLs listed in the -configuration file to point to your local repositories. - -3. LIVE CD INSTALLS - -As of Fedora 7, anaconda has support for doing an installation -from a live CD. To use this, double click on the "Install to Hard -Drive" item on the desktop or run /usr/bin/liveinst if you don't have -such an icon. - -4. LIVE CD MEDIA VERIFICATION - -The live CD can incorporate functionality to verify itself. To do so, -you need to have anaconda-runtime installed both on the system used -for creating the image and installed into the image. This is so that -the implantisomd5 and checkisomd5 utilities can be used. These -utilities take advantage of embedding an md5sum into the application -area of the iso9660 image. This then gets verified before mounting -the real root filesystem. - -In a future release, the isomd5 utilities will probably be split out -of anaconda. - -5. USING LIVE IMAGES FROM USB MEDIA - -USB sticks are becoming increasingly prevalent and are a nice way to -use live images. You can take a live CD iso image and transform it so -that it can be used on a USB stick. To do so, use the -livecd-iso-to-disk script. - /usr/bin/livecd-iso-to-disk /path/to/live.iso /dev/sdb1 - -Replace /dev/sdb1 with the (unmounted) partition where you wish to put -the live image. This is not a destructive process; any data you -currently have on your USB stick will be preserved. - diff --git a/config/livecd-fedora-minimal.ks b/config/livecd-fedora-minimal.ks deleted file mode 100644 index 91abe9e..0000000 --- a/config/livecd-fedora-minimal.ks +++ /dev/null @@ -1,15 +0,0 @@ -lang en_US.UTF-8 -keyboard us -timezone US/Eastern -auth --useshadow --enablemd5 -selinux --enforcing -firewall --disabled -part / --size 1024 - -repo --name=development --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=$basearch - - -%packages -@standard - -%end diff --git a/dead.repo b/dead.repo new file mode 100644 index 0000000..7dcd0e0 --- /dev/null +++ b/dead.repo @@ -0,0 +1,3 @@ +livecd-tools has moved to github: + +https://github.com/rhinstaller/livecd-tools diff --git a/docs/livecd-creator.pod b/docs/livecd-creator.pod deleted file mode 100644 index ce7b94e..0000000 --- a/docs/livecd-creator.pod +++ /dev/null @@ -1,117 +0,0 @@ -=pod - -=head1 NAME - -livecd-creator - creates live CD or DVD images. - -=head1 SYNOPSIS - -B [OPTIONS] - -=head1 DESCRIPTION - -B creates live CD or DVD images(ISO images) from kickstart files. Kickstart files contain information about packages and configuration settings which are used to build the image. - -=head1 OPTIONS - -=over 4 - -=item -h, --help - -Shows the help message and exits. - -=back - -=head1 IMAGE OPTIONS - -These options define the created image. - -=over 4 - -=item -c KSCFG, --config=KSCFG - -Path to kickstart configuration file. - -=item -b BASE_ON, --base-on=BASE_ON - -Add packages to an existing live CD iso9660 image. - -=item -f FS_LABEL, --fslabel=FS_LABEL - -Defines the file system label. The default is based on the configuration name. - -=item --compression-type=COMPRESSOR - -Specify a compressor recognized by mksquashfs. -xz is the default and works with 2.6.38 and later kernels. -gzip works with all kernels. -lzo works with 2.6.36 and later kernels. -lzma will only work with custom kernels. -Set to 'None' to force reading the compressor used in BASE_ON. -If gzip is used, the -comp option is not passed to mksquashfs to allow the use of older versions of mksquashfs. - -=item --releasever=VER - -Set the value to substitute for $releasever in kickstart repo urls - -=back - -=head1 SYSTEM DIRECTORY OPTIONS - -These options define directories used on your system for creating the live image. - -=over 4 - -=item -t TMPDIR, --tmpdir=TMPDIR - -defines the temporary directory to use. The default directory is /var/tmp. - -=item --cache=CACHEDIR - -Defines the cache directory to use (default: private cache). - -=back - -=head1 EXAMPLES - -Barebones LiveCD - -livecd-creator \ ---config=/usr/share/livecd-tools/livecd-fedora-minimal.ks - -Fedora Desktop Live CD - -livecd-creator \ ---config=/usr/share/livecd-tools/livecd-fedora-desktop.ks \ ---fslabel=Fedora9-LiveCD-foo - -=head1 REPO EXTENSIONS - -livecd-creator provides for some extensions to the repo commands similar -to what yum supports. The strings $arch, $basearch and $releasever -are replaced with the system arch, basearch and release version respectively. -When no --releasever is passed it defaults to the current system's version. -The allows the use of repo commands such as the following: - -repo --name=fedora --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch - -Note that in a chroot environment (like koji) the rpmdb is not available, -so either don't use $releasever in that case, or pass --releasever=VER - -=head1 CONTRIBUTORS - -David Zeuthen, Jeremy Katz, Douglas McClendon and a team of many other contributors. See the AUTHORS file in the source distribution for the complete list of credits. - -=head1 BUGS - -Report bugs to the mailing list C or directly to Bugzilla C against the C product, and the C component. - -=head1 COPYRIGHT - -Copyright (C) Fedora Project 2008,2009, and various contributors. This is free software. You may redistribute copies of it under the terms of the GNU General Public License C. There is NO WARRANTY, to the extent permitted by law. - -=head1 SEE ALSO - -C, project website C - -=cut diff --git a/docs/livecd-iso-to-disk.pod b/docs/livecd-iso-to-disk.pod deleted file mode 100644 index cef973f..0000000 --- a/docs/livecd-iso-to-disk.pod +++ /dev/null @@ -1,164 +0,0 @@ -=pod - -=head1 NAME - -livecd-iso-to-disk - installs bootable Live images onto USB/SD storage devices. - -=head1 SYNOPSIS - -B [--help] [--noverify] [--format] [--reset-mbr] [--efi] [--skipcopy] [--force] [--xo] [--xo-no-home] [--timeout