search for: 3_

Hi all, One of my variables looks like this: .7_-.3_-.2_.9 And this is a character variable. I made this by combining four different number like .7, -.3, -.2, and .9 using paste function. Now, I want to go back to original format from this one combined character variable. For instance, I want to extract 3rd number, -.2, from this character. I know...

...they get an error that a file -- usually a shortcut to "3-1/2 Floppy (A)" -- can't be found. The transcript from the Samba log appears below: ================================================================ [2002/09/18 14:54:45, 10] smbd/mangle_hash.c:is_mangled(317) is_mangled: 3_ FLOPPY (A).LNK : False [2002/09/18 14:54:45, 5] smbd/filename.c:unix_convert(314) New file 3_ FLOPPY (A).LNK [2002/09/18 14:54:45, 8] lib/util.c:is_in_path(1143) is_in_path: .ntprofile/Application Data/Microsoft/Office/Recent/3_ FLOPPY (A).LNK [2002/09/18 14:54:45, 8] lib/util.c:is_in_path(1148...

...ing correct? Yes, at least that is how I understand the provided [quote/] > > 2_ Are there any cases in which the resulting behavior is different > > from using the IMPLICIT directive (with respective labels)? > > > > While using 'ALLOWOPTIONS 0'... > > 3_ Should typing-in a 'label' (instead of the whole equivalent > > command) be accepted too? Yes, chosing a 'label' should be possible. Changing the behaviour of the label not. > > 4_ If I type-in a 'label' in the CLI, should additional options be > > a...

...ding to the following (fallback) rules: 1_ Search for the relevant lib*.c32 file(s) in the Current Working Directory. 2_ Search for the relevant lib*.c32 file(s) in the directory where ldlinux.c32 is located. Then the lib*.c32 files are searched-for according to the PATH directive, as follows: 3_ Search for the relevant lib*.c32 file(s) in the paths indicated by the PATH directive, in the same order as they are stated. 4_ Each path used in each PATH directive is appended to the end of the list of the searched-for paths previously set. So, I have several questions. 1_ Am I understanding...

...executing a label, then the command is "not accepted" ("not allowed"). 1_ Is my understanding correct? 2_ Are there any cases in which the resulting behavior is different from using the IMPLICIT directive (with respective labels)? While using 'ALLOWOPTIONS 0'... 3_ Should typing-in a 'label' (instead of the whole equivalent command) be accepted too? 4_ If I type-in a 'label' in the CLI, should additional options be allowed? 5_ If I press Tab in [vesa]menu.c32 and delete part of the command, is the resulting command allowed? 6_ How...

...; > To be clear, I am not saying there is no bug - there might be. > I performed the following test with several versions of Syslinux: 1_ Execute: 'extlinux --once=non_default_label --install /mnt/sda1' ; 2_ In first reboot, the "non_default_label" should be executed; 3_ In second reboot, the default label should be executed. Results: _ 4.05 to 4.07: OK. _ 5.00-pre1 to 5.00-pre7: fail. _ 5.00-pre8: step #2 OK, step #3 buggy. _ 5.00-pre9 to 5.11-pre9: OK. _ 6.xx and 6.xx-pre*: fail. Considering that the branches were developed simultaneously, I am guessing that a...

...ow > causcious or spacesaving you want to be. > > It seems both Thomas and I think it should remain. > > > -- > MartinS Then I would suggest: 1_ revert the wrong commit; 2_ apply the first part of the "right" patch in one commit, as it corrects one known bug; 3_ apply the second part of the "right" patch in a separated commit, which can potentially deal with a different situation than the first part of the patch, and, if for some reason additional space is needed in the future, it could be considered on its own for future edition. Regards, Ad...

.../dira /cat.c32 /config.c32 /ldlinux.c32 /ldlinux.sys /libcom32.c32 /pwd.c32 /syslinux.cfg /dira/dira.cfg 2_ Content of /syslinux.cfg: DEFAULT pwd1 PROMPT 0 LABEL config1 COM32 config.c32 /dira/dira.cfg APPEND /dira/ LABEL pwd1 COM32 pwd.c32 LABEL config11 CONFIG /dira/dira.cfg APPEND /dira/ 3_ Content of /dira/dira.cfg DEFAULT pwd2 LABEL pwd2 COM32 /pwd.c32 LABEL config2 COM32 /config.c32 /syslinux.cfg APPEND / LABEL config21 CONFIG /syslinux.cfg APPEND / 3_ Boot and Run "config1" label. 4_ Run config2 label 5_ Press TAB. Since "config2" should have loaded sysli...

...: YOCTO/OE uses a customized Syslinux. > > 2_ It is still not clear (to me) when exactly the failure occurs. Does > it fail before the bootloader? Is the bootloader itself failing? Is the > _kernel_ not loading, after the bootloader step got already to the boot > prompt? > > 3_ Perhaps it would help if you would post your entire syslinux.cfg. > > 4_ Someone might be interested in knowing the exact complete command > line that you are using in qemu (so the situation could be replicated > by others, maybe). > > 5_ You could also test with a publicly-avai...

