Thursday, 27 April 2017
Canonical has launched Ubuntu 17.04 Zesty Zapus with various features and fixes and if you want to try it before upgrading to it, you can install a copy of the latest Ubuntu release in Virtual Box and check by yourself if you really need to upgrade.
In this article, we will show you how to install Ubuntu 17.04 in Virtual Box.
I assume that you have downloaded and set up Virtual Box already and have the Ubuntu 17.04 ISO file ready with you. You can download the ISO file from the link: Ubuntu ISO download page.
The first half includes setting up of Virtual Box, assigning storage and RAM and choosing the ISO file to boot from.
Open Virtual Box and click on New.
Give it a name - Ubuntu1704 and it will automatically update the Type and version. Also, specify the Memory Size (RAM) here. I would suggest you to go with at least 4 GB of RAM. Under Hard Disk option, Create a virtual hard disk now is selected, do not disturb it unless you know what are doing. Click Create, a dialogue box will appear as shown below.
You can select the file location for the VM drive you are creating. Specify the disk space you want to allocate to the Virtual Hard Disk you are creating for Ubuntu 17.04. Also, under the Hard disk file type, I prefer keeping VDI - VirtualBox Disk Image and keep the drive dynamically allocated.
Click on Create and you will see a New Ubuntu 17.04 Machine in the left panel.
Now, before you start this machine, the VM will need the ISO location to boot from. Click on Settings and under Storage section, you will see different options.
Under Controller : IDE section, click on Empty. Now in the right side under Attributes, click on the CD drive icon and choose the first option : Choose a virtual disk option. Locate the ISO you have downloaded for Ubuntu 17.04 and click OK.
The first part to install Ubuntu 17.04 in Virtual Box is done. Lets look to the second part. Remember that if you are not satisfied about the selections of memory or storage, you can click on Settings and always change that.
Now start the Virtual Machine by clicking on Start. Ubuntu will boot and the installation screen will appear. You will have the option of trying Ubuntu or installing it. We will have to install Ubuntu 17.04 in Virtual Box so that we do not need to boot it from the ISO each time.
Choose Install Ubuntu after selecting the language from the left side.
The next screen will ask you whether you want to download and install third party software for graphics, wifi, flash, mp3 and other media. Select it to save some time downloading each of them manually and click on Continue.
The next screen is Installation Type. Since you are installing Ubuntu 17.04 in Virtual Box, select the first option : Erase disk and Install Ubuntu. There is no need to create of resize partitions. Also, you can select to Encrypt the new Ubuntu installation for security and use of LVM for the new Ubuntu installation. Once done, click on Install Now. Ignore the warning screen.
Next screen will ask your location.
Select your desired Keyboard layout from the options and click on Continue.
The next screen will ask your name, your PC name, a username with which you will login and password along with it. Fill all the details and click on Continue.
The installation process will begin and it will take some time to complete.
Installation will take some time as it will download various third party plugins. Once done, you are all good with the Ubuntu 17.04 installation in Virtual Box. Once the installation process completes, shutdown the Ubuntu and start again. Congratulations, you have successfully installed Ubuntu 17.04 in Virtual Box.
If you face any problem in the installation process, let me know in the comments and I will try to solve it.
Sunday, 16 April 2017
Ubuntu 17.04 code named Zesty Zapus is the 26th release for Ubuntu and is available to the end users. The release was in development from some time and will be supported for 9 months from April. The new Ubuntu release will support Kubernetes, Docker, LXD and Snaps and contains various bug fixes and software updates. With Mark Shuttleworth announcing the shutting down of Unity DE, the 17.04 and 17.10 release will run Unity 7 only.
What's new in Ubuntu 17.04 Zesty Zapus
Running on Linux Kernel 4.10, Ubuntu 17.04 has various new features and updates.
- LibreOffice updated to 5.3
- Supports printers which allow printing without printer-specific drivers.
- 32-bit PowerPC support dropped
- Default DNS resolver is now systemd-resolved.
- For new installs, a swap file is used instead of swap partition.
- Apps provided by Gnome has been updated to 3.24.
- Calendar app has a week view now.
- Unity 8 is available as an alternative session.
and more. You can read the complete update logs here.
The Ubuntu 17.04 release will use a swap file instead of swap partitions making the use of OS a bit faster in a resource crunch situation. Also, the Snaps is now been supported across 10 distributions including Arch and Fedora. Snap is a packaging tool from Canonical. There is support for AMD Ryzen and Intel Kaby Lake processors.
Download Ubuntu 17.04 Zest Zapus
You can download the latest Ubuntu release from the official website : https://www.ubuntu.com/download/desktop. You can find download links and torrents links to download Ubuntu 17.04 Zesty Zapus.
Upgrading to Ubuntu 17.04 from Ubuntu 16.10
To upgrade to Ubuntu 17.04 from 16.10, open Dash and search for Software Updater.
- In Software Updater, Select Updates and set the Notify me of a new Ubuntu version drop down menu to For any new version.
- Press Alt + F2 and type update-manager which will open the update manager confirming you for a new release availability.
- Click Upgrade and follow the on-screen instructions to upgrade to Ubuntu 17.04 Zesty Zapus.
If you are running the Ubuntu 16.04 LTS release, I will suggest to stick to it and wait for the next years 18.04 LTS release since the 17.04 Zesty Zapus do not pack something great. However, if you are a Ubuntu lover and wants to remain updated, go for it.
Thursday, 6 April 2017
|Unity / GNOME|
In a surprising move, Mark Shuttleworth announced in a blog post the shifting of default Ubuntu DE Unity to GNOME for Ubuntu 18.04 LTS. Along with it, he also announced the shutting down of Convergence and Ubuntu Phones and that Canonical will no longer invest in them. Canonical has worked a lot over refining the Unity desktop over these years and the shift to the classic GNOME desktop environment is something which the Ubuntu users are finding hard to believe. Some Linux users who switched from Ubuntu just because they didn't like the Unity interface are more than happy, though.
Mark Shuttleworth writes:
I’m writing to let you know that we will end our investment in Unity8, the phone and convergence shell. We will shift our default Ubuntu desktop back to GNOME for Ubuntu 18.04 LTS.
He also wrote that Canonical will keep on investing in Ubuntu Desktop, servers, VMs, Cloud and IoT. The Ubuntu Desktop will feature GNOME desktop by default from 18.04 LTS and will get constant updates.
Now, there are 2 sides of this announcement. One side is happier with Ubuntu returning to GNOME who always found Unity horrible and switched to Linux Mint or other Ubuntu derivatives after the frustration Unity caused to them. The other side feels Unity was the thing that kept Ubuntu a different OS than other. If anyone wants to use GNOME, he can switch to Debian for example. Plus. spending a good amount of time and resources refining a DE and then ditching it is a bad move!
It's been 6 years when Ubuntu switched to Unity as default user interface and there are chances that Unity will continue as a community-driven project along side Ubuntu touch and Convergence. However, it won't be supported/invested from the company anymore.
Time will tell if this decision of switching from Unity to GNOME is right. However, shutting down the Convergence is undoubtedly not a good news. With the aim of single OS for different devices and plugging a phone to a desktop and a keyboard to use it as an equivalent to PC is a great thing. Microsoft is trying the same with Continuum and I had hoped Ubuntu will succeed the race. Now, with dropping the development there is no choice anymore!
Are you happy with the decision of GNOME over Unity? Why / Why not, let us know in the comments. Lets have a healthy discussion.
Saturday, 18 March 2017
This is an open letter to open source lovers not to take it too far.
A great legacy
Open source is a beautiful movement with amazing people behind it, the works of GNU/GNU/Linux Torvalds and Richard Stallman enabled millions of people to enjoy open source software around the world, from developing nations (like my country) to huge companies like Amazon and Facebook for little to no cost (I think they should give something back to the open source community by the way).
Feeling like you belong
When getting into the open source world you can’t help but to feel like you belong! Everyone is so warm and welcoming at the door, and you feel obligated to help, to do something to contribute to the combined effort of these people, did you know that great software like LibreOffice is written by volunteer effort? Pretty amazing! They aren’t getting paid, the whole thing is staying afloat with donations, and it’s so good I’m using it right now to write this post!
You start telling your friends and family about these great tools and amazing software products that they can have for free, and maybe you volunteer sometime lecturing about open source to people who are interested to know.
GNU/Linux is gaining attention!
GNU/GNU/Linux is becoming mainstream, I like that! They say that the year 2017 could be the year that GNU/GNU/Linux reaches 5% of the total desktop market share (GNU/GNU/Linux dominates the server and the super computer world), I’m trying to read anything I could get my hands on when it comes to GNU/GNU/Linux, but there is a new trend that I’m noticing that is really upsetting me.
You are using GNU/GNU/Linux, that is good, I’m glad you found an accepting community for you to spread your wings and reach your maximum potential, I am really! But that doesn’t give you the right to make fun or make little of other system users!
Be respectful of others
You aren’t better than anyone else! Using this system doesn’t make you better or less of a human being than another person!
Making a nice joke is one thing, but going as far as saying that system “X” is trash, and that you use it by force is a different thing, Windows for example has over 90% of market share, and chances are it was your first system, it’s everywhere. Are you saying everyone doesn’t know anything about tech and you are the only one who does?
This is turning into a form of fanboy-ism, something I tried to avoid for years! Useless debates like the never ending debate between Android and iOS, Pepsi and Coca-cola, the list goes on!
This energy wasted “bashing” other systems could be constructively used to raise awareness about open source, or even develop something that would help fix a nagging bug, that is much more useful in my opinion!
An eye for an eye makes the world blind
By the way, I am fully aware of what Steve Ballmer the former C.E.O of Microsoft said about GNU/GNU/Linux a few years ago, it doesn’t represent every windows user, and even if it did? You should be able to use your system freely and not care for what he says.
Everybody should have a choice of using whatever tools they see fitting, make it be Windows, Mac OS, or GNU/GNU/Linux, after all the open source movement is about freedom.
Don’t let yourself be consumed by the cycle of hate, .
What do you think? Is it right for the users of any system to bash other users because they think they are better? Or is it just fun and games?
This article is contributed by Muaad Elsharif (Twitter handle: @MuaadElsharif) who writes about Linux / Open Source on his blog https://muaadelsharif.blogspot.in/. We at BeOpenSource thanks Muaad for his contribution.
Monday, 13 March 2017
If you prefer Notepad++ over other source code editor, it's time for an update. Wikileaks has revealed in its update : "Vault 7: CIA Hacking Tools Revealed" how CIA has hijacked scilexer.exe with their own modified copy on a compromised PC in Windows. The vulnerability or security issue is not with Notepad++ but Notepad++ has sent an update where Notepad++.exe checks for the certificate validation in scilexer.exe before loading it, and if the certificate is missing or invalid, then it won't be loaded and Notepad++ fails to launch.
This vulnerability fix is mainly for Windows OS and not for Linux. There are other bug fixes and enhancements for which you will need to update to v7.3.3.
Notepad++ v7.3.3 bug-fixes and enhancements:
- Fix CIA Hacking Notepad++ issue (https://wikileaks.org/ciav7p1/cms/page_26968090.html).
- Fix mouse wheel to task list scroll crash bug.
- Fix flickering issue while switching back after modifying or deleting a document from outside.
- Support Motorola S-Record, Intel and Tektronix extended hex file formats.
- Improve multi-line tab: maintaining the selected tab position.
- Fix add char into word char list bug.
- Add Shift+Enter in Find dialog for searching in the opposite direction.
- Fix a regression that delimiter settings is not retained correctly.
- Add clear command button in shortcut mapper.
- Enhancement: file extension supported in Load/Save Session dialog if a session file extension is set.
Notepad++ team issues the warning along with the update which I quote:
Just like knowing the lock is useless for people who are willing to go into my house, I still shut the door and lock it every morning when I leave home. We are in a f**king corrupted world, unfortunately.
It's really a serious issue where a Government organisation is trying to record and analyse (without permission) everything you type. They may not (I assume) be interested in your coding skills or the blog posts I type in my Notepad++ but by hacking the scilexer.exe, it stops any red flags while the infected DLL does data collection in the background.
If you are Windows user, I would suggest you to immediately update to v7.3.3 and if you are on Linux, you can still update Notepad++ for a better performance.
Saturday, 25 February 2017
Do you want to check the Ubuntu version you are running in your system? Or are you in a public system and wants to check which version of Ubuntu it is running? This article will tell you how to check Ubuntu version when you don't know of it. There are two ways to do that, either through the terminal or from Unity tools. We will check the both ways.
Checking Ubuntu Version from the Terminal
If you want to check the Ubuntu version from the terminal, open one terminal instance and type the following commands :
This command will show you the Description, release and codename of the particular version you are running.
If you want to see only the release then use the following commands:
Similarly, you can use -s for only getting the release no., -c for codename, -d for description.
There is another way of finding the Ubuntu version by checking the release file from /etc folder. Execute the following command in terminal to get the detailed information:
VERSION="16.04 LTS (Xenial Xerus)"
PRETTY_NAME="Ubuntu 16.04 LTS"
You can get the Linux kernel version and more information through the uname command. Type the below command in terminal :
VERSION="16.04 LTS (Xenial Xerus)"
PRETTY_NAME="Ubuntu 16.04 LTS"
You can get the Linux kernel version and more information through the uname command. Type the below command in terminal :
In the output, you will find the kernel information.
Checking Ubuntu version through Unity
If you have got Unity in your system, you can check from there too. Open System Settings from the launch pad or through the Dash and click on the Details icon under System menu. This will give the Device Name, Memory, Processor, Graphics, storage and OS type along with the Ubuntu Version. The unity method will provide only the release and not the exact version no. for which you will have to use the terminal only.
So, next time if you are on your friend's PC or in your practical classrooms which is running Ubuntu and you need to know the Ubuntu version it is running, use any of the above method to check Ubuntu Version. Let me know in the commends if you face any difficulty.
Wednesday, 1 February 2017
Online source code repository similar to github, GitLab went offline for more than 12 hours after one of the SysAdmin deleted the wrong folder in production. The service has been restored as of now and the data loss would impact less than 1% of the user base specifically peripheral metadata that was written during a 6 hours window.
GitLab, in a Google Docs File kept updating their operations. The possible impact according to the docs are :
- ±6 hours of data loss
- 4613 regular projects, 74 forks, and 350 imports are lost (roughly); 5037 projects in total. Since Git repositories are NOT lost, we can recreate all of the projects whose user/group existed before the data loss, but we cannot restore any of these projects’ issues, etc.
- ±4979 (so ±5000) comments lost
- 707 users lost potentially, hard to tell for certain from the Kibana logs
- Webhooks created before Jan 31st 17:20 were restored, those created after this time are lost
Also, there were several problems encountered during the restoration process.
- LVM snapshots are by default only taken once every 24 hours. YP happened to run one manually about 6 hours prior to the outage
- Regular backups seem to also only be taken once per 24 hours, though YP has not yet been able to figure out where they are stored. According to JN these don’t appear to be working, producing files only a few bytes in size.
- SH: It looks like pg_dump may be failing because PostgreSQL 9.2 binaries are being run instead of 9.6 binaries. This happens because omnibus only uses Pg 9.6 if data/PG_VERSION is set to 9.6, but on workers this file does not exist. As a result it defaults to 9.2, failing silently. No SQL dumps were made as a result. Fog gem may have cleaned out older backups.
- Disk snapshots in Azure are enabled for the NFS server, but not for the DB servers.
- The synchronisation process removes webhooks once it has synchronised data to staging. Unless we can pull these from a regular backup from the past 24 hours they will be lost
- The replication procedure is super fragile, prone to error, relies on a handful of random shell scripts, and is badly documented
- SH: We learned later the staging DB refresh works by taking a snapshot of the gitlab_replicator directory, prunes the replication configuration, and starts up a separate PostgreSQL server.
- Our backups to S3 apparently don’t work either: the bucket is empty
- We don’t have solid alerting/paging for when backups fails, we are seeing this in the dev host too now.
GitLab in it's blog said, "Losing production data is unacceptable, and in a few days we'll post the five why's of why this hapened and a list of measures we will implement".
Twitter is praising GitLab for the transparency with which the company has handled the things. Everything was updated through the blog / twitter account and the Google Docs. This was a really great way of keeping the users and press updated and GitLab surely deserves a praise for it. Though, I doubt neither GitLab nor any other organisation will even dream of any such worst situation.