[nos-bbs] JNOS TTY console - No Visual

Sat Feb 5 03:41:53 EST 2011

Bob:

I can't leave it in !!

If I leave it in, I get an "Ambiguous Redirect" error and JNOS wont run.

That was already posted.

Date: Sat, 5 Feb 2011 01:11:33 -0500
From: bobtenty at gmail.com
To: nos-bbs at tapr.org
Subject: Re: [nos-bbs] JNOS TTY console - No Visual

You shouldn't remove '2>&1' as it is needed to make it work

I use it too.

By the way, I find the /jnos after the '-d' parameter confusing

Below would also work..

"exec /jnos/jnos -a 40 -d  </dev/tty4> /dev/tty4 2>&1"

73,

Bob VE3TOK

On 11-02-04 11:50 PM, Wm Lewis wrote: 

Well, I did figure out one thing.... 

My inital post that JNOS was not automatically starting using this line:
"exec /jnos/jnos -a 40 -d/jnos </dev/tty4> /dev/tty4 2>&1"  was, in fact, correct.

Before this issue, when JNOS did auto-run, I did use that command.

After the issue arose, I had to modify the line and drop the last part of "...... 2>&1" so that the line now reads:
"exec /jnos/jnos -a 40 -d/jnos </dev/tty4> /dev/tty4"

I forgot to post that the yesterday when I discovered that JNOS now runs with just a blinking cursor.

If I manually enter the line as  "exec /jnos/jnos -a 40 -d/jnos </dev/tty4> /dev/tty4 2>&1" at a command promt, leaving the "2>&1" part in, linux responds with an "ambiguous redirect" error. That gave the clue to remove the "..2>&1" portion, thus getting JNOS to finally run on computer startup/boot.

I should re-state that JNOS was not starting until I removed the last part.

As for the "-a 40" part you asked about, that tells JNOS to allow no more than 40 axip/udp links.

So, as it is, JNOS starts. It just doesn't reveal that when I toggle to console 4. 

Booting with different kernals has no change.

In the words of Leonard Nimoy, I am still "In search of" ....

Bill
KG6BAJ

> Date: Fri, 4 Feb 2011 22:33:43 -0500
> From: k8rra at ameritech.net
> To: thunderft at hotmail.com
> Subject: Re: My interest is now piqued
> 
> OOPS Bill -- sorry I did not remember you spread out the stuff in your 
> reflector posts...
> 
> 
> On 02/04/2011 06:41 PM, Wm Lewis wrote:
> > Skip:
> >
> > JNOS is being started automatically on computer bootup/restart.
> FYI:
> "crw--w---- 1 root tty 4, 4 2011-01-31 00:34 /dev/tty4"
> 
> c -> is a "character by character" I/O device
> root -> root user owns the the device
> tty -> is the group of users with special privileged access to the
> device
> rw- -> is the basic "read" and "write" and "execute" privilege set
> rw--w---- -> the set is repeated three times for root, tty, and all
> other users
> 4, 4 -> is the programming linkage from the kernel to the outside world
> 2011-01-31 00:34 -> is the time stamp for the last time it was modified
> /dev/tty4 -> is the name of the device we all use [it's like "COM4"
> in the DOS world].
> 
> Does that help?
> 
> >
> > Jnos is loaded into TTY4/Console 4.
> Yup -- I got that part.
> Given the /var/log messages output, I'm surprised to see the "ps" return 
> jnos as running.
> From your earlier post the following:
> 
> Jan 30 19:07:25 linux init: tty4 main process ended, respawning
> Jan 30 19:07:25 linux init: tty4 main process (21226) terminated
> with status 2
> Jan 30 19:07:25 linux init: tty4 main process ended, respawning
> Jan 30 19:07:25 linux init: tty4 main process (21229) terminated
> with status 2
> Jan 30 19:07:25 linux init: tty4 main process ended, respawning
> 
> is telling you that the
> 
> ========================================================
> rm -f /jnos/spool/mqueue/*.lck 2> /dev/null
> rm -f /jnos/spool/mail/*.lck 2> /dev/null
> exec /jnos/jnos -a 40 -d/jnos </dev/tty4> /dev/tty4 2>&1
> ========================================================
> 
> Script is failing and then restarting.
> Notice the short time span for all the respawn cycles? -- its the 
> script itself.
> Jnos is never really getting started until the last try [when the kernel 
> sorta "gives up trying"]
> The last try is done without fully attaching the sysop console to tty4 
> [that's why the cursor only]
> 
> >
> > See my previous posts for the method used. (I don't want to repost it 
> > all over, again)
> I'm not comfortable with the:
> 
> "exec /jnos/jnos -a 40 -d/jnos </dev/tty4> /dev/tty4 2>&1"
> 
> 
> line in the init script.
> 
> -a 40 -- is a parm I don't recognize
> -d/jnos -- specifies the execution working directory
> </dev/tty4> -- specifies tty4 is used for both input & output
> /dev/tty4 -- HHMMM I wonder why the repeated ref to tty4
> 2>&1 -- put the error message stream together on the
> standard output stream.
> 
> But I can't tell you what a better syntax would be.
> Maybe "</dev/tty4> /dev/tty4" should be "</dev/tty4 >/dev/tty4"?
> I suggest you do some google research to get more opinions.
> WB8RCR has some good material for this purpose.
> 
> >
> > Yes, the only issue is that JNOS used to be *visible* when I toggled 
> > over to console 4.
> > Yes, I would like it to be visible again.
> >
> > Right now, when I toggle over to console 4, it only shows a blinking 
> > cursor line.
> Yes -- jnos is not hooking up properly to /dev/tty4 device.
> 
> >
> > Bill
> Good luck with the "init tty" approach to starting jnos.
> I'm delighted with the "service" approach including screen -- if you 
> want to switch to this method I'd be happy to send you the scripts I use 
> as a go-by.
> 
> 73
> Skip

_______________________________________________
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/20110205/a5892361/attachment.html>