To the Syslinux mailing list administrator(s): There seem to be some issue when searching the Syslinux mailing list archives. To replicate (example): 1_ Open a Google web search page 2_ Search for "site:http://www.syslinux.org/archives/" 3_ Click "Search tools" 4_ Limit the search to "Past month". Result: no match! This has been happening for about 10 months or so. A few mailing list search repositories / engines had kept caching the Syslinux mailing list until a few months ago, even after Google stopped. I k...

...u would need to hack the source code (and most probably you would be on your own at that). 2_ Regarding the color of the boot command (starting from the boot menu), the same link you posted also mentions other elements, such as "menu color cmdmark" and "menu color cmdline". 3_ Unless you specifically want to use a Syslinux variant (e.g. ISOLINUX), I would suggest not investing "too much" time on configuring it. In the near future, most Linux distributions won't be using it. 4_ If you still want to invest time on it, please carefully read the available d...

...ges -> Lists of pages -> Pages linking to disambiguation pages ( Special:Disambiguations ) _ Special Pages -> Media reports and uploads -> File path ( Special:ListFiles ) _ Special Pages -> High use pages -> Most linked-to templates ( Special:MostLinkedTemplates ) 3_ Additionally, the current layout of the Special Pages wiki page seems to be one column of links (under each section / subtitle of the page). The layout for this page used to be a list of links (under each section) distributed in two columns (not one). This is not critical, but perhaps there are...

Thanks. I've looked through all the links, and it seems everything is fine wrt. to what was mentioned there (I've disabled 64 bits in mke2fs, but it didn't help). I'd be glad to provide more details, but the error message is the only info I've got by now. It seems nothing else can be got from syslinux shell without modifiying the code. I've tried to make it load the kernel

...try to run a R file directly from the DOS shell. My R file (test.R) is intended to create a basic graph and has a very simple code: x<-rep(1:10,1) y<-rep(1:10,1) plot(x,y) I am using the following command to call this file directly from the c:/ root: C:/>R CMD BATCH e:/Documents Seb/3_/test.R And here is the error message (Translated from french to english): 'R' is not recognized as an internal or external command, an executable script or a command file My OS is a french Windows XP sp2 and I am using R version 2.5.0. I wonder if the problem comes from an installation...

Conditions to trigger this bug(s): 1_ Boot with ISOLINUX (SYSLINUX seems fine). 2_ Do NOT use the UI directive. 3_ In between TEXT HELP - ENDTEXT directives, use more than one line of text. *** syslinux.cfg start *** DEFAULT vesamenu.c32 PROMPT 0 LABEL pwd1 COM32 pwd.c32 TEXT HELP one line of text two lines of text ENDTEXT *** syslinux.cfg end *** Result: the system ([vesa]menu) hangs. So for whichev...

Hi, > 1_ "create a new DOS partition table"; > 2_ create a new partition; > 3_ format it. This could be added to http://www.syslinux.org/wiki/index.php/SYSLINUX#Creating_a_Bootable_Disk statement: "In order to create a bootable disk using SYSLINUX, prepare a normal MS-DOS formatted disk." Like "If in doubt, make a backup of your disk content, crea...

...hen the first step is to press TAB, then all labels are displayed. But, if any other combination of keys is pressed before TAB, then only one line of labels is displayed. For example: 1_ boot with ISOLINUX 5.10 to the "boot:" prompt; 2_ press ctrl+v (or any letter and delete it back); 3_ now press TAB; and under these circumstances, only one line of labels is displayed. Note that in the above point #2, if a letter is typed in, it should be also deleted back from the boot prompt before pressing TAB; otherwise only the labels starting with that letter are displayed. The latter b...

...the reasoning here), but the ESP is still an image, just as the "emulation" methods use for BIOS. So, someone could assert the following reasoning steps: 1_ We can workaround the Sector Count limitation of 32MiB for no-emulation methods. 2_ The ESP is considered a no-emulation method. 3_ From the above assertions, we could conclude that the limitation of 32MiB is not really relevant for the ESP. This would mean that, in spite of the UEFI specs stating that the Sector Count "field" determines the size of the ESP on optical media, this initial limitation could be overru...

...ting hello.c32 from the prompt, part of the values are different each time. Please clarify if the new behavior is the new expected one, or find the reason to the changed behavior. Having an unexpected behavior in hello.c32 could potentially mean that "something" is not quite right. 3_ The initial boot prompt is shown at an inadequate line in the screen. For example, the first line of a DISPLAY file is not seen, because the prompt uses that same line. The prompt should appear AFTER the end of the DISPLAY file. 4_ When using cat.c32 to display the content of a file, if the...

I'm starting this thread to discuss what git repository should be designated as primary and which repositories should be designated as secondary. For years, git.kernel.org has been the primary repo, updated at least with every full and pre- release. git.zytor.com has been the secondary and development repo. Additionally, I've maintained my repos at github.com and git.zytor.com as