Showing posts with label System. Show all posts
Showing posts with label System. Show all posts

Monday, October 22, 2012

System Log not Opening in Ubuntu 12.10? (fix)



The ‘system log’ in Ubuntu (or in any other OS) is not something that most users are interested in or use that much. However, it is a pretty useful tool that lets you track back software or hardware related issues etc.
And for some reason, in Ubuntu 12.10, I cannot open it by clicking on its icon in Unity’s ‘Dash’. I don’t know if it is a system wide bug, but if you are too having the issue, then until a fix comes in, you can still open it by using the below command in your Terminal window.
gnome-system-log
If you want to open it with administrative privileges, then use the below command instead.
gksudo gnome-system-log
That’s it.

Saturday, October 13, 2012

How To Configure Your Computer To Use The Tor Network System Wide - Ubuntu 12.10/12.04



In this tutorial we will help you configure your computer or laptop running under Ubuntu 12.10/12.04 to use the Tor network system wide instead of your actual internet connection. This will help you hide your real IP address to protect your online privacy.

1. Tor Installation

To install Tor on Ubuntu, open the terminal and run these commands:

sudo apt-add-repository ppa:ubun-tor/ppa
sudo apt-get update
sudo apt-get install tor privoxy

During the installation, you will be required to add your username to the debian-tor group. Check on your username using the spacebar and press Enter:



You can start now the Tor network with this command:

sudo /etc/init.d/tor start

2. System Configuration

Via the Unity dash, open Nework Manager:


In the left pane of the window select "Network proxy," then enter the following settings:

Method:         Manual

Socks Host:   127.0.0.1          9050


You must leave other settings empty, then click "Apply system wide" to apply the new changes (root password is required). Via your web browser (Firefox or Google Chrome), open now this link to verify if Tor is well enabled on your system:

https://check.torproject.org/

If enabled, you may see this:


3. Configure The Terminal To Use Tor

Although we applied the Tor network on system wide, you will find out that only your web browsers are working with Tor. If you check for example your current IP address from the terminal with this command:

curl icanhazip.com

It will detect your real IP address not that generated by Tor. To be able to use the Tor network from the terminal we need to use the "proxychains" package which will allow us to force the tcp connection to follow through proxy. You can install it under Ubuntu with this command:

sudo apt-get install proxychains

Edit now the proxychains config file with this command:

sudo gedit /etc/proxychains.conf

Make sure these two lines are available:

# defaults set to "tor"
socks4 127.0.0.1 9050


Save your file and exit. To make sure  proxychains is well configured with Tor, check again your current IP address with this command:

sudo proxychains curl icanhazip.com

Here are now some other examples of using proxychains with Tor from the terminal to hide your real IP:

   a. Installing A Package:

sudo proxychains apt-get install pidgin

The Pidgin package will now be downloaded via the Tor network.

   b. Updating/Upgrading Packages

sudo proxychains apt-get update

sudo proxychains apt-get upgrade

   c. Force Applications To Use Your Tor Connection

To force for example Rhythmobox to use the Tor proxy, run this command from the terminal:

sudo proxychains rhythmbox-client

You can now use any commands from the terminal with proxychains.

Tuesday, September 4, 2012

SystemRescueCd 3.0.0


François Dupoux has announced the release of SystemRescueCd 3.0.0, a live CD containing a large number of data rescue and disk management utilities, based on Gentoo Linux. What's new? "Added support for loading extra SRM module files (System Rescue Modules); added support for UEFI booting from the CD-ROM on x86_64 using GRUB 2.00 (efi.img); updated standard kernels to long-term supported Linux kernel 3.2.28 (rescuecd + rescue64); updated alternative kernels to long-term supported Linux kernel 3.4.9 (altker32 + altker64); the rescuecd kernel image has been renamed rescue32 for better consistency; configured isolinux to automatically use the 64-bit kernel if CPU is capable; automatically use 64-bit version of FSArchiver and memtester if CPU is capable; reorganized and updated isolinux configuration and help messages; updated e2fsprogs to 1.42.5, GParted to 0.13.1, Partclone to 0.2.50." Here is the complete changelog. Download: systemrescuecd-x86-3.0.0.iso (347MB, MD5).

Wednesday, July 18, 2012

SystemRescueCd 2.8.1


