Displaying 20 results from an estimated 200 matches similar to: "Thoughts: chaindev -> altchain"
2012 Mar 26
1
Request: merge chaindev
Hi,
Can chaindev of Michal Soltys, finally be merged?
http://www.syslinux.org/archives/2011-August/016777.html
- Gert
Michal Soltys message Mon Aug 1 16:38:16 PDT 2011:
http://www.syslinux.org/archives/2011-August/016777.html
-------------------------------------------------------------------------------------------------------------
On 11-08-01 20:07, H. Peter Anvin wrote:
> On
2010 Aug 28
0
Chain module - chaindev branch
git://git.hasevolq.net/syslinux.git
Split and expanded version of chain module is on the chaindev branch.
The module is fully documented in doc/chain.txt
I wasn't sure if to make one giant commit, or kept all the history as I
was going - so I chose the latter. Tag 'chaindev-review' marks the commit.
New feats since my last mail include options: mbrchs, hideall, bss, bs,
warn (see
2005 Feb 09
2
Startup Question
Guys, Im new to asterisk and voip but Im have a couple of questions
regarding the initial setup.
1. Im going to install an asterisk server at home, where I have 2 phone
lines, what kind of card do I need to get? I was thinking about 2 X100P
Cards, so 1 can have 2 FXO ports and regarding phones, what else do I need?
Ive seen the Grandstream HandyTone HT-286, I guess that servers as and FXS
devide
2020 Feb 13
2
[PATCH nbdkit 1/2] vddk: Delay loading VDDK until config_complete.
We were previously dlopen-ing it in the load() method. This is very
early and in particular means that the only possible way to configure
where we find the library is through environment variables and not
through config parameters. Also it's not necessary as we don't call
any functions from the library (such as VixDiskLib_InitEx) until
config_complete.
This change is neutral refactoring
2020 Feb 17
2
Re: [nbdkit PATCH v5 4/4] vddk: Drive library loading from libdir parameter.
Unfortunately this series doesn't work with the real VDDK library :-(
I see:
nbdkit: debug: vddk: config_complete
nbdkit: debug: dlopen shim prefix set to /home/rjones/tmp/vddk-6.7.3/vmware-vix-disklib-distrib/lib64
Then a little bit later during VDDK initialization it fails with:
nbdkit: debug: VixDiskLib: Could not load default plugins from
2020 Feb 13
4
[PATCH nbdkit v2 2/3] NOT WORKING: vddk: Drive library loading from libdir parameter.
I couldn't get this to work in the end. This is the latest
non-working version. This email documents what doesn't work for the
permanent record.
The central problem is that VDDK InitEx() appears to dlopen() various
of its own plugins. Although I wasn't able to capture exactly what
dlopen() command it is running, the plugins cannot be loaded because
they rely on the recompiled
2010 Oct 13
3
[syslinux:disklib] disklib: make CHS calculation match core/fs/diskio.c
On 10/13/2010 08:36 AM, syslinux-bot for Michal Soltys wrote:
> Commit-ID: 9c8db7560e2dc83d1191bb2f90b4d4d0ae3d37d6
> Gitweb: http://syslinux.zytor.com/commit/9c8db7560e2dc83d1191bb2f90b4d4d0ae3d37d6
> Author: Michal Soltys <soltys at ziu.info>
> AuthorDate: Wed, 13 Oct 2010 10:57:36 +0200
> Committer: Michal Soltys <soltys at ziu.info>
> CommitDate: Wed, 13
2017 Sep 06
1
BUILTIN\Administrators - failed to call wbcSidToUid: WBC_ERR_DOMAIN_NOT_FOUND
>On Wed, 06 Sep 2017 11:24:17 +0200>Jiří Černý via samba <samba at
lists.samba.org
( https://lists.samba.org/mailman/listinfo/samba) > wrote:>>> I feel
this all has something to do with the classicupgrade, the>> command
works for me, does 'wbinfo --sid-to-gid="S-1-5-32-544"'>> work ?>> Yes.
Take a look:wbinfo
2020 Feb 17
5
[nbdkit PATCH v5 0/4] vddk: Drive library loading from libdir parameter.
Differences from v4:
Patch 1 is simplified: I realized that since we already use -rdynamic
for nbdkit (after all, we WANT our dlopen()d plugins to be able to
call our nbdkit_* exports), it is only a matter of adding dlopen to
the set of symbols that we export. With that done, there is no
separate shared library needed; our dlopen shim is now part of nbdkit
proper, and we don't have to tweak
2020 Feb 13
1
[PATCH nbdkit] NOT WORKING vddk: Use dlmopen to isolate VDDK.
---
configure.ac | 5 +++++
plugins/vddk/vddk.c | 4 ++++
2 files changed, 9 insertions(+)
diff --git a/configure.ac b/configure.ac
index d71f06e4..57626a76 100644
--- a/configure.ac
+++ b/configure.ac
@@ -321,6 +321,11 @@ AC_SEARCH_LIBS([dlsym], [dl dld], [
])
LIBS="$old_LIBS"
+old_LIBS="$LIBS"
+LIBS="$LIBS -ldl"
+AC_CHECK_FUNCS([dlmopen])
2020 Feb 18
4
[nbdkit PATCH v7 0/2] vddk: Drive library loading from libdir parameter.
In v7:
everything should work now! The re-exec code is slightly simplified,
with Rich's suggestion to pass the original LD_LIBRARY_PATH rather
than just the prefix being added, and I've now finished wiring up the
initial dlopen() check into code that correctly computes the right
prefix dir to add to LD_LIBRARY_PATH.
Eric Blake (1):
vddk: Add re-exec with altered environment
Richard
2019 Apr 11
3
nbdkit, VDDK, extents, readahead, etc
As I've spent really too long today investigating this, I want to
document this in a public email, even though there's nothing really
that interesting here. One thing you find from search for VDD 6.7 /
VixDiskLib_QueryAllocatedBlocks issues with Google is that we must be
one of the very few users out there. And the other thing is that it's
quite broken.
All testing was done using
2019 Apr 12
2
Re: nbdkit, VDDK, extents, readahead, etc
On Fri, Apr 12, 2019 at 03:52:58PM +0200, Martin Kletzander wrote:
> On Thu, Apr 11, 2019 at 06:55:55PM +0100, Richard W.M. Jones wrote:
> >This seems to be a bug in VDDK, possibly connected with the fact that
> >we fork after initializing VDDK but before doing the
> >VixDiskLib_ConnectEx. I suspect it's something to do with the PID
> >changing.
> >
>
2019 Apr 05
2
[PATCH nbdkit] vddk: Add support for VIXDISKLIB_FLAG_OPEN_SINGLE_LINK
From: Martin Kletzander <mkletzan@redhat.com>
Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
---
plugins/vddk/nbdkit-vddk-plugin.pod | 7 ++++++-
plugins/vddk/vddk-structs.h | 1 +
plugins/vddk/vddk.c | 10 ++++++++++
3 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/plugins/vddk/nbdkit-vddk-plugin.pod
2010 Sep 21
1
[Pull request] disklib: fixes for write functions
Hello Erwan,
You will find below a pull request for the bug reported by Robert Jordan
in the disk library.
The first patch is the one he tested (see
http://syslinux.zytor.com/archives/2010-September/015341.html) and
the second one is a sanity check for the number of sectors written by call (
see http://syslinux.zytor.com/archives/2010-September/015342.html).
Thanks,
The following changes
2020 Feb 18
2
[nbdkit PATCH v6] vddk: Add re-exec with altered environment
In the next patch, we want to get rid of the requirement for the user
to supply LD_LIBRARY_PATH pointing to vddk libs, if we can derive it
ourselves from libdir. However, VDDK itself requires LD_LIBRARY_PATH
to be set (because it tries to load libraries that in turn depend on a
bare library name, which no manner of dlopen() hacking can work
around, and implementing la_objsearch() is no better for
2010 Sep 19
2
can't get write_sectors to work...
Hi,
Hopefully you someone can tell me what I'm doing wrong. First, the code. I
placed this at the bottom of the main loop in com32/modules/disk.c as a
simple test of writing to the disk:
printf(" Host bus: %s, Interface type: %s\n\n",
d->edd_params.host_bus_type, d->edd_params.interface_type);
zero_buf = calloc(1, d->edd_params.bytes_per_sector);
for(int
2009 May 05
7
HDT 0.3.3 is out
HDT 0.3.3 has just been released.
This release aims at solving some CLI bugs and adds a some new memory
mapping detection.
I'd like to thanks Dag Wieers for reporting many CLI bugs & pierre for
his work on the memory mapping.
Here come the changelog:
- A new memory mode
Memory items can be reached via the new "memory>" mode.
- Memory mapping display
Pierre did integrate
2009 May 05
7
HDT 0.3.3 is out
HDT 0.3.3 has just been released.
This release aims at solving some CLI bugs and adds a some new memory
mapping detection.
I'd like to thanks Dag Wieers for reporting many CLI bugs & pierre for
his work on the memory mapping.
Here come the changelog:
- A new memory mode
Memory items can be reached via the new "memory>" mode.
- Memory mapping display
Pierre did integrate
2019 Apr 15
1
Re: nbdkit, VDDK, extents, readahead, etc
On Mon, Apr 15, 2019 at 04:30:47PM +0200, Martin Kletzander wrote:
> On Fri, Apr 12, 2019 at 04:30:02PM +0100, Richard W.M. Jones wrote:
> > +-- nbdkit monitoring process
> > |
> > +-- first child = nbdkit
> > |
> > +-- second child = ‘--run’ command
> >
> >so when the second child exits, the monitoring process (which is doing
> >nothing