Linux - Revision history

Woozle: moved to htyp

2005-10-13T23:46:43Z

moved to htyp

← Older revision		Revision as of 23:46, 13 October 2005
Line 1:		Line 1:
	~~[[Category:Techniques]]~~		{{to htyp}}
	~~[[Techniques]]: Software: Operating Systems: '''Linux'''~~

	{{~~stub~~}}
	~~==Articles==~~
	*[[:Category:Linux Shell Commands\|Linux Shell Commands]]
	*Components:
	**[[KDE]]
	***[[Konqueror]]
	*[[Device management]]

	~~==Reference Links==~~
	*[http://www.reallylinux.com/ Really Linux]: for beginning Linux users
	*[http://wiki.linuxquestions.org/ LinuxQuestions wiki]
	*[http://linux.ctyme.com/ Linux Manpages]: [[Linux:man\|man]] documentation as searchable web pages

	~~==User/Security Admin==~~
	*Commands:
	**Users: [[useradd]], [[userdel]], [[usermod]]
	**Groups: [[groupadd]], [[groupdel]], [[groupmod]]
	*Links:
	**[http://www.net-security.org/article.php?id=809 Securing Linux]

	~~==Hardware==~~
	*[[Linux:Scanners\|Scanners]]
	*[[lspci]] - lists all PCI devices found
	*[[dmesg]]\|tail - somehow helps figure out what USB devices have been detected
	*To '''mount an ISO image as a folder''' ''(untested)'':
	~~[[mount]] -o loop NameOfISO.iso /mount/wherever~~
	*To swap drives so DOS or Windows can be booted off the 2nd drive:
	**On reboot, when you get to the boot loader startup, select whatever option gets you to a [[grub]] command line ("c" in Fedora Core)
	**At the grub prompt, enter the following:
	~~map (hd0) (hd1)~~
	~~map (hd1) (hd0)~~
	~~rootnoverify (hd1,0)~~
	~~chainloader +1~~
	~~makeactive~~
	~~boot~~
	This is a temporary fix which lets you test the changes without making your computer unbootable if they fail. To make the changes permanent, edit /boot/grub/menu.lst and enter the two "map" lines under the Windows entry. (Will document in more detail when I have time to look at the format of menu.lst. I'm also not sure if "hd" is always the prefix for the drives or if that might be different depending on the types of drives – e.g. SATA, ATA, IDE – involved.)

	~~==Issues==~~
	~~The following may reflect [[User:Woozle\|my]] own ignorance rather than an actual shortcoming in Linux:~~
	*Development
	**There appears to be no mechanism corresponding to [[ActiveX]] (as used for desktop app development)
	**There appears to be no application corresponding to [[Microsoft Access]]. Yes, you can do all the same stuff with various available tools, but not quickly; v2.0 of [[OpenOffice]] is apparently going to include a tool which may be a step in the right direction...
	*Regular Use
	*In Windows, if you create a link to an executable script (batch file -- .bat) on your desktop (or anywhere), the link is executable with a double-click. Under KDE (in [[Ubuntu]]), I can't figure out how to make it execute at all without using a terminal.
	~~==How To==~~
	*'''Time Zone''': If the [[KDE]] Clock-setting widget seems to be refusing to set the time zone (or your system clock is refusing to show anything except GMT time), this command may work:
	~~ln -s /usr/share/zoneinfo/America/NewYork /etc/localtime~~
	...where "/America/NewYork" should be replaced by the appropriate file for your time zone. I have not been able to find any documentation on this feature; the command was suggested to me by someone on the #kde forum at irc.freenode.net (see [http://freenode.net/]). Remember to use the console "date" command to verify what the system clock is currently set to. --[[User:Woozle\|Woozle]] 08:45, 23 Apr 2005 (CST)
	*To force an update of the system clock:
	~~ntpdate pool.ntp.org~~
	*'''Emptying the Trash''': KDE does have trash-management built in, but it's not made obvious. You can do any of the following:
	**Navigate (in Konqueror) to "trash:/", then right-click on the panel showing the contents, and select "Empty trash".
	**Right-click on the applet panel and add the Trash applet, then left-click on it to use its various functions.
	**Create a new URL link on the desktop, give it the URL "trash:/", then right-click on it (my preferred solution). A trashcan icon is available in the "filesystems" icon group.
	~~===Running a remote X session===~~
	~~To have a "window" into another computer -- sort of like VNC, but better:~~
	* On the local machine (note the space before the ":"):
	~~Xnest -ac :1~~
	* On the remote machine (via [[ssh]] or equivalent):
	~~export DISPLAY=''yourmachine'':1~~
	~~...where ''yourmachine'' is the name of your local machine. If you get messages indicating that it's having trouble connecting to ''yourmachine'', try using an IP address instead.~~
	* You will then need to run the command to start a GUI session; startkde starts [[KDE]]. Not sure what other commands might be available.

	~~==Things You Must Know==~~
	In Linux, you often run into things which you Just Have To Know in order to make things work; there is not really any way to find them out. This is bad UI design, but for now it's the situation. I will be listing them here as I find them out.
	* When Perl is missing a module, the package name is always (I am told) "perl-libraryname". For example, for Tk.pm, the package is perl-Tk. So in Fedora you would type "yum install perl-Tk". Presumably in debian-derived distributions, you would type "apt-get install perl-Tk", though I have not actually tested this. (Remember that package names, like Linux filenames, are case-sensitive, so that T must be uppercase or it won't work.) If the library is within a Perl package, e.g. Net::Telnet, then the format is perl-Package-Library, e.g. perl-Net-Telnet.
	* To run a binary which is located in the current directory, from the command line, you have to type "./" before the binary's name. It's not clear why this is.

Woozle: /* Articles */ device mgmt

2005-10-05T23:52:38Z

Articles: device mgmt

← Older revision		Revision as of 23:52, 5 October 2005
Line 8:		Line 8:
	**[[KDE]]		**[[KDE]]
	***[[Konqueror]]		***[[Konqueror]]
			*[[Device management]]

	==Reference Links==		==Reference Links==

Woozle: /* Running a remote X session */ not kdestart

2005-10-03T17:17:25Z

Running a remote X session: not kdestart

← Older revision		Revision as of 17:17, 3 October 2005
Line 62:		Line 62:
	export DISPLAY=''yourmachine'':1		export DISPLAY=''yourmachine'':1
	...where ''yourmachine'' is the name of your local machine. If you get messages indicating that it's having trouble connecting to ''yourmachine'', try using an IP address instead.		...where ''yourmachine'' is the name of your local machine. If you get messages indicating that it's having trouble connecting to ''yourmachine'', try using an IP address instead.
	* You will then need to run the command to start a GUI session; ~~kdestart~~ starts [[KDE]]. Not sure what other commands might be available.		* You will then need to run the command to start a GUI session; startkde starts [[KDE]]. Not sure what other commands might be available.

	==Things You Must Know==		==Things You Must Know==

Woozle: /* Hardware */ making the swap permanent

2005-10-02T16:04:58Z

Hardware: making the swap permanent

← Older revision		Revision as of 16:04, 2 October 2005
Line 27:		Line 27:
	*To '''mount an ISO image as a folder''' ''(untested)'':		*To '''mount an ISO image as a folder''' ''(untested)'':
	[[mount]] -o loop NameOfISO.iso /mount/wherever		[[mount]] -o loop NameOfISO.iso /mount/wherever
	*To swap drives so Windows can be booted off the 2nd drive:		*To swap drives so DOS or Windows can be booted off the 2nd drive:
	**On reboot, when you get to the boot loader startup, select whatever option gets you to a [[grub]] command line ("c" in Fedora Core)		**On reboot, when you get to the boot loader startup, select whatever option gets you to a [[grub]] command line ("c" in Fedora Core)
	**At the grub prompt, enter the following:		**At the grub prompt, enter the following:
Line 36:		Line 36:
	makeactive		makeactive
	boot		boot
	This is a temporary fix ~~to let~~ you test the changes without making your computer unbootable. Will document the ~~permanent fix once~~ I ~~know how it~~ is ~~done~~.		This is a temporary fix which lets you test the changes without making your computer unbootable if they fail. To make the changes permanent, edit /boot/grub/menu.lst and enter the two "map" lines under the Windows entry. (Will document in more detail when I have time to look at the format of menu.lst. I'm also not sure if "hd" is always the prefix for the drives or if that might be different depending on the types of drives – e.g. SATA, ATA, IDE – involved.)

	==Issues==		==Issues==

Woozle: /* Hardware */ swapping drives with grub

2005-10-02T15:57:11Z

Hardware: swapping drives with grub

@@ Line 27: / Line 27: @@
 *To '''mount an ISO image as a folder''' ''(untested)'':
   [[mount]] -o loop NameOfISO.iso /mount/wherever
 ==Issues==

Woozle: /* Reference Links */ Really Linux link

2005-09-29T12:53:01Z

Reference Links: Really Linux link

← Older revision		Revision as of 12:53, 29 September 2005
Line 10:		Line 10:

	==Reference Links==		==Reference Links==
			*[http://www.reallylinux.com/ Really Linux]: for beginning Linux users
	*[http://wiki.linuxquestions.org/ LinuxQuestions wiki]		*[http://wiki.linuxquestions.org/ LinuxQuestions wiki]
	*[http://linux.ctyme.com/ Linux Manpages]: [[Linux:man\|man]] documentation as searchable web pages		*[http://linux.ctyme.com/ Linux Manpages]: [[Linux:man\|man]] documentation as searchable web pages

Woozle: /* Hardware */ dmesg

2005-09-27T21:14:20Z

Hardware: dmesg

← Older revision		Revision as of 21:14, 27 September 2005
Line 23:		Line 23:
	*[[Linux:Scanners\|Scanners]]		*[[Linux:Scanners\|Scanners]]
	*[[lspci]] - lists all PCI devices found		*[[lspci]] - lists all PCI devices found
			*[[dmesg]]\|tail - somehow helps figure out what USB devices have been detected
	*To '''mount an ISO image as a folder''' ''(untested)'':		*To '''mount an ISO image as a folder''' ''(untested)'':
	[[mount]] -o loop NameOfISO.iso /mount/wherever		[[mount]] -o loop NameOfISO.iso /mount/wherever

Woozle: /* How To */ running remote X session

2005-09-22T18:30:06Z

How To: running remote X session

← Older revision		Revision as of 18:30, 22 September 2005
Line 43:		Line 43:
	**Right-click on the applet panel and add the Trash applet, then left-click on it to use its various functions.		**Right-click on the applet panel and add the Trash applet, then left-click on it to use its various functions.
	**Create a new URL link on the desktop, give it the URL "trash:/", then right-click on it (my preferred solution). A trashcan icon is available in the "filesystems" icon group.		**Create a new URL link on the desktop, give it the URL "trash:/", then right-click on it (my preferred solution). A trashcan icon is available in the "filesystems" icon group.
			===Running a remote X session===
			To have a "window" into another computer -- sort of like VNC, but better:
			* On the local machine (note the space before the ":"):
			Xnest -ac :1
			* On the remote machine (via [[ssh]] or equivalent):
			export DISPLAY=''yourmachine'':1
			...where ''yourmachine'' is the name of your local machine. If you get messages indicating that it's having trouble connecting to ''yourmachine'', try using an IP address instead.
			* You will then need to run the command to start a GUI session; kdestart starts [[KDE]]. Not sure what other commands might be available.

	==Things You Must Know==		==Things You Must Know==
	In Linux, you often run into things which you Just Have To Know in order to make things work; there is not really any way to find them out. This is bad UI design, but for now it's the situation. I will be listing them here as I find them out.		In Linux, you often run into things which you Just Have To Know in order to make things work; there is not really any way to find them out. This is bad UI design, but for now it's the situation. I will be listing them here as I find them out.
	* When Perl is missing a module, the package name is always (I am told) "perl-libraryname". For example, for Tk.pm, the package is perl-Tk. So in Fedora you would type "yum install perl-Tk". Presumably in debian-derived distributions, you would type "apt-get install perl-Tk", though I have not actually tested this. (Remember that package names, like Linux filenames, are case-sensitive, so that T must be uppercase or it won't work.) If the library is within a Perl package, e.g. Net::Telnet, then the format is perl-Package-Library, e.g. perl-Net-Telnet.		* When Perl is missing a module, the package name is always (I am told) "perl-libraryname". For example, for Tk.pm, the package is perl-Tk. So in Fedora you would type "yum install perl-Tk". Presumably in debian-derived distributions, you would type "apt-get install perl-Tk", though I have not actually tested this. (Remember that package names, like Linux filenames, are case-sensitive, so that T must be uppercase or it won't work.) If the library is within a Perl package, e.g. Net::Telnet, then the format is perl-Package-Library, e.g. perl-Net-Telnet.
	* To run a binary which is located in the current directory, from the command line, you have to type "./" before the binary's name. It's not clear why this is.		* To run a binary which is located in the current directory, from the command line, you have to type "./" before the binary's name. It's not clear why this is.

Woozle: /* Things You Must Know */ dotslash

2005-09-20T00:04:16Z

Things You Must Know: dotslash

← Older revision		Revision as of 00:04, 20 September 2005
Line 46:		Line 46:
	In Linux, you often run into things which you Just Have To Know in order to make things work; there is not really any way to find them out. This is bad UI design, but for now it's the situation. I will be listing them here as I find them out.		In Linux, you often run into things which you Just Have To Know in order to make things work; there is not really any way to find them out. This is bad UI design, but for now it's the situation. I will be listing them here as I find them out.
	* When Perl is missing a module, the package name is always (I am told) "perl-libraryname". For example, for Tk.pm, the package is perl-Tk. So in Fedora you would type "yum install perl-Tk". Presumably in debian-derived distributions, you would type "apt-get install perl-Tk", though I have not actually tested this. (Remember that package names, like Linux filenames, are case-sensitive, so that T must be uppercase or it won't work.) If the library is within a Perl package, e.g. Net::Telnet, then the format is perl-Package-Library, e.g. perl-Net-Telnet.		* When Perl is missing a module, the package name is always (I am told) "perl-libraryname". For example, for Tk.pm, the package is perl-Tk. So in Fedora you would type "yum install perl-Tk". Presumably in debian-derived distributions, you would type "apt-get install perl-Tk", though I have not actually tested this. (Remember that package names, like Linux filenames, are case-sensitive, so that T must be uppercase or it won't work.) If the library is within a Perl package, e.g. Net::Telnet, then the format is perl-Package-Library, e.g. perl-Net-Telnet.
			* To run a binary which is located in the current directory, from the command line, you have to type "./" before the binary's name. It's not clear why this is.

Woozle: /* Things You Must Know */ format for Perl pkgs

2005-09-19T23:52:10Z

Things You Must Know: format for Perl pkgs

← Older revision		Revision as of 23:52, 19 September 2005
Line 45:		Line 45:
	==Things You Must Know==		==Things You Must Know==
	In Linux, you often run into things which you Just Have To Know in order to make things work; there is not really any way to find them out. This is bad UI design, but for now it's the situation. I will be listing them here as I find them out.		In Linux, you often run into things which you Just Have To Know in order to make things work; there is not really any way to find them out. This is bad UI design, but for now it's the situation. I will be listing them here as I find them out.
	* When Perl is missing a module, the package name is always (I am told) "perl-libraryname". For example, for Tk.pm, the package is perl-Tk. So in Fedora you would type "yum install perl-Tk". Presumably in debian-derived distributions, you would type "apt-get install perl-Tk", though I have not actually tested this. (Remember that package names, like Linux filenames, are case-sensitive, so that T must be uppercase or it won't work.)		* When Perl is missing a module, the package name is always (I am told) "perl-libraryname". For example, for Tk.pm, the package is perl-Tk. So in Fedora you would type "yum install perl-Tk". Presumably in debian-derived distributions, you would type "apt-get install perl-Tk", though I have not actually tested this. (Remember that package names, like Linux filenames, are case-sensitive, so that T must be uppercase or it won't work.) If the library is within a Perl package, e.g. Net::Telnet, then the format is perl-Package-Library, e.g. perl-Net-Telnet.