lsattr: Operation not supported While reading flags
 

When running lsattr, I get

The file is a symlink, or your filesystem doesn't support file attributes.

Under Slacko, lsattr is a built in program.

No symlink involved.

What does "does not support file attributes" mean ?

You can run tune2fs -l /dev/sdXX to see features, mount command will tell what is in effect.

OK, some questions.

. Why, if this question refers to Slacko, is it in the non-*nix section?

. Why, if you're using Slacko, did you not mention this in the opening post or the thread title?

. Which folder or file is this not working on? Does it work on any folders/files on your system?

. Why didn't you try Google or similar?

lsattr puppy slacko

produces this as the first hit:

http://www.murga-linux.com/puppy/vie...cd485712fe2f7b

You must not read people's sig. My O.S. is in it !

How do you know I did not use google ?

You make a lot of assumptions.

Fact is, I used yahoo advanced search.

And no, it does not work on ANY folder.

:-) Linux Puppy is not "non-*NIX", well the last time I checked anyway. ;)

I made the assumption that you didn't use Google or equivalent because in a very short while I was able to find relevant information, and I know next to nothing about Puppy. I was very surprised you hadn't been able to. You should perhaps think about dropping Yahoo as your search engine of choice.

Anyway, the Puppy Linux forum I linked to appears to show that it's a recognised problem. I would suggest that you join that discussion, chase them up, and find out what the problem is, whether there are any workarounds, and how long it might to fix.

Good luck, and let us know if you resolve the problem.

Does anyone actually read sigs? Really? I don't have the time or patience to bother with them.

I used to read them until I realised that people were just putting all sorts of nonsense there such as non-existent places ("Baja Oklahoma" for example).

But seriously, yes I do, if the question is related to the distro and/or DE. I find them pretty useful. In the case of the OP, I thought that the fact that his Puppy Linux is Slacko should have been in the sig, thread title or opening post because that actually might make a difference to the problem and solution. However, I might have been splitting hairs on that one. ;)

It appears aufs does not support ext* extended attributes.

These are really not ext* extended attributes, other filesystems have them, too. Just not aufs.

To nitpick more, Baja Oklahoma is not in my sig. I don't have a signature. The stuff on the left, under the username, is from the user profile. The sig(nature) is at the bottom of the post. FWIW, not a lot really. Neither is necessarily accurate.

Ha ha. I know, but the OP erroneously used the word "sig" to refer to his user profile info, so I just assumed you were talking in his "language" when you asked whether anyone looked at sigs any more, and I carried on in that vein.

What a tangled web we weave... ;)

Edit: It turns out that I had the viewing of signatures turned off, so the OP was completely correct. As was sgosnell. May I declare here, for the benefit of these guys and for anyone reading this, that I is an idiot. :)

The OP does have a sig at the bottom of his posts, which actually gives more info than the data on the left. I hadn't bothered to read it, though, and I doubt most visitors do, either. As you don't seem to have... :)

Is it possible to have the reading of sigs turned off, or these to be blocked somehow in Firefox? Because to be perfectly honest, I'm reading the thread now and I don't see any sigs on any of the posts in the thread. Weird!

Edit: Well I never. I had a setting in Thread Display Options set to not show me any signatures on the posts. :-D

I've set it to show me them now so I don't get caught out again. ;)