Arch-releng December 2010

arch-releng@lists.archlinux.org

17 participants
23 discussions

[arch-releng] away mode on
by Gerardo Exequiel Pozzi 29 Dec '10

29 Dec '10

Hi I am going to take some days of vacation and detox of electronic devices from 01/01 to 15/01. PS: I am a bit out from here in these days because lots of problems with electrical supply. :( Good year \forall -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

2 1

[arch-releng] releng build environment moved
by Dieter Plaetinck 23 Dec '10

23 Dec '10

Hi, we just moved the releng image building stuff from sigurd.al.org to alberich.al.org To clarify: Moved: - image generation environment - http serving of testbuilds, releng packages, releng repos Untouched: - hosting of official images (http://www.archlinux.org/download/) - Torrent tracker (tracker.al.org) - releng mailing list The new machine is the VPS donated by airVM, see https://wiki.archlinux.org/index.php/Category:DeveloperWiki:Server_Configur… Two reasons for this move: - releng load patterns affected the AUR/community repos, running on sigurd, also disk space was getting tight - I wanted a separate env to perform all the critical releng stuff without worrying too much I might break some production service Folks following releng stuff, note: - build.archlinux.org has been deprecated, the new url is releng.archlinux.org - the same stuff (testbuilds, packages, etc) are available on the new location Releng TODO: - update scripts so we can fully automatically build testing images - update scripts to update tracker on sigurd - schedule automatic builds Dieter

1 0

[arch-releng] btrfs support in aif
by Dieter Plaetinck 21 Dec '10

21 Dec '10

Anthony and other interested folks, I've been looking a bit further, and it seems like btrfs support shouldn't be too hard to implement. It actually seems simpler then LVM (because lvm has 3 levels: PV,VG and LV; btrfs has just the btrfs itself (~default subvolume) and other subvolumes) subvolumes don't get a new devicefile but i'll probably use something like: /dev/sda:$spec to denote what's what. if $spec is a number, it will become mount option subvolid=$spec; otherwise subvol=$spec although from what i can tell, the id's aren't used often. and it seems more robust to me use names anyway. * which are the requirements your btrfs_advanced mkinitcpio hook implies? what things does aif need to do other then just doing mkfs.btrfs to get the full potential out of btrfs/your hook? please explain why a default btrfs configuration does not suffice. does it have something to do with https://btrfs.wiki.kernel.org/index.php/UseCases#Can_a_snapshot_be_replaced… ? * I've read a bit more about btrfs and I think an implementation like this will suffice for most users: - allow creation of a btrfs on top of 1-n blockdevices (user can pick raid levels for data and metadata) - allow creation of 0-m subvolumes - each subvolume as well as the default can get an arbitrary mountpoint, as well as specific mount options like compress, ssd, etc. if i understood correctly, that is. However, to be fully compatible with your hook, I will probably "strongly recommend" to create a subvolume __active and mount that as / Right? anything I missed? Dieter

2 7

[arch-releng] new testbuilds
by Dieter Plaetinck 20 Dec '10

20 Dec '10

http://build.archlinux.org/isos/2010.12.18/ a quick rundown of recent changes: * several aif bugfixes and improvements, mostly related to packages, filesystems, partitioning, font,keymap,editor selection, more robust checking if packages got installed properly, improved example configs for automatic profile, etc. * aif usability enhancements: - several nicer menu's in various places - package selection shows package info when you hover over it (note there's a small bug that causes packages to be ordered incorrectly, fixed in git but not worth rebuilding for). if you want the new package: http://build.archlinux.org/repos/releng-any/aif-2010.04.18-1-any.pkg.tar.xz (built from git, btrfs branch) * inclusion of nilfs and btrfs utilities, and support in aif. aif nilfs support should just work. aif has rudimental btrfs support, but untested. * a whole bunch of archiso changes by Gerardo (remove joe, new directory layout, squashfs support -although I don't know how this affects the images -, ..) * libui-sh bugfixes * dual images using split profile. here is the roadmap for the next official release. https://bugs.archlinux.org/roadmap/proj6 it doesn't include stuff like gpt or wireless support, because i have my hands more then full already. I would appreciate it if people can give this a testrun and report feedback. maybe even contribute patches.. everything should work nicely, except btrfs. and nilfs and btrfs utilities can't get installed to the target system. and initscripts needs a nilfs patch before that can work properly too. Dieter

3 9

[arch-releng] [PATCH 1/2] invoke aif with debugging and logging flags by default
by Dieter Plaetinck 20 Dec '10

20 Dec '10

these options have no real disadvantages, but can provide lots of useful info when the user runs into trouble, which still happens enough --- configs/syslinux-iso/overlay/arch/setup | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/configs/syslinux-iso/overlay/arch/setup b/configs/syslinux-iso/overlay/arch/setup index e9d1660..908d106 100755 --- a/configs/syslinux-iso/overlay/arch/setup +++ b/configs/syslinux-iso/overlay/arch/setup @@ -1,3 +1,3 @@ #!/bin/sh # -aif -p interactive +aif -p interactive -d -l -- 1.7.3.3

2 2

[arch-releng] how many/which non-base packages do you select during installation?
by Dieter Plaetinck 19 Dec '10

19 Dec '10

When I install arch, I don't really bother reviewing the package list to enable packages I want; I just install the system using the base group and install extra packages when I need them. With maybe the exception of openssh, I have noticed i always need that one right away anayway. Out of curiosity: do you guys also have this kind of approach, or do you actually take the time to review the package selection dialog? why? which packages do you usually choose right away? Dieter

4 3

[arch-releng] [PATCH 1/2] include nilfs utilities
by Dieter Plaetinck 17 Dec '10

17 Dec '10

--- configs/syslinux-iso/packages.i686 | 1 + configs/syslinux-iso/packages.x86_64 | 1 + 2 files changed, 2 insertions(+), 0 deletions(-) diff --git a/configs/syslinux-iso/packages.i686 b/configs/syslinux-iso/packages.i686 index 1b4be76..00c30ab 100644 --- a/configs/syslinux-iso/packages.i686 +++ b/configs/syslinux-iso/packages.i686 @@ -21,6 +21,7 @@ ndiswrapper ndiswrapper-utils netcfg nfs-utils +nilfs-utils nmap ntfs-3g ntfsprogs diff --git a/configs/syslinux-iso/packages.x86_64 b/configs/syslinux-iso/packages.x86_64 index 1b4be76..00c30ab 100644 --- a/configs/syslinux-iso/packages.x86_64 +++ b/configs/syslinux-iso/packages.x86_64 @@ -21,6 +21,7 @@ ndiswrapper ndiswrapper-utils netcfg nfs-utils +nilfs-utils nmap ntfs-3g ntfsprogs -- 1.7.3.3

2 2

[arch-releng] Last review of 14 patches before push to master.
by Gerardo Exequiel Pozzi 14 Dec '10

14 Dec '10

To avoid too many mails, I simply sent this one with summary. I now have access to archiso.git, any issues in pushing these changes? I done some test and all works: * build i686 and x86_64 iso. * build dual iso. * boot i686 and x86_64 (all syslinux options works) * boot dual (all syslinux options works, and also autodetection) * boot with newer options for loop support (with and without copytoram) * all tests done with default install_dir "/arch" and under random name "/pepito". * also just for see image size I build images with sqfs compressed with lzma, of course this does not boot at this moment. core-dual look like: http://djgera.pastebin.com/vYMCuM6w core-i686 look like: http://djgera.pastebin.com/5puDe02m As you can see now both single and dual, share the same directory scheme. https://github.com/djgera/archiso/compare/master...experimental 7e1d2fd [syslinux-iso] Add support to squashfs compression types. 7e18035 [archiso2dual] Autodetect whether we can boot x86_64 8f6a6ab Unify scheme of sed replacements. 8bdf43e [archiso] Add support to mount iso in loopback mode. 85e3798 [syslinux-cfg] Remove joe from packages.* ed2e27e [archiso2dual] Adapt to new dir scheme of source /${install_dir}/${arch}/ f7d5cbb [syslinux-iso] Unify dir scheme with -dual images d34f2c6 [archiso] Place *.sqfs images in /${install_dir}/${arch}/ 3d46d7e [archiso2dual] Adjust to work with new dir scheme aae85f4 [syslinux-cfg] Adjust to work with new -D option of mkarchiso c186a20 [archiso] Add -D <install_dir> option to mkarchiso f139527 [archiso2dual] Modify behaviour of -S parameter af66220 [archiso2dual] Add support for squashfs compression types 487436b [archiso] Add support for squashfs compression types Thanks. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

2 7

[arch-releng] Simple question about todo.
by Thomas Dziedzic 14 Dec '10

14 Dec '10

Regarding the AIF interactive procedure file, is this still relevant? #TODO: why does a '2' appear instead of '' ?? ask_option $default "MAIN MENU" '' required \ "1" "$worker_select_source_title" \ "2" "$worker_set_clock_title" \ I couldn't find a 2 anywhere, so maybe this comment is unneeded?

2 1

[arch-releng] Support mobile broadband with wvdial
by Ray Rashif 13 Dec '10

13 Dec '10

I refer to this: http://mailman.archlinux.org/pipermail/arch-general/2010-June/014388.html Other (desktop) distributions can skip wvdial on their installers because they have (1) a desktop environment by default and as such (2) some sort of GUI network management front-end that can handle most types of connections, including mobile broadband [1]. However, we are leaving out those users. I had posted another link to configuring such connections with ppp some months ago [2], but the fact of the matter is that it's all pretty cumbersome. On the other hand, wvdial is a well-known method for this and is easy to configure, aside from gathering ISP details like APN and putting that in a file (etc/wvdial.conf). Right now only the following people can install Arch Linux without having to go through a number of hoops: * with cable broadband * with DSL broadband * with wireless broadband I believe we'd be pretty much 'complete' if we added: * with mobile broadband At least, in the 'broadband' category. This effectively implies 2 packages from [extra]: wvdial wvstreams (dependency) Since a package needn't be in [core] to be included in the image, I say we should do this :) [1] http://en.wikipedia.org/wiki/Mobile_broadband [2] http://mailman.archlinux.org/pipermail/arch-general/2010-October/016727.html

4 8

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Arch-releng December 2010