It's just like the CxO of (I forget which telco) who said basically, "Why in the world would you expect your cellphone to work in your house?"
He's essentially clueless. Google, Yahoo et al. already do pay for the 'pipes'. They pay someone (or probably multiple someones) for their upstream bandwidth, who in turn will be paying their upstream, or in the case that they are tier-1, will own and will have paid for the infrastructure anyway. No one is getting to use the 'pipes' for free. The guy just doesn't have a clue, that's all.
Virtually no manpower. The only manpower needed will be to delete the DNS entries of those who are out of compliance.
HTML/XHTML validators already exist. A simple script that periodically validates all sites, and automatically emails the technical contact for any out of compliance site is needed - and eventually tells the.mobi administrators if it remains out of compliance outside of a given period. Or perhaps automatically drops the DNS entries for the domain.
Dunno whether you've been in any older tunnels recently, but typically, they are lit by low pressure sodium lights that are very close together - typically less than 3 feet apart.
India is bigger population wise than the USA and the European Union put together. Indians might be asking the same question of Hollywood, and why Bollywood has been named after it.
There wasn't a great (percentage-wise) increase in the price of crude due to Katrina, but there _was_ an increase - it caused oil to hit a record price of over $70/bbl.
For me it was because I wanted a Unix-like OS on my PC. Why not *BSD then? Well, in January 1992, *BSD wasn't available at any price a teenager could afford.
But Linux was, however barebones it was. Unlike DOS, there was no 640K limit on the early release 80386 machine with 2.5MB of RAM I bought cheap from a mail order house selling surplus computers (this was the early 80386, complete with bugs). Instead of all the nastiness of DOS/Windows 3.0, it was a nice, smooth flat memory model. With a proper VMM. Demand page loading. Etc. In January 1992, you had a boot floppy and a root floppy. To install this "distro", after making your hard drive partition, you just did a cp -a from the root floppy to the root of the hard drive. Then you used a hex editor to modify a couple of bytes on the boot floppy to tell it the root device was the hard disk. There was no LILO - it couldn't actually completely boot strap from a hard disk, you still needed to put the kernel on a floppy!
But it was a real *nix like system on my PC with many of the limitations of DOS gone. Very quickly it gained LILO, a proper init/getty/login and a TCP/IP stack (before Microsoft even had heard of the Internet). The NET1 TCP/IP stack was *extremely* basic - it could only work on a/24 subnet, but it worked. Since then, Linux has gone from strength to strength.
I learned C on that machine. In 1993, when I upgraded to a '486 with a whopping 80MB drive, I could install X as well - and learned all about Xlib. I wrote a media player on that 486 for playing Amiga MODs (basically a pure Xlib based playlist editor, complete with a VU meter for visualisation!) Wish I still had the source. In 1993, a 486 with 16MB of RAM could compile the kernel _under X_ without touching swap. I used that machine to learn about sockets, C++, NFS and all sorts of things that would have cost me thousands I didn't have in the proprietary world. My humble 486 was better than the Solbourne S4000 (Sun compatible) workstations at university that cost an order of magnitude more money!
I have had Linux on my PCs ever since because I like it. I've usually also had a Windows partition too, but a couple of years ago, I realised that I was only booting Windows once every three months and decided to blow it away when I got the then new Fedora Core 2.
Currently, my home is home to three architectures and three operating systems. I have a 333MHz UltraSPARC system running OpenBSD, a PowerBook running OS X and an Intel PC running Fedora Core. Linux still gives me the freedom to tinker - that's why I like it.
Actually, had the supply of _crude_ stayed the same, removing refineries would cause a _fall_ in demand for crude and a fall in the price of crude. Refineries consume crude and output refined products like diesel. Shortages in refining capacity will not push the price of crude up.
Why Katrina pushed the price of crude up was nothing to do with refineries in the NO area, but the drilling platforms in the Gulf.
That comparison is only valid if you're going to keep the CPU on your Sun V240 pegged at 100% for a year. Realistically, if your V240 is depreciated over a period of 3 years (quite common for computers) you'll need to keep the CPUs pegged at 100% for at least 6 months of these 3 years to get a better TCO (on just the hardware).
Especially if you need the power of a 300-machine cluster - then figure out the cost of the HVAC, depreciation of the HVAC, cost of the building to house it...the list goes on. If you just need a big cluster for a few weeks of processing, it really doesn't make sense to do it yourself.
There never will be a fatality free Oshkosh. TWENTY FIVE THOUSAND aircraft show up typically. It doesn't matter whether they are piloted by 100-hour private pilots or airline pilots - with that number of aircraft movements there are, you'll get the odd crash.
That doesn't mean the Oshkosh is a bad thing or that it should be banned. There are risks in life. It is exceedingly rare that an Oshkosh-related incident affects someone on the ground (such as the results of a mid-air collision landing on someone's house). It's not caused by the 'experimental, amateur built' status of *some* of the planes (a very large proportion, probably at least 50% of the aircraft are factory made, FAA certified aircraft - and the accidents that do happen are not limited to home builts).
Once a home built has flown off its initial 25 hour (or 50 hour depending on requirements) test period, most types have the same level of safety as FAA certificated aircraft.
Theory of corporations
on
Ma Bell is Back
·
· Score: 4, Insightful
It's sort of a bit like the opposite of the Big Bang really. You take a giant corporation, break it up into lots of little ones, and eventually it gravitationally collapses back into the original giant corporation (and gets broken up, rinse, lather repeat). I bet if they re-broke AT&T again tomorrow, in 20 years it will have re-formed, just like the Bad Terminator from Terminator 2.
Although the sharpness of a modern LCD monitor is better than my 21in Sony Trinitron monitor at home, overall, the Trinitron has them beat. Not just because the colours are better - but also that they don't change if you move your head or change your seating position, or adjust the monitor stand! The rather nice LCD I have at work - this Slashdot section here, if I move my head to the side, the background on the comment titles all but disappears, and the brightness changes. This is inherent in the way LCDs work.
I'll see your SLS and raise it a root and boot floppy (with hex editing the boot floppy to make it mount root off the hard drive). Installation of this, erm, 'distro' was to just essentially cp -r the root floppy to the newly made filesystem on the hard drive. This was in January 1992. The kernel version IIRC was 0.12.
I write code in vi (well vim). Actually, I went the other way - I started out in an IDE, found it got in the way (on the particular project we were using) and switched to vim. It supported things like regexps too, which the IDE didn't.
You can supress that warning trivially as well (and I think that the gcc people have decided not to deprecate #import any more anyway). That warning is supressed in Oolite-Linux since it's all Objective C making liberal use of #import.
It seems like lots of IDEs are bloated in the extreme, not just VS. I used to use IBM VisualAge. We actually started calling it TakesanAge because it just used up so much memory and made the machine thrash. (And when we moved from OS/2 to NT, we needed TWICE the memory to work on the same program!)
Why can't they provide OpenSSH? It's BSD licensed. Everyone uses it now (no one uses Kerberos+Telnet), it works well, it has good features. The best we can get at the moment Windows-wise is the OpenSSH installer which contains just enough cygwin to make it work - it's OK, but things like tab and the command history don't work with the Windows CLI, which is a minor annoyance. I'd love to see OpenSSH properly integrated into Windows (and not in an embrace/extend/extinguish manner - just integrated so it does what it does elsewhere). I wouldn't advocate turning it on by default, but having it in the standard install where the administrator can just switch it on.
There's no point spoofing your identity: any hacks/scripts/worms etc. do NOT check it - they try the exploit regardless of what the server reports itself as. That's why your Apache log (which is reporting itself as Apache) is full of attempted IIS exploits. Skript kiddies and worms _do not check_.
It really depends on who you work for - whether you work for the micromanaging type who hires IT specialists then micromanages them (rather than letting them get on with what they are paid to do, and him getting on with what he's paid to do) or whether you work somewhere which actually allows you to use your hard earned experience.
Change DOES need to be managed. Systems MUST be planned. However, in my situation, that's what *I*'m paid to do. Fortunately, I work for people who trust my judgement. That has meant we have saved significant amounts of money on hardware and licensing (for example, using OpenBSD instead of CheckPoint - CheckPoint is software that is rented at great expense. The savings by using OpenBSD on the firewall paid for the hardware in less than one year).
But some of it is just do it. When I'm talking about 'just do it' - allowing part of the business to expand by having IT facilitate this expansion, rather than retard it (by waiting on lengthy capital expenditure proposals to go through buying a CheckPoint firewall for a new network, instead of just using OpenBSD on hardware that we already had).
They do exist. We have a Sony Vaio at work with a 10 inch screen. It truly is tiny. It doesn't lack features though - DVD-RW, Firewire, Bluetooth and wireless ethernet and a decent sized hard disk. It is expensive though - it's more expensive than my 12 inch PowerBook and it still doesn't have a metal case. (That's one of the things I like about the PowerBook - not only is it price competitive with similar form factor PC laptops, but being made out of metal I don't worry about it getting scratched or cracked in the back compartment of my $14 K-Mart back pack - which incidentally, it fits precisely, like the backpack was *made* for a PowerBook!)
My old Amstrad portable PC (not really a laptop, but neither is a laptop with a 20in display) had a fullsize standard 102-key PC keyboard when you opened it. With a 20in screen, you've certainly got the width to do it.
The other thing is, Napster (and most P2P networks) are only good at finding the popular stuff - not the indy music by small bands. Napster was completely uncategorised, so you had to know what you were searching for beforehand - there was no discovering new bands. And - people had to have it up for download - so it was doubly only good for finding popular stuff.
The classic question for bands choosing the DIY vs. record deal route (assuming they have the required talent and luck to make this choice) is "do I want most of a really tiny pie, or a little bit of a potentially very fucking huge pie?". Another way of looking at it is whether you want to sink $10K of your own money into recording, engineering, producing, promoting and selling your CD (and hoping that you sell enough to make back your investment so that you can actually make some cash), or getting a record company to spend $100K of their money (and hoping that they sell enough to make back their investment so you can actually make some cash).
Ah. I see where you've gone wrong, and it probably suckers most artists too. It's actually a choice of sinking $10K of your own money into a recording et al., or getting a record company to sink $100K of your own money into the recording with the hope you make enough cash to actually pay it back. (And you lose your rights to your own work). Record companies don't give you studio time - they lend you money so you can pay for it yourselves, often at an inflated rate. They call it an 'advance', but you still must pay it back, so you probably won't actually start earning money until you've sold over 1 million CDs.
It's just like the CxO of (I forget which telco) who said basically, "Why in the world would you expect your cellphone to work in your house?"
He's essentially clueless. Google, Yahoo et al. already do pay for the 'pipes'. They pay someone (or probably multiple someones) for their upstream bandwidth, who in turn will be paying their upstream, or in the case that they are tier-1, will own and will have paid for the infrastructure anyway. No one is getting to use the 'pipes' for free. The guy just doesn't have a clue, that's all.
Virtually no manpower. The only manpower needed will be to delete the DNS entries of those who are out of compliance.
.mobi administrators if it remains out of compliance outside of a given period. Or perhaps automatically drops the DNS entries for the domain.
HTML/XHTML validators already exist. A simple script that periodically validates all sites, and automatically emails the technical contact for any out of compliance site is needed - and eventually tells the
That first link is 404 - Not found.
Dunno whether you've been in any older tunnels recently, but typically, they are lit by low pressure sodium lights that are very close together - typically less than 3 feet apart.
India is bigger population wise than the USA and the European Union put together. Indians might be asking the same question of Hollywood, and why Bollywood has been named after it.
FFS, *please* stop saying that awful marketing speak buzzword BLOGOSPHERE. Gah.
There wasn't a great (percentage-wise) increase in the price of crude due to Katrina, but there _was_ an increase - it caused oil to hit a record price of over $70/bbl.
For me it was because I wanted a Unix-like OS on my PC. Why not *BSD then? Well, in January 1992, *BSD wasn't available at any price a teenager could afford.
/24 subnet, but it worked. Since then, Linux has gone from strength to strength.
But Linux was, however barebones it was. Unlike DOS, there was no 640K limit on the early release 80386 machine with 2.5MB of RAM I bought cheap from a mail order house selling surplus computers (this was the early 80386, complete with bugs). Instead of all the nastiness of DOS/Windows 3.0, it was a nice, smooth flat memory model. With a proper VMM. Demand page loading. Etc. In January 1992, you had a boot floppy and a root floppy. To install this "distro", after making your hard drive partition, you just did a cp -a from the root floppy to the root of the hard drive. Then you used a hex editor to modify a couple of bytes on the boot floppy to tell it the root device was the hard disk. There was no LILO - it couldn't actually completely boot strap from a hard disk, you still needed to put the kernel on a floppy!
But it was a real *nix like system on my PC with many of the limitations of DOS gone. Very quickly it gained LILO, a proper init/getty/login and a TCP/IP stack (before Microsoft even had heard of the Internet). The NET1 TCP/IP stack was *extremely* basic - it could only work on a
I learned C on that machine. In 1993, when I upgraded to a '486 with a whopping 80MB drive, I could install X as well - and learned all about Xlib. I wrote a media player on that 486 for playing Amiga MODs (basically a pure Xlib based playlist editor, complete with a VU meter for visualisation!) Wish I still had the source. In 1993, a 486 with 16MB of RAM could compile the kernel _under X_ without touching swap. I used that machine to learn about sockets, C++, NFS and all sorts of things that would have cost me thousands I didn't have in the proprietary world. My humble 486 was better than the Solbourne S4000 (Sun compatible) workstations at university that cost an order of magnitude more money!
I have had Linux on my PCs ever since because I like it. I've usually also had a Windows partition too, but a couple of years ago, I realised that I was only booting Windows once every three months and decided to blow it away when I got the then new Fedora Core 2.
Currently, my home is home to three architectures and three operating systems. I have a 333MHz UltraSPARC system running OpenBSD, a PowerBook running OS X and an Intel PC running Fedora Core. Linux still gives me the freedom to tinker - that's why I like it.
Actually, had the supply of _crude_ stayed the same, removing refineries would cause a _fall_ in demand for crude and a fall in the price of crude. Refineries consume crude and output refined products like diesel. Shortages in refining capacity will not push the price of crude up.
Why Katrina pushed the price of crude up was nothing to do with refineries in the NO area, but the drilling platforms in the Gulf.
That comparison is only valid if you're going to keep the CPU on your Sun V240 pegged at 100% for a year. Realistically, if your V240 is depreciated over a period of 3 years (quite common for computers) you'll need to keep the CPUs pegged at 100% for at least 6 months of these 3 years to get a better TCO (on just the hardware).
Especially if you need the power of a 300-machine cluster - then figure out the cost of the HVAC, depreciation of the HVAC, cost of the building to house it...the list goes on. If you just need a big cluster for a few weeks of processing, it really doesn't make sense to do it yourself.
There never will be a fatality free Oshkosh. TWENTY FIVE THOUSAND aircraft show up typically. It doesn't matter whether they are piloted by 100-hour private pilots or airline pilots - with that number of aircraft movements there are, you'll get the odd crash.
That doesn't mean the Oshkosh is a bad thing or that it should be banned. There are risks in life. It is exceedingly rare that an Oshkosh-related incident affects someone on the ground (such as the results of a mid-air collision landing on someone's house). It's not caused by the 'experimental, amateur built' status of *some* of the planes (a very large proportion, probably at least 50% of the aircraft are factory made, FAA certified aircraft - and the accidents that do happen are not limited to home builts).
Once a home built has flown off its initial 25 hour (or 50 hour depending on requirements) test period, most types have the same level of safety as FAA certificated aircraft.
It's sort of a bit like the opposite of the Big Bang really. You take a giant corporation, break it up into lots of little ones, and eventually it gravitationally collapses back into the original giant corporation (and gets broken up, rinse, lather repeat). I bet if they re-broke AT&T again tomorrow, in 20 years it will have re-formed, just like the Bad Terminator from Terminator 2.
Although the sharpness of a modern LCD monitor is better than my 21in Sony Trinitron monitor at home, overall, the Trinitron has them beat. Not just because the colours are better - but also that they don't change if you move your head or change your seating position, or adjust the monitor stand! The rather nice LCD I have at work - this Slashdot section here, if I move my head to the side, the background on the comment titles all but disappears, and the brightness changes. This is inherent in the way LCDs work.
I'll see your SLS and raise it a root and boot floppy (with hex editing the boot floppy to make it mount root off the hard drive). Installation of this, erm, 'distro' was to just essentially cp -r the root floppy to the newly made filesystem on the hard drive. This was in January 1992. The kernel version IIRC was 0.12.
I write code in vi (well vim). Actually, I went the other way - I started out in an IDE, found it got in the way (on the particular project we were using) and switched to vim. It supported things like regexps too, which the IDE didn't.
You can supress that warning trivially as well (and I think that the gcc people have decided not to deprecate #import any more anyway). That warning is supressed in Oolite-Linux since it's all Objective C making liberal use of #import.
It seems like lots of IDEs are bloated in the extreme, not just VS. I used to use IBM VisualAge. We actually started calling it TakesanAge because it just used up so much memory and made the machine thrash. (And when we moved from OS/2 to NT, we needed TWICE the memory to work on the same program!)
Why can't they provide OpenSSH? It's BSD licensed. Everyone uses it now (no one uses Kerberos+Telnet), it works well, it has good features. The best we can get at the moment Windows-wise is the OpenSSH installer which contains just enough cygwin to make it work - it's OK, but things like tab and the command history don't work with the Windows CLI, which is a minor annoyance. I'd love to see OpenSSH properly integrated into Windows (and not in an embrace/extend/extinguish manner - just integrated so it does what it does elsewhere). I wouldn't advocate turning it on by default, but having it in the standard install where the administrator can just switch it on.
There's no point spoofing your identity: any hacks/scripts/worms etc. do NOT check it - they try the exploit regardless of what the server reports itself as. That's why your Apache log (which is reporting itself as Apache) is full of attempted IIS exploits. Skript kiddies and worms _do not check_.
It really depends on who you work for - whether you work for the micromanaging type who hires IT specialists then micromanages them (rather than letting them get on with what they are paid to do, and him getting on with what he's paid to do) or whether you work somewhere which actually allows you to use your hard earned experience.
Change DOES need to be managed. Systems MUST be planned. However, in my situation, that's what *I*'m paid to do. Fortunately, I work for people who trust my judgement. That has meant we have saved significant amounts of money on hardware and licensing (for example, using OpenBSD instead of CheckPoint - CheckPoint is software that is rented at great expense. The savings by using OpenBSD on the firewall paid for the hardware in less than one year).
But some of it is just do it. When I'm talking about 'just do it' - allowing part of the business to expand by having IT facilitate this expansion, rather than retard it (by waiting on lengthy capital expenditure proposals to go through buying a CheckPoint firewall for a new network, instead of just using OpenBSD on hardware that we already had).
They do exist. We have a Sony Vaio at work with a 10 inch screen. It truly is tiny. It doesn't lack features though - DVD-RW, Firewire, Bluetooth and wireless ethernet and a decent sized hard disk. It is expensive though - it's more expensive than my 12 inch PowerBook and it still doesn't have a metal case. (That's one of the things I like about the PowerBook - not only is it price competitive with similar form factor PC laptops, but being made out of metal I don't worry about it getting scratched or cracked in the back compartment of my $14 K-Mart back pack - which incidentally, it fits precisely, like the backpack was *made* for a PowerBook!)
My old Amstrad portable PC (not really a laptop, but neither is a laptop with a 20in display) had a fullsize standard 102-key PC keyboard when you opened it. With a 20in screen, you've certainly got the width to do it.
The IT world was full of sub-par staff even in the dot bomb days (possibly even more so).
The other thing is, Napster (and most P2P networks) are only good at finding the popular stuff - not the indy music by small bands. Napster was completely uncategorised, so you had to know what you were searching for beforehand - there was no discovering new bands. And - people had to have it up for download - so it was doubly only good for finding popular stuff.
Ah. I see where you've gone wrong, and it probably suckers most artists too. It's actually a choice of sinking $10K of your own money into a recording et al., or getting a record company to sink $100K of your own money into the recording with the hope you make enough cash to actually pay it back. (And you lose your rights to your own work). Record companies don't give you studio time - they lend you money so you can pay for it yourselves, often at an inflated rate. They call it an 'advance', but you still must pay it back, so you probably won't actually start earning money until you've sold over 1 million CDs.