|Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
|May the source be with you, but remember the KISS principle ;-)|
|Recommended Links||SLES Installation Checklist||Hard Drive Partitioning||SuSE install from USB drive||Installing Suse from ISO image|
|PXE installation||iLO 3 -- HP engineering fiasco||Dell DRAC||installing Qlogic QLE2460 cards||Linux Multipath||autoyast||YaST|
|SLES Registration||SupportConfig||Installation of Oracle 11g||Linux Software RAID||Sysadmin Horror Stories||Random Findings||Etc|
Suse installer (YaST) is pretty flexible, but there are a lot of idiosyncrasies and to learn the ropes takes a lot of time even for experienced with other flavors of Linux/Unix sysadmin. Especially tricky is autoyast with its XMLconfiguration file and poor detection of errors.
|!||After selection of Installation menu item on a boot screen of GUI installation, you can press F4 and select installation Source.|
We can structure installation into several (pretty arbitrary ;-) parts. That simply learning the intricacies and provides the ability to concentrate on important for each operation/part details:
There are two versions of Linux 32 bit and 64 bit. 64-bit version requires CPUs with extended instruction set (AMD64 and Intel 64 CPU). Those day servers have only 64-bit CPUs. It make sense to use 64-bit version unless software explicitly requires 32 bit version. 32-bit version actually can access more then 4GB of memory via PAE extensions. Another exception is virtual machine environment: 32-bit kernel is better for virtial guests. For example VMware allows to run paravirtualised vbersion of 32-bit Suse.
Availability of Linux for 64-bit Intel and AMD hardware platforms does not necessarily mean that all the applications included have already been ported to 64-bit platforms. Often this is not true and a lot of application even commercial one are distributed only for 32-bit mode. ^4-bit Suse contin fully functional 32 bit subsystem and can run 32 bit applications.
To be executed correctly, every application requires a range of libraries. Unfortunately, in many cases the names for the 32-bit and 64-bit versions of these libraries are identical. They must be differentiated from each other by placement:
Subdirectories of 32-bit /lib directories whose data content does not depend on the word size are not moved.The installed 32-bit and 64-bit libraries must have an API (application programming interface) that matches the installed header files. The normal Linux environment is designed according to this principle.
In the case of manually updated libraries, you need to resolve these issues yourself.
The Linux boot process consists of several stages each represented by another component. The following list briefly summarizes the boot process and features all the major components involved.
BIOS. After the computer has been turned on, the BIOS initializes
the screen and keyboard and tests the main memory. Up to this stage, the machine
does not access any mass storage media. Subsequently, the information about
the current date, time, and the most important peripherals are loaded from the
CMOS values. When the first hard disk and its geometry are recognized, the system
control passes from the BIOS to the boot loader.
MBR boot Loader. The first physical 512-byte data sector of the first
device defined in BIOS load chain is loaded into the main memory and the program
that resides at the beginning of this sector takes over. It usually loads another
loader but it can do so only if the latter is located at fixed disk addresses
as no file system is present. That's why it is often referred to as Master Boot
Record (MBR). The boot loader then passes control to the actual operating system,
in this case, the Linux kernel at /boot partition.
Kernel and initramfs. MBR loads both the kernel and an initial RAM–based file system (initramfs) into memory. initramfs is a small cpio archive. It contains a small executable that uses BIOS calls called init that handles the mounting of the real root file system. It provides a minimal Linux environment that enables the execution of programs before the actual root file system is created. This minimal Linux environment is loaded into memory by BIOS routines and does not have specific hardware requirements other than sufficient memory.
The main purpose of init on initramfs is to prepare the mounting of and access to the real root file system. Depending on your system configuration, init is responsible for the following tasks.
When init is called during the initial boot as part of the installation process, its tasks differ from those mentioned earlier:
Starting YaST. Finally, init starts YaST, which handles package installation and system configuration.
CD/DVD are default installation medium for YAST. Local CD/DVD installations are very much the same for Solaris and Linux. The installation program prompts for information when it is required. A menu of options is presented in some parts so that you can select the appropriate choice or choices. As with a Solaris installation, Linux will perform the following operations.
Modern Linux usually recognizes most devices and installs without major hardware problems on standard desktop and laptop.
Note: In Solaris, the installation program will use the current console as an I/O device, and if you are using a serial interface, it will use that same serial interface. In Linux for IA32 , the default console device used for installation is the graphics card. If you need to install the system using a serial interface, you need to specifically tell the installation program to do so by adding the nofb console=ttyS0 kernel boot options.
In Solaris, you can install using the local graphic display or the serial interface. In Linux, you can install using the local graphic display, serial interface, and a few other remote modes.
In RHEL, you have the following options:
|Add a display=IP_OF_REMOTE_X:0 argument to the kernel boot line for using a remote X Server for displaying the installation GUI.|
|Add a vnc vncpassword=MIN_6_CHAR_PASS argument to the kernel boot line for using a VNC client from another machine to connect to the installation GUI.|
In SLES, you have the following options:
|Add a usessh=1 sshpassword=MIN_1_CHAR_PASS argument to the kernel boot line for starting a ssh installation. If you connect with ssh -X, you can have graphical GUI.|
|Add a vnc=1 vncpassword=MIN_5_CHAR_PASS argument to the kernel boot line for using a vnclient from another machine to connect to the installation GUI.|
The two minimum partitions are the root partition, signified with a forward slash (/), and a swap partition, which Linux uses as virtual memory. You also would benefit form a separate /home partitions for the reasons explained above. Traditionally, the size of the swap partition is equivalent to (or a multiple of) the amount of hardware RAM you have installed.
If you have only these two partitions, YaST will put all standard directories on the same partition as /. These are
/boot—Files to boot Linux.
/home—Each user gets a data directory under this one (should generally be a separate partition)
/lib—Libraries, the underlying code for many applications.
/media—Removable disks and drives (floppy discs, CD-ROMs, Zips).
/mnt—The mount directory, where all partitions (mount points) are listed.
/opt—Some applications install to this directory instead of /usr.
/proc—A dynamic directory where all running processes are logged. Constantly changing.
/root—Not to be confused with plain / (also called "root"), this is the home directory for the root user.
/sbin—System binaries, usually files that need to run during startup.
/usr—Most applications, libraries and man files.
/var—Variable data, including syslog, print spoolers, mail files, cron files, are stored here.
Instead of a single file linux configuration files are often spitted into chunks which are stored then into directories. The main file just assembles the chunks. As in other areas of life this quest to more flexibility actually sometimes backfire and turns into its opposite.
Some of those "hacked" files include /etc/profile (with chunks stored at /etc/profile.d), crontab (crontab.d), syslog (actually Suse uses syslog-ng instead of regular syslog), etc. RC files are structures similarly to Solaris with links to each run level.
Some of the more important system-related configuration files in this directory are
Suse uses different default shell. But it is a better interactive shell then Korn shell.
Also the default ksh in linux is broken and ksh93 should be installed. It is also more reliable for complex scripts.
We call repositories "services" in SUSE Linux Enterprise. These commands have been tested on a SLES 10 SP1.
1) First create a directory where you will store your ISO files.
2) Now create your ISO
mkisofs -J -R -iso-level 4 -o /home/sources/sles10sp1.iso /media/SLES10SP_001/Click to view
3) Now we add the ISO as a service (installation source)
zypper sa "iso:/?iso=/home/sources/sles10sp1.iso" "SLES 10 SP1"
4) Verify that the service has been successfully added
5) Now we can delete the DVD as a service
zypper sd 1
6) Finally we now test the ISO as a service and install a package like nmap
zypper in -y nmap
Some miscellaneous tweaks that might be desired:
- Disable splash screen (mainly for servers which have no X) - /etc/sysconfig/bootsplash:SPLASH="no"
- Enable clearing out of /tmp and /var/tmp - /etc/sysconfig/cron:MAX_DAYS_IN_TMP="30" MAX_DAYS_IN_LONG_TMP="90" LONG_TMP_DIRS_TO_CLEAR="/var/tmp" OWNER_TO_KEEP_IN_TMP="" DAILY_TIME="HH:MM" # where HH:MM is the desired time to run cron.daily jobs CLEAR_TMP_DIRS_AT_BOOTUP="yes" SEND_MAIL_ON_NO_ERROR="yes" # if you have jobs from which you wish to see output SYSLOG_ON_NO_ERROR="yes"
- Enable chrooted postfix - /etc/sysconfig/postfix:POSTFIX_CHROOT="yes" POSTFIX_UPDATE_CHROOT_JAIL="yes"
- Enable tighter permissions of common programs - /etc/sysconfig/security:PERMISSION_SECURITY="secure local"
- Enable snort - /etc/sysconfig/snort:SNORT_ACTIVATE="yes" SNORT_AUTO="your-ip/mask" SNORT_PROMISC="yes"
- Enable magic SysRq key - /etc/sysconfig/sysctl:ENABLE_SYSRQ="yes"
Check out this new Novell Connection article by Nathan Conger for instructions on how to set up and configure a Network Installation Server for speedy, hands-free installations.
It turns out that SUSE Linux Enterprise won't boot properly if you move the hard drive from one machine to another machine (even if you connect the hard drive to the same controller). Not to worry - Muhammad Sharfuddin figured out a workaround, and shares it here.
Ashish Kumar shares a tip on how to install SLES on a machine that has Linux (boot loaded GRUB) already installed.
Scott Morris shares a new bash script that will help you get a web server installed and running with minimal effort.
September 12, 2002 | IBM
SuSE Server Setup
- 4.1 Setting Up Filespace
- 4.2 Copy Installation Media
- 4.3 Enable Remote Access
- 4.4 Package Customisation
SuSE Client Install
The installer certainly takes a while, but after the install, the system is set up with all online repose including non-oss repos (including if I remember correct packman) and all installed packages (and thus the whole OS) were up to date.
It certainly takes a while (though only an hour orso here) but it isn't 'antiquated'. It has many more options and features available than ubuntu and pclinuxos for example, and it leaves your system fully updated with all the latest updates.
That said, I do imagine that would be difficult to see after being bored to death for 6 hours. I certainly don't blame you for some hard feelings there. The livecd system would indeed by a good idea.
It is not necessary to download anything from the internet during installation. If you only want to use the CD medium uncheck the "Use online repositories" checkbox. It needs to be selected by default so netinstalls will "just work", and CD users can still have a complete experience with flash, java etc if they have an internet connection during install.
A live-cd with installer will be released in a week or so. (There is one for RC-1) This allows installing from the desktop as in some other distributions. It is significantly less flexible than the normal installer though. And using a livecd does not show whether things will work, in fact things are far less likely to work on a livecd.
Codec installation from packman you should find significantly easier than in previous versions. If you attempt to play an mp3 in e.g. amarok if you don't have fluendo's support installed (I think it will be if you included media from the online repositories) Then you would be linked to http://software.opensuse.org/codecs
The "community information" there will get you the fullest support, and will no longer require knowing how to add the packman repository etc.
Google matched content
Installing Linux Suse 11
Novell Documentation SUSE Linux Enterprise Server 10 - Installation Summary
Linux Partition HOWTO
Network Install HOWTO
C H A P T E R 5 - Installing SUSE Linux Enterprise Server 9 and 10
Novell Documentation SUSE Linux 10 - SUSE Linux 10 Reference GuideSection 1.0, Remote Installation
Novell is one of the few linux vendors that provides manuals that try to help users beyond installing the product. The following manuals are available for OpenSuse 11.2:
Getting Started view size last update openSuse 11.2 Start-Up html 2 MB 12/07/2006 KDE Quick Start html 2 MB 12/07/2006 GNOME Quick Start html 2 MB 12/07/2006
User Guides view size last update KDE User Guide html .1 MB 12/07/2006 GNOME User Guide html 10 MB 12/07/2006
Administration view size last update openSuse 11.2 Reference Guide html 7 MB 12/07/2006 AppArmor 2.0.1 Administration Guide html 2 MB 12/07/2006 AppArmor 2.0.1 Quick Start html 1 MB 12/07/2006
Additional Information view size last update Release Notes html 12/07/2006
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least
Copyright © 1996-2018 by Dr. Nikolai Bezroukov. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) in the author free time and without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info|
The statements, views and opinions presented on this web page are those of the author (or referenced source) 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.
Last modified: April 18, 2018