VirtualBox 3.0.0 - This version is a major update.
Find full features list and bug fixes on:
http://www.virtualbox.org/wiki/Changelog
Main features:
Guest SMP with up to 32 virtual CPUs (VT-x and AMD-V only;
Windows guests: ability to use Direct3D 8/9 applications / games
Support for OpenGL 2.0 for Windows, Linux and Solaris guests
As usual, find the VBoxGuestAdditions.iso with us.
Download the VBoxGuestAdditions.iso file from:
http://download.virtualbox.org/virtualbox/3.0.0/VBoxGuestAdditions_3.0.0...
Download the latest version (3.0.0) of VirtualBox from:
http://www.virtualbox.org/wiki/Linux_Downloads
USB setup Howto:
http://www.42droids.co.uk/setting-usb-ubuntu-904
Don't forget to remove any old version before installing VirtualBox 3
A free implementation of an NX server based on NoMachine's libraries named FreeNX was published in 2004 by Fabian Franz. FreeNX's primary target is to replace the one closed component and is written in a mix of several thousand lines of BASH, Expect and C, making FreeNX difficult to maintain.
Last week, Google Code released the source code of their own proof-of-concept implementation of an NX server, Neatx. Designed from scratch with flexibility and maintainability in mind, Neatx minimizes the number of involved processes and all code is split into several libraries. It is written in Python, with the exception of very few wrapper scripts in BASH and one program written in C for performance reasons. Neatx was also able to reuse some code from another Google Open Source project, Ganeti. The code still has some issues, but we're confident interested developers will be able to fix them.
Also, Neatx implements features not found in FreeNX, such as the drop-down menu for session control in rootless sessions. At the same time, not all of FreeNX's features are implemented in Neatx.
Find the Development page here: http://code.google.com/p/neatx/
Link to the original article: http://google-opensource.blogspot.com/2009/07/releasing-neatx-open-sourc...
This is a quick bug fix release.
Find more info about VirtualBox 3 here:
http://www.42droids.co.uk/virtualbox-300-out-now
Cron is a time-based job scheduler in Unix-like computer operating systems. 'cron' is short for 'chronograph'.
If you would like to set up your Drupal and linux server to use the cron, these steps will help to achieve your goal.
Open up a console and change to the user which will run the cron.
Every user has it's own cron tab (which is the list of jobs cron has to run.)
If you prefer, create a new user for this job.
To access your crontab use the following command:
crontabThis will give you a summary of crontab's commands and switches.
To list your cronlist type:
crontab -land to edit the list:
crontab -e
If this is the first time you edit the crontab, it will ask you which editor you would like to use.
If you are unsure, use google to find out which editor is the best for you.
Inside the editor, add the following line to the end of the list:
*/5 * * * * /usr/bin/wget -O - -q -t 1 http://[your server url]/cron.phpThis will execure the cron.php in every 5 minutes.
Here is a diagram of the general crontab syntax, for illustration:
* * * * * [command to be executed]
| | | | |
| | | | +----- day of week (0 - 6) (Sunday=0)
| | | +------- month (1 - 12)
| | +--------- day of month (1 - 31)
| +----------- hour (0 - 23)
+------------- min (0 - 59)
* in the value field above means all legal values as in braces for that column.
The value column can have a * or a list of elements separated by commas. An element is either a number in the ranges shown above or two numbers in the range separated by a hyphen (meaning an inclusive range).
If you would like to theme you view output (and I mean hard core theming) or would like to add a view into your module generated page or just like to pass in some arguments from you modules into a view, this very quick tutorial is for you.
In Drupal 6 all the views are objects. That means if we load them into a variable, we can do pretty much anything with them. Create your view. This is the first step. If you like, add Arguments to the view, so we can pass in variables when we execute the view.
You can add a page display or a block display if you like. Both has some advantage and disadvantage. If you create a page display, you have to specify a path, but if you will only use this view inside your module, there is no point doing this. If you use the block display, you will have a nice array with two items in it. 'subject' and 'content'. Clearly the subject is the title of the block and the content, well, it is just the content. :)
Create the page menu hook in your module. This is easy, just use standard Drupal code. (if you need help, look up the hook_menu on http://api.drupal.org/api/6)
Create the page function your hook_menu will call. This is just a function returning some standard HTML code coming for your customised view.
Loading the view is very simple really:
$view = views_get_view('[view name]');
The view name is always the main name of your view. (Not the display name.) Now, depending on which display you have added to the view, use block_1 for Block Display or use page_1 for Page Display. If you have not created a display (yes, you can do this as well.) just simply use default as a display name.
The following code will execute the view's selected Display. This is part of the view object.
$content = $view->execute_display('[display name]', array([arguments]));
The $content variable could be called $block if you used a Block Display or $page if you have used a Page Display. Page will change the Title of the page, Block will eventually have a block title, header, footer, etc. (This depends on how and where you want to show your view. The arguments are more interesting: You always have to pass in an array of arguments. The item(s) inside the array have to be a string. Plus sing means AND and the space means OR between the arguments.