Linux User Group of Mauritius Promoting open source software in our beautiful island

27Mar/170

Developers Conference 2017 – Linuxfest

Posted by Ish Sookun

Hey folks! We're back. It's time to meet up and have geek fun at the Developers Conference 2017. At its third edition, I am sure that, this great event of the Mauritius Software Craftsmanship Community will not disappoint you. Of course, there must be something in menu that will suit your appetite.

Shelly and I have planned our DevCon weekend carefully. We'll be there all three days.

I have a session on NGINX Microservices scheduled at 10h30 on Saturday at the Educator 2. The rest of the time that day you would find me hopping between Voilà Hotel and Flying Dodo helping folks from the Linux User Group of Mauritius with the full-day activities.


LUGM - Developers Conference 2017

Members of the Linux User Group will run a Linuxfest and help keen enthusiasts with Linux installs & troubleshoots in the conference room of Flying Dodo. You're all invited to come share your knowledge. We will be running demos on a projector and if you have some cool stuff about Linux which you'd like to share then get in touch, it'll be great to have more fellows around advocating Free Software/Open Source. Ping LUGM members Nirvan, Nadim on Twitter or get in touch with Ajay or Ronny on Facebook.


Care to tweet? Use the hashtag #DevConMru.

15Mar/170

Open and not extract .docx, .xlsx and .pptx files in the latest Gnome 3

Posted by Avinash Meetoo

In the latest version of Gnome 3, a subtle change was brought to Nautilus, the file manager, to automatically extract the content of a ZIP file in a new folder when it is double-clicked on instead of open an application to do so. The problem is that Microsoft Office files (.docx, .xlsx, .pptx, etc.) are ZIP files. This means that double-clicking on a .pptx file extracts its content instead of opening the file in, say, LibreOffice Impress!

This makes life miserable for all those who need to open Microsoft Office files on a regular basis and, of course, this is a bug (as acknowledged by the Gnome people  and the Red Hat / Fedora people).

Fortunately, it is quite easy to make Nautilus become sane again. Open Preferences and in the Behavior tab, unselect “Extract the files on open” in the Compressed Files section.

Phew!

15Mar/170

Open and not extract .docx, .xlsx and .pptx files in the latest Gnome 3

Posted by Avinash Meetoo

In the latest version of Gnome 3, a subtle change was brought to Nautilus, the file manager, to automatically extract the content of a ZIP file in a new folder when it is double-clicked on instead of open an application to do so. The problem is that Microsoft Office files (.docx, .xlsx, .pptx, etc.) are ZIP files. This means that double-clicking on a .pptx file extracts its content instead of opening the file in, say, LibreOffice Impress!

This makes life miserable for all those who need to open Microsoft Office files on a regular basis and, of course, this is a bug (as acknowledged by the Gnome people  and the Red Hat / Fedora people).

Fortunately, it is quite easy to make Nautilus become sane again. Open Preferences and in the Behavior tab, unselect “Extract the files on open” in the Compressed Files section.

Phew!

8Feb/170

8 bad habits Rich Dad says we have

Posted by Avinash Meetoo

While travelling in India in December, I stumbled upon Rich Dad Poor Dad by Robert Kiyosaki. I read it cover to cover in a few days, taking notes while discussing a lot with Christina and the kids. The book is an eye-opener on a number of bad habits or beliefs we all have:

Naturally, I do not agree with everything Robert Kiyosaki says but his arguments are very interesting to read and think deeply about.

Have fun!

Tagged as: No Comments
31Aug/160

Software Engineering needs to be taught by Software Engineers

Posted by Avinash Meetoo

complexity_small

Software is eating the world.

Quoting ACM:

The availability of qualified software engineers has not kept pace with the demand from industry, so that systems are designed and built by people with insufficient educational background or experience.

In other words, Software Engineering is Hard and we do not have enough Software Engineers to create and maintain all the software which is eating the world. The fundamental reason is that software is unlike all other kinds of engineering artifacts (such as a bridge, a house or a computer):

  • Software is abstract and invisible.
  • Software has both static and dynamic properties.
  • Software is intrinsically complex in terms of its organization.
  • No universal measures of quality exist for assessing a software product.

