ARCLoad - Revision history

Onion: SGI Category

2010-10-18T10:58:01Z

SGI Category

Jblache: Make the list of supported machines exhaustive

2007-09-04T12:38:03Z

Make the list of supported machines exhaustive

Jblache: /* Downloading and building */

2007-08-31T13:10:02Z

‎Downloading and building

Ralf: Add to ARC category.

2006-05-17T11:04:10Z

Add to ARC category.

Ralf: Link to Load64

2006-05-15T16:22:22Z

Link to Load64

Psi29a: /* Usage */ changed and to or.

2006-04-06T13:07:47Z

‎Usage: changed and to or.

Psi29a: /* Usage */ I ran into this problem where OSLoader was set to something else, due to fooling around with arcboot. Since it wasn't documented, I figured this tid-bit should be in here as well.

2006-04-06T13:06:18Z

‎Usage: I ran into this problem where OSLoader was set to something else, due to fooling around with arcboot. Since it wasn't documented, I figured this tid-bit should be in here as well.

Alec v: links

2006-01-29T14:59:05Z

links

Skylark: Let us Rejoice, for today the Filesystems arrived! I hope they work.

2006-01-20T05:32:40Z

Let us Rejoice, for today the Filesystems arrived! I hope they work.

Skylark: path convention for ARCLoad

2006-01-17T18:11:28Z

path convention for ARCLoad

← Older revision		Revision as of 10:58, 18 October 2010
Line 134:		Line 134:

	[[Category:ARC]]		[[Category:ARC]]
		+	[[Category:SGI]]

@@ Line 1: / Line 1: @@
 == General ==
-ARCLoad was built to load any Linux kernel on any SGI/ARCS machine. Therefore, it currently supports:
+ARCLoad was built to load any Linux kernel on any SGI/ARCS machine. It currently supports:
-* SGI [[IP22|Indy]]
+* [[IP22|IP22]]: SGI Indy, SGI Indigo2, SGI Challenge S
-* SGI [[IP27|Origin]]
+* [[IP27|IP27]]: SGI Origin200, SGI Origin2000, Onyx2
-* SGI [[IP28|Indigo2 R10000]]
+* [[IP28|IP28]]: SGI Indigo2 R10000
-* SGI [[IP30|Octane]]
+* [[IP30|IP30]]: SGI Octane, SGI Octane2
-* SGI [[IP32|O2]]
+* [[IP32|IP32]]: SGI O2
 == Paths and filesystems ==

