Hallo Dylan, op 25-08-14 19:43 schreef je:

On 25/08/14 18:27, Mark Ballard wrote:

...

64Gb HD flash drive 3 x size of internal HD partition used to run o/s.

Attempt to delete files on flash causes error: trash full.

Assuming you are using KDE4.x ... SHIFT-Delete will delete immediately without going to Trash

And uncheck "limit size to". (Dolphin, prefs or simular) Harrie -- Harrie Baken | Tekstbureau TekstBaken Copy-editing - proofreading (Dutch) http://www.tekstbaken.nl/ Registered Linux user #366560 | openSUSE 13.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 08/25/2014 01:33 PM, John Andersen wrote:

On 8/25/2014 10:43 AM, Dylan wrote:

...

On 25/08/14 18:27, Mark Ballard wrote:

...

64Gb HD flash drive 3 x size of internal HD partition used to run o/s.

Attempt to delete files on flash causes error: trash full. Assuming you are using KDE4.x ... SHIFT-Delete will delete immediately without going to Trash

Dx

That doesn't necessarily solve the whole problem though, because it can still leave your trash in a state of being plugged to the point that no subsequent move-to-trash operations work, and you have to manually dig around and find your trash directory to delete the contents and erase the file that has the "its full" setting.

I've had this happen on KDE4 many times, and I have a hints file that in my "closet of horrors" directory that tells me how to fix it. There is even a bug report on it somewhere, but I'm not in a position to look it up right now.

In the top left portion of my Dolphin window it shows: Home, Network, Root and Trash. Right click on <Trash> and choose "Empty Trash". It is the top choice in my context box. If I remember right is asks conformation. Give it permission to dump the trash and it's gone and you now have a nice empty trash to fill up again. -- Those who expect to reap the blessings of freedom must. like men, undergo the fatigue of supporting it.-Thomas Paine _ _... ..._ _ _._ ._ ..... ._.. ... .._ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

I don't know you or how you use your computer. I admit that. But over my years learning to use Linux I have seen a great number of, I shall call them "Old Timers" for lack of a better term, that have used Linux from the very beginning and are used to doing everything on the command line. There is nothing wrong with that but it often leads to them overlooking the simplest manner of doing something. Things such as emptying the trash. On 08/26/2014 10:24 AM, John Andersen wrote:

Chuckle. If it was that simple, I wouldn't have posted Billie. I was born in the morning, but not yesterday morning.

On August 25, 2014 11:41:48 AM PDT, Billie Walsh wrote:

...

On 08/25/2014 01:33 PM, John Andersen wrote:

...

On 8/25/2014 10:43 AM, Dylan wrote:

...

On 25/08/14 18:27, Mark Ballard wrote:

...

64Gb HD flash drive 3 x size of internal HD partition used to run o/s. Attempt to delete files on flash causes error: trash full. Assuming you are using KDE4.x ... SHIFT-Delete will delete immediately without going to Trash Dx

That doesn't necessarily solve the whole problem though, because it can still leave your trash in a state of being plugged to the point that no subsequent move-to-trash operations work, and you have to manually dig around and find your trash directory to delete the contents and erase the file that has the "its full" setting.

I've had this happen on KDE4 many times, and I have a hints file that in my "closet of horrors" directory that tells me how to fix it. There is even a bug report on it somewhere, but I'm not in a position to look it up right now.

In the top left portion of my Dolphin window it shows: Home, Network, Root and Trash. Right click on <Trash> and choose "Empty Trash". It is the top choice in my context box. If I remember right is asks conformation. Give it permission to dump the trash and it's gone and you now have a nice empty trash to fill up again.

--

Those who expect to reap the blessings of freedom must. like men, undergo the fatigue of supporting it.-Thomas Paine

_ _... ..._ _ _._ ._ ..... ._.. ... .._

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- Those who expect to reap the blessings of freedom must. like men, undergo the fatigue of supporting it.-Thomas Paine _ _... ..._ _ _._ ._ ..... ._.. ... .._ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-08-26 11:46 (GMT+0200) jdd composed:

Dirk Gently composed:

...

rm doesn't run out of space.

sometime rm needs some tweeks, when deleting files with zero in the name occur, usually using some * or ? solves the problem (I have some such files in my archives that come from time to time, mostly utf8 from/to iso failed conversions)

In OFMs I've ever used, delete always means delete, and they have no problem with whitespace or most (all?) special characters when deleting. This thread's OP is precisely why I rarely use GUI file management tools - when I delete something I want the space it took recovered right when I choose to delete, not as a result of some obtuse future activity that may depend on what DE I am or was in when a "delete" is or was selected. Whether GUI is running and in use or not, my file management chores get done in an OFM, which on Linux means either Midnight Commander or File Commander/L. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-08-26 13:39 (GMT+0200) jdd composed:

Felix Miata wrote:

...

which on Linux means either Midnight Commander or File Commander/L.

I mostly use dolphin with upper case key->delete, no trash can

