If the source code is included with the shipped distro, Yellow Dog is not required to make it available for download. Remember, the GPL is not internet-aware and only requires that sources accompany binaries without further restriction.
In this case, all it'll take is for one person to buy it and upload the sources in order to effectively make it downloadable - which is what the GPL ensures. But Yellow Dog doesn't have to do that themselves if they don't want to.
Not true. The word "download" isn't even in the GPL; instead, it states that the sources must either accompany the binaries or (alternatively) be made available to anyone that wants them. So long as Yellow Dog includes the sources (without further restriction on them) with its distro, there is no violation. Simply because most distros are kind enough to provide free ISOs does not mean it is a requirement.
Wrongo. The GPL says source must be included wherever the binaries are, and can't be further restricted. As long as Yellow Dog includes the sources with the distro, they're free to put it online or not at their own discretion.
If they want to sell it and not put it online, that's okay too. It'll just take one person to buy it and upload the sources, in that case.
Re:I know the Evil side will win their fight.
on
Lord of the Trailers
·
· Score: 1
Something along the lines of "and Sauron followed Morgoth down the same ruinous path into the Void" might be construed as a banishment - whereas Gandalf says he will become "a shadow of malice in the wilderness".
The discrepency is probably best explained that Sauron as a sentient entity became no more after the destruction of the One Ring, but the evil "leftovers" of him still haunted some desolate areas of the world after his passing.
At least, that's how I see it.
Re:I know the Evil side will win their fight.
on
Lord of the Trailers
·
· Score: 1
*ponders* I seem to recall Saruman's disembodied spirit looking to the West, perhaps in a vain hope of return to Valinor, before being dispersed by a west wind - his hope denied by Manwë for his treachery.
I think the key differences between LOTR and Star Wars is that LOTR has a third "chapter" that's quite good - whereas Star Wars' third film mostly sucks. That, and the "prequel" to LOTR is marvelous literature in its own right - whereas the Star Wars prequel is pretty crappy so far.
And I own one... They're superb for viewing and editing lots of text (due to their sharpness and non-refresh for static screens, both of which ease eyestrain) but they're less than ideal for gaming or video. This is because LCDs look like crap at anything but their native resolution and they don't update as fast as a CRT can - which results in blurriness in high-action situations.
That said, I find the idea of Apple forcing everyone to use LCDs somewhat obnoxious - and it sure isn't going to make Macs any cheaper...
And this is working for me right now. (GNOME/KDE users might need to place these in a different file) If that doesn't work, try adding:
XkbOptions "ctrl:nocaps"
to the keyboard segment of your XF86Config file. And if that doesn't work, you might have an oddball hardware-caps-lock type keyboard (which some Powerbooks use, and probably others) that might not be bind-able. In that case, try another keyboard, perhaps.
These guys make non-Windows keyboards with pride. And the best IBM ThinkPad lines ship without Windows keys to this day. So yes, fortunately for all of us, somebody still produces MS-free keyboards:)
If you're an X11 user, look up some of the functions of xmodmap. This will enable you to bind the ever-annoying "Caps Lock" into another "Control" key. I have my own laptop keyboard altered this way and it should work on any keyboard that doesn't implement the "Caps Lock" in pure hardware.
So, by virtue of choosing not to live free, I would, in effect, still be living free (since I chose not to live free) - and thus can't really choose not to live free after all.
My head still hurts. (And this is getting more silly:)
Are you offended
that "freedom" means that people don't have to make the same choices as you?
It's like the motto "live free or die". What if I don't want to live free? Does it mean I don't have the freedom to decide not to live free - and am therefore being not free to decide whether or not to live free.
Woah there. Some LCD monitors use standard analog VGA inputs, but not all. Please research this particular article for a listing of the more popular ones. There really is a difference.
Easy enough. Buy an X terminal to display all your X11 apps from the Big Noisy Box. Then you can just move Big Noisy Box anywhere you like with a bit of ethernet strung between the two.
This must be some definition of "lots of work" I was unaware of;)
In practice, most of the stuff that goes over 80 chars are long lists or function calls, which don't need the \ thingy whatsoever. But, in general, Python tends to reuse the basic syntax for lots of things and so it hasn't exhausted the list of special characters yet - I figure we can spare the \
The main problem, though, is long lines of code. What do you do when you hit the 80 character mark? The JavaScript implementation sucks,
it's no good if wrapover is also valid on its own... That's the annoying bit.
In Python, you can wrap code into another line by appending \ at the end of it. Or, if the syntax is unambiguous, even the \ can be dispensed with. For example:
I feel your pain. Growing up, it was always "Star Wars", followed by "the Empire Strikes Back", followed by "Return of the Jedi". The whole "you can't call it just 'Star Wars' now, it's 'A New Hope'" strikes me as a bit over-revisionist. If I say to anyone I know, "I'm gonna watch 'Star Wars' now", they'll know I mean the original - whereas saying "I'm gonna turn on 'A New Hope'" will draw confusion.
So, I'm gonna keep calling it "Star Wars" until Lucas' troops force me to call it otherwise.
If we waited for 2.4.4 and
released 7.1 after testing it, 2.4.5 would be current by the time it got out of the door. If we waited for 2.4.5, 2.4.6 would be current.
Obviously, you should wait until the Linux kernel is completely finished before shipping one. Once it reaches version 300.4-complete, then that should be about right.
Not officially supporting anything that hasn't passed QA isn't corporate idiocy either. It's simply practical.
Since RedHat is Linux (according to the press), you're obviously required to support every version of every piece of software that is compatible with Linux. Therefore, omniscience will be a hiring requirement for all support staff.
(but seriously, working on Linux all day must be a lot of fun except for all the stupid questions that pop up...)
does anyone see something weird too ? X-Windows is huge, big, feature rich and probably more bloated than any other piece of
open-source software available on earth.
You have got to be joking. XFree86 is about 30 megabytes for a full, compiled version. XEmacs is over 40. gcc+glibc is probably over 50.
So, yes, there are open-source projects that are a lot bigger.
Backward compatibility is the root of all (computer) evil !
This is even more stupid. Abandoning backwards-compatibility just for the sake of being "new and different" is a sure way to make a lousy, incompatible product that no one will use. The X11 protocol has its flaws, but addressing those flaws while keeping our existing clients intact will take a helluva lot less effort than reinventing the wheel just to make it "newer", "fancier" or "more like MS Windows".
Slashdot Mirror
In this case, all it'll take is for one person to buy it and upload the sources in order to effectively make it downloadable - which is what the GPL ensures. But Yellow Dog doesn't have to do that themselves if they don't want to.
The GPL is not internet-aware.
If they want to sell it and not put it online, that's okay too. It'll just take one person to buy it and upload the sources, in that case.
The discrepency is probably best explained that Sauron as a sentient entity became no more after the destruction of the One Ring, but the evil "leftovers" of him still haunted some desolate areas of the world after his passing.
At least, that's how I see it.
I think the key differences between LOTR and Star Wars is that LOTR has a third "chapter" that's quite good - whereas Star Wars' third film mostly sucks. That, and the "prequel" to LOTR is marvelous literature in its own right - whereas the Star Wars prequel is pretty crappy so far.
Even now, "^_^" is being documented as a new Perl operator...
Which is especially apt considering the amount of pr0n one can fit in 20GB. Maybe Iomega could make that part of its marketing campaign...
Perhaps they should exercise a bit more moderation in their moderation...
That said, I find the idea of Apple forcing everyone to use LCDs somewhat obnoxious - and it sure isn't going to make Macs any cheaper...
...but they just keep bouncing off the case of my Enterprise 4500 server. It's turning into quite a mess in there.
It's a bit like when the newbie walks into a lab full of Sparcs and asks whether they're Macs or PCs...
xmodmap -e "remove Lock = Caps_Lock"
xmodmap -e "remove Control = Control_L"
xmodmap -e "keysym Control_L = Caps_Lock"
xmodmap -e "keysym Caps_Lock = Control_L"
xmodmap -e "add Lock = Caps_Lock"
xmodmap -e "add Control = Control_L"
And this is working for me right now. (GNOME/KDE users might need to place these in a different file) If that doesn't work, try adding:
XkbOptions "ctrl:nocaps"
to the keyboard segment of your XF86Config file. And if that doesn't work, you might have an oddball hardware-caps-lock type keyboard (which some Powerbooks use, and probably others) that might not be bind-able. In that case, try another keyboard, perhaps.
These guys make non-Windows keyboards with pride. And the best IBM ThinkPad lines ship without Windows keys to this day. So yes, fortunately for all of us, somebody still produces MS-free keyboards :)
If you're an X11 user, look up some of the functions of xmodmap. This will enable you to bind the ever-annoying "Caps Lock" into another "Control" key. I have my own laptop keyboard altered this way and it should work on any keyboard that doesn't implement the "Caps Lock" in pure hardware.
My head still hurts. (And this is getting more silly :)
It's like the motto "live free or die". What if I don't want to live free? Does it mean I don't have the freedom to decide not to live free - and am therefore being not free to decide whether or not to live free.
Ow, my head hurts...
Woah there. Some LCD monitors use standard analog VGA inputs, but not all. Please research this particular article for a listing of the more popular ones. There really is a difference.
Easy enough. Buy an X terminal to display all your X11 apps from the Big Noisy Box. Then you can just move Big Noisy Box anywhere you like with a bit of ethernet strung between the two.
In practice, most of the stuff that goes over 80 chars are long lists or function calls, which don't need the \ thingy whatsoever. But, in general, Python tends to reuse the basic syntax for lots of things and so it hasn't exhausted the list of special characters yet - I figure we can spare the \
In Python, you can wrap code into another line by appending \ at the end of it. Or, if the syntax is unambiguous, even the \ can be dispensed with. For example:
1 + 2 + \
3
Is okay, as is:
1 + (2 +
3)
But:
1 + 2 +
3
will cause complaint.
So, I'm gonna keep calling it "Star Wars" until Lucas' troops force me to call it otherwise.
Obviously, you should wait until the Linux kernel is completely finished before shipping one. Once it reaches version 300.4-complete, then that should be about right.
Since RedHat is Linux (according to the press), you're obviously required to support every version of every piece of software that is compatible with Linux. Therefore, omniscience will be a hiring requirement for all support staff.
(but seriously, working on Linux all day must be a lot of fun except for all the stupid questions that pop up...)
You have got to be joking. XFree86 is about 30 megabytes for a full, compiled version. XEmacs is over 40. gcc+glibc is probably over 50. So, yes, there are open-source projects that are a lot bigger.
This is even more stupid. Abandoning backwards-compatibility just for the sake of being "new and different" is a sure way to make a lousy, incompatible product that no one will use. The X11 protocol has its flaws, but addressing those flaws while keeping our existing clients intact will take a helluva lot less effort than reinventing the wheel just to make it "newer", "fancier" or "more like MS Windows".
I just call em "ogg"s. It's two less syllables than the clunky "mp3" name, and sounds kinda neat. :)