Onderwerp: [ESXi] how to enable SSH

ESXi 3.5 does ship with the ability to run SSH, but this is disabled by default (and is not supported).

1) At the console of the ESXi host, press ALT-F1 to access the console window.
2) Enter unsupported in the console and then press Enter. You will not see the text you type in.
3) If you typed in unsupported correctly, you will see the Tech Support Mode warning and a password prompt. Enter the password for the root login.
4) You should then see the prompt of ~ #. Edit the file inetd.conf (enter the command vi /etc/inetd.conf).
5) Find the line that begins with #ssh and remove the #. Then save the file. If you're new to using vi, then move the cursor down to #ssh line and then press the Insert key. Move the cursor over one space and then hit backspace to delete the #. Then press ESC and type in :wq to save the file and exit vi. If you make a mistake, you can press the ESC key and then type it :q! to quit vi without saving the file.
6) Once you've closed the vi editor, run the command /sbin/services.sh restart to restart the management services. You'll now be able to connect to the ESXi host with a SSH client.

According to WD, if you want to upgrade to X58, a V1.1 model is required—this explains why there is still no X58 on the HCL because, according to MMC Services in Germany, the V1.1 still has not shipped. And if you have a V1.0 and want to go to X58, it's going to cost another $89 plus shipping. I'm beginning to feel nickel and dimed after a thorough price "gouging."
The USB Chameleon/EFIV10/XPC/BootThink route is looking more attractive by the day.

Yes just saw this .. what a marketing sham... how can you announce with 3.6.11 that X58 is supported when v1.1 was virtually unavailable knowing that the current install base of v1.0 was to be excluded...

Reality is that EFi-X is not needed to boot for Windows, Linux but is only really targeted for OS X - something which is available in other forms.

In some counties this is considered misleading, false advertising!!

ANd, unlike what WD would like you to believe, Efi-x is not really NEEDED to boot OS X. It's just an usb key in disguise ... you can do the same yourself with a cheap usb flash drive. Some people posted very good "HOw-To's" here for that purpose :-)

Our friend Li'l Vnukie might be running short of cash. Yes, no, maybe? He could be trying to suck in a whole new herd of users so it can be "biz as usual".

WhiteDragon "corrected" his post about only v1.1 supporting the X58 chipset, and then deleted it, stating he was just tired and forgot to mention that X58 will be supported by v1 units with a firmware update.

This directly contradicts the announcement that was made when the 3.6.11 firmware came out, which stated that X58 boards are supported, and WhiteDragon made it very clear that it was a part of the update, as it's in the update notes.

Again, I have my suspicions that he really has no idea what's going on and is just twiddling his thumbs waiting for some open-source developer to release a newer driver kext to fix issues like this and the onboard LAN problem (which we've already fixed here), so he can "borrow" them and repackage into a firmware update for a $280 product while hoping there's enough suckers who bought the first version will pay more money to upgrade to the newer version which has no real new features and fixes none of the issues customers are experiencing.

Yes .. corrected and other posts sanitized.. guess one will have to make copies of posts as they are listed before they or the thread gets deleted... it seems like the change to their new host server that the history of the v1.0 module is being erased...

If you remember not too long ago WD did have an X58 signature.. gone now, but it implied that this was all on v1.0 modules. Of course X58 runs OS X very well (without the module) and it is easy to do esp on the GB motherboards.

So they could very well be struggling esp. if their claim of 30 programmers just for EFI-X is true... they need to be feed and watered which does not come cheap even in Asia .. and I actually know what it costs in Asia.

What is also interesting is looking back over the 'independent' product reviews .. not one of them I can find actually opened up the unit itself, which is something very unusual for these reviewers - they open up all sorts of 'sealed' products - PSU, SSDs, RAM modules just to see how it ticks....

Yes, he was tired, hot and confused—can happen to anyone.
I am suspicious about this on/off X58 support of V1.0, especially in WD's signature. Every time I read posts from ASEM's spokesperson, alarm bells start ringing and the BS meter goes off the chart. It started with the price hike from $150 to $250+, etc., and now the $5 charges for LAB firmware updates, $89 to upgrade to V1.1, blah, blah. Then there was the publicity about how great V1 was (built from finest Grade-A materials) and now V1.1 is built from even better Grade-A materials. And there are still no recommended X58 boards in the HCL!
Coupled with 1 month delay in fixing the V(anishing) LAN just make me feel this is going nowhere fast. In short, V1.1 looks like a release perhaps to clear up prototype bugs in V1.0 and to raise more short-term cash. What the schedule is for V2.0 is anyone's guess.

Further to this is that the MODS are being used to shield ASEM.... for a Commercial product it has poor Product Management and no clear go to market plan.

The various versions are not really the issue, the comparison chart is ONLY about technology at a board/manufacture level and not what it can do for the User... and generally most users don't care what is inside but does it work and will it continue to work.

V1.0 is now no longer in production (according to a MOD), there is no announcement of EOL and when it will be finally not supported, product development is normal and of course expected but to have the majority of the customer base on v1.0 and be left behind so so quickly is again a reflection of their lack of strategy.

Yes .. indeed .. I think we are all missing the only important point here ... there is NO "commercial product" whatsoever, just a flash ram sealed in an epoxy package ... thus no V1, v1.1, v2 or v784-z .... still the same thing loaded with open source modules repackaged ...