Point Element

So I wanted to download only images from this one website for archival usage. After looking at all ready available page, I couldn't find anything suiting for my purpose. So I decided to throw in a little shell-script. It went on as follows: The pages are incremental in index. So I can use a while loop to fetch all pages one by one. Done. Need to fetch the page. Wget is fine. Done. Then I need to look for the image URL in retrieved HTML. Hmm. Bit of grep with cut does that. Done. Next get the actual image. Again prepare the image URL and wget. Done. Error handling? Gaah. Nothing since this is not that trivial. After testing for few pages it was golden. So I put it up with counter loop of hundred images at one time. That's because this script is kind of slow since I don't know nor care to put in multithreading in shellscript. Gaah. Plus as I later found out having 100's counter is good since wget hung out when the net went down for a moment, and I had to restart the scrip

Yesterday we went out for an outing on our bike. It was about 90kms round trip. We left in morning and planned to be back by noon. Going was nice, with normal weather. After reaching the place and sightseeing for about couple of hours we left by 11:30AM. We could feel the heat. It was not scorching yet, but we felt like we should have left an hour early, since it was easily an hour and half's ride back with all the traffic. So we were only 10kms away when the scooter lost power. We tried electric start first, but it won't start. Then we tried kick start, and still nothing. So we searched the net and found a mechanic and had him sent someone over. Then after 45 minutes couple of young mechanics reached us. After fiddling with the scooter they managed to kick start it. Initial prognosis was dead air filter. So we rode to their garage, and got it replaced in about half-an-hour. In Hero Duet the filter comes as a block of striped foam. In bikes it's often a round hose-lik

Been reading about the troubles with LG. To be frank, LG actually has crappy phones. Their mid range is non-existent and their high end is in search of identity. Add in these QA issues. I mean come on.... I have seen phones getting literally cooked at about 45-50 degrees when gaming and they did not fail - e.g. my Nubia Z9 mini and few more older phones. If LG cannot make a phone motherboard, they need to be put out of phone making business. Latest news is they have a Class Action lawsuit in US. Hmmm let everybody know LG hardware is crap. For comparisons we have not heard such things from almost all other manufacturers. And please leave aside chinese knock-offs. They can't even align their plastic edges. Haha. Cheers.

It was a surprise announcement. But then again maybe Mark Shuttleworth saw the writing on the wall, and thought about stopping the bleeding. And so the culling began... I was kind of shocked when I read Jono Bacon's post. Why? Because I'm not much online on G+. And Jono's was the latest post on Planet Ubuntu. Anyway I did try Unity 8, and it did look slick. Funny think is probably KDE has similar graphics and animations for ages, and they never appealed to me. Frankly I just hate the way KDE looks. The odd highlights, the cramped fonts, the weird effects I immediately disable... gaah!!! What I saw in Unity 8 though, I liked it. Anyway again Canonical has few resources and they are better spent on improving Canonical's longevity. Because It's Canonical that took Linux to the masses and not Redhat or SuSe or anybody else. For that..... Salute!!!

Recently I noticed that my Ubuntu installation has become slow to boot. It has seen couple of dist upgrades and a lot of application install/remove's. So I decided to dig in and see if there's anything I can do about it. First thing is how to measure current boot time. After a quick google search I ended up with following commands. systemd-analyze systemd-analyze blame systemd-analyze critical-path systemd-analyze plot > plot.svg systemd-analyze prints something like: Startup finished in 9.002s (kernel) + 22.322s (userspace) = 31.325s Which means system is taking 31.325 Secs to boot, out of which kernel part is 9Sec and remaining is user part. systemd-analyze blame prints list of applications/ services according to time taken to load. critical-path option shows a critical path graph and highlights applications/services which are taking more than average time. plot option plots a nice graph of the booting process. There are other ways too. E.g. if you want to see more in what

Well, I have been using Ubuntu 16.04, then 16.10 and now about to upgrade to 17.04 whenever it gets released. Problem is with Unity is we get updated Nautilus. And over the time I have seen the changes that have made me say WTF!!! More on this later. But this caused me to switch to Mate. I didn't want to replace my existing installation because there are about a dozen apps and half-dozen drivers that I have installed for office work. And I don't want to go through re-configuring everything again. So I just installed Mate desktop and been using it. Frankly, Mate is killer. It's lightweight and so fast. Very responsive. I didn't have much problems with Unity's search the app metaphor since I pin half a dozen apps which I use regularly, and that's it. But Unity has been pretty sluggish and I used it only because the indicators and stuff keeps running without breaking over updates.(Have used XFCE and LXDE, both exhibited this issue.) Anyway, so Mate it is for me. Le