Re: relevance
On Sun, Jul 16, 2000 at 08:23:37AM -0400, [EMAIL PROTECTED] wrote: Excuse my ignorance, but would you expand a bit on SDR? What is it; where is there documentation; and how does one make one's voice heard? Haines Brown At this point I don't think there are any concrete plans for such things. Right now they are vapor that the ARRL has asked the FCC to allow amateurs to develop such technologies. There may be more info at: http://www.arrl.org You may look into the W1AW bulletins archive over the past couple months to see if there is more info available. 73, de Nate -- Wireless | Amateur Radio Station N0NB | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Wichita, Kansas USA EM17hs | men; the rest love not Wichita area exams; ham radio; Linux info @ | freedom, but license." http://www.qsl.net/n0nb/ | -- John Milton
Re: relevance
On Sat, Jul 15, 2000 at 01:29:46PM +0100, Richard Stearn wrote: I suspect the answer lies in the OS used. Linux users are exposed to the Open Source ethos and given time to absorb the ethos will probably release the source. Those who are MicroSoft Windows tend (I regret to say) to adhere to the Shareware ethos and release only executables and ask for money. IMO, I think the reason most WinDOS software is shareware/closed/binary only stuff has much to do with what you mentioned above. I believe it also has a more basic reason. To do any serious development on a WinDOS platform requires a commitment of a substantial amount of money for compiler, IDE, and developer's kit. After making this purchase most software authors would like to recoup at least part of the investment. This (probably biased) view is based on my observation of the Open Source Shareware communities over the last few years. There is a spectrum in both communities. We in the Free Software community do get spoiled after a while with all the fantastic development tools available to us for just a bit of study. I thoroughly enjoy exploring this system and the more I do the more awe- struck I am. All the pieces fit together so well I just can't imagine anybody who wants to tinker with computers choosing something else. But then, I imagine others feel locked into their current systems and are reluctant to change. Is the answer to why circuits are in QST because the creator has got paid for them? Perhaps this, but circuits have been shared for as long as there has been a ham community, thus there is a history of sharing. The software side of ham radio has grown up around closed systems and reflects that heritage. Right now ARRL is pushing Software Defined Radios, SDR. It is imperitive that our voice be heard and that the protocols and implementations these devices will use are Free Software. We cannot afford to allow this technology to become the proprietary goods of a handful of manufacturers while amateurs are locked out of defining what these devices will do. We need to educate our fellow hams, especially those in positions to implement these kinds of policy as to the benefits and importance of Free/open protocols and implementations. Fortunately, I have hope that the ham community will come around. Just look at the embrace and explosion of PSK31. Meanwhile proprietary digital modes such as Clover and PacTOR II have become nothing more than curious footnotes in ham digital history. 73, de Nate -- Wireless | Amateur Radio Station N0NB | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Wichita, Kansas USA EM17hs | men; the rest love not Wichita area exams; ham radio; Linux info @ | freedom, but license." http://www.qsl.net/n0nb/ | -- John Milton
Predict not reading TLE file
Hi. I am using two different versions of predict and found the same problem in each. If I download the ISS TLEs from ftp.celestrak.com, I find that predict finds no satellite in the file. I've looked at the file and can see little difference in the format, etc., except the name which is shown as ISS (ZARYA). I added the (ZARYA) into predict with no positive results and removed it from the TLE file and still no satellite found. I entered the elements by hand and all seems well. I've had predict successfully read the file amateur.txt from the same archive. I have tried predict 2.1.0 (compiled from source) and 2.0.0-*.deb for Debian Potato. Both give the same results. I'm running both versions on the latest Potato release (two different machines). I am pleased with the speed and tightness of the program, brings back the joy of a well written program in this age of bloat-ware. 73, de Nate P.S. The voice announcement is cool and well-done! -- Wireless | Amateur Radio Station N0NB | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Wichita, Kansas USA EM17hs | men; the rest love not Wichita area exams; ham radio; Linux info @ | freedom, but license." http://www.qsl.net/n0nb/ | -- John Milton
Re: Predict not reading TLE file
On Fri, Jun 16, 2000 at 07:51:19AM +1000, Hamish Moffatt wrote: Could it be a problem with CRLF versus LF line endings? That was one of my intial thoughts, Hamish. I used an editor (FTE) that shows certain characters like CR and LF. I did a copy and paste of the iss.txt file into the amateur.txt file and saw that the CR was stripped after the paste. The ISS data still wasn't recognized by predict. 73, de Nate -- Wireless | Amateur Radio Station N0NB | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Wichita, Kansas USA EM17hs | men; the rest love not Wichita area exams; ham radio; Linux info @ | freedom, but license." http://www.qsl.net/n0nb/ | -- John Milton
Re: Best Tasting Club!
On Mon, Jun 12, 2000 at 06:27:44PM -0500, Jeffrey Knight wrote: Eamon: where did you find the list of local linux users groups? (and do you know of a list of local ham radio clubs?) thanks! Jeff I didn't see a reply to the list. A good start to finding a Linux Users Group (LUG is: http://noframes.linuxjournal.com/glue/ and a good place to start looking for a local radio club is: http://www.arrl.org/field/club/ Neither of these are likely to be a complete list, especially the radio clubs as the ARRL only lists those club that affiliated themselves with ARRL. Many others don't do that. 73, de Nate -- Wireless | Amateur Radio Station N0NB | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Wichita, Kansas USA EM17hs | men; the rest love not Wichita area exams; ham radio; Linux info @ | freedom, but license." http://www.qsl.net/n0nb/ | -- John Milton
Re: no bc0
Peter, bc0 is a network interface point and doesn't appear as an entry in /dev. Try the ifconfig command after you load the module like: ifconfig bc0 44.1.2.3 (substitute your actual address, of course) ifconfig has a number of options and takes additional arguments, but the above will at least get bc0 registered and useable for testing. To test for success, just use ifconfig without any arguments and all the active network interfaces should be displayed. HTH, 73, de Nate -- Wireless | Amateur Radio Station N0NB | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Wichita, Kansas USA EM17hs | men; the rest love not Wichita area exams; ham radio; Linux info @ | freedom, but license." http://www.qsl.net/n0nb/ | -- John Milton
ARRL Poll online
Hi all. Normally, I don't go around asking people to crash polls, but we need to let others know we're out here. The American Radio Relay League currently is running a click pool on their home page (http://www.arrl.org) with regard to what OS is used in the shack. Right now Linux is running a distant second with 10% of the vote (1288 votes as I write this), however I am encouraged! If you legitimately use Linux in the shack or plan to in the future, it may be a good idea to register your preference. I don't expect to see ARRL have Linux versions of its software at next year's Hamvention, but with 10% or more of the potential market now using Linux it stands to reason that their marketing and advertising depts may take notice of us. Really, I don't care if the commercial vendors support Linux at all so long as radio interface information remains publicly available. I did some checking at Ten-tec's site and found they have released the source code for the Pegasus under the GPL. Is anyone working on this? Also, I hope the League and QST's editors will recognize that many of the projects that use WinX programs are difficult or off limits to us using Linux. This month's PSK31 transceiver is something I'd really love to build and use, although I am unsure if it will work with any of the Linux PSK31 programs currently under development as it seems to refer to DigiPan quite often. Hopefully, a good showing in this poll will lead to the addition of Linux capable projects in QST in the future. 73, de Nate -- Wireless | Amateur Radio Station N0NB | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Wichita, Kansas USA EM17hs | men; the rest love not Wichita area exams; ham radio; Linux info @ | freedom, but license." http://www.qsl.net/n0nb/ | -- John Milton
Re: X
On Wed, May 17, 2000 at 05:55:28PM -0400, [EMAIL PROTECTED] wrote: Hi I am trying to compile an new version of GTK for my linux which is SuSE and it comes back telling me configure error X libraries or include files not found so i figure they are missing can someone tell me under what dirs will i find these files i need thanks! BOB I'm not familiar with SuSE's package management, but being familiar with Debian, it wouldn't surprise me if the X libs were split into a binaries only and a development version. The development version would contain the header files and such. A good place to start looking is /usr/X11R6/include. 73, de Nate -- Wireless | Amateur Radio Station N0NB | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Wichita, Kansas USA EM17hs | men; the rest love not Wichita area exams; ham radio; Linux info @ | freedom, but license." http://www.qsl.net/n0nb/ | -- John Milton
Re: Log Program for Linux
On Sun, Apr 30, 2000 at 11:37:02PM +1000, Hamish Moffatt wrote: All suggestions welcome. Testers welcome too! When do we start, Hamish? 73, de Nate -- Wireless | Amateur Radio Station N0NB | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Wichita, Kansas USA EM17hs | men; the rest love not Wichita area exams; ham radio; Linux info @ | freedom, but license." http://www.qsl.net/n0nb/ | -- John Milton
Re: Log Program for Linux
On Sat, Apr 29, 2000 at 08:09:48AM -0300, John Ackermann wrote: Hamish wrote: 1. A CW keyer on the parallel port with programmable speed. Personally, I would prefer to generate the CW as audio tones injected as SSB. This is probably not a good idea. Many (most?) rigs are only optimum for CW receive when set to CW mode -- operating in SSB will lose a lot of RX capability (narrow filters, fast AGC, and proper zero beat). From an operational standpoint John is right. However, we here in the States may run into another problem. Modulated CW (MCW) is limited by the U.S. rules to above 30 MHz. MCW is defined as, "Tone-modulated international Morse code telegraphy emissions..." I don't wish to start and off-topic discussion, but, at least for contest and normal CW work, I would prefer the program controlled the state of a pin on a port that I can drive my rig's key input with, or at leat had the option. Also, mentioned in this thread was rig control. IIRC, some months back a post was made to the list of someone writing a library for ICOM rig control. Perhaps this could be extended to other models. I think it would be a good idea to develop such a library so that any programmer doesn't have to re-invent the wheel each time rig control is needed. Along the same lines I recall a post concerning a CW library. This would be another good idea. Finally, I think the use of a real database like PostgreSQL is a great idea for a general logging program. However, for contesting a more specialized approach may be better. I had rolled around in my mind some time back of a contest logger using Berkeley DB for the database backend. I don't know squat about databases and programming, so this may be a lousy idea. That said, it would seem a contest logger needs to be optimized for speed and data integrity. We all know how the lights go out on Field Day or the power fails during the big 'test. One thing about CT is that I've never lost data on any completed and entered QSOs due to power failure and it's happened a lot! Also, it would be nice (essential?) for the contest logs to be read by the general log program for award tracking and the like. Food for thought or grist for the bit bucket... 73, de Nate -- Wireless | Amateur Radio Station N0NB | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Wichita, Kansas USA EM17hs | men; the rest love not Wichita area exams; ham radio; Linux info @ | freedom, but license." http://www.qsl.net/n0nb/ | -- John Milton
Re: Log Program for Linux
On Sat, Apr 29, 2000 at 05:40:43PM -0700, Shawn T. Rutledge wrote: Unfortunately the radio manufacturers seem to like to reinvent the wheel... too bad they're not all plain RS/232 with a standard control language. I agree the software layer should be abstract in spite of it, but it has the potential to get messy if a lot of different hardware must be used to interface to all the radios. Probably just means another layer should be used... SANE (the scanner abstraction layer) would provide a pretty good example. There is SANE itself, and there are plugin drivers for each scanner. Some are parallel, some are SCSI. I agree to a point, but if I'm not mistaken nearly all the radios capable of computer control receive their data through an RS-232 port. Now, the rigs themselves have a variety of of internal levels and require interfaces for RS-232 communication. Probably the most important consideration is the "non-standard" data format using 2 stop bits and the like. Now, whether the rigs' APIs are fully documented is another story. I have the supplied computer interface commands for both the TS-850S and the FT-890 that came with each radio's owners manuals. I've not ever played with them to see if they work as described. For speed, the program should be multithreaded; each new log entry gets enqueued in one thread while another thread reads them from the queue and puts them in the database. A good idea. That's bad for a Linux machine anyway, not just for your contest. Use a UPS or a laptop with charged batteries. Also, transaction-capable databases might help (but I don't have experience using the freeware databases this way, so don't know how robust the implementation is if they have transactions at all). Also, reiserFS or some other journaling filesystem would help. I agree it's bad, but I wonder how many would lug a UPS to the Field Day site? Improved filesystems will help in this regard. Unfortunately, just because one is using a laptop doesn't mean a power failure won't occur. For example, I need to use a port replicator on this Thinkpad 760ED in order to use an external keyboard. To power the laptop off of AC, the unit has to be fed through the replicator and if that power is lost, the laptop dies as the battery won't take over. So, it's still a problem. After they're in the database, arbitrary output formats could also be produced. If the contest authority finds out how you do this and doesn't like the indirectness of it for some snooty reason, then hook up a dot-matrix printer and modify your program to also spit out timestamped entries on paper as they are entered. That should be in a separate thread too, obviously. (Reminds me of the point-of-sale software I wrote a few years ago...) I'm not aware of contest authorities not accepting logs generated per their format, but then I'm a casual 'tester. I do know that as of the November Sweepstakes 2000, ARRL will require logs to be submitted in their new Cabrillo format. Apparently, all the major DOS/Win logging program authros have agreed to support this format by then. One question about a web browser based logger, will such an application require a running web server daemon (is that too obvious of a question)? I would love to see a completely modular system, but I understand this adds a certain level of complexity. Yet, if hams can figure out the new rigs, surely they can install a few more software packages...right? Right? RIGHT? ;-) 73, de Nate -- Wireless | Amateur Radio Station N0NB | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Wichita, Kansas USA EM17hs | men; the rest love not Wichita area exams; ham radio; Linux info @ | freedom, but license." http://www.qsl.net/n0nb/ | -- John Milton
Re: Log Program for Linux
On Sat, Apr 29, 2000 at 06:59:24PM -0700, Shawn T. Rutledge wrote: On Sat, Apr 29, 2000 at 08:31:18PM -0500, Nate Bargmann wrote: I'm not aware of contest authorities not accepting logs generated per their format, but then I'm a casual 'tester. I do know that as of the November Sweepstakes 2000, ARRL will require logs to be submitted in their new Cabrillo format. Apparently, all the major DOS/Win logging program authros have agreed to support this format by then. What does it look like? Check out http://www.kkn.net/~trey/cabrillo It looks like much info on it, but I haven't checked it out yet. That's what good package management is for. On Debian it could be made pretty foolproof; the log program has dependencies thus you ain't done installin' until those dependencies are installed too. It would depend on Apache, PostgreSQL, and PHP (or Java/servlet engine/JSP engine), with a browser, libradio-control and libcw being recommended. If everything (the browser, database, web server and connections to radios) is all on one machine it's easy; getting pieces of it distributed throughout a network would require some RTFMing. (Aside... in case the web server is not the machine with the radios hooked up, the radio control library should probably be a network server... clients attach to port x and send commands.) Those of us with Debian will have few problems. Others might not be so fortunate. 73, de Nate -- Wireless | Amateur Radio Station N0NB | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Wichita, Kansas USA EM17hs | men; the rest love not Wichita area exams; ham radio; Linux info @ | freedom, but license." http://www.qsl.net/n0nb/ | -- John Milton
Re: FCC's ULS appears to be accessible only from Windows
Bob Nielsen wrote: I've figured how to connect to their server, but it requires a lot of work (changing /etc/resolv.conf, ppp and all my routing). I believe I saw somehere that you can download form 605 and use that by mail as an option. This sounds like an opportunity to right up a mini-HOWTO as I'm sure this will become an FAQ, especially when I need to take the ULS plunge. :| 73, de Nate -- Packet | N0NB @ WF0A.#SCKS.KS.USA.NOAM | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Valley Center, Kansas USA EM17hs| men; the rest love not Visit my Linux + Ham Radio pages| freedom, but license." http://homepage.netspaceonline.com/~ka0rny/ | -- John Milton
Re: FCC's ULS ... OFFTOPIC
Randy Smith wrote: Sorry, this is off topic, but does anyone know what law gives the FCC permission to require an individual to divulge their SSN (TIN)? Hello Randy and All. Per the latest CQ magazine I received yesterday in the Washington Readout column by W5YI this authority is mandated by the Debt Collection Act of 1996. It is also known as Public Law 104-134. It's a crock, but until congress is pressured into amending the law and exempting radio amateurs, divulging your SSN or registering with ULS and aquiring a License ID Number (LIN) is required to effect any changes to your license information. 73, de Nate -- Packet | N0NB @ WF0A.#SCKS.KS.USA.NOAM | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Valley Center, Kansas USA EM17hs| men; the rest love not Visit my Linux + Ham Radio pages| freedom, but license." http://homepage.netspaceonline.com/~ka0rny/ | -- John Milton
[Fwd: No Ping Return]
This is on behalf of a friend who accesses the list through a BBS mail reader through a service provided by the local university. He is subscribed to the list and can read your responses. Should you wish to reply direct, hs address is: [EMAIL PROTECTED] (JOHN BANDY) 73, de Nate JOHN BANDY wrote: Hello Linux Hams, Profile. ax25 and netrom connects work ok. bc0 is the network device. Tigertronics bp-96a modem is plugged into the parallel port of a i486. 2.0.30 Linux RedHat 4.2 (Biltmore). TCP problem #1. Why do I get the following with "listen -act" while "ping -i6 k0top.ampr.org", "talk [EMAIL PROTECTED]", "finger [EMAIL PROTECTED]", etc.. ..w0ut-8-w0ut-8 ..44.122.0.51-44.122.0.41 The IP example addresses are correct but the "to" address of the ax25 addresses hould be for example "k0top-10". I get no returns and 100% packet loss on "ping". I use to get returns but not anymore. TCP problem #2. Users get "421 service not available. Remote server has closed connection." hen they try to "ftp" into my server. Same for me when I "ftp localhost". TCP problem #3. When I enter "mail [EMAIL PROTECTED]" etc.. , later the "mail" daemon sends me the following: "-transcript of session follows-- 550s... User unknown [EMAIL PROTECTED] Deferred. Name server: k0top.ampr.org. hostname lookup failure. Warning: message still undelivered after 4 hours. Will keep trying until message is 5 days old." An amateur radio transmission never occurs even though the above info imply one is made. The "resolv.conf" file is empty and the address is in the "hosts" file. Thanks for the help. 73. John W0UT ... * ATP/Linux 1.50 * Promote a STANDARD Application Programming Interface (API). -- Packet | N0NB @ WF0A.#SCKS.KS.USA.NOAM | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Valley Center, Kansas USA EM17hs| men; the rest love not Visit my Linux + Ham Radio pages| freedom, but license." http://homepage.netspaceonline.com/~ka0rny/ | -- John Milton Hello Nate, Hope all is going well for you. I tried uploading the following to [EMAIL PROTECTED] and got nothing back. The address is to long for my bbs reader so I have to put it on the first line of the message. I got on the list by using my boy's Wintendo. :) Please submit the following to the list. Thanks 73. John W0UT Hello Linux Hams, Profile. ax25 and netrom connects work ok. bc0 is the network device. Tigertronics bp-96a modem is plugged into the parallel port of a i486. 2.0.30 Linux RedHat 4.2 (Biltmore). TCP problem #1. Why do I get the following with "listen -act" while "ping -i6 k0top.ampr.org", "talk [EMAIL PROTECTED]", "finger [EMAIL PROTECTED]", etc.. ..w0ut-8-w0ut-8 ..44.122.0.51-44.122.0.41 The IP example addresses are correct but the "to" address of the ax25 addresses hould be for example "k0top-10". I get no returns and 100% packet loss on "ping". I use to get returns but not anymore. TCP problem #2. Users get "421 service not available. Remote server has closed connection." hen they try to "ftp" into my server. Same for me when I "ftp localhost". TCP problem #3. When I enter "mail [EMAIL PROTECTED]" etc.. , later the "mail" daemon sends me the following: "-transcript of session follows-- 550s... User unknown [EMAIL PROTECTED] Deferred. Name server: k0top.ampr.org. hostname lookup failure. Warning: message still undelivered after 4 hours. Will keep trying until message is 5 days old." An amateur radio transmission never occurs even though the above info imply one is made. The "resolv.conf" file is empty and the address is in the "hosts" file. Thanks for the help. 73. John W0UT ... * ATP/Linux 1.50 * Promote a STANDARD Application Programming Interface (API).
Re: ARRL Handbook on CD
Although an ARRL member continuosly since January of 1983, the League is not above criticism when I believe they are taking the wrong path. An interesting page I read last night is at: http://www.wm7d.net/az_proj/az_html/arrl_restructuring.html by NA3T. I know this is getting off target, but although we have seen support on this list from various HQ staff (keep up the good work guys!), from the view presented by the League to the mainstream membership, ARRL is a Wintendo (I like that) outfit. I admit, though, Linux has gotten at least two mentions in the Digital Dimension column some months back. Perhaps it behooves more experimenters to embrace Linux and write articles about it and using it for project development for QST. Perhaps some of the blame can be laid at our doorstep for not providing them with publishable articles. Unfortunately, I don't see the market emphasis of the League changing until they are losing sales because of the lack of Linux and X support. My crystal ball is cloudy, but until most of the computer software use in ham radio is ported to Linux/X, the League will continue to market to Wintendo only. 73, de Nate -- Packet | N0NB @ WF0A.#SCKS.KS.USA.NOAM | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Valley Center, Kansas USA EM17hs| men; the rest love not Visit my Linux + Ham Radio pages| freedom, but license." http://homepage.netspaceonline.com/~ka0rny/ | -- John Milton
uClinux
Here is an intersting project underway by the Ryerson ARC in Canada and featured today on Slashdot (http://slashdot.org) and you can find more info here: http://ryeham.ee.ryerson.ca/uClinux/simm/ Perhaps this would be a good base to build cheap AX.25 routers and the like for remote sites... 73, de Nate -- Packet | N0NB @ WF0A.#SCKS.KS.USA.NOAM | "None can love freedom Internet | [EMAIL PROTECTED] | heartily, but good Location | Valley Center, Kansas USA EM17hs| men; the rest love not Visit my Linux + Ham Radio pages| freedom, but license." http://homepage.netspaceonline.com/~ka0rny/ | -- John Milton
Re: Alias in ax25 util help
Ron Stordahl wrote: Minor point but aliases are limited to 5 characters I believe. I tried 6 in an eprom burn for a TheNet/X1J4 node and as I recall surrounding TheNet nodes only showed the first 5 in their routing tables. This is some time ago so I might have the details a little wrong. Does Linux work correctly with 6? Hi Ron and all. Per the AX.25 spec (I believe) aliases and callsigns are limited to 6 characters. I have burned a number of TheNet 1.0, TheNet Plus, and TheNet X-1J4 with 6 character aliases with no problems. All the nodes I've seen print 6 character aliases in their tables and nodes lists. Perhaps a non-printing character snuck into that field? Just a thought. Second, Re: your earlier message Ron, I think you are correct when you say that if your Linux node were set to respond to N5IN + any SSID when you have other stations on the same frequency using your call plus some SSID that there would be interesting problems. What I've seen happen is usually an agly race between the stations sharing the callsign+SSID with the end result being an FRMR packet generated by one or both and a nasty disconnect! As a result, the following unwritten rule appears to be adhered to by most node-ops in these parts: Callsigns aren't used as node aliases due to the SSID confusion caused by Net/ROM's allowance of any SSID to be used in conjunction with its alias. Third, Re: Tomi and your mention of the first callsign in nrports being the call broadcast as the node callsign. That is exactly how I have N0NB-10 assigned currently. No other services listen using N0NB-10 and it is only useful to another node (again I have not tested this to be absolutely sure of its behavior). Finally, thanks Jonathan for seconding my method! (BTW, I use Notus Lotes at work as well and found that when I send email over the 'Net I try to use courier font and hit Enter often! It is ugly for Internet email.) 73, de Nate -- Packet | N0NB @ WF0A.#SCKS.KS.USA.NOAM | "FAILURE IS NOT Internet | [EMAIL PROTECTED] | AN OPTION! Location | Valley Center, Kansas USA EM17hs| It's bundled Visit my Linux + Ham Radio pages| with the soft- http://homepage.netspaceonline.com/~ka0rny/ | ware..."
[Fwd: linux-hams frustration]
I'm passing along the following question on behalf of a friend having trouble subscribing to the list. JOHN BANDY wrote: Why does Linux command: /sbin/ifconfig bc0 up cause the Linux message: SIOCSIFFLAGS: Permission denied or why does Linux command: /sbin/ifconfig bc0 hw ax25 1 up cause the same Linux message: SIOCSIFFLAGS: Permission denied Have a Tigertronics BayPac BP-96A plugged into the parellel port. At boot time the following Linux messages display: baycom: version 0.3 compiled 19:40:53 May 31 1998 lp1 at 0x0378, (polling) from my RedHat 4.2, 2.0.30, i486, system. Thanks and 73, John W0UT ... * ATP/Linux 1.50 * Packet amateur radio, where home built modems are legal. -- Packet | N0NB @ WF0A.#SCKS.KS.USA.NOAM | "FAILURE IS NOT Internet | [EMAIL PROTECTED] | AN OPTION! Location | Valley Center, Kansas USA EM17hs| It's bundled Visit my Linux + Ham Radio pages| with the soft- http://homepage.netspaceonline.com/~ka0rny/ | ware..." Hello Nate, N0BN, Hope all is well with you. I have tried twice to subscribe to "linux-hams" of "majordomo.vger.rutgers.edu" and get NO reply. So would you ask the following question on it for me. Why does Linux command: /sbin/ifconfig bc0 up cause the Linux message: SIOCSIFFLAGS: Permission denied or why does Linux command: /sbin/ifconfig bc0 hw ax25 1 up cause the same Linux message: SIOCSIFFLAGS: Permission denied Have a Tigertronics BayPac BP-96A plugged into the parellel port. At boot time the following Linux messages display: baycom: version 0.3 compiled 19:40:53 May 31 1998 lp1 at 0x0378, (polling) from my RedHat 4.2, 2.0.30, i486, system. Thanks and 73, Nate. John W0UT ... * ATP/Linux 1.50 * Packet amateur radio, where home built modems are legal.
glibc 2.1 is out
I've read with interest the commentary regarding kernel 2.2.x. So far, I've not made the switch as too many packages would need updating and I wonder how many other things will break due to that. Now, the good folks down at GNU have released glibc 2.1. This, as I understand it is the newest stable branch of glibc and more details can be found here: http://linuxtoday.com/stories/2915.html Perhaps by the time the distributors get a glibc 2.1 based system with kernel 2.2.x, I'll have that screamer built (screamer as compared to this 486-100!). 73, de Nate -- Packet | N0NB @ WF0A.#SCKS.KS.USA.NOAM | "FAILURE IS NOT Internet | [EMAIL PROTECTED] | AN OPTION! Location | Valley Center, Kansas USA EM17hs| It's bundled Visit my Linux + Ham Radio pages| with the soft- http://homepage.netspaceonline.com/~ka0rny/ | ware..."
Re: Kiss and things
Mike Bilow wrote: I'll probably have my head handed to me for this, but at least accept that these comments are based on over 15 years of experience with packet. Not by me! I agree with all five points 100%. You said what I've been mulling over what to say for a week. I think we know that by now. Well, obviously most on this list do. Alas, Karl had to be reminded. I suggested this years ago. I even offerred to serve as de facto secretary, and asked that anyone interested contact me via e-mail. I received three responses and scrapped the idea. If people are willing to try it again, I think it would be a good project. There was some talk of TAPR facilitating something similar, but I think that discussion may have died out, too. It takes someone with more engineering background than I to be able to manage such a project. I would try to help in other ways such as beta testing or writing documentation if needed. Perhaps now is a better time to move this direction as I think we can implement new ideas without concern of its impact on commercial interests selling ancient TNC technology. However, I also have no sympathy for writing lots of nice papers about protocols without actually trying to implement them. An unimplemented protocol is obviously of no use to anyone, and it is impossible to know if it would even work until someone at least attempts to implement it. Perhaps Linux is the key to making this happen, since it provides a convenient and accessible platform for developing new hardware and software in the open. Excellent point. I think it was this talk of AX.25 Version 2.2 support in another thread that got me to thinking about this very problem. Given the mistakes and reasons for all prior protocols, a new implemention on Linux gives us advantages today only dreamed of when packet was in its infancy. I think the protocol(s) should be designed and implemented by those people on this list and perhaps adding in those others who have worked with implementing AX.25 or other protocols in other PC programs. To me it seems that a new protocol implemented on Linux would be the reference implementation for ham radio anyone else would need to follow when implementing it on another platform. I think the model presented by Linux development is an excellent one to follow for designing a next generation radio-based protocol. I'm willing to help. 73, de Nate P.S. I've been playing with packet for 11 years, so you have a couple on me! -- Packet | N0NB @ WF0A.#SCKS.KS.USA.NOAM | "The more you Internet | [EMAIL PROTECTED] | complain, the Location | Valley Center, Kansas USA EM17hs| longer God lets Visit my Linux + Ham Radio pages| you live." http://homepage.netspaceonline.com/~ka0rny/ |
Re: Kiss and things
Karl F. Larsen wrote: Hi Karl and all. Well, you're in luck as I'm in the mood for philosophical debate. ;-) I am worried about what I read and hear now about replacements for the old nodes and computer things we are now using. What we need far more urgently are users of our current network! Unfortunately, we HAD the users on our *current* network and they've already left. Why? I don't know. Blame the Internet, blame an unwillingness on the part of us node-ops and BBS ops to bankroll a highspeed network for a bunch of users that cared to do nothing more than to use the current system and then bitch about how slow it was rather than learn how packet actually works and show an interest in improving the network, but blame someone other than the users that have left, of course. One thing I have noticed is that those still on packet are having fun experimenting with the mode again, myself included. To those who feel that if we can speed up the Ham Packet Network we can regain users from the internet, I say your not even aware of the problem! Is this the object or even a goal of anyone on this list? For one thing the majority of the information passed on the Internet would be illegal on ham radio for various reasons. A radio network is fundamentally different in its design approach than a wired network and should probably use a completely different protocol that is specifically designed for radio networks and not an adaptation of wired network protocols. Also, an Internet speed radio network probably requires using microwave frequencies for point-to-point links with a maximum path length of 50 to 70 km over flat land. Such a network would require an immense number of relay sites just to cover and link the major population areas of North America. Just where will the ham community come up with the money to rent the required site space or construct it? Right now tower space is the hottest commodity in the technology world (right after spectrum) so we can forget about free access for the most part. The problem is that Amateur Radio holds nothing for the young person looking for a hobby. They all have cell phones and can talk to whom ever when ever. I still see teenagers back packing and running the rapids in the rivers, so things have not changed in a major way. But Ham Radio and Model planes are not being done any more. Radio holds the same mystique for those truly interested in it today as it has for those of previous generations. I think a lot of it has to do with the lack of leisure time today's kids have for hobbies that require a significant time investment unless it is something they are intensely interested in. Those interested in radio or model planes are doing it. I imagine these pursuits had wider participation in the past as they had less competition for kids' time and involved those with a passing interest as well. As for Kiss, I have a eprom burner and I have made a lot of kiss e-proms for tnc-2 tnc's. I only use the version written by G8BPQ because it is so well done. There is nothing wrong with this version and it runs faster than 115kbps. Speed doesn't equal precise control of what's on the other end of the KISS link. To those wishing for better nodes I suggest they look at the X1J release 4 software that makes a simple tnc-2 into a tcp/ip capable system. Development on this node ended simply because it works and does everything it should. You can even make your TNC at home a X1J-4 node and also "talk through the node" as if the TNC is a normal kiss type. My experience with X1j-4 was much less stellar. If you like trips to your remote node site, use it, otherwise forget it is my advice (This involves personal experience with three different TNCs all of different vintage and at two seperate sites. All suffered from lock-ups and crashes with the code including a new 1270-C). TheNet Plus 2.08B, OTOH, is simply bulletproof for a TNC based node. For Linux the existing software works just fine! All the new 2.2.0 kernel holds for me is the ability to have 6 netrom devices. The 2.0.36 kernel allows only 4. Hmmm, using this logic Linus should have stopped development somewhere around 0.99.x as IIRC he said it was serving his needs by that point. Fortunately Linus has facilitated Linux moving forward. The AX.25 utilities must be allowed to move forward as well. Heck, AX.25 must move forward or perhaps be scrapped and replaced altogether. That is what makes ham radio so great, we can *experiment* and learn what works and what doesn't. What ham radio doesn't need is a variety of protocols, or even one for that matter, owned by corporations or organizations or individuals and available only under a Non Disclosure Agreement or any other restrictive agreement. I think all ham radio protocols should be Free (LGPL?) and available to anyone wishing to implement or attempt to improve them. If we could establish
Re: ax25_subr.c, fix for ~ included in .../linux-2.0.36/net/ax25
Joerg Reuter wrote: It will however vaninsh with Matthias' new AX.25 code, as it will properly abstract the channel access from the network driver. Right now just leave it alone. Hi Joerg. Speaking of new AX.25 code, where does the AX.25 utilities project now stand? It seems the latest package is the 2.1.42a and the kernel drivers are now included with the kernel source for = 2.0.35 and I suppose the Pre-2.2 series. Watching the list for some time I gather patches have been made to 2.1.42a to compile it under Redhat 5.x. Yet, I've not seen any mention of newer patches or packages on the list. Is there a web site with development versions of the utilities, a changelog, etc.? Most everything works well, but what new features are planned, what bugs still need squashing, is this information publicly available? Is there a changelog of the kernel drivers? A question for the list, is someone taking over the AX25-HOWTO? I'm not using too many aspects of the Linux AX.25 utilities, but would be willing to pitch in if someone needed another proofreader or other help (there, I opened the floodgates!). Is there a need for an FAQ outside of the AX25-HOWTO? So many questions, so little time... 73 de Nate -- Packet | N0NB @ WF0A.#SCKS.KS.USA.NOAM | "The more you Internet | [EMAIL PROTECTED] | complain, the Location | Valley Center, Kansas USA EM17hs| longer God lets Visit my Linux + Ham Radio pages| you live." http://homepage.netspaceonline.com/~ka0rny/ |
No color from listen in Xterm
Hi All. Here is a bit of a puzzle. About a year ago I played with the AX.25 utilities for a time, but no one else was on TCP/IP locally. Now some interest is developing and I want to start playing again. The only problem I have now is that the listen program seems unable to display color in an xterm. Color works just fine on the console. The trouble is colorized listen *used* to work in xterm, but last summer sometime I fiddled with either my termcap or terminfo files and I think I lost color at that time (yeah, I know, no back-up lectures please ;) ). I echo ANSI codes to xterm in my PS1 line and these colors show just fine. Color works in a copy of rvxt (ver 2.20), but packets containing carriage returns and newlines overwrite others at the top of the window. The xterm I am using came with XFree86 3.3.0 and it seems to only utilize /etc/termcap and not terminfo supplied by the ncurses 4.2 package I have installed. Anyone have any ideas? Happy New Year! 73, de Nate -- Packet | N0NB @ WF0A.#SCKS.KS.USA.NOAM | "Depression is Internet | [EMAIL PROTECTED] | merely anger Location | Valley Center, Kansas USA EM17hs| without Visit my Linux + Ham Radio pages| enthusiasm." http://homepage.netspaceonline.com/~ka0rny/ |
Re: Access to the node from the console ?
Jose Angel Amador Fundora wrote: I wonder if someone knows how to get connected to the Linux node from the Linux console ? When I used BPQ with FBB5.15c, F9 did it. Wonder if there is any workaround I still don't know of. Hints welcome. Hi Jose. I'm sure there is a better way, but here is what I use. In /etc/inetd.conf I added this line: # Services local to linux.n0nb.ampr.org # nodestream tcp nowait root/usr/sbin/node node Then in /etc/services I added this: # Ports assigned local to linux.n0nb.ampr.org # node4000/tcp# OH2BNS's node software Then setup /etc/node.perms and all the rest. Since my hostname is linux, I just use this command: telnet linux 4000 This tells telnet to connect the port 4000 which is the node switch. Works rather well. Good luck, 73, de Nate -- Packet | N0NB @ WF0A.#SCKS.KS.USA.NOAM | "Depression is Internet | [EMAIL PROTECTED] | merely anger Location | Valley Center, Kansas USA EM17hs| without Visit my Linux + Ham Radio pages| enthusiasm." http://homepage.netspaceonline.com/~ka0rny/ |
