Mailing List Archive

> Is there a way to set a flag for Sun machines individually that have had
> this change made to them...
>
> http://sunsolve.sun.com/private-cgi/retrieve.pl?type=0&doc=srdb%2F20427&disp
> lay=plain
>


it's this bit of the patch
Step 2. Modify the /etc/default/kbd file, by removing the # from the entry:
#KEYBOARD_ABORT=enable

and changing it to:

KEYBOARD_ABORT=alternate

that actually sets the alternate break, just removing the comment will set it
to the standard break and setting (from memory)
KEYBOARD_ABORT=disable
will disable it completely, you can also use the kbd command to alter it.

NB one thing we were wondering about this is at what level does the standard
break operate, does anyone know if it's handled by something in the solaris
kernel or by something in firmware as we have a minor concern that we might be
losing some functionality by running with this patch.


> _______________________________________________
> users mailing list
> users@conserver.com
> https://www.conserver.com/mailman/listinfo/users

--
Iain Rae Tel:01316505202
Computing Officer JCMB:2148
Division of Informatics
The University of Edinburgh

Yes,

You need a patch and you must hae a sun support agreement to receive that
patch. Call SunSolve and they'll give it to you.


Chris

-----Original Message-----
From: Ernie Oporto [mailto:Ernie.Oporto@viragelogic.com]
Sent: Monday, April 30, 2001 10:05 AM
To: users@conserver.com
Subject: Sun alternate break


Is there a way to set a flag for Sun machines individually that have had
this change made to them...

http://sunsolve.sun.com/private-cgi/retrieve.pl?type=0&doc=srdb%2F20427&disp
lay=plain

_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users

RE: Sun alternate breakWhat I meant was, does applying that patch require
anything special to be done to conserver, or does the Solaris kernel for
that client understand the break from conserver and interpret it correctly?
I didn't want to patch conserver so that all machines it manages now have to
make use of that alternate break. Only one machine might be set up like
that, so that machine should still be "breakable", just not from those
inadvertent disconnects.

Ernie

-----Original Message-----
From: Chris Fowler [mailto:ChrisF@computone.com]
Sent: Monday, April 30, 2001 10:32 AM
To: 'Ernie Oporto'; users@conserver.com
Subject: RE: Sun alternate break


Yes,

You need a patch and you must hae a sun support agreement to receive that
patch. Call SunSolve and they'll give it to you.



Chris

-----Original Message-----
From: Ernie Oporto [mailto:Ernie.Oporto@viragelogic.com]
Sent: Monday, April 30, 2001 10:05 AM
To: users@conserver.com
Subject: Sun alternate break



Is there a way to set a flag for Sun machines individually that have had
this change made to them...


http://sunsolve.sun.com/private-cgi/retrieve.pl?type=0&doc=srdb%2F20427&disp
lay=plain

_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users

Yes, changes will need to be made to Conserver. I recoomend getting a
Terminal Server that does not send a break rather than using one that does.
Many models support that feature.

-----Original Message-----
From: Ernie Oporto [mailto:Ernie.Oporto@viragelogic.com]
Sent: Monday, April 30, 2001 10:33 AM
To: users@conserver.com
Subject: RE: Sun alternate break


What I meant was, does applying that patch require anything special to be
done to conserver, or does the Solaris kernel for that client understand the
break from conserver and interpret it correctly? I didn't want to patch
conserver so that all machines it manages now have to make use of that
alternate break. Only one machine might be set up like that, so that
machine should still be "breakable", just not from those inadvertent
disconnects.

Ernie


-----Original Message-----
From: Chris Fowler [mailto:ChrisF@computone.com]
Sent: Monday, April 30, 2001 10:32 AM
To: 'Ernie Oporto'; users@conserver.com
Subject: RE: Sun alternate break



Yes,

You need a patch and you must hae a sun support agreement to receive that
patch. Call SunSolve and they'll give it to you.


Chris

-----Original Message-----
From: Ernie Oporto [ mailto:Ernie.Oporto@viragelogic.com
<mailto:Ernie.Oporto@viragelogic.com> ]
Sent: Monday, April 30, 2001 10:05 AM
To: users@conserver.com
Subject: Sun alternate break


Is there a way to set a flag for Sun machines individually that have had
this change made to them...

http://sunsolve.sun.com/private-cgi/retrieve.pl?type=0
<http://sunsolve.sun.com/private-cgi/retrieve.pl?type=0&doc=srdb%2F20427&dis
p> &doc=srdb%2F20427&disp
lay=plain

_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users
<https://www.conserver.com/mailman/listinfo/users>

> RE: Sun alternate breakWhat I meant was, does applying that patch require
> anything special to be done to conserver, or does the Solaris kernel for
> that client understand the break from conserver and interpret it correctly?
> I didn't want to patch conserver so that all machines it manages now have to
> make use of that alternate break. Only one machine might be set up like
> that, so that machine should still be "breakable", just not from those
> inadvertent disconnects.
>
any suns which are patched should ignore any breaks sent via the conserver menu
( l1) but will halt if you type ~^b (quickly)at the terminal session. So you
can use it without changing conserver, you just have to remember ~^b.



> Ernie


--
Iain Rae Tel:01316505202
Computing Officer JCMB:2148
Division of Informatics
The University of Edinburgh

At first I thought the break was a stupid idea. I've grown to love that
break and wish that x86 machines supported it. Linux 2.4 with serial 5.05
does
support the break but if the kernel is locked you can not use it. So in a
way, it is not a break at all. The system continues to run after you issue
the break.

Chris


-----Original Message-----
From: Iain Rae [mailto:iainr@dcs.ed.ac.uk]
Sent: Monday, April 30, 2001 10:46 AM
To: users@conserver.com
Subject: Re: Sun alternate break


> RE: Sun alternate breakWhat I meant was, does applying that patch require
> anything special to be done to conserver, or does the Solaris kernel for
> that client understand the break from conserver and interpret it
correctly?
> I didn't want to patch conserver so that all machines it manages now have
to
> make use of that alternate break. Only one machine might be set up like
> that, so that machine should still be "breakable", just not from those
> inadvertent disconnects.
>
any suns which are patched should ignore any breaks sent via the conserver
menu
( l1) but will halt if you type ~^b (quickly)at the terminal session. So you

can use it without changing conserver, you just have to remember ~^b.



> Ernie


--
Iain Rae Tel:01316505202
Computing Officer JCMB:2148
Division of Informatics
The University of Edinburgh


_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users

And one of the things I wanted to do was add an 'l2' escape sequence to send
the <CR>~^b bits for you - it was suggested by a guy at the LISA conference -
good idea, no? The only trick is there's a bit of timing you have to get
right - I think it's a 0.5 second delay between each character, otherwise it
could be a random sequence coming over, say a modem (why put a modem on the
console port - ugh, I can see it being done, but haven't ever done it)
transfering a file. Anyway, you don't really want to "lock up" conserver for a
second or so while it's waiting the prerequisite amount of time...and the
sequence could be changed or different for another device ('l3', 'l4', etc) so
a real multi-threaded or alarm-based or something method needs to be put
together.

In the mean time, just type it by hand. One of these days all these things
will be in the code.

Bryan

Quoting Iain Rae <iainr@dcs.ed.ac.uk>:
> any suns which are patched should ignore any breaks sent via the
> conserver menu
> ( l1) but will halt if you type ~^b (quickly)at the terminal session. So
> you
> can use it without changing conserver, you just have to remember ~^b.