#syslinux

Due CrunchBang e un pennino

Visto che in estate c'è molto caldo e non si ha voglia di fare nulla, solitamente i linari si dedicano a discutere, e possibilmente a litigare, su quale distro sia migliore, se sia più bella Gnome o Kde o addirittura Unity, etc. etc. etc. Noi poveri utenti di Debian, che invece non abbiamo bisogno né di fare rollbacks, né di tirare il freno a mano, poiché la nostra distro, ancorché vecchia, si…

Debian stabile sostituire Grub2 con Syslinux

Syslinux è un avviatore di sitema molto più leggero di Grub ed anche la sua configurazione è molto più semplice. In realtà Syslinux originariamente veniva usato per avviare il sistema da filesystem FAT (File Allocation Table) come ad esempio dischi floppy o chiavette USB. In molte distribuzioni tipo ArchLinux il pacchetto da installare è syslinux mentre in Debian 7.0 stabile bisognerà installare

1. Basic Input Output System (BIOS) 2. Hardware with firmware 3. possible network boot 4.1. Master Boot Record (MBR) 4.2. Partition Tables 4.3. Volume Boot Record (VBR) 5.1. Grand Unified Bootloader (GRUB) 5.2. Syslinux 6. Initial Ramdisk (initrd) 7. Encrypted Partition 8. Tresor (keys in CPU)

1. Basic Input Output System (BIOS)

No good tools in Linux. Maybe flashrom can read the BIOS. But it does not work for all BIOS-Versions. Usually the BIOS vendors provide a flash tool to read and write the BIOS for Windows.

2. Hardware with firmware

Firmware depends on the hardware vendor. But is usually unknown.

3. possible network boot

etherboot.org

4.1. Master Boot Record (MBR)

The MBR are the first 512 byte on a disk. At the end it contains the partition table with up to 4 entries.

Get the MBR as user root with the following command:

DISK=/dev/sda # read first 512 block from /dev/sda dd if=${DISK} of=masterBootRecord.bin bs=512 count=1 # display the bytes of the MBR: hexdump -vC masterBootRecord.bin # or: hexedit masterBootRecord.bin # disassemble the MBR apt-get install nasm ndisasm masterBootRecord.bin > masterBootRecord.disassembled.txt

For assembler see: x86 instruction set and BIOS interrupt call 13 and not 100% correct analysis of MBRs.

Put as user root with the following command:

# write back the MBR to disk dd if=masterBootRecord.bin of=${DISK} bs=512 count=1

4.2. Partition Tables

Get the extended partition table:

DISK=/dev/sda sfdisk -dx ${DISK} > backup_extended.sfdisk

Write the extended partition table:

sfdisk -fx ${DISK} < backup_extended.sfdisk

Get each partition record as hexdump:

cfdisk -P r ${DISK} > partitionRecords.txt

Write partition records back as original hexdump:

numberOfRecords=$(expr \( $(cat partitionRecords.txt | wc -l) - 1 \) \/ 34) for index in $(seq $numberOfRecords);do let lineCounter=index*34 head -n $lineCounter partitionRecords.txt | tail -n 32 | sed 's/.*://g' | tr -d ' ' | xxd -ps -c16 -r > part${index}.bin sector=$(head -n $lineCounter partitionRecords.txt | tail -n 33 | head -n 1 | sed 's/Sektor \(.*\):/\1/g') let bytePosition=sector*512 echo "Index: $index, Sektor: $sector, bytePosition: $bytePosition" echo "dd if=part${index}.bin of=${DISK} bs=1 seek=$bytePosition count=512" dd if=part${index}.bin of=${DISK} bs=1 seek=$bytePosition count=512 done

4.3. Volume Boot Record (VBR)

The volume boot record are the first 512 byte of a partition. Get the volume boot record of the first partition:

PARTITION=/dev/sda1 dd if=${PARTITION} of=volumeBootRecord.bin bs=512 count=1 # disassemble the VBR: ndisasm volumeBootRecord.bin

5.1. Grand Unified Bootloader (GRUB)

GRUB is usually in the first megabyte of the disk after the master boot record.

# get GRUB from disk - and maybe a bit more DISK=/dev/sda dd if=${DISK} of=grub.bin bs=1 count=70000 skip=512 # find the correct grub.cfg strings -n 9 grub.bin # example output: (,msdos7)/boot/grub

