Archive for September, 2012
Synology offers free webinars to help you learn more about your DiskStation. Hosted by one of our knowledgeable engineers, the webinars provide how to’s and tips on fully utilizing your product.
Have a question in regards to a webinar? Email our engineer at firstname.lastname@example.org
Webinar length: 15 minutes
DiskStation Manager 3.1
- Remote Access with the Synology DiskStation
- Why do I want to access my DiskStation Remotely?
- What is Port Forwarding?
- Notes about Port Forwarding and ISPs
- Conducting Port Forwarding with DSM’s EZ Internet
- Examples of accessing the DiskStation remotely
The earlier Samsung Galaxy Tab 7.0 tablet was given some major boost in the form of its more muscular brother—the Samsung Galaxy Tab 7.0 Plus Wi-Fi GT-P6210. This newer 7-inch tablet now boasts a faster 1.2 GHz dual-core processor, Android 3.2 Honeycomb underneath, and several system improvements.
Just like any Android device, the Galaxy Tab 7.0 Plus Wi-Fi GT-P6210 is completely rootable. We’ll not go into the nitty-gritty of the pros and cons of rooting your device, but suffice it to say that root access is direly needed if you wish to load up your Galaxy Tab 7.0 Plus Wi-Fi with custom ROMs, or run root-only utilities on it.
XDA Developers member bdigitalstudio shares a rooting method for Samsung’s 7-inch tablet. Check out the rest of our step-by-step guide and learn how to root your Samsung Galaxy Tab 7.0 Plus Wi-Fi GT-P6210.
- A Samsung Galaxy Tab 7.0 Plus Wi-Fi GT-P6210. Do not attempt to use these instructions on other models or variants.
- Install USB drivers for your tablet by installing Samsung KIES.
- Backup your mobile phone data or securely store files on the tablet’s SD card prior to rooting your tablet.
- Maintain battery power of at least 60% to keep your tablet running throughout the entire rooting process.
- To minimize interruptions, temporarily disable antivirus software and firewall programs before you root your tablet.
- Rooting your Samsung Galaxy Tab 7.0 Plus Wi-Fi GT-P6210 will break the warranty.
- Root your tablet at your own risk. You alone shall be responsible for any damage dealt on your tablet.
- Download the rooting package (root.zip, 154.4 kB) and save the file to your computer. Do not extract the file.
- Connect your tablet to your computer.
- Copy root.zip to the microSD card of your tablet. You can use Samsung KIES for this.
- Disconnect your tablet from the computer.
- Turn off your tablet.
- Reboot your tablet into recovery mode. You can do this by pressing the Volume Up button and Power Button at the same time. When the tablet turns on, release the Power button while keeping the Volume Up key pressed until recovery loads.
- Once booted into recovery, navigate to Install update from external storage.
- Locate the root.zip file and tap the Power button to select it. This will initiate the rooting process on your tablet.
- Go back to the main recovery menu and reboot your rooted tablet.
- Install the following apps from the Google Play Store:
Good job! You have successfully rooted your Samsung Galaxy Tab 7.0 Plus Wi-Fi GT-P6210.
SOURCES XDA Developers Forum
- Select the host that you want to enable VMotion
- Click on Configuration, and on the left hand side there is a panel Hardware, click on Networking
- In the Virtual Switch that you want to enable VMotion, click on Properties
- In the vSwitch properties’ tab Ports, add a VMkernel configuration
- After you add it, click on Edit
- Here are the fields that are in the VMkernel Properties
- Port Properties
- Network Label: Use a name that is meaningful to you
- VLAN ID (Optional): Like what it said, you might not need it. But if you do, you should know what ID you need to use.
- VMotion: check to box to enable VMotion
- IP Settings
IP Address: 10.10.10.100
Subnet Mask: 255.255.255.0
VMkernel Default Gateway: 10.10.10.1
Here should be a subnet just for VMotion only, since it will generate lots of traffic when VMotion is in process. And the default gateway doesn’t have to be a real one. blockquote>
Example of VMkernel Properties
This is what it looks like after the VMkernel has been setup in vSwitch1.
- Do the same thing to the other host that is in same cluster (the resource pool).
- Now VMotion has been created in the cluster. We can go ahead to test VMotion, HA, and DRS. In fact, VMotion is the foundation of HA and DRS. If VMotion is working fine, all you need for HA and DRS is the licenses. Pretty simple and straight forward.
Here we are again. A few years on from the N97 system disk fiasco, we find many Nokia N8 owners running into similar disk space problems on disk C:, i.e. the internal system disk. Admittedly, the problems are nowhere near as severe as on the N97, but it’s still worth a few words and suggestions on how to remedy a gradually filling disk C…
On the ill-fated N97, the biggest problem was that there was about 50MB too little space to play with to begin with. After six months of life, with a few application updates and email use, the free space dwindled to near zero, with predictable catastrophic effect on the operating system’s operation!
With newer devices like the N8, with bigger system disk, the problem is a lot less severe, but with Qt updates and other system components being added in cyclically, there’s a real danger that space might get worryingly low if you don’t know what you’re doing. And with that in mind, let’s make sure that you know all the tricks and techniques needed:
NB. The exact settings paths and menu options below are from a Nokia N8 running Belle, but I’ve tagged this piece for older Symbian handsets since the general principles apply just as equally. Be aware that exact menus and settings will vary slightly!
NB2. Although nothing should go wrong when fiddling with files and settings below, this is a good time to remind you to do regular syncs of your data (to desktop or cloud) and to do regular backups (to desktop or microSD). You can never have too many copies of your data. And make sure you’ve got all relevant passwords written down – just in case!
1. Put all non-critical apps on mass memory
This sounds obvious, but it’s surprisingly easy to switch your Nokia Store installation preference to install to ‘C:Phone Memory’, for installing a theme or always-on background utility*, and then forget to switch it back to ‘E:Mass memory’ afterwards.
* Because your mass memory (E:) and microSD card (F:) get locked out whenever you plug your phone into a desktop or laptop computer, anything that simply has to be always available does actually need to be installed on C: It’s why most Nokia core updates always go to C: directly, without asking you.
- Check that your install preference is set up properly now by going into the Nokia Store and then tapping on the account icon. Scroll down and tap on ‘Installation preferences’.
- Go into Settings>Installations>Already installed and look down the list for any (obviously non-Nokia) items that don’t have a little ‘memory card’/disk icon besides them. Such applications may well have been installed onto disk C: by mistake – I found several in my case (SPB TV, shown below). Long press on each and ‘Remove’ them, then re-install from the Nokia Store now that your correct preference is in place.
2. Clear out your email
No, I don’t mean delete messages – you’ll want to keep all these on the appropriate (IMAP/Exchange/webmail) server, of course. The problem is that Nokia Email keeps all sorts of old messages and miscellaneous files and attachments all squirrelled away in a tortuous system folder structure. And however much it tries to do so efficiently, there’s an inevitable build up of ‘cruft’. Luckily there’s a painless way to clear all this out and reclaim, typically, between 10 and 25MB of space in one fell swoop:
- Go into Email and then Settings. Long press on your email address/mailbox name and choose ‘Delete mailbox’. Confirm the deletion.
- Resist the temptation to add it back in again immediately. Wait 10 minutes. Go and have a cup of tea, etc. Background processes are even now clearing out the mailbox’s files. If you keep an eye on disk C: in File manager, you’ll see the free space gradually rising.
- Choose ‘New mailbox’ and add your email account back in again. You’ll lose a few MB from the initial sync and download, but you’ll still be up to 20MB better off.
3. Empty out your Web browser cache (and more)
As with any computer, clearing your browser’s cache of visited sites and images can give a big short term gain of free space, though of course, it’ll all gradually fill up in normal use again.
The easy way to do this is to:
- Go into Web and tap on the menu icon and then on ‘Settings>Privacy’.
- Tap on the ‘Clear privacy’ line and then on the ‘Cache’ bullet point – the UI’s not too obvious at this point, but the browser cache does get immediately deleted.
The hard way to do this is to use a tool like X-plore to delve into the system folder as shown below and delete the appropriate cache folder manually. The advantage of this approach is that there are numerous other system cache and temporary file areas that are worth zapping if you’re desperate for short term disk space back. Just be careful – only go down this road if you know what you’re doing! By deleting the wrong folder it’s possible to stop normal operation of the phone and then you’re into option 5, below!
4. What else?
It goes without saying that you’ll have checked that you don’t have any large documents, music or media files stored on disk C: – the basics of file management can be done using either File manager or Photos, as appropriate – this is basic smartphone/computer use. If you’re in doubt as to what’s clogging up your C: disk, long press it in File manager and choose ‘Details’. Images, videos, documents, all get itemised.
5. Last resort
As a last resort, you can always do appropriate backups and syncs and then use *#7370# in the dialler screen to wipe your phone. Then rebuild/reinstall as needed (i.e. Sw_update, latest Store, latest Maps, set up email again, sync back on your PIM data, reinstall third party applications) – we’re talking an hour of work at least though and there’s the possibility that you’ll miss something important, so treat this very much as a last resort and for people who a) know what they’re doing and (like me) b) secretly enjoy the ‘set up from scratch’ process!
In my case, and the prompt for writing this tutorial, I was down to 17MB free on C: and, after doing steps 1 to 3 above, I got up to 60MB free, a massive improvement – and no need to go to step 5 at all.
If you try any or all of the above, comments welcome on their efficacy in your case – how much did you gain?
Now that VMware has released their new vSphere 5 into the public, questions always come up on how to make a bootable vSphere 5 USB installation media. As of now there isn’t any official way of doing this if you are using a Microsoft, Apple or Linux GUI based OS. So I have made a small step-by-step guide on how to achieve this. So here we go…
2. Download the VMware vSphere 5 ISO file -> VMware Download Center.
4. Choose Type: USB Drive and choose the correct USB drive letter that you want the bootable installer to be installed to.
5. You are now done! Just make sure you edit the boot sequence in your BIOS (UEFI mode on some systems).
You can also visit the vSphere 5 documentation online.