@@ Line 87: / Line 87: @@
 ARCLoad can be found at [ftp://ftp.linux-mips.org/pub/linux/mips/people/skylark/arcload-0.5.tar.bz2 Linux-MIPS]. Building it requires only a single setting in the Makefile: the ''MODE''. If it is set to ''M64'', a 64-bit ARCLoad binary will be built (for ip27, ip28 and ip30). If it is set to ''M32'', a 32-bit ARCLoad binary will be built (for ip22 and ip32). It is possible to place those binaries under the names of 'sash64' and 'sashARCS', respectively; in this case, it will be possible to use the ''Install New Software'' option in ARCS PROM to run the appropriate binary on any SGI machine.
-There is a patch for gcc, not available yet, that causes ARCLoad to skip the warning message on startup on M64 machines. It is related to a particularly obscure bug in GCC that affected nested function calls by function variable on 64-bit MIPS systems which don't use compatibility segments. :)
+There is a [ftp://ftp.linux-mips.org/pub/linux/mips/people/skylark/gcc-4.0.2-mips64tramp-fix.diff patch for gcc] < 4.2 (see also [http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25871 GCC PR 25871]), that causes ARCLoad to skip the warning message on startup on M64 machines. It is related to a particularly obscure bug in GCC that affected nested function calls by function variable on 64-bit MIPS systems which don't use compatibility segments. This bug has been fixed in gcc >= 4.2.
 == Usage ==

← Older revision		Revision as of 11:04, 17 May 2006
Line 132:		Line 132:
	== See also ==		== See also ==
	* [[Load64]] ARCLoad's now obsolete ancestor.		* [[Load64]] ARCLoad's now obsolete ancestor.
		+
		+	[[Category:ARC]]

← Older revision		Revision as of 16:22, 15 May 2006
Line 129:		Line 129:

	setenv OSLoadFilename ip28(new,debug)		setenv OSLoadFilename ip28(new,debug)
		+
		+	== See also ==
		+	* [[Load64]] ARCLoad's now obsolete ancestor.

@@ Line 91: / Line 91: @@
 == Usage ==
-As mentioned above, kernels are loaded from the location specified by the ''OSLoadPartition'' environment variable (if ''image system'' is used), and options are selected using the ''OSLoadFilename'' environment variable. The loaders mentioned above ('sash64' and 'sashARCS') need to also be set in the ''OSLoader'' environment variable, this should be default, however if it could have changed.
+As mentioned above, kernels are loaded from the location specified by the ''OSLoadPartition'' environment variable (if ''image system'' is used), and options are selected using the ''OSLoadFilename'' environment variable. The loaders mentioned above ('sash64' or 'sashARCS') needs to also be set in the ''OSLoader'' environment variable, this should be default, however if it could have changed.
 Suppose you have an arc.cf like the following:

@@ Line 11: / Line 11: @@
 == Paths and filesystems ==
-Filesystem support in ARCLoad is based on GNU GRUB filesystem code. The approach taken is somewhat more general than the common one (disk - filesystem - file), namely there is no difference between a partition and a file. This means that filesystems can be nested (e.g. loading kernels from ISO images). Kernels and configuration files are also loadable from the DVH (disk volume header). ARCLoad can also load kernels from a TFTP server, so a network-based install is possible.
+Filesystem support in ARCLoad is based on GNU GRUB filesystem code. The approach taken is somewhat more general than the common one (disk - filesystem - file), namely there is no difference between a partition and a file. This means that filesystems can be nested (e.g. loading kernels from ISO images). Kernels and configuration files are also loadable from the DVH ([[Disk Volume Header]]). ARCLoad can also load kernels from a [[TFTP]] server, so a network-based install is possible.
 A file path is defined as:
@@ Line 31: / Line 31: @@
   bootp():/vmlinux
-ARCLoad is always built into a relocatable binary: ELF64 on 64-bit platforms, ECOFF on 32-bit platforms. ARCLoad has its own ELF32 to ECOFF converter in the source package.
+ARCLoad is always built into a relocatable binary: [[ELF|ELF64]] on 64-bit platforms, [[ECOFF]] on 32-bit platforms. ARCLoad has its own ELF32 to ECOFF converter in the source package.
 == Configuration file ==

@@ Line 9: / Line 9: @@
 * SGI [[IP32|O2]]
-Currently ARCLoad does not support any filesystems by itself. It can load the kernels (and also its configuration file) from any place the PROM can access. Therefore, kernels are not loadable from ext2 partitions; they are loadable from xfs/efs partitions on some machines (notably IP27); they are also loadable from the DVH (disk volume header). ARCLoad can also load kernels from a TFTP server, so a network-based install is possible.
+== Paths and filesystems ==
-The current proposition for supporting filesystems is based on GNU GRUB filesystem code. The approach taken is somewhat more general than the common one (disk - filesystem - file), namely there is no difference between a partition and a file. This means that filesystems can be nested. It is not useful. It is just a side effect. :)
+Filesystem support in ARCLoad is based on GNU GRUB filesystem code. The approach taken is somewhat more general than the common one (disk - filesystem - file), namely there is no difference between a partition and a file. This means that filesystems can be nested (e.g. loading kernels from ISO images). Kernels and configuration files are also loadable from the DVH (disk volume header). ARCLoad can also load kernels from a TFTP server, so a network-based install is possible.
-A file path will be defined as:
+A file path is defined as:
   <file path> := <arc path> | <file path> '[' <fs name> ']' <fs path>
 Therefore, an kernel on the root partition can be accessed by:
-  xio(0)pci(15)scsi(0)disk(1)rdisk(0)partition(8)[ext2]/boot/vmlinux
+  xio(0)pci(15)scsi(0)disk(1)rdisk(0)partition(0)[ext2]/boot/vmlinux
 ARCLoad is always built into a relocatable binary: ELF64 on 64-bit platforms, ECOFF on 32-bit platforms. ARCLoad has its own ELF32 to ECOFF converter in the source package.
@@ Line 25: / Line 35: @@
 == Configuration file ==
-The text configuration file is named 'arc.cf' and loaded from the place pointed to by the 'SystemPartition' environment variable. ARCLoad reads the file and executes it in order. The configuration file is structured into ''options'' that can be nested. Comments begin with a '#' and are discarded (duh).  Options are selected by the 'OSLoadFilename' environment variable.
+The text configuration file is named 'arc.cf' and loaded from the place pointed to by the ''OSLoadPartition'' environment variable. ARCLoad reads the file and executes it in order. The configuration file is structured into ''options'' that can be nested. Comments begin with a '#' and are discarded (duh).  Options are selected by the ''OSLoadFilename'' environment variable.
 An ''option'' looks like this:
@@ Line 61: / Line 71: @@
   image absolute "filename";
-Sets the kernel image to be loaded. If "filename" is empty (""), the option is deemed to be unsupported. The ''system'' option directs ARCLoad to prepend the contents of 'SystemPartition' to the filename, while the ''absolute'' option exists only for completeness as it is the same as default.
+Sets the kernel image to be loaded. If "filename" is empty (""), the option is deemed to be unsupported. The ''system'' option directs ARCLoad to prepend the contents of ''OSLoadPartition'' to the filename, while the ''absolute'' option exists only for completeness as it is the same as default.
   append "arg1" "arg2";
@@ Line 75: / Line 85: @@
 == Downloading and building ==
-ARCLoad can be found at [ftp://ftp.linux-mips.org/pub/linux/mips/people/skylark/arcload-0.43.tar.bz2 Skylark's site]. Building it requires only a single setting in the Makefile: the ''MODE''. If it is set to ''M64'', a 64-bit ARCLoad binary will be built (for ip27, ip28 and ip30). If it is set to ''M32'', a 32-bit ARCLoad binary will be built (for ip22 and ip32). It is possible to place those binaries under the names of 'sash64' and 'sashARCS', respectively; in this case, it will be possible to use the ''Install New Software'' option in ARCS PROM to run the appropriate binary on any SGI machine.
+ARCLoad can be found at [ftp://ftp.linux-mips.org/pub/linux/mips/people/skylark/arcload-0.5.tar.bz2 Linux-MIPS]. Building it requires only a single setting in the Makefile: the ''MODE''. If it is set to ''M64'', a 64-bit ARCLoad binary will be built (for ip27, ip28 and ip30). If it is set to ''M32'', a 32-bit ARCLoad binary will be built (for ip22 and ip32). It is possible to place those binaries under the names of 'sash64' and 'sashARCS', respectively; in this case, it will be possible to use the ''Install New Software'' option in ARCS PROM to run the appropriate binary on any SGI machine.
 == Usage ==
-As mentioned above, kernels are loaded from the location specified by the ''SystemPartition'' environment variable, and options are selected using the ''OSLoadFilename'' environment variable.
+As mentioned above, kernels are loaded from the location specified by the ''OSLoadPartition'' environment variable (if ''image system'' is used), and options are selected using the ''OSLoadFilename'' environment variable.
 Suppose you have an arc.cf like the following: