Using a Mac with at least OS X 10.6.8 installed, access the Mac App Store and download the Lion (10.7) or Mountain Lion (10.8) app installer. Insert the USB drive into the Mac and launch Disk. How do I write an ISO image under Mac OS? The Toast program for Mac OS is reported to work fine with.iso files. You can be extra-safe by giving it the creator code CDr3 (or possibly CDr4) and type code iImg using e.g. Double-clicking on the file will then open up Toast directly, without having to drag-and-drop or go via the File. Buy TP-Link AC600 USB WiFi Adapter for PC (Archer T2U Plus)- Wireless Network Adapter for Desktop with 2.4GHz, 5GHz High Gain Dual Band 5dBi Antenna, Supports Win10/8.1/8/7/XP, Mac OS 10.9-10.14: USB Network Adapters - Amazon.com FREE DELIVERY possible on eligible purchases.

A live CD (also live DVD, live disc, or live operating system) is a complete bootable computer installation including operating system which runs directly from a CD-ROM or similar storage device into a computer's memory, rather than loading from a hard disk drive. A Live CD allows users to run an operating system for any purpose without installing it or making any changes to the computer's configuration. Live CDs can run on a computer without secondary storage, such as a hard disk drive, or with a corrupted hard disk drive or file system, allowing data recovery.

As CD and DVD drives have been steadily phased-out, live CDs have become less popular, being replaced by live USBs, which are equivalent systems written onto USB flash drives, which have the added benefit of having writeable storage. The functionality of a live CD is also available with a bootable live USBflash drive, or an external hard disk drive connected by USB. Many live CDs offer the option of persistence by writing files to a hard drive or USB flash drive.

Many Linux distributions make ISO images available for burning to CD or DVD. While open source Operating Systems can be used for free, some commercial software, such as Windows To Go requires a license to use. Many Live CDs are used for data recovery, computer forensics, disk imaging, system recovery and malware removal. The Tails operating system is aimed at preserving privacy and anonymity of its users, allowing them to work with sensitive documents without leaving a record on a computer's hard drive.^[1][2]

History[edit]

All computers except the earliest digital computers are built with some form of minimal built-in loader, which loads a program or succession of programs from a storage medium, which then operate the computer. Initially a read-only medium such as punched tape or punched cards was used for initial program load. With the introduction of inexpensive read-write storage, read-write floppy disks and hard disks were used as boot media.

After the introduction of the audiocompact disc, it was adapted for use as a medium for storing and distributing large amounts of computer data. This data may also include application and operating-system software, sometimes packaged and archived in compressed formats. Later, it was seen to be convenient and useful to boot the computer directly from compact disc, often with a minimal working system to install a full system onto a hard drive. While there are read-write optical discs, either mass-produced read-only discs or write-once discs were used for this purpose.

The first Compact Disc drives on personal computers were generally much too slow to run complex operating systems; computers were not designed to boot from an optical disc. When operating systems came to be distributed on compact discs, either a boot floppy or the CD itself would boot specifically, and only, to install onto a hard drive. The world's first and oldest non-Linux live CD was the FM Towns OS first released in 1989, before the release of Macintosh System 7 in 1991 and Yggdrasil Linux in 1992.^{[citation needed]}

Linux[edit]

Although early developers and users of distributions built on top of the Linux kernel could take advantage of cheap optical disks and rapidly declining prices of CD drives for personal computers, the Linux distribution CDs or 'distros' were generally treated as a collection of installation packages that would first need to be permanently installed to hard disks on the target machine.

However, in the case of these distributions built on top of the Linux kernel, the free operating system was meeting resistance in the consumer market because of the perceived difficulty, effort, and risk involved in installing an additional partition on the hard disk, in parallel with an existing operating system installation.

The term 'live CD' was coined because, after typical PC RAM was large enough and 52x speed CD drives and CD burners were widespread among PC owners, it finally became convenient and practical to boot the kernel and run X11, a window manager and GUI applications directly from a CD without disturbing the OS on the hard disk.

This was a new and different situation for Linux than other operating systems, because the updates/upgrades were being released so quickly, different distributions and versions were being offered online, and especially because users were burning their own CDs.

The first Linux-based 'Live CD' was Yggdrasil Linux first released in beta form 1992~1993 (ceased production in 1995), though in practice its functionality was hampered due to the low throughput of contemporary CD-ROM drives. DemoLinux, released in 1998, was the first Linux distribution specially designed as a live CD. The Linuxcarebootable business card, first released in 1999, was the first Live CD to focus on system administration, and the first to be distributed in the bootable business card form factor. As of 2015, Finnix (first released in 2000) is the oldest Live CD still in production. Knoppix, a Debian-derived Linux distribution, was released in 2003, and found popularity as both a rescue disk system and as a primary distribution in its own right.

