Sunday, October 28, 2012

Smartphones - iPhone 5 and Samsung Galaxy Note 2

v 0.2
28 Oct 12

Smartphones - it is coming to that time where the phone contract is about to expire, and we either negotiate a reduced rate or go on another contract with a new phone.  And so it is with me right now, with some really interesting choices around, and consumers being drip fed actual new hardware.

Just like a lot of people I've been looking seriously at the iPhone 5, Samsung Galaxy S3 and Samsung Galaxy Note 2.  I've had a brief play with an iPhone 5 in an Apple store, and have seen a couple of eager early adopter friends with them, I've had some friends show me their S3 phones, singing the praises and have read and watched as many reviews of all of them as I can.

So what to do - stay with my iPhone line and the Apple ecosystem or branch out to Android?

Well, it is not as simple as that.  Each of the reviews and commentaries I've seen comparing these phones miss the point completely in providing information to potential owners.  It has reached the stage I despair of any sensible commentary.  So, here are my thoughts as to what I want.  You'll notice that there are no performance specs or any of that - you have plenty of reviews to tell you all that.

 Do you want a phone that can do other things, or do you want a device that can also do phone calls?

My current phone is an iPhone 4.  It has been my tutor in my discovery of smartphones, my previous one being a Nokia which, whilst multi-function was rarely used for anything other than phone calls and the odd photo or two.  So at the start of my two-year contract, I was just using the phone, looking at the maps as a gimmick and trying out various apps.  Now, I use maps all the time, use Skype and messaging, and refer to documents.  I've gone from using the phone against my face, to now using the plug-in ear-piece and microphone leads.  It is my time-piece, my camera and alarm clock.  It is my notepad and emergency web browsing experience when I'm away from home (which is often).

Early on in the process, I acknowledged that the iPhone 5 would be the default replacement.  I found the Galaxy S3 to be an attractive phone that offered a lot, however for me, the iPhone offered consistency and integration within the Apple ecosystem - as Apple intended.  I also feel more comfortable with the IOS security the "walled garden" offers.  And yet there were niggling doubts.  Whilst the iPhone does all I want, there is still the question of the screen size and ability to easily view documents and web pages.  I have found both these functions require significant compromise on my current iPhone, and I don't see making the iPhone screen a little taller will fix that.

Enter the Samsung Galaxy Note 2.

My initial thoughts when I saw the reviews were that it was an interesting device.  In almost every case, whilst people initially baulked at its size, they soon became used to it and noted that it didn't bother them.  I wondered about the S Pen.  But I had to admit that the screen size was far more useful than the iPhone and, to a lesser extent the Galaxy S3.

And how do I view my needs now?

I spent some time trying to make sense of the facts and figures, until I realised that it came down to the question above.  Do you want a phone that can do other things, or a device that can also make phone calls?  For me, I think the latter is the answer.  I can use the iPhone 5 for these things, but the Note 2 is better overall.  I've cut a template for the size, and it fits in my pocket fine.  Phone calls?  Use an extension or bluetooth.  As a general device it is far better for note taking, reading documents and so forth.  Yes an iPad can do the general stuff, but you need to carry it around.

So for me, rightly or wrongly, I'm patiently waiting for the Note 2.  I see that as my next "communications device".


later ..........


Wednesday, June 13, 2012

Customising Gnome 3 - Making it Work

v 0.41
19 Jun 12

After playing with a fresh Xfce on a new install of Debian, I had one of those rare crash and freeze episodes, such that the window manager settings were all screwed up and the settings panel was blank.  There were a couple of other things I wasn't quite happy with so I decided to bite the bullet and do a complete re-install, correcting the mistakes I'd noted I'd made along the way.

Whilst I was having a think before this surgery (I learn something from every install, and it is really not a huge problem performing it) I was reminded of a thought I had when I was considering whether to undertake an Airbus A380 conversion from my Beloved Boeing 747-400.  I had been quite skeptical of the Airbus up until that time and I decided it was time I re-visited my "I ain't flying one of those new-fangled monoplanes!" prejudice.  Such was my thought process last night, as to the Gnome 3 desktop that was to be the standard on the next Debian Stable release. 

My first experience with Gnome 3 was a few months ago now - and whilst I recognised there was something to it, I just couldn't get into it.  So I moved to Xfce and thought about it as a "background process".  In the meantime, I kept hearing how extensible and flexible Gnome 3 was, but I just couldn't see the obvious way that it could be made more friendly.  One of the "Linux Action Show" podcasts put things into perspective, where they admitted that whilst it wasn't for them, it was a good piece of software.  Their main criticism was the need to continually move from left to right with the mouse to make a selection, and that it seemed as if Gnome was being placed to be efficient for touch-screen use.

Finally I thought, Gnome 3 is going to be with us from now on, and it is going to be the default desktop for Debian.  It has a lot of great stuff in it and if I'm going to be any help to friends, I better get in and see what we can do with it.

With that, I performed a standard Debian desktop install giving me Gnome 3 .

Standard Desktop

The first start-up gives you the standard Debian starry wallpaper (which I dislike) and along the top line, a black bar.

The Top Menu Bar
To the left is a button called "Activities", in the centre the day/date and on the right four button / menus.  There is an "accessibility menu of selections that can be made to improve things, then a volume and sound settings control, Network Settings, and then on the far right, a menu under the username that lets you adjust system settings or log out or to lock the screen.

The Desktop
There are no icons on the Desktop.  It is a straight backdrop of whatever wallpaper you wish to load.

The Activities Button
I guess you could think of the "Activities" button as the MS "Start" button on steroids.  When you click on it, there are three main areas of the screen that appear and one large area that depends upon your selection of "Windows / Applications".
  • On the left is a vertical stack of favourite applications.  It functions similarly to the "Dock" in OSX.  Right click and you can delete an application.  Any running applications you have started also appear temporarily in the "favourites" stack and you can add these permanently by right-click on the icon.
  • On the top right, a search entry box appears.
  • On the top towards the left, a two-choice button appears - Windows or Applications.
Windows / Applications
  • When "Windows" is selected, a vertical stack of active workspaces appears, and the selected workspace is reflected with an array of windows in that workspace, placed in the main part of the desktop.  As you cycle through the workspaces, you can see the windows in each workspace.
  • When "Applications"is selected, on the right you get the standard menu categories, and when each is selected, this is reflected by all the applications in that category appearing as icons in the main desktop area.
Window Decoration
By default, there is only a "close" button on the window - however - this can be easily fixed.

Logic
Now that I run through the logic flow of the standard desktop, it seems far better than I first thought.  Certainly the shock of transition puts one off.  The first reaction is "Not another thing I have to learn again!!"  Once you learn how this new system is just like the old, then it is not as much of a problem as it initially seems.

Customising the Gnome Desktop - a Start

The first thing you can do is visit "System Settings" and change the background and in "Details" set the default applications.

