Need RHEL/CentOS 7 'Little Endian' ISO for PowerPC

Operating Systems Linux Red Hat Need RHEL/CentOS 7 'Little Endian' ISO for PowerPC

09-22-2016

Registered User

70, 1

Join Date: Oct 2011

Last Activity: 19 September 2017, 11:33 AM EDT

Location: Hyderabad, Bharath

Posts: 70

Thanks Given: 4

Thanked 1 Time in 1 Post

Need RHEL/CentOS 7 'Little Endian' ISO for PowerPC

Hi!

One of our clients need RHEL 7 on PPC hardware for their R&D setup and they are particular about this being 'Little Endian'.

The problem is that Redhat doesn't have LE RHEL7 images below 7.1 while the latest toolkit (which is needed while reimaging an IBM LPAR) that IBM provides only works upto 7.0

I've be churning the web for hours together but in vain. Could anyone please shed some light here?

satish51392111

View Public Profile for satish51392111

Find all posts by satish51392111

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

RHEL Linux 6.2 to 7.3 - Bootable iso

Hi All On one of my sandbox machine, I want to replace RHEL 6.2 to RHEL 7.3. I am using both developer editions. rhel-server-7.3-x86_64-dvd.iso ... This is what I have downloaded from Red Hat Enterprise Linux Download | Red Hat Developers My understanding is this file would work as a...

2. Red Hat

How to reduce the LVM Size in RHEL/Centos 7 ?

Hi All, I have one logical volume with size as 900G and it is mounted as xfs file system. Now I want to reduce this partition to 500G. So I followed the below steps. unmount the mount point /home Reduced the volume using the command Now I remounted the partition. But the problem...

3. Red Hat

Network Teaming not working in RHEL/CentOS 7

I was testing Networking Teaming (activebackup) with a VM hosted on VmWare Workstation and VirtualBox, and the result is, if the active interface is down, the system is not using the backup interface. Tested on both CentOS / RHEL 7 Please find below the command I have used to configure teaming....

4. Red Hat

How to Upgrade Centos 5.7 using Centos 5.8 ISO image on Vmware workstation

Dear Linux Experts, On my windows 7 desktop with the help of Vmware workstation (Version 7.1), created virtual machine and installed Centos 5.7 successfully using ISO image. Query : Is this possible to upgrade the Centos 5.7 using Centos 5.8 ISO image to Centos version 5.8?.. if yes kindly...

5. Emergency UNIX and Linux Support

RHEL and Centos VMs with IO failure on root

Hello, I am running into this issues, few VMWare VM's that are running with RHEL 5.6 and Centos 5.7, are having read write errors on the root file system. This is noticed on all vm's. After looking to log files this what I noticed. #touch test.txt touch: cannot touch `test.txt': Read-only...

6. Red Hat

OpenSUSE installation using RHEL / CentOS Kickstart

Hi guys I have CentOS installed on my server. I have also installed TFTP server, DHCP server. I am able to install CentOS on remote machines using PXE boot and kickstart cfg file. I would like to install OpenSUSE using CentOS kickstart file. How do I do it ? I am also fine with any other...

7. Red Hat

Downloading RHEL ISO's!

Hi friends, I am a novice Linux user, and I want to take the RHCE test in future. As I have been told that the RHCE test is all about Redhat Enterprise Linux. I approached redhat.com to download RHEL 6.1, but they don't offer that to people who have email id's at gmail, yahoo etc. Where then I can...

8. Red Hat

Centos/rhel 5 cluster 3 nodes with out Quorum

Hi all, i have 3 nodes cluster (Centos 5 cluster suit) with out quorum disk, node vote = 1, the value of a quorum = 2, when 2 nodes going offline, cluster services are destoys. How i can save the cluster and all services(move all services to one alive node) with out quorum disk when other...

9. Virtualization and Cloud Computing

virtualization in RHEL 5.3 & Centos 5.3

Hi I would like to know how to do virtualization in Rhel 5.3 and Cent os 5.3, As i am new this Virtualization need guidence how to install and configure guest os in Rhel and Cent Os can some one guide me step by step Regards Solaris8in

