Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Difference between sun solaris and linux? Post 56475 by rhfrommn on Monday 4th of October 2004 10:15:36 AM
Old 10-04-2004
Solaris is a very high end commercial Unix. It is meant for running business applications, large databases like Oracle, and high end engineering graphics and other workstation apps like that. It isn't too appropriate for home use. It is overkill and also lacks some of the ease-of-use features that Linux offers.

If you are interested in learning about it download the free x86 version and give it a try, but if you're looking for your main OS to use I wouldn't suggest it for home.

If you want some details about their features go to www.sun.com. They are releasing Solaris 10 soon, so you can see lots of information about the features the new release will have. Some very interesting stuff like dtrace to watch the kernel as it runs for troubleshooting and performance purposes, zones which let you run completely independent instances of the OS on the same hardware concurrently, and lots of new security features.
This User Gave Thanks to rhfrommn For This Post:
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

What's the difference between Unix, Linux, and Solaris?

If anyone can tell me the difference between the three or where I can find more info I would appreciated it. I see alot of companies looking for people with knowledge in Unix but every time I try to find information about it I see Linux instead. Is there a market trend in these operating... (2 Replies)
Discussion started by: ITmommy
2 Replies

2. Programming

Difference in LINUX and SOLARIS

/* * one-way-pipe.c - example of using a pipe to communicate data between a * process and its child process. The parent reads input * from the user, and sends it to the child via a pipe. * The child prints the received data to the... (1 Reply)
Discussion started by: SQ4LIFE
1 Replies

3. UNIX for Dummies Questions & Answers

difference between AIX box and Sun Solaris box

Hi, I need a clarification. Is there any difference between AIX box and Sun Solaris box? The bzip command with -c option works in AIX box and the same does not work in Sun Solaris box. Can anyone please explain if there is an implementation difference in both these boxes for the shell... (1 Reply)
Discussion started by: nisha4680
1 Replies

4. Linux

Migrating from SENDMAIL on SUN SOLARIS to POSTFIX on Linux

Migrating from sendmail on SUN Solaris to POSTFIX on Linux. I have been asked to migrate our sendmail to postfix on Linux and would appreciate and information. Hints and tips on the process involved. Perhaps any links to useful site or documentation that you may know about. Many Thanks (2 Replies)
Discussion started by: Andrek
2 Replies

5. Shell Programming and Scripting

Array Difference Sun Vs Linux

Hi All, I have a script in which an array is defined. when i run that on Linux box its fine but when i run on SunOS its points to the line where array is defined as below : syntax error at line 9 : `(' unexpected array defined as ID=( ~Hog ~Todd ~Mike ) Thanks in advance (0 Replies)
Discussion started by: ravi.sadani19
0 Replies

6. Solaris

Vi in Linux Vs Sun Solaris

Hello All, there is some strange behaviour of VI editor while i am working in SunSolaris. I am trying to open a small file using vi abc.txt and it take around 5 mins for that file to open.. While i loggin to LINUX box which same profile and environment settings and opening the same file with vi... (3 Replies)
Discussion started by: ravi.sadani19
3 Replies

7. UNIX for Dummies Questions & Answers

UNIX, Linux and Sun Solaris Dummy

My name is Jimmy. My company support a client that using Sun Microsystems and Oracle. I'm totally zero knowledge about it. Only know installation a bit in Debian Linux and some commands. Do anyone here can help me at least some idea how to operate the Sun Microsystems. Please correct me if i'm... (14 Replies)
Discussion started by: jimmyysk
14 Replies

8. Shell Programming and Scripting

linux bash script to sun solaris

Hi guys, I seek a solution for this action for Sun solaris. find /sapmnt/${up}/global -prune -printf "%m %M %u %g %p\n" > $DAT1 The Application/Utilities in Sun Solaris are to old and cant understand "-printf". An update for Application/Utilities is exist, but not possible to implement... (6 Replies)
Discussion started by: ixibits
6 Replies
dpkg-architecture(1)						  dpkg utilities					      dpkg-architecture(1)

NAME
dpkg-architecture - set and determine the architecture for package building SYNOPSIS
dpkg-architecture [option...] [command] DESCRIPTION
dpkg-architecture does provide a facility to determine and set the build and host architecture for package building. The build architecture is always determined by an external call to dpkg(1), and can not be set at the command line. You can specify the host architecture by providing one or both of the options -a and -t. The default is determined by an external call to gcc(1), or the same as the build architecture if CC or gcc are both not available. One out of -a and -t is sufficient, the value of the other will be set to a usable default. Indeed, it is often better to only specify one, because dpkg-architecture will warn you if your choice does not match the default. COMMANDS
-l Print the environment variables, one each line, in the format VARIABLE=value. This is the default action. -edebian-architecture Check for equality of architecture. By default debian-architecture is compared against the current Debian architecture, being the host. This action will not expand the architecture wildcards. Command finishes with an exit status of 0 if matched, 1 if not matched. -iarchitecture-wildcard Check for identity of architecture by expanding architecture-wildcard as an architecture wildcard and comparing against the current Debian architecture. Command finishes with an exit status of 0 if matched, 1 if not matched. -qvariable-name Print the value of a single variable. -s Print an export command. This can be used to set the environment variables using eval. -u Print a similar command to -s but to unset all variables. -c command Execute a command in an environment which has all variables set to the determined value. -L Print a list of valid architecture names. -?, --help Show the usage message and exit. --version Show the version and exit. OPTIONS
-adebian-architecture Set the Debian architecture. -tgnu-system-type Set the GNU system type. -f Values set by existing environment variables with the same name as used by the scripts are honored (i.e. used by dpkg-architecture), except if this force flag is present. This allows the user to override a value even when the call to dpkg-architecture is buried in some other script (for example dpkg-buildpackage(1)). TERMS
build machine The machine the package is built on. host machine The machine the package is built for. Debian architecture The Debian architecture string, which specifies the binary tree in the FTP archive. Examples: i386, sparc, hurd-i386. architecture wildcard An architecture wildcard is a special architecture string that will match any real architecture being part of it. The general form is <kernel>-<cpu>. Examples: linux-any, any-i386, hurd-any. GNU system type An architecture specification string consisting of two parts separated by a dash: cpu and system. Examples: i386-linux-gnu, sparc-linux-gnu, i386-gnu, x86_64-netbsd. VARIABLES
The following variables are set by dpkg-architecture: DEB_BUILD_ARCH The Debian architecture of the build machine. DEB_BUILD_ARCH_OS The Debian system name of the build machine. DEB_BUILD_ARCH_CPU The Debian cpu name of the build machine. DEB_BUILD_ARCH_BITS The pointer size of the build machine (in bits). DEB_BUILD_ARCH_ENDIAN The endianness of the build machine (little / big). DEB_BUILD_GNU_CPU The CPU part of DEB_BUILD_GNU_TYPE. DEB_BUILD_GNU_SYSTEM The System part of DEB_BUILD_GNU_TYPE. DEB_BUILD_GNU_TYPE The GNU system type of the build machine. DEB_BUILD_MULTIARCH The clarified GNU system type of the build machine, used for filesystem paths. DEB_HOST_ARCH The Debian architecture of the host machine. DEB_HOST_ARCH_OS The Debian system name of the host machine. DEB_HOST_ARCH_CPU The Debian cpu name of the host machine. DEB_HOST_ARCH_BITS The pointer size of the host machine (in bits). DEB_HOST_ARCH_ENDIAN The endianness of the host machine (little / big). DEB_HOST_GNU_CPU The CPU part of DEB_HOST_GNU_TYPE. DEB_HOST_GNU_SYSTEM The System part of DEB_HOST_GNU_TYPE. DEB_HOST_GNU_TYPE The GNU system type of the host machine. DEB_HOST_MULTIARCH The clarified GNU system type of the host machine, used for filesystem paths. DEBIAN
/RULES The environment variables set by dpkg-architecture are passed to debian/rules as make variables (see make documentation). However, you should not rely on them, as this breaks manual invocation of the script. Instead, you should always initialize them using dpkg-architecture with the -q option. Here are some examples, which also show how you can improve the cross compilation support in your package: Retrieving the GNU system type and forwarding it to ./configure: DEB_BUILD_GNU_TYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) DEB_HOST_GNU_TYPE := $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) [...] configure --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE) Doing something only for a specific architecture: DEB_HOST_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH) ifeq ($(DEB_HOST_ARCH),alpha) [...] endif or if you only need to check the CPU or OS type, use the DEB_HOST_ARCH_CPU or DEB_HOST_ARCH_OS variables. Note that you can also rely on an external Makefile snippet to properly set all the variables that dpkg-architecture can provide: include /usr/share/dpkg/architecture.mk ifeq ($(DEB_HOST_ARCH),alpha) [...] endif In any case, you should never use dpkg --print-architecture to get architecture information during a package build. BACKWARD COMPATIBILITY
The /usr/share/dpkg/architecture.mk Makefile snippet is provided by dpkg-dev since version 1.16.1. The DEB_*_ARCH_BITS and DEB_*_ARCH_ENDIAN variables were introduced in dpkg-dev 1.15.4. Using them in debian/rules thus requires a build- dependency on dpkg-dev (>= 1.15.4). The DEB_HOST_ARCH_CPU and DEB_HOST_ARCH_OS variables were introduced in dpkg-dev 1.13.2. The -e and -i options were only introduced in relatively recent versions of dpkg-architecture (since dpkg 1.13.13). EXAMPLES
dpkg-buildpackage accepts the -a option and passes it to dpkg-architecture. Other examples: CC=i386-gnu-gcc dpkg-architecture -c debian/rules build eval `dpkg-architecture -u` Check if an architecture is equal to the current architecture or a given one: dpkg-architecture -elinux-alpha dpkg-architecture -amips -elinux-mips Check if the current architecture or an architecture provided with -a are Linux systems: dpkg-architecture -ilinux-any dpkg-architecture -ai386 -ilinux-any FILES
All these files have to be present for dpkg-architecture to work. Their location can be overridden at runtime with the environment variable DPKG_DATADIR. /usr/share/dpkg/cputable Table of known CPU names and mapping to their GNU name. /usr/share/dpkg/ostable Table of known operating system names and mapping to their GNU name. /usr/share/dpkg/triplettable Mapping between Debian architecture triplets and Debian architecture names. SEE ALSO
dpkg-buildpackage(1), dpkg-cross(1). Debian Project 2012-01-20 dpkg-architecture(1)
All times are GMT -4. The time now is 06:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy