Linux Tutorial

The terminal is the key instrument in each of its various Linux distributions available today. It is therefore very important to use it as convenient as possible.

Guake is a new way to bring up the terminal, allowing not only a convenient use of the same, even integration within a more pleasant workspace.

Once started, Guake can recall the terminal keyboard – using the F12 key by default – which is presented differently from how we used to. It is not the classic open window, but sort of semi-transparent layer that is placed on top of all windows that are open on the workspace, which is instantiated inside the terminal. In short, it is a sort of drop-down terminal that plugs from the top of the screen. In addition to providing support for tabs, Guake also has a series of pre-configured keyboard shortcuts that allow you to use it.

The application is widely configurable. First, you can choose the shell interpreter that you prefer to take lending itself well to different uses. In addition, you can manage other parameters like autoscroll, hotkeys and appearances including fonts used in graphics, color and background. Guake is available for several Linux distributions including Ubuntu, Debian, Fedora, Gentoo. To install under Ubuntu Guake the following command:

     sudo apt-get install Guake

As you can see, this is a version of Ubuntu that mounts the lightweight LXDE as the default DE in order to respect the longevity and performance of the entire system. What you need is VNC, the zip file with Ubuntu for Android and follow the guide below.

Obviously, this guide serves to introduce another system in addition to the native, but you have to do it carefully, because you risk everything Brikka!

Warning! I remember that the possibility of Brikka is always just around the corner and then I do not assume any responsibility for any “loss” of all!

1. Download http://www.bisme.net/update_b1_b2.zip
2. remove the /sdcard/ubuntu
3. open the terminal on, go to the folder you created, start ubuntu, and write

      sh update

• do a reboot and when finished, write

      ubuntu config

You can now reconfigure your resolution vnc

The Gnome Terminal and Synaptic FIX have the same installation like update b1_b2 (b1_b2 must be installed first)
http://www.bisme.net/update_b2_b3.zip

This is the second version. It is not upgradeable, so you have to delete the old /sdcard/ubuntu first.

[Via adb uninstall old]

adb remount
adb shell rm /system/bin/ubuntu*
adb shell rmdir /System/ubuntu

[Uninstall the old terminal]

su
mount -o remount,rw /system
rm /system/bin/ubuntu*
rmdir /system/ubuntu

[Requirements]

• A root folder (busybox not required, but only Xoom)
• download it from http://www.bisme.net/ubuntu.zip
• as an option you can use a VNC client as android-vnc

[Step by step]

• Extract the zipped file to /sdcard/ubuntu
• cd to this directory and type

      su

• then

      sh install ubuntu

you have to answer some questions, if you want you can just click on enter. after you have rebooted, open the terminal and write

    su

then

    ubuntu start

then

    ubuntu shell

wait a minutes, you are installing the most complete version of ubuntu on the Internet, otherwise you have to install the Desktop aspettari ubuntu, you must be sure that you have a stable connection

    installubuntu

save and exit window Android write (before you enter the Password)

    ubuntu vnc

connect via: localhost:5901 using vnc client and password that you selected.

[What you]

• you can start with ubuntu start
• Shell with Ubuntu you can open a bash session
• with ubuntu you can start the vnc vncservice
• Stop please stop with ubuntu ubuntu
• with ubuntu ubuntu uninstall uninstall script from the system (the /sdcard/ubuntu)

with ubuntu you can access:

