|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
dpkg -S filename. If you need
a particular file, but the package providing it is not installed,
you can install the apt-file package and then use
the command apt-file search filename to determine
which package or packages provide it.
[ More Info ]
dpkg --get-selections. You can also use the
Ubuntu Software Center, if you prefer a
GUI method of checking.
$ dpkg --get-selections | more accountsservice install acl install acpi-support install acpid install adduser install adium-theme-ubuntu install aisleriot install alsa-base install alsa-utils install amazonmp3 install anacron install
If you only want to determine whether a paricular package is installed,
you can use grep to filter the results.
$ dpkg --get-selections | grep libboost libboost-filesystem1.46.1 install libboost-serialization1.46.1 install libboost-system1.46.1 install
You can find the locations for the files installed when the package was
installed by using the -L option with dpkg
$ dpkg -L libboost-filesystem1.46.1 /. /usr /usr/lib /usr/lib/libboost_filesystem.so.1.46.1 /usr/share /usr/share/doc /usr/share/doc/libboost-filesystem1.46.1 /usr/share/doc/libboost-filesystem1.46.1/copyright /usr/share/lintian /usr/share/lintian/overrides /usr/share/lintian/overrides/libboost-filesystem1.46.1 /usr/share/doc/libboost-filesystem1.46.1/NEWS.Debian.gz /usr/share/doc/libboost-filesystem1.46.1/README.Debian.gz /usr/share/doc/libboost-filesystem1.46.1/changelog.Debian.gz
To obtain information regarding a package, including its description,
you can use the -s or --status option followed
by the complete package name.
$ dpkg -s libboost-filesystem1.46.1 Package: libboost-filesystem1.46.1 Status: install ok installed Priority: optional Section: libs Installed-Size: 208 Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Architecture: i386 Source: boost1.46 Version: 1.46.1-5ubuntu2 Depends: libboost-system1.46.1 (>= 1.46.1-1), libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1) Description: filesystem operations (portable paths, iteration over directories, etc) in C++ This package forms part of the Boost C++ Libraries collection. . The Boost Filesystem Library provides portable facilities to query and manipulate paths, files, and directories. The goal is to facilitate portable script-like operations from within C++ programs. Homepage: http://boost.org/libs/filesystem/ Original-Maintainer: Debian Boost Team <pkg-boost-devel@lists.alioth.debian.org>
[ More Info ]
dmesg
command feeding its results to grep and then use tail
to get just the last line containing the word "SCSI", since if you just
plugged the device into the system, that last line likely contains the relevant
entry.
$ su - root Password: # dmesg | grep -i 'SCSI device' | tail --lines=1 SCSI device sdb: 7813120 512-byte hdwr sectors (4000 MB)
Since I know the flash drive I plugged into the system in this case is
a 4 GB drive, I know that sdb is indeed the relevant drive
designator.
Alternatively you could look for the information in /var/log/messages
.
[root@example ~]# grep SCSI /var/log/messages | tail --lines=1 Nov 13 09:55:55 example kernel: SCSI device sdb: 7813120 512-byte hdwr secto rs (4000 MB)
You can then use the information you obtained for the drive designator,
in this case sdb to mount the drive. Note you might see other
"sd" designators, such as sda, sdc, sdd, etc., or "hd" designators, such as
hda, hdb, hdc, etc.
Use the mount command to mount the drive to an
exising mount point, such as one beneath /mnt or
/media. Unless a directory already exists that you
wish to use, you could create a directory which you will use to
access the contents of the USB drive. Let's suppose you want to use
myusb for that directory; you then need to create the
directory.
# mkdir /media/myusb
Presuming the file system on the flash drive is vfat, I could use the
command below to mount the device at the mount point /media/myusb.
You need to spcify the file system type with the -t option.
Note: I use sdb1 rather than just the designator sdb,
since I want to mount the first and, in this case, only partition, on the
flash drive. The
VFAT file system is a commonly used one for flash and other USB drives. It
is a Microsoft created file system that allows the use of file names longer
than an 8 character file name with a 3 character extension.
[root@example ~]# mount -t vfat /dev/sdb1 /media/myusb
I can then issue the mount command again without any parameters
to verify the drive is mounted.
[root@example ~]# mount | grep sdb /dev/sdb1 on /media/myusb type vfat (rw)
The rw on the output shows me that the drive is mounted
in read/write mode rather than read only (ro) mode, so I could write to
the drive as well as read from it.
You should then be able to access the drive using /media/myusb,
or whatever you used for the path designator.
[root@frostdragon ~]# ls /media/myusb aoss.txt definitions
When you are finished with the drive, you should unmount it using the
umount command prior to removing it from the system. You can
also remove the directory you created for mounting it using the rmdir
command, unless you will use that same directory for mounting it or
other drives in the future.
[root@example ~]# umount /media/myusb [root@example ~]# rmdir /media/myusb
References:
I created a Ubuntu 11.04 Desktop edition live CD for booting a system so that I could check on files on the system which had Microsoft Windows XP Home edition on the hard drive. The system's owner reported she was having problems with the system and I wanted to start with a quick look at some of the files on the system and make a backup of her "My Documents" folder. I needed to open Firefox on the system to check on some information online, but whenever I opened a second tab in Firefox to Amazon.com, Firefox would crash. It also crashed with only one tab open when I used Ctrl-Alt-F2 to obtain a shell prompt with an error message indicating that there was a problem with inadequate memory.
The system had a 3.2 GHz processor, but only 512 MB of memory and the system requirements for Ubuntu Desktop Edition 11.04 (Natty Narwhal) listed on the Ubuntu site were as follows:
Since the system just met the minimum memory requirement for Ubuntu 11.04, I decided to try Xubuntu (pronounced "zoo-BOON-too"), instead. Xubuntu is a derivative of Ubuntu, which uses the Xfce desktop environment, which requires less memory than the Unity desktop used by Ubuntu.
Xubuntu is a community developed, Ubuntu-based Linux operating system that is well-suited for both laptops and desktops. It contains all the applications you need - a web browser, document and spreadsheet editing software, instant messaging and much more.
Minimum system requirements
You need 256 MB RAM to run the Live CD or 256 MB RAM to install. The Alternate Install CD only requires you to have 64 MB RAM at install time.
To install Xubuntu with the standard installer (Ubiquity), you need 4.4 GB of free space on your hard disk. The Alternate Install CD only requires you to have 2 GB of free space on your hard disk.
Once installed, Xubuntu can run with starting from 256 (or even just 192) MB RAM, but it is strongly recommended to have at least 512 MB RAM.
I downloaded Xubuntu 11.04 (Natty Narwhal). I burned it to a CD and rebooted the system with it. I found that I didn't have any problems when I opened multiple tabs in Firefox under Xubuntu.
References:
If you have a Fedora 12 or Red Hat 6 (RHEL) or later versions of Linux on
a system and would like to install the
Google Chrome browser using the
YUM
package manager, you can do so using the following steps.
Note: You can determine which version of those operating systems or CentOS
you are using by examining the contents of /etc/redhat-release.
/etc/yum.repos.d/google.repo and place the following lines in it
depending on whether you are using a 32-bit version of Linux or a 64-bit
version. You can check whether you have a 64-bit version by issuing the
command uname -a. For a 64-bit version, you will see
x86_64 in the output.
32-bit
[google]
name=Google - i386
baseurl=http://dl.google.com/linux/rpm/stable/i386
enabled=1
gpgcheck=1
gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub
64-bit
[google64]
name=Google - x86_64
baseurl=http://dl.google.com/linux/rpm/stable/x86_64
enabled=1
gpgcheck=1
gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub
Note: you could also put both the 32-bit and 64-bit repo information in the same file, if you wish.
## Install Google Chrome Stable version
yum install google-chrome-stable
## OR install Google Chrome Beta version##
yum install google-chrome-beta
## OR install Google Chrome Unstable version##
yum install google-chrome-unstable
However, if you are using CentOS 5, you won't be able to install the Chrome browser using the above steps. When I attempted to install the package on a CentOS 5.5 system, I saw a message indicating that version 3.2 of the lsb package was needed:
Missing Dependency: lsb >= 3.2 is needed by package
google-chrome-stable-6.0.472.53-57914.x86_64 (google64)
# yum install google-chrome-stable
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
* addons: hpc.arc.georgetown.edu
* base: centos.mirror.netriplex.com
* extras: mirror.vcu.edu
* rpmforge: fr2.rpmfind.net
* updates: mirrors.serveraxis.net
google64 | 951 B 00:00
403 packages excluded due to repository priority protections
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package google-chrome-stable.x86_64 0:6.0.472.53-57914 set to be updated
--> Processing Dependency: lsb >= 3.2 for package: google-chrome-stable
--> Processing Dependency: xdg-utils for package: google-chrome-stable
--> Running transaction check
---> Package google-chrome-stable.x86_64 0:6.0.472.53-57914 set to be updated
--> Processing Dependency: lsb >= 3.2 for package: google-chrome-stable
---> Package xdg-utils.noarch 0:1.0.2-2.el5.centos set to be updated
--> Finished Dependency Resolution
google-chrome-stable-6.0.472.53-57914.x86_64 from google64 has depsolving proble
ms
--> Missing Dependency: lsb >= 3.2 is needed by package google-chrome-stable-6
.0.472.53-57914.x86_64 (google64)
Error: Missing Dependency: lsb >= 3.2 is needed by package google-chrome-stable-
6.0.472.53-57914.x86_64 (google64)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.
When I tried updating the lsb package, I saw the following:
# yum install lsb Loaded plugins: fastestmirror, priorities Loading mirror speeds from cached hostfile * addons: hpc.arc.georgetown.edu * base: mirrors.serveraxis.net * extras: mirror.vcu.edu * rpmforge: fr2.rpmfind.net * updates: mirrors.serveraxis.net 403 packages excluded due to repository priority protections Setting up Install Process Package redhat-lsb-3.1-12.3.EL.el5.centos.x86_64 already installed and latest ve rsion Package redhat-lsb-3.1-12.3.EL.el5.centos.i386 already installed and latest vers ion Nothing to do
I had similar results when I changed the contents of google.repo
to try the 32-bit version, instead.
I found lots of other people reporting the same problem with earlier versions of Red Hat Enterprise Linux (RHEL) 5 and versions of Fedora prior to 12. E.g., there are similar reports at How to install google Chrome in RHEL 5. and Add support for RHEL/CentOS for OS compatibility. At the latter problem report webpage, I found a suggestion from andrewrjones that people wanting to use chrome on CentOS check Chris Staite's webpage, Chrome on CentOS where he provides Chromium for CentOS. Chromium is Google's open source alternative to their Chrome browser.
You can download Chromium for CentOS 5 from his website or from this website. Chromium is an open-source browser project behind the Google Chrome browser that aims to build a safer, faster, and more stable way for all users to experience the web.
| Download Chromium |
|---|
| Chris Staite |
| MoonPoint Support |
Once you've downloaded it, you will need to unzip it and untar it.
When you extract the contents of the tar file, a chrome
directory will be created beneath the current directory. Make that
the working directory and run chrome-wrapper.
# gunzip chrome.tar.gz
# tar -xvf chrome.tar
# cd chrome
# ./chrome-wrapper
You will then be asked to choose the search engine you wish to use from Google, Yahoo!, or Bing.
Once you've started Chromium, you can control and customize it, by clicking on the wrench symbol in the upper, right-hand corner of the Chromium window.
When I ran chrome-wrapper, I received the error message below,
but the program ran.
# ./chrome-wrapper
[5578:5592:5060312371904:ERROR:base/nss_util.cc(184)] Error initializing NSS with a persistent database (sql:/root/.pki/nssdb): NSS error code -8174
The program that Chris provides is a 32-bit one.
# file chrome
chrome: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), not stripped
I found a discussion of the problems with Chrome and Chromium as well on CentOS systems at Google chrome for CentOS ?? that indicates Google has no interest in supporting Chrome on CentOS 5. There's also helpful information there on the Chromium software available from Chris Staite's site and how to resolve problems encountered with it on CentOS systems, but, since I have a lot of more pressing things to get done, I decided I couldn't afford to spend any more time troubleshooting issues with Chrome and Chromium on CentOS and just deleted the Chromium software from the system on which I had placed it.
References:
cat /etc/redhat-release.
References:
cdrecord command
under Linux, if you have the
cdrecord package
installed. E.g., cdrecord -v slax-6.1.2.iso. The -v
option, increments the general verbosity level by one. This can be used to
display the progress of the writing process.
CDRecord is a command line CD/DVD recording program. Cdrecord is an application for creating audio and data CDs. Cdrecord works with many different brands of CD recorders, fully supports multi-sessions and provides human-readable error messages.
ifdown eth0 and then brining it back up with ifup
eth0, which will cause the system to try to obtain an address via
DHCP.
