joi, 26 decembrie 2013

Ninite - surprize surprize ...

De curand dupa ce am reparat niscai sisteme windowziste din tagma lui xp am avut surpriza sa vad ca pe ninite cu ie6 implicit ... NEMA aplicatii ... pe celelate sisteme  nu e nici o problema ... deci rezolvarea? ... :
1- instaklati firefox
2-porniti pagina noua ptivata
3-intrati pe ninite si aveti aplicatiile in toata splendoarea

ps. daca aveti un browser portabil folosit-il pe acela ...

sâmbătă, 15 iunie 2013

mngm. serviciilor la boot-are

HowTo: Speed up ubuntu boot process - the way you can feel it.
  1. HowTo: Speed up ubuntu boot process - the way you can feel it. - updated

    This HowTo is for those who complaint ubuntu boot-up speed is pretty slow but not willing to install any alternative tools to speed up. The way I use here is not the altimate solution by any means but it does make differences and it does work. Everything done below is by tuning the boot process itself and because everyone's computer might be different, there is a little risk that something below might break your system. Take your own judgment before you perform a change and always good to do a backup for the /etc dir.

    **This HowTo is mainly for laptops and desktops, not for servers.**

    Due to Ubuntu Edgy Eft (6.10) is using upstart to manage the init process and it already has reducing boot time built in mind, many things have been changed. This thread is mainly for any ubuntu version older than 6.10. For how to customize upstart, please refer to upstart threads in this forum. The following is a very interesting and useful WiKi on how to further speed up the boot process by taking out some useless bootup/shutdown processes...

    Suggestions for this HowTo:
    1. I hope you learn something from here but not just a simple copy. So please, **DO NOT** follow exactly what I did and copy to your box. Read the descriptions of services and use your own judgment to determine if you need to keep them on or not. For instance, I turned GDM off on mine to boot to console, but if you do not feel confortable to see console at all, you should keep GDM or KDM on to boot directly to GUI.
    2. If you have a question about a boot up service and not really sure what it does, post a question here and see if anybody can help you. Ask before you do if you don't know. The bottom line to be safe is to leave a service on rather than turn it off if you do not understand.
    3. If you see a boot up service that you have but not in here, let us know what it does just like what I did here - give some descriptions and suggestions on whether it should be on or off on a normal laptop or desktop environment.

    Color reference : service I turned on
    service I turned off

    Screen shots contrib'ed by domino for the initial bootup settings. A great reference for those who mess up on runlevels... Thanks!!

    Page 1:

    Page 2:

    I. Install a tool - sysv-rc-conf. It is a perl based boot process adjustment tool.
    sudo apt-get update
    sudo apt-get install sysv-rc-conf
    It gives you a way to esaily config the boot process and runlevel configuration, but its not necessary if you want to do it manually by linking/unlinking the files... Its up to you.

    II. Ok, that's all we need. Now let's fire it up by
    sudo sysv-rc-conf
    and analyze each service one by one. **Note:** Some services I have here you might not have, perfectly ok. If some you have but I don't, then you will need to investigate on your own or ask here... But this HowTo should cover most of them...

    Throw a littel bit of runlevel knowledge here before we start messing them up.... All the boot processes are executed in sequence as following:
    runlevel S: the first runlevel in boot process. /etc/init.d/rcS script will be invoked to start and all the processes underneath /etc/rcS.d will be executed.
    runlevel 1: the single user mode. All processes underneath /etc/rc1.d will be executed.
    runlevel 2,3,4,5: in debain system, the multi-user env, may not may not include GUI. The same, processes under each of the corresponding dirs will be run. **Note** this is different than RedHat, SuSE, and other RPM based systems.
    runlevel 0: computer shutdown.
    runlevel 6: computer reboot.

    ok, back to sysv-rc-conf:

    1. acpi-support - You'd better leave it on the default runlevel. The default is 2,3,4,5.
    2. acpid - The acpi daemon. These two are for power management, quite important for laptop and desktop computers, so leave them on. The default is 2,3,4,5
    3. alsa - If you use alsa sound subsystem, yes leave it on. But if you have the service below, its safe to be off. The default is off when alsa-utils is on.
    4. alsa-utils - On my system, this service supercedes the alsa, so I turn off the alsa and turn this on at S level. **Note**, I mean "turn off" is to remove all "X" at all runlevels. If you don't have it on your system, no problem. Just keep going. The default is S runlevel.
    5. anacron - A cron subsystem that executes any cron jobs not being executed when the time is on. Most likely you've probably turned your computer off when a certain cron job time is ready. For example, updatedb is scheduled at 2am everyday, but at that moment, you computer is off, then if anacron service is on, it will try to catch up that updatedb cron... I turn it off cause it didn't turn my laptop off very offen, but its totally up to you for this one. The default is 2,3,4,5
    6. apmd - This is the one that confused me a quite bit. I have acpid on already and what's the benefits of having apmd on too? If you computer is not that old which can't even support acpi, then you may try to turn this off. I did anyway. The default is 2,3,4,5
    7. atd - like cron, a job scheduler. I turned it off. The default is 2,3,4,5
    8. binfmt-support - Kernel supports other format of binary files. I left it on. The default is 2,3,4,5
    9. bluez-utiles - I turned it off. I don't have any bluetooth devices. The default is 2,3,4,5
    10. bootlogd - Leave it on. The default is S.
    11. cron - Leave it on. The default is 2,3,4,5
    12. cupsys - subsystem to manager your printer. I don't have so I turned it off, but if you do, just leave it on. The default is 2,3,4,5
    13. dbus - Message bus system. Very important, leave it on. The default is 2,3,4,5
    14. dns-clean - Mainly for cleaning up the dns info when using dial-up connection. I don't use dial up, so I turn it off. The default is S.
    15. evms - Enterprise Volumn Management system. I turned it off. The default is S.
    16. fetchmail - A mail receving daemon. I turned it off. The default is 2,3,4,5
    17. gdm - The gnome desktop manager. I turned it off anyway since I get use to boot to console first. This is up to you if you want to boot directly to GUI. The default is 2,3,4,5
    18. gdomap - Actually I have no idea why this one should on. I didn't see any other systems have this daemon, so I turned it off and I don't feel I lose anything. Any benefits to have it on a loptop or desktop? The default is 2,3,4,5
    19. gpm - Mouse support for console. If you feel you'd better have a mouse on console, go turn it on at runlevel 1 and 2. That's all you need. The default is 2,3,4,5
    20. halt - Don't change it. The default is 0.
    21. hdparm - tuning harddisk script. I removed the 2,3,4,5 runlevel but add it to S runlevel. I feel that opening DMA, 32bit I/O, etc eariler will benefit the rest of the processes. Also I changed the original script to a very simple one that I made myself. I feel useless to put all those redundant checks if I know what I am doing. The configuration file is /etc/hdparm.conf. The default is 2,3,4,5
    22. hibernate - If your system support hibernate, leave it on. Otherwise, its useless for you. The default is S.
    23. hotkey-setup - This daemon setup some hotkey mappings for Laptop. Manufacturers supported are: HP, Acer, ASUS, Sony, Dell, and IBM. If you have a laptop in those brands, you can leave it on, otherwise, this might not have any benefits for you. The default is 2,3,4,5
    24. hotplug and hotplug-net #activating hotplug subsystems takes time. I'd consider to turn them off. I did some changes in my /etc/network/interfaces file. Instead of mapping my wireless card during hotplug process, I set it up to auto. So I can turn them off. I've tested even I turned them off, ubuntu can still detect my usb driver, my digital camera, etc. So I think its pretty safe to turn them off. **Note** If you find your sound card doesn't work after turning hotplug service off, you can turn it back. Or edit /etc/modules file to add your sound card's driver module. Tested out the later one is faster. The default is S.
    25. hplip - HP printing and Image subsystem. I turned it off. The default is S.
    26. ifrename - network interface rename script. Sounds pretty neat but I turned it off. Mainly for managing multiple network interfaces names. Since I have a wireless card and an ethernet card, they all assigned eth0 and ath0 from kernel, so its not really useful for me. The default is S.
    27. ifupdown and ifupdown-clean - Leave it on. They are network interfaces activation scripts for the boot time. ifupdown default is 0,6,S and ifupdown-clean is S.
    28. inetd or inetd.real - take a look your /etc/inetd.conf file and comment out any services that you don't need. If there aren't any services there, then its very safe to turn them off. The default is 2,3,4,5
    29. klogd - Leave it on. The default is 2,3,4,5
    30. laptop-mode - A service to tweak the battery utilization when using laptops. You can leave it on. The default is 2,3,4,5
    31. linux-restricted-modules-common - You need to see if you really have any restricted modules loaded on your system. Since I need madwifi ath_pci module, so I left it on. The restricted modules can be found from /lib/linux-restricted-modules. If you find that you are not using any of the restricted modules, then its ok to turn it off. The default is 0,6, and S.
    32. lvm - I don't use it so I turned it off. Leave it on if you *DO* have lvm. The default is S.
    33. makedev - Leave it on. The default is 2,3,4,5
    34. mdamd - Raid management tool. I don't use it so I turned it off. The default is 2,3,4,5
    35. mdamd-raid - Raid tool. If you don't have Raid devices, turn it off. The default is S.
    36. module-init-tools - Load extra modules from /etc/modules file. You can investigate your /etc/modules file and see if there is any modules that you don't need. Normally, this is turned on. The default is S.
    37. mountvirtfs - mount virtual filesystems. Leave it on. The default is S.
    38. networking - bring up network interfaces and config dns info during boot time by scaning /etc/network/interfaces file. Leave it on. The default is 0,6,S
    39. ntpdate - Sync time with the ubuntu time server. The default is S. QUOTED: "If you are dual-booting with Windows, it is probably a good idea to leave ntpdate on. Windows can only deal with the hardware clock set to local (not UTC) and Linux needs ntpdate to correct this, otherwise your clock will increase an hour everytime you boot into Linux from Windows." Thanks dejitarob for the update!! I don't have dual boot, so I turned it off, but if you have multiple systems, suggestion is to turn it on.
    40. nvidia-kernel - I compiled the nvidia driver by myself, so its useless for me now. If you use the ubuntu nvidia driver from the restrict modules, just leave it on. The default is 1,2,3,4,5
    41. pcmcia - Active pcmcia device. I changed it to start on 0,6,S runlevel instead of on each 2,3,4,5 cause I feel its better to have hardware device ready at first. Also, useless if you are using desktop which doesn't have pcmcia card. So in that case, turn it off please. The default is 2,3,4,5
    42. portmap - daemon for managing services like nis, nfs, etc. If your laptop or desktop is a pure client, then turn it off. The default is 2,3,4,5,0,6,S
    43. powernowd - client to manage cpufreq. Mainly for laptops that support CPU speed stepping technology. Normally, you should leave it on if you are configuring a laptop, but for desktop, it might be useless. The default is 2,3,4,5
    44. ppp and ppp-dns - Useless to me. I don't have dial-up. The default for ppp is 2,3,4,5 and pppd-dns is S.
    45. readahead - **Thanks mr_pouit!** It seems readahead is a kind of "preloader". It loads at startup some libs on memory, so that some programs will start faster. But it increases startup time for about 3-4 seconds. So, you can keep it... or not . **update**, I tested and I just didn't feel difference loading programs. So I decided to turn it off. If you have a reason to keep it on, please do so. The default is S
    46. reboot - Don't change it. The default is 6
    47. resolvconf - Automatically configuring DNS info according to your network status. I left it on. The default is S.
    48. rmnologin - Remove nologin if it finds it. It wouldn't happen on my laptop, so I got rid of it. The default is 2,3,4,5
    49. rsync - rsync daemon. I don't use it on my laptop, so turned it off. The default is 2,3,4,5
    50. sendsigs - send signals during reboot or shutdown. Leave it as it is. The default is 0,6
    51. single - Active single user mode. Leave it as it is. The default is 1
    52. ssh - ssh daemon. I need this so I turned it on. The default is 2,3,4,5
    53. stop-bootlogd - stop bootlogd from 2,3,4,5 runlevel. Leave it as it is. The default is 2,3,4,5
    54. sudo - check sudo stauts. I don't see any good to run it everytime on a laptop or desktop client, so I turned it off. The default is S
    55. sysklogd - Leave it as it is. The default is 2,3,4,5
    56. udev and udev-mab - Userspace dev filesystem. Good stuff, I left them on. The defaults are all S runlevels.
    57. umountfs - Leave it as it is. The default is 0,6
    58. urandom - Random number generator. Might not useful but I left it on. The default is 0,6,S
    59. usplash - Well, if you really want to see the nice boot up screen, leave it as it is. I just turned it off anyway. If you want to turn it off, you also need to edit /boot/grub/menu. lst file to comment out the splashimage line and get rid of the splash kernel boot option. The default is 2,3,4,5
    60. vbesave - video card BIOS configuration tool. Its able to save your video card status. I left it on. The default is 2,3,4,5
    61. xorg-common - setup X server ICE socket. I moved it from starting at runlevel S to runlevel 2,3,4,5. Since I don't need this if I boot to single user mode. This way it wouldn't occupy time during the initial booting. The default is 2,3,4,5
    ============ My bootup services end up here============

    ============ Some services from others================
    62. adjtimex - This is a kernel hw clock time adjusting too. Normally, you shouldn't see this on your boot up list. In very rare case if you do see its on your boot up process, then there might be a reason why it is on, so better leave it that way. In my case, it is off.
    63. dirmngr - A certification lists management tool. Work with gnupg. You will have to see if you need it or not. In my case, I turned it off. Default runlevel 2,3,4,5
    64. hwtools - A tool to optimize irqs. Not sure what's the benefits of turning it on. In my case, I turned it off.
    65. libpam-devperm - A daemon to fix device files permissions after a system crash. Sounds pretty good, so I left it on.
    66. lm-sensors - If you matherboard has builtin some sensor chips, it might be helpful to see hw status via userspace. I ran it and it said "No sensors found", so I turned it off.
    67. screen-cleanup - A script to cleanup the boot up screen. Well, turn on or off is up to you. In my case, I left it on. The default is S
    68. xinetd - A inetd super daemon to manage other damons. In my system, the xinetd is managing chargen, daytime, echo and time (find them from /etc/xinetd.d dir), I care none of them, so I turned it off. If you do have some important services configured under xinetd, then leave it on.

    III. Alter the /etc/inittab file
    vi /etc/inittab
    then comment out tty4,tty5, and tty6. Just leave tty1, tty2, and tty3. Three vts should be enough for a laptop or desktop user. Save the file.

    IV. Ok, now, we can reboot our box and see how it goes. From what I've tested, before I got tons of services stopped, the whole process is about 85 secs to 90 secs to boot to console. (At that time, I also has samba and nfs services turned on which I shouldn't. Apparently, I turned them off too). After this change, the whole boot up process took about 50 secs. I have a P4M 1.8G CPU laptop. Some of the high-end desktops or laptops should take even less time.

    **UPDATE**: speed up/clean system reboot or shutdown process.
    1. start sysv-rc-conf by issuing:
    sudo sysv-rc-conf
    2. ok, open your eyes and look very carefully for those SERVICES THAT DO NOT HAVE A "X" ON ANY RUNLEVELS (Any runlevel means 1,2,3,4,5,6, and S), write them down one by one. Don't make mistakes here. Double check after you've done. Thanks ice60 for wording recommendation!
    3. quit sysv-rc-conf.
    cd /etc/rc0.d
    - This is for the system shutdown process.
    5. ok, now,
     ls K*
    will list all links starting from UPPERCASE letter "K". Compare with your list, change each of the filename containing the service name in your list to start from a lowercase "k". For example, in your list, you have ppp service (which means ppp is turned off at all runlevels), then you can do like:
    sudo mv K00ppp k00ppp
    . You just change the UPPERCASE K to lowercase k, keep the rest the same. Do this on all of the services in your list.
    cd ../rc6.d
    - This is for the system reboot process.
    7. ok, you should see similar things here too. So do the same thing here as you did on rc0.d.
    8. Now, you reboot and shutdown process should be cleaned up and faster.

    The explanation for what you did is pretty simple. The /etc/rc and /etc/rcS scripts run start on each link on each runlevel by scaning if it is starting with a UPPERCASE "S" and run stop on each by scaning if it is starting with a UPPERCASE "K". So for reboot and shutdown runlevels, the most thing we care is the "K" links cause for those services not running on all runlevels, its just not needed to stop them. They are not runing at all. If some day you want to turn some of the services back on, just change the lowercase "k" to UPPERCASE "K". That's all.

    Anyway, it is not intend to work on servers, but I did try on one of my servers has 2.7G P4 and 1.5G mem. It brought the boot process down to 31 secs. I calc'ed it with my watch. Besides, this is with my ftp server and nfs server started on boot time.

    For all of those that having HAL failure problem, try this:
    1. change acpi-support from S to 2,3,4,5
    2. change acpid from S to 2,3,4,5
    3. change dbus from S to 2,3,4,5
    4. Reboot. Go to the console and do
    ps -aef|grep hald
    . If hald service is up, then your dbus subsystem is running fine now. Try it.

    Great comments added by bodhi.zazen. Thanks!!
    First we should make sure we are left with a bootable system and have backups.

    Since we are changing our boot process:

    Step 1- Make a bootable GRUB floppy.

    Step 2- Backup
    Is there any need to back up more then menu.1st, /etc/init.d, /etc/rcS.d, and /etc/rc*.c ( *= 0,1,2,3,4,5,6)?
    mkdir /~/bakup.files
    sudo cp -P /etc/init.d /~/backup.files
    sudo cp -P /boot/grub/menu.1st /~/backup.files
    sudo cp -P /etc/rc*.d /~/backup.files
    Although a backup of /etc is nice, is it not overkill for this exercise?

    Setp 3- Know you Ubuntu Root device (hda1, hdb1, hda2,) and kernel (the numbers in "vmlinuz").
    Location of kernel is /boot

    Step 4- Modify runlevels.
    ie as system boots (at default) the scritps in rcS.d are run first, then rc2.d

    Therefore, if you disable a script in "S", enable the script in runlevel 2
    This should guarantee your system will remain bootable to the default run level (2)

    In Ubuntu the default run level is 2
    Modify only 1 test run level at a time. Choose a custom run level (I will use 3 for the rest of this post, you can use 3,4, or 5).
    After modifying the runlevel test without re-booting
    sudo init 3
    This will change to run level 3
    Now check your system.
    Problems? Return to default run level and re-configure run level 3
    sudo init 2
    No problem -> Boot from floppy
    No problem, boot from floppy.
    When booting (from diskette) to the default run level, the "kernel" line looks like:
    kernel=/boot/vmlinuz- root=/dev/hda1 ro quiet splash
    In menu.1st this looks like this:
    kernel /boot/vmlinuz- root=/dev/hda1 ro quiet splash
    To boot to run 3 (from GRUB diskette), add a "3" at the end of the line
    kernel=/boot/vmlinuz.... root=/dev/..... ro quiet splash 3
    Note: the number 3 was added at the end (without quotes)
    time boot process.
    If OK boot again from floppy (to default run level)
    kernel=/boot/vmlinuz..... root=/dev/....
    Note: no number 3 at the end of this line
    time boot process
    This is the default boot and you can measure any time savings.
    booting from a floppy to compair apples to apples
    If OK you can now change the default run level (or not)
    There is more then 1 way to do this
    My preferance is to leave the default runlevel unmodified
    This leaves the default boot process as a future referance
    Change the default boot level
    sudo nano /boot/grub/menu.1st
    add init=3 to end of line

    kernel /boot/vmlinuz- root=/dev/hda1 ro quiet splash 3

    Or create 2 Ubuntu titles, one for each run level.


    Edit /etc/inittab

    Step 4- Modify shutdown scripts if desired.

    This process should guide users through a logical process of modifying boot scripts without generating a non-bootable system. Backups were made "just in case" but really should not be needed.

    Last edited by i3dmaster; January 15th, 2007 at 10:40 PM. Reason: Add comments made by bodhi.zazen.
    alte surse:

