Path: nntp.gmd.de!Germany.EU.net!EU.net!uunet!gatech!news-feed-1.peachnet.edu!
news.duke.edu!eff!usenet.ins.cwru.edu!news.ecn.bgu.edu!psuvax1!
news.cc.swarthmore.edu!netnews.upenn.edu!cronkite.ocis.temple.edu!
astro.ocis.temple.edu!rt
From: r...@astro.ocis.temple.edu (r...@astro.ocis.temple.edu)
Newsgroups: comp.os.linux.help
Subject: How stable is Linux?
Date: 10 Jun 1994 04:49:54 GMT
Organization: Temple University, Academic Computer Services
Lines: 7
Message-ID: <2t8rdi$fi1@cronkite.ocis.temple.edu>
NNTP-Posting-Host: astro.ocis.temple.edu
X-Newsreader: TIN [version 1.2 PL2]


What is the likelyhood of a crash every week, every month or what ever?
Is Linux bullet-proof and crash-proof like XENIX? How buggy is it?

--
My opinion does not reflect that of Temple U. This is because it is made 
up of a non-reflective material. 

Newsgroups: comp.os.linux.help
Path: nntp.gmd.de!Germany.EU.net!EU.net!uknet!cf-cm!cybaswan!iiitac
From: iii...@uk.ac.swan.pyr (Alan Cox)
Subject: Re: How stable is Linux?
Message-ID: <1994Jun10.100053.5546@uk.ac.swan.pyr>
Organization: Swansea University College
References: <2t8rdi$fi1@cronkite.ocis.temple.edu>
Date: Fri, 10 Jun 1994 10:00:53 GMT
Lines: 16

In article <2t8rdi$...@cronkite.ocis.temple.edu> r...@astro.ocis.temple.edu 
(r...@astro.ocis.temple.edu) writes:
>
>What is the likelyhood of a crash every week, every month or what ever?
>Is Linux bullet-proof and crash-proof like XENIX? How buggy is it?

By my experience without a lot of networking its as bullet proof as good ole
Xenix was. With networking I'm normally getting reports of 5 day - 2 week
uptimes with some people getting months and a few people having problems.

My target with the networking code is to be as reliable as SunOS 4.1.3 is
on our Sun's. Nine month uptimes are good news, although I doubt most PC
hardware is up to that without some kind of flake out or device crash.

Alan

Path: bga.com!news.sprintlink.net!hookup!yeshua.marcam.com!zip.eecs.umich.edu!
umn.edu!zib-berlin.de!uni-paderborn.de!urmel.informatik.rwth-aachen.de!scotch!
bart
From: b...@rog.rwth-aachen.de (Michael Bartmann)
Newsgroups: comp.os.linux.development
Subject: BUG ? read/write on shared memory in 1.1.2x
Date: 30 Jun 1994 09:30:51 GMT
Organization: AEDVS an der RWTH-Aachen
Lines: 27
Sender: bart@scotch (Michael Bartmann)
Distribution: world
Message-ID: <2uu3cb$adk@urmel.informatik.rwth-aachen.de>
NNTP-Posting-Host: scotch.rog.rwth-aachen.de
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Keywords: bug ipc kernel socket


Hello developers,

i have some serious problems with ipc/sockets.
When I allocate a shared memory block with
shmget/shmat and try a write/read on a buffer
in this memory it works fine under 1.0.0
but spites on it with a

write: Bad address

when I use kernel 1.1.20 - 1.1.24.
I have no problems accessing the shared memory
in C-code (no segment-violation).

Any clues are greatly appreciated. Please mail me
any comments. (I am on vacation for 2 weeks from
now on and the articles would expire in my news-feed)

Thanks in advance,

             Michael

-- 
Michael Bartmann                | internet: bartm...@rog.rwth-aachen.de
Rogowski Institut RWTH-Aachen   | tel:      0241/80-7584
52062 Aachen, Schinkelstr. 2    | fax:      0241/80-7605