Furthermore,

  • The manufacturing cycle for software products is not a significant element in software development, and it mainly involves the needs of distribution mechanisms.
  • Software does not wear out.

Quoting ACM again,

  • Software engineering practices are therefore largely concerned with managing relevant processes and with design activities.
  • A high-quality faculty and staff is perhaps the single most critical element in the success of a Software Engieering program.

And they conclude,

  • Faculty members who have a primarily theoretical computer science background might not adequately convey to students the engineering-oriented aspects of software engineering.
  • Faculty members from related branches of engineering might deliver a software engineering program or course without a full appreciation of the computer science fundamentals that underlie so much of what software engineers do.
  • Faculty members who have not experienced the development of large systems might not appreciate the importance of process, quality, and security.
  • Faculty members who have made a research career out of pushing the frontiers of software development might not appreciate that students first need to be taught what they can use in practice.

In other words, faculty members who teach Software Engineering need to be Software Engineers themselves. And this is là où le bât blesse (the main problem) in most universities: those teaching cannot do! This is true abroad but also true in most (all?) universities in Mauritius.

Mauritius needs universities with teachers who are doers and who know how to make students become doers.

And this needs to happen now!

15Jun/160

Automatically raise windows in Gnome

Posted by Avinash Meetoo

20160615-automatically-raise-windows

I love Gnome 3… except when I am using a terminal, decide to launch Chrome by clicking on its icon in the Dash and not realising that the terminal still have focus despite Chrome being shown on screen. Consequently, typing, say, www.noulakaz.net and pressing enter only sends these keystrokes to the terminal (despite Chrome being shown) with potentially serious consequences.

But lo and behold, I have just found a solution. Just launch the Gnome Tweak Tool as shown above and put “Automatically Raise Windows” to ON.

I have regained my sanity!

15Jun/160

Automatically raise windows in Gnome

Posted by Avinash Meetoo

20160615-automatically-raise-windows

I love Gnome 3… except when I am using a terminal, decide to launch Chrome by clicking on its icon in the Dash and not realising that the terminal still have focus despite Chrome being shown on screen. Consequently, typing, say, www.noulakaz.net and pressing enter only sends these keystrokes to the terminal (despite Chrome being shown) with potentially serious consequences.

But lo and behold, I have just found a solution. Just launch the Gnome Tweak Tool as shown above and put “Automatically Raise Windows” to ON.

I have regained my sanity!

1Jun/160

Vagrant box export and import

Posted by Ish

I’ve been a VirtualBox user for a few years but I started working with Vagrant only recently. Vagrant provides an easy-to-use portable environment on top of virtual machine providers like VirtualBox, VMware, AWS etc; at least that is what is written everywhere.

While the internet abounds with articles and «expert» answers about how to work with Vagrant, I stumble upon a lot of blurry advice in needy times. The last resort, though not very tempting, is the official documentation. I say not very tempting because of the amount of reading required for just one set of command options.

Vagrant box export and import

Hashicorp, the company that funds the full-time development of Vagrant, hosts a catalog of Vagrant boxes for the different virtual machine providers, which is called Atlas. Let’s look at the command that is used to add a box to Vagrant.

vagrant box add opensuse/openSUSE-42.1-x86_64

In the above command opensuse is a user of Atlas and openSUSE-42.1-x86_64 is the name of the box. You might need the --provider option if you’re not using VirtualBox. Once the box has been added, it can be initialized as follows:

vagrant init opensuse/opensuse-42.1-x86_64

The command creates a Vagrantfile in the current directory with a lot of commented lines which you can uncomment to specify needed options with your Vagrant box (e.g shared folders, set memory etc). The following line in the file tells vagrant which base to use when provisioning the virtual machine the first time:

config.vm.box = "opensuse/opensuse-42.1-x86_64"

To start up the Vagrant box we’ll do vagrant up and a bunch of messages depending on the Vagrantfile parameters will show up (e.g SSH port forwarding). Next we do vagrant ssh to jump inside the Vagrant box. The first time the Vagrant box is started, a virtual machine is provisioned in VirtualBox (since that is what I am using as provider). At next boot the VM will jump to normal startup unless «provisioning» options are specified.

As Vagrant users enjoy easy portability of the boxes, the same can be exported following this quick procedure:

vagrant package --output opensuse-devel.box

