search for: exithelp

...oesn't seem to be hung. This suggestion was made in order to distinguish a potential "apparent hang" vs. "it really hang". It was not really about "text clarity". > > BTW, Debian's prompt.cfg has one line INCLUDEing another cfg file, > > 'exithelp.cfg'. Although I mentioned this "exithelp.cfg" file in my "15 > > steps" in a previous email, I did not mention that this 'exithelp.cfg' > > file is incorrect, because I didn't want to add complexity to the > > instructions (and considering that...

...s not really about "text clarity". > > > > I'll look at this again, but I've lost track of where it is. > syslx64debian604displayfiles? > > > > > > > BTW, Debian's prompt.cfg has one line INCLUDEing another cfg file, > > > > 'exithelp.cfg'. Although I mentioned this "exithelp.cfg" file in my "15 > > > > steps" in a previous email, I did not mention that this 'exithelp.cfg' > > > > file is incorrect, because I didn't want to add complexity to the > > > > inst...

...vs. "it really hang". It was not really about "text clarity". > I'll look at this again, but I've lost track of where it is. syslx64debian604displayfiles? > > > > BTW, Debian's prompt.cfg has one line INCLUDEing another cfg file, > > > 'exithelp.cfg'. Although I mentioned this "exithelp.cfg" file in my "15 > > > steps" in a previous email, I did not mention that this 'exithelp.cfg' > > > file is incorrect, because I didn't want to add complexity to the > > > instructions (and c...

...ot;. > > > > > > > I'll look at this again, but I've lost track of where it is. > > syslx64debian604displayfiles? > > > > > > > > > > BTW, Debian's prompt.cfg has one line INCLUDEing another cfg file, > > > > > 'exithelp.cfg'. Although I mentioned this "exithelp.cfg" file in my "15 > > > > > steps" in a previous email, I did not mention that this 'exithelp.cfg' > > > > > file is incorrect, because I didn't want to add complexity to the > > >...

...As I mentioned before, ATM I am not willing to do all the testing and reports for Debian, especially when there is no indication that either upstream nor downstream developers care (with very few exceptions, too-few). BTW, Debian's prompt.cfg has one line INCLUDEing another cfg file, 'exithelp.cfg'. Although I mentioned this "exithelp.cfg" file in my "15 steps" in a previous email, I did not mention that this 'exithelp.cfg' file is incorrect, because I didn't want to add complexity to the instructions (and considering that your intention was/is to s...

...fg ../../ > > > 3_ Rename 'target/syslinux.cfg' to 'target/debian.cfg' > > > 4_ Edit content of 'target/debian.cfg' to (only) be: > > include menu.cfg > default vesamenu.c32 > prompt 0 > timeout 0 > > > 5_ Edit content of 'target/exithelp.cfg' to (only) be: > > label menu > kernel vesamenu.c32 > config debian.cfg > > > 6_ (Possibly you need some special/root rights/permissions for this > step) Delete 'target/ldlinux.*' and 'target/*.c32'. > > > 7_ From the 'bio...

...TM I am not > willing to do all the testing and reports for Debian, especially when > there is no indication that either upstream nor downstream developers > care (with very few exceptions, too-few). > > BTW, Debian's prompt.cfg has one line INCLUDEing another cfg file, > 'exithelp.cfg'. Although I mentioned this "exithelp.cfg" file in my "15 > steps" in a previous email, I did not mention that this 'exithelp.cfg' > file is incorrect, because I didn't want to add complexity to the > instructions (and considering that your intention...

On Mon, Dec 3, 2018 at 10:02 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Now it is just dd, mkfs and copy in the files we need. > > One less thing to worry about keeping versions consistent. > > > > > > I just noticed those 2 files that were added by > > > > syslinux -i boot.img > > > > (right?) > > > >

On Fri, Dec 7, 2018 at 11:16 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > If this is the best we can do, I'm ok with that. > > It's _not_ the best we can do. The question is... what exactly is this > "we"? We have both made some contributions to my little goal. you certainly share in the credit. > > After some testing (which I

...h drive boots the Debian installer in the old PC! Congrats. > There is no syslinux.cfg on debian-8.7.1-i386-xfce-CD-1.iso: The configuration is named /isolinux/isolinux.cfg. Looks like it is surrounded by a little empire of .cfg files: /isolinux/adgtk.cfg /isolinux/adtxt.cfg /isolinux/exithelp.cfg /isolinux/gtk.cfg /isolinux/isolinux.cfg /isolinux/menu.cfg /isolinux/prompt.cfg /isolinux/rqgtk.cfg /isolinux/rqtxt.cfg /isolinux/spkgtk.cfg /isolinux/stdmenu.cfg /isolinux/txt.cfg The "append" statements are in several of the subordinate files. E.g. in /isolinux/t...

...86 looks like:- |-- gtk | |-- initrd.gz | |-- install.bat | `-- vmlinuz |-- initrd.gz |-- install.bat |-- vmlinuz `-- xen |-- debian.cfg |-- initrd.gz `-- vmlinuz 2 directories, 9 files and /mnt/sr0/isolinux looks like:- |-- adgtk.cfg |-- adtxt.cfg |-- boot.cat |-- dtmenu.cfg |-- exithelp.cfg |-- f1.txt |-- f10.txt |-- f2.txt |-- f3.txt |-- f4.txt |-- f5.txt |-- f6.txt |-- f7.txt |-- f8.txt |-- f9.txt |-- gtk.cfg |-- isolinux.bin <-ISOLINUX 4.05 20121210 |-- isolinux.cfg |-- kde | |-- adgtk.cfg | |-- adgtkdt.cfg | |-- adtxt.cfg | |-- adtxtdt.cfg | |-- gtk.cfg | |-- gt...

...H ./ DEFAULT debian PROMPT 0 LABEL debian CONFIG ../../debian.cfg ../../ 3_ Rename 'target/syslinux.cfg' to 'target/debian.cfg' 4_ Edit content of 'target/debian.cfg' to (only) be: include menu.cfg default vesamenu.c32 prompt 0 timeout 0 5_ Edit content of 'target/exithelp.cfg' to (only) be: label menu kernel vesamenu.c32 config debian.cfg 6_ (Possibly you need some special/root rights/permissions for this step) Delete 'target/ldlinux.*' and 'target/*.c32'. 7_ From the 'bios' subdirectory for Syslinux files in your OS (package), c...

David Christensen wrote: > This is how I prepared an ADATA USB Flash Drive 4 GB: ... install-mbr /dev/sdb ... [Rest of very clear description snipped.] What's that? That desn't exist in the Debian I'm running. Otherwise you gave a very good description of what you're doing. >From another message: > Please provide a URL for documentation that explains how to build a >

...??? pxechn.c32 ? ??? reboot.c32 ? ??? rosh.c32 ? ??? sanboot.c32 ? ??? sdi.c32 ? ??? sysdump.c32 ? ??? syslinux.c32 ? ??? vesa.c32 ? ??? vesainfo.c32 ? ??? vesamenu.c32 ? ??? vpdtest.c32 ? ??? whichsys.c32 ? ??? zzjson.c32 ??? exithelp.cfg ??? f10.txt ??? f1.txt ??? f2.txt ??? f3.txt ??? f4.txt ??? f5.txt ??? f6.txt ??? f7.txt ??? f8.txt ??? f9.txt ??? g2ldr ??? g2ldr.mbr ??? gtk.cfg ??? initrdg.gz ??? initrd.gz ??? ldlinux.c32 ??? ldlinux.sys ??? libcom32.c32 ??? libutil.c32 ??? linux ??? menu.cfg ??? NvVars ??? prompt.cfg ??? r...

....c32 > ? ??? sanboot.c32 > ? ??? sdi.c32 > ? ??? sysdump.c32 > ? ??? syslinux.c32 > ? ??? vesa.c32 > ? ??? vesainfo.c32 > ? ??? vesamenu.c32 > ? ??? vpdtest.c32 > ? ??? whichsys.c32 > ? ??? zzjson.c32 > ??? exithelp.cfg > ??? f10.txt > ??? f1.txt > ??? f2.txt > ??? f3.txt > ??? f4.txt > ??? f5.txt > ??? f6.txt > ??? f7.txt > ??? f8.txt > ??? f9.txt > ??? g2ldr > ??? g2ldr.mbr > ??? gtk.cfg > ??? initrdg.gz > ??? initrd.gz > ??? ldlinux.c32 > ??? ldlinux.sys &g...

I want to eufi boot this image: http://cdn-fastly.deb.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz there is a bug against it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913523 I'd like to fix the resulting usb stick for my use, and also fix it in a way that can be used to fix the upstream bug. I'm trying to follow the guids

...??? sdi.c32 > > ? ??? sysdump.c32 > > ? ??? syslinux.c32 > > ? ??? vesa.c32 > > ? ??? vesainfo.c32 > > ? ??? vesamenu.c32 > > ? ??? vpdtest.c32 > > ? ??? whichsys.c32 > > ? ??? zzjson.c32 > > ??? exithelp.cfg > > ??? f10.txt > > ??? f1.txt > > ??? f2.txt > > ??? f3.txt > > ??? f4.txt > > ??? f5.txt > > ??? f6.txt > > ??? f7.txt > > ??? f8.txt > > ??? f9.txt > > ??? g2ldr > > ??? g2ldr.mbr > > ??? gtk.cfg > > ??? init...