Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Distribution: RedHat 9.0 / Slackware 9.0/ FreeBSD 4.8 / Solaris 8 x86 / Mandrake 9.0
Posts: 90
Rep:
Unlocatable unzipped file
Hi,
I've entered this into the terminal:
unzip -v filename.zip
and unzip extracts the file but it does not say where it is extracting it to. I looked into the current directory and it did not unzip there. When I try to specify a directory unzip doesn't do anything. Can anyone tell me where it has been unzipped to?
Try 'which foo' maybe, or 'updatedb' and 'locate foo' - or, if it's large and you know about what 'du' should produce, do 'du' and look for what's expanded.
Or, just fire up a file manager and do a lot of wandering around in directories. If it's a binary some of it should have ended up in bin, of course - which bin might be a question, depending on the type of app.
And it's possible it just disappeared. *g* Stuff should untar - and unzip, I guess - in a new subdirectory in the same directory as the compressed file. Or, rather, it should unzip to the directory you're running the command from which, based on your quote, was the same as the zip.
Um, and of course, if this was on a mounted floppy none of the above except maybe du will work because it'll be on the floppy. And if it was from a mounted cdrom it should have given an error but might have exited silently - it would have unzipped to RAM but not written anything.
Distribution: RedHat 9.0 / Slackware 9.0/ FreeBSD 4.8 / Solaris 8 x86 / Mandrake 9.0
Posts: 90
Original Poster
Rep:
God, I must look so stupid! Thanks aizkorri, I just typed in that unzip with no options and it worked(This took me hours to do)! In my weaker moments I want to go back to Windoze!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.