HDTenEightyP/NetNews huggingface dataset:
From: euajpa@eua.ericsson.se (Johan Parin)
Subject: X386 Video Configuration [386BSD] (HELP)
Summary: Only flicker on screen
Keywords: Xconfig, ET4000, Fixed Frequency
Organization: Ellemtel Telecom Systems Labs, Stockholm, Sweden
Date: Sun, 6 Sep 1992 20:22:30 GMT

I have the following problem when trying to bring up X386; I start X
with xinit (or X386). The banner is printed and a switch to graphics
mode is made, *but*: Only flicker shows on screen. This is about the
same behavior I get if I try to switch to a video mode my monitor does
not support (i.e. 800x600). I have a fixed frequency monitor
(Resolutions of 800x600 or above are not supported, but 640x480
definitely is). My video board is based on ET4000 (1 MB RAM), but is
from an unknown (Taiwanese) manufacturer. I *have* made the required
patches to the files pccons.c and locore.s and rebuilt the kernel with
-DXSERVER (before I did that the server never switched to graphics
mode). This is my Xconfig:


vga256
  Chipset	"et4000"
  Clocks	25 28 40 36 0 44 0 62

NoSpeedUp

  ViewPort      0 0
  Modes	        "640x480"

ModeDB
# clock  horzontal timing      vertical timing
 "640x480"   25     640  672  768  800    480  490  492  525
             28     640  672  768  800    480  490  492  525

Isn't this a setup that all et4000 based video boards should support?
(The documentation for the board is very poor, so I will not be able
to find out the supported dot clock rates)

PLEASE, any advice will be appreciated!

Johan Parin

Newsgroups: comp.unix.bsd
From: wolfy@ba.ncu.edu.tw (Jann-Yea Sue)
Subject: Re: WD Ethernet Problems with 386BSD
Reply-To: wolfy@ba.ncu.edu.tw
Organization: Sun Microsystems, Inc.
Date: Tue, 8 Sep 1992 10:56:38 GMT



Newsgroups: comp.unix.bsd
From: jlu@cs.umr.edu (Eric Jui-Lin Lu)
Subject: [Xfree86] installation problems and requests...
Date: Fri, 11 Sep 1992 22:52:08 GMT
Organization: University of Missouri - Rolla
Originator: jlu@mcs213i.cs.umr.edu

Greetings *,

Before I installed and tested Xfree86 from /pub/incoming/X386 at
agate, I have a few questions and requests so that, I hope,
I can smoothly install Xfree86.

1.  What's the major and minor number of /dev/tty00?  Is it
    same as com1 or com2?
2.  Where can I get xterm termcap?  More general, where can I get
    /etc/termcap?  I didn't see such file in /etc.  Also, it
    vt100 possible?
3.  I have NEC 2A and Mentor's SVGA which has ET4000 Turbo Mega
    chipset.  Is there anyone out there successfully install
    Xfree86?  I need your Xconfig file.

You can either post or email.  Thanks in advance!!!!


   --Eric

-- 
***************************************---       Grad. student          ---*
* Obviousness is always the enemy of  *   \     Jui-Lin Lu (Eric)      /   *
* correctness.  -- Bertrand Russell   *   /      jlu@cs.umr.edu        \   *
***************************************---   Univ. of Missouri-Rolla    ---*
Newsgroups: comp.unix.bsd
From: terry@thisbe.Eng.Sandy.Novell.COM (Terry Lambert)
Subject: Re: 386BSD #!/bin/csh
Organization: Novell NPD -- Sandy, UT
Distribution: comp
Date: Thu, 10 Sep 1992 16:44:15 GMT

In article <MICHAEL.92Sep10112416@athene.uni-paderborn.de> michael@uni-paderborn.de (Michael Schmidt) writes:
>
>>386bsd 0.1 doesn't seem to respect #! in beginning
>>of the shell scripts, Anyone knows why? Fixes?
>
>>>>>> About Re: 386BSD #!/bin/csh, Terry Lambert said:
>Terry> Instead of:
>Terry> 	#!/bin/sh
>Terry> use:
>Terry> 	:
>Terry> 	#
>
>Terry> This will result in invocation of /bin/sh.  Sorry; no
>Terry> workaround known to make it execute csh instead.
        ^^^^^^^^^^
