Hello. I am trying to figure out how to use mkcdimage. Does anyone have any suggestions for using this script to create an ISO / IMG of my boot loader? I'm trying to create this to use with VirtualBox to create a Virtual connection to my dual boot Ubuntu 16.04 installation within Windows 10. Here are a few specific questions:
1. The notes on a recent mkcdimage commit says "use /usr/bin/env." Does this mean I need to copy mkcdimage and/or the boot loader folder structure to /usr/bin/? Where exactly should mkcdimage be placed, relative to the boot launcher or the rEFInd install directory?
2. Should I launch the process of creating my img from a Linux Live Boot Disk? Or can / should it be run from the booted linux environment that I want to create my IMG / ISO from?
3. Should I make any modifications to mkcdimage to point to my drives, partitions, and directories? Do I need to make sure my boot sector is copied to a specific location?
4. Do I also need to run mkdistrib and/or any other particular script before , during or after?
5. Any other advice for successfully creating this image?
All help and advice is appreciated. Thank you!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The commit message refers to the first line of the script, which now references /usr/bin/env, rather than /bin/bash (or whatever it had been using before that commit). This does not change where you install the script or how you use it.
The script is intended to be launched from my own development environment, in my main rEFInd source directory. It's completely untested anywhwere else, so you're basically on your own. As a starting point, try downloading the entire source tree (either via git or from a source code tarball -- but git may give you a few files that aren't in the source code tarball) and running mkdistrib, followed by mkcdimage, from there. Note that you'll need to have development tools, including GNU-EFI and/or TianoCore, installed. (You should probably test basic building via make before trying to use these scripts.)
On my system, mkdistrib and mkcdimage create files in ../snapshots/{version}, where {version} is the version number you pass to the scripts. (See the comments at the start of the scripts.) You'll probably have to create ../snapshots before you begin. You can change this, but then you'll need to debug your changes. A "boot sector" is an MBR booting concept; it's not used in EFI-mode booting, and rEFInd is an EFI-booting tool.
Yes, mkcdimage relies upon mkdistrib having already been run.
I've provided those scripts on the git repository mainly to help people who might want to pick up with rEFInd development -- to create a fork, say. They aren't well debugged, and you're pretty much on your own in using them. (I wrote them ages ago and have barely touched them since then, so I don't even remember what they do all that well.) Depending on your exact needs, you might be better off using mkcdimage as a model. That is, you can tweak a rEFInd configuration until it works the way you want, and then look at how the script creates a .img file and then calls mkisofs to create your own customized .iso file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello. I am trying to figure out how to use mkcdimage. Does anyone have any suggestions for using this script to create an ISO / IMG of my boot loader? I'm trying to create this to use with VirtualBox to create a Virtual connection to my dual boot Ubuntu 16.04 installation within Windows 10. Here are a few specific questions:
1. The notes on a recent mkcdimage commit says "use /usr/bin/env." Does this mean I need to copy mkcdimage and/or the boot loader folder structure to /usr/bin/? Where exactly should mkcdimage be placed, relative to the boot launcher or the rEFInd install directory?
2. Should I launch the process of creating my img from a Linux Live Boot Disk? Or can / should it be run from the booted linux environment that I want to create my IMG / ISO from?
3. Should I make any modifications to mkcdimage to point to my drives, partitions, and directories? Do I need to make sure my boot sector is copied to a specific location?
4. Do I also need to run mkdistrib and/or any other particular script before , during or after?
5. Any other advice for successfully creating this image?
All help and advice is appreciated. Thank you!
/usr/bin/env, rather than/bin/bash(or whatever it had been using before that commit). This does not change where you install the script or how you use it.gitor from a source code tarball -- butgitmay give you a few files that aren't in the source code tarball) and runningmkdistrib, followed bymkcdimage, from there. Note that you'll need to have development tools, including GNU-EFI and/or TianoCore, installed. (You should probably test basic building viamakebefore trying to use these scripts.)mkdistribandmkcdimagecreate files in../snapshots/{version}, where{version}is the version number you pass to the scripts. (See the comments at the start of the scripts.) You'll probably have to create../snapshotsbefore you begin. You can change this, but then you'll need to debug your changes. A "boot sector" is an MBR booting concept; it's not used in EFI-mode booting, and rEFInd is an EFI-booting tool.mkcdimagerelies uponmkdistribhaving already been run.I've provided those scripts on the
gitrepository mainly to help people who might want to pick up with rEFInd development -- to create a fork, say. They aren't well debugged, and you're pretty much on your own in using them. (I wrote them ages ago and have barely touched them since then, so I don't even remember what they do all that well.) Depending on your exact needs, you might be better off usingmkcdimageas a model. That is, you can tweak a rEFInd configuration until it works the way you want, and then look at how the script creates a.imgfile and then callsmkisofsto create your own customized.isofile.