[bug #21528] Please support IPv6

2007-11-06 Thread Laurent Bigonville
URL: Summary: Please support IPv6 Project: GNU Midnight Commander Submitted by: bigon Submitted on: mardi 06.11.2007 à 22:14 Category: VFS Severity: 3 - Normal

[bug #21524] Dangerous unpacking (disk full is not reported, unpacked files become corrupt)

2007-11-06 Thread Pavel Tsekov
Follow-up Comment #6, bug #21524 (project mc): Ok. According to the bash manual: [...] A failure to open or create a file causes the redirection to fail. [...] Unfortunately failure to write is not detected :( So, yes - this method is unsafe.

[bug #21524] Dangerous unpacking (disk full is not reported, unpacked files become corrupt)

2007-11-06 Thread Nagy Gabor
Follow-up Comment #5, bug #21524 (project mc): [EMAIL PROTECTED]:~$ df -h /dev/sda8 950M 869M 34M 97% /tmp [EMAIL PROTECTED]:~$ dd if=/dev/zero bs=50M of=./bigfile count=1 [EMAIL PROTECTED]:~$ zip a 1.zip bigfile _Then_ I starts mc, I press enter on 1.zip, and I try to copy out b

[bug #21524] Dangerous unpacking (disk full is not reported, unpacked files become corrupt)

2007-11-06 Thread Pavel Tsekov
Follow-up Comment #4, bug #21524 (project mc): I did not try a disk full on /tmp but I rather forget the temporary file name to point to a file writable by root which produces Permission denied error - but there should be no difference. ___

[bug #21524] Dangerous unpacking (disk full is not reported, unpacked files become corrupt)

2007-11-06 Thread Pavel Tsekov
Follow-up Comment #3, bug #21524 (project mc): Well, I took the time to try and reproduce an error condition while extracting an archive entry into tmp (i.e. copyout). The copyout action reports the error and MC captures it and displays it in a red dialog box. I don't know what caused the data co

[bug #21524] Dangerous unpacking (disk full is not reported, unpacked files become corrupt)

2007-11-06 Thread Nagy Gabor
Follow-up Comment #2, bug #21524 (project mc): Well. I'm not really familiar in perl. But as your example shows, here obviously _bash_ reports the error instead of unzip. If you modify the script to detect bash errors too, that would be OK. But imho unzip's disk-full detection is much better, bec

[bug #21524] Dangerous unpacking (disk full is not reported, unpacked files become corrupt)

2007-11-06 Thread Pavel Tsekov
Follow-up Comment #1, bug #21524 (project mc): Are you sure ? [EMAIL PROTECTED] Desktop]$ unzip -p bless-bin-0.5.0.zip bless-bin-0.5.0/NEWS > /bin/mv bash: /bin/mv: Permission denied [EMAIL PROTECTED] Desktop]$ echo $? 1 So errors are reported. Maybe the return status is not checked properly

[bug #21524] Dangerous unpacking (disk full is not reported, unpacked files become corrupt)

2007-11-06 Thread Nagy Gabor
URL: Summary: Dangerous unpacking (disk full is not reported, unpacked files become corrupt) Project: GNU Midnight Commander Submitted by: ngaba Submitted on: Tuesday 11/06/2007 at 12:45