>
>Ooops. The patch to kern_execve in
>agate.berkeley.edu:pub/386BSD/386bsd-0.1/unofficial/williams/kern_shell.0_1
>works for me (somehow (;-).

Grrrr.   It was a *workaround* to avoid kernel recompilation.   Grrrr.


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu

---
Disclaimer:  Any opinions in this posting are my own and not those of
my present or previous employers.
From: aw2t+@andrew.cmu.edu (Alex R.N. Wetmore)
Newsgroups: comp.unix.bsd
Subject: Re: setting up 3c503
Date: 6 Sep 92 01:28:00 GMT
Organization: Sophomore, Math/Computer Science, Carnegie Mellon, Pittsburgh, PA

Excerpts from netnews.comp.unix.bsd: 4-Sep-92 Re: setting up 3c503 by
Adrian Hall@ibmpcug.co.u 
> PS - If you get it going, please let me know what you did.
>  
> Adrian

Here are the changes that I had to make to get 386bsd to work with the
3c503 card through the AUI (thick) port:

Edit /usr/src/sys.386bsd/i386/isa/if_ec.c (might be the wrong path, this
is out of memory), and search for thick.  There is a port number there
that needs to be changed from a 2 to a 0.  Then recompile the sources,
and everything should work fine.

alex
Newsgroups: comp.unix.bsd
From: pauls@icecreambar.css.itd.umich.edu (Paul Southworth)
Subject: 386bsd booting / partitioning problem
Reply-To: pauls@umich.edu
Organization: University of Michigan
Date: Tue, 8 Sep 1992 20:35:15 GMT

HERE IS A QUESTION FROM A COMPUSERVE USER...

If anyone can answer this, post response here or email it to me and
I will forward it.

* * *

I'm having a problem with the 386BSD "Tiny" install.  The install
appears to work correctly, but when I boot off the hard drive, I get the
following messages:"Copying RAM area to device 1, ofsset 0"
"Press any key to abort Bad Device" and then the system reboots.  I won't  
swear
to the word-for-word accuracy of the messages, because they are only  
visible
for a fraction of a second.  I've got a 486/50 with a 124M IDE (Maxtor).   
It is
in two 62M partitions at the moment, and is listed as a user-defined drive  
with
the specs that Maxtor recommends.  Any ideas on how I can get around this
problem?
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject:  fdprobe() returns 0 
Keywords: fdc wdc patch fdprobe
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Mon, 7 Sep 92 19:25:40 GMT


I installed the 2nd drive (updated) patch from Tom Helbekkmo
(tih@barsoom.nhh.no) and since then (?) I cannot access my fd drive any longer.

I peeked into fdprobe() with a printf() and find that fdprobe() does
not even see the FD controller (at 3f0). 

I'm baffled. I will now successively go back in steps to see at which kernel 
configuration I can see my floppies again. 

It does not seem to be hardware - a different IDE controller gave the same
bad result and I can still boot dist.fs (I'm using a 386SX 16MHz Morse Motherboard with 8MB, two disks). It's really strange, maybe too strange 
to post it here - but if anyone has a vague idea what I could also look for or check I'd be thankful.



Below is my CONFIG file:

--Chris
-----------------------------------------------------------------
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.

#
# My latest and greatest GATEWAY kernel
#
machine		"i386"
cpu		"i386"
ident		GATEWAY
timezone	-1 dst
maxusers	10
options		INET,ISOFS,NFS,GATEWAY
options		"COMPAT_43"
options		"TCP_COMPAT_42"

config		"386bsd"	root on wd0 swap on wd0 and wd1 and as0

controller	isa0
controller	wdc0	at isa? port "IO_WD1" bio irq 14 vector wdintr
disk		wd0	at wdc0 drive 0
disk		wd1	at wdc0 drive 1

controller	fdc0	at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
disk		fd0	at fdc0 drive 0
disk		fd1	at fdc0 drive 1

controller	as0	at isa? port 0x330 bio irq 11 drq 5 vector asintr
disk		as0	at as0 drive 0
disk		as1	at as0 drive 1

device		pc0	at isa? port "IO_KBD" tty irq 1 vector pcrint
device		npx0	at isa? port "IO_NPX" irq 13 vector npxintr
device		com1	at isa? port "IO_COM1" flags 0x01 tty irq 4 vector comintr
device		com2	at isa? port "IO_COM2" flags 0x01 tty irq 3 vector comintr

device we0 at isa? port 0x280 net irq 2 iomem 0xd0000 iosiz 8192 vector weintr
device ne0 at isa? port 0x360 net irq 5  vector neintr
#device ec0 at isa? port 0x250 net irq 2 iomem 0xd8000 iosiz 8192 vector ecintr
#device is0 at isa? port 0x280 net irq 10 drq 7 vector isintr

device		wt0	at isa? port 0x300 bio irq 5 drq 1 vector wtintr

pseudo-device	loop
pseudo-device	ether
pseudo-device	sl	2
pseudo-device	log
pseudo-device	pty	4

pseudo-device	swappager
pseudo-device	vnodepager
pseudo-device	devpager
------------------------------------

--Chris
------------------------------------
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.
Newsgroups: comp.unix.bsd
From: u4901ac@sun7.LRZ-Muenchen.DE ()
Subject: HP Vectra and 386BSD, hope it's not a FAQ
Keywords: HP Vectra
Organization: Leibniz-Rechenzentrum, Muenchen (Germany)
Date: Tue, 15 Sep 1992 11:29:21 GMT

Hi,
I tried to boot the tiny boot diskette on a HP Vectra 386/25 with 170 MB disk
space. But the PC always reboots a few seconds after displaying the rom bios
copyright. I've read bsd.faq very carefully and read nearly everything related
in this newsgroup -- nothing seems to help me. I think it a problem of the 4
extra k that this machine  uses for the rom bios. I tried the instructions
recommended in bsd.faq but they are for an american setup program - I have
a german one.

Has anyone an idea to get rid of these 4 k ?


-----------------------------------------------------------------------------
Henning Brockfeld        u4901ac@sun7.lrz-muenchen.de
Institute for economic geography
University of Munich
-----------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: richard@pegasus.com (Richard Foulk)
Subject: Re: 386bsd -- The New Newsgroup
Organization: Pegasus,  Honolulu
Date: Thu, 10 Sep 92 02:29:57 GMT

>> 	comp.os.386bsd		(general questions and trivia)
>> 	comp.os.386bsd.kernel	(discussion on kernel content/structure)
>> 	comp.os.386bsd.windows	(ditto, on windowing systems like X)
>> 	comp.os.386bsd.sharedlib (shared library and programming environment)
>> 	comp.os.386bsd.net	(networking topics)
>> 	comp.os.386bsd.bugs	(new bugs)
>> 	comp.os.386bsd.ann	(announcements, fixes, additions)
>
>Actually, I'd probably be more interested in seeing a single comp.os.386bsd
>than in seeing a set of groups this fragmented.  Good threaded user interfaces
>make keeping discussions together easy, and it takes less time and effort to
>keep up with if it's all in one place...
>

Or, better yet, how about comp.unix.bsd.  Works for me.

Let's not fix something that's not broken.


-- 
Richard Foulk		richard@pegasus.com
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: [386BSD] cc1 fatal error & more!
Organization: Weber State University  (Ogden, UT)
Date: Fri, 11 Sep 92 01:26:23 GMT

In article <6703@vtserf.cc.vt.edu> linkt@GroupW.cns.vt.edu (Tim Link) writes:
>In article <0efk57e00WB60gg0pN@andrew.cmu.edu> tj2n+@andrew.cmu.edu (Tao Jiang) writes:
>>
>>Hi, I tried to compile a program and got the cc1 fata error like:
>>cc -I.. -I../..  -O -c fogdeck.c
>>cc: Program cc1 got fatal signal 6.
>>*** Error code 1
>>
>
>	I have exactly this same problem when trying to build the
>system.  (Smaller compiles seem to go OK).  Re-running make will usually
>continue and compile a few more things and then it happens again,
>howeever it seems to get stuck on some files, forcing me to reboot and
>then continue.  Sounds like something is being left hanging around in
>memory after cc runs but who knows?  Any thoughts or patches???

	Make has a terrific leak.  I compiled up a different version (sorry,
proprietary).  You may want to try gnumake.

I used to get around the problem by doing:

	make -n > foo
	vi foo
	sh foo

Now I have a grundle of memory and it doesn't matter any more.  You can
try any or all of these; one of them will probably kill the problem.


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                                       terry@icarus.weber.edu
 "I have an 8 user poetic license" - me
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: nyse@nicedel.north.de (Hermann Behrens)
Subject: Problem with 386BSD and Network
Organization: NICE DELmenhorst, Germany
Date: Sat, 5 Sep 1992 09:55:21 GMT

Hello!

I've installed 386BSD correct, but I'm not able to establish a
connection to my 2nd computer. The 2nd computer works well and there
are sure no problems with the ethernet-card. The ethernet-card in the
Peacock 386/20 is a FD0490 EtherBoard16. I've installed it for IRQ2, but
386BSD says the following:

ne0 ethernet address 00:00:4d:21:65:97 at 0x300 irq9 on isa

?? I installed ther card on all available IRQ's(2,3,4,5,12) but it
will always be detected on IRQ 9. Then I type the following:

>ifconfig ne0 192.1.1.2		# I type in
<neinitstartartstartart		# 386BSD answers
>route add default 192.1.1.10 (The IP-Number for my 2nd computer).

Now I tried to start ftp but I was never successful. Does someone knows
the answer for the problem? The rest of the peripherie: 8 MB RAM, 50
MB HD, VGA(an old one: MORSE KP 1000 EVGA) etc...

ciao, Hermann Behrens
-- 
Hermann Behrens || 04221-71932 || Bremerstr. 323 || nyse@nicedel.north.de
From: David.Fox@Saigon.COM
Newsgroups: comp.unix.bsd
Subject: Math emulation quite slow on 386bsd
Keywords: emulation, 387
Date: 11 Sep 92 23:25:14 GMT
Distribution: usa
Organization: Station Zebra Corp, Sunnyvale CA Ph:408-739-1520

Hi.

I've noticed that the math emulation seems extremely slow compared to
DOS with 386BSD.  I suspected this for a while, but didn't have any
real checks to test this.  I just pulled off source code to the dhry-
stone and whetstone benchmarks, and got the following results:

With 386bsd, no tasks other than the standard ones running (i.e., single
user):

whetstones = 1903
dhrystones (no register) = 3092
dhrystones (register)    = 3099

QAPLUS under DOS 5.0:
 
whetstones = 49.4K
dhrystones = 3251

QAPLUS under DOS 5.0, no QEMM/386:
 
whetstones = 69.8K
dhrystones = 3251

This is rather interesting, especially the large jump (49.4K vs. 1903).  
Unless QAPLUS's idea of what a whetstone is is radically different than
the whet.c program's idea, this shows a substantial decrease in emulator
performance.
 
What I got when I did 'time whet': 
7.6u  525s 8:52.77 100.0% 0+0K 0+0io 0pf+0w (whatever this means) :)_
 
I can't really interpret this but it looks like it took roughly 525 seconds
to run it.  Whet.c includes a define that says it's going to run for
a million whetstones.  Ergo, 1,000,000 / 525 gives approximately 1,903.
 
Unfortunately, at this time, my dos partition is small, and rather flaky, so
I wasn't able to restore a C compiler off of tape and run whet.c under DOS.
 
If anyone has whet.c whetstone benchmark and has MSC or TC please run it
and see if there is such a substantial difference between the two math
emulators, and email me about it.
 
If I can get the DOS partition to be less flaky (maybe a new HD?) I'll
post a followup article on this point.
Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: Re: X386 xdm with crypt, other tools, printer EXPERIENCES
Date: Wed, 09 Sep 92 23:22:56 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Keywords: xdm X386 crypt lpt.c 

In article <1992Sep9.122332.22785@cs.tu-berlin.de> engel@opal.cs.tu-berlin.de (Christian Engel) writes:
>Printer Support
>===============
>
>I had many problems using the original lpt.c driver although patched with
>lpt-haugh and the lp.c drivers.
>Printing of normal ascii files was ok using the lp.c driver. But when I tried to
>print a .dvi-djc file (Deskjet 500 output from dvi), character losses and even
>crashes (lpt.c) occurred.
>Switching off the printer caused a reboot.
>I could solve the problem for lpt.c using an output filter, that flushed the
>output and waited for a while (usleep) after a certain amount of characters were
>sent to the printer.
>I didn't need to use this filter for the new version of lpt.c that does busy
>waiting.

I had similar problems with the Eric Haug patches to  the  lpt driver.
But I have not had any such problems since I recompiled lpd.c
(in /usr/src/usr.sbin/lpr/lpd).  BTW, what does an lpt driver without
interrupts buy me?  What is the cost?
-Andrew Moore <alm@netcom.com>
Newsgroups: comp.unix.bsd
From: tom@izf.tno.nl (Tom Vijlbrief)
Subject: Re: 386BSD & COMPAQ 486/33
Organization: TNO Institute for Perception
Date: Fri, 11 Sep 1992 13:49:47 GMT

Stephan Heuer <HEUER@DMSWWU1A.UNI-MUENSTER.DE> writes:

>I have 386BSD 0.1 running on a Compaq Deskpro 386/20 with 387,
>ethernet and 60MB hard disk. 0.1 refused to boot, but I had 0.0 running
>so I used the 0.0 boot block. I just copied the first 8k from the 0.0
>boot disk to the 0.1 boot disk and voila ... I have *not* changed my 0.0
>disklabel on the hard disk!

This procedure indeed starts the 0.1 kernel from the 0.1 boot floppy,
but the kernel crashes after writing the fist screen of messages.....


Tom
From: wjolitz@soda.berkeley.edu (William F. Jolitz)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd -- The New Newsgroup
Date: 8 Sep 1992 18:02:33 GMT
Organization: U.C. Berkeley, CS Undergraduate Association
NNTP-Posting-Host: soda.berkeley.edu
Keywords: newsgroup 386bsd news group

In article <1992Sep8.140141.10371@terminator.cc.umich.edu> pauls@umich.edu writes:
>I'm getting just about anxious enough about having a 386bsd-only  
>newsgroup(s) to do something about it.  It appears to me, and from some  
>brief discussions with various other enthusiasts, that coordination is  
>what is required for this effort, since there are plenty of supporters out  
>there....

This is exactly the problem. Unfortunately, I'm snowed under at this time
manually putting together SIG mailing lists groups (we are not at this
time connected to the internet, so processing is quite tedious and not
timely). 

I'm eager for volunteers! 

As per Bill's suggestion, here's a breakdown of some of the suggested 
topics and groups:

	comp.os.386bsd		(general questions and trivia)
	comp.os.386bsd.kernel	(discussion on kernel content/structure)
	comp.os.386bsd.windows	(ditto, on windowing systems like X)
	comp.os.386bsd.sharedlib (shared library and programming environment)
	comp.os.386bsd.net	(networking topics)
	comp.os.386bsd.bugs	(new bugs)
	comp.os.386bsd.ann	(announcements, fixes, additions)

I'd love to hear back from people, and help/suggestions are gratefully
appreciated.

Thank you.

Lynne Jolitz.
From: goran@astro.uu.se (Goran Hammarback)
Newsgroups: comp.unix.bsd
Subject: Re: ps -aux yields Floating exception
Date: 14 Sep 1992 12:58:03 GMT
Organization: Uppsala University
Distribution: world
NNTP-Posting-Host: solaris.astro.uu.se
Keywords: ps FP exception Floating

In article <1992Sep13.171803.3954@Urmel.Informatik.RWTH-Aachen.DE>, kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes:
|> 
|> I recently installed a kvm.c patch (though I'm not sure if I installed
|> it completely and c orrect) - anyway, when I do a ps -aux I get
|> the header line of ps (CPU % etc..) and then in the next line a 
|> Floating exception.
|> 
|> Is this a known and already mentioned problem or do I have to 'patch harder'
|> :-)? 


