Technically the subway co. of NY city are right. It *is* copyright infringement and the map *was* distributed without their permission.
That said, in practice the NYC subway co. already made the map available to the general public, so it's not like there are any losses or damages as a result of this. In fact making the map available on IPod might actually increase the number of subway users. This rises the question, "what's the problem?" Conclusion: NYC subway co., get a life.
This is my third Ubuntu install now, before that I ran RH9.
One of the main reasons I switched to Ubuntu was because I wanted a distro with 2.6 kernel with proper package management. At the time, there were 2 realistic options; Gentoo and Ubuntu. Gentoo seemed to be too much of a fuss.
The breezy preview installed pretty smoothly. The majority of the work however comes after the install. I keep an install log to make it easier to tweak the install to my liking.
I took out my soundcard in favor of the one that's on the mainboard. I found that the MIDI device was not detected properly 'out of the box'; because of this, amidi --dump did not find the default MIDI device. This was solved after making a symbolic link (ln -s midiC1D0 midiC0D0). No big thing here; by what I could tell this behaviour was present in the previous release as well.
The main difference I found with hoary is that GCC 4 is the compiler of choice now, as x.org instead of xfree86 can be considered the 'main difference' to the version before hoary. This is actually a bit of a fuss, however being on the leading edge is why I went for Ubuntu in the first place.
To allow realtime capabilities in userland, recompiling the kernel is needed (as it was before) to allow running the realtime-lsm module. This requires pointing the Makefile of the linux sources to gcc 4 rather than 3.4. I find this a bit odd.
I found the kernel sources initially didn't compile on gcc 4; In one instance, a filesystem function declaration in the header file (.h) differs from the source file (.c/c++), which is a matter of things being declared 'static' in one place and not in the other. I fixed this by letting the function declaration in the source file follow the declaration of the header file.
After this, the kernel compiled and things seem to be stable. I have the impression it runs slightly smoother than hoary, but this is subjective.
The main thing I haven't gotten around to buidling yet is mplayer. I did notice that it complains about GCC 4 because it hasn't been tested on it. It will refuse to build unless forced. When forced, GCC 4 will give some errors. I'll still have to figure out how to complete building it properly. I've heard some people run gcc 3.4 alongside 4 for cases like this. YMMV.
Main question I have myself is, will the 5.10 preview automatically upgrade to 5.10 once it is released?
Unlike the late Clippy, a ghostly text-formatting toolbar hovers near your cursor; it fades or darkens in response to your mouse movements. Right-clicking a mouse will reveal the same task-specific menu choices as offered in the masthead banner. (cues creepy music) I see dead Clippies...
1. Have someplace you can put things to drink. It always breaks concentration when you have to get up, go to another room, and get a drink.
3. Get a pet. Preferrably a cat. [...snip...]Because there is this little thing called Phlebitus that you can get. (It is also called Secretary's Disease.) You get it from spending long hours sitting doing something.
Is it me or can you simplify by getting rid of both the fridge and the pet? If your hourly drinks are a bit away, you'll need to get up for them and have your Phlebitus problem solved. Also I couldn't help wondering: do you or do you not want to have your concentration broken?
With a good system, you should be able to point out where the instruments are - can't do this with the Bose, piece of cake with the Magnats.
From a soundperson perspective I find this discussion 'A is better than B' a bit pointless.
In a discussion "Bose vs Magnat", "Better" is relative.
First of all recording technique makes a huge difference in this. In signals recorded with crossed microphones (x/y), locating the instrument is a piece of cake, though it might lack in 'spatial' feeling. When recorded with 2 parallel mics (A/B), things might sound very spatial but locating the panorama of the instrument in the stereo image is much harder. For this reason, most pop recordings are recorded in X/Y (mono compatible for radio play, good panning, does not sound very spatial) while most classical/jazz is recorded A/B (spatial sound but poor localization of instruments. Phase problems may occur, possible mono incompatibility).
Something similar happens in playing back the sound. Bose designed their speakers to have an as large as possible 'sweet spot', resulting in a more consistent spatial sound across the room, however this is at the cost of localization of the instruments.
The magnats have a relatively narrow 'sweet spot' compared to the bose speakers. As a result, localization of the instruments in a stereo image is more accurate, but the 'sweet spot' is much smaller.
All other things left out of consideration, if accuracy in stereo image is your thing, you'll prefer the Magnats. If you prefer consistent sound all over the room, you'll prefer Bose.
Which is why I always tape the mouse cord to the table at some distance from the mouse. Keeps it from tangling up the cable, prevents the cable from being pulled back behind the table (solving the tugging) and generally solves the irritation problem.
"This has never been tested experimentally: no one has measured how gravity behaves over distances below about a hundredth of a millimetre."
On atomic scale, 1/100 mm is still pretty huge and I understand science itself has progressed enough to have the means to make such measurements. So before speculating any further, it seems it would make sense to start doing that first then, wouldn't it?
Nobody seems to have thought of writing the formula part of the snippet of perl as
$e=$m*($c*$c)
This would help portability to other programming languages, as the * operator is pretty much universal. Also, in various languages, c*c most likely compiles more cleanly and run faster than c^2 because multiplication is a simpler operation than 'to the power of'. Moreover, some languages require linking in a math library to calculate the square of a number, whereas multiplication does not usually have these requirements.
It already has all these neat features in it including a clock (otherwise how would it measure pulse?). I wonder if this device also show the time of day on its display? That would free the wearer from needing to wear 2 'watches'.
The built-in phone is kinda neat though... all we need now is a fully automated, bullet proof car to go with it.
"The crocodile has an immune system which attaches to bacteria and tears it apart and it explodes. It's like putting a gun to the head of the bacteria and pulling the trigger," he said, "dodge *this*".
Oh, not me. I'd never do that. And I'd say it's pretty obvious why.
Everybody else is on board with plain text
I don't know where you live/work, but out here in the real world, not everybody is on board with plain text. Not anymore.
I use mutt and fetchmail in a company of Exchange users. Almost every email I get at work now, from everybody, is in html. (Unless I sent it to myself.) I don't like it, but I deal with it. It's certainly easier to deal with it than to try and change everybody else.
I could change jobs, but over something as trivial as html emails? No. I like my job, I like the people I work with, so I just bend like the reed in the wind...
Still, the executives are certainly worse about email ettiquette than most, and it's not just in this company -- everywhere I've worked I've found this to be the case. They don't include Subjects at all, or include useless ones like `message'. Some will type up a memo and send it as a.pdf file attachment, or worse as a.bmp file. They rarely trim anything when responding to a post -- they just top post away. (But many people do that...)
Swarzenegger against violence in games... Isn't that just tad hypocritical?
How about:
1. Intercept output stream of fail-safe codec (DRM enabled, if you wish)
to screen
2. Save to disk
3. Fail-safe method no longer is fail-safe.
How about:
1. View content on screen
2. Capture with camcorder, save to disk
3. Obvious
If you can view it, it isn't fail-safe.
No "profit" step here.
a piece of the human body that babies drink from.
FYI it's called a boob.
Only one problem here. There is no spoon.
...at least I'll no longer be forced to send my CV as .doc.
Technically the subway co. of NY city are right. It *is* copyright infringement and the map *was* distributed without their permission.
That said, in practice the NYC subway co. already made the map available to the general public, so it's not like there are any losses or damages as a result of this. In fact making the map available on IPod might actually increase the number of subway users. This rises the question, "what's the problem?" Conclusion: NYC subway co., get a life.
This is my third Ubuntu install now, before that I ran RH9.
One of the main reasons I switched to Ubuntu was because I wanted a distro with 2.6 kernel with proper package management. At the time, there were 2 realistic options; Gentoo and Ubuntu. Gentoo seemed to be too much of a fuss.
The breezy preview installed pretty smoothly. The majority of the work however comes after the install. I keep an install log to make it easier to tweak the install to my liking.
I took out my soundcard in favor of the one that's on the mainboard. I found that the
MIDI device was not detected properly 'out of the box'; because of this, amidi --dump did not find the default MIDI device. This was solved after making a symbolic link (ln -s midiC1D0 midiC0D0). No big thing here; by what I could tell this behaviour was present in the previous release as well.
The main difference I found with hoary is that GCC 4 is the compiler of choice now, as
x.org instead of xfree86 can be considered the 'main difference' to the version before hoary. This is actually a bit of a fuss, however being on the leading edge is why I went for Ubuntu in the first place.
To allow realtime capabilities in userland, recompiling the kernel is needed (as it was before) to allow running the realtime-lsm module. This requires pointing the Makefile of the linux sources to gcc 4 rather than 3.4. I find this a bit odd.
I found the kernel sources initially didn't compile on gcc 4; In one instance, a filesystem function declaration in the header file (.h) differs from the source file (.c/c++), which is a matter of things being declared 'static' in one place and not
in the other. I fixed this by letting the function declaration in the source file follow the declaration of the header file.
After this, the kernel compiled and things seem to be stable. I have the impression it runs slightly smoother than hoary, but this is subjective.
The main thing I haven't gotten around to buidling yet is mplayer. I did notice that it complains about GCC 4 because it hasn't been tested on it. It will refuse to build unless forced. When forced, GCC 4 will give some errors. I'll still have to figure out how to complete building it properly. I've heard some people run gcc 3.4 alongside 4 for cases like this. YMMV.
Main question I have myself is, will the 5.10 preview automatically upgrade to 5.10 once it is released?
Unlike the late Clippy, a ghostly text-formatting toolbar hovers near your cursor; it fades or darkens in response to your mouse movements. Right-clicking a mouse will reveal the same task-specific menu choices as offered in the masthead banner. (cues creepy music) I see dead Clippies...
And in fact, that law was also quoted in Steve McConnell's "Rapid Development", published by Microsoft Press. They should know better.
The simpler the better, I second that.
1. Have someplace you can put things to drink. It always breaks concentration when you have to get up, go to another room, and get a drink.
3. Get a pet. Preferrably a cat. [...snip...]Because there is this little thing called Phlebitus that you can get. (It is also called Secretary's Disease.) You get it from spending long hours sitting doing something.
Is it me or can you simplify by getting rid of both the fridge and the pet? If your hourly drinks are a bit away, you'll need to get up for them and have your Phlebitus problem solved. Also I couldn't help wondering: do you or do you not want to have your concentration broken?
Best of all, you won't need to bring the dog, cause he's only needed to take the blame :)
Let me ask you.
With a good system, you should be able to point out where the instruments are - can't do this with the Bose, piece of cake with the Magnats.
From a soundperson perspective I find this discussion 'A is better than B' a bit pointless. In a discussion "Bose vs Magnat", "Better" is relative.
First of all recording technique makes a huge difference in this. In signals recorded with crossed microphones (x/y), locating the instrument is a piece of cake, though it might lack in 'spatial' feeling. When recorded with 2 parallel mics (A/B), things might sound very spatial but locating the panorama of the instrument in the stereo image is much harder. For this reason, most pop recordings are recorded in X/Y (mono compatible for radio play, good panning, does not sound very spatial) while most classical/jazz is recorded A/B (spatial sound but poor localization of instruments. Phase problems may occur, possible mono incompatibility).
Something similar happens in playing back the sound. Bose designed their speakers to have an as large as possible 'sweet spot', resulting in a more consistent spatial sound across the room, however this is at the cost of localization of the instruments.
The magnats have a relatively narrow 'sweet spot' compared to the bose speakers. As a result, localization of the instruments in a stereo image is more accurate, but the 'sweet spot' is much smaller.
All other things left out of consideration, if accuracy in stereo image is your thing, you'll prefer the Magnats. If you prefer consistent sound all over the room, you'll prefer Bose.
For those wondering what he's talking about, here is a link.
Which is why I always tape the mouse cord to the table at some distance from the mouse. Keeps it from tangling up the cable, prevents the cable from being pulled back behind the table (solving the tugging) and generally solves the irritation problem.
...those stars are being blown up by the Death Star.
...the Hollywood version probably cost less too. Still, pretty neat.
... bring out the tar and feathers.
"This has never been tested experimentally: no one has measured how gravity behaves over distances below about a hundredth of a millimetre."
On atomic scale, 1/100 mm is still pretty huge and I understand science itself has progressed enough to have the means to make such measurements. So before speculating any further, it seems it would make sense to start doing that first then, wouldn't it?
Nobody seems to have thought of writing the formula part of the snippet of perl as
$e=$m*($c*$c)
This would help portability to other programming languages, as the * operator is pretty much universal.
Also, in various languages, c*c most likely compiles more cleanly and run faster than c^2 because multiplication is a simpler operation than 'to the power of'.
Moreover, some languages require linking in a math library to calculate the square of a number, whereas multiplication does not usually have these requirements.
It already has all these neat features in it including a clock (otherwise how would it measure pulse?). I wonder if this device also show the time of day on its display? That would free the wearer from needing to wear 2 'watches'. The built-in phone is kinda neat though... all we need now is a fully automated, bullet proof car to go with it.
No it isn't Goatse. Really. Go ahead. Click that link. Muhahaha.
"The crocodile has an immune system which attaches to bacteria and tears it apart and it explodes. It's like putting a gun to the head of the bacteria and pulling the trigger," he said, "dodge *this*".
Oh, not me. I'd never do that. And I'd say it's pretty obvious why.
...
.pdf file attachment, or worse as a .bmp file. They rarely trim anything when responding to a post -- they just top post away. (But many people do that ...)
Everybody else is on board with plain text
I don't know where you live/work, but out here in the real world, not everybody is on board with plain text. Not anymore.
I use mutt and fetchmail in a company of Exchange users. Almost every email I get at work now, from everybody, is in html. (Unless I sent it to myself.) I don't like it, but I deal with it. It's certainly easier to deal with it than to try and change everybody else.
I could change jobs, but over something as trivial as html emails? No. I like my job, I like the people I work with, so I just bend like the reed in the wind
Still, the executives are certainly worse about email ettiquette than most, and it's not just in this company -- everywhere I've worked I've found this to be the case. They don't include Subjects at all, or include useless ones like `message'. Some will type up a memo and send it as a
OK, I'll bite. You got the grammar wrong. It is "All your code ARE belong to us".