Yup... DrudgeReport.com is a fairly good indicator of the general most-breaking news story of the moment, which is a good way to roll out of bed and start my morning.
I'm damn sure that it's the start page of at least a third of DC.
Then, it's off to work where my start page is Google, even though there's an Intranet page I probably should be using instead.
Slashdot loads too slowly for a start page when I'm opening new windows. I used to keep it at Yahoo.com when I'd set up other people's computers because it was quick, moderately useful, and rather neutral.
Why not use a Big Brother or network status page as your start page? Simple, have the condensed view on your desktop permanently instead. It's an actual use for Windows' Active Desktop feature:)
On other distribututions, rpm (yes, rpm) works fine. it doesn't strip binaries it shouldn't touch (arm for instance in an x86 package), it doesn't add depenedencies it doesn't need, it basically just works as advertised.
Have you used the 'AutoReqProv: no' line in RPM? Works fine for me in preventing spurious dependancies.
there is no such thing as a minimal redhat9 installation. all we wanted was to build packages for redhat9, 2gig was as small as I could get the build.
Have we not heard of "Select individual packages?" I routinely build RH9 and FC1 boxes in the 800-900MB range. Could probably do with less if I really wanted to.
There are also the configs, the different command usages, etc. etc.
When you're using any package management system there are bound to be configs that are placed in automatically. Aside from RH basically not using/usr/local (something that I agree with), I don't see what you're complaining about.
Redhat: new users and coporate users needing a good backup plan.
etc...
Blah blah blah. It's certainly as possible to tune a RH system for low-fussness, or for high performance (i386 packages don't make that much of a difference!) just as it is to mis-configure any of the other distros. Use what works for you.
What would the Microsoft source code be doing on a Linux machine? Mainsoft ports applications from Windows to Unix, not Linux. IE and WinAmp are two examples that they've ported.
...If this is the case, Mainsoft was porting Windows applications to Linux as well as Unix.
Umm.. did we not click on our links today? The article linked to has a big, fat link to the MainWin product page which states, in part:
Visual MainWin is an enterprise-class application-porting platform that enables software developers to develop C++ applications on Windows using Visual Studio and deploy them on Unix
and Linux. Visual MainWin is a complete cross-platform solution that speeds development and deployment. Developers will also appreciate Visual MainWin's J2EE Integration Package and industry-leading XML support. And it actually recompiles Windows source code with the Unix compilers to create native Unix applications.
I think it's certainly safe to assume that they were compiling on a box.
They wanted to make "system interaction and direction" as easy as making usable stacks was in HyperCard. With AppleScript Studio, it seems like they've finally succeeded.
You can't put a company in jail; it's an entity that exists on paper. Nor can you put the execs in jail - corporate shield, as long as they didn't break the law (significantly).
Nope, but a company that is ceasing to "act in the public service" can be given the so-call corporate death penalty by having their corporate charter revoked by the state that granted it to them. Do a search for charter revocation" and unocal for an example of the kinds of pressure than can be drawn upon it.
I really think that, when all is said and done, and assuming SCO doesn't go bankrupt and collapse itself after it loses this fight, corporate charter revocation should be something that we as a community should investigate pushing.
Weird problems may ensue when the clock wraps around which is not necessarily a rare event; on systems counting 10 ticks per second, a signed 32-bit count of ticks is good only for 6.8 years. The 1-tick-per-second clock of Unix is good only until January 18, 2038, assuming at least some software continues to consider it signed and that word lengths don't increase by then.
You're confusing the epoch datetime and "ticks," at least on the Macintosh.
The classic Mac OS had the normal epoch seconds time (which is what is referenced in the story), and then a value called "ticks" which was 60ths of a second since system boot.
Epoch time was used when determining current time, but ticks, because of their decent resolution, were often used for timing duration of things.
Censored music. Yuck! Why don't they just let the listener decide what is and what isn't appropriate? Shesh!
They do. You can opt to purchase your music elsewhere.
IT'S ONLY CENSORSHIP WHEN THE GOVERNMENT RESTRICTS SPEECH, Mr. Wolf-cryer.
Speaking as someone who's DJ'd before and tried forever to search for "clean", radio versions, of songs to play at HS-type dances, I can say that there are definitely some people who actively search for the clean material. They like the groove of Snoop Dogg's "What's My Name", but can deal without the constant swearing and other ghettoness.
Anybody work in that industry and have any insights?
Yes, and not really. We're still sitting here trying to decide what to do about it. Chances are, we'll be installing the latest quasi-stable release of Fedora on it and brand it as a "Linux Server". We'll probably use up3date pointing to a local repository of tested RPMS to manage auto updates for clients, but we haven't decided for sure yet.
You're right in that our margins are already pretty thin. $65-year for a supported server was doable for us to be able to provide some sort of warrantee, but $399+ isn't.
Taking a wait-and-see approach, but we'll almost certainly not move to FreeBSD as a provider-supported option (too complex, and foreign to most of our customers), nor will we stop selling the "Dedicated Linux Server" product; it's just too useful to people.
... when it comes out. I'm just guessing on the content of this article since it's already Slashdotted and no one seems to have posted a copy, strangely enough, but it seems that he's beored with over-defined "games" that require significant blocked time effort and mandate certain types of social interaction to achieve anything "fun".
Frankly, maybe you should re-visit the type of "game" you play. I plan to start Uru (aka Mudpie, aka Online Myst) as soon as it comes out for just this reason. You completely free to explore on your own, and you're also able to explore with others, if you so desire.
I tried Red Hat Linux Severn yesterday, I had some terrible problems with it. I had bought a 3.2Ghz Pentium 4 Box to replace my old 68K based imac with MacOS 6.8 running photoshop 3.1
God I hate feeding trolls.. but for those who didn't catch this:
- There was no 6.8 (there was a 6.0.8, but it was only released as an after-thought for increased compatability with the already-out 7.0) - There were no 68k iMacs.
Subject: Re: Request for Advice on VGRS IDN Announcement To: "M. Stuart Lynn" Cc: Leslie Daigle,
Chuck Gomes,
Brad Verd,
Masanobu Katoh,
Steve Crocker,
Vint Cerf,
Louis Touton,
Andrew McLaughlin,
iab@ietf.org Date: Sat, 25 Jan 2003 10:19:37 +1100
Dear Stuart,
Thanks for your message. After reviewing the announcement, examining the behavior of the deployed system, discussing the issue with colleagues external to the IAB, and meeting with VeriSign's technical staff to go over the system's aim and implementation, the IAB has come to the following consensus.
The IAB feels that the system VeriSign had deployed for.com and.net contains significant DNS protocol errors, risks the further development of secure DNS, and confuses the resolution mechanisms of the DNS with application-based search systems. The IAB understands the efforts that VeriSign has made to limit the applicability of this system to queries which would normally not correspond to registered domains, and it recognizes the importance of the distribution of IDN-capable systems to end users. While the IAB agrees with VeriSign that rapid adoption of IDN-capable systems is desirable, the IAB feels that the very limited gain in distribution cannot balance the shortcomings of this deployment strategy.
The IAB has begun the process of shepherding the creation of an Informational RFC on concerns with operational practices with the DNS. We anticipate discussing the issues raised in your notes in more detail as part of that document. Given the scope of the issue, and our desire to ensure that it will have adequate review by the (DNS) operational community, we will be enlisting the help of the broader IETF community through relevant IETF working groups. In advance of that document, we have outlined below the issues with the VeriSign system which led us to the conclusion above.
As a lookup system, the DNS is designed to provide authoritative answers to queries. The DNS protocol specifies behavior for queries whose targets do occur in a zone by describing the data format for the specific resource records and the wire format for the response. The DNS protocol also specifies behavior for queries whose targets do not occur in a zone by describing the wire format for a negative response.
The system deployed for.com and.net does not follow the specification for targets not in a zone. Instead, it examines the target and decides whether to give the specified negative response or a synthesized record based on whether the target contains a code point above 127. This is a violation of the DNS protocol as described in RFC 2308, Section 2.1. While it is possible within the DNS protocol to include wildcard records which cover all queries not otherwise specified by a zone, this is not what VeriSign has done. Negative answers for records which do not contain code points above 127 continue to be sent.
It would, of course, be theoretically possible to add zone entries for all records containing code points above 127. Given that the Verisign system does not recognize "." as a label delimiter for testing these records, the size of the resulting zone is unimaginably large. VeriSign confirms that they are not managing a zone of the size this would imply and is, instead, synthesizing these entries. This implies that the zone as currently served by VeriSign cannot be transferred using either AXFR or file transfers in master file format. Though the choice of who may employ AXFR or file transfer to get copies of a zone is a policy decision, the IAB notes that the current system does
A wildcard entry in a zone affects DNS responses for that zone. For existing applications that do not contemplate the effects of wildcard entries, application developers should consider taking appropriate corrective actions.
The Good Side to all this is that there's finally a large-scale, mass-customer-affecting issue that Verisign has caused. Those of us in the US can now point to something (something easy-to-understand as an abuse of power) when we go talk to our Congressmen about overseeing the Department of Commerce.
Verisign is no longer worthy of the Internet's trust. It's time for the Dept. of Commerce to take the InterNIC back under its wing.
To all you damn Libertarians that thing private commerce and capitalism is important for the proper functioning of ANYTHING, wake up and take a look around. Some things NEED to be regulated by the government; some times efficency is NOT as important as accountability. This is one of them (as a Californian, energy regulation is another!).
Holding domains hostage for 6 months after registration
Providing features (snap-back, etc...) only available to Registrars with close (same-company) relationships with the Registry
Over-charging for SSL certificates almost to the point of extortion
Not to nit-pick, but a 404 message is only displayed when you've hit a valid server, but the file you've requested isn't there (page/resource cannot be found).
The message IE normally displays (if you've turned off MSN's search feature) is:
The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.
Not as helpful as it could be, but at least it's something. Incidentally, this is what users will STILL get at my ISP once we null-route that IP address. =)
Slashdot Mirror
Yup... DrudgeReport.com is a fairly good indicator of the general most-breaking news story of the moment, which is a good way to roll out of bed and start my morning.
:)
I'm damn sure that it's the start page of at least a third of DC.
Then, it's off to work where my start page is Google, even though there's an Intranet page I probably should be using instead.
Slashdot loads too slowly for a start page when I'm opening new windows. I used to keep it at Yahoo.com when I'd set up other people's computers because it was quick, moderately useful, and rather neutral.
Why not use a Big Brother or network status page as your start page? Simple, have the condensed view on your desktop permanently instead. It's an actual use for Windows' Active Desktop feature
People would be much better off with hardware versions of Internet Explorer and Outlook (Express) in that respect. Yikes.
Wouldn't that basically be an embedded system, running on non-volatile or read-only memory?
every user a developer
Oh please. Who exactly will benefit, and how?
Go read up on the history of HyperCard, yo. Plenty of people benefited from the use of it, and many are still benefiting today.
I'm surprised no one's posted a link to this yet... O'Reilly's Mac Dev Center has a nice article on "the often misunderstood world of talking to your Mac" that goes over the existing speech (and speech recognition) interface.
A good overview of past and present, with a little bit of technical information there for AppleScripters too.
On other distribututions, rpm (yes, rpm) works fine. it doesn't strip binaries it shouldn't touch (arm for instance in an x86 package), it doesn't add depenedencies it doesn't need, it basically just works as advertised.
Have you used the 'AutoReqProv: no' line in RPM? Works fine for me in preventing spurious dependancies.
there is no such thing as a minimal redhat9 installation. all we wanted was to build packages for redhat9, 2gig was as small as I could get the build.
Have we not heard of "Select individual packages?" I routinely build RH9 and FC1 boxes in the 800-900MB range. Could probably do with less if I really wanted to.
There are also the configs, the different command usages, etc. etc.
When you're using any package management system there are bound to be configs that are placed in automatically. Aside from RH basically not using
Redhat: new users and coporate users needing a good backup plan.
etc...
Blah blah blah. It's certainly as possible to tune a RH system for low-fussness, or for high performance (i386 packages don't make that much of a difference!) just as it is to mis-configure any of the other distros. Use what works for you.
and she made an educated guess that Napster would last about as long as Right Said Fred.
I'm too sexy for my iPod.
Would that be morse-over-morse, or maybe metamorse?
Quick! Somebody call Hofstadter!
What would the Microsoft source code be doing on a Linux machine? Mainsoft ports applications from Windows to Unix, not Linux. IE and WinAmp are two examples that they've ported.
Umm.. did we not click on our links today? The article linked to has a big, fat link to the MainWin product page which states, in part:
I think it's certainly safe to assume that they were compiling on a box.
Why do people insist on inventing their own scripting languages instead of picking one of the handful of fine existing languages?
Actually, AppleScript's roots harken back to HyperTalk, the inner scripting language of HyperCard. (With minor changes, such as "it" now being called "(the) result").
They wanted to make "system interaction and direction" as easy as making usable stacks was in HyperCard. With AppleScript Studio, it seems like they've finally succeeded.
I wish they'd do something with HyperCard though...
And here's a general OSA link... blah
You can't put a company in jail; it's an entity that exists on paper. Nor can you put the execs in jail - corporate shield, as long as they didn't break the law (significantly).
Nope, but a company that is ceasing to "act in the public service" can be given the so-call corporate death penalty by having their corporate charter revoked by the state that granted it to them. Do a search for charter revocation" and unocal for an example of the kinds of pressure than can be drawn upon it.
See also, CA's still-born Corporate 3 Strikes Law.
I really think that, when all is said and done, and assuming SCO doesn't go bankrupt and collapse itself after it loses this fight, corporate charter revocation should be something that we as a community should investigate pushing.
Weird problems may ensue when the clock wraps
around which is not necessarily a rare
event; on systems counting 10 ticks per second, a signed
32-bit count of ticks is good only for 6.8 years. The
1-tick-per-second clock of Unix is good only until January 18,
2038, assuming at least some software continues to consider it
signed and that word lengths don't increase by then.
You're confusing the epoch datetime and "ticks," at least on the Macintosh.
The classic Mac OS had the normal epoch seconds time (which is what is referenced in the story), and then a value called "ticks" which was 60ths of a second since system boot.
Epoch time was used when determining current time, but ticks, because of their decent resolution, were often used for timing duration of things.
"If it is silly, shouldn't it stopped at first judgement?"
It's called due process.
Apache 2 displays that icon for any file named just "core" when FancyIndexing, or Icon Indexing, or something like it, is turned on.
Censored music. Yuck! Why don't they just let the listener decide what is and what isn't appropriate? Shesh!
They do. You can opt to purchase your music elsewhere.
IT'S ONLY CENSORSHIP WHEN THE GOVERNMENT RESTRICTS SPEECH, Mr. Wolf-cryer.
Speaking as someone who's DJ'd before and tried forever to search for "clean", radio versions, of songs to play at HS-type dances, I can say that there are definitely some people who actively search for the clean material. They like the groove of Snoop Dogg's "What's My Name", but can deal without the constant swearing and other ghettoness.
To each their own.
Anybody work in that industry and have any insights?
Yes, and not really. We're still sitting here trying to decide what to do about it. Chances are, we'll be installing the latest quasi-stable release of Fedora on it and brand it as a "Linux Server". We'll probably use up3date pointing to a local repository of tested RPMS to manage auto updates for clients, but we haven't decided for sure yet.
You're right in that our margins are already pretty thin. $65-year for a supported server was doable for us to be able to provide some sort of warrantee, but $399+ isn't.
Taking a wait-and-see approach, but we'll almost certainly not move to FreeBSD as a provider-supported option (too complex, and foreign to most of our customers), nor will we stop selling the "Dedicated Linux Server" product; it's just too useful to people.
Frankly, maybe you should re-visit the type of "game" you play. I plan to start Uru (aka Mudpie, aka Online Myst) as soon as it comes out for just this reason. You completely free to explore on your own, and you're also able to explore with others, if you so desire.
More info:
Open Directory Project on Myst
Uru Live
Except that I'm a dork and Sliders was purchased from FOX well before Stargate was destroyed.
You forgot:
WHEREAS,
We turned STARGATE SG-1 into total crap.
WHEREAS,
We turned then proceeded to turn SLIDERS into total crap, too.
I tried Red Hat Linux Severn yesterday, I had some terrible problems with it. I had bought a 3.2Ghz Pentium 4 Box to replace my old 68K based imac with MacOS 6.8 running photoshop 3.1
God I hate feeding trolls.. but for those who didn't catch this:
- There was no 6.8 (there was a 6.0.8, but it was only released as an after-thought for increased compatability with the already-out 7.0)
- There were no 68k iMacs.
Go mooch off some other pond, foo.
From: http://www.iab.org/Documents/icann-vgrs-response.h tml
Subject: Re: Request for Advice on VGRS IDN Announcement
To: "M. Stuart Lynn"
Cc: Leslie Daigle
Chuck Gomes
Brad Verd
Masanobu Katoh
Steve Crocker
Vint Cerf
Louis Touton
Andrew McLaughlin
iab@ietf.org
Date: Sat, 25 Jan 2003 10:19:37 +1100
Dear Stuart,
Thanks for your message. After reviewing the announcement, examining the behavior of the deployed system, discussing the issue with colleagues external to the IAB, and meeting with VeriSign's technical staff to go over the system's aim and implementation, the IAB has come to the following consensus.
The IAB feels that the system VeriSign had deployed for
The IAB has begun the process of shepherding the creation of an Informational RFC on concerns with operational practices with the DNS. We anticipate discussing the issues raised in your notes in more detail as part of that document. Given the scope of the issue, and our desire to ensure that it will have adequate review by the (DNS) operational community, we will be enlisting the help of the broader IETF community through relevant IETF working groups. In advance of that document, we have outlined below the issues with the VeriSign system which led us to the conclusion above.
As a lookup system, the DNS is designed to provide authoritative answers to queries. The DNS protocol specifies behavior for queries whose targets do occur in a zone by describing the data format for the specific resource records and the wire format for the response. The DNS protocol also specifies behavior for queries whose targets do not occur in a zone by describing the wire format for a negative response.
The system deployed for
It would, of course, be theoretically possible to add zone entries for all records containing code points above 127. Given that the Verisign system does not recognize "." as a label delimiter for testing these records, the size of the resulting zone is unimaginably large. VeriSign confirms that they are not managing a zone of the size this would imply and is, instead, synthesizing these entries. This implies that the zone as currently served by VeriSign cannot be transferred using either AXFR or file transfers in master file format. Though the choice of who may employ AXFR or file transfer to get copies of a zone is a policy decision, the IAB notes that the current system does
More importantly, services like ssh should be implemented in Java or some other language in which errors in "buffer management" don't happen so often.
How about re-implimenting it in Perl, which doesn't generally have problems like this (from the code perspective -- but Perl itself is well-tested).
Hmm... *checks CPAN*...
Nice...
6 Conclusion
A wildcard entry in a zone affects DNS responses for that zone. For existing applications
that do not contemplate the effects of wildcard entries, application developers should
consider taking appropriate corrective actions.
The Good Side to all this is that there's finally a large-scale, mass-customer-affecting issue that Verisign has caused. Those of us in the US can now point to something (something easy-to-understand as an abuse of power) when we go talk to our Congressmen about overseeing the Department of Commerce.
Verisign is no longer worthy of the Internet's trust. It's time for the Dept. of Commerce to take the InterNIC back under its wing.
To all you damn Libertarians that thing private commerce and capitalism is important for the proper functioning of ANYTHING, wake up and take a look around. Some things NEED to be regulated by the government; some times efficency is NOT as important as accountability. This is one of them (as a Californian, energy regulation is another!).
Available here
How nice of them to let us know...
Not to nit-pick, but a 404 message is only displayed when you've hit a valid server, but the file you've requested isn't there (page/resource cannot be found).
The message IE normally displays (if you've turned off MSN's search feature) is:
The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.
Not as helpful as it could be, but at least it's something. Incidentally, this is what users will STILL get at my ISP once we null-route that IP address. =)