Run the following command (Start->Run or ctrl + r), assuming your Dropbox is installed at your profile directory (%userprofile%), if not alter it properly:
regedit /e "%userprofile%\Dropbox\putty.reg" HKEY_CURRENT_USER\Software\SimonTatham
With Dropbox installed on the user’s profile directory you just run this command in the most up to date machine and later on you get your entire PuTTY setup when logged in your other hosts.
Red Hat generally provides a stable Linux distribution in its currently supported releases. And one might want to only use the packages that came along with the distribution media i.e. a cdrom or an .iso file containing that cd’s image.
To be able to use a CD’s or .iso file’s packages in RHEL (Red Hat Enterprise Linux) 5.7, create this file in /etc/yum.repos.d/:
[user@localhost yum.repos.d]$ cat redhat_cdrom.repo [redhat_cdrom] name=Red Hat Enterprise Linux $releasever - CD-ROM baseurl=file:///media/rhel/Server enabled=1 gpgcheck=1 gpgkey=file:///media/rhel/RPM-GPG-KEY-redhat-release
This is assuming you had mounted the cdrom or the distribution’s .iso file to the /media/rhel directory.
Then do:
# yum update
And then pick up the desired software and install it:
# yum install <packages>
That is all.
FreeBSD has its Package and Ports software scheme. Both have dependency check and handle the automatic installation(s) when there is (are) any.
First of all, if you want to have a program but you do not have a clue of what is its name, try searching for it in popular FOSS sites such as Freecode (formerly known as freshmeat.net) etc. If you know the name and want to perform a search for it on the system you can do:
# whereis lsof
lsof: /usr/ports/sysutils/lsof
or:
# echo /usr/ports/*/*lsof*
/usr/ports/sysutils/lsof
The latter will also include matches found in /usr/ports/distfiles/.
Generally, the ports directory structure is inside the /usr/ports directory.
You can also use the handy Ports Collection’s built-in search mechanism, by cd‘ing to the /usr/ports directory and executing:
# make search name=program(port)-name
The system search above is for the FreeBSD Ports facility. We will come back to it shortly.
Packages are convenient as they are pre-compiled versions of applications. As such, they have the primary advantage of not imposing the awareness and compilation setup work (as when any tweak is desired), but you have to accept a software that was compiled with a very simple configuration as it must be able to execute smoothly in many platforms. Another advantage (if you considered the latter as such ;)) is that the compressed archive is a lot smaller than the source code archive. You handle packages with simple commands such as pkg_add, pkg_info, pkg_version, pkg_delete etc.
Ports, on the other hand, are a set of files (Makefile, patch files etc.) that make the source code for applications to be ported to (able to compile in and, hence, function correctly in) the FreeBSD realm.
To have compiled software is more secure and you have the control of the application aspects, including the ability to turn features on or off during compilation. The port’s corresponding source code archive (known as the distfile) is larger than a correspondent (pre-compiled) package for the software, though. Nevertheless the many benefits it brings, like security, source code availability, and compiling for the architecture make it the best choice for a handful of people e.g. developers or folks that just appreciate one of the many advantages listed.
So, we will cover a bit of Ports usage. For more information on Package usage in FreeBSD go to its official handbook documentation.
In order to be able to use the Ports facility you must first get the Ports Collection:
# csup -L 2 -h cvsup.FreeBSD.org /usr/share/examples/cvsup/ports-supfile
Instead of the value for the -h option above, choose a mirror near you.
The Ports Collection is comprised of a set of Makefiles, patches and description files, divided up into port skeletons (one skeleton is a port) each of which is a minimal set of files containing instructions on how to build (compile) the source code, but does not include the actual source code.
With an Internet connection already setup, go to the port directory e.g. for lsof:
# cd /usr/ports/sysutils/lsof
and (also as root) execute make, make install, and then, as advised by the handbook, make clean (temporary files used during compilation). To run all of them with only one command you can just run make install clean – this will do all the work for you: download the distfile, uncompress, build and install it and then clean its temporary compilation files.
The following passage from the handbook (section on ports usage) is very important for those that do not have an Internet connection up all the time:
For users which cannot be connected all the time, the make fetch option is provided. Just run this command at the top level directory (/usr/ports) and the required files will be downloaded for you. This command will also work in the lower level categories, for example: /usr/ports/net. Note that if a port depends on libraries or other ports this will not fetch the distfiles of those ports too. Replace fetch with fetch-recursive if you want to fetch all the dependencies of a port too.
Note: You can build all the ports in a category or as a whole by running make in the top level directory, just like the aforementioned make fetch method. This is dangerous, however, as some ports cannot co-exist. In other cases, some ports can install two different files with the same filename.
For more activities on Ports, like changing the Default Ports Directories, Reconfiguring, Upgrading or Removing Installed Ports, consult the handbook section on ports usage.
The Ports Collection will use disk space over time. Always remember to make clean while inside the relevant directory, or simply portsclean -C (in any directory). To remove all the distfiles not referenced by any port, execute portsclean -D, or portsclean -DD to delete the ones not referenced by any port currently installed on your system. portsclean is a part of the portsupgrade suite (also explained by the handbook section on ports usage which makes numerous more tips not present in this article available!).
Welcome to FreeBSD!
The pythonbrew utility is a complete environment manager for Python. It allows one to list and switch permanently between python versions or just as a temporary in the current shell session.
Usage syntax is very simple:
pythonbrew command [options]
And here are some command examples from its README document (that file on github also includes the installation procedure), showcasing its set of features:
# Install some pythons: pythonbrew install 2.7.2 pythonbrew install --verbose 2.7.2 pythonbrew install --force 2.7.2 pythonbrew install --no-test 2.7.2 pythonbrew install --configure="CC=gcc_4.1" 2.7.2 pythonbrew install --no-setuptools 2.7.2 pythonbrew install http://www.python.org/ftp/python/2.7/Python-2.7.2.tgz pythonbrew install /path/to/Python-2.7.2.tgz pythonbrew install /path/to/Python-2.7.2 pythonbrew install 2.7.2 3.2 # Permanently use the specified python: pythonbrew switch 2.7.2 pythonbrew switch 3.2 # Use the specified python in current shell: pythonbrew use 2.7.2 # Runs a named python file against specified and/or all pythons: pythonbrew py test.py pythonbrew py -v test.py # Show verbose output pythonbrew py -p 2.7.2 -p 3.2 test.py # Use the specified pythons # List the installed pythons: pythonbrew list # List the available installation pythons: pythonbrew list -k # Uninstall the specified python: pythonbrew uninstall 2.7.2 pythonbrew uninstall 2.7.2 3.2 # Remove stale source folders and archives: pythonbrew cleanup # Upgrades pythonbrew to the latest version: pythonbrew update pythonbrew update --master pythonbrew update --develop # Disable pythonbrew: pythonbrew off # Create/Remove a symbolic link to python (in a directory on your $PATH): pythonbrew symlink # Create a symbolic link, like "py2.7.2", for each installed version pythonbrew symlink -p 2.7.2 pythonbrew symlink pip # Create a symbolic link to the specified script in bin directory pythonbrew symlink -r # Remove a symbolic link pythonbrew symlink -v foo # Create a symbolic link to the specified virtual environment python in bin directory # Runs the buildout with specified or current using python: pythonbrew buildout pythonbrew buildout -p 2.6.6 # Create isolated python environments (uses virtualenv): pythonbrew venv init pythonbrew venv create proj pythonbrew venv list pythonbrew venv use proj pythonbrew venv delete proj # Show version: pythonbrew version
Xfce is one of the greatest desktop environments ever. It is beautiful, lean, and thus it is also very fast.
One of its great customizable aspects is the assignment of commands for Keyboard Shortcuts (Xfce Menu > Settings > Keyboard > Application Shortcuts).
I immediately found out two nice applications for it: screenshot and sound attenuation. This post gives you the hint on the sound attenuation command when using ALSA (Advanced Linux Sound Architecture).
I usually cycle between 40% of the card’s volume when attenuated and 80% when playing audio normally. So I took the keys F9 and F10, respectively, and assigned them the following ALSA commands, also respectively:
amixer set Master 40%
and
amixer set Master 80%
The “Master” simple mixer control name I knew via listing the simple mixer controls available via the
amixer scontrols
command. Do the same and substitute “Master” in the commands above with whatever value you see in place of the blue value below (“Master”, in this example, matching the “Master” in the above commands):
Simple mixer control 'Master',0
Simple mixer control 'PCM',0
Simple mixer control 'IEC958',0
Simple mixer control 'IEC958 Default PCM',0
Simple mixer control 'Digital',0
Simple mixer control 'Ext Mic',0
Simple mixer control 'ExtMic',0
Simple mixer control 'Int Mic',0
Simple mixer control 'IntMic',0
Enjoy! :)
I often use the Xfce 4 timer (on Debian it is installed via the xfce4-timer-plugin package and you plug it in a panel by adding it to the panel, via the panel’s context menu) or a similar application in conjunction with some dialog window generator (and trigger) for immediate alerts during daily activities.
We will create 2 scripts that make it easier to assemble a command to display such dialogs. In this case we will tackle on creating simple, informational dialogs only, with whiptail (text) and zenity (graphical). Note that their Debian packages have the same name as the respective commands.
We need a terminal emulator, in this case the Xfce 4 terminal emulator which is available as the xfce4-terminal package on Debian.
Create (as root) with mode 755 the file /usr/bin/zen with the following contents:
#!/usr/bin/env bash xfce4-terminal -x bash -ic ' clear echo "MESSAGE DIALOG (TEXT: '"${1}"') OPENED!" zenity --info --text "'"${1}"'"'
For whiptail (text mode dialog), create (as root) with mode 755 the file /usr/bin/whip with the following contents:
#!/usr/bin/env bash xfce4-terminal -x bash -ic ' clear whiptail --nocancel --title message --msgbox "'"${1}"'" 12 64'
Now, to call the text-mode dialog (whiptail), do:
whip 'This is my new message!'or call the graphical dialog (zenity) like this:
zen 'This is my new message!'Here is how the zenity version will be displayed:
And here is how the whip version will be displayed:
You can also elaborate on your whiptail and zenity codes as they are very complete, and so you can construct timer or other types of commands and scripts that do much more than these.
Important note: the post title part “in Xfce 4″ is merely related to the example, nothing more. It is not required that you assemble your code for Xfce nor its terminal emulator xfce4-terminal. You can do all of this while on your preferred window manager and for/with your favorite terminal emulator program.
I think these basic examples are very handy already. I am sure you will, too!
As root, execute one of these depending on the desired action:
echo -n mem > /sys/power/state # suspend to ram echo -n disk > /sys/power/state # suspend to disk
Credits / Source: TipsForLinux’s post.
This post is intended for you fellow users of Xfce, a window manager and suite of applications.
The Thunar file browser is a very interesting of these applications:
The one awesome feature we discuss here is about incrementing your configuration with custom actions for files and directories that are made accessible via their context menu.
Now for the 3rd field, “Command” here is the very nice and handy part:
Insert a command of yours to do something. In my case, I want to rename files so that they do not have special characters. I will do this by invoking the xfce4-terminal (obviously, also from the Xfce suite of applications) which in turn invokes bash with its -c option (which receives an argument string comprised of commands to be evaluated i.e. executed).
Here ‘s the code:
xfce4-terminal -x bash -c '/path_to_script/renameok.sh %f'
The script renameok.sh iterates through directories renaming their files stripping special characters. Soon a post will be included containing its source code and explanation.
If your script (generally referred to as script.sh instead of the specific renameok.sh) depends on stuff setup in .bashrc (the shell resource file) then just call bash with -i (bash -ic “command(s)”) which sets the interactive mode on and calls the resource file before executing the -c option commands. Also realize that when in an interactive session, if script.sh is in a PATH setup by .bashrc you are safe to remove the /path_to_script/ part of script.sh ‘s call as it will be thus found. And last, as my .bashrc can have some echo commands in it, I will deliberately add a clear command before the script call so that the resulting code will look like:
xfce4-terminal -x bash -ic 'clear; renameok.sh %f'
Now, in the Appearance Conditions tab uncheck every options but Directories as in this example we use the directory in which the context menu was invoked as the script ‘s argument (as it wants a directory path). This indeed causes the action to be available only for directories’ context menus in Thunar. The main purpose in this tab is for you to choose which type(s) of files (directories are a type of file) you want the action to be executable.
In the custom action entry edition dialog, still, notice the bottom of the window, which explains the meanings of the expansions including the %f shown in the examples herein. One interesting and awesome thing is that Thunar is also smart enough to realize that the actions must not be made available if more than one file (or directory, as in these examples) are selected in case you are using %f. Conversely, the action is selectable both for just one file or for multiple files when using %F instead.
To know more check the official wiki entry.
Enjoy! ;)