特殊:Badtitle/NS100:Beginners/FAQ/zh

翻译人员:

王楠

{{#ifexist: :Beginners/FAQ/zh/zh | | {{#ifexist: Beginners/FAQ/zh/zh | | {{#ifeq: {{#titleparts:Beginners/FAQ/zh|1|-1|}} | zh | | }} }} }} {{#ifeq: {{#titleparts:Beginners/FAQ/zh|1|-1|}} | zh | | }}

此页的目的是按顺序地收集对（在完全新手论坛中）常见问题的好的回答。欢迎提建议： Feature Requests

如何安装Ubuntu

安装操作系统（OS）对大多数计算机用户来讲是一件困难并且陌生的任务。在开始之前，你最好备份关键性的数据。在着手时你将会面临分配硬盘分区（为新的操作系统腾出地方）以及安装开机引导器（boot loader）（用于引导你的多个操作系统）的任务。幸运的是，安装Ubuntu相对来说要容易得多。你需要烧录一张CD，之后从这张光盘启动你的计算机，这能让你能够预览一下Ubuntu操作系统。你还可以使用这张光盘意孤行化的简单方式将Ubuntu安装到你的计算机上。参考GraphicalInstall关于使用图形化安装器安装Ubuntu的帮助。偶尔桌面或Live CD安装也会失败。这时，考虑使用Alternate CD或许会有帮助。Alternate CD使用命令行安装器，是针对更高级的用户设计的。如果你感觉使用Alternate CD不舒服，可以从更有经验的Ubuntu用户那里寻求帮助，他们能帮你完成这一过程。在irc.freenode.net上的#ubuntu的IRC频道是个很不错的获得帮助的地方。总览（更多信息）：Installing from the Alternate CD 图形化向导： Windows (NTFS) + Ubuntu

附加信息

下载Ubuntu: GettingUbuntu 如何烧录CD镜像至CD：BurningIsoHowto 从CD引导：BootFromCD 分区基础：Basic Partitioning GRUB: GrubHowto Hermanzone: How to Grub

定制桌面

辅助功能

当Ubuntu安装完成后，对于最新的Ubuntu 7.04 (Feisty Fawn)系统版本，在主菜单（默认情况下在屏幕左上角）中选择系统->参数设置->辅助功能 。选择键盘辅助功能，打开按键粘连以及等其它辅助功能。在老的系统版本中，此设定在系统->参数设置->键盘中。 更多信息请参考Accessibility。

基本定制

Desktop Customization

安装软件

软件库

通常来说从Ubuntu软件库安装软件是最好（也是最容易）的方法。Ubuntu是一个基于Debian的发行版，因此使用Synaptic, apt-get, 和aptitude (以及dpkg). dpkg, apt-get, 和aptitude都是命令行工具。Synaptic是apt-get的图形界面前端。应用程序被包装成.deb文件： 注意: 你需要将软件库列表中类似网址的所有行的最前面的“#”号去掉以使所有的软件库生效， 保存该文件并重新载入软件源。

' Ubuntu 或 Gnome

gksudo gedit /etc/apt/sources.list

Kubuntu 或 KDE

kdesu kate /etc/apt/sources.list

Xubuntu 或 Xfce

gksudo mousepad /etc/apt/sources.list

服务器用户

sudo nano /etc/apt/sources.list

例如 foo-xvz.deb

• foo = 应用程序(程序)名
• -xyz = 版本

dpkg 可以安装一个你已经下载的 .deb文件。 dpkg 负责安装.deb，但不处理依赖关系。apt-get， aptitude， and synaptic可以下载并安装你的应用程序及依赖库。获得更多信息：InstallingSoftware

使用源码安装应用程序

你可以通过编译源码的方式安装程序。源码是程序员创建程序所编写的代码。编译是将这种代码转化为计算机能够识别的代码形式的过程，使用这些编译后的代码程序才能够被执行。Ubuntu软件库里所有可用的程序都处在可以被执行（编译后）的状态。通常来讲你只有在一个应用程序在软件库里不可用的时候才需要编译。对源码的编译可能是一个很棘手的过程，因为在这一过程中很多事情都可能出错。因此只推荐高级用户使用这一方法。要从源码编译生成程序， 首先应安装build-essential和checkinstall 包。build-essential 安装所有的编译源码所需的基本工具。checkinstall会将你新编译的应用程序转化为Ubuntu/Debian包(.deb)之后安装。这样捉的好处是之后你就可以使用apt-get或aptitude来安装或卸载这一程序了。关于checkinstall的更多信息请参考CheckInstall。一般的步骤如下：

1. 下载源码。
2. 解压缩源码。源码一般以.tar或类似.zip文件的形式封装 。

注意: 不是所有.tar中的文件都是源码。有的可能是安装脚本，也可能是预编译二进制文件。3 察看README文件以获得更多的信息和指令。

1. 打开一个终端(应用程序-> 附件-> 终端)
2. 在终端中敲入 ./configure --help 列出所有选项。
3. 敲入 ./configure 为编译源码作准备。
4. 敲入 make 编译源码。
5. 敲入 sudo checkinstall 创建Ubuntu/Debian安装包。

更多信息清访问： http://cutlersoftware.com/ubuntuinstall/

硬件

很多人遇到过硬件相关的问题。这一节将介绍一些处理常见问题的方法。

识别你的硬件

你的硬件设备上的型号名在Linux下可能毫无意义，重要的是芯片组。另外还应该注意即使同一品牌的一个型号的芯片组也可能有不同版本，甚至是不同的芯片组。

 PCI 设备

• 我们可以通过在终端中输入lspci来查询硬件以便识别一个PCI设备。
• 要识别一个图形卡（显卡），我们可以通过在lspci命令的输出结果中查找术语“VGA”的方式缩小硬件查询的范围：

lspci | grep VGA

输出举例: 0000:01:00.0 VGA compatible controller（VGA兼容控制器）: nVidia Corporation NV17 [GeForce4 MX 440 ] (rev a3)

USB 设备

• 要识别一个USB设备，我们可以在终端中输入lsusb来查询。

输出举例: Bus 004 Device 002: ID 152e:2507 LG (HLDS)

• Above, we see the output Bus 004 Device 002. This is handy if we need to point a program/driver to the "location" of the hardware.
• The ID allows us to search for the make and model of the device. From 152e:2507, we can find out that the manufacturer is LG (basic USB information)
• For more detailed information on USB devices and their capabilities, run lsusb -v in a Terminal.
• To see recent events involving USB devices which the kernel has recognized (for example, plugging and unplugging), type dmesg | tail in a Terminal
• To monitor other events involving USB devices, type sudo udevmonitor into a Terminal

For more information on troubleshooting certain types of USB device, see Debugging USB Storage Devices and USB Flash Drives

Hard drive info

Hard drive and partition information

sudo fdisk -l

You can also use gparted which can be installed by installing the gparted package. Installing Software Mount removable devices as normal user pmount is a wrapper around the standard mount program which permits normal users to mount removable devices without a matching /etc/fstab entry. This provides a robust basis for automounting frameworks like GNOME's Utopia project and confines the amount of code that runs as root to a minimum. This package also contains a wrapper "pmount-hal" which reads some information like device labels and mount options from hal and passes them to pmount. Install the package "hal" if you want to use this feature. If a LUKS capable cryptsetup package is installed, pmount is able to transparently mount encrypted volumes. example

pmount /dev/sda

For USB storage that do not get recognized you could try:

sudo modprobe usb-storage

sudo locate usb_storage

followed by pmount command

Query Motherboard bios

for board type /bios version etc

sudo lshw | less

sudo dmidecode

Other possible diagnostics

lsmod — program to show the status of modules in the Linux Kernel so if we wanted to just list USB modules and ignore case

sudo lsmod | grep -i usb

or all devices general info

lsmod

To display the SCSI devices currently attached (and recognized) by the SCSI subsystem use

cat /proc/scsi/scsi.

The output looks like this: Attached devices: Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: PIONEER Model: DVD-ROM DVD-303 Rev: 1.10 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: IBM Model: DNES-309170W Rev: SA30 Type: Direct-Access ANSI SCSI revision: 03 After the "Attached devices:" line there are 3 lines for each recognized device. The first of these lines is SCSI address information discussed in Section 3.1. The following 2 lines of data are obtained from a INQUIRY command that was performed on the device when it was attached. See Section 9.4 for the relationship between the ordering of these devices compared with the sg driver's ordering (which most of the time is the same). Existing devices can be removed using echo "scsi remove-single-device <h> <t> <l>" > /proc/scsi/scsi where the variables are host, bus (channel), target (scsi id) and lun. The success (or otherwise) of this command can be determined by sending a subsequent cat /proc/scsi/scsi command. The removal will fail if the device is busy (e.g. if a file system on the device is mounted). New devices can be added using echo "scsi add-single-device <h> <b> <t> <l>" > /proc/scsi/scsi where the variables are host, bus (channel), target (scsi id) and lun. The success (or otherwise) of this command can be determined by sending a subsequent cat /proc/scsi/scsi command. [1] The SCSI subsystem does not support hot-plugging of SCSI devices (there may also be electrical issues on the associated SCSI parallel bus). It is recommended that those who use add+remove-single-device make sure that other devices on that SCSI bus are inactive if re-plugging is going to take place. To output a list of internal SCSI command blocks use echo "scsi dump <n>" > /proc/scsi/scsi where the numeric value of <n> doesn't matter. This is probably only of interest to people chasing down bugs within the SCSI subsystem. To start (or stop) logging information being sent to the console/log use echo "scsi log <token> <n>" > /proc/scsi/scsi where <token> is one of: {all, none, error, timeout, scan, mlqueue, mlcomplete, llqueue, llcomplete, hlqueue, hlcomplete, ioctl} and <n> is a number between 0 and 7. The tokens "all" and "none" don't take an <n> argument. Prefix meanings: hl upper level drivers [exception: sg uses "timeout"] ml mid level ll lower level drivers [adapter drivers often have there own flags] The value "0" turns off logging while "7" maximizes the volume of output. Logging information will only be output if CONFIG_SCSI_LOGGING was selected in the kernel build.'Warning'': "scsi log all" (and several other variants) can cause a logging infinite loop if the log file (typically /var/log/messages ) lies on a SCSI disk. Either turn off the kernel logging daemon or direct its output to a non SCSI device. Notes [1] The parsing of "add-single-device" and "remove-single-device" is rather inflexible. Hence it is best to stay close to the demonstrated syntax with no extra spaces (and no tabs).Something else to check/try: Add irqpoll to grub

'''gksudo gedit /boot/grub/menu.lst
'''

1. defoptions=quiet splash noapic irqpoll

'sudo update-grub'

WiFi

Although often WiFi will work out of the box, sometimes a particular WiFi card will work in either Ubuntu 6.06 LTS or 6.10 but not both. Therefore if you are having problems with your WiFi you may want to try a different version of Ubuntu. See WirelessNetworking for instructions on how to configure your wireless connection. If you are still having problems with your WiFi you can try to manually configure the interface. In some cases there may be more than one method to get your wireless card to work. Make sure to keep track of which set of instructions you have followed in order to avoid unnecessary repetition. The first step is to identify which wifi card you have so that you can pick the relevant set of instructions, to do this type the following in the terminal:

'''lspci
'''

The output you are looking for will look similar to this:

'''00:09.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
'''

Once you have identified your WiFi card you can proceed to the WifiDocs page and pick the relevant instructions (don't let the long list scare you, you only need the relevant entries). Please note that Ubuntu 6.06 and 6.10 do not natively support WiFi access to WPA encrypted networks. You will be required to install additional packages to access such networks. For further information please read WifiDocs/WPAHowTo For further information, see the Wireless Troubleshooting Guide.

Winmodem

No information yet.

Printers

No information yet.

Multimedia

People sometimes have problems with certain types of audio and video file, or do not like the default multimedia applications. See below for information on working with multimedia in Ubuntu:

• Restricted Formats - Information on playing multimedia files which use restricted formats
• Multimedia Applications - Listings of multimedia software available with Ubuntu

System Administration

Sometimes you may need to perform administrative tasks on your system. This section provides help with some common administrative tasks.

Mounting Disk Partitions

Sometimes, in order to access a hard drive (or a partition on the hard drive), you must mount the hard drive. Mounting is when Ubuntu connects a disk to itself, thus making it available for access. Different disks/partitions can have different file system types. A file system is a way of organizing information on a disk, and much initial configuration depends on the tye of file system the disk has.

Windows

To mount a Windows disk for both reading and writing:

1. For vfat (FAT32) format disks, use umask=000
2. For NTFS format disks, use ntfs-3g and an /etc/fstab entry something like this:

'''/dev/hda1 /media/windows ntfs-3g defaults 0 0
'''

1.#3 An alternate is ntfs-config. ntfs-config uses ntfs-3g to mount windows partitions via a GUI. See Mount Windows (Psychocats) and ntfs-config (GWOS) for more information.

Linux

To set permissions:

1. Mount the partition
2. Use chmod on the directory which you mounted the disk to by typing something like sudo chmod 755 /mount/point into a Terminal

To mount a partition at boot you will need to edit the /etc/fstab file. For an overview of fstab see Understanding fstab (GWOS). If you would like to access EXT2 and EXT3 partitions from Windows, take a look at FS-Driver. See Mount Linux (Psychocats) for more information.

Server Install

Server installs typically have no GUI, and servers may administered remotely via SSH or Webmin. If you are new to server installs you can add a light window manager such as Fluxbox, IceWM, Openbox, or the Ubuntu desktop.

---