search for: _some

...l quoted (above) are the primary concerns. One possible solution to my issue would be something like this: /some text/ --> <font style="italic">some text</font> -s-o-m-e-t-e-x-t- --> <font style="struckout">some text</font> _some text_ --> <font style="underline">some text</font> *some text* --> <font style="bold">some text</font> I anticipate that there probably won't be much appetite for changing the markdown tool, so I intend to have a go at imp...

...keytab-lilo.pl /path/to/us.map.gz /path/to/dvorak.map.gz > /path/to/dvorak.ktl or: # keytab-lilo.pl /path/to/us.map /path/to/dvorak.map > /path/to/dvorak.ktl Then copy the resulting "dvorak.ktl" file to "/boot/syslinux/" (or to the relevant location for Syslinux). In _some cases_ you might also want to (as root): # chown root:root /boot/syslinux/dvorak.ktl where: _ *.{k,}map[.gz] are _*existing*_ [gzipped] keyboard map files; _ us.{k,}map[.gz] represents the default keyboard map used by the BIOS (not necessarily by your OS); _ the file names and paths of each one...

...ectly, it supports SATA already). I am going to guess that you also performed your tests with an updated mbr.bin. I am also going to guess that, during your tests, you (re)installed Syslinux manually (not with scripts). We should also discard the possibility of some other issue. For instance, if _some specific_ kernels are failing with other bootloaders after an update, then there is a chance that some update could be messing with Syslinux too, right? You seem to be suggesting that Syslinux is not really installed in EDD mode, or that the EDD mode is somehow failing (or buggy) when Syslinux...

...map.gz > > /path/to/dvorak.ktl > > or: > # keytab-lilo.pl /path/to/us.map /path/to/dvorak.map > > /path/to/dvorak.ktl > > Then copy the resulting "dvorak.ktl" file to "/boot/syslinux/" (or to > the relevant location for Syslinux). > > In _some cases_ you might also want to (as root): > > # chown root:root /boot/syslinux/dvorak.ktl > > where: > _ *.{k,}map[.gz] are _*existing*_ [gzipped] keyboard map files; > _ us.{k,}map[.gz] represents the default keyboard map used by the BIOS > (not necessarily by your OS); >...

On Sunday, December 27, 2015, 23:34:11, Ady via Syslinux wrote: > How this change would affect users with older versions of kbd / > loadkeys / or in older OSes? I mean, let's assume a user using a newer > version of Syslinux (containing this proposed change in its keytab-lilo > perl script) but with an older OS / older version of kbd / loadkeys / > map files. The changed

Hello, I've successfully installed Asterisk from last CVS and configured it for using with DLINK-DG104S as mgcp CPE and PGW2200 as external sip server. All are work fine at G711 codecs, but then I disable all codecs except g729 some calls failed (Not all calls. Some calls passed at g729 succesfully). All my devices configred to use only g729 and I don't see other codecs at mgcp or sip

On Feb 23, 2009, at 2:15 PM, Scott Michel wrote: > And the first thing the helper method would have to check is if this > SDNode is a BUILD_VECTOR node, right? Right. It's really not much different than what you have now, just moving the point where you check. In your code right now, when you want to call your isConstantSplat method, you first dyn_cast the node to a

....ktl >> >> or: >> # keytab-lilo.pl /path/to/us.map /path/to/dvorak.map > >> /path/to/dvorak.ktl >> >> Then copy the resulting "dvorak.ktl" file to "/boot/syslinux/" (or to >> the relevant location for Syslinux). >> >> In _some cases_ you might also want to (as root): >> >> # chown root:root /boot/syslinux/dvorak.ktl >> >> where: >> _ *.{k,}map[.gz] are _*existing*_ [gzipped] keyboard map files; >> _ us.{k,}map[.gz] represents the default keyboard map used by the BIOS >> (not nec...

Hi I keep trying syslinux on my testing machine with BIOS and btrfs on root partition. I use syslinux 6.03pre18, kernel 3.15.4. A number of btrfs related bugs has been fixed in syslinux 6.03 recently, but I still see one more. Syslinux stops booting my kernel from btrfs partition. The partition itself is fine - I can mount it from other kernel booted from USB. The partition superblock is fine,

Until Syslinux 3.86, isolinux.bin contained a checksum that was calculated by 'core/checksumiso.pl'. The checksum is related to the patching of the boot info table. During May 2009, a commit by Peter deleted the checksumiso.pl file. The commit is: core: LZO compress the PM part of the core repo.or.cz/syslinux.git/commit/0d82b71304d596d80f3c4520f9dcf90048ca50b7 And so, since

...n ISO image that was created without patching the boot info table would at least have a chance of successfully booting anyway, under certain (simplified) conditions. But then, by version 4.00 the checksumiso.pl file was gone (by means of the commit I posted in my prior email) and instead "_some kind of_ checksum" is introduced in isolinux.bin when building it from source. Apparently, one of the consequences seems to be that the default checksum included in isolinux.bin doesn't seem to help those users/programs that, for whichever reason (e.g. user lacking knowledge), do not...

On Mon, Feb 23, 2009 at 1:46 PM, Chris Lattner <clattner at apple.com> wrote: > > On Feb 23, 2009, at 1:20 PM, Scott Michel wrote: > > Chris: >> >> I did float this by the dev list first a couple of weeks ago, didn't >> receive any comments. >> > > Ok, I didn't see it, sorry about that. It happens. :-) > a) Convenience for the

Hi Stefanos, Attached the testcase. I tried to reduce it further, but the problem goes away when I remove the instructions further. There is a nested loop and the fault occurs while processing the inner loop (for.body) To reproduce the crash: opt -O3 testcase.ll -o out.ll > `groupChecks()` will only try to group pointers that are on the same alias set. If that’s true, the RT check