hello. although this list seems a bit dead i thought it nice to announce my prescence. i am about to try the version at http://www.samnjack.com/crux-amd64/ and maybe do some experimenting of my own from there on. i found this link, http://home.ix.netcom.com/~ejohns/glfs-amd64/index.html that i hope can be helpful. is there still anyone out there interested in this project? cheers, lars
hi lars, On Mon, 2005-03-28 at 18:50 +0200, lasso@spacecentre.se wrote:
hello.
although this list seems a bit dead i thought it nice to announce my prescence. i am about to try the version at http://www.samnjack.com/crux-amd64/ and maybe do some experimenting of my own from there on.
The version up at samnjack.com (my first try) is a bit old, and, in fact, the iso is unbootable. I have a some newer (maintained) stuff running on my personal box at the moment. Perhaps later today I can get the newer stuff moved up to that site. Anyway, welcome. Jeremy
hello jeremy, i guess i can abort the download then... ;) it would be really great if you could make the newer stuff available soon-ish... i am running gentoo now, and it is not really my cup of tea i've come to realize... if you need webspace for the files just let me know. cheers, lars
hi lars,
On Mon, 2005-03-28 at 18:50 +0200, lasso@spacecentre.se wrote:
hello.
although this list seems a bit dead i thought it nice to announce my prescence. i am about to try the version at http://www.samnjack.com/crux-amd64/ and maybe do some experimenting of my own from there on.
The version up at samnjack.com (my first try) is a bit old, and, in fact, the iso is unbootable. I have a some newer (maintained) stuff running on my personal box at the moment. Perhaps later today I can get the newer stuff moved up to that site.
Anyway, welcome.
Jeremy
_______________________________________________ Clc-crux64 mailing list Clc-crux64@lists.berlios.de http://lists.berlios.de/mailman/listinfo/clc-crux64
Hi Lars, On Mon, Mar 28, 2005 at 18:50:38 +0200, lasso@spacecentre.se wrote:
hello.
although this list seems a bit dead i thought it nice to announce my prescence. i am about to try the version at http://www.samnjack.com/crux-amd64/ and maybe do some experimenting of my own from there on. There's another ISO/build setup at http://www.magog.se/crux-amd64/
i found this link, http://home.ix.netcom.com/~ejohns/glfs-amd64/index.html that i hope can be helpful.
is there still anyone out there interested in this project? As far as I can tell, no real subproject has been created so far, but
According to the webpage there's a fully functional ISO image available. there's certainly (growing) interest in an x86_64 / amd64 port of CRUX. Also questions regarding a port to amd64 come up rather frequently in the crux IRC channel, so I'd expect that finding testers should not be a problem. I've also heard from others that they plan to get an amd64, and they'd like to work on a crux port for it. As for port maintenance, we (at CLC) are looking into a way to simplify merging between multiple platforms, but we're not quite there yet. (if you're interested please read https://lists.berlios.de/pipermail/clc-devel/2004-December/000730.html https://lists.berlios.de/pipermail/clc-devel/2005-March/000793.html https://lists.berlios.de/pipermail/clc-devel/2005-March/000798.html ). Please keep us informed about your progress. Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net
hello
Hi Lars,
On Mon, Mar 28, 2005 at 18:50:38 +0200, lasso@spacecentre.se wrote:
hello.
although this list seems a bit dead i thought it nice to announce my prescence. i am about to try the version at http://www.samnjack.com/crux-amd64/ and maybe do some experimenting of my own from there on. There's another ISO/build setup at http://www.magog.se/crux-amd64/
According to the webpage there's a fully functional ISO image available.
i already tried this one a while back, but i get a kernel panic or something similar when booting.
i found this link, http://home.ix.netcom.com/~ejohns/glfs-amd64/index.html that i hope can be helpful.
is there still anyone out there interested in this project? As far as I can tell, no real subproject has been created so far, but there's certainly (growing) interest in an x86_64 / amd64 port of CRUX. Also questions regarding a port to amd64 come up rather frequently in the crux IRC channel, so I'd expect that finding testers should not be a problem. I've also heard from others that they plan to get an amd64, and they'd like to work on a crux port for it.
As for port maintenance, we (at CLC) are looking into a way to simplify merging between multiple platforms, but we're not quite there yet. (if you're interested please read https://lists.berlios.de/pipermail/clc-devel/2004-December/000730.html https://lists.berlios.de/pipermail/clc-devel/2005-March/000793.html https://lists.berlios.de/pipermail/clc-devel/2005-March/000798.html ).
Please keep us informed about your progress.
this looks very interesting and i'll definitely get back when and if i make some progress. cheers, lars
Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net _______________________________________________ Clc-crux64 mailing list Clc-crux64@lists.berlios.de http://lists.berlios.de/mailman/listinfo/clc-crux64
ok... at http://www.samnjack.com/crux-amd64 is an iso + my build tree for amd64 arch. i've not tried to boot the iso... not in front of my 64 bit box at the moment. should work, but no promises yet. if it doesn't boot for you, let me know what happens & i'll try & fix it. the cd image has udev, not devfs, and i've never tested this with a bootable cdrom before. here's the README: *********************************************************************** This is a modified version of CRUX for x86_64. It was built with an amd64 machine, so I can't say whether it'll work on an intel 64-bit box or not. A few things to note: 1. for the most part, the ports are out of the current cvs, NOT 2.0 ports. we use gcc-3.4.3, glibc-2.3.4, linux-2.6.11 headers, and some other updated stuff. having said this, note that using the crux ports system (we can only use httpup here, no cvsup for x86_64 yet...) is not at all foolproof. i recommend downloading my ports.tar.gz, decompressing somewhere neutral (like /tmp), and copying the base & opt directories to /usr/ports/base64 and /usr/ports/opt64. if you use prt-get (i can't live without it), edit your prt-get.conf to put base64 and opt64 (and optionally contrib64 & unmaintained64 etc) before base & opt. 2. the kernel i use has 32bit emulation enabled, but i've not provided any 32bit libraries, and gcc is build w/out multilib enabled. you can use a 32-bit crux install & chroot to it to build static 32-bit binaries if you like. 3. /lib and /usr/lib are symlinks to /lib64 and /usr/lib64 respectively. you need to install the filesystem port first on a new install, then the rest of the stuff. reason is, the ports/packages themselves don't know the difference between the real /lib64 or /usr/lib64 and the symlinked /lib or /usr/lib. please remember this! 4. i'm using udev, not devfs. the devfs port isn't included. it will build, and it will install, and it will work if you edit the rc scripts. i just like udev better. bit of a pain, though. i've not included an updated handbook or anything. basically, before chrooting, but after installing packages, run: # mknod /mnt/dev/console c 5 1 # mount --bind /dev /mnt/dev then chroot. skip the part where you mount devfs. 5. with regards to building ports, often software that's not been updated for a while barfs in ./configure stage, complaining about the architecture. often this can be overcome by copying a newer config.sub and config.guess into the source directory. see the dhcpcd port, for an example. some stuff is a real pain to get working. some stuff works just fine. 6. anyone who can and want's to make this better, please feel free. i'm a bit too busy to be a real maintainer of this stuff. well, maybe a bit too lazy is more appropriate. for the most part, i just plug away on my own pc without too much thought about whether what i'm doing is right or proper in a distribution development sense. 7. glibc is built with linuxthreads. i personally needed that to run some software that doesn't play nice with nptl. nptl ought to be easy enough to put back in: just edit the glibc port, recompile everything, & voila! you can contact me at jeremy at samnjack dot com enjoy! jeremy
hello jeremy. 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? 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?). moreover, i think udev is the right way to go :) cheers, lars
ok...
at http://www.samnjack.com/crux-amd64 is an iso + my build tree for amd64 arch.
i've not tried to boot the iso... not in front of my 64 bit box at the moment. should work, but no promises yet. if it doesn't boot for you, let me know what happens & i'll try & fix it. the cd image has udev, not devfs, and i've never tested this with a bootable cdrom before.
here's the README:
***********************************************************************
This is a modified version of CRUX for x86_64. It was built with an amd64 machine, so I can't say whether it'll work on an intel 64-bit box or not. A few things to note:
1. for the most part, the ports are out of the current cvs, NOT 2.0 ports. we use gcc-3.4.3, glibc-2.3.4, linux-2.6.11 headers, and some other updated stuff. having said this, note that using the crux ports system (we can only use httpup here, no cvsup for x86_64 yet...) is not at all foolproof. i recommend downloading my ports.tar.gz, decompressing somewhere neutral (like /tmp), and copying the base & opt directories to /usr/ports/base64 and /usr/ports/opt64. if you use prt-get (i can't live without it), edit your prt-get.conf to put base64 and opt64 (and optionally contrib64 & unmaintained64 etc) before base & opt.
2. the kernel i use has 32bit emulation enabled, but i've not provided any 32bit libraries, and gcc is build w/out multilib enabled. you can use a 32-bit crux install & chroot to it to build static 32-bit binaries if you like.
3. /lib and /usr/lib are symlinks to /lib64 and /usr/lib64 respectively. you need to install the filesystem port first on a new install, then the rest of the stuff. reason is, the ports/packages themselves don't know the difference between the real /lib64 or /usr/lib64 and the symlinked /lib or /usr/lib. please remember this!
4. i'm using udev, not devfs. the devfs port isn't included. it will build, and it will install, and it will work if you edit the rc scripts. i just like udev better. bit of a pain, though. i've not included an updated handbook or anything. basically, before chrooting, but after installing packages, run:
# mknod /mnt/dev/console c 5 1 # mount --bind /dev /mnt/dev
then chroot. skip the part where you mount devfs.
5. with regards to building ports, often software that's not been updated for a while barfs in ./configure stage, complaining about the architecture. often this can be overcome by copying a newer config.sub and config.guess into the source directory. see the dhcpcd port, for an example. some stuff is a real pain to get working. some stuff works just fine.
6. anyone who can and want's to make this better, please feel free. i'm a bit too busy to be a real maintainer of this stuff. well, maybe a bit too lazy is more appropriate. for the most part, i just plug away on my own pc without too much thought about whether what i'm doing is right or proper in a distribution development sense.
7. glibc is built with linuxthreads. i personally needed that to run some software that doesn't play nice with nptl. nptl ought to be easy enough to put back in: just edit the glibc port, recompile everything, & voila!
you can contact me at jeremy at samnjack dot com
enjoy! jeremy
_______________________________________________ Clc-crux64 mailing list Clc-crux64@lists.berlios.de http://lists.berlios.de/mailman/listinfo/clc-crux64
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
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
On Wed, 2005-03-30 at 23:08 +0200, Lars Helmer wrote:
hello jeremy
thanks a lot for the "howto" :)
sure thing. may have forgotten something, though... you need to compile your kernel w/out devfs and w/hotplug support. maybe this helps? Jeremy
i had devfs support in the kernel, but removing it didn't help. i will look into it some more during the weekend and get back with any results or new suspicions... cheers, lars On Wed, March 30, 2005 11:59 pm, Jeremy Jones said:
On Wed, 2005-03-30 at 23:08 +0200, Lars Helmer wrote:
hello jeremy
thanks a lot for the "howto" :)
sure thing. may have forgotten something, though... you need to compile your kernel w/out devfs and w/hotplug support. maybe this helps?
Jeremy
_______________________________________________ Clc-crux64 mailing list Clc-crux64@lists.berlios.de http://lists.berlios.de/mailman/listinfo/clc-crux64
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 I've experience the same error (I sent an email earlier on, but due to
Hi, On Wed, Mar 30, 2005 at 23:08:13 +0200, Lars Helmer wrote: [...] the problems with the mailing list, it didn't get through). Anyway, I think this is because you left 'sysfs' and 'proc' in your /etc/fstab. See the README for udev for more information, including Han Boetes fix for this: http://clc.morpheus.net:6999/clc/getfile/clc/udev/README?v=1.6 Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net
thank you. didn't work though... :( maybe the readme can help, will look into that next. cheers, lars On Mon, April 4, 2005 1:03 pm, Johannes Winkelmann said:
Hi,
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 I've experience the same error (I sent an email earlier on, but due to
On Wed, Mar 30, 2005 at 23:08:13 +0200, Lars Helmer wrote: [...] the problems with the mailing list, it didn't get through).
Anyway, I think this is because you left 'sysfs' and 'proc' in your /etc/fstab. See the README for udev for more information, including Han Boetes fix for this: http://clc.morpheus.net:6999/clc/getfile/clc/udev/README?v=1.6
Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net _______________________________________________ Clc-crux64 mailing list Clc-crux64@lists.berlios.de http://lists.berlios.de/mailman/listinfo/clc-crux64
ok, for the sake of simplicity, i'm rebuilding as close to an exact copy of 2.1rc1 as i can right now. using per's ports for 2.1rc1 i686, with some modification where necessary -- this one'll be strict crux, i.e. nptl, devfs, kernel 2.6.11.6, etc. also, i'm building this iso using a pkgmk wrapper script i've whipped up: pkgmk64. basically, what it does is looks for Pkgfile.x86_64, .footprint.x86_64, .md5sum.x86_64, and .nostrip.x86_64 in the port directory; if it find's any of those, it copies the original to <filename>.orig, copies <filename>.x86_64 to <filename>, runs pkgmk w/whatever args you pass to pkgmk64 (i.e. -f -d -u), then copies all the files back to their original states. so, for instance, if i have a port directory with: Pkgfile Pkgfile.x86_64 .footprint .footprint.x86_64 .md5sum .nostrip calling "pkgmk64 -d -u" in that directory does this: cp Pkgfile Pkgfile.orig cp Pkgfile.x86_64 Pkgfile cp .footprint .footprint.orig cp .footprint.x86_64 .footprint pkgmk -d -u cp Pkgfile Pkgfile.x86_64 cp Pkgfile.orig Pkgfile cp .footprint .footprint.x86_64 cp .footprint.orig .footprint rm *.orig not really elegant, but it allows me to keep all the vanilla crux stuff untouched, and just mess with what needs to be changed to work for x86_64. at any rate, this otta be done by the end of the week (working on this off & on) and should be quite a bit more straightforward (and less sloppy) that what i've done with this arch so far. On Tue, 2005-04-05 at 20:20 +0200, Lars Helmer wrote:
thank you.
didn't work though... :(
maybe the readme can help, will look into that next.
cheers,
lars
On Mon, April 4, 2005 1:03 pm, Johannes Winkelmann said:
Hi,
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 I've experience the same error (I sent an email earlier on, but due to
On Wed, Mar 30, 2005 at 23:08:13 +0200, Lars Helmer wrote: [...] the problems with the mailing list, it didn't get through).
Anyway, I think this is because you left 'sysfs' and 'proc' in your /etc/fstab. See the README for udev for more information, including Han Boetes fix for this: http://clc.morpheus.net:6999/clc/getfile/clc/udev/README?v=1.6
Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net _______________________________________________ Clc-crux64 mailing list Clc-crux64@lists.berlios.de http://lists.berlios.de/mailman/listinfo/clc-crux64
_______________________________________________ Clc-crux64 mailing list Clc-crux64@lists.berlios.de http://lists.berlios.de/mailman/listinfo/clc-crux64
this sounds really great. just post on the list when you've got something and i'll try it out. if you need any help just let me know and i see if i can be of any use... cheers, lars On Tue, April 5, 2005 11:24 pm, Jeremy Jones said:
ok, for the sake of simplicity, i'm rebuilding as close to an exact copy of 2.1rc1 as i can right now. using per's ports for 2.1rc1 i686, with some modification where necessary -- this one'll be strict crux, i.e. nptl, devfs, kernel 2.6.11.6, etc.
also, i'm building this iso using a pkgmk wrapper script i've whipped up: pkgmk64. basically, what it does is looks for Pkgfile.x86_64, .footprint.x86_64, .md5sum.x86_64, and .nostrip.x86_64 in the port directory; if it find's any of those, it copies the original to <filename>.orig, copies <filename>.x86_64 to <filename>, runs pkgmk w/whatever args you pass to pkgmk64 (i.e. -f -d -u), then copies all the files back to their original states.
so, for instance, if i have a port directory with:
Pkgfile Pkgfile.x86_64 .footprint .footprint.x86_64 .md5sum .nostrip
calling "pkgmk64 -d -u" in that directory does this:
cp Pkgfile Pkgfile.orig cp Pkgfile.x86_64 Pkgfile cp .footprint .footprint.orig cp .footprint.x86_64 .footprint pkgmk -d -u cp Pkgfile Pkgfile.x86_64 cp Pkgfile.orig Pkgfile cp .footprint .footprint.x86_64 cp .footprint.orig .footprint rm *.orig
not really elegant, but it allows me to keep all the vanilla crux stuff untouched, and just mess with what needs to be changed to work for x86_64.
at any rate, this otta be done by the end of the week (working on this off & on) and should be quite a bit more straightforward (and less sloppy) that what i've done with this arch so far.
On Tue, 2005-04-05 at 20:20 +0200, Lars Helmer wrote:
thank you.
didn't work though... :(
maybe the readme can help, will look into that next.
cheers,
lars
On Mon, April 4, 2005 1:03 pm, Johannes Winkelmann said:
Hi,
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 I've experience the same error (I sent an email earlier on, but due to
On Wed, Mar 30, 2005 at 23:08:13 +0200, Lars Helmer wrote: [...] the problems with the mailing list, it didn't get through).
Anyway, I think this is because you left 'sysfs' and 'proc' in your /etc/fstab. See the README for udev for more information, including Han Boetes fix for this: http://clc.morpheus.net:6999/clc/getfile/clc/udev/README?v=1.6
Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Bern, Switzerland http://jw.tks6.net _______________________________________________ Clc-crux64 mailing list Clc-crux64@lists.berlios.de http://lists.berlios.de/mailman/listinfo/clc-crux64
_______________________________________________ Clc-crux64 mailing list Clc-crux64@lists.berlios.de http://lists.berlios.de/mailman/listinfo/clc-crux64
_______________________________________________ Clc-crux64 mailing list Clc-crux64@lists.berlios.de http://lists.berlios.de/mailman/listinfo/clc-crux64
participants (4)
-
Jeremy Jones -
Johannes Winkelmann -
Lars Helmer -
lasso＠spacecentre.se