https://wiki.linuxquestions.org/api.php?action=feedcontributions&feedformat=atom&user=DennisDanielsLQWiki - User contributions [en]2026-04-15T11:59:59ZUser contributionsMediaWiki 1.37.0https://wiki.linuxquestions.org/index.php?title=Talk:Ps&diff=15205Talk:Ps2005-03-02T20:42:14Z<p>DennisDaniels: </p>
<hr />
<div>How do I kill all processes owned by a user or group? I've noticed that after logout some users are still showing as active on the network.<br />
<br />
: Write a script or something. Here's a tip, <br />
ps au | tr -s ' ' | cut -d' ' -f1,2 | grep $username | cut -d' ' -f2<br />
gets you the pids of all $username's processes. [[User:Dysprosia|Dysprosia]] 01:32, Aug 28, 2004 (EDT)<br />
<br />
Could somebody write out some typical scripts for inclusion in the article? [[User:Crazyeddie|Crazyeddie]] 19:15, Aug 28, 2004 (EDT)<br />
<br />
: It would have been Better if the author above (who should have signed his/her posts, I'm not going to bother checking the history) learnt how to write a script and wouldn't have to ask, but I can see how it would be a useful example to have in the article ;)<br />
: I haven't tested this, though, since it'll be too much effort to minimize the disruption on my own system. [[User:Dysprosia|Dysprosia]] 03:50, Aug 29, 2004 (EDT)<br />
<br />
<br />
I'm getting insane load on my dual xeon 35+ users and the average load is over 30. I'm looking at the ps to try and hunt down the culprits. Could someone point to a tracking tool for isolating load hogs? thanks! --[[User:DennisDaniels|DennisDaniels]] 15:42, Mar 2, 2005 (EST)</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Chmod&diff=17067Chmod2004-12-15T00:13:22Z<p>DennisDaniels: /* Using chmod */===Case study===</p>
<hr />
<div>In Unix and Unix-like operating systems, a file has associated with it a number of security properties that control what the owner of the file and other users can do to the file. These properties are known as [[permissions]], and the '''<tt>chmod</tt>''' command modifies them.<br />
<br />
== Permissions ==<br />
Unix recognizes three groups of users who may want to access the file and bases the permissions accordingly. These groups are:<br />
* the ''owner'' of the file (who created it)<br />
* the ''group'' of that user - that is, other users who belong in the same group as the owner<br />
* all other users.<br />
<br />
These three groups are often abbreviated ''u'', ''g'', and ''o'' respectively.<br />
<br />
Based on these three groups, a file can be <br />
* readable - allow a file to be viewed <br />
* writable - allow a file to be edited<br />
* executable - allow a binary file to be run,<br />
and are abbreviated ''r'', ''w'', and ''x'' respectively.<br />
<br />
Other attributes for a file include a <br />
* [[suid]] or [[sgid]] property, abbreviated ''s''<br />
* a [[sticky]] bit, abbreivated ''t'' (seldom used)<br />
<br />
<br />
==Notation==<br />
The <tt>chmod</tt> command can be used to set permissions on a directory or its files. However, how can we tell <tt>chmod</tt> how to apply the permissions?<br />
<br />
Chmod accepts two notations, an alphabetic-based notation using the abbreviations mentioned above, and an [[octal]], numeric based notation. It is possible to perform every operation using alphabetic notation as you can in octal, and vice versa. For new users, they may only need to learn the alphabetic notation.<br />
<br />
<br />
=== Alphabetic notation ===<br />
Say we want to set a file to have read and write access by the group the user is in. The notation for this permission is <br />
g+rw<br />
<br />
Or, say a file is set read-write-execute for all users, and we wish to limit the access to all other users, the permission is<br />
o-rwx<br />
<br />
In general, the permission is notated with the character of the user type first, + to set and - to clear, and then the characters representing the permissions to set.<br />
<br />
===Numeric permissions===<br />
Numeric permissions work by a group of octal numbers. Recall firstly that each digit in a hexadecimal number represents a block of 4 binary digits - similarly, for octal numbers, each digit represents a block of 3 binary digits.<br />
<br />
Recall also that when a <tt>ls -l</tt> command is issued for a file, the permissions are listed in the form similar to<br />
-rwxr-xr-x 1 yourusername yourgroup 19 Oct 22 09:25 yourfile<br />
<br />
The permisssion list, <tt>-rwxr-xr-x</tt> is treated as a block of binary digits, a [[bitfield]]. Translating this into octal, we would get 0755, which is 0111101101 base 2.<br />
<br />
We can then represent each permission for each user type by a single octal digit (plus an extra digit for the first bit).<br />
<br />
* 400 <tt>-r--------</tt> read by owner<br />
* 040 <tt>----r-----</tt> read by group<br />
* 004 <tt>-------r--</tt> read by anybody (other)<br />
* 200 <tt>--w-------</tt> write by owner<br />
* 020 <tt>-----w----</tt> write by group<br />
* 002 <tt>--------w-</tt> write by anybody<br />
* 100 <tt>---x------</tt> execute by owner<br />
* 010 <tt>-----x----</tt> execute by group<br />
* 001 <tt>---------x</tt> execute by anybody<br />
* 4000 <tt>s---------</tt> suid<br />
* 2000 <tt>s---------</tt> sgid<br />
* 1000 <tt>t---------</tt> sticky<br />
<br />
These permissions on their own may not be very useful, but we can add the octal numbers to get a combination of permissions. For example, 4, which corresponds to r-- (for some user type), and 2, which corresponds to -w- (for some user type), can be added to get 6, 110 in binary, which corresponds to rw-, read and write. Note also that in a group of three octal digits, the "place" of the digit signifies where we assign the permission. 600 octal, in binary is 0110000000, so we are setting read and write permissions for us, but not the group or other users. 060 octal, in binary however is 0000110000, and sets it for the group only, and likewise.<br />
<br />
So, for example, if we want to set read and write for ourselves and the group, and have no permissions whatsoever for the other users, we could use the permission 660.<br />
<br />
For the extra bit at the front, if the<br />
fourth digit is omitted, chmod will leave the current setting. To clear the suid, sgid, and sticky bits, you must specify a 0 firstly to zero out the bit.<br />
<br />
==Using chmod==<br />
<tt>chmod</tt> is used by specifying the permissions, then the file to be operated on, for example:<br />
chmod g+rwx filename<br />
grants the group read/write/execute permissions to that file, or<br />
chmod 755 filename<br />
Writing 755 octal into binary would give us 0111101101, which translated into the usal permission notation would be -rwxr-xr-x, which gives all users the ability to read and execute the file, but the group nor any other users can write to the file.<br />
<br />
<br />
<tt>chmod</tt> can be used to [[recursion|recurse]] down a directory tree - that is apply the same permissions to all files in a directory and its subdirectories by using the -R flag. For example,<br />
chmod -R 755 *<br />
sets all files in the current directory to the same permission above.<br />
<br />
===Case study===<br />
LTSP environment, students were able to view other students' work. <br />
<br />
cd /home; chmod -R 750 *<br />
<br />
Worked like a charm so that only owner can veiw and edit files.<br />
<br />
==Similar commands==<br />
*[[chown]] - Changes user/group ownership of a file<br />
*[[chgrp]] - Changes the group of a file/directory<br />
*[[ls]] - Lists files<br />
<br />
==See also==<br />
*[[Permissions]]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Md5sum&diff=19468Md5sum2004-12-01T05:42:53Z<p>DennisDaniels: md5sum -c md5sum.txt</p>
<hr />
<div>'''md5sum''' is a program for verifying that contents of a file have been exactly reproduced without having access to the original file. It is often used for large files like [[ISO]] images that must be verified before they are used. A large number called the MD5 checksum (MD5sum) is calculated from the file's contents in a reproducible way that, with extremely high probability, will never produce the same MD5sum for different files. The user compares the MD5sum of the downloaded file to that obtained separately from the original source.<br />
<br />
The algorithm is designed to make it difficult to tamper with the file while still producing the same MD5sum for the tampered file. If two instances of a file have the same MD5sum, the user is assured that the instances are identical. If one is the official version, so is the other.<br />
<br />
To compute the MD5sum of a file (e.g., tmp.iso) and display it as a [[hex]] number, execute the command:<br />
$ md5sum tmp.iso<br />
<br />
<br />
You can use the -c (?) option to md5sum to check the files against the md5sum file as below.<br />
<br />
md5sum -c md5sum.txt <br />
<br />
==External links==<br />
<br />
*[http://man.linuxquestions.org/index.php?query=md5sum&section=0&type=2 md5sum man page]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Ps&diff=23778Ps2004-11-07T03:35:22Z<p>DennisDaniels: ps auxw | grep [name-of-executable]</p>
<hr />
<div>The <tt>'''ps'''</tt> command lists [[process]]es. The [[command options]] determine both which processes are listed and the format of the output. Unlike most commands, some of the options to <tt>ps</tt> do not use the hyphen ("-"), so some letters have different meanings with and without the hyphen.<br />
<br />
Examples:<br />
$ ps -fu ''username'' # "full listing" of user's processes.<br />
$ ps -fe # "full listing" of all processes.<br />
<br />
The following script kills all processes running by another user (if you are the [[superuser]])<br />
#!/bin/sh<br />
$username=$1<br />
$user_pids=`ps au | tr -s ' ' | cut -d' ' -f1,2 | grep $username \<br />
| cut -d' ' -f2`<br />
for pid in $user_pids<br />
do<br />
kill -9 $pid<br />
done<br />
<br />
To find a list of offending processes<br />
ps auxw | grep [name-of-executable]<br />
<br />
Running pkill afterward might also be nice.<br />
<br />
<br />
==See also==<br />
<br />
* <tt>[[top]]</tt> - displays a continuously updating list of processes.<br />
* <tt>[[pstree]]</tt> - displays a chart showing the hierarchy of processes.<br />
<br />
==External links==<br />
<br />
*[http://man.linuxquestions.org/index.php?query=ps&section=0&type=2 ps man page]<br />
<br />
''This article is a [[LQWiki:stub articles|stub]] and needs to be finished. [[LQWiki:plunging forward|plunge forward]] and [[LQWiki:How to edit a page|help it grow]]!''</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Find&diff=21824Find2004-11-07T01:25:01Z<p>DennisDaniels: /* Examples */ cd /tmp;find ./ -name 'dummie*' -exec rm -f \{\} ';'</p>
<hr />
<div>'''<tt>find</tt>''' is a tool which allows primarily for the searching of files in a directory hierachy. It allows for versatile search criteria, for<br />
formatted output, and for custom commands to be<br />
run on search-results<br />
<br />
==Examples==<br />
If one wants to find and delete all old backup files from your vi or emacs edit sessions, but save directories that happen to end in a tilde<br />
<br />
As root:<br />
<br />
find / -type f -name "*~" -exec rm {} \;<br />
<br />
That's it<br />
<br />
Another example, if you wanted to perform a simple recursive grep:<br />
<br />
find . -exec grep -H "searchtext" {} \;<br />
<br />
Find also works well with [[xargs]]. Using xargs minimizes the number of times that [[grep]] or [[rm]] is run, speeding things up. The last commands could have been:<br />
<br />
find / -type f -name "*~" | xargs rm<br />
find | xargs grep "searchtext"<br />
<br />
From the current dir down<br />
find . -type f -ctime -3 -exec ls -l {} \;<br />
<br />
for the last 72 hours<br />
find . -daystart -type f -ctime -3 -exec ls -l {} \;<br />
<br />
To delete all files with the name dummy in tmp try<br />
cd /tmp;find ./ -name 'dummie*' -exec rm -f \{\} ';'<br />
<br />
==External links==<br />
<br />
*[http://man.linuxquestions.org/index.php?query=find&section=0&type=2 find man page]<br />
*[http://www.gnu.org/software/findutils/findutils.html findutils web page]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Find&diff=13773Find2004-11-07T01:05:34Z<p>DennisDaniels: find . -daystart -type f -ctime -3 -exec ls -l {</p>
<hr />
<div>'''<tt>find</tt>''' is a tool which allows primarily for the searching of files in a directory hierachy. It allows for versatile search criteria, for<br />
formatted output, and for custom commands to be<br />
run on search-results<br />
<br />
==Examples==<br />
If one wants to find and delete all old backup files from your vi or emacs edit sessions, but save directories that happen to end in a tilde<br />
<br />
As root:<br />
<br />
find / -type f -name "*~" -exec rm {} \;<br />
<br />
That's it<br />
<br />
Another example, if you wanted to perform a simple recursive grep:<br />
<br />
find . -exec grep -H "searchtext" {} \;<br />
<br />
Find also works well with [[xargs]]. Using xargs minimizes the number of times that [[grep]] or [[rm]] is run, speeding things up. The last commands could have been:<br />
<br />
find / -type f -name "*~" | xargs rm<br />
find | xargs grep "searchtext"<br />
<br />
From the current dir down<br />
find . -type f -ctime -3 -exec ls -l {} \;<br />
<br />
for the last 72 hours<br />
find . -daystart -type f -ctime -3 -exec ls -l {} \;<br />
<br />
==External links==<br />
<br />
*[http://man.linuxquestions.org/index.php?query=find&section=0&type=2 find man page]<br />
*[http://www.gnu.org/software/findutils/findutils.html findutils web page]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Future_Tech&diff=12516Future Tech2004-09-29T03:24:23Z<p>DennisDaniels: vandalism in progress... rec. block this guy's IP</p>
<hr />
<div><b>Future Tech</b><br />
<br />
* [[New Hardware]]<br />
* [[PDA | PDAs]]<br />
* [[Tablet PC | Tablet PCs]]<br />
* [[Non-Stable Kernels]]<br />
<br />
<b>Upcoming Desktop Software</b><br />
<br />
* [http://galago.sf.net Galago] - this is a unified desktop "presence" framework, which allows instant messengers and other chat programs to broadcast information on who is online and what their status is. Other parts of the desktop like email programs, web browsers etc can watch this information and use it to present a better interface. It's in the early stages of development but shows great potential for the future.<br />
<br />
* [http://autopackage.org/ autopackage] - a software installation framework for Linux that hopes to make installing programs far easier in future<br />
<br />
* [http://www.nat.org/dashboard/ Dashboard] - the Dashboard watches what you are doing on the desktop and ties information from many different sources together into a coherant whole. This is sort of a dynamic, constantly updating search engine. Still in the early stages.<br />
<br />
<br />
http://wiki.linuxquestions.org/wiki/Hardware</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Permissions&diff=12132Permissions2004-09-15T02:43:54Z<p>DennisDaniels: =Why permissions?=</p>
<hr />
<div>Unix and Unix-like systems associate with each file a number of properties for security and other reasons. One set of properties, known as '''''permissions''''' are special attributes which control the ability of users to perform various operations on them.<br />
<br />
==Why permissions?==<br />
Unix and Unix-like systems such as Linux, are inherently multiuser operating systems, and have the need to issue greater control, so that one malicious user cannot interfere with another users files. For example, one user may have sensitive information that another user may want to access. Without file permissions, the other user may be able to access them. With them, the user can't read the file.<br />
<br />
On the above systems, each and every file, directory, or device has a set of permissions associated with it. These permissions are visible if one does a [[ls]] with the <tt>-l</tt> flag, which may show something like<br />
-rw-r--r-- 1 root root 1059 Dec 18 13:23 /etc/passwd<br />
<br />
The permissions block is the first thing on the line:<br />
-rw-r--r--<br />
<br />
We break this string up into four sections:<br />
- rw- r-- r--<br />
^ ^ ^ ^<br />
| | | |<br />
4 1 2 3<br />
# represents the permissions associated with the ''user'' (who created it)<br />
# represents the permissions associated with the ''group'' the user belongs to<br />
# represents the permissions associated with everyone else (often termed ''world'').<br />
# represents the file type (see below.)<br />
The first "-" is used for file type and will be explained later.<br />
<br />
In each block of three characters, the <tt>r</tt>, <tt>w</tt>, and <tt>x</tt> characters signify that the file can be ''r''ead, ''w''ritten to, or e''x''ecuted. A dash means the permission is not set (eg in 1 above, the file can be read and written by the owner, but not executed).<br />
<br />
<br />
<pre><br />
OWN GRP OTH<br />
RWX RWX RWX<br />
421 421 421<br />
</pre><br />
<br />
===Owner===<br />
Every file has an owner user. This is assigned by the [[chown]] command as such<br />
<pre><br />
chown root /etc/passwd<br />
<br />
owner<br />
read write execute<br />
R_W_X<br />
4 2 1 =7<br />
</pre><br />
<br />
===Group===<br />
Every file has an owner group. This is assigned by the [[chgrp]] command as such<br />
<pre><br />
chgrp admin /etc/passwd<br />
</pre><br />
<br />
==Changing permissions and ownerships==<br />
* To change [[file]]-permissions, use the [[chmod]] command.<br />
* To change the owner and the group of a [[file]] or [[directory]], use the [[chown]] command.<br />
<br />
Files can be marked readable (r), writable (w), and executable (x) for each of their owner, their group, and the world (everyone else). When the file is a directory, the executable byte refers to everyone. They are often represented as 3-digit octal numbers where the first digit refers to the owner, the second to the group, and the third to everyone. Each digit is the sum of the permissions one wants to grant to that user - read is 4, write is 2, and execute is 1. So, the a file that could be read and executed by all but only written by the owner would have permissions 755.<br />
<br />
When determining who has permission to do what with a file, <b>only</b> the most specific permission is evaluated. Take the following completely fictional file:<br />
<br />
-r---w---x 1 james webusers 1059 Dec 18 13:23 foo.sh<br />
<br />
This indicates that james (and only james) can read foo.sh. james cannot write or execute foo.sh (footnote: missing x permission on a shellscript can be gotten around by running it by the appropriate shell: "<code>bash foo.sh</code>"). Members of the webusers group can only write to foo.sh, and cannot read or run it. If james is a member of the webusers group, he still cannot write to the file, because only the Owner permissions (the most specific) apply to james. Everyone who is not james, or a member of webusers, can execute foo.sh, but not read or write it. (footnote: In reality, shell scripts require read permissions to execute)<br />
<br />
There is a 4th bit for each permission as well. The Owner's fourth bit is [[suid]], which causes a program to always be executed as the Owner, regardless of the user who runs the program. The Group's fourth bit has two purposes: on files, it is [[sgid]], and causes the program to always execute in that group. On directories, it causes all new files written to that directory to belong to that group automatically. The World's fourth bit is called [[sticky]]. Its most common use is on directories, where it prevents users from deleting files owned by someone else, even if they have write access to the directory (it is often used on mail spools and on /tmp). In a normal <code>ls -l</code> listing, suid and sgid are marked with "s" in place of "x". If s is set, but x is unset, then ls will display "S" instead. The sticky bit appears as "t" in place of x, and as T when x is unset. With all bits set: rwsrwsrwt, or after <code>chmod -x</code>: rwSrwSrwT.<br />
---------<br />
The precise meanings of read, write and execute can vary depending on the type of object (for example, a [[file]] or [[directory]]), in addition there may be other permissions that can be applied depending on the type of filesystem in use.<br />
<br />
Permissions may also be applied to network resources such as file or printer shares.</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Permissions&diff=12117Permissions2004-09-15T02:42:15Z<p>DennisDaniels: =Owner=</p>
<hr />
<div>Unix and Unix-like systems associate with each file a number of properties for security and other reasons. One set of properties, known as '''''permissions''''' are special attributes which control the ability of users to perform various operations on them.<br />
<br />
==Why permissions?==<br />
Unix and Unix-like systems such as Linux, are inherently multiuser operating systems, and have the need to issue greater control, so that one malicious user cannot interfere with another users files. For example, one user may have sensitive information that another user may want to access. Without file permissions, the other user may be able to access them. With them, the user can't read the file.<br />
<br />
On the above systems, each and every file, directory, or device has a set of permissions associated with it. These permissions are visible if one does a [[ls]] with the <tt>-l</tt> flag, which may show something like<br />
-rw-r--r-- 1 root root 1059 Dec 18 13:23 /etc/passwd<br />
<br />
The permissions block is the first thing on the line:<br />
-rw-r--r--<br />
<br />
We break this string up into four sections:<br />
- rw- r-- r--<br />
^ ^ ^ ^<br />
| | | |<br />
4 1 2 3<br />
# represents the permissions associated with the ''user'' (who created it)<br />
# represents the permissions associated with the ''group'' the user belongs to<br />
# represents the permissions associated with everyone else (often termed ''world'').<br />
# represents the file type (see below.)<br />
The first "-" is used for file type and will be explained later.<br />
<br />
In each block of three characters, the <tt>r</tt>, <tt>w</tt>, and <tt>x</tt> characters signify that the file can be ''r''ead, ''w''ritten to, or e''x''ecuted. A dash means the permission is not set (eg in 1 above, the file can be read and written by the owner, but not executed).<br />
<br />
===Owner===<br />
Every file has an owner user. This is assigned by the [[chown]] command as such<br />
<pre><br />
chown root /etc/passwd<br />
<br />
owner<br />
read write execute<br />
R_W_X<br />
4 2 1 =7<br />
</pre><br />
<br />
===Group===<br />
Every file has an owner group. This is assigned by the [[chgrp]] command as such<br />
<pre><br />
chgrp admin /etc/passwd<br />
</pre><br />
<br />
==Changing permissions and ownerships==<br />
* To change [[file]]-permissions, use the [[chmod]] command.<br />
* To change the owner and the group of a [[file]] or [[directory]], use the [[chown]] command.<br />
<br />
Files can be marked readable (r), writable (w), and executable (x) for each of their owner, their group, and the world (everyone else). When the file is a directory, the executable byte refers to everyone. They are often represented as 3-digit octal numbers where the first digit refers to the owner, the second to the group, and the third to everyone. Each digit is the sum of the permissions one wants to grant to that user - read is 4, write is 2, and execute is 1. So, the a file that could be read and executed by all but only written by the owner would have permissions 755.<br />
<br />
When determining who has permission to do what with a file, <b>only</b> the most specific permission is evaluated. Take the following completely fictional file:<br />
<br />
-r---w---x 1 james webusers 1059 Dec 18 13:23 foo.sh<br />
<br />
This indicates that james (and only james) can read foo.sh. james cannot write or execute foo.sh (footnote: missing x permission on a shellscript can be gotten around by running it by the appropriate shell: "<code>bash foo.sh</code>"). Members of the webusers group can only write to foo.sh, and cannot read or run it. If james is a member of the webusers group, he still cannot write to the file, because only the Owner permissions (the most specific) apply to james. Everyone who is not james, or a member of webusers, can execute foo.sh, but not read or write it. (footnote: In reality, shell scripts require read permissions to execute)<br />
<br />
There is a 4th bit for each permission as well. The Owner's fourth bit is [[suid]], which causes a program to always be executed as the Owner, regardless of the user who runs the program. The Group's fourth bit has two purposes: on files, it is [[sgid]], and causes the program to always execute in that group. On directories, it causes all new files written to that directory to belong to that group automatically. The World's fourth bit is called [[sticky]]. Its most common use is on directories, where it prevents users from deleting files owned by someone else, even if they have write access to the directory (it is often used on mail spools and on /tmp). In a normal <code>ls -l</code> listing, suid and sgid are marked with "s" in place of "x". If s is set, but x is unset, then ls will display "S" instead. The sticky bit appears as "t" in place of x, and as T when x is unset. With all bits set: rwsrwsrwt, or after <code>chmod -x</code>: rwSrwSrwT.<br />
---------<br />
The precise meanings of read, write and execute can vary depending on the type of object (for example, a [[file]] or [[directory]]), in addition there may be other permissions that can be applied depending on the type of filesystem in use.<br />
<br />
Permissions may also be applied to network resources such as file or printer shares.</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Permissions&diff=12116Permissions2004-09-15T02:42:00Z<p>DennisDaniels: =Owner=</p>
<hr />
<div>Unix and Unix-like systems associate with each file a number of properties for security and other reasons. One set of properties, known as '''''permissions''''' are special attributes which control the ability of users to perform various operations on them.<br />
<br />
==Why permissions?==<br />
Unix and Unix-like systems such as Linux, are inherently multiuser operating systems, and have the need to issue greater control, so that one malicious user cannot interfere with another users files. For example, one user may have sensitive information that another user may want to access. Without file permissions, the other user may be able to access them. With them, the user can't read the file.<br />
<br />
On the above systems, each and every file, directory, or device has a set of permissions associated with it. These permissions are visible if one does a [[ls]] with the <tt>-l</tt> flag, which may show something like<br />
-rw-r--r-- 1 root root 1059 Dec 18 13:23 /etc/passwd<br />
<br />
The permissions block is the first thing on the line:<br />
-rw-r--r--<br />
<br />
We break this string up into four sections:<br />
- rw- r-- r--<br />
^ ^ ^ ^<br />
| | | |<br />
4 1 2 3<br />
# represents the permissions associated with the ''user'' (who created it)<br />
# represents the permissions associated with the ''group'' the user belongs to<br />
# represents the permissions associated with everyone else (often termed ''world'').<br />
# represents the file type (see below.)<br />
The first "-" is used for file type and will be explained later.<br />
<br />
In each block of three characters, the <tt>r</tt>, <tt>w</tt>, and <tt>x</tt> characters signify that the file can be ''r''ead, ''w''ritten to, or e''x''ecuted. A dash means the permission is not set (eg in 1 above, the file can be read and written by the owner, but not executed).<br />
<br />
===Owner===<br />
Every file has an owner user. This is assigned by the [[chown]] command as such<br />
<pre><br />
chown root /etc/passwd<br />
</pre><br />
<br />
owner<br />
read write execute<br />
R_W_X<br />
4 2 1 =7<br />
</pre><br />
<br />
===Group===<br />
Every file has an owner group. This is assigned by the [[chgrp]] command as such<br />
<pre><br />
chgrp admin /etc/passwd<br />
</pre><br />
<br />
==Changing permissions and ownerships==<br />
* To change [[file]]-permissions, use the [[chmod]] command.<br />
* To change the owner and the group of a [[file]] or [[directory]], use the [[chown]] command.<br />
<br />
Files can be marked readable (r), writable (w), and executable (x) for each of their owner, their group, and the world (everyone else). When the file is a directory, the executable byte refers to everyone. They are often represented as 3-digit octal numbers where the first digit refers to the owner, the second to the group, and the third to everyone. Each digit is the sum of the permissions one wants to grant to that user - read is 4, write is 2, and execute is 1. So, the a file that could be read and executed by all but only written by the owner would have permissions 755.<br />
<br />
When determining who has permission to do what with a file, <b>only</b> the most specific permission is evaluated. Take the following completely fictional file:<br />
<br />
-r---w---x 1 james webusers 1059 Dec 18 13:23 foo.sh<br />
<br />
This indicates that james (and only james) can read foo.sh. james cannot write or execute foo.sh (footnote: missing x permission on a shellscript can be gotten around by running it by the appropriate shell: "<code>bash foo.sh</code>"). Members of the webusers group can only write to foo.sh, and cannot read or run it. If james is a member of the webusers group, he still cannot write to the file, because only the Owner permissions (the most specific) apply to james. Everyone who is not james, or a member of webusers, can execute foo.sh, but not read or write it. (footnote: In reality, shell scripts require read permissions to execute)<br />
<br />
There is a 4th bit for each permission as well. The Owner's fourth bit is [[suid]], which causes a program to always be executed as the Owner, regardless of the user who runs the program. The Group's fourth bit has two purposes: on files, it is [[sgid]], and causes the program to always execute in that group. On directories, it causes all new files written to that directory to belong to that group automatically. The World's fourth bit is called [[sticky]]. Its most common use is on directories, where it prevents users from deleting files owned by someone else, even if they have write access to the directory (it is often used on mail spools and on /tmp). In a normal <code>ls -l</code> listing, suid and sgid are marked with "s" in place of "x". If s is set, but x is unset, then ls will display "S" instead. The sticky bit appears as "t" in place of x, and as T when x is unset. With all bits set: rwsrwsrwt, or after <code>chmod -x</code>: rwSrwSrwT.<br />
---------<br />
The precise meanings of read, write and execute can vary depending on the type of object (for example, a [[file]] or [[directory]]), in addition there may be other permissions that can be applied depending on the type of filesystem in use.<br />
<br />
Permissions may also be applied to network resources such as file or printer shares.</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Permissions&diff=12115Permissions2004-09-15T02:41:38Z<p>DennisDaniels: =Owner= 4 2 1 =7</p>
<hr />
<div>Unix and Unix-like systems associate with each file a number of properties for security and other reasons. One set of properties, known as '''''permissions''''' are special attributes which control the ability of users to perform various operations on them.<br />
<br />
==Why permissions?==<br />
Unix and Unix-like systems such as Linux, are inherently multiuser operating systems, and have the need to issue greater control, so that one malicious user cannot interfere with another users files. For example, one user may have sensitive information that another user may want to access. Without file permissions, the other user may be able to access them. With them, the user can't read the file.<br />
<br />
On the above systems, each and every file, directory, or device has a set of permissions associated with it. These permissions are visible if one does a [[ls]] with the <tt>-l</tt> flag, which may show something like<br />
-rw-r--r-- 1 root root 1059 Dec 18 13:23 /etc/passwd<br />
<br />
The permissions block is the first thing on the line:<br />
-rw-r--r--<br />
<br />
We break this string up into four sections:<br />
- rw- r-- r--<br />
^ ^ ^ ^<br />
| | | |<br />
4 1 2 3<br />
# represents the permissions associated with the ''user'' (who created it)<br />
# represents the permissions associated with the ''group'' the user belongs to<br />
# represents the permissions associated with everyone else (often termed ''world'').<br />
# represents the file type (see below.)<br />
The first "-" is used for file type and will be explained later.<br />
<br />
In each block of three characters, the <tt>r</tt>, <tt>w</tt>, and <tt>x</tt> characters signify that the file can be ''r''ead, ''w''ritten to, or e''x''ecuted. A dash means the permission is not set (eg in 1 above, the file can be read and written by the owner, but not executed).<br />
<br />
===Owner===<br />
Every file has an owner user. This is assigned by the [[chown]] command as such<br />
<pre><br />
chown root /etc/passwd<br />
</pre><br />
<br />
owner<br />
read write execute<br />
R_W_X<br />
4 2 1 =7<br />
<br />
===Group===<br />
Every file has an owner group. This is assigned by the [[chgrp]] command as such<br />
<pre><br />
chgrp admin /etc/passwd<br />
</pre><br />
<br />
==Changing permissions and ownerships==<br />
* To change [[file]]-permissions, use the [[chmod]] command.<br />
* To change the owner and the group of a [[file]] or [[directory]], use the [[chown]] command.<br />
<br />
Files can be marked readable (r), writable (w), and executable (x) for each of their owner, their group, and the world (everyone else). When the file is a directory, the executable byte refers to everyone. They are often represented as 3-digit octal numbers where the first digit refers to the owner, the second to the group, and the third to everyone. Each digit is the sum of the permissions one wants to grant to that user - read is 4, write is 2, and execute is 1. So, the a file that could be read and executed by all but only written by the owner would have permissions 755.<br />
<br />
When determining who has permission to do what with a file, <b>only</b> the most specific permission is evaluated. Take the following completely fictional file:<br />
<br />
-r---w---x 1 james webusers 1059 Dec 18 13:23 foo.sh<br />
<br />
This indicates that james (and only james) can read foo.sh. james cannot write or execute foo.sh (footnote: missing x permission on a shellscript can be gotten around by running it by the appropriate shell: "<code>bash foo.sh</code>"). Members of the webusers group can only write to foo.sh, and cannot read or run it. If james is a member of the webusers group, he still cannot write to the file, because only the Owner permissions (the most specific) apply to james. Everyone who is not james, or a member of webusers, can execute foo.sh, but not read or write it. (footnote: In reality, shell scripts require read permissions to execute)<br />
<br />
There is a 4th bit for each permission as well. The Owner's fourth bit is [[suid]], which causes a program to always be executed as the Owner, regardless of the user who runs the program. The Group's fourth bit has two purposes: on files, it is [[sgid]], and causes the program to always execute in that group. On directories, it causes all new files written to that directory to belong to that group automatically. The World's fourth bit is called [[sticky]]. Its most common use is on directories, where it prevents users from deleting files owned by someone else, even if they have write access to the directory (it is often used on mail spools and on /tmp). In a normal <code>ls -l</code> listing, suid and sgid are marked with "s" in place of "x". If s is set, but x is unset, then ls will display "S" instead. The sticky bit appears as "t" in place of x, and as T when x is unset. With all bits set: rwsrwsrwt, or after <code>chmod -x</code>: rwSrwSrwT.<br />
---------<br />
The precise meanings of read, write and execute can vary depending on the type of object (for example, a [[file]] or [[directory]]), in addition there may be other permissions that can be applied depending on the type of filesystem in use.<br />
<br />
Permissions may also be applied to network resources such as file or printer shares.</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Vmstat&diff=12066Vmstat2004-09-12T23:42:21Z<p>DennisDaniels: </p>
<hr />
<div>If your CPU is going hog wild try '''vmstat 5''' for a five second snapshot of your usage.<br />
<br />
The 'us' (user) column will be mostly from application level<br />
processing, while the 'sy' (system) column is kernel (inside device<br />
drivers, filesystem code, etc.).<br />
<br />
see also [[top]]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Vmstat&diff=12051Vmstat2004-09-12T23:41:26Z<p>DennisDaniels: </p>
<hr />
<div>If your CPU is going hog wild try vmstat 5 for a five second snapshot of your usage.<br />
<br />
The 'us' (user) column will be mostly from application level<br />
processing, while the 'sy' (system) column is kernel (inside device<br />
drivers, filesystem code, etc.).<br />
<br />
see also [[top]]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Talk:Screenshot&diff=18801Talk:Screenshot2004-09-08T03:14:13Z<p>DennisDaniels: </p>
<hr />
<div>gif is more for cartoons and paintings and artwork of that sort. Jpeg is more for photographic realism which is generally what people are shooting for (npi) with screenshots. And both have licensing issues. png is similar to jpeg , probably better, and doesn't have issues. AFAIK. IMHO. ETC. :)<br />
<br />
<br />
<br />
View (previous 50) (next 50) (20 | 50 | 100 | 250 | 500).<br />
<br />
Legend: (cur) = difference with current version, (last) = difference with preceding version, M = minor edit<br />
<br />
* (cur) (last) . . 12:52, Apr 9, 2004 . . Skyline (moved to "Screenshot")<br />
<br />
View (previous 50) (next 50) (20 | 50 | 100 | 250 | 500).<br />
<br />
<br />
Skyline, I assume this is the page that you are refereing to about me duplicating? I can't get the information from my previous edit to merge with the older edit... I'm not smoking anything! I swear!<br />
[[User:AaronPeterson|AaronPeterson]] 04:23, Apr 11, 2004 (EDT)<br />
<br />
:It was "merged" in a couple of days ago - check the link below<br />
<br />
:http://wiki.linuxquestions.org/wiki.phtml?title=Screenshot&diff=7780&oldid=7774<br />
<br />
:You'll see that it has been intergrated further since then - [[User:Skyline|Skyline]] 09:44, Apr 11, 2004 (EDT)<br />
------<br />
How do we post screengrabs to the pages?<br />
<br />
<br />
:images cannot be uploaded to the LQ Wiki, but you can link to off site images. See http://wiki.linuxquestions.org/wiki/LQWiki:Wiki_markup#Pictures for more info. Note that you should follow the MoS and also use images somewhat sparingly, as some people are still stuck on dialup. [[User:Jeremy|Jeremy]] 20:51, Sep 7, 2004 (EDT)<br />
::K, thanks <br />
http://images.linuxquestions.org/questions/images/LinuxQuestions-wiki.gif<br />
<br />
--[[User:DennisDaniels|DennisDaniels]] 23:13, Sep 7, 2004 (EDT)</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Talk:Screenshot&diff=11787Talk:Screenshot2004-09-08T03:13:08Z<p>DennisDaniels: </p>
<hr />
<div>gif is more for cartoons and paintings and artwork of that sort. Jpeg is more for photographic realism which is generally what people are shooting for (npi) with screenshots. And both have licensing issues. png is similar to jpeg , probably better, and doesn't have issues. AFAIK. IMHO. ETC. :)<br />
<br />
<br />
<br />
View (previous 50) (next 50) (20 | 50 | 100 | 250 | 500).<br />
<br />
Legend: (cur) = difference with current version, (last) = difference with preceding version, M = minor edit<br />
<br />
* (cur) (last) . . 12:52, Apr 9, 2004 . . Skyline (moved to "Screenshot")<br />
<br />
View (previous 50) (next 50) (20 | 50 | 100 | 250 | 500).<br />
<br />
<br />
Skyline, I assume this is the page that you are refereing to about me duplicating? I can't get the information from my previous edit to merge with the older edit... I'm not smoking anything! I swear!<br />
[[User:AaronPeterson|AaronPeterson]] 04:23, Apr 11, 2004 (EDT)<br />
<br />
:It was "merged" in a couple of days ago - check the link below<br />
<br />
:http://wiki.linuxquestions.org/wiki.phtml?title=Screenshot&diff=7780&oldid=7774<br />
<br />
:You'll see that it has been intergrated further since then - [[User:Skyline|Skyline]] 09:44, Apr 11, 2004 (EDT)<br />
------<br />
How do we post screengrabs to the pages?<br />
<br />
<br />
:images cannot be uploaded to the LQ Wiki, but you can link to off site images. See http://wiki.linuxquestions.org/wiki/LinuxQuestions.org_Wiki:Wiki_markup#Pictures for more info. Note that you should follow the MoS and also use images somewhat sparingly, as some people are still stuck on dialup. [[User:Jeremy|Jeremy]] 20:51, Sep 7, 2004 (EDT)<br />
::K, thanks --[[User:DennisDaniels|DennisDaniels]] 23:13, Sep 7, 2004 (EDT)</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Talk:Screenshot&diff=11785Talk:Screenshot2004-09-07T23:12:22Z<p>DennisDaniels: </p>
<hr />
<div>gif is more for cartoons and paintings and artwork of that sort. Jpeg is more for photographic realism which is generally what people are shooting for (npi) with screenshots. And both have licensing issues. png is similar to jpeg , probably better, and doesn't have issues. AFAIK. IMHO. ETC. :)<br />
<br />
<br />
<br />
View (previous 50) (next 50) (20 | 50 | 100 | 250 | 500).<br />
<br />
Legend: (cur) = difference with current version, (last) = difference with preceding version, M = minor edit<br />
<br />
* (cur) (last) . . 12:52, Apr 9, 2004 . . Skyline (moved to "Screenshot")<br />
<br />
View (previous 50) (next 50) (20 | 50 | 100 | 250 | 500).<br />
<br />
<br />
Skyline, I assume this is the page that you are refereing to about me duplicating? I can't get the information from my previous edit to merge with the older edit... I'm not smoking anything! I swear!<br />
[[User:AaronPeterson|AaronPeterson]] 04:23, Apr 11, 2004 (EDT)<br />
<br />
:It was "merged" in a couple of days ago - check the link below<br />
<br />
:http://wiki.linuxquestions.org/wiki.phtml?title=Screenshot&diff=7780&oldid=7774<br />
<br />
:You'll see that it has been intergrated further since then - [[User:Skyline|Skyline]] 09:44, Apr 11, 2004 (EDT)<br />
------<br />
How do we post screengrabs to the pages?</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Chmod&diff=11788Chmod2004-09-07T23:10:34Z<p>DennisDaniels: =Numeric permissions= The left number is read, center write and right excute.</p>
<hr />
<div>'''chmod''' is a command that changes the permissions of a file.<br />
<br />
==Syntax==<br />
'''chmod [-r] permissions filenames'''<br><br />
* ''-r'' Change the permission on files that are in the subdirectories of the directory that you are currently in.<br />
* ''permissions'' Specifies the rights that are being granted. Below is the different rights that you can grant in alpha an numeric format.<br />
* ''filenames'' File or directory you want to associate the file with.<br />
<br />
===Permissions===<br />
* ''u'' - User who owns the file.<br />
* ''g'' - Group that owns the file.<br />
* ''o'' - Other.<br />
* ''a'' - All.<br />
* ''r'' - Read the file.<br />
* ''w'' - Write or edit the file.<br />
* ''x'' - Execute or run the file as a program.<br />
* ''s'' - [[Suid]] or [[Sgid]] bit<br />
* ''t'' - [[Sticky]] bit<br />
<br />
===Numeric permissions===<br />
<br />
Permissions can be added to a file or directory by experessing if with a number that is generated from these basic blocks. A system admin can assign (4) read, (2)write and (1)execute. The left number is read, center write and right excute.<br />
<br />
* ''400'' read by owner<br />
* ''040'' read by group<br />
* ''004'' read by anybody (other)<br />
* ''200'' write by owner<br />
* ''020'' write by group<br />
* ''002'' write by anybody<br />
* ''100'' execute by owner<br />
* ''010'' execute by group<br />
* ''001'' execute by anybody<br />
<br />
Add up your total list of perms you want for a file and then you'll be able to know the permission settings.<br />
For example: I want owner to be able to read and write but not execute.<br />
<br />
<tt>400 read by owner</tt><br />
<br />
<tt>200 write by owner</tt><br />
<br />
<tt>=600</tt><br />
Pass this command and only the owner will be able to read and write.<br />
<br />
<tt>chmod 600 filename</tt><br />
--------<br />
An optional fourth octet is used for suid/sgid/sticky:<br />
<br />
* ''4000'' suid<br />
* ''2000'' sgid<br />
* ''1000'' sticky<br />
<br />
If this fourth digit is omitted, chmod will leave the current setting. To clear the suid, sgid, and sticky bits, you must specify a 0, for example: 0755.<br />
<br />
==Examples==<br />
'''chmod g+rwx filename'''<br><br />
:Grants the group read/write/execute permissions to that file<br />
<br />
''' chmod 755 filename'''<br><br />
:Which would be the following 400+040+004+200+020+100+010+001 = 775 where you are giving all the rights but the capability for anyone to edit the file.<br />
<br />
''' chmod -R 755 *.*''' <br><br />
:Set all files in the current dir to chmod 755.<br />
Another way to achieve this, including to use subdirectories would be to use one of the following:<br />
<br />
*) In current working directory do:<br />
find . -type f -name "*\.pl" | xargs chmod 755<br />
<br />
*) Or, specify the root dir:<br />
find /path/to/that/dir -type f -name "*\.pl" | xargs chmod 755 <br />
<br />
<br />
==Additional information==<br />
By using the command [[ls]], for example ''ls -l'', you see the following result:<br><br><br />
''-rwxr-xr-x 1 yourusername yourgroup 19 Oct 22 09:25 yourfile''<br><br />
:The first '''rwx''' is owner permission, which means that the user ''yourusername'' can read, write and execute the file. '''r-x''' means that members of ''yourgroup'' can read and execute, but not write, and the last '''r-x''' means that others can read, and execute, but not write.<br />
<br />
==Similar commands==<br />
*[[chown]] - Changes user/group ownership of a file<br />
*[[chgrp]] - Changes the group of a file/directory<br />
*[[ls]] - Lists files<br />
<br />
==See also==<br />
*[[Permissions]]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Chmod&diff=11783Chmod2004-09-07T23:04:21Z<p>DennisDaniels: Pass this command and only the owner will be able to read and write.</p>
<hr />
<div>'''chmod''' is a command that changes the permissions of a file.<br />
<br />
==Syntax==<br />
'''chmod [-r] permissions filenames'''<br><br />
* ''-r'' Change the permission on files that are in the subdirectories of the directory that you are currently in.<br />
* ''permissions'' Specifies the rights that are being granted. Below is the different rights that you can grant in alpha an numeric format.<br />
* ''filenames'' File or directory you want to associate the file with.<br />
<br />
===Permissions===<br />
* ''u'' - User who owns the file.<br />
* ''g'' - Group that owns the file.<br />
* ''o'' - Other.<br />
* ''a'' - All.<br />
* ''r'' - Read the file.<br />
* ''w'' - Write or edit the file.<br />
* ''x'' - Execute or run the file as a program.<br />
* ''s'' - [[Suid]] or [[Sgid]] bit<br />
* ''t'' - [[Sticky]] bit<br />
<br />
===Numeric permissions===<br />
<br />
Permissions can be added to a file or directory by experessing if with a number that is generated from these basic blocks.<br />
<br />
* ''400'' read by owner<br />
* ''040'' read by group<br />
* ''004'' read by anybody (other)<br />
* ''200'' write by owner<br />
* ''020'' write by group<br />
* ''002'' write by anybody<br />
* ''100'' execute by owner<br />
* ''010'' execute by group<br />
* ''001'' execute by anybody<br />
<br />
Add up your total list of perms you want for a file and then you'll be able to know the permission settings.<br />
For example: I want owner to be able to read and write but not execute.<br />
<br />
<tt>400 read by owner</tt><br />
<br />
<tt>200 write by owner</tt><br />
<br />
<tt>=600</tt><br />
Pass this command and only the owner will be able to read and write.<br />
<br />
<tt>chmod 600 filename</tt><br />
--------<br />
An optional fourth octet is used for suid/sgid/sticky:<br />
<br />
* ''4000'' suid<br />
* ''2000'' sgid<br />
* ''1000'' sticky<br />
<br />
If this fourth digit is omitted, chmod will leave the current setting. To clear the suid, sgid, and sticky bits, you must specify a 0, for example: 0755.<br />
<br />
==Examples==<br />
'''chmod g+rwx filename'''<br><br />
:Grants the group read/write/execute permissions to that file<br />
<br />
''' chmod 755 filename'''<br><br />
:Which would be the following 400+040+004+200+020+100+010+001 = 775 where you are giving all the rights but the capability for anyone to edit the file.<br />
<br />
''' chmod -R 755 *.*''' <br><br />
:Set all files in the current dir to chmod 755.<br />
Another way to achieve this, including to use subdirectories would be to use one of the following:<br />
<br />
*) In current working directory do:<br />
find . -type f -name "*\.pl" | xargs chmod 755<br />
<br />
*) Or, specify the root dir:<br />
find /path/to/that/dir -type f -name "*\.pl" | xargs chmod 755 <br />
<br />
<br />
==Additional information==<br />
By using the command [[ls]], for example ''ls -l'', you see the following result:<br><br><br />
''-rwxr-xr-x 1 yourusername yourgroup 19 Oct 22 09:25 yourfile''<br><br />
:The first '''rwx''' is owner permission, which means that the user ''yourusername'' can read, write and execute the file. '''r-x''' means that members of ''yourgroup'' can read and execute, but not write, and the last '''r-x''' means that others can read, and execute, but not write.<br />
<br />
==Similar commands==<br />
*[[chown]] - Changes user/group ownership of a file<br />
*[[chgrp]] - Changes the group of a file/directory<br />
*[[ls]] - Lists files<br />
<br />
==See also==<br />
*[[Permissions]]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Chmod&diff=11782Chmod2004-09-07T23:01:25Z<p>DennisDaniels: =Numeric permissions=</p>
<hr />
<div>'''chmod''' is a command that changes the permissions of a file.<br />
<br />
==Syntax==<br />
'''chmod [-r] permissions filenames'''<br><br />
* ''-r'' Change the permission on files that are in the subdirectories of the directory that you are currently in.<br />
* ''permissions'' Specifies the rights that are being granted. Below is the different rights that you can grant in alpha an numeric format.<br />
* ''filenames'' File or directory you want to associate the file with.<br />
<br />
===Permissions===<br />
* ''u'' - User who owns the file.<br />
* ''g'' - Group that owns the file.<br />
* ''o'' - Other.<br />
* ''a'' - All.<br />
* ''r'' - Read the file.<br />
* ''w'' - Write or edit the file.<br />
* ''x'' - Execute or run the file as a program.<br />
* ''s'' - [[Suid]] or [[Sgid]] bit<br />
* ''t'' - [[Sticky]] bit<br />
<br />
===Numeric permissions===<br />
<br />
Permissions can be added to a file or directory by experessing if with a number that is generated from these basic blocks.<br />
<br />
* ''400'' read by owner<br />
* ''040'' read by group<br />
* ''004'' read by anybody (other)<br />
* ''200'' write by owner<br />
* ''020'' write by group<br />
* ''002'' write by anybody<br />
* ''100'' execute by owner<br />
* ''010'' execute by group<br />
* ''001'' execute by anybody<br />
<br />
Add up your total list of perms you want for a file and then you'll be able to know the permission settings.<br />
For example: I want owner to be able to read and write but not execute.<br />
400 read by owner<br />
200 write by owner<br />
=600<br />
''' chmod 600 filename'''<br />
--------<br />
An optional fourth octet is used for suid/sgid/sticky:<br />
<br />
* ''4000'' suid<br />
* ''2000'' sgid<br />
* ''1000'' sticky<br />
<br />
If this fourth digit is omitted, chmod will leave the current setting. To clear the suid, sgid, and sticky bits, you must specify a 0, for example: 0755.<br />
<br />
==Examples==<br />
'''chmod g+rwx filename'''<br><br />
:Grants the group read/write/execute permissions to that file<br />
<br />
''' chmod 755 filename'''<br><br />
:Which would be the following 400+040+004+200+020+100+010+001 = 775 where you are giving all the rights but the capability for anyone to edit the file.<br />
<br />
''' chmod -R 755 *.*''' <br><br />
:Set all files in the current dir to chmod 755.<br />
Another way to achieve this, including to use subdirectories would be to use one of the following:<br />
<br />
*) In current working directory do:<br />
find . -type f -name "*\.pl" | xargs chmod 755<br />
<br />
*) Or, specify the root dir:<br />
find /path/to/that/dir -type f -name "*\.pl" | xargs chmod 755 <br />
<br />
<br />
==Additional information==<br />
By using the command [[ls]], for example ''ls -l'', you see the following result:<br><br><br />
''-rwxr-xr-x 1 yourusername yourgroup 19 Oct 22 09:25 yourfile''<br><br />
:The first '''rwx''' is owner permission, which means that the user ''yourusername'' can read, write and execute the file. '''r-x''' means that members of ''yourgroup'' can read and execute, but not write, and the last '''r-x''' means that others can read, and execute, but not write.<br />
<br />
==Similar commands==<br />
*[[chown]] - Changes user/group ownership of a file<br />
*[[chgrp]] - Changes the group of a file/directory<br />
*[[ls]] - Lists files<br />
<br />
==See also==<br />
*[[Permissions]]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Chmod&diff=11781Chmod2004-09-07T23:00:54Z<p>DennisDaniels: add 'em up</p>
<hr />
<div>'''chmod''' is a command that changes the permissions of a file.<br />
<br />
==Syntax==<br />
'''chmod [-r] permissions filenames'''<br><br />
* ''-r'' Change the permission on files that are in the subdirectories of the directory that you are currently in.<br />
* ''permissions'' Specifies the rights that are being granted. Below is the different rights that you can grant in alpha an numeric format.<br />
* ''filenames'' File or directory you want to associate the file with.<br />
<br />
===Permissions===<br />
* ''u'' - User who owns the file.<br />
* ''g'' - Group that owns the file.<br />
* ''o'' - Other.<br />
* ''a'' - All.<br />
* ''r'' - Read the file.<br />
* ''w'' - Write or edit the file.<br />
* ''x'' - Execute or run the file as a program.<br />
* ''s'' - [[Suid]] or [[Sgid]] bit<br />
* ''t'' - [[Sticky]] bit<br />
<br />
===Numeric permissions===<br />
Permissions can be added to a file or directory by experessing if with a number that is generated from these basic blocks.<br />
<br />
* ''400'' read by owner<br />
* ''040'' read by group<br />
* ''004'' read by anybody (other)<br />
* ''200'' write by owner<br />
* ''020'' write by group<br />
* ''002'' write by anybody<br />
* ''100'' execute by owner<br />
* ''010'' execute by group<br />
* ''001'' execute by anybody<br />
<br />
Add up your total list of perms you want for a file and then you'll be able to know the permission settings.<br />
For example: I want owner to be able to read and write but not execute.<br />
400 read by owner<br />
200 write by owner<br />
=600<br />
''' chmod 600 filename'''<br />
--------<br />
An optional fourth octet is used for suid/sgid/sticky:<br />
<br />
* ''4000'' suid<br />
* ''2000'' sgid<br />
* ''1000'' sticky<br />
<br />
If this fourth digit is omitted, chmod will leave the current setting. To clear the suid, sgid, and sticky bits, you must specify a 0, for example: 0755.<br />
<br />
==Examples==<br />
'''chmod g+rwx filename'''<br><br />
:Grants the group read/write/execute permissions to that file<br />
<br />
''' chmod 755 filename'''<br><br />
:Which would be the following 400+040+004+200+020+100+010+001 = 775 where you are giving all the rights but the capability for anyone to edit the file.<br />
<br />
''' chmod -R 755 *.*''' <br><br />
:Set all files in the current dir to chmod 755.<br />
Another way to achieve this, including to use subdirectories would be to use one of the following:<br />
<br />
*) In current working directory do:<br />
find . -type f -name "*\.pl" | xargs chmod 755<br />
<br />
*) Or, specify the root dir:<br />
find /path/to/that/dir -type f -name "*\.pl" | xargs chmod 755 <br />
<br />
<br />
==Additional information==<br />
By using the command [[ls]], for example ''ls -l'', you see the following result:<br><br><br />
''-rwxr-xr-x 1 yourusername yourgroup 19 Oct 22 09:25 yourfile''<br><br />
:The first '''rwx''' is owner permission, which means that the user ''yourusername'' can read, write and execute the file. '''r-x''' means that members of ''yourgroup'' can read and execute, but not write, and the last '''r-x''' means that others can read, and execute, but not write.<br />
<br />
==Similar commands==<br />
*[[chown]] - Changes user/group ownership of a file<br />
*[[chgrp]] - Changes the group of a file/directory<br />
*[[ls]] - Lists files<br />
<br />
==See also==<br />
*[[Permissions]]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Chmod&diff=11780Chmod2004-09-07T22:59:30Z<p>DennisDaniels: =Numeric permissions=</p>
<hr />
<div>'''chmod''' is a command that changes the permissions of a file.<br />
<br />
==Syntax==<br />
'''chmod [-r] permissions filenames'''<br><br />
* ''-r'' Change the permission on files that are in the subdirectories of the directory that you are currently in.<br />
* ''permissions'' Specifies the rights that are being granted. Below is the different rights that you can grant in alpha an numeric format.<br />
* ''filenames'' File or directory you want to associate the file with.<br />
<br />
===Permissions===<br />
* ''u'' - User who owns the file.<br />
* ''g'' - Group that owns the file.<br />
* ''o'' - Other.<br />
* ''a'' - All.<br />
* ''r'' - Read the file.<br />
* ''w'' - Write or edit the file.<br />
* ''x'' - Execute or run the file as a program.<br />
* ''s'' - [[Suid]] or [[Sgid]] bit<br />
* ''t'' - [[Sticky]] bit<br />
<br />
===Numeric permissions===<br />
Permissions can be added to a file or directory by experessing if with a number that is generated from these basic blocks.<br />
<br />
* ''400'' read by owner<br />
* ''040'' read by group<br />
* ''004'' read by anybody (other)<br />
* ''200'' write by owner<br />
* ''020'' write by group<br />
* ''002'' write by anybody<br />
* ''100'' execute by owner<br />
* ''010'' execute by group<br />
* ''001'' execute by anybody<br />
<br />
Add up your total list of perms you want for a file and then you'll be able to know the permission settings.<br />
For example: I want owner to be able to read and write but not execute.<br />
400 read by owner<br />
200 write by owner<br />
=600<br />
An optional fourth octet is used for suid/sgid/sticky:<br />
<br />
* ''4000'' suid<br />
* ''2000'' sgid<br />
* ''1000'' sticky<br />
<br />
If this fourth digit is omitted, chmod will leave the current setting. To clear the suid, sgid, and sticky bits, you must specify a 0, for example: 0755.<br />
<br />
==Examples==<br />
'''chmod g+rwx filename'''<br><br />
:Grants the group read/write/execute permissions to that file<br />
<br />
''' chmod 755 filename'''<br><br />
:Which would be the following 400+040+004+200+020+100+010+001 = 775 where you are giving all the rights but the capability for anyone to edit the file.<br />
<br />
''' chmod -R 755 *.*''' <br><br />
:Set all files in the current dir to chmod 755.<br />
Another way to achieve this, including to use subdirectories would be to use one of the following:<br />
<br />
*) In current working directory do:<br />
find . -type f -name "*\.pl" | xargs chmod 755<br />
<br />
*) Or, specify the root dir:<br />
find /path/to/that/dir -type f -name "*\.pl" | xargs chmod 755 <br />
<br />
<br />
==Additional information==<br />
By using the command [[ls]], for example ''ls -l'', you see the following result:<br><br><br />
''-rwxr-xr-x 1 yourusername yourgroup 19 Oct 22 09:25 yourfile''<br><br />
:The first '''rwx''' is owner permission, which means that the user ''yourusername'' can read, write and execute the file. '''r-x''' means that members of ''yourgroup'' can read and execute, but not write, and the last '''r-x''' means that others can read, and execute, but not write.<br />
<br />
==Similar commands==<br />
*[[chown]] - Changes user/group ownership of a file<br />
*[[chgrp]] - Changes the group of a file/directory<br />
*[[ls]] - Lists files<br />
<br />
==See also==<br />
*[[Permissions]]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Chown&diff=11790Chown2004-09-07T22:50:28Z<p>DennisDaniels: </p>
<hr />
<div>In Linux and other Unix-like operating systems, each user on the system has control about what other users can do to your files, and to whom does the files on the system belong to. The ownership of a file has a number of consequences, and in some cases, it may be useful to ''change'' the ownership of a file. <br />
<br />
Only the [[superuser]] can use '''chown''' because it changes the ownership of a file. File and directory control is critical for [[system security]].<br />
<br />
== Using chown ==<br />
Chown is used as follows:<br />
chown ''owner'' ''file''<br />
<br />
For example, if you wanted to "give" the file <tt>picture.jpg</tt> to the user <tt>john</tt>, you could use<br />
chown john picture.jpg<br />
<br />
Instead of just the owner, the [[group]] can be changed as well, or both the user and group. Use a colon to seperate owner from group (with no space).<br />
<br />
For example, <br />
chown john:family picture.jpg<br />
changes the owner of ''picture.jpg'' to <tt>john</tt>, and the group to <tt>family</tt><br />
<br />
== Changing ownership of a tree ==<br />
<br />
If you want to transfer ownership of a whole section of a tree, you can use:<br />
<br />
chown -R ''user''.''group'' ''/path/to/subtree''<br />
<br />
<tt>-R</tt> means "recursive."<br />
<br />
For instance, if you want to change ownership of the immediate subtree to root, you can write:<br />
<br />
chown -R root.root .<br />
<br />
It is tempting to use "*" to refer to all files. However, this will not change ownership of dot files. It may also be tempting to use ".*", however, this will match against "..", and change ownership of all files in the parent directory as well! Note that the argument when using <tt>-R</tt> is a ''directory,'' not individually named files.<br />
<br />
==See also==<br />
*[[chmod]] - changes permissions of a file, instead of the owner<br />
*[[chgrp]] - changes the group of a file/directory</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Talk:Rsync&diff=24041Talk:Rsync2004-09-04T04:30:02Z<p>DennisDaniels: </p>
<hr />
<div>How do I exclude multiple directories when doing an rsync? rsync --exclude /foo works, but I want to specify more directories to exclude, any ideas?<br />
<br />
--[[User:Hackeron|Hackeron]] 13:50, May 9, 2004 (EDT)<br />
<br />
<br />
Questions should be posted at [http://www.linuxquestions.org/ LQ]. This part of LQ is for articles. Thanks. --[[User:Digiot|Digiot]] 15:06, May 9, 2004 (EDT)<br />
<br />
:port number? --[[User:DennisDaniels|DennisDaniels]] 00:30, Sep 4, 2004 (EDT)</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=LTSP&diff=12675LTSP2004-09-04T04:24:26Z<p>DennisDaniels: =config scroll mouse= clean up</p>
<hr />
<div>[http://ltsp.org/ Linux Terminal Server Project] allows a [[system administrator]] to easily set up a single Linux server to provide multiple [[dumb client]]s with network service.<br />
<br />
===config scroll mouse===<br />
Set the following in the lts.conf file:<br />
<br />
<pre><br />
X_MOUSE_PROTOCOL = "IMPS/2"<br />
X_MOUSE_DEVICE = "/dev/psaux"<br />
X_MOUSE_BUTTONS = 3<br />
</pre><br />
<br />
{{msg:stub}}</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=LTSP&diff=11516LTSP2004-09-04T04:23:59Z<p>DennisDaniels: =config scroll mouse=</p>
<hr />
<div>[http://ltsp.org/ Linux Terminal Server Project] allows a [[system administrator]] to easily set up a single Linux server to provide multiple [[dumb client]]s with network service.<br />
<br />
===config scroll mouse===<br />
Set the following in the lts.conf file:<br />
<br />
<tt><br />
X_MOUSE_PROTOCOL = "IMPS/2"<br />
X_MOUSE_DEVICE = "/dev/psaux"<br />
X_MOUSE_BUTTONS = 3<br />
</tt><br />
<br />
{{msg:stub}}</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=LTSP&diff=11515LTSP2004-09-04T04:23:48Z<p>DennisDaniels: =config scroll mouse=</p>
<hr />
<div>[http://ltsp.org/ Linux Terminal Server Project] allows a [[system administrator]] to easily set up a single Linux server to provide multiple [[dumb client]]s with network service.<br />
<br />
===config scroll mouse===<br />
Set the following in the lts.conf file:<br />
<tt><br />
X_MOUSE_PROTOCOL = "IMPS/2"<br />
X_MOUSE_DEVICE = "/dev/psaux"<br />
X_MOUSE_BUTTONS = 3<br />
</tt><br />
{{msg:stub}}</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=LTSP&diff=11514LTSP2004-09-04T04:23:30Z<p>DennisDaniels: </p>
<hr />
<div>[http://ltsp.org/ Linux Terminal Server Project] allows a [[system administrator]] to easily set up a single Linux server to provide multiple [[dumb client]]s with network service.<br />
<br />
===config scroll mouse===<br />
Set the following in the lts.conf file:<br />
<br />
X_MOUSE_PROTOCOL = "IMPS/2"<br />
X_MOUSE_DEVICE = "/dev/psaux"<br />
X_MOUSE_BUTTONS = 3<br />
<br />
{{msg:stub}}</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=LTSP&diff=11513LTSP2004-09-04T04:23:17Z<p>DennisDaniels: bits and pieces</p>
<hr />
<div>[http://ltsp.org/ Linux Terminal Server Project] allows a [[system administrator]] to easily set up a single Linux server to provide multiple [[dumb client]]s with network service.<br />
<br />
==config scroll mouse===<br />
Set the following in the lts.conf file:<br />
<br />
X_MOUSE_PROTOCOL = "IMPS/2"<br />
X_MOUSE_DEVICE = "/dev/psaux"<br />
X_MOUSE_BUTTONS = 3<br />
<br />
{{msg:stub}}</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Gdm&diff=11415Gdm2004-09-02T00:44:04Z<p>DennisDaniels: </p>
<hr />
<div>'''GDM''' ('''GNOME Display Manager''') is the [[GNOME]] "login manager". It is a complete re-write of [[xdm]], and shares no code with it.<br />
<br />
(Disrupts service)<br />
<br />
/usr/sbin/gdm-restart<br />
<br />
or<br />
<br />
(Does not disrupt service)<br />
<br />
/usr/sbin/gdm-safe-restart<br />
<br />
Easy way to change from gdm to kdm change /etc/sysconfig/desktop so it contains the following:<br />
<br />
DESKTOP="KDE"<br />
DISPLAYMANAGER="KDE"<br />
<br />
==See also==<br />
*[[xdm]]<br />
*[[kdm]]<br />
<br />
{{msg:stub}}</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Gdm&diff=11414Gdm2004-09-02T00:39:33Z<p>DennisDaniels: </p>
<hr />
<div>'''GDM''' ('''GNOME Display Manager''') is the [[GNOME]] "login manager". It is a complete re-write of [[xdm]], and shares no code with it.<br />
<br />
(Disrupts service)<br />
<br />
/usr/sbin/gdm-restart<br />
<br />
or<br />
<br />
(Does not disrupt service)<br />
<br />
/usr/sbin/gdm-safe-restart<br />
<br />
==See also==<br />
*[[xdm]]<br />
*[[kdm]]<br />
<br />
{{msg:stub}}</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Gdm&diff=11413Gdm2004-09-02T00:39:21Z<p>DennisDaniels: </p>
<hr />
<div>'''GDM''' ('''GNOME Display Manager''') is the [[GNOME]] "login manager". It is a complete re-write of [[xdm]], and shares no code with it.<br />
<br />
(Disrupts service)<br />
/usr/sbin/gdm-restart<br />
<br />
or<br />
<br />
(Does not disrupt service)<br />
/usr/sbin/gdm-safe-restart<br />
<br />
==See also==<br />
*[[xdm]]<br />
*[[kdm]]<br />
<br />
{{msg:stub}}</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Yum&diff=11557Yum2004-09-02T00:32:04Z<p>DennisDaniels: </p>
<hr />
<div>'''Yum''' ('''Y'''ellow dog '''U'''pdater '''M'''odified) is an [[RPM]] manager that provides facilities for downloading, installing and upgrading programs.<br />
<br />
A 'yum check-update' will tell you what updates are available and applicable to your system. You could create a simple cron job of your own to email that to you, or you could modify /etc/cron.daily/yum.cron to do it (that is what the yum rc.d script enables), or you could install yum-applet (see http://www.fedoranews.org/tchung/yum-applet/ ) for a gui desktop indicator.<br />
<br />
==See also==<br />
*[[Synaptic]]<br />
*[[Up2date]]<br />
<br />
==External links==<br />
*[http://linux.duke.edu/projects/yum/ Yum homepage]<br />
*[http://linux.duke.edu/projects/yum/howitworks.ptml How Yum works]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=IceWM&diff=15899IceWM2004-09-02T00:28:31Z<p>DennisDaniels: =menu=</p>
<hr />
<div>==General==<br />
<br />
[http://www.icewm.org/ IceWM] is a fast, lightweight window manager capable of emulating the look and feel of many other GUIs or of attaining a look all its own.<br />
<br />
Ice provides a toolbar with an application menu, region of application buttons, window buttons, system tray area, system monitors, and clock. It is similar to the Windows/KDE/Gnome/etc toolbars. Conversely, the entire menu or parts of it may be disabled. It provides sophisticated windowing controls, a host of right click menus (including a desktop menu identical to the toolbar's menu) and several ways to manage multiple windows and desktops. And all in a handful of executables and a few plain-text configuration files.<br />
<br />
Eye candy is not the primary focus, but it can be 'prettier' than some give it credit for. More important than that, it is very usable, configurable, and stable.<br />
<br />
==Disclaimer==<br />
<br />
I (the initial author) use Slackware and do everything the 'hard' way and am not very good at it. One could emerge or apt-get ice or at least install a package, and there are GUI configuration tool add-ons for Ice (tried one, once - didn't like it), but I prefer to get and compile the source and open up every configuration file in my text editor(s) and make my changes. So be aware that this takes a manual approach and may be filled with errors and silliness. I rely on anyone finding any to correct it, as that's a big strength of collaborative editing.<br />
<br />
==Install==<br />
<br />
===Download===<br />
<br />
Perhaps the best place to go to download is<br />
[http://sourceforge.net/projects/icewm/ Sourceforge] as the Ice page is a bit<br />
out of date and even [http://freshmeat.net/projects/icewm/ Freshmeat] offers 1.2.11 - though both link to CVS. The latest regular release (at the time of this writing) actually seems to be 1.2.14pre9.<br />
<br />
===Compile===<br />
<br />
<tt>tar xzf ice<tab><br><br />
cd ice<tab><br><br />
./configure --help</tt> [Check out your options; pick what you'd like - nothing special is really required.]<br><br />
<tt>./configure<br><br />
make<br><br />
su<br><br />
checkinstall</tt> [or 'make install' if you don't have checkinstall]<br><br />
<br />
==Configure==<br />
<br />
===Default Files===<br />
<br />
If you start bare, ~/.icewm/ and ~/.icewm/theme are generated, but see below for the 'startup' file and what can be pulled from the system-wide configs.<br />
<br />
If you installed to /usr/local, then /usr/local/share/icewm/ will contain<br />
something like the directories:<br />
<br />
icons<br><br />
ledclock<br><br />
mailbox<br><br />
taskbar<br><br />
themes<br><br />
<br />
and the files:<br />
<br />
keys<br><br />
menu<br><br />
preferences<br><br />
toolbar<br><br />
winoptions<br><br />
<br />
Copy over whatever you'd like to modify to ~/.icewm.<br />
<br />
For example, my ~/.icewm contains the directory<br />
<br />
themes<br />
<br />
(And I then renamed the system themes directory to 'not.themes' because I didn't feel like either deleting those themes - useful reference - or having them appear in my themes menu. I'm the only user on my system so I can do stuff like that. :) )<br />
<br />
and the files:<br />
<br />
keys<br><br />
menu<br><br />
preferences<br><br />
<nowiki>*</nowiki>prefoverride<br><br />
<nowiki>*</nowiki>startup<br><br />
<nowiki>*</nowiki>theme<br><br />
toolbar<br><br />
winoptions<br><br />
<br />
<nowiki>*</nowiki> These are not in the system-wide directory - the first two are created manually and the last is generated automatically.<br />
<br />
<br />
===Custom Files===<br />
<br />
====startup====<br />
<br />
'startup' is a file that can be used by ice but doesn't have to exist and isn't automatically created. It is read only if ice is invoked as 'icewm-session'.<br />
<br />
The ice documentation provides some suggestions and your startup method would<br />
vary upon your distro and configuration. For Slackware in runlevel 3 using<br />
'startx', for instance, I wanted a clean, simple startup. I have a poor man's<br />
replacement for xwmconfig and run that script to produce my ~/.xinitrc which is<br />
a symlink to ~/.xinit/xinitrc.ice which, other than the default file variables,<br />
says only:<br />
<br />
<tt># Declare what we're starting:<br><br />
export JWM=ice</tt> [not an ice thing - just a variable for use in some scripts]<br><br />
<tt># Start the window manager:<br><br />
exec icewm-session</tt><br />
<br />
and icewm-session reads ~/.icewm/startup which is only<br />
<br />
<tt>#!/bin/bash<br />
<br />
gkrellm --geometry +955+0 &<br><br />
aterm -name jterm &</tt><br />
<br />
Thus, as part of 'ps xo command' reports, this is what's started at invocation.<br />
<br />
<tt>/bin/sh /usr/X11R6/bin/startx -- -nolisten tcp<br><br />
xinit /home/j/.xinitrc -- /usr/X11R6/bin/X -nolisten tcp<br><br />
icewm-session<br><br />
icewmbg<br><br />
icewm --restart<br><br />
icewmtray<br><br />
gkrellm --geometry +955+0<br><br />
aterm -name jterm<br><br />
bash</tt><br />
<br />
(Well, except the '--restart' part, I think. Ice reads menu changes on the fly but other changes require a restart - oddly, even changing the path on the menu seems to result in ice trying to start the old one unless it's restarted.)<br />
<br />
This way, ice takes care of its own background and tray processes.<br />
<br />
====themes (directory)====<br />
<br />
This is where to untar any personal themes you add to ice. These themes can be used out of the box by selecting them from the menu (where they automatically appear) or they can be modified by editing the <i>name-of-theme</i>.theme file - and the pixmaps, too, if you have graphics talent.<br />
<br />
I initially tried an old version of ice and didn't like it. It was only recently, playing around with Gentoo, that I tried it again (pre7) and converted. But when I got back to Slack and tried to install it there (pre9), I had one particular problem, in that the themes' fonts didn't work. In my install, all themes contained things like:<br />
<br />
<tt>TitleFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
MenuFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
MinimizedWindowFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
ActiveButtonFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
NormalButtonFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
QuickSwitchFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
ListBoxFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
StatusFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
ToolTipFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
ActiveTaskBarFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
NormalTaskBarFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
ClockFontName = "-b&h-lucida-bold-r-normal-sans-14-*-*-*-*-*-*-*"<br><br />
ApmFontName = "-b&h-lucida-bold-r-normal-sans-14-*-*-*-*-*-*-*"</tt><br />
<br />
But only 'default' also contained<br />
<br />
<tt># Font Specification<br><br />
TitleFontNameXft = "Snap:size=10"<br><br />
MenuFontNameXft = "Snap:size=10"<br><br />
MinimizedWindowFontNameXft = "Snap:size=10"<br><br />
ActiveButtonFontNameXft = "Snap:size=10"<br><br />
NormalButtonFontNameXft = "Snap:size=10"<br><br />
QuickSwitchFontNameXft = "Snap:size=10"<br><br />
ListBoxFontNameXft = "Snap:size=10"<br><br />
StatusFontNameXft = "Snap:size=10"<br><br />
ToolTipFontNameXft = "Snap:size=10"<br><br />
ActiveTaskBarFontNameXft = "Snap:size=10"<br><br />
NormalTaskBarFontNameXft = "Snap:size=10"<br><br />
ClockFontNameXft = "lucida:size=14:bold"<br><br />
ApmFontNameXft = "lucida:size=14:bold"</tt><br />
<br />
Copying that last section to all theme files made the fonts work. (Or recompiling and changing a lot of settings and monkeying around generally did, but I think it was just that section.) In looking over the change file, I came across this:<br />
<br />
<tt>1.2.14pre8: 2003-01-11<br><br />
add Xft font specification for Infadel2 theme</tt><br />
<br />
and this:<br />
<br />
<tt>all font preferences now have a ...Xft variant<br><br />
that can be set to fontconfig pattern specification.<br><br />
example: MenuFontNameXft=sans-serif:size=12:bold</tt><br />
<br />
Something may have gotten confused between pre7,8,9.<br />
<br />
TODO: more on the theme file itself<br />
<br />
====menu====<br />
You can modify IceWM to your hearts content....use IceMC 'icemc" should be installed with K12LTSP. Disregard the first error message and navigate to<br />
/usr/share/icewm and edit the menu file.<br />
<br />
This governs the contents of the pop-up application launcher.<br />
<br />
The basic syntax is<br />
<br />
<i>entry-type menu-name menu-icon command-line</i><br><br />
or<br><br />
menufile <i>menu-name menu-icon menu-file</i><br />
<br />
For instance<br />
<br />
<tt>prog "ATerm 0.4.2" terminal3_16x16 aterm</tt><br />
<br />
'prog', 'menu', 'menufile', and 'separator' are the only types I know of. Quotes are optional unless there are spaces (or possibly other special marks) in a field. See 'preferences' about icons, icon paths, and naming conventions.<br />
<br />
Separators are created simply with<br />
<br />
<tt>separator</tt><br />
<br />
For subsections in your menu, there are two different approaches: 'menu' can<br />
basically have 'include' directives - for instance:<br />
<br />
<tt>menufile Programs folder programs</tt><br />
<br />
works like 'include programs' if you have a file called 'programs' with more<br />
entries in it. Another way is in the main menu file, but by declaring the type<br />
as 'menu' and surrounding the block with braces like so:<br />
<br />
<tt>menu "Editors" folder {<br><br />
prog "NEdit 5.4rc2" nedit /home/j/bin/nedit<br><br />
prog "GVim 6.2" gvim gvim<br><br />
}</tt><br />
<br />
(Ice seems to have trouble with tilde expansion in the menus, so I write out the full paths.)<br />
<br />
====toolbar====<br />
<br />
This governs the contents of the 'one-click' application section of the toolbar.<br />
<br />
According to ice logic, it's actually just another one of those submenu files<br />
that happens to show up on the toolbar as well. However, I removed it from the<br />
menu (pointless redundancy) and only have them appear on the toolbar -<br />
specifically in what Win98 (etc) would call the 'quicklaunch' area, and that's really what the file is - a definition of the apps that appear in that area - it doesn't configure the whole toolbar.<br />
<br />
====keys====<br />
<br />
This defines your keyboard accelerators.<br />
<br />
<br />
This section digresses a bit from ice in part, but relates and may be useful (or wrong and harmful - reader beware).<br />
<br />
If you have a special key that's not really doing anything, type [[xev]] and then <br />
hit the key you're interested in. Look for the keycode (such as 222) in the<br />
output. Look through /usr/X11R6/lib/X11/XKeysymDB especially, or maybe also<br />
/usr/include/X11/XF86keysym.h or /usr/include/X11/keysym.h or<br />
/usr/include/X11/keysymdef.h (or whatever - and /usr/include is a symlink to<br />
/usr/X11R6/include on my box) and find a keysym such as 'XF86PowerOff'. Now<br />
that you've pulled out xev and some files, pull out [[xmodmap]] and issue <br />
<br />
<tt>xmodmap -e "keycode 222 = XF86PowerOff"</tt><br />
<br />
(The quotes are vital to parse the lines correctly and the *precise* keysymname - I got confused because the files differ and I'd picked up XF86_PowerOff and XF86poweroff and so on from other files.) Then that key should be identified.<br />
<br />
If it works, you can add it to ~/.Xmodmap. Mine has<br />
<br />
<tt>keycode 117 = XF86MenuKB<br><br />
keycode 222 = XF86PowerOff<br><br />
keycode 223 = XF86Sleep<br><br />
keycode 227 = XF86WakeUp</tt><br />
<br />
Then, since you're doing this for ice, you can then edit the keys file to say <br />
<br />
<tt>key "XF86PowerOff" killall -QUIT icewm</tt><br />
<br />
and hitting that button will then perform that action.<br />
<br />
The following lines<br />
<br />
<tt>key "Alt+Ctrl+KP_Divide" aumix -v -5 # lower volume</tt><br><br />
<tt>key "Alt+Ctrl+KP_Multiply" aumix -v +5 # raise volume</tt><br />
<br />
were in the original file and didn't work for some reason. (Possibly a number lock issue, but I think I tried that.) And no variations I attempted with, say, rexima, worked either. But going through the above process and putting the following did and gave those keys, that I didn't use, something to do.<br />
<br />
<tt>key "XF86Sleep" aumix -v -5<br><br />
key "XF86WakeUp" aumix -v +5</tt><br />
<br />
Another example is<br />
<br />
<tt>key "Super+Print" /home/j/sbin/xgrabroot</tt><br />
<br />
This illustrates that your Mod4, Windows, AltAlt, Super, Whatever key is called 'Super' by ice and that things like the 'print screen' key can be incorporated.<br />
<br />
====winoptions====<br />
<br />
This tells ice specifically how to handle the windowing and other aspects of selected applications.<br />
<br />
<br />
Something useful for setting winoptions is to know what the windows are called.<br />
As something portable between GUIs, creating an executable file with<br />
<br />
<nowiki>#</nowiki><tt>!/bin/bash<br />
<br />
xprop | grep WM_CLASS | xmessage -file - -center</tt><br />
<br />
and adding the name of the file to the menu, rather than locking it directly in a menu or an often inaccessible bash alias is helpful. Then you can just click on the menu and then click on the app and get a report. Not all apps set this value, but they should. And some set transitory windows to the same value, which they shouldn't. But it is still usually useful.<br />
<br />
Specifying icons for the menu is handled in the menu file. To specify them<br />
elsewhere (title-bar-buttons, windowlist, system menu, systray, etc.), use<br />
winoptions. If the icon file is in ice's search path (defined in 'preferences')<br />
and is an xpm, just specifying the name will do. If it's a png or other format,<br />
specify <i>name</i>.png (or the image's extension, in other words). I believe ice requires imlib to handle anything other than xpm's. If it's not on the path, move it or specify the full path. Many applications specify their own icons, but those can be overridden. (A tip for snagging icons: some apps compile in an icon but place the independent file nowhere on the system. Poke around in the source code and it'll be there.)<br />
<br />
Ice can handle certain genuine 'systray-capable' apps such as gaim but it just takes a trio of lines to make a 'systray-like' app. Then it just takes another line to position the app and another to specify its icon. There are a host of other options, though. As an example, gkrellm:<br />
<br />
<tt>gkrellm.Gkrellm.icon: gkrellm<br><br />
gkrellm.Gkrellm.geometry: +956+0<br><br />
gkrellm.Gkrellm.tray: Exclusive<br><br />
gkrellm.Gkrellm.allWorkspaces: 1<br><br />
gkrellm.Gkrellm.ignoreQuickSwitch: 1</tt><br />
<br />
(I include a massive digression on [[Aterm in Ice]] but only as a separate page because it's really silly.)<br />
<br />
====preferences====<br />
<br />
The master file of ice's look and feel.<br />
<br />
I don't use a menu much but, when I do, setting 'MenuMouseTracking=1' is a huge<br />
plus. If you hate the application icon over your windowing buttons like I do,<br />
'ShowMenuButtonIcon=0' is the thing.<br />
<br />
TODO: make this a real section<br />
<br />
====prefoverride====<br />
<br />
AKA !important preferences.<br />
<br />
To generate a quick version of this file, maybe<br />
<br />
<tt>cat preferences | sed -e 's/^[ ]$//g' | grep -v '^$' | grep -v '^#' ><br />
prefoverride</tt><br />
<br />
would do. I did something similar but can't remember what. Be warned that the<br />
prefoverride file is for just that: overriding anything, such as a theme, that<br />
specifies something that would override 'preferences'. But if you didn't want<br />
those preferences, you wouldn't have changed the defaults in the first place,<br />
right? The order of priority is prefoverride, theme, preferences. So if something is vital to you, this is the place to make sure nothing messes with it. But if you don't wish to override a theme, don't include it here.<br />
<br />
====theme====<br />
<br />
Lastly, the 'theme' file is generated by ice for its internal use and specifies the theme in use and a history of past themes used.<br />
<br />
===Notes===<br />
<br />
I had a hideous time with inconsistent and unappealing fonts and my notes make<br />
no sense. I believe I ended up deleting the Infadel theme's icons and adding <br />
<br />
<nowiki>#</nowiki><tt> change to less obtrusive cursor images <br><br />
Xcursor.theme: whiteglass</tt><br />
<br />
to ~/.Xresources. Still not perfect, but better to me.<br />
<br />
At one time I substituted dillo for ice's documentation viewer because the viewer was almost unusable, but it has been much improved. The changelog notes:<br />
<br />
<tt> - improvements to icehelp</tt><br />
<br />
However, Ice wanted the help file to be in /usr/local/share/doc/icewm-1.2.14pre9/, yet didn't create it. Maybe I did something wrong. However, I had my old docs and ice's docs are mostly out of date anyhow :), so I su'ed and moved my old /usr/local/share/icewm/doc/<br />
directory to that location and access them as normal.</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Configuring_X&diff=16760Configuring X2004-09-02T00:17:56Z<p>DennisDaniels: =What? No graphics?=</p>
<hr />
<div>Configuration of the [[XFree86]] (commonly called just X) server is hopefully done automatically by your Linux distribution. If it fails at this or it just doesn't do it, you have the messy task of setting it up yourself. This often ends up being a great frustration for most users.<br />
<br />
== Various Tools That Make Things Easier ==<br />
There are many programs that automatically configure XFree86 for you. Your first stop should be the tool your distribution provides.<br />
<br />
You can also use the tools that come with XFree86:<br />
;'''xf86config''': A text-based tool that asks you a bunch of questions. Downside: rewrites your configuration on every use. If you messed it up, you need to have a backup copy of the XF86Config file around.<br />
;'''xf86cfg''': Starts a session of XFree86 with a minimal configuration so it you can configure graphically. If it doesn't work, you can use it's text-mode: 'xf86cfg --textmode'<br />
<!-- XFree86 ? --><br />
<br />
Some video card makers provide their own tools for you to use, and some distributions also provide their own tools - for example, Mandrake.<br />
<br />
== The XF86Config file ==<br />
<br />
This is what XFree86 reads upon startup, so that it knows what devices it needs to load drivers for. These devices typically include a mouse, a keyboard, one (or more) video cards, and one (or more) monitors. The mouse and keyboard are typically easy enough to configure, and newer XFree86 setups will commonly know what card is in the machine. However, older versions of XFree86 (3.x and earlier) needed to have specific details about the video card chipset put into the file.<br />
<br />
<br />
== Manual editing of XF86Config ==<br />
<br />
This should only be used if your previous attempts at using either xf86config or xf86cfg do not work.<br />
<br />
First, figure out what you're favorite (or least hated) [[cli]] text [[editor]] is.<br />
<br />
== Customizing your system ==<br />
<br />
<br />
<ol>Here are your options:<br />
<li>Use the tool your distribution provides <br />
<li>Use xf86config<br />
<li>Use xf86cfg<br />
<li>Edit the /etc/X11/XF86Config-4 file by hand.<br />
<li>Use a third party configuration tool, for example, if you use the ati-drivers, they come with an fglrxconfig tool that inserts special options for the ati cards.<br />
</ol><br />
<br />
NOTE: If you are using version 4.x chances are your file will be named XF86Config-4. This takes precedence over the old XF86Config file, which was used with XFree86-3.x.<br />
<br />
<br />
== Mouse configuration ==<br />
<br />
The mouse often is the most difficult to get working for new users. You'll want to verify you have a working mouse at /dev/mouse. If not, you need to create the link. The easiest way to find out, is just to type:<br />
cat /dev/mouse<br />
<br />
Now move your mouse around and you should have random characters fly up your screen. Press "Control-C" to quit.<br />
If you don't see strange characters, and you perhaps get back "no such file", then you need to tell your computer you actually have one. See [http://wiki.linuxquestions.org/wiki/Configuring_mice_(Serial%2C_PS/2%2C_USB) Configuring mice (Serial, PS/2, USB] for further help.<br />
Come back here when you need to continue.<br />
<br />
Within the configuration when asked for the protocol, most people will use PS/2, or IMPS/2 for usb mice.<br />
However, if you have an older serial mouse, then you perhaps need to choose "Microsoft" (the most common for two-button mice) or "MouseSystems" if you have a three-button mouse. You will find that if one doesn't work, then the other will. There may even be a switch on the mouse labeled "PC/MS" to select the protocol.<br />
<br />
Another option is to see if XFree86 discovers the correct protocol for itself - by putting in "auto". This works for really modern mice (the Explorer types, for example).<br />
<br />
A very common problem is getting the scroll wheel to work, if you have one. This is generally very easy to do.<br />
There will be a section labeled "InputDevice" that relates to the mouse. Within that section, add the line: <br />
<br />
<tt>Option "ZAxis Mapping" "4 5"</tt><br />
<br />
For older mice that only have two buttons, or do NOT have a clickable wheel (some scroll wheel mice), you may also select to turn on "Emulate3Buttons" by adding the following line:<br />
<br />
<tt>Option "Emulate3Buttons"</br><br />
Option "Emulate3Timeout" "50"</tt><br />
<br />
If you have a mouse with three buttons (or even more, perhaps) then you won't need these two lines. This also applies if your scroll wheel also clicks as well as rolling.<br />
<br />
== Keyboard ==<br />
<br />
There is support for many different keyboards - more commonly this will affect what keys do when you hit them. If you don't specify a change in the type of keyboard you have, XFree86 will assume that you are using a USA keyboard, and all your keys will react as if they are on a USA keyboard.<br />
<br />
Choosing a keyboard mapping that supports the closest country to yours will help you out when you want to enter non-US characters that you find typically in the French, Spanish, Russian, or perhaps even Greek keyboards.<br />
<br />
There are several HOWTO documents that cover "localising" your keyboard and setup, available at [http://www.tldp.org The Linuxdoc Project], and they're written either in English, or in the language of the country that they address.<br />
<br />
(This section needs to be expanded)<br />
<br />
== Video cards ==<br />
<br />
(Add a description of correct configuration of video driver selection)<br />
<br />
== Monitors ==<br />
<br />
(Add a description of selecting correct monitor devices)<br />
<br />
== Running XFree86 ==<br />
<br />
Once you have all your hardware details specified correctly, you are ready to test out XFree86. For most users, you will have to be the root user to do this step.<br />
You are probably at the root prompt already, so type "startx" and wait.<br />
<br />
After a few seconds, you ought to see a grey screen with a cross (X) in the middle. It is also possible that KDE may load after this, but we're not counting on that yet.<br />
If you get this grey screen, and it sits around, and the cross moves when you move the mouse, then congratulations. Your XFree86 works - but you may need to do a few minor tweaks with regard to resolution or whatever. Hit "Control-Alt-Backspace" together, you will then be put back to the console screen.All you need to do now is fire up KDE or GNOME (or some other window manager).<br />
<br />
If you end up with a KDE or GNOME screen, then choose "Logout" from the startup menu. Again, congratulations.<br />
You may need to tweak things like available resolutions, and bitdepths, but that is for further discussion in another section.<br />
<br />
== What? No graphics? ==<br />
<br />
If you GET something that looks more like text, and stays at your console, then you need to work out (from what XFree86 said) what section you need to alter.<br />
XFree86 also leaves a log file in /var/log/XFree86.0.log for you to look at, but this is a pretty long file to look at for people new to the process.<br />
<br />
(Needs to be filled in further)<br />
Common reasons for this include:<br />
<dl><br />
<dt>XFree86 couldn't figure out what your card was.</dt><br />
<dd>This is common when you have an older version of XFree and a really new video card. Examples of this can include having an Intel 845 graphics chipset, and not having a Intel 845 driver within your version of XFree86.<br />
This is a very specific example of a card that will not work (properly) with an Intel 830 driver).<br />
Mostly, upgrading either XFree86 itself, or the whole distribution itself will generally cure this. If you already HAVE the latest, then you have some work to do.</dd><br />
<dt>It found your card, but "no suitable screens were found"</dt><br />
<dd>This can happen if you didn't correctly specify what resolutions you wanted to make available. This can also include selecting correct bitdepths (8, 16, 24 or 32-bit resolutions). When you have a modern flat-panel display, it's even more important you get the available resolutions correct.</dd><br />
</dl><br />
<br />
TODO: We will probably need to break up sections of the X configuration process (now done) and organize it nicely. This is just a slightly less rough overview. Categories about video cards and screens need to be filled out, as well as the troubleshooting section.<br />
<br />
===screensaver===<br />
Typing xscreensaver at the prompt will launch a diaolog to edit your preferences. You can also go in manually; grep for xscreensaver, it'll be something like <tt>/usr/X11R6/lib/X11/app-defaults/XScreenSaver</tt><br />
<br />
==See also==<br />
*[[Using multiple monitors with XFree86]]<br />
*[[OpenGL]]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Terminal_Server&diff=20978Terminal Server2004-09-01T23:27:30Z<p>DennisDaniels: </p>
<hr />
<div>Terminal server allows many '[[dumb terminal|dumb]]' clients to log into a server. [[LTSP]] is a fine choice when reviewing terminal server applications.<br />
<br />
<br />
[[FreeNX]] offers a X windows session over a 40kb connection.</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Rdesktop&diff=23015Rdesktop2004-09-01T23:23:56Z<p>DennisDaniels: </p>
<hr />
<div>Quoting from the [[http://www.rdesktop.org/ rdesktop homepage]]:<br />
<br />
"'''rdesktop''' is an open source client for Windows NT Terminal Server and Windows 2000/2003 Terminal Services, capable of natively speaking Remote Desktop Protocol ([[RDP]]) in order to present the user's NT desktop. Unlike [[Citrix]] ICA, no server extensions are required."<br />
<br />
'''Using rdesktop:'''<br />
<br />
Type:<br />
rdesktop <[[IP]] of your terminal services server><br />
<br />
and you happily have a Windows session in an X window.<br />
<br />
Point the program to a box running Windows Terminal Services:<br />
<br />
<tt>$rdesktop 192.168.1.10</tt><br />
<br />
This starts rdesktop, opens up a terminal session on the machine indicated, and opens a Windows login screen where you can type your username and password for the Windows machine.<br />
<br />
----<br />
''This article is a [[LQWiki:stub_articles|stub]] and needs to be finished. [[LQWiki:plunging_forward|Plunge forward]] and [[LQWiki:How_to_edit_a_page|help it grow]] !''</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Rdesktop&diff=11406Rdesktop2004-09-01T23:20:04Z<p>DennisDaniels: tips</p>
<hr />
<div>Quoting from the [[http://www.rdesktop.org/ rdesktop homepage]]:<br />
<br />
"'''rdesktop''' is an open source client for Windows NT Terminal Server and Windows 2000/2003 Terminal Services, capable of natively speaking Remote Desktop Protocol ([[RDP]]) in order to present the user's NT desktop. Unlike [[Citrix]] ICA, no server extensions are required."<br />
<br />
'''Using rdesktop:'''<br />
<br />
Type:<br />
rdesktop <[[IP]] of your terminal services server><br />
<br />
and you happily have a Windows session in an X window.<br />
<br />
Point the program to a box running Windows Terminal Services:<br />
<tt>$ rdesktop 192.168.1.10</tt><br />
<br />
This starts rdesktop, opens up a terminal session on the machine indicated, and opens a Windows login screen where you can type your username and password for the Windows machine.<br />
<br />
----<br />
''This article is a [[LinuxQuestions.org_Wiki:stub_articles|stub]] and needs to be finished. [[LinuxQuestions.org_Wiki:plunging_forward|Plunge forward]] and [[LinuxQuestions.org_Wiki:How_to_edit_a_page|help it grow]] !''</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=GQview&diff=12829GQview2004-09-01T00:06:12Z<p>DennisDaniels: GQview a decent choice.</p>
<hr />
<div>'''GQview''' is a convenient, configurable [[image browser]] that runs well regardless of [[desktop environment]], though it does require [[GTK]] 2.2. It has rudimentary image file management capabilities, for example it is difficult to save changes to image orientation. Several interesting features such as a duplicate finder, and can call on an external editor such as [[Gimp|The GIMP]] makes GQview a decent choice.<br />
<br />
==External links==<br />
*[http://gqview.sourceforge.net/ GQview homepage]<br />
*[http://gqview.sourceforge.net/view-shot.html GQview screenshots]<br />
<br />
{{msg:stub}}</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Image_browser&diff=12340Image browser2004-09-01T00:04:36Z<p>DennisDaniels: =Specific applications= *Gimp runs on windows as well</p>
<hr />
<div>An '''image browser''' is a utility that can organize and view images quickly and efficiently. Usually they can also perform basic manipulation tasks such as resizing, cropping and re-colouring.<br />
<br />
Most Image Browsers allow good use of meta data to organize pictures and sort through them.<br />
<br />
==Specific applications==<br />
Some open source examples are:<br />
<br />
*[[Eye of GNOME]]<br />
*[[Gimp]] runs on windows as well<br />
*[[GQview]]<br />
*[[GThumb]]<br />
*[[imgSeek]]<br />
*[[KimDaBa]]<br />
*[[pixieplus]]<br />
*[[GLiv]]<br />
*[[Gwenview]]<br />
<br />
Some commercial examples include:<br />
<br />
* Apple's [http://www.apple.com/iphoto iPhoto]<br />
* ACD System's [http://www.acdsystems.com/English/Products/ACDSee/ ACDSee]<br />
* Adobe's [http://www.adobe.com/products/photoshopalbum/main.html Photoshop Album]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Gqview&diff=11389Gqview2004-09-01T00:03:31Z<p>DennisDaniels: delete this article</p>
<hr />
<div>delete this page; user error</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Gqview&diff=11381Gqview2004-09-01T00:02:17Z<p>DennisDaniels: place holder</p>
<hr />
<div>[https://sourceforge.net/projects/gqview/ gqview] is a nice little shoe box application.</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Rmutt&diff=11365Rmutt2004-08-30T18:38:50Z<p>DennisDaniels: </p>
<hr />
<div>rmutt is a fascinating tool that randomly generates text from user created files. http://www.schneertz.com/rmutt/<br />
<br />
The potential application in an education environment are enormous. There is some evidence to suggest text generators like rmutt are not responsible for much of the text in [[spam]].</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Applications&diff=12447Applications2004-08-30T18:36:03Z<p>DennisDaniels: =Education=</p>
<hr />
<div>Use the pages leading from this section to collect notes and information on common Linux software!<br />
Please read the [[LinuxQuestions.org Wiki:Do's and Dont's]] before editing this page.<br />
<br />
==Development==<br />
{| border=1<br />
! Development<br />
|-<br />
|<br />
*[[Compiler]]<br />
*[[Integrated Development Environment]]<br />
*[[Web development]]<br />
|-<br />
|}<br />
<br />
==Multimedia applications==<br />
{| border=1<br />
! Multimedia applications<br />
|-<br />
|<br />
* 3D Graphics<br />
** [[3D modeling]]<br />
* 2D Graphics<br />
** [[Image browser]]<br />
** [[Image manipulation]]<br />
* Audio<br />
** [[Music player]]<br />
** [[Sound server]]<br />
** [[Midi]]<br />
** [[Audio editor]]<br />
** [[Synthesis]]<br />
* Video<br />
** [[Video capture]]<br />
** [[Video editor]]<br />
** [[Video player]]<br />
|-<br />
|}<br />
<br />
==Networking==<br />
{| border=1<br />
! Networking<br />
|-<br />
|<br />
* Client<br />
** [[Email client]]<br />
** [[Instant Messaging]]<br />
** [[Internet Relay Chat]]<br />
** [[Web browser]]<br />
<br />
*Server<br />
** [[Web Server]]<br />
** [[Mail Server]]<br />
** [[FTP Server]]<br />
** [[Proxy Server]]<br />
** [[Terminal Server]]<br />
<br />
*Peer to peer<br />
** [[File sharing]]<br />
|-<br />
|}<br />
<br />
==Office and Productivity==<br />
{| border=1<br />
! Office and Productivity<br />
|-<br />
|<br />
* [[Citation Management]]<br />
* [[Database]]<br />
* [[Database tools]]<br />
* [[Editor|Text Editor]]<br />
* [[Office suite]]<br />
* [[Personal Information Management]]<br />
* [[Spreadsheet]]<br />
* [[Text processing]]<br />
* [[Word processor]]<br />
* [[Presentation]]<br />
|-<br />
|}<br />
<br />
==Education==<br />
{| border=1<br />
! Education<br />
|-<br />
|<br />
*Quizzing<br />
** [[keduca]]<br />
*Typing<br />
** [[tuxtype]]<br />
** [[ktouch]]<br />
*Writing<br />
** [[diction]]<br />
** [[style]]<br />
** [[rmutt]]<br />
|-<br />
|}<br />
<br />
==Utilities==<br />
{| border=1<br />
! Utilities<br />
|-<br />
|<br />
* [[Backup]]<br />
* [[CD/DVD Burning]]<br />
* [[File manager]]<br />
* [[Installing Software]]<br />
* [[Security]]<br />
* [[System configuration]]<br />
* [[System Statistics]]<br />
* [[Terminal emulator]]<br />
|-<br />
|}<br />
<br />
==Miscellaneous==<br />
{| border=1<br />
! Miscellaneous<br />
|-<br />
|<br />
* [[Emulation]]<br />
* [[PVR]]<br />
* [[Scientific applications]]<br />
* [[Silly applications]]<br />
* [[Useful Sites]]<br />
|-<br />
|}<br />
<br />
==X (GUI)==<br />
{| border=1<br />
! X (GUI)<br />
|-<br />
|<br />
* [[Desktop environment]]s<br />
* [[Window manager]]s<br />
* [[X utilities]]<br />
<br />
* '''[[X Window System]]'''<br />
**[[General Tips]]<br />
**[[Programming in X]] <!--Formatted like this a subsections rather--><br />
**[[Configuring X|Configuring]] <!--app list, so should look different --><br />
**[[Screenshots]]<br />
**[[Remote desktop connection]]<br />
|-<br />
|}<br />
<br />
==Linux/Windows equivalent software==<br />
{| border=1<br />
! Linux/Windows equivalent software<br />
|-<br />
|<br />
* [[Linux software equivalent to Windows software]]<br />
|-<br />
|}<br />
<br />
==See also==<br />
*[[Useful Sites]]<br />
*[[A useable example desktop|An example desktop's program listing for Debian Sarge]]</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Talk:Cron&diff=24768Talk:Cron2004-08-25T04:01:16Z<p>DennisDaniels: </p>
<hr />
<div>more examples for sys admins</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Talk:Ps&diff=11321Talk:Ps2004-08-25T03:52:10Z<p>DennisDaniels: </p>
<hr />
<div>How do I kill all processes owned by a user or group? I've noticed that after logout some users are still showing as active on the network.</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Userdel&diff=24766Userdel2004-08-25T03:50:58Z<p>DennisDaniels: </p>
<hr />
<div>To delete a user try<br />
<tt>userdel ''username''</tt></div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=IceWM&diff=11346IceWM2004-08-25T03:23:08Z<p>DennisDaniels: =keys= xev</p>
<hr />
<div>==General==<br />
<br />
[http://www.icewm.org/ IceWM] is a fast, lightweight window manager capable of emulating the look and feel of many other GUIs or of attaining a look all its own.<br />
<br />
Ice provides a toolbar with an application menu, region of application buttons, window buttons, system tray area, system monitors, and clock. It is similar to the Windows/KDE/Gnome/etc toolbars. Conversely, the entire menu or parts of it may be disabled. It provides sophisticated windowing controls, a host of right click menus (including a desktop menu identical to the toolbar's menu) and several ways to manage multiple windows and desktops. And all in a handful of executables and a few plain-text configuration files.<br />
<br />
Eye candy is not the primary focus, but it can be 'prettier' than some give it credit for. More important than that, it is very usable, configurable, and stable.<br />
<br />
==Disclaimer==<br />
<br />
I (the initial author) use Slackware and do everything the 'hard' way and am not very good at it. One could emerge or apt-get ice or at least install a package, and there are GUI configuration tool add-ons for Ice (tried one, once - didn't like it), but I prefer to get and compile the source and open up every configuration file in my text editor(s) and make my changes. So be aware that this takes a manual approach and may be filled with errors and silliness. I rely on anyone finding any to correct it, as that's a big strength of collaborative editing.<br />
<br />
==Install==<br />
<br />
===Download===<br />
<br />
Perhaps the best place to go to download is<br />
[http://sourceforge.net/projects/icewm/ Sourceforge] as the Ice page is a bit<br />
out of date and even [http://freshmeat.net/projects/icewm/ Freshmeat] offers 1.2.11 - though both link to CVS. The latest regular release (at the time of this writing) actually seems to be 1.2.14pre9.<br />
<br />
===Compile===<br />
<br />
<tt>tar xzf ice<tab><br><br />
cd ice<tab><br><br />
./configure --help</tt> [Check out your options; pick what you'd like - nothing special is really required.]<br><br />
<tt>./configure<br><br />
make<br><br />
su<br><br />
checkinstall</tt> [or 'make install' if you don't have checkinstall]<br><br />
<br />
==Configure==<br />
<br />
===Default Files===<br />
<br />
If you start bare, ~/.icewm/ and ~/.icewm/theme are generated, but see below for the 'startup' file and what can be pulled from the system-wide configs.<br />
<br />
If you installed to /usr/local, then /usr/local/share/icewm/ will contain<br />
something like the directories:<br />
<br />
icons<br><br />
ledclock<br><br />
mailbox<br><br />
taskbar<br><br />
themes<br><br />
<br />
and the files:<br />
<br />
keys<br><br />
menu<br><br />
preferences<br><br />
toolbar<br><br />
winoptions<br><br />
<br />
Copy over whatever you'd like to modify to ~/.icewm.<br />
<br />
For example, my ~/.icewm contains the directory<br />
<br />
themes<br />
<br />
(And I then renamed the system themes directory to 'not.themes' because I didn't feel like either deleting those themes - useful reference - or having them appear in my themes menu. I'm the only user on my system so I can do stuff like that. :) )<br />
<br />
and the files:<br />
<br />
keys<br><br />
menu<br><br />
preferences<br><br />
<nowiki>*</nowiki>prefoverride<br><br />
<nowiki>*</nowiki>startup<br><br />
<nowiki>*</nowiki>theme<br><br />
toolbar<br><br />
winoptions<br><br />
<br />
<nowiki>*</nowiki> These are not in the system-wide directory - the first two are created manually and the last is generated automatically.<br />
<br />
<br />
===Custom Files===<br />
<br />
====startup====<br />
<br />
'startup' is a file that can be used by ice but doesn't have to exist and isn't automatically created. It is read only if ice is invoked as 'icewm-session'.<br />
<br />
The ice documentation provides some suggestions and your startup method would<br />
vary upon your distro and configuration. For Slackware in runlevel 3 using<br />
'startx', for instance, I wanted a clean, simple startup. I have a poor man's<br />
replacement for xwmconfig and run that script to produce my ~/.xinitrc which is<br />
a symlink to ~/.xinit/xinitrc.ice which, other than the default file variables,<br />
says only:<br />
<br />
<tt># Declare what we're starting:<br><br />
export JWM=ice</tt> [not an ice thing - just a variable for use in some scripts]<br><br />
<tt># Start the window manager:<br><br />
exec icewm-session</tt><br />
<br />
and icewm-session reads ~/.icewm/startup which is only<br />
<br />
<tt>#!/bin/bash<br />
<br />
gkrellm --geometry +955+0 &<br><br />
aterm -name jterm &</tt><br />
<br />
Thus, as part of 'ps xo command' reports, this is what's started at invocation.<br />
<br />
<tt>/bin/sh /usr/X11R6/bin/startx -- -nolisten tcp<br><br />
xinit /home/j/.xinitrc -- /usr/X11R6/bin/X -nolisten tcp<br><br />
icewm-session<br><br />
icewmbg<br><br />
icewm --restart<br><br />
icewmtray<br><br />
gkrellm --geometry +955+0<br><br />
aterm -name jterm<br><br />
bash</tt><br />
<br />
(Well, except the '--restart' part, I think. Ice reads menu changes on the fly but other changes require a restart - oddly, even changing the path on the menu seems to result in ice trying to start the old one unless it's restarted.)<br />
<br />
This way, ice takes care of its own background and tray processes.<br />
<br />
====themes (directory)====<br />
<br />
This is where to untar any personal themes you add to ice. These themes can be used out of the box by selecting them from the menu (where they automatically appear) or they can be modified by editing the <i>name-of-theme</i>.theme file - and the pixmaps, too, if you have graphics talent.<br />
<br />
I initially tried an old version of ice and didn't like it. It was only recently, playing around with Gentoo, that I tried it again (pre7) and converted. But when I got back to Slack and tried to install it there (pre9), I had one particular problem, in that the themes' fonts didn't work. In my install, all themes contained things like:<br />
<br />
<tt>TitleFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
MenuFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
MinimizedWindowFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
ActiveButtonFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
NormalButtonFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
QuickSwitchFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
ListBoxFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
StatusFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
ToolTipFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
ActiveTaskBarFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
NormalTaskBarFontName = "-artwiz-snap-regular-r-normal-sans-10-*-*-*-*-*-*-*"<br><br />
ClockFontName = "-b&h-lucida-bold-r-normal-sans-14-*-*-*-*-*-*-*"<br><br />
ApmFontName = "-b&h-lucida-bold-r-normal-sans-14-*-*-*-*-*-*-*"</tt><br />
<br />
But only 'default' also contained<br />
<br />
<tt># Font Specification<br><br />
TitleFontNameXft = "Snap:size=10"<br><br />
MenuFontNameXft = "Snap:size=10"<br><br />
MinimizedWindowFontNameXft = "Snap:size=10"<br><br />
ActiveButtonFontNameXft = "Snap:size=10"<br><br />
NormalButtonFontNameXft = "Snap:size=10"<br><br />
QuickSwitchFontNameXft = "Snap:size=10"<br><br />
ListBoxFontNameXft = "Snap:size=10"<br><br />
StatusFontNameXft = "Snap:size=10"<br><br />
ToolTipFontNameXft = "Snap:size=10"<br><br />
ActiveTaskBarFontNameXft = "Snap:size=10"<br><br />
NormalTaskBarFontNameXft = "Snap:size=10"<br><br />
ClockFontNameXft = "lucida:size=14:bold"<br><br />
ApmFontNameXft = "lucida:size=14:bold"</tt><br />
<br />
Copying that last section to all theme files made the fonts work. (Or recompiling and changing a lot of settings and monkeying around generally did, but I think it was just that section.) In looking over the change file, I came across this:<br />
<br />
<tt>1.2.14pre8: 2003-01-11<br><br />
add Xft font specification for Infadel2 theme</tt><br />
<br />
and this:<br />
<br />
<tt>all font preferences now have a ...Xft variant<br><br />
that can be set to fontconfig pattern specification.<br><br />
example: MenuFontNameXft=sans-serif:size=12:bold</tt><br />
<br />
Something may have gotten confused between pre7,8,9.<br />
<br />
TODO: more on the theme file itself<br />
<br />
====menu====<br />
<br />
This governs the contents of the pop-up application launcher.<br />
<br />
The basic syntax is<br />
<br />
<i>entry-type menu-name menu-icon command-line</i><br><br />
or<br><br />
menufile <i>menu-name menu-icon menu-file</i><br />
<br />
For instance<br />
<br />
<tt>prog "ATerm 0.4.2" terminal3_16x16 aterm</tt><br />
<br />
'prog', 'menu', 'menufile', and 'separator' are the only types I know of. Quotes are optional unless there are spaces (or possibly other special marks) in a field. See 'preferences' about icons, icon paths, and naming conventions.<br />
<br />
Separators are created simply with<br />
<br />
<tt>separator</tt><br />
<br />
For subsections in your menu, there are two different approaches: 'menu' can<br />
basically have 'include' directives - for instance:<br />
<br />
<tt>menufile Programs folder programs</tt><br />
<br />
works like 'include programs' if you have a file called 'programs' with more<br />
entries in it. Another way is in the main menu file, but by declaring the type<br />
as 'menu' and surrounding the block with braces like so:<br />
<br />
<tt>menu "Editors" folder {<br><br />
prog "NEdit 5.4rc2" nedit /home/j/bin/nedit<br><br />
prog "GVim 6.2" gvim gvim<br><br />
}</tt><br />
<br />
(Ice seems to have trouble with tilde expansion in the menus, so I write out the full paths.)<br />
<br />
====toolbar====<br />
<br />
This governs the contents of the 'one-click' application section of the toolbar.<br />
<br />
According to ice logic, it's actually just another one of those submenu files<br />
that happens to show up on the toolbar as well. However, I removed it from the<br />
menu (pointless redundancy) and only have them appear on the toolbar -<br />
specifically in what Win98 (etc) would call the 'quicklaunch' area, and that's really what the file is - a definition of the apps that appear in that area - it doesn't configure the whole toolbar.<br />
<br />
====keys====<br />
<br />
This defines your keyboard accelerators.<br />
<br />
<br />
This section digresses a bit from ice in part, but relates and may be useful (or wrong and harmful - reader beware).<br />
<br />
If you have a special key that's not really doing anything, type [[xev]] and then <br />
hit the key you're interested in. Look for the keycode (such as 222) in the<br />
output. Look through /usr/X11R6/lib/X11/XKeysymDB especially, or maybe also<br />
/usr/include/X11/XF86keysym.h or /usr/include/X11/keysym.h or<br />
/usr/include/X11/keysymdef.h (or whatever - and /usr/include is a symlink to<br />
/usr/X11R6/include on my box) and find a keysym such as 'XF86PowerOff'. Now<br />
that you've pulled out xev and some files, pull out [[xmodmap]] and issue <br />
<br />
<tt>xmodmap -e "keycode 222 = XF86PowerOff"</tt><br />
<br />
(The quotes are vital to parse the lines correctly and the *precise* keysymname - I got confused because the files differ and I'd picked up XF86_PowerOff and XF86poweroff and so on from other files.) Then that key should be identified.<br />
<br />
If it works, you can add it to ~/.Xmodmap. Mine has<br />
<br />
<tt>keycode 117 = XF86MenuKB<br><br />
keycode 222 = XF86PowerOff<br><br />
keycode 223 = XF86Sleep<br><br />
keycode 227 = XF86WakeUp</tt><br />
<br />
Then, since you're doing this for ice, you can then edit the keys file to say <br />
<br />
<tt>key "XF86PowerOff" killall -QUIT icewm</tt><br />
<br />
and hitting that button will then perform that action.<br />
<br />
The following lines<br />
<br />
<tt>key "Alt+Ctrl+KP_Divide" aumix -v -5 # lower volume</tt><br><br />
<tt>key "Alt+Ctrl+KP_Multiply" aumix -v +5 # raise volume</tt><br />
<br />
were in the original file and didn't work for some reason. (Possibly a number lock issue, but I think I tried that.) And no variations I attempted with, say, rexima, worked either. But going through the above process and putting the following did and gave those keys, that I didn't use, something to do.<br />
<br />
<tt>key "XF86Sleep" aumix -v -5<br><br />
key "XF86WakeUp" aumix -v +5</tt><br />
<br />
Another example is<br />
<br />
<tt>key "Super+Print" /home/j/sbin/xgrabroot</tt><br />
<br />
This illustrates that your Mod4, Windows, AltAlt, Super, Whatever key is called 'Super' by ice and that things like the 'print screen' key can be incorporated.<br />
<br />
====winoptions====<br />
<br />
This tells ice specifically how to handle the windowing and other aspects of selected applications.<br />
<br />
<br />
Something useful for setting winoptions is to know what the windows are called.<br />
As something portable between GUIs, creating an executable file with<br />
<br />
<nowiki>#</nowiki><tt>!/bin/bash<br />
<br />
xprop | grep WM_CLASS | xmessage -file - -center</tt><br />
<br />
and adding the name of the file to the menu, rather than locking it directly in a menu or an often inaccessible bash alias is helpful. Then you can just click on the menu and then click on the app and get a report. Not all apps set this value, but they should. And some set transitory windows to the same value, which they shouldn't. But it is still usually useful.<br />
<br />
Specifying icons for the menu is handled in the menu file. To specify them<br />
elsewhere (title-bar-buttons, windowlist, system menu, systray, etc.), use<br />
winoptions. If the icon file is in ice's search path (defined in 'preferences')<br />
and is an xpm, just specifying the name will do. If it's a png or other format,<br />
specify <i>name</i>.png (or the image's extension, in other words). I believe ice requires imlib to handle anything other than xpm's. If it's not on the path, move it or specify the full path. Many applications specify their own icons, but those can be overridden. (A tip for snagging icons: some apps compile in an icon but place the independent file nowhere on the system. Poke around in the source code and it'll be there.)<br />
<br />
Ice can handle certain genuine 'systray-capable' apps such as gaim but it just takes a trio of lines to make a 'systray-like' app. Then it just takes another line to position the app and another to specify its icon. There are a host of other options, though. As an example, gkrellm:<br />
<br />
<tt>gkrellm.Gkrellm.icon: gkrellm<br><br />
gkrellm.Gkrellm.geometry: +956+0<br><br />
gkrellm.Gkrellm.tray: Exclusive<br><br />
gkrellm.Gkrellm.allWorkspaces: 1<br><br />
gkrellm.Gkrellm.ignoreQuickSwitch: 1</tt><br />
<br />
(I include a massive digression on [[Aterm in Ice]] but only as a separate page because it's really silly.)<br />
<br />
====preferences====<br />
<br />
The master file of ice's look and feel.<br />
<br />
I don't use a menu much but, when I do, setting 'MenuMouseTracking=1' is a huge<br />
plus. If you hate the application icon over your windowing buttons like I do,<br />
'ShowMenuButtonIcon=0' is the thing.<br />
<br />
TODO: make this a real section<br />
<br />
====prefoverride====<br />
<br />
AKA !important preferences.<br />
<br />
To generate a quick version of this file, maybe<br />
<br />
<tt>cat preferences | sed -e 's/^[ ]$//g' | grep -v '^$' | grep -v '^#' ><br />
prefoverride</tt><br />
<br />
would do. I did something similar but can't remember what. Be warned that the<br />
prefoverride file is for just that: overriding anything, such as a theme, that<br />
specifies something that would override 'preferences'. But if you didn't want<br />
those preferences, you wouldn't have changed the defaults in the first place,<br />
right? The order of priority is prefoverride, theme, preferences. So if something is vital to you, this is the place to make sure nothing messes with it. But if you don't wish to override a theme, don't include it here.<br />
<br />
====theme====<br />
<br />
Lastly, the 'theme' file is generated by ice for its internal use and specifies the theme in use and a history of past themes used.<br />
<br />
===Notes===<br />
<br />
I had a hideous time with inconsistent and unappealing fonts and my notes make<br />
no sense. I believe I ended up deleting the Infadel theme's icons and adding <br />
<br />
<nowiki>#</nowiki><tt> change to less obtrusive cursor images <br><br />
Xcursor.theme: whiteglass</tt><br />
<br />
to ~/.Xresources. Still not perfect, but better to me.<br />
<br />
At one time I substituted dillo for ice's documentation viewer because the viewer was almost unusable, but it has been much improved. The changelog notes:<br />
<br />
<tt> - improvements to icehelp</tt><br />
<br />
However, Ice wanted the help file to be in /usr/local/share/doc/icewm-1.2.14pre9/, yet didn't create it. Maybe I did something wrong. However, I had my old docs and ice's docs are mostly out of date anyhow :), so I su'ed and moved my old /usr/local/share/icewm/doc/<br />
directory to that location and access them as normal.</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Xvidcap&diff=22124Xvidcap2004-08-25T03:01:15Z<p>DennisDaniels: =cons=</p>
<hr />
<div><br />
* [http://sourceforge.net/projects/xvidcap/ xvidcap]: a great way to create documentation<br />
===Why?===<br />
<br />
*free video AND audio capture tool for Linux... need to communicate difficult interface ideas or problems to a developer? Notes and documentation are nice but it will make your life easier to send a video of what you want to your developer. <br />
<br />
===Video of a computer interface===<br />
It's been around for a while too:<br />
**camtasia<br />
**lotus screencam<br />
**and that old video cap tool that MS had out for awhile and now defunct<br />
<br />
===Linux apps related vaguely to xvidcap===<br />
*gnomemeeting<br />
*VNC<br />
<br />
*Video capture is the dummies way to document stuff... why write it when you can record it? (Few read anymore anyway, spoon fed is the preference for most (:sad:) )<br />
see some of my movies here:<br />
[training and bug vids http://dgd.mose.fr/?M=D]<br />
* http://sourceforge.net/projects/xvidcap/<br />
*Running rh9/ kde2 (digging KDE over Gnome in a big way, especially with the easy and beauty of kb3!)<br />
**localhost:~$ :rpm --nodeps -ivh xvidcap-1.1.xxxx.rpm <br />
<br />
Xvidcap is beta but useful ... figuring out what it does well first is my goal<br />
<br />
===Before===<br />
Set your video display to something small and manageable... I did my first screen grab at 1000s of colors, 1028 X 960 (?) and each frame was 1.2 meg! 240 frames and my machine<br />
800 MgHz AMD/ 1 GIG Ram / RH9 choked on trying to make that set into a movie.<br />
<br />
===install and running===<br />
1.1.3 is a snap. <br />
rpm -ivh xvidcapxxxx.rpm<br />
<br />
After installng, at the prompt type:<br />
$xvidcap<br />
<br />
I checked the options file $HOME/.xvidcap.scf and I set it to mpeg4.<br />
<br />
saving as mpeg4<br />
===.xvidcap.scf===<br />
<pre><br />
<br />
#SCFF<br />
# xvidcap configuration file<br />
<br />
# frames per second<br />
fps: 5.000000<br />
<br />
# file pattern<br />
file: capture-01.mpeg<br />
<br />
# max frames <br />
max_frames: 0<br />
<br />
# max time <br />
max_time: 0.000000<br />
<br />
# quality (JPEG)<br />
quality: 15<br />
<br />
# compression (PNG, GZIP)<br />
compression: 0 <br />
<br />
# use shared memory<br />
shm: 16<br />
<br />
# video codec used by ffmpeg<br />
codec: MPEG4<br />
<br />
# what kind of mouse pointer should be recorded?<br />
# 0 = none, 1 = white, 2 = black<br />
mouse_wanted: 2<br />
<br />
# toggle audio capture (0/1)<br />
audio: 1<br />
<br />
# device to grab audio from<br />
audio_in: /dev/dsp<br />
<br />
# sample rate for audio capture<br />
audio_rate: 22050<br />
<br />
# bit rate for audio capture<br />
audio_bits: 32000<br />
<br />
# number of channels to use in audio capture<br />
audio_channels: 1<br />
</pre><br />
<br />
===playback===<br />
I'm using [http://xinehq.de/xine] for movie playback.<br />
<br />
<br />
File format .xwd<br />
*xvidcap can save a series of screen grabs XXX.xwd files, they are numbered sequentially<br />
**localhost:~$ :echo this was used for getting rid of all the spare xwd files created by xvidcap<br />
***this was used for getting rid of all the spare xwd files created by xvidcap <pre>find . -name "frm*.xwd" -exec rm -f {} \;~/pp~ </pre><br />
<br />
***I echo operations back so that when I go back through the history I'll have clues as to what I did.<br />
<br />
<br />
===Pros===<br />
*audio recording<br />
*clicking on the target icon will record the entire screen<br />
<br />
===cons===<br />
*the gui control interface is touchy at best, I do all config in the .scf file<br />
*maximizing target recording area hides GUI toolbar. The only way to get GUI visible is to reset capture screen to something smaller...<br />
*The arrow key on the GUI advances the XXX.xwd but apparently is not acting as a manual screen grab tool <br />
**If an audio controller interface and the arrow key did in fact function as an incremental screen grabber xvidcap may be very useful for doing 'stop motion' videos of the linux interface with voice overs<br />
*doesn't prompt user for location of save screen grabs<br />
*no project folder prompt<br />
*GUI is not very opaque in its usage<br />
*movie playback happens in imagemagick though there is supposedly a way to do the playback as an mpeg4 file<br />
<br />
<br />
===Wishes===<br />
*audio controller on toolbar<br />
*frame rate controller on toolbar<br />
*make video interface to specific output format<br />
*swf output<br />
<br />
===Note===<br />
* Another alternative is gvidcap. If there are problems with crashing, it may be due to a clash in png libraries. Making from source resolves this error and allows gvidcap to run without crashing. The gvidcap client provides an interface a lot more convenient to setting preferences. The animate command is strictly for animating a sequence of images and will not work with mpegs. Use your usual video player (videolan/[[mplayer]]) for this.</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Xvidcap&diff=11303Xvidcap2004-08-25T03:00:31Z<p>DennisDaniels: =install and running=</p>
<hr />
<div><br />
* [http://sourceforge.net/projects/xvidcap/ xvidcap]: a great way to create documentation<br />
===Why?===<br />
<br />
*free video AND audio capture tool for Linux... need to communicate difficult interface ideas or problems to a developer? Notes and documentation are nice but it will make your life easier to send a video of what you want to your developer. <br />
<br />
===Video of a computer interface===<br />
It's been around for a while too:<br />
**camtasia<br />
**lotus screencam<br />
**and that old video cap tool that MS had out for awhile and now defunct<br />
<br />
===Linux apps related vaguely to xvidcap===<br />
*gnomemeeting<br />
*VNC<br />
<br />
*Video capture is the dummies way to document stuff... why write it when you can record it? (Few read anymore anyway, spoon fed is the preference for most (:sad:) )<br />
see some of my movies here:<br />
[training and bug vids http://dgd.mose.fr/?M=D]<br />
* http://sourceforge.net/projects/xvidcap/<br />
*Running rh9/ kde2 (digging KDE over Gnome in a big way, especially with the easy and beauty of kb3!)<br />
**localhost:~$ :rpm --nodeps -ivh xvidcap-1.1.xxxx.rpm <br />
<br />
Xvidcap is beta but useful ... figuring out what it does well first is my goal<br />
<br />
===Before===<br />
Set your video display to something small and manageable... I did my first screen grab at 1000s of colors, 1028 X 960 (?) and each frame was 1.2 meg! 240 frames and my machine<br />
800 MgHz AMD/ 1 GIG Ram / RH9 choked on trying to make that set into a movie.<br />
<br />
===install and running===<br />
1.1.3 is a snap. <br />
rpm -ivh xvidcapxxxx.rpm<br />
<br />
After installng, at the prompt type:<br />
$xvidcap<br />
<br />
I checked the options file $HOME/.xvidcap.scf and I set it to mpeg4.<br />
<br />
saving as mpeg4<br />
===.xvidcap.scf===<br />
<pre><br />
<br />
#SCFF<br />
# xvidcap configuration file<br />
<br />
# frames per second<br />
fps: 5.000000<br />
<br />
# file pattern<br />
file: capture-01.mpeg<br />
<br />
# max frames <br />
max_frames: 0<br />
<br />
# max time <br />
max_time: 0.000000<br />
<br />
# quality (JPEG)<br />
quality: 15<br />
<br />
# compression (PNG, GZIP)<br />
compression: 0 <br />
<br />
# use shared memory<br />
shm: 16<br />
<br />
# video codec used by ffmpeg<br />
codec: MPEG4<br />
<br />
# what kind of mouse pointer should be recorded?<br />
# 0 = none, 1 = white, 2 = black<br />
mouse_wanted: 2<br />
<br />
# toggle audio capture (0/1)<br />
audio: 1<br />
<br />
# device to grab audio from<br />
audio_in: /dev/dsp<br />
<br />
# sample rate for audio capture<br />
audio_rate: 22050<br />
<br />
# bit rate for audio capture<br />
audio_bits: 32000<br />
<br />
# number of channels to use in audio capture<br />
audio_channels: 1<br />
</pre><br />
<br />
===playback===<br />
I'm using [http://xinehq.de/xine] for movie playback.<br />
<br />
<br />
File format .xwd<br />
*xvidcap can save a series of screen grabs XXX.xwd files, they are numbered sequentially<br />
**localhost:~$ :echo this was used for getting rid of all the spare xwd files created by xvidcap<br />
***this was used for getting rid of all the spare xwd files created by xvidcap <pre>find . -name "frm*.xwd" -exec rm -f {} \;~/pp~ </pre><br />
<br />
***I echo operations back so that when I go back through the history I'll have clues as to what I did.<br />
<br />
<br />
===Pros===<br />
*audio recording<br />
*clicking on the target icon will record the entire screen<br />
<br />
===cons===<br />
*the gui control interface is touchy at best, I do all config in the .scf file<br />
*maximizing target recording area hides GUI toolbar. The only way to get GUI visible is to reset capture screen to something smaller...<br />
*The arrow key on the GUI advances the XXX.xwd but apparently is not acting as a manual screen grab tool <br />
**If an audio controller interface and the arrow key did in fact function as an incremental screen grabber xvidcap may be very useful for doing 'stop motion' videos of the linux interface with voice overs<br />
*doesn't prompt user for location of save screen grabs<br />
*no project folder prompt<br />
*GUI is not very opaque in its usage<br />
*movie playback happens in imagemagick though there is supposedly a way to do the playback as an mpeg4 file<br />
<br />
<br />
Wishes<br />
*audio controller on toolbar<br />
*frame rate controller on toolbar<br />
*make video interface to specific output format<br />
*swf output<br />
<br />
Note<br />
* Another alternative is gvidcap. If there are problems with crashing, it may be due to a clash in png libraries. Making from source resolves this error and allows gvidcap to run without crashing. The gvidcap client provides an interface a lot more convenient to setting preferences. The animate command is strictly for animating a sequence of images and will not work with mpegs. Use your usual video player (videolan/mplayer) for this.</div>DennisDanielshttps://wiki.linuxquestions.org/index.php?title=Xvidcap&diff=11302Xvidcap2004-08-25T02:58:55Z<p>DennisDaniels: </p>
<hr />
<div><br />
* [http://sourceforge.net/projects/xvidcap/ xvidcap]: a great way to create documentation<br />
===Why?===<br />
<br />
*free video AND audio capture tool for Linux... need to communicate difficult interface ideas or problems to a developer? Notes and documentation are nice but it will make your life easier to send a video of what you want to your developer. <br />
<br />
===Video of a computer interface===<br />
It's been around for a while too:<br />
**camtasia<br />
**lotus screencam<br />
**and that old video cap tool that MS had out for awhile and now defunct<br />
<br />
===Linux apps related vaguely to xvidcap===<br />
*gnomemeeting<br />
*VNC<br />
<br />
*Video capture is the dummies way to document stuff... why write it when you can record it? (Few read anymore anyway, spoon fed is the preference for most (:sad:) )<br />
see some of my movies here:<br />
[training and bug vids http://dgd.mose.fr/?M=D]<br />
* http://sourceforge.net/projects/xvidcap/<br />
*Running rh9/ kde2 (digging KDE over Gnome in a big way, especially with the easy and beauty of kb3!)<br />
**localhost:~$ :rpm --nodeps -ivh xvidcap-1.1.xxxx.rpm <br />
<br />
Xvidcap is beta but useful ... figuring out what it does well first is my goal<br />
<br />
===Before===<br />
Set your video display to something small and manageable... I did my first screen grab at 1000s of colors, 1028 X 960 (?) and each frame was 1.2 meg! 240 frames and my machine<br />
800 MgHz AMD/ 1 GIG Ram / RH9 choked on trying to make that set into a movie.<br />
<br />
===install and running===<br />
1.1.3 is a snap. <br />
rpm -ivh xvidcapxxxx.rpm<br />
<br />
After installng, at the prompt type:<br />
$xvidcap<br />
<br />
I checked the options file $HOME/.xvidcap.scf and I set it to mpeg4.<br />
<br />
saving as mpeg4<br />
<br />
<pre><br />
#SCFF<br />
# xvidcap configuration file<br />
<br />
# frames per second<br />
fps: 5.000000<br />
<br />
# file pattern<br />
file: capture-01.mpeg<br />
<br />
# max frames <br />
max_frames: 0<br />
<br />
# max time <br />
max_time: 0.000000<br />
<br />
# quality (JPEG)<br />
quality: 15<br />
<br />
# compression (PNG, GZIP)<br />
compression: 0 <br />
<br />
# use shared memory<br />
shm: 16<br />
<br />
# video codec used by ffmpeg<br />
codec: MPEG4<br />
<br />
# what kind of mouse pointer should be recorded?<br />
# 0 = none, 1 = white, 2 = black<br />
mouse_wanted: 2<br />
<br />
# toggle audio capture (0/1)<br />
audio: 1<br />
<br />
# device to grab audio from<br />
audio_in: /dev/dsp<br />
<br />
# sample rate for audio capture<br />
audio_rate: 22050<br />
<br />
# bit rate for audio capture<br />
audio_bits: 32000<br />
<br />
# number of channels to use in audio capture<br />
audio_channels: 1<br />
</pre><br />
<br />
I'm using [http://xinehq.de/xine] for movie playback.<br />
<br />
<br />
File format .xwd<br />
*xvidcap can save a series of screen grabs XXX.xwd files, they are numbered sequentially<br />
**localhost:~$ :echo this was used for getting rid of all the spare xwd files created by xvidcap<br />
***this was used for getting rid of all the spare xwd files created by xvidcap find . -name "frm*.xwd" -exec rm -f {} \;~/pp~<br />
<br />
***I echo operations back so that when I go back through the history I'll have clues as to what I did.<br />
<br />
<br />
Pros<br />
*audio recording<br />
*clicking on the target icon will record the entire screen<br />
<br />
cons<br />
*the gui control interface is touchy at best, I do all config in the .scf file<br />
*maximizing target recording area hides GUI toolbar. The only way to get GUI visible is to reset capture screen to something smaller...<br />
*The arrow key on the GUI advances the XXX.xwd but apparently is not acting as a manual screen grab tool <br />
**If an audio controller interface and the arrow key did in fact function as an incremental screen grabber xvidcap may be very useful for doing 'stop motion' videos of the linux interface with voice overs<br />
*doesn't prompt user for location of save screen grabs<br />
*no project folder prompt<br />
*GUI is not very opaque in its usage<br />
*movie playback happens in imagemagick though there is supposedly a way to do the playback as an mpeg4 file<br />
<br />
<br />
Wishes<br />
*audio controller on toolbar<br />
*frame rate controller on toolbar<br />
*make video interface to specific output format<br />
*swf output<br />
<br />
Note<br />
* Another alternative is gvidcap. If there are problems with crashing, it may be due to a clash in png libraries. Making from source resolves this error and allows gvidcap to run without crashing. The gvidcap client provides an interface a lot more convenient to setting preferences. The animate command is strictly for animating a sequence of images and will not work with mpegs. Use your usual video player (videolan/mplayer) for this.</div>DennisDaniels