Difference between revisions of "Linux"
m (→Articles: device mgmt) |
m (post-import cleanup & annotation) |
||
Line 1: | Line 1: | ||
− | [[ | + | {{seed}} |
− | [[ | + | [[Computing]]: [[Linux]] |
− | |||
==Articles== | ==Articles== | ||
− | *[[ | + | *[[Linux Shell Commands]] |
*Components: | *Components: | ||
**[[KDE]] | **[[KDE]] | ||
Line 22: | Line 21: | ||
*[[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 | + | *[[dmesg]]|[[tail]] - somehow helps figure out what USB devices have been detected |
− | detected | + | *To '''mount an ISO image as a folder''' ''(untested)'': |
− | *To '''mount an ISO image as a folder''' ''(untested)'': [[mount]] -o | + | [[mount]] -o loop NameOfISO.iso /mount/wherever |
− | loop NameOfISO.iso /mount/wherever | ||
*To swap drives so DOS or 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 | + | **On reboot, when you get to the boot loader startup, select whatever option gets you to a [[grub]] command line ("c" in Fedora Core) |
− | 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: map (hd0) (hd1) map (hd1) | + | map (hd0) (hd1) |
− | (hd0) rootnoverify (hd1,0) chainloader +1 makeactive boot | + | map (hd1) (hd0) |
− | This is a temporary fix which lets you test the changes without making | + | rootnoverify (hd1,0) |
− | your computer unbootable if they fail. To make the changes permanent, | + | chainloader +1 |
− | edit /boot/grub/menu.lst and enter the two "map" lines under the | + | makeactive |
− | Windows entry. (Will document in more detail when I have time to look | + | boot |
− | at the format of menu.lst. I'm also not sure if "hd" is always the | + | 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.) |
− | prefix for the drives or if that might be different depending on the | ||
− | types of drives – e.g. SATA, ATA, IDE – involved.) | ||
==Issues== | ==Issues== | ||
− | The following may reflect [[User:Woozle|my]] own ignorance rather than | + | The following may reflect [[User:Woozle|my]] own ignorance rather than an actual shortcoming in Linux: |
− | an actual shortcoming in Linux: | ||
*Development | *Development | ||
− | **There appears to be no mechanism corresponding to [[ActiveX]] (as | + | **There appears to be no mechanism corresponding to [[ActiveX]] (as used for desktop app development) |
− | 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... |
− | **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 | *Regular Use | ||
− | **In Windows, if you create a link to an executable script (batch file | + | **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. ('''Update''': I have figured this out. Must document.) |
− | -- *.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== | ==How To== | ||
− | *'''Time Zone''': If the [[KDE]] Clock-setting widget seems to be | + | *'''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: |
− | refusing to set the time zone (or your system clock is refusing to show | + | ln -s /usr/share/zoneinfo/America/NewYork /etc/localtime |
− | anything except GMT time), this command may work: ln -s | + | ...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 in the #kde chat room 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) |
− | /usr/share/zoneinfo/America/NewYork /etc/localtime | + | *To force an update of the system clock: |
− | ...where "/America/NewYork" should be replaced by the appropriate file | + | ntpdate pool.ntp.org |
− | for your time zone. I have not been able to find any documentation on | + | *To make this update run automatically, go into root and run kcron (or cron if you're comfortable with [[CLI]] |
− | this feature; the command was suggested to me by someone | + | *'''Emptying the Trash''': KDE does have trash-management built in, but it's not always 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". | |
− | the console "date" command to verify what the system clock is currently | + | **Right-click on the applet panel and add the Trash applet, then left-click on it to use its various functions. |
− | set to. --[[User:Woozle|Woozle]] 08:45, 23 Apr 2005 (CST) | + | **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. |
− | *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 | ||
− | **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=== | ===Running a remote X session=== | ||
− | To have a "window" into another computer -- sort of like VNC, but | + | To have a "window" into another computer -- sort of like VNC, but better: |
− | better: | + | * On the local machine (note the space before the ":"): |
− | * On the local machine (note the space before the ":"): Xnest -ac :1 | + | Xnest -ac :1 |
− | * On the remote machine (via [[ssh]] or equivalent): export | + | * On the remote machine (via [[ssh]] or equivalent): |
− | DISPLAY=''yourmachine'':1 | + | export DISPLAY=''yourmachine'':1 |
− | ...where ''yourmachine'' is the name of your local machine. If you get | + | ...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. |
− | messages indicating that it's having trouble connecting to | + | * You will then need to run the command to start a GUI session; startkde starts [[KDE]]. Not sure what other commands might be available. |
− | ''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== | ==Things You Must Know== | ||
− | In Linux, you often run into things which you Just Have To Know in | + | 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. |
− | order to make things work; there is not really any way to find them | + | * 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. |
− | out. This is bad UI design, but for now it's the situation. I will be | + | * 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. |
− | 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. |
Revision as of 23:38, 13 October 2005
This page is a seed article. You can help HTYP water it: make a request to expand a given page and/or donate to help give us more writing-hours!
|
Articles
- Linux Shell Commands
- Components:
- Device management
Reference Links
- Really Linux: for beginning Linux users
- LinuxQuestions wiki
- Linux Manpages: man
documentation as searchable web pages
User/Security Admin
- Commands:
- Links:
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. (Update: I have figured this out. Must document.)
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 in the #kde chat room 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
- To make this update run automatically, go into root and run kcron (or cron if you're comfortable with CLI
- Emptying the Trash: KDE does have trash-management built in, but it's not always 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.