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.
Perhaps unSpawn asked the OP (Original Poster) that is you, to execute that command in response to post number 107, I am not very sure though, lets see if he sheds some light on it.
Yeah I did. Given the null result there's no ~/.wgetrc. NP.
unSpawn - it sure seems that I do have a problem with handles. Sorry about that. But then Shawn is quite a nice name - It's got to be better than "Dead Dog"
Quote:
The force, weak in you, is. A problem, you have, typing peoples handles correctly ;-p
Yeah I did. Given the null result there's no ~/.wgetrc. NP.
Now if that name problem happens again, I know what to look for, thanks to you.
But I would still like to know : How to make sure that "wget" saves the file with a proper name ALWAYS and what must be the cause behind "wget"'s improper behavior in this particular case ?
Last edited by Aquarius_Girl; 10-18-2010 at 08:26 PM.
How to make sure that "wget" saves the file with a proper name ALWAYS and what must be the cause behind "wget"'s improper behavior in this particular case ?
That link clearly states that if the url which we are using for downloading has got something like this at the end : wget -c http://www.example.com/somepage.html?foo=bar
Then wget will save the file with the name: "somepage.html?foo=bar"
as it did in our case where we used a mirror at the end :
Which means to me that if I HAD LOOKED at the code ending when I had
downloaded that file it would have told me under what name it had been
saved.
I don't follow all of this, but I think I get the idea.
It's early where you are but its sleep time here. So I'll say sleep well and
prosper
Yes! you are quite right, I just haven't looked at it properly. The reason being I had thought the post was intentioned as a part question yet fact for unSpawn Therefore I will now look at it more closely and if I have specific questions I will address them to this thread.
I've just noticed that my 1st post sat by itself for 4 weeks before you came across it - so actually it took 3 weeks to work through the problem not 7 weeks as I have stated in a previous post. You were right in renaming the thread and my comments about titles in another thread you helped out in - were totally incorrect. I hate being wrong, but what I hate even more is not admitting it when one is wrong :-/
What gets directly executed on the terminal is called a command.
Example:
Code:
anisha@linux-uitj:~> ls -la
Code is something which we write (mostly in a text editor) and then compile it using some command.
Following is an example of a C code written in a file named helloo.c
Code:
#include <stdio.h>
int main ()
{
int x = 10;
return 0;
}
and to compile it I use a command named gcc:
Code:
anisha@linux-uitj:~> gcc helloo.c
If you call a command, code, repeatedly, people may not understand what you are talking about !
Like you said in the other post of yours that you have tried all codes I wrote for gparted...I couldn't make out which codes you were referring to, since I had not written any !
Later I realized that you were referring to website links as codes :-/
Point taken and understood: Not very bright I'm afraid, I've been known to get peoples names wrong as well
But I think I am following your command structure OK, and the reasons for it. I'll lay it out line line for you shortly, so you can make sure I have it right.
Why then do we encase it in a frame and label the frame with the word "code" as above ?
Because the owner of the site has perhaps decided that CODE tags are sufficient to enclose codes, commands, outputs, warning/error messages etc. and left it to the users to refer to the same using some discretion on their own.
and I don't have any problems neither I am concerned with whichever way you choose to refer to things. I thought it was my duty to make you aware of LQ atticates that's why I wrote the above post. I think this thread has reached its end now.
Because the owner of the site has perhaps decided that CODE tags are sufficient to enclose codes, commands, outputs, warning/error messages etc. and left it to the users to refer to the same using some discretion on their own.
and I don't have any problems neither I am concerned with whichever way you choose to refer to things. I thought it was my duty to make you aware of LQ atticates that's why I wrote the above post. I think this thread has reached its end now.
OUCH! I had already answered that I understood what you meant and that I would in future use the word commands This was only an afterthought question, which you have explained well. It was good that you felt duty bound--- The End of this thread!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.