10. UNIX and Linux Applications

Migrating Oracle from Big Endian to Little Endian Platorm

Hi, We are trying to migrate an oracle database from Sun Solaris (SunOS 5.9 Generic_118558-28 sun4u sparc SUNW,Ultra-60) to Linux 2.6.18-53.1.19.el5 #1 SMP Tue Apr 22 03:01:10 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux which is basically a Big Endian to Little Endian conversion. We shutdown...

LEARN ABOUT BSD

inet

INET(4F)																  INET(4F)

NAME

       inet - Internet protocol family

SYNOPSIS

       #include <sys/types.h>
       #include <netinet/in.h>

DESCRIPTION

       The Internet protocol family is a collection of protocols layered atop the Internet Protocol (IP) transport layer, and utilizing the Inter-
       net address format.  The Internet family provides protocol support for the SOCK_STREAM, SOCK_DGRAM, and SOCK_RAW socket types; the SOCK_RAW
       interface provides access to the IP protocol.

ADDRESSING

       Internet  addresses  are  four  byte quantities, stored in network standard format: layed out as highest to lowest order bytes in memory or
       ``Big Endian'' (the VAX is word and byte reversed, or ``Little Endian''; the  PDP-11  is  byte  reversed  within  each  word,  or  ``Middle
       Endian'').  The include file <netinet/in.h> defines this address as a discriminated union.

       Sockets bound to the Internet protocol family utilize the following addressing structure,

       struct sockaddr_in {
	      short	sin_family;
	      u_short	sin_port;
	      struct	in_addr sin_addr;
	      char	sin_zero[8];
       };

       Sockets	may  be created with the local address INADDR_ANY to effect "wildcard" matching on incoming messages.  The address in a connect(2)
       or sendto(2) call may be given as INADDR_ANY to mean ``this host.''  The distinguished address INADDR_BROADCAST is allowed as  a  shorthand
       for the broadcast address on the primary network if the first network configured supports broadcast.

PROTOCOLS

       The Internet protocol family is comprised of the IP transport protocol, Internet Control Message Protocol (ICMP), Transmission Control Pro-
       tocol (TCP), and User Datagram Protocol (UDP).  TCP is used to support the SOCK_STREAM  abstraction  while  UDP	is  used  to  support  the
       SOCK_DGRAM  abstraction.  A raw interface to IP is available by creating an Internet socket of type SOCK_RAW.  The ICMP message protocol is
       accessible from a raw socket.

       The 32-bit Internet address contains both network and host parts.  It is frequency-encoded; the most-significant bit is clear  in  Class  A
       addresses,  in  which the high-order 8 bits are the network number.  Class B addresses use the high-order 16 bits as the network field, and
       Class C addresses have a 24-bit network part.  Sites with a cluster of local networks and a connection to the DARPA Internet may  chose	to
       use  a  single network number for the cluster; this is done by using subnet addressing.	The local (host) portion of the address is further
       subdivided into subnet and host parts.  Within a subnet, each subnet appears to be an individual network; externally,  the  entire  cluster
       appears	to be a single, uniform network requiring only a single routing entry.	Subnet addressing is enabled and examined by the following
       ioctl(2) commands on a datagram socket in the Internet domain; they have the same form as the SIOCIFADDR command (see intro(4N)).

       SIOCSIFNETMASK	   Set interface network mask.	The network mask defines the network part of the address;  if  it  contains  more  of  the
			   address than the address type would indicate, then subnets are in use.

       SIOCGIFNETMASK	   Get interface network mask.

SEE ALSO

       ioctl(2), socket(2), intro(4N), tcp(4P), udp(4P), ip(4P), icmp(4P)

       An Introductory 4.3BSD Interprocess Communication Tutorial (PS1:7).

       An Advanced 4.3BSD Interprocess Communication Tutorial (PS1:8).

CAVEAT

       The  Internet  protocol	support is subject to change as the Internet protocols develop.  Users should not depend on details of the current
       implementation, but rather the services exported.

4.2 Berkeley Distribution					  August 1, 1987							  INET(4F)

Red Hat