|
Softpanorama
(slightly skeptical)
Open Source Software Educational Society |
May the
source be with you,
but remember the KISS principle ;-)
|
Novell OpenSUSE and Enterprise Edition
I know that suesse means sweet in German, but the name
is just abbreviation.
It is one of two major enterprise version of Linux which can run of cheap
but high quality Intel-based hardware provided by Dell and HP. Suse has
relatively short for enterprise OS life span: five years. For example
-
Suse 9 general support will end Jul 30, 2009
-
Suse 10 general support will end
Jul 31, 2011
Visually Suse 10 is very appealing. But appearance is deceptive and inside
it is a pretty complicated and capricious monster with a lot of non-server
components present by default on the server (games, audio, etc). Novell
products that are used instead of simpler alternatives (Red Carpet vs. yum,
etc). As for enterprise-class OS the registration process so complex
unreliable and capricious in case HTTP proxy is used within the organization.
In this case it would not be exaggeration to say that it is worse that any
other proprietary product or that it is completely broken.
According to Novell there will be a simplified JeOS version of Suse (See
press-release
Novell Announces SUSE Appliance Program and
LimeJeos - openSUSE) . Suse
10 supports Xen. See:
Novell is one of the few linux vendors that provides decent manuals which
can help users beyond installing the product. This is true even for a free
version (OpenSuse). The following manuals are available for OpenSuse
10.2 (OpenSuse manuals are different then SLES; the latter has much
better admin guide; see SLES Documentation):
The online versions of the manuals are updated regularly, so check for
updates at least a couple times a year to be sure you have the latest version.
Again, I would like to stress that, like is the case with the Red Hat,
registration process is horrible. In the initial version of Suse 10 the
registration software that comes on CD/DVD was seriously buggy. Quality
of Suse 10 was dramatically improved after SP1 and SP2 were released,
so using Suse 10 without SP2 is not recommended.
SUSE Linux Enterprise patching is difficult to configure but after configuration
works more or less OK. Parckage management is not that polished in comparison
with smart and also much slower
but we have what we have. OpenSuse users actually can use Smart without
any problems.
SUSE Linux Enterprise can work with Microsoft Active Directory but I
did not check that.
SUSE Linux Enterprise includes
Novell AppArmor
application-level security which is vastly superior to Red Hat solution
based on SE-linux. AppArmore works by enforcing of a set of application-based
file permissions (which is a pretty elegant idea). Because each application
can have different set of permissions such a system tremendously helps to
protect against typical attacks as assumptions about system file permissions
used by the attacker became invalid. The latter alone makes it much more
difficult to explore application flaws as well as packaging flaws.
Many network application security solutions
never meet the purposes for which they were designed because they are
too complex or require too much maintenance. AppArmor,
on the other hand, is designed to get you started quickly with minimal
investment in time and resources. Its name-based access-control method
does not require relabeling of the file system as other methods do,
and applications don't have to be modified to benefit from AppArmor
protection. In addition, the default configuration of AppArmor includes
a number of predefined profiles for common Linux programs like Web,
e-mail and remote-login servers that can be deployed immediately. Security
profiles for custom or third-party applications can be developed using
the included wizard-based tools, which also make policy updates simple
as your environment change.
SUSE Linux Enterprise includes AutoYast, a tool similar to Jumpstart
in Solaris and Kickstart in Red Hat. It can help to deploy a custom configuration
across multiple machines. Documentation for AutoYast is weak and inconsistent.
Even Yast documentation is not that good probably because this is a moving
target.
OpenSuse is essentially an open beta of enterprise desktop. It is adequate
as pilot/experimentation OS and does not require a Novell license. Free
security patches are provided for two years which is a serious advantage
over Fedora. You can configure automatic patching or download patches
manually from
http://download.suse.com/update/10.2/
See also Package Repositories
- OpenSuse
YAST2 is dual purpose
software. It is simultaneously GUI installer and configuration tool. As
a configuration tool it looks superficially similar to Microsoft control
Panel: a single application that supposedly can help to configure almost
any aspect of the system, including such things as software installation,
services configuration, sharing files or configuring the external devices.
When it works it's OK (and actually hardware detection is really good
-- no complain here -- and this really matters). Interface (not mix with
functionality) is another story and it can be better. But when it does not
the quality of diagnostics is sometimes problematic. In a few cases is can
be misleading. My recommendation would be to try command line version of
YAST which sometimes provides more helpful diagnostics.
There is also a X-Window configuration tool — SaX2. It gives ability
to choose graphic card, set resolution, color depth etc. Please note
that Suse sometimes set refresh rate for monitors too high.
Notes:
- This is a Spartan WHYFF (We Help
You For Free) site written by people for whom English
is not a native language.
Some amount of grammar and spelling errors should be
expected.
- The site contain some broken links
as it develops like a living tree...
Please try to use Google, Open directory,
etc. to find a replacement link (see
HOWTO search the WEB for details). We would appreciate
if you can
mail us a correct link.
|
|
|
|
| 2016 |
2015 |
2014 |
2013 |
2012 |
2011 |
2010 |
2009 |
2008 |
2007 |
By Mohamed El-Erian
Last Updated: 9:09PM BST 30 May 2009
Comments
1 |
Over the last few weeks, and especially last week, we have witnessed
dramatic moves in a market that is central to many financial and economic
activities around the world.
On Wednesday alone, the yield on the 10-year bond surged by an unusual
19 basis points (to more than 3.7pc), bringing the one-month move to
almost 100 basis points. All this took place despite dramatic policy
actions to keep interest rates low, not only by anchoring the overnight
rate near 0pc but also through direct purchases of securities by the
Federal Reserve.
So, what is going on and why should investors and policymakers care?
The answer is simple yet consequential: the bond market's gyrations
are significant in terms of the causes and implications – the why and
what now. On the why, four factors are currently in play:
First, the market is coming to grips with the US Treasury's bond
issuance plan which involves a massive jump on account of the country's
stimulus package, the funding of multiple emergency facilities, and
compensating for the recession's impact on tax collections.
The amounts involved are huge, whether you use absolute, relative
or historical metrics. As an illustration, just look at the error term
we attach to our 12-month issuance projection:
+/- $500bn (£309bn) around a central forecast of $2 trillion. The error
term is bigger than the largest 12-month issuance in history.
Second, the market is internalising the Treasury's desire to reverse
a trend that has seen the average life of its outstanding debt fall
to just 48 months. Such a low level has not been recorded since the
beginning of the 1980s. It is not a good position to be in on the eve
of an era of major debt issuance. If the low average debt maturity is
not addressed, look for an increase in the government's vulnerability
to re-financing risks.
Third, there is concern about a potential deterioration in inflationary
expectations notwithstanding the fact that the country is still mired
in recession. This has technical, political and economic dimensions.
Markets have started to recognise that it will not be easy for any
future government to drain the enormous amount of emergency liquidity
that is being pumped into the system. History is full of examples where,
facing various uncertainties and resistance, governments overstay their
presence in the emergency mode.
Technically, it is very difficult to determine with confidence whether
the economy is ready for a withdrawal of emergency support. As a result,
once committed to the task of stabilisation, governments can end up
doing too much rather than too little. Then there is the political angle.
It is difficult to say "no more" to sectors that benefit from subsidised
funds.
Markets are also starting to realise that the speed limit for sustainable
US economic growth is coming down as credit contracts, saving behaviour
changes, and regulation increases. Put all this together and you come
to a simple conclusion: inflationary pressures will take hold well before
what would be expected based on recent historical experience based on
"output gap" analyses.
Finally, S&P's announcement earlier this month that put the UK's
AAA rating on negative outlook is a reminder that the sovereign risk
of the US could eventually also be in play. And this is more than a
US issue. It is an uncomfortable possibility for all those large holders
of US debt around the world that had been attracted by the US dollar's
role as the world's reserve currency, and by the depth and predictability
of US financial markets
The Treasury bond sell-off is now putting pressures on other markets
in the economy. We should worry most about housing where borrowing rates
are rising notwithstanding the Federal Reserve purchase programme. Indeed,
according to data released on Thursday, already 12pc of US households
are facing difficulties meeting their mortgage payments.
Housing is still central to the stabilisation and eventual recovery
of the US and global economies. Any further decline in house prices
will erode the collateral many Americans borrowed against, dampen their
already-fragile consumption appetite, and increase the headwinds facing
a banking system that is finally regaining its footing. The US can ill-afford
a further sell-off in US bonds at this stage in the economy's rehabilitation
process. Yet there is no easy way for policymakers to address this challenge.
As an illustration, consider the dilemma facing the Federal Reserve.
Should the central bank step up its purchases of both Treasuries and
mortgages in order to stabilise interest rates, but at the risk of adding
to the distortions in these markets; or should it refrain from intervening
further and risk a return of widespread economic and financial disruptions?
I suspect that, when push comes to shove, policymakers will opt for
greater purchases of mortgages and Treasuries – not because they really
want to, but because the alternative is viewed as worse.
Believe it or not, there is a silver lining in all this. As they
contemplate this difficult situation, they can draw some comfort from
one thing: with the anchoring of the short-term policy rate near 0pc,
the steepening of the yield curve is generating significant profits
for banks.
Remember, banking is fundamentally about mobilising cheap deposits
(at the short end of the curve) and, supported by deposit insurance
and central bank liquidity windows, lending at the longer-end of the
yield curve. Come to think of it, the smartest trade for investors today
is to find a bank that, unencumbered by legacy issues, is able to take
advantage of an enormously attractive environment for old-style banking.
Mohamed El-Erian is chief executive of Pimco. His bestselling
book, When Markets Collide: Investment Strategies for the Age of Global
Economic Change, won the 2008 FT/Goldman Sachs Business Book of the
Year. This article contains the current opinions of the author but not
necessarily those of Pimco.
InternetNews.com
"We have invested heavily in our Linux business to gain
market share and acquire new customers," Novell CFO Dana Russell said
on the company's quarterly conference call last night. "While the business
is not yet profitable, we are making steady progress and plan for it
to be break-even no later than 12 to 18 months from today."
Novell entered the Linux business in 2003 with the
acquisition
of SUSE Linux for $210 million and
Linux desktop vendor Ximian.
Novell reported its second quarter fiscal 2009 results
after the market close yesterday, with net revenue for the quarter coming
in at $216 million, a decline from the $236 million reported for the
second quarter of 2008 and just below Wall Street estimates.
Kiwi is one of the tools used by the openSUSE Build Service, a complete
distribution development platform that allows you to create and release
software for openSUSE and other Linux distributions.
Kiwi focuses on openSUSE itself, allowing you to do the following:
- Create a custom, bootable live CD/DVD image of the openSUSE
distribution, containing only the packages you want or need.
- Build a bootable USB image.
- Create Xen, VMware or QEMU virtual machine images, complete
with configuration files.
- Convert (migrate) your own installation into a deployable image
of any kind.
We've already seen most of these cool tricks done:
- We've had
Remastersys,
which runs on Debian-based distros and can convert your physical
installation into a bootable .iso image, whether to be used for
backup or distributed as a live CD/DVD.
- We've had remaster-on-the-fly, in
PCLinuxOS, which does the same as Remastersys.
- We've had QEMU at work, converting VMware hard disks (.vmdk)
disks into Amazon Elastic Compute Cloud (EC2) images (.ami), as
covered in
this
tutorial.
- We've learned how to clone VMware
Server and
ESXi virtual machines.
- We've had
VMware Converter doing lots of wonders, creating all sorts of
images.
Still, some of these phenomenal solutions did not provide us with
everything we need. For instance, Remastersys does not create virtual
machines, only images that you can use to install as guest operating
systems. But this requires extra work and user interaction. Amazon conversion
was neat, but this was mainly a command-line work, with quite a few
preparatory steps and lots of user interaction. VMware Converter provided
us with an almost the entire solution that we need here.
Kiwi can do all of the above - and then some.
that's a very useful trick: single init=/bin/sh. It works also
with grub.
Resetting a forgotten root password
To perform system administration tasks, you have
to know the root password. What happens if you
forget the root password? Not to worry: Just
reboot the PC and you can reset the root password
by following these steps:
1. Reboot the PC (select Reboot as
you log out of the GUI screen) or power up as usual.
Soon you see the graphical boot
screen that shows the names of the operating systems
you can boot. The text cursor rests on a line labeled
Boot Options.
2. If you have more than one operating
system installed, use the arrow key to select SUSE Linux
as your operating system.
3. Type the following and then press
Enter:
single init=/bin/sh
Linux starts up as usual but
runs in a single-user mode that does not require you
to log in. After Linux starts, you see the following
command line prompt that ends with a hash mark (#),
similar to the following:
sh-3.00#
4. Type the following command, and
then press Enter:
mount / -n -o remount,rw
This makes the root file system
— the forward slash (/) in the mount command — writeable
so that you can change the password (which is stored
in a file in the root file system).
5. Type the passwd command to change
the root password as follows:
sh-3.00# passwd
Changing password for user root.
New password:
6. Type the new root password that
you want to use (it doesn't appear on-screen), and then
press Enter.
The passwd command asks for
the password again, like this:
Re-enter new password:
7. Type the password again, and press
Enter.
If you enter the same password
both times, the passwd command changes the root password.
8. Type the following command and
press Enter.
mount / -n -o remount,ro
This remounts the root file
system in a read-only mode.
9. Now type /sbin/reboot to reboot
the PC.
After SUSE Linux restarts, you
can again become root by typing su - and entering the
new password. When GUI utilities such as YaST prompt
for the root password, enter the new root password.
Make sure that your SUSE Linux PC
is physically secure. As these steps show, anyone who
can physically access your SUSE Linux PC can simply
reboot, set a new root password, and do whatever
they want with the system.
See also KleanSweep:
http://www.kde-apps.org/content/show.php?content=28631
BleachBit is a simple cool utility to delete unnecessary files on
the systemt to free disk space. This includes
application and browser cache, temporary fiiles and
cookies. Among the many supported application files are Bash, Beagle,
Epiphany, firefox, Adobe flash,
java, KDE, openoffice,Opera, XChat, rpmbuild etc.
While, DIsk space may not be an issue these days on most of the
systems, it is always cool clear those items not required
anymore on the system.
Novell has one three major disk imaging solutions on the market...
Step 1: Prepare the USB Hard drive for use with ZENworks Imaging
- The first step in this is to create an ext2fs partition on the
external hard drive. This is to get over the 2GB file-size limitation
Linux has on Fat 32 partitions. To do this I used the GParted utility
in the System Rescue CD. An ISO and further instructions for use
can be found here.
- Boot to the CD.
- Type startx to bring up the graphical interface.
- Double-click on the highlighted icon on the right side of the
screen to open the gparted partitioning tool.
- You should create and format a partition at least as big as
the image you want to create. I would suggest a minimum of 30Gb
to give you plenty of space, the rest of the disk can be partitioned
and formatted as NTFS/Fat32 and used with your Windows PC without
affecting the ZENworks images.
Step 2: Mount the USB Hard Drive Within the ZENworks Boot CD environment
- Attach your USB Hard Drive to the PC you want to image.
- Insert ZENworks 7 Boot CD and restart the PC.
- When prompted, select Manual Mode and boot as normal.
- Start Imaging application (img).
- Press F8 to Modify partitions. You will now see a list of devices
attached to your PC.
- Find the one that has partition type of "Linux EXT2". Take note
of this as this is the device you need to mount.
- Exit Imaging application.
- Now you need to create a mount point for the USB hard drive.
Do this by typing:
mkdir /mnt/usbhd.
- To mount the drive type the following command:
mount /dev/sdb1 /mnt/usbhd
(change /dev/sdb1 to the device you noted earlier)
- The drive is now mounted to /mnt/usbhd.
Step 3: Start Imaging to USB Hard Drive
- Type img at bash prompt to load imaging application.
- Select Make Image.
- Select Local as destination.
- Type path as /mnt/usbhd/<filename>.zmg
- Start Image creation.
Step 4: Copy Image from USB Hard Drive (optional)
- Attach the USB Hard Drive to a PC running Windows.
- Install the ext2fsd driver (which can be downloaded from
here). This will allow you
to access the ext2fs (linux) file system from Windows and copy to
another drive.
- Once loaded you can view the ext2fs file system as normal and
copy, delete, etc., from Windows Explorer.
Tabbed viewing was added
Adobe Reader 9.1 for Linux and Solaris x86 has been released today.
Solaris x86 support was one of the most requested feature by users.
As per the
Reader team's announcement, this release includes the following
major features: - Support for Tabbed Viewing (preview)
- Super fast launch, and better performance than previous
releases
- Integration with Acrobat.com
- IPv6 support
- Enhanced support for PDF portfolios (preview)
The complete list is available
here.
Adobe Reader 9.1 is now
available for download and works on OpenSolaris, Solaris 10 and
most modern Linux distributions such as Ubuntu 8.04, PCLinuxOS, Mandriva
2009, SLED 10, Mint Linux 6 and Fedora 10.
See also Sneak Preview of the Tabbed Viewing interface in Adobe
Reader 9.x (on Ubuntu)
Oracle Cluster File System 2 (OCFS2) is a general-purpose
journaling file system that is fully integrated in the Linux 2.6 kernel
and later. OCFS2 allows you to store application binary files, data
files, and databases on devices in a SAN. All nodes in a cluster have
concurrent read and write access to the file system. A distributed lock
manager helps prevent file access conflicts. OCFS2 supports up to 32,000
subdirectories and millions of files in each directory. The O2CB cluster
service (a driver) runs on each node to manage the cluster.
In SUSE Linux Enterprise Server 10 and later,
OCFS2 can be used for any of the following storage solutions:
-
Oracle RAC and other databases
-
General applications and workloads
-
XEN image store in a cluster
XEN virtual machines and virtual servers
can be stored on OCFS2 volumes that are mounted by cluster
servers to provide quick and easy portability of XEN virtual
machines between servers.
-
LAMP (Linux, Apache, MySQL, and PHP
| PERL | Python) stacks
In addition, it is fully integrated with Heartbeat
2.
As a high-performance, symmetric, parallel cluster
file system, OCFS2 supports the following functions:
-
An application’s files are available
to all nodes in the cluster. Users simply install it once
on an OCFS2 volume in the cluster.
-
All nodes can concurrently read and
write directly to storage via the standard file system interface,
enabling easy management of applications that run across
a cluster.
-
File access is coordinated through the
Distributed Lock Manager (DLM).
DLM control is good for most cases,
but an application’s design might limit scalability if it
contends with the DLM to coordinate file access.
-
Storage backup functionality is available
on all back-end storage. An image of the shared application
files can be easily created, which can help provide effective
disaster recovery.
OCFS2 also provides the following capabilities:
-
Metadata caching
-
Metadata journaling
-
Cross-node file data consistency
-
A GTK GUI-based administration via the
ocfs2console utility
-
Operation as a shared-root file system
-
Support for multiple-block sizes (each
volume can have a different block size) up to 4 KB, for
a maximum volume size of 16 TB
-
Support for up to 255 cluster nodes
-
Context-dependent symbolic link (CDSL)
support for node-specific local files
-
Asynchronous and direct I/O support
for database files for improved database performance
Oracle Cluster File System 2 (OCFS2) is a general-purpose journaling
file system that is fully integrated in the Linux 2.6 kernel and later.
OCFS2 allows you to store application binary files, data files, and
databases on devices in a SAN. All nodes in a cluster have concurrent
read and write access to the file system. A distributed lock manager
helps prevent file access conflicts. OCFS2 supports up to 32,000 subdirectories
and millions of files in each directory. The O2CB cluster service (a
driver) runs on each node to manage the cluster.
13.1.1 Features and Benefits
In August 2005, OCFS2 was added to SUSE Linux Enterprise Server
9 to support Oracle Real Application Cluster (RAC) databases and
Oracle Home (its application files). In SUSE Linux Enterprise Server
10 and later, OCFS2 can be used for any of the following storage
solutions:
-
Oracle RAC and other databases
-
General applications and workloads
-
XEN image store in a cluster
XEN virtual
machines and virtual servers can be stored on OCFS2 volumes
that are mounted by cluster servers to provide quick and
easy portability of XEN virtual machines between servers.
-
LAMP (Linux, Apache, MySQL, and PHP
| PERL | Python) stacks
In addition, it is fully integrated with Heartbeat 2.
As a high-performance, symmetric, parallel cluster file system,
OCFS2 supports the following functions:
-
An application’s files are available
to all nodes in the cluster. Users simply install it once
on an OCFS2 volume in the cluster.
-
All nodes can concurrently read and
write directly to storage via the standard file system interface,
enabling easy management of applications that run across
a cluster.
-
File access is coordinated through the
Distributed Lock Manager (DLM).
DLM control is good for most cases,
but an application’s design might limit scalability if it
contends with the DLM to coordinate file access.
-
Storage backup functionality is available
on all back-end storage. An image of the shared application
files can be easily created, which can help provide effective
disaster recovery.
OCFS2 also provides the following capabilities:
-
Metadata caching
-
Metadata journaling
-
Cross-node file data consistency
-
A GTK GUI-based administration via the
ocfs2console utility
-
Operation as a shared-root file system
-
Support for multiple-block sizes (each
volume can have a different block size) up to 4 KB, for
a maximum volume size of 16 TB
-
Support for up to 255 cluster nodes
-
Context-dependent symbolic link (CDSL)
support for node-specific local files
-
Asynchronous and direct I/O support
for database files for improved database performance
SUSE Linux Enterprise Server 11 was released on March 24, 2009 and include
Linux kernel 2.6.27,
Oracle Cluster File System 2, support for the
OpenAIS cluster communication protocol for server and storage clustering,
and
Mono 2.0.
Meanwhile, Novell is also hoping to rev up the application market
around its OS, with SUSE Linux Enterprise JeOS (just enough operating
system), which ISVs can use along with a
set of
tools called
Suse Studio, to package their products as virtual appliances.
Novell has a "supportability algorithm" for vetting appliances; those
that pass muster will receive technical support from Novell
Perl-based
freshmeat.net
Cluster SSH opens terminal windows with connections to specified
hosts and an administration console. Any text typed into the administration
console is replicated to all other connected and active windows.
This tool is intended for, but not limited
to, cluster administration where the same configuration or commands
must be run on each node within the cluster. Performing
these commands all at once via this tool ensures all nodes are kept
in sync.
See also:
Software Distribution, Enterprise Unix
System Administration
Problem:
As an administrator of SLES/OES Linux clusters or multiple SUSE Linux
servers you are probably familiar with that fact that you have to make
an identical change on more than one server. Those can be things like
editing files, execute commands, collect data or some other administrative
task.
There are a couple of way to do this. You can write a script that
performs the change for you, or you can SSH into a server, make the
change and repeat that task manually for every server.
Now both ways can cost an extended amount of time. Writing and testing
a shell script takes some time and performing the task by hand on lets
say five or more servers also costs time.
Now, wouldn't it be a real timesaver when you have only one console
in which you can perform tasks on multiple servers simultaneously? This
solution can be found in ClusterSSH.
Solution:
With ClusterSSH it is possible to make a SSH connection to multiple
servers and perform tasks from one single
command window, without any scripting. The 'cssh' command
lets you connect to any server specified as a command line argument,
or to groups of servers (or cluster nodes)
defined in a configuration file.
The 'cssh' command opens a terminal window to every server which
can be used to review the output sent from the cssh-console, or to edit
a single host directly. Commands given in to the cssh-console are executed
on every connected host. When you start typing in the cssh-console you'll
see that the same command also show up on the commandline of the connected
systems.
The state of connected systems can be toggled from the cssh-console.
So if you want to exclude certain hosts temporarily from specific command,
you can do this with a single mouseclick. Also, hosts can be added on
the fly and open terminal windows can automatically be rearranged.
One caveat to be aware of is when editing files. Never assume that
file is identical on all systems. For example, lines in a file you are
editing may be in a different order. Don't just go to a certain line
in a file and start editing. Instead search for the text you want to
exit, just to be sure the correct text is edited on all connected systems.
Example:
Configuration files section from the man-page:
/etc/clusters
This file contains a list of tags to server names mappings. When
any name is used on the command line it is checked to see if it is a
tag in /etc/clusters (or the .csshrc file, or any additional cluster
file specified by -c). If it is a tag, then the tag is replaced with
the list of servers from the file. The file is formatted as follows:
<tag> [user@]<server> [user@]<server> [...]
i.e.
# List of servers in live
live admin1@server1 admin2@server2 server3 server4
Clusters may also be specified within the users .csshrc file, as
documented below.
/etc/csshrc & $HOME/.csshrc
This file contains configuration overrides - the defaults are as
marked. Default options are overwritten first by the global file, and
then by the user file.
Environment:
ClusterSSH can be used to any system running the SSH daemon.
See also: Software
Distribution, Enterprise Unix System
Administration
- MySQL 5 Installation
- Prerequisites
- Download the Source
- Unpack, Copy, Configure
- Create my.cnf File
- Additional Settings
- Start Server, Check It, Connect
- Set the Root Password
- Restart MySQL Server
- Automatic Startup
- Apache
2 Installation
- PHP 5
Installation
If you've ever typed a command at the Linux shell
prompt, you've probably already used bash -- after all, it's the default
command shell on most modern GNU/Linux distributions.
The bash shell is the primary interface to the Linux operating system
-- it accepts, interprets and executes your commands, and provides you
with the building blocks for shell scripting and automated task execution.
Bash's unassuming exterior hides some very powerful tools and shortcuts.
If you're a heavy user of the command line, these can save you a fair
bit of typing. This document outlines 10 of the most useful tools:
- Easily recall previous commands
Bash keeps track of
the commands you execute in a history buffer, and allows you to
recall previous commands by cycling through them with the Up and
Down cursor keys. For even faster recall, "speed search" previously-executed
commands by typing the first few letters of the command followed
by the key combination Ctrl-R; bash will then scan the command history
for matching commands and display them on the console. Type Ctrl-R
repeatedly to cycle through the entire list of matching commands.
- Use command aliases
If you always run a command with the same set of options, you
can have bash create an alias for it. This alias will incorporate
the required options, so that you don't need to remember them or
manually type them every time. For example, if you always run ls
with the -l option to obtain a detailed directory listing, you can
use this command:
bash> alias ls='ls -l'
To create an alias that automatically includes the -l option.
Once this alias has been created, typing ls at the bash prompt will
invoke the alias and produce the ls -l output.
You can obtain a list of available aliases by invoking alias
without any arguments, and you can delete an alias with unalias.
- Use filename auto-completion
Bash supports filename
auto-completion at the command prompt. To use this feature, type
the first few letters of the file name, followed by Tab. bash will
scan the current directory, as well as all other directories in
the search path, for matches to that name. If a single match is
found, bash will automatically complete the filename for you. If
multiple matches are found, you will be prompted to choose one.
- Use key shortcuts to efficiently edit the command line
Bash supports a number of keyboard shortcuts for command-line navigation
and editing. The Ctrl-A key shortcut moves the cursor to the beginning
of the command line, while the Ctrl-E shortcut moves the cursor
to the end of the command line. The Ctrl-W shortcut deletes the
word immediately before the cursor, while the Ctrl-K shortcut deletes
everything immediately after the cursor. You can undo a deletion
with Ctrl-Y.
- Get automatic notification of new mail
You can configure
bash to automatically notify you of new mail, by setting the $MAILPATH
variable to point to your local mail spool. For example, the command:
bash> MAILPATH='/var/spool/mail/john'
bash> export MAILPATH
Causes bash to print a notification on john's console every time
a new message is appended to John's mail spool.
- Run tasks in the background
Bash lets you run one or
more tasks in the background, and selectively suspend or resume
any of the current tasks (or "jobs"). To run a task in the background,
add an ampersand (&) to the end of its command line. Here's an example:
bash> tail -f /var/log/messages &
[1] 614
Each task backgrounded in this manner is assigned a job ID, which
is printed to the console. A task can be brought back to the foreground
with the command fg jobnumber, where jobnumber
is the job ID of the task you wish to bring to the foreground. Here's
an example:
bash> fg 1
A list of active jobs can be obtained at any time by typing jobs
at the bash prompt.
- Quickly jump to frequently-used directories
You probably
already know that the $PATH variable lists bash's "search path"
-- the directories it will search when it can't find the requested
file in the current directory. However, bash also supports the $CDPATH
variable, which lists the directories the cd command will look in
when attempting to change directories. To use this feature, assign
a directory list to the $CDPATH variable, as shown in the example
below:
bash> CDPATH='.:~:/usr/local/apache/htdocs:/disk1/backups'
bash> export CDPATH
Now, whenever you use the cd command, bash will check all the
directories in the $CDPATH list for matches to the directory name.
- Perform calculations
Bash can perform simple arithmetic
operations at the command prompt. To use this feature, simply type
in the arithmetic expression you wish to evaluate at the prompt
within double parentheses, as illustrated below. Bash will attempt
to perform the calculation and return the answer.
bash> echo $((16/2))
8
- Customise the shell prompt
You can customise the bash
shell prompt to display -- among other things -- the current username
and host name, the current time, the load average and/or the current
working directory. To do this, alter the $PS1 variable, as below:
bash> PS1='\u@\h:\w \@> '
bash> export PS1
root@medusa:/tmp 03:01 PM>
This will display the name of the currently logged-in user, the
host name, the current working directory and the current time at
the shell prompt. You can obtain a list of symbols understood by
bash from its manual page.
- Get context-specific help
Bash comes with help for
all built-in commands. To see a list of all built-in commands, type
help. To obtain help on a specific command, type help command,
where command is the command you need help on. Here's an
example:
bash> help alias
...some help text...
Obviously, you can obtain detailed help on the bash shell by
typing man bash at your command prompt at any time.
Configuration Steps
-
Connect a null
modem cable between the system that will act as the console and
the server. Refer to the Wikipedia article
Null modem for details,
including pin mapping.
-
If the server's BIOS supports serial console, configure the BIOS
for it. The details of this procedure are dependent on the BIOS
vendor - refer to vendor documentation.
- Configure GRUB
on the server to use the first serial port. In the file
/boot/grub/menu.lst,
comment out the
color
and gfxmenu
lines and add the following lines:
serial --unit=0 --speed=115200
terminal --timeout=15 serial console
- Configure the
kernel (and hypervisor) on the server to use the serial port.
This configuration differs between Xen setups and non-Xen setups.
Non-Xen setup
In the file /boot/grub/menu.lst,
add the following options to the kernel command line:
console=tty0 console=ttyS0,115200
Kernel messages will be written to both
tty0
and ttyS0,
but OS messages will only be written to
ttyS0.
OS messages go to the last console defined on the boot options line.
A sample /boot/grub/menu.lst
file illustrating these changes:
#color white/blue black/light-gray
default 0
timeout 8
#gfxmenu (hd0,1)/boot/message
serial
--unit=0 --speed=115200
terminal
--timeout=15 serial console
title Linux
! SERIAL CONSOLE !
kernel (hd0,1)/boot/vmlinuz
root=/dev/sda3 selinux=0 splash=0 resume=/dev/sda1 showopts
elevator=cfq vga=791 console=tty0
console=ttyS0,115200
initrd (hd0,1)/boot/initrd
Xen setup
When Xen virtualization is used, both the Xen hypervisor and the
Dom0 kernel need to be instructed to use the serial connection:
- Add
console=vga,com1
com1=115200 to the parameters for
the hypervisor.
- Add console=tty0
console=xvc0,115200 to the parameters
for the Dom0 kernel.
A sample /boot/grub/menu.lst
file illustrating these changes:
#color white/blue black/light-gray
default 0
timeout 8
#gfxmenu (hd1,0)/boot/message
serial --unit=0
--speed=115200
terminal
--timeout=15 serial console
title Linux - Xen
! SERIAL CONSOLE !
kernel (hd0,1)/boot/xen.gz
console=vga,com1 com1=115200
module (hd0,1)/boot/vmlinuz
root=/dev/sda3 console=tty0
console=xvc0,115200
module (hd0,1)/boot/initrd
Configure the server to allow logins
over the serial connection. In the file
/etc/inittab,
add the following line.
S0:12345:respawn:/sbin/agetty
-L 115200 console vt102
To allow single-user mode to work using the serial connection, additionally
change the line
~~:S:respawn:/sbin/sulogin
in /etc/inittab
to
~~:S:respawn:/sbin/sulogin
/dev/console
NOTE: Single-user mode will
only work on the serial console with this option. You will need
to change it back, to run on the local console.
Configure the
serial port on the server as a secure port, so a login as
root
is possible on it without the need to log in as a regular user first.
Add lines
console
ttyS0
xvc0
to the file /etc/securetty
Ensure the
package screen
is installed on the server; this will be used later on to send
control sequences to it.
FSlint is a simple yet very easy to use utility to
find and clean various forms of lint on a filesystem. i.e., unwanted
or problematic cruft in your files or file names. For example, one form
of lint it finds is duplicate files. FSlint operates in both GUI and
Command Line mode and the GUI is very straight forward to use especially
there isn’t much of hidden menu options.
FSlint basically checks if sizes are same, files are not hardlinked
to each other, md5sums are the same, sha1sums are the same (in case
of md5 collisions).
"Novell just released the
first alpha
of SUSE Studio (screencast),
which provides an easy way to customize your own Linux distribution
with the software and configuration you want. Among other things, you
can spin a Live CD, a USB image, or create a VMware image. It builds
upon the already established
openSUSE Build Service
and KIWI imaging system."
Problem:
As an administrator of SLES/OES Linux clusters or multiple SUSE Linux
servers you are probably familiar with that fact that you have to make
an identical change on more than one server. Those can be things like
editing files, execute commands, collect data or some other administrative
task.
There are a couple of way to do this. You can write a script that
performs the change for you, or you can SSH into a server, make the
change and repeat that task manually for every server.
Now both ways can cost an extended amount of time. Writing and testing
a shell script takes some time and performing the task by hand on lets
say five or more servers also costs time.
Now, wouldn't it be a real timesaver when you have only one console
in which you can perform tasks on multiple servers simultaneously? This
solution can be found in ClusterSSH.
Solution:
With ClusterSSH it is possible to make a SSH connection to multiple
servers and perform tasks from one single command window, without any
scripting. The 'cssh' command lets you connect to any server specified
as a command line argument, or to groups of servers (or cluster nodes)
defined in a configuration file.
The 'cssh' command opens a terminal window to every server which
can be used to review the output sent from the cssh-console, or to edit
a single host directly. Commands given in to the cssh-console are executed
on every connected host. When you start typing in the cssh-console you'll
see that the same command also show up on the commandline of the connected
systems.
The state of connected systems can be toggled from the cssh-console.
So if you want to exclude certain hosts temporarily from specific command,
you can do this with a single mouseclick. Also, hosts can be added on
the fly and open terminal windows can automatically be rearranged.
One caveat to be aware of is when editing files. Never assume that
file is identical on all systems. For example, lines in a file you are
editing may be in a different order. Don't just go to a certain line
in a file and start editing. Instead search for the text you want to
exit, just to be sure the correct text is edited on all connected systems.
Example:
Configuration files section from the man-page:
/etc/clusters
This file contains a list of tags to server names mappings. When
any name is used on the command line it is checked to see if it is a
tag in /etc/clusters (or the .csshrc file, or any additional cluster
file specified by -c). If it is a tag, then the tag is replaced with
the list of servers from the file. The file is formatted as follows:
<tag> [user@]<server> [user@]<server> [...]
i.e.
# List of servers in live
live admin1@server1 admin2@server2 server3 server4
Clusters may also be specified within the users .csshrc file, as
documented below.
/etc/csshrc & $HOME/.csshrc
This file contains configuration overrides - the defaults are as
marked. Default options are overwritten first by the global file, and
then by the user file.
Environment:
ClusterSSH can be used to any system running the SSH daemon.
Probably does not make much sense but Perl codebase might be reused.
Posted by admin on October 4th, 2008
rsnapshot is a filesystem backup utility based on rsync.
Using rsnapshot, it is possible to take snapshots of your filesystems
at different points in time. Using hard links, rsnapshot creates the
illusion of multiple full backups, while only taking up the space of
one full backup plus differences. When coupled with ssh, it is possible
to take snapshots of remote filesystems as well.
rsnapshot is written in Perl, and depends on rsync. OpenSSH, GNU
cp, GNU du, and the BSD logger program are also recommended, but not
required. rsnapshot is written with the lowest common denominator in
mind. It only requires at minimum Perl 5.004 and rsync. As a result
of this, it works on pretty much any UNIX-like system you care to throw
at it.
rsnapshot can run almost out of the box with very little configuration
changes although advanced configurations can be done with little more
effort.
aMSN is a free open source MSN Messenger clone for
Windows, Linux, Unix & Mac
Some of the Features include,
Offline Messaging
Voice Clips
Display pictures
Custom emoticons
Multi-language support (around 40 languages currently supported)
Webcam support
Sign in to more than one account at once
Full-speed File transfers
Group support
Normal, and animated emoticons with sounds
Chat logs
Timestamping
Event alarms
Conferencing support
Tabbed chat windows
Things go wrong. Hard disks fail and whole servers crash. Luckily, many
Linux-based distributions are available to help systems administrators
handle minor catastrophes. We looked at four of the most portable, all
of which fit on a 210MB mini CD -- SliTaz, Parted Magic, GParted, and
RIPLinuX.
Each of these distributions is easy to use -- just insert the CD
or plug in the USB drive on which it's installed, then boot. Each gives
you access to a variety of open source tools that you can use to manage
disks, partitions, and files and perform diagnostics and network troubleshooting.
These distributions provide most of the tools that you might need in
an emergency situation.
To choose the most appropriate sysadmin distribution, you have to
consider several factors. One is the supported boot devices. Most distributions
can boot and run from a live CD, but you may want the flexibility of
being able to boot from a USB device or even network Preboot eXecution
Environment (PXE). Another factor is size: can it fit onto a 128MB USB
drive or a mini CD, or do you need a DVD? If you like a smaller distribution,
make sure that it holds all the tools and utilities you need. Lastly,
consider usability. Does the distro offers tools that have a GUI, or
only those you can use from the command line? The CLI may not pose a
problem for system administrators, but a GUI may expedite the solution
and increase the user base of the distribution, often resulting in greater
support and more frequent updates.
Parted Magic
,,,
,,, ,,.
Parted Magic
is a Linux From Scratch
(LFS) distribution, and only 45MB in size. The latest version, 3.0,
runs on the 2.6.26 kernel. You can boot and run it using a live CD,
USB, or even PXE. It features an aesthetically pleasing GUI based on
Xfce. However, be wary of its memory requirements. The latest version
removed the live boot option, so the whole distribution is loaded into
memory. You must have at least 300MB of RAM. Failure to meet this minimum
requirement will result in problems loading Parted Magic. You may not
be able to load all the programs, and even if you can, you might not
have access to the graphical desktop.
This distribution's primary component is the popular GParted tool,
but it also includes the data recovery tools
TestDisk and PhotoRec, as well as a disk imaging program
called Partition Image. Other tools include Xarchiver for viewing and
extracting archives,
- Xfburn for CD burning,
- ISO Master for creating ISO images.
- Use the graphical Leafpad for text editing,
- the latest version of Firefox (3.0.1) for Internet browsing,
- Grsync for backing up data.
Parted Magic includes several command-line tools; most are disk related
and include dd, ddrescue (for disk recovery), cfdisk, and fdisk. The
variety of disk tools enables Parted Magic to support many file systems,
including ext2, ext3, ext4, FAT16, FAT32, HFS, HFS+, JFS, Linux swap,
NTFS, ReiserFS, Reiser4, and XFS. It includes some advanced network
tools too, such as tcpdump.
Parted Magic is a great distribution for its intended purpose: filesystem
and partition management, manipulation, and recovery. Its GUI makes
it easy for average users and system administrators alike to perform
disk-related tasks.
GParted Live
GParted Live
is a Debian-based distribution from the
GParted team. The latest
version is 0.3.7-7, running on the 2.6.24 kernel, and is only 90MB in
size. You can boot and run it via live CD, USB, or PXE, and you can
even install it on a hard disk. You will need a Pentium II or higher
and at least 64MB of RAM, with 128MB recommended.
GParted's boot menu is simple and mostly related to the type of video
display. Like other live CD sysadmin distributions, it offers Memtest86+
as a choice in the boot menu. Upon boot, it asks you about the keyboard
type you'll be using.
GParted Live's graphical desktop is simple and shows a shortcut to
the GParted tool on the desktop. It utilizes a Fluxbox menu in which
you can run other disk programs and editing tools. The Fluxbox menu
has a limited set of tools:
- Vim and nano for text editing,
- GNU Midnight Commander for file management,
- Partition Image for imaging,
- TestDisk for partition recovery, and PhotoRec for file recovery.
As with Parted Magic, you can access other disk tools using the CLI.
An extensive collection of tools enables GParted Live to support the
same filesystems as Parted Magic, and a shortcut for live USB creation
is also available on the desktop. However, unlike Parted Magic, GParted
Live doesn't have network support. This means it's missing Internet
browsers, commands like ping and netstat, and features like rsync and
Grsync, because they're dependent on a network connection. Likewise,
the distribution offers no CD-burning software.
With no network support or ability to burn data on a CD, GParted
is designed solely for partition management and manipulation on a local
machine. You can recover data, but you need a locally accessible device,
such as another hard disk or an external drive, to save the recovered
data.
If you're concerned only with disk partitioning and related tasks,
GParted Live is easy enough to use for both system administrators and
average users. However, if you're able to meet its higher memory requirements,
Parted Magic may be a better way to go.
A lazy sysadmin is a good sysadmin. Time spent in finding more-efficient
shortcuts is time saved later on for that ongoing project of "reading
the whole of the internet", so try Juliet Kemp's 10
handy tips to make your admin life easier...
- Cache your password with ssh-agent
- Speed up logins using Kerberos
- screen: detach to avoid repeat logins
- screen: connect multiple users
- Expand Bash's tab completion
- Automate your installations
- Roll out changes to multiple systems
- Automate Debian updates
- Sanely reboot a locked-up box
- Send commands to several PCs
In this situation you need to switch to update from DVD. That usually
helps. Otherwise you need to reregister your suse system and retry again.
On a test device that has been patched up to SP2, SPident still reports
this:
dss-cs99la03:/var/opt/novell/log # SPident
CONCLUSION: System is NOT up-to-date!
found SLE-10-i386 + "online updates"
expected SLE-10-i386-SP2
---
SuSE-release thinks I'm on SP1, so it's all out of whack.
dss-cs99la03:/var/opt/novell/log # cat /etc/SuSE-release
SUSE Linux Enterprise Server 10 (i586)
VERSION = 10
PATCHLEVEL = 1
---
How is this all determined by SLES?
Ryan,
first you need to load the full sp2 distribution media using the zlmload
tool into a single zlm bundle. The zlmload is available here:
ZLMLoad 1.4 | Novell User Communities
a sample command line:
# zlmload -P password -d /install/sles10sp2 -b SLES10-SP2-i586-DIST
-a sles-10-i586
/install/sles10sp2 was where the extracted sp2 iso was at that time
After you have that single bundle, add it to a catalog and assign it
to the device you want to update. Next refresh that device, subscribe
to the catalog and run "rug up". That should bring you up to sp2. If
you want to install the post sp2 updates as well, assign that catalog
also during that time and then you will have a fully pachted system.
Rainer
rsmccain Junior Member Join Date: Jul 2008
Posts: 28
No luck attempting to patch SLED 10 device Here's
the steps I followed........................
I download SLED-10-SP1-x86-DVD1.iso here:
NOVELL: Downloads
Next, I mount the .iso to /media/iso and run zlmload:
dss-cs99la36:# zlmload -P foo -b SLED10-x86-SP1-ZLMLOAD -a sles-10-i586
-d /media/iso
As you can see, I have the correct ISO:
dss-cs99la36:# cat /media/iso/content
PRODUCT SUSE_SLED_SP1
VERSION 10.1-0
DISTPRODUCT SUSE-Linux-Enterprise-Desktop-SP1
DISTVERSION 10-SP1
VENDOR SUSE LINUX Products GmbH, Nuernberg, Germany
RELNOTESURL
http://www.novell.com/linux/releasen...notes-sled.rpm
ARCH.i686 i686 i586 i486 i386 noarch
ARCH.i586 i586 i486 i386 noarch
ARCH.i486 i486 i386 noarch
ARCH.i386 i386 noarch
DEFAULTBASE i586
REQUIRES sled-release-10-sp1 pattern:basesystem
PROVIDES product:SUSE_SLED = 10.1
PROVIDES product:SUSE_SLE = 10.1
PATTERNS desktop-base x11 desktop-gnome apparmor 32bit
OBSOLETES product:SUSE_SLED < 10.1
SHORTLABEL SLED 10 SP1
LABEL SUSE Linux Enterprise Desktop 10 SP1 10.1-0
LABEL.de SUSE Linux Enterprise Desktop 10 SP1
DESCRDIR suse/setup/descr
DATADIR suse
FLAGS update
LANGUAGE en_US
TIMEZONE America/Los_Angeles
--SNIP--
This creates the bundle fine. I then create an empty catalog, then assign
this bundle to it and name the catalog 'SLED10-x86-SP1-ZLMLOAD.' I then
assign the catalog to my workstation, "3N2DHB1".
This is from my workstation:
3N2DHB1:/tmp/zlm # SPident -vv
Summary (using 1152 packages)
Product/ServicePack conflict match update (shipped)
SLE-10-i386 11 0.4% 478 41.5% 19 (2524 18.9%)
- MozillaFirefox 2.0.0.13-1.1 < 1.5.0.4-1.7
- flash-player 9.0.31.0-2.1 < 7.0.63.0-8.1
- imlib2 1.4.0-0.pm.0 < 1.2.1-17.2
- mozilla-nspr 4.7.0-7.4 < 4.6.1-22.2
- mozilla-nspr-devel 4.7.0-7.4 < 4.6.1-22.2
- mozilla-nss 3.11.9-1.2 < 3.11-21.2
- mozilla-nss-devel 3.11.9-1.2 < 3.11-21.2
- netcat 0.7.1-1.i386 < 1.10-883.2.i586
- nmap 2:4.20-1.i386 < 4.00-14.2.i586
- python-elementtree 1.2.6-18 < 1.2.6-18.2
- rpm-python 4.4.2-40 < 4.4.2-43.4
SLE-10-i386-SP1 12 0.6% 984 85.4% 5 (1948 50.5%)
- MozillaFirefox 2.0.0.13-1.1 < 2.0.0.2-2.13
- flash-player 9.0.31.0-2.1 < 9.0.31.0-1.7
- imlib2 1.4.0-0.pm.0 < 1.2.1-17.2
- mozilla-nspr 4.7.0-7.4 < 4.6.4-0.7
- mozilla-nspr-devel 4.7.0-7.4 < 4.6.4-0.7
- mozilla-nss 3.11.9-1.2 < 3.11.4-0.7
- mozilla-nss-devel 3.11.9-1.2 < 3.11.4-0.7
- netcat 0.7.1-1.i386 < 1.10-883.2.i586
- python-elementtree 1.2.6-18 < 1.2.6-18.2
- rpm-python 4.4.2-40 < 4.4.2-43.19
- rug 7.1.1.0-18.23 < 7.2.0.0-0.8
- yast2-samba-server 2.13.11-1.3 < 2.13.22-0.8
Unknown 166 14.4%
Legend for Package Details:
- conflicting package (found < expected)
CONCLUSION: No supported Product/ServicePack found at all!
(at least one conflict has been detected everywhere)
3N2DHB1:/tmp/zlm # cat /etc/novell-release
SUSE Linux Enterprise Desktop 10 (i586)
VERSION = 10
PATCHLEVEL = 1
3N2DHB1:/tmp/zlm # cat /etc/SuSE-release
SUSE Linux Enterprise Desktop 10 (i586)
VERSION = 10
PATCHLEVEL = 1
3N2DHB1:/tmp/zlm # rug ca
Sub'd? | Name | Service
-------+------------------------+--------------------------
Yes | SLED10-x86-SP1-ZLMLOAD | ZENworks Linux Management
3N2DHB1:/tmp/zlm # rug lu
No updates are available.
3N2DHB1:/tmp/zlm # rug pa SLED10-x86-SP-ZLMLOAD
WARNING: 'SLED10-x86-SP-ZLMLOAD' is not a valid catalog.
S | Catalog | Bundle | Name | Version | Arch
--+-----------------+--------+------------------------------------------+-------------------------------+-------
i | System packages | | 3ddiag | 0.735-1.5 | i586
-SNIP-
i | System packages | | imlib | 1.9.14-215.2 | i586
i | System packages | | imlib2 | 1.4.0-0.pm.0 | i586
-SNIP-
i | System packages | | MozillaFirefox | 2.0.0.13-1.1 | i586
i | System packages | | mozilla-nspr | 4.7.0-7.4 | i586
i | System packages | | mozilla-nspr-devel | 4.7.0-7.4 | i586
i | System packages | | mozilla-nss | 3.11.9-1.2 | i586
i | System packages | | mozilla-nss-devel | 3.11.9-1.2 | i586
-SNIP-
i586
i | System packages | | netcat | 0.7.1-1 | i386
i | System packages | | nmap | 4.20-1 | i386
-SNIP-
3N2DHB1:/tmp/zlm #
---
2 questions:
1) Why is it an invalid catalog?
2) Why does it not detect any updates? I guess that could be because
it's an invalid catalog.....
Thanks, Ryan
The typical situation after attempt to upgrade to SP2 is:
SPident:
CONCLUSION: System is NOT up-to-date!
found SLE-10-x86_64-SP1 + "online updates"
expected SLE-10-x86_64-SP2
Look like Novell screwed the patches database during the update to SP2
on many servers. It ian undocumented database and we are stuck with
Microsoft style situation. In this situation you need to switch to
update from DVD. That usually helps. Otherwise you need to reregister your
suse system and retry again.
zugenmaier
Junior Member Join Date: Aug 2008 Posts: 2
SP2: Broken patches & newer version installed than available
Hello,
I updated to SLES 10 SP2, and now I have "broken patches". In the
graphical GUI of Yast2, they are marked with an exclamation mark
in a triangle (road sign). The cli says "this patch is broken".
In the "add/remove software" GUI, some software packages are marked
red, and the installed version is newer than the available version.
That is the state after my own efforts to solve the problem. Before
that, it was the other way round, and the line was marked blue instead
of black. If I try to "update" these software-packages, than Yast
says, it cannot resolve the dependencies and it wants to deinstall
all dependent packages.
>SPident:
CONCLUSION: System is NOT up-to-date!
found SLE-10-x86_64-SP1 + "online updates"
expected SLE-10-x86_64-SP2
>rug sa:
Sub'd? | Name | Service
-------+-------------------------------------------------------+------------------------------------------------------
| SUSE Linux Enterprise Server 10 | SUSE Linux Enterprise Server
10
| SUSE Linux Enterprise Server 10 SP2 | SUSE Linux Enterprise Server
10 SP2
Yes | SUSE Linux Enterprise Software Development Kit 10 SP2 | SUSE
Linux Enterprise Software Development Kit 10 SP2
| SLES10-SP1-Online |
https://nu.novell.com
| SLES10-SP1-Updates |
https://nu.novell.com
| SLE10-SP1-Debuginfo-Updates |
https://nu.novell.com
| SLES10-Updates |
https://nu.novell.com
| SLE10-Debuginfo-Updates |
https://nu.novell.com
Yes | SLES10-SP2-Online |
https://nu.novell.com
Yes | SLES10-SP2-Updates |
https://nu.novell.com
| SLE10-SP2-Debuginfo-Updates |
https://nu.novell.com
>rug sl:
# | Status | Type | Name | URI
--+--------+------+-------------------------------------------------------+-----
1 | Active | ZYPP | SUSE Linux Enterprise Server 10 | i...
2 | Active | ZYPP | SUSE Linux Enterprise Server 10 SP2 | i...
3 | Active | NU |
https://nu.novell.com
| h...
4 | Active | ZYPP | SUSE Linux Enterprise Software Development Kit
10 SP2 | i...
I have a test system, where the "broken patches" problem does not
appear. I experimented a bit, but I only worsened things. ZMD is
now permanently refreshing ...
I cannot find anywhere a reasonable description of the several SUSE
updater services around ... Can anyone help?
OAKLAND, California – Linux guru and convicted murdered Hans Reiser
was handed a prison sentence of 15-to-life Friday, putting a final capstone
on a case that began as a murder mystery, and ended with Reiser leading
police to a makeshift grave a short distance from where he strangled
his wife.
"I wish to humbly apologize to society for my crime," Reiser said
in a statement before his sentence was pronounced. "Every human life
is sacred. I took the life of a human being and I'm very sorry for that."
Hans Reiser killed his wife, Nina, at about 4:30 p.m. on Sept. 3,
2006, according to the belated confession Reiser wrote as part of his
deal, said prosecutor Paul Hora after the sentencing. He first punched
her in the mouth, cutting his hand, then strangled her to death.
He briefly stored the body in the bathroom, then moved it to his
car, where it stayed for two days while he searched for a place to bury
her.
Nina Reiser, at age 31, was last seen alive at Hans Reiser's
house in the Oakland hills on the day of her murder, when she dropped
off the once-happy couple's two young children to stay with him the
Labor Day weekend. The couple were in the middle of a heated divorce.
The developer of the ReiserFS file system becomes eligible for parole
in about 13 years, having already served two years since his October
2006 arrest.
The 44-year-old defendant's jury trial here concluded in April this
year with Reiser's first-degree murder conviction. That carries a 25-to-life
term, but the authorities, in a backroom deal, later offered him 15-to-life
if he produced his wife's body and waived any rights to appeal his conviction.
New in OpenSuSE 10.1 is also "rug - rug is the command-line interface
to the ZENworks Linux Management (ZLM) agent. It works with the ZLM
daemon to install, update, and remove software according to the commands
you give it. The software which it installs can be from ZENworks 7 Linux
Management, ZENworks 6.6.x Linux Management servers, aptrpm repositories,
as well as local files.
ZENworks Linux Management servers sort software by category into catalogs,
which are groups of similar software. For example, one catalog might
contain software from the operating system vendor, and another the Novell
Linux Desktop. You can subscribe to individual catalogs to control the
display of available packages and prevent the accidental installation
of unwanted software. By default, all operations are performed on software
from within catalogs to which you are subscribed, although you may alter
this with the --allow-unsubscribed flag."
As I said, suse_register is used by the update (and install ?!) manager.
The tool automatically detects package and patch sources suitable
for the current device and feeds the underlying package management system
(zmd)
accordingly.. You may wonder why. Here it is:
To perform its task suse_register transfers zmd's unique device identifier
to Novell's registration webservice.
In order for the webservice to calculate the appropriate package and
package
sources, suse_register also passes hardware architecture, operating
system and version to the webservice. The current timezone is also passed
so that the webservice can select a geographically close source mirror
sites of its
knowledge.
Additionally Novell's backend systems allow for customer device management.
Customers can review their available systems and associate them with
appropriate entitlements they have purchased. In order to fulfill that
task
suse_register can be configured to also transmit certain device details
like
hostname, CPU type etc. so that customers can easier identify their
devices.
To provide a maximum amount of flexibility Novell's webservice is able
to ask back for needed parameters dependent on the needs of the registration
procedure. Therefore certain device side invoked commands can be requested
for their outputs. These hard coded commands are:
On Wed, 28 May 2008 19:26:02 +0000, swicklund wrote:
> If I select to the check box to enter registration codes then click
next I
> get a server error.
>
> None of the installed products can be registered at the Novell
> registration server.
>
> My server stopped downloading updates, so I deleted its registration.
Now
> I am trying to re-register it.
Stop the zmd service, delete the deviceid & secret files from /etc/zmd,
start the zmd service, then try running the NCC Configuration utility
again.
--
Joe Marton
Novell Support Forum SysOp
Novell does not officially monitor these forums!
http://forums.novell.com/
On Wed, 07 Mar 2007 02:26:42 +0000, haych.c wrote:
> I can see all three of the servers. One server works, two don't. I
have
> tried removing the broken ones and re-registering them. They do re-appear
> in customer centre wit han active status but still dont work on the
> system.
Interesting. I would remove all three, not just the two broken ones.
Then pick a broken one and following the following TIDs to clear secrets,
database, and cache before rerunning suse_register: 3303599, 3181469,
and
3818394.
--
Joe Marton
Novell Support Forum SysOp
Novell does not officially monitor these forums!
Version 13, 19 December 2006.
This paper describes how the registration process is implemented
on Linux systems. What happens on Novell.com is documented elsewhere.
The registration process is invoked in one of the following ways:
1. During interactive installation, the user will be asked if they
want to connect to the network and retrieve updates. This will cause
interactive registration (see below). The user may skip this process,
in which case the system will not be updated and the ZMD update facility
will not be configured.
2. During scripted installation (i.e. with autoyast) registration
may be completely scripted using the registration utility (see below).
As with interactive installation, this may be skipped.
3. Manually calling the registration utility from YaST. When running
in a graphical mode (i.e., webconsole or when YaST can realize an HTML
widget), the registration process may be interactive.
4. Manually calling the registration utility from the command-line.
5. When the user attempts to use a ZMD-related command and ZMD is
not configured, an error message will be generated prompting them to
register in order to configure the update service. They will then need
to manually register using one of the entry points described above.
Optionally, if appropriate, the command may invoke a wrapper script
that will call the registration utility.
Registration Utility: suse_register
suse_register [ options ] [-a parameter=value ...]
The suse_register utility collects system configuration and user
information needed to connect the system to network-delivered services
from Novell and configure the patch and update service. The information
is supplied to a registration service at Novell.com, and Novell.com
will return an XML-structured file with the information needed to configure
ZMD for patch and update.
Options
-i | --interactive – launch web browser and interactively
collect registration information
--product <product> - product to register
-p | --list-parameters – contact the registration service
for a list of parameters
--xml-output – print results in XML to stdout (for scripting)
-n | --no-optional – don't submit passively collected optional
system information
-f | --force-registration – mark all parameters mandatory
which are required for registration even though registration itself
might be optional
--no-hw-data – never submit hardware data, even if they are
mandatory
-L file | --log=file – log XML blocks sent to and received
from the registration service to file
--locale=locale – force messages to a specific language and
encoding
-b path | --browser=path – use web browser specified by path
for interactive registration
--no-proxy – don't use proxies, even if the appropriate environment
variables are set
--xml-output – print XML output
-h | -? | --help – print command-line syntax help
[edit]
Description
List Products
At the beginning of each call, suse_register will ask the
server so send a list of known products. This happens by calling the
URL
https://secure-www.novell.com/center/regsvc/?command=listproducts
.
The server return a list of products, for example:
<?xml version="1.0" encoding="UTF-8"?>
<productlist xmlns="http://www.novell.com/center/xml/regsvc10"
lang="en-US">
<privacy url="http://www.novell.com/company/policies/privacy/"
description="Novell Privacy Statement"
class="informative"/>
<product>Novell Linux Desktop</product>
<product>SUSE Linux</product>
<product>SUSE SLES</product>
</productlist>
List Parameters
When invoked with the --list-parameters option, the suse_register
command will contact the registration service at
https://secure-www.novell.com/center/regsvc/?command=listparams,
supplying the desired encoding and language identifiers for textual
descriptions of the parameters. The content includes the product information.
<?xml version="1.0" encoding="UTF-8"?>
<listparams xmlns="http://www.novell.com/xml/center/regsvc-1_0">
<product version="10.1" release="Beta9" arch="i686"><![CDATA[SUSE LINUX]]></product>
</listparams>
The encoding and language specifiers are supplied using HTML form
post or get methods, and are passed using the encoding
and lang identifiers, respectively. The default values for encoding
and language are derived from the LANG locale variable, and may
be set in the runtime environment using the LANG environment
variable. An appropriate value may also be passed on the command line
using the --locale option. This value is structured as lang.encoding.
The value for lang may require normalization by suse_register
in order to conform to IETF
RFC 3066. For example, en_US would be transformed to en-US.
The value for encoding must be UTF-8; in instances where
other character encodings are required, suse_register must normalize
or de-normalize message strings.
The registration service will then return an XML structured document
with a list of parameters, their description, and a command that may
be used to collect the desired information (if applicable). The registration
service may modify the language and encoding to match supported message
catalogs. For example, if suse_register passes lang="en-GB",
the registration service may change the language value to en
because a single English language message catalog is supported.
The tag privacy has an url and a description
attribute. The url is the link to the current privacy policy
of Novell. The description a short description about the policy.
<?xml version="1.0" encoding="utf-8"?>
<paramlist xmlns="http://www.novell.com/center/xml/regsvc10" lang="en">
<param id="ostype"
description="Operating System Type"
command="lsb_release -sd"/>
<param id="osversion"
description="Operating System Version"
command="lsb_release -sr"/>
<param id="processor"
description="Processor Type"
command="uname -p"/>
<param id="platform"
description="Hardware Platform Type"
command="uname -i"/>
<param id="timezone"
description="Timezone Offset from GMT"
command="date +'%z'"/>
<param id="username"
description="Novell Account User Name"/>
<!-- etc. -->
<privacy url="http://www.novell.com/company/policies/privacy/"
description="Submit information to help you manage systems in the Customer Center."
class="informative"/>
</paramlist>
If suse_register was invoked with the --xml-output
option, then the returned file will be sent to stdout. Otherwise,
a human-readable version of the parameter list will be printed to
stdout.
Registration
In all other cases, the suse_register command will send an
XML structured document to the registration service at
https://secure-www.novell.com/center/regsvc/?command=register .
The registration service may respond with a redirect, in which case
the request is resubmitted to the indicated URL.
The URL should contain the protocol version of suse_register,
e.g. version=1.0, as query option.
The XML document will contain a globally-unique identifier (GUID)
for the device provided by ZMD and any collected parameters. The ZMD
GUID is one of two randomly-generated “unique" numbers that the system
and the Novell.com ZLM server will exchange with each other. The other
is a registration code that will be passed back later in the process.
For virtualization the GUID of the Domain-0 could be provide inside
the <host>...</host> element. This could be understand as a “link"
to the entitlement of Domain-0. More about this is defined in an separate
document.
At a minimum, the suse_register command will passively collect
the products, the processor and hardware platform type, and the timezone.
The products are used for update catalog selection. The timezone information
is used to select an update server. The XML document will also include
the desired language and encoding specifiers, as outlined above.
The mirrors tag ask for maximal count of mirrors returned
by the registration server. If this value is missing in the request,
the value is “1" . Update sources with the same catalog name are defined
to be mirrors with the same content.
The product has the following attributes: version, release
(might be empty) and arch. The value is the product name.
<?xml version="1.0" encoding="UTF-8"?>
<register xmlns="http://www.novell.com/xml/center/regsvc-1_0"
lang="en" accept="optional" force="registration">
<guid>1badbeef4abadb01</guid>
<host>564894af454e9d12</host>
<product version="10" release="" arch="i686">
<![CDATA[SUSE-Linux-Enterprise-Server-i386]]>
</product>
<param id="processor">i686</parameter>
<param id="platform">i386</parameter>
<param id="timezone">US/Mountain</parameter>
<mirrors count="5" />
</register>
It is possible to register more that one product. suse_register
will submit the set intersection of server known products (i.e., products
returned from a listproducts command), installed products, and any products
provided via the --product command line parameter.
If the supplied information is sufficient to complete registration
of the system, then the registration service will send back and XML
structured document with configuration information for ZMD.
<?xml version="1.0" encoding="UTF-8"?>
<zmdconfig xmlns="http://www.novell.com/xml/regsvc10" lang="en">
<guid>1badbeef4abadb01</guid>
<param id="update_inventory">true</param>
<service id="novell-emea"
description="Novell Network European Update Service"
type="zenworks">
<param id="url">
https://dublin.network.novell.com/zlm7/
</param>
<param id="regcode">fade4badbeeffeed</param>
<param name="catalog">sle-10-common-i586</param>
<param name="catalog">sle-10-server-i586</param>
<param name="catalog">sle-10-sdk-i586</param>
<param name="catalog">sle-10-unsupported-i586</param>
</service>
<service id="mirror1"
description="Mirror 1 in Germany"
type="yum">
<param id="url">
ftp://ftp.suse.com/pub/suse/i386/update/10.1
</param>
<param name="catalog">SUSE-Linux-10.1-Update</param>
</service>
</zmdconfig>
The registration code returned for a particular update service is
not the activation code; it is one of two randomly-generated “unique"
numbers that ZMD on the system and a Novell-hosted ZLM server exchange
with each other. Types other than “zenwork" may not have a registration
code. The other is the ZMD GUID that was provided earlier in the process.
By using two randomly-generated numbers, a different activation code
may be assigned to a system at Novell.com without having to update the
system.
The server returned is either a best-guess appropriate server hosted
by Novell, where “best" is determined by the timezone information supplied
to the registration process, or, when possible, a company-hosted update
server. In order to provide a company hosted update server, an interactive
registration process must have been used so that the user could provide
the necessary Novell user name and password.
The only other option currently defined is to have ZMD update the
hardware and software inventory information. If optional (inventory)
parameters are sent to the registration service, this will be set. If
optional parameters are not sent (i.e., if the --no-optional
command-line option is used), then this option will be unset. This option
is a global ZMD parameter so it is send outside of a service
tag.
The set of catalogs returned are based on the product information
provided. For Novell-hosted update servers, Novell-defined catalogs
are returned (defined elsewhere). For customer-hosted update servers,
customer-defined catalogs are returned. For SUSE Linux (not enterprise)
the best of a list of university mirrors are returned.
Need Info
The registration service may require additional information before
completing the registration. In such cases, the registration service
will return an XML structured document with a list of parameters that
must be supplied to complete the registration process.
<?xml version="1.0" encoding="utf-8"?>
<needinfo xmlns="http://www.novell.com/xml/regsvc10" lang="en"
href="https://secure-www.novell.com/center/regsvc?command=interactive&guid=1badbeef4ab">
<param id="indentification" class="mandatory"
description="Identify System Owner">
<select>
<param id="email" description="E-Mail Address"/>
<param id="elogin" description="Novell Account Login">
<param id="username" description="Username"/>
<param id="password" description="Password"/>
</param>
<param id="custid" description="Customer Number"/>
</select>
</param>
<param id="sysident" description="System Identification">
<param id="hostname" description="Hostname" command="uname -n"/>
<!-- etc. -->
</param>
<param id="hw_inventory" description="Hardware Inventory">
<param id="cpu" description="CPU Details" command="hwinfo --cpu"/>
<!-- etc. -->
</param>
<!-- etc. -->
<privacy url="http://www.novell.com/company/policies/privacy/"
description="Submit information to help you manage systems in the Customer Center."
class="informative"/>
</needinfo>
The above <needinfo> response is also sent by the service
if the accept="optional" attribute is specified in the <register>
request made by suse_register. This attribute should always be
specified on the first <register> request made, and tells the
service that respond back with optional parameters is allowed even if
all mandatory parameters were already met. Whether the server really
returns with a <needinfo> dependents on the business logic of
the product.
If the –no-optional parameter is given, accept="mandatory" is included
in the first register request.
If the –force-registration parameter is given, force="registration"
is included in the first register request. In this case the server knows
that the user wants a registration. Customers still would like to be
able to register because they might get additional services by Novell
other than patches, for example specific NTS services.
To suppress any interactive <needinfo> parameters force="batch"
can be added to the <register> request by using --batch
commandline parameter. When it is impossible for the server to perform
the registration in this case, and error is returned.
The suse_register command will then passively collect information
for all parameters where a command property is specified unless
the --no-optional option is specified. If --no-optional
is specified, then only parameters of class “mandatory" where a command
property is specified shall be collected. The command must be one of
hwinfo, lsb_release or uname; the command name
will be substituted with a command-path determined by suse_register.
All other command names will be rejected. lsb_release might not
be installed. In this case an empty value is returned back to the server.
There are some additional "virtual" commands which are directly implemented
in suse_register. These "virtual" commands are: zmd-secret, zmd-ostarget
and installed-desktops .
Interactive parameters may be logically grouped by nesting parameter
blocks (<param>...</param>) inside other parameter blocks, as
shown in the example above. Where a choice one of a set of possible
parameters is required, then the parameter blocks shall be contained
within a a selection block (<select>...</select>). Note that
a selection block masks inheritance of the mandatory class property.
A selection block (<select>...</select>) is forbidden if a
command property is specified below.
If any information was passively collected, the registration request
will be resubmitted to the registration service before suse_register
continues.
If suse_register reaches a state where it does not have and
cannot passively collect a value for a mandatory parameter, and the
--interactive option has not been set, then it will terminate
with an exit code and a diagnostic message. The diagnostic message will
contain the XML “need information" block when the --xml-output
option is specified, or printed in human-readable form otherwise. When
the --no-optional option is used, optional parameters will be
stripped from the diagnostic message.
When suse_register is invoked with the --interactive
option, the utility will launch a web browser to collect the needed
registration information and exchange it with Novell.com. The script
will wait for the browser to exit before continuing, so the HTML exchange
between the browser and Novell.com should attempt to close the browser,
and advise the user that the browser must be closed in order to continue
the registration process.
Because suse_register is a command-line tool, a text browser
is started when the --interactive parameter is given. If the
--browser option is given, it cannot be sure that calling this
browser really blocks the terminal until the browser is closed, and
in that case suse_register will exit with a message to restart suse_register
if the registration in the browser has completed.
The privacy tag has the same information as in command=listparams.
Standard Assumption for User Identification
In the general case an e-mail address is used as a rendezvous point
for subsequent subscription management information functions at Novell.com.
It is used in place of Novell “eLogin" account information for usability
(e.g., in cases where the user does not yet have a Novell account, can't
remember the information, etc.). The activation code, if provided, enables
completion of the registration process without the registering user
having to subsequently visit Novell.com.
Richer workflows may be implemented using autoyast scripting or interactive
registration.
Privacy Policy
Documentation and interactive user interfaces should explain that
the required system information (ZMD GUID, hardware architecture tag,
operating system type, OEM edition, and timezone) are required to complete
the registration process, and Novell reserves the right to use this
information for aggregate reporting. However, no personal- or company-identifying
information will be shared outside Novell.
Documentation and interactive user interfaces should explain that
the optional system information is collected and stored at Novell.com,
but is not used by Novell in any way or shared with any party. It is
simply collected for the convenience of the user in managing their systems
and subscriptions. While users are encouraged to permit transmittal
of this information for their own use, they are not required to do so.
Provisional Registration and Re-Registration
If an activation code is not supplied when suse_register is
run, then Novell.com will automatically allocate an evaluation activation
code according to current Novell business policies. The registering
user may subsequently assign as permanent activation code using web-based
tools at Novell.com, or using the suse_register process.
The suse_register command may be re-run at any time in order
to submit an activation code for this system via the command-line, change
the setting for inventory transmittal, or change the identifying information.
The system information at Novell.com will then be updated accordingly.
This provides a mechanism for finding “lost systems" in the registration
process.
Server Errors
If an error on the server occurs, it will send an HTTP error with
a HTML error message page. Javascript in the error message page is not
allowed.
Exit Codes
0 – registration or list command completed
1 – more information needed, not interactive
>= 2 – error
What are some important Xen considerations when updating SLES 10 SP1
to SLES 10 SP2?
Symptoms
ERROR:
Error: (2, 'Invalid kernel',
'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen
kernel, sorry\n')
The
Novell note (document 5027381 ) about this version describes
it as SPident 20080409. SP Update via YAST installs .14 by default. This
version can detect if after semi-failed install the system is SP2 but is
not called SP2
SPident 20080409 (83403d4cbac105fb425b735b6d8dc7d7)
This document (5027381) is provided subject
to the disclaimer at the end of this document.
patches this patch supersedes
This patch does not supersede any other patches.
patches that supersede this patch This patch is not superseded
by any other patches.
patch attributes
Architecture: x86-64
Document ID: 5027381
Creation Date: 2008-06-04 15:46:55
abstract
SPident
SuSE Linux Maintenance Web (83403d4cbac105fb425b735b6d8dc7d7)
Applies to
Package: SPident
Product(s):
SUSE Linux Enterprise Desktop 10 SP2 for x86
SUSE Linux Enterprise Desktop 10 SP2 for AMD64 and Intel EM64T
SUSE Linux Enterprise Server 10 SP2 for x86
SUSE Linux Enterprise Server 10 SP2 for IPF
SUSE Linux Enterprise Server 10 SP2 for IBM POWER
SUSE Linux Enterprise Server 10 SP2 for IBM zSeries 64bit
SUSE Linux Enterprise Server 10 SP2 for AMD64 and Intel EM64T
Patch: sledp2o-SPident-5160
Release: 20080409
Obsoletes: none
Details
Indications Everyone should update.
Contraindications None.
Problem description
SPident has data for all architectures of SLES/SLED. Since this data
is generated during the final media creation, only the local data can
be completely correct. This update is meant to consolidate the data
for all architectures.
Solution
Please install the updates provided at the location noted below.
Installation notes
This update is provided as an RPM package that can easily be installed
onto a running system by using this command:
rpm -Fhv SPident.rpm
file contents
|
Files Included |
Size |
Date |
| SPident-0.9-74.24.noarch.rpm |
200.7 KB (205529) |
2008-06-04 15:46:58 |
| readme_5027381.html |
N/A |
2008-06-04 15:48:26 |
source packages
Download
the source code of the patches for maintained products.
Update to SP2 via patchesAttention:The update process
has to be done completely from beginning to reboot. There is no automatic
way to revert changes. Furthermore, the server has to be connected online
during the whole update process. Prerequisites: You have
to make sure to have your system registered. If you have not done this
already, you can either do so by using the "Novell Customer Center Configuration"
module in YaST or use the suse_register
commandline tool. This will add an update source to your system.
1) Update by using YaST Online Update
- Start the Online-Update module (YOU) from the YaST control center.
- Press 'Accept' to apply updates with 'package management' flag
set. Among others, this will install SLE 10 SP2 maintenance stack
updates (Patch 'slesp1-libzypp' / 'sledp1-libzypp'). After installing
those, YOU will restart itself.
- Press 'Accept' to apply all available updates that are available
for SP1. This may also install a new kernel, so you should reboot
the system after applying this one.
- Start the Online-Update module from the YaST control center
again.
- Select the optional "Update to SUSE Linux Enterprise Server/Desktop
Service Pack 2" ('move-to-sles10-sp2'
/ 'move-to-sled10-sp2')
patch. Do not select any other patch at the same time - except for
for additional migration patches for add-on products. If an add-on
product (e.g. the SDK) is installed, the respective migration patch
will be selected automatically. The migration of the add-on product
should be done at the same time as the base product, otherwise there
would be rpm dependency conflicts.
- After the patch is installed, YOU will close.
- Start the Online-Update module from the YaST control center
again.
- Amongst others patches, 'slesp2o-sp2_online'
and 'product-sles10-sp2'
(or 'sledp2o-sp2_online'
and 'product-sled10-sp2'
accordingly) are preselected. Apply these patches to bring the system
to SP2 level.
- Reboot the system.
2) Update by using zen-updater
- Start zen-updater from the system tray.
- Apply updates with 'package management' flag ('slesp1-libzypp'
/ 'sledp1-libzypp',
amongst others).
- At this point, an 'rczmd
restart' and a restart of the zen-updater application might
be necessary.
- Apply all maintenance updates that are available up to this
point. This may also install a new kernel (a subsequent reboot is
recommended).
- Select the 'move-to-sles10-sp2'
patch (or 'move-to-sled10-sp2'
accordingly). If add-on products are installed, migration patches
for these will be selected automatically.
- Select "Refresh" from the zen-updater context menu.
- After that, amongst other patches 'slesp2o-sp2_online'
and 'product-sles10-sp2'
(or 'sledp2o-sp2_online'
and 'product-sled10-sp2'
accordingly) are preselected in zen-updater. Apply these patches
to bring the system to SP2 level.
- Reboot the system.
3) Update by using rug
- Open a root shell.
- It is recommended to quit zen-updater. Do not only close it's
window! If unsure, run 'killall
zen-updater'.
- Run 'rug in -t patch
slesp1-libzypp' (or 'rug
in -t patch sledp1-libzypp' accordingly). This will update
the maintenance stack.
- Run 'sleep 40 && rug
ping -a' to wait for the ZMD to wake up after it's restart.
- Run 'rug in -t patch
move-to-sles10-sp2' (or 'rug
in -t patch move-to-sled10-sp2' accordingly).
- Run 'rug refresh && rug
ping -a'.
- Run 'rug up -t patch'
to update more packages with 'packagemanagement flag' set.
- Run 'sleep 240 && rug
ping -a' in order to wait for ZMD to become responsive again.
- Run 'rug up -t patch'
again.
- Reboot the system.
- The following script can be used as a base for a complete
unattended update from SP1 to SP2:
#!/bin/bash
set -x
rug in -y -t patch slesp1-libzypp
# For SLED use sledp1-libzypp
sleep 40 && rug ping -a
rug in -y -t patch move-to-sles10-sp2
# For SLED use move-to-sled10-sp2
rug refresh && rug ping -a
rug up -y -t patch
sleep 240 && rug ping -a
rug up -y --agree-to-third-party-licences
-t patch <<EOF
n
# For an automatic reboot after the migration, you may change 'n'
to 'y'
EOF
This document (3303599) is provided subject to the
disclaimer at the end of this document.
Environment
Novell SUSE Linux
Enterprise Desktop 10
Novell SUSE Linux
Enterprise Server 10
Novell ZENworks Linux
Management Linux Management 7 - ZLM7
Situation
Registering another
key for the SUSE Linux Enterprise 10 server or desktop is resulting
in a quick response of "success". However, the key is still not used
and is also not listed.
If the evaluation
key was used first to register SLED 10 or SLES 10, the new registration
key that is aquired on purchase needs to be changed by following the
below steps. The old key needs to be cleared to enable the new key to
be used.Resolution
The key must be cleared
from the local server or workstation. The process is :
- Stop the Zen
management daemon using "/etc/init.d/novell-zmd
stop".
- Remove the
device ID using "rm
/etc/zmd/deviceid".
- Remove the
Zen secret using "rm
/etc/zmd/secret".
- Restart the
Zen management daemon using "/etc/init.d/novell-zmd
start"
With this complete,
restart YaST, and then launch the Novell Customer Center. This will
register any new keys that were needed.
[Aug 20, 2008] It's probably time to install Suse 10 SP2 on production systems...
It's already thee month old upgrade. Major problems with installer
are ironed out and automatic patch install does a reasonable job in
upgrading the system. Installation takes than less hour on PE1950/2050
and requires a couple of reboots.
Problem arise when you use privately compiled bind or sendmail. In
this case it's better to use default Suse upgrade and face consequences.
after that you can restore your pre-compiled packages and delete
those that are not needed.
Virtualization cannot be that simpler than in openSUSE 11.0. In openSUSE
11.0, Xen Virtualization ins pre-built and all it takes is a few clicks
away from up and running with Virtualization in no time. Xen is a virtual
machine monitor for x86 that supports execution of multiple guest operating
systems with unprecedented levels of performance and resource isolation.
This package contains the Xen Hypervisor.
"...SUSE Linux Enterprise – version 11 – is due to arrive in the first
half of 2009 and is slated to deliver major advancements in mission-critical
data center technologies, UNIX* migration, virtualization, interoperability,
green computing and desktop Linux. More information on SUSE Linux Enterprise
can be found at www.novell.com/linux.
"
WALTHAM, Mass.— 21 May 2008— Novell today announced the availability
to customers worldwide of SUSE® Linux Enterprise 10 Service Pack 2 (SP2),
containing enhancements in virtualization, management, hardware enablement
and interoperability. SUSE Linux Enterprise Server 10 SP2 is the only
Xen-based virtualization solution with full support from Microsoft for
Windows* Server 2008 and Windows Server 2003 guests and live migration
of those guests across physical machines. Several improvements specific
to SUSE Linux Enterprise Desktop 10 and SUSE Linux Enterprise Real Time
10 are also included in SP2. Novell further unveiled the Subscription
Management Tool for SUSE Linux Enterprise, designed to help customers
better manage their SUSE Linux Enterprise software updates.
“This service pack for SUSE Linux Enterprise 10 has something for
almost everyone – customers, partners and developers," said Holger Dyroff,
vice president of outbound product management for SUSE Linux Enterprise
at Novell. “The benefits of Linux in the enterprise are becoming well
known, and Novell's focus is on continuing to simplify the customer's
experience, always with an eye to reducing costs. Reliability, security
and interoperability don't need to break the bank. That's the ongoing
value Novell provides with SUSE Linux Enterprise."
Subscription Management Tool for SUSE Linux Enterprise
The Subscription Management Tool (SMT) for SUSE Linux Enterprise helps
customers easily manage their SUSE Linux Enterprise software updates
while maintaining corporate firewall policy and regulatory compliance
requirements. SMT is a package proxy system that is integrated with
the Novell® Customer Center and provides key Novell Customer Center
capabilities locally at the customer site. It provides a repository
and registration target that is synchronized with the Novell Customer
Center, thus maintaining all the capabilities of the Novell Customer
Center while allowing a more secure centralized deployment.
SMT allows customers to easily distribute updates for all SUSE Linux
Enterprise devices (server, desktop or point-of-service terminal) that
are running Service Pack 2 or subsequent releases. By downloading these
updates only once and distributing them throughout the enterprise, the
customer is able to set more restrictive firewall policies and, where
applicable, avoid significant network usage stemming from repeated downloads
of the same updates by each device. SMT is fully supported and available
as a download to customers with an active SUSE Linux Enterprise product
subscription.
SUSE Linux Enterprise Server Enhancements
Delivering Xen* version 3.2, SUSE Linux
Enterprise Server 10 SP2 includes several virtualization advances, including
support for fully virtualized Windows Server 2008 and Windows Server
2003 and the live migration of those Windows Server guests across physical
machines. SUSE Linux Enterprise Server is the only third-party
virtualization solution offering full support directly from Microsoft
for Windows Server guests. In addition, extensive updates to the YaST
management toolset encompass first-boot enhancements and network module
support for new devices.
Srinivasa Rao Addepalli, CTO and chief architect of Intoto Inc. and
a participant in the SP2 beta program, said, “SUSE Linux Enterprise
Server has been the choice of customers for security applications in
the virtualized environment. To secure virtual systems, Intoto has been
providing UTM and MultiService Business Gateway solutions using Xen
running on SUSE Linux Enterprise Server 10, and we have been pleased
with the increase in performance and manageability of the SP2 release.
With the addition of fully virtualized Windows Server 2008 guest support,
the SP2 release facilitates creation of a true virtualization system."
Advances in high availability and storage management such as updates
to Heartbeat 2 and OCFS2 are also included in SP2. Network management
improvements include support for IPv6. SUSE Linux Enterprise Server
10 SP2 has been designed to meet the U.S. government's requirements
for IPv6 and is currently in the certification process. Enhanced hardware
enablement includes new network, storage and other drivers along with
support for IBM* cryptographic hardware.
SUSE Linux Enterprise Desktop Enhancements
SUSE Linux Enterprise Desktop 10 SP2 provides improved interoperability
with Microsoft* Windows and Office via local
NTFS file system support, improved integration with Microsoft
Active Directory* and an upgrade to OpenOffice.org 2.4 Novell Edition.
The OpenOffice.org productivity suite features key enhancements to VBA
macro support within Calc and embedded audio and video within Impress,
as well as a technical preview of the Office Open XML (OOXML) translator.
Other enhancements include plug-and-play support for wireless broadband
(UMTS, 3G), improvements to Network Manager, and support for new hardware
technologies from Novell partners.
Nick Piccone, network engineer for University Community Hospital
and an SP2 beta tester, said, “The improved interoperability with Microsoft
Windows and Office combined with the networking and hardware enablement
enhancements that come with this release have demonstrated the level
of productivity and reliability we have come to expect from SUSE Linux
Enterprise Desktop."
Updates to SUSE Linux Enterprise Real Time
SUSE Linux Enterprise Real Time is specifically engineered to reduce
the latency and increase the predictability of time-sensitive mission
critical applications. Service Pack 2 further improves the performance
and predictability of time-sensitive applications running on SUSE Linux
Enterprise Real Time through support for adaptive locking, OpenFabrics
Enterprise Distribution (OFED) 1.3 and the Precise Timing Protocol.
OFED 1.3 enables the implementation of unified high-speed interconnects
based on InfiniBand and 10-Gigabit Ethernet. With SP2, Novell becomes
the first Linux* distributor to support OFED 1.3.
SUSE Linux Enterprise Software Development Kit (SDK)
The SUSE Linux Enterprise SDK also provides new capabilities in SP2,
giving developers and technical enthusiasts even more ways to create
powerful new software on and with SUSE Linux Enterprise. It includes
updates to several tools that enable the creation of installation media
and appliances: KIWI, YaST2 Product Creator, YaST2 Add-on Creator and
YaST2 Image Creator.
Kernel v2.6.9 /Documentation/filesystems/ext3.txt
+noload Don't load the journal on mounting.
+
+data=journal All data are committed into the journal prior
+ to being written into the main file system.
+
+data=ordered (*) All data are forced directly out to the main file
+ system prior to its metadata being committed to
+ the journal.
+
+data=writeback Data ordering is not preserved, data may be
+ written into the main file system after its
+ metadata has been committed to the journal.
+
+commit=nrsec (*) Ext3 can be told to sync all its data and metadata
+ every 'nrsec' seconds. The default value is 5 seconds.
+ This means that if you lose your power, you will lose,
+ as much, the latest 5 seconds of work (your filesystem
+ will not be damaged though, thanks to journaling). This
+ default value (or any low value) will hurt performance,
+ but it's good for data-safety. Setting it to 0 will
+ have the same effect than leaving the default 5 sec.
+ Setting it to very large values will improve
+ performance.
+
+barrier=1 This enables/disables barriers. barrier=0 disables it,
+ barrier=1 enables it.
+
+orlov (*) This enables the new Orlov block allocator. It's enabled
+ by default.
+
+oldalloc This disables the Orlov block allocator and enables the
+ old block allocator. Orlov should have better performance,
+ we'd like to get some feedback if it's the contrary for
+ you.
+
+user_xattr (*) Enables POSIX Extended Attributes. It's enabled by
+ default, however you need to confifure its support
+ (CONFIG_EXT3_FS_XATTR). This is neccesary if you want
+ to use POSIX Acces Control Lists support. You can visit
+ http://acl.bestbits.at to know more about POSIX Extended
+ attributes.
+
+nouser_xattr Disables POSIX Extended Attributes.
+
+acl (*) Enables POSIX Access Control Lists support. This is
+ enabled by default, however you need to configure
+ its support (CONFIG_EXT3_FS_POSIX_ACL). If you want
+ to know more about ACLs visit http://acl.bestbits.at
+
+noacl This option disables POSIX Access Control List support.
+
+reservation
+
+noreservation
+
+resize=
+
bsddf (*) Make 'df' act like BSD.
minixdf Make 'df' act like Minix.
@@ -30,8 +87,6 @@
debug Extra debugging information is sent to syslog.
-noload Don't load the journal on mounting.
-
errors=remount-ro(*) Remount the filesystem read-only on an error.
errors=continue Keep going on a filesystem error.
errors=panic Panic and halt the machine if an error occurs.
@@ -48,17 +103,6 @@
sb=n Use alternate superblock at this location.
-data=journal All data are committed into the journal prior
- to being written into the main file system.
-
-data=ordered (*) All data are forced directly out to the main file
- system prior to its metadata being committed to
- the journal.
-
-data=writeback Data ordering is not preserved, data may be
- written into the main file system after its
- metadata has been committed to the journal.
-
quota Quota options are currently silently ignored.
noquota (see fs/ext3/super.c, line 594)
grpquota
"Barriers do provide a greater degree of performance for journaling
file systems and help ensure data is correctly written out to the disk so
this patch can degrade filesystem performance. " So disabling them due to
the bug described in Novell support note 3605538
Ext3 filesystem goes read-only without the underlying storage reporting
errors can degrade performance
This document (3907838) is provided subject
to the disclaimer at the end of this document.
environment
Novell SUSE Linux Enterprise Server
10
Novell SUSE Linux Enterprise Server 9
Novell Open Enterprise Server (Linux based)
Novell SUSE Linux Enterprise Desktop 10situation
ERROR:
JBD: barrier-based sync failed
on sda1 - disabling barriers"
or, in general:
JBD: barrier-based sync failed
on storage_device - disabling
barriersresolution
This message is primarily an informational
message; it does not indicate a problem.
Suppress this message
globally
Please note: This method is only available for
SUSE Linux Enterprise Server / Desktop
(SLES/SLED) up to version 9 and for
Open Enterprise Server (OES) version
1. From SLES/SLED 10 and OES2 on it is not possible to suppress the
message globally. Instead use the solution in the section "Suppress
this message for one filesystem".
To suppress this message globally, pass the parameter
barrier=off
to the
kernel when booting (e.g., when using the GRUB boot loader, through
/boot/grub/menu.lst).
This will cause the kernel not to attempt to use the transaction barrier
mechanism.
Suppress this message
for one filesystem
To suppress this message for one particular
ext3 filesystem, use the mount option
barrier=0 when mounting
the filesystem.
Additional notes
Background
By default, the Linux kernel will try to use transaction barriers. Transaction
barriers are an additional mechanism to help maintain data integrity.
In general, modern storage subsystems may cache writes and may occasionally
reorder pending writes in order to increase write performance. While
this is fine in general, it is not desirable when handling journal data
for journaled filesystems. With journal data, metadata updates, that
is updates to the journal, should be written out to the storage prior
to the regular data they are associated with, to make true crash recovery
possible.
The informational message indicates that the storage driver and/or
the storage device do not support transaction barriers. Under normal
operation, this does not compromise data integrity. However, barriers
do provide a greater degree of performance for journaling file systems
and help ensure data is correctly written out to the disk.
"JBD" in this message
refers to the Journaling Block Device, an abstraction that was developed
to provide the journaling capabilities of the ext3 filesystem on top
of the infrastructure of the ext2 filesystem on which ext3 is based.
JBD is now used by the OCFS2 filesystem as well.document
| Document ID: |
3907838 |
| Creation Date: |
2008-02-01 05:33:00.0 |
| Modified Date: |
2008-02-01 05:32:20.0 |
| Novell Product: |
Open Enterprise Server |
| Novell Product: |
SUSE Linux Enterprise Desktop |
| Novell Product: |
SUSE Linux Enterprise Server |
| Novell Product: |
SUSE Linux |
This was the first serious problem with Suse 10 that we faced since
Feb 2007. It proved to be quite critical for us. Now it is described in
Novell support note 3605538
Ext3 filesystem goes read-only without the underlying storage reporting
errors The frequency of experiencing of this bug on production
servers diminished after installation of SP1 but it did not went away. As
of Feb 2008 it still exists as we were never informed about workaround
proposed (may be the workaround was created only in Feb 2008; we discovered
the document only in May 2008)
Status(Last
updated: 2008-02-25)
This issue is not yet fixed in a maintenance update of the kernel.
Root cause analysis has been performed and it is expected that a fix
for this issue will be included in the next maintenance update of the
kernel.
Workaround
Explicitly disable barrier support
for the affected filesystems, e.g. by specifying
barrier=0
in
/etc/fstab's mount options
field for the affected filesystems.
JeOS is the abbreviation (pronounced "juice") for the concept
of Just Enough Operating System as it applies to a
software appliance.JeOS is not a generic, one-size-fits-all operating
system. Rather, it refers to a customized operating system that precisely
fits the needs of a particular application. The application's OS requirements
can be determined manually, or with an analytical tool, such as
rPath's
rBuilder.
Therefore, JeOS includes only the pieces of an
operating system (often
Linux)
required to support a particular application and any other third-party
components contained in the appliance. This makes the appliance more
efficient, smaller, more secure and higher performing than an application
running under a full general purpose OS.
The program will enable ISVs to create appliances combining their
applications with Suse Linux Enterprise in an integrated package.
Novell also announced the beta release of Suse Linux Enterprise JeOS,
a minimized version of the Suse Linux Enterprise platform that ISVs
can use for creating appliances
... ... ...
Novell also announced Wednesday that it will officially participate
in the LimeJeOS project, which is an existing
community-led project building a minimized version of the openSuse Linux
distribution. Novell will release several new components
of the Suse Appliance Program, including an automated tool to build
appliances, it added.
Microsoft will deliver more than 1,000 support subscription certificates
for Suse Linux Enterprise Server to French automaker Renault, under
an agreement announced by Microsoft and Novell on Wednesday.
Renault will receive priority support subscriptions to Novell's Suse
Linux distribution. Renault plans to consolidate existing Linux distributions
to Suse Linux Enterprise Server with the intent of improving interoperability
and taking better advantage of virtualization, Microsoft and Novell
said.
Through a 2006 agreement between Novell and Microsoft, Microsoft
has purchased support certificates to Suse Linux, with Novell to provide
the support.
The package also contain Solaris binary of
chpasswd clone, which is extremely
useful for mass changes of passwords in corporate environments which include
Solaris and other Unixes that does not have chpasswd utility (HP-UX is another
example in this category). Version 1.3.2 now includes Solaris
binary of chpasswd which works
on Solaris 9 and 10.
cgipaf is a combination of three CGI programs.
- passwd.cgi, which allow
users to update their password,
- viewmailcfg.cgi, which allows
users to view their current mail configuration,
- mailcfg.cgi, which updates
the mail configuration.
All programs use PAM for user authentication. It is possible to run
a script to update SAMBA passwords or NIS configuration when a password
is changed. mailcfg.cgi creates a .procmailrc in the user's home directory.
A user with too many invalid logins can be locked. The minimum and maximum
UID can be set in the configuration file, so you can specify a range
of UIDs that are allowed to use cgipaf.
October 27, 2005 |
All about Linux
For logging on to the net or for attaching as a node on a LAN, your
computer needs a network card. The network card forms the interface
between your computer and the network. There are different kinds of
network cards available in the market depending on its speed and other
features. Here is a tip to find out the characteristics of your network
card.
If you want to find what type of network card is used, its speed,
on which IRQ
it is listed, and the chip type used, you use the following command
:
# dmesg |grep eth0
Here eth0
is the first network card. If you have additional cards, it will be
named eth1,
eth2 and so on. And here
is the output of the above command :
divert: allocating divert_blk for eth0
eth0: RealTek RTL8139 at 0xd800, 00:80:48:34:c2:84, IRQ 9
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
divert: freeing divert_blk for eth0
divert: allocating divert_blk for eth0
eth0: RealTek RTL8139 at 0xd800, 00:90:44:34:a5:33, IRQ 9
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
eth0: no IPv6 routers present
...
The important things to note here are those highlighted in colour. As
you can see from the above listing, my ethernet card is a
RealTek RTL8139 chipset
based card on IRQ 9 (Interrupt
Request). Its speed is 100 Mbps
and is a full-duplex card.
And the link is up.
... ... ... Another tool which also does the same thing is
ethtool.
Try the following command on your machine to see the output.
# ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: p
Current message level: 0x00000007 (7)
Link detected: yes
Here full duplex, half duplex and auto-negotiation have the following
meanings.
Full Duplex
- Logic that enables concurrent sending and receiving. This is usually
desirable and enabled when your computer is connected to a switch.
Half Duplex
- This logic requires a card to only send or receive at a single point
of time. When your machine is connected to a Hub, it auto-negotiates
itself and uses half duplex to avoid collisions.
Auto-negotiation
- This is the process of deciding whether to work in full duplex mode
or half duplex mode. An ethernet card supporting autonegotiation will
decide for itself which mode is the optimal one depending on the network
it is attached to.
In case of broken links
please try to use Google search. If you find the page please notify
us about new location
Novell
OpenSuse
News
Documentation, guides and tips
Help, forums, community
Software — official and unofficial repositories. Smart
Derivative works and LiveCD
Reviews
- 10.3: www.tuxmachines.org
- 10.2:
justanothertechblog.blogspot.com,
shiftbackspace.com,
All about Linux,
Software
in Review, Michael Dolan,
Friendly
Linux,
free-bees.co.uk,
element 14, tuxmachines.org,
tuxmachines.org
InformationWeek,
Linux
Forums, www.agt.id.au,
DesktopLinux,
Linux.com,
tuxmachines (alpha 3),
blogbeebe,
Projectsite 2007,
ReviewLinux,
eWeek,
Ruminations on
the Digital Realm,
BlogoWogo,
ArsGeek,
JonRob's blog,
Our Picks,
Linux and Open Source Blog,
CyberNet News,
LinuxLookup, SUSE Linux
Rants,
vnunet.com,
Linux Today,
Softpedia, tuxmachines.org
(rc 1)
- 10.1:
Linux Forums,
Linux Online,
Software
in Review,
Linux.com,
Software package resources,
Network World,
Computer World,
DesktopLinux
Interviews
Download
Screenshots
- 10.3: news.opensuse.org,
news.opensuse.org,
opensuse.org,
shots.osdir.com
- 10.2:
shiftbackspace.com,
opensuse.org,
OSDir.com,
Tuxmachines' Gallery,
Tuxmachines Gallery
(rc 1), Tuxmachines
Gallery (beta 2),
LinuxShots,
Softpedia,
LinuxQuestions,
Stefan Reisinger,
Phoronix
- 10.1:
Debian Admin,
UnixTutorials
Just released, this prescriptive guide shows IT Pros how to use Microsoft
Windows Server 2003 Active Directory for both authentication and identity
storage within heterogeneous Microsoft Windows and UNIX environments.
Planet SUSE
REDBOOK
Sg245863
[PDF]
SuSE Linux Integration Guide for IBM for xSeries and Netfinity
Download.openSUSE.org - downloads
from this site using HTTPD are unreliable.
FileMirrors for DVD
LQ
ISOs SUSE openSUSE 10.2
OpenSuse
Documentation
Official repository
http://download.opensuse.org/distribution/10.2/repo/oss/
http://download.opensuse.org/distribution/10.2/repo/non-oss/
Security and bug fixes
http://download.suse.com/update/10.2/
Midnight Commander
Snort
Copyright © 1996-2008 by Dr. Nikolai Bezroukov.
www.softpanorama.org was
created as a service to the UN Sustainable Development Networking Programme (SDNP)
in the author free time.
Submit
comments This document is an industrial compilation designed and created
exclusively for educational use and is placed under the copyright of the
Open Content License(OPL).
Original materials copyright belong to respective owners. Quotes are made
for educational purposes only in compliance with the fair use doctrine.
Standard disclaimer:
- The statements, views and opinions presented on
this web page are those of the author and are not endorsed by, nor do they necessarily
reflect, the opinions of the author present and former employers, SDNP or any other
organization the author may be associated with.
- We do not warrant the correctness of the information provided or its
fitness for any purpose
- In no way this site is associated with or endorse cybersquatters
using
the term "softpanorama" with other main or country domains (e.g. softpanorama.com) with
bad faith intent to profit from the goodwill belonging to
someone else.
Last modified:
June 01, 2009