Next, install the " gnome-tweak-tool " package.  This appears as " Advanced Settings " in the application list. Here, you can:
  • Have icons on the desktop by having the filemanager handle the desktop.
  • Modify the "shell" (desktop) appearance, notably "Arrangement of buttons on the titlebar".
  • Install shell extensions from http://extensions.gnome.org .  Once you have found the extension you like, then click the on/off button to "on" and the extension will be downloaded and installed for you.  There are two menu extensions you may like that install a menu a'la Gome 2 - Axe Menu and Applications Menu.
Install the " Docky " package.  This lets you have a dock just like OSX.  Whilst Docky does give you a nice dock, it drags in a lot of dependencies, but more importantly, kills one of the significant keyboard shortcuts - the Windows key, or Alt-F1 to change from overview to details view.

Another problem I found, was when I removed Docky with Synaptic, it only removed the application, not the libraries (which aptitude would have done).  Deborphan would be a good idea here, as I found that on reboot, Gnome froze and only became free when I had re-installed Docky (though not started it).

From what I've seen, whilst Docky seems a good application, it tells me to only install Gnome Extensions, rather than extra programs.

gnome-system-tools

The standard system settings tools are lacking the old "users and groups" gui administration.  You need to install " gnome-system-tools " .

Thoughts

I must say that I'm far more comfortable with Gnome 3 now than I was before, and that maybe it isn't the disaster it first appeared.  With some extra reading I can see that it is no use trying to turn Gnome 3 into Gnome 2.  It won't work.  Like any new system, you just need to think about it.

In a way, you can compare Gnome 3 to the vi editor.  It has two main modes - an "overall viewing" mode where you get to see what you have, and a "doing" mode where you do the work.  Taking the time to read about this, and in particular the keyboard shortcuts and you can get to what you want in a couple of key-presses rather than tediously moving the mouse around.

So, even though I've installed some extensions that give a more "Gnome 2 - like" experience, I can see myself getting rid of them back to the original intent of Gnome 3 (and I'm already doing this).  Like a lot of things in life - Gnome 3 works best of you learn the basics and then perhaps carefully add some extensions from the Gnome site.







Later ......

Tuesday, June 12, 2012

Wicd Wireless, Port Forwarding

v 0.2
12 Jun 12

Xfce Wireless

I installed Debian Wheezy onto my old IBM T31 laptop this morning.  The netinstall via a wireless network went smoothly.  I installed Xfce rather than Gnome, so the Wireless network manager was Wicd.  When I booted up, no wireless network was found.  Dead.  It should have detected at least two networks.

The fix was amazingly simple.  Open the Wicd window, Options, General.  There is an entry there for the wired "eth0".  In the Wireless entry, enter "wlan0".  

It works.

Port Forwarding and Blocked Ports

I have been driven to distraction the last week or so trying to port forward port 80 to allow some friends to play with a demonstration I've set up.  I blamed my Apple Time Capsule, particularly when I saw so many complaints that people were unable to port forward.  I bought another router, and then found THAT would not forward port 80.  Grrrrr.

I rang up my ISP over the matter and they said that they did not block port 80.  (yeah ... riiigghhhhttt)

They do.

So, I set the demo server to work on port 2000 and forwarded it from the router.

VICTORY!!

Another expensive lesson.  But I did bumble my way through it.


Later .......

Tuesday, May 29, 2012

The Law and TLD, The Cloud and Home Servers

v 0.22
12 Jun 12

I've recently had a few disparate threads of the Cosmos come together to lead me down a new line of interest with my Computing.  It all started a few months ago when I was reading my daily dose of "Slashdot" and has finished with me starting to set up a Home Server for myself.

The Law

Whilst the Slashdot article was about the US Government seeking the extradition of a UK Student, the issue was their assertion that all ".com , .net , .org " etc domain names were subject to US Law, no matter where the servers or businesses or organisations were located.  Now, whilst the current actions involve copyright infringement allegations, I can see that this could easily be extended to other areas of the law,  were it convenient for those in power.  A link to a relevent article:

http://www.theinquirer.net/inquirer/news/2083906/claims-com-net-websites-jurisdiction

Whether the legalities of this assertion by the US Government are shown to be valid or not, what it means (to me, anyway) is that if you host a website with one of these top level domains, then you potentially must comply with US Law.  You may, for example, run a business in one particular country using such a website, so not only do you need to comply with your own country's laws, you must also comply with those of the US.  Some (legitimate) Canadian businesses are already discovering this.

The lesson I've taken away from this is that if I need a business or other serious website, then a domain name from maybe my own country would be a better decision.

The Cloud

The Cloud is certainly a convenient place to store data, and in all normal circumstances, your data should be quite safe - Google has just received security certification for its services.  Dropbox, whilst convenient, doesn't store your data encrypted, whilst SpiderOak does.  If you are paranoid and want to use Cloud storage, then SpiderOak would be great.  Or encrypt your data on ANY Cloud device.

Of course the problem comes when your provider has their server seized by whichever Law Enforcement agency, because of some other entity which also uses that server ........

Home Servers

It almost feels to me that the concept of keeping your own data is making a comeback - perhaps not for all, but "the Cloud" is not necessarily the best move in all circumstances.  There are some really interesting Web applications that can be hosted on your own server.  Several I'm fascinated with are "OwnCloud", "OnEye", "Diaspora" and "Citadel".  I easily set up "OnEye" on a test virtual server at home, and did the same with "Citadel".

Routers

When I tried to demonstrate Citadel to an organisation I was a member of though, I found I couldn't get my router (Apple Time Capsule) to open any ports to allow this.  Googling for a solution gained me nothing other than finding more than a few others with the same problem and the best I could find was that it was a flaw in the firmware.

Bad Time Capsule .... Bad Bad Time Capsule.

So out of that, I thought maybe time for a "proper" router.  I'd recently seen an interesting "Category5TV" Episode 166 dealing with DD-WRT firmware and a Netgear router.  In the end, I chose to get a WNDR 3700 Netgear - for it's firmware flashing capabilities and the wireless range it offered.

* Subsequently I found that my ISP was blocking some ports - it wasn't helped by them denying it when I called to see if this was in fact happening.  Unfortunately I had to fall back on detective work to discover this (and then have my Nephew say "yes, of course they do, didn't you know?").  So Ultimately, I could have saved my money and continued with the Time Capsule by using unblocked ports.  Sigh

Server Hardware

As I mentioned before, I'd been playing with servers within Virtualbox Virtual Machines on my Desktop - now whilst at the time I knew my desktop wasn't the best machine to use as a server if only for its power consumption, I was prepared to live with this for a short while, however once I started thinking about the router problem, my mind drifted back a week or so to when Dell sent me an advertisement for what I considered to be a cheap desktop that would be suitable.  Of course, I wouldn't be buying the Dell because I had plenty of screens and keyboards already and saw no point in buying anymore, not to mention that I had no use for Windows on my server.  But research into the components did lead me to an interesting setup.

