Showing posts from April, 2014

Going outside for a change

I have mostly been spending my free time on the computer lately, either programming or reading Google+. But I've been getting a little bored of doing the same old thing all the time, so I recently started walking around outside at LTU.

My cousin Joe showed me where the real nature path is (not the short fake one I mistakenly showed a friend once), and I've been hooked on walking through there, aiming for about once or twice a day. Since I was a kid I was always the type to like to explore, so I had a great time traversing the entire thing multiple times and figuring out where all the paths lead.

Along the way, I also tried out the new Google Camera app for Android and took various pictures with it, including using the new "lens blur" feature. I found that this works really well for creating pictures with a feeling of depth to them, such as when something is jutting out at you. A number of these make for decent wallpapers, I found. I'll likely post some under my a…

grive-daemon update: autostart added

grive-daemon is now capable of starting automatically after you login. This new feature works by having sudo make install add a file called into your /etc/profile.d/ directory. Each time you log in, the script will fork, wait five seconds, then start grive-daemon.

The effect is that once you are logged in, and hopefully by the time Unity is finished loading, you will see a notification indicating grive-daemon is doing its usual thing of doing a sync to ensure everything is up-to-date.

This means you no longer have to call grive-daemon manually after you log in. Automation FTW!

grive-daemon update: new building method and bugfix

I was working some more on my grive-daemon hobby project today, and I accomplished a couple things.

The first thing was that I added a proper makefile to the project. This means that instead of calling g++ directly to build grive-daemon after you clone it, you just type in make. Moreover, you can now install and uninstall grive-daemon on your system after building it by using the sudo make install and sudo make uninstall commands, respectively. After installation, you can just type grive-daemon into your terminal or Alt+F2 dialog to start the daemon - no more needing to call the executable directly! Pretty cool stuff.

The second thing was that I found a bug where changes made to the lowest directories in your ~/Google Drive folder were not being noticed by grive-daemon, and hence not synced until something else caught its eye. This was an issue with the initial recursive setup for directory watching, and it was quickly and easily fixed.

Getting recursive

Not too long ago I wrote my first post about my latest hobby project, grive-daemon. I guess it's time for an update.

Just today, I merged in a branch I was working on which converts grive-daemon from C to C++ (you should now use g++ to build it) and implements recursive directory watching with inotify. This means that you should now be able to make changes anywhere within your ~/Google Drive folder or its subfolders, and the daemon will be able to see and sync those changes. This will no doubt make it many times more useful for people who have a lot of folders on Google Drive (like me).

Nothing else has been fixed or added, however. If there is something you might like to see, then go ahead and open an issue on GitHub. I can't promise I'll actually do anything about it, but the feedback would be appreciated.

grive-daemon is born

Background With the recent announcement of Ubuntu One's death, it seems a lot of people are in a scramble to find a file sync alternative. I'm one of those people who really likes using Google Drive, but unfortunately there is still no official Linux client. For people using Linux, there are a couple of different sync clients they can use:
grive: This is an open-source sync client which you must run manually through a terminal. Does the job, but is not user-friendly.Insync: This is a closed-source, paid sync client. If you don't want to spend money and/or prefer libre alternatives, this is not an option. As some of you may know, I'm the type who will go to extreme lengths to fix a problem if it has been bugging me for a long time. In this case, the problem is that there is currently no good software for syncing Google Drive to a local folder on your Linux computer like the official client for Windows does.

The Creation of grive-daemon I knew nothing about daemons. I k…

Make sure you're using LTU Network

This morning, I was a little confused. I booted up my Fujitsu LifeBook T900 into Ubuntu 14.04 LTS, and went to check Blackboard at LTU. But the page was taking forever to load, and when it finally did, it redirected to one of their pages concerning Bannerweb instead.

I went and talked to LTU's help desk, and it turns out that the problem was that my laptop had connected to LTU Guest instead of LTU Network for its wireless connection. I switched connections, and everything was working fine.

The rationale was that LTU Guest is unsecured while LTU Network is secured, so Blackboard is only supposed to be accessible through the latter connection. LTU students are only supposed to be able to access their email through the latter connection, as well.

So, if you're a Linux at Lawrence Technological University user like me, always ensure you are connected to LTU Network before trying to get anything done through Blackboard or email. I have previously written a blog post on how to set u…

Getting Ubuntu 14.04 LTS Connected to the LTU Network

A while back, I wrote one of my first blog posts concerning how to get Ubuntu 12.04 LTS connected to Lawrence Technological University's "LTU Network" Wi-Fi connection. I figured that now that I am running the second beta of Ubuntu 14.04 LTS (the next long term support release) on my school-issued Fujitsu LifeBook T900 laptop, I would make a new post refreshing the instructions a bit.

Not much has changed since the last LTS release. If you want to connect, go the network indicator in the upper-right hand corner of the screen (I'm assuming you're using Unity). Click on it to open a menu displaying various connections, and click on the one which says "LTU Network".

A window like the one below should open up. Enter all the same security settings I input (your username and password are the same as your LTU username and password):

Click the Connect button in the lower-right once you're finished. A dialog box may pop up warning you about not choosing a CA…