Pacman Error when chroot'ed from live cd

Question

I get this error when trying to chroot into my system from a kubuntu live cd.
Total Package Size: 104.61 MB
Proceed with installation? [Y/n] y
checking package integrity... done.
cleaning up... done.
(78/78) checking for file conflicts [#####################] 100%
error: could not prepare transaction
error: failed to commit transaction (not enough space on disk)
I followed the wiki at http://wiki.archlinux.org/index.php/Ins … _Interface and typed the following commands in the terminal. so i could try to install kde and configure my wireless connection
here are the exact commands i entered to chroot into the system
sudo mkdir /mnt/arch
sudo mount -t jfs /dev/sdb3 /mnt/arch
sudo cp /etc/resolv.conf /mnt/arch/etc/
sudo mount -t proc none /mnt/arch/proc
sudo mount -o bind /dev /mnt/arch/dev
sudo chroot /mnt/arch /bin/bash
source /etc/profile
In the Newbie forum http://bbs.archlinux.org/viewtopic.php?id=35158 another user mentioned solving this error by adding the folowing lines to /etc/mtab:
/dev/sda5 / ext3 rw 0 0
can someone explain how exactly i would go about doing this for my system
as far as i can tell i would add /dev/sdb3 / jfs rw 0 0  but i dont know what rw 0 0 refers to and whether or not to change that.  and i dont know where exactly to add these lines.
Any help or guidance is appreciated.

Answer 1

pl2lnce wrote:
as far as i can tell i would add /dev/sdb3 / jfs rw 0 0  but i dont know what rw 0 0 refers to and whether or not to change that.  and i dont know where exactly to add these lines.
Any help or guidance is appreciated.
rw tells mount to mount the filesystem read-write, the first 0 is the dump value (when dump if installed should make a backup), en the second 0 is the pass value, in which order the filesystems should be checked at boot. For more information on fstab you should read the wiki entry: http://wiki.archlinux.org/index.php/Fstab
Note that mtab works more or less (though not exactly) as fstab (mtab has only ro and rw options AFAIK, and dump and pass values are not passed to mtab as it is a dynamic file and is empty when rebooting). Mtab keeps dynamically the filesystems that are mounted. So adding
/dev/sdb3 / jfs rw 0 0
to mtab, lets your system think that /dev/sdb3 is mounted read-write on / (which in your case is true )
Last edited by pressh (2007-12-11 09:28:00)