similar to: vesamenu back to text before booting

Displaying 20 results from an estimated 1000 matches similar to: "vesamenu back to text before booting"

2014 Dec 03
4
vesamenu back to text before booting
On Tue, 2 Dec 2014, H. Peter Anvin wrote: > This is the default unless the "quiet" option is set. Hmm. tglaser at luna:/srv/tftp $ fgrep -ri quiet . Binary file ./hdt.c32 matches Binary file ./ldlinux.c32 matches Binary file ./vmlinuz matches Binary file ./linux.c32 matches Binary file ./debian-installer/jessie/amd64/linux matches Binary file ./debian-installer/jessie/i386/linux
2014 Dec 02
0
vesamenu back to text before booting
On 12/02/2014 06:48 AM, Thorsten Glaser wrote: > Hi, > > I still have the question: when I have an environment that uses > vesamenu, for example on PXE, how do I configure it so that, for > some of the menu entries, it switches back to the text mode (03h) > before handing off to the next bootloader / kernel? > This is the default unless the "quiet" option is set.
2014 Dec 03
0
vesamenu back to text before booting
On Dec 3, 2014 3:54 AM, "Thorsten Glaser" <t.glaser at tarent.de> wrote: > > On Tue, 2 Dec 2014, H. Peter Anvin wrote: > > > This is the default unless the "quiet" option is set. > > Hmm. > It does not switch back to text mode when chaining to > https://www.mirbsd.org/MirOS/current/i386/boot renamed > to "pxebsd.0" (used to be
2014 Dec 05
2
vesamenu back to text before booting
On Fri, 5 Dec 2014, Ady wrote: > > > If so: http://www.syslinux.org/wiki/index.php/Mboot.c32 > > > > I?m not permitted to edit either that page or its talk page. > > Do I submit the content addition here, then? > > Please do. Okay, MediaWiki syntax docs follow. Note I have tested those only a bit, and not within the vesamenu context, but if mboot.c32 resets to
2014 Dec 05
8
vesamenu back to text before booting
On Fri, 5 Dec 2014, Gene Cumm wrote: > >> mostly in C and be BIOS-only) or making the MirOS kernel act like > >> either an MBOOT kernel or a Linux kernel (for their boot protocols), The MirBSD _bootloader_ (not kernel) can act as a Multiboot kernel. It can then use disc access (not PXE), or you can pass it the ?real? kernel, but also e.g. configuration files, as Multiboot
2014 Dec 03
0
vesamenu back to text before booting
Ah, depends on the image type. We spoke reset for an NBP though. On December 3, 2014 12:50:24 AM PST, Thorsten Glaser <t.glaser at tarent.de> wrote: >On Tue, 2 Dec 2014, H. Peter Anvin wrote: > >> This is the default unless the "quiet" option is set. > >Hmm. > >tglaser at luna:/srv/tftp $ fgrep -ri quiet . >Binary file ./hdt.c32 matches >Binary file
2014 Dec 04
2
vesamenu back to text before booting
On Thu, 4 Dec 2014, Gene Cumm wrote: > Ady has an excellent point. Try the following instead: > > LABEL test > MENU LABEL test > COM32 pxechn.c32 > APPEND pxebsd.0 Thanks, that works! How do I use that in the generic case? The ?pxebsd.0? file can be called as? ? PXE loader ? COMBOOT (16-bit) ? DOS .COM ? Multiboot (although it switches back to 16-bit mode
2014 Dec 04
0
vesamenu back to text before booting
On Thu, Dec 4, 2014 at 8:45 AM, Ady <ady-sf at hotmail.com> wrote: > >> On Thu, 4 Dec 2014, Ady wrote: >> >> > Perhaps there should be a new MENU-type directive, so to force the >> > screen to text mode (as opposed to leaving it in graphics mode for as >> > long as it can be)? Perhaps this could also be useful when exiting a >> > vesamenu to
2014 Dec 05
0
vesamenu back to text before booting
> On Fri, 5 Dec 2014, Gene Cumm wrote: > > > >> mostly in C and be BIOS-only) or making the MirOS kernel act like > > >> either an MBOOT kernel or a Linux kernel (for their boot protocols), > > The MirBSD _bootloader_ (not kernel) can act as a Multiboot kernel. > It can then use disc access (not PXE), or you can pass it the "real" > kernel, but
2015 Jan 21
2
PXE Error Reporting
On Wed, 21 Jan 2015, Andreas Gruenbacher wrote: > Not really. As a security requirement, if this even really is anyone's > security requirement, this is pointless -- the ErrCode is set to 0 ("Not Still, requirements like this d?o? exist in the real world, dismissing them is a, I quote, stupid idea. I?d suggest to please wake up. bye, //mirabilos (not speaking for his employer
2020 Jan 12
2
Why are the arguments supplied for the command run through ssh interpreted by shell before they are passed to the command on the server side?
On Sun, 12 Jan 2020, Yuri wrote: > This was English, not German, BTW. For some values of English, perhaps. > You would lose the ability to redirect I/O in an immediate way, but you would > always be able to run a shell command like "/bin/sh" "-c" "any-command | tee > cmd.log | process-further" which would regain the ability to do everything > that a
2020 Jan 12
2
Why are the arguments supplied for the command run through ssh interpreted by shell before they are passed to the command on the server side?
On Sun, 12 Jan 2020, Yuri wrote: > dedicated argument, for example -z. The specification can be like this: The wording could need some translation by a native speaker, but the idea of this feature request is certainly sound. Of course you?d lose the ability to run multiple commands, redirect I/O, etc. when using your proposed flag. bye, //mirabilos -- tarent solutions GmbH Rochusstra?e
2014 Dec 04
3
vesamenu back to text before booting
> On Thu, 4 Dec 2014, Ady wrote: > > > Perhaps there should be a new MENU-type directive, so to force the > > screen to text mode (as opposed to leaving it in graphics mode for as > > long as it can be)? Perhaps this could also be useful when exiting a > > vesamenu to Syslinux CLI? > > Yes, please. To make this dependent *only* on the configuration of >
2014 Dec 05
2
vesamenu back to text before booting
On Thu, 2014-12-04 at 21:26 -0500, Gene Cumm wrote: > > Thanks, that works! How do I use that in the generic case? > > The ?pxebsd.0? file can be called as? > > > > ? PXE loader > > ? COMBOOT (16-bit) > > ? DOS .COM > > ? Multiboot (although it switches back to 16-bit mode immediately) > > ? from its own bootsector, if installed on disc (blocklist)
2014 Dec 03
3
vesamenu back to text before booting
On Wed, 3 Dec 2014, H. Peter Anvin wrote: > Ah, depends on the image type. We spoke reset for an NBP though. ?! //mirabilos -- tarent solutions GmbH Rochusstra?e 2-4, D-53123 Bonn ? http://www.tarent.de/ Tel: +49 228 54881-393 ? Fax: +49 228 54881-235 HRB 5168 (AG Bonn) ? USt-ID (VAT): DE122264941 Gesch?ftsf?hrer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
2020 Aug 03
6
Deprecation of scp protocol and improving sftp client
I hear you - but it seems that the choice is between (a) limiting "scp" functionality to address the security vulnerability, and (b) killing "scp" altogether. I'd much prefer (a), even if it means I lose "scp remotehost:foo\* .". Especially, since (almost always) I have equal privileges on both local and remote hosts, so in that case I just originate that
2020 Aug 03
6
Deprecation of scp protocol and improving sftp client
I conjecture that only few of the existing use cases rely on remote expansion. In any case (no pun intended), IMHO it would be better to break a few of the current use cases but leave the majority functional - than kill scp for all. Regards, Uri > On Aug 3, 2020, at 02:50, Jakub Jelen <jjelen at redhat.com> wrote: > > ?On Sat, 2020-08-01 at 00:17 +0000, Blumenthal, Uri - 0553
2014 Dec 05
0
vesamenu back to text before booting
On Thu, Dec 4, 2014 at 11:40 PM, Jeffrey Hutzelman <jhutz at cmu.edu> wrote: > On Thu, 2014-12-04 at 21:26 -0500, Gene Cumm wrote: > >> > Thanks, that works! How do I use that in the generic case? >> > The ?pxebsd.0? file can be called as? >> > >> > ? PXE loader >> > ? COMBOOT (16-bit) >> > ? DOS .COM >> > ? Multiboot
2014 Dec 04
0
vesamenu back to text before booting
On Thu, 4 Dec 2014, Ady wrote: > Perhaps there should be a new MENU-type directive, so to force the > screen to text mode (as opposed to leaving it in graphics mode for as > long as it can be)? Perhaps this could also be useful when exiting a > vesamenu to Syslinux CLI? Yes, please. To make this dependent *only* on the configuration of the menu entry started is, IMHO, the only way
2014 Dec 05
0
vesamenu back to text before booting
> On Fri, 5 Dec 2014, Ady wrote: > > > > > If so: http://www.syslinux.org/wiki/index.php/Mboot.c32 > > > > > > I?m not permitted to edit either that page or its talk page. > > > Do I submit the content addition here, then? > > > > Please do. > > Okay, MediaWiki syntax docs follow. Note I have tested those > only a bit, and not