Skip navigation.

exploreopera

| Help

Sign up | Help

JaDa's blog about Opera and Linux

I usually work on Free things. "Free" doesn't just mean zero cost; it means the freedom to copy, to share, to modify and redistribute without arbitrary restrictions.

Posts tagged with "Archlinux"

Archlinux with Opera 9.51 RC2

,

Some screenshots

Opera



Archlinux





Ulteo Online Desktop: your applications and data in a web browser!

, ,

The Ulteo Online Desktop has been designed to offer both the software applications you are using and the your personal data within a webbrowser. As a result you can retrieve your Digital Life anywhere!

http://www.ulteo.com/

A screenshot taken from me today. I was using Archlinux i686 and Kernel 2.6.25.4, with the Browser Opera-9.50-gcc4-shared-qt3 Build 1997, QT 3.3.8!



Opera 9.50 Beta 2 Build 1997 (Opera-9.50-gcc4-shared-qt3)

Today, I set up ...

I set up today a new box with Arch Linux and the Opera 9.20!
]

Exercise for study Arch Linux Part 2

Part 2

Pacman
pacman is the package manager which tracks all the software installed on your system. It has simple dependency support and uses the standard tar-gz archive format for all packages. Some common tasks are explained below with the respective commands in long and short option form. For an up to date explanation of pacman's options, read man pacman. This overview is merely scratching the surface of pacman's current capabilities.

Refreshing the package list:
# pacman --sync --refresh
# pacman -Sy

This will retrieve a fresh master package list from the repositories defined in the /etc/pacman.conf file and uncompress it into the database area. You should use this before using --sysupgrade to make sure you get the newest packages. Depending on your pacman.conf settings, this command may require a working internet connection to access FTP-based repositories. This option is quite similar to Debian's apt-get update command.
Upgrading the system:
# pacman --sync --sysupgrade
# pacman -Su

This command will upgrade all packages that are out-of-date on your system by comparing the local package version to the versions in the master package list that gets downloaded with the --refresh command. It's a good idea to run this every now and then to keep your system up to date. Note that this command does NOT implicitly refresh the master package list, so it's usually wiser to combine both commands into one:
# pacman --sync --refresh --sysupgrade
# pacman -Syu

With these options pacman will automatically retrieve the current master package list and do a full system upgrade to the latest packages with all dependencies being automagically resolved. You will want to run this quite often.
Querying the Package Database:
Pacman can search the package database for a list of packages, you can enter part of the package name to search for all packages matching the string:
pacman -Ss package

To search installed packages only:
pacman -Qs package

Once you know the name of the package you are looking for, you can display some information on the package. Note that query info (-Qi) will show more info than sync info (-Si), as long as the package is installed.
pacman -Si package  
pacman -Qi package

For a list of files contained in a package:
pacman -Ql package

You can also query what package a file on your system belongs to.
pacman --query --owns /path/to/file
pacman -Qo /path/to/file

This query displays the name and version of the package which contains the file referenced by it's full path as a parameter.
Accessing Repositories
A package repository is a collection of packages and a package meta-info file that can reside in a local directory or on a remote FTP/HTTP server. The default repository for an Arch system is the current repository. This is kept up to date with the latest version of most software and stays fairly bleeding-edge.
Many users also choose to activate the extra package repository which contains more packages that are not part of Arch's core package set. You can activate this repo by uncommenting the appropriate lines in your /etc/pacman.conf. This repository is activated by default.
You can also build, maintain and use your own package repositories. See the pacman manpage for instructions.
If you install from a CD and end up having a problem accessing the Internet, you may need to install additional packages from the CD. You can locate the packages on the cd and install them manually using pacman -A packagename.pkg.tar.gz Alternatively, you can temporarily set up a local repository to access the CD. Mount the CD on /mnt/cd using the command mount /mnt/cd (assuming your fstab is properly set up). Then add the following lines to your /etc/pacman.conf:
[cd]
Server = file:///mnt/cd/arch/pkg

