As such it would be a RNT if a complete release with all the
binaries be made, including all man pages, include files, binaries
such as idoc, ibuild, iclass, and both static libraries & jump (4.3)
as an 'official' release for XFree86-1.2 and libc.so.4.3.
--
Mike Irons;
Mike Irons;
|> Upon upgrading to linux 99.1-4, I found that many functions which
|> require the shell dump core. Is there a bash fix, for this release?
|> Thanks for any help... wendell nichols
I have the same problem (I think)... e.g. make dumps core when it attempts to
do an "echo" command, when I run the kernel I have compiled and use bash as the
shell. On the other hand, if I boot with a version of the kernel that is
available as a bootdisk (I think .99p4) then this fault does not occur. I also
upgraded my compiler to gcc233 when I changed the kernel, so maybe the
upgrade didn't go that well although everything else seems to compile just
fine. I like to be able to compile the kernel, if only to change the
keyboard definitions.. Anyone any ideas?
Ari
No need. Just do 'compress *.pcf; mkfontdir' in the font directories.Quote:> When making the XFree86-1.2 dis the person neglected to
>compress the fonts. As such they take up a considerably larger amount
>of disk space. Could the person (Orst) please compress the fonts, and
>re-tar the 1-2 fonts files. Remember compressing the tars more won't
>help save space after X is installed, and that should be of prime concern.
>--
Regards,
/Muhammad M. Saggaf | Stop the genocide
PLEASE get in the habit of reading all the documentation. It is there
for you benifit, (usually so you don't post to the net asking faq's!!! :)
Just go into the font dirs and do compress *.pcf
The reason the fonts are expanded un-compressed, is that gzip is much
better at compressing un-compressed fonts than compressed ones.
The README files clearly details that you need to compress the fonts
again with 'compress' before starting.
: Mike Irons;
Michael
There there Michael. Actually, if memory serves me correctly, theQuote:>PLEASE get in the habit of reading all the documentation. It is there
>for you benifit, (usually so you don't post to the net asking faq's!!! :)
>better at compressing un-compressed fonts than compressed ones.
[...]
>The README files clearly details that you need to compress the fonts
>again with 'compress' before starting.
A bit of tolerance, please.
P.S. XFree86 1.2 is wonderfull, thanks to Orest and the rest of the
people who worked on it. Tremendous job.
Cheers,
/Muhammad M. Saggaf | Stop the genocide
-Eric
--
A package with multipule, and conflicting README/install instructions
is poor programming, and unfortunatly very typical of linux (as a
whole system) these days.
--
Mike Irons;
Your right. If I were you, I would drop out of this newsgroup immediately,Quote:> A package with multipule, and conflicting README/install instructions
> is poor programming, and unfortunatly very typical of linux (as a
>whole system) these days.
Linux is a hacker's operating system. If you're not a hacker, and are unable
to figure out that the fonts need to be compressed (either by reading ALL
of the available documentation, as you didn't do--- or by reading this
newsgroup or figuring it out yourself) then prehaps you're not ready for
Linux.
No one has given you any guarantee that any of the software used under
Linux will work as is. In fact, the GPL directly states that there is no
such guarantee.
The Linux Doc Project is trying to make up for this situation. However,
at present, you're going to actually have to figure some things out
for yourself instead of expecting everyone to spell it out for you.
mdw
--
"What are you doing, Dave?"
1. bash 1.12 link error- IGNORE
Oops - slip of the mouse - wrong news group. Sorry
--
Keith Hollister
2. often getting "can't find libXXX.so.3"
3. Bash 1.12 for Unicos 6.1.X and Solaris 2.X
5. Trouble with Bash 1.12 under OS/2 Warp
6. Help: Iomega Ditto and RedHat Linux
8. ???Adding a 2nd SOUND CARD???
9. Bash 1.12 SIGHUP problems -- help!
12. Solaris 2.2 config for bash 1.12?
13. linux 99.4 boot image woes