I just found a nice, well commented screenrc on davekaufman.net.
I figured you might like it as much as I do.
Copy to /etc/screenrc :)

I just found a nice, well commented screenrc on davekaufman.net.
I figured you might like it as much as I do.
Copy to /etc/screenrc :)

This is actually just a clipboard for myself as I’m not very good at remembering bash commands I don’t use on a regular base.
recordmydesktop (http://recordmydesktop.sourceforge.net/) is a handy little tool to capture the desktop with audio. I just used it to create a small presentation of the wordpress engine.
If you wanna capture just a single window you need to know the window id:
xwininfo
will help you with that.
Now we can have fun:
recordmydesktop -windowid 0×1600040 –overwrite -o output.ogg
–overwrite because you’ll probably not have a perfect solution with the first try.
–nosound if you don’t wanna speak or have sound captioned.
Spare -windowid ### to capture the whole desktop.
By the way, if you wanna play it with, let’s say mplayer, you’ll need to compile it with theora support (+theora flag on –omg-optimized gentoo). VLC plays it out of the box.
So, I wanted to upload it on youtube. Of course they can’t handle that much of coolness so I had to convert it first:
mencoder output.ogg -o output.avi -ovc lavc -oac mp3lame
Again, change mp3lame to nosound if You want to.
Yay, and that’s it :)
Notes:
On my ~amd64 box I had to emerge it with ACCEPT_KEYWORDS=”~*” but it works really smooth. Sometimes it loses the audio source. Happened 1 of 3 times. And be careful with scrolling (on firefox for example).
Besides that it’s a really cool & handy tool :)
I came across some lines of code I started some time this year and decided to release a beta preview. My Movie DataBase is a database frontend which allows users to scan for moviefiles located in their filesystem and manage those files using a SQL based database system. In order to create an account, the user must have an existing unix account on the very same box. This programm is just a small preview and just features some very basic stuff, some of which is not implemented to its fullest extend. If anyone is willing to assist me writing the programm you are free to leave a comment, the programm is written in TCL and is only available on Linux, so if you want to contribute you need to know some basics.
I am also planning a TK GUI and since I have never ever coded TK I would be glad to find someone to help me with that. Anyways you can download the code and the required sql queries from the TeRaNetworks site using the provided links.
License: GPL
If you are using this software, please report any bug and feel free to make suggestions whereever you feel a need of improovement.
This should be a well known issue, just posting it here in case you didn’t know or forgot how to do it :>. This guide will describe how you can restrict ssh access to your server/desktop to the keys located in the user’s ‘authorized_keys’ file.
Lets assume we want to restrict access to ALL accounts except for user root, using a Desktop (DT) and a Server (SV), let’s also assume that DT is the computer which wants to access SV.
Run the following command as ROOT
root@DT:/ ssh-keygen
Save the key to the default file. After that cat the following file:
root@DT:/ cat /root/.ssh/id_rsa.pub
And copy the key to SV:
root@SV:/ nano /root/.ssh/authorized_keys
Save the file and restart your sshd on SV. Now check if your are able to access your server with your passphrase, do that by connecting to your shell via SSH as usual.
root@SV:/ /etc/init.d/sshd restart
root@DT:/ ssh host.of.SV
You should get a line like:
Enter passphrase for key ‘/root/.ssh/id_rsa’:
Which refers to the file on DT which contains the rsa-key created with ssh-keygen. If everything works fine you can edit your /etc/ssh/sshd_config file using your favourite editor and change ‘PasswordAuthentication’ to no, doing that will disallow users whose keys are not in the authorized_keys file of the specific user on the server to connect via ssh. This also means that you have to create a keyfile for every user on your SV in order to grant them access. One advantage of this method is that you can remove a user’s priviledge (eg if you have one or two users sharing the root account) by just removing his key from the file.
This oneliner was given to me by mrnice, it basically prints out the top 10 of the most used shell commands of the current user, just something to play with :>
history|awk ‘{print $2}’|awk ‘BEGIN {FS=”|”} {print $1}’|sort|uniq -c|sort -rn |head
