crux-amd64 iso (Was: Re: [Clc-crux64] newcomer) [RESENT]

Jeremy Jones jeremy at
Tue Apr 5 21:24:33 UTC 2005

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, 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:


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

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,
> >
> > On Wed, Mar 30, 2005 at 23:08:13 +0200, Lars Helmer wrote:
> > [...]
> >> 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
> > 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:
> >
> >
> > Kind regards, Johannes
> > --
> > Johannes Winkelmann              mailto:jw at
> > Bern, Switzerland      
> > _______________________________________________
> > Clc-crux64 mailing list
> > Clc-crux64 at
> >
> >
> _______________________________________________
> Clc-crux64 mailing list
> Clc-crux64 at

More information about the crux64 mailing list