Did you forget to patch ps itself?

From: davidg@agora.rain.com (David Greenman):

*** /usr/src/bin/ps/ps.c.01orig	Mon Jul  1 17:54:45 1991
--- /usr/src/bin/ps/ps.c	Sun Aug  9 05:35:26 1992
***************
*** 78,83 ****
--- 78,84 ----
  
  uid_t	getuid();
  char	*ttyname();
+ double	getpcpu();
  
  char dfmt[] = "pid tt state time command";
  char jfmt[] = "user pid ppid pgid sess jobc state tt time command";


-- 

Goran

------------------------------+---------------------------------
Goran Hammarback              |     goran@astro.uu.se
Astronomiska Observatoriet    |
Uppsala Universitet           |
S-751 20 SWEDEN               |
------------------------------+---------------------------------
From: adrian@ibmpcug.co.uk (Adrian Hall)
Newsgroups: comp.unix.bsd
Subject: Re: How can I print on my parallel printer?
Date: 9 Sep 92 09:27:49 GMT
Organization: The IBM PC User Group, UK.

In article <colin.716015692@marsh> colin@marsh.cs.curtin.edu.au (Colin Manning) writes:
>Hi,
>	I've applied the patches in unofficial/williams/lpt.*.haug.
>
>	I still can't print.  I have a Panasonic KPX1180 (80 col, 9pin)
>attached to LPT1.  When I boot under DOS (yuk) the printer head jumps about,
>but I get nothing from 386BSD.

