Monthly Archives: June 2014

how to disable GNOME remote desktop keyring (vino)

You may receive a following dialog due to the gnome bug:

gnomeKeyringDialog

 

Already tested various solutions to that problem such as:
– Disabling/removing  GNOME Keyring Daemon in System -> Preferences -> Startup Applications
– Editing /etc/gconf/schemas/gnome-keyring.schemas and replacing TRUE with FALSE value

The only working solution was:
– Renaming /usr/bin/gnome-keyring-daemon to /usr/bin/gnome-keyring-daemon.bak
mv /usr/bin/gnome-keyring-daemon /usr/bin/gnome-keyring-daemon.bak

how to share files – samba

  1. Install samba repository.
    sudo yum install samba -y
  2. Set user’s password
    smbpasswd -a dartron
  3. Create a share folder.
    cd /
    mkdir share
  4. Edit samba configuration file.
    vim /etc/samba/smb.conf
    At the end of the file, add these lines:
    [share]
    path = /share
    available = yes
    valid users = dartron
    read only = no
    browsable = yes
    public = no
    writable = yes
    Depending on your case the above may vary.
  5. Save and exit the file.
  6. Restart samba service.
    service smbd restart

enable root gui login ubuntu 12.04

By default root login is disabled in Ubuntu 12.04 and newer.
Follow the steps to enable the logon:

  1. Open a terminal window.
  2. Using your favorite editor open the file with privileged rights:
    sudo vim /etc/lightdm/lightdm.conf
  3. Append the line at the end of the file
    greeter-show-manual-login=true
  4. Set root password
    sudo passwd root
  5. Reboot the machine and you will be able to login as root.

kernel panic – not syncing: VFS: unable to mount root fs on unknown-block(0,0)

This error has been thrown while upgrading from Red Hat 6.3 Santiago to Red Hat 6.5
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper Not tainted 2.6.32-431.17.1.el6.i686 #1
Call Trace:
[] ? panic+0x6e/0x122
[] ? mount_block_root+0x1dd/0x274
[] ? prepare_namespace+0x14b/0x191
[] ? sys_access+0x1f/0x30
[] ? kernel_init+0x226/0x234
[] ? kernel_init+0x0/0x234
[] ? kernel_thread_helper+0x7/0x10

The error was most probably caused by some kernel bug (see references).

SOLUTION:
dracut

  1. Navigate to /boot/ directory
  2. Run the command to recreate an initial RAM disk image:
    dracut "initramfs-$(uname -r).img" $(uname -r)
  3. Reboot the machine

References:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html