Google Hates Blogs?

As of late I’ve been noticing that a lot of blog posts are not appearing in Google. A similar behavior was found by Marco Arment. Sure, my blog isn’t really the most relevant piece of journal in the internet.

Amusingly, I think the crawlers are doing their job. However, what goes on their results is being filtered. For example, all the tags pages (linux, programming, etc) have been thoroughly indexed by Google. Only ONE article I have written made it to the index. It could simply be a rule set to withhold any of the following URI [site]/posts/* where posts already determines the resource is in fact a blog post.

In a related note, I don’t know if I’m crazy but in the past you could actually search blogs. It was one of my favorite features from Google as you could really find a lot of educational material that websites couldn’t provide.

Will this keep me from writing posts? Not really. I’m not popular now, and I will not be popular in the future. Even if I was popular, I don’t think people should write to appear in a search engine. It kills the very notion of why weblogs exists in the first place, pretty sure it’s not for SEO or anything related to search engines.

Site Update – 2015-02-13

I spent this friday cleaning up the theme. I’m overly pleased on all the changes that have been done today. The site should provide useful metadata to crawlers, and of course it’ll be making it easier for results to become revelant. Quite nice, right?

I have yet to write more articles for my blog. Ultimately, I don’t want to just write guides for WINE, or make small posts of little progress. That’s what I’d love to say, sadly my time is limited; even simple cleanup tasks like the one I did today took a few hours to complete. This is simply because initially the theme I’m using was for Movable Type and I ported it to Pelican so yea, it was meant to be messy.

Good news? Nuja is closing in for a release. So if you are a Pelican user, be on the look out!

A Quick Review of OpenSUSE Tumbleweed!

OpenSUSE{ .center }
Today, I’ll be giving my impressions of OpenSUSE Tumbleweed, as of today, February 11, 2015. Who is this post for? Well, generally speaking it’s for everyone. But, if you must know I recently jumped to OpenSUSE from Arch Linux. I had my fair of struggles, regardless, I guess I should go ahead and say that OpenSUSE KDE is still the best out there.

Installation

The installation of OpenSUSE Tumbleweed was rather straightforward. The installer has been polished; I noticed it’s faster than the past installations I’ve done of OpenSUSE.

I had a really good experience using the partitioner provided by the installer. By far one of the best I’ve used, albeit a bit slow, however the user interface is so friendly and straight to the point.

Impressions so far

After the installation of OpenSUSE I was met with a unique theme in the display manager and desktop. The first hours of using OpenSUSE were spent restoring my data, and installing all usual applications. There were no crashes as far as I remember.

YaST

Volume Manager

One the reasons I switched to OpenSUSE was pretty much the need to automate some tasks (samba configuration, user management, printer, etc). YaST’s the perfect candidate for the job. Another reason for switching to OpenSUSE was the KDE experience, which is by far one of the best experiences.

Where YaST still fails is how slow it is. YaST takes a while to read and write configuration files. Launching the software management takes patience if you are used to applications like Apper which doesn’t take long to give you the results you want in a timely manner.

Zypper, zip it!

Coming from Arch Linux and jumping straight to OpenSUSE gave me headaches. Starting with the package naming in OpenSUSE, and locating multilib packages to compile applications like WINE 32bit work. One of the saddest thing of zypper is that even if you do sudo zypper si -d wine-32bit it would look for the 64bit devel packages.

Another thing to point out of Zypper is how slow it is. You’ll wish you had pacman back.

Repositories, Repositories, Repositories!

Software Manager
As someone who started using OpenSUSE seriously it dawned on me that OpenSUSE comes with two repositories with critical software. The Open Source repository and the Non-OSS repository.

Not all the software you want is there. This will hit you as you start looking for software. For example, I use Cantata and Music Player Daemon, they are incredibly popular and I’ve yet to find it in the main repositories.

For this, you’ll have to enable Packman repositories which give you the essentials, multimedia, games, and so on.

There are also repositories for NVIDIA, VLC, KDE:Extra packages.

Although this sounds all great, it introduces a variable of uncertainty.

Priority #1

Repositories

Like any decent package manager, zypper can prioritize repositories from 1 to 99, where the lower count is the highest priority.

Being exposed to Packman repositories will undoubtedly make you want to install all the software there is; in my opinion, you should refrain from doing so, or at the very least use the priority.

For example, the main repositories of OpenSUSE has a priority of 50, while Packman repositories have a priority of 99.

Why? One has to maintain the stability of the system.

A case that happened to me recently was a crippled package I got from Packman. I use Linphone, a software that allows me to use VoIP services and make calls. The package in Packman is broken, while the one in the OpenSUSE repos is working.

So please, consider using priorities.

Overlooking the slowness

While OpenSUSE has its flaws when it comes to its package manager. It’s a very, very strong GNU/Linux distribution. A very well polished KDE 5(Plasma 5).

I still recommend OpenSUSE to anyone know who hasn’t ever touched GNU/Linux in his/her life.

The flaws it shows

Being on a rolling release stage of OpenSUSE there’s always something that breaks. In this case, I’ve been having problems with Dolphin, it doesn’t want to save new Places. It’s a bit annoying, but not something that breaks the experience for me.

I should mention that OpenSUSE is still a VERY SOLID distribution, regardless of Dolphin file manager playing foul.

The verdict

Keeping things short. OpenSUSE Tumbleweed has proven to be a very reliable distribution. If you are KDE lover like me, please consider switching to it.

My only MAJOR complaint is the package naming and development packages. It’s FRUSTRATING hunting down each package, truly a nightmare compared to other distributions.

It’s still nice to play games and all

Final Fantasy XIV, because why not

Running Child of Light on Linux

Child of Light

Hello everyone, today I’ll be posting a guide on how to run Child of Light, a beautiful RPG game by Ubisoft. This how-to requires you to have minimum knowledge of the terminal. Do not fret though, if you do all the steps you shouldn’t worry about a thing.

My guides don’t include installation process. I will only include them when I see the need to have one. I got Child of Light on Steam, however the process should be similar to uPlay too. You can contact me through e-mail, please understand that I might be busy and it’ll take a while for me to reply.

Gameplay Video on Linux

Let’s get started! Here we will create a directory, download the binaries and extract it. By the way, for the binaries signature, click here.

:::bash
mkdir -p ~/WINE/binaries/patched/x86
cd ~/WINE/binaries/patched/x86
wget http://dgzen.pw/assets/archives/wine-1.7.36-COL.tar.xz
tar xvf wine-1.7.36-COL.tar.xz

Now let’s export WINE to the PATH.

Important Note: You need GNUTLS libraries installed for uPlay to work.

:::bash

export PATH=$PATH:/home/$USER/WINE/binaries/patched/x86/wine-1.7.36-COL/bin
export WINEPREFIX=/home/$USER/WINE/bottles/childoflight
winetricks d3dx9 wininet winhttp

We have finally set up our WINE bottle, called childoflight. Let’s launch Steam, if you don’t have it installed, take your time now and install it. After you install Steam, remember to run Steam.exe like this.

:::bash

wine /path/to/steam/folder/Steam.exe -no-dwrite

Once you have Steam installed, please download Child of Light. Once it has finished downloading. Launch the game from Steam.

You’ll see uPlay installing itself as base. Once it’s done you’ll be asked to log in.

Once you have set uPlay, close it completely and only leave Steam open. This is something you need to know.

Important Note:

uPlay doesn’t close completely. You have to look for the process and kill it. If you use applications like htop or ksysguard or an equivalent, look for the process and kill it. This step has to be done manually, even if you close Steam it will ask you to close Child of Light, this is because uPlay.exe process hangs.

Now launch the game. Play to your heart’s content!

Set up a shell script.

Please note that you have to edit it at your discretion.

:::bash
#!/bin/sh

export WINEPREFIX=/home/YOUR_USER/WINE/bottles/childoflight
export WINEDEBUG=-all
WINE=/home/YOUR_USER/WINE/binaries/patched/x86/wine-1.7.36-COL/bin/wine

$WINE "/PATH/TO/STEAM/Steam.exe" -no-dwrite

Save as ChildOfLight in ~/WINE/shortcuts. Remember to chmod +x it. Now you can easily run it as ~/WINE/shortcuts/ChildOfLight

That’s all.

Have suggestions, want to tell me something? Hit the About Me page and contact me. I might not get to you fast. I would be thankful if you use “[DGZEN]” as prefix in the start of the title, it’ll be easier to look for.

Screenshot1
Screenshot1
Screenshot1
Screenshot1

Pelican Theme: Nuja

It’s been a completely crazy day. Today I finished porting a theme I created for Movable Type called Nuja. I actually worked on it in 2013, but due to life I couldn’t keep updating it. It also amazes me how time passes. I didn’t think this was from 2013, I guess life is going faster than I thought; hopefully for the better.

Nuja is a simple theme, it was created as a tribute to Nujabes. The theme might be released over time; I’m planning to polish it before release of course. I had a bit of trouble working with Pygments, apparently Bootstrap kept overriding CSS elements when it shouldn’t. In the end I just decided to hardcore the solution as I knew I couldn’t do anything about it.

RSync + Pelican: A Short Note About Permissions

Yesterday I spent most of my time dabbling in Pelican’s configuration file. Right now how dgzen.pw is set is pretty simple. I just rsync the data to the server, and back up the project on a weekly basis to my personal account in BitBucket. There’s a catch on this, any tool using rsync will upload the data as the user you are uploading it as. This doesn’t sound as a problem at all if you are using a shared hosting! However, I use a VPS from DigitalOcean, so it sort of changes quite a bit.

I’ll be frank, before explaining my solution which is just a simple line. I haven’t configured my nginx completely, and if there’s another way to do this it’s lost on me. Feel free to contact me, my e-mail is in the About Me page!

What I did was simple, edit your Pelican generated Makefile and add this line in the rsync_upload action:

:::Makefile
rsync_upload: publish
rsync -e "ssh -p $(SSH_PORT)" -P -rvzc --delete $(OUTPUTDIR)/ $(SSH_USER)@$(SSH_HOST):$(SSH_TARGET_DIR) --cvs-exclude
ssh $(SSH_USER)@$(SSH_HOST) "chown -R www-data:www-data $(SSH_TARGET_DIR)"

That’s all you really need to solve the permission problems. There’s another way which is adding rsync to sudoers, but doing so introduces a security risk. The alteration made my way simply re-uses the variables that were previously declared. Once rsync finishes syncing the files, it will make open up ssh and chown the folder.

That’s all, and if you are using vim. Type :make rsync_upload (you must have your virtualenv enabled if you didn’t install it system wide). 🙂

[Guide] Final Fantasy XIV: A Realm Reborn on GNU/Linux


Final Fantasy XIV: A Realm Reborn is a Massive Multiplayer Online Game (MMO) by Square Enix. As you might expect the world of FFXIV is filled incredibly amazing music that revolves around old themes, and classes such as Dragoons, Summoners, White Mages, Black Mages, Ninja, Botanist, etc.

I’ll be breaking down this guide into several sections.

Sections

Overview

The WINE I’m providing has CSMT patches integrated. I also merged the patches that were made a year ago to solve the user interface flickering issue. Originally this guide was going to include PlayOnLinux instructions, but it became apparent that creating a shortcut in POL is an uphill battle, for some reason it didn’t want to create a simple shortcut.

Winetricks is required to be installed before using this guide.

Getting it running

First, I’m going to assume that you have downloaded the game either through Virtual Box or having a Windows partition. This guide will not cover the installation phase of the game. However, you are most welcome to create a new thread on GamersOnLinux forums.

Download the binaries here, you can also download the source here.

After downloading the binaries:

Create the following folder

    $ mkdir -p ~/WINE/binaries/x86
    $ cd ~/WINE/binaries/x86
    $ wget http://thehumble.ninja/pelican_backup/assets/archives/wine-1.7.24-FFXIV-CSMT.tar.xz

Move the downloaded binaries to that folder, once moved type in the terminal

    $  tar xfv wine-1.7.24-FFXIV-CSMT.tar.xz

Temporarily we will append WINE to the PATH environment variable.

Type this to get the current directory you are in.

    $ cd wine-1.7.24-FFXIV-CSMT/bin; pwd

Copy/Paste the result here, example:

    $ export PATH=$PATH:/home/$USER/WINE/binaries/x86/wine-1.7.24-FFXIV-CSMT/bin

Now, it’s time to install all the software required to run Final Fantasy XIV.

    $ export WINEPREFIX=/home/$USER/WINE/bottles/FFXIV; export WINEARCH=win32
    $ winetricks d3dx9 devenum ie8 quartz wininet winhttp xact_jun2010 wmp10

It’s important that the applications be installed, do not skip any of them.

Let’s launch it!

Once it’s done, go to the installation folder of Final Fantasy XIV. For example, my installation folder is this one (“/media/david/Usagi/FINAL FANTASY XIV - A Realm Reborn/“). You will need to enter the boot folder, thus making it “/media/david/Usagi/FINAL FANTASY XIV - A Realm Reborn/boot

Launch the game!

    $ cd /PATH/TO/YOUR/FFXIV INSTALLATION/boot/
    $ wine ffxiboot.exe

If it doesn’t let you click on the EULA, don’t worry.

Edit the EULA file:

    nano ~/my games/FINAL FANTASY XIV - A Realm Reborn/FFXIV_BOOT.cfg

Turn

EulaAgreement   0

into

EulaAgreement   1

Now, let’s just forget about the game for a moment. If you are following the instruction to install FFXIV without PlayOnLinux, do these steps:

    $ wine regedit

Follow the steps: We are going to create some keys here.
In a nutshell, we just create the folder (key) in HKCU/Software

The key will be named “Direct3D”

The string keys within Direct3D will be the following

CSMT = enabled
StrictDrawOrdering = disabled

Here are some images so you get the idea!


Once everything is set, run the game again.

:::bash
$ wine ffxivboot.exe

Log in, and play to your hearts content!

Let me simplify this for you, my dear reader! Let’s create a shell script

:::bash
$ mkdir ~/WINE/shortcuts

Using your favorite editor, create a file called FFXIV

    #!/bin/sh 

    export WINEPREFIX=/home/david/WINE/bottles/FFXIV 
    #COMMENT IF THE GAME IS FAILING TO LAUNCH 
    export WINEDEBUG=-all 

    #UNCOMMENT THESE LINES IF YOU USE NVIDIA DRIVERS 
    #export LD_PRELOAD="libpthread.so.0 libGL.so.1" 
    #export __GL_THREADED_OPTIMISATIONS=1 

    WINE=/home/david/WINE/binaries/x86/wine-1.7.24-FFXIV-CSMT/bin/wine 

    $WINE "/media/david/Usagi/FINAL FANTASY XIV - A Realm Reborn/boot/ffxivboot.exe"

Important note:

After the game launches, be sure to kill ffxivlauncher.exe in the terminal. The process does not close completely and it hogs the CPU.

Simply type

:::bash
$ killall ffxivlauncher.exe