On 06/14/2011 01:51 AM, Gerardo Exequiel Pozzi wrote:

Make releng images / how to build:

pacman -S devtools --noconfirm --needed mkarchroot /tmp/pichicho base mkarchroot -r bash /tmp/pichicho

mknod /dev/loop0 b 7 0 # or any available ;)

echo 'Server = ftp://192.168.0.66/archlinux/$repo/os/$arch' >> /etc/pacman.d/mirrorlist #your mirror! pacman -S make git squashfs-tools syslinux devtools cdrkit mkinitcpio-nfs-utils nbd --noconfirm --needed cd /tmp git clone git://github.com/djgera/archiso.git -b dm-snapshot cd archiso/archiso make install cd ../configs/releng/ ./build.sh all_iso #or net_iso | core_iso Enjoy!

-- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

Am 14.06.2011 06:51, schrieb Gerardo Exequiel Pozzi:

While in the union mount approach, if "tmpfs" (rw_branch) is full a ENOSPC is reported, and nothing more. In this case, if in the device where the "cow" file reside is full, and you write to the dev-mapper, the system will crash, no ENOSPC is reported. OK?

When a snapshot device becomes full, it "disappears". This means that reading and writing will fail (probably with EACCESS). As reading fails, your system crashes.

* Directory scheme or core-iso.

??? arch ? ??? aitab ? ??? any ? ? ??? core-any-pkgs.sfs ? ? ??? usr-share.fs.sfs ? ??? boot ? ? ??? i686 ? ? ? ??? archiso.img ? ? ? ??? vmlinuz26 ? ? ??? memtest ? ? ??? memtest.COPYING ? ??? i686 ? ??? core-pkgs.sfs ? ??? lib-modules.fs.sfs ? ??? root-image.fs.sfs ??? syslinux ??? boot.cat ??? *.com ??? *.c32 ??? *.0 ??? hdt ? ??? modalias.gz ? ??? pciids.gz ??? isolinux.bin ??? memdisk ??? splash.png ??? syslinux.cfg

I sent you incomplete work to move everything to /arch once. I want to include this, but never had the time to finish it. Basically, everything is moved to /arch/boot/syslinux instead of /syslinux. The /syslinux folder would only contain boot.cat, isolinux.bin and a small syslinux.cfg, that only launches CONFIG /arch/boot/syslinux/syslinux.cfg APPEND /arch/boot/syslinux/ This 'cd's to /arch/boot/syslinux. This will make it easier to produce scripts that create a live USB by copying /arch to a flash drive, as /arch is self-contained and no config files need to be adjusted. Just copy /arch, adjust archisolabel and install syslinux into /arch/boot/syslinux/. If you have any more time for this, I would appreciate if you would take the work out of my hands.

Am 14.06.2011 11:14, schrieb Dieter Plaetinck:

On Tue, 14 Jun 2011 01:51:00 -0300 Gerardo Exequiel Pozzi wrote:

...

First, aufs2 is not used anymore. The new approach is using device mapper with a snapshot feature, it has some advantages and disadvantages.

can you list the advantages and disadvantages? I mean, from a topdown end-user perspective..

Advantage: Snapshotting is supported and works with all kernels, aufs does not work with 2.6.39 and is not officially supported. Disadvantage: More memory needed - the read-write overlay is now block-based instead of file-based.

On 06/14/2011 05:39 AM, Thomas Bächler wrote:

Am 14.06.2011 06:51, schrieb Gerardo Exequiel Pozzi:

...

While in the union mount approach, if "tmpfs" (rw_branch) is full a ENOSPC is reported, and nothing more. In this case, if in the device where the "cow" file reside is full, and you write to the dev-mapper, the system will crash, no ENOSPC is reported. OK? When a snapshot device becomes full, it "disappears". This means that reading and writing will fail (probably with EACCESS). As reading fails, your system crashes.

...

* Directory scheme or core-iso.

??? arch ? ??? aitab ? ??? any ? ? ??? core-any-pkgs.sfs ? ? ??? usr-share.fs.sfs ? ??? boot ? ? ??? i686 ? ? ? ??? archiso.img ? ? ? ??? vmlinuz26 ? ? ??? memtest ? ? ??? memtest.COPYING ? ??? i686 ? ??? core-pkgs.sfs ? ??? lib-modules.fs.sfs ? ??? root-image.fs.sfs ??? syslinux ??? boot.cat ??? *.com ??? *.c32 ??? *.0 ??? hdt ? ??? modalias.gz ? ??? pciids.gz ??? isolinux.bin ??? memdisk ??? splash.png ??? syslinux.cfg I sent you incomplete work to move everything to /arch once. I want to include this, but never had the time to finish it.

Basically, everything is moved to /arch/boot/syslinux instead of /syslinux. The /syslinux folder would only contain boot.cat, isolinux.bin and a small syslinux.cfg, that only launches

