|
|
|
Use this tool to learn about websites, specifically the one you just entered. If you find some aspect of it inappropriate it is not our fault. If you are the owner of this website: yes we are a real search engine, we do have a real web crawler called FyberSpider and you can block it if you feel the urge.
We are in the process of updating this tool. Until we are done just use our search results to check the inclusion status of your site.
Kernel Planet
This is just a sample of the content found on this website. Please visit the website to read the entire page. "Kernel Planet July 06, 2009 Pete Zaitcev : Jon Masters was right Or at least that was what I thought when, after years of service, Rawhide finally cooked itself on my laptop enough to become unbootable due to a crash of glibc. After a short period of despair it turned out that an invocation of cp on ld-2.10.1.so and libc-2.10.1.so was enough to recover (trusting prelink -ua seems suicidal to me, honestly). But all things said, it's not question of if, it's when your Rawhide will brick (or worse, corrupt something). But even so, there's no choice for me but to persist with the latest and greatest, just because it's the only place where the fixes happen (ouside of expensive commercially supported branches). Sorry, Jon. This recurrent thought is prompted by an article at LWN . July 06, 2009 10:21 PM Matthew Garrett : What does the desktop want from the kernel? I'll be running a session on Wednesday at GCDS to find out what desktop developers would like to see from the kernel. There's a lot of interest in making things easier for file indexers, but if anyone has other problems that could be made easier with some level of kernel support then please turn up. No precise time or location yet, but probably around 3PM at the university. More details forthcoming. July 06, 2009 06:07 PM Matthew Garrett : One of the strengths of the open source community is that so much happens in the open. It's generally easy to find out what's happening in a project and directly interact with the developers. Code is out in the public. People frown upon closed discussion and implementation. But there's also a cost. Personality conflicts get hidden in the corporate world. We air them in public. And while in some ways that's arguably an advantage, it also results in things like this . Now, to be fair, I've never been an especially big fan of Sam's work. His journalism generally leans towards la" .... read entire page
|
|
|