VNC server
e.g Tightvnc
user profile based (per user profile)
~/home/username/.bashrc
e.g /home/ammar/.bashrc
Machine Based
/etc/rc.d/init.d
keep the script in init.d
to access GUI
init .d is used mainly for
1. GUI
2. CLI
no more than one concurrent connection
one of these will be the init level
alt+ctrl+(F1-F10) are the user interfaces. example
alt+Ctrl+F1 = may be the GUI for Ubuntu
alt+Ctrl+F5 = Maybe the GUI (depends on different Distribution, tested on mostly RHEL, or based distro)
The console is always active at the back end. and the GUI only will be active in the background if the system boots in GUI mood (init 5) otherwise GUI can be started by the user IF the system is running Xserver at the backend
Xserver has 2 modes
1 per user (init 5)
2 per System ( always started by the user )
Run Levels (init Run Levels)
0 = Halt
example #init 0
~ or $ sudo init 0
1 = single user mood (used for Troubleshooting)
example for the running system in case of Miss config (chawal) and stuck
#init 1
1. most services will be off, Read write permissions will be limited, and the mount may be unmounted
in some cases, you will have to Chroot
2. for troubleshooting, use init 1 and do chroot to execute the next commands
3. system is not booting at all, boot from external media,
dd if=/bootfile of=/dev/sdX
dd= duplicate disk, if=input file, of =output file path
2 = Multiuser mode Without NFS
3 = wiely used for servers no GUI
4 = Undefined
5 = GUI Meant for Desktop users
6 = Reboot or schdual reboot, halt
examples
shutdown -h 23:30 it will halt the system at 11:30 pm
shutdown -r 03:30 it will reboot the system at 03:30 am
Comments
Post a Comment