similar to: [Bug 3757] New: snappet

I hacked out a rough first implementation of parisc64 for klibc last month, and only just got around to testing it now. The good news, it compiled fine on the first shot. The bad news, it failed to link usr/klibc/libc.so, and I'm not clueful enough to know why. hppa64-linux-gnu-ld -Ttext 0x40001000 -o usr/klibc/libc.so --start-group [...] usr/klibc/socketcalls/recvmsg.o

--- src/kernel.ml | 2 ++ src/utils.ml | 2 ++ 2 files changed, 4 insertions(+) diff --git a/src/kernel.ml b/src/kernel.ml index 356ac4b..9b0e8a2 100644 --- a/src/kernel.ml +++ b/src/kernel.ml @@ -30,6 +30,8 @@ let patt_of_cpu host_cpu = | "ppc" | "powerpc" | "powerpc64" -> ["ppc"; "powerpc"; "powerpc64"] |

Hy you all, Short version: I think I have some code that could be interesting to make the R architecture evolve towards better thread support, easier memory management, better user interface programming (progress bar, logs), powerful debugging without recompiling (hach!) some years ago I start learning C with an ambitious project: write a C library for multivariate data analysis. On the route I

This was used only in the RPM package handler. --- src/utils.ml | 27 --------------------------- src/utils.mli | 3 --- 2 files changed, 30 deletions(-) diff --git a/src/utils.ml b/src/utils.ml index f85418f..b25df88 100644 --- a/src/utils.ml +++ b/src/utils.ml @@ -172,33 +172,6 @@ and split_version = function ) in first :: split_version rest -let compare_architecture a1 a2 = -

Hallo, We protect linux/apache server with mod_auth_ntlm_winbind.so to authenticate users with their domain accounts. The server is joined into windows domain (Windows 2003 Server). Apache/mod_auth_ntlm_winbind.so is configured for NTLM+SPNEGO authentication. So far users can login when providing valid credentials. Users login into their windows workstation (Windows XP SP2 IE/Firefox) with

Dear developers, Our server implements two SSH services on ports 22 & 8022, with different PAM settings. The daemon is built from source of OpenSSH portable releases. Following the instructions in the INSTALL file, we made a copy of "<prefix>/sbin/sshd" (for port 22) as "<prefix>/sbin/sshd2" (for port 8022), created a separate "sshd2_config" file,

On 07/29/2015 01:45 AM, Ron via Syslinux wrote: > > Take 2 at bouncing this to the rest of the original recipients through a > different MTA, since mail.zytor.com refused to accept it the first time. > > Please re-add Jason Gunthorpe <jgg at obsidianresearch.com> and > 793921 at bugs.debian.org to the CC for replies. > > > On Wed, Jul 29, 2015 at 05:34:00PM

Take 2 at bouncing this to the rest of the original recipients through a different MTA, since mail.zytor.com refused to accept it the first time. Please re-add Jason Gunthorpe <jgg at obsidianresearch.com> and 793921 at bugs.debian.org to the CC for replies. On Wed, Jul 29, 2015 at 05:34:00PM +0930, Ron wrote: > > Hi Jason, > > On Tue, Jul 28, 2015 at 03:45:30PM -0600, Jason

On 12/11/2024 12:39, anctop wrote: > It seems that release 9.9p1 does not use the binary filename as the > PAM service name, but sticks to "sshd" for all instances. man sshd_config: ???? PAMServiceName ???????????? Specifies the service name used for Pluggable Authentication Modules (PAM) authentication, authorisation and session controls when ???????????? UsePAM is

Hi, Many thanks for your prompt answer. We overlooked this new option because it was not available in the 9.3p1 config. On Tue, 12 Nov 2024 at 20:52, Brian Candler <b.candler at pobox.com> wrote: > > On 12/11/2024 12:39, anctop wrote: > > It seems that release 9.9p1 does not use the binary filename as the > PAM service name, but sticks to "sshd" for all

Good evening, Kenneth. Thank you to apply (and rewrite my naive code better) and to file the issue to http://llvm.org/bugs/show_bug.cgi?id=7304 I have checked r105528 at this morning. I think the pass must be still cleaned up and rewritten. There are my two proposals for enhancement. 1) To separate Specialization(and rewriting callsites) to other module. It would be better if new module were

I am getting an error message, which I do not know the source to. I have a matrix SAMPLES that has preexisting rownames that I would like to change. GENE_NAMES contains these rownames. > rownames(SAMPLES) = GENE_NAMES Error in "dimnames<-.data.frame"(`*tmp*`, value = list(list(V1 = c(3843, : invalid 'dimnames' given for data frame > dim(SAMPLES) [1] 12626

Dear R-Helpers, I have a data.frame (df) and the head of data.frame looks like ProbeUID ControlType ProbeName GeneName SystematicName 1665 1577 0 pSysX_50_22_1 pSysX_50 pSysX_50 5422 5147 0 pSysX_49_8_1 pSysX_49 pSysX_49 4042 3843 0 pSysX_51_18_1 pSysX_51 pSysX_51 3646 3466 0 sll1514_0_2 sll1514 sll1514

Applied, with minor changes: 1. deleted[std:distance(as, ai)] creates a map entry (with a null value if the operator[] is not the left-hand-side of an assignment statement) if one doesn't already exist. deleted->find returns deleted.end() if the entry doesn't exist and doesn't change the map. 2. Included a comment to make it easy to find the spot where the callsite is checked

> You could configure default scheme as CRYPT. It covers these all. Otherwise > you need to make sure passwords have {SCHEME} prefix when it differs from > default or oddities occur. --- Thank you for the tip with CRYPT. Is there any explanation for this behaviour though? Why are BCRYPT hashes accepted when default_pass_scheme is set to SHA512-CRYPT and not vice versa? Is this

Greetings, this is less of a bug report or a help request, but we would like to know if someone can explain the following: Environment: Centos 7 with Dovecot 2.3.4-2 default_pass_scheme = BLF-CRYPT password hash in database : BLF-CRYPT login = works default_pass_scheme = SHA512 or SHA256-CRYPT password hash in database : BLF-CRYPT login = also works default_pass_scheme = BLF-CRYPT password

OpenSSH 9.9 has just been released. It will be available from the mirrors listed at https://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol 2.0 implementation and includes sftp client and server support. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches, reported bugs, tested

OpenSSH 9.9 has just been released. It will be available from the mirrors listed at https://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol 2.0 implementation and includes sftp client and server support. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches, reported bugs, tested

OpenSSH 9.9 has just been released. It will be available from the mirrors listed at https://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol 2.0 implementation and includes sftp client and server support. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches, reported bugs, tested

OpenSSH 9.9 has just been released. It will be available from the mirrors listed at https://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol 2.0 implementation and includes sftp client and server support. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches, reported bugs, tested