Say you have set up a development environment on the openSUSE box and you need to share the same with other developers. The above command packages the virtual machine in one file, in our case it’s called opensuse-devel.box. Next each developer needs to add the box as follows:

vagrant box add openSUSE-devel opensuse-devel.box

I am naming the project openSUSE-devel for easy reference.

Sure, if not executed from the directory containing opensuse-devel.box then the full path to the file should be used. It makes the box available to Vagrant and a machine can then be initialized.

vagrant init openSUSE-devel; vagrant up

This creates the Vagrantfile and fires up the box. When one needs to destroy the box, just execute vagrant destroy and the virtual machine will be gone.

The post Vagrant box export and import appeared first on HACKLOG.

Tagged as: No Comments
23May/160

Developers Conference 2016, day 3 with openSUSE bug hunting

Posted by Ish

I had my «openSUSE bug hunting» presentation scheduled at 09h30 this morning. I’m usually very lazy on Sundays but the enthusiasm of the Developers Conference is just an amazing feeling. Though we live on a small island, we get to meet some people maybe just once a year during this fun event. I picked up Shelly on the way and we reached Voilà Hotel at 09h05. Right at the hotel entrance Yash was waiting, he might have seen us coming. We went upstairs chatting and met JoKi. My presentation was scheduled at the Accelerator and I thought I’d just go and test the gear. Aargh! The TV had only HDMI cable and my ThinkPad had VGA & a Mini DisplayPort. That said, I needed an adapter. Joffrey who came around greeting everyone had a HDMI to VGA cable, which he lent me. At that same time JoKi also came with a Mini DisplayPort to HDMI convertor. Great! Then I had an adapter plus a backup.

I mirrored my laptop display and checked if everything’s fine. All good and it was 09h30.

Developers Conference 2016, openSUSE bug hunting

Thank you for the photo, Shelly :)

However, folks were still coming, so we thought let’s just wait till 09h45 giving a chance for others to arrive. Indeed I started at 09h45 sharp with a 3/4 full room and just a few minutes later it was «house full». That was great and a true encouragement though a Sunday morning.







Thank you for the (re-)tweets folks. :D

I chose the title of my prez «openSUSE bug hunting» from a blog post I wrote in 2013 while running «release candidates» of openSUSE. Starting the presentation I spoke about how some folks might organize special events working to hunt and find bugs, while some bugs we just encounter when doing regular tasks. What do we do when we find one of those bugs? Do we just ignore and think, «it’s just an error, nothing more», and we continue work? Do we search on the internet whether others encountered similar errors and if there is a fix? Few people ever consider filing a bug report through the right channel, unless it’s just a «button» away like some applications (e.g web browsers) offer.

Bug reporting most of the time require some information gathering from the system; that is where I took the presentation. Before diving further into the system though, I opened a few bug reports from openSUSE Bugzilla to show as example. I also gave a quick overview of the openSUSE Build Service and openSUSE Connect. That helped show the audience how to find package maintainers and get information about official and non-official packages.

I did not have slides; but I rather fired-up an openSUSE Vagrant box inside which I had setup an environment for demos. The rest of the «talking» happened within the Vagrant box. We looked at how to obtain system information using command-line utilities and from the /proc fs. Next we looked at digging for application error info in log files. We played with systemctl and journalctl which gave us clear and concise information about application states. We then queried using rpm and its various options to get as much information about packages that we can use when filing the bug report. At that time an openSUSE user from the audience said we can also use zypper to search for installed packages on the system. Yes, indeed, but rpm -qa | grep php shows no clutter compared to zypper se php. I however grabbed the opportunity to tell the audience that folks having a «debian lifestyle» can still type aptitude equivalents to search and install packages from the command-line; thanks to the «zypper-aptitude» compatibility scripts written by Bernhard M. Wiedemann.

All while we continued digging for application errors and how to search and sort things from the logs; I did a quick demo using Nginx and PHP-FPM.


We talked about the need of default configuration files after installing PHP 7 and that such changes need to be addressed with the «openSUSE factory» guys.

