Sponsored Content
Operating Systems Solaris Dual Booting - Solaris image CD doesn't read in BIOS Post 302504388 by Tenyhwa on Monday 14th of March 2011 12:42:35 PM
Old 03-14-2011
1) Check your machine by running a detection tool (usually found where HCL is) on it to see if Solaris 10 can be installed on it
2) If it is ok then make sure the CD you are using is okay to burn Solaris onto - This is also found at the same page
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Dual booting :-)

I have some problems with LILO/Grub... When I try to start Linux it says> EBDA too big How can I fix this problem? //Nevsky (2 Replies)
Discussion started by: Nevsky
2 Replies

2. UNIX for Dummies Questions & Answers

question about dual booting

question: 1. Which partioning wizard is better to use, System Commander V7.0, or Partition Magic V7.0? 2. Which version of linux is better to start with for beginners Mandrake, SuSe, or Corel? :) (4 Replies)
Discussion started by: CmpKillr
4 Replies

3. Solaris

Dual booting Linux and Solaris

Ok, so I'm a bit new to the whole Unix/Linux thing, but I'm no stranger to dual booting... However, the problem that I am having is that I am unable to create a dual boot with Unix (in this case I's using Sun Solaris 9.0 x86) and for linux either RH 9 or Mandrake 9.1, but for the purpose of just... (1 Reply)
Discussion started by: AndroidI6
1 Replies

4. Solaris

Dual Booting with UNIX

Dear All, I want use Unix (Sun Solaris 10) in my PC, and now I'm using windows, can Unix intalled to My PC and make dual booting like linux?? any one have experienced about this..? please help me..? Thank you for your help Regards, Heru (4 Replies)
Discussion started by: heru_90
4 Replies

5. Linux

Dual Booting issue

Hi Experts, I have windows XP and fedora core 3 in a PC i.e dual booting. I want to share some of the files in Windows Operating system to Linux(the other OS in the PC). How can i do it Thanks Shaan (2 Replies)
Discussion started by: shaan_dmp
2 Replies

6. UNIX for Dummies Questions & Answers

Dual Booting

I first had windows xp 64-bit installed on my system, and then installed fedora 10 on a partition (partition was created while installing fedora). When installation was completed, I could not boot on Windows or Fedora, I keep on getting this disc error and system asking to press ctrl+alt+del to... (0 Replies)
Discussion started by: lucianvibz
0 Replies

7. Ubuntu

Dual booting problem with XP-Pro

Hi Everyone, I was using XP-Home along with Ubuntu (dual booting) in my laptop. At the booting screen the Grub loader used to show me like this- Ubuntu Other operating system Inside 'Other operating system' I used to find 'XP- Home'. Oflate I installed XP-Professional and there I faced the... (2 Replies)
Discussion started by: adc22
2 Replies

8. SuSE

Dual booting suse 11.1 and XP

I'm running Tiny XP on my laptop and i'm wanting to dual boot it with OpenSUSE 11.1. can anyone guide me how to set it up or direct me to a site that could? thanks (2 Replies)
Discussion started by: brendanb
2 Replies

9. Red Hat

Dual Boot Problem - Vista & Redhat -Incorrect BIOS geometry

Hi Folks, Initially I had vista and redhat 9 .. due to some reasons i had to re instal my vista again.. since then the dual boot menu disappeared.. i tried to re install redhat and changing the boot configuration of redhat 9 but i am not getting both the OS back .. I am not aboe to boot linux... (2 Replies)
Discussion started by: subhotech
2 Replies

10. Red Hat

Dual booting problem

Hi all, I have an problem with dual booting. I installed windows7 and i want to install redhat linux on same system. When i insert the cd and boot with the cd it is not showing the hard drive. If i boot with hard disk its booting with windows7. But, if i boot with cdrom it is showing an... (7 Replies)
Discussion started by: mastansaheb
7 Replies
ATTILA(1)						  Alliance - attila User's Manual						 ATTILA(1)

NAME
attila - A Tool Installer SYNOPSIS
attila [ -h ] [ -S ] [ -U ] [ -F ] [ -A ] [ --help ] [ --ssh ] [ --user ] [ --asim ] [ --prefix=INSTALL_DIR ] [ --builddir=BUILD_DIR ] --tool=name1 [ --tool=name2... ] [ -c- configure_arg1 [ configure_arg2 ... ] ] [ -m- make_arg1 [ make_arg2... ] ] DESCRIPTION
attila automates the process of compiling and installing one or more Alliance tools. The tool can be installed either in the user's account (during the devellopment stage) or in the Alliance system wide tree (for instance /asim/alliance) when a new version is made avalaible to all. attila proceed with the following steps : 1. Checks if the sources of tools are present in the user's account. If not, check them out from the Alliance CVS tree. Note that you must have access to it. 2. In case of --asim or --full installations, attila will fork itself on one Linux computer (currently bip) and on one Solaris computer (beny). As to connect on thoses computer it will uses rsh so you must setup your ~/.rhosts to access them whithout passwords. You also can uses ssh (but the procedure to allow automatic login is more complicated). 3. Run autostuff for the tool in the ~/alliance/src directory. 4. Run configure in the build directory (see below). 5. Install the tool in the local install directory (see below) or in the system-wide Alliance directory rooted under /asim/alliance. After an --asim install: the build directory tree of the tool will be removed to avoid messing with further local installations. DIRECTORY STRUCTURE attila relies on the following tree structure : (all paths below are given relative to the user's home directory) o ~/alliance/src where the tools sources are to be found. o ~/alliance/Linux/build/$TOOL : the top directory under which the tool will be compiled for Linux. This is where the configure script will be run. o ~/alliance/Linux/install : the top of the install tree when the tool is compiled locally for Linux. Under this directory you will found (at least) : ./bin, ./lib and ./include. o ~/alliance/Solaris/build/$TOOL : the tool's build directory for Solaris. o ~/alliance/Solaris/install : top of the local install tree for Solaris. CVS CHECKOUT If the sources of the requested tool(s) are not found under ~/alliance/src/ attila will try to check them out. So, as says above, you must have access rights to the Alliance CVS tree. In addition to the tool(s) sources, it will also checks for the minimal set of files needed for configure to run. As for now : o autostuff o alliance.m4 o motif.m4 o Makefile.am GUESSING CVSROOT The root of the CVS tree will be set according to the following rules : 1. Uses the user's environment variable CVSROOT if sets. 2. Uses the attila default value sets in attila.conf (variable ATTILA_CVSROOT). GUESSING ALLIANCE_TOP The root of the Alliance installed distribution tree will be set according to the following rules : 1. Uses the user's environment variable ALLIANCE_TOP if sets. 2. Uses the attila default value sets in attila itself (variable ATTILA_ALLIANCE_TOP). ALLIANCE_TOP: is set in attila itself because its value is a prerequisite to load the configuration file attila.conf which is in the directory $ALLIANCE_TOP/etc/. ARGUMENTS
attila accepts the followings arguments : o -h, --help : print help. o -S, --ssh : uses ssh instead of rsh to connect to the remote computers (in case of --asim or --full). o -U, --user : perform a local installation. o -F, --full : install for all avalaibles architectures (currently Linux and Solaris). o -A, --asim : install in the system-wide directory (/asim/alliance). o --prefix=INSTALL_DIR : override the default installation directory. o --builddir=BUILD_DIR : override the default building directory. o --tool=name1 : name of the tool to be installed. o -c- configure_arg1 : all arguments following -c- (until a -m- is encountered) are passed as is to the subsequent call to configure. For example, if you want to first use your local libraries, give --enable-devel. If you want to link or install dynamic libraries, give --enable-alc-shared for alliance libraries and give --enable-shared for other libraries. o -m- make_arg1 : all arguments following -m- are passed as is to the subsequent call to make. If no -m- argument is given, then install is assumed. If you want to completly uninstall a tool and clean it's build directory you can pass uninstall clean CONFIGURATION FILE ATTILA.CONF The configuration file is located in $ALLIANCE_TOP/etc. This file is to be read by the sh shell. It sets up the following variables : o LINUX_TARGET : the computer where to compile for the Linux architecture (default bip). o LINUX_CC : the name or full path to to the C compiler for Linux system (default gcc3). o LINUX_CXX : the name or full path to to the C++ compiler for Linux system (default g++3). o SOLARIS_TARGET : the computer where to compile for the Solaris architecture (default beny). o SOLARIS_CC : the name or full path to to the C compiler for Solaris system (default /usr/local/gcc-3.0.4/bin/g++3). o SOLARIS_CXX : the name or full path to to the C++ compiler for Solaris system (default /usr/local/gcc-3.0.4/bin/g++3). o ATTILA_CVSROOT : the root of the Alliance CVS tree (default /users/outil/alliance/cvsroot). o CVS_STARTUP_FILES : the minimal set of files needed to run configure. EXAMPLES
Compile & install nero tool on the local computer (must be either a Linux or a Solaris one) : $ attila --tool=nero Compile & install nero tool for all architectures (currently only Linux and Solaris are supported) : $ attila --full --tool=nero Compile & install nero tool in the system-wide directory (a new version for everyone to use) : $ attila --asim --tool=nero Compile & install mbk then genlib (the order is significant) in a row for a local install on the current computer : $ attila --tool=mbk --tool=genlib Compile nero tool and link it against the locally installed libraries (if any). $ attila --tool=nero -c- --enable-devel Remove poire tool from the system-wide tree. (poire is the old name of nero). $ attila --asim --tool=poire -m- uninstall ASIM
/LIP6 13 October 2002 ATTILA(1)
All times are GMT -4. The time now is 09:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy