[arch-general] Arch Linux installation only with pacman
Hello all! I remember looking at the installation script about one year ago, and all it had done (to install the base packages), was to use pacman. Now if I try to use the same procedure now (or what I remember from it), I get a lot of errors from the install hooks (script-lets). I've tried to install them once without by disabling scriptlets, and then once more by using them, but the errors are still there. So my question is: how can I install Arch Linux now, by having only a static built pacman? (I want to use this for an automated installation procedure for virtual machines.) (I think I've tried the procedure on the Wiki page with the same outcome.) Thanks, Ciprian Craciun. P.S.: Maybe it's Ok to have those scriptlet errors?
On Wed, Oct 14, 2009 at 4:16 PM, Ciprian Dorin, Craciun
Hello all!
I remember looking at the installation script about one year ago, and all it had done (to install the base packages), was to use pacman. Now if I try to use the same procedure now (or what I remember from it), I get a lot of errors from the install hooks (script-lets). I've tried to install them once without by disabling scriptlets, and then once more by using them, but the errors are still there.
So my question is: how can I install Arch Linux now, by having only a static built pacman? (I want to use this for an automated installation procedure for virtual machines.) (I think I've tried the procedure on the Wiki page with the same outcome.)
Thanks, Ciprian Craciun.
P.S.: Maybe it's Ok to have those scriptlet errors?
It's easy with: pacman --root=/path/to/my/install -S base You will get scriptlet errors, however. It can't be helped as there's crazy dependency cycles happening. I think it might be safe to just run the above command twice if you really want to make it clean
Ciprian Dorin, Craciun schrieb:
Hello all!
I remember looking at the installation script about one year ago, and all it had done (to install the base packages), was to use pacman. Now if I try to use the same procedure now (or what I remember from it), I get a lot of errors from the install hooks (script-lets). I've tried to install them once without by disabling scriptlets, and then once more by using them, but the errors are still there.
So my question is: how can I install Arch Linux now, by having only a static built pacman? (I want to use this for an automated installation procedure for virtual machines.) (I think I've tried the procedure on the Wiki page with the same outcome.)
Thanks, Ciprian Craciun.
P.S.: Maybe it's Ok to have those scriptlet errors?
Install to /mnt as root (provided you have a working pacman.conf in .) # mkdir -p /mnt/var/lib/pacman/{local,sync} # ./pacman.static --root /mnt --config ./pacman.conf -Sy base That's it, all you need to do is configure the system (you need to know how) and install a bootloader. I did this recently and the system worked (it was a test system though, it's not in any productive use). There will be _some_ errors from scriptlets in the beginning, but those should be fine - you can paste the output here in case you are unsure.
Thomas Bächler schrieb:
Install to /mnt as root (provided you have a working pacman.conf in .)
# mkdir -p /mnt/var/lib/pacman/{local,sync} # ./pacman.static --root /mnt --config ./pacman.conf -Sy base
That's it, all you need to do is configure the system (you need to know how) and install a bootloader. I did this recently and the system worked (it was a test system though, it's not in any productive use).
There will be _some_ errors from scriptlets in the beginning, but those should be fine - you can paste the output here in case you are unsure.
Forgot something: It might be a good idea to run those commands before you start: mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys mount --bind /dev /mnt/dev
Thank you all for your feedback! I'm more confident now that I can
just ignore those errors.
One observation though: having dev, proc, and sys mounted in the
new chroot, wouldn't it misslead the scriptlets? Because these special
files would be from the live host machine, and not the guest machine?
(Anyway I could just boot inside the guest machine and have the
installation done there...)
Ciprian.
On Thu, Oct 15, 2009 at 12:30 AM, Thomas Bächler
Thomas Bächler schrieb:
Install to /mnt as root (provided you have a working pacman.conf in .)
# mkdir -p /mnt/var/lib/pacman/{local,sync} # ./pacman.static --root /mnt --config ./pacman.conf -Sy base
That's it, all you need to do is configure the system (you need to know how) and install a bootloader. I did this recently and the system worked (it was a test system though, it's not in any productive use).
There will be _some_ errors from scriptlets in the beginning, but those should be fine - you can paste the output here in case you are unsure.
Forgot something: It might be a good idea to run those commands before you start: mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys mount --bind /dev /mnt/dev
Ciprian Dorin, Craciun schrieb:
Thank you all for your feedback! I'm more confident now that I can just ignore those errors.
One observation though: having dev, proc, and sys mounted in the new chroot, wouldn't it misslead the scriptlets? Because these special files would be from the live host machine, and not the guest machine? (Anyway I could just boot inside the guest machine and have the installation done there...)
The only thing that really depends on /sys is the autodetection in mkinitcpio - if you're going to boot this on another machine, you'll have to boot the fallback initramfs anyway, so it doesn't matter. I remember some install scriptlets look at files in /proc, but not having /proc shouldn't make problems either. The only thing you really need is /dev - or at least some nodes. If you don't want to bind-mount /dev, you need to create at least /mnt/dev/null (maybe also zero, not sure). On udev installation, /dev/{zero,null,console} are created there anyway, but that happens later. Note that our installer also bind-mounts proc, sys and dev from the live system to the installation system - it's safe and can avoid problems.
participants (3)
-
Aaron Griffin
-
Ciprian Dorin, Craciun
-
Thomas Bächler