luni, 15 aprilie 2013


Posted by iheartubuntu on Saturday, February 04, 2012

Canon is well known for their large printer selection. Unfortunately Canon has, up until this point, only provided printer drivers for Windows and Mac computers. Canon did release some printer drivers for linux, but the majority of Canon printer owners were out of luck.

About a year ago my dad bought a new computer at Fry's electronics store and along with the computer came a free Canon ip2600 printer. It was difficult to say the least to get the printer working in Ubuntu 10.10. Luckily Canon provided 32 bit drivers after some time, and then someone converted this to work on 64 bit systems as well.

Ubuntu 11.10 DOES see and attempt to install the Canon printer of mine, although trying to print a domcument does nothing. Thankfully, there is now a PPA available for many many commonly used Canon printers.

To install these Canon printer driver for Ubuntu you need to add the PPA below in your Ubuntu system. Open a "terminal" window and copy and paste these commands:

sudo add-apt-repository ppa:michael-gruz/canon
sudo apt-get update

(If don`t work tray changes Source with :
  Canon printer driver daily.

deb precise main 
deb-src precise main 


Make sure to disconnect the Canon printer from your computer first.
Now copy and paste your appropriate install command based on your printer:

Canon iP100 series Ubuntu Driver

sudo apt-get install cnijfilter-ip100series

Canon iP1800, iP1880, iP1890 Ubuntu Driver

sudo apt-get install cnijfilter-ip1800series

Canon iP1000 series Ubuntu Driver

sudo apt-get install cnijfilter-pixmaip1000series

Canon iP1500 series Ubuntu Driver

sudo apt-get install cnijfilter-pixmaip1500series

Canon iP1900 series Ubuntu Driver

sudo apt-get install cnijfilter-ip1900series

Canon iP2200 series Ubuntu Driver

sudo apt-get install cnijfilter-ip2200series

Canon iP2500 series Ubuntu Driver

sudo apt-get install cnijfilter-ip2500series

Canon iP2600 series Ubuntu Driver

sudo apt-get install cnijfilter-ip2600series

Canon iP2700 series Ubuntu Driver

sudo apt-get install cnijfilter-ip2700series

Canon iP3300 series Ubuntu Driver

sudo apt-get install cnijfilter-ip3300series

Canon iP3500 series Ubuntu Driver

sudo apt-get install cnijfilter-ip3500series

Canon iP3600 series Ubuntu Driver

sudo apt-get install cnijfilter-ip3600series

Canon iP4200 series Ubuntu Driver

sudo apt-get install cnijfilter-ip4200series

Canon iP4500 series Ubuntu Driver

sudo apt-get install cnijfilter-ip4500series

Canon iP4700 series Ubuntu Driver

sudo apt-get install cnijfilter-ip4700series

Canon iP4800 series Ubuntu Driver

sudo apt-get install cnijfilter-ip4800series

Canon iP5200 series Ubuntu Driver

sudo apt-get install cnijfilter-ip5200series

Canon iP6600 series Ubuntu Driver

sudo apt-get install cnijfilter-ip6600series

Canon iP7500 series Ubuntu Driver

sudo apt-get install cnijfilter-ip7500series

Canon MG5100 series Ubuntu Driver

sudo apt-get install cnijfilter-mg5100series

Canon MG5200 series Ubuntu Driver

sudo apt-get install cnijfilter-mg5200series

Canon MG6100 series Ubuntu Driver

sudo apt-get install cnijfilter-mg6100series

Canon MG8100 series Ubuntu Driver

sudo apt-get install cnijfilter-mg8100series

Canon MP140 Ubuntu Driver

sudo apt-get install cnijfilter-mp140series

Canon MP160 series Ubuntu Driver

sudo apt-get install cnijfilter-mp160series

Canon MP190 series Ubuntu Driver

sudo apt-get install cnijfilter-mp190series

Canon MP210 series Ubuntu Driver

sudo apt-get install cnijfilter-mp210series

Canon MP240 series Ubuntu Driver

sudo apt-get install cnijfilter-mp240series

Canon MP490 series Ubuntu Driver

sudo apt-get install cnijfilter-mp490series

Canon MP500 series Ubuntu Driver

sudo apt-get install cnijfilter-mp500series

Canon MP510 series Ubuntu Driver

sudo apt-get install cnijfilter-mp510series

Canon MP520 series Ubuntu Driver

sudo apt-get install cnijfilter-mp520series

Canon MP540 series Ubuntu Driver

sudo apt-get install cnijfilter-mp540series

Canon MP550 series Ubuntu Driver

sudo apt-get install cnijfilter-mp550series

Canon MP560 series Ubuntu Driver

sudo apt-get install cnijfilter-mp560series

Canon MP600 series Ubuntu Driver

sudo apt-get install cnijfilter-mp600series

Canon MP610 series Ubuntu Driver

sudo apt-get install cnijfilter-mp610series

Canon MP630 series Ubuntu Driver

sudo apt-get install cnijfilter-mp630series

Canon MX320 series Ubuntu Driver

sudo apt-get install cnijfilter-mx320series

Canon MX330 series Ubuntu Driver

sudo apt-get install cnijfilter-mx330series

Canon MX350 series Ubuntu Driver

sudo apt-get install cnijfilter-mx350series

Canon MX360 series Ubuntu Driver

sudo apt-get install cnijfilter-mx360series

Canon MX410 series Ubuntu Driver

sudo apt-get install cnijfilter-mx410series

Canon MX420 series Ubuntu Driver

sudo apt-get install cnijfilter-mx420series

Canon MX860 series Ubuntu Driver

sudo apt-get install cnijfilter-mx860series

Canon MX870 series Ubuntu Driver

sudo apt-get install cnijfilter-mx870series

Canon MX880 series Ubuntu Driver

sudo apt-get install cnijfilter-mx880series

Canon MP640 series Ubuntu Driver

sudo apt-get install cnijfilter-mp640series

Canon Pixus 550 series Ubuntu Driver

sudo apt-get install cnijfilter-pixus5510iseries

Canon Pixus 560 series Ubuntu Driver

sudo apt-get install cnijfilter-pixus560iseries

Canon Pixus 850 series Ubuntu Driver

sudo apt-get install cnijfilter-pixus850iseries

Canon Pixus 860 series Ubuntu Driver

sudo apt-get install cnijfilter-pixus860iseries

Canon Pixus 865 series Ubuntu Driver

sudo apt-get install cnijfilter-pixus865iseries

Canon Pixus 950 series Ubuntu Driver

sudo apt-get install cnijfilter-pixus950iseries

Canon Pixus 990 series Ubuntu Driver

sudo apt-get install cnijfilter-pixus990iseries

Canon Pixus ip3100 series Ubuntu Driver

sudo apt-get install cnijfilter-pixusip3100series

Canon Pixus ip4100 series Ubuntu Driver

sudo apt-get install cnijfilter-pixusip4100series

Canon Pixus ip8600 series Ubuntu Driver

sudo apt-get install cnijfilter-pixusip8600series

After the Canon printer driver is installed, connect the Canon printer to your computer and turn it on. Your printer will automatically be detected by the system.

vineri, 12 aprilie 2013

Brosix Free - Alternative Yahoo Mess. , Skype

Download Brosix for Personal Use

Get Brosix for Personal Use

Secure communication, high privacy, no advertisements, and completely free.

Want to download the Enterprise version? Click here.

If you want to create a private Instant Messenger for your company, organization, or team, check out Brosix Enterprise or compare Brosix Personal and Brosix Enterprise.



Brosix for Windows

Installs Brosix on a Windows computer or laptop.


Installer instructions
Portable instructions

download_icon Installer (.exe)


download_icon Portable (.zip)



Brosix for Mac

Use all Brosix features on a Mac computer.



download_icon Download (.dmg)



Brosix for Android

Stay in touch on your Android phone or tablet.



download_icon Download

from Google Play



Brosix for iOS

It runs on iPhone, iPad and iPod touch.



download_icon Download

from iTunes



Brosix for Linux

Use all Brosix features on a Linux computer or laptop.



download_icon Ubuntu (.deb)


download_icon Fedora (.rpm)


download_icon Portable (.tar.gz)


Web client

Brosix Web Client

Use Brosix right from your web browser. No installation is required.




Have fun and enjoy the Free Version of Brosix!


Looking for Enterprise Instant Messenger? click here.


Brosix Enterprise

With Brosix Enterprise, you can create your own private Instant Messenger in a minute. It will have all the features you love about Brosix, plus you also get a full control over the Instant Messaging group you create. This is suitable for companies, organizations, and teams that want enterprise-level communication through the Internet.

Compare Brosix Personal and Brosix Enterprise

joi, 11 aprilie 2013

yahoo messenger cu webcam si audio chat pe ubuntu 12.04

Install Gyachi Yahoo Messenger in Ubuntu 12.04 | Handy Tutorial

Install Gyachi Yahoo Messenger in Ubuntu 12.04

GYachE Improved (gyachi) is a gtk+ Yahoo Client with webcam and room voice chat features. It’s an unofficial fork of the GyachE, intended for bug-fixes and further development. This simple tutorial is going to show you how to install it in Ubuntu using PPA.

UPDATE: Now the ppa has updated with 12.10 Quantal support. This tutorial also works on Ubuntu 12.10.

Install GYachE Improved (Gyachi) from PPA:

The PPA provides the packages of Gyachi for Ubuntu 12.04, 11.10, 11.04, and 10.04. Theses packages are experimental. Use them at your own risk.

To add the PPA repository, open Ubuntu Software Center -> Edit -> Software Sources… -> Other Software tab. Click Add button and type in this code to add PPA:


Then hit Ctrl+Alt+T, copy and paste the 2 commands into terminal one by one and hit enter to update and install:

sudo apt-get update
sudo apt-get install gyachi

Once installed, search for and open it from the Unity dash.


  1. sali says:

    Special thanks,about three days im tryin’ to install Gyachi at the last i found this solution.Thanksssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss

  2. Paul says:

    This made it SO much easier – thank you. If only these notes were with the download file I might still have some hair. ;-)

  3. Mike Hammer says:

    Was not able to make this work on mint 14 thats based on ubuntu 12.10

  4. endang says:

    Thank you very much, I’ll try first

Leave a Reply

Your email address will not be published. Required fields are marked *

marți, 9 aprilie 2013

rezolutia 1024/600 minilaptop, EEEPC

puteti rezolva problema rezolutiei de 1024/600 modificand-o in 1024/768 punand in start-up o comanda:
xrandr --fb 1024x768 --output LVDS1 --panning 1024x768 --scale 1x1.28

How to clean up Ubuntu

How to clean up Ubuntu - Easy Linux tips project

This is Tux, the official mascot of Linux

Ubuntu 12.10 Quantal Quetzal has been released!

A star of the Ubuntu family: Xubuntu!

16days until
Ubuntu 13.04 Raring Ringtail

Release schedule of Ubuntu 13.04 Raring Ringtail

How to clean up Ubuntu

Back to the home page

Never use cleaning applications like Bleachbit or Computer Janitor! They are very risky and may damage your system beyond repair. There are a few safe cleaning actions, which I'll describe below.

Ubuntu doesn't get polluted much over time. It even doesn't need defragmentation. The only cleaning actions you might want to do in Ubuntu, are the following:

Clear the updates cache

1. Use Ubuntu Software Center to install Synaptic Package Manager.

Click on the grey Ubuntu logo (Dash home). Query: synaptic.
Click on Synaptic Package Manager

Settings - Preferences - Files

Put the dot at: Delete downloaded packages after installation

Press the button: Delete cached package files

Remove unused remains of uninstalled software

2. Still in Synaptic Package Manager:

In the lower left corner of the Synaptic window, click on the button Status.
Then, in the upper left corner, click the following line:
Not installed (residual config)

Mark all shown packages for complete removal and click Apply.

Clear the thumbnail cache

3. For each shown picture, Ubuntu automatically creates a thumbnail, for viewing in the file manager.

Over time, the number of thumbnails can increase dramatically. Moreover, the thumbnail cache will eventually contain many superfluous thumbnails of pictures that don't exist anymore.

My advice is therefore, to clear the thumbnail cache every six months or so. The quickest way is to use the terminal:

Click on the grey Ubuntu logo (Dash home). Query: terminal.
Click on Terminal.

Type (use copy/paste to avoid errors):
rm -f ~/.thumbnails/normal/*

Press Enter.

You can permanently limit the size of the thumbnail cache as follows:

Click on the grey Ubuntu logo (Dash home). Query: terminal.
Click on Terminal.


Press Enter

Note: in 12.04 you have to install the package dconf-tools first (not necessary in 12.10).

In dconf-editor, click on the small triangle to expand a category. Like this, click your way to:
org - gnome - desktop - thumbnail_cache
.... and set the maximum-age to 90 (press Enter) and the maximum-size to 64 (press Enter again).

Close dconf-editor.

(continued in the column on the right)

This website is being sponsored by Google Ads.

Are you using an ad blocker? Then you're also blocking my earnings from advertisements....

If you wish to support this website, you can (temporarily?) switch off your ad blocker. Thanks in advance....

Remove old kernels

4. After a kernel update, the old kernel still shows in the Grub boot menu, under the header: "Previous Linux versions" (In Ubuntu 12.10 this header is called "Advanced options for Ubuntu"). Because you might want to start your machine with the old kernel, if the new kernel doesn't function well.

So far, so good. But having more than one redundant kernel, is superfluous and a waste of disk space. This is how you can remove old kernels and thereby clean up the Grub boot loader menu as well:

An Ubuntu version sticks to the main kernel version it had on release date. Kernel updates are only minor versions of that main version.

For example: Ubuntu 12.04 was first released with 3.2.0-23. It will always remain 3.2.0, but the minor version number receives regular updates.

Now let's get started (based on the example of 12.04):

Click on the grey Ubuntu logo (Dash home). Query: synaptic.
Click on Synaptic Package Manager.

kernel 3.

(use the Search button and not the buggy Quick search)

Mark all installed kernels that you want to remove, for "complete removal". You should find that each kernel version has at least three installed packages; remove all three of them (usually two headers packages and one image package). Press the Apply button in the panel.

Tip: leave the newest redundant old kernel intact, just to be on the safe side.

Now reboot your computer. The Grub menu should be cleansed.

Ready! That's all you ever need to do. Doing more is risky and not advisable.

Note: don't use cleaning applications like Computer Janitor. They are dangerous and at best nearly useless.

The registry

5. There's no need to clean the registry of Linux, as it can't get polluted in the first place. For the following reasons:

- Only the operating system itself has a central registry. The configurations of the applications aren't in there, because they don't have access to it. So they can't mess it up. They place their own default settings in their own folders in the system.

- applications place upon installation a hidden settings file in the personal folder of each user. That's the only settings file that a user has access to. More or less like MS-DOS did, when each application only created it's own .ini file with it's settings.

- each user has his own hidden copy of the central registry in his personal folder. That copy is the only thing that he can mess up, not the registry of another user account.

Want more?

Do you want more tips and tweaks for Ubuntu? There's a lot more of them on this website! For example 10 fatal mistakes that you'll want to avoid in Ubuntu.

To the content of this website applies a Creative Commons license.