Hardly the only reason I only use OFMs. A small sample of others: 1-configurable to not require delete/copy/move operation confirmation 2-built in view access to archive files, including editing of content in place 3-works (essentially, subject to bugs) the same regardless of distro or DE 4-configurable location hotkeys 5-integral (s)ftp/smb access 6-doesn't require X 7-intuitive built-in editor 8-configurable to use favorite other text editors 9-shell cmdline integration (optional use of cmdline at any time) 10-*no* *mouse* *required* for seriously fast, easy task completion http://www.softpanorama.org/OFM/Paradigm/index.shtml http://en.wikipedia.org/wiki/Orthodox_file_manager#Orthodox_file_managers https://www.midnight-commander.org/ -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 26/08/2014 19:40, Dirk Gently a écrit :

jdd wrote:

...

Le 25/08/2014 21:24, Dirk Gently a écrit :

...

rm doesn't run out of space.

sometime rm needs some tweeks, when deleting files with zero in the name occur, usually using some * or ? solves the problem (I have some such files in my archives that come from time to time, mostly utf8 from/to iso failed conversions)

Considering that filenames are null-terminated, how do you bury a null inside a filename?

don't know. I sometime have a black square in place of some random character in the filename and this makes it unusable - impossible to mv, rename... only rm except with some joker like * or ? being unable to manipulate the file, I can only guess why. My best guess is that some unicode chars failed to translate. usually the problem come with mp3 names being taken from song title name or ntfs to/from unix translation all what I know for sure is that rm do not remove them jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-08-26 16:42 (GMT-0400) Patrick Shanahan composed:

And now

Dejavu 11:59 ago: http://lists.opensuse.org/opensuse/2014-08/msg00740.html

is time for the "cure all"(tm!) mc *can* do it. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 27/08/2014 06:05, Dirk Gently a écrit :

If you come across one of those again, try this:

ls | od -c

and you will see the bizarro characters that got embedded in your file name.

will try this :-) thanks jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 08/27/2014 01:40 PM, Anton Aylward wrote:

I do know from experience that it works for embedded nulls

(Binary) nulls are definitely not possible in file names - Dirk mentioned that already. File names can consist of *any* character except the directory separator ('/' on Linux), and the binary Null (because that is the string termination character). I.e., a file name can very well include unusual characters like a newline character, or any other binary or otherwise non-printable character. The problem for passing such names to command line tools like rm arises when your keyboard doesn't have a key for it. E.g. my keyboards don't have German umlauts, but hitting TAB to trigger bash's tab-completion feature helps in most of the cases. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 08/27/2014 03:19 PM, Anton Aylward wrote:

The real problem arises when file systems get corrupt and things walk over the inode. That's why we have FSCK. Yes, this was worse in the days of the V7 FS and even the later 20th century file systems where the inode space was separate from the data space. The V7 file system was the limiting case of that! With b-tree based FS the distinction either no longer exists or is very fuzzy.

But an intermediate problem is when the file-that-is-the-directory gets corrupted. Plonk random characters in that and who knows.

Essentially the structure used by readdir has the name and inode. The name_should_ be null terminated. If the directory entry gets corrupted in just the right way, that is the name gets hit rather than the inode field or one of the other supported fields then we have the oddity that the record size and the name length don't match. Yes its a YMMV situation, but I've BTDT. Often you recognise it by very weird 'ls' listings or names you know getting truncated.

yes, that's bad. In such a situation I'd hopefully not try to remove such a file, but rather copy as much as I can into a fresh file system, and then care about those oddities there instead of touching the original, corrupted file system. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

jdd wrote:

Le 26/08/2014 19:40, Dirk Gently a écrit :

...

jdd wrote:

...

Le 25/08/2014 21:24, Dirk Gently a écrit :

...

rm doesn't run out of space.

sometime rm needs some tweeks, when deleting files with zero in the name occur, usually using some * or ? solves the problem (I have some such files in my archives that come from time to time, mostly utf8 from/to iso failed conversions)

Considering that filenames are null-terminated, how do you bury a null inside a filename?

don't know. I sometime have a black square in place of some random character in the filename and this makes it unusable - impossible to mv, rename... only rm except with some joker like * or ?

personally, I would open Konqueror or Dolphin, and use the rename function (F2)

being unable to manipulate the file, I can only guess why. My best guess is that some unicode chars failed to translate.

usually the problem come with mp3 names being taken from song title name or ntfs to/from unix translation

all what I know for sure is that rm do not remove them

It does when you put wildcards in the correct spot, OR use ls | od -c to figure out the control character Or you could even do something like You can also use the -v flag with rm there's many ways of skinning this cat...

jdd

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 08/26/2014 10:32 PM, jdd wrote:

don't know. I sometime have a black square in place of some random character in the filename and this makes it unusable - impossible to mv, rename... only rm except with some joker like * or ?

If it's in the middle, then chance are you can get its name with bash's TAB completion. Just start the with the first characters of the file name and hit TAB. The shell will automatically complete the file name or propose the alternatives if the already typed part is not yet unambiguous. Or if it's at the beginning, then type "rm ./*other-part*" followed by a TAB; again the shell will do the pattern matching immediately, so you see what would be executed (before hitting enter). Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org