I haven't looked at ESXi in depth. The biggest missing component I see is the lack of a service console--no command line. I have a few Dell 2550(?) that for some reason have CDrom issues that I need console access for.
It looks like you have plenty of time to install ESXi and play with it. As long as your virtual servers aren't resource hogs, you can save bundles in hardware. If you step up to ESX and Virtual Ifrastructure, you can manage all your VM's through a single server. You can move, with VMotion VM's from one hypervisor to another (running, if they are using the same SAN), take snapshots (and restore!) of running machines live. virtualizaiton makes your life so much easier.
The part you are missing is that with paper, you can, and often do, pick it up and hold it at an angle that makes it easier to read. Easier on your eyes and easier in your upper body. For that matter, talk a tour through any research library and you will see people propping up the book they are reading against a stack of other books.
Don't believe me? Do this, for one week, everything you read must be horizontal and perpendicular to your body. Come back after that week and let us know how you feel.
We've had that for ten goddamn years. It is called apt.
For Debian, but what about the rest of the world? Well, they use Yum or some other front end to RPM. Now, what does RPM do? package stuff up into directories. Gee, how is that defined? By the developers! Is there a common code of conduct (again, I don't know) for packaging apps? When do you put files into/etc or/usr/etc? Then there is the famous/lib//etc What about the apps? Do they go in/usr,/usr/bin,/usr/sbin,/usr/local, or what about/opt? Hey, what about logs? Under/var? Shared libraries? Under/lib,/lib/,/usr/lib,/usr/local/lib? Now for Gui apps, where do icons end up in the menu system? Not all apps show up in the right place. Where are docs saved? What about config options.
Yeah, because application developers for Windows are sooo conscientious about coding to desktop standards.
A fine example of fallacious reasoning. Just because a group doesn't do something doesn't mean others shouldn't. Your response is also a prime example of why zealotry is worse for the cause. You bring up a tiny world view, Debian, as the way it should be, rather than acknowledging what is.
Do other OS's have similar problems, yes, but we aren't talking about other OS's. We are talking about Linux
What makes Windows and OSX more popular than Linux is the same reason why Java is more popular than Python or Ruby, it's corporate sponsorship.
Nope. Not even close. How are these for corporate sponsors: Redhat, Novell, Sun.
What makes Windows and OSX so popular are applications that are commercially supported. That's it. Look no further. Without applications, your OS, no matter how fancy, is useless. I rememeber when I got my first computer, I turned it on to see C:\>. It was useless to me without apps that I could use (I was also introduced to warez that day).
Now, I know that there are alot of apps for Linux, but the installation and use of them are not as seamless as those for Windows or OSX. What I would like to see, and perhaps this is already available, is a set of agreed upon application practices, written by distribution maintainers, that developers follow that standardize the interface, the population of the OS menus, the distribution of files, etc, so that it app installs are seamless. Yes, it would be a PITA to support each distribution of OS, but quite frankly, that could be automated. And then have app developers actually follow the guidelines.
That would go along way to streamlining apps in Linux.
I have FiOS with the actiontec router and all you need is the password and you can tweak whatever you want. Verizon is actually pretty good about letting you manage your the router they supply. Of course, of you hork it, they tell to to reboot to factory defaults.:)
Re: the GP and not getting good tech support. When they first starting doing this, I followed the help, and it didn't work. I called tech support, the guy I talked to argued with me that 1) Verizon does mess with DNS and 2) I had a virus. Idiot.
for a small business owner, why not. I manage a few websites. Very, very small. Less than 20 people have write access. They wanted email. some users would use outlook or outlook express, others wanted a web mail front end. The email client the hosting service had was horrible so I hooked them up with a gmail hosted services. It works very, very nicely for them.
there are some cases where Google is a good alternative to other options.
1) It's a bug in many platforms 2) It's the exact same bug in many platforms (design bugs, they are a pain) " How is this not the same flaw DJB described?
You are looking at two separate issues. The flaw Kaminsky found is apparently a newly discovered design flaw that makes DNS forging easy even with todays, unpatched DNS servers. In the advisory, they discussed previous problems with generating the transactionID to explain the problem and point out that what Dan found is not something already known (alot of people missed that very obvious point).
The second seperate, issue is UDP source port randomization. That is what Kaminsky was referring to DJB's solution. Kaminsky's assertion is that UDP source port is a good development practice which DJB incorporated into his DNS server.
Bear in mind that UDP source port generation doesn't solve the underlying problem, it simply makes blind DNS forging more difficult because now an attacker has to guess both a pseudo random transaction ID and a pseudo random UDP source port number. Alot of DNS servers and OS, simply picked source port numbers incrementally or in the case of a DNS server, re-used the some one over and over.
I don't know hom much more difficult DNS forging will be by randomizing the UDP source port numbers. The additional keyspace is (2^16-1023) and you can probably divide that in half again. But it's better then nothing and probably provides enough time (the time it would take an attacker to blindly guess the transactionID and UDP source port number) for the actual response to hit the DNS server. In DNS, the first response wins.
Listen to yourself, arth1. So if said user connects to uber-secret network, surfs to a web site his choosing, his IP is dutifully logged in the web server logs and the users cookie is logged in the app. So now the owner of the website is liable for having that IP?
Not likely. 1) traceroute is NOT hacker activity. It is a function of a properly working network stack. 2) if the user is connected to uber-secret network and htat network is in the reserved address space (rfc 1918), then the IP doens't matter. What does matter is the need to have one public IP addresses to track, hence the need for a traceroute. 3) traceroute only traces one path out. It does not "map the internal network."
Hell, I'd do it and laugh at anyone who wanted to charge me.
The advisory indicated two different scenarios and discussed specifically that section 2.2 (the advisory did not call it out by name). the flaw Kaminsky found he claims, is still possible even while addressing transaction ID guessing.
Its a problem in the protocol. So the only systems that would not be vulnerable are those that did -not- follow the specs. Guess Windows is safe, since Microsoft never follows the specs:)
I know you meant that to be funny, but the truth is, is that the "fix" that is being deployed is to randomize UDP port numbers. We will have to wait until August 6th to find out what the exploit is all about.
Somebody post a copy of Windows XP: I want to memorialize and preserve it, and I'd like to launch a discussion about how MS should continue to sell and support XP.
I guess what I'm saying is, as nice as these Fair Use guidelines are, they're only as good as the lawyers that fight for them and the deep pockets that will fund them.
The part you are missing is the limiations. From teh TFA: Fair use reaches its limits when the entertainment content is reproduced in amounts that are disproportionate to purposes of documentation, or in the case of archiving, when the material is readily available from authorized sources.
If you post full copy of XP, you are clearly violating the limitations. An overriding theme of teh guidelines is to copy enough of the original content (and cite it) to make your point.
Also, there are better ways to memorilaze the XP experience like screen shots, screen movies, etc.
But when you transcribe tab, you're not adding any new content. You're just translating from one form to another. The translation process may be difficult and require skill, but it's still not a creative process. I'd like to think tab sites were legal; I used to use them quite a bit myself. But realistically, I can't see how they would be.
Depends on the tab. A tab can be a faithful reproduction of the song, or it can be an interpretation of the song. I think the latter has a better chance of being "fair use" than the former.
Yeah, that's a problem in the US. There are still places
that are remote enough that cell coverage doesn't exist
and you're lucky enough to have running water. You can't
use GPS to find it because none of the GPS navigation
systems know how to get there.
That is a problem with Russia as well. And Canada. And China. And any country that isn't nut-to-butt people.
and to be clear, the reason why you "don't get GPS" is because either your mapping software doesn't have a map for where you are standing or because you don't have a clear view of the sky.
There is *nothing* special about dial-up users that makes them more or less prone to attack. Nothing, nada, zip. It's an IP connection just like broadband with the limitation of 33.6 Kbps and 56Kbps down. Period.
And no, having a modem attached to your computer does not mean anyone can dial-in. You need to have software running that will 1) answer the phone and 2) enable the modem to make the connection. The problem is that people would put remote control software on their computers which would answer the phone by design, and therein lies the problem.
I hate loud typers. I worked with a guy that would wail on his keyboard. He went through a series of Dell quiet keys, but when he typed, and he was fast, it sounded like he was shooting a machine gun. It was truly distracting.
We have two dogs and two cats. We finally broke down and bought a Dyson Animal a few years ago. A bit over $450. Seems pretty extravagant at the time. But it works extremely well, picks up all the dog hair and other crap.
It is not good on throw rugs because it tends to lift them, so you have to be careful.
And yet, barely anyone gives a second thought to tuning their radio while driving or talking to a passenger while driving - both things that are shown to create just as much of a distraction.
You young-uns. Back in the late 70's/early 80's, there was an explosion in the car audio market. A slew of components from EQ's, amps, cross-overs, speakers, and decks were flooding audio shops. And the prices were coming down on decks with cassette players.
There was out-cry back then about the danger of people being distracted with finding cassettes, fast forwarding and rewinding, any playing with the knobs.
In the 90's when car stereos with CD players became common, there was outcry about people swapping CD's and not paying attention to the road.
Today, every time I start my car, I have to "agree" to pay attention to the road while driving because my vehicle has an on-dash read-out (car stats, GPS, etc).
When I used to be on the road alot, I say people applying make-up, reading the news paper, eating lunch, checking a computer--pretty much doing anything other than driving.
People get too comfortable and don't expect the accident to happen to them. When it does, they are shocked.
It's more than that. It mandates a first step toward IPv6 conversion. The mandate also stated that dual stack (running Ipv4 along with IPv6) was OK too. The fundamental problem is that all the other network devices that run only IPv4 still have to supported.
This is fundamentally no different than when companies had to run IP and IPX on computers during Novells transition in the 90's.
I manage a blog where most of the users are authors and they are not technical folks that might visit a site like pcpro on a regular basis. You might say they are average folk.
In the last few months, I have been seeing an increase in firefox from maybe 10% in January to close to 45% today. Of that 45% of FF users, 23% are already using FF3. I think that is pretty impressive. By comparison, 52% use IE and the majority of them, 67% use IE7.
Slashdot Mirror
The first book I ever read was "Childhoods End.", I think I was 8. a truly memorable read.
I am curious, what would you need firewire support for? Are you talking firewire for servers or workstations?
You can find a FAQ.
I haven't looked at ESXi in depth. The biggest missing component I see is the lack of a service console--no command line. I have a few Dell 2550(?) that for some reason have CDrom issues that I need console access for.
It looks like you have plenty of time to install ESXi and play with it. As long as your virtual servers aren't resource hogs, you can save bundles in hardware. If you step up to ESX and Virtual Ifrastructure, you can manage all your VM's through a single server. You can move, with VMotion VM's from one hypervisor to another (running, if they are using the same SAN), take snapshots (and restore!) of running machines live. virtualizaiton makes your life so much easier.
Guess I am a bit of a fan-boi.
Bugger. My Verizon DNS servers have great TXID randomness and poor source port randomness.
The part you are missing is that with paper, you can, and often do, pick it up and hold it at an angle that makes it easier to read. Easier on your eyes and easier in your upper body. For that matter, talk a tour through any research library and you will see people propping up the book they are reading against a stack of other books.
Don't believe me? Do this, for one week, everything you read must be horizontal and perpendicular to your body. Come back after that week and let us know how you feel.
We've had that for ten goddamn years. It is called apt.
/etc or /usr/etc? Then there is the famous /lib//etc What about the apps? Do they go in /usr, /usr/bin, /usr/sbin, /usr/local, or what about /opt? Hey, what about logs? Under /var? Shared libraries? Under /lib, /lib/, /usr/lib, /usr/local/lib? Now for Gui apps, where do icons end up in the menu system? Not all apps show up in the right place. Where are docs saved? What about config options.
For Debian, but what about the rest of the world? Well, they use Yum or some other front end to RPM. Now, what does RPM do? package stuff up into directories. Gee, how is that defined? By the developers! Is there a common code of conduct (again, I don't know) for packaging apps? When do you put files into
Yeah, because application developers for Windows are sooo conscientious about coding to desktop standards.
A fine example of fallacious reasoning. Just because a group doesn't do something doesn't mean others shouldn't. Your response is also a prime example of why zealotry is worse for the cause. You bring up a tiny world view, Debian, as the way it should be, rather than acknowledging what is.
Do other OS's have similar problems, yes, but we aren't talking about other OS's. We are talking about Linux
What makes Windows and OSX more popular than Linux is the same reason why Java is more popular than Python or Ruby, it's corporate sponsorship.
Nope. Not even close. How are these for corporate sponsors: Redhat, Novell, Sun.
What makes Windows and OSX so popular are applications that are commercially supported. That's it. Look no further. Without applications, your OS, no matter how fancy, is useless. I rememeber when I got my first computer, I turned it on to see C:\>. It was useless to me without apps that I could use (I was also introduced to warez that day).
Now, I know that there are alot of apps for Linux, but the installation and use of them are not as seamless as those for Windows or OSX. What I would like to see, and perhaps this is already available, is a set of agreed upon application practices, written by distribution maintainers, that developers follow that standardize the interface, the population of the OS menus, the distribution of files, etc, so that it app installs are seamless. Yes, it would be a PITA to support each distribution of OS, but quite frankly, that could be automated. And then have app developers actually follow the guidelines.
That would go along way to streamlining apps in Linux.
I have FiOS with the actiontec router and all you need is the password and you can tweak whatever you want. Verizon is actually pretty good about letting you manage your the router they supply. Of course, of you hork it, they tell to to reboot to factory defaults. :)
Re: the GP and not getting good tech support. When they first starting doing this, I followed the help, and it didn't work. I called tech support, the guy I talked to argued with me that 1) Verizon does mess with DNS and 2) I had a virus. Idiot.
for a small business owner, why not. I manage a few websites. Very, very small. Less than 20 people have write access. They wanted email. some users would use outlook or outlook express, others wanted a web mail front end. The email client the hosting service had was horrible so I hooked them up with a gmail hosted services. It works very, very nicely for them.
there are some cases where Google is a good alternative to other options.
1) It's a bug in many platforms 2) It's the exact same bug in many platforms (design bugs, they are a pain) " How is this not the same flaw DJB described?
You are looking at two separate issues. The flaw Kaminsky found is apparently a newly discovered design flaw that makes DNS forging easy even with todays, unpatched DNS servers. In the advisory, they discussed previous problems with generating the transactionID to explain the problem and point out that what Dan found is not something already known (alot of people missed that very obvious point).
The second seperate, issue is UDP source port randomization. That is what Kaminsky was referring to DJB's solution. Kaminsky's assertion is that UDP source port is a good development practice which DJB incorporated into his DNS server.
Bear in mind that UDP source port generation doesn't solve the underlying problem, it simply makes blind DNS forging more difficult because now an attacker has to guess both a pseudo random transaction ID and a pseudo random UDP source port number. Alot of DNS servers and OS, simply picked source port numbers incrementally or in the case of a DNS server, re-used the some one over and over.
I don't know hom much more difficult DNS forging will be by randomizing the UDP source port numbers. The additional keyspace is (2^16-1023) and you can probably divide that in half again. But it's better then nothing and probably provides enough time (the time it would take an attacker to blindly guess the transactionID and UDP source port number) for the actual response to hit the DNS server. In DNS, the first response wins.
this article at information week said it best the day after the announcement.
Geez, if you want responsible disclosure, you have to trust the experts when they say "it's new and it's bad"
Listen to yourself, arth1. So if said user connects to uber-secret network, surfs to a web site his choosing, his IP is dutifully logged in the web server logs and the users cookie is logged in the app. So now the owner of the website is liable for having that IP?
Not likely. 1) traceroute is NOT hacker activity. It is a function of a properly working network stack. 2) if the user is connected to uber-secret network and htat network is in the reserved address space (rfc 1918), then the IP doens't matter. What does matter is the need to have one public IP addresses to track, hence the need for a traceroute. 3) traceroute only traces one path out. It does not "map the internal network."
Hell, I'd do it and laugh at anyone who wanted to charge me.
A bare island. Whoda thunk it?
The advisory indicated two different scenarios and discussed specifically that section 2.2 (the advisory did not call it out by name). the flaw Kaminsky found he claims, is still possible even while addressing transaction ID guessing.
Its a problem in the protocol. So the only systems that would not be vulnerable are those that did -not- follow the specs. Guess Windows is safe, since Microsoft never follows the specs :)
I know you meant that to be funny, but the truth is, is that the "fix" that is being deployed is to randomize UDP port numbers. We will have to wait until August 6th to find out what the exploit is all about.
Ignorance of the law does not excuse.
Somebody post a copy of Windows XP: I want to memorialize and preserve it, and I'd like to launch a discussion about how MS should continue to sell and support XP.
I guess what I'm saying is, as nice as these Fair Use guidelines are, they're only as good as the lawyers that fight for them and the deep pockets that will fund them.
The part you are missing is the limiations. From teh TFA:
Fair use reaches its limits when the entertainment content is reproduced in amounts that are disproportionate to purposes of documentation, or in the case of archiving, when the material is readily available from authorized sources.
If you post full copy of XP, you are clearly violating the limitations. An overriding theme of teh guidelines is to copy enough of the original content (and cite it) to make your point.
Also, there are better ways to memorilaze the XP experience like screen shots, screen movies, etc.
But when you transcribe tab, you're not adding any new content. You're just translating from one form to another. The translation process may be difficult and require skill, but it's still not a creative process. I'd like to think tab sites were legal; I used to use them quite a bit myself. But realistically, I can't see how they would be.
Depends on the tab. A tab can be a faithful reproduction of the song, or it can be an interpretation of the song. I think the latter has a better chance of being "fair use" than the former.
Yeah, that's a problem in the US. There are still places that are remote enough that cell coverage doesn't exist and you're lucky enough to have running water. You can't use GPS to find it because none of the GPS navigation systems know how to get there.
That is a problem with Russia as well. And Canada. And China. And any country that isn't nut-to-butt people.
and to be clear, the reason why you "don't get GPS" is because either your mapping software doesn't have a map for where you are standing or because you don't have a clear view of the sky.
There is *nothing* special about dial-up users that makes them more or less prone to attack. Nothing, nada, zip. It's an IP connection just like broadband with the limitation of 33.6 Kbps and 56Kbps down. Period.
And no, having a modem attached to your computer does not mean anyone can dial-in. You need to have software running that will 1) answer the phone and 2) enable the modem to make the connection. The problem is that people would put remote control software on their computers which would answer the phone by design, and therein lies the problem.
I hate loud typers. I worked with a guy that would wail on his keyboard. He went through a series of Dell quiet keys, but when he typed, and he was fast, it sounded like he was shooting a machine gun. It was truly distracting.
Don't buy cheap vacuums.
We have two dogs and two cats. We finally broke down and bought a Dyson Animal a few years ago. A bit over $450. Seems pretty extravagant at the time. But it works extremely well, picks up all the dog hair and other crap.
It is not good on throw rugs because it tends to lift them, so you have to be careful.
And yet, barely anyone gives a second thought to tuning their radio while driving or talking to a passenger while driving - both things that are shown to create just as much of a distraction.
You young-uns. Back in the late 70's/early 80's, there was an explosion in the car audio market. A slew of components from EQ's, amps, cross-overs, speakers, and decks were flooding audio shops. And the prices were coming down on decks with cassette players.
There was out-cry back then about the danger of people being distracted with finding cassettes, fast forwarding and rewinding, any playing with the knobs.
In the 90's when car stereos with CD players became common, there was outcry about people swapping CD's and not paying attention to the road.
Today, every time I start my car, I have to "agree" to pay attention to the road while driving because my vehicle has an on-dash read-out (car stats, GPS, etc).
When I used to be on the road alot, I say people applying make-up, reading the news paper, eating lunch, checking a computer--pretty much doing anything other than driving.
People get too comfortable and don't expect the accident to happen to them. When it does, they are shocked.
It's more than that. It mandates a first step toward IPv6 conversion. The mandate also stated that dual stack (running Ipv4 along with IPv6) was OK too. The fundamental problem is that all the other network devices that run only IPv4 still have to supported.
This is fundamentally no different than when companies had to run IP and IPX on computers during Novells transition in the 90's.
I manage a blog where most of the users are authors and they are not technical folks that might visit a site like pcpro on a regular basis. You might say they are average folk.
In the last few months, I have been seeing an increase in firefox from maybe 10% in January to close to 45% today. Of that 45% of FF users, 23% are already using FF3. I think that is pretty impressive. By comparison, 52% use IE and the majority of them, 67% use IE7.