Excellent!
On Sat, 16 Jun 2001, Klaus Reinhardt wrote:
> Date: Sat, 16 Jun 2001 09:45:41 +0200
> From: Klaus Reinhardt <[EMAIL PROTECTED]>
> To: Tom Oehser <[EMAIL PROTECTED]>
> Subject: Re: [tomsrtbt] splitvt-problem
>
> Hi!
> Problem solved:
> ln ash csh
> then I can do
> splitvt -login -upper ile -lower ile
> K@Rdt
> ----------------- mailto:[EMAIL PROTECTED] !end! -------------------
>
> 09.06.01 14:07:27, Tom Oehser <[EMAIL PROTECTED]> wrote:
>
> >Well, I guess, what I want to make sure you understand, is that I have
> >made the judgement that all of these things are automatically secondary
> >given the rescue/recovery focus of tomsrtbt- it isn't generally something
> >that you are using long enough to care about split terminals or even about
> >command line history- rather, you use it long enough to get your 'real'
> >system back up and functioning. So, these issues do go into the file of
> >things I would like to work better- but, they go *way* down towards the
> >bottom of the stack, since I have so many things that more directly affect
> >whether it even works in many situations. -Tom
> >
> >On Sat, 9 Jun 2001, Klaus Reinhardt wrote:
> >
> >> Date: Sat, 09 Jun 2001 18:35:48 +0200
> >> From: Klaus Reinhardt <[EMAIL PROTECTED]>
> >> To: Tom Oehser <[EMAIL PROTECTED]>
> >> Subject: Re: [tomsrtbt] splitvt-problem
> >>
> >> ----------------- mailto:[EMAIL PROTECTED] start -------------------
> >> Hi
> >>
> >> Device problem solved by hard-linking in TRB:/dev
> >> ?typ? => ?tya?
> >> 'cause splitvt is searching ptya? and ttya? master-slave-
> >> pair.
> >>
> >> It remains the problem with command-line-editing,
> >> cause ile is active (ps!) but not working (without further
> >> error messages); this on IBM with 8 MB and COMPAQ
> >> with 32 MB.
> >>
> >> Source 'experiments' with splitvt.c and ile.c aren't
> >> crowned with success..
> >>
> >> On the other hand. IF I change the passwd from my
> >> 'big linux' to invoke ash, there are the same problems:
> >> After ile:
> >> <cur>+<up> gives ^A (or so) and not the last executed
> >> command.
>
>