In this example it is "msdos7" partition 7 - in Linux /dev/sda7. There you can find the grub.cfg.

mount /dev/sda7 /mnt cat /mnt/boot/grub/grub.cfg # wait 10 seconds set timeout=10 # example of a menu entry: menuentry 'Ubuntu, with Linux 3.2.0-37-generic' --class ubuntu --class gnu-linux --class gnu --class os { recordfail insmod part_msdos insmod ext2 set root='(hd0,msdos7)' search --no-floppy --fs-uuid --set 296bd37b-d6f6-48b6-9c94-5d6463ffec62 linux /boot/vmlinuz-3.2.0-37-generic root=UUID=296bd37b-d6f6-48b6-9c94-5d6463ffec62 ro quiet splash initrd /boot/initrd.img-3.2.0-37-generic }

In the example above, the Linux kernel and the initial ramdisk are found on the first hard disk (hd0) in partition 7 (msdos7 means /dev/sda7). The root file system is found on the partition with the UUID of root=UUID=...

# example for an encrypted partition: linux /boot/vmlinuz-3.2.0-37-generic root=/dev/mapper/volumegroup1-root ro quiet splash

In this example the initial ramdisk contains information where to find the encrypted partition and /dev/mapper/volumegroup1-root is mounted when the partition is decrypted.

5.2. Syslinux

The following steps describe how to prepare a (USB) disk to boot with syslinux. To boot from USB you have to go to the BIOS at start-up and change the boot order to USB first (before hard disk).

# run the following steps as root sudo bash usbDevice=/dev/sdc # unmount the USB device in case it is mounted umount ${usbDevice}* > /dev/null 2>&1 # overwrite the master boot record and # the partition table with zeroes dd if=/dev/zero of=$usbDevice bs=512 count=1 # create new master boot record # with assembler code (first 440 byte) echo " eb 58 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fa 31 c0 8e d8 8e c0 8e d0 bc 00 7c fb fc 89 e6 bf 00 06 b9 00 01 f3 a5 ea 77 06 00 00 88 16 00 08 be 9b 07 f6 c2 80 74 03 be 9f 07 e8 c7 00 b4 08 cd 13 31 c0 88 f0 40 a3 74 07 80 e1 3f 88 0e 76 07 be be 07 31 c0 b9 04 00 f6 04 80 74 03 40 89 f7 83 c6 10 e2 f3 83 f8 01 74 03 e9 88 00 8a 16 00 08 b8 00 41 bb aa 55 31 c9 30 f6 f9 cd 13 72 2e 81 fb 55 aa 75 28 f6 c1 01 74 23 be a3 07 e8 73 00 57 be 64 07 8b 5d 08 89 5c 08 8b 5d 0a 89 5c 0a 8a 16 00 08 8c d8 8e c0 b8 00 42 eb 34 be a9 07 e8 50 00 57 8b 45 08 8b 55 0a f7 36 76 07 42 89 d1 31 d2 f7 36 74 07 88 c5 d1 e8 d1 e8 24 c0 08 c1 88 d6 8a 16 00 08 8c d8 8e c0 bb 00 7c b8 01 02 cd 13 72 16 5e 81 3e fe 7d 55 aa 75 08 fa ea 00 7c 00 00 77 05 be 78 07 eb 03 be 8e 07 e8 02 00 eb fe ac 20 c0 74 0c b4 0e 8a 3e 62 04 b3 07 cd 10 eb ef c3 00 00 10 00 01 00 00 7c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4e 6f 20 6f 70 65 72 61 74 69 6e 67 20 73 79 73 74 65 6d 0d 0a 00 44 69 73 6b 20 65 72 72 6f 72 0d 0a 00 46 44 44 00 48 44 44 00 20 45 42 49 4f 53 0d 0a 00 00 00 00 00 00 00 00 00 00 2c 44 63" | sed 's/ /\\\\x/g' | xargs echo -en > mbr_boot_usb.bin # copy that code to the usb disk dd if=mbr_boot_usb.bin of=$usbDevice count=1 bs=440 # create the partition table on the USB disk # 1. partition 40 MB FAT bootable # 2. partition 40 MB FAT databackup # 3. partition rest with linux ext3 sfdisk -uM $usbDevice << EOF ,40,c,* ,40,c ,,83 EOF # create the file systems on the USB disk mkfs.vfat -F 32 ${usbDevice}1 -n boot mkfs.vfat -F 32 ${usbDevice}2 -n databackup mkfs.ext4 ${usbDevice}3 tune2fs -c 0 ${usbDevice}3 e2label ${usbDevice}3 usb # syslinux is usually available in Ubuntu # write it to the first partition of the USB disk syslinux -f ${usbDevice}1 sync pmount ${usbDevice}1 /media/boot # or mkdir /media/boot mount ${usbDevice}1 /media/boot # create a syslinux.cfg - the boot menu cat > /media/boot/syslinux.cfg << EOF # PROMPT 1 DEFAULT ubu1 TIMEOUT 20 SAY boot options: SAY ubu1 - Ubuntu 64 Bit LABEL ubu1 KERNEL linux1 APPEND initrd=initrd1 root=/dev/sda6 ro quiet splash EOF # now copy your linux kernel (linux1) and # your initial ramdisk (initrd1) to /media/boot cp /boot/initrd.img-3.2.0-37-generic /media/boot/initrd1 cp /boot/vmlinuz-3.2.0-37-generic /media/boot/linux1 # the root=/dev/sda6 tells the initrd scripts # to mount /dev/sda6 and use it as root file system