It was near 10h30 and Jeshan signaled me that the next speaker had already come. I asked for a last 5 mins to show something quick using the «strace» tool. Actually a university student asked me a question before the event and I invited him to come to the prez and ask the question again so we could altogether see how tracing tools can help us find useful information for bug reports. That part of the prez might be good for a separate blog post. I sincerely have to apologize to the next speaker if he is reading this post; we started 15 mins late and that surely must have impacted other presentations.

Eddy and I talked about work stuffs after the presentation. Then some of us went to Bagatelle food-court for a mini-break. When we came back Sun was preparing his gear for the next presentation. He talked about grid systems, explained what are decks & cards and how it’s used on lexpress.mu. He showed some hidden features of lexpress.mu, like what happens when you type «heart» or «superlsl» while you’re on the homepage and how the text is read if you type «kozer» while you’re on an article page.


Sun demoed the «live article» feature of lexpress.mu and the work needed behind to keep it light, simple and fast. He talked about «facebook instant articles» and definitely we’re proud to be the first media group, not just in Mauritius, but in the African continent to deploy the same.


After Sun’s presentation I met my ex-colleagues and we went for a pizza & beer lunch at Flying Dodo.


The pizza being late and as the Developers Conference closing ceremony had started Shelly, Ubeid and I rushed back.

JoKi’s wife, Mary Jane, Vincent, Louis, Arnaud and a few others, we had figured how to hijack JoKi’s speech and bring on some more party time to celebrate JoKi’s birthday. Yeah, he’s getting old, now it’s confirmed as he turns 40. Ubeid quickly edited some slides and we told JoKi that as he finished his speech thanking everyone, we had a quick stuff to show; some sort of observation we’ve made. Ahaan! That’s when Arnaud, helped by Mary Jane’s cousin, they brought that big cake along with its table.

Everybody cheered! Everybody laughed. We all had fun, we had cake, we took crazy photos and celebrated the end of Developers Conference 2016.

Developers Conference 2016

Developers Conference 2016

Developers Conference 2016

The post Developers Conference 2016, day 3 with openSUSE bug hunting appeared first on HACKLOG.

Tagged as: No Comments
21May/160

DevConMru 2016, day 2 – Linux Installfest

Posted by Ish

It was Saturday morning and I found myself rushing to be at Flying Dodo just in time. Oh, to be precise «not in time» but like 15 mins later than I expected to be, that 09h45. The night before I got busy preparing the box of openSUSE goodies, sorted the stickers, pamphlets, DVDs and cheat sheets. Little I knew that folks would like those so much. I would tweet as I got the pack ready.





Shelly and I were the first geeks to reach Flying Dodo. While I would setup my laptop with the projector, she prepared the tables with the stickers and cheat sheets.

Developers Conference, Linux Installfest

The first few geeks came shortly afterwards. Ronny and Ajay from the Linux User Group of Mauritius came along with their gear. Oh, this little gang from the University of Mauritius hopped in and yes we were under attack. We also received the visit of folks from the PHP Mauritius User Group.



The morning session was great. Ajay, Pritvi, Ronny and Avish helped people getting their laptop Tux’ed either with Ubuntu or with openSUSE. Meanwhile I got to run an interactive session with the university folks with a command-line walk-through.


There was a question about email headers. I showed email headers from my Gmail account and also from Thunderbird. We talked a little bit about IETF RFC 2822 and together we looked at some of those colon-separated field values. Ajay gave us a simple yet clear explanation on SPF and DKIM. We did a ‘dig’ on a couple few domains to read the TXT records. Ajay explained about hard-fail and soft-fail in the SPF records and how they affect delivery of email.


I tried answering other questions that popped up; covering various topics like SSH, file permissions, etc, and we had real fun during that interactive session.


Jeshan joined us later after his AWS Lambda presentation at Voilà Hotel and offered a little support to Ashmita who tried installing openSUSE (dual boot) on her laptop. Mission was successful! It was great to meet Bernard who got an Ubuntu dual-boot on his laptop and Nirvan Mahadooa who wanted to meet the Linux geeks. I really hope we can continue the geek chat at a later time folks.


Some of us stayed till dinner-time at Flying Dodo sharing «samousa», pizza and beer. Oh, Shelly and I had non-alcoholic drinks. :D

Developers Conference day 2

The post DevConMru 2016, day 2 – Linux Installfest appeared first on HACKLOG.

Tagged as: No Comments