locate command can be a powerful tool however in order to use it the database needs to be created/updated.
It is enough to execute
updatedb command in the terminal
and after a while you will be able to localize files.
By default open jdk package for CentOS(Red Hat) doesn’t contain java compiler therefore you may face problems setting up your dev environment.
Install the following package to get rest of java tools:
yum install java-ver-openjdk-devel
yum install java-1.7.0-openjdk-devel
You may receive a following dialog due to the gnome bug:
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
- Install samba repository.
sudo yum install samba -y
- Set user’s password
smbpasswd -a dartron
- Create a share folder.
- Edit samba configuration file.
At the end of the file, add these lines:
[share]Depending on your case the above may vary.
path = /share
available = yes
valid users = dartron
read only = no
browsable = yes
public = no
writable = yes
- Save and exit the file.
- Restart samba service.
service smbd restart
By default root login is disabled in Ubuntu 12.04 and newer.
Follow the steps to enable the logon:
- Open a terminal window.
- Using your favorite editor open the file with privileged rights:
sudo vim /etc/lightdm/lightdm.conf
- Append the line at the end of the file
- Set root password
sudo passwd root
- Reboot the machine and you will be able to login as root.
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
 ? 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).
- Navigate to /boot/ directory
- Run the command to recreate an initial RAM disk image:
dracut "initramfs-$(uname -r).img" $(uname -r)
- Reboot the machine
If the User Accounts dialog doesn’t contain ‘enter password’ option you can modify registry to automatically log user on.
- Click Start type regedit.exe
- Navigate to HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows NT -> Current Version -> Winlogon
- The entry should contain:
DefaultUserName -> Account name
DefaultPassword -> Your password
AutoAdminLogon -> 1
If the values don’t exist click Edit -> New -> String Value and create them.
- Save all the changes, reboot the machine and you will be logged in automatically.