Pages

Super

I have been advised in good authority, that a Dutch tourist is more likely to to be heard saying "Super" than any of their other European brethren. I have insufficient empirical evidence either for or against the statement,

I have also been advised, again by people who know better, never to use

sudo ...

where

su -c ...

can be used instead. This "super" advice, after having been burnt several times over in the past few days, I now hold as undeniable truth.

I remember, I remember
The house where I was born
the super user (mis)privilege
haunted me till the morn!

Word

TIL that "today" is probably not in the list of the 500 most used words, but "never" is. That we use "study" more than "eat" or "talk" or even "sleep". We "plan" more than we "develop", and are at "long" more often than on "short". 

So, "We never plan to study or talk long." is a very reasonable sentence, but "Today?Absolutely unlikely, almost incredible." isn't.
I would say it was another of those long rants, except in that it isn't.

Why today? Because xkcd is something that makes you stranger, if it doesn't kill you first!

Source:
http://www.world-english.org/english500.htm
https://en.wikipedia.org/wiki/Most_common_words_in_English
http://www.insightin.com/esl/

A thousand words...

If "a picture is worth a thousand words", we can actually determine it's resolution.

We know the average length of an English word lies in the vicinity of 5.1 letters.
Assuming 8-bit ASCII uncompressed text, and using RGB bitmap with 24bit colour for the image,

1000 words ~ 5100 letters + 999 spaces + n punctuation marks.

Average length of an English sentence approaches 14.3 words. Each sentence needs a concluding punctuation in form of a period. Non-concluding punctuation is observed slightly more regularly than in every other sentence. For the sake of simplicity, let's consider it converges at 1.6 punctuation marks per sentence.

So, number of sentences =  1000 / 14.3  =  69.93  ~  70
Therefore,  n  ~  70  *  1.6  =  112

So, 1000 words ~ (5100 + 999 + 112) = 6211 characters = 49688 bits.

Getting to the image side of affairs,

