Displaying 20 results from an estimated 4000 matches similar to: "suggestions for global APPEND consistency"
2019 Apr 22
1
Bug/limitation: allowoptions (for label), implicit (for automated)
Hello,
At the boot prompt ALLOWOPTIONS 0 is only applied to implicit kernels and not to labels. For configuration which want to allow selection, but prevent customization of the kernel command line, this behaviour is bad.
Also the IMPLICIT 0 is applied to both the boot prompt and configuration setting (like DEFAULT); but one could argue that only the command supplied at the prompt make sense to
2014 Jun 26
2
ALLOWOPTIONS directive
I have some questions about "ALLOWOPTIONS 0".
[quote]
ALLOWOPTIONS flag_val
If flag_val is 0, the user is not allowed to specify any arguments on
the kernel command line. The only options recognized are those
specified in an APPEND) statement. The default is 1.
[/quote]
My understanding of the behavior of "ALLOWOPTIONS 0" is that unless I
type-in a command that is exactly
2014 Jul 13
1
ALLOWOPTIONS directive
My summary:
reviewing ALLOWOPTIONS found reasons
for further reviewing 'ALLOWOPTIONS'
Op 2014-07-12 om 04:35 schreef Ady:
>
> > I have some questions about "ALLOWOPTIONS 0".
> >
> > [quote]
> > ALLOWOPTIONS flag_val
> > If flag_val is 0, the user is not allowed to specify any arguments on
> > the kernel command line. The only
2014 Mar 23
2
global append changes since version 5
In Syslinux 5-6.02, the "global append" directive is being
(unintentionally) ignored in some cases.
Updating Syslinux from prior versions, when using a "global append"
directive, will cause unexpected results.
For example, take the following simple configuration file:
***
DEFAULT mykernel
APPEND root=/dev/sda2
***
Note that the 'append' line is a global
2017 Sep 24
3
Fallback to second menu entry, ONERROR looping forever
Hello
I want to fallback to a second boot entry, if the kernel is missing for
the first entry.
So I through I could use ONERROR, but syslinux just continue to try
starting the first entry.
Am I doing something wrong? or can't this be done with syslinux?
default menu.c32
prompt 0
MENU HIDDEN
MENU AUTOBOOT
TIMEOUT 2
ONERROR live-generic
label grub
??? menu label ^Grub
??? menu default
2014 Mar 23
0
global append changes since version 5
On Sun, Mar 23, 2014 at 7:17 AM, Ady <ady-sf at hotmail.com> wrote:
> 2_ In prior versions, a specific entry was executed as follows:
> <mykernel> <global_append> <myappend_options>
> corresponding to:
>
> ***
> # The following is the global append, not part of a label entry.
> APPEND <global_append>
>
> #The following is a sample
2023 Nov 20
2
Online Backup failed....
Full output:
root at iob-master:~# samba-tool domain backup online --server=dc01
--targetdir=/autofs/backup/linux/samba_dom/$(hostname -d) -U administrator
Password for [SAMBA\administrator]:
INFO 2023-11-20 15:30:05,639 pid:73781
/usr/lib/python3/dist-packages/samba/join.py #1614: workgroup is SAMBA
INFO 2023-11-20 15:30:05,640 pid:73781
/usr/lib/python3/dist-packages/samba/join.py #1617: realm
2007 Jan 16
1
ONERROR not triggered in PXELINUX 3.31 when ramdisk missing
Hello,
I tested some things, and found the following:
when the kernel image file is present, but the initrd image is not,
ONERROR is not called, and PXELINUX stays in the prompt forever ...
Other error scenarios tested okay, a down/unresponding TFTP server can
lead to 15-20 minutes delay until all tried filenames timeout out ...
Just to let you know :)
Andreas
--
"The problem is not
2012 May 04
3
[GIT PULL] elflink fixes
Peter,
Paulo reported some problems with his config files under ISOLINUX and
PXELINUX - basically TIMEOUT and TOTALTIMEOUT were broken. The patches
I've pushed to the elflink branch fix this and also fix parsing of the
ALLOWOPTIONS config directive.
The following changes since commit d5e02fb16a11bfdbce1e90a39e6cb5f2ad925389:
get_key: Valid key values are positive (2012-04-17 11:25:53
2014 Mar 19
2
Checking CRC (of bzImage) before loading
On 03/19/2014 01:30 PM, Gene Cumm wrote:
> On Wed, Mar 19, 2014 at 4:16 PM, Mau Z <zmau1962 at gmail.com> wrote:
>> Hi,
>>
>> I am wondering how to implement the following customer's requirement :
>> The system is a stand alone embedded system with no operator (with Linux).
>> There is one SSD for the system's usage (and that is where the system loads
2004 May 11
0
[LLVMdev] Problems accessing structs
Anders Alexandersson wrote:
> Hello!
>
> I get some odd behaviour using my structs:
>
> "myKernelMap" = type {int (sbyte*)*, int ()*}
> "Kernel" = type {"myKernelMap"*}
>
> The second member ( int()* ) is a pointer to the %getchar() function.
>
> I want to call getchar using this function:
>
> int
2004 May 11
2
[LLVMdev] Problems accessing structs
Hello!
I get some odd behaviour using my structs:
"myKernelMap" = type {int (sbyte*)*, int ()*}
"Kernel" = type {"myKernelMap"*}
The second member ( int()* ) is a pointer to the %getchar() function.
I want to call getchar using this function:
int "callmyKernelgetchar_kernel"("Kernel"* "myKernel")
{
"PTRMAP" =
2014 Jul 12
0
ALLOWOPTIONS directive
> I have some questions about "ALLOWOPTIONS 0".
>
> [quote]
> ALLOWOPTIONS flag_val
> If flag_val is 0, the user is not allowed to specify any arguments on
> the kernel command line. The only options recognized are those
> specified in an APPEND) statement. The default is 1.
> [/quote]
>
> My understanding of the behavior of "ALLOWOPTIONS 0"
2002 Oct 03
2
maximum number of characters in APPEND
There is a maximum of 255 characters of parameters you can pass to the
kernel.
At least that's what I recall, but I may be wrong.
-----Original Message-----
From: Roberto De Leo [mailto:deleo at unica.it]
Sent: Thursday, October 03, 2002 5:19 PM
To: syslinux at zytor.com
Subject: [syslinux] maximum number of characters in APPEND
Hi,
I wonder whether there is a maximum number of
2009 Jun 13
1
menu broken if default 'append' option specified
Hello.
This is my first post here. ;)
I noticed that if the default 'append' option is
specified in the config file, menu and vesamenu
wont boot the system. Instead of offering a menu,
the screen goes blank; after hitting any key on the
keyboard, empty menu frame gets displayed with no
boot entry list inside.
It gets fixed by removing default 'append' entry
(the one before any
2007 Apr 03
2
Some cryptic error in IE
Hello,
I am using Sarissa v 0.9.7.6 and prototype v 1.5. In ajax application,
I am retrieving xml string from a local servlet and displaying it using xslt
processing by sarissa. This works perfectly well in FF, however it gives
bunch of error in IE. I have posted same type of problem quite few days back
and I stopped using Sarissa. Now I need to use Sarissa so any help would be
highly
2023 Nov 20
1
Online Backup failed....
On Mon, 20 Nov 2023 15:34:19 +0100
Dirk Laurenz via samba <samba at lists.samba.org> wrote:
> Full output:
>
> root at iob-master:~# samba-tool domain backup online --server=dc01
> --targetdir=/autofs/backup/linux/samba_dom/$(hostname -d) -U
> administrator Password for [SAMBA\administrator]:
> INFO 2023-11-20 15:30:05,639 pid:73781
>
2005 Aug 14
1
"NOESCAPE 1" is easily escapable
(I apologise if this has already been reported - the archive isn't very
searchable.)
At present the NOESCAPE keyword seems rather useless, because a boot
prompt is offered whenever attempts to load a boot image is interrupted
using <Ctrl>C. Intuitively, I would expect "NOESCAPE 1" to lock this
down also, and that {sys,pxe,iso.ext}linux would simply fall through to
the
2004 May 03
0
[LLVMdev] Problems with getelementptr
On Mon, 3 May 2004, Anders Alexandersson wrote:
> Hello!
>
> I'm having trouble with pointer traversing. I have a design as follows:
> class -> map -> classFunctions
>
> Starting with a pointer to the class, I want to get a pointer to a
> classFunction via a pointer to the map.
Okay...
> I can't get that function pointer!
>
> How shall I think to get
2012 Nov 27
0
Syslinux-5.00-pre11
Hi guys,
Here's another 5.00 prerelease. This one includes fixes for most of the
bugs reported in the last round of feedback. The XFS filesystem code
from Paulo also got merged this time and there were a bunch of fixes
from a Coverity report.
This won't be the last prerelease, but we are nearing the end of the
5.00 release cycle, so please do test.
Shortlog append below.
---
Chen