One bit of advice: if you have any interest, sign up now for a network feed in a different timezone. Here's why.
If you don't have your local TV via dish, you can get access to a package of either NY or LA network stations. Once your local TV is available, you can't sign up anymore, but your existing package is grandfathered. This gives you twice as many chances to view/tape a network program, which can be handy at times.
My city didn't have a UPN affiliate, so I qualified for a package with 3 WB and 2 UPN stations. The WB's are in NY, Denver and LA while the UPNs are in Boston and NY (both EST, which is a bummer), so my one-receiver DVR could, for instance, record Enterprise and Jake 2.0 from Boston, then get Angel from Denver, and then Smallville from LA. This makes all members of my family happy. OTOH, if '24' conflicts with something on ABC, CBS, or NBC, I'm screwed.
So, if you have a DVR and can justify an extra $5 or $10 a month, get those packages now while you can, and keep them once you can get your local TV. I predict that you'll be glad you did.
I don't know why someone modded this as funny. My in-laws live on a farm in Arkansas and I installed DishNetwork for them about five or six years ago. Last summer, they said that reception was getting iffy. I stepped outside and noticed that since getting rid of their chickens (stop laughing, it's true!), they'd let some trees grow along a fence row. I got their chainsaw out and within a few minutes their signal strength had moved from 80 to 112.
# Title: A -- Defense Sciences Research and Technology
# Special Focus Area: Time Reversal Methods
# Announcement#: BAA03-02, Addendum 3
# FedBizOpps Reference: February 4, 2003
Why not have the smallest addressable unit be a 16-bit value, instead of the now-standard 8 bits? This would remove the need to distinguish between chars and wchars, with "bytes" able to hold Unicode. Then, shorts would be two "bytes", or 32 bits, ints would be four "bytes", or 64 bits, and longs could even be 128 bits, without any issues.
Here are the patents' abstracts. They all relate to long filename support, so if you were willing to limit yourself to 8.3 names, you don't need a license. This is easly done with dedicated devices, since you just implement your own index file on top of the 8.3 names; this was a common technique back in the old FAT16 days.
An operating system provides a common name space for both long filenames and short filenames. In this common namespace, a long filename and a short filename are provided for each file. Each file has a short filename directory entry and may have at least one long filename directory entry associated with it. The number of long filename directory entries that are associated with a file depends on the number of characters in the long filename of the file. The long filename directory entries are configured to minimize compatibility problems with existing installed program bases.
U.S. Patent #5,745,902
Method and system for accessing a file using file names having different file name formats
A multiple file name referencing system stores multiple file names in a file. These multiple file names include an operating system formatted file name and an application formatted file name. When an operating system formatted file name is created or renamed, the multiple file name referencing system automatically generates an application formatted file name having a potentially different format from, but preserving the extension of, the operating system formatted name. The multiple file name referencing system similarly generates an operating system formatted name upon creation or renaming of an application formatted name. A B-tree is provided which contains an operating system entry for the operating system formatted name and an application entry for the application formatted name, each entry containing the address of the same file to which both names refer. The multiple file name referencing system converts the operating system formatted file name to the application formatted file name by accessing the B-tree with reference to the operating system entry, and vice versa. As a result, either file name can be used to directly reference the file without requiring additional file name translation.
An operating system provides a common name space for both long filenames and short filenames. In this common namespace, a long filename and a short filename are provided for each file. Each file has a short filename directory entry and may have at least one long filename directory entry associated with it. The number of long filename directory entries that are associated with a file depends on the number of characters in the long filename of the file. The long filename directory entries are configured to minimize compatibility problems with existing installed program bases.
U.S. Patent #6,286,013
Method and system for providing a common name space for long and short file names in an operating system
An operating system provides a common name space for both long filenames and short
I have 16' of 2'-deep shelving, about 6' tall. On the ends are peg boards for hand tools and soldering irons and such. On the shelves are those boxes you get issued when your office decides to move everyone to new cubicles. The shelves and boxes are labeled according to the signs over the aisles at the hardware/computer stores. Hardware store stuff is classified as electrical, plumbing, automotive, paint, etc. Computer stuff is classified as system units, monitors, keyboards and mice, software, etc.
Meanwhile, my vast collection of CDs plus the data in my personal SAN are organized according to MIME types: text, message, audio, image, video, model, application, and subfolders thereunder. Also, I saw somewhere the suggestion that the only indexing scheme that endures is chronological, so everything is cross-linked into directories of the form YYYY/MM/DD going back to 1990.
You seem disappointed that "Linux" isn't a monolithic system.
This is one place where RMS's insistance on calling it GNU/Linux pays off. The GNU components have standardized on "--help" and "--version" to get command line help. What they need next is to add "--help-html" and "--help-xml" options to completely automate web-based help systems and the automagical creation of GUI front-ends for everything. This shouldn't be too hard; I've seen (and written) tools that take a man-page and generate not only support for the previous options but also generate all the code for your getopt processing.
X11 is totally separate from Linux; you should complain to whomever about the multiplicity/lack of good config tools. Note that X11 config tools generally have to run in both text mode, for when your setup is totally broken, and GUI mode for when you want to tune a working environment.
Finally, the things that are actually part of the kernel, like ifconfig, have a third "universe" of authors to talk to, so don't expect them to have the same standards of documentation. This is where the HOWTOs live. Yeah, ifconfig could use a good save-/load-config option, but that's pretty easy to build with Perl using both ifconfig and netstat. I don't see that as just "wrappering a bunch of buttons around the already broken framework". Millions use the framework everyday, it's just not oriented toward newbies. The framework isn't broken, it's just baroque.;-)
Every time I see a commercial for Video Professor, I wonder about producing something similar for *nix. Call it Professor Tux. There are extensions for VNC that let you record and play-back interactions, so you'd just need to add a synchronized audio/text-caption stream and show how to do things inside a 640x480 window, then have a hierarchical index of tasks front-ending the animations. You could probably create something that does it all entirely in JavaScript off of a CD-ROM.
Of course, I haven't actually viewed a Video Professor lesson, so they may do more things than I've just listed.
Is anyone old enough to recall the 1983 TV movie Special Bulletin? It was presented as real-time coverage of a nuclear terrorist/hostage situation. Everyone at the network remembered the WotW broadcast, so the show carried lots of disclaimers. In spite of that, there were a lot of phone calls made to the police, especially in the area where the story was supposed to be taking place.
OS/2 advocates often point the fact that OS/2 being a "better Windows than Windows" strangled the OS/2 application development industry in it's cradle.
But WINE isn't a "better Windows than Windows", in fact it is mostly inferior to Windows. OS/2 and Windows developed from the same roots, so it was easy for one to support the other's programs (and Windows started off with an OS/2 compatibility mode). Likewise, Linux and Unix share common roots, so it's easy for BSD, for example, to run Linux binaries.
WINE, on the other hand, has to emulated a lot more than a "compatibility layer", so programs running under WINE don't run quite as well. If an outfit sees a lot of people running their product under WINE, they realize that those people would probably want a Linux version that runs better.
Finally, EMC just bought Documentum, the CMS that you are considering. EMC is primarily a storage company, and I cannot help but wonder how CMS fits into their storage strategy.
The quick answer is that content has to be kept somewhere, i.e. storage, and EMC is always interested in things that help sell storage.
The long answer is that so-called fixed content is an growing slice of the storage pie. EMC has a nifty way to store fixed content (see this article), but that's only the bottom layer of the stack. Documentum provides higher layers that already integrate well with the Centera. EMC is wanting to get more into software, so buying one of the industry leaders make a lot of sense.
Your link to Group Wants to Protect Apollo Site reminds me of a bit in John Varley's SF novel, Steel Beach, where the narrator tells of a group of lunar frat boys who got drunk one night and went out and messed up the Sea of Tranquility landing site (driving over the footprints and tipping over the LEM). Fortunately, it was the most photographed tourist spots on the moon, so the restorationists got as many photos as they could lay their hands on and put things back exactly the way they were.
BTW, (possible spoiler follows) this side story foreshadowed a major plot revelation, in that just about everyone knew that the site was, in a sense, fake, but no one ever talked about the "secret" in public.
I'd be interested in how a Storage Tank differs from EMC's Centera, which provides WAN access to large amounts of storage. Centera is a Linux-based rack of P2P nodes with ATA-based storage, all accessible only via HTTP. You "POST" the content of a file, and get back a cryptographic checksum as a file identifier which you then use to retreive the content later. This lets you verify that the data is still intact. Here's the marketing-speak:
Centera's architecture is based on redundant arrays of independent nodes (RAIN)--offering petabyte scalability. Adding capacity is easy: Centera auto-discovers and configures the new capacity as it's installed.
When using content mirroring protection, all information objects are synchronously mirrored within a local Centera cluster to support automatic recovery from component failures. Centera also can be configured to maintain duplicate copies of fixed content at a remote site to guard against site disaster.
Centera continuously monitors to detect and repair soft errors. It also automatically reconfigures itself and replicates objects as necessary if hardware failures occur such as disks or nodes--which are automatically reported through EMC's remote monitoring system.
My father has an old Atari that hasn't been turned on in years. He used it to write his "memoirs", which wouldn't be interesting to anyone but his kids. The point is, the floppies that he used seem to be FAT compatible, so I was able to move the files directly to a PC, then whipped up a quick Perl program to strip out the text from the formatting codes. This allowed me to avoid the use of a serial connection to transfer the data by wire.
In 1787, Mozart invented A Musical Dice Game for Composing a Minuet. Given the results of the game, I assume that one can derive the dice numbers that created it. (If not, it shouldn't be hard to modify the game to possess that property.) Now, play the game using a fixed string of bits instead of a random number generator. The result is very definitely music, and it isn't steganography.
The use of a Mozart encoder and decoder would be even more powerful than Ka-Blamo.
Mudwin is my favorite, but I'm a bit biased. I guess that I need to dust off the source code and recompile it for native Win32. When I wrote it, most MUD clients for Windows 95 were written in Visual Basic. Mine was one of, if not the first to be written in C. Given the hardware of the time, it blew away the competition.
Several other posters have mentioned features that their ideal client would possess. I'll try to see how many I can easily add.
Several people have mentioned "an Empire game", but I'm more interested in "file version numbers". Does anyone know about a file system that natively supports versions, like VMS did?
Re:Not exactly... well, to be honest: the opposite
on
Plasma Comes Alive
·
· Score: 1
it still begs the question about the Sun in general being cooler under the surface than on top
Part of the problem is the definition of "hotter" and "cooler". Temperature is a measure of the average kenetic energy of molecules. At the surface of the earth, where all things have roughly equal densities, we learn to expect certain things about heat transference. In a near vacumn, the molecules can be very "hot", but the heat doesn't transfer to denser objects. Thus, the following facts:
Temperature in the troposphere decreases with height to -76 degrees Fahrenheit.
In the lower levels of the stratosphere the temperature remains the same, but in the upper levels the temperature actually increases to roughly the same as that at sea level.
In the mesosphere, which extends to about 50 miles, temperature drops again to as low as -173 degrees F.
The thermosphere extends to 400 miles and is characterized by large fluctuations of temperature (thermo means "heat"). At these heights there are relatively few molecules and heat retention should be low. However, within the thermosphere solar energy is absorbed and reradiates heat. At its upper limits the temperature reaches 441 degrees F.
So, the Earth's atmosphere shows the same effects that as the Sun.
It's a single record for verisign, but there's no difference in the DNS response record. This means that a caching DNS has to keep every record that it gets back. This means that you could overload Google, but verisign would be unlikely to be affected.
And you can't ignore domains that resolve to identical addresses. Virtual web servers share the same address with different domain names. The web server uses the name to decide which set of web pages to serve up.
Given how widespread mobile phone use has become, will we even have an adequate control group 50 years from now to gauge what the effects have been?
Yes, we will, and they are called the Amish. I doubt that there will be many cell towers built in areas where they live. Other rural areas, yes, because a cell phone is so damn convenient when you're out on the back forty, but not in areas where the land owners don't believe in any new-fangled technology more complicated that in-line roller skates.
SCO vs. Linux: The time of the conspiracy theories
In history around SCO and the source code from SCO existence, rich at idioms and twists, possibly transferred after Linux, new turns are to be reported. With the conspiracy theory that Microsoft behind SCO stands, it associates the theory that the refusal of the requirements of SCO is a only one, well camouflaged campaign of IBM. Thus the InfoWorld reportedthat SCO boss sees Darl McBride IBM as an author of the dirt campaign. IBM caused Novell to place itself against SCO meant McBride, employed long years with Novell as a director/conductor of the Netware Embedded division (NEST). IBM has talks floated to complain against SCO means it in addition. Also Eric Raymond of the open SOURCE initiative would stand on the pay roll IBMs, which would finance besides the Free software Foundation and thus the lawyer evenly Moglen, continued to implement Darl McBride.
While IBM as talk has the accusations lapidary for nonsense explained and about Novell none came, Eric Raymond raffte itself up to send an open letter at Darl McBride. In it answered in the negative Raymond by IBM to be paid did not deny however IBM to have helped. Altogether Raymond appealed to the reason of the SCO upper one with an allusion to the insight ability of Darth Vader: "you have the choice. Remove the dark helmet and converse with us like a human nature, or you continue your way, which lets bad times fear for us, however you and the entire SCO Topmanagement into the ruin will completely surely float."
Off the roaring star Wars Rhetorik Eric Raymond used the open letter, in order to make attentive on a Petition of the Linux Community, which were read out on the SCOForum. In their the SCO Group is requested to give up and all inkriminierten places in the SOURCE code call the confrontation course. In response the Linux programmers want to assure to revise all questionable places: "if right right-hurt-hurting that code in the Linux Kernel to be present should become, we it remove, because our community would not like to have a part of this Kernels."
The polite request will possibly remain without answer, because SCO with first, on which SCOForum published proofs could not convince. Apart from the problem of the "Greek" code is in the meantime the Berkeley presented by SCO pack filter (BPF) into the center of the interest moved. The SCO example originates from the file/sys/net/bpf.c, which is available here. In the cutout shown by SCO is missing the BSD Lizenzbedigungen, which is to be always called in accordance with BSD license: "Redistributions OF SOURCE code must retain the above copyright notice, this cunning OF conditions and the following more disclaimer." Because they are missing, code experts go such as Bruce Perens and Greg Lehey of the fact out that SCO with the example proved that the license conditions were removed agreement-adversely.
Thus a classical self-gate could be present, particularly since other possibilities are impossible. Like that the programmer of the version used in Linux was employed by BPF, Jay trainingist, with Caldera, wrote however the Clean Room variant of BPF before its time with Caldera. From the circles of former Caldera developers several persons can remember that in the SCO Trees in many places with the BSD code the copyright notes were missing. The procedure to cut "redundant" licenses off seems to have practiced also at other companies. Thus heise on-line developers to, that experienced the "technology" at Siemens Nixdorf, announced themselves. If the proof situation in the case SCO should confirm itself, then the code Hunter of this company excavated a proof, which occupies the exact opposite of the accusations by SCO. At least in the case of BPF SCO the power POINT presentation would not only have (when ppt, when pdf) separate the whole code make public, in order to weaken the suspicion.
To the recent developments in the controversy between SCO, the open SOURCE municipality and the Linux companies see als
Reply comments for the BPL proceeding are due on or before August 20, 2003. Interested parties may submit electronically filed comments via the FCC's Electronic Comment Filing System (ECFS). Under ECFS Main Links, click on "Submit a Filing." In the "Proceeding" field, enter "03-104" and complete the required field. Comments may be typed into a form or you may attach a file containing your comments. Comments also may be submitted via e-mail, per instructions on the ECFS page.
Here's what I had to say:
I am against permiting further expansion of Broadband over Power
Line (BPL). The use of power lines to carry these signals turns
them into log antenas, broadcasting interference throughout their
length. As an Electrical Engineering student in college, I learned
that signal strength falls off from a point source according to the
inverse square law. From a wire, however, signal strength falls off
much more slowly. In the past, power companies have demonstrated
little interest in resolving complaints of power line noise. The
increased noise produced by BPL is unlikely to be reduced if left
to self-policing by the power industry.
Slashdot Mirror
http://www.deskdemon.com/pages/uk/services/invisib le
Not any fancy-pants API or beta/lab thing. I just type some ingredients into the main search engine and pick the recipes out of the results.
Uh, the... internet... has... been... very... good... to... me...
If you don't have your local TV via dish, you can get access to a package of either NY or LA network stations. Once your local TV is available, you can't sign up anymore, but your existing package is grandfathered. This gives you twice as many chances to view/tape a network program, which can be handy at times.
My city didn't have a UPN affiliate, so I qualified for a package with 3 WB and 2 UPN stations. The WB's are in NY, Denver and LA while the UPNs are in Boston and NY (both EST, which is a bummer), so my one-receiver DVR could, for instance, record Enterprise and Jake 2.0 from Boston, then get Angel from Denver, and then Smallville from LA. This makes all members of my family happy. OTOH, if '24' conflicts with something on ABC, CBS, or NBC, I'm screwed.
So, if you have a DVR and can justify an extra $5 or $10 a month, get those packages now while you can, and keep them once you can get your local TV. I predict that you'll be glad you did.
I don't know why someone modded this as funny. My in-laws live on a farm in Arkansas and I installed DishNetwork for them about five or six years ago. Last summer, they said that reception was getting iffy. I stepped outside and noticed that since getting rid of their chickens (stop laughing, it's true!), they'd let some trees grow along a fence row. I got their chainsaw out and within a few minutes their signal strength had moved from 80 to 112.
# Title: A -- Defense Sciences Research and Technology
# Special Focus Area: Time Reversal Methods
# Announcement#: BAA03-02, Addendum 3
# FedBizOpps Reference: February 4, 2003
Why not have the smallest addressable unit be a 16-bit value, instead of the now-standard 8 bits? This would remove the need to distinguish between chars and wchars, with "bytes" able to hold Unicode. Then, shorts would be two "bytes", or 32 bits, ints would be four "bytes", or 64 bits, and longs could even be 128 bits, without any issues.
U.S. Patent #5,579,517 Common name space for long and short filenames
An operating system provides a common name space for both long filenames and short filenames. In this common namespace, a long filename and a short filename are provided for each file. Each file has a short filename directory entry and may have at least one long filename directory entry associated with it. The number of long filename directory entries that are associated with a file depends on the number of characters in the long filename of the file. The long filename directory entries are configured to minimize compatibility problems with existing installed program bases.
U.S. Patent #5,745,902 Method and system for accessing a file using file names having different file name formats
A multiple file name referencing system stores multiple file names in a file. These multiple file names include an operating system formatted file name and an application formatted file name. When an operating system formatted file name is created or renamed, the multiple file name referencing system automatically generates an application formatted file name having a potentially different format from, but preserving the extension of, the operating system formatted name. The multiple file name referencing system similarly generates an operating system formatted name upon creation or renaming of an application formatted name. A B-tree is provided which contains an operating system entry for the operating system formatted name and an application entry for the application formatted name, each entry containing the address of the same file to which both names refer. The multiple file name referencing system converts the operating system formatted file name to the application formatted file name by accessing the B-tree with reference to the operating system entry, and vice versa. As a result, either file name can be used to directly reference the file without requiring additional file name translation.
U.S. Patent #5,758,352 Common name space for long and short filenames
An operating system provides a common name space for both long filenames and short filenames. In this common namespace, a long filename and a short filename are provided for each file. Each file has a short filename directory entry and may have at least one long filename directory entry associated with it. The number of long filename directory entries that are associated with a file depends on the number of characters in the long filename of the file. The long filename directory entries are configured to minimize compatibility problems with existing installed program bases.
U.S. Patent #6,286,013 Method and system for providing a common name space for long and short file names in an operating system
An operating system provides a common name space for both long filenames and short
Meanwhile, my vast collection of CDs plus the data in my personal SAN are organized according to MIME types: text, message, audio, image, video, model, application, and subfolders thereunder. Also, I saw somewhere the suggestion that the only indexing scheme that endures is chronological, so everything is cross-linked into directories of the form YYYY/MM/DD going back to 1990.
This is one place where RMS's insistance on calling it GNU/Linux pays off. The GNU components have standardized on "--help" and "--version" to get command line help. What they need next is to add "--help-html" and "--help-xml" options to completely automate web-based help systems and the automagical creation of GUI front-ends for everything. This shouldn't be too hard; I've seen (and written) tools that take a man-page and generate not only support for the previous options but also generate all the code for your getopt processing.
X11 is totally separate from Linux; you should complain to whomever about the multiplicity/lack of good config tools. Note that X11 config tools generally have to run in both text mode, for when your setup is totally broken, and GUI mode for when you want to tune a working environment.
Finally, the things that are actually part of the kernel, like ifconfig, have a third "universe" of authors to talk to, so don't expect them to have the same standards of documentation. This is where the HOWTOs live. Yeah, ifconfig could use a good save-/load-config option, but that's pretty easy to build with Perl using both ifconfig and netstat. I don't see that as just "wrappering a bunch of buttons around the already broken framework". Millions use the framework everyday, it's just not oriented toward newbies. The framework isn't broken, it's just baroque. ;-)
Of course, I haven't actually viewed a Video Professor lesson, so they may do more things than I've just listed.
Is anyone old enough to recall the 1983 TV movie Special Bulletin? It was presented as real-time coverage of a nuclear terrorist/hostage situation. Everyone at the network remembered the WotW broadcast, so the show carried lots of disclaimers. In spite of that, there were a lot of phone calls made to the police, especially in the area where the story was supposed to be taking place.
But WINE isn't a "better Windows than Windows", in fact it is mostly inferior to Windows. OS/2 and Windows developed from the same roots, so it was easy for one to support the other's programs (and Windows started off with an OS/2 compatibility mode). Likewise, Linux and Unix share common roots, so it's easy for BSD, for example, to run Linux binaries.
WINE, on the other hand, has to emulated a lot more than a "compatibility layer", so programs running under WINE don't run quite as well. If an outfit sees a lot of people running their product under WINE, they realize that those people would probably want a Linux version that runs better.
The quick answer is that content has to be kept somewhere, i.e. storage, and EMC is always interested in things that help sell storage.
The long answer is that so-called fixed content is an growing slice of the storage pie. EMC has a nifty way to store fixed content (see this article), but that's only the bottom layer of the stack. Documentum provides higher layers that already integrate well with the Centera. EMC is wanting to get more into software, so buying one of the industry leaders make a lot of sense.
BTW, (possible spoiler follows) this side story foreshadowed a major plot revelation, in that just about everyone knew that the site was, in a sense, fake, but no one ever talked about the "secret" in public.
Centera's architecture is based on redundant arrays of independent nodes (RAIN)--offering petabyte scalability. Adding capacity is easy: Centera auto-discovers and configures the new capacity as it's installed.
When using content mirroring protection, all information objects are synchronously mirrored within a local Centera cluster to support automatic recovery from component failures. Centera also can be configured to maintain duplicate copies of fixed content at a remote site to guard against site disaster.
Centera continuously monitors to detect and repair soft errors. It also automatically reconfigures itself and replicates objects as necessary if hardware failures occur such as disks or nodes--which are automatically reported through EMC's remote monitoring system.
My father has an old Atari that hasn't been turned on in years. He used it to write his "memoirs", which wouldn't be interesting to anyone but his kids. The point is, the floppies that he used seem to be FAT compatible, so I was able to move the files directly to a PC, then whipped up a quick Perl program to strip out the text from the formatting codes. This allowed me to avoid the use of a serial connection to transfer the data by wire.
In 1787, Mozart invented A Musical Dice Game for Composing a Minuet. Given the results of the game, I assume that one can derive the dice numbers that created it. (If not, it shouldn't be hard to modify the game to possess that property.) Now, play the game using a fixed string of bits instead of a random number generator. The result is very definitely music, and it isn't steganography.
The use of a Mozart encoder and decoder would be even more powerful than Ka-Blamo.
Several other posters have mentioned features that their ideal client would possess. I'll try to see how many I can easily add.
Maybe I'll turn it into a SourceForge project...
Several people have mentioned "an Empire game", but I'm more interested in "file version numbers". Does anyone know about a file system that natively supports versions, like VMS did?
Part of the problem is the definition of "hotter" and "cooler". Temperature is a measure of the average kenetic energy of molecules. At the surface of the earth, where all things have roughly equal densities, we learn to expect certain things about heat transference. In a near vacumn, the molecules can be very "hot", but the heat doesn't transfer to denser objects. Thus, the following facts:
- Temperature in the troposphere decreases with height to -76 degrees Fahrenheit.
- In the lower levels of the stratosphere the temperature remains the same, but in the upper levels the temperature actually increases to roughly the same as that at sea level.
- In the mesosphere, which extends to about 50 miles, temperature drops again to as low as -173 degrees F.
- The thermosphere extends to 400 miles and is characterized by large fluctuations of temperature (thermo means "heat"). At these heights there are relatively few molecules and heat retention should be low. However, within the thermosphere solar energy is absorbed and reradiates heat. At its upper limits the temperature reaches 441 degrees F.
So, the Earth's atmosphere shows the same effects that as the Sun.And you can't ignore domains that resolve to identical addresses. Virtual web servers share the same address with different domain names. The web server uses the name to decide which set of web pages to serve up.
Yes, we will, and they are called the Amish. I doubt that there will be many cell towers built in areas where they live. Other rural areas, yes, because a cell phone is so damn convenient when you're out on the back forty, but not in areas where the land owners don't believe in any new-fangled technology more complicated that in-line roller skates.
SCO vs. Linux: The time of the conspiracy theories
/sys/net/bpf.c, which is available here. In the cutout shown by SCO is missing the BSD Lizenzbedigungen, which is to be always called in accordance with BSD license: "Redistributions OF SOURCE code must retain the above copyright notice, this cunning OF conditions and the following more disclaimer." Because they are missing, code experts go such as Bruce Perens and Greg Lehey of the fact out that SCO with the example proved that the license conditions were removed agreement-adversely.
In history around SCO and the source code from SCO existence, rich at idioms and twists, possibly transferred after Linux, new turns are to be reported. With the conspiracy theory that Microsoft behind SCO stands, it associates the theory that the refusal of the requirements of SCO is a only one, well camouflaged campaign of IBM. Thus the InfoWorld reportedthat SCO boss sees Darl McBride IBM as an author of the dirt campaign. IBM caused Novell to place itself against SCO meant McBride, employed long years with Novell as a director/conductor of the Netware Embedded division (NEST). IBM has talks floated to complain against SCO means it in addition. Also Eric Raymond of the open SOURCE initiative would stand on the pay roll IBMs, which would finance besides the Free software Foundation and thus the lawyer evenly Moglen, continued to implement Darl McBride.
While IBM as talk has the accusations lapidary for nonsense explained and about Novell none came, Eric Raymond raffte itself up to send an open letter at Darl McBride. In it answered in the negative Raymond by IBM to be paid did not deny however IBM to have helped. Altogether Raymond appealed to the reason of the SCO upper one with an allusion to the insight ability of Darth Vader: "you have the choice. Remove the dark helmet and converse with us like a human nature, or you continue your way, which lets bad times fear for us, however you and the entire SCO Topmanagement into the ruin will completely surely float."
Off the roaring star Wars Rhetorik Eric Raymond used the open letter, in order to make attentive on a Petition of the Linux Community, which were read out on the SCOForum. In their the SCO Group is requested to give up and all inkriminierten places in the SOURCE code call the confrontation course. In response the Linux programmers want to assure to revise all questionable places: "if right right-hurt-hurting that code in the Linux Kernel to be present should become, we it remove, because our community would not like to have a part of this Kernels."
The polite request will possibly remain without answer, because SCO with first, on which SCOForum published proofs could not convince. Apart from the problem of the "Greek" code is in the meantime the Berkeley presented by SCO pack filter (BPF) into the center of the interest moved. The SCO example originates from the file
Thus a classical self-gate could be present, particularly since other possibilities are impossible. Like that the programmer of the version used in Linux was employed by BPF, Jay trainingist, with Caldera, wrote however the Clean Room variant of BPF before its time with Caldera. From the circles of former Caldera developers several persons can remember that in the SCO Trees in many places with the BSD code the copyright notes were missing. The procedure to cut "redundant" licenses off seems to have practiced also at other companies. Thus heise on-line developers to, that experienced the "technology" at Siemens Nixdorf, announced themselves. If the proof situation in the case SCO should confirm itself, then the code Hunter of this company excavated a proof, which occupies the exact opposite of the accusations by SCO. At least in the case of BPF SCO the power POINT presentation would not only have (when ppt, when pdf) separate the whole code make public, in order to weaken the suspicion.
To the recent developments in the controversy between SCO, the open SOURCE municipality and the Linux companies see als
Here's what I had to say: