|
||
First, it is necessary to configure boot of schemes so that it initialize first for cdrom. After this step,
it places the compact disc 1 of installation of the Slackware-Linux version 10.2 in drive and binds schemes it.
When the compact disc will be identified will go to appear the figure below.
If its schemes will be one schemes with record in standard IDE only uses a keyboard the ENTER so that he is
loaded boot of the compact disc If in the case, its schemes will have HD SCSI, types above in prompt shown
in the figure scsi.s. If it will have some doubt in which Kernel will have to choose for its it later schemes,
it types F2 and F3 that it shows to a small available description of all kernel.
After the choice of kernel of boot, will go to appear the screen (Picture2), that it will go to ask to which
the layout of the used keyboard.
Where we can simply ENTER if you it will be to choose keyboard US.
After the election of the keyboard will go to appear the screen below (Picture3) where it asks for to carry through login as root to make the
installation. It types root and it uses a keyboard ENTER.
Now we go prepares hard disk to carry through the installation properly said. It types in the prompt
When you start fdisk you need to specify the device to use. By default it will try to open /dev/hda, but in some cases this is not the correct device
to use. Just specify the device name after typing fdisk on the command line.
This will tell fdisk to open the primary slave IDE hard disk. Notice that you do not specify a partition number on the device name.
An alternative to fdisk is cfdisk, which provides a menu-based setup program for the partition setup (DOS users comfortable with DOS's fdisk may find
this program easier). Just run cfdisk at the prompt instead of fdisk.
# fdisk /dev/hda
The number of cylinders for this disk is set to 4998.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/hda: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 1429 11478411 83 Linux
/dev/hda2 2999 4997 16056967+ f W95 Ext'd (LBA)
/dev/hda3 1430 1493 514080 82 Linux swap / Solaris
/dev/hda4 1494 2998 12088912+ 83 Linux
/dev/hda5 2999 4997 16056936 83 Linux
Partition table entries are not in disk order
Command (m for help):
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)
# cfdisk /dev/hda
cfdisk 2.12q
Disk Drive: /dev/hda
Size: 41110142976 bytes, 41.1 GB
Heads: 255 Sectors per Track: 63 Cylinders: 4998
Name Flags Part Type FS Type [Label] Size (MB)
------------------------------------------------------------------------------
hda1 Boot Primary Linux ReiserFS 11753.93
hda3 Primary Linux swap / Solaris 526.42
hda4 Primary Linux ReiserFS 12379.05
hda5 Logical Linux ReiserFS 16442.34
Logical Free Space 8.23
[Bootable] [ Delete ] [ Help ] [Maximize] [ Print ]
[ Quit ] [ Type ] [ Units ] [ Write ]
Toggle bootable flag of the current partition
So what kind of partitions should we make? It is always a good idea to make the swap
partition first so you specify an exact size for it. It is also
a good idea to make seperate partitions for /, /home, and /usr.
People will tell you many things about how to divide up your disk, but it really
comes down to what you want.
There are many good reasons to breaking it up into /, /home, and /usr. For example:
Home directories are always on their own partition and you can upgrade the distribution
without having to backup the home directories.
/usr is where software goes, so you can keep that whenever you upgrade distributions.
The root directory should really remain untouched, except for the modified files in /etc and root's home directory.
Others may tell you that you must have a seperate /var partition so log files won't fill
up the root filesystem or so that the mail spool gets its
own partition. Really, the choice is yours. Experiment with it, you can always change it later.
Create swap partition.
What is swap partition?
Swap partition is linux systems typically use a partition as swap space. This is where unused items taking up space in memory are placed until they
are needed again so that the memory they are using can be used for something else. Other operating systems use a file on the file system for this
purpose, and while Linux can be set up to do the same thing it is typically set up to use a swap partition because it is faster and isolated from the
rest of the file systems.
But you can't have too much swap space. Although excessive swap space may amount to wasted resources, it will not cause the system to exhibit
thrashing or otherwise cause operational problems. It simply will not get used unless memory usage escalates.
Enter the ADDSWAP to set up our swap partition
The first thing that most new users shifting from Windows will find
confusing is navigating the Linux filesystem. The Linux filesystem
does things a lot more differently than the Windows filesystem.
This article explains the differences and takes you through the
layout of the Linux filesystem.
For starters, there is only a single hierarchal directory structure.
Everything starts from the root directory, represented by '/', and then
expands into sub-directories. Where DOS/Windows had various partitions and
then directories under those partitions, Linux places all the partitions
under the root directory by 'mounting' them under specific directories.
Closest to root under Windows would be c:.
Under Windows, the various partitions are detected at boot and assigned a
drive letter. Under Linux, unless you mount a partition or a device, the
system does not know of the existence of that partition or device. This
might not seem to be the easiest way to provide access to your partitions
or devices but it offers great flexibility.
This kind of layout, known as the unified filesystem, does offer several
advantages over the approach that Windows uses. Let's take the example of
the /usr directory. This directory off the root directory contains most of
the system executables. With the Linux filesystem, you can choose to mount
it off another partition or even off another machine over the network. The
underlying system will not know the difference because /usr appears to be
a local directory that is part of the local directory structure! How many
times have you wished to move around executables and data under Windows,
only to run into registry and system errors? Try moving c:windowssystem
to another partition or drive.
Another point likely to confuse newbies is the use of the frontslash '/'
instead of the backslash '' as in DOS/Windows. So c:windowssystem would
be /c/windows/system. Well, Linux is not going against convention here.
Unix has been around a lot longer than Windows and was the standard a lot
before Windows was. Rather, DOS took the different path, using '/' for
command-line options and '' as the directory separator.
[A] The A (base) series contains the kernel and main system utilities.
[AP] The AP series is a collection of useful applications.
[D] The D series contains compilers, debuggers, and other programming tools.
[E] The E series contains the GNU Emacs advanced real-time display editor
[F] The F series contains essential documentation for Linux system administrators.
[K] The K series contains the source code for the linux kernel.
[KDE] The KDE series contains the K Dekstop Environment and related libraries.
[KDEI] The KDEI series provides support for languages other than US English in KDE
[L] The L series contains important libraries needed by the rest of the system.
[N] The N series contains network related client and servers
[T] TeX is a typesetting system often used for mathematics and technical papers
[TCL] The TCL series contains the TcL/Tk/TclX languages and programs that us them
[X] The series containes X, the window system (or GUI) used by linux
[XAP] The XAP series is a collection of applications for X.
[Y] The Y series contains a collection of classic text-based games.
After selecting expert options, screen will go to A series package. We'll select what package we need, certain important package already selected
for us. So we go to unselected packages if needed to install.
Press SPACEBAR to select or unselect. Series A Unchecked
1.kbd
2.minicomm
3.pcmcia-cs
Series AP
Checked
1.at
2.groff
3.man
4.man pages
5.mysql
6.quota
7.rzip
8.sudo
9.textinfo
10.vim
11.zsh
Series D
Checked
1.perl
Series N
Checked
1.apache
2.curl
3.dhcpd
4.dhcp
5.elm
6.fetchmail
7.getmail
8.gnupg
9.htdigs
10.imapd
11.inetd
12.iproute2
13.iptables
14.iptrafs
15.iltp
16.links
17.lynx
18.mail
19.metamail
20.mod_ssl
21.mutts
22.nc
23.ncftp
24.netwatch
25.nmap
26.ntp
27.openssh
28.openssl
29.php
30.pidentd
31.pine
32.popa3d
33.procmail
34.proftpd
35.rp_pppoe
36.sendmail
37.sendmailcf
38.stunnel
39.tcpdump
40.tcpip
41.traceroute
42.vsftpd
43.wget
44.whois
After that the screen of Expert LILO Installation will appear.(Picture32) Then select Begin Start LILO configuration with a new LILO header. After hit Begin option just enter screen below. (Picture33) Then screen to select frame buffer console will appear, just select option default (picture34) After that, screen to Select LILO Target Location will appear (Picture35). Select MBR (Master Boot Record) Then confirm location to install LILO, type /dev/sda (refer to partitionn table) (Picture36) After confirm location to install LILO, then choose LILO timeout. Select None because we have only one operating system (os). See (Picture37) After that, screen will back to menu Expert LILO Installation. Then select option Linux, See (Picture38) After select Linux options, the screen will go to menu Select Linux Partition and type /dev/sda1 to confirm boot partition for LILO. See (Picture39) Then, give a name to boot partition. See (Picture40). Now, the screen will go back again to menu Expert LILO Installation, now select Install, to install LILO. See (Picture41) Now, the screen will go back again to menu Expert LILO Installation, now select Install, to install LILO. See (Picture41) Now select
First enter hostname for your machine, see (Picture43)
Then, enter the domain name for network, see (Picture44)
After that, screen will appear menu Setup IP address, select static ip. See (Picture45)
Then enter the ip address, see (Picture46)
After that enter the netmask for local network, see (Picture47)
Then enter the gateway address, see (Picture48)
Now, enter the nameserver, see (Picture49)
After that, confirm your network setup and select
Now confirm startup services to run, See (Picture51)
After that, we'll set hardware clock, select NO for hardware clock is set to local time. See (Picture52).
Now, select local time. See (Picture53)
Now enter your password. See (Picture54)
After this, Exit your slackware setup and reboot the machine. See (Picture55)
|
||
http://opensource.terengganu.gov.my |