You will then be able to install additional packages to help you get your Internet access set up.

Part 3 will follow soon ...

Exercise for study Arch Linux Part 1

The basic nature fom Arch Linux

:star:

What is Arch Linux?

Arch Linux is an i686-optimized linux distribution that was originally based on ideas from CRUX, a great distribution developed by Per Lidén.
Arch is fast, lightweight, flexible and simple. Those aren't very fancy buzzwords but they're all true. Arch is optimized for the i686 processor, so you get more for your cpu cycle. It's lightweight compared to RedHat et al, and its simple design makes it easy to extend and mold into whatever kind of system you're building.
This is backed by an easy-to-use binary package system that allows you to upgrade your entire system with one command. Arch also uses a ports-like package build system (Arch Build System) to make it easy to build packages, which can also be synchronized with one command. Oh yeah, and you can rebuild your entire system with one command, too. Everything is done quite simply and transparently.
Arch Linux strives to maintain the latest stable version of its software.
Arch Linux also strives to use some of the newer features that are available to linux users, such as hotplug and udev support. Arch Linux 0.8. (Voodoo) uses the 2.6 Linux kernel and udev by default.

:yikes:

Lightweight and simple. Note that doesn't mean it's for everyone....
NOT designed as a newbie distro; it's intended for more experienced users. The aim is to develop Arch into as nearly a perfect base as is humanly possible. A base doesn't include fancy tools and auto configuration mechanisms, but rather contains manual configuration tools and few functions, for the users to further develop and/or learn on their own.
The core development of Arch Linux will NOT be providing any "newbie-friendly" GUIs/utilities at any time in the near future.

Part 1

Step 1: I have download the Full Arch Linux Version 0.8 (Voodoo) here from the Mirrors via Http
Step 2: Burn the CD Imagine
Step 3: Base Installation
Step 4:Configure /etc/rc.conf
This is the main configuration file for Arch Linux. It allows you to set your keyboard, timezone, hostname, network, daemons to run and modules to load at bootup, profiles, and more. You should read through all the settings in this file and make sure you understand them:
eth0="dhcp"
This was my only changes!
Step 5: Install the Kernel
Install Kernel will ask you which kernel image to install on your hard drive.
Recommended: Install the stock 2.6.x kernel with SCSI/SATA/IDE support. The exact support each 2.6.x kernel has will depend on how you have configured your initial ramdisk, but the default has support for all known SCSI, SATA, and IDE systems. See the System Configuration section for more information about the initrd.
Please note that Arch Linux uses the 2.6 kernel by default.
Step 6: Install Bootloader
Install Bootloader will install a bootloader on your hard drive, either GRUB (recommended) or LILO, depending on your personal preference.
Before installing the bootloader, the setup script will want you to examine the appropriate configuration file to confirm the proper settings. Make sure you know what your root (and /boot, if you have it) partitions are.
If you choose to install LILO, the bootloader will be automatically installed according to your settings in the configuration file, whilst GRUB demands the selection of a partition to install the bootloader to. Here you should choose what you would enter as the boot option of LILO, which is usually the entry named /dev/hda, as it refers the master boot record of the first hard disk. Detailed error messages can be found as usual on VC5 (virtual console 5), if anything goes wrong.
If you plan on setting up a multiboot system, it might be a better option to install the bootloader in your root or /boot partition, and refer to that boot sector from whatever other boot loader you want to reside in the master boot record.
Installing a boot loader in the MBR will relentlessly overwrite any existing bootloader! Make sure you understand the implications of that if you're running a multiboot system, or want to preserve an installed bootloader from another OS!
Step 7: Exit and Reboot
You think that's it, think again........



Part 2 will follow in the next days :wink:
July 2008
SMTWTFS
June 2008August 2008
12345
6789101112
13141516171819
20212223242526
2728293031