[nos-bbs] ubuntu 9.1 compiles OK now, but...
Bob Tenty
bobtenty at gmail.com
Sat Nov 27 01:23:29 EST 2010
Bill:
To start it in virtual tty5 add </dev/tty5>/dev/tty5 2>&1 to the "exec"
line in your startnos file.
like:
exec ./jnos -g2 -w7+4 -d </dev/tty5>/dev/tty5 2>&1
export TERM=linux is not necessary
Don't use tty5 (or whatever console not in use) to your tty5.conf file
if you use
</dev/tty5>/dev/tty5 2>&1 , etc in your startnos file.
You can stop and start tty5 with the commands:
initctl stop tty5
initctl start tty5
73,
Bob VE3TOK
On 10-11-26 09:42 PM, Wm Lewis wrote:
> Bob:
>
> Can we see a copy of your "dojnos" file ?
>
> I call up a file named "startnos". Here it is
>
> =======================================
> cd /jnos
> rm -f /jnos/spool/mqueue/*.lck 2> /dev/null
> rm -f /jnos/spool/mail/*.lck 2> /dev/null
> sleep 1
> export TZ=EST5EDT
> export TERM=linux
> exec ./jnos -d/jnos -v
> =======================================
>
> I'm running Ubuntu 10.04.1
>
> I tried using tty5 as my test console. Still no joy.
>
> First, Ubuntu would not run "startnos" until I manually flagged it an
> executable file.
>
> Then in my "startnos file" I had to comment out the line "export
> TERM=linux". Ubuntu doesn't seem to like it from inside "startnos".
>
> Then, I also had to comment out the "sleep 1". When running from the
> "startnos" Ubuntu also does not like it.
>
> Although, if I'm at the terminal command line myself and type either
> one manually, Ubuntu seems fine with them. Go figure.
>
> So, from tty5 (brought up by f5) I can "cd /jnos" and then can also
> "*.*/startnos" and JNOS boots up.
> If I "exit" JNOS, it does not respawn in tty5 at all. I just get
> dropped back to the /jnos directory at the command line.
>
> When I change the /_tty5.conf_/ file to attempt to kick JNOS on boot,
> (since I can manually do it from the command line as above) I can
> access tty1 through tty4, and tty6 and tty7(GUI). tty5 is just has a
> blinking cursor line with nothing happening....ever.
>
> Here is my revised tty5.conf file
>
> =====================================
> # tty5 - getty
> #
> # This service maintains a getty on tty5 from the point the system is
> # started until it is shut down again.
>
> start on runlevel [23]
> stop on runlevel [!23]
>
> respawn
> exec /jnos/startnos tty5
> # exec /sbin/getty -8 38400 tty5
>
> =====================================
>
> I know I'm close. Just cant seem to get tty5 to run JNOS
>
> Also, I'm new to linux, so all of this is a huge learning curve for me.
>
> 73,
>
> Bill - de KG6BAJ
>
>
> ------------------------------------------------------------------------
> Date: Fri, 26 Nov 2010 18:10:01 -0500
> From: bobtenty at gmail.com
> To: nos-bbs at tapr.org
> Subject: Re: [nos-bbs] ubuntu 9.1 compiles OK now, but...
>
> In Ubuntu the consoles/ virtual tty's are started from
>
> /etc/init/
>
> Editing tty5.conf for example (jnos running as "root")
>
> # tty5 - getty
> #
> # This service maintains a getty on tty5 from the point the system is
> # started until it is shut down again.
>
> start on runlevel [23]
> stop on runlevel [!23]
>
> respawn
> #exec /sbin/getty -8 38400 tty5
> exec /srv/home-remote/hamradio/jnos/dojnos
>
>
> "dojnos" is a bash/sh file that starts jnos in a console/virtual tty
>
> To start the jnos executable "jnos" directly in console/virtual tty5
>
> Replace the last line with:
>
> exec /srv/home-remote/hamradio/jnos/jnos tty5
>
>
> Older versions of Ubuntu use the directory /etc/event.d/
> ---------------------------------------------------------------------------
>
> For example:
>
> editing the file "tty5"
>
> # tty5 - getty
> #
> # This service maintains a getty on tty5 from the point the system is
> # started until it is shut down again.
>
> start on runlevel 2
> start on runlevel 3
>
> stop on runlevel 0
> stop on runlevel 1
> stop on runlevel 4
> stop on runlevel 5
> stop on runlevel 6
>
> respawn
> # exec /sbin/getty 38400 tty5
> exec /bin/su - hamradio -c "/srv/home-remote/hamradio/jnos/dojnos"
>
> The last line can be replaced for user "root" with:
>
> exec /bin/su - root -c "/srv/home-remote/hamradio/jnos/dojnos"
>
> or just..
>
> exec /srv/home-remote/hamradio/jnos/dojnos
>
> or without bash file "dojnos" and using the jnos executable "jnos"
> directly:
>
>
> exec /srv/home-remote/hamradio/jnos/jnos tty5
>
>
> 73,
>
> Bob VE3TOK
>
> On 10-11-26 04:20 PM, Jim Smith wrote:
>
> I haven’t tried to do this in Ubuntu, but on Slackware 10.1 I use
> the install script Maiko provides. I install it into /opt then
> modify /etc/iniitab to use console 5 as the JNOS console with
> “c5:1235:respawn:/opt/jnos/startnos /dev/tty5” in place of the
> usual line for console 5. Works fine. If I need to I kill it and
> it automatically respawns.
>
> More than one way to fire it off…
>
> Cheers!
>
> Jim N8AVX
>
> *From:*nos-bbs-bounces at tapr.org <mailto:nos-bbs-bounces at tapr.org>
> [mailto:nos-bbs-bounces at tapr.org] *On Behalf Of *Michael Fox - N6MEF
> *Sent:* Friday, November 26, 2010 12:46 AM
> *To:* 'TAPR xNOS Mailing List'
> *Subject:* Re: [nos-bbs] ubuntu 9.1 compiles OK now, but...
>
> What we do is run a script that is executed from /etc/rc.local.
> This is run at boot time. The script calls JNOS in a the “screen”
> command, so that we can attach/detach to the console from any
> terminal. The script also executes in a loop which tests the exit
> code of JNOS and, if not 0, restarts it. Works FB.
>
> Michael
>
> N6MEF
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org <mailto:nos-bbs at tapr.org>
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>
>
>
> _______________________________________________ nos-bbs mailing list
> nos-bbs at tapr.org https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20101127/68057e25/attachment.html>
More information about the nos-bbs
mailing list