Path: bga.com!news.sprintlink.net!news.onramp.net!convex!cs.utexas.edu!
howland.reston.ans.net!agate!darkstar.UCSC.EDU!nic.scruz.net!
loach.cichlid.com!not-for-mail
From: a...@loach.cichlid.com (Andy Burgess)
Newsgroups: comp.os.linux.development
Subject: Re: BUG ? read/write on shared memory in 1.1.2x
Date: 5 Jul 1994 23:35:12 -0700
Organization: Cichlid.com
Lines: 42
Message-ID: <2vdjb0$ju@loach.cichlid.com>
References: <2uu3cb$adk@urmel.informatik.rwth-aachen.de>
NNTP-Posting-Host: loach.cichlid.com
Keywords: bug ipc kernel socket

In <2uu3cb$...@urmel.informatik.rwth-aachen.de> b...@rog.rwth-aachen.de 
(Michael Bartmann) writes:

>i have some serious problems with ipc/sockets.
>When I allocate a shared memory block with
>shmget/shmat and try a write/read on a buffer
>in this memory it works fine under 1.0.0
>but spites on it with a
>write: Bad address
>when I use kernel 1.1.20 - 1.1.24.
>I have no problems accessing the shared memory
>in C-code (no segment-violation).

>Any clues are greatly appreciated. Please mail me
>any comments. (I am on vacation for 2 weeks from
>now on and the articles would expire in my news-feed)

Well I'm not on vacation and I'm having the same problem. I'm using the
buffer program (comp.sources.misc/volume38) which double buffers using 
shared memory (to keep your tape streaming). 

Worked in 1.1.19, 1.1.24 gives:

loach:aab % buffer
buffer: failed to read input: Bad address
buffer: failed to attach shared memory: Invalid argument

Then after a few times gives:

loach:aab % buffer
buffer: failed to read input: Bad address
internal error, lock id 256
buffer: lock error: Identifier removed

Any ideas? I did ask for the SysV stuff and load sharing during make config.
Thanks

-- 
Andrew A. Burgess                                  a...@cichlid.com
Free newsfeeds and SLIP, Santa Cruz CA area, mail i...@cichlid.com
-- 
Andrew A. Burgess                                  a...@cichlid.com
Free newsfeeds and SLIP, Santa Cruz CA area, mail i...@cichlid.com

Newsgroups: comp.os.linux.development
Path: bga.com!news.sprintlink.net!hookup!yeshua.marcam.com!MathWorks.Com!
europa.eng.gtefsd.com!howland.reston.ans.net!pipex!uknet!cf-cm!cybaswan!
iiitac
From: iii...@uk.ac.swan.pyr (Alan Cox)
Subject: Re: BUG ? read/write on shared memory in 1.1.2x
Message-ID: <1994Jul6.151903.13103@uk.ac.swan.pyr>
Keywords: bug ipc kernel socket
Organization: Swansea University College
References: <2uu3cb$adk@urmel.informatik.rwth-aachen.de> 
<2vdjb0$ju@loach.cichlid.com>
Date: Wed, 6 Jul 1994 15:19:03 GMT
Lines: 17

In article <2vdjb0...@loach.cichlid.com> a...@loach.cichlid.com 
(Andy Burgess) writes:
>In <2uu3cb$...@urmel.informatik.rwth-aachen.de> b...@rog.rwth-aachen.de 
(Michael Bartmann) writes:
>Well I'm not on vacation and I'm having the same problem. I'm using the
>buffer program (comp.sources.misc/volume38) which double buffers using 
>shared memory (to keep your tape streaming). 
>
>Worked in 1.1.19, 1.1.24 gives:
>
>loach:aab % buffer
>buffer: failed to read input: Bad address
>buffer: failed to attach shared memory: Invalid argument

1.1.20 + are buggy - they are ALPHA test kernels for a reason. I suspect once
Linus is back this will get fixed.

Alan

