(redirected from Main.Faq)
Table of contents
Original author: The CRUX Team
Maintained by: Jonathan Asghar
Sorry, there's no interesting story behind the name. Per chose it simply because he thought it sounded cool, it was short, it was fairly easy to remember and it had the mandatory X in the end to make it UNIX/Linux-ish ;)
Well, the standard answer to this question is “when it's done”. New versions are however usually released every 3 or 4 months. Between releases, updated packages are made available through the ports system.
None of the above. It's called CRUX, no more no less.
No, that's incorrect. CRUX was built from scratch and has never been based on any other Linux distribution.
Most of the developers and users prefer mailing lists over forums. It's much simpler to follow discussion when using a mailing list--forums require constant polling if you are trying to stay up to date about what's happening.
First off try searching the mailing lists. Browsing the archives (marc.theaimsgroup.com provides a nice, searchable archive) is always a good way to start. If that doesn't work, try asking in one of the IRC channels.
Create ports and maintain a repository of your own, help people on the mailing list and in the IRC channels and write documentation.
Maintain a personal port repository for a while, make sure that your ports adhere to the port guidelines and contact the CRUX team.
Yes and No. AMD K6, K6-II and K6-III have an i586 (Pentium) compatible instruction set. Packages on the official CRUX ISO are compiled with -march=i686, which means that CRUX requires a processor which has an i686 compatible instruction set (i.e. Intel PPro/Celeron/PII/PIII/P4 or AMD K7/Athlon). However, Jürgen Daubert maintains an i586 version of the CRUX ISO image which can be found here. The i586 version of the CRUX ISO works on AMD K6/K6-II/K6-III.
This can happen if you have more than one CD-ROM drive. Make sure you boot from then "first" CD-ROM drive, i.e. /dev/cdroms/cdrom0. If you must boot from a different drive (i.e. not the first one) you can still do that but you have to type CRUX root=/dev/cdroms/cdrom1 at the boot prompt (cdrom1 indicates that it is the second drive, cdrom2 that it is the third, and so on).
You most likely forgot to enable devfs or didn't tell the kernel to mount devfs at boot. The installation instructions (Handbook Section 2.2, “Installing From CD-ROM”) tell you how to enable it.
You most likely forgot to edit /mnt/etc/fstab before you rebooted or you entered the wrong name of your new root partition at the boot prompt.
Create a httpup repository and register it with the ports database. Basically you just make a directory which contains your ports, run httpup-repgen <directory> to generate an index file and upload the directory in your personal web space. It's as simple as that. More detailed infos here.
Install httpup and put the corresponding .httpup file in your /etc/ports directory. Running ports -u should now make the ports available in /usr/ports/<repository>. If you are using prt-get, you might want to add the port directory to /etc/prt-get.conf e.g. prtdir /path/to/repository.
Use prt-get (depends or deptree to check the dependencies and depinst to actually install them) from the opt tree (opt/prt-get).
Follow the instructions for either GNOME? or KDE.
prt-utils is a good place to start and have a look at our ToolsAndScripts page.
Have a look at our httpup page.
If the port is from the core, base or opt collections, this is considered a bug. Feel free to report it using the ticket system. Please make sure there isn't already a bug report for this version difference. Also note that all CRUX team members only work on CRUX in their free time, so the respective person might already know about the new version (submitting a bug report an hour after the release doesn't make any sense).
A good "new version out" bug report also contains a note whether it is enough to just update the version in the Pkgfile. Important: If the update is security related, please contact the port maintainer directly (and immediately).
It seems to be a problem with the round-robin DNS that SourceForge uses. The best way to fix it is by editing /etc/hosts and making an alias to a mirror that is closest to you.
For example, to use the heanet mirror:
193.1.193.66 download.sourceforge.net download.sf.net dl.sourceforge.net dl.sf.net
You forgot to install the opt/cvsup package. You will find it on the CRUX ISO (under /crux/opt/).
Edit /etc/pkgmk.conf. Change this part:
# PKGMK_SOURCE_DIR="$PWD" # PKGMK_PACKAGE_DIR="$PWD" # PKGMK_WORK_DIR="$PWD/work"
To this:
PKGMK_SOURCE_DIR="/usr/ports/distfiles"
PKGMK_PACKAGE_DIR="/usr/ports/packages"
PKGMK_WORK_DIR="/usr/ports/work/${PWD##*/}"
Finally create the directories:
# mkdir /usr/ports/{distfiles,packages,work}
Have a close look at the mismatch. If there are lots of new files, it's probably just because you have some software installed the packager didn't, which is no problem at all. In this case, just ignore or update the footprint (see the pkgmk manpage) and install it. If you're missing a lot of files, make sure you have all dependencies installed. Also make sure you built the package as root.
The md5sum is a security feature, so you shouldn't just ignore this one. The package you downloaded could be manipulated. But there are other reasons why this can happen, without a malicious action: the download might have failed (try to decompress the tarball to see whether is is corrupt), or the requested file might have been changed on the server without its name being changed; this usually happens for things like theme-packs which change constantly without getting another name.
You have to edit /etc/hosts.deny and/or /ets/hosts.allow to specify which hosts are allowed/denied access. To allow anyone to connect to your machine you can add sshd: ALL to /etc/hosts.allow. See the hosts_access(5) man-page for further information about the file format. When this is done you can start sshd by entering the command /etc/rc.d/sshd start and/or edit /etc/rc.conf and add sshd to the SERVICES array, i.e. SERVICES=(... sshd ...), which means that sshd will be started when the system boots.
If you need something off of the CD, you can grab the base install packages from core and opt (provided by Matt Housh) or core and opt (provided by Tilman Sauerbeck). Either should work
If you are using the binary NVidia driver (opt/nvidia) for xorg, keep in mind to run the gl-select tool after installation to set up your OpenGL environment, as pointed out in the README file. X dying like this happens not only with openoffice but most of the glx stuff such as childsplay, showfont etc.