Archive:Getting Started/Run/Shell - Revision history

AnneW: Reverted edits by KennethMartinez (talk) to last revision by AnneW

2012-07-31T15:55:19Z

Reverted edits by KennethMartinez (talk) to last revision by AnneW

KennethMartinez: minor updates

2012-07-31T12:51:51Z

minor updates

AnneW at 17:57, 25 March 2012

2012-03-25T17:57:50Z

AnneW: moved Getting Started/Run/Shell to Archive:Getting Started/Run/Shell

2012-03-24T19:54:23Z

moved Getting Started/Run/Shell to Archive:Getting Started/Run/Shell

AnneW: Removed i18n bar (Unused)

2011-09-23T16:31:10Z

Removed i18n bar (Unused)

Neverendingo: Text replace - "" to ""

2011-06-29T20:57:07Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T20:47:31Z
Text replace - "<code>" to "<syntaxhighlight lang="text">"

				
				
				
				
			
			← Older revision
			Revision as of 20:47, 29 June 2011
			
Line 28:
Line 28:
    
  Although your X server should accept incoming TCP connections, this is often switched off as a distribution default (like with Kubuntu Feisty). When using <tt>kdm</tt> you must edit <tt>/etc/kde3/kdm/kdmrc</tt> as root and make sure it does not contain:   Although your X server should accept incoming TCP connections, this is often switched off as a distribution default (like with Kubuntu Feisty). When using <tt>kdm</tt> you must edit <tt>/etc/kde3/kdm/kdmrc</tt> as root and make sure it does not contain:
− <code>ServerArgsLocal=-nolisten tcp</code> + <syntaxhighlight lang="text">ServerArgsLocal=-nolisten tcp</code>
  Once you have fixed this, you will need to restart your X server. The <tt>xhost</tt> command should no longer return an "unable to open display" error.   Once you have fixed this, you will need to restart your X server. The <tt>xhost</tt> command should no longer return an "unable to open display" error.



Neverendingo: Text replace - "" to ""

2011-06-29T20:41:30Z
Text replace - "<code bash>" to "<syntaxhighlight lang="bash">"

				
				
				
				
			
			← Older revision
			Revision as of 20:41, 29 June 2011
			
Line 5:
Line 5:
  For this method, the tool '''sux''' (http://fgouget.free.fr/sux/sux-readme.shtml) is required. '''sux''' is available on most distributions. Otherwise you could rely on the ''normal shell without sux'' method below. '''sux''' allows you to change to another user with an implicit managing of the X forwarding details (authentication and DISPLAY exporting) in a clean and simple way.   For this method, the tool '''sux''' (http://fgouget.free.fr/sux/sux-readme.shtml) is required. '''sux''' is available on most distributions. Otherwise you could rely on the ''normal shell without sux'' method below. '''sux''' allows you to change to another user with an implicit managing of the X forwarding details (authentication and DISPLAY exporting) in a clean and simple way.
    
− To login, type <code bash>sux - kde-devel</code> + To login, type <syntaxhighlight lang="bash">sux - kde-devel</code>
    
− All environment variables and everything else should be set up correctly by your {{path|[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|.bashrc]]}}. To start an application, simply type it's name; for example <code bash>kwrite</code> + All environment variables and everything else should be set up correctly by your {{path|[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|.bashrc]]}}. To start an application, simply type it's name; for example <syntaxhighlight lang="bash">kwrite</code>
− {{Note|If you get errors about missing mimetypes or such, try running the following:<code bash>unset XDG_DATA_DIRS ; kbuildsycoca4</code> + {{Note|If you get errors about missing mimetypes or such, try running the following:<syntaxhighlight lang="bash">unset XDG_DATA_DIRS ; kbuildsycoca4</code>
  }}   }}
    
  == Using the normal shell without sux ==   == Using the normal shell without sux ==
  The simplest method to launch KDE 4 applications is using <tt>su</tt> to login as the <tt>kde-devel</tt> user and then simply start any KDE 4 application from command line. To login, type   The simplest method to launch KDE 4 applications is using <tt>su</tt> to login as the <tt>kde-devel</tt> user and then simply start any KDE 4 application from command line. To login, type
− <code bash>su - kde-devel</code> + <syntaxhighlight lang="bash">su - kde-devel</code>
  and then, after entering your password   and then, after entering your password
− <code bash>export DISPLAY=:0</code> + <syntaxhighlight lang="bash">export DISPLAY=:0</code>
  {{Note|Exporting the <tt>DISPLAY</tt> variable is necessary so that the KDE 4 applications appear on your normal KDE 3 desktop.}}   {{Note|Exporting the <tt>DISPLAY</tt> variable is necessary so that the KDE 4 applications appear on your normal KDE 3 desktop.}}
