Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I tried recursively removing an entire folder, sub-folders, and files on one of my partitions. the command i used was rm -rdf /mnt/mypartition/myfolder
this removed ALL files as i wanted. however it only removed say 95% of folders. i still have a directory tree of folders left over that will not remove. I cannot say what these folders have in common, other than the terminal just wont give up on the notion that they are "non-empty" directories
checking a folder with ls -al reveals no files that i can see. am I missing something? how can i forcefully delete these so called "non-empty" folders? rmdir and unlink also will not work.
You might try "rm -vri" on a small portion of this zombie tree. It will prompt you before every attempted deletion, and perhaps give a little bit more information about why it is not deleting it.
there are no other file systems mounted in the dir tree
upon checking, the fs type is NTFS. is there any way to check ntfs from within linux or do i need to remove this drive and put it into a windows machine to run chkdsk?
i dont think this is due to corruption but i'm not ruling it out. i actually copied over this directory tree from a different drive (ext2) so i could format the other drive, and then replaced the data. the data was on this ntfs partition for maybe a week or two before i copied it all back. when i went to remove the data from this temporary ntfs partition was when this 'non-empty' directory error occured.
according to slapt-get, my ntfs-3g is up to date. i dont believe it though, so i downloaded the 2009.4.4 sources as you said
but now i get an error when trying to compile:
Code:
administrator:$ ./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.
i tried configure as root as well, no luck. i have compiled other programs on this system with no problems before. the config.log was not helpful to me, but i can post if needed.
Distribution: approximately NixOS (http://nixos.org)
Posts: 1,900
Rep:
So you have /usr/lib/libc.so.5 ? Usually the only libc is /lib/libc.so.6 . Try to find out what package installs the file.. Also, what does "file /usr/lib/lib.so.6" print?
i think what you're seeing on that line is a semicolon ":" and not a period "." with "libc.so:5: parse error" ??
"file /usr/lib/lib.so.6" prints no file or directory. neither does lib.so.5 or libc.so.6 or 5.
however, "file /usr/lib/libc.so" prints: ASCII C program text
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.