Linux

Techniques: Software: Operating Systems: Linux Template:stub

Articles

• Linux Shell Commands
• Components:
  • KDE
    • Konqueror
• Device management

Reference Links

• Really Linux: for beginning Linux users
• LinuxQuestions wiki
• Linux Manpages: man

documentation as searchable web pages

User/Security Admin

• Commands:
  • Users: useradd, userdel, usermod
  • Groups: groupadd, groupdel, groupmod
• Links:
  • Securing Linux

Hardware

• 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 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 [1]). Remember to use the console "date" command to verify what the system clock is currently set to. --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.