iGh0st/Utilitesetup

## Utilitesetup
1.Verify root access

/*Drag & Drop sudo
This is a trick from this thread on the Ubuntu Forums.

Create a launcher with the following command:

gksudo "gnome-open %u"
When you drag and drop any file on this launcher (it's useful to put it on the desktop or on a panel), it will be opened as Root with its own associated application. This is helpful especially when you're editing config files owned by Root, since they will be opened as read only by default with gedit, etc
https://help.ubuntu.com/community/RootSudo
There are two different folders called the "root" folder: / (the root of the filesystem, which is really the only folder that should ever be called the "root folder"), and /root (the root user's home directory). During the normal course of operation (i.e., except while performing administrative tasks), users cannot create new files in / or /root.

You should not change the ownership or permissions of either directory (changing them for / in particular could break things very badly, perhaps even beyond creating security problems depending on what assumptions your applications and services make about the ownership and permissions of /).

If you have the gksu package installed, you can run gksudo nautilus to open a root-owned file browser window. If you do this, please be extra careful to only use it for tasks where you must be root, and to close it when you're done (so you don't later confuse it with an ordinary Nautilus window).

If you don't have gksu installed and don't want to install it, sudo -i nautilus or sudo -H nautilus are reasonably safe. (In contrast, if you were to use plain sudo nautilus, you might have to fix some things in your home directory to get Nautilus to work properly again when you're not running it as root.)

However, usually you don't need to do that either. You rarely have to manually edit the top-level contents of / or the contents of /root. I recommend providng more information--or asking a new question--to explain exactly what you're trying to accomplish. The particular task you need to do will determine how you should proceed.

Finally, a note on lost+found. This stores files recovered in filesystem repair operations. Since such files could be from anywhere in the filesystem, it's necessary to require root permissions to access them (or any information on the system could potentially be accessed by someone who is not an administrator). If you think there may be files there that you wish to reclaim, you can check by running

sudo ls /lost+found
in a Terminal window (Ctrl+Alt+T).

If there are files there that you want, then you can copy them out (and if their ownership and permissions don't give you the necessary access, change them). You can do that as root from the Terminal with cp, chmod and chown (run as root with sudo), or with a root-owned Nautilus window as described above.*\

*******
ut, if you really want it, the command is chmod:

sudo chmod -R 777 /root
***********
http://askubuntu.com/questions/187997/i-cant-access-the-root-folder


2.follow sintructions
	1.Verify root access

	/*Drag & Drop sudo
	This is a trick from this thread on the Ubuntu Forums.

	Create a launcher with the following command:

	gksudo "gnome-open %u"
	When you drag and drop any file on this launcher (it's useful to put it on the desktop or on a panel), it will be opened as Root with its own associated application. This is helpful especially when you're editing config files owned by Root, since they will be opened as read only by default with gedit, etc
	https://help.ubuntu.com/community/RootSudo
	There are two different folders called the "root" folder: / (the root of the filesystem, which is really the only folder that should ever be called the "root folder"), and /root (the root user's home directory). During the normal course of operation (i.e., except while performing administrative tasks), users cannot create new files in / or /root.

	You should not change the ownership or permissions of either directory (changing them for / in particular could break things very badly, perhaps even beyond creating security problems depending on what assumptions your applications and services make about the ownership and permissions of /).

	If you have the gksu package installed, you can run gksudo nautilus to open a root-owned file browser window. If you do this, please be extra careful to only use it for tasks where you must be root, and to close it when you're done (so you don't later confuse it with an ordinary Nautilus window).

	If you don't have gksu installed and don't want to install it, sudo -i nautilus or sudo -H nautilus are reasonably safe. (In contrast, if you were to use plain sudo nautilus, you might have to fix some things in your home directory to get Nautilus to work properly again when you're not running it as root.)

	However, usually you don't need to do that either. You rarely have to manually edit the top-level contents of / or the contents of /root. I recommend providng more information--or asking a new question--to explain exactly what you're trying to accomplish. The particular task you need to do will determine how you should proceed.

	Finally, a note on lost+found. This stores files recovered in filesystem repair operations. Since such files could be from anywhere in the filesystem, it's necessary to require root permissions to access them (or any information on the system could potentially be accessed by someone who is not an administrator). If you think there may be files there that you wish to reclaim, you can check by running

	sudo ls /lost+found
	in a Terminal window (Ctrl+Alt+T).

	If there are files there that you want, then you can copy them out (and if their ownership and permissions don't give you the necessary access, change them). You can do that as root from the Terminal with cp, chmod and chown (run as root with sudo), or with a root-owned Nautilus window as described above.*\

	*******
	ut, if you really want it, the command is chmod:

	sudo chmod -R 777 /root
	***********
	http://askubuntu.com/questions/187997/i-cant-access-the-root-folder


	2.follow sintructions