• by android /dev ubuntu/dev(fdisk/dev/block/mmcblk0 that it’s okay NOT TOUCH/ or dev/block/mmcblk1 Brikko Android
• by android /system to ubuntu/android/system
• Android by date /ubuntu/Android/date
• by android /mnt/sdcard to ubuntu/adnroid/sdcard

[What works]

• android-vnc with gnome (bluetooth keyboard and mouse)
• screen
• LibreOffice
• Gnome Terminal

and many others

[What does not work]

• Firefox 4
• Chromium Browser
• Ubuntu Software Center

[The technical side]

• Ubuntu Natty Narwhal (11:04) from http://elinux.org/BeagleBoardUbuntu
• dd to create the image (the filesystem on the disk only supports files images formatted with ext2
• positioned adb /sdcard/ubuntu/img/ubuntu.img
• chroot env
• tightvnc, gnome-session, maximus

[Changelog]

• no image supplied, created from an archive. tar
• Android script rewritten to use their own bash and busybox
• the full version of ubuntu / dev
• Ubuntu 11.04
• using the sdcard
• the system should not be reinstalled if you want to install the script
• add uninstall script part of the Android (the mountpoint is located on /sdcard/ubuntu/root)
  

VMware virtual machines

The boot screen of the Virtual Machine in VMware, very often, takes less than a blink of an eye. How to display it longer? Simply insert a new parameter in the configuration file.

VMware, as we all know, is virtualization software that comes in several versions: those addressed to the public desktop VMware Player, Free, and the counterparty paid VMware Workstation. The virtualized operating system is in all respects similar to a real.

As known, the computer always starts with the usual boot screen, which are searched for bootable devices such as CD ROMs, hard drives and so on. This screen, which is the option to press ESC to select a device to boot, and takes a few seconds in reality, in the virtual machine.

How, then, to use the commands in this screen without it running away?

Simple. Each virtual machine also virtualizes your BIOS and your boot screen, then in the configuration file can set rules on the matter.

In the context of this article, we will insert a rule in the configuration file to ensure that the boot screen is displayed for a period of time at our discretion.

We close the virtual machine

This change must be made to the virtual machine off. Then make sure that the VM is involved arrested (NOT pause) and, just to be safe, that VMware is closed.

Localize the configuration file

The configuration file of the virtual machine vmx format and is located within the directory that contains all other files. Generally, unless otherwise set by the user, all virtual machines are located in My Documents, My Virtual Machines subfolder.

Once you have located the directory, we find that as the only vmx file name has the name assigned to the virtual machine. There will be several files with that name, but the only one that interests us is what, precisely, vmx format.

Select it with the right mouse button and in Open With, choose our favorite text editor (or use the items in the same context menu, choose according to the editor).

I would recommend Notepad++, especially for reasons like these. Once opened, the file will look like.

VMware virtual machines

We make the change

In any position, preferably at the beginning of the file, insert the line = 4500 bios.bootdelay within appropriate carriage returns, so that the file looks like this.

The number 4500, in milliseconds, indicates the length of the screen and can be customized at will to suit your needs. In principle, I remind you that a second is expressed with 1000 milliseconds.

Save the file and start the virtual machine, so that changes can be made. Ensure that the screen placed at the beginning, not the same as that which appears after the application of the technique.

While the first owner and has the logo used commands, the second depicts a real boot screen.

Join our facebook page, and you will report daily all new content on numango.com!

How to set up a VPN server (PPTP) with CentOS

Have the resources on the local network even when you are physically out of the office is a goal within reach of any system administrator. Just a machine with CentOS, just and open source software are some tips to configure all the best.

As it is configured up to now, the server “switch” traffic between the VPN and the Internet interface in a “transparent”.

However, if the machine is also equipped proxy “Squid” (perhaps with some additional filtering), it might be interesting also to ensure that all requests from VPN clients are handled by this component.

Adjust the routing

Open the file with gedit used for routing (was saved in /root/routing.sh, if you had followed the instructions of the wizard dedicated) and identified the portion of text delimited by the indication ============ BLOCK OF INSTRUCTION THAT ENABLE THE ENTRY ============ VPN (it’s towards the end of the file).

Just below, you should find 3 blocks of 5 lines each: get rid of all signs (#) to find the beginning of the 15 lines in question

Save the file and close the editor.
Everything is ready

At this point, reboot the server for changes to take effect (or run the script again and restart Squid with routing service squid restart) and that’s it: all requests for web access from the VPN client will be handled by the proxy

Clients may have some difficulty managing the pages transmitted via HTTPS, but as we said, everything is normal.

If this limitation is unacceptable, the alternative is to allow users to access encrypted pages without going through Squid to do so, insert the # character at the beginning of the following lines in the file routing.sh (are the last of the block of instruction devoted to the combined use of Squid VPN)

# $ IPT-t nat-A PREROUTING-i ppp0-p tcp - dport 443-j REDIRECT - to-port 3129
# $ IPT-A INPUT-j ACCEPT-m state - state NEW, ESTABLISHED, RELATED-i ppp0-p tcp - dport 3129
# $ IPT-A OUTPUT-j ACCEPT-m state - state NEW, ESTABLISHED, RELATED-o $ WAN-p tcp - dport 443
# $ IPT-A INPUT-j ACCEPT-m state - state ESTABLISHED, RELATED-i $ WAN-p tcp - sport 443
# $ IPT-A OUTPUT-j ACCEPT-m state - state ESTABLISHED, RELATED-o ppp0-p tcp - sport 443

Useful, but not conclusive

For completeness, I invite you to note that the use of Squid via VPN is simply a measure intended to prevent the server for any unlawful or inappropriate circles, but is in no way a protection for the client: if a user of VPN would work around the block, just disconnect from the virtual network and direct access to the sites as usual using the supplied connection to the computer, or set up the VPN in a “split tunnel”.

See previous post :

• CentOS: How to set up a VPN server (PPTP) Part.1
• CentOS: How to set up a VPN server (PPTP) Part.2
• CentOS: How to set up a VPN server (PPTP) Part.3
• CentOS: How to set up a VPN server (PPTP) Part.4

How to set up a VPN server (PPTP) with CentOS

Have the resources on the local network even when you are physically out of the office is a goal within reach of any system administrator. Just a machine with CentOS, just and open source software are some tips to configure all the best.

As anticipated at the beginning, the technique proposed here is not exactly “old hat”. Consequently, there are many aspects that may hinder the proper functioning of the VPN.

This page of the official documentation offers a wide array of tests, tips and solutions to various problems: I have summarized below the most common.

The client can not connect

If the service is started (you can check quickly by giving service pptpd restart), but clients can not connect, it means that there is some “barrier”.

Move the two computers within the same LAN and try again: If it works, almost certainly means that you have properly configured the router.

Otherwise, the firewall may not let the traffic properly: try to disable it temporarily (perhaps by disconnecting everything from the Internet to prevent security problems!) And try again.

The connection is established but the computer does not see

If the VPN connection is established correctly, but PCs are not accessible, could be a configuration problem.

On the client, run ping 192.168.0.201 (substituting the appropriate IP address of VPN server) and Make sure you get a response.

If not, run yum install tcpdump-y on the server to install a software-capture packets, then proceed with tcpdump-n-i ppp0 and try again to ping: If the terminal does not appear to informational messages, means that the client is not “talking” in any way with the server.
Server and VPN client are spoken, the VPN client and PC LAN no

Trace the cause of this problem is far from easy.

Check that the server itself is having problems communicating with other PCs on the LAN and, perhaps, try to download an updated version of the script routing.

Unable to access files and printers

If everything works, but you can not share resources, you have probably a problem with the specific features of Windows: See the article “Setting up a computer network (LAN)” for more information.