There're some files that refuse to let me delete them within the WINE folder. Have tried everything I imagined would work but they remain fixed in the spot. The scenario is as follows:

<compact flash card = sda1> : <extracted_files = folder/directory> : <wine-1.2.2 = directory> : <dlls = directory> : <cards = directory> , <clusapi = directory> , comcat = file?.

The cards & clusapi directories above aren't empty.

Any ideas as to what to do next? Thanks!

PS. Never got to use WINE anyway.

PSS. Today, the same thing happenned after deleting Firefox from the CFCard where it was residing, a few files refuse to be deleted or moved. By the way, they appear in bright color with a tringle containing a "!" symbol (I hope I'm remembering it correct).

Did you install the programs using the Puppy Package Manager or from a PET package?
If so, you should have been able to remove them by using Puppy Package Manager and clicking on the installed package in the lower window.
Barring that, you could also navigate to /root/.packages/name_of_package opened as a text file.
It gives a list of just what files were in the install.

1 members found this post helpful.

Thanks, 8-bit, for responding!

I'm running PL5.1* from a live cd since I don't have a hdd in this Sony VAIO. Any PET or api that's d/l is put in a CFCard (like FF or Chromium PETs). As far as I can remember WINE was d/l as PET from the repos; but, since it's not persistent, WINE was installed within a folder in the card. The previous argument I think points us to the fact that, when PL starts isn't aware of any of these packages & probably is for this reason the syst. doesn't recognize my 'authority' to perform this task.

Obviously, I can't change any of the configurations that would permit me to perform the deletion. But I still believe there's an option somewhere that would wipe these files mabe by applying 'brute force procedures' (don't want to resort to re-formating the card). I'm in real need of the extra MBs there.

Thanks again. Hope you have enough info now to reply with a hint!

Ok, you have a Sony VAIO that you are using to boot PL from cd and a Cf card for storage.
First, will the Sony burn CDs?
Second, if it will, did you burn the first Puppy CD as multi-session?
The reason I ask is that Puppy can be run from CD with sessions (works like a pupsave file) saved back to the CD and the sessions get loaded along with Puppy on the next boot.
So if you install a Pet package and choose to save to CD on poweroff or reboot, it becomes part of a saved session that is loaded when you run from CD.
Also, depending on the size of the CF, you could have chose the option of creating a pupsave file on it instead and applications and settings could be stored in it and removed if you did not like them.

In the mean time, what would happen if you made a small file in Geany and saved it with the same name as the file you are trying to delete?
The original file would get overwritten and then just delete the new file you made.

Also!!!! Have you tried opening a terminal in the directory those files are in and from the terminal, first type "ls" to list the files.
Then type "rm -f name_of_file". The -f means force.

1 members found this post helpful.

Thanks 8-bit for responding!

Yes, I had performed your last suggestion &, right now, repeated it with the '-f' switch. The result is the same: "rm: cannot remove 'hj.bmp': Operation not permitted". I tried it with another file from the same folder ...with same result.

Later, I tried your first suggestion with Geany & the operation was not permitted: in a popup little window it says <Error saving file. Permission denied>.

As far as I can see it, the situation is as follows:
In linux there're levels of authority; within the regular user acct. you're not permitted many things; for some not permitted things you have to become SU (Super User, or what in other systems is known as Administrator); further authority resides (and it exists) within the kernel itself (correct me if I'm wrong here). For the purpose of eliminating those files I should become 'kernel'.

PS. When I fetch for the properties of those files & folders I find it clicked a box named SUID, which I can't modify.

I found this in a search that may help. It is on unix file permissions.

Set uid and set gid on files

When run Unix executables can use the effective rights of a different user or group. This is shown by having an 's' rather than 'x'. For example:

bash> ls -l /bin/su
-rwsr-xr-x 1 root root 22904 Apr 27 2003 /bin/su

When su is run it runs with the same rights as the user root.

Any program which is suid or sgid must be written very carefully to make sure that it can not be abused by malicious users to do things they shouldn't.
Commands
chmod u+s Set the suid bit
chmod u-s Clear the suid bit
chmod g+s Set the sgid bit
chmod g-s Clear the sgid bit

1 members found this post helpful.

Thanks 8-bit for responding to this! I found difficult to understand your post/instructions. Tried to execute some of those commands but they failed in one of 2 ways: 'operation not permitted' or 'no such file or directory'.

If I'm running PL from a live cd I'm assuming that whenever I open a terminal window I'm already root. Nonetheless, I tried various ways of issuing the 'su' switch at the time of execution but no username I used was recognized as a valid one (tried user, root, my nickname & others with first letter as capital also).

Where can I find a complete list of commands for doing this kind of things?

PS. You mention bash in your post. What should I understand for it instead of another thing?

Thanks!

I have never used the command, but you can find examples of chmod at http://www.thegeekstuff.com/2010/06/...mand-examples/

As I was saying though, I am not a command line unix/linux expert by any means.
This is just what I have found on the web by doing a search.

I hope this last link helps you.

1 members found this post helpful.

8-bit - I seem to have missed something here. How do you know the sticky bit is set in this case?

A standard Puppy only has the root user, so you should be able to delete any file unless:
- the sticky bit is set (IIRC the sticky bit only exists on ext* filesystems, but a CF would be formatted as VFAT unless you reformatted it).
- the filesystem is read-only (I imagine CF cards have a write-protect switch, also it could be simply mounted read-only, possibly automatically due to file system corruption).
- the filesystem is corrupted in certain ways (it would normally be obvious if the problem was due to file system corruption as the rox filer would describe it as something funny or give it a funny icon. You were told how to fix a corrupted filesystem in your thread on the main puppy forum).

Is the sticky bit set?
Do you know what filesystem is on the disk (if there is a desktop icon for the disk it will tell you if you hover your mouse over it)?
I presume you can still create and delete other files on the disk?
Did you try what was suggested in the other forum?

1 members found this post helpful.

disciplepup,


I figured it was set after reading this line "PS. When I fetch for the properties of those files & folders I find it clicked a box named SUID, which I can't modify." in one of Benny's posts.
Maybe my assumption was wrong.

Ah, that's what I missed. Sounds to me like you're interpreting it correctly. Unless the box shows as checked but greyed out when a filesystem doesn't support sticky bits.

I can't think how root could be unable to modify the sticky bit unless the filesystem is read-only or corrupted.

1 members found this post helpful.

Thanks 8-bit & disciplepup for responding!

8-bit, your link proved to be very interesting; never have seen that site before.

disciplepup, you're right when thinking I reformatted the CFCard to ext2. With respect to any 'read-only' switch at formatting time I don't know, but can't remember having set any; even more, at the time I formatted the card setting such a switch would have been a mistake taking into acct. my plans for the card. By the way, I've put some files there afterward & deleted/moved many of them without any problem. The thing is that after d/l WINE I installed it right in the card, never used it & when tried to delete all of it to use the space for other purposes many of the included files were deleted except for those that have proved to be 'STICKED'.

If there're still any doubts I'm attaching a screenshot for you to inspect.

Thanks!

Attached Thumbnails

 

> With respect to any 'read-only' switch at formatting time I don't know

I was actually talking about a physical write-protect switch on the card. I know SD cards have them, but I'm not sure about CF cards. But of course that couldn't be the problem if you can still modify or delete other files on the card.

To create or delete files the directory that contains them (in this case /mnt/mmcblk0p1/extractedfiles/zip/wine-1.2.2/dlls/card) needs to be writeable. Did you check whether it is?

If you display the properties for one of those files, what does it say it is, under "Type:"?

Benny7740,
Try these in order.
1 Boot from the Puppy CD with the typed in option puppy pfix=ram
Go through the initial processes til you get to a desktop.
Your CF card that you say is formatted to ext2 should show on the desktop.
Do NOT mount it yet.
Open a terminal and type "e2fsck -y /dev/[name of device as shown on desktop]
An example would be "e2fsck -y /dev/sdb1"
If it then reports the partition as clean, you can proceed to try again to delete those files.
Just click on the desktop icon for that device to mount it and it should display in rox file manager.

1 members found this post helpful.

Thanks 8-bit, excellent approach! Just the kind of command I like! Yes, it seems to be a 'brute force' approach but, under my circumstances, it was precisely what I needed...

After running the command (I was reading your suggestion with FF running from the said CFCard, so I copied the web-addrss's to a newly opened session with Midori, stopped what I was doing from FF & closed it, then unmounted the card & ran the magic command) I verified that all that I needed to delete from the card was deletable (and, infact, deleted those files). All that I've to check now is if, at least my FF there, is still usable. In that case I'm login in again & see how I cam add a SOLVED 'sticker' somewhere around here.

Thanks again for your help!

PS. Disciplepup, check my post #12 above (attachment).