Motherboard   Asus P8H61-M LX Rev 3
CPU                Intel i-3 2120
Memory          8 gig
HDD               Western Digital 2 TB Caviar Green
DVD drive

This machine is about 10 times as fast as a P4 3.0 box I already have and uses less power.  How much less?   Testing I've seen indicates the machine should use between 50 and 100 watts under most conditions.  Using this as a server rather than one of the previous two I've mentioned would be a minimum saving of 200 watts.  This works out at roughly 5kwhr per day or over $1 per day where I live.  It would pay for itself in electricity charges in a year.

Server Software

Having worked out the hardware, I'm planning on replacing an old P4 desktop that is used by the family.  I intend having it used as a desktop, with Virtualbox providing servers in virtual machines.

Debian "Wheezy"  64bit
Xfce Desktop
Virtualbox

At the moment, I intend setting up one or two virtual machines as Citadel servers - one for the family and one for my organisation to evaluate.  After that, well there are a number of interesting projects that are available, even within the Debian repositories.

I think that is enough for now ... I shall report back with my installation adventures.



Later ...........

Tuesday, May 22, 2012

Citadel Groupware - Some Possibilities

v 0.3
23 May 12

I was thinking this morning that Citadel provides the possibility of some really interesting implementations.  It is easy to install (especially in Debian), and they provide up-to-date debs from their own repository.  You can even have it running in a Virtualbox instance.

I strongly recommend you install Citadel via a Debian install and use the Citadel repository.  I was using the Wheezy version which had severe flaws in Wiki and File rooms - fixed when I updated to the latest version.

Don't like how it looks?  Easy .. just adjust the CSS and have it look any way you like.  They give you the page structure on the website and a CSS example to use and modify.

