Gregarius » linux kernel monkey log

Feeds

15081 items (9404 unread) in 27 feeds

• mypapit gnu/linux blog (215 unread)
• Catatan merepek ku... (25 unread)
• Affiliate Program Tip Blog (792 unread)
• GMS Blog
• Robert Love's Log (149 unread)

ComputerTechnology (4265 unread)

• Linux and Open Source Blog (473 unread)
• Ubuntu Blog (14 unread)
• linux kernel monkey log (52 unread)
• PHP Classes: Latest entries (1727 unread)
• PHP Freaks Tutorials (81 unread)
• Tien Soon's Tech Blog (25 unread)
• When {Puffy} Meets ^RedDevil^ (262 unread)
• anti-keseronokan (25 unread)
• TaoSecurity (678 unread)
• Ari Jaaksi's Blog (46 unread)
• Marc Abramowitz (110 unread)
• IconBuffet
• Your LiNa Job Matches (714 unread)
• Patpat's Scrap Notes (58 unread)

RantsandRamblings (3958 unread)

• #fakap community speaks (86 unread)
• 5xmom ~ Humour, Life, Lies, Sex (1565 unread)
• Infoplease - This Day in History (1470 unread)
• Dilbert (377 unread)
• Tip Satu Minit: Irfan Khairi.com (384 unread)
• Tips Temuduga (8 unread)
• Road 2 Millionaire (43 unread)
• Download Ebook PERCUMA (25 unread)

linux kernel monkey log (3 unread)

• 

  Android and the Linux kernel community

  Posted: February 3rd, 2010, 8:18am MYT

  As the Android kernel code is now gone from the Linux kernel, as of the 2.6.33 kernel release, I'm starting to get a lot of questions about what happened, and what to do next with regards to Android. So here's my opinion on the whole matter...

  See more ...

• 

  Stable kernel tree status, January 18, 2010

  Posted: January 19th, 2010, 3:11am MYT

  Here's the state of the -stable kernel trees, as of January 18, 2010.

  2.6.27-stable

  The 2.6.27-stable kernel tree is still living on, as a "long-term" stable release. But, I do have to warn users of this tree, the older it gets, the less viable it becomes. Not all bugfixes are being backported to this kernel version due to massive code changes in the over 2 years since this kernel has been released. I am doing my best to backport fixes that I become aware of, and I encourage anyone who does fix any types of bugs in the main kernel tree to let me know if the change should be applied to this older kernel version.

  I'll probably keep maintaining it for at least 6-8 more months, but after that, I can not guarantee it's viability. Note, one other developer has volunteered to pick up the tree after I am finished with it, but I can not speak for him at this time.

  2.6.31-stable

  Today the last 2.6.31-stable kernel was released, all users of this kernel series are strongly encouraged to switch to the 2.6.32 kernel series, as there will not be any more updates for this branch in the future.

  2.6.32-stable

  I'd like to announce that the 2.6.32-stable tree is also going to be maintained as a "long-term" stable release, living for 2-3 years, like the 2.6.27 kernel is. This is because a number (i.e. more than 2) Linux distributions are basing their "enterprise" releases on this kernel version, and it will make their lives easier if I keep it alive.

  Note, the viability of me keeping this tree alive for such a length of time relies on the developers working for those distros to keep me informed of patches that need to be backported and applied to it. Without their help, I will have no problem in stopping the maintenance of the tree.

  Submitting patches for stable trees

  Again, the easiest way to get your patch into a -stable tree is to merely add the line:

  Cc: stable <stable@kernel.org>
  

  to the Signed-off-by: area of your patch. When the patch goes into Linus's tree, it will be automatically sent to the stable address, and I will know to apply it to the trees. If I have any problem applying it at that time, I will email the author and reviewers of the patch about it.

  If you forgot to add this line to the patch, or you have found a patch written by someone else that you wish to have applied to the stable trees, email the git commit id of the patch as it shows up in Linus's tree to the stable@kernel.org email address. Any stable correspondence sent to my personal accounts has the chance of being lost in the shuffle, so please try to not do that.

  If a patch needs to be backported to one of the stable trees because it does not apply directly, please send the backported patch, along with the git commit id of the original patch, to the stable@kernel.org address, with a description of which kernel tree it should be applied to.

  If anyone has any other questions about stable releases, please let me know.

• 

  Twitter experiment over

  Posted: January 6th, 2010, 8:52am MYT

  Way back in 2008 I started to use twitter as a dump of my command line. Well, 23 thousand tweets later, most of them being something as boring as q ref, I've stopped the experiment. Turns out just seeing one side of the conversation (what I type) and not the output, is a pretty boring thing.

  That being said, 155 people did find it amusing enough to follow, and for that, I am totally amazed. True, 150 of them are probably bots, I sure hope their scripts enjoyed the show. Twitter also started to rate limit me after the first few months, in a silent manner. The server would say it accepted the message, yet it would never show up anywhere.

  The good thing out of this, was the tool, bti, which lots of people seem to be using as it provides an easy way to pipe output to twitter-like services. It has also grown way beyond my initial expectations, now providing the ability to read messages, and lots of other things (readline? Yeah, readline, the GPL trojen horse, is now supported, I need to work on making it so that readline doesn't force a GPLv3 change to the codebase.)

  So, it's back to normal for twitter and identi.ca for me now, just kernel release announcements and complaints about companies not working well with the kernel community.