From: jwinstea@jarthur.claremont.edu (Jim Winstead Jr.) Subject: Re: INFAQ (Infrequently Asked Questions) Date: 1 Jul 1992 05:40:43 GMT
In article <1992Jun30.144818.14463@cbnewsl.cb.att.com> pete@cbnewsl.cb.att.com (peter.j.fillingham) writes:
>
>Infrequently asked questions [INFAQ]:
Actually, not. Most of your questions are covered in Marc Corsini's
FAQ. It is a bit hard to find things there - that's why he's trying
to clean it up. :)
>(1) will the real tar please stand up ?
> tar 149127 bytes
> tar 335879 bytes
>Why not distribute CRC's along with prgs ?
The 'real' tar is whatever one didn't come from the 0.95a root disk.
Somehow, that one got broken, and as a result, it causes problems with
large tar files (GCC distribution, usually).
The 0.96 root disk will fix this problem with a newly compiled tar
linked against shared libraries (I compiled it yesterday, finally, and
it comes out to 91140 bytes.)
Would people find it useful if I ran 'sum' against all the files on
the fileson the root disk and released this? It would be a fairly
simple matter to do with a shell script, I think, so don't worry about
the time aspect - I just wonder if it's really that useful. (For
example, it would not have caught the broken tar - it would have
happily summed it.)
>(2) Following others recommendations regarding floppy backup:
>Using EITHER of the foregoing tar's and
>
># tar cvzMf /dev/at0 /*
>
>results in much verbose activity ending with
>"tar(child) only wrote 0 of 10240 bytes to /dev/at0"
>and a quiet return to
>#
>Obviously I am missing something [ -F script ?]
You cannot use the 'z' in conjunction with the M (multiple archive)
flag.
A workaround is the multiple floppy backup utilties that have been
posted, or sending the files through tar twice. (tar zcv /* | tar cMf
/dev/fd0) I haven't tested this, but it should work, in theory. :)
>(3) Following installation of GCC2.2.2 (or 2.1XXX):
>Using
># gcc hullo.c
>produces messages similar to
>"/usr/include/stdio.h:101: parse error before `('"
>even dropping #include <stdio.H>
>results in a similar message for main()
>WILL someone please have mercy and give a DETAILED description of
>installing GCC2.2.X ? e.g. where do the shared libs go ? etc...
>I do not have any compiler on linux and must rely on the binary forms.
>I have read GCCFAQ and all of release2.X.X and feel a little numb...
This is the result of the broken tar. This is covered in the FAQ.
As for installing GCC 2.2.2, this is in the GCC FAQ. Run the script
inst2.x in /usr/install/gcc (or something like that), and then the
fixfiles script. You should make sure that you have removed any old
compilers first.
These questions *are* answered in the FAQs, people! Those FAQs do no
good if you do not read them *carefully*.
>(4) Finally, does someone have the equivalent of the SYSV badblocks
>program to detect and mark badblocks AFTER installation ?
>Something (?) occasionally creates a directory /.badblocks which
>seems to have little or nothing to do with BADBLOCKS !
I don't know about this one - /.badblocks, is created by mkfs, I
believe. Since most people seem to run IDE drives, this isn't an
issue for them.
--
+ Jim Winstead Jr. (CSci '95)
| Harvey Mudd College
| jwinstea@jarthur.Claremont.EDU
+ This is all my words. Honest!