Daily trivia: In Sweden, PriceWaterhouseCoopers have merged with Öhrlings Reveko and thankfully they 'only' answer ÖhrlingsPriceWaterhouseCoopers on the phone. But the logo looks hilarious and their newspaper ads don't have much room for anything else.:-)
I use Gandi. www.gandi.net - easy to use online management, reliable warnings for 30, 15, 1 and 0 days before a domain expires. 12 EUR/year. I've been using them since 2001 with no complaints or problems whatsoever.
Re:the C. P. Snow Divide of Sciences and Humanitie
on
Flash, Meet Sparkle
·
· Score: 1
Our network here is 100% windows and has close to 99% uptime. More downtime? Ah, hire a (better) admin!
YOU need a better admin. "close to" 99% is major suckage for an enterprise system and would simply not be acceptable in any major setting. Hell, I was part of a group that built 99.999% uptime servers on Windows NT 4 back in 1998. And THAT was an uphill battle convincing large mobile phone telcos to switch from UNIX where they typically had *zero* downtime. If we had 99% uptime we'd been dead and gone looong before MS bought us.
One reboot later and the server is back in production. Hell? Not more than applying a patch for any other OS.
Um, you really have no idea how to manage a real enterprise class system, do you? Very, very few patches in the UNIX world need full system reboots. The vast majority of them merely require restarting the affected application since they are not integrated into the OS in interesting and illegal ways but kept separate from the kernel.
Hell, I currently run a dinky little one-man webhosting and consulting biz on the side with no hotswap server redundancy and *I* have way better than 99% uptime since I switched from Win2k on the servers to Linux. Only downtime I have had the last four years has been planned downtime for hardware upgrades (mostly adding disk to the fileserver) which is maybe all of ten minutes per year, total. When I ran Win2k, the fucker had to be constantly rebooted after patches, hung spontaneously sometimes just for fun and finally ate my file system. That's when I switched and I have never looked back.
"It's this need for choice and flexibility that led Microsoft to design Office in a way that supports any XML schemas that a customer chooses"
And this customer chooses OpenDocument, an XML schema. So, it would appear that either MS Office or Microsoft is not flexible enough to actually "support any XML schemas that a customer chooses". Microsoft spokesman lying through his teeth, sun rises, sun sets, film at eleven.
I wonder if this is related to the PayPal emails I've been receiving recently regarding suspicious activity on my account.
Hook, line, sinker and a lifetime subscription to Field and Stream. I was wondering what kind of gullible soul fell for those badly created phishing scams. Apparently, it's reformed ex-cons. Tell you what, roll back some of that reformation and take another look at those e-mail.
However, that's impossible, because we have an internal document-retrieving website that uses links to documents on our network file servers.
Heh, I heard that argument the first time back in 1998. My response was to make the internal website link to the documents through the webserver instead of directly:
where Path is mapped from the filestore to the internal webserver, ie the webserver sees the filestore and serves all files to the browser.
As an additional bonus, this also works as an Extranet without having to open up Windows filesharing ports to the outside - everything is tunneled through the HTTP connection. Just add SSL and a login and you have baseline security for external access.
Triple bonus - if you give selected users write-access to the filestore, they can actually manage their own sub-websites just by adding an index.html (or Default.htm if they are so inclined) to any of their subdirectories - giving them the chance to spice their shit up if they want to add metadata not available in the document-retriever framework. This works just like the advanced folders views in WinXP, only more flexible.
Quad-damage shield - you can use this to lock-out some users [1] from the filestore so they can't access it directly - only through the web interface. It's a pretty efficient way of implementing need-to-know. Sadly, it didn't keep us from being bought by Microsoft...:-(
The potential implications are positively mammoth.
Yeah, it means we have to aim for the head when the monster-mice attack. Personally, I welcome our new genetically modified near-unkillable regenerative mice overlords.
That aside, I first thought they had made a computer mouse that generated power when moved á la regenerative braking in electrical cars.
Yeah, but apart from that, did it work out for you? Don't hold back, I can take the truth.
Daily trivia: In Sweden, PriceWaterhouseCoopers have merged with Öhrlings Reveko and thankfully they 'only' answer ÖhrlingsPriceWaterhouseCoopers on the phone. But the logo looks hilarious and their newspaper ads don't have much room for anything else. :-)
I say, give the damned seal his fish ration and be done with it.
Every time we masturbate, God kills slashdot while small sites and kittens watch?
*fade in the chorus of "Oh, Tanenbaum"*
I got one of those and I second the recommendation. Just remember to don't keep the zippers up top. Pull them down one side instead. How I know.
OK, so I just got up, but still!
Just being American is a disability in it's own right.
I use Gandi. www.gandi.net - easy to use online management, reliable warnings for 30, 15, 1 and 0 days before a domain expires. 12 EUR/year. I've been using them since 2001 with no complaints or problems whatsoever.
Well, can you prove that you're a person? :-)
YOU need a better admin. "close to" 99% is major suckage for an enterprise system and would simply not be acceptable in any major setting. Hell, I was part of a group that built 99.999% uptime servers on Windows NT 4 back in 1998. And THAT was an uphill battle convincing large mobile phone telcos to switch from UNIX where they typically had *zero* downtime. If we had 99% uptime we'd been dead and gone looong before MS bought us.
One reboot later and the server is back in production. Hell? Not more than applying a patch for any other OS.
Um, you really have no idea how to manage a real enterprise class system, do you? Very, very few patches in the UNIX world need full system reboots. The vast majority of them merely require restarting the affected application since they are not integrated into the OS in interesting and illegal ways but kept separate from the kernel.
Hell, I currently run a dinky little one-man webhosting and consulting biz on the side with no hotswap server redundancy and *I* have way better than 99% uptime since I switched from Win2k on the servers to Linux. Only downtime I have had the last four years has been planned downtime for hardware upgrades (mostly adding disk to the fileserver) which is maybe all of ten minutes per year, total. When I ran Win2k, the fucker had to be constantly rebooted after patches, hung spontaneously sometimes just for fun and finally ate my file system. That's when I switched and I have never looked back.
How much is that in VW Beetles?
- You're a gargoyle.
Google - Collecting people
Especially as it's the heatpipe for the CPU cooler. :-)
To lock the XML schema and force upgrades to Office 13, starring Tom Hanks.
I hope you're right. I'd hate for anyone to take those phishing messages seriously...
And this customer chooses OpenDocument, an XML schema. So, it would appear that either MS Office or Microsoft is not flexible enough to actually "support any XML schemas that a customer chooses". Microsoft spokesman lying through his teeth, sun rises, sun sets, film at eleven.
Hook, line, sinker and a lifetime subscription to Field and Stream. I was wondering what kind of gullible soul fell for those badly created phishing scams. Apparently, it's reformed ex-cons. Tell you what, roll back some of that reformation and take another look at those e-mail.
Well, if you don't have a link template somewhere, then write a script.
Sure. Ever heard of a small place called "Europe"?
Heh, I heard that argument the first time back in 1998. My response was to make the internal website link to the documents through the webserver instead of directly:
<A HREF="\\SERVER\Path\Document.doc">linked document</A>
becomes
<A HREF="/Path/Document.doc">linked document</A>
where Path is mapped from the filestore to the internal webserver, ie the webserver sees the filestore and serves all files to the browser.
As an additional bonus, this also works as an Extranet without having to open up Windows filesharing ports to the outside - everything is tunneled through the HTTP connection. Just add SSL and a login and you have baseline security for external access.
Triple bonus - if you give selected users write-access to the filestore, they can actually manage their own sub-websites just by adding an index.html (or Default.htm if they are so inclined) to any of their subdirectories - giving them the chance to spice their shit up if they want to add metadata not available in the document-retriever framework. This works just like the advanced folders views in WinXP, only more flexible.
Quad-damage shield - you can use this to lock-out some users [1] from the filestore so they can't access it directly - only through the web interface. It's a pretty efficient way of implementing need-to-know. Sadly, it didn't keep us from being bought by Microsoft... :-(
[1] Like Sales & Marketing.
Yeah, it means we have to aim for the head when the monster-mice attack. Personally, I welcome our new genetically modified near-unkillable regenerative mice overlords.
That aside, I first thought they had made a computer mouse that generated power when moved á la regenerative braking in electrical cars.
If anyone asks, you didn't get it from me. :-/
<FONT SIZE="-10" FACE="flyspeck">
This web site is not<BR>
</FONT>
<FONT SIZE="+5"><B>
THE OFFICIAL WEB SITE OF THE 2012 LONDON OLYMPICS
</FONT></B>
Maybe put a BLINK tag in there too, for good measure. :-)