March 2009 - Arch-releng - lists.archlinux.org

[arch-releng] the future of quickinst
by Dieter Plaetinck 13 Mar '09

13 Mar '09

quickinst: http://projects.archlinux.org/?p=installer.git;a=blob;f=quickinst;h=23e41cc… Is there anyone who actually uses this? If so, can you tell me why? It's stated quickinst is meant for people who want to mkfs/mount their filesystems themselves, okay I understand that. But, as a "consequence" you can only install the base packages, your keyboard/time/.. settings don't go into /mnt/etc/rc.conf automatically, you need to install the bootloader manually (which means having to mount some things yourself, chroot etc. What is the advantage of this over just using the normal installer and skipping the steps you don't want to do? I'm wondering if shouldn't just drop it. Note that with AIF it's quite easy to implement a "partial procedure", which is a procedure to do one or a few specific things. (right now there are partial procedures which let you do keymap/font selection, disk/partition/filesystem config, and network setup). I could add one to let the user just do package selection & installation, for example. Dieter

5 9

[arch-releng] dialog sizes in archlinux-installer / aif
by Dieter Plaetinck 07 Mar '09

07 Mar '09

Hi all, A purely cosmetical issue, but something that I want to address: the sizes of dialog boxes in aif current approach in aif: some hardcoded values in the revelant functions of lib-ui. problem: for some dialogs they look good, for others they are waay to big (if you've played with aif you may have noticed this already), and hardcoding values is bad practice anyway. Dialog seems to have an "auto sizing" (just fill in 0 as height/width/.. parameter) feature which seems to work quite well: it makes sure what you want to display fits in the dialog and there is some extra padding space so it looks good, so I think I should use this. However, the old installer ( http://projects.archlinux.org/?p=installer.git;a=blob_plain;f=setup;hb=HEAD ) seems to make use of the autosizing often, but also often it still uses hardcoded values. Is there any specific reason for this? Can things go "wrong" by just relying on auto-sizing everywhere? Also, dialog provides an --aspect parameter to control the aspect when using autosizing, however I don't see the need for this. without it, dialog always makes sure the content fits nicely. Even more, I noticed that even when you use extreme aspects (--aspect 1 or --aspect 500), it still shows your content nicely (even if it's for example one long line), looks to me like it doesn't even do much? Dieter

2 2

Re: [arch-releng] AIF [PATCH 1/2] Fix URL parsing for core repo
by Gerhard Brauer 06 Mar '09

06 Mar '09

Am Montag, den 02.03.2009, 06:25 +1000 schrieb Allan McRae: > Gerhard Brauer wrote: > > Dieter, have you seen the attachements (git patches) on both of my > > mails? In sent folder the have the attachements, but my mails getting on > > the ML i don#t see the attached files... > > > > I didn't receive the patches either. You might want to look into "git > send-email" so thing are sent inline rather than as attachments. It > makes commenting on patches a lot easier. Ok, i will have a look at. But i have sent often patches as attachemnts to the list, without any problem. Something changed in the mailing list software so that not all mime files are allowed? (I sent the mail again to my address to see if i made a mistake, but there not problem with the attached patch..) But i will sent them inline again.... > Allan Gerhard > > >

3 3

[arch-releng] AIF [PATCH 2/2] Already running dhcpcd is not stopped during network setup
by Gerhard Brauer 06 Mar '09

06 Mar '09

If network is already set up during ftp install (dhcpcd already running and $INTERFACE is running) aif failed when stopping and reconfigure during interactive network setup. Reason: we kill a process named dhcpd, but it must be dhcpcd. So no running dhcp client is stopped and the network setup failed cause already a client running on $INTERFACE. So we have to kill: kill dhcpcd. Or better use the dhcpcd function fur such a case: dhcpcd -k $INTERFACE. Regards Gerhard

5 8

[arch-releng] AIF [PATCH 1/2] Fix URL parsing for core repo
by Gerhard Brauer 02 Mar '09

02 Mar '09

When doing ftp install method the selected mirror URL is badly parsed to the generated /tmp/pacman.conf. So fetching the core db from mirror fails. Example: [gerhard@ws01 ~]$ serverurl='ftp://ftp.he.de/mirror/$repo/os/i686' [gerhard@ws01 ~]$ echo $serverurl ftp://ftp.he.de/mirror/$repo/os/i686 [gerhard@ws01 ~]$ repo=core old code: --------- [gerhard@ws01 ~]$ echo "Server = ${serverurl/\/\$repo\//\/$repo\/}" Server = ftp://ftp.he.de/mirror\/core\/os/i686 patched: [gerhard@ws01 ~]$ echo "Server = ${serverurl/\$repo/$repo}" Server = ftp://ftp.he.de/mirror/core/os/i686 Cause this code section is commented already as a "hack" maybe it's better to have a solution where we split the $serverurl to get only the absolute mirror URL path (ex: ftp://ftp.he.de/mirror) and build from that our download line for the core repo (ex: "$url/core/os/$ARCH), so we avoid regexe's. Only the core repo needs a "extra" handling, all other repos (if there are any!) uses the pacman.d/mirrorlist method. Regards Gerhard

4 7