README FILE FOR CRUX-X86_64 LINUX
	release 2.1
	April 25, 2005

INTRODUCTION

	crux-x86_64 is a port of CRUX Linux by Per Liden (http://www.crux.nu)
	for the x86_64 architecture.  It aims to keep as close to standard
	crux as possible, with as few changes as necessary to run in a 64-bit
	environment.

DOCUMENTATION
	
	For installation, usage and other information please refer to the
	CRUX handbook, available at CRUX Home Page or in the /crux directory
	of the crux-x86_64 cdrom.  Differences from the original CRUX Linux
	are discussed in the next section.

DIFFERENCES WITH CRUX

	Here is a small list of differences between CRUX and CRUX-X86_64:

	- All packages compiled with "-O2 -march=x86-64 -pipe -fPIC"

	- The directories /lib and /usr/lib are symlinks to /lib64 and
	  /usr/lib64, respectively.  This causes some minor issues with
	  the pkgutils utility:  specifically, running

		pkginfo -o /usr/lib64/some_lib.so

	  will tell you:

		pkginfo: no owner(s) found

	  Redirecting your query to /usr/lib/some_lib.so will yeild correct
	  results.

	- Where necessary, base and opt ports have been modified to build
	  properly on the x86_64 platform.  Where I have altered a port, it
	  is noted in the Pkgfile.

	- To use my modified repository of ports, you must install curl and
	  httpup.  The base-x86_64.httpup and opt-x86_64.httpup files, as
	  well as crux.cvsup and clc.cvsup, are installed by the ports 
	  package.  The x86_64-specific repositories will be downloaded to
	  /usr/ports/{base-x86_64,opt-x86_64}.  The prt-get packagae on the
	  cdrom will install a prt-get.conf file that reflects this.

	- To download the standard base, opt, contrib, and unmaintained 
	  repositories, you must either:

		1. Download the appropriate .httpup files from CLC
		2. Install my glibc32, zlib32, and cvsup32 ports

	  Taking the second option is recommended, as you will tend to get
	  more up-to-date ports this way.  Since cvsup will not build on
	  this platform presently (although the ezm3 folks are working on
	  the compile problems, from what I understand), I've simply 
	  repackaged pre-compiled libs and binary files from a standard
	  crux-2.1 installation.  Read on...

	- 32-bit compabibility libs can be installed.  See my glibc32 and
	  zlib32 ports.  More will follow.  Checking my ports repository
	  periodically will keep you up to date on 32-bit compatibility libs.
	  Currently, as stated above, I simply repackage stock crux-2.1
	  packages.  Once I get multilib capabilities figured out for gcc,
	  we'll probably be able to build these natively.  This would be
	  a Good Thing (tm).  32-bit libs go in /lib32 and /usr/lib32.

	- I've noticed several ports from contrib/unmaintained require a 
	  newer version of libungif than that installed by stock crux-2.1.
	  Version 4.1.3 is included here.

	- The emacs package is a development version.  The version on crux-2.1
	  for i686 won't compile for x86_64.

	- The bin86 package is a development version.  The version on crux-2.1
	  for i686 won't compile for x86_64.

	- Within the next few weeks, I plan to start contrib-x86_64 and 
	  unmaintained-x86_64 repositories, where CLC ports that require
	  patches or changes can be stored.  Please be warned, however:  I
	  will NOT try to keep up-to-date on a daily basis with these
	  repositories.  At best, you can expect weekly updates to some of
	  these ports.  Check at http://www.samnjack.com/crux-amd64/ for
	  new .httpup files between now and mid-May.  If you find you need
	  to alter Pkgfiles for anything in the CLC repositories, and you'd
	  like to share your changes with other x86_64 users, please e-mail
	  your Pkgfiles & patches to me.  PLEASE don't send me source
	  code or pre-compiled packages...

CHANGELOG

	Version 2.1rc1 and 2.1rc1.5 helped me get up to speed on what I'd have
	to do to maintain a parallel fork of crux for x86_64.  Version 2.1 
	should be considered the first "stable" release.  Users of 2.1rc1 and
	2.1rc1.5 can probably simply update their ports repositories and
	recompile changed packages to update.  But I ain't making any promises
	here.  To have a stable (ummm, maybe...) and up-to-date system, I
	recommend re-installing with the new iso if you've used one of the 
	release candidates.

BUGS, PROBLEMS, QUESTIONS

	Anyone with bug reports can contact me directly if they wish.  If
	you intend to use this distribution and want help, please subscribe
	to both the CRUX mailing list, at:
		https://mail.fukt.bth.se/cgi-bin/mailman/listinfo/crux/
	and the CRUX-AMD64 mailing list, at:
		http://lists.berlios.de/mailman/listinfo/clc-crux64
	If you think your problem is not specific to this architecture, you're
	best bet is to ask a question on the CRUX list.  If you have some
	suspicion that it's x86_64 specific, please don't clutter up the 
	CRUX list, use the CRUX-AMD64 list.

ME

	You can contact me by e-mail: jeremy at samnjack dot com

ACKNOWLEDGEMENTS

	Thanks to Per, of course.  Also, Mattias Hedenskog, whose original
	work with crux-2.0 and the amd64 I've shamelessly stolen.  And, finally
	thanks to those of you who tested my last couple releases.