DOCSLIB.ORG

Copyrighted Material

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Copyrighted Material Book Title <Chapter No> V1 - MM/DD/2010 INDEX Symbols AFP. See Apple Filing Protocol AGL, 35 \ (backslash), NVRAM variables, 199 Air Drop, 8 ?? (question mark-double), dyld, 114 alarm_expire_timer, 380 alarm_lock, 380 allmemory(1), 160, 161 A alloca(), 138–139 AllocatePages, 189 -a, 126 AllocatePool, 189 aapl, 193 allocation fi le, B-Tree, 642 ABIs, 779–780 alloc_size, 469 abnormal_exit_notify, 438 _AllowedClients, 257 aborts, 270 al_port, 380 ABRT(), 534 alternate data streams, 611 Absinthe, 173 AMFI. See AppleMobileFileIntegrity ABT, 268 amfi_*, 563 Accelerate, 35 Amfid, 244 accept(), 240 Animation, 201 Access Control Lists (ACLs), 578, 608 APIC. See Advanced PIC accessory_device_arbitrator, 244 APM. See Apple Partitioning Scheme Accounts, 35 App Store, 11, 25–26 accountsd*, 244 AppKit, 35 ACLs. See Access Control Lists AppKitScripting, 35 -acm, 578 apple argument, 130 acpi_*, 329 Apple Filing Protocol (AFP), 582, 651, 652 act_set_astbsd(), 325 Apple Partitioning Scheme (APM), 570–572 act_set_bsdast(), 536 Apple policy modules, BSD, 560–563 addDisk, 576 Apple Protect pager, 491–493 AdditionalEssentials.pkg, 216 Apple TV, 11–12 AdditionalSystemVoices.pkg, 216 AppleACPIPlatform.Kext, 329 Address Family (AF), 650 APPLE_BOOT_GUID, 193 Address Space Layout Randomization (ASLR), 12, 122, AppleEvents, 72–79 131–132, 173, 548–549 AppleFSCompressionTypeZlib.kext, 612 AddressBook, 35 COPYRIGHTEDAppleIDAuthAgent() MATERIAL, 242 ADD_TO_ZONE, 469 AppleMobileFileIntegrity (AMFI), 89–90, 331, Advanced PIC (APIC), 270 562–563 Adv-cmds, 14 AppleOnBoardSerialBSDClient, 656 AEDebug*, 73 AppleProfile*, 155 AEServer, 73 appleprofilepolicyd, 242 AF. See Address Family apple_protect_pager_setup(), 493 AF_, 650 AppleScript*, 35, 72–79 afc, 246 AppleShareClientCore, 35 affi nity, CPU threads, 415 AppleTalk, 35 AFFINITY_POLICY, 421 APPLE_VENDOR_NVRAM_GUID, 195 affinity_tag, 421 /Applicants, 23 AF_INET, 677 /Application, 25 793 bbindex.inddindex.indd 779393 99/29/2012/29/2012 55:56:50:56:50 PPMM Book Title <Chapter No> V1 - MM/DD/2010 applications – backing store applications ARM_ARCH, 12 bundles, 24 arm_init, 311 containers, Lion, 84–97 ARM_THREAD_STATE, 109 debugging arm_vm_init(), 311 crashes, 170–176 array, 255 hangs, 173–174 AS, 302 sampling, 173–174 asctl(1), 84 defaults, 30–32 A_SETCOND, 557 Java, 44–45 AsianLanguagesSupport.pkg, 216 NeXTSTEP, 4, 24 ASL, 70–71 OS X, 24–32 -asl_in 1, 70 Application Frameworks layer, 15 aslmanager, 242 Application Services, 18 ASLR. See Address Space Layout Randomization Applications, 26 assemblies /Applications, 23 ARM, 784–786 ApplicationServices, 35 mnemonics, 783–784 Application.System, 257 assert_wait, 406, 414 Application.User, 257 assert_wait_deadline, 430 <app>.pkg, 216 Assetsd, 244 Apsd, 244 AssetsLibrary, 35 ApTicket, 213 AST. See asynchronous system trap Aqua, 17–18 AST_*, 406, 424, 426, 430 arbiter, kernel, 262 ASTs. See Asynchronous Software Traps arch(1), 100, 101–102 ast_taken(), 425–426 architecture asynchronous interrupts, 431 ARM, 519 asynchronous kernel, 268 Intel, Mach physical memory management, 465–467 Asynchronous Software Traps (ASTs), 275, 423–427 kernel, 261–287 asynchronous system trap (AST), 325 XNU, 302–305 Atc, 244 Mach atd, 231 Intel, physical memory management, 465–467 atomicity VM, 447–462 ARM, 788–790 modular, 712–713 Intel, 787–788 OS X, 518 atrun, 231 PPC, 518–519 Attribute B-Tree, 640–641 arg_ptr, 304 Audio*, 35 arg_string, 304 audit(), 61 arguments, XNU boots, 329–331 audit_*, 60–61, 352 argv[], 326–327 AUDIT_ARG, 557 ARM, 12, 14 auditctl(), 61 architecture, 519 auditing, OS X, 59–62, 556–558 ASLR, 549 auditon(), 61, 557 assemblies, 784–786 AUDIT_SYSCALL_*, 557 atomicity, 788–790 authentication, 80 Darwin, 5 auto-boot, 212 EFLAGS, 296 autofsd, 587 exception vector, 268 Automator, 36 Intel trap handlers, 275–278 automount, 587 interrupts, 296 autorun, 237 iOS, 5, 261 AVFoundation, 35 kernel, 267–268 locking, 788–790 machine_init, 316 B multithreading, 787 registers, 776–779 -b, XNU boot argument, 330 SWI, 280 Background Color, 199 VM, 447, 791 BACKGROUND_APPLICATION, 423 voluntary user/kernel transition, 280–282 BACKGROUND_POLICY, 421 __arm__, 12 backing store, 452, 497 794 bbindex.inddindex.indd 779494 99/29/2012/29/2012 55:56:51:56:51 PPMM 10 Book Title <Chapter No> V1 - MM/DD/2010 BackupAgent – BSD BackupAgent, 173 installation images, 214–225 Backupd, 242 Mach zones, 470–471 bad_info, 395 traditional, 183–185 Baker, 11 XNU barriers, 256, 790–791 arguments, 329–331 BaseSystemBinaries.pkg, 216 kernel, 299–340 BaseSystem.dmg, 214, 215 Boot Camp, 204 BaseSystemResources.pkg, 216 boot loader, 184 Basic Input Output System (BIOS), 183–185 Boot Logo*, 199 Basic Security Module (BSM), 59 Boot Services, 188–191 BBTicket, 213 boot-args, 193 BeepGen, 191 launchd, 228 Berkeley Packet Filter (BPF), 701–705 nvram, 329 BigBear, 11 boot_args /bin, 22 dTrace, 202–203 binaries Lion, 201–202 BSD process creation, 516–522 Revision, 202 EFI, 187 Version, 202 ELF, 15–16 boot-command, 212 Mach-O, 522–525 boot.efi, 187, 195, 204 portability, 46, 502 BootServices, 201 __stubs, 115 EFI GUIDs, 192–193 universal OS X, 194–210 executables, 98 boothowto, 326 file(1), 99 boot-image*, 193 kernel, 100 BootMGR, 184 Mach-O, 102–105 bootsArgs, 304 OS X, 99 BootServices, 201 processes, 99–111 BOOT_SERVICES_TABLE, 188 Snow Leopard, 99 boot-signature, 193 Tiger, 6 bootstrap server, 234–235 widgets, 47 bootstrap_cmds, 300 /bin/csh, 21 bootstrap_server, 235 binding, Mach, 415 Bourne Again shell, 20 binfmt, 516 Bourne shell, 20 /bin/ksh, 21 BPF. See Berkeley Packet Filter /bin/sh, 20 bpfattach(), 702 /bin/tcsh, 21 BPF_WORDALIGN, 705 binutils, 102 bplist, 26 /bin/zsh, 21 bridge, 678 /bin/zsh -i, 241 BSD, 22, 45, 501–536 BIOC*, 702, 705 advanced aspects, 519–563 BIOS. See Basic Input Output System Apple policy modules, 560–563 bit shifting, 785 ASLR, 548–549 Blazakis, Dionysus, 561 cache, 545 bless(1), 204–206, 215 disk image fi les, 589 bless(8), 204–206 EFI, 203 block fragmentation, 624 heirlooms, 55–65 blockCount, 639 implementing, 503 BLOCK_IO_PROTOCOL, 190 initialization, 318 /bn/bash, 20 I/O Kit, 737, 769–771 Bom, 217, 613 kqueues, 555–556 bond, 678 ledgers, 398 Bonjour, 6 MAC, 318, 558–560 bool, 254 Mach, 343, 501, 510–512 boot, 183–225 tasks, 395 disk image fi les, 590–591 malloc(), 541–544 EFI, 185–210 _MALLOC, 479 iBoot, 210–214 mcache, 545 795 bbindex.inddindex.indd 779595 99/29/2012/29/2012 55:56:52:56:52 PPMM Book Title <Chapter No> V1 - MM/DD/2010 bsd – CARenderServerSBUserNotifi cationUIKit.statusbarserverbulletinboard.*.chatkit memory allocation fi le, 642 management, 539–549 Attribute, 640–641 pressure, 545 catalog, 633–640 mincore(2), 456 deletions, 636–637 msync(2), 454, 458 forks, 639–640 network stack, 649 hard links, 639 OS X, 501 insertions, 636 packet fi ltering, 693, 697 lookups, 634–636 POSIX, 501, 503 permissions, 637–639 system calls, 284–287 soft links, 639 processes, 504–508 components, 630–645 control and tracing, 525–529 defi nition of, 625 creating, 512–525 extent overfl ow, 640 groups, 507–508 header node, 627–629 lists, 507–508 HFS+, 624–645 software, 535 journaling, 642–643 structs, 504–507 volume header, 631–632 suspension and resumption, 529 hot fi les, 641–642 signals, 529–536 insertions, 624 handling by victims, 536 catalog, 636 hardware, 534 nodes, 625–627 slab allocators, 545 random access, 624 sysctl(8), 552–555 search, 624, 629–630 system calls, 47–48 updates, 624 threads, 508–512 buffer overfl ow, 131 objects, 508–510 bundle, 248 UNIX, 501–502 bundles work queues, 550–552 applications, 24 XNU, 49–50, 501, 504 Finder, 25 zones, 541–544 frameworks, 32–34 bsd, 307 Info.plist, 26 BSD(4), 167 NeXTSTEP, 4, 24 bsd_ast(), 536 OS X, 24 bsd_info, 510 Quicklook, 18 bsd_init(), 318, 320–325, 326, 544, 673 byteordering, 100 bsdinit_task(), 227, 325–328, 530 bsd/kern_descrip.c, 601–602 bsd/kern/kern_descrip.c, 603–604 C bsd/kern/mach_loader.c, 522–523 bsd/kern/makesyscalls.master, -c, dtruss, 151 285–286 C++, I/O Kit, 737, 740–741 bsd/kern/uipc_domain.c, 673 C++, 302 bsd/net/if_var.h, 680–681 cache, 23, 121, 545 bsd/net/kpi_protocol.h, 677 shared library, 121 -bsd_out, 70, 71 Unifi ed Buffer Cache, 484, 488, 596 BSD.pkg, 216 Calaccessd, 244 bsd/sys/file_internal, 602–603 CalendarStore, 36 bsd/sys/mount.h, 591–592 CALL, 279 bsd/sys/mount_internal.h, 592–593 call psignal(), 535 bsd/sys/protosw.h, 672–673 call_continuation(), 420 bsd/sys/sysent, 285 callnum, 156–157 bsd/sys/user.h, 508–510 calloutart, 508 bsd/sys/vnode_if.h, 597 canblock, 469 bsd_utasbootstrap(), 325 cansignal(), 535 bsd/uxkern/ux_exception.c, 529–533 can_update_priority(), 430 BSM. See Basic Security Module Carbon, 34, 122 bsm/security, 307 Carbon, 36 bstree, 253 CARenderServerSBUserNotificationUIKit. BTNodeDescriptor, 625 statusbarserverbulletinboard.*.chat B-Tree kit, 245 796 bbindex.inddindex.indd 779696 99/29/2012/29/2012 55:56:52:56:52 PPMM 10 Book Title <Chapter No> V1 - MM/DD/2010 Cascading Style Sheet – core dumps Cascading Style Sheet (CSS), 45 CodeRequirements, 717 widgets, 47 CodeResources, 29–32, 717 case sensitivity, 21, 619 codesign(1), 80, 86–87, 110 cat(1), 88–89 CodeSignatures, 717 catalog, B-Tree, 633–640 Collaboration, 36 deletions, 636–637 com.apple.audited.plist, 59 forks, 639–640 com.apple.blued.plist, 237 hard links, 639 com.apple.Boot.plist, 199 insertions, 636 com.apple.decmpfs, 612, 613 lookups, 634–636 com.apple.dock.extra, 247 permissions, 637–639 com.apple.iokit.matching, 237 soft links, 639 com.apple.kpi*, 714 Catalog Node ID (CNID), 633–634, 635 com.apple.syslogd.plist, 233–234 catch_mach_exception_raise, 533 com.apple.WindowServer.plist, 235–236 CC, 302 Comex, 11, 12 CCALL, 274 commpage, 318 CD-Audio File System (CDDAFS), 581 compartmentalization. See sandboxing CD-ROM File System (CDFS/ISO-9660), 582 compression, 7, 612–617 CFBundle*, 27, 248, 257, 718 compute_averages, 411 C++filt, 300 compute_priority(), 429 CG(11), 167 Computer Hardware Understanding and Development CGXServer.
Load more

