Re: shell-init: could not get current directory

"Kurc, Marcin A." wrote: > > how do you remove it? > dpkg --purge package-name? Yes, I do dpkt -P cracklib-runtime on both machines, then I do dpkg -P cracklib2 on both machines, and then I reinstall with apt-get install cracklib2 and apt-get install cracklib-runtime. On the purge, the machine t

Re: shell-init: could not get current directory

"Kurc, Marcin A." wrote: > > Try to install not from the directory that is removed while Good point. The shell-init messages have now gone away, but I still run: apt-get install cracklib-runtime for only a few seconds and I get no /var/cache/cracklib/*_dict.* files. Again, this works

RE: shell-init: could not get current directory

Try to install not from the directory that is removed while you are removing cracklib* -Original Message- From: Xeno Campanoli [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2002 1:27 PM To: debian-user@lists.debian.org Cc: debian-user@lists.debian.org Subject: shell-init: could no

Re: shell-init: could not get current directory: getcwd: cannot access....

> "Alexander" == Alexander Wallace <[EMAIL PROTECTED]> writes: Alexander> shell-init: could not get current directory: getcwd: cannot Alexander> access parent directories: No such file or directory This either means your current directory has been deleted, or you don't have permissions to rea