[arch-releng] [RFC] [PATCH] [archiso] Add support for squashfs compression types
Add a note about supported status in Linux versions. Needs squashfs-tools-4.1 (now on extra). Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> --- archiso/mkarchiso | 12 +++++++++--- 1 files changed, 9 insertions(+), 3 deletions(-) diff --git a/archiso/mkarchiso b/archiso/mkarchiso index c7de1da..e836a35 100755 --- a/archiso/mkarchiso +++ b/archiso/mkarchiso @@ -7,6 +7,7 @@ PACCONFIG="/etc/pacman.conf" export LABEL="ARCH_$(date +%Y%m)" PUBLISHER="Arch Linux <http://www.archlinux.org>" APPLICATION="Arch Linux Live/Rescue CD" +COMPRESSION="gzip" CREATE_DEFAULT="n" APPNAME=$(basename "${0}") @@ -22,6 +23,10 @@ usage () echo " -L <label> Set a label for the disk" echo " -P <publisher> Set a publisher for the disk" echo " -A <application> Set an application name for the disk" + echo " -c <compressor> Set SquashFS compression type: gzip, lzma or lzo. Default $COMPRESSION" + echo " NOTES:" + echo " lzma: not officially supported yet by Linux (2.6.36)" + echo " lzo: needs Linux >= 2.6.36" echo " -d Create default user directory /home/arch" echo " -v Enable verbose output" echo " -h This message" @@ -34,13 +39,14 @@ usage () exit $1 } -while getopts 'p:C:L:P:A:dfvh' arg; do +while getopts 'p:C:L:P:A:cdfvh' arg; do case "${arg}" in p) PKGLIST="${PKGLIST} ${OPTARG}" ;; C) PACCONFIG="${OPTARG}" ;; L) LABEL="${OPTARG}" ;; P) PUBLISHER="${OPTARG}" ;; A) APPLICATION="${OPTARG}" ;; + c) COMPRESSION="${OPTARG}" ;; d) CREATE_DEFAULT="y" ;; f) FORCE="y" ;; v) QUIET="n" ;; @@ -187,9 +193,9 @@ _mksquash () { echo "Creating SquashFS image. This may take some time..." start=$(date +%s) if [ "${QUIET}" = "y" ]; then - mksquashfs "${1}" "${sqimg}" -noappend >/dev/null + mksquashfs "${1}" "${sqimg}" -noappend -comp "${COMPRESSION}" >/dev/null else - mksquashfs "${1}" "${sqimg}" -noappend + mksquashfs "${1}" "${sqimg}" -noappend -comp "${COMPRESSION}" fi minutes=$(echo $start $(date +%s) | awk '{ printf "%0.2f",($2-$1)/60 }') echo "Image creation done in $minutes minutes." -- 1.7.3.1
Am 17.10.2010 21:22, schrieb Gerardo Exequiel Pozzi:
Add a note about supported status in Linux versions. Needs squashfs-tools-4.1 (now on extra).
Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
I have actually built squashfs-lzma images with a (very ugly) hacked archiso today, so I appreciate this. Your option looks good, I'll look at it more thoroughly tomorrow though. It also seems like there is some messed up indentation (not in your patch, but around it). I guess you can put these patches on your github for me to pull. The aforementioned test images are here: http://alberich.archlinux.org/misc/testiso/ As for the "hacked" part: 1) I built kernel26-live with squashfs-lzma and aufs in the kernel (will become an [extra] package maybe?). 2) I removed tiacx and ndiswrapper as I didn't want to build any external modules for now (Can we drop them from the ISO?). 3) I patched syslinux-iso to pacman -Rn kernel26 (this is ugly, but I see no better way). 4) I hardcoded vmlinuz26-live everywhere (and vmlinuz26_live in syslinux.cfg, as level1 isofs does not know '-') - long-term, the package name should be kernel26_live so that the file name will be vmlinuz26_live. On another note, archisobasedir was broken (still is in the test images), and converting an ISO to run from a subfolder requires some sed-work. Maybe it would be easier to just have everything in the archlinux/ subfolder on the ISO, so that remastering onto another medium will be less messy (I copied the ISO to a FAT32 into an archlinux/ subfolder, adjusted archisolabel, archisobasedir, installed syslinux(FAT version) and changes some paths here and there - I now have an Arch system contained entirely in a subfolder on my USB).
On 10/17/2010 05:45 PM, Thomas Bächler wrote:
Am 17.10.2010 21:22, schrieb Gerardo Exequiel Pozzi:
Add a note about supported status in Linux versions. Needs squashfs-tools-4.1 (now on extra).
Signed-off-by: Gerardo Exequiel Pozzi<vmlinuz386@yahoo.com.ar> I have actually built squashfs-lzma images with a (very ugly) hacked archiso today, so I appreciate this. Your option looks good, I'll look at it more thoroughly tomorrow though. It also seems like there is some messed up indentation (not in your patch, but around it). I guess you can put these patches on your github for me to pull. Good, all these patches (compression support + archiso2dual -S change) are on my "experimental" branch.
http://github.com/djgera/archiso/compare/master...experimental
The aforementioned test images are here: http://alberich.archlinux.org/misc/testiso/
As for the "hacked" part: 1) I built kernel26-live with squashfs-lzma and aufs in the kernel (will become an [extra] package maybe?).
Sounds good. What patches are you using? Is not posible/easy to build only "sqfslzma" module? (plus a trivial patch for add lzma "as supported" in kernel26 package). (We have a party when we lzma + Val's writable overlays in Linux vanilla :P)
2) I removed tiacx and ndiswrapper as I didn't want to build any external modules for now (Can we drop them from the ISO?). I don't know I never used that. 3) I patched syslinux-iso to pacman -Rn kernel26 (this is ugly, but I see no better way). another workaround can be in Makefile
- mkarchiso -p base create $(WORKDIR) + mkarchiso -p $(shell pacman -Sgq base | grep -v ^kernel26$) create $(WORKDIR)
4) I hardcoded vmlinuz26-live everywhere (and vmlinuz26_live in syslinux.cfg, as level1 isofs does not know '-') - long-term, the package name should be kernel26_live so that the file name will be vmlinuz26_live. yes On another note, archisobasedir was broken (still is in the test images), and converting an ISO to run from a subfolder requires some sed-work. Maybe it would be easier to just have everything in the archlinux/ subfolder on the ISO, so that remastering onto another medium will be less messy (I copied the ISO to a FAT32 into an archlinux/ subfolder, adjusted archisolabel, archisobasedir, installed syslinux(FAT version) and changes some paths here and there - I now have an Arch system contained entirely in a subfolder on my USB).
Yes I want this, seems that other people too :) In these days I am busy, but I can experiment on this in some days. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
Am 17.10.2010 23:55, schrieb Gerardo Exequiel Pozzi:
The aforementioned test images are here: http://alberich.archlinux.org/misc/testiso/
As for the "hacked" part: 1) I built kernel26-live with squashfs-lzma and aufs in the kernel (will become an [extra] package maybe?). Sounds good. What patches are you using? Is not posible/easy to build only "sqfslzma" module? (plus a trivial patch for add lzma "as supported" in kernel26 package).
No, the part that was rejected by Linus was making the lzma decompressor available to non-init code. The changes to the squashfs module are rather small. http://git.kernel.org/?p=linux/kernel/git/pkl/squashfs-lzma.git;a=summary The last 6 patches can be cleanly rebased upon 2.6.35.7, that's what I use.
(We have a party when we lzma + Val's writable overlays in Linux vanilla :P)
We can try porting archiso to union-mounts soon and see how that works out.
2) I removed tiacx and ndiswrapper as I didn't want to build any external modules for now (Can we drop them from the ISO?). I don't know I never used that.
The tiacx has no future, and ndiswrapper is almost dead these days.
3) I patched syslinux-iso to pacman -Rn kernel26 (this is ugly, but I see no better way). another workaround can be in Makefile
- mkarchiso -p base create $(WORKDIR) + mkarchiso -p $(shell pacman -Sgq base | grep -v ^kernel26$) create $(WORKDIR)
If we do not insist on using the base group, why not?
On another note, archisobasedir was broken (still is in the test images), and converting an ISO to run from a subfolder requires some sed-work. Maybe it would be easier to just have everything in the archlinux/ subfolder on the ISO, so that remastering onto another medium will be less messy (I copied the ISO to a FAT32 into an archlinux/ subfolder, adjusted archisolabel, archisobasedir, installed syslinux(FAT version) and changes some paths here and there - I now have an Arch system contained entirely in a subfolder on my USB).
Yes I want this, seems that other people too :) In these days I am busy, but I can experiment on this in some days.
Then the easiest thing to do is move all files to archlinux/ (including isomounts) and set archisobasedir=archlinux/.
On 10/17/2010 07:12 PM, Thomas Bächler wrote:
Am 17.10.2010 23:55, schrieb Gerardo Exequiel Pozzi:
The aforementioned test images are here: http://alberich.archlinux.org/misc/testiso/
As for the "hacked" part: 1) I built kernel26-live with squashfs-lzma and aufs in the kernel (will become an [extra] package maybe?). Sounds good. What patches are you using? Is not posible/easy to build only "sqfslzma" module? (plus a trivial patch for add lzma "as supported" in kernel26 package). No, the part that was rejected by Linus was making the lzma decompressor available to non-init code. The changes to the squashfs module are rather small.
http://git.kernel.org/?p=linux/kernel/git/pkl/squashfs-lzma.git;a=summary The last 6 patches can be cleanly rebased upon 2.6.35.7, that's what I use. OK.
(We have a party when we lzma + Val's writable overlays in Linux vanilla :P) We can try porting archiso to union-mounts soon and see how that works out. Interesting. I never experimented with this, only read the documentation. We need a patched util-linux-ng. (I guess the patch for e2fsprogs is not needed because writable branch will be tmpfs in our case).
2) I removed tiacx and ndiswrapper as I didn't want to build any external modules for now (Can we drop them from the ISO?). I don't know I never used that. The tiacx has no future, and ndiswrapper is almost dead these days. OK. 3) I patched syslinux-iso to pacman -Rn kernel26 (this is ugly, but I see no better way). another workaround can be in Makefile
- mkarchiso -p base create $(WORKDIR) + mkarchiso -p $(shell pacman -Sgq base | grep -v ^kernel26$) create $(WORKDIR) If we do not insist on using the base group, why not? Sorry, I did not understand this. Could you put it another way?
Are you saying that do not "force" in install all the base packages, only a selection?
On another note, archisobasedir was broken (still is in the test images), and converting an ISO to run from a subfolder requires some sed-work. Maybe it would be easier to just have everything in the archlinux/ subfolder on the ISO, so that remastering onto another medium will be less messy (I copied the ISO to a FAT32 into an archlinux/ subfolder, adjusted archisolabel, archisobasedir, installed syslinux(FAT version) and changes some paths here and there - I now have an Arch system contained entirely in a subfolder on my USB).
Yes I want this, seems that other people too :) In these days I am busy, but I can experiment on this in some days. Then the easiest thing to do is move all files to archlinux/ (including isomounts) and set archisobasedir=archlinux/.
So the medium, by default created by archiso will look like: / /boot/ /archlinux/ isomounts *.sqfs and by archiso2dual: / /boot/ /archlinux/ isomounts* /archlinux/any/ *.sqfs /archlinux/i686/ *.sqfs /archlinux/x86_64/ *.sqfs OK? -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
Am 18.10.2010 00:48, schrieb Gerardo Exequiel Pozzi:
We can try porting archiso to union-mounts soon and see how that works out. Interesting. I never experimented with this, only read the documentation. We need a patched util-linux-ng. (I guess the patch for e2fsprogs is not needed because writable branch will be tmpfs in our case).
One reason not to do it until it is accepted upstream.
another workaround can be in Makefile
- mkarchiso -p base create $(WORKDIR) + mkarchiso -p $(shell pacman -Sgq base | grep -v ^kernel26$) create $(WORKDIR) If we do not insist on using the base group, why not? Sorry, I did not understand this. Could you put it another way?
Are you saying that do not "force" in install all the base packages, only a selection?
There shouldn't be a difference, it's just more code to do this instead of installing base.
Then the easiest thing to do is move all files to archlinux/ (including isomounts) and set archisobasedir=archlinux/.
So the medium, by default created by archiso will look like:
/ /boot/ /archlinux/ isomounts *.sqfs
and by archiso2dual:
/ /boot/ /archlinux/ isomounts* /archlinux/any/ *.sqfs /archlinux/i686/ *.sqfs /archlinux/x86_64/ *.sqfs
No, /boot moves to /archlinux/boot as well. The only directory in the root of the file system would be /archlinux.
- mkarchiso -p base create $(WORKDIR) + mkarchiso -p $(shell pacman -Sgq base | grep -v ^kernel26$) create $(WORKDIR) If we do not insist on using the base group, why not? Sorry, I did not understand this. Could you put it another way?
Are you saying that do not "force" in install all the base packages, only a selection?
There shouldn't be a difference, it's just more code to do this instead of installing base. I want the form of difference "base" - "noinstall". Is easy way to
On 10/17/2010 07:53 PM, Thomas Bächler wrote: maintain, since there is no need to add/remove packages to the list when there is a change in base group. For example: BASE=$(comm -2 -3 <(pacman -Sgq base | sort) <(for x in $NOINST;do echo $x;done | sort))
Then the easiest thing to do is move all files to archlinux/ (including isomounts) and set archisobasedir=archlinux/.
So the medium, by default created by archiso will look like:
/ /boot/ /archlinux/ isomounts *.sqfs
and by archiso2dual:
/ /boot/ /archlinux/ isomounts* /archlinux/any/ *.sqfs /archlinux/i686/ *.sqfs /archlinux/x86_64/ *.sqfs No, /boot moves to /archlinux/boot as well. The only directory in the root of the file system would be /archlinux.
OK, Of course! I was forgetting that at the time of the creation of the iso, you specify the path of the syslinux, hehe :) -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
On 10/17/2010 08:07 PM, Gerardo Exequiel Pozzi wrote:
Then the easiest thing to do is move all files to archlinux/ (including
isomounts) and set archisobasedir=archlinux/.
So the medium, by default created by archiso will look like:
/ /boot/ /archlinux/ isomounts *.sqfs
and by archiso2dual:
/ /boot/ /archlinux/ isomounts* /archlinux/any/ *.sqfs /archlinux/i686/ *.sqfs /archlinux/x86_64/ *.sqfs No, /boot moves to /archlinux/boot as well. The only directory in the root of the file system would be /archlinux.
OK, Of course! I was forgetting that at the time of the creation of the iso, you specify the path of the syslinux, hehe :)
archlinux has 9 chars, iso9660 level 1 is limited to 8.3, sugestions? arch archiso My Arch Linux Booteable Medium Made By ArchISO :P -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
Am Sun, 17 Oct 2010 20:18:41 -0300 schrieb Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>:
archlinux has 9 chars, iso9660 level 1 is limited to 8.3, sugestions?
arch archiso
archlnx Heiko
Am 18.10.2010 01:18, schrieb Gerardo Exequiel Pozzi:
No, /boot moves to /archlinux/boot as well. The only directory in the root of the file system would be /archlinux.
OK, Of course! I was forgetting that at the time of the creation of the iso, you specify the path of the syslinux, hehe :)
archlinux has 9 chars, iso9660 level 1 is limited to 8.3, sugestions?
arch archiso My Arch Linux Booteable Medium Made By ArchISO :P
Oops - I just did it on vfat. I'd prefer arch/.
On 10/17/2010 08:43 PM, Thomas Bächler wrote:
Am 18.10.2010 01:18, schrieb Gerardo Exequiel Pozzi:
No, /boot moves to /archlinux/boot as well. The only directory in the root of the file system would be /archlinux.
OK, Of course! I was forgetting that at the time of the creation of the iso, you specify the path of the syslinux, hehe :)
archlinux has 9 chars, iso9660 level 1 is limited to 8.3, sugestions?
arch archiso My Arch Linux Booteable Medium Made By ArchISO :P Oops - I just did it on vfat. I'd prefer arch/.
I made changes to mkarchiso and syslinux-iso/Makefile but... does not work (config file not found) Seems that you only played with extlinux, because isolinux.... 72 ++++ NOTE ON THE CONFIG FILE DIRECTORY ++++ 73 74 ISOLINUX will search for the config file directory in the order 75 /boot/isolinux, /isolinux, /. The first directory that exists is 76 used, even if it contains no files. Therefore, please make sure that 77 these directories don't exist if you don't want ISOLINUX to use them. And this documentation is up to date acording to the code http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=core/fs/iso9660... isofs still uses this custom method instead of generic for syslinux/extlinux http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=core/fs/lib/loa... -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
On 10/17/2010 09:41 PM, Gerardo Exequiel Pozzi wrote:
On 10/17/2010 08:43 PM, Thomas Bächler wrote:
Am 18.10.2010 01:18, schrieb Gerardo Exequiel Pozzi:
No, /boot moves to /archlinux/boot as well. The only directory in the root of the file system would be /archlinux.
OK, Of course! I was forgetting that at the time of the creation of the iso, you specify the path of the syslinux, hehe :)
archlinux has 9 chars, iso9660 level 1 is limited to 8.3, sugestions?
arch archiso My Arch Linux Booteable Medium Made By ArchISO :P Oops - I just did it on vfat. I'd prefer arch/.
I made changes to mkarchiso and syslinux-iso/Makefile but... does not work (config file not found)
Seems that you only played with extlinux, because isolinux....
72 ++++ NOTE ON THE CONFIG FILE DIRECTORY ++++ 73 74 ISOLINUX will search for the config file directory in the order 75 /boot/isolinux, /isolinux, /. The first directory that exists is 76 used, even if it contains no files. Therefore, please make sure that 77 these directories don't exist if you don't want ISOLINUX to use them.
And this documentation is up to date acording to the code http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=core/fs/iso9660...
I missed "not" word, anyway does not work.
isofs still uses this custom method instead of generic for syslinux/extlinux http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=core/fs/lib/loa...
I think we have two or three options, please make a choice (I currently working now on this) /boot (place like now kernel+memtest+syslinux here) /archlinux OR /boot/syslinux (place only syslinux files here) /archlinux /archlinux/boot (place kernel+memtest) OR /syslinux (place only syslinux files here) /archlinux /archlinux/boot (place kernel+memtest) -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
On 10/17/2010 10:05 PM, Gerardo Exequiel Pozzi wrote:
On 10/17/2010 09:41 PM, Gerardo Exequiel Pozzi wrote:
On 10/17/2010 08:43 PM, Thomas Bächler wrote:
Am 18.10.2010 01:18, schrieb Gerardo Exequiel Pozzi:
No, /boot moves to /archlinux/boot as well. The only directory in the root of the file system would be /archlinux.
OK, Of course! I was forgetting that at the time of the creation of the iso, you specify the path of the syslinux, hehe :)
archlinux has 9 chars, iso9660 level 1 is limited to 8.3, sugestions?
arch archiso My Arch Linux Booteable Medium Made By ArchISO :P Oops - I just did it on vfat. I'd prefer arch/.
I made changes to mkarchiso and syslinux-iso/Makefile but... does not work (config file not found)
Seems that you only played with extlinux, because isolinux....
72 ++++ NOTE ON THE CONFIG FILE DIRECTORY ++++ 73 74 ISOLINUX will search for the config file directory in the order 75 /boot/isolinux, /isolinux, /. The first directory that exists is 76 used, even if it contains no files. Therefore, please make sure that 77 these directories don't exist if you don't want ISOLINUX to use them.
And this documentation is up to date acording to the code http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=core/fs/iso9660...
I missed "not" word, anyway does not work.
isofs still uses this custom method instead of generic for syslinux/extlinux http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=core/fs/lib/loa...
I think we have two or three options, please make a choice (I currently working now on this)
/boot (place like now kernel+memtest+syslinux here) /archlinux
OR
/boot/syslinux (place only syslinux files here) /archlinux /archlinux/boot (place kernel+memtest)
OR /syslinux (place only syslinux files here) /archlinux /archlinux/boot (place kernel+memtest)
brb archlinux -> arch of course, just a typo here :) -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
On 10/17/2010 08:22 PM, Heiko Baums wrote:
Am Sun, 17 Oct 2010 20:18:41 -0300 schrieb Gerardo Exequiel Pozzi<vmlinuz386@yahoo.com.ar>:
archlinux has 9 chars, iso9660 level 1 is limited to 8.3, sugestions?
arch archiso archlnx
Heiko
arch wins! Don't worry I make this option configurable at make time via new -D <install_dir> parameter on mkarchiso. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
Am Sun, 17 Oct 2010 22:10:24 -0300 schrieb Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>:
arch wins!
Don't worry I make this option configurable at make time via new -D <install_dir> parameter on mkarchiso.
I don't worry. I just gave you my suggestion, because you asked for it. ;-) I can live very well with arch. :-) Heiko
On 10/17/2010 10:05 PM, Gerardo Exequiel Pozzi wrote:
On 10/17/2010 09:41 PM, Gerardo Exequiel Pozzi wrote:
On 10/17/2010 08:43 PM, Thomas Bächler wrote:
Am 18.10.2010 01:18, schrieb Gerardo Exequiel Pozzi:
No, /boot moves to /archlinux/boot as well. The only directory in the root of the file system would be /archlinux.
OK, Of course! I was forgetting that at the time of the creation of the iso, you specify the path of the syslinux, hehe :)
archlinux has 9 chars, iso9660 level 1 is limited to 8.3, sugestions?
arch archiso My Arch Linux Booteable Medium Made By ArchISO :P Oops - I just did it on vfat. I'd prefer arch/.
I made changes to mkarchiso and syslinux-iso/Makefile but... does not work (config file not found)
Seems that you only played with extlinux, because isolinux....
72 ++++ NOTE ON THE CONFIG FILE DIRECTORY ++++ 73 74 ISOLINUX will search for the config file directory in the order 75 /boot/isolinux, /isolinux, /. The first directory that exists is 76 used, even if it contains no files. Therefore, please make sure that 77 these directories don't exist if you don't want ISOLINUX to use them.
And this documentation is up to date acording to the code http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=core/fs/iso9660...
I missed "not" word, anyway does not work.
isofs still uses this custom method instead of generic for syslinux/extlinux http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=core/fs/lib/loa...
I think we have two or three options, please make a choice (I currently working now on this)
/boot (place like now kernel+memtest+syslinux here) /archlinux
OR
/boot/syslinux (place only syslinux files here) /archlinux /archlinux/boot (place kernel+memtest)
OR /syslinux (place only syslinux files here) /archlinux /archlinux/boot (place kernel+memtest)
I take the last option, I think is the best, for example if you want to use another boot manager, just only copy "arch" directory. The work is done for RFC, in my install_dir branch [#1][#2]. Also I removed two things that I always dislike: isomounts generated by mkarchiso and README. Please let me know if re-add it. This how media looks [#3]. Tested and works fine. TODO: update archiso2dual, when this become accepted. [#1] http://github.com/djgera/archiso/tree/install_dir [#2] http://github.com/djgera/archiso/compare/experimental...install_dir [#3] http://djgera.pastebin.com/7Ttc5Crq -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
Am 18.10.2010 02:41, schrieb Gerardo Exequiel Pozzi:
I made changes to mkarchiso and syslinux-iso/Makefile but... does not work (config file not found)
Seems that you only played with extlinux, because isolinux....
72 ++++ NOTE ON THE CONFIG FILE DIRECTORY ++++ 73 74 ISOLINUX will search for the config file directory in the order 75 /boot/isolinux, /isolinux, /. The first directory that exists is 76 used, even if it contains no files. Therefore, please make sure that 77 these directories don't exist if you don't want ISOLINUX to use them.
And this documentation is up to date acording to the code http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=core/fs/iso9660...
Oh, I thought isolinux can also use the same folder as the bootloader resides in. The idea was to be able to just copy the arch/ folder to a USB and install syslinux on it, without modifying configuration files (beyond adjusting the label. Right now, you need to change syslinux.cfg massively). Using a subfolder would be nice for the Arch media to coexist with other programs on the USB. If we have to keep /boot or /syslinux, then you'll loose this. Does ISO Level 1 support something equivalent to symlinks?
On 10/18/2010 05:32 AM, Thomas Bächler wrote:
Am 18.10.2010 02:41, schrieb Gerardo Exequiel Pozzi:
I made changes to mkarchiso and syslinux-iso/Makefile but... does not work (config file not found)
Seems that you only played with extlinux, because isolinux....
72 ++++ NOTE ON THE CONFIG FILE DIRECTORY ++++ 73 74 ISOLINUX will search for the config file directory in the order 75 /boot/isolinux, /isolinux, /. The first directory that exists is 76 used, even if it contains no files. Therefore, please make sure that 77 these directories don't exist if you don't want ISOLINUX to use them.
And this documentation is up to date acording to the code http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob;f=core/fs/iso9660... Oh, I thought isolinux can also use the same folder as the bootloader resides in.
The idea was to be able to just copy the arch/ folder to a USB and install syslinux on it, without modifying configuration files (beyond adjusting the label. Right now, you need to change syslinux.cfg massively). Using a subfolder would be nice for the Arch media to coexist with other programs on the USB. If we have to keep /boot or /syslinux, then you'll loose this. Does ISO Level 1 support something equivalent to symlinks?
Yes I understand the advantage, not only for just that purpose, since can be used to put multiple versions. No, there is nothing equivalent to "multiple names for same object". Anyway if you normally put these files on VFAT is the same... What about my work on install_dir[#1] branch(*)? I think that is still useful. / /syslinux (place only syslinux files here) /arch /arch/boot (place kernel+memtest) Another thing (I think about this in the past when I make the archiso2dual script): What do you think about this modification in mkarchiso: "a bit ready for simple merge" / /syslinux (place only syslinux files here) /arch/${arch} /arch/boot/${arch} [#1] http://github.com/djgera/archiso/compare/experimental...install_dir (*) experimental and install_dir are rebased to the recent master changes. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
On Sun, 17 Oct 2010 22:10:24 -0300 Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> wrote:
On 10/17/2010 08:22 PM, Heiko Baums wrote:
Am Sun, 17 Oct 2010 20:18:41 -0300 schrieb Gerardo Exequiel Pozzi<vmlinuz386@yahoo.com.ar>:
archlinux has 9 chars, iso9660 level 1 is limited to 8.3, sugestions?
arch archiso archlnx
Heiko
arch wins!
Don't worry I make this option configurable at make time via new -D <install_dir> parameter on mkarchiso.
Why should it be configurable? it's just the name of the directory containing the files, right? I would say convention over configuration, unless I'm missing something. Dieter
On 10/19/2010 04:40 AM, Dieter Plaetinck wrote:
On Sun, 17 Oct 2010 22:10:24 -0300 Gerardo Exequiel Pozzi<vmlinuz386@yahoo.com.ar> wrote:
On 10/17/2010 08:22 PM, Heiko Baums wrote:
Am Sun, 17 Oct 2010 20:18:41 -0300 schrieb Gerardo Exequiel Pozzi<vmlinuz386@yahoo.com.ar>:
archlinux has 9 chars, iso9660 level 1 is limited to 8.3, sugestions?
arch archiso archlnx
Heiko
arch wins!
Don't worry I make this option configurable at make time via new -D <install_dir> parameter on mkarchiso.
Why should it be configurable? it's just the name of the directory containing the files, right? I would say convention over configuration, unless I'm missing something.
Dieter
For official isos its OK to have this fixed, like for publisher/application. But mkarchiso is not limited to official media. So If I want to make an .iso with multiple versions on it, this is at least, one way to leave things easy. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
participants (4)
-
Dieter Plaetinck
-
Gerardo Exequiel Pozzi
-
Heiko Baums
-
Thomas Bächler