From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Walton Subject: XFBB Nightmares! Date: Tue, 18 Mar 2003 15:59:46 -0800 Sender: linux-hams-owner@vger.kernel.org Message-ID: <3E77B2F2.7030806@kj6eo.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: LINUX HAMS MAILING LIST Cc: Jack Eifer Nobody on the XFBB mailing list seemed to be interested in answering my questions. Would anyone here on the linux-hams mailing list care to comment on my concerns listed below? Have all of you installed XFBB without a single problem? Could I be living on top of an Indian Burial Ground or something? I would certainly like to move on to the next set of error codes if someone would be kind enough to comment on my current dilemma. Thank you in advance for your expert advice and support! Regards, Bill KJ6EO (copy of message sent to xfbb@f6fbb.org mailing list) Gentlemen - Thank you for taking the time to read my message. I have finally resolved my AX25 and Linuxnode problems and I am ready to tackle my final problem XFBB. Everyone else seems to have little or no problems getting XFBB running. So, I must assume that I am overlooking some menial information that is keeping my XFBB setup from working. The README file is simple and clear and I have followed the steps: (FYI) ... I am running RedHat v7.2 with a 2.4.20 kernel. AX25 and Linuxnode installed. 1) Put tarball in a specific directory 2) un-tar it 3) Run the install shell and answer the questions 4) Edit the appropriate files ... port.sys, init.srv, etc. 5) Run it ... execute the program shell ... ./xfbb.sh However ... the result is always the same "Unknown return value 127". I have heard rumors that XFBB has to be compiled. There are no instructions with my tarball that says it has to be compiled (x700e_full.tgz). If I am missing the compile step I would appreciate it if someone would point me in the right direction. Is it possible that I have the wrong tarball? I have been stuck with the "unknown return value 127" error for ever. It would be nice to at least move on to the next set of error codes. Any information that you might be able to offer would be appreciated! Regards, Bill KJ6EO