On Nov 12, 2007 4:51 PM, Damir Perisa wrote:

are there plans for a i686 built-machine?

For pacbuild, absolutely. This, however, is something different. It's possibly to setup a 32bit chroot on a 64bit machine (as 64bit machines will run 32bit code), but it is not really possible to do the other direction (last I checked). So this machine is here for people who don't have 64bit hardware, or do but don't want to wipe their machines just yet.

my old machine is dying slowly but steadily and i do not yet have a bigger harddrive on my new one... so i'm kind of handicapped on i686 atm.

@ all : if you find some x86_64 pkgs of mine not updated/build for i686, this is the reason - feel free to build them if you have the resources. thanx

Well is this is a problem at this moment, I can look into this. In fact, I might be able to setup a 32bit chroot on the same machine, which would make everything easier.

Aaron Griffin schrieb:

...

@ all : if you find some x86_64 pkgs of mine not updated/build for i686, this is the reason - feel free to build them if you have the resources. thanx

Well is this is a problem at this moment, I can look into this. In fact, I might be able to setup a 32bit chroot on the same machine, which would make everything easier.

In fact, it is a simple matter of pacman -r /mnt/arch32 -c /mnt/arch32/pacman.conf -S base base-devel (with the right pacman.conf) pacman -S dchroot vi /etc/dchroot.conf I have tons of scripts for that stuff, like scripts for bind-mounting /home and such. BTW, you should add a SRCDEST directory globally if you have not already done so. Some script snippets from me: Bash prompt: USERCOL= HOSTCOL= EXTRAPROMPT= RSTCOL='\[\033[0m\]' NCOL='\[\033[0;37;40m\]' case $UID in 0) USERCOL='\[\033[0;31;40m\]' ;; *) USERCOL='\[\033[0;32;40m\]' ;; esac HOSTCOL='\[\033[1;33;40m\]' EXTRAPROMPT="[$(cat /etc/archlinux-root)]" case ${EXTRAPROMPT} in [i686*) [ "$(uname -m)" != "i686" ] && EXTRAPROMPT="\[\033[1;31;40m\]${EXTRAPROMPT}${NCOL}" ;; [x86_64*) [ "$(uname -m)" != "x86_64" ] && EXTRAPROMPT="\[\033[1;31;40m\]${EXTRAPROMPT}${NCOL}" ;; esac export PS1="${NCOL}${EXTRAPROMPT}[\t][${USERCOL}\u${NCOL}@${HOSTCOL}\h${NCOL} \W]${RSTCOL}\\$ " unset USERCOL HOSTCOL RSTCOL NCOL EXTRAPROMPT The middle part is interesting, where it makes the [i686] red if one forgets to run "linux32" with dchroot. To make life easier, I use the "arch32" script: #!/bin/sh if [ -n "$*" ]; then CMD="$*" exec linux32 dchroot -c arch32 "$CMD" else exec linux32 dchroot -c arch32 fi (This fixes some weirdness in the way dchroot works with passing a command). linux32 is part of the util-linux-ng package. Now, for bind-mounting (don't do it via fstab, it will break): for p in tmp dev dev/pts dev/shm proc proc/bus/usb sys home; do mount --bind /$p /mnt/arch32/$p done mount --bind -o ro / /mnt/arch32/mnt/arch64 Do something similar for umount. The bindmount that leads back from arch32 to arch64 is useful to symlink resolv.conf and mtab, so I don't have to adjust resolv.conf in arch32 every time I switch networks. I also symlink some files from profile.d. I hope this makes it easier for you.

Aaron Griffin schrieb:

I apparently need to add support for linux32 (not a problem), but also would like to know why you use dchroot over plain old chroot?

dchroot is designed to be used as a non-privileged user, but only works for roots that have been allowed by the admin.

On 11/14/07, Eric Belanger wrote:

If you don't mind giving access to TU, forward that post to the TUR ML. They are the ones that needs that the most. I believe I'm the only one that regularly builds stuff for community64. The workload can get pretty high sometimes. ;)

I was under the impression that most TU's now had x86_64 boxes and were building on their own, so I stopped building for c64. Guess I was mistaken. Will help you out soon, Eric. :) Varun