Recommended publications
  • CERIAS Tech Report 2017-5 Deceptive Memory Systems by Christopher N
    CERIAS Tech Report 2017-5 Deceptive Memory Systems by Christopher N. Gutierrez Center for Education and Research Information Assurance and Security Purdue University, West Lafayette, IN 47907-2086 DECEPTIVE MEMORY SYSTEMS ADissertation Submitted to the Faculty of Purdue University by Christopher N. Gutierrez In Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy December 2017 Purdue University West Lafayette, Indiana ii THE PURDUE UNIVERSITY GRADUATE SCHOOL STATEMENT OF DISSERTATION APPROVAL Dr. Eugene H. Spa↵ord, Co-Chair Department of Computer Science Dr. Saurabh Bagchi, Co-Chair Department of Computer Science Dr. Dongyan Xu Department of Computer Science Dr. Mathias Payer Department of Computer Science Approved by: Dr. Voicu Popescu by Dr. William J. Gorman Head of the Graduate Program iii This work is dedicated to my wife, Gina. Thank you for all of your love and support. The moon awaits us. iv ACKNOWLEDGMENTS Iwould liketothank ProfessorsEugeneSpa↵ord and SaurabhBagchi for their guidance, support, and advice throughout my time at Purdue. Both have been instru­ mental in my development as a computer scientist, and I am forever grateful. I would also like to thank the Center for Education and Research in Information Assurance and Security (CERIAS) for fostering a multidisciplinary security culture in which I had the privilege to be part of. Special thanks to Adam Hammer and Ronald Cas­ tongia for their technical support and Thomas Yurek for his programming assistance for the experimental evaluation. I am grateful for the valuable feedback provided by the members of my thesis committee, Professor Dongyen Xu, and Professor Math­ ias Payer.
    [Show full text]
  • HTTP-FUSE Xenoppix
    HTTP-FUSE Xenoppix Kuniyasu Suzaki† Toshiki Yagi† Kengo Iijima† Kenji Kitagawa†† Shuichi Tashiro††† National Institute of Advanced Industrial Science and Technology† Alpha Systems Inc.†† Information-Technology Promotion Agency, Japan††† {k.suzaki,yagi-toshiki,k-iijima}@aist.go.jp [email protected], [email protected] Abstract a CD-ROM. Furthermore it requires remaking the entire CD-ROM when a bit of data is up- dated. The other solution is a Virtual Machine We developed “HTTP-FUSE Xenoppix” which which enables us to install many OSes and ap- boots Linux, Plan9, and NetBSD on Virtual plications easily. However, that requires in- Machine Monitor “Xen” with a small bootable stalling virtual machine software. (6.5MB) CD-ROM. The bootable CD-ROM in- cludes boot loader, kernel, and miniroot only We have developed “Xenoppix” [1], which and most part of files are obtained via Internet is a combination of CD/DVD bootable Linux with network loopback device HTTP-FUSE “KNOPPIX” [2] and Virtual Machine Monitor CLOOP. It is made from cloop (Compressed “Xen” [3, 4]. Xenoppix boots Linux (KNOP- Loopback block device) and FUSE (Filesys- PIX) as Host OS and NetBSD or Plan9 as Guest tem USErspace). HTTP-FUSE CLOOP can re- OS with a bootable DVD only. KNOPPIX construct a block device from many small block is advanced in automatic device detection and files of HTTP servers. In this paper we describe driver integration. It prepares the Xen environ- the detail of the implementation and its perfor- ment and Guest OSes don’t need to worry about mance. lack of device drivers.
    [Show full text]
  • DMFS - a Data Migration File System for Netbsd
    DMFS - A Data Migration File System for NetBSD William Studenmund Veridian MRJ Technology Solutions NASAAmes Research Center" Abstract It was designed to support the mass storage systems de- ployed here at NAS under the NAStore 2 system. That system supported a total of twenty StorageTek NearLine ! have recently developed DMFS, a Data Migration File tape silos at two locations, each with up to four tape System, for NetBSD[I]. This file system provides ker- drives each. Each silo contained upwards of 5000 tapes, nel support for the data migration system being devel- and had robotic pass-throughs to adjoining silos. oped by my research group at NASA/Ames. The file system utilizes an underlying file store to provide the file The volman system is designed using a client-server backing, and coordinates user and system access to the model, and consists of three main components: the vol- files. It stores its internal metadata in a flat file, which man master, possibly multiple volman servers, and vol- resides on a separate file system. This paper will first man clients. The volman servers connect to each tape describe our data migration system to provide a context silo, mount and unmount tapes at the direction of the for DMFS, then it will describe DMFS. It also will de- volman master, and provide tape services to clients. The scribe the changes to NetBSD needed to make DMFS volman master maintains a database of known tapes and work. Then it will give an overview of the file archival locations, and directs the tape servers to move and mount and restoration procedures, and describe how some typi- tapes to service client requests.
    [Show full text]
  • Unionfs: User- and Community-Oriented Development of a Unification File System
    Unionfs: User- and Community-Oriented Development of a Unification File System David Quigley, Josef Sipek, Charles P. Wright, and Erez Zadok Stony Brook University {dquigley,jsipek,cwright,ezk}@cs.sunysb.edu Abstract If a file exists in multiple branches, the user sees only the copy in the higher-priority branch. Unionfs allows some branches to be read-only, Unionfs is a stackable file system that virtually but as long as the highest-priority branch is merges a set of directories (called branches) read-write, Unionfs uses copy-on-write seman- into a single logical view. Each branch is as- tics to provide an illusion that all branches are signed a priority and may be either read-only writable. This feature allows Live-CD develop- or read-write. When the highest priority branch ers to give their users a writable system based is writable, Unionfs provides copy-on-write se- on read-only media. mantics for read-only branches. These copy- on-write semantics have lead to widespread There are many uses for namespace unifica- use of Unionfs by LiveCD projects including tion. The two most common uses are Live- Knoppix and SLAX. In this paper we describe CDs and diskless/NFS-root clients. On Live- our experiences distributing and maintaining CDs, by definition, the data is stored on a read- an out-of-kernel module since November 2004. only medium. However, it is very convenient As of March 2006 Unionfs has been down- for users to be able to modify the data. Uni- loaded by over 6,700 unique users and is used fying the read-only CD with a writable RAM by over two dozen other projects.
    [Show full text]
  • We Get Letters Sept/Oct 2018
    SEE TEXT ONLY WeGetletters by Michael W Lucas letters@ freebsdjournal.org tmpfs, or be careful to monitor tmpfs space use. Hey, FJ Letters Dude, Not that you’ll configure your monitoring system Which filesystem should I use? to watch tmpfs, because it’s temporary. And no matter what, one day you’ll forget —FreeBSD Newbie that you used memory space as a filesystem. You’ll stash something vital in that temporary space, then reboot. And get really annoyed Dear FreeBSD Newbie, when that vital data vanishes into the ether. First off, welcome to FreeBSD. The wider com- Some other filesystems aren’t actively terrible. munity is glad to help you. The device filesystem devfs(5) provides device Second, please let me know who told you to nodes. Filesystems that can’t store user data are start off by writing me. I need to properly… the best filesystems. But then some clever sysad- “thank” them. min decides to hack on /etc/devfs.rules to Filesystems? Sure, let’s talk filesystems. change the standard device nodes for their spe- Discussing which filesystem is the worst is like cial application, or /etc/devd.conf to create or debating the merits of two-handed swords as reconfigure device nodes, and the whole system compared to lumberjack-grade chainsaws and goes down the tubes. industrial tulip presses. While every one of them Speaking of clever sysadmins, now and then has perfectly legitimate uses, in the hands of the people decide that they want to optimize disk novice they’re far more likely to maim everyone space or cut down how many copies of a file involved.
    [Show full text]
  • System Profile
    Steve Sample’s Power Mac G5 6/16/08 9:13 AM Hardware: Hardware Overview: Model Name: Power Mac G5 Model Identifier: PowerMac11,2 Processor Name: PowerPC G5 (1.1) Processor Speed: 2.3 GHz Number Of CPUs: 2 L2 Cache (per CPU): 1 MB Memory: 12 GB Bus Speed: 1.15 GHz Boot ROM Version: 5.2.7f1 Serial Number: G86032WBUUZ Network: Built-in Ethernet 1: Type: Ethernet Hardware: Ethernet BSD Device Name: en0 IPv4 Addresses: 192.168.1.3 IPv4: Addresses: 192.168.1.3 Configuration Method: DHCP Interface Name: en0 NetworkSignature: IPv4.Router=192.168.1.1;IPv4.RouterHardwareAddress=00:0f:b5:5b:8d:a4 Router: 192.168.1.1 Subnet Masks: 255.255.255.0 IPv6: Configuration Method: Automatic DNS: Server Addresses: 192.168.1.1 DHCP Server Responses: Domain Name Servers: 192.168.1.1 Lease Duration (seconds): 0 DHCP Message Type: 0x05 Routers: 192.168.1.1 Server Identifier: 192.168.1.1 Subnet Mask: 255.255.255.0 Proxies: Proxy Configuration Method: Manual Exclude Simple Hostnames: 0 FTP Passive Mode: Yes Auto Discovery Enabled: No Ethernet: MAC Address: 00:14:51:67:fa:04 Media Options: Full Duplex, flow-control Media Subtype: 100baseTX Built-in Ethernet 2: Type: Ethernet Hardware: Ethernet BSD Device Name: en1 IPv4 Addresses: 169.254.39.164 IPv4: Addresses: 169.254.39.164 Configuration Method: DHCP Interface Name: en1 Subnet Masks: 255.255.0.0 IPv6: Configuration Method: Automatic AppleTalk: Configuration Method: Node Default Zone: * Interface Name: en1 Network ID: 65460 Node ID: 139 Proxies: Proxy Configuration Method: Manual Exclude Simple Hostnames: 0 FTP Passive Mode:
    [Show full text]
  • Mis Chuletas De Mac OS X Impreso El 9 De Junio De 2009, a Las 11:03 Horas
    Mis chuletas de Mac OS X Impreso el 9 de junio de 2009, a las 11:03 horas Índice 1 Versiones de Mac OS X 2 2 Hardware 2 2.1 MacBook casa 2 2.2 iMac trabajo 2 3 Uso 2 3.1 Atajos de teclado 2 3.2 Terminal (y comandos) 3 3.3 Aplicación por defecto 3 3.4 Arranque 4 3.4.1 Modo usuario único 4 3.4.2 Modo seguro 4 3.4.3 Arranque múltiple 4 3.4.4 Arranque de unidad de CD/DVD 4 3.5 Capturas de pantalla 4 3.5.1 Captura de pantalla de ordenador remoto 4 3.6 Redes mixtas: Windows 4 3.6.1 Compartiendo FAT32 y NTFS con Samba 5 3.7 Cambio de nombre de carpeta en red 5 3.8 Buscando símbolos 6 3.9 Dos instancias simultáneas de una aplicación 6 3.10 Finder 6 3.10.1 Atajo a carpeta superior 6 3.10.2 Ordena alfabéticamente 6 3.10.3 Ruta en Finder 6 3.10.4 Preferencias vista columnas 7 3.11 Vista previa 7 3.11.1 Añadir extensiones 7 3.11.2 Ver pdf inmediatamente o descargarlo 7 3.11.3 Zoom en modo vista previa 7 3.11.4 Crear pdf multipáginas desde imágenes en Vista Previa 7 3.12 Calendarios 8 3.12.1 Mezclar múltiples calendarios en uno 8 3.12.2 Sincronizar iCal y Google Calendar 8 3.13 Opciones avanzadas en cuentas 8 3.14 Correo 8 3.14.1 Thunderbird es indexado por Spotlight 8 3.14.2 Reparar índice en Mail 8 3.14.3 Correos con CCO (con copia oculta) 8 3.14.4 Copia del perfil de Mail 8 3.14.5 MS Entourage 9 3.15 Conexión a escritorio remoto 9 3.16 Añadir radios a iTunes 9 3.17 CD / DVD 9 3.17.1 Quemar un DVD-Video 9 3.17.2 Pasdar de .iso a .dmg y al revés 9 3.17.3 Crear una imagen ISO 9 3.18 Borrado seguro espacio libre 10 3.19 Borrar todas las papeleras de
    [Show full text]
  • Vcenter Server Upgrade
    vCenter Server Upgrade Update 2 VMware vSphere 7.0 vCenter Server 7.0 vCenter Server Upgrade You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com © Copyright 2018-2021 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 2 Contents 1 About vCenter Server Upgrade 7 2 vCenter Server Upgrade Options 8 Overview of the vSphere Upgrade Process 8 Overview of the vCenter Server Upgrade Process 10 vCenter Server Upgrade Compatibility 12 vCenter Server 7.0 Component Behavior Changes That Affect Upgrade 13 Removal of Platform Services Controller 14 Upgrade or Migration for vCenter Server Instances with an External Platform Services Controller 14 Upgrading or Migrating to vSphere License Service 15 Upgrading the Trust Authority vCenter Server 16 Differences Between vSphere Upgrades, Patches, Updates, and Migrations 16 Support for Upgrading a vCenter Server with Multi-Homing 17 Support for Federal Information Processing Standard 140-2 17 Support for Transport Security Layer 1.2 17 Moving from a Deprecated to a Supported vCenter Server Deployment Topology Before Upgrade or Migration 18 Example Upgrade Paths from vCenter Server 6.5 and 6.7 to vCenter Server 7.0 19 Example Migration Paths from vCenter Server for Windows to vCenter Server 7.0 20 3 Upgrading the vCenter Server Appliance 22 About the Upgrade Process of the vCenter Server Appliance 24 System Requirements for the New vCenter Server Appliance
    [Show full text]
  • Opencore Reference Manual (0.5.9::::::::: 0.6.0) [2020.07.05]
    OpenCore Reference Manual (0.5.90.6.0::::::::: ) [2020.07.05] Copyright ©2018-2020 vit9696 1 Introduction This document provides information on OpenCore user configuration file format used to setup the correct functioning of macOS operating system. It is to be read as the official clarification of expected OpenCore behaviour. All deviations, if found in published OpenCore releases, shall be considered documentation or implementation bugs, and are requested to be reported through Acidanthera Bugtracker. ::::::Errata :::::sheet::is::::::::available:::in OpenCorePkg repository.: This document is structured as a specification, and is not meant to provide a step by step algorithm for configuring end-user board support package (BSP). The intended audience of the document are programmers and engineers with basic understanding of macOS internals and UEFI functioning. For these reasons this document is available exclusively in English, and all other sources or translations of this document are unofficial and may contain errors. Third-party articles, utilities, books, and alike may be more useful for a wider audience as they could provide guide-like material. However, they are prone to their authors’ preferences, tastes, this document misinterpretation, and essential obsolescence. In case you use these sources, for example, Dortania’s OpenCore Desktop Guide and related material, please ensure to follow this document for every made decision and judge its consequences. Be warned that regardless of the sources used you are required to fully understand every dedicated OpenCore configuration option and concept prior to reporting any issues in Acidanthera Bugtracker. 1.1 Generic Terms • plist — Subset of ASCII Property List format written in XML, also know as XML plist format version 1.
    [Show full text]
  • Interacting with *OS Hardware from User Space
    Interacting with *OS Hardware from User Space ??? Jiska Classen Secure Mobile Networking Lab - SEEMOO Technical University of Darmstadt, Germany As a… hardware hacker I want to… buy iPhones So that… I can break the most recent chips Wait, what? ● Official development kits often lag behind. ○ Bluetooth/Wi-Fi kits by Cypress (aka Broadcom) are stuck on a firmware state around 2016. ○ Ultra Wideband kits by Decawave added features like direction measurement much later than it was available in iPhones. ● Official development kits miss proprietary features. ○ Intel baseband chips use a proprietary, undocumented interface on Apple devices. Bluetooth Chip Build Dates iPhone 11: Oct 25 2018 iPhone 12: Oct 29 2019 Samsung Galaxy S21: April 13 2018 (S21+ Ultra probably got an update) Hardware in an iPhone ● Bluetooth+Wi-Fi combo chip by Broadcom ● Baseband chip by Intel or Qualcomm ● U1 chip (in-house, since iPhone 11) ● NFC chip ● … and that’s just the wireless chips! If I deal with iPhones, jailbreaks, etc. I can access quite a lot of hardware Goals 1. Find chip interfaces. 2. Find protocol handlers. 3. Decode proprietary protocols. 4. Inject custom payloads. ??? Why from user space?! ● The daemon that interacts with the chip already holds a correct state. ○ Chip initialization/activation on startup and when leaving flight mode. ○ Complex protocol internals are implemented here. ● The daemon’s protocol implementation will typically: ○ parse crash logs, ○ acknowledge packets, CommCenter ○ forward information to other daemons, ○ … User Space Kernel Space ● FЯIDA only supports user space. Hardware But you said *OS??! ● XNU kernel is very similar on MacOS, iOS, and the iOS derivatives like audioOS, watchOS, tvOS, … ● User space is also mostly similar.
    [Show full text]
  • Mac OS X Desktop.Pdf
    Apple Training Series Mac OS X Support Essentials v10.6 Kevin M. White Apple Training Series: Mac OS X Support Essentials v10.6 Kevin M. White Copyright © 2010 by Apple Inc. Published by Peachpit Press. For information on Peachpit Press books, contact: Peachpit Press 1249 Eighth Street Berkeley, CA 94710 510/524-2178 510/524-2221 (fax) www.peachpit.com To report errors, please send a note to [email protected]. Peachpit Press is a division of Pearson Education. Apple Training Series Editor: Rebecca Freed Production Editors: Danielle Foster, Becky Winter Copyeditor: Peggy Nauts Tech Editor: Gordon Davisson Apple Editor: Shane Ross Proofreader: Suzie Nasol Compositor: Danielle Foster Indexer: Valerie Perry Cover design: Mimi Heft Cover illustrator: Kent Oberheu Notice of Rights All rights reserved. No part of this book may be reproduced or transmitted in any form by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. For infor- mation on getting permission for reprints and excerpts, contact [email protected]. Notice of Liability The information in this book is distributed on an “As Is” basis without warranty. While every precaution has been taken in the preparation of the book, neither the author nor Peachpit shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the instructions contained in this book or by the computer software and hardware products described in it. Trademarks Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks.
    [Show full text]
  • INSTALLING the PRINT DRIVER Ignore the Detailed Instructions: PRINTING
    INSTALLING THE PRINT DRIVER Ignore the detailed instructions: PRINTING To print wirelessly from your Mac at SMPL, In any program, print as you would you must install a driver. This will only work normally. When the Print dialog box with Mac OS 10.4 or later (Tiger or appears, the printer you chose will be one Leopard). of your choices: Go to www.smpl.org/depts/im/WiFiPrinting.html Choose the first or second floor location and click MacOS . Choose Open with DiskImageMounter in the dialog box: SMPL has already customized this software for our network. Click Continue. When the installer finishes, you are ready to print. If you’d like to verify your installation, open System Preferences: Select it, and click Print. This will mount the disk image Choose Print & Fax and Choose a name and password (optional) Popup 8.0: look for Mac_WiFi_Printer or for your document and click Print again to 2nd_Floor_Mac_Wifi_Printer on your list of send it off: printers: The installer is inside: Double click to launch it, then click through the menus. Note: Passwords are case sensitive. TO GET YOUR PRINT JOB Wi-Fi Printing There are two locations: 1st Floor Copy Santa Monica Public Center and 2nd Floor to the left of the UNINSTALLING THE PRINT DRIVER Reference Desk. Insert your library card Main Library or print card into the box located next If you plan to print at SMPL in the future, to the printer. you can leave the driver installed. It is very small and will not affect your computer’s other functions.
    [Show full text]