main June 2007

main@lists.alug.org.uk

47 participants
63 discussions

kubuntu apt-get not installed
by elc 18 Jun '07

18 Jun '07

Tried what you suggested Adam, and got 'command not found' for aptitude install apt. Also had 'command not found' for sudo aptitude install apt. In fact I also tried commands ls, man, sudo, and they all returned 'command not found'. Does this mean that all (most) of my commands are unavailable? About a week ago I went through the update procedure. I started with Dapper 6.06 (from live CD), updated to Edgy 6.10, then updated to Feisty 7.04. Things worked perfectly until last weekend when I tried to boot up linux and got this result. Would I presume that the live CD 6.06 would not now be of any use since I am 2 upgrades up? I've alo tried recover mode at Grub but doesn't work either - same results. Is there such a thing as a rescue disk that will repair my OS without losing my work? Fortunately I am dual booting with Win98 (wash my mouth out), but it is a right pain rebooting backwards and forwards. I look forward to any suggestions - elc > > It gets to a point > > "the program 'apt-get' is currently not installed. You can install > > it by typing: > > apt-get install apt > > > Try > > aptitude install apt (or possibly sudo aptitude install apt) > > >> > What I am trying to get to is my normal GUI or desktop. >> > > It sounds like your machine might have serious problems, has anything > changed recently or any other things that might be relevant to this > problem? > > Adam

7 9

FAO: Wayne (was Re: [ALUG] [ALUG Announce] 3rd Monday Monthly Ipswich Social Meeting : The Milestone, Woodbridge Road)
by samwise 17 Jun '07

17 Jun '07

Hey, Wayne, Are you coming tomorrow, should I bring my pair of book-laden carrier bags? Peter.

3 3

kubuntu apt-get not installed
by elc 16 Jun '07

16 Jun '07

Various people at ALUG are trying to help me with my problem, and I thank them for their help in trying to get me back into Kubuntu. Someone asked if anything unusual has occured in the recent past to maybe cause my current situation. Only one thing comes to mind, is that when I first enter my password at the beginning of a session the first character depressed on my keyboard is not registered. There is no fault with my keyboard, - I have checked this. When I have tried to test my OS with your suggestions during the past week, I have got to a terminal prompt without any imput from me and at the first occassion of me entering a character the character is not registered, the second character (which is a repeat of the first) is registered. Do I have a gremlin here? Is it a cause or a symptom of my problem? On another thought, can I re-install my OS on top of my existing (non-working) OS to resolve my problem, as I can do with Windows? elc

1 0

kubuntu apt-get not installed
by elc 16 Jun '07

16 Jun '07

I entered 'cat /etc/environment' and got PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games" LANG="en_GB.UTF-8" LANGUAGE="en_GB:en" in this order elc Wayne Stallwood wrote > Right this either means that something nasty has happened > to /etc/environment or your boot process is getting suck because of > another problem and not even getting to the point that the running PATH > is set. > > Can you tell me what the output of the following looks like- > > cat /etc/environment > > You should get something like > > LANGUAGE="en_GB:en" > > LANG=en_GB.UTF-8 > PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games" > > It's the PATH= bit that I am interested in > > If it looks similar to mine then I suspect the problem is earlier on in > the boot process and we are just looking at a symptom.

1 0

kubuntu apt-get not installed
by elc 16 Jun '07

16 Jun '07

I entered 'find / -name dpkg' and got '/var/lib/dpkg' '/etc/dpkg' '/etc/logrotate.d/dpkg' '/usr/bin/dpkg' '/usr/lib/dpkg' '/usr/share/doc/dpkg' '/usr/share/dpkg' '/usr/share/lintian/overides/' I entered 'find / -name wget' and got '/usr/bin/wget' '/usr/share/doc/wget I'm typing at 'root@elc-desktop:~# _' I entered 'set> /tmp/set.txt' 'set>/tmp/set.txt' 'set > /tmp/set.txt' and got nothing to all three I entered 'more /tmp/set.txt' and got about 50 lines of BASH=/bin/bash BASH_ARGC=() BASH_ARGV=() and so on, elc > '$ which dpkg' and got nothing - just returns to cursor > '$ which wget' and got nothing - just returns to cursor > > this means that it didnt find the command. If you are used to M$ DOS then the path is normally c:\windows\system32 > > try the commands > find / -name dpkg > find / -name wget > > if this comes back with "not found" then > cd /sbin > and then issue the commands with a dot slash in front > ./find / -name dpkg > ./find / -name wget > > or cd into /bin /usr/sbin /usr/bin or /usr/local/bin > > and I hope we can find the commands. > > Is this as a user or root you are doing this? If its a user the "su minus" which gets you to root with roots environment. > su - > > and then try the "which dpkg" and such like again. > > Keith >

1 0

kubuntu apt-get not installed
by elc 15 Jun '07

15 Jun '07

Did as suggested 'echo $PATH' gave /lib/init:/sbin:/bin and 'ls' just returns me to desktop cursor and '/usr/bin/apt-get' gives me a fast scroll which I was not able to record and 'cd /bin' gives 'root@elc-desktop:/bin#_' and 'cd/usr/sbin' gives 'root@elc-desktop:/usr/sbin#' Wayne Stallwood wrote > Given that it worked for a while after the upgrade I am guessin that > either your system volumes is not available or your path is wrong. > > > What is the output of - > echo $PATH > > (case sensitive) > > does /bin/ls work rather than ls on it's own ? > or /usr/bin/apt-get ? > > Can you 'cd' to /bin or /usr/sbin ? >

3 2

kubuntu apt-get not installed
by elc 15 Jun '07

15 Jun '07

I also entered 'type -a ls' and got 'ls is aliased to 'ls --color=auto' 'ls is /bin/ls' also entered 'type aP /bin ls' gives '$type -aP /bin ls' '/bin/ls' elc

