If you like cscope, I think you'll really like kscope (http://kscope.sourceforge.net/) - best for C code but it can be useful for C++ too. The LLVM folks seem to think that a new collection of tools are needed to help with a variety of stages of program analysis....
If the Coverity (google: coverity ethereal) results are any indication things have gotten somewhat better, I'm not sure if any of the BSDs have changed their minds.
XenoLinux - a virtual machine layer to support linux and other free OSes at almost native speeds. Alot faster than UML!
CKRM - not new but I didn't know about it. From their sf site: The Class-based Kernel Resource Management (CKRM) project seeks to develop Linux kernel mechanisms providing differentiated service to resources such as CPU time, memory pages, I/O and incoming network bandwith based on user defined groups of tasks called classes
TIPC - Transparent Inter Process Communication protocol is specially designed for intra cluster communication but definately not for the internet.
I talked to Karim Yaghmour about getting LTT into the kernel. He said that the kernel folks didn't think there was enough demand from the community and that if you want it in the kernel, post to lkml explaining why. There was a nice session on relayfs but again, the claim was that netlink mostly does the job. Well according to the developers not really but rather than introduce relayfs, folks were encouraged to merge features into netlink.
Re:PRL publication information -- LANL archive
on
Stop, Light.
·
· Score: 1
Here is the Los Alamos preprint entry.
http://xxx.lanl.gov/format/quant-ph/0012138
Great! The Linux kernel is on schedule to change at 2.6.42.
I thought they were going to call it the RIMshot!
The RIMShot? !!
Clearly Google is trying to use this issue to overcome the next few weeks of media buzz about the Apple Tablet release! ;-)
The article is from 2007 but I guess it's news to most nerds.
Arxiv link: http://arxiv.org/abs/quant-ph/0701237
Now we just need to figure out if this has any impact on Ultimate Physical Limits of Computation as linked to in LWN: http://lwn.net/Articles/286233/
If you like cscope, I think you'll really like kscope (http://kscope.sourceforge.net/) - best for C code but it can be useful for C++ too. The LLVM folks seem to think that a new collection of tools are needed to help with a variety of stages of program analysis....
2^31 -1 seems like a more than generous limit for real life too!
If the Coverity (google: coverity ethereal) results are any indication things have gotten somewhat better, I'm not sure if any of the BSDs have changed their minds.
I think the OP missed some of the best talks:
XenoLinux - a virtual machine layer to support linux and other free OSes at almost native speeds.
Alot faster than UML!
CKRM - not new but I didn't know about it. From their sf site:
The Class-based Kernel Resource Management (CKRM) project seeks to develop Linux kernel mechanisms providing differentiated service to resources such as CPU time, memory pages, I/O and incoming network bandwith based on user defined groups of tasks called classes
TIPC - Transparent Inter Process Communication protocol is specially designed for intra cluster communication but definately not for the internet.
I talked to Karim Yaghmour about getting LTT into the kernel. He said that the kernel folks didn't think there was enough demand from the community and that if you want it in the kernel, post to lkml explaining why. There was a nice session on relayfs but again, the claim was that netlink mostly does the job. Well according to the developers not really but rather than introduce relayfs, folks were encouraged to merge features into netlink.
Here is the Los Alamos preprint entry.
http://xxx.lanl.gov/format/quant-ph/0012138