You need to make the /dev/lp and /dev/lpt1 nodes.

	mknod /dev/lpt1 c 15 64
	ln -s /dev/lpt1 /dev/lp

Adrian
-- 
--------------------------------------------------------------------------
Adrian Hall					Connect Systems Manager
adrian@ibmpcug.co.uk				The IBM PC User Group
Tel: +44 81 863 1191				Harrow, London, UK
From: r_moore@vger.nsu.edu
Newsgroups: comp.unix.bsd
Subject: Minimum system requirements for 386bsd ?
Date: 15 Sep 92 12:59:12 EDT

I need to know what the minimum requirements are to run 386bsd are. More
specifically will it run on this configuration:
386sx @16mhz
1 meg RAM
40 meg HD
if it will not run on this system what additions will I need to make ?
        Thanks, Richard

Newsgroups: comp.unix.bsd
From: colin@marsh.cs.curtin.edu.au (Colin Manning)
Subject: How can I print on my parallel printer?
Organization: Curtin University of Technology
Date: Wed, 9 Sep 1992 05:14:52 GMT

Hi,
	I've applied the patches in unofficial/williams/lpt.*.haug.

	I still can't print.  I have a Panasonic KPX1180 (80 col, 9pin)
attached to LPT1.  When I boot under DOS (yuk) the printer head jumps about,
but I get nothing from 386BSD.

