I installed FC2 test1 and it worked for the most part... Obviously being a beta, there were bugs with some applications, but overall it was quite stable. However, I didn't keep my system bleeding-edge (up2date every day), one of my friends did though. I remember he encountered a bug with a new package that prevented him from logging in as anyone but root... lol. Can't recall the reason but it was fixed not too long later.
Overall I've been pretty happy considering its a test release. I'm even running XFS on most of my filesystems, using several USB devices, and pretty much everything is stable.
My friend's (same one) problems were limited to getting Totem working... I think there was a period it would hardlock the machine and it might have happened once or twice to me as well, but not too much.
Good job guys, keep up the good work. I can't wait to see FC2 final.
It has to do with the inperfections and variations in the original silicon wafer. Small deviations can effect the maximum speed the chip can run at while maintaining stability. You are right though, the process to create each chip (at least in each batch) is identical, however. I'm sure Intel has some whitepapers on the subject but slightly too busy at work to Google for them now. Hope this helps.
...like two smitten children fumbling and tumbling over themselves.
I think they're like two monkeys banging away on a keyboard instead... Hey maybe they'll create the next Longhorn source by the time the courts settle.
The connection between $DEVICE and $DISPLAY will be an encrypted HDCP/HDMA connection
True, encryption would pose a more difficult challenge. I still think it would only be a matter of time until a workaround::checking for DMCA's prying eyes:: is discovered/created.
The question is which "some poor evil empire" is going to get hit next. I think our favorite software company in Redmond is a likely next target (can't say I have any sympathy with the recent story)
At least the technology demonstrated by AudibleMagic could have a good use (and no, I don't mean in P2P software, in fact count that whole idea out in this rant). It could be used as the next CDDB technology... Think of it:
Online databases of psycho-acoustical information on enormous amounts of music could be created (depending upon the amount of data needed to uniquely identify a particular song/piece). New software could be written to poll the database from your MP3 collection and automatically fill in the ID3 tags... It could have many powerful uses.
However, as I'm sure most would agree, it could also have many negative side effects, the big one being previously mentioned.
I am in the market for a new car. I'll be buying a honda. They dont break. Sure - you'll find a couple of horror stories about some broken Hondas - but nothing like the number with other makes.
Ditto. My 95 Accord with 200k+ mi runs amazing. My friend's 94 with 250k+ mi still runs well. They might break if you don't take care of them but with proper maintaince they are easily mistaken for a good Linux box....(good uptimes):)
I'd like to get an S2000 to replace it, but also looking for a 3-series or an STI, also good cars.
Even so, I still wouldn't buy one with a sealed hood - I enjoy working on it myself.
This is very good news for me as my wipeouts are usually at a pretty high velocity too... I find it somewhat surprizing that it survived in one piece and yet still working months later.
Sounds like Apple has done a good job designing the iPod, although the recent article on the dissection/"murder" of one made it pretty clear there isn't too much inside.
I probably got lucky because it wasn't accessing the hard drive when it hit.
I wonder though... I highly doubt Apple has designed the iPod to spin up the drive, buffer large amounts of data, then spin it back down. That would be the only possible way I could see it designed to allow for "non-harddrive" (as in not spinning) operational periods during use. (It'd also dramatically increase random-access times). Obviously that design strategy is very inefficient so I don't think it's likely. IMHO, the probable design they followed is to just constantly spin the drive and stream small amounts of data off at a time, in which case the drive would always been operating while in use, and in turn means there wouldnt really be any "safe" times for it to experience excess vibration/shock... Although I suppose they could always park the heads to a safe location while not reading from the disk (which is a possibility), but that would reduce battery life with excess head movement. Anyone else like to comment on these ideas?
I'm not sure about everyone else, but I find it very surprizing that it can handle such shock. Anyone have Apple's specs on the maximum operational G-force?
Cold does affect the ipod's battery life (much like most batteries you'll encounter).
Agreed. Low temperatures always seem to drain the the charge out of a battery, I have the same problem with my cell when I take it boarding. Wondering if I could figure out a way to keep it warmer, maybe an inside pocket will help... Could always throw one of those glove warmers in the pocket additionally.
Anyone know the cause of this cold-temperature battery problem? Lower internal resistance perhaps? I knew hot temperatures were bad for batteries as well, the cold doesn't make too much sense to me. Most (almost all to my knowledge) electronics operate better in colder temperatures, but then again a battery is more of an electro-chemical reaction.
Excellent... This is all very good news. I'd like to thank each of you for your comments, they have proven to be most useful. Money permitting I will hopefully be able to purchase one soon.
Several of my friends have them and say nothing but excellent things, I'm sure I will agree.
That is definately a high-ranking geek item. Can't say I've ever heard of it before, looks like they've done a good job of it.
Now only if I could hook up a Transwarp conduit for an Internet connection....::starts design plans::
Somewhat related question
on
iPod Mini Autopsy
·
· Score: 4, Interesting
Please don't mod this offtopic, as it is a relevant question...
For those iPod owners out there: What has been your experience with the device as far as strength/stability goes? As in... Does a drop off a table crash the heads? I am looking into purchasing one possibly, but my main use will be for snowboarding and if it's not gonna be able to take some abuse (obviously it will be in my jacket but still subject to vibration and the occassional wipeouts), I would rather go with a solid-state one. Any feedback would be most useful.
It's not that a new chip is needed, it's just a matter that it's easier (and probably more accurate) to do it in hardware.
Oh yes, I'm aware of that... the problem is (at least in OS design) if you have to use software emulation for memory access, it's pointless. Memory management is a time-critical portion of modern OS design and it couldn't allow taking a performance hit from that.
I wasn't aware OpenBSD utilized segmentation, perhaps a look at the source could help some.
Ahh yes, this sounds familiar... In protected mode on the x86 (with segmentation enabled), far memory pointers are 48-bit, are they not? 16-bit segment selector + 32-bit memory offset into 4gb virtual address space. That is something of a problem, not being able to fit a far pointer into a general register (kinda makes indirect memory references via pointer hard, don't it?).
However, the new 64-bit architecture as proposed by AMD (I don't have Intel's specs) seem to suggest this might not be a problem anymore. The AMD64 Architecture Programmer's Manual Volume 2: System Programming has lots of information and I must admit it's a lot to read, but from what I gather would this not be an issue anymore? 32-bit memory offset (upto 4gb virtual address space) + 16-bit segment selector can easily fit within a 64-bit register, however I'm not sure if the CPU is designed to handle such things. From the Application Programming Documentation (at http://www.amd.com/us-en/Processors/DevelopWithAMD/0,,30_2252_875_7044,00.html) , AMD claims that "In 64-bit mode, the AM64 architecture supports only the flat-memory model in which there is only one data segment, so the effective address is used as the virtual (linear) address and far pointers are not needed." (page 23).
So maybe I have indeed answered my own question... segmentation as it was designed for will not easily be utilized... If so, would anyone with any sort of CPU architecture design/experience possibly give any reasons for this? Would it just be too difficult to modify the instruction sets and architecture to easily accomodate full segmentation support?
Call me stupid, but AFAIK x86 chips have full segmentation support (in protected mode obviously) - ability to define different segment types (read only, r/w, execute only, etc)... For those of you not familiar with it, it allows the programmer to define different types of memory segments, which would allow you to do some pretty interesting things such as defining read-only code segments (so the machine instructions can't be modified in memory), and non-executing data segments (to prevent OS from trying to run code stored in program data/buffers). This would solve the problem, at least how they addressed it in the article.
If current operating systems actually used this in addition to paging (which is what most of them only use now), why would they need to create a new chip? Linux does not fully utilize segmention, mostly only paging. I don't have any resources on MS OS design right now so I can't comment on it... (although maybe looking at the recent source would help some;)
Slashdot Mirror
Nurses ask: "What's that blue aura coming from the OR??"
Yeah, let's hope the wonderful Doctors don't get Quake flashbasks and end up gibbing their patient instead of performing surgery.
Next thing you know, they'll walk into the OR and mutter under their breath, "It's time to kick ass and chew bubble-gum..."
I installed FC2 test1 and it worked for the most part... Obviously being a beta, there were bugs with some applications, but overall it was quite stable. However, I didn't keep my system bleeding-edge (up2date every day), one of my friends did though. I remember he encountered a bug with a new package that prevented him from logging in as anyone but root... lol. Can't recall the reason but it was fixed not too long later. Overall I've been pretty happy considering its a test release. I'm even running XFS on most of my filesystems, using several USB devices, and pretty much everything is stable. My friend's (same one) problems were limited to getting Totem working... I think there was a period it would hardlock the machine and it might have happened once or twice to me as well, but not too much. Good job guys, keep up the good work. I can't wait to see FC2 final.
Well this is somewhat related to the second, but I bet his Nigerian friend helped him bring in a few extra thousand a month.
It has to do with the inperfections and variations in the original silicon wafer. Small deviations can effect the maximum speed the chip can run at while maintaining stability. You are right though, the process to create each chip (at least in each batch) is identical, however. I'm sure Intel has some whitepapers on the subject but slightly too busy at work to Google for them now. Hope this helps.
Can't sleep, pengiuns will eat me...
... :)
Can't sleep, pengiuns will eat me...
Can't sleep, pengiuns will eat me...
...like two smitten children fumbling and tumbling over themselves.
I think they're like two monkeys banging away on a keyboard instead... Hey maybe they'll create the next Longhorn source by the time the courts settle.
The connection between $DEVICE and $DISPLAY will be an encrypted HDCP/HDMA connection
::checking for DMCA's prying eyes:: is discovered/created.
True, encryption would pose a more difficult challenge. I still think it would only be a matter of time until a workaround
In Soviet Russia, your television set will control the Motion Picture Association of America!
:)
How can we get that technology over here??
Someone will create a new "blackbox" not to dissimilar from a cable-descrambler nowadays to change the bit. Bingo, flag off, problem solved. :)
The question is which "some poor evil empire" is going to get hit next. I think our favorite software company in Redmond is a likely next target (can't say I have any sympathy with the recent story)
At least the technology demonstrated by AudibleMagic could have a good use (and no, I don't mean in P2P software, in fact count that whole idea out in this rant). It could be used as the next CDDB technology... Think of it:
Online databases of psycho-acoustical information on enormous amounts of music could be created (depending upon the amount of data needed to uniquely identify a particular song/piece). New software could be written to poll the database from your MP3 collection and automatically fill in the ID3 tags... It could have many powerful uses.
However, as I'm sure most would agree, it could also have many negative side effects, the big one being previously mentioned.
I am in the market for a new car. I'll be buying a honda. They dont break. Sure - you'll find a couple of horror stories about some broken Hondas - but nothing like the number with other makes.
:)
Ditto. My 95 Accord with 200k+ mi runs amazing. My friend's 94 with 250k+ mi still runs well. They might break if you don't take care of them but with proper maintaince they are easily mistaken for a good Linux box....(good uptimes)
I'd like to get an S2000 to replace it, but also looking for a 3-series or an STI, also good cars.
Even so, I still wouldn't buy one with a sealed hood - I enjoy working on it myself.
..how long it's gonna be till Microsoft gets DOS'd/hacked now. They just pissed off a lot of people [even more than before], myself included.
Yeess, Darl. When you wave your hands like that I realize these are not the droids I'm looking for.
::with recent headline news and slight wave of hand:: Yeeesss, Microsoft is not the software you are looking for.
I'm an idiot... I hyperlinked to the same damn article. Please forgive my stupidity.... Should pay a little more attention next time. :)
This is very good news for me as my wipeouts are usually at a pretty high velocity too... I find it somewhat surprizing that it survived in one piece and yet still working months later.
Sounds like Apple has done a good job designing the iPod, although the recent article on the dissection/"murder" of one made it pretty clear there isn't too much inside.
I probably got lucky because it wasn't accessing the hard drive when it hit.
I wonder though... I highly doubt Apple has designed the iPod to spin up the drive, buffer large amounts of data, then spin it back down. That would be the only possible way I could see it designed to allow for "non-harddrive" (as in not spinning) operational periods during use. (It'd also dramatically increase random-access times). Obviously that design strategy is very inefficient so I don't think it's likely. IMHO, the probable design they followed is to just constantly spin the drive and stream small amounts of data off at a time, in which case the drive would always been operating while in use, and in turn means there wouldnt really be any "safe" times for it to experience excess vibration/shock... Although I suppose they could always park the heads to a safe location while not reading from the disk (which is a possibility), but that would reduce battery life with excess head movement. Anyone else like to comment on these ideas?
I'm not sure about everyone else, but I find it very surprizing that it can handle such shock. Anyone have Apple's specs on the maximum operational G-force?
Cold does affect the ipod's battery life (much like most batteries you'll encounter).
Agreed. Low temperatures always seem to drain the the charge out of a battery, I have the same problem with my cell when I take it boarding. Wondering if I could figure out a way to keep it warmer, maybe an inside pocket will help... Could always throw one of those glove warmers in the pocket additionally.
Anyone know the cause of this cold-temperature battery problem? Lower internal resistance perhaps? I knew hot temperatures were bad for batteries as well, the cold doesn't make too much sense to me. Most (almost all to my knowledge) electronics operate better in colder temperatures, but then again a battery is more of an electro-chemical reaction.
Excellent... This is all very good news. I'd like to thank each of you for your comments, they have proven to be most useful. Money permitting I will hopefully be able to purchase one soon.
Several of my friends have them and say nothing but excellent things, I'm sure I will agree.
That is definately a high-ranking geek item. Can't say I've ever heard of it before, looks like they've done a good job of it.
::starts design plans::
Now only if I could hook up a Transwarp conduit for an Internet connection....
Please don't mod this offtopic, as it is a relevant question...
For those iPod owners out there: What has been your experience with the device as far as strength/stability goes? As in... Does a drop off a table crash the heads? I am looking into purchasing one possibly, but my main use will be for snowboarding and if it's not gonna be able to take some abuse (obviously it will be in my jacket but still subject to vibration and the occassional wipeouts), I would rather go with a solid-state one. Any feedback would be most useful.
It was meant as more of a tongue-in-cheek comment... although UNIX was around a lot longer than MS. The 'good'ness is debatable obviously...
Actually I think it'd be more accurate similar to this:
:)
In the beginning there was UNIX. And it was good. And then Windows came along. And then all hell broke loose... ad infinitum, you get the idea.
It's not that a new chip is needed, it's just a matter that it's easier (and probably more accurate) to do it in hardware.
Oh yes, I'm aware of that... the problem is (at least in OS design) if you have to use software emulation for memory access, it's pointless. Memory management is a time-critical portion of modern OS design and it couldn't allow taking a performance hit from that.
I wasn't aware OpenBSD utilized segmentation, perhaps a look at the source could help some.
Ahh yes, this sounds familiar... In protected mode on the x86 (with segmentation enabled), far memory pointers are 48-bit, are they not? 16-bit segment selector + 32-bit memory offset into 4gb virtual address space. That is something of a problem, not being able to fit a far pointer into a general register (kinda makes indirect memory references via pointer hard, don't it?).
D /0,,30_2252_875_7044,00.html) , AMD claims that "In 64-bit mode, the AM64 architecture supports only the flat-memory model in which there is only one data segment, so the effective address is used as the virtual (linear) address and far pointers are not needed." (page 23).
However, the new 64-bit architecture as proposed by AMD (I don't have Intel's specs) seem to suggest this might not be a problem anymore. The AMD64 Architecture Programmer's Manual Volume 2: System Programming has lots of information and I must admit it's a lot to read, but from what I gather would this not be an issue anymore? 32-bit memory offset (upto 4gb virtual address space) + 16-bit segment selector can easily fit within a 64-bit register, however I'm not sure if the CPU is designed to handle such things. From the Application Programming Documentation (at http://www.amd.com/us-en/Processors/DevelopWithAM
So maybe I have indeed answered my own question... segmentation as it was designed for will not easily be utilized... If so, would anyone with any sort of CPU architecture design/experience possibly give any reasons for this? Would it just be too difficult to modify the instruction sets and architecture to easily accomodate full segmentation support?
Call me stupid, but AFAIK x86 chips have full segmentation support (in protected mode obviously) - ability to define different segment types (read only, r/w, execute only, etc)... For those of you not familiar with it, it allows the programmer to define different types of memory segments, which would allow you to do some pretty interesting things such as defining read-only code segments (so the machine instructions can't be modified in memory), and non-executing data segments (to prevent OS from trying to run code stored in program data/buffers). This would solve the problem, at least how they addressed it in the article.
;)
If current operating systems actually used this in addition to paging (which is what most of them only use now), why would they need to create a new chip? Linux does not fully utilize segmention, mostly only paging. I don't have any resources on MS OS design right now so I can't comment on it... (although maybe looking at the recent source would help some