Path: bga.com!news.sprintlink.net!redstone.interpath.net!ddsw1!news.kei.com!
sol.ctr.columbia.edu!xlink.net!isar.de!colin.muc.de!loki.muc.de!loki.muc.de!
not-for-mail
From: m...@loki.muc.de (Michael Lausch)
Newsgroups: comp.os.linux.development
Subject: Re: BUG ? read/write on shared memory in 1.1.2x
Date: 10 Jul 1994 23:06:05 +0200
Organization: /etc/organization
Lines: 89
Message-ID: <2vpnrt$3fh@loki.muc.de>
References: <2uu3cb$adk@urmel.informatik.rwth-aachen.de> 
<2vdjb0$ju@loach.cichlid.com> <1994Jul6.151903.13103@uk.ac.swan.pyr>
NNTP-Posting-Host: localhost.muc.de
Keywords: bug ipc kernel socket

In article <1994Jul6.151903.13...@uk.ac.swan.pyr>,
Alan Cox <iii...@uk.ac.swan.pyr> wrote:
>In article <2vdjb0...@loach.cichlid.com> a...@loach.cichlid.com 
(Andy Burgess) writes:
>>In <2uu3cb$...@urmel.informatik.rwth-aachen.de> b...@rog.rwth-aachen.de 
(Michael Bartmann) writes:
>>Well I'm not on vacation and I'm having the same problem. I'm using the
>>buffer program (comp.sources.misc/volume38) which double buffers using 
>>shared memory (to keep your tape streaming). 
>>
>>Worked in 1.1.19, 1.1.24 gives:
>>
>>loach:aab % buffer
>>buffer: failed to read input: Bad address
>>buffer: failed to attach shared memory: Invalid argument
>
>1.1.20 + are buggy - they are ALPHA test kernels for a reason. I suspect once
>Linus is back this will get fixed.
>
>Alan
>
Okay here is a quick and dirty patch to repair this. I posted it to
the kernel channel, but my internet connection is currently rather
unreliable. IMHO the shared memory should be included in the
vm_area_struct list of a process. Why isn't it? Is there a reason i've
missed? 

Patch
 

----- END OF PATCH ----
-- 
---
Magic is real unless declared integer
Michael Lausch 			e-mail: m...@loki.muc.de
Office: +41 089 93001 427	Home: +41 089 361 00 926

Path: bga.com!news.sprintlink.net!hookup!swrinde!howland.reston.ans.net!
EU.net!sunic!news.funet.fi!hydra.Helsinki.FI!news.helsinki.fi!not-for-mail
From: torva...@cc.Helsinki.FI (Linus Torvalds)
Newsgroups: comp.os.linux.development
Subject: Re: BUG ? read/write on shared memory in 1.1.2x
Date: 13 Jul 1994 00:23:30 +0300
Organization: University of Helsinki
Lines: 33
Message-ID: <2vv1ki$stp@klaava.Helsinki.FI>
References: <2uu3cb$adk@urmel.informatik.rwth-aachen.de> 
<2vdjb0$ju@loach.cichlid.com> <1994Jul6.151903.13103@uk.ac.swan.pyr> 
<2vpnrt$3fh@loki.muc.de>
NNTP-Posting-Host: klaava.helsinki.fi
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Keywords: bug ipc kernel socket

In article <2vpnrt$...@loki.muc.de>, Michael Lausch <m...@loki.muc.de> wrote:
>In article <1994Jul6.151903.13...@uk.ac.swan.pyr>,
>Alan Cox <iii...@uk.ac.swan.pyr> wrote:
>>In article <2vdjb0...@loach.cichlid.com> a...@loach.cichlid.com 
(Andy Burgess) writes:
>>>In <2uu3cb$...@urmel.informatik.rwth-aachen.de> b...@rog.rwth-aachen.de 
(Michael Bartmann) writes:
>>>Well I'm not on vacation and I'm having the same problem. I'm using the
>>>buffer program (comp.sources.misc/volume38) which double buffers using 
>>>shared memory (to keep your tape streaming). 
>>>
>>>Worked in 1.1.19, 1.1.24 gives:
>>>
>>>loach:aab % buffer
>>>buffer: failed to read input: Bad address
>>>buffer: failed to attach shared memory: Invalid argument
>>
>>1.1.20 + are buggy - they are ALPHA test kernels for a reason. I suspect once
>>Linus is back this will get fixed.
>>
>>Alan
>>
>Okay here is a quick and dirty patch to repair this. I posted it to
>the kernel channel, but my internet connection is currently rather
>unreliable. IMHO the shared memory should be included in the
>vm_area_struct list of a process. Why isn't it? Is there a reason i've
>missed? 