SystemRescueCd 2.8.1, a Gentoo-based live CD with specialist utilities for data rescue and disk management tasks, has been released. From the changelog: "Updated standard kernels to Long-Term-Supported linux-3.2.23 (rescuecd + rescue64); updated alternative kernels to latest stable: linux-3.4.5 (altker32 + altker64); updated X.Org graphical environment and drivers to xorg-server-1.12.3; updated Grub2 bootloader to 2.00 (grub-0.97-r12 is also provided); updated Super-Grub2-Disk to version 2.00-beta1 (based on GRUB-2.00); updated lvm2 to 2.02.93, e2fsprogs to 1.42.4; updated GParted to 0.13.0, partclone to 0.2.49; removed Ranish floppy disk image; added spacefm-0.7.8 file manager." Download: systemrescuecd-x86-2.8.1.iso (381MB, MD5).

Tuesday, June 26, 2012

Download LiVES 1.6.2


LiVES, LiVES is a Video Editing System.
LiVES began as the Linux Video Editing System. Since it now runs on more operating systems, LiVES is a Video Editing System. It is designed to be simple to use, yet powerful. It is small in size, yet it has many advanced features.
LiVES is part editor, part VJ tool. It is fully extendible through open standard RFX plugin scripts.
LiVES lets you start editing and making video right away, without having to worry about formats, frame sizes, or framerates. LiVES will let you start creating your own tools, utilities and effects via the built in RFX builder.
LiVES is aimed at the digital video artist who wants to create their own content, the video editor who wants to create professional looking video, and the VJ who wants to captivate with spectacular images.

Download LiVES 1.6.2

Wednesday, June 13, 2012

Prevent Ubuntu from asking a password after resuming from Hibernate or Suspend



When you close the lid of your laptop and Ubuntu is running, the computer goes into Suspend mode. Same goes for chosing Hibernate from the shutdown menu, when the laptop goes into deep sleep and consumes less power. When resuming from these two states, Ubuntu will ask you for your password. If you’d like to get rid of this password field, you need to launch gconf-editor and navigate to apps > gnome-power-manager > lock. There you’ll find a checkbox for hibernate and one for suspend. Uncheck these and close the Configuration Editor. Next time you resume from Suspend and Hibernate, you won’t be prompted for a password.
You can still manually lock your screen before closing the lid by using Ctrl+Alt+L.

How to Color Man Pages & How It Works



In this tutorial I’ll show how to get some nicely colored man pages by adding several lines inside the .bashrc file, explaining what the code means and how it works.

Except for the eye-candy, colors may help when it comes to clarity, although some prefer the default monochrome approach. At the start of this article there is the actual code which can be copied and pasted inside the ~/.bashrc file, and which can be modified depending on each person’s preferences. If you don’t care about what it does you can just insert it in ~/.bashrc, restart your terminal and start reading some man pages to see how it looks (e.g. man man). After this part I tried to explain how this code works and how to modify it in order to get new ‘themes’.

The code
For this tutorial we’ll be editing the ~/.bashrc file, which is a hidden file located in your home directory which gets read each time a new Bash instance starts up. Bash reads all the commands found in this file and executes them (hence the rc part, which stands for run commands).
We will edit this file and add some lines which specify certain colors for the $LESS_TERMCAP variables.

export LESS_TERMCAP_mb=$(printf '\e[01;31m') # enter blinking mode - red
export LESS_TERMCAP_md=$(printf '\e[01;35m') # enter double-bright mode - bold, magenta
export LESS_TERMCAP_me=$(printf '\e[0m') # turn off all appearance modes (mb, md, so, us)
export LESS_TERMCAP_se=$(printf '\e[0m') # leave standout mode
export LESS_TERMCAP_so=$(printf '\e[01;33m') # enter standout mode - yellow
export LESS_TERMCAP_ue=$(printf '\e[0m') # leave underline mode
export LESS_TERMCAP_us=$(printf '\e[04;36m') # enter underline mode - cyan
Don’t forget to reset your terminal after entering this code in order for the changes to take effect, e.g. type reset or exit and start up another shell.
This will mostly use magenta and cyan as the colors. Next, I’ll explain what these lines mean and how you can modify the colors.

Explaining it

As you can see, there are several variables which are assigned different values. As shown in the comments after the # sign, every one is used when needed. When text is in bold (double-bright mode), the formatting option is set to bold and the color magenta.
Let’s take, for example, the following line:

export LESS_TERMCAP_md=$(printf '\e[01;35m') # enter double-bright mode - bold, magenta

