asomiv

The way I read it is that they want other operating systems to adopt the same infrastructure, e.g. kernel mode setting, instead of implementing an abstraction layer in Wayland itself.

If winlogon runs in the same security context and the same desktop as explorer.exe then a key logger will be able to intercept all logins, and a screenshotter will be able to take screenshots of your login screen. Clearly you don't want that to be possible.

Or are you saying that they never should have made Ctrl-Alt-Del do anything else but starting the task manager?

Then have git output a message telling the user that the setting is now global. That way you accomodate for both cases in a usable manner.

I dispute this claim. There are only very few ways your ~/.gitconfig can be corrupted:

1. You edited it by hand and fucked up the syntax. In this case git could print an error instead if offering to add the username/email.

2. You deleted itself. When git asks you for the username/email again it'll actually tell you that that file was for storing the username/email.

3. Filesystem error. A faulty gitconfig with be the last thing the user is worrying about.

All in all I don't see how all of this would imply that prompting a username/email isn't a good idea.

I'm not the guy who voted you down, but I'm guessing other people did it because your posts' attitude imply that new users are absolutely not worth accommodating for and that usability is not important. It comes over as rather elitist.

Your posts remind me of typical Linux-on-the-desktop-defending posts that claim Linux's usability is just fine. Making X.org work isn't difficult, just run these 4 incomprehensible commands, edit this configuration file and insert this snippet for which you have to read a 50 page manual to understand. It's easy! What, can't do it? Then you're not deserving to use Linux, but Linux is oh so user friendly! (disclaimer: I love Linux, I want it to succeed on the desktop, but this kind of attitude is helping neither Linux nor Git)

You can provide a virtual keyboard the way E-Gold does it in order to fight key loggers.

I haven't used RedHat-based distros for years now but I remember that back when I switched to Debian-based distros I was equally confused about Debian's package management system. I didn't think, and still don't think, that dpkg and apt are documented that well. To answer your question: yum is to rpm as apt is to dpkg. But I've always found it weird that there's a difference between apt-get and apt-cache; in contrast, "yum install" and "yum search" use the same executable. The documentation concerning building Debian packages is often out of date and scattered all over the Internet with no clear central place. And finally there's this "aptitude" thing; I still don't understand why it exists and how it's different from regular apt.

This is actually a pretty good idea. The captcha should include some kind of system for reporting slavery or other kinds of work-related abuse, whereby the reporter will be rewarded if the report results in the slavedriver being successfully prosecuted. As the number of employees become bigger, the likelihood that at least one of the employees will rat out his employer increases exponentially.

Why is grsecurity not merged upstream?

There are a lot of local root exploits in Linux the past few years. But ever since Linux dropped the stable-unstable version numbering scheme, different distributions ship a wide variety of kernels + their own patches instead of "the latest kernel" because the latest may not necessarily be stable. How do I find out which local root exploits my distribution's kernel is vulnerable against, and how do I find out how quickly they get fixed? I'm on Debian 6 right now.

WebM isn't a container format. It's a standard which specifies MKV (container) + VP8 (video codec) + Vorbis (audio codec).

I keep hearing this battery life thing but how much battery life does H264 hardware acceleration really save? I dare to wager that the majority of the power is used by the screen, not the CPU.

That's because someone deleted the site object. The demo database is reset every 24 hours and I've just issued a manual reset.

Finally! I was waiting for someone to recognize the name. :D

The sections are really short. Giving each section its own URL will make the reading experience horrible. Most of my users told me that they actually prefer a one-page manual because it makes searching easier.

The thread identifier is not the problem. I'm only displaying one comment topic at a time by using a lightbox. However once I have loaded a Disqus comment topic, switching to another one seems to fail randomly even if I call their documented DISQUS.reset API.

If people keep repeating the same thing then that would qualify as an active discussion. Juvia is specifically not designed for active discussion. It's just for simple commenting.

Yes. Still working on it though: https://github.com/FooBarWidget/mizuho It's not finished yet. The Juvia site key and URL are currently hardcoded in the source.

The submitter probably just meant "Disqus-like commenting server".

I just added a 'Reply to this comment' button because so many people asked for it.

No it's not a final decision, but I'm not going to write support for it so feel free to contribute. That said I did add a 'Reply to comment' button a few minutes ago by popular demand.

I wrote it mainly because I found Disqus and IntenseDebate too limiting, not because of concerns about hosting or data ownership. I'm trying to implement per-section commenting for the Phusion Passenger manual similar to how it's done in the Django book (http://www.djangobook.com/). However after a week of trying it became painfully clear that Disqus was only designed for one use case in mind: a single comment box per page, e.g. blogs. Comment topics in Disqus are tied to the URL, which doesn't work in my case because I want each section on the same page to have a different comment topic. The Disqus developer documentation says that they support AJAX but I did things exactly as documented and all I got was vague undebuggable JavaScript errors.

IntenseDebate was the almost exactly same. I gave up after two days.

I finished the most important parts of Juvia today. I got Juvia commenting in the manual working in about 15 minutes.

The program in question is not a conforming program in the first place. It's the Ruby interpreter and it does all kinds of low-level stuff. alloca(0) is called from the garbage collector in order to detect the end of the stack so that the garbage collector can scan the stack for pointers. The code assumes that it's running on a system where there is a stack at all, which is pretty much all systems nowadays.

You're right, but would alloca(0) be undefined behavior or simply implementation-specific behavior? I think the latter would make more sense, and if so then alloca(0)'s behavior should at least be consistent and not depend on any optimization settings.

The point is that the behavior depends on the optimization setting. Worse: as you saw on the example, the optimizer actually expects the result to be non-NULL!

After seeing how all the ads and flash websites slow down my dad's Firefox browsing experience, I tried to switch him to Chrome. After a while, he switched back to Firefox by himself.

The reason? He uses the dropdown box in the location bar as a kind of bookmarking mechanism. Chrome doesn't have such a location bar. And he's not content with using real bookmarks, it has to be the location bar dropdown and nothing else.

Good luck making SCTP work with the $50 routers that everybody has in their homes. While you're at it, will you convince the rest of the world to switch to IPv6 please?

You can't poll on TTYs for example. I remember this bug from 2004 and apparently they still haven't fixed it.

Yes I would say kqueue, the interface, is superior to epoll. Kqueue allows one to batch modify watcher states and to retrieve watcher states in a single system call. With epoll, you have to call a system call for every modification. Kqueue also allows one to watch for things like filesystem changes and process state changes, epoll is limited to socket/pipe I/O only. It's a shame that Linux doesn't support kqueue.

But as awesome as kqueue is, OS X apparently broke it: http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#OS_X_AN...

The kqueue interface is awesome, but unfortunately kqueue is bugged on OS X: http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#OS_X_AN... (as are poll() and select()!)