I get the same problem on a Dell Optiplex DGX 5133 trying to install the
slink release. Fortunately, I still have an earlier rescue disk for Debian
2.0.21 which I used to boot with and then used slink's base floppies to
install from. Seemed to work ok.
> -Original Message-
> From: dormat [
Is your current directory on a NFS filesystem when you do su? Are you having
NFS problems at the same time? I've seen this problem in these circumstances
as the su tries to get the current directory but can't as the remote server
is down/unreachable. Hope this helps.
Rgds, Andy Chittenden
Email:
WARNING: I have had files disappear on me when using such a script when the
target filesystem is on a Win32 machine. It is safer to rename them via an
intermediate name:
for file in $*
do
to=`echo $file | tr [:upper:] [:lower:]`
mv $file $to.newone;mv $to.newone $to
done
Rgds, And
We're using NIS with hamm and slink with no problems. Our NIS server runs on
Netware (don't blame me - that's corporate MIS for you!). We did have
problems at one stage which meant we had to set the ypserver's address in
/etc/yp.conf.
Rgds, Andy Chittenden
Email: [EMAIL PROTECTED] Fax:
Is anybody working on a journalling/resilient file system for Linux?
Rgds, Andy Chittenden
Email: [EMAIL PROTECTED] Fax:+44 1753 661011
Multimedia Development, Madge Networks Ltd
Wexham Springs, Framewood Road, Wexham, Slough SL3 6PJ, England
5 matches
Mail list logo