By -
Installation of LinuxMethods: Text, GUI, Scripted (optional) - on multiple machinesNetwork installation (ftp,http,LAN)
- otherwise choose text or GUI
Network installation not for novice users

What type of system would you like to install?
- Workstation- Server- Laptop- Custom- Upgrade
existing systemDisk partitioning setup
Autopartition (basic partition),
Disk Druid (partition yourself),
fdiskAutopartition -> Automatic Partitioning :
-Remove all Linux Partitions on this system
-Remove all partitions on this system-Keep all partitions and use existing free spaceDevice/dev/sda (scsi disk)
- holds info of every partition/dev/sda1
- Mount Point /boot/dev/sda2
- Mount Point /Boot Loader

Configuration
-Use GRUB Boot Loader
-Use LILO Boot Loader
-No Boot LoaderBoot Loader
Password:___
Confirm:___
Firewall Configuration:
Security Level: High, Medium, No firewall
Root Password:
Add User:
User ID Password Full Name User
Account Setup:

Authentication Configuration
- Use Shadow Passwords
- Enable MD5 Passwords
-Enable NIS-Enable LDAP
-Enable Kerberos
Package Group Selection:
-Printing Support
-Classic X Window
-GNOME
-KDE
-SQL Database Server
-Anonymoud FTP Server
-NFS File Server
-EMACS
-Router/Firewall
-Web Server
-Software Development
-Kernel DevelopmentBoot Disk (without installed LILO on your system)
May be used as rescue disk

Comments

Post a Comment

Popular posts from this blog

teamcity Automatic Agent Start under Linux

By OK -
Automatic Agent Start under Linux To run agent automatically on the machine boot under Linux, configure daemon process with the  agent.sh start  command to start it and  agent.sh stop  command to stop it. Refer to an example procedure below: 1. Navigate to the services start/stop services scripts directory: cd /etc/init.d/ 2. Open the build agent service script: sudo vim buildAgent 3. Paste the following into the file : #!/bin/sh ### BEGIN INIT INFO # Provides: TeamCity Build Agent # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start build agent daemon at boot time # Description: Enable service provided by daemon. ### END INIT INFO #Provide the correct user name: USER="agentuser" case "$1" in start) su - $USER -c "cd BuildAgent/bin ; ./agent.sh start" ;; stop) su - $USER -c "cd BuildAgent/bin ; ./agent....
Read more

15 managing disk - understanding /etc/fstab xfs_admin mount -o rw,remount /

By OK -
the classical way to mount filelsystems automatically is to use fstab there is another method which is based on systemd [root@svn ~]# cat /etc/fstab # # /etc/fstab # Created by anaconda on Wed Apr 26 17:25:59 2017 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/mapper/cl-root     /                       xfs     defaults        0 0 UUID=6e3708b2-09ea-43f3-b0f0-9b43a157b3b1 /boot                   xfs     defaults        0 0 /dev/mapper/cl-swap     swap                    swap    defaults        0 0 [root@svn ~]#  #description /boot - where you want to mount filesystem xfs - filesystem defaults ...
Read more

HAproxy logging

By OK -
ubuntu@ubuntu:/etc/haproxy$ cat /etc/rsyslog.d/haproxy.conf # Create an additional socket in haproxy's chroot in order to allow logging via # /dev/log to chroot'ed HAProxy processes $ModLoad imudp $UDPServerRun 514 local0.* -/var/log/haproxy-0.log local1.* -/var/log/haproxy-1.log ### keep logs in localhost ## $AddUnixListenSocket /var/lib/haproxy/dev/log ------------------- ubuntu@ubuntu:/etc/haproxy$ cat /etc/haproxy/haproxy.cfg global chroot /var/lib/haproxy user haproxy group haproxy log 127.0.0.1   local0         log 127.0.0.1   local1 notice daemon frontend www     bind 192.168.40.128:8282    # haproxy public IP     default_backend as-backend    # backend used backend as-backend    balance leastconn    mode http  server as1 192.168.40.128:8082 check    # application srv 1 defaults log ...
Read more