hej harald,
> So for me it doesn't look anything wrong. Editor shows read only
> mode, so if you try to change something, you need to write to a
> different file. If necessary the resulting file can then be
> renamed/moved to the name of the original file.
let sleeping dogs lie.
greets,
manuel
_
Hi Manuel !
>you already have that improvement as mentioned above.
Thx for the information. I did not know about this, as I'm not a vi
user.
So for me it doesn't look anything wrong. Editor shows read only
mode, so if you try to change something, you need to write to a
different file. If necess
hej harald,
> >vim shows a red "warning: file is in read only mode!" when i open it.
> >busybox vi shows no warning at all.
so the "[Readonly] 1/1 100%" sign right of the filename is "no warning
at all" for you john? the question is: what version of busybox are you
using? on current master it wor
>
> I have built Busybox v1.19.4 with Buildroot for my target device and added
> the sendmail command.
>
> The problem is that I am not allowed to tell sendmail to stop getting data
> from stdin and finally send the email.
>
> I have tried in the following ways:
>
> 1. sendmail -f f...@domain.com -
On Thu, Oct 11, 2012 at 06:00:22AM +0200, Harald Becker wrote:
> Hi Rich !
>
> >Of course this also has down-sides, such as losing extended attributes
> >and other file properties the application is not aware of, and not
> >being able to preserve ownership. That's why most programs by default
> >d
Hi Rich !
>Of course this also has down-sides, such as losing extended attributes
>and other file properties the application is not aware of, and not
>being able to preserve ownership. That's why most programs by default
>do what busybox vi is doing.
... and not being able to write to special fil
On Thu, Oct 11, 2012 at 03:16:28AM +0200, Harald Becker wrote:
> Hi Jim !
>
> >Normally, in an editor, you do NOT do this. Consider what happens
> >if, behind the scenes, somebody did an "rm file". Your hours of
> >typing would go into a still-open file, to an anonymous inode, and
> >then quietl
Original Message
Subject: Re: [BUG] vi does not recognize changed permissions on read
only files
Date: Wed, 10 Oct 2012 20:50:07 -0400
From: Doug Clapp
Reply-To: doug.clapp1...@alumni.unc.edu
To: Manuel Zerpies
Manuel Zerpies wrote:
hej john,
i edited l
Hi Jim !
>Normally, in an editor, you do NOT do this. Consider what happens
>if, behind the scenes, somebody did an "rm file". Your hours of
>typing would go into a still-open file, to an anonymous inode, and
>then quietly disappear.
... which I call correct behavior! If someone removed the fil
>This is wrong. Normally you keep the file descriptor open, then
>rewind/seek to the beginning of the file and write the new content.
>That way the system overhead for file reopen is avoided.
Normally, in an editor, you do NOT do this. Consider what happens
if, behind the scenes, somebody did an
Hi John !
>vim shows a red "warning: file is in read only mode!" when i open it.
>busybox vi shows no warning at all.
This may be a possible improvement. Busybox vi could display a
message, when the file is opened in read-only mode.
>you could type a long long letter for hours, and when you want
On 10/10/2012 11:29 PM, Manuel Zerpies wrote:
hej john,
i edited less-444/configure, and when i wanted to :wq vi claimed:
"file is read-only".
so i changed the perms in another shell to 755.
retrying :wq yielded the same error again.
after closing vi with :q! and opening it again, i was able
hej john,
> i edited less-444/configure, and when i wanted to :wq vi claimed:
> "file is read-only".
>
> so i changed the perms in another shell to 755.
> retrying :wq yielded the same error again.
>
> after closing vi with :q! and opening it again, i was able to save it.
>
> i had to redo all
i edited less-444/configure, and when i wanted to :wq vi claimed: "file
is read-only".
so i changed the perms in another shell to 755.
retrying :wq yielded the same error again.
after closing vi with :q! and opening it again, i was able to save it.
i had to redo all previous changes of course.
I reproduced it.
Unfortunately, since I don't understand ash.c code fully,
the fix won't be easy.
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
On 10/10/2012 03:56 AM, walter harms wrote:
Am 09.10.2012 23:08, schrieb Jon Tollefson:
I have an ash script that I have stripped down to its simplest form
below that still exhibits the behavior. While the script is running
under busybox I look at 'top' output in another window and see the RE
stat can be useful on non-Linux platforms if filesystem support is
turned off.
Signed-off-by: Ron Yorston
---
coreutils/Config.src | 10 +-
coreutils/stat.c | 21 +
2 files changed, 26 insertions(+), 5 deletions(-)
diff --git a/coreutils/Config.src b/coreutil
On 10.10.2012 12:56, walter harms wrote:
> Am 09.10.2012 23:08, schrieb Jon Tollefson:
>> I have an ash script that I have stripped down to its simplest form
>> below that still exhibits the behavior. While the script is running
>> under busybox I look at 'top' output in another window and see the
Am 09.10.2012 23:08, schrieb Jon Tollefson:
> I have an ash script that I have stripped down to its simplest form
> below that still exhibits the behavior. While the script is running
> under busybox I look at 'top' output in another window and see the RES
> column for busybox slowly increasing.
19 matches
Mail list logo
