It's a fact that SPDIF doesn't use ACKs/ retransmits, yes. But that's not even relevant in this case. Clock recovery / regeneration never had anything to do with that.
While -1, Troll is not the correct mod for an insubstantial argument, at this stage the GP is quite deserving of the downmods. I'm surprised more of his posts aren't -1, Funny.
Yo. I don't know if you actually believe all this utter nonsense you're spouting, of it you're just trying to see what you can get away with, but nonetheless:
Thanks. You've caused a lot of knowledgeable people to stand up and correct your unending bullshit. From those people I've learned a thing or two that I didn't know before, and that wouldn't have happened if you hadn't been here today.
Again, whether you actually believe your bullshit, or you're just doing this for fun, cheers.
If I had a nickel for every time I deliberately pressed control-alt-backspace after begrudgingly accepting that thanks to Beryl/Compiz/Whoever the buck gets passed to these days crashing, I've lost all my unsaved state AGAIN.
Re:HTML5 for the win? Sorry, that's not a codec.
on
YouTube Revamp Imminent?
·
· Score: 2, Informative
Been using Linux since '95, and plaing MP3s on it since '99. Basically well before Ubuntu has been along. Slackware -> RedHat -> Mandrake -> Debian -> Gentoo and finally to MacOS 10.5
No, it's never been particularly awkward getting.mp3 files to play. Much as plenty of other things about running on Linux have bugged me, absolutely no problems in decoding every single codec of audio, even the more obscure.mpc, for free.
It came from the common way of representing decimals in Electrical Engineering - BCD
Numbers were often driven directly to 7-segment displays, or set by groups of dials, each with its own decimal place. It avoid a lot of complication to use nibbles with a BCD code, particularly if only used for a counter an no arithmetic as such. Accordingly, the two CPUs I'm most familiar with: Z80 and m68k - both have instructions for adding and subtracting BCD values - often these would have been written directly to hardware registers.
In the case of every arcade game I have reverse engineered, the player's score and all the high scores (among many other things) have without exception been stored as BCD. This is because each digit will later be used as a lookup value to some graphic tile-map, and it's awfully convenient to just be able to add some particular offset value to each nibble, and then copy the entire string directly to display RAM.
Given that every time a number is presented to you on a computer BCD will need to be used in some form or another, I don't agree that is 'smells of obsolescence'. Binary numbers being converted to decimal representations are the only reason we can read numbers of computers reliably.
I had pasted some code, but ran into post filter errors. Good thing those filters stop all the trolls, eh?
Laughter
One should not be ashamed of laughing over the misfortune of others. Humor is perceived by human brains alone, which sets us apart from all other beings. Jokes always involve the unexpected clash between reality and expectation
Give him a break - the conversation was already nerdy and pedantic, he's only engaging in debate.
Save the "must be fun at parties" line for people who over-analyse jokes or provide pointless quibbles. If you thought his post was too nitpicky or boring, you might be in the wrong place.
That's the first time I've ever heard this, but I'll believe it. Nothing, I repeat nothing, will ever surprise me about the evolution of x86 any more.
If you were to tell me that Little Endianness was simply the result of someone putting something on an overhead projector the wrong way, I'd believe you (because it seems like an extremely fucking stupid idea otherwise: "2 ^ 16 equals five-hundred-thirty-six, sixty-five thousand"
If you were to tell me that the Pentium was really 64-bit, but the fabricators never hooked up the address pins because they never got the memo, I'd believe you.
No doubt, x86 is the cheapest, fastest and most prevalent CPU in computers today, and probably always will be, but fuck me if it doesn't look like the biggest kluge in the world.
One thing that needs even more explanation is when you (in XP) bring up properties for a Folder.
You also get two numbers, the size of all the files, and the size on disk. Oh wait! It keeps changing! It keeps changing as it sums up the entire contents of the folder. How am I really supposed to know when it's finished?
I'm just saying, from a security perspective it's really no different than simply handing over the root password. Parent said "can't mess with stuff the rest of the time", I said 'don't be so sure'.
What phrase? Might help if you explain what you are on about.
The parent to his post had two sentences, only one of which could be regarded as being a "phrase". Furthermore, his post was among the more concise and coherent here, so I really don't see how you missed it. Only quoting you because I think I have to.
If you were a native English speaker, you'd have picked up that I'm not interested in whether people think a certain word is valid or not. There would be dozens of words and idioms that always cause so much pointless debate here (see below). While I understand what they mean, and never pull anyone up for using them, I would also never use them myself, just to avoid what's happened here: Almost the entire first page of comments are completely pointless to anyone wanting to read about filesystems
The handling of drives, etc. is not done with/dev/raw1394 so the mounting of Firewire drives on Linux really is no different to USB. Firwire itself is a lot more versatile than USB and consequently needs a more complex security model. On the (admittedly small) fraction of Linux machines with potentially hostile people running programs, this security most certainly is necessary.
That's life on a Unix-like system I'm afraid. Ideally, distributions would have lovely baselayouts that would take care of everything like that for you. As you'll no doubt learn, while life on Linux is indeed free and diverse, it's far from ideal, and you end up patching up things like that yourself because at the end of the day probably 1% of linux users plug DV-cameras in. Of those, 50% will give up trying to edit video on linux within the hour anyway;)
Ignore this thread. Once you get past all the first post trolls, the rest of it mainly contains bickering over whether "irregardless" is a word or not. Slashdot at its finest, I know. So I'm jumping in at the top of the thread to warn you and save you the time.
As for which filesystem to use: It's a shitfight at the end of the day. OSS-NTFS is reverse engineered so you can never trust that it really is complete, nor that Microsoft will never bend/break it in the future. FAT32 sucks but is unquestionably the lowest common denominator. I like to use Ext2 for getting big files from Linux to Windows (I transfer a lot of DV files), but you have to install something on the Windows/Mac/etc. to use that. HFSplus support on Linux is fine, you just need to disable the journal on the Mac first.
Like I said, it's a shitfight. Learn the pros and cons of the main filesystems: NTFS, Ext-2/3 family, HFS, FAT32. Break them out as each situation merits. But with regard to NTFS and the specs changing: Microsoft have done it before and they'll do it again, just ask Norton Utilities. While my Windows PC is a very important part of my operation (I edit all my video on it), I don't use Windows for enough other things to justify using NTFS unless I'm forced to.
Slashdot Mirror
Crowbars and fuses are sooo 20th century.
1mm twist = much more copper to travel over. 2m twist = almost completely untwisted.
While -1, Troll is not the correct mod for an insubstantial argument, at this stage the GP is quite deserving of the downmods. I'm surprised more of his posts aren't -1, Funny.
Y'know how I said earlier that I wasn't sure whether you're trolling or dead-pan? Yeah, I take that back now.
Thanks. You've caused a lot of knowledgeable people to stand up and correct your unending bullshit. From those people I've learned a thing or two that I didn't know before, and that wouldn't have happened if you hadn't been here today.
Again, whether you actually believe your bullshit, or you're just doing this for fun, cheers.
Understandable - the keys are right next to each other.
If I had a nickel for every time I deliberately pressed control-alt-backspace after begrudgingly accepting that thanks to Beryl/Compiz/Whoever the buck gets passed to these days crashing, I've lost all my unsaved state AGAIN.
No, it's never been particularly awkward getting .mp3 files to play. Much as plenty of other things about running on Linux have bugged me, absolutely no problems in decoding every single codec of audio, even the more obscure .mpc, for free.
Awesome. Too help keep me safe from apps written by random strangers, I can flash my firmware with code from random strangers!
Um, which people will notice?
I'm still converting it from scientific notation.
Linux drivers don't need no stinkin' excuse to be delayed / absent.
Numbers were often driven directly to 7-segment displays, or set by groups of dials, each with its own decimal place. It avoid a lot of complication to use nibbles with a BCD code, particularly if only used for a counter an no arithmetic as such. Accordingly, the two CPUs I'm most familiar with: Z80 and m68k - both have instructions for adding and subtracting BCD values - often these would have been written directly to hardware registers.
In the case of every arcade game I have reverse engineered, the player's score and all the high scores (among many other things) have without exception been stored as BCD. This is because each digit will later be used as a lookup value to some graphic tile-map, and it's awfully convenient to just be able to add some particular offset value to each nibble, and then copy the entire string directly to display RAM.
Given that every time a number is presented to you on a computer BCD will need to be used in some form or another, I don't agree that is 'smells of obsolescence'. Binary numbers being converted to decimal representations are the only reason we can read numbers of computers reliably.
I had pasted some code, but ran into post filter errors. Good thing those filters stop all the trolls, eh?
Save the "must be fun at parties" line for people who over-analyse jokes or provide pointless quibbles. If you thought his post was too nitpicky or boring, you might be in the wrong place.
If you were to tell me that Little Endianness was simply the result of someone putting something on an overhead projector the wrong way, I'd believe you (because it seems like an extremely fucking stupid idea otherwise: "2 ^ 16 equals five-hundred-thirty-six, sixty-five thousand"
If you were to tell me that the Pentium was really 64-bit, but the fabricators never hooked up the address pins because they never got the memo, I'd believe you.
No doubt, x86 is the cheapest, fastest and most prevalent CPU in computers today, and probably always will be, but fuck me if it doesn't look like the biggest kluge in the world.
One thing that needs even more explanation is when you (in XP) bring up properties for a Folder.
You also get two numbers, the size of all the files, and the size on disk. Oh wait! It keeps changing! It keeps changing as it sums up the entire contents of the folder. How am I really supposed to know when it's finished?
What a worthwhile argument to be having!
I'm just saying, from a security perspective it's really no different than simply handing over the root password. Parent said "can't mess with stuff the rest of the time", I said 'don't be so sure'.
The parent to his post had two sentences, only one of which could be regarded as being a "phrase". Furthermore, his post was among the more concise and coherent here, so I really don't see how you missed it. Only quoting you because I think I have to.
If they wanted to retain access after you've changed the password, they could have easy enough.
If you were a native English speaker, you'd have picked up that I'm not interested in whether people think a certain word is valid or not. There would be dozens of words and idioms that always cause so much pointless debate here (see below).
While I understand what they mean, and never pull anyone up for using them, I would also never use them myself, just to avoid what's happened here: Almost the entire first page of comments are completely pointless to anyone wanting to read about filesystems
That's life on a Unix-like system I'm afraid. Ideally, distributions would have lovely baselayouts that would take care of everything like that for you. As you'll no doubt learn, while life on Linux is indeed free and diverse, it's far from ideal, and you end up patching up things like that yourself because at the end of the day probably 1% of linux users plug DV-cameras in. Of those, 50% will give up trying to edit video on linux within the hour anyway ;)
Ignore this thread. Once you get past all the first post trolls, the rest of it mainly contains bickering over whether "irregardless" is a word or not. Slashdot at its finest, I know. So I'm jumping in at the top of the thread to warn you and save you the time.
As for which filesystem to use: It's a shitfight at the end of the day. OSS-NTFS is reverse engineered so you can never trust that it really is complete, nor that Microsoft will never bend/break it in the future. FAT32 sucks but is unquestionably the lowest common denominator. I like to use Ext2 for getting big files from Linux to Windows (I transfer a lot of DV files), but you have to install something on the Windows/Mac/etc. to use that. HFSplus support on Linux is fine, you just need to disable the journal on the Mac first.
Like I said, it's a shitfight. Learn the pros and cons of the main filesystems: NTFS, Ext-2/3 family, HFS, FAT32. Break them out as each situation merits. But with regard to NTFS and the specs changing: Microsoft have done it before and they'll do it again, just ask Norton Utilities. While my Windows PC is a very important part of my operation (I edit all my video on it), I don't use Windows for enough other things to justify using NTFS unless I'm forced to.
Whoosh!