This line could be broken into this:
  • the environment variable LESS_TERMCAP_md will be assigned the value to the right of the equal sign
  • the right side says execute the command between the $( and ) characters, just like the older ` ` did
  • printf is a command similar with C’s printf and means “print with format”. The characters between the double quotes specify a color and a font style (e.g. in this case, bold and magenta).
The part that is inside the double quotes are format specifiers like bold, regular, or color to be used. More on these can be found on Wikipedia, here.

Color codes

The color codes are as follows:
  • 30 – black
  • 31 – red
  • 32 – green
  • 33 – orange
  • 34 – blue
  • 35 – magenta
  • 36 – cyan
  • 37 – white
Some other escape codes which you could use include:
  • 0 – reset/normal
  • 1 – bold
  • 3 – italic/reversed
  • 4 – underlined
  • 5 – blink
You can check this by typing in a terminal something like:

printf '\e[31m'
printf '\e[32m'
printf '\e[37m'
So, if we have something like printf ‘\e[01;33m’ it means enter bold and color yellow, according to the listing above.

What about ‘export’?

export is a Bash built-in used to assign values to variables in such a manner that any subsequent application that runs in that shell will be aware of the variable’s value. If, for example, we would simply assign a value to a variable, say MYVAR=”this is my variable” and we would then issue echo $MYVAR, we would see that the variable’s value will be printed. However, try to make a simple script which would echo it, for example:

#!/bin/bash

echo $MYVAR

And then run it e.g. bash myscript.sh – you will see that the value is lost, not visible in the script. So this is where export is useful, because it will make any further script or application “see” the variable. When we invoke the man command, it will need to see the values for our LESS_TERMCAP variables.

More color schemes

Here is another color scheme:

export LESS_TERMCAP_mb=$(printf '\e[01;31m') # enter blinking mode
export LESS_TERMCAP_md=$(printf '\e[01;38;5;75m') # enter double-bright mode
export LESS_TERMCAP_me=$(printf '\e[0m') # turn off all appearance modes (mb, md, so, us)
export LESS_TERMCAP_se=$(printf '\e[0m') # leave standout mode
export LESS_TERMCAP_so=$(printf '\e[01;33m') # enter standout mode
export LESS_TERMCAP_ue=$(printf '\e[0m') # leave underline mode
export LESS_TERMCAP_us=$(printf '\e[04;38;5;200m') # enter underline mode





Samsung Galaxy S3 gets an early firmware upgrade

The best-selling Samsung Galaxy S3 handset has received its first over-the-air update, with UK users reporting a pair of firmware downloads.
The Android 4.0 device is not experiencing any issues, to our knowledge, but that hasn't stopped Samsung pushing out updates promising "Improved stability" and nothing else.
The 31.7mb download can be installed over Wi-Fi or 3G.
Slashgear is reporting, following the completion of the initial firmware update, that users are being prompted to download another smaller 15mb file, which also promises improved stability.

Taking care of business (TCOB)

The updates suggest that, even with no complaints from an already sizable userbase, Samsung may have spotted something its not completely happy with.
The company has enjoyed some incredibly good, almost Apple-esque feedback from users and critics, so it's good to see it staying on top of matters to ensure that remains the case.
If you haven't been prompted to download the upgrades yet, you can get them by visiting the software updates page within the Android OS settings menu
And, if you're still weighing up whether a 4.8-inch smartphone is really for you, check out our Samsung Galaxy S3 review.

Monday, June 11, 2012

SystemRescueCd 2.8.0

SystemRescueCd 2.8.0, a Gentoo-based live CD with specialist utilities for data rescue and disk management tasks, has been released. What's new? "Updated standard kernels to long-term supported Linux 3.2.19 (rescuecd + rescue64); updated alternative kernels to latest stable Linux 3.4.2 (altker32 + altker64); fixed USB installer script for Linux: usb_inst.sh; updated GPT fdisk to 0.8.5 (fdisk utility for GPT partition tables); updated FSArchiver to 0.6.15 to support recent features in Btrfs and ext4 file systems; updated firmware files in the initramfs from Linux firmware 20120502; Updated DBAN to 2.2.6 (hard drive disk wipe and data clearing program); updated GRUB 2 bootloader to 2.00beta6 (GRUB 0.97 is also provided); updated list of kernel modules to put in the initramfs (storage and network); do not attempt to find sysrcd.dat on extended partitions." Here is the complete changelog. Download: systemrescuecd-x86-2.8.0.iso (379MB, MD5).