You should install the ntp-doc package and then check out/usr/share/doc/ntp-doc/html/ntpq.html:
peers
Obtains a current list peers of the server, along with a summary of each peer's state. Summary information includes the address of the remote peer, the reference ID (0.0.0.0 if this is unknown), the stratum of the remote peer, the type of the peer (local, unicast, multicast or broadcast), when the last packet was received, the polling interval, in seconds, the reachability register, in octal, and the current estimated delay, offset and dispersion of the peer, all in milliseconds. The character at the left margin of each line shows the synchronization status of the association and is a valuable diagnostic tool. The encoding and meaning of this character, called the tally code, is given later in this page.
Furthermore, note that you will get a more accurate reading if you switch from using the generic worldwide 'debian' pool, to a country specific one, as described on How do I setup NTP to use the pool?.
Most companies producing anime do not go after file-sharers unless a particular anime has been licensed in that region. That has no bearing on whether distributing these works constitutes copyright infringement.
I wonder how much of it is legally grey? For example, anime that is not licensed for distribution (completely unavailable) in the US. Yes, it's still copyrighted, but that doesn't mean it's a copyright violation. Seems like a straightforward case of copyright infringement to me. If the copyright holder has not granted you permission to distribute their work then you simply are not allowed to do so!
More seriously, I expect it is because it ships its own copy of QT, which uses one of the default QT themes---'Windows' from the look of it---rather than whatever theme you have told your distro's copy of QT to use.
What's wrong with google earth, besides trying to muddle through with Qt instead of having a native UI, is that it has a nasty habit of buggering window server memory that it shouldn't be touching. Isn't it the display server's job to disallow that from happening in the first place?
Sometimes, someone's a bastard and takes all the candy. (Proprietary) How so? The code is still there for anyone else to take.
Other times, someone takes all your candy, eggs your house and gives your candy to everyone in your stead without saying anything.. (GPL)
Both ways you end up with no candy, but I think the GPL thieves are much more insulting. Oh, grow up. Your analogy is terrible.
If the person who wrote the code didn't want this to happen (and, guess what--he didn't), then he would have chosen a copyleft license that would have prevented it from happening.
Their Linux version is shit, it can't even use ALSA!
This means that it will fail to work if any other app has your sound device open when it wants to play sounds; and that, while it has the sound device open, all other apps will similarly fail...
Yeah, and we've always been at war with Eastasia. The security restrictions we have put in place are temporary measures only. They are necessary for your own safety and protection. They will be relaxed once we have won the war.
Hold on a second... you are talking about both Linux (the kernel) and Linux (the platform, which does not in fact exist). Which do you mean?
If you are talking about the kernel, then you should read the COPYING file: if your work is a derived work of the Linux kernel, then it must be released under the GPL. If it is not a derived work of the kernel then you can do whatever you want.
If you are talking about one of the many platforms based on Linux (e.g., RHEL, Debian GNU/Linux, etc) then you must consider the licensing terms of every work which you derive from (e.g., the GNU C Library, GTK+).
I harken back to the days of Netware NLMs. Netware didn't seem to want some sort of ownership for people loading things onto their kernel, nor did Microsoft demand rights for people distributing TSRs. So why is this different? And look where it got them. Well, I have no idea if Netware is still alive and/or relevant today, but the sheer number of crappy proprietary drivers written by two bit hardware companies has locked them to the shitty old i386 architecture, and it looks like this will continue to be the case for decades to come.
BTW, I must correct your implied assertion that the free software community wants "ownership" of a vendor's code. This is not the case! We merely want vendors to respect the licensing terms of any works from which they create a derivative work.
Slashdot Mirror
Probably not. ntpd has to be able to set the system clock, and has to be able to listen on port 123.
You should install the ntp-doc package and then check out /usr/share/doc/ntp-doc/html/ntpq.html:
Furthermore, note that you will get a more accurate reading if you switch from using the generic worldwide 'debian' pool, to a country specific one, as described on How do I setup NTP to use the pool?.
George Carlin gets it so so right!
Because it uses QT! :)
More seriously, I expect it is because it ships its own copy of QT, which uses one of the default QT themes---'Windows' from the look of it---rather than whatever theme you have told your distro's copy of QT to use.
Those are all library functions wrapping the same underlying system call (execve).
Please elaborate?
You save on disk space and memory use by not having to have a copy of all your libs compiled for i386 lying around.
:(
It's a real shame that the Java browser plugin is not a part of the OpenJDK release.
Both ways you end up with no candy, but I think the GPL thieves are much more insulting. Oh, grow up. Your analogy is terrible.
If the person who wrote the code didn't want this to happen (and, guess what--he didn't), then he would have chosen a copyleft license that would have prevented it from happening.
It's always sad to see formerly free works adopting non-free licenses. :(
Tell that to all the PIRA members living free in the US.
http://en.wikipedia.org/w/index.php?title=NatWest_ Three&oldid=141975014
Their Linux version is shit, it can't even use ALSA!
This means that it will fail to work if any other app has your sound device open when it wants to play sounds; and that, while it has the sound device open, all other apps will similarly fail...
A shame that it's useless because it can't use ALSA.
Yeah, and we've always been at war with Eastasia. The security restrictions we have put in place are temporary measures only. They are necessary for your own safety and protection. They will be relaxed once we have won the war.
People should really RTFM of the tool they are using.
l ities/RootkitRevealer.mspx
http://www.microsoft.com/technet/sysinternals/Uti
This is CVE-2007-4324.
s/inefficient BSD crap/functions that result in silent loss of data/
Since you are the one asserting that it is viral, surely you should be the one to prove it?
If you are talking about the kernel, then you should read the COPYING file: if your work is a derived work of the Linux kernel, then it must be released under the GPL. If it is not a derived work of the kernel then you can do whatever you want.
If you are talking about one of the many platforms based on Linux (e.g., RHEL, Debian GNU/Linux, etc) then you must consider the licensing terms of every work which you derive from (e.g., the GNU C Library, GTK+). I harken back to the days of Netware NLMs. Netware didn't seem to want some sort of ownership for people loading things onto their kernel, nor did Microsoft demand rights for people distributing TSRs. So why is this different? And look where it got them. Well, I have no idea if Netware is still alive and/or relevant today, but the sheer number of crappy proprietary drivers written by two bit hardware companies has locked them to the shitty old i386 architecture, and it looks like this will continue to be the case for decades to come.
BTW, I must correct your implied assertion that the free software community wants "ownership" of a vendor's code. This is not the case! We merely want vendors to respect the licensing terms of any works from which they create a derivative work.
And Microsoft is merely "following orders", right?
I think that 'nodiratime' has no effect if you set 'noatime'.
:)
Down with cargo-culting!