Tag Info

New answers tagged

0

The problem was that the user launching mc didn't had /bin/bash as its init script but a scpecific script. To keep the init script that is used I had to add into it this little bit of code to enable mc to execute: mc=`ps $PPID | grep mc` if [ ! -z "$mc" -a "$mc"!=" " ] then if [ ! -z "admin" ] then bash $1 $2 $3 $4 $5 exit fi fi ...


0

Some possible reasons I know are connected with file permissions these are mostly too wide and Particularly I can recall two reasons exposing /home/user directory to more that the owner .ssh and/or authorized_keys file permissions (set them to 700/600 respectively if they are more than that) the exact reason of key is refused by starting an additional ...


0

some obvious check format of authorized_keys ssh-rsa AA...long_line_of_char comment putty gen sometime give another form. authorization: ~user/.ssh/authorized_keys is -rw-r--r-- ~user/.ssh/ is drwx------ ~user is not worl writable. key sould be deployed id ~root or in ~user depending on the user you connect to. some less obvious: root is not ...


0

I was encountering a similar issue, this evening. Similarly, I'm running Virtualbox on a Microsoft Windows Host OS. The Guest OS I'm using is Kubuntu, but of course the configuration between each of XMing, PuTTY, and Virtualbox would be similar. Though my reply is a little belated, maybe it'll be of help. This solution was made with a VirtualBox virtual ...


1

You may find this helpful: http://blog.jimueller.com/post/29709142253/use-putty-with-console2 If you call plink as an argument of ansicon.exe, this translates the escape sequences automatically. When I connect to my linux box, the output of ls is coloured automatically.


0

In RaspBMC I've added the line: export LC_TYPE=ru_UA.UTF-8 LC_ALL=ru_UA.UTF-8 LANG=ru_UA.UTF-8 at the end of /home/pi/.bashrc file. This works, if one wants to see Cyrillic file names (particularly in Midnight Commander) after logging as default 'pi' user via PuTTY from Windows. No suing, as it was described above, is needed anymore.


0

Try adding this (from /etc/screenrc) to your ~/.screenrc: # Change the xterm initialization string from is2=\E[!p\E[?3;4l\E[4l\E> # (This fixes the "Aborted because of window size change" konsole symptoms found # in bug #134198) termcapinfo xterm* 'is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;4;6l' http://superuser.com/a/217281/6593



Top 50 recent answers are included