Posts

Showing posts from November, 2020

AUTOMATING INSTALLATION WITH KICKSTART

Image
  CHAPTER 1  AUTOMATING    INSTALLATION    WITH      KICKSTART Some Information about Kickstart If we install Linux OS on  single standalone machine, it is easy to install manually. But if we want to install 30/40 or more machines  for your organization, then it will be more complicated work due of time. Right? So, then we will use automated  installation process. so that all client machines can be installed from a single server machine automatically.  That's why - we will  " kickstart method" **  Kickstart  is an automated installation method used primarily by Red Hat Enterprise Linux. ** Kickstart in Red Hat Enterprise Linux is similar to Jumpstart for Oracle Solaris, or to an unattended installation (WDS Deployment) for Microsoft Windows. Video Links: Part-01: Part-02: Our LAB Scenario : But we will take One Client and One Server Server Name -> Kickstart-Server Client Name -> Kickstart-Client-1 In VMware , We will connect those 2 machines by host-only adapter No

CHAPTER-14 : ACCESSING LINUX FILE SYSTEMS

  CHAPTER 14 ACCESSING LINUX    FILE SYSTEMS 1.        Hard disks and storage devices are normally divided up into smaller chunks called -- a.        Partitions b.       Drives c.        Parts d.       Block device   2.        Storage devices are represented by a special file type called ---- a. Partitions b. Drives c. Parts d. Block device   3.        The block device is stored in the ----- directory a.        /etc b.       /var c.        /dev d.       /sbin 4.        the first SCSI, PATA/SATA, or USB hard drive detected as   ------ , the second is --------- a.        /dev/sda   &   /dev/sdc b.       /dev/sda   &   /dev/sdb c.        /dev/sdb1   &   /dev/sdc2 d.       /dev/sda1   &   /dev/sda2   5.        The first primary partition on /dev/sda is --------- , the second partition is ------- , and so on a. /dev/sda   &   /dev/sdc b. /dev/sda   &   /dev/sdb c. /dev/sdb1   &   /dev/sdc2 d. / dev/sda1