similar to: [PATCH] Fix compile-time warning

Hi, This patch includes port of NUT to LynxOS 4.0. The patch is against yesterday's svn tree. Here is a brief description of changes: drivers/powercom.c: Rename shutdown() to shutdown2(). shutdown() is already defined in LynxOS system header files. Please feel free to rename it more appropriately. (I didn't do it due to lack of imagination :-) ) include/proto.h: Added

Olli Savia wrote: > The attached patch is a port of the current CVS (2005-08-11) version > of OpenSSH portable to LynxOS. Could you consider adding it to the > future releases of OpenSSH? If the patch needs additional work, please > let me know. Looks mostly reasonable, some comments and questions below. > + AC_DEFINE(LYNXOS_BROKEN_SETVBUF, 1, [LynxOS has broken setvbuf()

Hi I'm trying to make my machine to boot over network with pxelinux. My machine has two network interfaces and I'd like to use pxelinux's IAPPEND option to pass network configuration to the kernel. Unfortunately, with IAPPEND option I can't pass default interface to the kernel and my boot fails. Could it possible to add a feature to pxelinux that can be used to add <device>

Hi, With reference to my previous mail: 1. I use openssh-2.9p2 on a LynxOS i386 system. The ssh and scp clients work fine. Even sftp from other Linux systems works. But, if I run the sftp client in LynxOS to localhost (LynxOS) or remote sshd in Linux, the authentication succeeds, prints sftp> prompt and then exits. I don't know why this happens. The problem is with the sftp client

Hi, I have ported the portable version of openssh (openssh-2.9p2) to LynxOS. I have had to install Perl5 and openssl-0.9.5a. Also since the regex library in LynxOS is not POSIX compliant I had to use PCRE. Then I configured openssh-2.9p2 with the library option -lbsd. One more problem was the macro "howmany(x,y)" is not defined in any of the /usr/include header files n LynxOS. So I

Hi, I work on openssh-2.9p2 installed on LynxOS i386 system. sshd, ssh, scp and sftp-server all work fine. The problem is sftp client, in interactive mode, exits after authentication printing the sftp prompt. sftp client works fine in non-interactive mode. i.e., lynxos>sftp hari at linuxsystem:test works fine But, lynxos>sftp hari at linuxsystem ... sftp> lynxos> Any help, as to why

When I attempted to build Samba (v2.0.7) on a LynxOS (v3.1) box I was told that configure could determine my operating system. LynxOS, for those that don't know, is a Unix-like RTOS. It comes with a binary version of Samba, but a) it's old and b) it's not built for encrypted passwords which means I can't access it from WinNT. Can anyone advise me on what it would take to build

Hi, I use openssh-2.9p2 on an i386 LynxOS system. Since LynxOS does not have support for /dev/[u]random, I installed openssh with prngd support. It so happened by accident on installation that prngd.conf got truncated to zero size. With prngd running as such, ssh-keygen just hangs. I notice similar case with sshd, ssh, ... as all these depend on prngd for random number. SMMEstack# /usr/sbin/sshd

I am trying to initiate an sftp session from a Linux (Redhat) to a LynxOs machine (where i have ported opnessh-2.9p1) and configured without PAM support (as I was not able to find PAM version for LynxOS operating system) I get the following error: $ sftp -P /home/telica -l telica -v ben select: Bad file descriptor read: Input/output error sftp> Can somebody help me asap on this?

Hello Thanks for your response. The platform is lynxos. However when I add --with-ldflags=-lcrypt I get the following error: WS5000# ./configure --with-ssl-dir=/usr/local --with-ldflags=-lcrypt checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for executable suffix...

Here's what I get: bash-2.02# sshd -ddd -p 1234 debug3: Seeding PRNG from /usr/local/libexec/ssh-rand-helper debug1: sshd version OpenSSH_3.5p1 debug1: private host key: #0 type 0 RSA1 debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key. debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key. debug1: read PEM

Hello I am attempting to build on a LynxOS platform and am using a old version of zlib and OpenSSL-0.9.6a. I get past the configure stage by ignoring the zlib version check. However, at make stage I run into the following undefineds. Any idea what may be causing this. I am using version 3.8p1 of OpenSSH. Thank you in advance for your response Amba (cd openbsd-compat && make)

Thanks to Olli, I can now talk to my PW9125 via SNMP: > upsc cscfups001@localhost ambient.temperature: 031.0 battery.charge: 090.0 battery.runtime: 2640.0 battery.voltage: 055.5 driver.name: snmp-ups driver.parameter.mibs: pw driver.parameter.port: cscfups001.cs.uwaterloo.ca driver.version: 2.1.0 driver.version.internal: 0.41 input.frequency: 060.0 input.voltage: 120.0 output.current: 020.0

Hi, I am running sshd (openssh-2.9p2) on a power-pc LynxOS box, and am connecting from a ssh client (openssh-2.9p2) on an x86 Linux box. This works fine for ssh protocol version 1, but am getting the below error for ssh v2: Disconnecting: Bad packet length -857542839. I am also attaching the complete debug traces from sshd & ssh below. I am not sure if this is an "endian" issue.

Hello, I tried to install Samba-2.0.8 and Samba 2.2.0 on our LynxOS System. uname -a: LynxOS imklynxa 3.0.1 110298-G i386 gcc --version: 2.7-97r1 First problem in both packets: There is no LynxOS Version 3.0.1 in config.guess. I added 3 lines and tried again. configure ended only with a WARNING about the Network interface. Second Problem I had with the make command. Second Problem at 2.0.8:

Hello I have ported OpenSSH 3.8p1 to a LynxOS platform. Recently I heard a report from the field that v2 is perceived to be significantly slower than v1. Is this a known issue? Are there any configuration parameters that can be modified to make v2 faster? Thanks in advance for your response Amba

Hi, 1. Does ssh, scp and sftp client programs work on LynxOS? I use openssh-2.9p2 on a LynxOS i386 system. The ssh and scp clients work fine. Even sftp from other Linux systems works. But, if I make sftp to the localhost (LynxOS), the authentication succeeds, prints sftp> prompt and then exits. I don't know why this happens. I have not set the euid of ssh program to root as it does not

EFI booting may hang indefinitely when no keyboard is present on a machine (or when UEFI has chosen to not init USB due to fast boot). Reproducible at least with "EFI v2.31 by American Megatrends" on an Asrock H81M-ITX board. Reason is the input draining loop near the end in efi/main.c; it calls ReadKeyStroke() as long as EFI_NOT_READY is not returned. On machines without keyboard,

Hi, I use openssh-2.9p2 on LynxOS i386 system. sshd runs on LynxOS and ssh client on Redhat 7.0 Linux system (openssh-2.9p2 ssh client). The ssh client hangs on exit 90% of times. I don't think this is the usual hang-on-exit bug, because, there are no background processes running, I suppose. I attach the server debug messages. $ssh -V hari at lynx (From Linux) ... Password: ... lynx>

[Steve Snyder <swsnyder@home.com>] > When I attempted to build Samba (v2.0.7) on a LynxOS (v3.1) box I was > told that configure could determine my operating system. > > LynxOS, for those that don't know, is a Unix-like RTOS. It comes > with a binary version of Samba, but a) it's old and b) it's not built > for encrypted passwords which means I can't