Re: Linux Live Usb Creator Anleitung
Thechosen Wong
This page discusses various multi-platform methods on how to create an Arch Linux Installer USB drive (also referred to as "flash drive", "USB stick", "USB key", etc) for booting in BIOS and UEFI systems. The result will be a live USB system that can be used for installing Arch Linux, system maintenance or for recovery purposes, and that, because of using Overlayfs for /, will discard all changes once the computer shuts down.
If you would like to run a full install of Arch Linux from a USB drive (i.e. with persistent settings), see Install Arch Linux on a removable medium. If you would like to use your bootable Arch Linux USB stick as a rescue USB, see chroot.
KDE ISO Image Writer can be downloaded via isoimagewriter. It can auto-detect the USB-drive and you need to manually select a ISO file. It is recommended to use .sig file to signature but it can be skipped by clicking "create".
Linux distributions running GNOME can easily make a live CD through nautilus and gnome-disk-utility. Simply right-click on the .iso file, and select Open With Disk Image Writer. When GNOME Disk Utility opens, specify the flash drive from the Destination drop-down menu and click Start Restoring.
xorriso-dd-target (from libisoburn) is a shell script which attempts to reduce the risk of overwriting the wrong storage device. Its safest mode is named -plug_test. For example, to use it as a regular user who can elevate to root using sudo:
KDE ISO Image Writer can be downloaded as .exe file at isoimagewriter. It can auto-detect the USB-drive and you need to manually select a ISO file. It is recommended to use .sig file to signature but it can be skipped by clicking "create".
win32diskimager is another graphical tool for writing images to USB sticks or SD/CF cards from Windows. Select your ISO image and the target USB drive letter (you may have to format it first to assign it a drive letter), and click Write.
This method does not require any workaround and is as straightforward as dd under Linux. Just download the Arch Linux ISO, and with local administrator rights use the USBwriter utility to write to your USB flash memory.
If your Arch Linux ISO is elsewhere you may need to state the full path, for convenience you may wish to put the Arch Linux ISO into the same folder as the dd executable. The basic format of the command will look like this.
Your USB device will appear as something like /dev/disk2 (external, physical). Verify that this is the device you want to erase by checking its name and size and then use its identifier for the commands below instead of /dev/diskX.
This command will run silently. To view progress, send SIGINFO by pressing Ctrl+t. Note diskX here should not include the s1 suffix, or else the USB device will only be bootable in UEFI mode and not legacy. After completion, macOS may complain that The disk you inserted was not readable by this computer. Select Ignore. The USB device will be bootable.
To create an Arch Linux installer, download the ISO image file on your Android device. Plug the USB drive to your device, using a USB-OTG adapter if needed. Open EtchDroid, select Flash raw image, select your Arch ISO, then select your USB drive. Grant the USB API permission and confirm.
This method is more complicated than writing the image directly with dd, but it does keep the flash drive usable for data storage (that is, the ISO is installed in a specific partition within the already partitioned device without altering other partitions).
Syslinux files for BIOS systems are already copied to /mnt/boot/syslinux/. Unmount the FAT file system, install the syslinux and mtools packages and run the following commands to make the partition bootable:
It does not require creating a EFI system partition on the drive as all UEFI will happily boot any FAT volume from USB flash drives. The most compatible setup would be using the MBR partition table with a single active (bootable) primary partition of type 0c "W95 FAT32 (LBA)".[3]
Ventoy is an open source tool to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. With ventoy, you do not need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD(x)EFI files to the USB drive and boot them directly. You can copy many files at a time and ventoy will give you a boot menu to select them. It is available as ventoy-binAUR.
This method uses Syslinux and a Ramdisk (MEMDISK) to load the entire Arch Linux ISO image into RAM. Since this will be running entirely from system memory, you will need to make sure the system you will be installing this on has an adequate amount. A minimum amount of RAM between 500 MB and 1 GB should suffice for a MEMDISK based, Arch Linux install.
Next copy the ISO that you would like to boot to the Boot/ISOs folder. After that, extract from the following files from the latest release of syslinux from here and copy them into the following folders.
Use the c command to create a new partition (leave the default values for the first and last sectors if it should span all available free size). If you want to access it in other operating systems, change the MBR partition type ID using the t command (e.g. to 0c "W95 FAT32 (LBA)" or 07 "HPFS/NTFS/exFAT"). Write the changes to disk and exit via the w command.
Permission is granted to copy, distribute and/or modify this documentunder the terms of the GNU Free Documentation License, Version 1.2 orany later version published by the Free Software Foundation; with noInvariant Sections.
Briefly, a boot loader is the first software program that runs whena computer starts. It is responsible for loading and transferringcontrol to an operating system kernel software (such as Linux orGNU Mach). The kernel, in turn, initializes the rest of the operatingsystem (e.g. a GNU system).
GNU GRUB is a very powerful boot loader, which can load a wide varietyof free operating systems, as well as proprietary operating systems withchain-loading1. GRUB is designed toaddress the complexity of booting a personal computer; both theprogram and this manual are tightly bound to that computer platform,although porting to other platforms may be addressed in the future.
One of the important features in GRUB is flexibility; GRUB understandsfilesystems and kernel executable formats, so you can load an arbitraryoperating system the way you like, without recording the physicalposition of your kernel on the disk. Thus you can load the kerneljust by specifying its file name and the drive and partition where thekernel resides.
When booting with GRUB, you can use either a command-line interface(see Command-line interface), or a menu interface (see Menu interface). Using the command-line interface, you type the drivespecification and file name of the kernel manually. In the menuinterface, you just select an OS using the arrow keys. The menu isbased on a configuration file which you prepare beforehand(see Configuration). While in the menu, you can switch to thecommand-line mode, and vice-versa. You can even edit menu entriesbefore using them.
In the following chapters, you will learn how to specify a drive, apartition, and a file name (see Naming convention) to GRUB, how toinstall GRUB on your drive (see Installation), and how to boot yourOSes (see Booting), step by step.
Erich then began modifying the FreeBSD boot loader so that it wouldunderstand Multiboot. He soon realized that it would be a lot easierto write his own boot loader from scratch than to keep working on theFreeBSD boot loader, and so GRUB was born.
Erich added many features to GRUB, but other priorities prevented himfrom keeping up with the demands of its quickly-expanding user base. In1999, Gordon Matzigkeit and Yoshinori K. Okuji adopted GRUB as anofficial GNU package, and opened its development by making the latestsources available via anonymous CVS. See Obtaining and Building GRUB, for more information.
Over the next few years, GRUB was extended to meet many needs, but itquickly became clear that its design was not keeping up with the extensionsbeing made to it, and we reached the point where it was very difficult tomake any further changes without breaking existing features. Around 2002,Yoshinori K. Okuji started work on PUPA (Preliminary Universal ProgrammingArchitecture for GNU GRUB), aiming to rewrite the core of GRUB to make itcleaner, safer, more robust, and more powerful. PUPA was eventually renamedto GRUB 2, and the original version of GRUB was renamed to GRUB Legacy.Small amounts of maintenance continued to be done on GRUB Legacy, but thelast release (0.97) was made in 2005 and at the time of writing it seemsunlikely that there will be another.
GRUB 2 is a rewrite of GRUB (see History), although it shares manycharacteristics with the previous version, now known as GRUB Legacy. Usersof GRUB Legacy may need some guidance to find their way around this newversion.
Except for specific compatibility modes (chain-loading and the Linuxpiggyback format), all kernels will be started in much the samestate as in the Multiboot Specification. Only kernels loaded at 1 megabyteor above are presently supported. Any attempt to load below thatboundary will simply result in immediate failure and an error messagereporting the problem.
Support a human-readable text configuration file with preset bootcommands. You can also load another configuration file dynamically andembed a preset configuration file in a GRUB image file. The list ofcommands (see Commands) are a superset of those supported on thecommand-line. An example configuration file is provided inConfiguration.
A menu interface listing preset boot commands, with a programmabletimeout, is available. There is no fixed limit on the number of bootentries, and the current implementation has space for several hundred.
A fairly flexible command-line interface, accessible from the menu,is available to edit any preset commands, or write a new boot commandset from scratch. If no configuration file is present, GRUB drops tothe command-line.
d3342ee215