Size and Weight3 | Height: 4.5 inches (115.2 mm) Width: 2.31 inches (58.6 mm) Depth: 0.37 inch (9.3 mm) Weight: 4.9 ounces (140 grams) | |||
---|---|---|---|---|
Cellular and Wireless |
| |||
Location |
| |||
Display |
| |||
Camera, Photos, and Video |
| |||
External Buttons and Connectors | External Buttons and Controls Connectors and Input/Output | |||
Power and Battery5 |
| |||
Audio Playback |
| |||
TV and Video |
| |||
Headphones |
| |||
Mail Attachment Support | Viewable Document Types.jpg, .tiff, .gif (images); .doc and .docx (Microsoft Word); .htm and .html (web pages); .key (Keynote); .numbers (Numbers); .pages (Pages); .pdf (Preview and Adobe Acrobat); .ppt and .pptx (Microsoft PowerPoint); .txt (text); .rtf (rich text format); .vcf (contact information); .xls and .xlsx (Microsoft Excel) | |||
Sensors |
| |||
System Requirements | Mac System Requirements
PC System Requirements
| |||
Environmental Requirements |
| |||
Languages | Language SupportEnglish (U.S.), English (UK), Chinese (Simplified), Chinese (Traditional), French, German, Italian, Japanese, Korean, Spanish, Arabic, Catalan, Croatian, Czech, Danish, Dutch, Finnish, Greek, Hebrew, Hungarian, Indonesian, Malay, Norwegian, Polish, Portuguese, Portuguese (Brazil), Romanian, Russian, Slovak, Swedish, Thai, Turkish, Ukrainian, Vietnamese Keyboard SupportEnglish (U.S.), English (UK), Chinese - Simplified (Handwriting, Pinyin, Wubihua), Chinese - Traditional (Handwriting, Pinyin, Zhuyin, Cangjie, Wubihua), French, French (Canadian), French (Switzerland), German (Germany), German (Switzerland), Italian, Japanese (Romaji, Kana), Korean, Spanish, Arabic, Bulgarian, Catalan, Cherokee, Croatian, Czech, Danish, Dutch, Emoji, Estonian, Finnish, Flemish, Greek, Hawaiian, Hebrew, Hindi, Hungarian, Icelandic, Indonesian, Latvian, Lithuanian, Macedonian, Malay, Norwegian, Polish, Portuguese, Portuguese (Brazil), Romanian, Russian, Serbian (Cyrillic/Latin), Slovak, Swedish, Thai, Tibetan, Turkish, Ukrainian, Vietnamese Dictionary Support (enables predictive text and autocorrect)English (U.S.), English (UK), Chinese (Simplified), Chinese (Traditional), French, French (Canadian), French (Switzerland), German, Italian, Japanese (Romaji, Kana), Korean, Spanish, Arabic, Catalan, Cherokee, Croatian, Czech, Danish, Dutch, Estonian, Finnish, Flemish, Greek, Hawaiian, Hebrew, Hindi, Hungarian, Indonesian, Latvian, Lithuanian, Malay, Norwegian, Polish, Portuguese, Portuguese (Brazil), Romanian, Russian, Slovak, Swedish, Thai, Turkish, Ukrainian, Vietnamese Siri LanguagesEnglish (U.S., UK, and Australian), French, German | |||
In the Box |
|
This Blog is intended to collect information of my various Intrests,pen my opinion on the information gathered and not intended to educate any one of the information posted,but are most welcome to share there view on them
Thursday, December 1, 2011
iPhone 4S Technical Specifications
Thursday, November 24, 2011
NIC Bonding in Linux
Linux allows binding multiple network interfaces into a single channel/NIC using special kernel module called bonding. The behavior of the bonded interfaces depends upon the mode; generally speaking, modes provide either hot standby or load balancing services. Additionally, link integrity monitoring may be performed.
Step 1: Create a bond0 configuration file
# vi /etc/sysconfig/network-scripts/ifcfg-bond0
Append following lines to it:
DEVICE=bond0
IPADDR=192.168.0.100
NETWORK=192.168.0.0
NETMASK=255.255.255.0
USERCTL=no
BOOTPROTO=none
ONBOOT=yes
Replace above IP address with your actual IP address. Save file and exit to shell prompt.
Step 2: Modify eth0 and eth1 config files:
# vi /etc/sysconfig/network-scripts/ifcfg-eth0
Modify/append directive as follows:
DEVICE=eth0
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none
Save file and exit to shell prompt.
Step 3: Load bond driver/module
Make sure bonding module is loaded when the channel-bonding interface (bond0) is brought up. You need to modify kernel modules configuration file:
# vi /etc/modprobe.conf
Append following two lines:
alias bond0 bonding
options bond0 mode=1 miimon=1000 ###Note: mode 1 is “active-backup”
{Please consider removing the line 'options bonding miimon=100 mode=0' from modprobe.conf and place this line in ifcfg-bond0
BONDING_OPTS="miimon=100 mode=1"
RHEL5 and later support setting the bonding options in the ifcfg-bondX file, not in modprobe.conf.}
Step 4: Probe bonding module and test configuration
# /etc/init.d/network stop
# modprobe -r bonding
# lsmod |grep -i bond
# modprobe bonding
Restart networking service in order to bring up bond0 interface:
# /etc/init.d/network restart
If you get the below output, then everything is fine.
# cat /proc/net/bonding/bond0
Bonding Mode: active-backup
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth0
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:00:00:00:00:00
Slave Interface: eth1
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:00:00:00:00:00
===============================================================
Options for mode types:
You can set up your bond interface according to your needs. In order to do this, you simply change the mode type depicted in the examples below (mode=X). There are seven mode types available. They are as follows:mode=0This mode uses the Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.
mode=1This mode uses an Active-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance. The primary option affects the behavior of this mode.
mode=2Transmit based on [(source MAC address XOR'd with destination MAC address) modulo slave count]. This selects the same slave for each destination MAC address. This mode provides load balancing and fault tolerance.
mode=3Broadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance.
mode=4IEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification.
*Pre-requisites:1. Ethtool support in the base drivers for retrieving the speed and duplex of each slave.2. A switch that supports IEEE 802.3ad Dynamic link aggregation. Most switches will require some type of configuration to enable 802.3ad mode
mode=5Adaptive transmit load balancing: channel bonding that does not require any special switch support. The outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave.*Prerequisite: Ethtool support in the base drivers for retrieving the speed of each slave.
mode=6Adaptive load balancing: includes balance-transmit load balancing plus receive load balancing for IPV4 traffic, and does not require any special switch support. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware address of one of the slaves in the bond such that different peers use different hardware addresses for the server.
Wednesday, November 23, 2011
Add Dag RPM Repository in RHEL5
Add Dag RPM Repository for yum because that has many useful packages.
[root@dns ~]# wget http://dag.wieers.com/rpm/packages/RPM-GPG-KEY.dag.txt
[root@dns ~]# rpm --import RPM-GPG-KEY.dag.txt
[root@dns ~]# rm -f RPM-GPG-KEY.dag.txt
[root@dns ~]# vi /etc/yum.repos.d/dag.repo ###Create this file and add following lines:
[dag]
name=Dag RPM Repository for Red Hat Enterprise Linux
baseurl=http://apt.sw.be/redhat/el5/en/$basearch/dag/
gpgcheck=1
enabled=0
# When you use dag repository, Input yum command like below.
[root@dns ~]# yum --enablerepo=dag install [package]
[root@dns ~]# wget http://download.fedora.redhat.com/pub/epel/RPM-GPG-KEY-EPEL
[root@dns ~]# rpm --import RPM-GPG-KEY-EPEL
[root@dns ~]# rm -f RPM-GPG-KEY-EPEL
[root@dns ~]# vi /etc/yum.repos.d/epel.repo ###Create this file and add following lines:
[root@jbox01 ~]# rpm -qa|grep gpg-pubkey*
gpg-pubkey-217521f6-45e8a532
[root@jbox01 ~]# rpm -qi gpg-pubkey-217521f6-45e8a532
[root@dns ~]# yum --enablerepo=epel install [package]
[root@dns ~]# wget http://download.fedora.redhat.com/pub/epel/RPM-GPG-KEY-EPEL
[root@dns ~]# rpm --import RPM-GPG-KEY-EPEL
[root@dns ~]# rm -f RPM-GPG-KEY-EPEL
[root@dns ~]# vi /etc/yum.repos.d/epel.repo ###Create this file and add following lines:
[epel]
name=EPEL RPM Repository for Red Hat Enterprise Linux
baseurl=http://download.fedora.redhat.com/pub/epel/$releasever/$basearch/
gpgcheck=1
enabled=0
name=EPEL RPM Repository for Red Hat Enterprise Linux
baseurl=http://download.fedora.redhat.com/pub/epel/$releasever/$basearch/
gpgcheck=1
enabled=0
[root@jbox01 ~]# rpm -qa|grep gpg-pubkey*
gpg-pubkey-217521f6-45e8a532
[root@jbox01 ~]# rpm -qi gpg-pubkey-217521f6-45e8a532
# When you use dag repository, Input yum command like below.
[root@dns ~]# yum --enablerepo=epel install [package]
Repository Configuration
Fedora : RPM Fusion- Fedora Core : Extras and Livna
- RHEL or CentOS : EPEL
This are the only third repositories I use, I contribute to and I recommend.
1. Download
It is preferable to use YUM to download and install RPM available on this site, however il can be useful to download a RPM for a futher use or for another computer.
Locations :
- http://rpms.famillecollet.com/ the repositories (repoview browser).
http://rpms.famillecollet.com/SPEC/ spec file used to build the RPM.(not more updated, use the git repo)- http://rpms.famillecollet.com/SRPMS/ sources RPM.
- http://github.com/remicollet/remirepo the git repository with all the files needed to build the RPM (spec, patches, ...)
2. Package manager configuration
This repository use the YUM format, it can also be used with APT and SMART. It need to be declared.
Notes :
- ppc64 (PowerPC 64 bits) repositories are only open for Fedora 8 and newer.
- x86_64 (64 bits) and ppc (PowerPC) repositories are only open for Fedora Core 6 and newer.
- For older releases only the i386 (32 bits) repository is open.
- 2008-05-17 : The Fedora Core 3 repository is closed (it stay available but will not be updated).
- 2009-04-19 : The Fedora Core 4 and 5 repositories are closed.
- 2010-10-11 ; The Fedora Core 6 and Fedora 7 repositories are closed.
- 2011-09-16 ; The Fedora 8 and Fedora 9 repositories are closed.
2.1. YUM automatic configuration
The simplest way is to install the remi-release package which provides the repository configuration for YUM and the GPG key used to sign the RPM.
Fedora 15 i386 or x86_64
rpm -Uvh http://rpms.famillecollet.com/remi-release-15.rpm
Fedora 14 i386 or x86_64
rpm -Uvh http://rpms.famillecollet.com/remi-release-14.rpm
Fedora 13 i386 or x86_64
rpm -Uvh http://rpms.famillecollet.com/remi-release-13.rpm
Fedora 12 i386, ppc, ppc64 or x86_64
rpm -Uvh http://rpms.famillecollet.com/remi-release-12.rpm
Fedora 11 i386, ppc, ppc64 or x86_64
wget http://rpms.famillecollet.com/remi-release-11.rpm rpm -Uvh remi-release-11.rpm
Fedora 10 i386, ppc, ppc64 or x86_64
wget http://rpms.famillecollet.com/remi-release-10.rpm rpm -Uvh remi-release-10.rpm
Enterprise Linux 6 (with EPEL)
wget http://download.fedora.redhat.com/pub/epel/beta/6/i386/epel-release-6-5.noarch.rpm wget http://rpms.famillecollet.com/enterprise/remi-release-6.rpm rpm -Uvh remi-release-6*.rpm epel-release-6*.rpm
Enterprise Linux 5 (with EPEL)
wget http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm wget http://rpms.famillecollet.com/enterprise/remi-release-5.rpm rpm -Uvh remi-release-5*.rpm epel-release-5*.rpm
Enterprise Linux 4 (with EPEL)
wget http://download.fedora.redhat.com/pub/epel/4/i386/epel-release-4-10.noarch.rpm wget http://rpms.famillecollet.com/enterprise/remi-release-4.rpm rpm -Uvh remi-release-4*.rpm epel-release-4*.rpm
2.2. APT configuration
As for YUM, install the automatic configuration package. To enable the repository, you need to uncomment, in /etc/apt/sources.list.d/remi.list file, the line :
repomd http://rpms.famillecollet.com/ fc$(VERSION).$(ARCH)
2.3. SMART configuration
As for YUM, install the automatic configuration package. To enable the repository, you have to select it in the Edition / Channel menu.
2.3. YUM manual configuration
You just have to download the repository file configuration and to save it in the appropriate direcotry.
Fedora :
su - cd /etc/yum.repos.d wget http://rpms.famillecollet.com/fedora/remi.repo
Enterprise Linux (RHEL, CentOS) :
su - cd /etc/yum.repos.d wget http://rpms.famillecollet.com/enterprise/remi.repo
This file provides configuration for remi and remi-test repositories.
Notice : the repository is not enabled on install (enabled=0). You need to enable it when you need it, for example :
yum --enablerepo=remi install firefox-langpack-fr
3. Compatibility with other repositories
On Fedora, available RPM mainly use dependencies from fedora, and updates repositories, sometime from Livna. (And, from Extras when Fedora <= 6) and now from Rpmfusion.
On Redhat and CentOS dépendencies are in main repositories and in EPEL. I really discourage you from using Rpmforge (well known conflicts with EPEL).
Exceptions are explained on the blog article of each RPM.
4. Remi's signature Installation (GPG Key)
This step is not required if you use a package manager (Yum of Apt).
The RPM validity check requires my key to be imported on your system before use. Download This GPG key and install it with :
rpm --import RPM-GPG-KEY-remi
YUM will propose you to automatic install it on first installation of a RPM from my repository.
You can list the installed key with :
rpm -q gpg-pubkey --qf "%{summary} ->%{version}-%{release}\n"
My old key fingerprint was : 00f97f56-4267cb5c
My new key fingerprint is : 00f97f56-467e318a
Subscribe to:
Posts (Atom)