It is easy to set up a secure (you get https out of the box) network of Citadel servers (don't forget, this is not a client, it is a series of SERVERS that you can view as localhost on your web browser on the same computer if you like) and have your own secure independent email network - share projects, share files all over https.  Use a dynamic DNS provider and you can have a mobile node that can make connection from a hotel and the network sharing is up and running again.

These are just a few thoughts, however I'm sure there are more uses.

In case you are wondering what I'm saying about an independent email network...  Out of he box, Citadel will send email to users of the independent system based on their username.  Consequently, if you simply connect two Citadel servers together, then you can share email between the servers directly within that network.  Add connect via https and you are up and away .....

Finally, what servers are included in Citadel?  Here is what I've worked out so far:
  • Web server (webcit)  (http  https)
  • Mail Server (SMTP POP3 IMAP)
  • Calendar Server
  • Jabber (IM) Server (XMPP)

Later....

Sunday, May 20, 2012

Citadel Groupware

 v 0.22
24 May 12

Citadel is different - on first glance, it looks like a BBS with aspirations above its station.  I’ve had a love/hate relationship with this Groupware from the first time I saw it in the Debian repository and read about it.  

It has history … extensive history.  It grew out of the old BBS systems of Dial-up modem times, and still has a text mode that replicates that, although normal interaction is through a web browser and the “Webcit” server application.

Citadel looks, at first, a little dated and I’ve found user documentation a little sparse, however I’m slowly “getting” it and starting to really like it.  One thing I especially like is that it has several security advantages over other packages, notably immunity to PHP and SQL attacks.  It has its own inbuilt servers and it does not use PHP or MySQL.

So, how does Citadel qualify for the compliments I’ve seen about it?

Whilst it may seem a little “clunky” at first glance (it can be modified), its power lies in its simplicity of concept and gentle learning curve.  It is easy to set up, and you can start out with a very simple configuration and expand as you become familiar with how to use it.  It is like being given a pile of different lego blocks and discovering how to assemble them into ever more complex objects.

It is probably time for a screenshot (from the Citadel website), and then a discussion of how the setup works.  Once logged in to the application, this is how it generally looks, with a menu on the left and the subject of whatever you have selected in the main window.  Note:
  • login and viewing details in the top right
  • selection options for the current viewing window along the top menu-bar



Of the “Menu Selection Buttons” on the left, the private “rooms” for each user are:
  • Mail
  • Calendar
  • Contacts
  • Notes
  • Tasks
 

  • The “ +Rooms “ selection expands to the current “room” matrix.  These can be public or private, hidden or password protected, as determined when they are created.
  • “Advanced” is allocated on a per-user basis, depending on what permissions a user gets.
  • “Administration” is, obviously, allocated to an Administrator.
  • The menu is tailored to each user and setup.

At its core, Citadel is an old-style BBS.  Forums use the paradigm of “Floors and Rooms” of a building.  Each “Floor” has a broad subject, with each room being a more specific subject.  Where this differs from a standard BBS is that each room can take several forms.  The “room” could be a standard message topic discussion, or it could be a task list or a Blog.  So, in the case of a company project, there could be one floor named “Project” with separate rooms for message discussions, task lists, a blog talking of progress on issues and even perhaps a calendar.

Communication.  
  • Out of the box, Citadel offers email between registered users, with only the username required.  After it is configured, then conventional email is available.
  • There is an IM facility between logged in members.  There is more. Put a “Jabber” client such as Pidgin on your desktop and tell it about Citadel, and Citadel can act as a Jabber server connecting users.

Office Documents
  • Blog and Wikis.  Any room can be configured to act as it says.  I have to say though that I’ve yet to get the Wiki feature to work as I’d like (upgrade to 8.11 fixed that problem).
  • Calendars and Notes and Tasklists.  As it says, you can also nominate any room for these.  The “Notes” are sticky notes, and the Tasklists, while basic, can be categorised quite finely.

Networking
  • Citadel servers can be configured to network together simply by telling them about each other.  Users, rooms etc can be shared and a quite complex “social network” of sorts can be constructed.  These building blocks can link together to construct quite a complex system.  Impressive.

One final thing for the moment.  FLOSS Weekly Episode 209 is all about Citadel.  Worth the look.


Later...

Thursday, May 17, 2012

Debian - Package Management Atrocities

v 0.2
17th May 12

Flush with my success at installing "onEye" and a LAMP capability to my Wheezy server, I thought I'd have a look at the Citadel Groupware, provided in the "Main" Wheezy repository.  All went well, and I answered the configuration questions to the best of my ability.  I elected to use Apache as the web server rather than the internal one provided.  Unfortunately, I couldn't find how to run Citadel in the web mode (it ran fine in BBS command line mode).  It eventually turned out that the Webcit web client listens on port 8504 (from memory).  In any event, think carefully how you are going to use Citadel in concert with other web applications.

I decided to reconfigure the application and ran:
# dpkg-reconfigure citadel-suite

this did nothing and before I found out what I SHOULD have done, I ended up deleting some of the configuration files after mistakenly thinking I'd purged the whole thing.

What I SHOULD have done was:
# dpkg-reconfigure citadel-server citadel-webcit

Seems if I'd re-configured these packages that are called by the meta-package, all would have been well.  Lesson here.

note:  There may be some minor errors above as I've written it from memory, however the overall lesson remains.  look at re-configuring the correct packages ......


later ...

Saturday, May 12, 2012

OnEye - Installing to Debian Wheezy on Virtualbox

v 0.35
13 May 12

Last post I said I had OnEye successfully installed.  Here is how I did it.

Initially when I thought of setting up a server, I thought of buying a low power piece of hardware and using that, but then realised I already had an under-utilised desktop that could easily run a server in the background using virtualisation - an opportunity to try out and learn a few skills in the process.

After updating Virtualbox to the latest version, I created a new virtual machine.  I've learnt a bit about setting the boot device since my last installation and so with the new virtual machine entry highlighted in the VirtualBox window, press the "Settings" button.  Press "Storage" and then click the CD icon under "IDE Controller", then on the right where it says cd/dvd drive, click the icon of the cd and from the dialog box, move to and select the iso image you want to boot from.  Now when you press "Start" it will boot from your downloaded ISO - in my case, the Debian Testing Netinstall ISO -

http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso  .


Once I started the install, it came up with the standard debian install dialog - as contained in a number of Debian installation how-tos. The text installer is readable and when you think about the selections, they are logical.

  • English language
  • Where you are in the world (Australia for me)
  • American English keyboard

I chose the guided partitioning with separate partitions and accepted the defaults - I'd created an expandable 250 GB virtual machine so this is what the Debian Installer gave me:

/ 350mb
/usr  9 GB
/var  3 GB
/swap 2.1 GB
/tmp  398 mb
/home 233.5 GB

When Tasksel presented itself, I deselected the desktop and selected
  • Web server
  • SSH server 
  • Standard System Utilities

Later, just to be sure I also installed the apache2 package and restarted apache2.  I installed links2 and was able to confirm the webserver was functioning in both root and user accounts with

$ links2 http://localhost/index.html  and
$ links2 http://localipaddress/index.html

Unfortunately, I was unable to see the page on any other machine on the network.  A read of the Virtualbox documentation.  I was using NAT which was fine for general web browsing etc, however for using a server, I needed a Bridged adapter.  I shut down the server, changed the network adapter to "bridged" and restarted.  Fixed.

On an external computer, simply type the local ip address into the web-browser and it will be found - so that worked.

Next task was to assign a permanent ip address from my router.  Logged into it and assigned a local ip address based on the MAC address shown with "ifconfig" in the Virtual Machine.  Restarted networking and my new assigned ip address was done.

The default webserver install of debian also installs php5.  To that I added
  • php5-sqlite 
  • php5-imap 
  • sqlite 
  • gzip 
  • mc  (midnight commander)

As root, downloaded the latest oneye 0.9, moved it to /var/www/ and unzipped it.

# cd /var/www
# chmod -R 777 oneye/

on another computer, opened web browser  http://ipaddress/oneye

violas .....



There are an initial few questions, however they are pretty quickly sorted and the installation takes only a short time.  The only other thing you need to do is to edit the config file to make yourself the admin instead of root on the system.  Do this by going to:

# cd /var/www/oneye/
# vi settings.php
or whatever editor you like - I actually used mc for this

About 80% the way through the file is a comment that says

"// The real god of oneye users, the master of masters "
define('REAL_ROOTUSER','root');

change the "root" for whichever user you like.  Now when you set system preferences, you will get access to the Admin panel.


That's it.

Later 12 May ....

  • Installation of additional applications is dead simple.  Download the "eyepackage" to the admin desktop and click it - it installs.  Done.
  • Integration of FengOffice and SugarCRM is available, so instead of using "sqlite" as the database manager, it might be advisable to use "Mysql" in the initial install.
13 May

Something that shows my inexperience in servers.  It occurred to me this morning that the data from web users was being accumulated in /var rather than /home.  Obvious when you think about it, but when you are used to a desktop  system, all the users having their data in /home is ingrained.

So, need to download "PartedMagic" and "boot" from the iso to graphically resize the partitions of my virtual machine.  I could also use "parted" from the command line I guess and it would do me good to have a look at it.  In any case, another wrinkle in the saga and something else learned.

    Later....

    Friday, May 11, 2012

    EyeOS v OnEye - Your Computing Desktop in the Cloud

    v 0.2
    11 May 12

    For those who like looking at the last page .. I now have a onEye setup working on my home network.  It was easy to set up (using a Debian Apache webserver in Virtualbox) and is pretty neat.

    Now to what I was about to talk about.

    A couple of weeks ago, I was watching an episode of "The Linux Action Show" where they were talking about personal alternatives to cloud computing services.  One of these was the EyeOS product.  I was interested and had a look.  Whilst I really wanted to like this, I had the impression that the people there had moved solidly towards their "Professional" product (good on them) and their "2.5" release was just missing things that I would have liked.  I couldn't quite put my finger on it, but the feeling was there.

    A bit more research and I was starting to get a feeling for what was going on.  It seems that the EyeOS has forked at the 1.9 branch as a community project, renamed "onEye" and that many people prefer this branch to what has been produced to the 2.x series.  I have the feeling that the 2.x series would appeal to businesses, whereas the 1.9 series is more for the community.  The thing that really got me interested in looking at onEye rather than EyeOS was an evaluation which suggested that installation was less than ideal in the EyeOS implementation, and that the 2.x series was incompatible to many add-on applications that had been developed.

    So what is it about all this that you should be interested about?  Effectively, when you log on to onEye / EyeOS, you are logging on to a computer desktop in the cloud.  Think Dropbox with a desktop and applications.  They have a sync applicaton along with some standard apps that are supplemented by a whole swag of others.  There is even a web browser in the standard setup.  Now why would you want a web browser within a web browser?  Well for a start, all browsing traces are left in the cloud.

    Whilst reaction time for this desktop over the Internet is entirely dependent upon your connection speed, on a home network it is quite snappy and could be really useful for organising the sometimes chaotic things that happen on different computers at home - particularly in centralising backups of files we don't want to use.  (of course .. ownCloud is a contender for that as well).


    Later ....

    Saturday, April 21, 2012

    Google Script - What is It?

    v 0.2

    Said one way ..... Google Script is server-side javascript with Google API extensions that can be used to manipulate Google services and create User Interfaces.  Scripts are typically stored within Google Docs Spreadsheets or Websites and executed within the Google Cloud.

    Some examples:
    • Create user functions within a spreadsheet and use them for additional formula functionality
    • Read and write data to spreadsheets
    • Create new spreadsheet menus
    • Create a user dialog or form or other application interface.
    • Create a simple database using an interface and a spreadsheet or Fusion table to store data.
    Yes, there is so much more you can do, however if you already know that, then you don't need my description ..

    In order to USE Google Script within your Google Account, you really do need to understand how to program Javascript.  In particular, you need to understand Javascript objects, since they are central to the use of Google Script.  Youtube has an extensive list of tutorials and lectures for Javascript, and there is now one book available for Google Script.  Google has full documentation for its API set, though this can be a little hard going for the inexperienced.

    Whilst ultimately I want to end up with a complete application, I have found that I've had to go through the Google documentation - work out what I need to do, and then find example routines to do what I want - read and write to spreadsheets, create and re-order sheets, build a dialog etc.  It starts out slowly, but does speed up as you get into it.

    One thing I'll say about the GUI techniques - I've found them very similar to those used in the TK interface of TCL/TK, notably the Pack and Grid modes.


    Later ....

    Friday, April 20, 2012

    Stores Filing System - Considerations

    v 0.21

    When I'm not away on my "real" job, I spend time with a group called "HARS" - the "Historical Aircraft Restoration Society".  One of the projects there is to repair the damage on the replica "Southern Cross" Fokker Tri-Motor (the original is safely housed in a display at Brisbane Airport).  I was asked "Can you come up with a program to allow us to keep track of the parts here - BUT - it has to be SIMPLE!!

    No problems I thought - I can just use LibreOffice or a simple database program .. but as I found, it is not quite as simple as that.  Simple programs are not simple.

    The first obstacle is that if you use a database program of whatever kind on a single computer, the stores system is useless if you don't have THAT computer available.  Sharing the database file is a kludge that rapidly becomes really scary.

    Next, I talked to the guys that looked after the servers there.  They immediately told me that they already had a stores database system there - would I like to look at it and get it going?  Absolutely!  Unfortunately, after a LOT of reading and thinking about it, I realised that this stores system, whilst available over a network was designed for companies that had dedicated and trained people who used it all the time.  A 70 year old Aircraft Engineer who had spent his career with paper and files would not have a hope of walking up to this system and doing what he wanted - especially since he was here to play with aircraft for fun, not learn how to use a complex computer program.  So after a lot of time trying to find out what I'd missed about the program, I realised I hadn't missed anything and that it was quite unsuitable for what we needed.

    Perhaps I could get them to install PostgreSQL as a relational database manager and I could then write something to connect to it in LibreOffice, or a scripting language or whatever ...... I was met with looks of suspicion (which I can understand, given some of the "offers" of assistance these people have had in the past).  More street Cred needed before I proceed down that path.

    After some thinking, I finally settled on trying a system using Google Docs and Google Script.  The more I looked at it, the better it seemed for what I want.  It was in "The Cloud", it could be accessed from anywhere and on any Internet enabled device.  Now to work out how to implement it.



    Later ............

    Wednesday, February 15, 2012

    Comparing Debian Netinstall with MSDOS

    v 0.2
    15Feb12

    Why would I bother comparing Debian Netinstall with MSDOS?  Sounds silly - HOWEVER - when you look at it in a historical perspective, it is quite interesting.  This has no secret how-to at the end, I was simply thinking this morning when I was doing my 3k walk ... "isn't that cool" ....

    In the '80s, MSDOS was king.  You got to pay good money to get a box and some diskettes that had a single user operating system that you could add to to get anything useful done.  Of course, if you were keen, you had the batch language and GWBASIC, but that was pretty much it.
    • If you wanted, you could pay more good money and get Turbo-Pascal, or MS-Basic or some other compiled language.
    • Perhaps you'd like to spend some more money and buy QNX - a multi-user system (that I think still exists).
    • How about a DOS Markup Text processing language?
    Now, Debian Netinstall (doesn't matter whether it is Squeeze or Wheezy, the principle is the same) - you get to download it for free.  Looking at what you get in what is considered today to be "a bootstrap loader" for the real system - well we are smothered in riches and don't even know it.
    • You get the same sort of screen those MS-DOS users got, except you have Bash - a powerful programming language in its own right - but that is the SHELL!   
    • zip/unzip .. bzip .. grep ... awk ... wow!
    • Multi-User / Multi-tasking out of the box.
    •  Not happy with Bash?  How about Perl?  Pretty hard to beat that!
    • Typesetting?  Groff.  At least as powerful as those systems you paid good money for, but .. yes .. it's free.
    • No edline here - Vim.  You may laugh, however Vim is a pretty damn powerful editor.  But if you don't like that, how about Nano - still better than anything MS included at that time.
     There's more, but you get my drift ..



    Later ...

    Monday, February 6, 2012

    Debian - Memory Footprints

    v 0.2

    Over the last few days, I've been having some fun working out exactly what you can do with the Debian netinstall ISO image.  It doesn't really matter whether you use the Squeeze or Wheezy image, the memory footprints will be about the same.

    For the record, I've been using Virtualbox to look at these results.
    • In a text-only system as described earlier you could do useful work in under 32 meg.
    • With Xorg and a simple window manger like Openbox, Fluxbox, Fvwm or the like, 64 meg.
    • Xfce 128 meg
    Remember, these memory footprints are minimums ... I had an Openbox session using 28 meg - then I opened Iceweasel and it went to 60 meg.  Even a terminal session will add 5 meg to your memory requirements.

    Now we come to more complex stuff.  A Linux system has many processes operating in the background and the memory observations above probably simplify that a little too much.

    So, a broad observation:
    • 1 gig ... use KDE or Gnome if you like (they are not for me)
    • 512 meg .. Xfce
    • 256 meg ... Xfce will do, but you will have more fun with Lxde / Openbox / Window Maker
    • 128 meg .. Openbox / Window Maker / Fluxbox / Fvwm will make you happy.
    • 64 meg ... Same as above but you will just have to be frugal.
    • 32 meg .. restricted use of window mangers or use the command line (ie no Xorg)
    Enjoy




    Later ...........

    Saturday, February 4, 2012

    Debian - Netinstall + Window Manager

    v 0.4.7

    Subsequent to my last post about the Netinstall as a console system, I experimented with installing Xorg and a Window Manger.

    " aptitude install xserver-xorg wdm wmaker xterm "

    as I found when I did the initial install, xterm was not installed and this made it all very difficult.

    18 meg unpacked ... reboot and works like a charm.  Now, having given the example, you could insert gdm3 or slim instead of wdm and fluxbox or whatever instead of wmaker.  I simply did this as an experiment.

    Since we are talking about Window Maker as a manager, here is a description as to how to configure it ...

    http://maketecheasier.com/create-a-great-window-maker-desktop/2009/02/14


    Later .....

    Update Monday 6 Feb (just after shaking my head in wonder at how you get to the Superbowl, then get caught out putting 12 men on the field .....)

    I also installed Fluxbox and Fvwm.  Both seems to have improved default values these days - but I also installed Conky from the repositories.

    Netinstall + X + Window manager (Fvwm) + conky .... under 35 meg memory useage!  And this from a standard Debian install - just choosing what you run.

    Others (approx):
    • Fvwm   34 meg
    • Fluxbox  32 meg
    • Window Maker  28 meg
    • Openbox-Session 24 meg
    • Add 5 meg for each terminal
    By way of comparison, the Wheezy Xfce install I did previously uses just on 92mb.

      Later....

      Debian - What is Netinstall Made Of?

      v 0.2

      Let us say that you are a curious person and you decided to do a Debian Netinstall (Squeeze or Wheezy, it matters not), but when you reached the "tasksel" screen you unchecked everything, so that nothing further would be installed.  What sort of system would you end up with?

      Well, it's actually not a bad console system.  Obviously there is no X, however you can start it up, and log in to a console.  Apt is set up with appropriate sources.list and you have Internet capability.

      If you want to list the packages, then:
            " dpkg --get-selections > selections.txt "

      as root will place a list of installed packages into the file " selections.txt " in the root account.

      Of course, if you want use this principle to duplicate what you have on one Debian install onto another, then you update the package database of installed packages with:
              " dpkg --set-selections < selections.txt "
      Once again as root, before doing an Aptitude update and upgrade.

      Now, looking through the packages in  " selections.txt " the included ones that caught my eye were:
      • The complete Dpkg / Apt / Aptitude toolset
      • bash
      • gcc
      • gnupg
      • groff
      • gzip
      • mawk
      • nano
      • perl
      • sed
      • tar
      • vim
      • wget
      In its own right, this represents quite a capable system, three programming languages, a typesetting system, excellent text editor, encryption, backup and an awk text reporting language.  Not bad and certainly fun.


      Expanding the System

      As part of the netinstall setup, the apt sources.list was configured for your preferred country, and even though this is only for the "main" sections, that is perfectly adequate if we wish to build our own custom Linux system.  We don't have a graphical client like synaptic, but we have the Debian tools we can use.  Aptitude provides a consistent front end to the Apt and Dpkg tools.

      "  aptitude search xorg | more "

      will return a list of those packages that are to do with xorg.  You can repeat the process with any search criteria you like to have a look at available packages you might like to install.

      To show details of a particular package you are interested in:

      " aptitude show xserver-xorg "

      You are now well on your way to installing Xorg to your machine.  To find a graphical login manager, try:

      "  aptitude search x-display-manager "

      and you'll be shown a number of packages on the last line that you might like to look at.  Likewise, you can look at window managers, desktops or whatever you like.


      Conclusion

      I haven't set out to provide a definitive set of instructions here, but to show what you can do when given a minimal system and the sorts of things you might like to poke around with.  With some care you can have just the packages you want, and a slim, fast setup.


      Later ............

      CrunchBang

      v 0.2.7

      A couple of nights ago, I was sitting in the bar at my hotel in Melbourne whilst consuming my accumulated drink vouchers, when an elderly lady who had clearly been enjoying the hospitality of the establishment started randomly haranguing groups of patrons as to the greatness of John Oppenheimer.  This enjoyable "impromptu theatre" was terminated when she was quietly led away.

      What has this to do with the subject?  Everything.  Mr Oppenheimer was one of the major contributors to the ultimate "CrunchBang" at the aptly named "Trinity Site".  So CrunchBang stuck in my mind and the more I read about it, the more I liked it (the Linux Distro that is).

      This minimalist distro is built directly upon a Debian Squeeze Netinstall and uses the Openbox window manager.  The Debian Backports and a Crunchbang repository are also used.  It is installed using a modified Debian Installer script, and like Ubuntu and a few other distros, the sudo command is used for administrator privileges.  A "cb-welcome" bash script enables additional functionality to be installed, however I found it failed when the technique to detect an internet connection simply wouldn't work.  Iceweasel release (the latest) is included along with Flash.

      I installed it in Virtualbox just as described in a previous post, though with a smaller "disk" and less memory.

      This is definitely not a beginner-friendly distro.  Straight up, editing of the sources.list is needed to tailor it for closer Debian repositories, and commenting out the "check-internet-connection" line in the "/usr/bin/cb-welcome" script is needed.  Simple, but a show-stopper for many.

      HOWEVER

      I REALLY like Crunchbang.  Why?  Crunchbang is built the way I think many more distros should be built that expand or modify a parent distro (in this case Debian Stable).  It uses the parent distro as a base and modifies it with additional repositories and scripts.  At all times you can go back and use the documentation of the parent distro.  This is truly using the "standing on the shoulders of giants" technique and benefits both the user and the Distro maintainer by (in this case) using what Debian has provided and improving just what needs to be tidied up for what that person wants.  No re-invented wheels needed.



      Later .....

      Update:
      The initial install uses 70 meg memory at idle and just under 1.9 gig disk space.

      Update 11 Feb.
      I encourage you to visit the Crunchbang support forums.  There are some really good posts with some great advice for modifying systems (how to for Xfce for example) or setup Conky (which I've become somewhat enamoured with).
      In addition, Openbox has started to grow on me.  Combined with the Debian Menu system it is really quite slick.

      Saturday, January 28, 2012

      Debian Wheezy - Web Browsers

      v0.3.1

      I've been working with Debian Wheezy with Virtualbox.  It occurred to me that I've long ago stopped talking about how to install Debian within VBox, and have transferred to talking about Wheezy itself.  Hopefully naming the posts about what they really are will be more productive.

      Whilst purists might disagree, I think that using synaptic is a wonderful and easy tool to explore the world of Debian packages.  The sections are nicely laid out and it is easy to see which packages meet your search criteria .. and who knows, you might find some wonderful gem you never thought existed.

      Take Web Browsers for example ......

      When you search on that, some really interesting variants appear.
      • Chromium from which Google Chrome is derived.  And it accepts the Google extensions.
      • IceApe.  The Debian version of SeaMonkey which is the Mozilla version of Netscape.
      • Dillo.  It is a cool, FAST web browser.  Yes, a little basic but did I mention is is FAST.
      • Conkeror.  Emacs.  But this one does graphics.
      • W3m.  Emacs.  But this one doesn't.
      • Links2.  Just on 2 meg and it is not bad ...
      • Lynx
      Whilst there are a few more, I just wanted to illustrate what you can find.  I know there are the standard Gnome and KDE browsers, but at the  moment I'm inclined to avoid them since upon installing them you are obliged to install the majority of the appropriate desktop and whilst this might be fine for you, that is not what I'm looking at here.

      I guess what I'm trying to point out is that the Debian repository of software is pretty extensive, and whilst I'd like to get back to configuring the overall system and finding those tips and tricks that seem elusive, there is so much to be found in Synaptic.


      Later ........

      Further to the above ....

      I did of course negelect Debian's Firefox - IceWeasel which is provided in the latest variant.


      :)

      Thursday, January 26, 2012

      Debian Wheezy in VirtualBox - Part 6

      v 0.2

      I have to say that I'm really enjoying playing with Wheezy in Virtualbox.  It is letting me have a really good look at where things are going - although the downside is that it is too easy to just stop my work and have a bit more of a peek.  I'm no expert, however it is really interesting finding a problem and then seeing what information there is available to get around it.  It is made so much easier because I am starting with a solid base system that I'm not relying on that I can just incrementally improve.

      On to what I have been doing ..

      Documentation

      There really is an amazing amount of documentation and how-to information available for Debian, not only on the Internet at large but also on the Debian Website and within the installation itself.  One example is the "Debian Reference" we installed in my last post. 

      Another package to look at installing is the "menu-xdg" to compliment "menu", the Debian menu package.  I installed it thinking I would perhaps GET a Debian menu in Xfce, but not to be - I think I'll have to define a menu-hook for it and do it manually - but not right now.

      " dhelp " is a package worth installing.  Once it is on your system, open a terminal and type " dhelp" .. it compiles a list of HTML documentation on your system and presents it in the default Web browser.

      If you get really keen and open the file browser, look in " /usr/share/doc " .. a documentation package for almost every package you have installed .. even one that describes the Debian Menu system in detail.

      Open Synaptic and search on "documentation" ... extensive stuff in the Debian Repositories.

      Other places to find great stuff are The Linux Documentation Project , and the Rute User Tutorial , not forgetting the Linux Cookbook .  Of course, the Slackware Linux Book project is just wonderful, and I've really been impressed with the detail of the documentation at Gentoo Linux.

      I think that is enough for today.



      Later ...............

      Debian Wheezy in VirtualBox - Part 5

      v 0.2

      This time I'd thought I'd talk about packages I've installed / uninstalled. 

      • First up is the Flash plugin.  Wheezy comes with the latest IceWeasel browser (Firefox) however uses the Gnash plugin.  Whilst this is improving steadily, for what I want to do especially in Youtube, the Adobe Flash is much better.  Ensure you have  "main contrib non-free" activated for your repositories in "/etc/apt/sources.list" and after updating the repositories, fire up Synaptic and search for "Flash".  You will find the "Browser plugin for Gnash" is installed - mark it for removal, and at the same time, mark the Adobe Flash non-free for installation.  Apply, and now you have the Adobe Flash plugin installed.
      • Some fonts.  Search for " ttf-mscorefonts-installer " and mark that for installation.
      • Gdebi.  When you wish to install a " deb " package to your system that you have manually downloaded, if you use Gdebi to install, then all the dependencies will be checked and if available, downloaded from the Debian repository.  Once installed, it appears in the "System" section.
      • Boot-Up Manager.  Look for " bum " .  What it does is to allow you to control which services run on startup.
      • Debian-reference-en  .. an excellent book all about Debian.  This also installs the  debian-reference-common package.  If you are not careful and don't just choose your preferred language, you'll end up installing the lot.  You might also consider the debian refcard, and the installation guide as well.  Now, because of the wonders of the Debian menu system (worth finding out about), the Debian reference is now in the  "accessories" section.
      • xchm - to view Microsoft compiled help files.  Once installed, it appears in the "Office" menu.  There is also kchmviewer, however though that is a little more capable, it is also somewhat larger.  If you are going to have a number of KDE applications though, it might not be so bad.
      • xcal - an old and basic calendar / memo / alarm program - but interesting.  AND it brings up another question - that of modifying the Xfce menu, since xcal does not appear and can only be launched via the terminal (unless you create a launcher).
       Of course, the "application finder" spyglass on the dock could be used to do some modifying of the menu, however I've not chased it up yet.

      Menus in Debian

      Menus in Debian are interesting - there is an automated system to add and delete items that enables the menu of any desktop / window manager to be automatically updated as packages are moved in and out.  You can start reading about the Debian Menu System, and then,of course, Google is your friend.

      Alacarte Menu Editor

      The Gnome menu editor was the first to cross my mind .. " Alacarte" however when I went to install it, many of the Gnome packages were listed for installation as well, which was not what I was after.

      The Debian Menu

      One menu selection that is missing is the "Debian" menu, which DOES include all the installed applications.




      Enough for the moment.



      More later .......

      Tuesday, January 24, 2012

      Debian Wheezy in VirtualBox - Part 4

      v0.2
      Xfce

      The first thing I'd like to cover is the customisations I did and why I did them.

      I didn't like the desktop icons.  They were just yuk.  I found it difficult to open them - perhaps their target "doubleclick" area was too small.  So:
      • Application Menu > Settings > Appearance > Icons > Gnome
      • Much better
      • ps .. subsequently I had problems with the doubleclick ... right click and .. "open" .
      Wallpaper - For the first time, I've found some really nice wallpaper in the default install.
      • Application Menu > Settings > Desktop
      • Choose your wallpaper
      Yup, that's it.  They are the only two things I changed.  And I love the desktop.

      I had a look at the Xfce website, and there are a couple of webpages that are REALLY interesting - additions to the basic install ......
      Synaptic is your friend.


      Other Stuff

      I was going to leave this for a bit and round it out, however since I have a Licence renewal Simulator in a couple of days, perhaps I should concentrate on that.  Although this is fun as a diversion.

      Looking at Xfce has made me keen to look more closely at the GnuStep Desktop, Lxde, Fvwm and a couple of others (including JWM and Fluxbox) to see just what we can do to make a nice easy desktop.  At the moment though, Xfce is just beautiful.



      Later ...............

      Debian Wheezy in VirtualBox - Part 3

      v0.2

      I finished the previous part having just booted into a nice shiny Gnome 3 desktop in Virtualbox.  It certainly was a change to what I was used to.

      Before I get started though, what the Guest Additions do for you are that they allow seamless mouse movement between Guest and Host, and the ability to re-size the Guest desktop.  Just drag and it all works.  Three other features I'll mention in passing here are the ability to mount a DVD drive or ISO image, the ability to use a USB memory stick (after you have introduced it to Virtualbox in the USB section) and the ability to set up a shared folder between the two operating systems.

      Gnome 3

      I have to say that my initial experience was somewhat jarring.  I sort-of worked out some of the functionality, however it still largely felt like a bad visit to cartoonland.  I think I shall have to let it sit for a while, see if I can find a straightforward set of documentation and then re-visit.

      Despite my reservations, I can perhaps see the point of the developers in that new users MAY find it a good experience, though I still wonder.

      Xfce

      Whilst I had used Xfce a little in the past, I was keen to see how it had developed in the latest incarnation. Those who are used to Debian being associated with "old" software have obviously never visited the "Testing" branch.

      I re-did the Netinstall and put Xfce as the desktop of choice so as to see what came with it.  I found the log-in screen a little different to what I was used to (I use gdm and I assume this was different) however it went fine.  I don't care for the Debian starry wallpaper and need to do some reading to see how to replace it for the bootup and login.  The Xfce desktop came up very nicely and I had a great feeling about it right away - I can understand Linus's comments now about abandoning Gnome for Xfce.  I checked the "About" menu option and found it was Xfce 4.8, the latest version.

      About now would be a good time for a screenshot, but I won't.  Instead I shall use the wonder of text to describe it (you'll thank me for not exposing you to the starry paper background).

      Debian has Xfce set up with three bands by default.
      • Of course there is the desktop in the centre which has three icons at the top left for "Home", "Filesystem" and "Trash".  Right click the mouse and a menu allowing you to create desktop icons or select properties or applications, appears.  
      • Along the top is a panel reminiscent of the Gnome 2 setup.  On the left is a main dropdown menu of applications, then a shutdown button next to it.  On the right at the top are the icons for the default 4 workspaces, the time and the network status.
      • At the bottom is a panel in the centre that works a little like the OSX "Dock".  There are six icons by default.  Minimise Windows, Terminal, File Manager, Web Browser, Find Applications, and an icon that allows you to open any folder in your home folder in either the file manager or terminal.
      It is rather pointless talking about standard applications that come with Debian because it is easy to simply use the package manager and install those you like and eliminate those you don't.  I will say though that those that stood out to me were Iceweasel v9.0 (ie the running latest release of firefox) and LibreOffice.  I also like the lack of some of the major applications that come with Gnome by default that I just don't use.

      So in contrast with my initial impression of the latest Gnome, I rather like Xfce.  I'll leave this post here (and get back to what I should be doing) and next time I'll talk about some initial customisations I have done to make things just that bit better.


      Later ..............

      Monday, January 23, 2012

      Debian Wheezy in VirtualBox - Part 2

      v 0.2

      In Part 1 of this post, I talked generally about the requirements for setting up a Wheezy Gnome VM in Virtualbox.  I shall assume that you have the Machine specified, but not installed yet.  I shall also be rash and write these notes from memory.

      Installation
      • Start the VM.  If you are using a Windows host, it will politely ask you to tell it where the installation iso is, otherwise, you will need to let it fail, then use the "Device" menu at the top to select the CD netinstall iso image and restart.
      • The standard Debian installer screen is your first port of call.  If you want a Gnome desktop, just continue.  I never bother with the graphical install since it is just a more complex version of the standard text interface.  But then, I like the Slackware installer as well ......
      • To install a desktop OTHER than Gnome, go to "Advanced" and you will find links to a number of alternatives including KDE, Xfce and Lxde.
      • Now you need to simply proceed through the standard Debian installation routine for what you want.  There is an EXCELLENT Debian installation guide at "Howtoforge" entitled "The Perfect Desktop Debian Squeeze" which I strongly recommend.
      Installing Guest Additions

      If you are using the Gnome 3 desktop,  the initial log-in will be slow while it works out that it cannot use the standard Gnome and will fall back to the "classic" look (which you could also select on log-in the first time).  The steps I followed to get the guest additions installed and Gnome 3 running (I also described the guest additions with Debian in another post - read it and you can tell me where I differ to it):
      • Open a "root" terminal.  I'll describe the commands to type in between the "  " ....
      • "  aptitude install synaptic "   Synaptic is a nice graphical package manager that has its uses.
      • "  aptitude install module-assistant  "   Module assistant is the key to installing guest additions
      • "  m-a prepare "     This gets module assistant to load the dependencies for the guest additions
      • Start Synaptic, search (there is a magnifying glass button for search) for " virtualbox " and mark any installed virtualbox package for removal (they will be marked as guest additions), then " Apply "
      • The tricky bit is coming up
      • You need to mount the "guest additions iso" which is located in the installation directory for virtualbox.  You can either select "install guest additions" from the "device" menu on the VM or you can use the " device " menu and CD/DVD selection to search for the guest additions iso.  In either case, you should make sure it is mounted.  It will appear mounted under " /media/cdrom0 "
      • Once you have it mounted, use the root terminal to "  cd /media/cdrom0 " and to execute the "VBoxLinuxAdditions.run"  as shown in the next part
      • "  bash ./VBoxLinuxAdditions.run "   using the root terminal after changing to the iso.   You need to have the "  ./  " in front of the Vbox..etc because it explicitly tells Linux where the file is.  (ie a period and forward slash).
      • At some stage, it will complain that there are already Guest Additions installed - ignore it because you just deleted them and it has detected the remnants.
      • Once this is completed, reboot the VM and you will now have an accelerated Gnome 3 desktop.
      That's it for the moment.

      As always, corrections or additions welcome.


      Later ................

      Debian Wheezy in VirtualBox - Part 1

      v 0.2

       This post has grown significantly since I started, so I've had to split it up ...... here goes ..

      I'm a fan of Debian Linux.  Whilst Ubuntu is fine, Debian just sits right with me.  Same with Virtualbox.  I have had a Debian Squeeze virtual machine on my laptop and desktop for some time and thought I'd explore a bit further. 

      One thing I did recently was to explore the concept of using a Debian VM as an encrypted volume.  Whilst there are some other means of encrypting files and partitions, I've found it is quite effective to install a Debian encrypted VM and use that.  It is quite straight-forward, as I described in an earlier post installing to an old laptop. Free and neat.

      What I have been thinking of recently, though, is exploring Wheezy (Debian Testing) and the new Gnome.  I'd been hearing a few things about it that disturbed me, and I have been eager to explore a bit, since I have shown a few people Debian recently, and they love it.  Gnome in Squeeze is quite easy for them and I've been wondering how they would fare.


      Wheezy Netinstall

      First, how do you find an ISO to install?  Easy - search on "debian installer" and it will take you to the page from which to download a "netinstall" image.

      http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/

      You can see from this that this is the link to the "i386" image.

      http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso

      Now, what is a "Netinstall" iso image?  It is a Debian Installer cd image that will install a base Linux system onto your computer from which it then connects to a Debian Repository to download the remaining files to produce a complete system.  Note, you need to be connected to the Internet when you use the Netinstall image - I guess that is .. er .. why it is called "Netinstall".

      Virtualbox

      Given that Virtualbox is free and available for all common platforms, I've found it most useful.  I can run a copy of the same Linux VM on both my Windows desktop and my Mac Laptop. 

      For those who don't know, Virtualbox started as a private, open-source project many years ago before being bought by Sun, who continued developing it, before in turn being bought by Oracle who have thankfully kept the project going.  The latest can be downloaded from http://virtualbox.org  .  You will need both the version for your platform, and the guest additions (which install into virtualbox easily).

      Preparing Virtualbox for Gnome 3

      I have two Wheezy VMs - one for Gnome and one for Xfce desktops, to see what is available and how best to tailor Wheezy for what I want, however I used the same recipie for both VMs.  It is pretty straight forward to prepare a VM in Virtualbox, and you can always read the documentation or Google for some pointers, so I'll only cover the particulars of my install.
      • I started the new Gnome VM by calling it WheezyGnome - Virtualbox immediately figured it was going to be a Linux VM.  
      • I created an expanding volume, max 15 gig
      • In the Display section, I gave it 128 meg of video memory and ticked the 3d acceleration
      Gnome 3 needs 3d acceleration to give you the best "experience" otherwise it starts in a fall-back mode.  When you first install any Linux distro with Gnome 3, you will need to start the fall-back mode until you have installed the "Guest Additions" to the VM.

      Next ...

      Next I'll talk about how I got Gnome 3 up and running in Wheezy ...



      Later .....