Since 2003, the popularity of live CDs has increased substantially, partly due to Linux Live scripts and remastersys, which made it very easy to build customized live systems. Most of the popular Linux distributions now include a live CD variant, which in some cases is also the preferred installation medium.

Uses[edit]

Live CDs are made for many different uses. Some are designed to demonstrate or 'test drive' a particular operating system (usually Linux or another free or open source operating system). Software can be tested, or run for a particular single use, without interfering with system setup. Data on a system which is not functioning normally due to operating system and software issues can be made available; for example, data can be recovered from a machine with an active virus infection without the virus process being active and causing more damage, and the virus can be removed with its defences against removal bypassed.

Although some live CDs can load into memory to free the optical drive for other uses, loading the data from a CD-ROM is still slower than a typical hard drive boot, so this is rarely the default with large live CD images, but for smaller live CD images loading the filesystem directly into RAM can provide a significant performance boost, as RAM is much faster than a hard drive, and uses less power.^[3] Experienced users of the operating system may also use a live CD to determine whether and to what extent a particular operating system or version is compatible with a particular hardware configuration and certain peripherals, or as a way to know beforehand which computer or peripheral will work before buying.^[3] A live CD can be used to troubleshoot hardware, especially when a hard drive fails, and more generally as a recovery disc in case of problems. Some live CDs can save user-created files in a Windows partition, a USB drive, a network drive, or other accessible media. Live backup CDs can create an image of drives, and back up files, without problems due to open files and inconsistent sets.

A few additional uses include:

• installing a Linux distribution to a hard drive
• Virus scanning and Malware removal^[4]
• system repair and restoration
• testing new versions of software
• listing & testing hardware^[5]
• Internet kiosks and public computers, which can be brought back to their original state by a reboot
• high security/non-invasive environment for a guest
• cracking, stealing, and changing passwords
• network security testing
• being the primary or backup operating system for any computer
• quick and simple clustering of computers^[6]
• playing video games or running applications that require a different operating system
• providing a secure server platform where crucial files cannot be permanently altered
• providing a secure, reliable platform for the performance of high-vulnerability tasks such as internet banking;
• Bypassing parental controls and other restrictions

Several live CDs are dedicated to specific type of applications according to the requirements of thematic user communities. These CDs are tailored to the needs of the applications in subject including general knowledge, tutorial, specifications and trial data too.

Some of these topics covers sub topics, e.g. IT administration breaks down to firewall, rescue, security, etc. type of live CDs. In some cases a particular Live DVD covers more than one topic.

Software appliances[edit]

Packaging a software appliance as an installable live CD, or live ISO, can often be beneficial as a single image can run on both real hardware and on most types of virtual machines.

This allows developers to avoid the complexities involved in supporting multiple incompatible virtual machine images formats andfocus on the lowest common denominator instead.

Typically after booting the machine from the live CD, the appliance either runs in non-persistent demo mode or installs itself, at the user's request, to an available storage device.

Mounting without burning[edit]

The files on a live CD ISO image can be accessed in Microsoft Windows with a disk image emulator such as Daemon Tools, or in Unix variants by mounting a loop device. Later versions of Windows (i.e. Windows 8 and later), and software available for earlier versions, allow an ISO to be mounted as a volume.

After mounting the live CD's filesystem, software on the live CD can be run directly, without booting it, by chrooting into the mounted filesystem.

A live CD ISO image can also be mounted by Virtual Machine software such as VirtualBox and VMware Workstation or can be converted to a Live USB using SYSLINUX. Special tools can automate this process.^[7]

Features[edit]

During live CD initialization, a user typically may resort to using one or more boot codes to change the booting behavior. These vary from distribution to distribution but can most often be accessed upon first boot screen by one of the function keys.

Some live CDs come with an installation utility launchable from a desktop icon that can optionally install the system on a hard drive or USB flash drive. Most live CDs can access the information on internal and/or external hard drives, diskettes and USB flash drives.

Live CDs are usually distributed on read-only media, requiring either copying to rewriteable media (i.e. a hard drive or CD writer) or complete remastering to install additional software; however, there are exceptions. If Puppy Linux is recorded to an open multisession medium, changes made during use (such as files created, programs installed, and preferences customised) are written in a new session to the boot medium^[8] persisting through subsequent boots.

The term 'Live CD' came to be used for any CD containing operating system and software which could be run without installation on the host computer. Operating systems which can be used live include AmigaOS 4, Amithlon, AROS, FreeBSD, FreeDOS, classic Mac OS, macOS, Microsoft Windows installation and repair discs, OS/2, ReactOS, NetBSD, OpenBSD, MINIX 3, Plan 9 from Bell Labs, MorphOS, OpenSolaris, BeleniX and others based on Solaris. There are maintenance versions of Microsoft Windows bootable from CD such as BartPE, Windows PE, and Microsoft Diagnostics and Recovery Toolset (DaRT), previously known as Emergency Repair Disk Commander (ERD Commander).

