remastering trisquel 8 iso (having a problem with it)
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
tried to "remaster" trisquel 8 iso (64bit, default 2.6 Gb edition) using these instructions:
https://trisquel.info/en/wiki/customizing-trisquel-iso
resulting iso was only 2.2 Gb (the only change I made is installing tiny 2048-qt package, to test if remastering process works)
after making bootable USB flash drive from it (trie twice: with rufus and trisquel's own "startup disk creator") and tried to boot from it
drive written with startup disk creator it refused to even start to boot, as if the drive was not bootable
with drive written with rufus got this error (instead of # and $ were "table corner" characters, no idea how to type them):
SYSLINUX 4.07 EDD 2013-07-25 Copyright (C) 1994-2013 H. Peter Anvin et al
Unknown keyword in configuration file: #u$nU
No DEFAULT or UI configuration directive found
boot:
multiple forum posts suggested renaming isolinux folder and files to syslinux, after doing so I got this error:
SYSLINUX 4.07 EDD 2013-07-25 Copyright (C) 1994-2013 H. Peter Anvin et al
Could not find kernel image: /isolinux/isolinux.cfg
boot:
and could not find how to resolve it. there is a (text) isolinux.cfg file in USB drive's root folder which references /isolinux/isolinux.cfg but after changing this reference according to changed folder/file name I got exactly same error
any pointers on what may be causing there errors and what can I try to fix them?
or maybe alternative remastering tool or process?
Obviously, your USB drive was indeed "bootable", otherwise you wouldn't see syslinux's error messages, only that you have to correct the configuration files.
You may need to read syslinux's documentation. I recently tried to remaster a Debian Live USB and managed to make the persistence partition working under either BIOS or UEFI. To achieve this, I plowed through both syslinux's and grub's documentation, and succeeded on the second try.
UPDATE:
unpacked both original *.iso image and "remastered" and compared: almost all files are different.
for example \isolinux\isolinux.cfg file unpacked from original *.iso contains following text:
# D-I config version 2.0
include menu.cfg
default vesamenu.c32
prompt 0
timeout 300
ui gfxboot bootlogo
same file from "remastered" *.iso contans this:
УuГnU†R ЌjqяPЭ,ДђЋэ`aЁэЎ¦ЬФ н‡ЉТ…»±Q@zЭх›3u#џ Ш HЇIЬ4ЉFjє?»р yыБ lЁIt±АЊщрЈ›Е©Жvј-ЗЎшзd$ь»П
replaced all files (except contents of \casper\ folder) on my bootable USB flash drive with same files from original *.iso and tried to boot from this frankenstein: got trisquel's boot menu but after selecting "try without installing" it wrote this:
Invalid or corrupt kernel image.
boot:
apparently squashfs is mangled too
\isolinux\isolinux.cfg file in src folder created during remastering process (as described in https://trisquel.info/en/wiki/customizing-trisquel-iso) contains same text as original one so it should have been mangled during (re)packing stage
can somebody please point me to build script or instructions for how to build *.iso of trisquel 8 (or trisquel 9) from source code?
I see weird characters. Which coding do you use?
yes, that's what I called "mangled"
I did not change anything in my settings so should be whatever encoding trisquel 8 uses by default
I am running it from USB flash drive and choose default (English) language in its boot menu
update:
tried to unpack my modified .iso and check a bunch of text files contained inside squashfs file - they are readable and seem to be as they should be
tried to make boot flash drive from modified .iso with rufus and hen replace flash drive's contents (except squashfs file) with contents of another boot flash drive made in the same way except from original trisquel 8 .iso file.
it shows boot menu but when "try trisquel without installing" is chosen it shows this error:
Invalid or corrupt kernel image.
apparently only some parts of modified .iso got mangled (possibly written with incorrect encoding, see above discussion)
how can I find out what parts got mangled?
- Vous devez vous identifier ou créer un compte pour écrire des commentaires