I just forgot about the shared mem stuff, but it should be ok now in
version 1.1.27.  The sysv shared memory is still a rather non-integrated
piece of work, so I just used the minimal vm_area_struct stuff there,
but I'll get around to fixing that properly some other time (or somebody
else will, which is even better :-)

		Linus

Path: bga.com!news.sprintlink.net!hookup!swrinde!gatech!
howland.reston.ans.net!EU.net!i2unix!pianosa.to.sem.it!pianosa.to.sem.it!
not-for-mail
From: pa...@to.sem.it (Paolo Zeppegno)
Newsgroups: comp.os.linux.development
Subject: Where has Stephen Tweedie gone??
Date: 22 Jun 1994 13:30:48 +0200
Organization: Systems & Management S.p.A.
Lines: 21
Message-ID: <2u97d8$7si@pianosa.to.sem.it>
NNTP-Posting-Host: pianosa.to.sem.it

Having been a Linuxer from the 0.12 days, and having spent too much time
reading the mailing lists and newsgroups, I see some people in the Linux
world come, do LOTS of very important stuff and then disappear. One of
the people that really contributed to the linux movement is Stephen Tweedie

While I have nothing to say about the reasons why he doesn't seem to be
with us anymore (maybe a marriage???) there is one thing he promised to
work on that I really would like to see, that is support for a compressed
filesystem. (I know about DOUBLE).

What happened in this year??


(One other project I would like to know more about is the porting of
the Sprite/BSD4.4 log structured filesys "lfs"). Now that 4.4bsd is
available, is anybody working on it? I'm wondering how easy would be
to do some experience porting lfs under userfs to start playing with
it in userland.


	paolo zeppegno

Path: bga.com!news.sprintlink.net!hookup!swrinde!emory!cherry.atlanta.com!
nntp.mindspring.com!usenet
From: rsand...@mindspring.com (Robert Sanders)
Newsgroups: comp.os.linux.development
Subject: Re: Where has Stephen Tweedie gone??
Date: 23 Jun 1994 04:02:57 GMT
Organization: MindSpring Enterprises, Inc.
Lines: 35
Message-ID: <RSANDERS.94Jun23000310@hrothgar.mindspring.com>
References: <2u97d8$7si@pianosa.to.sem.it>
NNTP-Posting-Host: msdem5.mindspring.com
In-reply-to: paolo@to.sem.it's message of 22 Jun 1994 13:30:48 +0200

In article <2u97d8$...@pianosa.to.sem.it> pa...@to.sem.it (Paolo Zeppegno) 
writes:

   While I have nothing to say about the reasons why he doesn't seem to be
   with us anymore (maybe a marriage???) there is one thing he promised to
   work on that I really would like to see, that is support for a compressed
   filesystem. (I know about DOUBLE).

I think his job's gotten extremely busy; at least that's the rumor.
Also, Stephen spent a lot of time chasing and fixing a couple of
long-lived subtle bugs in all the Linux filesystems, and that's
exactly the sort of unrewarding work that will put someone off
volunteer work for a while.

Stephen's a great guy, but he's not the only one of us who's capable
of writing a compressed filesystem.  If you really want to see, and
you're a competene programmer, here's your chance to learn a lot about
kernel internals.

   (One other project I would like to know more about is the porting of
   the Sprite/BSD4.4 log structured filesys "lfs"). Now that 4.4bsd is
   available, is anybody working on it? I'm wondering how easy would be
   to do some experience porting lfs under userfs to start playing with
   it in userland.

Well, Remy Card recently said that as soon as he could get the code
for anon. ftp, he'd work at porting it.  I think this may require some
enhancements to Linux's VFS, among other things, so it's likely to be
a big project; I'm sure Remy would appreciate some help.  As for when
4.4BSD will be available for anon. ftp, nobody seems to want to make
it available because of the guaranteed ftp storm.  FreeBSD will
probably have some of the 4.4BSD code incorporated soon (they have to
because of the USL lawsuit), but there's no telling when.  Several
months, at least.

  -- Robert

