On Mon, Jan 25, 2021 at 03:47:03PM -0500, Gene Heskett wrote: > > 1) You have a shell function or alias that overrides the wget command. > > Diagnose this by running "type wget". > > > Interesting: > gene@coyote:~/src/build$ type wget > wget is hashed (/usr/bin/wget) > gene@coyote:~/src/build$ > > What the heck does that mean?
It means you don't have a shell alias or function named wget. It also means you've run wget at least once previously in the current interactive shell, so that its location in the PATH list is cached. > gene@coyote:~/src/build$ id > uid=1000(gene) gid=1000(gene) groups=1000(gene),4(adm),5(tty),6(disk),7 > (lp),8(mail),12(man),20(dialout),24(cdrom),25(floppy),27(sudo),29 > (audio),33(www-data),44(video),46(plugdev),50(staff),100(users),102 > (systemd-timesync),116(lpadmin),118(pulse),119(pulse-access),120 > (scanner),122(colord),123(saned),125(nut) > > gene@coyote:~/src/build$ ls -ld > drwxr-xr-x 19 gene gene 4096 Jan 25 14:05 . OK. > > 3) You pasted the command from a source that has non-breaking spaces > > or other non-ASCII garbage polluting the arguments. > > How would that be diagnosed? By reading the error message extremely carefully. Or possibly by hex-dumping the command, extremely carefully. > df -h grep sda > /dev/sda5 1.8T 291G 1.4T 18% / > /dev/sda1 922M 183M 677M 22% /boot > /dev/sda3 46G 4.7G 39G 11% /var This command got mangled. I am guessing you ran "df -h | grep sda", and this all looks fine, but it doesn't tell us anything about ~gene. > > 5) Quotas. > > Diagnostic for that? No idea. You'd probably remember if you had set up user quotas, though. Why don't you just show us the wget command and its error message so we can stop guessing?
