Clifford Wolf
20 years ago
7 changed files with 0 additions and 264 deletions
Split View
Diff Options
-
+0 -55architecture/powerpc/faq/rs6k_20_openfirmware.faq75
-
+0 -20misc/faq/about_rock.faq00
-
+0 -13misc/faq/about_thisfaq.faq01
-
+0 -25misc/faq/faq.faq99
-
+0 -19misc/faq/otherdocs.faq02
-
+0 -54package/base/mine/pkg_management.faq15
-
+0 -78scripts/Puzzle
@ -1,55 +0,0 @@ |
|||
|
|||
Q: How do I boot Linux on an RS/6000 (OpenFirmware) |
|||
|
|||
Build the kernel with "make zImage" and use "arch/ppc/boot/images/ |
|||
zImage.chrp-rs6k" as kernel image for booting your RS/6000. |
|||
|
|||
If you are running your RS/6000 on a serial console, remember to set your |
|||
terminal program to 9600 Bps (8N1). Read Documentation/serial-console.txt |
|||
for the linux kernel sources for details on how to let the kernel use a |
|||
serial console. |
|||
|
|||
Enter the OpenFirmware (can be done by pressing 'F8' on startup when using |
|||
the VGA console or just '8' on a serial console). The RS/6000 BIOS calls the |
|||
OpenFirmware prompt the "OK Prompt". Put the kernel image on a floppy with |
|||
MS-DOS FAT filesystem. Use a filename like "zimage" without extension. The |
|||
RS/6000 OpenFirmware doesn't know about long file names on a DOS floppy. Boot |
|||
the kernel with: |
|||
|
|||
boot floppy:,<filename> <kernel-options> |
|||
|
|||
e.g.: |
|||
|
|||
0 > boot floppy:,zimage root=/dev/discs/disc1/part3 |
|||
|
|||
Note that 'floppy' is a device-alias. |
|||
|
|||
Other useful commands: |
|||
|
|||
printenv shows the current contents of the variables |
|||
dev / ls shows the device tree |
|||
devalias shows the device aliases and the OpenFirmware pathnames |
|||
|
|||
setenv variable value set the content of the variable |
|||
reset-all restart the machine |
|||
shut-down power off the machine |
|||
|
|||
If you want to permanently boot a linux kernel from the OpenFirmware, create |
|||
a small partition of the 'PPC PReP Boot' (Id 41) partition type for it and |
|||
write the kernel image directly to the partition block device: |
|||
|
|||
# dd if=/mnt/zImage of=/dev/discs/disc0/part1 |
|||
|
|||
Now reboot to the OpenFirmware prompt (F8 again) and type: |
|||
|
|||
0 > setenv boot-device disk:1 |
|||
0 > setenv boot-file root=/dev/discs/disc0/part2 |
|||
|
|||
now you con boot with |
|||
|
|||
0 > boot |
|||
|
|||
and if you don't enter the OpenFirmware (F8) on further reboots this kernel |
|||
will automatically be loaded. If you need any other kernel parameters, just |
|||
append them to the 'setenv boot-file ..' line. |
|||
|
|||
@ -1,20 +0,0 @@ |
|||
|
|||
Q: What is ROCK Linux |
|||
|
|||
ROCK Linux is a distribution development kit. People can use it to build their |
|||
own Linux distributions. There are two ways of customizing the build of a |
|||
new distribution in ROCK Linux: |
|||
|
|||
1. The Configuration. ROCK Linux has a powerfull configuration |
|||
system which gives the user full control over a wide range of |
|||
options used during the build. This includes stuff like selecting |
|||
the CPU optimisation, compiler, c-library, various install |
|||
prefixes, packages to build or not to build, etc. |
|||
|
|||
2. The ROCK Linux build system is designed to be flexible, open and |
|||
easy to extend. So if any option is missing it's easy to add it. |
|||
|
|||
So there are two groups of ROCK Linux users: Those who are using a ROCK Linux |
|||
based distribution and those who are using the ROCK Linux build system for |
|||
building distributions. |
|||
|
|||
@ -1,13 +0,0 @@ |
|||
|
|||
Q: What is this FAQ |
|||
|
|||
This FAQ is mostly covering installing and using a ROCK Linux based |
|||
distribution which is build with the default-settings. |
|||
|
|||
So the distribution you are using might be entirely diffrent from what we |
|||
do cover here. Most special-purpose distributions (like single-floppy systems) |
|||
do belong to this category (such special distributions are called `targets' |
|||
in ROCK Linux). |
|||
|
|||
An extra section in this FAQ is just handling those targets. |
|||
|
|||
@ -1,25 +0,0 @@ |
|||
|
|||
Q: How is this FAQ generated |
|||
|
|||
This FAQ is generated with the ./scripts/Puzzle script using *.faq[0-9][0-9] |
|||
files from architecture/, package/, target/ and misc/ in the ROCK Linux |
|||
sources. |
|||
|
|||
The the first number after *.faq in the filename specifies an FAQ section, |
|||
the second number the position within the section. The following sections |
|||
are defined at the moment: |
|||
|
|||
0 Generic information about ROCK Linux |
|||
1 Installation and administration |
|||
2 Configuring the hardware (X11, PC-Cards, ...) |
|||
3 Server applications (setup and infos) |
|||
4 User applications (setup and infos) |
|||
5 Reseverd |
|||
6 Reseverd |
|||
7 Architectures |
|||
8 Targets and special-purpose systems |
|||
9 Building ROCK Linux |
|||
|
|||
Every FAQ file should only cover one question and should have one empty line |
|||
at the begin and one the end of the file. |
|||
|
|||
@ -1,19 +0,0 @@ |
|||
|
|||
Q: Where do I find documentation for ROCK Linux |
|||
|
|||
The documentation which comes with the ROCK Linux sources (mostly developers |
|||
documentation and documentation about building distributions using ROCK Linux) |
|||
can be found at /usr/doc/ROCK installed on the system, in Documentation/ as |
|||
part of the source tar.bz2 file and at |
|||
|
|||
http://www.rocklinux.org/sources/Documentation/ |
|||
|
|||
on the web. This also includes this FAQ. The "ROCK Linux Guide" (something |
|||
like the ROCK Linux user manual) can be found at |
|||
|
|||
http://www.rocklinux.org/guide.html |
|||
|
|||
Documentation about the software running on the system can be found in the |
|||
directory /usr/doc on the system as well as in the `man' and `info' pages |
|||
and in this FAQ. |
|||
|
|||
@ -1,54 +0,0 @@ |
|||
|
|||
# --- ROCK-COPYRIGHT-NOTE-BEGIN --- |
|||
# |
|||
# This copyright note is auto-generated by ./scripts/Create-CopyPatch. |
|||
# Please add additional copyright information _after_ the line containing |
|||
# the ROCK-COPYRIGHT-NOTE-END tag. Otherwise it might get removed by |
|||
# the ./scripts/Create-CopyPatch script. Do not edit this copyright text! |
|||
# |
|||
# ROCK Linux: rock-src/package/base/mine/pkg_management.faq15 |
|||
# ROCK Linux is Copyright (C) 1998 - 2003 Clifford Wolf |
|||
# |
|||
# This program is free software; you can redistribute it and/or modify |
|||
# it under the terms of the GNU General Public License as published by |
|||
# the Free Software Foundation; either version 2 of the License, or |
|||
# (at your option) any later version. A copy of the GNU General Public |
|||
# License can be found at Documentation/COPYING. |
|||
# |
|||
# Many people helped and are helping developing ROCK Linux. Please |
|||
# have a look at http://www.rocklinux.org/ and the Documentation/TEAM |
|||
# file for details. |
|||
# |
|||
# --- ROCK-COPYRIGHT-NOTE-END --- |
|||
|
|||
Q: How is package management working in ROCK Linux |
|||
|
|||
ROCK Linux has two binary package formats: *.gem files and plain *.tar.bz2 |
|||
files. The GEM package format is just an envelope for *.tar.bz2 packages. |
|||
|
|||
The program 'mine' is used to install, update and remove packages from the |
|||
system. More information about 'mine' can be found at /usr/share/doc/mine. |
|||
|
|||
Some examples for using mine: |
|||
|
|||
mine -i xine.gem .............. install or update the 'xine' package |
|||
mine -r xine .................. remove the 'xine' package |
|||
|
|||
mine -l xine.gem m4 ........... print file list for xine.gem and for |
|||
the already installed m4 package |
|||
|
|||
mine -q ....................... list all installed packages |
|||
|
|||
The shell script 'tarbz2gem' can be used for creating a gem package from a |
|||
tar.bz2 file. Extracting the tar.bz2 file from the gem package is possible |
|||
with 'mine' itself. Examples: |
|||
|
|||
tarbz2gem xine.tar.bz2 xine.gem |
|||
|
|||
mine -k package_tarbz2 xine.gem > xine.tar.bz2 |
|||
|
|||
The package metadata is stored in the /var/adm tree using plain ascii files. |
|||
|
|||
You should always run the script 'cron.run' after installing, updating or |
|||
removing packages. This updates some important system files. |
|||
|
|||
@ -1,78 +0,0 @@ |
|||
#!/bin/bash |
|||
# |
|||
# --- ROCK-COPYRIGHT-NOTE-BEGIN --- |
|||
# |
|||
# This copyright note is auto-generated by ./scripts/Create-CopyPatch. |
|||
# Please add additional copyright information _after_ the line containing |
|||
# the ROCK-COPYRIGHT-NOTE-END tag. Otherwise it might get removed by |
|||
# the ./scripts/Create-CopyPatch script. Do not edit this copyright text! |
|||
# |
|||
# ROCK Linux: rock-src/scripts/Puzzle |
|||
# ROCK Linux is Copyright (C) 1998 - 2003 Clifford Wolf |
|||
# |
|||
# This program is free software; you can redistribute it and/or modify |
|||
# it under the terms of the GNU General Public License as published by |
|||
# the Free Software Foundation; either version 2 of the License, or |
|||
# (at your option) any later version. A copy of the GNU General Public |
|||
# License can be found at Documentation/COPYING. |
|||
# |
|||
# Many people helped and are helping developing ROCK Linux. Please |
|||
# have a look at http://www.rocklinux.org/ and the Documentation/TEAM |
|||
# file for details. |
|||
# |
|||
# --- ROCK-COPYRIGHT-NOTE-END --- |
|||
# |
|||
# The following files get created: |
|||
# |
|||
# Documentation/FAQ |
|||
# Documentation/LSM |
|||
# download/INDEX |
|||
# |
|||
|
|||
eval "`grep -A 10 '\[BEGIN\]' scripts/parse-config | grep -B 10 '\[END\]'`" |
|||
rockver="`echo $rockver | sed 's,-DEV,,'`" |
|||
|
|||
echo "Creating Documentation/FAQ ..." |
|||
# |
|||
find architecture/. misc/. package/. target/. -name '*.faq[0-9][0-9]' | \ |
|||
sed 's,^.*\(..\)$,\1 &,' | sort | cut -f2 -d' ' | xargs cat > Documentation/FAQ |
|||
|
|||
echo "Creating Documentation/LSM ..." |
|||
# |
|||
cat > Documentation/LSM << EOF |
|||
Begin3 |
|||
Title: ROCK Linux |
|||
Version: $rockver |
|||
Entered-date: `date` |
|||
Description: ROCK Linux is a Linux distribution build kit designed for |
|||
Linux Users and Administrators and to create custom distri- |
|||
butions e.g. for embedded systems. ROCK Linux features a |
|||
automated build system implemented in shell-scripts. This |
|||
build system will also download the vanilla package sources |
|||
from the internet, (cross-)compile them, build the |
|||
package files and create a CD-ROM image. |
|||
ROCK Linux is a small Linux Distribution, but is't not a "mini |
|||
distribution". It comes with over 800 packages including X11 |
|||
and the KDE and GNOME Desktop. |
|||
The ROCK Linux Homepage is http://www.rocklinux.org/. |
|||
Keywords: Distribution Linux Admin |
|||
Author: god@clifford.at (Clifford Wolf) |
|||
Primary-site: gd.tuwien.ac.at opsys/linux/ROCK/ |
|||
Platforms: Alpha, PPC, SPARC, MIPS, ia64, x86, x86_64 |
|||
Copying-policy: GPL |
|||
End |
|||
EOF |
|||
|
|||
echo "Creating download/INDEX ..." |
|||
mkdir -p download/{mirror,nodist} |
|||
{ |
|||
echo "# This directory contains the package sources. They don't come" |
|||
echo "# with the rock-linux source distribution - so you need to download" |
|||
echo "# them. Type './scripts/Help Download' for details." ; echo "#" |
|||
|
|||
./scripts/Download -list-cksums | |
|||
tr ' ' '\t' | tr -s '\t' | sort -k2 | |
|||
awk '$1 !~ /^XX*$/ { printf("%010.0f %-50s %s\n", $1, $2, $3); } |
|||
$1 ~ /^XX*$/ { printf("XXXXXXXXXX %-50s %s\n", $2, $3); }' |
|||
} > download/INDEX |
|||
|
|||