What's BUILD-ESSENTIAL equivalent in FEDORA ?

1.    Needing to install the equivalent of build-essential we require in Ubuntu for Fedora is given by this command line in root mode :

yum groupinstall "Development Tools" "Development Libraries"

FUDUNTU : Ubuntu + Fedora

1.     How about the best from Ubuntu and Fedora into one single OS?... that's rightly heard....the name is FUDUNTU....few things about this mentioned below :

- Website at http://www.fuduntu.org/

- Fuduntu aims to fit somewhere between Fedora and Ubuntu

- Fuduntu is a lighthearted and fun Linux distribution

 - Option to download directly as well as through torrent

- Fuduntu is optimized for on the go computing(good for Laptop and Netbook users )

- Improved battery life of 30% or more over other Linux distributions.

- The latest Fuduntu 2013.2 has LibreOffice, GIMP, Thunderbird, and other software that takes up a lot of space, approximately 10GB of disk space when installed. However, if you don’t need all that, try out the Lite version, where ISO weighs 800 MB and eats up 6 GB when installed.

2.   The download has started and if I feel it worth will show up with something about it...btw the looks are promising!!!!!

Upgrading Fedora 17 to Fedora 18

1.   Like me so many of you would have been waiting for the final release of Fedora 18 spherical cow...but at the same time when u see it released u have so many links to move around on how to upgrade from 17 to 18 but u keep ending up with previous one....i went through the same for past hour...:-)

2.  The only set of commands Fedora 17(only) users need to put in are these :

Reach the Root first with the password ie 

su -
*******(ur password)
su -c 'rpm --import https://fedoraproject.org/static/DE7F38BD.txt'


su -c 'setenforce Permissive'

su -c 'yum update yum'

su -c 'yum clean all'

su -c 'yum --releasever=18 --disableplugin=presto distro-sync'

su -c 'rpm --rebuilddb', or rpm -qa will not work due to a upgrade of rpm

3.   For me the upgrade is around 1.6 G as seen in the screen shot below :

4.   Mine is upgrading on way....another few hours should be ok....:-) all the best for your upgrade

FEDORA 18 RELEASE DATE : 08 Jan 2013

Hi guys....a very HAPPY NEW YEAR 2013 to you.....and for those of you like me who are waiting to upgrade ur Beefy Miracle to Fedora 18 Spherical Cow..u need to wait a few more days till 8 January 2013... that's the release date scheduled now..hope that stands by the time!!!

India developing own Secure OS to strengthen Cyber Security

1.   India is developing own secure OS to strengthen cyber security.Got this news piece from here.The key points from the news are :

- India's own secure operating system to strengthen cyber security.

- 150 Engineers across the country have already been working on creating an Indian OS for over one year and a half. 

- According to Times of India ,it will be ready in next three years.

- There is no foreign involvement in this project. It is purely build by Indians.

2.   It is indeed heartening to know all this...but whats the point? Does the team of 150 engineers and the vision behind think they are creating a secure and 100% fool proof OS?...The moment it is released...there will be many vulnerabilities that will be gradually known...and then the same cat mouse race will being like with any other OS..so whats the point of starting from scratch?....will it not be wise to securify existing opensource available and invest in something like improving upon existing resources?.....Case in point,the DESI OS....will lag behind in terms of experiences gained by Windows and other OS Communities who have been in the game for years...........who have been improving daily for so many years!!!like Fedora...Ubuntu...they have been improving for last so many years to reach a level like as on date available to us....

3.  Although it is a veri good thought to have a desi OS....but I sincerely feel that we are slightly late in realizing the need of a desi OS...

How to Format a USB drive with FAT32 file system: FEDORA 17/LINUX

1.   The ease of formatting that the regular windows user is used involves a simple right click on the drive and clicking format.But for a linux user the scene is a little different involving a set of commands.Shown here with screen shots.The commands used are :

- df -h
- fdisk -l
- umount /run/media/duqu/?????***(ur mount name)
- mkdosfs -F 32 -I /dev/sdc1

(CLICK ON THE IMAGE TO ENLARGE)

(CLICK ON THE IMAGE TO ENLARGE)

(CLICK ON THE IMAGE TO ENLARGE)

TRUE CRYPT IN FEDORA 17: INSTALLATION

1.   The earlier version of Fedora had some token issues to deal with while installing True Crypt but not with this Fedora 17 Beefy Miracle.

