June 2011 - Arch-releng - lists.archlinux.org

[arch-releng] [RFC] [PATCH] [archiso] README update
by Gerardo Exequiel Pozzi 22 Jun '11

22 Jun '11

[RFC]: Please review english grammar. Thanks. * Added boot parameters. * Reorder and clarify build steps. Signed-off-by: Gerardo Exequiel Pozzi <vmlinuz386(a)yahoo.com.ar> --- README | 196 ++++++++++++++++++++++++++++++++++++++++++++-------------------- 1 files changed, 136 insertions(+), 60 deletions(-) diff --git a/README b/README index dee3a50..7743018 100644 --- a/README +++ b/README @@ -1,6 +1,12 @@ INDEX ----- +* Boot parameters (initramfs stage) + * hooks/archiso + * hooks/archiso_pxe_nbd + * hooks/archiso_loop_mnt +* Boot parameters (only for configs/releng) + * etc/rc.conf * Image types generated by mkarchiso. * File format for aitab. * Why the /isolinux and /arch/boot/syslinux directories? @@ -9,6 +15,78 @@ INDEX +*** Boot parameters (initramfs stage) + +** hooks/archiso + +* archisolabel= Set the filesystem label where archiso files reside. + Default: (unset) +* archisodevice= Set the device node where archiso medium is located. + Default: "/dev/disk/by-label/${archisolabel}" +* archisobasedir= Set the base directory where all files reside. + Default: "arch" +* aitab= Set the path for "aitab" file. + Default: ${archisobasedir}/aitab +* copytoram= If set to "y" or just "copytoram" without arguments, + all SquashFS are copied to "RAM". + Default: (unset) +* cowspace_size= Set the size of tmpfs /cowspace. This space is used for + Copy-On-Write files of dm-snapshot. + (directory not visible outside initramfs) + Size is in bytes (suffix with "k", "m" and "g") or + in percentage of available RAM. + Default: "75%" +* copytoram_size= Set the size of tmpfs /cowpytoram. This space is used for + copy of all SquashFS images used, if copytoram=y. + (directory not visible outside initramfs) + Size is in bytes (suffix with "k", "m" and "g") or + in percentage of available RAM. + Default: "75%" +* arch= Force an architecture type (i686 | x86_64). + Do not set it for normal operations. + Useful for running a 64 bit kernel / 32 bit userspace. + Default: (architecture of running kernel) + + +** hooks/archiso_pxe_nbd + +* ip= This parameter is setup automatically by PXELINUX + when option "IPAPPEND" is set to 1 or 2 in config. + ip=<client-ip>:<boot-server-ip>:<gw-ip>:<netmask> + Default: (set via PXE server) +* BOOTIF= This parameter is setup automatically by PXELINUX + when option "IPAPPEND" is set to 2 or 3 in config. + BOOTIF=<hardware-address-of-boot-interface> + Default: (set via PXELINUX) + + +** hooks/archiso_loop_mnt + +* img_dev= Device where archiso-image.iso reside. + Default: (unset) +* img_loop= Full path where archiso-image.iso is located on ${img_dev} + Default: (unset) + + + +*** Boot parameters (only for configs/releng) + +** /etc/rc.conf + +By default these parameters are set by default to these values +if nothing is specified on command line. + +locale= "en_US.UTF-8" +daemon_locale= "no" +hardwareclock= "UTC" +timezone= "Canada/Pacific" +keymap= "us" +consolefont= (unset) +consolemap= (unset) +usecolor= "yes" + + + *** Image types generated by mkarchiso. * image-name.sfs SquashFS image with all files directly on it. @@ -60,35 +138,34 @@ When make your custom boot-pendrive, you need to copy /arch directory to it. *** Building the most basic Arch Linux live media. (configs/baseline) -* First install devtools if needed, mkarchroot needs it. - [host] # pacman -S devtools +* Install devtools if needed, mkarchroot needs it + [host] # pacman -S devtools --needed -* Create a chroot to work on it. +* Create a base chroot to work on it. (prefix with linux32 if you want to build a 32 bits enviroment under 64 bits) [host] # mkarchroot /tmp/chroot base -* Enter it. (prefix with linux32 if needed). +* Install archiso on chroot (needs git and make) + [host] # pacman -S git make --needed + [host] # git clone git://projects.archlinux.org/archiso.git + [host] # make -C archiso/archiso DESTDIR=/tmp/chroot install + +* Enter to chroot (prefix with linux32 if needed). [host] # mkarchroot -r bash /tmp/chroot * Create a loopback device. - (mkarchiso does not create it, use other number if not available) + (mkarchroot does not create it, use other number if not available) [chroot] # mknod /dev/loop0 b 7 0 * Setup a mirror. [chroot] # echo 'Server = MIRROR/archlinux/$repo/os/$arch' >> /etc/pacman.d/mirrorlist * Install aditional packages needed for mkarchiso. - (git is only needed to get a copy of archiso.git) - [chroot] # pacman -S git squashfs-tools syslinux devtools cdrkit make - -* Install archiso. - [chroot] # cd /tmp - [chroot] # git clone git://projects.archlinux.org/archiso.git - [chroot] # cd archiso/archiso - [chroot] # make install-program + [chroot] # pacman -S devtools squashfs-tools syslinux cdrkit * Build a basic iso. - [chroot] # cd /tmp/archiso/configs/baseline + [chroot] # cp -r /usr/share/archiso/configs/baseline /tmp + [chroot] # cd /tmp/baseline [chroot] # ./build.sh * Exit from chroot. @@ -105,52 +182,51 @@ Note: These steps should be done with 64 bits support. * Prepare a 32 bit chroot enviroment. -linux32 mkarchroot /tmp/chroot32 base -linux32 mkarchroot -r bash /tmp/chroot32 -echo 'Server = MIRROR/archlinux/$repo/os/$arch' >> /etc/pacman.d/mirrorlist -pacman -S squashfs-tools syslinux devtools cdrkit make mkinitcpio-nfs-utils nbd --noconfirm --needed -exit + [host64] # linux32 mkarchroot /tmp/chroot32 base + [host64] # linux32 mkarchroot -r bash /tmp/chroot32 + [chroot32] # echo 'Server = MIRROR/archlinux/$repo/os/$arch' >> /etc/pacman.d/mirrorlist + [chroot32] # pacman -S devtools squashfs-tools syslinux cdrkit mkinitcpio-nfs-utils nbd + [chroot32] # exit * Prepare a 64 bits chroot enviroment. -mkarchroot /tmp/chroot64 base -mkarchroot -r bash /tmp/chroot64 -echo 'Server = MIRROR/archlinux/$repo/os/$arch' >> /etc/pacman.d/mirrorlist -pacman -S squashfs-tools syslinux devtools cdrkit make mkinitcpio-nfs-utils nbd --noconfirm --needed -exit - -* Create a shared directory which archiso can access from both chroot enviroments. - -mkdir /tmp/shared -cd /tmp/shared -git clone git://github.com/djgera/archiso.git -b dm-snapshot -cd -mount --bind /tmp/shared /tmp/chroot32/tmp -mount --bind /tmp/shared /tmp/chroot64/tmp - -* Enter 32 bits chroot enviroment, install mkarchiso, - then build core and netinstall single images. - -linux32 mkarchroot -r bash /tmp/chroot32 -mknod /dev/loop1032 b 7 1032 -cd /tmp/archiso/archiso -make install-program -cd ../configs/releng/ -./build.sh all_iso_single - -* Enter 64 bits chroot enviroment, install mkarchiso, - then build core and netinstall single images. - -mkarchroot -r bash /tmp/chroot64 -mknod /dev/loop1064 b 7 1064 -cd /tmp/archiso/archiso -make install-program -cd ../configs/releng/ -./build.sh all_iso_single - -* Finally build core and netinstall dual images - from any of the chroot enviroments. (The final result is the same). - -mkarchroot -r bash /tmp/chroot64 -cd /tmp/archiso/configs/releng/ -./build.sh all_iso_dual + [host64] # mkarchroot /tmp/chroot64 base + [host64] # mkarchroot -r bash /tmp/chroot64 + [chroot64] # echo 'Server = MIRROR/archlinux/$repo/os/$arch' >> /etc/pacman.d/mirrorlist + [chroot64] # pacman -S devtools squashfs-tools syslinux cdrkit mkinitcpio-nfs-utils nbd + [chroot64] # exit + +* Install archiso on both chroots. + + [host64] # git clone git://github.com/djgera/archiso.git -b dm-snapshot + [host64] # make -C archiso/archiso DESTDIR=/tmp/chroot32 install + [host64] # make -C archiso/archiso DESTDIR=/tmp/chroot64 install + +* Create a shared /tmp directory between two chroots for working. + + [host64] # mkdir /tmp/shared + [host64] # chmod 1777 /tmp/shared + [host64] # mount --bind /tmp/shared /tmp/chroot32/tmp + [host64] # mount --bind /tmp/shared /tmp/chroot64/tmp + +* Enter 32 bits chroot enviroment then build core and netinstall single images. + + [chroot32] # linux32 mkarchroot -r bash /tmp/chroot32 + [chroot32] # mknod /dev/loop1032 b 7 1032 #assumed loop.max_part=0 (by default) + [chroot32] # cp -r /usr/share/archiso/configs/releng /tmp + [chroot32] # cd /tmp/releng + [chroot32] # ./build.sh all_iso_single + +* Enter 64 bits chroot enviroment then build core and netinstall single images. + + [chroot64] # mkarchroot -r bash /tmp/chroot64 + [chroot64] # mknod /dev/loop1064 b 7 1064 #assumed loop.max_part=0 (by default) + [chroot64] # cp -r /usr/share/archiso/configs/releng /tmp + [chroot64] # cd /tmp/releng + [chroot64] # ./build.sh all_iso_single + +* Build core and netinstall dual images from any of the chroot enviroments. + + [host64] mkarchroot -r bash /tmp/chroot64 + [chroot64] # cd /tmp/releng + [chroot64] # ./build.sh all_iso_dual -- 1.7.5.2