Each pixel in a RGB bitmap with 24-bit colour (I really hope you don't need more than 16 million colours for that picture we are talking about) is naturally of 24 bits.

So we can fit in a mere 49688/24 = 2070 pixels into such an image. That would be smaller than even an iPhone icon, which requires 3249 of those dots (Android icon sizes vary).

Given that text is usually in Unicode these days (UTF-32 needs 4B per character), and jpeg/tiff/png, etc compresses images in a major manner(15:1 compression is passe), more pixels could be fitted into the 1000 words in question. About 3-5 times the pixels, to be precise. Text compression using Huffman encoding (~2.9:1 for a 27 letter alphabet), quite commonplace, however results in even fewer pixels.

All these and other intricate considerations may possibly average each other out in the greater scheme of things.

This, however, does not change the fundamental truth that if your average photo is worth a thousand average words, you need a new photo.

Or to paraphrase what I read somewhere on twitter, A picture may be worth a thousand words, but it takes up ten thousand times the space.

Anybody interested in helping me write an app/program that calculates how many words your picture is worth? Mail me.

P.S. I have corroborated the word statistics from several sources, but had no way of testing their authenticity/data. So I'm not linking to any of them.

Please copy this as your status if you...

Dear friends,
So you didn't have a laptop in your childhood. That was not because of how your parents raised you, but because it was not at all useful for you to have that prohibitively costly toy then, which can bring to a kid today the world's storehouse of knowledge, and a lot more. 

The iPod wasn't invented, Blackberry is not meant for children to play with, some of you probably did have a Nintendo, and just didn't know it, and the Xboxes and PS3s were yet to be brought out in their current form. 
 
And really, Wi-fi? What would you be doing with a Wifi again, if there was no internet backbone to connect it to?

You have possibly lost out on a lot more than you purportedly gained because you had a Contra instead of a Commodore, an Atari, an Apple II, or the likes back then.

I had a beautiful childhood too, not because I didn't have a lappie, a PS3 or whatever, but because of all the great things I did have, among them great family and friends.

It is good to appreciate what you have, but that does not entail begrudging others their benefits or differences.

Sharing lame statuses in an attempt to appear what ever you are trying to appear as, does not change the lameness of the initial premise.




GROW UP!

Yours sincerely,

Koushik Kumar Nundy.

P.S. This is in direct response to a facebook status meme about how beautiful some of my peers' childhoods were, and how cool they are courtesy their non-involvement in technical and democratic exercises in their tiny tot times. However it can be generalised to cover any such "Please copy this as your status if you.." incidents, because,

  1. FB asks for what's on YOUR mind, G+ asks for what's NEW,... please, this is neither particularly in your mind, nor is it too new!
  2. Twitter asks what's happening, if you post such status forwards, your childishness, if not your childhood is still happening.
  3. If copying statuses would cure cancer and rid us of terrorism, corruption and a thousand other maladies, oncologists, radiologists, soldiers, political leaders would have all become "Social Media Experts" instead.
  4. People who are on such platforms to keep in touch with old friends or develop bonds with new ones, are truly, madly, deeply getting irritated.
  5. When people start getting tired of such stuff, they will write even more tiring blogposts as this.
  6. Some people will get an irrepressible urge to post this as their status "Please copy this as your status if you don't like "Please copy this as your status ..." statuses."

openSUSE 11.4 - A new life

As many of you know, and the rest, well they'll know by the end of this sentence, openSUSE 11.4 released yesterday, the 10th of March, 2011. It'll be the seventh straight release I use, and the 4th release since I became associated with the Project.

To download visit : http://software.opensuse.org/

Unfortunately, my old machine is still running on 11.3, and the all new Vostro I got today has, wait for it, Windows Vista, both of which I plan to amend tomorrow. Sadly, that was not possible today because seeding the ISO was, I felt, more important than selfishly enjoying Geeko glory. So, no donut, oh sorry, screenshot for you.

The journey to openSUSE 11.4 has been anything but smooth. [1] says well why.
But I'd like to add to that.

The initial rumours about Novell, openSUSE's primary being up for sale did not go down well with the community, as we have seen the last major sale of a Free Software leaning company, Stanford University Networks, as very unfavourable to the FOSS community, with important jobs axed, opensolaris dead, and Openoffice.org left to potentially rot, with Libreoffice being a bold step by the people who care, to infuse life into the best office suite in the world.

The sale to Attachmate that eventually followed, did not help cool matters, due to the following,
1. No one had ever heard of it.
2. The sale of those patents to a shady conglomerate!

However, Attachmate seems to be serious enough about the feasibility of SUSE to run it as a separate division. And THIS is what they have to say about openSUSE. May be lip service, or may not be.

Now to the many firsts. openSUSE 11.4 is the first major distribution release to have stable LibreOffice, has Firefox 4, GNOME 3 preview(optional), KDE 4.6 and loads of other new stuff like Scribus 1.4, KOffice 2.3.1, etc. Also new is the support for Tumbleweed, a rolling release.
A more detailed Product Highlights is available.

But these are not the only important changes. Many new faces in every team, marketing collaboration days, a great openSUSE Conference, attempts at clearly defined strategies and trademark guidelines, all this has worked to largely improve the cohesive co-operation that is the openSUSE project.

We have had our share of growing pains, with membership issues and policy being cause for heated debate. Stability has always been the strength of the openSUSE distribution. The openSUSE community has done well to learn that it has to show the same stability in every step, not just in the lines of code. We have come out of it, not just better, but cleverer. We are a community that has a worldwide spread, contributors and users alike. In our do-o-cracy, we are not judged by our race, sex, or politics, but by our actions. A great example would be our team of 125 Ambassadors, who come from a whooping 47 countries. Another new initiative to overcome the gender divide otherwise stark in FOSS is the Women of openSUSE Project.

We have been lucky to have partners like OMG!SUSE! at our side.

With a clearer sense of identity and purpose, we hope to march from strength to strength, so that we can continue to bring to you, openSUSE, all of it!
(Now, now I can't promise what the next release number will be, so hang on for the ride!)

Join us in making the world Greener (most puns intended)! http://www.opensuse.org

As we heard in Batman Begins, "It's not who you are underneath - it's what you do that defines you."

My views on openSUSE LTS

There has been a lot of discussion recently on the viability of a Long Term Support release for openSUSE. Some have proposed a separate LTS version, some a rolling release called Tumbleweed. Some have shown support for both, suggesting they coexist as separate sub-projects. Yet others have suggested we create an openSLES, a "free as in free beer"(to think that this phrase even exists) version for SUSE Enterprise, much like what the CentOS people do with RedHat Enterprise Linux.

This discussion has spiralled into multiple threads on the opensuse-project list. The threads have been linked to at the end of this post.

My reply in regards to the discussion is summed up below:-

1. I have a feeling the two being analogised to CentOS is a bit unfair. openSUSE's relation with SLE has always been more the Fedora to RHEL kind. We, as a project, form a base, not a copy of SUSE's enterprise offerings, if typically more conservatively than competition.

2. openSUSE has the direct primary sponsorship of Novell. CentOS has no official affiliation with RH. An openSLES may antagonise Novell/SUSE/Attachmate's friendly approach.

3. Offering of an LTS version alternately with a couple of normal versions has not been discussed. I wonder why. Ubuntu does that quite appreciably, (though I have never personally encountered an Ubuntu-powered server).
From Wikipedia, "To date every fourth release, in the second quarter of even-numbered years, has been designated as a Long Term Support (LTS) release, indicating that it has updates for three years for desktop use and five years for server"

To say what that means, let's say we have 12.0 as LTS(5 release cycle support), then 12.1, 12.2 and 12.3 with normal 2.2 cycle support. Then again 13.0 as LTS, and so on. This will cause an LTS version to be perennially active, while having a "cutting edge" version for systems here stability is not primary.
This would help a only one extra already present older version needs to be maintained, reducing stress on the developers.

4. The point mooted in (3) can also help on standardising a versioning scheme, the need for which was discussed but never finalised some time earlier, probably on the marketing and project lists.

5. Nelson Marques has a point. Too many offerings would cause confusion. Normal openSUSE vs openSUSE LTS vs openSUSE Tumbleweed vs openSLES has already confused me to an extent.

6. Someone suggested binary compatibility with SLES would make people recommend SLES for paid-for-support Linux. While I appreciate Novell's roles in what openSUSE is today, I personally feel SLES sales figures are not supposed to be the concern of the openSUSE project.
Furthermore, even openSUSE can be paid-for-support Linux, considering people pay for 90 day support or something like that when they buy the box.




Threads
[1] Announcing openSUSE Tumbleweed project Nov '10 Dec'10
[2] openSUSE LTS Nov '10 Dec'10
[3] Packman for Tumbleweed