From owner-freebsd-emulation Sun Oct 4 12:05:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12186 for freebsd-emulation-outgoing; Sun, 4 Oct 1998 12:05:21 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12164 for ; Sun, 4 Oct 1998 12:05:01 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id RAA10040; Sun, 4 Oct 1998 17:04:16 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199810041904.RAA10040@roma.coe.ufrj.br> Subject: Re: APC PowerChute under FreeBSD In-Reply-To: from John Fieber at "Oct 3, 98 06:14:37 pm" To: jfieber@indiana.edu (John Fieber) Date: Sun, 4 Oct 1998 17:04:16 -0200 (EDT) Cc: jonny@jonny.eng.br, mike@smith.net.au, emulation@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org #define quoting(John Fieber) // On Sat, 3 Oct 1998, Mike Smith wrote: // // > > Has anybody suceeded in running APC's PowerChute for SCO under // > > FreeBSD -stable ? // > // > I don't believe so. // // You might also search the BUGTRAQ archives for references to // PowerChute before even bothering with the software. There is a Thanks for the reference. It was very useful. But since I do not intend to use network control (yet), this wil not affect me. // upsd daemon in the ports collection that is pretty quirky, but // does work with SmartUPS and SmartUPS v/s models. I've seen it, but it appears to support only 220v models and has a very poor documentation. I've once made my own upsd daemon, for BackUPS, but now I need something a bit more powerful. PowerChute could be the answer. I have been using the netware version of it for 5 years, at least. I've also tried the Linux apcupsd (binary only), but it also seems to have an ioctl emulation incompatibility. And I thought serial ports were the most portable device between unixen, after /dev/null. :) BTW: Is there some way to request a signal from the serial port when some line or modem control bit changes ? The serial chip generates interrupts for then, but I ould not find an Unix signal equivalent. :( Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Oct 4 12:22:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14122 for freebsd-emulation-outgoing; Sun, 4 Oct 1998 12:22:21 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14101 for ; Sun, 4 Oct 1998 12:22:07 -0700 (PDT) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with SMTP id OAA01101; Sun, 4 Oct 1998 14:21:40 -0500 (EST) Date: Sun, 4 Oct 1998 14:21:39 -0500 (EST) From: John Fieber To: Joao Carlos Mendes Luis cc: emulation@FreeBSD.ORG Subject: Re: APC PowerChute under FreeBSD In-Reply-To: <199810041904.RAA10040@roma.coe.ufrj.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 4 Oct 1998, Joao Carlos Mendes Luis wrote: > I've seen it, but it appears to support only 220v models and > has a very poor documentation. What documentation? :) Actually, adding support for new models is pretty trivial. However, I'm not using it at all for the moment because it had some problems with FreeBSD 3.0-BETA that I haven't even begun to investigate. I'd actually like to find something else because on the surface the upsd config file looks relatively simple and flexible but in practice it is incomprehensible and I've failed to get it to do anything beyond the simplest of shutdown procedures. > I've also tried the Linux apcupsd (binary only), but it also seems > to have an ioctl emulation incompatibility. And I thought serial ports > were the most portable device between unixen, after /dev/null. :) Since I've just been working in the guts of the emulator to get Sybase running...what is the ioctl in question? -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Oct 4 12:37:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15339 for freebsd-emulation-outgoing; Sun, 4 Oct 1998 12:37:15 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15327 for ; Sun, 4 Oct 1998 12:37:05 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id RAA10583; Sun, 4 Oct 1998 17:36:39 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199810041936.RAA10583@roma.coe.ufrj.br> Subject: Re: APC PowerChute under FreeBSD In-Reply-To: from John Fieber at "Oct 4, 98 02:21:39 pm" To: jfieber@indiana.edu (John Fieber) Date: Sun, 4 Oct 1998 17:36:39 -0200 (EDT) Cc: jonny@jonny.eng.br, emulation@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org #define quoting(John Fieber) // > I've seen it, but it appears to support only 220v models and // > has a very poor documentation. // // What documentation? :) That one. :) // Actually, adding support for new models is pretty trivial. If you have the documentation for both hardware and software. // > I've also tried the Linux apcupsd (binary only), but it also seems // > to have an ioctl emulation incompatibility. And I thought serial ports // > were the most portable device between unixen, after /dev/null. :) // // Since I've just been working in the guts of the emulator to get // Sybase running...what is the ioctl in question? There are at least 4 Unknown errors in the linux_kdump below. The program writes a probe string to the UPS, and waits for an answer that never comes back. The cable is working, I have tested it with apcmon and upsd. roma::root [767] ktrace ./apcupsd-libc5 ./apcupsd-libc5: PANIC! Cannot talk to UPS roma::root [768] linux_kdump: ... 10485 apcupsd-libc5 CALL linux_open(0x80556b8,0x502,0) 10485 apcupsd-libc5 NAMI "/compat/linux/dev/ups" 10485 apcupsd-libc5 NAMI "/dev/ups" 10485 apcupsd-libc5 RET linux_open 3 10485 apcupsd-libc5 CALL linux_open(0x805ac18,0xc2,0x1a4) ... 10485 apcupsd-libc5 CALL linux_ioctl(0x3,0x5401 ,0x805aba0) 10485 apcupsd-libc5 RET linux_ioctl 0 10485 apcupsd-libc5 CALL linux_sigaction(0x1,0xefbfd500,0xefbfd4f0) 10485 apcupsd-libc5 RET linux_sigaction 0 10485 apcupsd-libc5 CALL linux_sigaction(0x2,0xefbfd4f8,0xefbfd4e8) 10485 apcupsd-libc5 RET linux_sigaction 0 10485 apcupsd-libc5 CALL linux_sigaction(0xf,0xefbfd4f0,0xefbfd4e0) 10485 apcupsd-libc5 RET linux_sigaction 0 10485 apcupsd-libc5 CALL linux_ioctl(0x3,0x540b ,0) >> Probably this is the guilty one. 10485 apcupsd-libc5 RET linux_ioctl -1 errno -14 Unknown error: -14 10485 apcupsd-libc5 CALL linux_ioctl(0x3,SNDCTL_TMR_START,0x805a9c0) 10485 apcupsd-libc5 RET linux_ioctl 0 10485 apcupsd-libc5 CALL write(0x3,0xefbfd533,0x1) 10485 apcupsd-libc5 GIO fd 3 wrote 1 byte "Y" 10485 apcupsd-libc5 RET write 1 10485 apcupsd-libc5 CALL linux_sigprocmask(0,0xefbfd4ec,0xefbfd4e8) 10485 apcupsd-libc5 RET linux_sigprocmask 0 10485 apcupsd-libc5 CALL linux_sigaction(0xe,0xefbfd500,0xefbfd4f0) 10485 apcupsd-libc5 RET linux_sigaction 0 10485 apcupsd-libc5 CALL linux_time(0) 10485 apcupsd-libc5 RET linux_time 907529171/0x3617cbd3 10485 apcupsd-libc5 CALL linux_alarm(0x1) 10485 apcupsd-libc5 RET linux_alarm 0 10485 apcupsd-libc5 CALL linux_sigsuspend(0,0,0) 10485 apcupsd-libc5 PSIG SIGALRM caught handler=0x280c3cb0 mask=0x2000 code=0x 0 10485 apcupsd-libc5 RET linux_sigsuspend -1 errno -4 Unknown error: -4 10485 apcupsd-libc5 CALL linux_sigreturn(0xefbfd454) 10485 apcupsd-libc5 RET linux_sigreturn JUSTRETURN 10485 apcupsd-libc5 CALL linux_time(0) 10485 apcupsd-libc5 RET linux_time 907529172/0x3617cbd4 10485 apcupsd-libc5 CALL linux_sigaction(0xe,0xefbfd4f0,0) 10485 apcupsd-libc5 RET linux_sigaction 0 10485 apcupsd-libc5 CALL linux_alarm(0) 10485 apcupsd-libc5 RET linux_alarm 0 10485 apcupsd-libc5 CALL linux_sigprocmask(0x2,0xefbfd4e8,0) 10485 apcupsd-libc5 RET linux_sigprocmask 0 10485 apcupsd-libc5 CALL linux_ioctl(0x3,0x540b ,0x2) 10485 apcupsd-libc5 RET linux_ioctl -1 errno -14 Unknown error: -14 10485 apcupsd-libc5 CALL write(0x3,0xefbfd533,0x1) 10485 apcupsd-libc5 GIO fd 3 wrote 1 byte "Y" 10485 apcupsd-libc5 RET write 1 10485 apcupsd-libc5 CALL linux_sigaction(0xe,0xefbfd4e8,0xefbfd4d8) 10485 apcupsd-libc5 RET linux_sigaction 0 10485 apcupsd-libc5 CALL linux_alarm(0x3) 10485 apcupsd-libc5 RET linux_alarm 0 10485 apcupsd-libc5 CALL read(0x3,0xefbfd513,0x1) 10485 apcupsd-libc5 PSIG SIGALRM caught handler=0x8051980 mask=0x0 code=0x0 10485 apcupsd-libc5 RET read -1 errno -4 Unknown error: -4 10485 apcupsd-libc5 CALL linux_sigreturn(0xefbfd490) 10485 apcupsd-libc5 RET linux_sigreturn JUSTRETURN 10485 apcupsd-libc5 CALL linux_alarm(0) 10485 apcupsd-libc5 RET linux_alarm 0 10485 apcupsd-libc5 CALL linux_sigaction(0xe,0xefbfd4e4,0xefbfd4d4) 10485 apcupsd-libc5 RET linux_sigaction 0 10485 apcupsd-libc5 CALL write(0x2,0xefbfcb40,0x2c) 10485 apcupsd-libc5 GIO fd 2 wrote 44 bytes "./apcupsd-libc5: PANIC! Cannot talk to UPS \a" 10485 apcupsd-libc5 RET write 44/0x2c ... I've also tested it with kermit. Sending a single 'Y' char gives me a 'SM' back, instantly. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Sun Oct 4 14:13:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28973 for freebsd-emulation-outgoing; Sun, 4 Oct 1998 14:13:06 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from dingo.cdrom.com (castles320.castles.com [208.214.167.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28952 for ; Sun, 4 Oct 1998 14:12:47 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA06715; Sun, 4 Oct 1998 14:17:23 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810042117.OAA06715@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joao Carlos Mendes Luis cc: jfieber@indiana.edu (John Fieber), emulation@FreeBSD.ORG Subject: Re: APC PowerChute under FreeBSD In-reply-to: Your message of "Sun, 04 Oct 1998 17:36:39 -0200." <199810041936.RAA10583@roma.coe.ufrj.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Oct 1998 14:17:23 -0700 From: Mike Smith Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > // Since I've just been working in the guts of the emulator to get > // Sybase running...what is the ioctl in question? > > There are at least 4 Unknown errors in the linux_kdump below. The > program writes a probe string to the UPS, and waits for an answer that > never comes back. The cable is working, I have tested it with apcmon > and upsd. Linux negates its error returns (for what reason I can't imagine). I didn't change linux_kdump to translate these (I guess I was lazy). > roma::root [767] ktrace ./apcupsd-libc5 > ./apcupsd-libc5: PANIC! Cannot talk to UPS > roma::root [768] > > linux_kdump: > > ... > 10485 apcupsd-libc5 CALL linux_open(0x80556b8,0x502,0) > 10485 apcupsd-libc5 NAMI "/compat/linux/dev/ups" > 10485 apcupsd-libc5 NAMI "/dev/ups" > 10485 apcupsd-libc5 RET linux_open 3 > 10485 apcupsd-libc5 CALL linux_open(0x805ac18,0xc2,0x1a4) > ... > 10485 apcupsd-libc5 CALL linux_ioctl(0x3,0x5401 ,0x805aba0) > 10485 apcupsd-libc5 RET linux_ioctl 0 > 10485 apcupsd-libc5 CALL linux_sigaction(0x1,0xefbfd500,0xefbfd4f0) > 10485 apcupsd-libc5 RET linux_sigaction 0 > 10485 apcupsd-libc5 CALL linux_sigaction(0x2,0xefbfd4f8,0xefbfd4e8) > 10485 apcupsd-libc5 RET linux_sigaction 0 > 10485 apcupsd-libc5 CALL linux_sigaction(0xf,0xefbfd4f0,0xefbfd4e0) > 10485 apcupsd-libc5 RET linux_sigaction 0 > 10485 apcupsd-libc5 CALL linux_ioctl(0x3,0x540b ,0) > >> Probably this is the guilty one. > 10485 apcupsd-libc5 RET linux_ioctl -1 errno -14 Unknown error: -14 That's bad, but probably not fatal. 14 is EFAULT; this looks like it's attempting to flush the serial interface, but 0 is definitely an invalid argument from our point of view. > 10485 apcupsd-libc5 CALL linux_ioctl(0x3,SNDCTL_TMR_START,0x805a9c0) > 10485 apcupsd-libc5 RET linux_ioctl 0 I don't quite understand the sound ioctl here. > 10485 apcupsd-libc5 CALL write(0x3,0xefbfd533,0x1) > 10485 apcupsd-libc5 GIO fd 3 wrote 1 byte > "Y" > 10485 apcupsd-libc5 RET write 1 > 10485 apcupsd-libc5 CALL linux_sigprocmask(0,0xefbfd4ec,0xefbfd4e8) > 10485 apcupsd-libc5 RET linux_sigprocmask 0 > 10485 apcupsd-libc5 CALL linux_sigaction(0xe,0xefbfd500,0xefbfd4f0) > 10485 apcupsd-libc5 RET linux_sigaction 0 > 10485 apcupsd-libc5 CALL linux_time(0) > 10485 apcupsd-libc5 RET linux_time 907529171/0x3617cbd3 > 10485 apcupsd-libc5 CALL linux_alarm(0x1) > 10485 apcupsd-libc5 RET linux_alarm 0 > 10485 apcupsd-libc5 CALL linux_sigsuspend(0,0,0) > 10485 apcupsd-libc5 PSIG SIGALRM caught handler=0x280c3cb0 > mask=0x2000 code=0x > 0 > 10485 apcupsd-libc5 RET linux_sigsuspend -1 errno -4 Unknown error: > -4 > 10485 apcupsd-libc5 CALL linux_sigreturn(0xefbfd454) > 10485 apcupsd-libc5 RET linux_sigreturn JUSTRETURN > 10485 apcupsd-libc5 CALL linux_time(0) > 10485 apcupsd-libc5 RET linux_time 907529172/0x3617cbd4 > 10485 apcupsd-libc5 CALL linux_sigaction(0xe,0xefbfd4f0,0) > 10485 apcupsd-libc5 RET linux_sigaction 0 > 10485 apcupsd-libc5 CALL linux_alarm(0) > 10485 apcupsd-libc5 RET linux_alarm 0 > 10485 apcupsd-libc5 CALL linux_sigprocmask(0x2,0xefbfd4e8,0) > 10485 apcupsd-libc5 RET linux_sigprocmask 0 > 10485 apcupsd-libc5 CALL linux_ioctl(0x3,0x540b ,0x2) > 10485 apcupsd-libc5 RET linux_ioctl -1 errno -14 Unknown error: -14 > 10485 apcupsd-libc5 CALL write(0x3,0xefbfd533,0x1) > 10485 apcupsd-libc5 GIO fd 3 wrote 1 byte > "Y" > 10485 apcupsd-libc5 RET write 1 > 10485 apcupsd-libc5 CALL linux_sigaction(0xe,0xefbfd4e8,0xefbfd4d8) > 10485 apcupsd-libc5 RET linux_sigaction 0 > 10485 apcupsd-libc5 CALL linux_alarm(0x3) > 10485 apcupsd-libc5 RET linux_alarm 0 > 10485 apcupsd-libc5 CALL read(0x3,0xefbfd513,0x1) > 10485 apcupsd-libc5 PSIG SIGALRM caught handler=0x8051980 mask=0x0 > code=0x0 > 10485 apcupsd-libc5 RET read -1 errno -4 Unknown error: -4 > 10485 apcupsd-libc5 CALL linux_sigreturn(0xefbfd490) > 10485 apcupsd-libc5 RET linux_sigreturn JUSTRETURN > 10485 apcupsd-libc5 CALL linux_alarm(0) > 10485 apcupsd-libc5 RET linux_alarm 0 > 10485 apcupsd-libc5 CALL linux_sigaction(0xe,0xefbfd4e4,0xefbfd4d4) > 10485 apcupsd-libc5 RET linux_sigaction 0 > 10485 apcupsd-libc5 CALL write(0x2,0xefbfcb40,0x2c) > 10485 apcupsd-libc5 GIO fd 2 wrote 44 bytes > "./apcupsd-libc5: PANIC! Cannot talk to UPS > \a" > 10485 apcupsd-libc5 RET write 44/0x2c > ... > > I've also tested it with kermit. Sending a single 'Y' char gives me a > 'SM' back, instantly. Looks like there might be a problem with setting the right modes on the serial interface. You should look for ioctls setting CBREAK or RAW mode, as I suspect this might be being lost. You could also loop the serial interface back to another port, and use kermit to pretend to be the UPS. If you see the Y, and say "SM" and it works, you will know that it's a raw/cookedness problem. At any rate, it would be good to know why the Linux TCFLSH ioctl is being called with a NULL argument - perhaps this has some special significance under Linux? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Tue Oct 6 13:56:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17081 for freebsd-emulation-outgoing; Tue, 6 Oct 1998 13:56:28 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16977 for ; Tue, 6 Oct 1998 13:56:03 -0700 (PDT) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id PAA07679; Tue, 6 Oct 1998 15:55:26 -0500 (EST) Date: Tue, 6 Oct 1998 15:55:26 -0500 (EST) From: John Fieber To: Joao Carlos Mendes Luis cc: emulation@FreeBSD.ORG Subject: Re: APC PowerChute under FreeBSD In-Reply-To: <199810041936.RAA10583@roma.coe.ufrj.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 4 Oct 1998, Joao Carlos Mendes Luis wrote: > #define quoting(John Fieber) > // > I've seen it, but it appears to support only 220v models and > // > has a very poor documentation. > // > // What documentation? :) > > That one. :) > > // Actually, adding support for new models is pretty trivial. > > If you have the documentation for both hardware and software. If you have a smartups, it is just cut and paste in the apc* source files. Each "supported" model has a datastructure of various parameters...why these are hardwired in and not runtime determined is beyond me...but just cut and paste to make a new one and change the name. I was able to add a SmartUPS v/s without any documentation which is a lot more difficult that adding a different size of the SmartUPS. However, I'd still rather find some different software. The upsd is just too wierd. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Oct 7 10:34:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05242 for freebsd-emulation-outgoing; Wed, 7 Oct 1998 10:34:27 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05231 for ; Wed, 7 Oct 1998 10:34:25 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA01163; Wed, 7 Oct 1998 10:39:06 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810071739.KAA01163@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: paulk@hitti.com cc: emulation@FreeBSD.ORG Subject: Re: Oracle 8 In-reply-to: Your message of "Wed, 07 Oct 1998 17:32:24 +0800." <48256696.00345A3C.00@mi.hitti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Oct 1998 10:39:06 -0700 From: Mike Smith Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Please don't post emulation-related questions to -hackers, and please search the archives before asking questions. The correct list for this question is 'emulation@freebsd.org' > Can Oracle 8 for Linux work on FreeBSD? Not yet; we don't expect to have it working until after 3.0 is released. Sybase's Linux product is mostly working, however, and we do expect it to be functional under 3.0. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Oct 7 16:29:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21753 for freebsd-emulation-outgoing; Wed, 7 Oct 1998 16:29:34 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21747; Wed, 7 Oct 1998 16:29:31 -0700 (PDT) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id SAA14644; Wed, 7 Oct 1998 18:29:26 -0500 (EST) Date: Wed, 7 Oct 1998 18:29:25 -0500 (EST) From: John Fieber To: Alex Nash cc: msmith@FreeBSD.ORG, emulation@FreeBSD.ORG, databases@FreeBSD.ORG Subject: Sybase/uname: mystery resolved Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Our linux uname(2) emulation is just dandy fine. There is a bug in the Sybase client library. It uses uname(2) to get the local host name which it sends along to the server. It turns out that it doesn't matter at all what uname(2) returns for a hostname as long as it is less than 30 bytes in length. Sounds like a buffer overflow if you ask me. Other than this, sybase is working fine. (Note: I have not yet tried it on a raw partition--I'll have to cannibalize a swap partition to test that--and a few other more exotic things.) Also, a big thanks to Alex Nash for providing a Linux box for debugging and comparison purposes. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Wed Oct 7 22:47:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24588 for freebsd-emulation-outgoing; Wed, 7 Oct 1998 22:47:01 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from dingo.cdrom.com (castles134.castles.com [208.214.165.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24579; Wed, 7 Oct 1998 22:46:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA01336; Wed, 7 Oct 1998 22:51:45 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810080551.WAA01336@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Fieber cc: Alex Nash , msmith@FreeBSD.ORG, emulation@FreeBSD.ORG, databases@FreeBSD.ORG Subject: Re: Sybase/uname: mystery resolved In-reply-to: Your message of "Wed, 07 Oct 1998 18:29:25 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Oct 1998 22:51:44 -0700 From: Mike Smith Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Our linux uname(2) emulation is just dandy fine. There is a bug > in the Sybase client library. It uses uname(2) to get the local > host name which it sends along to the server. Funky stuff! > Other than this, sybase is working fine. Great. Can we expect a port from you shortly that knows how to unpack/ brand/install/whatever it? Or should we just point people at the instructions that come with it? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Oct 8 07:07:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02354 for freebsd-emulation-outgoing; Thu, 8 Oct 1998 07:07:17 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02332; Thu, 8 Oct 1998 07:07:12 -0700 (PDT) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id JAA06166; Thu, 8 Oct 1998 09:06:48 -0500 (EST) Date: Thu, 8 Oct 1998 09:06:48 -0500 (EST) From: John Fieber To: Mike Smith cc: Alex Nash , emulation@FreeBSD.ORG, database@FreeBSD.ORG Subject: Re: Sybase/uname: mystery resolved In-Reply-To: <199810080551.WAA01336@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 7 Oct 1998, Mike Smith wrote: > > Other than this, sybase is working fine. > > Great. Can we expect a port from you shortly that knows how to unpack/ > brand/install/whatever it? Or should we just point people at the > instructions that come with it? A port would be relatively simple to make (and I'll probably do one in time), but given the current state of the license I'm not sure it would be good form to have it officially in the ports collection. Basically... The linux_lib-2.4 port won't cut it, you need a ld-linux.so.2 and a newer libc (at least, I have not nailed down exactly what is needed). As root you unpack the distribution using rpm2cpio. It expects to be in /opt/sybase and opt/sybase is in the filnames in the rpm file. Create a sybase user (home directory /opt/sybase) and group. As root, run the /opt/sybase/install/setperm_all, this fixes all the file ownership an permissions in the sybase tree. Log in as sybase...it will automagically run the sybinit program to setup a database. OR, run /opt/sybase/install/sybint manually after setting the environment variables appropriately (see ~sybase/.profile). -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Thu Oct 8 23:45:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08223 for freebsd-emulation-outgoing; Thu, 8 Oct 1998 23:45:53 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from poboxer.pobox.com (port39.prairietech.net [208.141.230.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08152 for ; Thu, 8 Oct 1998 23:45:32 -0700 (PDT) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.1/8.7.3) id BAA21146; Fri, 9 Oct 1998 01:43:16 -0500 (CDT) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 9 Oct 1998 01:43:12 -0500 (CDT) X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Reply-To: alk@pobox.com To: jfieber@indiana.edu Cc: emulation@FreeBSD.ORG Subject: Re: Sybase/uname: mystery resolved References: <199810080551.WAA01336@dingo.cdrom.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13853.44860.175168.738233@avalon.east> Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoth John Fieber on Thu, 8 October: : The linux_lib-2.4 port won't cut it, you need a ld-linux.so.2 and : a newer libc (at least, I have not nailed down exactly what is : needed). I needed a newer bash to get as far as I did. : As root, run the /opt/sybase/install/setperm_all, this fixes all : the file ownership an permissions in the sybase tree. : : Log in as sybase...it will automagically run the sybinit program : to setup a database. When I run sybinit I get: ---quote Running task: create the master device. Building the master device .execl() returned: operating system error. Press to continue. ............................................ ---unquote The dots seem to be a forked copy of sybinit spinning until I hit . Spinning, I assume, because execl() failed. Did you see this? How did you overcome it, if so? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message From owner-freebsd-emulation Fri Oct 9 06:40:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03471 for freebsd-emulation-outgoing; Fri, 9 Oct 1998 06:40:50 -0700 (PDT) (envelope-from owner-freebsd-emulation@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03453 for ; Fri, 9 Oct 1998 06:40:43 -0700 (PDT) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id IAA10395; Fri, 9 Oct 1998 08:40:34 -0500 (EST) Date: Fri, 9 Oct 1998 08:40:33 -0500 (EST) From: John Fieber To: alk@pobox.com cc: emulation@FreeBSD.ORG Subject: Re: Sybase/uname: mystery resolved In-Reply-To: <13853.44860.175168.738233@avalon.east> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 9 Oct 1998, Tony Kimball wrote: > Quoth John Fieber on Thu, 8 October: > : The linux_lib-2.4 port won't cut it, you need a ld-linux.so.2 and > : a newer libc (at least, I have not nailed down exactly what is > : needed). > > I needed a newer bash to get as far as I did. I discovered that the bash in linux_lib-2.4 falls if you have a both an (v5) and a new (v6) libc in /compat/linux/lib...ldd shows it being linked to both versions.... > ---quote > Running task: create the master device. > Building the master device > > .execl() returned: operating system error. > Press to continue. ............................................ > ---unquote > > The dots seem to be a forked copy of sybinit spinning until I hit > . Spinning, I assume, because execl() failed. > Did you see this? How did you overcome it, if so? I can't say I encountered it. At that point in the process, sybinit runs the buildmaster program which appears to be failing for some reason. Try doing a ktrace or truss and see if you can figure out why/how execl() is failing. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message