1 0

[arch-releng] dm-snapshot branch is now merged in official master branch.
by Gerardo Exequiel Pozzi 19 Jun '11

19 Jun '11

Hello @Dieter: Please ask if you need help for your helper scripts. @Sven: I fews days I will update the wiki. Please check the english grammar. Thanks. -------------- [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. * Fix install/archiso_pxe_nbd (due recent change in mkinitcpio-0.6.15 on checked_modules()/all_modules()) [Thanks Dave for the improved workaround] * New configs/releng to build official images. * Works with a Bash script instead of Makefile. (better control and easy to maintain) * Remove configs/syslinux-iso. * Remove archiso2dual script. Integrate functionality in configs/releng. * New configs/baseline to build the most basic live medium or use as template. * New README (draft). [Thanks Dieter for fixing english grammar] -------------- Good Luck. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

5 7

[arch-releng] Call for test: archiso with dm-snapshot
by Gerardo Exequiel Pozzi 18 Jun '11

18 Jun '11

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 :) TODO: details to current work and archiso2dual. https://github.com/djgera/archiso/tree/dm-snapshot (single commit) (sorry for the grammar, my english is poor) Some highlights: ----- First, aufs2 is not used anymore. The new approach is using device mapper with a snapshot feature, it has some advantages and disadvantages. Basically this is a filesystem image that is read-only associated to a loopback device and another file with an special format (copy on write[COW]) associated to another loopback device. From these two loop dev, a dev-mapper is created, that is writeable. ------ [images] There are three types of images: (*.sqfs renamed to a more standard *.sfs) a) *.sfs: Classic SquashFS compressed images. [no COW used] b) *.fs.sfs: SquashFS with only one file. This file is an image of some filesystem (ext4, ext3, ...). [COW is used] c) *.fs: A filesystem (ext4, ext3, ...) without compressing with SquashFS. Can be useful for doing some test... [COW is used] ------ [aitab] The "isomounts" file is now called "aitab", since a new format is used. #img mnt arch sfs_comp fs_type fs_size img = filename of the image _without_ the extension mnt = mount point of the image arch = architecture of the image (valid options: i686 | x86_64 | any) sfs_comp = SquashFS compression type of the image (valid options gzip | lzo | xz) or "none" if no SquashFS. fs_type = Filesystem of the image (valid options: ext4 | ext3 | ext2 | xfs) or "none" if no filesystem is used. COW mode is only if this is used. fs_size = Total size of the image (absolute value in MiB) or percent of amount of free space (aproximated) in the image (valid values from 1% to 99%). [Ignored if fs_type=none] Of course some options are invalid sfs_comp=none, fs_type=none -------- [initcpio] How archiso hook works now (resume): 1) mount boot device where all images reside 2) mount a tmpfs filesystem to store all cow images (/cowspace) 3) mount all images listed in "aitab" For *.sfs: * assing the image to a loop dev, and mount it. For *.fs.sfs: * assing the image to a loop dev, and mount it to /sfs/$image_name * assing the image inside (*.fs) to a loop dev (A) (ro) * create an empty and sparse file of the same size of the loop dev (A), in the /cowspace * assing that file to a loop dev (B) (rw) * create a dm-snapshot from both loop devs (A) and (B), and mount it to desired location For *.fs * Same as previous without the first step. Note: copytoram does not work with *.fs images (TODO low priority). ------ 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? ------- [mkarchiso] NOTE: need an available loop device. (warning when run on chroot created by mkarchroot, since it does not create any loopback device node) * set -e -u * _msg_info and _msg_error functions _show_config => better (more clear) info / error messages :) * Some command line options remove since become obsolete (squashfs compression type, home dir, force) * New command "prepare", make all needed images (except iso). * Filesystem (*.fs) are created with space used plus 10% more (take care (aproximated for most cases) of metadata). * All directories (future images) listed on aitab should exists (aitab is parsed instead of using find) ----------- [configs/releng] (was syslinux-iso) * The build now uses a bash script instead of Makefile, we can take a better control of the build process. * There is no more "overlay" concept like with union mounts, all changes now are merged at build time in root-image. * directory scheme is more "dual-iso" friendly.. * Warning: Do not build net_iso after core_iso! (TODO stop with error) * download-repo.sh discarded, this process is now done in the same build.sh script (can exclude packages listed on a file) * core-pkgs.sfs (mounted at /repo/pkg): core.db + core_$arch_packages + core_any_symlinks (relative ../any/ ) * core-any-pkgs.sfs (mounted at /repo/any): core_any_pkgs * Warning: neither /repo/pkg and /repo/any is writeable (previously /src/... was) * .iso sizes: 382M archlinux-2011.06.14-core-i686.iso 392M archlinux-2011.06.14-core-x86_64.iso 195M archlinux-2011.06.14-netinstall-i686.iso 200M archlinux-2011.06.14-netinstall-x86_64.iso * 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 ------------- [configs/baseline] * A minimal working profile as example, booteable, just to do tests or use as template for other projects, etc. 145M archlinux-2011.06.14-i686.iso ??? arch ? ??? aitab ? ??? boot ? ? ??? i686 ? ? ??? archiso.img ? ? ??? vmlinuz26 ? ??? i686 ? ??? root-image.fs.sfs ??? syslinux ??? boot.cat ??? isolinux.bin ??? menu.c32 ??? syslinux.cfg -------- Make releng images / how to build: pacman -S devtools --noconfirm --needed mkarchroot /tmp/pichicho base mkarchroot -r bash /tmp/pichicho 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

3 18

[arch-releng] Update needed to releng scripts
by Gerardo Exequiel Pozzi 17 Jun '11

17 Jun '11

Hello Dieter I want some coordination with you to merge my dm-snapshot branch in master (archiso) so you can change releng scripts. Detailed manually build steps are here [#1] If you need more info please let me know. Basically the changes are (from build view): ---- Single ISOs ---- * Deprecated configs/syslinux-iso in favour to configs/releng * configs/releng uses a bash script instead of make * Equivalence of commands is: make net-iso -> ./build.sh net_iso_single make core-iso -> ./build.sh core_iso_single make [all] -> ./build.sh all_iso_single make clean -> ./build.sh clean_single * Note: Like with previous method, after building "core", if you build "netinstall" you get a "core" iso called "netinstall". (TODO: I need to fix this in a easy way) * Important: inside the chroot you need one loopback device available (@1) ---- Dual ISOs ---- * Deprecated archiso2dual script in favour of configs/releng/build.sh * While archiso2dual use *.iso images, build.sh use the result of ./build.sh *_iso_single commands, in other words join ${work_dir}/${arch}/iso (via hardlinks). * No more profiles (single, split, full), since the work of profile "split" is now done for single images. * build.sh accept these commands for doing dual images. ./build.sh net_iso_dual ./build.sh core_iso_dual ./build.sh all_iso_dual ./build.sh clean_dual * These commands does not trigger the build of single images. You need to do it before. * No issues if execute first "core" then "netinstall" (I managed it in this case) * No loopback device is needed for this step. (@1) Create one, for example "mknod /dev/loop1032 b 7 1032" for 32 bit chroot and loop1064 for 64 bits (of course this will work only if loop module is loaded without any parameters that limit the number of loop devices or set number of partitions). [#1] https://wiki.archlinux.org/index.php/User:Djgera#archiso -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

2 2

[arch-releng] ArchWiki: merge Official and Beginners' Guides? (or change titles)
by Dario Giovannetti 16 Jun '11

16 Jun '11

This discussion was started in https://wiki.archlinux.org/index.php/Talk:Official_Arch_Linux_Install_Guide… What do you think of merging the Beginners' Guide and the Official Arch Linux Install Guide into a unified Installation Guide? In my opinion having 2 separate installation guides on the wiki only creates confusion for beginners who wonder why they are directed to an "unofficial" guide, and is of no help for experienced users. This gets reinforced by the fact that the Official Guide is rarely maintained, and almost if not all of its content is already duplicated in the Beginners' Guide. Also, wiki users tend to report bugs in the Official Guide in its talk page, instead of posting to the releng team. I would then link the guide in git from the new unified article. In alternative to all this, I'd propose to change the titles of the two guides to something like "Installation Tutorial" (or Guide) in place of the Beginners', and "Quick installation reference" (or Guide, or Notes) in place of the Official. Dario

5 10

[arch-releng] archiso2dual becoming obsolete?
by Gerardo Exequiel Pozzi 16 Jun '11

16 Jun '11

Hello, I will deprecate this tool. Since in few days with dm-snapshot (if become to master), the directory scheme for isos is "dual friendly". Instead of reworking archiso2dual I will push this feature integrated into "configs/releng/build.sh" avoiding some code duplication. My idea is build them directly from "${work_dir}/iso" instead of mounting isos, then do lots of tasks depending on profile selected and finally build dual-iso. So the workflow can be something like (under 64 bit): * 0) bind mount bind some directory so can be shared between two chroots (32 and 64). * 1) build 32 bits isos under chroot (work_dir will be work/i686) * 2) build 64 bits isos under chroot (work_dir will be work/x86_64) * 3) build dual isos in any chroot. (work_dir will be work/dual) opinions? -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

1 1

Re: [arch-releng] Iso tests
by Dieter Plaetinck 15 Jun '11

15 Jun '11

I fetched Tom's latest testresults branch, followed all instructions in the README - all steps executed fine with the exception of https://bugs.archlinux.org/task/23228 -, But when I go to http://127.0.0.1:8000/isotests/ I get: DatabaseError at /isotests/ no such column: isotests_test.architecture_id Request Method: GET Request URL: http://127.0.0.1:8000/isotests/ Django Version: 1.2.4 Exception Type: DatabaseError Exception Value: no such column: isotests_test.architecture_id here's some more output from during the setup part: (archweb-env)17:54:44 dieter@ws archweb testresults ? diff local_settings.py.example local_settings.py 4c4 < DEBUG = False --- > DEBUG = True 12,13c12,13 < #DATABASE_ENGINE = 'sqlite3' < #DATABASE_NAME = 'archweb.db' --- > DATABASE_ENGINE = 'sqlite3' > DATABASE_NAME = 'archweb.db' 24c24 < CACHE_BACKEND = 'memcached://127.0.0.1:11211' --- > #CACHE_BACKEND = 'memcached://127.0.0.1:11211' (archweb-env)17:54:47 dieter@ws archweb testresults ? ./manage.py syncdb 1 ↵ Syncing... Creating table isotests_hardwaretype The following content types are stale and need to be deleted: isotests | hardware Any objects related to these content types by a foreign key will also be deleted. Are you sure you want to delete these content types? If you're unsure, answer 'no'. Type 'yes' to continue, or 'no' to cancel: yes No fixtures found. Synced: > django.contrib.auth > django.contrib.contenttypes > django.contrib.messages > django.contrib.sessions > django.contrib.sites > django.contrib.sitemaps > django.contrib.admin > django.contrib.markup > devel > public > south > isotests Not synced (use migrations): - main - mirrors - news - packages (use ./manage.py migrate to migrate these) (archweb-env)17:55:09 dieter@ws archweb testresults ? ./manage.py migrate Running migrations for main: - Migrating forwards to 0042_auto__del_field_packagefile_path. > packages:0004_auto__add_license > packages:0005_move_license_data > main:0038_add_depends_optional_description > main:0039_auto__del_field_package_license > main:0040_split_package_files > main:0041_move_package_files_data > main:0042_auto__del_field_packagefile_path - Loading initial data for main. No fixtures found. Running migrations for mirrors: - Nothing to migrate. - Loading initial data for mirrors. No fixtures found. Running migrations for news: - Nothing to migrate. - Loading initial data for news. No fixtures found. Running migrations for packages: - Nothing to migrate. - Loading initial data for packages. No fixtures found. (archweb-env)17:55:23 dieter@ws archweb testresults ? ./manage.py loaddata main/fixtures/arches.json Installing json fixture 'main/fixtures/arches' from absolute path. Installed 3 object(s) from 1 fixture(s) (archweb-env)17:55:29 dieter@ws archweb testresults ? ./manage.py loaddata main/fixtures/repos.json Installing json fixture 'main/fixtures/repos' from absolute path. Installed 7 object(s) from 1 fixture(s) (archweb-env)17:55:34 dieter@ws archweb testresults ? ./manage.py loaddata main/fixtures/groups.json Installing json fixture 'main/fixtures/groups' from absolute path. Problem installing fixture 'main/fixtures/groups.json': Traceback (most recent call last): File "/home/dieter/workspaces/eclipse/archweb-env/lib/python2.7/site-packages/django/core/management/commands/loaddata.py", line 169, in handle for obj in objects: File "/home/dieter/workspaces/eclipse/archweb-env/lib/python2.7/site-packages/django/core/serializers/json.py", line 38, in Deserializer for obj in PythonDeserializer(simplejson.load(stream), **options): File "/home/dieter/workspaces/eclipse/archweb-env/lib/python2.7/site-packages/django/core/serializers/python.py", line 105, in Deserializer m2m_data[field.name] = [m2m_convert(pk) for pk in field_value] File "/home/dieter/workspaces/eclipse/archweb-env/lib/python2.7/site-packages/django/core/serializers/python.py", line 100, in m2m_convert return field.rel.to._default_manager.db_manager(db).get_by_natural_key(*value).pk File "/home/dieter/workspaces/eclipse/archweb-env/lib/python2.7/site-packages/django/contrib/auth/models.py", line 50, in get_by_natural_key content_type=ContentType.objects.get_by_natural_key(app_label, model) File "/home/dieter/workspaces/eclipse/archweb-env/lib/python2.7/site-packages/django/contrib/contenttypes/models.py", line 15, in get_by_natural_key ct = self.get(app_label=app_label, model=model) File "/home/dieter/workspaces/eclipse/archweb-env/lib/python2.7/site-packages/django/db/models/manager.py", line 132, in get return self.get_query_set().get(*args, **kwargs) File "/home/dieter/workspaces/eclipse/archweb-env/lib/python2.7/site-packages/django/db/models/query.py", line 347, in get % self.model._meta.object_name) DoesNotExist: ContentType matching query does not exist. (archweb-env)17:55:39 dieter@ws archweb testresults ? ./manage.py loaddata mirrors/fixtures/mirrorprotocols.json Installing json fixture 'mirrors/fixtures/mirrorprotocols' from absolute path. Installed 3 object(s) from 1 fixture(s)

3 31

[arch-releng] [archiso] saying good-bye to union-fs-method?
by Gerardo Exequiel Pozzi 13 Jun '11

13 Jun '11

Hi * With 2.6.39 there is no aufs2 support, at least for a long time[#1]. * I think that back in time with unionfs is not desirable, needs a complete kernel patch. * union-fs-fuse does not work good. What about using the method like in Fedora? (basically a device-mapper with a snapshot in tmpfs). This change from file-to-file level to block-to-block logic. I can do some research in my free time if there any interest on this. I am open to all sugestions. Thanks. [#1] http://www.mail-archive.com/aufs-users@lists.sourceforge.net/msg03315.html -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

2 12

[arch-releng] AIF Install Troubles - Encrypted LVM
by Francis L Young III 02 Jun '11

02 Jun '11

I am trying to make an AIF install script by modifying the "fancy-install-on-sda" example. My troubles lie at the very end of line 35. https://github.com/Dieterbe/aif/blob/master/examples/fancy-install-on-sda I want to set the home partition to extend to the remaining free space, but I don't know what token or variable to put there that AIF recognizes as the equivalent of '+100%FREE' (which I have tried with no success). Any suggestions?

2 1