Those people wouldn't need directions as to how to do this, either, and therefore are outside of the realm of discussion. I mean, if "don't use the default settings" is valid, then "hold down shift when inserting the CD" and "why are you using Windows at all, dumbass?" are just as valid. Also, WMA sucks, even at high bitrates (where its space gain is lost in favor of other CODECs that were created for a reason other than "We're MS, we need to reinvent the wheel to make DRM more popular").
If only there was a free alternative one could use on most any platform that matters. Why, those diagrams could be easily produced and updated without a great expenditure of time or effort.
bash-2.05a$ which ftp.exe c:\WINNT\system32/ftp.exe bash-2.05a$ strings `which ftp.exe` @(#) Copyright (c) 1983 The Regents of the University of California.
All rights reserved. bash-2.05a$ uname -a Windows_NT XhostnameX 5 01 586
They must have forgotten to rewrite the copyright line...
Actually, the default WMA settings are pretty crummy, and unless you have some kind of low-fi setup costing $10, you probably can discern a difference. Not that Switchfoot is known for their subtle musical nuances, but none the less, it's likely that a difference will be perceptible unless you crank the quality all the way up (or use another codec all together - perhaps one designed for sound quality rather than size, maybe even a lossless codec like "monkey's audio").
They probably wouldn't use actual Velcro(R)(TM)(ASAP)(C)(DR) brand Velcro(R)(TM)(ASAP)(C)(DR) anyway, likely opting for something cool like SuperLock fasteners. By golly, I'd go to a public demonstration of SuperLock fasteners...
I was hoping that it'd behave like lots of other programs ("make -t install" included) where it was more like a test mode. Though, in retrospect, that *still* wouldn't do what you wanted... Remind me to check on an actual machine before posting suggestions in the future.:)
That's what the --prefix option in./configure is for - to specify that you're usign a root other than/. Similarly, there are --bindir, --mandir, etc arguments for installers. In fact, most package managers just change those parameters around to build their package in a temp dir using their preferred paths, bundle the files up, and go.
Best to stick with the abstraction - it generally structures things so that your changes aren't blown away when you upgrade a package (RPM is a poop package manager). You'll be happier when you learn to work *with* the tools rather than working around them, and YaST is really a nice, handy tool once you decide that it's worth learning (since SuSE's not getting rid of it any time soon).
How dare you not know the American culture's slang? Why, if it's derisive here, then no one anywhere in the world can use it. Nor can they name their dog Wilbur. In the UK, you guys also took our perfectly good derisive term "fag" and applied it to cigarettes. Man, have you people no care for the homosexual community? That whole smoking thing will probably never catch on now...
P2 was a PPro with MMX, which was *not* basicaly a Pentium. Notably, the PPro used a RISC core and could translate CISC, while the Pentium was straight CISC, and you could run 4 PPros - which you could only run up to two Pentiums (or first-gen PIIs, for that matter). The PPro was also optimized for 32-bit apps, while the Pentium actually outperformed on 16-bit apps at the same clock speed. Otherwise, your lineage is simplistically accurate...:)
Itanium hasn't been a giant success largely because of software screw-ups - it took a while for compilers to properly optimize for the CPU, and programmers failed to think of it as being a different CPU than their P3 or Xeon. Lots of x86 stuff just didn't (some still doesn't) build well for ia64 (Itanium), while it may still work well on the more similar em64t (Xeon). Ia64 is a really cool architecture, it's just not yet fully exploited. http://www.gelato.org/ and http://www.ia64-linux.org/ are good starting points for Linux-oriented information on that arch...
I guess Ballmer is pretty big & retarded looking, while Gates is fairly small and geeky. I think I'll refer to them collectively as Master Blaster henceforth. They need a big leather outfit now...
So, I presume that, since we can't do shit to stop it, I can go back to buying R-12 for my old cars again real soon? The evaporator in my Caprice just doesn't work as efficiently with the R-134a conversion, and Freeze-12 isn't as effective.:)
I've been a *nix sysadmin for about a decade, and in that time I have tested several fairly unstable hardware configurations - not to mention the experimenting I do on my home network. The more stuff you mess with the more likely you are to run in to / cause failures, even though failure's still a very low percentage overall.:)
Generally, though, problems are introduced through too many unclean shutdowns (due to lower-level development), or flaky hardware of some sort.
That's somewhat irrelevent, since reiser isn't the filesystem you ideally want to be using for a few really large files. You want XFS for that (or possibly ext3). Reiser's big thing is good journaling, awesome performance and space usage with a bunch of really small files (think maildirs, where each message is a separate file and probably less than a single filesystem block) or "regular" usage. It works with huge files, but that's not really where it shines.
That said, I have no problems with reads during the creation of 4-6GB files on recent revisions of Reiser 3 (BTW, I use Reiser because performance isn't as critical and I'm familiar with the recovery tools - after a crash isn't the time to be learning about how to recover a damaged filesystem). I haven't done any formal benchmarking, but I have done things that do in fact read from files while a big one's being written, and I don't have 6GB RAM so I know it's not being cached.:)
Personally, I've found Reiser to be the best. I've lost data on ext2 and ext3, as well as jfs (and reiser, once). Overall, I've also lost weeks of time waiting for ext to fsck on an "unscheduled" reboot.:)
Of course, this is moot since none of them will regularly lose files, and anything important is regularly backed up. Not to mention that a single UPS to weather minor power interruptions costs under $100... Right?;)
Just in case you care about the extent of my vocabulary, I'm well aware of the meaning of "girding" as a sort of protective bolstering.:) None the less, the obscurity of the term combined with the context and similarity to "grinding", etc - well, it struck me as amusing. I think I'd enjoy watching that guy talking to a bunch of pot heads, especially if that's an example of an expression that he uses in normal conversation...
"we're girding our loins"? I don't care how excited they are about this potential money maker - that sounds like a means of celebration one would generally keep private.
Slashdot Mirror
Those people wouldn't need directions as to how to do this, either, and therefore are outside of the realm of discussion. I mean, if "don't use the default settings" is valid, then "hold down shift when inserting the CD" and "why are you using Windows at all, dumbass?" are just as valid. Also, WMA sucks, even at high bitrates (where its space gain is lost in favor of other CODECs that were created for a reason other than "We're MS, we need to reinvent the wheel to make DRM more popular").
Imprecise pronouns. They'll get you every time, expecially when you say "it" in a discussion titled "ftp.exe". :)
If only there was a free alternative one could use on most any platform that matters. Why, those diagrams could be easily produced and updated without a great expenditure of time or effort.
Actually, the default WMA settings are pretty crummy, and unless you have some kind of low-fi setup costing $10, you probably can discern a difference. Not that Switchfoot is known for their subtle musical nuances, but none the less, it's likely that a difference will be perceptible unless you crank the quality all the way up (or use another codec all together - perhaps one designed for sound quality rather than size, maybe even a lossless codec like "monkey's audio").
They probably wouldn't use actual Velcro(R)(TM)(ASAP)(C)(DR) brand Velcro(R)(TM)(ASAP)(C)(DR) anyway, likely opting for something cool like SuperLock fasteners. By golly, I'd go to a public demonstration of SuperLock fasteners...
I was hoping that it'd behave like lots of other programs ("make -t install" included) where it was more like a test mode. Though, in retrospect, that *still* wouldn't do what you wanted... Remind me to check on an actual machine before posting suggestions in the future. :)
"Spelling police, get on this ASAP!!"
That's what the --prefix option in ./configure is for - to specify that you're usign a root other than /. Similarly, there are --bindir, --mandir, etc arguments for installers. In fact, most package managers just change those parameters around to build their package in a temp dir using their preferred paths, bundle the files up, and go.
If you pass a -t in there, does that cause the package to be empty, to not be installed, or barf? :)
Best to stick with the abstraction - it generally structures things so that your changes aren't blown away when you upgrade a package (RPM is a poop package manager). You'll be happier when you learn to work *with* the tools rather than working around them, and YaST is really a nice, handy tool once you decide that it's worth learning (since SuSE's not getting rid of it any time soon).
How dare you not know the American culture's slang? Why, if it's derisive here, then no one anywhere in the world can use it. Nor can they name their dog Wilbur. In the UK, you guys also took our perfectly good derisive term "fag" and applied it to cigarettes. Man, have you people no care for the homosexual community? That whole smoking thing will probably never catch on now...
Just a couple of minor notes...
:)
P2 was a PPro with MMX, which was *not* basicaly a Pentium. Notably, the PPro used a RISC core and could translate CISC, while the Pentium was straight CISC, and you could run 4 PPros - which you could only run up to two Pentiums (or first-gen PIIs, for that matter). The PPro was also optimized for 32-bit apps, while the Pentium actually outperformed on 16-bit apps at the same clock speed. Otherwise, your lineage is simplistically accurate...
Itanium hasn't been a giant success largely because of software screw-ups - it took a while for compilers to properly optimize for the CPU, and programmers failed to think of it as being a different CPU than their P3 or Xeon. Lots of x86 stuff just didn't (some still doesn't) build well for ia64 (Itanium), while it may still work well on the more similar em64t (Xeon). Ia64 is a really cool architecture, it's just not yet fully exploited. http://www.gelato.org/ and http://www.ia64-linux.org/ are good starting points for Linux-oriented information on that arch...
Probably because I stopped changing my refrigerant monthly, and instead fixed the leak. Sorry 'bout that. :)
I guess Ballmer is pretty big & retarded looking, while Gates is fairly small and geeky. I think I'll refer to them collectively as Master Blaster henceforth. They need a big leather outfit now...
Wait, so the Apple machines will be based on several Cyrix processors in parallel? I thought Cyrix went under years ago...
So, I presume that, since we can't do shit to stop it, I can go back to buying R-12 for my old cars again real soon? The evaporator in my Caprice just doesn't work as efficiently with the R-134a conversion, and Freeze-12 isn't as effective. :)
Smart buildings? Someone's built a self-managing home or business out of Legos? I'll be darned.
This'd be a good time for the Homer quote about bacon, ham, and sausage coming from the same, magical animal, wouldn't it? :)
I've been a *nix sysadmin for about a decade, and in that time I have tested several fairly unstable hardware configurations - not to mention the experimenting I do on my home network. The more stuff you mess with the more likely you are to run in to / cause failures, even though failure's still a very low percentage overall. :)
Generally, though, problems are introduced through too many unclean shutdowns (due to lower-level development), or flaky hardware of some sort.
That's somewhat irrelevent, since reiser isn't the filesystem you ideally want to be using for a few really large files. You want XFS for that (or possibly ext3). Reiser's big thing is good journaling, awesome performance and space usage with a bunch of really small files (think maildirs, where each message is a separate file and probably less than a single filesystem block) or "regular" usage. It works with huge files, but that's not really where it shines.
:)
That said, I have no problems with reads during the creation of 4-6GB files on recent revisions of Reiser 3 (BTW, I use Reiser because performance isn't as critical and I'm familiar with the recovery tools - after a crash isn't the time to be learning about how to recover a damaged filesystem). I haven't done any formal benchmarking, but I have done things that do in fact read from files while a big one's being written, and I don't have 6GB RAM so I know it's not being cached.
Personally, I've found Reiser to be the best. I've lost data on ext2 and ext3, as well as jfs (and reiser, once). Overall, I've also lost weeks of time waiting for ext to fsck on an "unscheduled" reboot. :)
;)
Of course, this is moot since none of them will regularly lose files, and anything important is regularly backed up. Not to mention that a single UPS to weather minor power interruptions costs under $100... Right?
Just in case you care about the extent of my vocabulary, I'm well aware of the meaning of "girding" as a sort of protective bolstering. :) None the less, the obscurity of the term combined with the context and similarity to "grinding", etc - well, it struck me as amusing. I think I'd enjoy watching that guy talking to a bunch of pot heads, especially if that's an example of an expression that he uses in normal conversation...
Heh. Monkeys.
"we're girding our loins"? I don't care how excited they are about this potential money maker - that sounds like a means of celebration one would generally keep private.