2.   Few commands to be run from root after downloading the requisite version from the True Crypt site go as follows :

tar xvf truecrypt-7.1a-linux-x86.tar.gz 

yum install nss-pkcs11-devel fuse-devel wxGTK wxGTK-devel

yum load-transaction /tmp/yum_save_tx.2012-12-13.14-20.laXbNn.yumtx

yum install gnome-keyring-devel gcc-c++

export PKCS11_INC=/usr/include/gp11

./truecrypt-7.1a-setup-x86 

3.   Well if there are some token issues like shown below : 

../Common/SecurityToken.cpp:660: error: ‘CKR_NEW_PIN_MODE’ was not declared in this scope

../Common/SecurityToken.cpp:661: error: ‘CKR_NEXT_OTP’ was not declared in this scope

then you need to Open Common/SecurityToken.cpp in any editor and Scroll to line 660 and simply Comment out line 660 and 661. It should look like this after you edit:

//TC_TOKEN_ERR (CKR_NEW_PIN_MODE)

//TC_TOKEN_ERR (CKR_NEXT_OTP)

FEDORA 17 & VIRTUAL BOX : Virtualbox Installs but won't load

1.   This particular problem kept me busy the whole day....and in fact I reached a point of frustration that I should switch back to Ubuntu that I was earlier using.......so the problem goes like when I install virtual box via the rps and yum commands ...I used to invariably get some odd message that mostly included the following :

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

'/etc/init.d/vboxdrv setup'

2.    I would not actually lie about it...but i checked about so many forums that gave relatively the same solutions that you would have mostly found out by now...but to no avail...so the two command simple solution that would make you VB run like a horse without any issues goes like this :

yum install dkms binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-PAE-devel

/etc/init.d/vboxdrv setup

offcourse you have to run this as a su -

3.   Do let me know if u r stuck on this again...the sets of commands that I run since morning as root are produced below for info only.BUt I am sure the commands above would solve your problem.

   21  wget http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo

   22  yum update

   23  rpm -qa kernel |sort |tail -n 1

   24  uname -r

   25  reboot

   26  rpm -Uvh http://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm

   27  pwd

   28  cd /etc/init.d/

   29  ls

   30  cd vboxdrv

   31  /etc/init.d/vboxdrv setup

   32  cd /var/log/

   33  more vbox-install.log 

   34  cd /etc/yum.repos.d/

   35  wget http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo

   36  yum update

   37  yum install binutils qt gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel      

   dkms   

   38  yum install VirtualBox-4.2                                                                                  

   39  virtualbox                                                                                                  

   40  KERN_DIR=/usr/src/kernels/2.6.18-194.11.1.el5-x86_64                                                        

   41  export KERN_DIR                                                                                             

   42  yum update virtualbox-4.2                                                                                   

   43  aptitude update                                                                                             

   44  yum install dkms gcc                                                                                        

   45  yum install kernel-headers kernel-devel                                                                     

   46  /etc/init.d/vboxdrv setup                                                                                   

   47  more /var/log/vbox-install.log                                                                                                                                                                    

   49  wget http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo                                   

   50  uname -r                                                                                                                                                                             

   53  rpm -qa kernel |sort |tail -n 1                                                                             

   54  uname -r

   55  service vboxdrv setup

   56  uname -r

   57  KERN_DIR=/usr/src/kernels/3.6.6-1.fc17.i686.PAE

   58  export KERN_DIR

   59  virtualbox

   60  usermod -a -G vboxusers duqu

   61  virtualbox

   62  apt-get install dkms

   63  wget install dkms

   64  uname -r

   65  rpm -q kernel-devel

   66  uname -r

   67  virtualbox

   68  /etc/init.d/vboxdrv setup

   69  more /var/log/vbox-install.log

   70  KERN_DIR=/usr/src/kernels/3.6.6-1.fc17.i686.PAE

   71  export KERN_DIR

   72  virtualbox

   73  /etc/init.d/vboxdrv setup

   74  uname -r

   75  yum install kernel-headers-3.6.6-1.fc17.i686.PAE

   76  exit

   77  yum install kernel-headers gcc

   78  /etc/init.d/vboxdrv setup

   79  exit

   81  yum install dkms binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-   

   PAE-devel

   82  /etc/init.d/vboxdrv setup