T R Y to delete my personal data !!
see you..

Of course it’s not Redmond’s fault that we don’t have touch screens. At this point, it’s a safe bet to assume that about 99% of all computer users do not have touch screens. And that is what makes this whole investment into touch interfaces a wasted effort: Nobody -can- use them, even if they wanted to. Outside the tablet niche, the market for such interfaces simply doesn’t exist.
So why is every major DESKTOP operating system – Windows, OS X, Ubuntu – trying to push a user interface created for touch screens?
The business/corporate PC and notebook are not going anywhere. Not even the home PC is in a rush to retire.
I just don’t see where this development is supposed to bring an improvement for users of traditional input devices – and those input devices are still the standard.
It just doesn’t make sense.
Anyway, Ubuntu 12.04 LTS Beta 1 is out. I’ll give it a look while I’m installing a new server. Maybe I’ll get used to that new HUD thingee. Maybe.

have a good time – Tilo

have you tried the Ubuntu ISO file that contains the Mac drivers? It’s different from the regular alternative ISO file and supposedly contains several drivers for Apple systems:

http://cdimage.ubuntu.com/releases/11.10/release/ubuntu-11.10-desktop-amd64+mac.iso

I don’t have a Bluetooth keyboard or mouse – I don’t like wireless input devices for exactly those problems that you have. And on top of that, they always deplete their batteries when I need them the most. I prefer cables, and that includes my network connection.

Anyway, maybe you should give that Mac ISO file a shot and maybe it will make your life easier. If not, borrow a USB keyboard and mice from somebody for the installation and configure your Bluetooth devices once you have a working installation.

Good luck!

I had a few issues that I hope to share to learn and help others who may vary in their installations

1: I used apt-get tasksel and sudo tasksel to get a clean lamp server install done.

2: I did not like having the cacti install in the /var/www so I altered it to /var/www/cacti and it works as long as you also edit the line if the /include/config.php about the location of cacti to /cacti/

3: This was the most frustrating – the cron.d/cacti cron. As if this fails then you are lost to understand what to do for new linux admins. Some things that helped me overcome my issues
> 1: manually kickstarting the poller is a good idea in case for whatever reason it is not able to work – usually a permission problem and also good to check your path
# sudo php /var/www/cacti/poller.php
(should give you a poller stat output and should also show up in the log) this way you know your poller can work.
>2 : Permissions of the cron user and the log folder you choose – I found that because my cron user was not able to write to /var/log/ folder the cron job failed and I did not see an error – maybe this is something I did as a mistake but it helped to check it
> 3 : # service cron stop and start to force the cron service to run
> 4 : make sure that during the install process that no other cron is running anywhere else – like admin or root user – #crontab -l will display this for the current user and sudo crontab -u [user] -l for other users.

This is the crontab command I finally got working after also changing the permissions based on the cacti -how-to
1- permissions run from the /var/www/cacti folder
chown www-data:www-data ./* -R
chmod 775 ./* -R
2: changed the log location to match the /var/www/cacti/log folder so I can go to the one place to see both logs
3: added the following lines to /etc/cron.d/cacti
MAILTO=root
*/1 * * * * www-data php /var/www/cacti/poller.php –force /var/www/cacti/log/poller-crond-error.log 2>&1

Hope it may help someone