Instalace Solarisu 10 --------------------- clustery: seznamnainstalovanych clusteru /var/sadm/system/admin/CLUSTER seznam clusteru: SUNWCreq - Core Distribution SUNWCuser - End User distribution SUNWCprog - The Developer Distribution SUNWCall - Entire Distribution SUNWCxall - Entire Distribution plus OEM support Naroky na HW RAM uplne minimalni minimum: 64 M pouzitelne minimum: 128 M doporucene minimum: 256M pro consoli: 128-384M pro GUI: >384M CPU SPARC: 200MHz x86: 120MHz HDD 5 GB je minimum kolik zabiraji jednotlive typy instalace: 2.0 GB - Reduced Network Support Software Group 2.0 GB - Core System Support Software Group 5.0 GB - End User Solaris Software Group 6.0 GB - Developer Solaris Software Group 6.5 GB - Entire Solaris Software Group 6.7 GB - Entire Solaris Software Group Plus OEM Support Instalace na SPARC: Posbirat vsechny ty pitome pozadavky jako je IP, maska, heslo roota a podobne Boot instalace z CD/DVD-ROM boot cdrom - GUI instalace boot cdrom - text - desktop session boot cdrom - nowin - console session logy z instalace jsou dostupne v adresarich /var/sadm/system/logs /var/sadm/install/logs Instalace na x86 boot z diskety: copy Solaris Device Configuration Assistant to diskette boot z CD/DVD-ROM: proste nabootuj :-) po bootu je mozne behem 5 sekund stisknout ESC pro spusteni DCA instalace ovladacu instalace ITUs (co to je?) vypnuti ACPI nastaveni TTY reset the default boot device po probehnuti DCA na nas vybafne pozadavek na vyber typu instalace: 1) Solaris Interactive klasicka instalace v GUI 2) Custom Jumpstart 3) Solaris Interactive Text (desktop session) textova instalace v grafice 4) Solaris Interactive Text (console session) klasicka textova instalace po volbe se pokud je potreba spusti ptregamm kdmconfig Po instalaci je treba provest reboot a je hotovo. sys-unconfig "odnastavi" pocitac a vypne vhodne pokud po instalaci chcete dat pocitac zakaznikovi at si nastavi parametry pro pripojeni sam Souborove systemy: ------------------ Slices: SPARC 0 root 1 swap 2 backup 3 Vx 4 Vx 5 var 6 7 metadb x86 0 root 1 swap 2 backup 3 Vx 4 Vx 5 var 6 7 metadb 8 boot 9 alternates prtconf - print system configuration -D ukaze u kazdeho zarizeni i ovladac -F vypise device-path k framebufferu (symlink z /dev/fb) -p ukaze device-tree z PROM (sparc) nebo z bootu x86 -V verze PROM na SPARCu nebo booting-system na x86 sysdef - print system definition -i system config from /dev/kmem -h hostid -d vypis jako device-tree -D ukaze ovladac pro kazde zarizeni /etc/path_to_inst mapovani cisel instanci na zarizeni je modifikovan pomoci: add_drv drvconfig devfsadm Natahne postupne vsechny ovladace z jadra, pokusi se jim priradit zarizeni. Pokud se podari, tak vyrobi spravne odkazy v /dev/ a /devices/, demon devfsadm slouzi pro dynamickou rekonfiguraci -C clean-up mode vycisti vsechny odkazy -c device-class omezeni na urcite druhy zarizeni disk tape port audio pseudo -i driver-name omezi pouze na tento ovladac -t devlink.tab pouziti alternativniho devlink.tab -r root pouziti jineho root adresare -v ukecanej rezim drvconfig, disks, ports reconfigurtion boot parametr -r pri bootu vytvorit soubor /reconfig rmformat - sprava RW medii jako jsou diskety -H format 1.44MiB diskety -D 720KiB disketa -l vypis vsech dostupnych zarizeni fmthard rozdeli disk prtvtoc /dev/rdsk/c0t0d0 | fmthard -s - /dev/rdsk/c0t1d0 umi zapsat bootblk a pboot (na x86), ale lepsi je installboot fmthard -p pboot -b bootblk /dev/rdsk/c0t1d0s0 bootblk je soubor /usr/platform/`uname -i`/lib/fs/ufs/bootblk pboot je soubor /usr/platform/`uname -i`/lib/fs/ufs/pboot format rozdeleni disku vypis rozdeleni analyze - testy disku nedestruktivni read destruktivni write compare fdisk zapise rozdeleni disku prtvtoc vytiskne rozdeleni disku cdrw -l vypis zarizeni -d cdrom0 identifikace zarizeni na ktere pisu -b fast, all smazani zaznamu -M identifikace media v mechanice -x grabnuti audia -iS -p file.iso vypaleni CDcka z isa mkisofs -R - rock ridge -J - joliet -o file - vystupni soubor -V label - popisek mkfs -F fstype newfs -b velikost bloku fsck -y porad na vsechno rika ano mount -F fs -o options clri clear i-node cfsadmin cachefsstat cachefslog cachefspack cachefswssize Zalohovani a obnova dat ----------------------- ufsdump ufsrestore fssnap Balickovaci system a patche: ---------------------------- pkgadm pkgadd pkgrm pkginfo pkgchk pkgtrans prevod formatu balicku z "file system" z adresare /tmp do datastream prevede balicky pkg1 a pkg2 pkgtrans -s /tmp /tmp/neco pkg1 pkg2 -s vystup bude datastream, defaultne je file system -k keystore uloziste privatniho klice -P heslo heslo k privatnimu klici cilem/zdrojem muze byt i obecne zarizeni /etc/device.tab patchadd patchrm showrev prodreg keytool Nastroje pro spravu Solarisu 10 ------------------------------- smc - Solaris Management Console smcron - manages crontab jobs smdiskless - manages diskless client support smexec - manages exec_attr databaze smgroup - manages group entries smlog - manages and view WBEM log files smmultiuser - manages bulk operations on multiple user accounts smosservice - Add Operating System (OS) services and diskless support smprofile - manages profile in the prof_attr and exec_attr databases smrole - Manages roles and users in role accounts smserialports - manages serial ports smuser - manages user accounts Boot Solarisu na x86 -------------------- Primary boot ------------ Boot from FDD 0. sektor na FDD obsahuje Master Boot Block MBB nacte image boot loaderu strap.com strap.com nacte boot.bin boot.bin natahuje jadro Boot z CD-ROM je stejny jako z FDD, jen je MBB nahrazeny podle specifikaci El-Torito Boot z HDD 0. sektor na HDD obsahuje MBB a FDISK tabulku (rozdeleni disku) MBB najde v FDISK tabulce prvni aktivni oddil nacte z nej prvni sektor a skoci na jeho prvni byt v pameti (az potud to je standardni PC-kompatinilni rezim boot) boot solarisu: slice s0 1 cylindr slice boot 1. sektor obsahuje partition boot program (pboot) 2. a 3. sektor obsahuje VTOC (tabulka rozdeleni na slices) 4. a dalsi sektory bootblk Master boot program (mboot) nacte partition boot program (pboot) a spusti ho pboot nacte bootblk a spusti ho pokud disk obsahuje dalsi partisny, tak muze user nabootovat z jine bootblk nebo strap.com nacte boot.bin z UFS / a spusti ho Boot ze site boot z FDD PXE Secondary boot -------------- boot.bin prepne CPU do 32bit, paget, protectet rezimu provede omezenou inicializaci stroje Configuration Asistant pokud je auto-boot?=false, tak se zastavi boot Disky (i CDROM) zvladne v pripade, ze pouzivaji UFS network rarp dhcp root se mountuje pres NFS po namountovani / spusti nacte /etc/bootrc Jakmile jsem uz v prikazovem radku, tak muzu zadat prikaz ekvivalentni boot -as b -as Soubory: ------- /etc/bootrc /platform/`uname -i`/boot/solaris/boot.bin SMF --- boot -m verbose boot -m milestone=1 /var/svc svcs - vypis vsech sluzeb a jejich stavu -x - detailni vypis -p - vypise procesy, ktere patri dane sluzbe -d - vypise sluzby, ktere na dane sluzbe zavisi -l detailni popis sluzby -H -o state,fmri svcadm - ovladani sluzeb enable - enable and online service disable - disable and offline service restart - restart specified service refresh - re-read service configuration mark - set maintenance state clear - clear maintenance state milestone - advance to a service milestone svcprop - vypis parametru sluzby hlavne pro skripty svccfg archive > /root/backup.xml - vypise stav vsech sluzeb, vhodne pro archivaci apply /root/nove.xml - natazeni nove konfigurace inetadm stav sluzeb degraded - The service is running, but something is wrong, or its capacities are limited in some way. disabled - The service has been disabled and is not running. legacy_run - A legacy rc.X script has been started by the system, and is running. We'll talk more about legacy services later. maintenance - The instance has encountered some sort of error, and it needs to be repaired by an administrator. offline - The service is enabled, but not running yet, usually because a service it depends on is not online yet. online - The service is both enabled and running successfully. uninitialized - svc.startd has not yet read this service's configuration. pridani nove sluzby do solarisu: /lib/svc/method/ tady v tom adresari je treba vyrobit shell skript, ktery startuje a stopuje sluzbu /var/svc/manifest/application/ ke skriptu je treba udelat odpovidajici xml ktery naimportujeme do systemu: svccfg -v import /var/svc/manifest/application/neco.xml no a pak jen omrkneme jestli funguje svcs -vx neco