Category: POP3, IMAP
Fedora’s repositories provide most of the software packages needed when using Linux. However, for various consideration, they do not provide some packages, such as MPlayer, ffmpeg. Fortunately, some community maintained repository provides these software. And they may also package propriety software, , such as ATI fglrx dive, NVIDIA driver, into rpm packages. In this post, we introduce theses additional repositories and how to install them into Fedora.
RPM Fusion
“RPM Fusion provides software that the Fedora Project or Red Hat doesn’t want to ship. That software is provided as precompiled RPMs for all current Fedora versions and Red Hat Enterprise Linux 5 and 6; you can use the RPM Fusion repositories with tools like yum and PackageKit.”
RPM Fusion has two separate software repositories. The free for Open Source Software (as defined by the Fedora Licensing Guidelines) which the Fedora project cannot ship due to other reasons. The nonfree for redistributable software that is not Open Source Software (as defined by the Fedora Licensing Guidelines); this includes software with publicly available source-code that has “no commercial use”-like restrictions.
To enable access to both the free and the nonfree repository use the following command.
Released and currently supported Fedora versions:
# yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm # yum localinstall --nogpgcheck http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm
Fedora Rawhide and what will become the next Fedora version (Alpha, Beta and snapshots):
# yum localinstall --nogpgcheck http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-rawhide.noarch.rpm # yum localinstall --nogpgcheck http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-rawhide.noarch.rpm
This post makes a list of actions should be done to upgrade Fedora using yum. Please note that this is for experienced users only, if you are not sure what you are doing and what do these commands mean, please stop here and read the manuals first, or go to Fedora’s Wiki about upgrading Fediora using yum.
This post aims to be a general method, although we use Fedora 15 to Fedora 16 as the example. We configure and install grub2 as the bootloader.
Clean Stuff
It is a good time to remove packages we don’t use. These packages could be candidates for removal, but check to see whether you use them directly or if they are used by applications not backed by rpm packages.
# package-cleanup --leaves
You can find orphaned packages (i.e. packages not in the repositories anymore). This will also show packages which have been partially uninstalled but where the “%postun” script failed.
# package-cleanup --orphans
Do the upgrade
Go to a text console and run in level 3
ctrl + alt + F2
init 3
Update yum first
yum update yum
Clean all cached meta data and packages
yum clean all
Import the key for the newer version’s repository
For Fedora 16, it is
rpm --import https://fedoraproject.org/static/A82BA4B7.txt
Synchronizes the installed package set with the latest packages available
yum --releasever=<release_number_you_want_to_sync_to> distro-sync
For upgrading Fedora 15 to Fedora 16:
yum --releasever=16 --disableplugin=presto distro-sync
Double check the updated repositories after distro-sync
yum repolist
Update groups
yum groupupdate Base
List all other groups
yum grouplist
and also update them
yum groupupdate ALL GROUPS LISTED
Use grub2 instead of grub
Make configuration for grub2
/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg
Install grub2
/sbin/grub2-install BOOTDEVICE
For example, to install grub2 on sda:
/sbin/grub2-install /dev/sda
Reset services start/stop priorities
cd /etc/rc.d/init.d; for f in *; do /sbin/chkconfig $f resetpriorities; done
Reboot the system now
After reboot, you may see new kernel version on new Fedora version. For example, kernel 3.1.1 on Fedora 16
[root@localhost ~]# uname -a Linux localhost.localdomain 3.1.1-1.fc16.x86_64 #1 SMP Fri Nov 11 21:47:56 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
I’ve been having the same issue for the past 4-5 days, since gmail got it’s new look here in italy (but i started having the problem even before switching to the new look)
vafer.org – Latest Comments in Gmail POP3/IMAP problems?
This is a tutorial on ns-2 which gives a overview of ns-2 and introduces how to define a simple topology and the network flow. This tutorial is based on the slides for Lab session of COMP 4622 at HKUST in the fall semester of 2011.
The slides of tutorial on ns-2 can be download from here:
Read more:
- A Good Bash Tutorial: Advanced Bash-Scripting Guide
- Installing ns-2 and ns-3 on Fedora Linux
- Automatically Backing Up Xen File-backed DomU
ns is a discrete-event network simulator targeted primarily for research and educational use. There are two version of ns, ns-2 and ns-3, which are quite different with each other in the implementation and method to use them. In this post, we introduce how to install ns-2 and ns-3 on Fedora Linux.
Install ns-2.34 on Fedora 15
Download the allinone package
$ wget http://downloads.sourceforge.net/project/nsnam/allinone/ns-allinone-2.34/ns-allinone-2.34.tar.gz
Uncompress the pacakge
$ tar xf ns-allinone-2.34.tar.gz
Install needed pacakges
# yum install gcc make libX11-devel libXt-devel libXmu-devel
Ns-2 requires older version of gcc. So we install gcc-34 and gcc-34-c++ for it
# yum install compat-gcc-34 compat-gcc-34-c++
Install the allinon package of ns-2. During the install process, specify the CXX compiler we use
$ cd ns-allinone-2.34 $ CXX=g++34 ./install
Configure the environmental variables for ns-2 and nam, and add the executables to the PATH so that we can use ns and nam directly.
Add to ~/.bashrc if you use bash
NS_HOME=/full/path/to/ns-allinone-2.34 PATH=$NS_HOME/bin:$NS_HOME/tcl8.4.18/unix:$NS_HOME/tk8.4.18/unix:$PATH export PATH
or
Add to ~/.cshrc_user if you use c shell
setenv NS_HOME "/full/path/to/ns-allinone-2.34"
setenv PATH "${PATH}:${NS_HOME}/bin:${NS_HOME}/tcl8.4.18/unix:${NS_HOME}/tk8.4.18/unix"
setenv LD_LIBRARY_PATH "${NS_HOME}/otcl-1.13:${NS_HOME}/ns-2.34/lib:/usr/local/lib"
setenv TCL_LIBRARY "${NS_HOME}/tcl8.4.18/library"
The installation is done by this step. Open another shell and try our installation:
$ nam
and
$ ns
Install ns-3.12.1 on Fedora 15
Install needed packages
# yum install libxml2 libxml2-devel gcc gcc-c++ make automake \ autoconf binutils openssh-server openssh-clients openssl python \ python-devel mercurial bzr scons flex bison tcpdump valgrind gdb
Download the allinone pacakge for ns-3
$ mkdir tarballs $ cd tarballs $ wget http://www.nsnam.org/release/ns-allinone-3.12.1.tar.bz2 $ tar xjf ns-allinone-3.12.1.tar.bz2
Build ns-3
$ cd ns-allinone-3.12.1/ $ ./build.py
We will now interact directly with Waf in the ns-3.12.1 directory
$ cd ns-3.12.1
Configuration with Waf
$ ./waf -d optimized configure --enable-examples; ./waf
Validate our installation by running one example
$ ./waf shell $ cd build/optimized/examples/ $ udp/udp-echo
Use tcpdump to display the simulation result
$ tcpdump -tt -r udp-echo-0-1.pcap
Read more:
- Installing and Configuring 32bit Firefox on 64bit Linux (Fedora)
- Problems during Installing Xen Dom0 in Fedora
- Installing Nvidia Driver on Fedora
NFS is widely deployed and used even after more than twenty year. NFS is easy to set up and easy to use. This introduces how to set up the NFS server and clients. We use the Fedora system as the example.
Set up a NFS Server
Configure /etc/exports to give clients the permission to use the NFS directories.
Edit /etc/exports
For example, to allow the servers inside subnet 10.0.0.1/24 to mount the /home directory with read/write permission. Add this line to /etc/exports:
/home 10.0.0.1/24(rw)
For details of the exports functions, please refer to export manual.
Start up the NFS service
Enable nfs service on the NFS server so that the NFS service daemon automatically starts each time the server starts:
# /sbin/chkconfig nfs on
You may also manually start it
# service nfs start
Client-slide configuration
Package installation
# yum nfs-utils
Start the rpcbind service
# service rpcbind restart
You may also set it to start automatically
# chkconfig rpcbind on
Mount the NFS directory
# mount NFS_SERVER:/lhome/userdir MOUNT_POINT
where NFS_SERVER is the NFS server’s address, and MOUNT_POINT is the local mount point on the client side for the NFS directory.
You may also consider using autofs on top of NFS as described in Unified Linux Login and Home Directory Using OpenLDAP and NFS/automount.
Read more:
- Configure mailx to Use Gmail’s smtp
- Fixing Ports Used by NFS Server
- Setting Up a NFS Server on Top of tmpfs /dev/shm
Struggling with falling market shares, lower Blackberry shipments and the recent outage of service for users across the country, mobile phone and tablet maker RIM is in a difficult position. Inroads are quickly being made into what was once exclusively their territory by both Apple and Google, and the company is hoping that its newly-announced cross-platform OS, BBX, will be what puts them back on top.
BBX is a combination of the Blackberry OS and the QNX platform which RIM acquired last year. Together, they create BBX. But this is an entirely new animal – apps that work on current versions of the Blackberry and PlayBook OS won’t work with BBX. The company hopes, however, that the all-inclusive nature of the OS will make up for the fact that users are going to have to update all of their apps and favorite programs. RIM intends this version of their OS to work on all of their tablets and smartphones as well as in users’ cars, in enterprise-scale business, and in the cloud.
There is no release date for the new BBX as yet, something that disappointed many of the press and tech sites covering the announcement, but RIM indicates that both smartphones and tablets should see the new OS in 2012. While no smartphone or tablet was shown running a demo of the new OS during the announcement, there is speculation that the Blackberry Colt will be the first smartphone to use BBX, and that it will be released in the middle of 2012.
BBX comes with a number of notable features, starting with the fact that it is open-source, allowing developers to create apps in whatever environment they are comfortable with and then port them over to Blackberry’s OS. BBX is therefore expected to have a large variety of apps to choose from, and while it won’t run old BlackBerry OS apps or iOS apps, it will run Android, Adobe Flash 11 and Adobe Air 3. In addition, Blackberry Email users can likely expect and update from the current Blackberry Enterprise Server that handles business email to a more cloud-friendly version that will sync their mail on the fly. Whether this will come in the form of Exchange ActiveSync or another type of syncing has yet to be announced, but it should provide a more streamlined experience for business users.
RIM’s strength has always been to play to the business market, something they are clearly taking aim at with the BBX announcement. In addition to ensuring that their enterprise-level functionality is improving, however, the company is also looking to add better support for games, design, and mulch-platform app designs with their new OS. Additionally, its ability to work in a vehicle – QNX already works in over 200 vehicle types – is something that RIM hopes will put it ahead of the competition. BBX promises a great deal, but with no release date, only time will tell if the new OS can get RIM back on track in time.
Related posts:
On a x86-64 64 bit Linux system, sometimes we may want to use the 32 bit Firefox, although the support to 64 bit Firefox is getting much better. Just for needed ones, this post introduces how to install 32 bit Firefox on 64 bit Linux (Fedora as the example).
First, install firfox.i686 package.
# linux32 # yum install firefox.i686
Firefox can simply run now. But we still need to fix some issues.
When run firefox, we may get these warnings:
(firefox:4860): Gtk-WARNING **: Unable to locate theme engine in module_path: “clearlooks”,
Gtk-Message: Failed to load module “pk-gtk-module”: libpk-gtk-module.so: cannot open shared object file: No such file or directory
Gtk-Message: Failed to load module “canberra-gtk-module”: libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
To fix these warnings, install needed packages:
# yum install libcanberra-gtk2.i686 \ gtk2-engines.i686 \ PackageKit-gtk-module.i686
However, there is no input method. To enable ibus-gtk2 input method in 32bit Firefox, install the ibus-gtk2 package
# yum install ibus-gtk2.i686
Install the flash-plugin
Enable rpmfusion repository
# rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm # rpm -Uvh http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm
Install flash plugin
# yum install flash-plugin.i386
Set up flash plugin
# /usr/lib/flash-plugin/setup
There is no sound in flash. For sound support and curl support, install
# yum install alsa-plugins-pulseaudio.i686 curl.i686
You should have sound. flash-plugin works.
Firefox should complain nothing and work well now. Enjoy it.
Read more:
- Installing the Flash Plugin for 64-bit Firefox in Linux x86-64
- Speeding Up Firefox in Linux
- Problems during Installing Xen Dom0 in Fedora
Following eight successful months in beta, Greatmail’s MxGrid SMTP service is now fully integrated into the company’s service line and renamed simply ‘SMTP Hosting’.
The SMTP offering includes support for sender authentication technologies including DKIM signing and SPF validation, feedback loop management, optional bounce account hosting, and IP reputation monitoring.
Greatmail’s SMTP hosting targets customers sending marketing campaigns, transactional emails and other bulk messages. Clients are expected to adhere to CAN-SPAM best practices including bounce removal processing, one-click unsubscribing, and double opt-in verified sending.
SMTP hosting pricing starts at just .95 per month for 50,000 sends. The service uses both dedicated and shared IPs designed to deliver optimal delivery rates for established account holders depending on their sending patterns.
Existing MxGrid customers will not be affected by the service name change. In the next quarter, MxGrid customers will receive instructions to access a newly developed web based control panel for account management and statistical reporting.
This post is a tutorial for new users to set up git and clone and use the first repository. This post introduces how to start using git for new users. This post does not introduce details of how to use git commands. Please refer to the git manual or other tutorials for how to commit, push, etc.
In this post, we introduce how to set up keys for git, how to configure non-standard SSH port for git, and how to use the first git repository.
Users’ SSH private/public key pairs
Every user of git, administrator or a normal user, need to have a private/public SSH key pairs in ~/.ssh.
New users need to generate the key pairs (if they don’t have one) by executing this command:
$ ssh-keygen -t rsa
After generating the key pairs, the user can give the public key (~/.ssh/id_rsa.pub) to the git server administrator and ask he/she to create a account and repository.
After the git server administrator adds the new user by its public key to the git server, the user can starts to use git.
Non-standard SSH port
This section only for the git servers that use non-stardard SSH port, i.e. other than 22.
If sshd is listening on non-standard port(s) on the git server, for example 22111, the user should set SSH to use the special port. We use example.org:22111 as the example here.
Put these two lines in your ~/.ssh/config file:
Host example.org Port 22111
If this ~/.ssh/config file doesn’t exist, you should create it first and set it’s mod to 744:
$ chmod 744 ~/.ssh/config
Create the new repository
This section only for users to create new repository. If the user is to use an already exist repository, please skip this section. Besides, the steps in this section only need to be done once for one repository.
We use the example that the administrator create repository repo1 for user1 and give user1 write privilege to this repository. We assume the address for this repository is git@example.org:repo1.git . Now we introduce how does user1 create the new repository repo1.
As user1 has the write privilege on the repo1 repository, it can create this repository on it’s local machine first and then push it to the git server. After pushing it to the git server.
These operations are done by user1 on its local machine:
$ mkdir repo1 $ cd repo1 $ git init $ touch README $ git add README $ git commit -a -m 'first commit' $ git remote add origin git@example.org:repo1.git $ git push origin master
If it successes, the new repository is created on the git server.
Use the repository
Please note that step 1 only need to be done for the first time. After getting the repository to a local directory on the user’s local machine, the user only need to follow step 2 to step 5.
1. Clone the repository for the first-time. You only need to do it once for the first time, for the later usage of this repository, you continue use this local directory.
$ git clone git@example.org:repo1.git
A directory named repo1 will be created in the current directory.
If you want to use the repository directory in the previous section, just add these line to the end of .git/config:
[branch "master"] remote = origin merge = refs/heads/master
2. Pull the updates made before by you or the others. Use “git pull” command in the repository’s directory.
$ cd repo1 $ git pull
Then you can work on this updated copy of the repository by editing the files.
If you add a file or directory (for example, add directory a/b and file a/t.txt), you can add it to the repository by:
$ git add a/b a/t.txt
3. Commit the changes made by you with a message
$ git commit -a -m 'update the files'
4. Push it to the git server
$ git push
By now, your changes have been pushed to the git server. When the others use “git pull” command, they will get the new version of the source codes that have changed by you.
You can use “git log” to see the logs of all the commits of this repository.
You may be also interested in more git solutions.
Read more: