info-3b2@lamc.UUCP (Info-3b2 Mailer) (03/02/89)
Info-3b2 Digest, Number 64
Wednesday, March 1st 1989
Today's Topics:
Re: UUCP bug not in SVR3.0.
UUCICO bugs
Re: HoneyDanBer UUCP uucico problem (bug?)
Re: 3b2 Questions - Answers Appreciated
Mailer Problems
From: !
Info-3b2 Digest, Number 64
Wednesday, March 1st 1989
Today's Topics:
Re: UUCP bug not in SVR3.0.
UUCICO bugs
Re: HoneyDanBer UUCP uucico problem (bug?)
Re: 3b2 Questions - Answers Appreciated
Mailer Problems
----------------------------------------------------------------------
Subject: Re: UUCP bug not in SVR3.0.
Date: Tue, 28 Feb 89 17:01:34 -0500
From: len@netsys.Netsys.COM
I am using SVR3.1.2 so doubt that an upgrade will help. The problem
may have existed in SVR3.0 , I forget. I may load it to prove to
myself. I have heard that the problem even exists on the very latest
R & D versions, but cannot verify this since I do not work for AT&T.
Len
len@ames.arc.nasa.gov or len@netsys.com
------------------------------
Subject: UUCICO bugs
Date: Wed, 01 Mar 89 09:31:30 -0500
From: len@netsys.Netsys.COM
Here is something that was on the net..
I am going to mail it to info-3b2 just to clarify my previous
statements.
############## Beginning of article ###################
From: denny@mcmi.UUCP (Dennis Page)
Newsgroups: comp.sys.att,comp.mail.uucp
Subject: Re: HoneyDanBer UUCP uucico problem (bug?)
Keywords: hdb uucico 3b2 att
Message-Id: <803@mcmi.UUCP>
Date: 27 Feb 89 23:05:34 GMT
References: <133@aucis.UUCP> <810@sigmast.UUCP>
Reply-To: denny@mcmi.UUCP (Dennis Page)
Distribution: usa
Organization: MCMI, Omaha, NE
Lines: 30
Xref: netsys comp.sys.att:5282 comp.mail.uucp:2021
In article <810@sigmast.UUCP> dgy@sigmast.UUCP (Dave Yearke) writes:
>Devices File:
>ACU tty26,M - 2400 modema
>ACU tty26,M - 1200 modema
>Systems File:
>alpha ACU 2400 555-1212 (rest of stuff omitted)
>alpha ACU 1200 555-1213 (rest of stuff omitted)
>uucico will try the first number at 2400 using "modema". If it is busy, it
>will try the second number in the list using "modema", BUT IT IS STILL TALKING
>TO THE MODEM AT 2400!!
The problem is actually caused in the Dialers file with the use of
the "\M" and "\m" commands. It seems that the ioctl structure used by
these commands are initialized only at the beginning of the dialing
sequence. Somebody trying to save an ioctl or two.
>The AT&T hotline people, who are usually on top of things, have never heard of
>this happening.
AT&T (New Jersey) has acknowledged the problem (and tested a fix for
it), and will be sending a change/fix request to whomever they send
those things to within AT&T. A fix should appear in future versions
of HDB.
What an annoying little bug.
################ end of article #################
--
len@ames.arc.nasa.gov
or len@netsys.com
------------------------------
Subject: Re: 3b2 Questions - Answers Appreciated
Date: Wed, 1 Mar 89 20:06:13 GMT
From: Graham Glen (Technical Manager) <qukmips!graham>
>
> Never remove a mounted floppy filesystem without first
> unmounting it, especially a boot disk. Doing this may leave the
> filesystems's status flag in an "active" state and prevent the
> boostrap from recognizing it. The umount operation insures that
> the disk is properly updated before it is closed. When the green
> drive light goes off, remove the floppy and return it to its
> proper home.
>
Does this hold true for read only file systems as well?
>
> While some errors are to be expected while checking the
> root partition, a total failure is a very serious error. Our
> experience defines "total failure" as an indication by fsck
> that it cannot find any possible traces of a filesystem. In
> particular, "CAN NOT READ: BLK 1" is one of the more ominous
> messages we have seen.
>
This nearly gave me brown trousers the first time I had it happen. If the
machine is up and running and it is not the root file system that has this
problem then it can be cured very easily.
/bin/dd if=/dev/dsk/fs1 of=/dev/dsk/fs2 bs=1b count=1
Where fs1 is another file system that is not bootable (I'm not sure what
would happen if you used a bootable file system as input), and fs2 is the
file system that will not fsck.
It doesn't matter whether the file system used for input is dirty (eg.
needs fsck'ing itself).
The first time I tried this I took the precaution of dumping the damaged
file system onto a reel of 9 track first (eg. just dd'ing from the raw
device to the tape drive), but since then I haven't bothered and on the (3
I think) occasions where fsck has not been able to read block 1 it has
saved me rebuilding the whole partition.
Graham
--
Graham Glen | Voice +44 1 371 5755
Quadratron Systems (UK) Ltd. | +44 836 380006 (mobile)
--------------------------------------+----------------------------------------
{quad1,qnorth,qswiss,ukc,attunix!uel}!quaduk!graham
------------------------------
Subject: Mailer Problems
Date: Wed, 01 Mar 89 19:27:46 -0500
From: len@netsys.Netsys.COM
My apologies to info-3b2 .. My mailer was having a problem
due to some previous hacking in my sendmail.cf and I had to
kill some jobs.. Info-3b2 is on auto-pilot at lamc it seems and
the error message is being fowarded all over the universe.
Len
len@ames.arc.nasa.gov
or len@netsys.com
-------------------------------------
To join this group or have your thoughts in the next issue, please
send electronic mail to Ken Davis at the following address;
{pacbell,netsys,hoptoad,well}!lamc!info-3b2-request
The views expressed in Info-3b2 Digest are those of the
individual authors only.
*********************
End of Info-3b2 Digest
*********************
-------------------------------------
To join this group or have your thoughts in the next issue, please
send electronic mail to Ken Davis at the following address;
{pacbell,netsys,hoptoad,well}!lamc!info-3b2-request
The views expressed in Info-3b2 Digest are those of the
individual authors only.
*********************
End of Info-3b2 Digest
*********************