similar to: Custom CentOS DVD, isolinux.bin, and isohybrid...

The Asterisk Development Team has announced the release of libpri 1.4.13. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri The release of libpri 1.4.13 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following are the issues resolved in this release: * --- Outgoing

I'm trying to get ChansSpy to work. It works, in the pass/fail sense, but it is difficult to understand the various speakers. I can hear users on our end just fine, but the other end sounds like their going through a vocoder, if I can understand them at all. Otherwise it is just garbled. We are using the following setup: all of our phones are SIP phones; for our outgoing calls we make use of a

I have an analog phone connected to a Sipura 2100 which in turn connecteds to * over a 100mbps LAN. When I do ChanSpy on a bridged call, it causes massive jitter. When I attempt ChanSpy with a Grandstream GXP-2000 the monitored call is clear. Has anyone had this happen? Any suggestions? ScriptHead

Thomas Schmitt wrote: > I still don't get the "backwards" aspect. (Probably not enough background > knowledge.) Sigh. inst x, y gas use x and possibly y, operates according to inst and puts the result in y. Intel lives with the misconception this should mean use y and possibly x, operate according to inst and put the result in x. If you come from gas background the first

hello a while ago i posted a question about my troubles remastering isolinux bootable cds. after that Steffen Winterfeldt helped me out a lot and now my problems are gone. i wrote a document about my experiences and i thought i'd share it with you: http://littlesvr.ca/isomaster/eltoritosuppl.php and since i'm in pimping mode, my interest in isolinux is purely because of iso master (

> Hi, > > Ady wrote: > > so, why the original isohybrid image from Debian and many other > > isohybrid images have mostly (but not all) "00s" in place of the "90s"? > > That's a fake Block0 of an Apple Partition Map. Part of mjg's layout. > Caused by isohybrid option --mac or xorrisofs option -isohybrid-apm-hfsplus. > > * Fedora

Thomas Schmitt wrote: > I ponder whether it would be possible to create a diagnostic MBR > which does not necessarily have to boot but rather tells what the > isohybrid MBR would perceive: Presence of partition table, > EBIOS or CBIOS, block address used with INT 13, content of the block > read by the first INT 13, ... ... > The diagnostic MBR should only use 432 bytes because at

Hi, MartinS wrote: > Sigh. Ok. I deserve that. I was stubbornly looking at the structure of the documentation rather than at the documented sequence of instruction parameters. I ponder whether it would be possible to create a diagnostic MBR which does not necessarily have to boot but rather tells what the isohybrid MBR would perceive: Presence of partition table, EBIOS or CBIOS, block

> Hi, > > Ady wrote: > > If a specific BIOS' CHS/LBA translations cannot cope with the above, it > > is no surprise that we get some mess, somewhere. > > Currently my suspicion is that the isohdpfx.S code simply mishandles > the two conversion factors which it correctly got from BIOS call > INT 13H AH 8. > > > > Boot System ID : First

Tried my first CentOS 6 install on a system currently running 5.6. My attempt was not an upgrade, but a full re-format. I have verified the checksums of the ISO and did the pre-install disk verify and everything checked out. However after the screen for setting up the bootloader I get the following error "Unable to read group information from repositories. This is a problem with the

Hi, Ady wrote: > We seem to be suggesting to just dd' the first 432 bytes of their USB > devices with Martin's isohybrid Yes. As long as it is not about the old Macs which the APM of Fedora and some Gentoo ISOs wants to make boot, and not about ISOs made with isohybrid options --partok -ctrlhd0 --forcehd0. > which would be the step-by-step instructions for users of other >

Hi, Ady wrote: > http://repo.or.cz/syslinux.git/tree/HEAD:/diag > "handoff.bin This does not look like it would tell much of the properties in question. Nevertheless its print functions might be of interest for an isohybrid diagnostic MBR. > and at least 2 geodsp*.{bin,img(gz)} I am now reading http://repo.or.cz/syslinux.git/blob/HEAD:/diag/geodsp/README These programs

Hi, Ady wrote: > In the last few years, ISOLINUX has received very low attention, both > upstream and downstream. Nevertheless the well established Linux distros use it for their ISOs. Most have adopted mjg's isohybrid --uefi layout. Only SuSE does it different. So for me with my xorriso hat on, ISOLINUX is as an important partner as is GRUB. > So I' am about to (attempt to)

Hello, I am an active member of the Vinux community and have taken on a project of remastering a Ubuntu installation Cd in order to make it accessable to a blind user. I am able to sound the system bell when the boot menu loads by adding a ^G to the label statement which works well to tell a blind user they are at the boot menu. My intent is to sound the bell at each menu item, but I'm unable

Hi, Gene Cumm wrote: > it seems the stack format got > set, changed, then mostly reverted back, with this code being the last > piece missing from 2009. The commit to isohdpfx.S of 2009-05-31 looks incomplete. The sequence of the stack pointers was swapped, but the sequence of stack pushes was not.

On 2 January 2018 at 17:08, Marc Haber <mh+openssh-unix-dev at zugschlus.de> wrote: > On Tue, Jan 02, 2018 at 04:03:34PM +1030, David Newall wrote: >> On 02/01/18 03:29, Michael Str?der wrote: >> > How high is the risk that this unmaintained device is added to >> > yet-another-bot-net in the Internet-of-shitty-devices or is used to >> > enter parts of your

> > I ponder whether it would be possible to create a diagnostic MBR > which does not necessarily have to boot but rather tells what the > isohybrid MBR would perceive: Presence of partition table, > EBIOS or CBIOS, block address used with INT 13, content of the block > read by the first INT 13, ... > > One could preserve the isohybrid MBR of an ISO and replace it by >

Good morning! We're experiencing rather very bad latency spikes on busy Linux systems, for example if one machine is the jumphost (ssh -J) for a few hundred connections, while at the same time handles CPU intensive tasks. Would RT/Linux SCHED_FIXED or SCHED_RR be of help in such a case, e.g. put all ssh processes into the SCHED_FIXED scheduling class, with a priority higher than the

Hi, Ady wrote: > If a specific BIOS' CHS/LBA translations cannot cope with the above, it > is no surprise that we get some mess, somewhere. Currently my suspicion is that the isohdpfx.S code simply mishandles the two conversion factors which it correctly got from BIOS call INT 13H AH 8. > Boot System ID : First : Last : Relative : Number of: > Flag

On Wed, Mar 22, 2017 at 03:18:44PM +0100, Thomas Schmitt via Syslinux wrote: > Hi, > > > In theory, the geometry assumed in the MBR should > > match the one assumed by the BIOS. > > To be exacting: The geometry assuming part of the MBR is the partition > table, not the executable MBR code. > > Of course it would be nice if C/H/S was not such a brain damaged