Newsgroups: comp.os.linux.development
Path: bga.com!news.sprintlink.net!hookup!usc!howland.reston.ans.net!
gatech!swrinde!pipex!lyra.csx.cam.ac.uk!warwick!uknet!cf-cm!cybaswan!
iiitac
From: iii...@uk.ac.swan.pyr (Alan Cox)
Subject: Re: Where has Stephen Tweedie gone??
Message-ID: <1994Jun23.131929.10685@uk.ac.swan.pyr>
Organization: Swansea University College
References: <2u97d8$7si@pianosa.to.sem.it> 
<RSANDERS.94Jun23000310@hrothgar.mindspring.com>
Date: Thu, 23 Jun 1994 13:19:29 GMT
Lines: 10

In article <RSANDERS.94Jun23000...@hrothgar.mindspring.com> 
rsand...@mindspring.com (Robert Sanders) writes:
>enhancements to Linux's VFS, among other things, so it's likely to be
>a big project; I'm sure Remy would appreciate some help.  As for when
>4.4BSD will be available for anon. ftp, nobody seems to want to make
>it available because of the guaranteed ftp storm.  FreeBSD will

src.doc.ic.ac.uk:/packages/unix/4.4bsd-lite/......

ALan

Path: bga.com!news.sprintlink.net!hookup!swrinde!howland.reston.ans.net!
xlink.net!scsing.switch.ch!swidir.switch.ch!univ-lyon1.fr!jussieu.fr!card
From: c...@masi.ibp.fr (Remy CARD)
Newsgroups: comp.os.linux.development
Subject: Re: Where has Stephen Tweedie gone??
Date: 26 Jun 1994 20:07:48 GMT
Organization: Laboratoire MASI - Universite Pierre et Marie Curie 
- Paris - France
Lines: 45
Message-ID: <2ukn6k$men@vishnu.jussieu.fr>
References: <2u97d8$7si@pianosa.to.sem.it> 
<RSANDERS.94Jun23000310@hrothgar.mindspring.com>
NNTP-Posting-Host: ares.ibp.fr
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

In article <RSANDERS.94Jun23000...@hrothgar.mindspring.com>,
Robert Sanders <rsand...@mindspring.com> wrote:
] I think his job's gotten extremely busy; at least that's the rumor.
] Also, Stephen spent a lot of time chasing and fixing a couple of
] long-lived subtle bugs in all the Linux filesystems, and that's
] exactly the sort of unrewarding work that will put someone off
] volunteer work for a while.

	I can't speak for Stephen but I think that he is overloaded with
work and could not work much on the Linux kernel during the last months.

] Stephen's a great guy, but he's not the only one of us who's capable
] of writing a compressed filesystem.  If you really want to see, and
] you're a competene programmer, here's your chance to learn a lot about
] kernel internals.

	You're right but any volunteer should check with Stephen by e-mail
to avoid duplicating efforts, just in case.

] Well, Remy Card recently said that as soon as he could get the code
] for anon. ftp, he'd work at porting it.  I think this may require some
] enhancements to Linux's VFS, among other things, so it's likely to be
] a big project; I'm sure Remy would appreciate some help.  As for when
] 4.4BSD will be available for anon. ftp, nobody seems to want to make
] it available because of the guaranteed ftp storm.  FreeBSD will
] probably have some of the 4.4BSD code incorporated soon (they have to
] because of the USL lawsuit), but there's no telling when.  Several
] months, at least.

	I already have LFS since it is now included in NetBSD current.
I have taken a look at the LFS code and porting it to Linux is far from
trivial.  Like FFS, LFS relies on the BSD VFS and buffer cache features
and there is a lot of work to do to make it fit in the Linux kernel.

	BTW, I have been overloaded with work too (actually, the whole
set of ext2fs programmers have been recently :-() and I won't be able to
work on it in the next weeks (next week is the Linux Conference in
Heidelberg and I had to work a lot to prepare the FS presentations).

	After I come back from Germany, I will look into LFS again and
I'll try to incorporate it in Linux.

]   -- Robert

		Remy