Any ideas/help/comments/suggestion?


Thanks
Colin.
--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
Xref: sparky comp.unix.bsd:5492 comp.protocols.tcp-ip:4380 comp.protocols.tcp-ip.domains:617
From: feoh@hal.gnu.ai.mit.edu (Chris Patti)
Newsgroups: comp.unix.bsd,comp.protocols.tcp-ip,comp.protocols.tcp-ip.domains
Subject: Adress correction (for previous article: nameserver problems (HELP!!!)
Date: 10 Sep 92 23:02:40 GMT
Organization: MIT Laboratory for Computer Science

Hello, an incorrect adress was given in the previous article regarding name 
server resolution problems. the correct adress to reply to is: 
bild@ncm.ncm.interlan.com (we can't get our sendmail to realize that 
ncm.interlan.com is equivalent to ncm.ncm.interlan.com :)

Thanks in advance,
feoh@gnu.ai.mit.edu
posting for bild@ncm.ncm.interlan.com
Newsgroups: comp.unix.bsd
From: toad@rubikon.han.de (Peter Cleve)
Subject: Re: backup w/ compression for UN*X?
Organization: Rubikon Rethen BRD
Date: Mon, 07 Sep 92 11:10:18 GMT

In <BRTMAC.92Sep6140131@maverick.ksu.ksu.edu> brtmac@maverick.ksu.ksu.edu (Brett McCoy) writes:

>Also, if a disk in the middle of the dump is bad there is no way to
>get the data from the disks following the bad one because you can't
>start reading a compressed file in the middle.

This problem solved by compact too, compact writes the information who is
need to keep the compressed Datastream in "sync" every n bytes to the
compressed data-stream.

By

-- 
Peter Cleve, Hildesheimer Str. 316, 3014 Laatzen 3, Tel. 05102/1854 (Voice)
  Energiesparen ist das moralische Aequivalent zum Krieg. (Jimmy Carter)
Xref: sparky comp.unix.solaris:216 comp.sys.sun.misc:4241 comp.unix.programmer:4673
From: atk@stekt2.oulu.fi (Antti Kyll|nen)
Newsgroups: comp.unix.solaris,gnu.gcc.help
Subject: Where to get GCC for Solaris 2.0 ?
Date: 14 Sep 92 08:34:20 GMT
Reply-To: atk@stekt.oulu.fi
Followup-To: comp.unix.solaris
Organization: University of Oulu, Dept. of EE, Finland
To: gnu-gcc-announce@prep.ai.mit.edu

Where can I find the Solaris 2.0 version of GCC (via ftp, preferably)?
We didn't get it with our Solaris 2.0 Distribution CD-ROM.
Please reply via email.

--
Antti Kyll|nen (atk@stekt.oulu.fi)
Xref: sparky comp.unix.solaris:207 gnu.emacs.help:4046