6. Initial Ramdisk (initrd)

The initial ramdisk (initrd) contains additional kernel modules and reads information where the root file system can be found. You can also take a look at the "initramfs-tools". To extract the initrd type:

# preparation in the memory mkdir /dev/shm/extractedInitrd cd /dev/shm/extractedInitrd # enter your initial ramdisk here initrd="/boot/initrd.img-3.2.0-37-generic" # backup the original initial ramdisk cp "$initrd" "$initrd".backup # extract an intial ramdisk gunzip -dc "$initrd" | cpio -id # create an initial ramdisk find ./ | cpio -H newc -o > ../initrd-new; gzip -f ../initrd-new # overwrite to original initial ramdisk mv ../initrd-new.gz "$initrd"

These are the basics. To test the initrd it is useful to take a virtual machine. But you can also boot your system to test the initrd. To remove unnecessary kernel modules from the initial ramdisk do the following:

cd /dev/shm/extractedInitrd/lib/modules/*-generic/kernel # now check which modules are used and remove the others # the following commands need to be run in one line find -type f | egrep -v "$(lsmod | cut -f 1 -d ' ' | grep -v Module$ | xargs -i modinfo '{}' | grep filename | sed 's/^.* \/lib\/modules\/.*\/kernel\///g' | grep -v "^filename" | tr '\n' '|' | sed 's/|$//g')" | xargs -i rm -f '{}' cd ../../../.. # There is also the directory "lib/firmware" which contains # some megabytes which can be removed. # create the initial ramdisk find ./ | cpio -H newc -o > ../initrd-new; gzip -f ../initrd-new

This makes the initrd smaller and speeds up booting from slow USB disks.

If you want to copy your encrypted partition / root file system to another disk or partition you need to change the configuration of the initial ramdisk:

# change the following line with your device number DISK=sda8 UUID_OF_DISK=$(blkid -o value /dev/${DISK} | head -n 1 | tr -d '\n') cd /dev/shm/extractedInitrd/ # backup the configuration cp conf/conf.d/cryptroot conf/conf.d/cryptroot.original # create the new configuration echo "target=${DISK}_crypt,source=UUID=${UUID_OF_DISK},key=none,rootdev" > conf/conf.d/cryptroot # maybe you need to add an entry for the # logical volume manager if you did use it: # ,lvm=volumegroup1-root

7. Encrypted Partition

The encrypted partition itself contains two configuration files:

cat /etc/fstab # for example: /dev/mapper/volumegroup1-root / ext4 noatime,errors=remount-ro 0 1 cat /etc/crypttab # for example: sdc7_crypt UUID=b0e3d5d9-8dd4-4815-a583-1a71896d163b none luks

To create a new encrypted partition:

DISK=/dev/sda3 # create an encrypted container: cryptsetup luksFormat ${DISK} YES 2 x passphrase cryptsetup luksOpen ${DISK} volume mkfs.ext4 -L volume /dev/mapper/volume tune2fs -c 0 -i -1 -m 0 /dev/mapper/volume mount /dev/mapper/volume /mnt # close the container: umount /mnt cryptsetup luksClose volume

cryptsetup with logical volume group - lvm2.

cryptsetup luksOpen /dev/sda5 myvolume # with logical volume manager apt-get install lvm2 # make the volume group available: vgchange -ay mount /dev/mapper/volumegroup1-root /mnt/ # close the partition: umount /mnt/ vgchange -an cryptsetup luksClose myvolume

Basic commands for cryptsetup:

# backup the key header: # copies ~1 MB of the first bytes of the partition cryptsetup luksHeaderBackup --header-backup-file cryptHeader.backup.bin /dev/sda7 # restore it cryptsetup luksHeaderRestore --header-backup-file cryptHeader.backup.bin /dev/sda7 # change key: cryptsetup luksAddKey /dev/sda7 # enter the old passphrase first => "Enter any passphrase" # show how many keys / slots are used: cryptsetup luksDump /dev/sda7 # 8 keys are possible # with two keys installed, both keys can be used # remove key from a certain key slot: cryptsetup luksRemoveKey --key-slot 2 # add key to a certain slot cryptsetup luksAddKey --key-slot 2

8. Tresor (keys in CPU)

ESXi 5.0からは3.5までのddでのインストールはできないらしく、 USBメモリから起動できるようにしたい場合はとりあえずインストールイメージをUSBメモリにコピーして インストール先を「その起動したUSBメモリ」にすることでUSBメモリ1本で起動可能なUSBメモリを作成できるようです。 しかし光学メディアってほんと必要なくなったなぁ。 ちなみに新規インストールイメージです。過去のESXiを使用している場合はアップグレードしないとすでに作成済みの仮想マシンが使えなくなる可能性がありますので注意してください。 Linux上から作成する手順はみかけたもののWindows上からでも多分できるだろうってことで手順をかきながらやってみます。 0. VMware vSphere Hypervisor (ESXi) のダウンロード とりあえず公式サイトからESXiをダウンロードします。（無償） ダウンンロードにはアンケートに回答する必要があります。 注意点は ・ビジネスユースだとライセンスをきちんと登録してstandardとかprofessionalとかでやる必要がある？（今回評価ライセンスでしか考えてないので詳しくは各自でお調べ下さい） ・メールアドレスをきちんと登録しないとアクティベーションできずに評価版ライセンスキーがもらえない。 ・クライアントもあとで必要になると思うんでvClientもダウンロードしましょう。 ・VMware toolsのダウンロードは必要に応じて。 1. インストールUSBメモリの作成 まずはUSBメモリをFat32でフォーマットします。 フォーマットに「FAT」を選んで、クイックフォーマットをオフにしましょう。 USBメモリがエクスプローラで見えていない場合はコンピュータの管理＞ディスクの管理からフォーマットできると思います。 ESXi 3.5や4.0用に作成したUSBメモリを再利用したい場合は過去の投稿を見てください。

2. syslinuxのインストール boot可能なUSBとするためにsyslinuxを用意します。 syslinuxの昔の公式が移転済みだったので、ファイルのありかを直に紹介。 http://www.kernel.org/pub/linux/utils/boot/syslinux/ syslinux-x.xx.zipみたいなファイル名のファイル一つダウンロードすればいいと思います。 ダウンロードしたらzipファイルを解凍して、コマンドプロンプトで解凍したディレクトリの下のwin32ディレクトリまで移動します。 win32ディレクトリの中身を別のディレクトリにコピーしてそこで実行しても構わないようです。 ※ この際、コマンドプロンプトは「管理者で実行」で起動します。じゃないと多分書き込めない。 以下のコマンドを実行します。 syslinux -a [USBのドライブレター]: # 起動に失敗する場合はmオプション(mbrをインストール)でsyslinux -ma [USBのドライブレター]: で実行します。 ドライブは慎重に確認してください。ここで間違えたドライブを指定するとそのドライブは壊れます。 うちの環境ではgドライブがUSBメモリだったので syslinux -a g: となります。 （画像はmオプション付き）

昔作ったESXi 3.5のブート用USBを再利用しようと思ったら、そのままじゃダメで、40MBのディスクとして認識されてしまっていた（syslinux分かな） ファイル書きこんで未フォーマットなディスクとして認識させる必要があったんだよね。 パーティションブロック壊せればいいので小さいファイル書きこめば、windowsがフォーマットされてないと認識するはず。 で、それを実現するためのツールとしてDD for Windowsというシリコンリナックス社が公開しているツールがあります。 ファイルイメージをUSBなどに書きこむGUIツールです。 Linuxのddコマンドみたいなものですね。 ※ 同名のツールがchrysocome.netで公開されているコマンドラインのツールもあります。あれも便利ですが、今回扱うものとは違います。こっちでやってもいいし、それと別にrawwrite用のツールもあるけど、ドライブをUIで指定できる分こっちのが安全かも。 Linuxのブートイメージなんかを作るのに便利なんですが、どうもWindows 7 の64bit版だとUSBを認識してくれない。 単純なことでしたが解決したので公開。

I read that some people had difficulties booting Acronis Backup & Recovery 10 with Syslinux. I had these difficulties, too. Why would you boot Acronis Backup & Recovery 10 with Syslinux? Because you want to make a bootable USB stick with more than Acronis Backup & Recovery 10. Here is how you can get Acronis Backup & Recovery 10 to boot with Syslinux.

Create an emergency disk image (extension .iso) with Acronis Rescue Media Builder.

In order to boot with Syslinux you need to setup a syslinux usb-stick (read about that in the documentation provided by syslinux. A basic syslinux.cfg for booting Acronis Backup & Recovery 10 looks like this:

MENU DEFAULT acronis LABEL acronis MENU LABEL Acronis: Backup & Recovery 10 KERNEL /boot/br10/kernel.dat APPEND initrd=/boot/br10/ramdisk.dat vga=794 ramdisk_size=49152 acpi=off product=bootagent media_for_windows quiet noapic

Of course you have to make the paths fitting to the location where you store the kernel.dat and the ramdisk.dat (or agent_ramdisk.dat).

Now, Acronis uses a trick to fool you. The files visible when looking in the ISO-file are not the real ones used too boot Acronis Backup & Recovery 10. These are the ones for the trial verison of the program. And if you use these, you will get an error message, saysing your license is deactivated.

Failed to check the License Key. The key is disabled

The real files are hidden in the ISO as well but made invisible by Acronis by manipulating the file table. I do not know which free programs can do this, but you need to extract two files from the ISO-image: one is dat2.dat (the ramdisk file) and the other dat3.dat (the kernel file). A workaround would be a hex-editor (like the free HxD) and search inside the ISO for the beginning of dat2.dat

1F 8B 08 08 E0 13 F5 4C 00 00 61 67 65 6E 74 5F

and the ending

FC 9F 7F 96 F2 BF B5 34 F1 23 44 09 CA 09

and copy everything between (including the bytes posted above) into a new file dat2.dat. Be aware that there are two locations in the ISO-file that match. You care only about the first one. The second is for the trial version file. Do the same for dat3.dat with the beginning

EA 05 00 C0 07 8C C8 8E D8 8E C0 8E D0 31 E4 FB

and the end

>00 00 00 00 00 00 00 00 00 00 00 00 B3 2B A8 58

rename dat2.dat to ramdisk.dat and rename dat3.dat to kernel.dat, place both files on the USB-stick and make sure the paths in the syslinux.cfg are set right.

You can use the following Python script (I am using Python 3.1.2, sorry, but maybe you can edit) to extract the files from the ISO-file, you only need to make sure to edit the filename constants in the script:

# -*- coding: utf-8 -*- # filename: extract.py import os import os.path from optparse import OptionParser N_RAMD = 'ramdisk.dat' N_KERN = 'kernel.dat' # helper class for struct-like object class Bunch: def __init__(self, **kwds): self.__dict__.update(kwds) # signatures of the different files dd11 = Bunch( kernel=Bunch(begin=b'\xea\x05\x00\xc0\x07\x8c\xc8\x8e\xd8\x8e\xc0\x8e\xd0\x31\xe4\xfb', end=b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x77\xa4\x1e\xce', name=N_KERN), ramdisk=Bunch(begin=b'\x1f\x8b\x08\x00\xe0\xfc\x29\x4d\x02\x03\xb4\xbd\x7b\x73\x25\xd7', end=b'\x58\xff\x3f\x3e\xd5\xc7\xff\x00\x11\xdd\xa0\x53\x00\x06\x53\x05', name=N_RAMD)) tih2011 = Bunch( kernel=Bunch(begin=b'\xea\x05\x00\xc0\x07\x8c\xc8\x8e\xd8\x8e\xc0\x8e\xd0\x31\xe4\xfb', end=b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x4f\xf7\xc0\xc6', name=N_KERN), ramdisk=Bunch(begin=b'\x1f\x8b\x08\x08\x16\xe0\x86\x4c\x00\x00\x72\x61\x6d\x64\x69\x73', end=b'\x42\x16\xc0\xfc\x9f\x73\xce\x3b\x60\xb5\x88\x69\xbc\xf8\x79\x04', name=N_RAMD)) br10 = Bunch( kernel=Bunch(begin=b'\xea\x05\x00\xc0\x07\x8c\xc8\x8e\xd8\x8e\xc0\x8e\xd0\x31\xe4\xfb', end=b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xb3\x2b\xa8\x58', name=N_KERN), ramdisk=Bunch(begin=b'\x1f\x8b\x08\x08\xe0\x13\xf5\x4c\x00\x00\x61\x67\x65\x6e\x74\x5f', end=b'\x9a\x6a\xfc\x9f\x7f\x96\xf2\xbf\xb5\x34\xf1\x23\x44\x09\xca\x09', name=N_RAMD)) # helper function to copy bytes from one file to anonther def cp(iname, oname, pos, n_bytes): buffer_size = 2048 buffer = c_bytes = 0 with open(iname, 'rb') as ifile: with open(oname, 'wb') as ofile: ifile.seek(pos) while (1): if ((n_bytes - c_bytes) < buffer_size): buffer = ifile.read(n_bytes - c_bytes) else: buffer = ifile.read(buffer_size) if buffer: c_bytes += len(buffer) ofile.write(buffer) else: break # helper function to find position of string in a large file def fnd(fname, s, start=0): with open(fname, 'rb') as infile: size = os.path.getsize(fname) buffer_size = 4096 buffer = None infile.seek(start) prebuffer = len(s)-1 while (1): if (infile.tell() >= prebuffer and infile.tell() < size): infile.seek(infile.tell() - prebuffer) buffer = infile.read(buffer_size) if buffer: found = buffer.find(s) if found >= 0: return infile.tell()-(len(buffer)-found) else: return -1 # begin: option parsing parser = OptionParser(usage='Usage: %prog [options] ISOFILE', version='%prog 0.1') parser.add_option("--product", dest="product", help="PRODUCT is BR10 or DD11 or TIH2011 (for Backup & Recovery 10, Disk Director 10 or True Image Home 2011)", metavar="PRODUCT") (options, args) = parser.parse_args() if options.product == None or options.product == 'BR10': print('Assuming product: Acronis: Backup & Recovery 10') product = br10 elif options.product == 'DD11': print('Assuming product: Acronis: Disk Director 11') product = dd11 elif options.product == 'TIH2011': print('Assuming product: Acronis: True Image Home 2011') product = tih2011 else: parser.error('Invalid argument to option --product. Try --product followed by either BR10, DD11 or TIH2011.') if len(args) == 0: parser.error('Argument ISOFILE required.') if not os.path.exists(args[0]): parser.error('Argument ISOFILE must be a valid path to an existing file.') # end: option parsing error = False # finding and extracting the files for f in (product.ramdisk, product.kernel): if not error: b_pos = e_pos = 0 b_pos = fnd(args[0], f.begin) if (b_pos >= 0): e_pos = fnd(args[0], f.end, start=(b_pos + len(f.begin))) if (e_pos >= 0): print('Extracting file ({0}).'.format(f.name)) cp(args[0], os.path.join(os.path.dirname(os.path.abspath(args[0])),f.name), b_pos, (e_pos - b_pos + len(f.end))) if error: print('Error: Something went wrong. Maybe wrong product. See help for option --product.')

Converted Script as executable file (rapidsharecom)