Oberon Community Platform Forum
December 13, 2019, 04:04:16 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
   Home   Help Search Login Register  
Pages: [1]
Author Topic: A lost+found bug which breaks Find.Panel, and a solution.  (Read 3508 times)
Full Member
Posts: 100

« on: November 09, 2013, 09:54:41 PM »

A filesystem on a volume on a removable store is feasible and useful.  Therefore a UnixAos working directory on a removable volume is a significant possibility.

Normally an ext filesystem contains a directory named lost+found in the root directory.  If the UnixAos working directory is on a removable volume, it will contain a lost+found directory.  When the Find.Panel is used to search in the working directory,  Files.Old("lost+found") will freeze the system.  My initial solution is to add a condition in BrowseFile.
    IF filename = "./lost+found" THEN RETURN END;

Then in the Find.Panel, searches in lo*, in ./lo* and in ./* work.  Provided "lost+found" is not a parameter of Domain, Find.All has no problem.

lost+found might cause a problem in another module.  Can the solution be in Files and be generalized to cover any subdirectory?  Haven't tackled that yet.

Regards,               ... Peter E.
« Last Edit: November 11, 2013, 06:05:39 PM by peasthope » Logged
Pages: [1]
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!