− All environment variables and everything else should be set up correctly by your {{path|[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|.bashrc]]}}. To start an application, simply type it's name; for example <code bash>kwrite</code> + All environment variables and everything else should be set up correctly by your {{path|[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|.bashrc]]}}. To start an application, simply type it's name; for example <syntaxhighlight lang="bash">kwrite</code>
  {{Note|   {{Note|
  If you get errors about missing mimetypes or such, try the following:   If you get errors about missing mimetypes or such, try the following:
− * run <code bash>unset XDG_DATA_DIRS ; kbuildsycoca4</code> + * run <syntaxhighlight lang="bash">unset XDG_DATA_DIRS ; kbuildsycoca4</code>
  }}   }}
  {{Note|   {{Note|
  If you get an error about not being able to connect to an X server, be sure to issue   If you get an error about not being able to connect to an X server, be sure to issue
− <code bash>sudo xhost +local:kde-devel</code> + <syntaxhighlight lang="bash">sudo xhost +local:kde-devel</code>
  as your regular KDE 3 user to ensure that the application can connect to your current X session.   as your regular KDE 3 user to ensure that the application can connect to your current X session.
    
Line 32:
Line 32:
    
  For convenience, you should put this in the Autostart of your regular user. To do this, create a new file in the <tt>$HOME/.kde/Autostart</tt> directory of your regular user with the following content:   For convenience, you should put this in the Autostart of your regular user. To do this, create a new file in the <tt>$HOME/.kde/Autostart</tt> directory of your regular user with the following content:
− <code bash> + <syntaxhighlight lang="bash">
  #! /bin/sh   #! /bin/sh
  xhost +local:kde-devel   xhost +local:kde-devel
Line 44:
Line 44:
    
  The simplest way to run a KDE 4 application with SSH in your current desktop environment is to get an X-aware shell prompt as the <tt>kde-devel</tt> user like this:   The simplest way to run a KDE 4 application with SSH in your current desktop environment is to get an X-aware shell prompt as the <tt>kde-devel</tt> user like this:
− <code bash>ssh -X kde-devel@localhost</code> + <syntaxhighlight lang="bash">ssh -X kde-devel@localhost</code>
  Now you can launch KDE apps as usual, for example:   Now you can launch KDE apps as usual, for example:
− <code bash>kwrite</code> + <syntaxhighlight lang="bash">kwrite</code>
  The two lines can be conveniently combined:   The two lines can be conveniently combined:
− <code bash>ssh -X kde-devel@localhost kwrite</code> + <syntaxhighlight lang="bash">ssh -X kde-devel@localhost kwrite</code>
    
  {{Note|   {{Note|
Line 57:
Line 57:
  === Passwordless login ===   === Passwordless login ===
  Before anything serious can be done using this method, a passwordless login needs to be set up. To start, run the following command as the regular desktop user:   Before anything serious can be done using this method, a passwordless login needs to be set up. To start, run the following command as the regular desktop user:
− <code bash>ssh-keygen -t rsa</code> + <syntaxhighlight lang="bash">ssh-keygen -t rsa</code>
  Hit enter three times to accept the path of {{path|~/.ssh/id_rsa}} and an empty passphrase. Now, copy the single line in {{path|~/.ssh/id_rsa.pub}} that's printed after running this command:   Hit enter three times to accept the path of {{path|~/.ssh/id_rsa}} and an empty passphrase. Now, copy the single line in {{path|~/.ssh/id_rsa.pub}} that's printed after running this command:
− <code bash>cat ~/.ssh/id_rsa.pub</code> + <syntaxhighlight lang="bash">cat ~/.ssh/id_rsa.pub</code>
  After that line is copied, <tt>ssh</tt> back into the <tt>kde-devel</tt> user and put the copied line in the file {{path|$HOME/.ssh/authorized_keys}}:   After that line is copied, <tt>ssh</tt> back into the <tt>kde-devel</tt> user and put the copied line in the file {{path|$HOME/.ssh/authorized_keys}}:
− <code bash>ssh -X kde-devel@localhost $HOME/kde/bin/kwrite \ + <syntaxhighlight lang="bash">ssh -X kde-devel@localhost $HOME/kde/bin/kwrite \
     $HOME/.ssh/authorized_keys</code>      $HOME/.ssh/authorized_keys</code>
  Paste in the line, save the file, and quit KWrite.   Paste in the line, save the file, and quit KWrite.
    
  Next make sure {{path|$HOME/.ssh/authorized_keys}} has the correct permissions:   Next make sure {{path|$HOME/.ssh/authorized_keys}} has the correct permissions:
− <code bash>ssh kde-devel@localhost chmod og-xrw ~kde-devel/.ssh/authorized_keys</code> + <syntaxhighlight lang="bash">ssh kde-devel@localhost chmod og-xrw ~kde-devel/.ssh/authorized_keys</code>
  Now try running KWrite again with the same SSH command; you shouldn't have to enter a password anymore:   Now try running KWrite again with the same SSH command; you shouldn't have to enter a password anymore:
− <code bash>ssh -X kde-devel@localhost $HOME/kde/bin/kwrite</code> + <syntaxhighlight lang="bash">ssh -X kde-devel@localhost $HOME/kde/bin/kwrite</code>
    
  {{warning|Using a passwordless SSH login has certain '''security risks''', so make sure you protect your <tt>~/.ssh/id_rsa</tt> file by restricting access to it with     {{warning|Using a passwordless SSH login has certain '''security risks''', so make sure you protect your <tt>~/.ssh/id_rsa</tt> file by restricting access to it with  
− <code bash>chmod og-xrw ~/.ssh/id_rsa</code>(although the file should have these permissions when it is created)}} + <syntaxhighlight lang="bash">chmod og-xrw ~/.ssh/id_rsa</code>(although the file should have these permissions when it is created)}}
    
  === The SSH desktop file ===   === The SSH desktop file ===
Line 78:
Line 78:
    
  You can start with an existing .desktop file as a template (like one from your desktop) or you can make one from scratch. The main idea is to prefix the command being run with this string:   You can start with an existing .desktop file as a template (like one from your desktop) or you can make one from scratch. The main idea is to prefix the command being run with this string:
− <code bash> + <syntaxhighlight lang="bash">
  ssh -X kde-devel@localhost $HOME/kde/bin/   ssh -X kde-devel@localhost $HOME/kde/bin/
  </code>   </code>



Neverendingo: Text replace - "" to ""

2011-06-29T20:37:48Z
Text replace - "<code ini>" to "<syntaxhighlight lang="ini">"

				
				
				
				
			
			← Older revision
			Revision as of 20:37, 29 June 2011
			
Line 84:
Line 84:
  A simple .desktop file that runs KWrite would have the following contents:   A simple .desktop file that runs KWrite would have the following contents:
    
− <code ini> + <syntaxhighlight lang="ini">
  [Desktop Entry]   [Desktop Entry]
  Categories=Qt;KDE;TextEditor;   Categories=Qt;KDE;TextEditor;



Odysseus: Created page with '{{Template:I18n/Language Navigation Bar|Getting_Started/Run/Shell}}  == Using the normal shell with sux ==  For this method, the tool '''sux''' (http://fgouget.free.fr/sux/sux-re...'
2011-03-03T14:47:10Z
Created page with '{{Template:I18n/Language Navigation Bar|Getting_Started/Run/Shell}}  == Using the normal shell with sux ==  For this method, the tool '''sux''' (http://fgouget.free.fr/sux/sux-re...'
New page
{{Template:I18n/Language Navigation Bar|Getting_Started/Run/Shell}}



== Using the normal shell with sux ==



For this method, the tool '''sux''' (http://fgouget.free.fr/sux/sux-readme.shtml) is required. '''sux''' is available on most distributions. Otherwise you could rely on the ''normal shell without sux'' method below. '''sux''' allows you to change to another user with an implicit managing of the X forwarding details (authentication and DISPLAY exporting) in a clean and simple way.



To login, type <code bash>sux - kde-devel</code>



All environment variables and everything else should be set up correctly by your {{path|[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|.bashrc]]}}. To start an application, simply type it's name; for example <code bash>kwrite</code>

{{Note|If you get errors about missing mimetypes or such, try running the following:<code bash>unset XDG_DATA_DIRS ; kbuildsycoca4</code>

}}



== Using the normal shell without sux ==

The simplest method to launch KDE 4 applications is using <tt>su</tt> to login as the <tt>kde-devel</tt> user and then simply start any KDE 4 application from command line. To login, type

<code bash>su - kde-devel</code>

and then, after entering your password

<code bash>export DISPLAY=:0</code>

{{Note|Exporting the <tt>DISPLAY</tt> variable is necessary so that the KDE 4 applications appear on your normal KDE 3 desktop.}}

All environment variables and everything else should be set up correctly by your {{path|[[Getting_Started/Increased_Productivity_in_KDE4_with_Scripts/.bashrc|.bashrc]]}}. To start an application, simply type it's name; for example <code bash>kwrite</code>

{{Note|

If you get errors about missing mimetypes or such, try the following:

* run <code bash>unset XDG_DATA_DIRS ; kbuildsycoca4</code>

}}

{{Note|

If you get an error about not being able to connect to an X server, be sure to issue

<code bash>sudo xhost +local:kde-devel</code>

as your regular KDE 3 user to ensure that the application can connect to your current X session.



Although your X server should accept incoming TCP connections, this is often switched off as a distribution default (like with Kubuntu Feisty). When using <tt>kdm</tt> you must edit <tt>/etc/kde3/kdm/kdmrc</tt> as root and make sure it does not contain:

<code>ServerArgsLocal=-nolisten tcp</code>

Once you have fixed this, you will need to restart your X server. The <tt>xhost</tt> command should no longer return an "unable to open display" error.



For convenience, you should put this in the Autostart of your regular user. To do this, create a new file in the <tt>$HOME/.kde/Autostart</tt> directory of your regular user with the following content:

<code bash>

#! /bin/sh

xhost +local:kde-devel

</code>

Make sure that the new file is executable by using <tt>chmod +x</tt> on it.



If you'd like to find out more about the '''security issues''' involved with using <tt>xhost</tt>, see [http://bau2.uibk.ac.at/matic/xsecur.htm this article]

}}



== Using SSH ==



The simplest way to run a KDE 4 application with SSH in your current desktop environment is to get an X-aware shell prompt as the <tt>kde-devel</tt> user like this:

<code bash>ssh -X kde-devel@localhost</code>

Now you can launch KDE apps as usual, for example:

<code bash>kwrite</code>

The two lines can be conveniently combined:

<code bash>ssh -X kde-devel@localhost kwrite</code>



{{Note|

If this gives you any errors, try the troubleshooting tips from the section above.

If you receive something like "kwrite: cannot connect to X server", open /etc/ssh/sshd_config and enable the "X11Forwarding" key.  Restart sshd and it should work fine.

}}



=== Passwordless login ===

Before anything serious can be done using this method, a passwordless login needs to be set up. To start, run the following command as the regular desktop user:

<code bash>ssh-keygen -t rsa</code>

Hit enter three times to accept the path of {{path|~/.ssh/id_rsa}} and an empty passphrase. Now, copy the single line in {{path|~/.ssh/id_rsa.pub}} that's printed after running this command:

<code bash>cat ~/.ssh/id_rsa.pub</code>

After that line is copied, <tt>ssh</tt> back into the <tt>kde-devel</tt> user and put the copied line in the file {{path|$HOME/.ssh/authorized_keys}}:

<code bash>ssh -X kde-devel@localhost $HOME/kde/bin/kwrite \

  $HOME/.ssh/authorized_keys</code>

Paste in the line, save the file, and quit KWrite.



Next make sure {{path|$HOME/.ssh/authorized_keys}} has the correct permissions:

<code bash>ssh kde-devel@localhost chmod og-xrw ~kde-devel/.ssh/authorized_keys</code>

Now try running KWrite again with the same SSH command; you shouldn't have to enter a password anymore:

<code bash>ssh -X kde-devel@localhost $HOME/kde/bin/kwrite</code>



{{warning|Using a passwordless SSH login has certain '''security risks''', so make sure you protect your <tt>~/.ssh/id_rsa</tt> file by restricting access to it with 

<code bash>chmod og-xrw ~/.ssh/id_rsa</code>(although the file should have these permissions when it is created)}}



=== The SSH desktop file ===

If you want to be able to launch apps more easily than running them with an SSH command from the command line, one way is to create <tt>.desktop</tt> files that <tt>ssh</tt> into the other account. 

{{Note|This will only be useful if your desktop environment supports .desktop files, but at least KDE and GNOME do.}}



You can start with an existing .desktop file as a template (like one from your desktop) or you can make one from scratch. The main idea is to prefix the command being run with this string:

<code bash>

ssh -X kde-devel@localhost $HOME/kde/bin/

</code>



A simple .desktop file that runs KWrite would have the following contents:



<code ini>

[Desktop Entry]

Categories=Qt;KDE;TextEditor;

Comment=

DocPath=kwrite/index.html

Encoding=UTF-8

Exec=ssh -X kde-devel@localhost /home/kde-devel/kde/bin/kwrite %U

GenericName=Text Editor

Icon=kwrite

InitialPreference=8

MimeType=text/plain

Name=KWrite (kde-devel)

Path=

StartupNotify=false

Terminal=false

TerminalOptions=

Type=Application

X-DBUS-StartupType=Multi

X-DCOP-ServiceType=non

X-KDE-StartupNotify=true

X-KDE-SubstituteUID=false

X-KDE-Username=

</code>



{{tip|Apps launched using SSH like this don't trigger the correct launch responses, so you probably want to disable "launch feedback" for your .desktop files}}



{{note|In order to create a .desktop file for a KDE 4 app by using this pattern, the app's package will have to have been installed into <tt>~/kde/bin</tt> using the <tt>cmakekde</tt> command}}



[[Category:KDE4]]

← Older revision		Revision as of 17:57, 25 March 2012
Line 1:		Line 1:
		+	__NOINDEX__
	== Using the normal shell with sux ==		== Using the normal shell with sux ==

@@ Line 109: / Line 109: @@
 {{tip|Apps launched using SSH like this don't trigger the correct launch responses, so you probably want to disable "launch feedback" for your .desktop files}}
-{{note|In order to create a .desktop file for a KDE 4 app by using this pattern, the app's package will have  ... \n
+{{note|In order to create a .desktop file for a KDE 4 app by using this pattern, the app's package will have to have been installed into <tt>~/kde/bin</tt> using the <tt>cmakekde</tt> command}}
-== Meet The New Boss: You ==
+[[Category:KDE4]]
-−
-What do coffee growers in Ethiopia, hardware store owners in America, and Basque entrepreneurs have in common? For one thing, many of them belong to cooperatives. By pooling their money and resources, and voting democratically on how those resources will be used, they can compete in business and reinvest the benefits in their communities.
-−
- [[http://goodvillenews.com/Meet-The-New-Boss-You-wF4aeF.html Meet The New Boss: You]]
-−
-[[http://goodvillenews.com/wk.html GoodvilleNews.com - good, positive news, inspirational stories, articles]]
-−
-== Why You Should Always Trust Yourself ==
-−
-Trust yourself. You know more than you think you do. Benjamin SpockAs time passes by and the more work you will do on discovering and improving yourself, the more you will realize that the ancient Latin quotation: Ne te quaesiveris extra - Do not look outside of yourself for the truth, is true.
-−
- [[http://goodvillenews.com/Why-You-Should-Always-Trust-Yourself-TR2gYW.html Why You Should Always Trust Yourself]]
-−
-[[http://goodvillenews.com/wk.html GoodvilleNews.com - good, positive news, inspirational stories, articles]]
-−
-== Student Goes From Homeless to Harvard ==
-−
-Despite being abandoned to homelessness by her parents, Dawn Loggins worked as a high school custodian by day and studied hard by night to become the first person from her school to ever be admitted to Harvard.
-−
- [[http://goodvillenews.com/Student-Goes-From-Homeless-to-Harvard-QX9Vg4.html Student Goes From Homeless to Harvard]]
-−
-[[http://goodvillenews.com/wk.html GoodvilleNews.com - good, positive news, inspirational stories, articles]]
-−
-== What Is Your Legacy? Living A Meaningful life ==
-−
-I want the world to be better because I was here. I want my life, I want my work, my family, I want it to mean something and if you are not making someone elses life better then you are wasting your time Will Smith
-−
- [[http://goodvillenews.com/What-Is-Your-Legacy-Living-A-Meaningful-life-oBtnrB.html What Is Your Legacy? Living A Meaningful life]]
-−
-[[http://goodvillenews.com/wk.html GoodvilleNews.com - good, positive news, inspirational stories, articles]]
-−
-== Man Builds Fairy Tale Home for $4700 ==
-−
-Simon Dale is a family man in Wales, the western part of Great Britain. His interest in self-sustainability and an ecological awareness led him to dig out and build his own homeone of the loveliest, warmest, most inviting dwellings you could ever imagine. And it cost him only 3,000, about $4,700 American dollars!
-−
- [[http://goodvillenews.com/Man-Builds-Fairy-Tale-Home-for-4700-CHIO9L.html Man Builds Fairy Tale Home for $4700]]
-−
-[[http://goodvillenews.com/wk.html GoodvilleNews.com - good, positive news, inspirational stories, articles]]

← Older revision		Revision as of 16:31, 23 September 2011
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Getting_Started/Run/Shell}}~~
−
	== Using the normal shell with sux ==		== Using the normal shell with sux ==