The first personal computer operating system on a CD to support 'live' operations might have been the AmigaOS, which could be booted from CD on an Amiga CDTV in 1990.^{[citation needed]}. Earlier examples of live OS are of course the operating systems used from floppy, and most widely spread is DOS.

Unlike previous operating systems on optical media, though, Linux and OS/2 'live CDs' were specifically designed to run without installation onto other media like a hard disk drive. The live CD concept was meant to promote Linux and showcase the abilities of the free, open source operating system on conventional personal computers with Microsoft Windows already installed.^{[citation needed]}

On a PC, a bootable Compact Disc generally conforms to the El Torito specification, introduced in 1994. Many Linux based live CDs use a compressed filesystem image, often with the cloop compressed loopback driver, or squashfs compressed filesystem, generally doubling effective storage capacity, although slowing application start up^{[citation needed]}.

The resulting environment can be quite rich: typical Knoppix systems include around 1,200 separate software packages. Live CDs have a reputation for supporting advanced auto-configuration and plug-and-play functionality. This came out of necessity to avoid requiring the user to configure the system each time it boots and to make it easily usable by those who are new to the operating system.

Creation[edit]

A read-only file system, such as on a CD-ROM has the drawback of being unable to save any current working data. For this reason, a read-only file system is often merged with a temporary writable file system in the form of a RAM disk. Often the default Linux directories '/home' (containing users' personal files and configuration files) and '/var' (containing variable data) are kept in ramdisk, because the system updates them frequently. Puppy Linux and some other live CDs allow a configuration and added files to be written and used in later sessions.

In modern live CDs, a read-only file system is merged with a RAM drive using transparent techniques such as UnionFS, AuFS or EWF. Boot loaders like syslinux can boot ISO files from USB memory devices.

Live CDs have to be able to detect and use a wide variety of hardware (including network cards, graphic cards etc.) in realtime, often using facilities such as udev, hotplug, hal, udisk etc.. which are a common part of all distributions based on Linux kernel 2.6.

See also[edit]

References[edit]

1. ^Timm, Trevor (2 April 2014). 'Help Support the Little-Known Privacy Tool That Has Been Critical to Journalists Reporting on the NSA'. Freedom of the Press Foundation. Retrieved 18 April 2014.
2. ^Finley, Klint (14 April 2014). 'Out in the Open: Inside the Operating System Edward Snowden Used to Evade the NSA'. WIRED. Retrieved 18 April 2014.
3. ^ ^abBrickner, David (2005). Test Driving Linux: From Windows to Linux in 60 Seconds. O'Reilly. ISBN0-596-00754-X.
4. ^'Scan a Windows PC for Viruses from a Ubuntu Live CD'. howtogeek.com. Retrieved 19 March 2018.
5. ^'Home - HDT Project'. HDT Project. Archived from the original on 25 July 2018. Retrieved 19 March 2018.
6. ^'FlashMob Computing – FlashMob Computing'. flashmobcomputing.org. Retrieved 19 March 2018.
7. ^'USB Installation Media - UNetbootin'. community.ubuntu.com. Ubuntu Community. Retrieved 11 February 2014.
8. ^'How to Create a Multi-session LiveDVD'. Puppy Linux. 26 April 2011. Retrieved 1 August 2018.

External links[edit]

• Pondering Live CDs - A BSD perspective on the concept of Live CDs

• Download
• Misc

A CD image is the exact representation of the data on a CD in anormal computer file, that can e.g. be transmitted over theInternet. CD burning programs can use the image files to make realCDs.

In Debian, we use the term CD image as a common way todescribe a range of things, many of which don't even fit on CD! Thename is old, but it has stuck. We regularly build multiple differenttypes of image:

• Debian installer images in multiple sizes. These range from small CD-sized netinst images for quick download up to large complete sets of images designed for DVD, Blu-Ray (BD) or Dual-Layer Blu-Ray (DLBD) media.
• Debian live images - live systems designed to be run directly from CD/DVD/USB without needing installation. See below for more details.

In many cases, these installer and live images can often be writtendirectly to USB flash drives with no CD involved;see below. Don't be put off by the name CDimage!

For a correctly written image, the .iso file must notappear on the media when you access it! Instead, you should see anumber of files and directories - in the case of a Debian installerimage, this includes adists directory and a README.html file.

The .iso format we use for our images is roughlycomparable to a .zip file: It contains other files anddirectories, and only these will appear on the final CD/DVD/USBmedium. Some archive programs allow you to unpack.iso files. Do not use this feature to create a CD from theunpacked files! The resulting medium will fail to boot because the.iso format includes special information related to bootingfrom the CD/DVD/USB, which is lost when you unpack the file. See below on howto correctly write a CD/DVD image under Linux,Windows or MacOS, or how to write an image to a USB flashdrive.

Many devices require firmware to operate. Historically, firmwarewould be built into the device's ROM or Flash memory, but more andmore often, a firmware image has to be loaded into the device by adevice driver during device initialiaation.

Some firmware images are free and open-source, and some of them arenon-free, which means that you would need to add the non-free andcontrib components to your APT sources.

In some cases the installer detects the need for non-free firmwareand prompts the user to make the firmware available to the installerto complete the installation. This can happen, for example, withwireless network cards which often require non-free firmware tofunction (see ipw2200 for an example).

There are two ways to proceed here:

• An easy method is to use an installer image that includes all non-free firmware packages directly. See https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/ for those.
• You can also download a firmware archive for your platform and unpack it into a directory named firmware in the root of a removable storage device (USB/CD drive). You can find firmware downloads for your Debian version at https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/. When the installer starts, it will automatically find the firmware files in the directory on the removable storage and, if needed, install the required firmware. This is documented in the Debian installer manual.

If you cannot find an answer to your question here, you can ask forhelp on one of the Debian mailing lists.In all cases, you should searchthe mailing list archives before sending mail to the lists.You can subscribeto and unsubscribefrom the lists. However, you do not need to be subscribed in orderto send mail to the lists - if you are not subscribed, ask forreplies to be CC'd to you.

Mailing lists relevant to problems with CD installation:

• debian-cd: Discussion about the CD image creation process, available CD mirrors, problems when booting from CD, announcements of new official images.
• debian-boot: A bit of a misnomer, this list actually covers the installation process; any problems encountered after successfully booting from CD may be more appropriate here than in debian-cd.
• debian-live: A list for the Debian Live project, focused on development of the software that is used to build Debian Live images, but also appropriate for discussion particular to using those images.
• debian-user: General support list for users of Debian. Focus is more on problems encountered after a successful installation, when using the system. There are also several lists for non-English speakers, in Català, Chinese, Dansk, Esperanto, Français, Deutsch, Magyar, Indonesian, Italiano, 日本語 (Nihongo), Polski, Português, Русский (Russkij), Español, Svenska, Türkçe, and Ukrainian.

Live Usb Mac Os Recovery Tool

Today, there are nearly 300 Debianmirrors (which contain the complete Debian distribution as .deb files),but far fewer machines serving Debian CD images.As a result, the CD image servers are constantly overloaded.

Additionally, nobody is very enthusiastic about setting up moreCD servers because of the tremendous amounts of wasted bandwidth(some people keep restarting failed downloads instead ofresuming from the point where the connection was closed)and because a regular mirror is more attractive (it allowscontinuous upgrades of Debian, or using the testing/unstabledistribution instead of the stable one).

jigdo tries to makethe most out of this situation, by downloading the data for the CDimages from one of the 300 mirrors. However, these mirrors onlyhold individual .deb files, not the CD image, so some additionalmanipulation of the data is necessary to produce one big CD imagefile from the many small .deb files.

Do not be afraid to try out jigdo!The complex process of generating the CD image is completelyhidden from you - instead, you benefit from the fact that one ofthe 300 Debian mirrors is bound to be nearer and faster than anyof the CD servers.

No. First, of course you only need to download CD or DVDor BD images - the three types of images contain the samepackages.

Also, you only need the CD/DVD/BD images for your computer'sarchitecture. The architecture is the type of hardware your computeruses. By far the most popular one is the 64-bit Intel/AMD PCarchitecture, so most people will only want to get the imagesfor amd64. If your PC has an older 32-bit AMD or Intelprocessor, you will most likely need thei386 images instead.

Furthermore, in most cases it is not necessary to download all ofthe images for your architecture. The packages are sorted bypopularity: The first CD/DVD/BD contains the installation system andthe most popular packages. The second one contains slightly lesspopular ones, the third one even less popular ones, etc. You willprobably only need the first couple of DVDs (or the first BD, etc.)unless you have very special requirements. (And in case you happen toneed a package later on which is not on one of the CDs/DVDs/BDs youdownloaded, you can always install that package directly from theInternet.)

Please also read the next paragraphs to determine whether youwant/need to download network install CDs, update CDs or sourceCDs.

To quote the network install page: Anetwork install or netinst CD is a single CD which enables you toinstall the entire operating system. This single CD contains just theminimal amount of software to start the installation and fetch theremaining packages over the Internet.

If you only want to install Debian on a single machine which has afast Internet connection, the network install may be the fastest andeasiest option for you: You only download the packages that youselected for installation on your machine, which saves both time andbandwidth.

Update CDs/DVDs are CDs/DVDs which contain all the packages thatchanged between a major release version (e.g. 7.0,8.0, etc.) and a later point release of that stabledistribution. For example, if you already have the full set ofdebian-8.0.0 CDs/DVDs, you can add thedebian-update-8.2.0 disc set to turn this debian-8.0.0set into a debian-8.2.0 set.

This type of CD/DVD is intended for vendors having large amounts ofpressed versions of CDs/DVDs (which makes them cheaper thanindividually burned CDs/DVDs). If you order CDs/DVDs from such avendor, it is possible that you'll receive CDs/DVDs for a slightlyolder point release, plus some update CDs/DVDs for the latestrevision. This is a perfectly acceptable way of distributing Debian onCD/DVD.

Of course, this type of CD/DVD can also be useful to you as an end user;instead of creating the full set of CDs/DVDs for each new revision of arelease, you only need to download and burn update CDs/DVDs foryour architecture.

Note that update CDs/DVDs are not meant to boot, they just contain thepackages needed to upgrade an existing installation. If you don't havethat existing installation, then you'll need to use the normalinstallation CDs/DVDs. After the new system is booted, the updated CD/DVD can be added withapt-cdrom add.

Now, what if for some reason you do not want to download the updateCD/DVD even though you already have the full set of CDs/DVDs/BDs forthe previous revision? In this case, you should consider using jigdo's update feature: jigdo can readthe contents of the old CDs/DVDs/BDs, download only those files thathave changed for the new CDs/DVDs, and create the full set of newCDs/DVDs/BDs. Still, it will have done this by downloading only aboutthe same amount of data as for an update CD/DVD.

There are two types of images, the binary CDs that containprecompiled, ready-to-run programs, and the source CDs thatcontain the source code for the programs. The vast majority ofpeople do not need the source CDs; you should not download themunless you really have a good reason for it.

Debian has a quite strict view with regard to the licenses ofsoftware: Only software that is Free in the sense of theDebian Free SoftwareGuidelines is allowed into the actual distribution. All the other,non-free software (for example, software for which source code is notavailable) is not supported officially.

The official CDs may freely be used, copied and sold by anyone anywherein the world. Packages of the non-free category have restrictions thatconflict with this, so these packages are not placed on the officialCDs.

Sometimes, someone is kind enough to create unofficial non-freeCDs. If you cannot find any links on this website, you can tryasking on the debian-cd mailing list.

Official images are built by a member of the Debian CD team andhave undergone some testing to ensure they work. Once they have beenreleased, the images never change - if they turn out to be broken, anew set with a different version number is released.

Unofficial images can be built by anyone - CD team members, otherDebian developers or even advanced Debian users. Typically, they aremore up-to-date, but have received less testing. Some have newfeatures (e.g. installation support for new hardware), or containadditional software packages which are not part of the Debian archive.

Yes. A so-called live image (live CD), or moreprecisely, a live system, is a complete system prepared for aDVD, USB key or other medium. You do not need to install anything onthe hard drive. Instead you boot from the medium (DVD or USB key) andare able to start working on the machine right away. All programs rundirectly from the medium.

The Debian Live Project produceslive image files for a variety of system types andmedia.

Only the first CD/DVD/BD in a set is bootable.

If your Debian disc fails to boot, first ensure that you havecorrectly written it to the medium - please see theexplanation above. Additionally, please check whether your BIOS isset up to boot from your optical or USB drive.

Depending on the state of support for a certain architecture,CD/DVD images are available from different places:

• If the architecture you are looking for is officially supported by the current stable release, see the Debian on CD page for the available download options.
• If a Debian port for an architecture exists, but has not yet been released officially, CD images may or may not be available. Again, see the Debian on CD page - in contrast to stable images, only one download option may be supported, so have a look at both the jigdo and HTTP sections.
• For the Debian port to the GNU/Hurd, see the page about unofficial Hurd CDs.
• Otherwise, check the Debian port pages for the architecture you are interested in.

There are no unstable full CD/DVD/BD images. Due to the factthat the packages in unstable change so quickly, it is moreappropriate for people to download and install unstable using anormal Debian HTTP mirror.

If you are aware of the risks ofrunning unstable, but still want to install it, you have a fewchoices:

Live Usb Mac Os

• Install testing using a netinst image, then upgrade to unstable by changing the entries in your /etc/apt/sources.list. To avoid unnecessary downloads and package upgrades, it is advisable to install a minimal testing system first and only to install most of the software (e.g. desktop environment) after the switch to unstable.
• Use the stable installer to install a minimal stable system and then change your /etc/apt/sources.list file to use testing and do an apt-get update and apt-get dist-upgrade. Finally, install the packages you desire. This method is the most likely to work of those presented here.
• Be a tester of the testing installer and install testing using a netinst image, then upgrade to unstable by changing the entries in your /etc/apt/sources.list. To avoid unnecessary downloads and package upgrades, it is advisable to install a minimal testing system first and only to install most of the software (e.g. desktop environment) after the switch to unstable. Then apt-get update and apt-get -u dist-upgrade - then you have a sid release.
• Use a netboot mini.iso image. You will find it on any of the Debian mirrors under debian/dists/unstable/main/installer-*/current/images/netboot/mini.iso. During the installation choose Advanced options ->Expert install. In the step Choose a mirror of the Debian archive choose version sid - unstable.

To find out which image contains a certain file, usethe cdimage searchtool. It has knowledge of just about all the Debian CDs/DVDs/BDsproduced by Debian since the 3.0 (Woody) release, covering all theofficial releases (both older archived releases and the current stablerelease) and the current sets of daily and weekly testing builds.

Yes. Lookon cdimage.debian.orgfor the corresponding .list.gz file - it will list all thepackages and source files included in the image. For Debian Liveimages, you can find in the same directory as the image files somesimilarly named files suffixed with .packages. Download theseand then search them for the desired package name.

We only make official releases of the stable distributionwhen we think they truly deserve that name. Unfortunately, this meansthat stable releases only happen about every 2 years...

If you require more recent versions of some of the software inDebian, you can install stable and then upgrade (via the net)those parts you want to the versions from testing - it ispossible to mix software from the different releases.

Alternatively, try out the images of testing that aregenerated automatically every week. More information about testing security supportis available from the security FAQ.

If you only need newer versions of specific packages, you can alsotry the backports service, which takes packages from testingand modifies them to work on stable. This option may be safer thaninstalling the same package directly from testing.

The note at the bottom of the Debian on CD pagealways shows the version number of the latestrelease.

Detailed information on how to authenticate the signed checksumfiles containing the checksums of the ISO image files is available onthe authenticity verification page. Aftercryptographically verifying the checksum files, we can check that:

• Checksums of the downloaded ISO image files match those found in the checksum files. Computing the checksum of the ISO image files is performed by tools such as sha512sum and sha256sum.
• Checksums of already written optical media match those found in the checksum files. This is a slightly more difficult operation to describe.

The problem with the verification of written optical media is thatsome media types will possibly return more bytes than those found inthe ISO image. This trailing garbage is impossible to avoid with CDwritten in TAO mode, incrementally recorded DVD-R[W], formattedDVD-RW, DVD+RW, BD-RE, and also with USB keys. Therefore, we need toread exactly the same number of sectors of data from the media as arefound in the ISO image itself; reading any more bytes from the mediawill alter the checksum result.

• The isosize program can be used to find out the appropriate amount of bytes to be read from the optical media. It shows the sector count and the sector size from the optical media, where <device> is the device file of the loaded optical media.
  $ /sbin/isosize -x <device>
  sector count: 25600, sector size: 2048
• Then sector count and sector size are passed to dd to read the appropriate amount of bytes from the optical media and the byte stream is then piped to the appropriate checksum tool (sha512sum, sha256sum, etc).
  $ dd if=<device> count=<sector count> bs=<sector size> | sha512sum
• The computed checksum is to be compared against the corresponding checksum found in the appropriate checksum file (SHA512SUMS, SHA256SUMS, etc).

Alternatively, there is a useful helper script called check_debian_iso which can verify ISO image files andoptical media, reading the appropriate amount of bytes frommedia then computing the checksum and comparing it against thechecksum file.

• ISO image file verification. This will compare the checksum of the debian-6.0.3-amd64-netinst.iso image file against the corresponding checksum found in the SHA512SUMS checksum file.
  $ ./check_debian_iso SHA512SUMS debian-6.0.3-amd64-netinst.iso
• Optical media verification. This will compare the checksum of the media accessible as /dev/dvd against the checksum of debian-6.0.3-amd64-DVD-1.iso as found in the SHA512SUMS checksum file. Note that the ISO image file itself is not needed, its name is merely used to locate the corresponding checksum in the checksum file.
  $ ./check_debian_iso SHA512SUMS debian-6.0.3-amd64-DVD-1.iso /dev/dvd

Most likely, the tool you use for downloadingthe image does not have large file support, i.e. it has problemsdownloading files larger than 4 GBytes. The usual symptom forthis problem is that when you download the file, the file sizereported by your tool (and the amount of data that it downloads) istoo small by exactly 4 GB. For example, if the DVD image is4.4 GB, your tool will report a size of 0.4 GB.

Some old versions of wget also suffer from this problem -either upgrade to a version of wget which does not have thisrestriction or use the curl command line download tool:curl -C - live-usb-mac-os.html

Note that Debian ISO images for i386, amd64 and arm64 are alsobootable from a USB key; see below.

xorrisofor all optical media types (also doable as non-root user):
xorriso -as cdrecord -v dev=/dev/sr0 -eject debian-x.y.z-arch-MEDIUM-NN.iso
In order to get the full nominal speed when writing to BD-RE(i.e. without the slowdown caused by the drive's internal defectmanagement), add the option stream_recording=on.

growisofsfor DVD and BD optical media types:
growisofs -dvd-compat -Z /dev/sr0=debian-x.y.z-arch-MEDIUM-NN.iso

wodimfor CD optical media type:
wodim -v dev=/dev/sr0 -eject -sao debian-x.y.z-arch-CD-NN.iso

Kali Linux Live Usb Mac Os X

For Linux, there are also the X programsBrasero,K3B andX-CD-Roast,to name a few. Note that they're all frontends to the previouslymentioned low-level burning applications.

Brasero

Select the button Burn Image. Then click on Click here to select a disc image, browse and select your downloaded ISO file, check whether the settings under Properties are correct and choose Create Image.

K3b

Select the menu entry Tools - CD - Burn CD Image. In the dialog that opens, enter the path to the image in the Image to Burn field, check whether the other settings are correct, then click on Start.

X-CD-Roast

After the program has started, click onSetup and choose the HD settings tab. Copy the Debian CDimage to one of the directories that are displayed in the table. (Ifthe table is empty, enter the path of a directory you want to use fortemporary storage, and click on Add.) Click on OK toexit the setup. Next, select Create CD and then WriteTracks. Choose the Layout tracks tab, select the linedisplaying the image filename and click on Add, then click onAccept track layout. Finally, click on Write tracks.

On recent versions of Windows, this can be done nativley byright-clicking the ISO and selecting 'Burn image to disk (or similar)'

This might be a little problem on older versions of Windows, asmany Windows image-burning programs use their own formats for CDimages. To burn the .iso images you will most likely have touse a special menu. Look for options like ISO9660 file,Raw ISO image or 2048 bytes/sector. (Note: otherbytes/sector values are fatal!) Some programs do not offer thesechoices; use another burning program instead (ask a friend orcolleague). Here is some information about how to write CD images withspecific products:

ImgBurn (Freeware)

There are screenshots of how to write an image to CD/DVD

CDBurnerXP Pro (Freeware)

The process of writing an .iso image is described in the program's manual.

Roxio Easy-CD Creator

From the File menu, choose Create CD from image.... Then select the .iso file type, and the correct image. This opens up the CD creation setup GUI, from there ensure that all the information for your CD-R is correct. In the Create options portion, choose Create CD; under Write method, choose Track at once and Close CD.

Nero from Ahead Software

Disable the Wizard, then select Burn Image from the File or Recorder menu. Select All Files in the file selection window if necessary. Select the .iso file, click OK in the this is a foreign file dialogue box, in case one is displayed. In the option box that opens, the defaults should be okay: Data Mode 1, Block Size 2048, Raw Data, Scrambled, and Swappednot selected, and Image Header and Image Trailer left at 0. Click OK. Under Write CD or Burn, use the default options, e.g. Write and Determine maximum speed, plus check the Finalize CD option.

Microsoft Resource Kit Tools

The command-line Resource Kit Tools are provided by Microsoft free of charge, they work with Windows 2003 and XP. Two programs to write images to CD and DVD are included, they are named Cdburn.exe and Dvdburn.exe. Usage of the programs is described in the accompanying help file - essentially, the command to be executed is something like cdburn drive: iso-file.iso /speed max

If you can provide updated information or details for otherprograms, please let us know.

The Toast program for Mac OS is reported to work fine with.iso files. You can be extra-safe by giving it thecreator code CDr3 (or possibly CDr4) and type codeiImg using e.g. FileTyper. Double-clicking on the file willthen open up Toast directly, without having to drag-and-drop or govia the File-Open menu.

Another option is Disk Utility (included with Mac OSX 10.3 and higher): After opening the Disk Utility application (inthe /Applications/Utilities folder), selectBurn... in the Image menu and choose the CDimage to burn. Ensure that the settings are correct, then click onBurn.

Another option is Disk Copy (included with Mac OSX 10.1 and higher): After opening the Disk Copy application (inthe /Applications/Utilities folder), selectBurn Image... in the Image menu and choose the CDimage to burn. Ensure that the settings are correct, then click onBurn.

Several of the Debian and Debian Live images, notably all i386,amd64 and arm64 images, are created using the isohybridtechnology, which means that they may be used in two differentways:

• They may be written to CD/DVD/BD and used as normal for CD/DVD/BD booting.
• They may be written to USB flash drives, bootable directly from the BIOS / EFI firmware of most PCs.

On a Linux machine, simply use the cp command, to copy animage to a USB flash drive:

cp <file> <device>

Alternatively you can also use dd:

dd if=<file> of=<device> bs=4M; sync

where:

• <file> is the name of the input image, e.g. netinst.iso
• <device> is the device matching the USB flash drive, e.g. /dev/sda, /dev/sdb. Be careful to make sure you have the right device name, as this command is capable of writing over your hard disk just as easily if you get the wrong one!
• bs=4M tells dd to read/write in 4 megabyte chunks for better performance; the default is 512 bytes, which will be much slower
• The sync is to make sure that all the writes are flushed out before the command returns.

Additionally to the method above for Linux systems, there is also the win32diskimager program available, which allows writing such bootable USB flash drives under Windows. Hint: win32diskimager will apparently only list input files named *.img by default, while the Debian images are named *.iso. Change the filter to *.* if you use this tool.

Please note, that Debian advises not using unetbootin for this task. It can cause difficult-to-diagnose problems with booting and installing, so is not recommended.

There is no obligatory way of labeling. However, we suggest youuse the following scheme to ensure interchangeability:

Debian GNU/{Linux|Hurd|kFreeBSD} <version>[<revision>]
Official {<architecture>} {CD|DVD|BD}-<number>

For example:

Debian GNU/Linux 6.0.3
Official amd64 DVD-2

Debian GNU/kFreeBSD 6.0.3
Official i386 Netinst CD

If you have enough space, you can also add the codename to thefirst line, as in: Debian GNU/Linux 6.0.3 Squeeze.

Note that you are allowed to use the Officialdesignation only on CDs the image of which has achecksum that matches the one from thejigdofiles of official releases.Any CD that has no matching checksum (e.g. your own creations) must beclearly labelled as Unofficial, for example:

In the case of official weekly snapshots, version numbers like6.0.3 should not be used to avoid confusion with releasedDebian versions. Instead, label the image with a codename likeetch or a distribution name like testing. Also addSnapshot and the date of the snapshot to help identify it:

Debian GNU/Linux etch
Official Snapshot alpha Binary-2
2005-06-17

There is no official layout for the cover, back and label of aDebian CD/DVD/BD, but a number of people have produced nice-lookingimages. Please see the separate artworkpage.

Some older images are available from the archivesection on cdimage.debian.org. For example, you might want to tryout older images if you need support for a certain (sub)architecturewhich has been dropped for a newer release.

Note that when you install using a really old CD/DVD (pre 4.0,Etch), the contents of /etc/apt/sources.list will referencethe current stable Debian release by default. This means thatany upgrade over the net will upgrade to the current stablerelease.

If you want to install Debian on a large number of machines andthen keep all these installations up-to-date (e.g. security updates),installing from optical media is not ideal, but then neither isinstalling via the Internet, because the packages will have to bedownloaded again for each machine. In this case, you should set up alocal cache, the three options being:

• Make disc contents available via HTTP: Download the images, then make their contents available to your LAN on a local mirror. The individual machines can use this mirror as if it were a regular Debian server. For example, if the contents of a CD are available under the URL http://10.0.0.1/cd1/, machines in the local network can use the packages from the CD with the following line in their /etc/apt/sources.list:
  deb http://10.0.0.1/cd1/ stable main contrib
  A different URL and a separate entry in sources.list is necessary for each CD.
• Instruct your HTTP proxy to cache .deb files: Configure the proxy to keep .deb files for a long time, then set http_proxy in your environment on each machine to point at the cache, and use apt's HTTP acquisition method.
  This gives you most of the benefits of running a mirror, with none of the admin hassle. Since you can set limits on the proxy's disk usage, it works even for sites with limited disk space, and it has the advantage over mirroring that you only download those packages you install, which saves bandwidth. Squid can be told to keep the files by adding a line to /etc/squid/squid.conf:
  refresh_pattern debian.org/.*.deb$ 129600 100% 129600
• Set up a private Debian packages mirror: Beware that the Debian archive has grown to a tremendous size! Refer to the mirroring page for details.

Installing on a large number of machines can be tricky.Fully automaticinstallation (FAI), which is also available as a Debianpackage, may help you with this task.

Apart from a local Debian mirror, youalso need plenty of disc space. The image creation scripts arepackaged in the debian-cd package. However, it is usually abetter idea to use the latest code from git. (Still, you should have alook at the package's dependencies to ensure you have all thenecessary tools.)

To get the latest git version, make sure you have gitinstalled. From an empty directory, give the following command:

git clone https://salsa.debian.org/images-team/debian-cd.git

Should you try to use the scripts, check thedebian-cd mailing listarchive for solutions to the questions that will inevitablyshow up. :-)

The necessary steps to set up your debian-cd image mirror and keepit up to date are described on a separatepage.

We don't store/serve the full set of ISO images for all architectures,to reduce the amount of space taken up on the mirrors. You canuse the jigdo tool to recreate the missing ISOimages instead.