You pay for a printed copy of your credit history, don't you? You pay for a title search; school transcript...etc.
Don't be [simplistic] lame [/simplistic]...you are not paying to receive something you already own. You are simply paying for the transcript of the analysis of the raw data.
What is going on here is paying to have all this data dycrypted in advance. It won't be long before some business markets forecasting on the bulk data.
In Beijing, you can buy an RTR Korean identity for $1,000.00. In Mexico, you can get a SSN for much less. When virtual identities trade on parody w/actual, I'll switch.
...and it is defined as being able to clearly remember your goal at all times. Paper chasing has it's merits...such as a higher salary than someone who didn't finish the chase.
Without it, you are doomed to a life as a semi-pro.
Pick something and stay with it. (haven't we been around this tree once already this year?)
I'm sorry...north west of Sacto. Located just outside Dunnigan, in Yolo County, north of Woodland, Calif. At that time, it was really in the boonies, but today, I'm sure civilization has closed the gap.
I worked on ones built in Northern Calif. To my knowledge, they were normally placed in the middle of no where, frequently without improved access roads, etc. The locations were generally picked with a bias towards line of site to the next tower, etc. Scenery and bubbling brooks were never on the shopping list. Just the occasional oak tree and rattle snake. But if you're living below the horizon, I guess the view from the kitchen is always uninspiring.
I did concrete and steel inspection. One batch of concrete samples failed about a month after the main ceiling was poured (hot day and the cement trucks were waiting in line)...the result was that the contractor was held responsible, with the 90% completed structure being abandoned. They buried it and moved over a bit and built again. If you can find that site, you can get two-for-one. Look north east of Sacramento....about two hours out.
These were built by ITT, under contract to Uncle Sam, who didn't feel like bothering ground troops with terrestrial communications. The usual method of out-sourcing, only on a very large scale.
The dialtone joke is just that...how can any govt. think it is doing the populace good by keeping the phonelines up when they won't be seeing daylight for a generation or two.
Ok, I'll answer my own Q...they were spending cold war $$ while providing 'make work' for the communications industry. 'money' is the key word in why these were built, not concern for the American way.
I worked on some of these (underground bunker types), as an Inspector (concrete/steel), during the early '70s. I recall at least one had to be abandoned due to several batches of concrete that failed strength testing in the lab. They simply covered it with dirt and moved over several hundred yards to begin again.
They were heavily compartmented, and built much like a bank vault, where you have a box inside a box inside a box. There was at least one central cavity that was meant to be home for worst case attacks.
I worked on some of these (underground bunker types), as an Inspector (concrete/steel), during the early '70s. I recall at least one had to be abandoned due to several batches of concrete that failed strength testing in the lab. They simply covered it with dirt and moved over several hundred yards to begin again.
They were heavily compartmented, and built much like a bank vault, where you have a box inside a box inside a box. There was at least one central cavity that was meant to be home for worst case attacks.
As I recall, this was pre ATT, and they were built for ITT, under a government contract to provide domestic communications if WWW III (as stated) broke out. And yes, there was considerable money invested.
I was an Inspector on these in Northern Calif. I monitored the construction for a private firm. Concrete pours and steel, etc.
They are hell-for-stout, no doubt. You could wipe out everything above ground in the US, and still get a dial tone. Most are in remote locations, naturally, and include fuel storage tanks (propane) and blast shielding. Just the ticket for anyone looking for the ultimate private bomb shelter.
In MS speak, 'apply' and 'submit' are synonymous. No one ever 'applies' to work for MS. You 'submit' to the collective.....remember? This page starts the brainwashing and indoctrination up-front.
Note a mouseover on the submit button does use the word 'apply'. But why-oh-why doesn't someone check these things...oh, wait..this is/. - I mean MS.
Not when you consider that John overlooked some state of this release. He could have waited for the first update and done the world a bigger favor.
Read this from the disc recording developer list...
==============
First things first... let's get down to the nitty gritty. Jaguar marks
the first public release of these APIs, and there are several fairly
big known problems and issues already that we want you to be aware of.
The largest number of issues are in the filesystem generation code.
Known issues in 6C115:
(1) [Content] ISO-9660/Joliet broken - there are problems in the
ISO/Joliet structures written to disc which make files deeper than the
root directory unreadable on Windows 2000 and XP. (Specifically, the
parent directory pointers in the path table are incorrect.) Some
ISO-9660/Joliet implementations can read these discs successfully, but
you should not rely upon them to work everywhere.
(2) [Content] Virtual filesystem hierarchies broken - the APIs to
create and burn virtual hierarchies (DRFile.h, DRFolder.h,
DRContentFile.h, and DRContentFolder.h) do not work. You will get an
error when burning, and in some cases may crash due to a bad pointer
reference inside the filesystem generator.
(3) [Content] HFS+ CDs report a (harmless) "bitmap needs minor repair"
when run through Disk First Aid.
(4) [CoreEngine, DiscRecUI] Certain notifications having to do with the
drive tray state may not be sent. When a disc is ejected via the
keyboard eject button, or when the tray is opened via the front panel
eject button on the drive, you are supposed to get a device status
changed notification, but won't. This is visible in the DiscRecording
UI components as well; we're waiting on a bugfix and an additional
feature from IOKit before this will work.
(5) [Content] Virtual links (symlinks, aliases) are mostly untested and
may not work correctly.
(6) [Content] UDF is not yet available in the first release.
(7) [DiscRecUI] Carbon/C APIs to the UI components are not yet
available in the first release.
That's all I have on my notepad at the moment. The good news is, the
first three have been fixed already and scheduled for release with the
first Jaguar update. I don't have timeframes available for when, other
than "soon". The remainder are being worked on but I don't have
timeframes available for those either.
John's review lacked thoroughness. He missed the fact that this version of OS X has been let out without it's pants being cuffed.
Read this from one of Apple's Developer lists:
First things first... let's get down to the
nitty gritty.
Jaguar marks
the first public release of these APIs, and there are several fairly
big known problems and issues already that we want you to be aware of.
The largest number of issues are in the filesystem generation code.
Known issues in 6C115:
(1) [Content] ISO-9660/Joliet broken - there are problems in the
ISO/Joliet structures written to disc which make files deeper than the
root directory unreadable on Windows 2000 and XP. (Specifically, the
parent directory pointers in the path table are incorrect.) Some
ISO-9660/Joliet implementations can read these discs successfully, but
you should not rely upon them to work everywhere.
(2) [Content] Virtual filesystem hierarchies broken - the APIs to
create and burn virtual hierarchies (DRFile.h, DRFolder.h,
DRContentFile.h, and DRContentFolder.h) do not work. You will get an
error when burning, and in some cases may crash due to a bad pointer
reference inside the filesystem generator.
(3) [Content] HFS+ CDs report a (harmless) "bitmap needs minor repair"
when run through Disk First Aid.
(4) [CoreEngine, DiscRecUI] Certain notifications having to do with the
drive tray state may not be sent. When a disc is ejected via the
keyboard eject button, or when the tray is opened via the front panel
eject button on the drive, you are supposed to get a device status
changed notification, but won't. This is visible in the DiscRecording
UI components as well; we're waiting on a bugfix and an additional
feature from IOKit before this will work.
(5) [Content] Virtual links (symlinks, aliases) are mostly untested and
may not work correctly.
(6) [Content] UDF is not yet available in the first release.
(7) [DiscRecUI] Carbon/C APIs to the UI components are not yet
available in the first release.
That's all I have on my notepad at the moment. The good news is, the
first three have been fixed already and scheduled for release with the
first Jaguar update. I don't have timeframes available for when, other
than "soon". The remainder are being worked on but I don't have
timeframes available for those either.
============
When these and others are fixed, it will be appropriate to review. John may know this, but he wanted to be first to the party, and now many readers will take what he says without knowing the facts.
He ingored the information about how more than one API was broken in 10.2, and thus resulting in things like CD support for Windows being broken as well.
My point is that 10.2 has some rather tender flesh on it's bones, and until 10.2.1 etc. come out, there are many areas that shouldn't be reviewed just yet.
His article is flowery and premature...wait a while and this will be obvious. OS X 10.2 is a teenager with acne. Let it's balls drop before you write about it's ability to get off the porch and run with the BDs.
Sorry, I saw you leave and head back here. You know you are not supposed to do this. I'm removing the information from your message (before you write it) and I hope you don't try to repeat this futile effort again.
The 'story' isn't on/.
It's on the BBC, and if you spend your time wishing and waiting for this or any other news to show up on/., you risk dissapointment.
Slashdot Mirror
Any of the CoolPix, either in the 800 or 900 range (990 or 995 at this time, as an example). Buy the most camera you can afford.
The Canon camera mentioned in the blurb is not digital.
The human eye can only discern 40 lines per inch.
black-----
white
black-----
white
black-----
white
black-----
white
black-----
white
black-----
white
black-----
white
black-----
white
You pay for a printed copy of your credit history, don't you? You pay for a title search; school transcript...etc.
Don't be [simplistic] lame [/simplistic]...you are not paying to receive something you already own. You are simply paying for the transcript of the analysis of the raw data.
What is going on here is paying to have all this data dycrypted in advance. It won't be long before some business markets forecasting on the bulk data.
In Beijing, you can buy an RTR Korean identity for $1,000.00. In Mexico, you can get a SSN for much less. When virtual identities trade on parody w/actual, I'll switch.
Can you say 'sendmail'....check it out via WebMin.
...how much of the overload is product placement?
Same way they handle more cell phone users. More switches and code multiplication.
...and it is defined as being able to clearly remember your goal at all times. Paper chasing has it's merits...such as a higher salary than someone who didn't finish the chase.
Without it, you are doomed to a life as a semi-pro.
Pick something and stay with it. (haven't we been around this tree once already this year?)
I'm sorry...north west of Sacto. Located just outside Dunnigan, in Yolo County, north of Woodland, Calif. At that time, it was really in the boonies, but today, I'm sure civilization has closed the gap.
I worked on ones built in Northern Calif. To my knowledge, they were normally placed in the middle of no where, frequently without improved access roads, etc. The locations were generally picked with a bias towards line of site to the next tower, etc. Scenery and bubbling brooks were never on the shopping list. Just the occasional oak tree and rattle snake. But if you're living below the horizon, I guess the view from the kitchen is always uninspiring.
I did concrete and steel inspection. One batch of concrete samples failed about a month after the main ceiling was poured (hot day and the cement trucks were waiting in line)...the result was that the contractor was held responsible, with the 90% completed structure being abandoned. They buried it and moved over a bit and built again. If you can find that site, you can get two-for-one. Look north east of Sacramento....about two hours out.
These were built by ITT, under contract to Uncle Sam, who didn't feel like bothering ground troops with terrestrial communications. The usual method of out-sourcing, only on a very large scale.
The dialtone joke is just that...how can any govt. think it is doing the populace good by keeping the phonelines up when they won't be seeing daylight for a generation or two.
Ok, I'll answer my own Q...they were spending cold war $$ while providing 'make work' for the communications industry. 'money' is the key word in why these were built, not concern for the American way.
I worked on some of these (underground bunker types), as an Inspector (concrete/steel), during the early '70s. I recall at least one had to be abandoned due to several batches of concrete that failed strength testing in the lab. They simply covered it with dirt and moved over several hundred yards to begin again.
They were heavily compartmented, and built much like a bank vault, where you have a box inside a box inside a box. There was at least one central cavity that was meant to be home for worst case attacks.
I worked on some of these (underground bunker types), as an Inspector (concrete/steel), during the early '70s. I recall at least one had to be abandoned due to several batches of concrete that failed strength testing in the lab. They simply covered it with dirt and moved over several hundred yards to begin again.
They were heavily compartmented, and built much like a bank vault, where you have a box inside a box inside a box. There was at least one central cavity that was meant to be home for worst case attacks.
As I recall, this was pre ATT, and they were built for ITT, under a government contract to provide domestic communications if WWW III (as stated) broke out. And yes, there was considerable money invested.
I was an Inspector on these in Northern Calif. I monitored the construction for a private firm. Concrete pours and steel, etc.
They are hell-for-stout, no doubt. You could wipe out everything above ground in the US, and still get a dial tone. Most are in remote locations, naturally, and include fuel storage tanks (propane) and blast shielding. Just the ticket for anyone looking for the ultimate private bomb shelter.
In MS speak, 'apply' and 'submit' are synonymous. No one ever 'applies' to work for MS. You 'submit' to the collective.....remember? This page starts the brainwashing and indoctrination up-front.
/. - I mean MS.
Note a mouseover on the submit button does use the word 'apply'. But why-oh-why doesn't someone check these things...oh, wait..this is
NASA has been underdelivering for decades and now someone wants to throw another bandaid on the wound?
Why are we talking about cysts and lesions when the carcass has no head, legs or arms?
Not when you consider that John overlooked some state of this release. He could have waited for the first update and done the world a bigger favor.
... let's get down to the nitty gritty. Jaguar marks
the first public release of these APIs, and there are several fairly
big known problems and issues already that we want you to be aware of.
The largest number of issues are in the filesystem generation code.
Read this from the disc recording developer list...
==============
First things first
Known issues in 6C115:
(1) [Content] ISO-9660/Joliet broken - there are problems in the ISO/Joliet structures written to disc which make files deeper than the root directory unreadable on Windows 2000 and XP. (Specifically, the parent directory pointers in the path table are incorrect.) Some ISO-9660/Joliet implementations can read these discs successfully, but you should not rely upon them to work everywhere.
(2) [Content] Virtual filesystem hierarchies broken - the APIs to create and burn virtual hierarchies (DRFile.h, DRFolder.h, DRContentFile.h, and DRContentFolder.h) do not work. You will get an error when burning, and in some cases may crash due to a bad pointer reference inside the filesystem generator.
(3) [Content] HFS+ CDs report a (harmless) "bitmap needs minor repair" when run through Disk First Aid.
(4) [CoreEngine, DiscRecUI] Certain notifications having to do with the drive tray state may not be sent. When a disc is ejected via the keyboard eject button, or when the tray is opened via the front panel eject button on the drive, you are supposed to get a device status changed notification, but won't. This is visible in the DiscRecording UI components as well; we're waiting on a bugfix and an additional feature from IOKit before this will work.
(5) [Content] Virtual links (symlinks, aliases) are mostly untested and may not work correctly. (6) [Content] UDF is not yet available in the first release.
(7) [DiscRecUI] Carbon/C APIs to the UI components are not yet available in the first release.
That's all I have on my notepad at the moment. The good news is, the first three have been fixed already and scheduled for release with the first Jaguar update. I don't have timeframes available for when, other than "soon". The remainder are being worked on but I don't have timeframes available for those either.
John's review lacked thoroughness. He missed the fact that this version of OS X has been let out without it's pants being cuffed. Read this from one of Apple's Developer lists:
... let's get down to the
nitty gritty.
Jaguar marks
the first public release of these APIs, and there are several fairly
big known problems and issues already that we want you to be aware of.
The largest number of issues are in the filesystem generation code.
First things first
Known issues in 6C115:
(1) [Content] ISO-9660/Joliet broken - there are problems in the ISO/Joliet structures written to disc which make files deeper than the root directory unreadable on Windows 2000 and XP. (Specifically, the parent directory pointers in the path table are incorrect.) Some ISO-9660/Joliet implementations can read these discs successfully, but you should not rely upon them to work everywhere.
(2) [Content] Virtual filesystem hierarchies broken - the APIs to create and burn virtual hierarchies (DRFile.h, DRFolder.h, DRContentFile.h, and DRContentFolder.h) do not work. You will get an error when burning, and in some cases may crash due to a bad pointer reference inside the filesystem generator.
(3) [Content] HFS+ CDs report a (harmless) "bitmap needs minor repair" when run through Disk First Aid.
(4) [CoreEngine, DiscRecUI] Certain notifications having to do with the drive tray state may not be sent. When a disc is ejected via the keyboard eject button, or when the tray is opened via the front panel eject button on the drive, you are supposed to get a device status changed notification, but won't. This is visible in the DiscRecording UI components as well; we're waiting on a bugfix and an additional feature from IOKit before this will work.
(5) [Content] Virtual links (symlinks, aliases) are mostly untested and may not work correctly.
(6) [Content] UDF is not yet available in the first release.
(7) [DiscRecUI] Carbon/C APIs to the UI components are not yet available in the first release.
That's all I have on my notepad at the moment. The good news is, the first three have been fixed already and scheduled for release with the first Jaguar update. I don't have timeframes available for when, other than "soon". The remainder are being worked on but I don't have timeframes available for those either.
============
When these and others are fixed, it will be appropriate to review. John may know this, but he wanted to be first to the party, and now many readers will take what he says without knowing the facts.
He ingored the information about how more than one API was broken in 10.2, and thus resulting in things like CD support for Windows being broken as well.
My point is that 10.2 has some rather tender flesh on it's bones, and until 10.2.1 etc. come out, there are many areas that shouldn't be reviewed just yet.
His article is flowery and premature...wait a while and this will be obvious. OS X 10.2 is a teenager with acne. Let it's balls drop before you write about it's ability to get off the porch and run with the BDs.
...and it's been tug'in at satelliti for years now.
This 'news' is so yesterday.
I can't wait until another article about self-tying shoe laces hits the airwaves.
Sorry, I saw you leave and head back here. You know you are not supposed to do this. I'm removing the information from your message (before you write it) and I hope you don't try to repeat this futile effort again.
Let's see....I have at least six out of ten and I was just tested and I don't have diabetes.
What does that mean?
The 'story' isn't on /.
/., you risk dissapointment.
It's on the BBC, and if you spend your time wishing and waiting for this or any other news to show up on
...right, and the check is in the mail. How's it feel being duped?