Re: [arch-general] Holy Cow -- What happened to bash / vi??

2009-06-23 Thread Gerardo Exequiel Pozzi
Gerardo Exequiel Pozzi wrote: > David C. Rankin wrote: > > > >> I get this new message: >> >> [00:08 archangel:/etc] # noc fstab >> bash: /usr/local/bin/noc: /bin/bash: bad interpreter: Text file busy >> >> >> > > >> Text file busy?? It's a text file, it's not busy, it's e

Re: [arch-general] Holy Cow -- What happened to bash / vi??

2009-06-22 Thread Gerardo Exequiel Pozzi
David C. Rankin wrote: > I get this new message: > > [00:08 archangel:/etc] # noc fstab > bash: /usr/local/bin/noc: /bin/bash: bad interpreter: Text file busy > > > Text file busy?? It's a text file, it's not busy, it's either saved or > you > get what was present the last time

Re: [arch-general] Holy Cow -- What happened to bash / vi??

2009-06-22 Thread Andrei Thorp
Excerpts from Aaron Griffin's message of Mon Jun 22 12:27:01 -0400 2009: > On Mon, Jun 22, 2009 at 7:02 AM, Daenyth Blank wrote: > > On Mon, Jun 22, 2009 at 07:47, Loui Chang wrote: > >> On Mon 22 Jun 2009 03:09 -0500, David C. Rankin wrote: > >>> I will downgrade vi. If that is what the future of

Re: [arch-general] Holy Cow -- What happened to bash / vi??

2009-06-22 Thread Aaron Griffin
On Mon, Jun 22, 2009 at 7:02 AM, Daenyth Blank wrote: > On Mon, Jun 22, 2009 at 07:47, Loui Chang wrote: >> On Mon 22 Jun 2009 03:09 -0500, David C. Rankin wrote: >>> I will downgrade vi. If that is what the future of vi looks like, I >>> don't want any part of it. Changes that dramatic ought to be

Re: [arch-general] Holy Cow -- What happened to bash / vi??

2009-06-22 Thread Dieter Plaetinck
On Mon, 22 Jun 2009 08:02:43 -0400 Daenyth Blank wrote: > On Mon, Jun 22, 2009 at 07:47, Loui Chang wrote: > > On Mon 22 Jun 2009 03:09 -0500, David C. Rankin wrote: > >> I will downgrade vi. If that is what the future of vi looks like, I > >> don't want any part of it. Changes that dramatic ough

Re: [arch-general] Holy Cow -- What happened to bash / vi??

2009-06-22 Thread Daenyth Blank
On Mon, Jun 22, 2009 at 07:47, Loui Chang wrote: > On Mon 22 Jun 2009 03:09 -0500, David C. Rankin wrote: >> I will downgrade vi. If that is what the future of vi looks like, I >> don't want any part of it. Changes that dramatic ought to be forked. > > You were previously using vim named 'vi'. > Th

Re: [arch-general] Holy Cow -- What happened to bash / vi??

2009-06-22 Thread Loui Chang
On Mon 22 Jun 2009 03:09 -0500, David C. Rankin wrote: > I will downgrade vi. If that is what the future of vi looks like, I > don't want any part of it. Changes that dramatic ought to be forked. You were previously using vim named 'vi'. The new one is actually a fork of vi called nvi.

Re: [arch-general] Holy Cow -- What happened to bash / vi??

2009-06-22 Thread David C. Rankin
On Monday 22 June 2009 12:42:18 am Grigorios Bouzakis wrote: > On Mon, Jun 22, 2009 at 8:26 AM, David C. Rankin < > > drankina...@suddenlinkmail.com> wrote: > > Listmates, > > > >I updated to [testing] and now I am having strange behavior from > > ... > > Any p

Re: [arch-general] Holy Cow -- What happened to bash / vi??

2009-06-21 Thread Grigorios Bouzakis
On Mon, Jun 22, 2009 at 8:26 AM, David C. Rankin < drankina...@suddenlinkmail.com> wrote: > Listmates, > >I updated to [testing] and now I am having strange behavior from > ... > Any partiular reason you did that? Its likely BOTH vi and bash are to blame as

[arch-general] Holy Cow -- What happened to bash / vi??

2009-06-21 Thread David C. Rankin
Listmates, I updated to [testing] and now I am having strange behavior from either bash or vi. (the new vi has many issues, but ignoring those for the moment) I have one of my simple parse scripts open in vi in one console window and I make a few changes to a sed expression, then :w to