Although I'm not volunteering to knock up a new slashdot based on discourse
Also, the exact user id is mostly for bragging rights anyway, but it does give an indication as to whether the user is a long time user of slashdot or not. Although other indications such as the karma of the user might be more useful in most situations...
* The current version has very clear boundaries between stories in the form of the green bar. (Same for (expanded) comments.) With the new design it is simply harder to find these boundaries.
* Why all the wasted space in this new design? If I want a narrow column I'll just resize my web browser. The old layout was good because it allowed me to quickly scan through a lot of stories to select the ones that interested me. Same with comments. With the new design I need to scroll quite a bit more before having seen all the content.
* Speaking of comments, what is going on with the comment system? I hope the limited comment functionality (for example, lack of folding, etc) is just due to the fact that this is a beta.
If you are going to try this out, note that you'll need to do this immediately, before the memory has been overwritten by another process. (And you obviously need to be root to be able to access
- * Specially crafted file on a CD inserted into the CD player
- * Exploit weakness in the car bluetooth interface
- * Exploit weakness in built in GSM modem
For the details, see http://www.autosec.org/pubs/cars-usenixsec2011.pdf. (Pretty scary reading. In this case they are also able to disable the brakes and they are also able to engage the brakes on only one of the front wheels for all sorts of "fun"...)
This seems similar to how a malformed RDS packet sent via FM radio can disable the brakes on a certain car: http://www.autosec.org/pubs/cars-usenixsec2011.pdf (among other things).
Exactly how similar these attacks are are difficult to ascertain as the presentation leaves a lot to be guessed, although the net-security report on his talk gives some more details.
At the time I read the lwn article and the associated papers I thought to myself that the car industry should learn security and stability from the aerospace industry. Unfortunately it now turns out that they seem to have done so
However, there are ways around this. IIRC chrome decodes images inside a seccomp jail, causing an exploit in the image decoder to be very hard to use for anything except showing a a naughty image and eating CPU time. (I don't know if the enlightenment guys are doing this or not, but I hope they are considering it at least.)
"When set to 1, the ALTINST bit in the FCR enables ex ecution of an alternate (not x86) instruction set. While setting this FCR bit is a privileged operation, ex ecuting the alternate instructions can be done from any protection level.
This alternate instruction set includes an extended set of integer, MMX, floating-point, and 3DNow! in- structions along with additional registers and so me more powerful instruction forms over the x86 instruction architecture. For example, in the alternat e instruction set, privileged functions can be used from any protection level, memory descriptor checki ng can be bypassed, and many x86 exceptions such as alignment check can be bypassed.
This alternate instruction set is intended for testing, debug, and special application usage. Accordingly, it is not documented for general usage. If you have a ju stified need for access to these instructions, contact your VIA representative. "
I have tried to find some details about this alternate instruction set but haven't been able to find anything unfortunately. (And I'm not so interested in this any longer as my remaining Via C3 machine is now only used for backups and does not require very high performance...) Anyway, I'm guessing that it didn't become very popular due to the fact that they kept the details secret.
If you are running commands that outputs a lot of text in the terminal the search capability of emacs is really useful as well.
Another use case is the integration between macros, text buffers, and terminals. Consider a use case where you are editing an HTML file and want to ensure that all images referred to in IMG tags are available at a remote location. It is then easy to create a macro in emacs that finds all IMG tags, extract the file name and copy the file name to a suitable scp command that you can paste into the terminal window.
However, I must admit that I still have a few xterms open, but I find myself gravitating towards running shell commands in a shell buffer in emacs, especially when programming. Also, there are of course other ways to solve all of these issues (scripting, file redirection, etc), but for myself I usually find myself preferring to use emacs in most of these cases.
Also, for those of you who are interested in what the phase noise looks like there is a nice article about this over at leapsecond.net: http://www.leapsecond.com/pages/mains/ where the phase noise of the power grid is compared to a GPS clock.
I have been wondering about this myself. This situation is not really that well explored and I'd really like to see a license for HDL-like code with some high quality lawyering behind it.
One problem is that hardware such as ASICs are typically not protected by copyright. Instead it is protected by maskworks laws which are similar to, but not as strong as copyright. The intention is that ASIC-like hardware should be protected by patents. (Although I guess an exception would be made for ROMs where the layout itself would be protected by maskworks whereas the actual metal configuration of the ROM array would be protected by copyright.)
For FPGAs I have heard people claim that their lawyers consider the bitstream to fall under copyright law -> e.g., the GPL would be fully enforcable. Another interesting case in point is that SUN choose the GPLv3 as the license when releasing the source code for the Niagara processor. Personally I've used an MIT-style license when releasing open source hardware because I was more interested in getting the (fairly small) designs out there than to try to enforce the GPL license for something it wasn't really designed to protect.
Also note that the GNU FAQ has the following to say about hardware:
Any material that can be copyrighted can be licensed under the GPL. GPLv3 can also be used to license materials covered by other copyright-like laws, such as semiconductor masks. So, as an example, you can release a drawing of a physical object or circuit under the GPL.
In many situations, copyright does not cover making physical hardware from a drawing. In these situations, your license for the drawing simply can't exert any control over making or selling physical hardware, regardless of the license you use. When copyright does cover making hardware, for instance with IC masks, the GPL handles that case in a useful way.