Many python books, articles and learning guides refer to a python development GUI named IDLE. Why its recommended is that it comes with features that many other text editors - such as VI and gedit - have such as highlighting and closing (where it shows if you have not closed off a string for example) but IDLE also comes with the ability to show you where you may be making mistakes.
I have been working in VI, gedit, notepad++ and even the python shell of late. While all are usable - and yes I still revert to VI a lot - with all the references being made to IDLE I thought I would take a look.
I first tried it on Windows 7 - all good and an easy install as it is included in the installer exe.
I then tried it on Ubuntu - again, easy to install as you can just search for it in the software installer.
Alas, I then tried CentOS and came up short. In fairness I was using the cmdline more, as I often do in CentOS, but I could not find a package named IDLE.
For any others who need IDLE on CentOS and also didnt find many articles about it, its really very easy.
bash#: sudo yum install python-tools
its as easy as that!
Showing posts with label centos. Show all posts
Showing posts with label centos. Show all posts
Tuesday, December 17, 2013
Thursday, May 3, 2012
Linux AD Integration with Powerbroker
Linux and Window Authentication is a topic that comes up often and there are various ways of achieving this. We have been testing the Powerbroker Identity Services Open Source Edition (PBIS) and have found it very easy to install and use.
PBIS comes with a GUI and CLI installation interface. In order to test it, we decided that the CLI would be the better approach and give us a better insight into the tool. For the test we used Centos 6.0 and Fedora 16 as the Linux hosts.
The installation is simple and straight forward. Just type the following cmd and answer yes to the questions:
BASH# sh pbis-open-6.5.561.linux.x86_64.rpm.sh
The installation may require a reboot, but we found it was not always necessary. The default installation will create the directory /opt/pbis for the installation.
Once installed its time to add the linux host to the active directory domain and gain, using CLI, this is easily done. For this example we were joining the linux host to the domain example.com. We used the account administrator but this can be any account with privilege on the active directory domain.
BASH# /opt/pbis/bin/domainjoin-cli join EXAMPLE.COM administrator
That completed the installation and the linux host was then part of the domain. A straight forward and easy installation. To test we then logged in via SSH with the following:
BASH# ssh "example\gtlg"@192.168.1.2
by default pbis however does not use the BASH shell and creates the home diretory as follows:
/home/local/EXAMPLE/gtlg
This was not in-line with our normal standards and led us to dig a bit further into pbis to see how we could make it match our policies. Again pbis turned out to be very easy to use and very straight forward in editing the configuration. To change the default settings requires simple cmd's from pbis to edit the pbis "registry".
To change the default shell to the BASH shell was as follows:
in /opt/pbis/bin: ./config LoginShellTemplate /bin/bash
To change the default home directory is match this standard - /home/EXAMPLE/gtlg
in /opt/pbis/bin: ./config HomeDirTemplate %H/%D/%U
%H = /home
%D= Domain Name
%U = Username
At this point we had working logins via console or ssh, the use of the BASH shell by default and the directory structure that we wanted. Our last test was to see how to add users to groups and visudo. Again we are pleased to say that it was very simple.
in /opt/pbis/bin: use the command enum-groups and find a group in Active Directory that you want to use. In our case we used the group Domain Admins which was displayed by pbis as EXAMPLE\domain^admins. Adding this to our linux host was as simple as editing /etc/group and adding EXAMPLE\domain^admins into a group.
adding a group to sudo is just as easy and is as follows:
EXAMPLE\\domain^admins ALL=(ALL) ALL
Powerbroker Identity Services is great and works exactly as described.We have tested the file permissions and sudo rights successfully.
PBIS comes with a GUI and CLI installation interface. In order to test it, we decided that the CLI would be the better approach and give us a better insight into the tool. For the test we used Centos 6.0 and Fedora 16 as the Linux hosts.
The installation is simple and straight forward. Just type the following cmd and answer yes to the questions:
BASH# sh pbis-open-6.5.561.linux.x86_64.rpm.sh
The installation may require a reboot, but we found it was not always necessary. The default installation will create the directory /opt/pbis for the installation.
Once installed its time to add the linux host to the active directory domain and gain, using CLI, this is easily done. For this example we were joining the linux host to the domain example.com. We used the account administrator but this can be any account with privilege on the active directory domain.
BASH# /opt/pbis/bin/domainjoin-cli join EXAMPLE.COM administrator
That completed the installation and the linux host was then part of the domain. A straight forward and easy installation. To test we then logged in via SSH with the following:
BASH# ssh "example\gtlg"@192.168.1.2
by default pbis however does not use the BASH shell and creates the home diretory as follows:
/home/local/EXAMPLE/gtlg
This was not in-line with our normal standards and led us to dig a bit further into pbis to see how we could make it match our policies. Again pbis turned out to be very easy to use and very straight forward in editing the configuration. To change the default settings requires simple cmd's from pbis to edit the pbis "registry".
To change the default shell to the BASH shell was as follows:
in /opt/pbis/bin: ./config LoginShellTemplate /bin/bash
To change the default home directory is match this standard - /home/EXAMPLE/gtlg
in /opt/pbis/bin: ./config HomeDirTemplate %H/%D/%U
%H = /home
%D= Domain Name
%U = Username
At this point we had working logins via console or ssh, the use of the BASH shell by default and the directory structure that we wanted. Our last test was to see how to add users to groups and visudo. Again we are pleased to say that it was very simple.
in /opt/pbis/bin: use the command enum-groups and find a group in Active Directory that you want to use. In our case we used the group Domain Admins which was displayed by pbis as EXAMPLE\domain^admins. Adding this to our linux host was as simple as editing /etc/group and adding EXAMPLE\domain^admins into a group.
adding a group to sudo is just as easy and is as follows:
EXAMPLE\\domain^admins ALL=(ALL) ALL
Powerbroker Identity Services is great and works exactly as described.We have tested the file permissions and sudo rights successfully.
Wednesday, April 18, 2012
Subscribe to:
Posts (Atom)