hello jeremy thanks a lot for the "howto" :) i managed an install by booting from the cd and mounting the iso image and installing the packages from it following your manual steps below. but unfortunately the boot wasn't all successfull. i got messages something like this: VFS: Mounted root (ext3 filesystem) readonly [something unimportant] The system is coming up. Please wait. can't create lock file /etc/mtab~467: Read-only filesystem (use -n flag to override) [the same again but with ~472 instead] swapon: cannot stat /dev/sda5: No such file or directory ... and some more similar things before i get the option to enter a repair shell. i am not very experienced when it comes to the linux boot-up process, but it seems to me that the root filesystem isn't re-mounted r/w and hence /dev not populated and a bunch of errors follow. any ideas? cheers, lars On Tue, March 29, 2005 6:33 pm, Jeremy Jones said:
hi,
i just tried your iso and it booted ok, but i got some errors in the setup. the following packages didn't install because of "invalid archive": db, gcc, glibc, libtool, perl, sendmail, vim, emacs, firefox, gdb, gtk, nfs-utils, openssl, pine and x11. this could be because of a faulty download -- maybe you could put up an md5sum of the iso aswell?
done.
more serious i think are two other errors: filesystem: lib usr/lib pkgadd: listed files already installed
linux: tar: /mnt/usr/src: Cannot chdir: No such file or directory tar: Error is not recoverable: Exiting now.
my theory is that the latter is because of the former, and maybe the former has something todo with your (3) below, since the filesystem package wasn't installed first (or maybe it was installed first aswell?).
Here's what i just tried -- again, i can't boot from the iso right now, as i'm not in front of the box.
1. created an xfs filesystem on a new partition 2. mounted my the crux-amd64 iso at /mnt/iso 3. mounted my new xfs filesystem at /mnt/iso/mnt 4. chroot to /mnt/iso 5 mkdir -p /mnt/var/lib/pkg; touch /mnt/var/lib/pkg/db 6. pkgadd -r /mnt /crux/base/filesystem#2.0-1.pkg.tar.gz 7. cd /crux/base; for pkg in `ls -1`; do pkgadd -r /mnt $pkg done (filesystem fails, 'cuz I already installed it in step 6...) 8. cd /crux/opt; for pkg in `ls -1`; do pkgadd -r /mnt $pkg done 9. cd /crux/contrib; for pkg in `ls -1`; do pkgadd -r /mnt $pkg done
All this tells me the packages are ok.
Please note:
during the install, before running setup, mount your partitions, create your /mnt/var/lib/pkg directory and touch /mnt/var/lib/pkg/db. then run pkgadd -r /mnt /crux/base/filesystem#2.0-1.pkg.tar.gz. This will ensure that /lib -> /lib64 and /usr/lib -> /usr/lib64. After that, the installation should go ok. If you leave filesystem selected when you run setup, you'll get an error about the package being already installed -- no big deal, you just installed it manually before running setup.
If the setup program just refuses to run properly, install everything manually:
1. create and mount your filesystems 2. mkdir -p /mnt/var/lib/pkg; touch /mnt/var/lib/pkg/db 3. pkgadd -r /mnt /crux/base/filesystem#2.0-1.pkg.tar.gz 4. cd /crux/base; for pkg in `ls -1`; do pkgadd -r /mnt $pkg done 5. cd /crux/opt; for pkg in `ls -1`; do pkgadd -r /mnt $pkg done 6. cd /crux/contrib; for pkg in `ls -1`; do pkgadd -r /mnt $pkg done 7. cd /mnt/usr/src 8. bzcat /crux/kernel/linux-2.6.11.tar.bz2 | tar xv 9. mknod /mnt/dev/console c 5 1 10. mount --bind /dev /mnt/dev 11. chroot /mnt 12. mount proc -t proc /proc 13. edit what needs editing in /etc 14. cd /usr/src/linux-2.6.11 15. build your kernel 16. copy your kernel where you like to copy your kernels 17. run lilo & reboot
please let me know if this works for you.
jeremy
_______________________________________________ Clc-crux64 mailing list Clc-crux64@lists.berlios.de http://lists.berlios.de/mailman/listinfo/clc-crux64