Differences between version 8 and predecessor to the previous major change of NewUserTips.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 8 | Last edited on Monday, June 27, 2005 4:17:27 pm | by AristotlePagaltzis | Revert |
Older page: | version 3 | Last edited on Sunday, July 27, 2003 1:26:23 pm | by AristotlePagaltzis | Revert |
@@ -1,39 +1,49 @@
-* The Linux equivalent of Windows
' __
ipconfig__
command is ifconfig(8).
+* The [
Linux]
equivalent of MicrosoftWindows
' <tt>
ipconfig</tt>
command is ifconfig(8).
-* Your initial windowmanager
settings are (generally) stored in the __
.xinitrc__
file.
+* Your initial WindowManager
settings are (generally) stored in the <tt>
.xinitrc</tt> or <tt>.xsession</tt>
file in your home
.
-* Global system configuration files are in the __
/etc__
directory.
+* Global system configuration files are in the <tt>
/etc</tt>
directory.
-* Use __
rpm -Uvh filename__ to install a .rpm file
. See rpm(8)
+* Install [RPM] [Package]s using <tt>
rpm -Uvh filename</tt>
. See rpm(8). However, investigate a better PackageManagementTool urgently. On FedoraCore, that would be AptForRpm or [Yum].
-* Use __
tar -
xzvf filename__
to decompress a .tar.gz or .tgz file. See tar(1)
+* Use <tt>
tar xzvf filename</tt>
to decompress a <tt>
.tar.gz</tt>
or <tt>
.tgz</tt>
file, otherwise known as a TarBall
. See tar(1)
-* Don't get involved in emacs(1) vs. vi(1) arguments. Use nano(1), pico(1), joe(1), or jed(1) for your initial editing needs. Once you have gotten a little more comfortable with the system, however, be sure to revisit emacs(1) and vi(1) as they offer __
tons__
of power you will never get with the simple minded editors. For the latter, vim(1)
is the proposed
clone, which comes with a __
vimtutor__
program that should get your over the initial hurdles quickly. ''Does any equivalent for emacs(1) exist?''
+* Don't get involved in emacs(1) vs. vi(1) arguments. Use nano(1), pico(1), joe(1), or jed(1) for your initial editing needs. Once you have gotten a little more comfortable with the system, however, be sure to revisit emacs(1) and vi(1) as they offer ''
tons''
of power you will never get with the simple minded editors. For the latter, [Vim]
is the suggested
clone, which comes with a <tt>
vimtutor</tt>
program that should get your over the initial hurdles quickly. ''Does any equivalent for emacs(1) exist?''
-* The cp(1) command copies files. The __
-R__
switch is for copying directories.
+* The cp(1) command copies files. The <tt>
-a</tt>
switch is for copying directories.
* Before you ask for help online, be sure to read the documentation first. It is sometimes difficult to understand so don't feel bad if you don't get it, just make the attempt. It will either make any explanation you get from someone else clearer, or the explanation will help you understand the documentation. Next time you look at it, the documentation will be less puzzling. If you repeat this a couple times, then you'll soon be cruising along with the docs just fine.
-* If your desktop locks up, Ctrl-Alt-Backspace will kill the GUI
and drop you to the command line
(or your display manager) without having to reboot the system.
+* If your desktop locks up, Ctrl-Alt-Backspace will kill the graphical environment (the [XServer], in technical terms)
and drop you to the [Shell]
(or your display manager) without having to reboot the system.
* You don't have to worry about defragmenting your disks.
* You don't have to worry about defragmenting your memory.
-* You don't have to worry about mail worms
.
+* You don't have to worry about mail [Worm]s
.
-* Linux will crash on you at some point. It happens, no matter what anybody says. However, it won't happen nearly as much as it does on Windows
.
+* [
Linux]
will crash on you at some point. It happens, no matter what anybody says. However, it won't happen nearly as much as it does on MicrosoftWindows
.
-* You don't have to shut down or restart every day. It's ok to leave a Linux system running for a week or more (some users have their system running for months at a time). You should still conserve electricity, tho.
+* You don't have to shut down or restart every day. It's ok to leave a [
Linux]
system running for a week or more (some users have their system running for months at a time). You should still conserve electricity, tho.
-* There is no way to undelete a file in Linux. You deleted it, it's gone. See rm(1)
+* There is no way to undelete a file in [
Linux]
. You deleted it, it's gone. See rm(1)
-* The
command __
su -__ lets you assume
root user powers
(if you have
the password
). See su(1)
+* sudo(1) will let you execute a
command with SuperUser (or any other) privileges; it may need to be configured, in that case, see SudoNotes. If you really need a root shell, you can use su(1): execute <tt>
su -</tt> and type the root password. You should never log in as
root (except
if you managed to get
the system so shot up that you can't log in as a user
).
-* Installing a program from source is easier than you think. The sequence is usually along the lines of %%% %%%
tar xvzf filename-version.tar.gz %%%
cd filename-version %%%
./configure && make &&
make install %%% %%%
Note you have to be root for the __
make install__
step if you are installing into system wide directories. You can always install to your home directory, of course.
+* Installing a program from source is easier than you think. The sequence is usually along the lines of:
+ <pre>
+
tar xvzf ''
filename''
-''
version''
.tar.gz
+
cd ''
filename''
-''
version''
+
./configure && make
+ sudo
make install
+ </pre>
+
Note you have to be root for the <tt>
make install</tt>
step if you are installing into system wide directories. You can always install to your home directory, of course -- which you need to indicate by saying <tt>./configure --prefix=$HOME</tt> on the relevant step. You can also pass many more options, to <tt>configure</tt>, most of which needn't concern you, except for the (usually few) <tt>--enable-''foo''</tt>/<tt>--disable-''foo''</tt> and <tt>--with-''bar''</tt>/<tt>--without-''bar''</tt> which let you hand-pick features to include or omit from the resultant build of the software
.
-* Make sure you are working on the correct drive when doing any filesystem
level work - nuking the wrong partition or disk is annoying to say the least.
+* Make sure you are working on the correct drive when doing any FileSystem
level work -
- nuking the wrong partition or disk is annoying to say the least.
-* Learn how to use redirection "<"
/ ">" and pipes "|" in the shell
. See bash(1)
+* Learn how to use redirection (
"<tt><<
/tt>
", "<tt>></tt
>")
and pipes (
"<tt>
|</tt>
")
in the [Shell]
. See bash(1)
-See also AdvancedUserTips and [HowToTipsHOWTO]
+See also AdvancedUserTips
+
+----
+CategoryBeginners