CONFIG /arch/boot/syslinux/syslinux.cfg APPEND /arch/boot/syslinux/

This 'cd's to /arch/boot/syslinux. This will make it easier to produce scripts that create a live USB by copying /arch to a flash drive, as /arch is self-contained and no config files need to be adjusted. Just copy /arch, adjust archisolabel and install syslinux into /arch/boot/syslinux/.

If you have any more time for this, I would appreciate if you would take the work out of my hands.

I know about it, but if you insist I will do it, no problem. I personally dislike the idea, since it is currently divided in a certain logical form(ArchLinux in one place, Syslinux in another), and serves the time to put several "Linux's" on the same storage medium, sharing the same bootloader -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

Am 14.06.2011 17:12, schrieb Gerardo Exequiel Pozzi:

I know about it, but if you insist I will do it, no problem.

I personally dislike the idea, since it is currently divided in a certain logical form(ArchLinux in one place, Syslinux in another), and serves the time to put several "Linux's" on the same storage medium, sharing the same bootloader

I want to eventually be able to copy just the 'arch' folder onto another medium, install syslinux and use the arch live environment without modifications. Currently, this is messy, and it will only get better if we get the syslinux stuff into /arch. We can discuss this further if you like, which use cases do you know for this separation?

Am 15.06.2011 02:49, schrieb Gerardo Exequiel Pozzi:

On 06/14/2011 02:21 PM, Thomas Bächler wrote:

...

Am 14.06.2011 17:12, schrieb Gerardo Exequiel Pozzi:

...

I know about it, but if you insist I will do it, no problem.

I personally dislike the idea, since it is currently divided in a certain logical form(ArchLinux in one place, Syslinux in another), and serves the time to put several "Linux's" on the same storage medium, sharing the same bootloader I want to eventually be able to copy just the 'arch' folder onto another medium, install syslinux and use the arch live environment without modifications.

Currently, this is messy, and it will only get better if we get the syslinux stuff into /arch.

We can discuss this further if you like, which use cases do you know for this separation?

OK, done it. Since this is specific to isolinux component of syslinux. I pushed it on /isolinux ;)

/mnt/ ├── arch │ ├── aitab │ ├── any │ │ ├── core-any-pkgs.sfs │ │ └── usr-share.fs.sfs │ ├── boot │ │ ├── i686 │ │ │ ├── archiso.img │ │ │ └── vmlinuz26 │ │ ├── memtest │ │ ├── memtest.COPYING │ │ └── syslinux │ │ ├── *.0 │ │ ├── *.c32 │ │ ├── *.com │ │ ├── hdt │ │ │ ├── modalias.gz │ │ │ └── pciids.gz │ │ ├── memdisk │ │ ├── splash.png │ │ └── syslinux.cfg │ └── i686 │ ├── core-pkgs.sfs │ ├── lib-modules.fs.sfs │ └── root-image.fs.sfs └── isolinux ├── boot.cat ├── isolinux.bin └── isolinux.cfg

OK?

Do you have test builds somewhere (one image is enough, like net-i686)?

Am 15.06.2011 23:54, schrieb Gerardo Exequiel Pozzi:

...

Do you have test builds somewhere (one image is enough, like net-i686)?

My upstream is really poor, I can upload if you want, it will take about of 11 hours or more for ~195M :s

I'll need to set up a build environment then, whenever I get to it.

On Sat, 18 Jun 2011 03:03:01 -0300 Gerardo Exequiel Pozzi wrote:

On 06/14/2011 01:51 AM, Gerardo Exequiel Pozzi wrote:

...

Hello all

I want to know opinions about my recent work to archiso, since there are lots of changes. If someone can do some tests, they are very welcomed. Sugestions are very appreciated. Thanks :)

Basic documentation, done Comments in code, done. Testing all builds, done. Booting all builds, done.

Untested: archiso_pxe_nbd, and archiso_loop_mnt.

If there are no objections, I will merge dm-snapshot branch in official master branch in about 12 hours.

commit msg is:

[archiso] Use dm-snapshot instead of aufs2 (A.K.A. "The Big Commit")

* Use device mapper + snapshot module, instead union layer filesystem. * A block-level approach vs vfs-level. * No more unofficial (Linux) things. * More memory is needed. * Refactor mkarchiso. * Refactor hooks/archiso. * New configs/releng to build official images. * Removed configs/syslinux-iso. * Removed archiso2dual script. Now functionallity integrated in configs/releng. * New configs/baseline to build the most basic live medium or use as template. * New README file.

try to keep the commit message current tense. i.e: s/Removed/Remove/ s/Now functionality integrated/Integrate functionality/ Maybe add something like: * Replace limited Makefile with new build.sh script And btw, I'm not sure 'releng' is a good name for the default configs, 'releng' is the name of the team doing the work and releasing images, but doesn't really describe the images which will be generated. I think something like 'installation-images' or 'official-images' or 'official-installation-images' or something would be better (the last one has my preference) Dieter