1 0

kubuntu apt-get not installed
by elc 15 Jun '07

15 Jun '07

At command line I did 'set' and this gave a long listing which might have scrolled off the top of screen. What is showing on screen is no line starting with PATH= , nearest to it is a line 'verbose= no = path' Ted wrote > On 12-Jun-07 22:31:22, elc wrote: > >> > Tried what you suggested Adam, and got 'command not found' for aptitude >> > install apt. >> > Also had 'command not found' for sudo aptitude install apt >> >> Looks to me as though your PATH is empty, so your shell has >> nowhere to look for the commands. >> >> >From you command line, enter: >> >> set >> >> and look down the resulting list for a line that starts >> with "PATH=...." >> >> If you do not find one, then you have an empty PATH and that >> is the problem. On the other hand, if you get a result which >> includes things like >> >> PATH=/usr/local/bin:/bin:/usr/bin:.... >> >> then you have real problems. In particular, the command 'ls' >> should be in /bin. and therefore found; the command 'man' >> should be in /usr/bin and likewise found. So in that case >> there is something seriously wrong with your installation. >> >> If you have an empty PATH, this means that some initial >> configuration is not taking place when you log in, and we >> can probably help you track that down (there are not a lot >> of possibilities for what could go wrong there). >> >> But if you get a PATH like the above, it's trouble! >> >> ('set', by the way, should work regardless of your PATH >> since it is a shell command and not a binary. On the other >> hand, if your PATH is empty, then 'echo $PATH' will not >> work, since 'echo' is in /bin. Nor will 'env', since it >> is also in /bin)). >> >> Hoping this helps. Let us know what you see! >> >> Ted. >>

2 2

kubuntu apt-get not installed
by elc 15 Jun '07

15 Jun '07

Did 1) as suggested did '$ which dpkg' and got nothing - just returns to cursor did '$ which wget' and got nothing - just returns to cursor Did 2) '$ wget' and got 'bash: wget: command not found' Didn't do 3), was this reliant on 2) ? you'll need to forgive me I'm a newbie and didn't really understand your instructions, but thanks anyway. > On Tuesday 12 June 2007 23:31:22 elc wrote: > >> > Tried what you suggested Adam, and got 'command not found' for aptitude >> > install apt. >> > Also had 'command not found' for sudo aptitude install apt. >> > In fact I also tried commands ls, man, sudo, and they all returned >> > 'command not found'. >> > >> > Your problem may well be disk errors, but in case you just want to get apt > installed (which will be handy for helping to diagnose other problems) try > this. (Note, however, that if your disk is /very/ broken, this is unlikely to > work.) > > 1) Check dpkg and wget are still available: > $ which dpkg > /usr/bin/dpkg > $ which wget > /usr/bin/wget > > (if dpkg isn't there then, um, well I'm not sure what you'll do) > (if wget is unavailable then you can just use a web browser) > > 2) Download the apt deb: > $ wget > http://www.mirror.ac.uk/mirror/archive.ubuntu.com/ubuntu/pool/main/a/apt/ap… > > [previous command all on one line] > > 3) install it: > $ sudo dpkg -i apt_0.6.46.4ubuntu10_i386.deb > > And then you should have apt back on your box which will mean you can > (re)install other useful things. e.g.: > > $ sudo apt-get --reinstall install coreutils > > May I also suggest smartmontools? To help diagnose any possible disk errors? > > > Also, you may like to run an fsck (filesystem check; see $ man fsck). The > easiest way to do this is to force one to be scheduled next time you boot. > (fsck is most effective when run in single user mode.) > > $ sudo tune2fs -c 0 -i 30d -T 20070501 > > (This is a bit of a hack so I'd better explain: it makes tune2fs check the > drive on boot every every 30 days ["-i 30d"], tells it not to schedule tests > based on the number of times the drive has been mounted ["-c 0"] and tells it > that the last time it was checked was 1st May 2007 which, assuming your > computer's clock is about right, was more than 30 days ago; see also $ man > tune2fs) > > This will do an fsck next time you boot. > > Cheers, > Richard > > PS. I've just read the rest of this thread more carefully and now my message > seems a bit unhelpful (seeing as how you don't seem to /any/ programs > available). But I've typed it now, so I'm going to send it anyway.

2 1

kubuntu apt-get not installed
by elc 15 Jun '07

15 Jun '07

Tried 'type echo' and got 'echo is a shell built in' Tried also 'which echo' and got '/bin/echo' this doesn't mean anything to me, - hope it means something to you > On 13-Jun-07 08:07:29, Jon Dye wrote: > >> > (Ted Harding) wrote: >> >>> >> On 13-Jun-07 07:02:04, Brett Parker wrote: >>> >>> >> >> > Try "type echo" instead of "which echo" >> > >> > JD >> > > And, now that you point that out, > > type -a echo > > gives you the lot: > > $ type -a echo > echo is a shell builtin > echo is /bin/echo > > $ type -a type > type is a shell builtin > > Which raises an interesting question: If "type -a" can find everything > (including binaries), it must be making implicit reference to a PATH > which presumably is the user's $PATH by default (though neither > "help type" nor "man bash" is explicit about this). You can of course > set a search-path with option "-P" to "type". > > So, since "type" is a shell built-in, it should work for elc whatever > the PATH situation is. Therefore, going back to the "missing" commands, > if elc enters, for instance, > > type -a ls > > and gets: > > $ type -a ls > bash: type: ls: not found > > while "type -aP /bin ls" gives > > $type -aP /bin ls > /bin/ls > > this is presumably a pretty sure-fire diagnostic of PATH problems. > > Best wishes to all, > Ted. > >

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

main June 2007