HDTenEightyP/NetNews huggingface dataset:
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] How can I expand data segment?
Date: 6 Oct 92 18:33:11 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.uni-duisburg.de

In <1asb9mINNcov@usenet.INS.CWRU.Edu> ljo@r2d2.eeap.cwru.edu (L. Jonas Olsson) writes:

>In article <veit.718359993@du9ds3> veit@du9ds3.uni-duisburg.de writes:
>>In <45240004@hpycla.kobe.hp.com> yas@hpycla.kobe.hp.com (Yasuyuki Suzuki) writes:
>>
>>>I have 50MB of swap space on my 386BSD disk. But the data segment size
>>>of each process seems to be limited around 4MB.
>>
>>>How can I expand data/stack/text segment size of each process?
>>
>>limit datasize unlimited
>>limit stacksize unlimited
>>

>With the stock sources this will give you a 32MB limit on the data size,
>for even more you need to edit /usr/src/sys.386bsd/i386/include/vmparam.h.
>In this file you have the parameters for default data size (DFLDSIZ) and
>max data size (MAXDSIZ) among others. I have them set to 16 and 128MB and

That's right. Using the above limit commands and re-issuing 'limit' again
shows the limit on the datasize.

>have successfuly used up to 45MB in one process. The system seems a little
>more flaky though so some other tweaking/bug fixing might be needed. Also
>note that the system grinds to a halt when the swap space is used up, there
>is no friendly message "virtual memory exhausted" and the mallocs don't
>return 0.

This is also right, and this was the reason for me *not to recommend*
modification in the vmparam.h part.

>Jonas Olsson
>ljo@po.cwru.edu

Holger
-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
|  | /   Dept. of Electr. Eng.   |   Sorry, the above really good fortune has
|  |/    Inst. f. Dataprocessing |      been CENSORED because of obscenity"
From: rich@Rice.edu (Richard Murphey)
Newsgroups: comp.unix.bsd
Subject: Re: xdm not running because cannot find crypt.
Date: 6 Oct 92 04:00:41 GMT
Reply-To: Rich@rice.edu
Distribution: usa
Organization: Department of Electrical and Computer Engineering, Rice
	University

In article <1aqnsrINNivm@gossip.pyramid.com> dinesh@pyramid.COM (Dinesh Jalisatgi) writes:
    When I run xdm on X386 it fails saying that crypt not found.  When loaded the system using

    extract bin01  it didnot load crypt. Does crypt come with the system or.

There is a (dummy) crypt in /usr/lib/libc.a in the bin01 distribution.
It's staticly linked in to xdm, and export restrictions prevent us
from providing binaries with a real crypt.  Since it's linked in, I
can't imagine why it's not found.  Rich
From: hedrick@geneva.rutgers.edu (Charles Hedrick)
Newsgroups: comp.unix.bsd
Subject: Re: Catch What They're Saying About Us...
Date: 2 Oct 92 22:11:19 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

erc@unislc.uucp (Ed Carp) writes:

>Not to flame Charles, but I find it hard to believe that if the courts find
>that the NET-2 distribution *does* contain AT&T proprietary code, that they
>will not issue a "cease and desist" order prohibiting UCB from distributing
>the NET-2 code.  The issue of whether or not derivitives of NET-2 are
>"non-commercial" or not is irrelevent.  I don't agree with your friend on
>his interpretation - but what you or your friend or I or Bill Jolitz feel
>about the issue is irrelevent, too.  What the judge says is the only
>relevent issue.

I'm not the best one to discuss this, but you will note that claims
are being made other than simply that NET-2 contains ATT code.  There
is also a claim that Berkeley exceeded the scope of their educational
license.  I think (and I hate to speak for him) that my lawyer friend
thought the question of whether Berkeley had used the ATT product as
the basis of commerial work might not depend upon whether the final
product had any ATT code in it.  He didn't go so far as to predict
what a final outcome might look like if the court accepted such a
theory.  One could imagine that they might decide that indeed Berkeley
had developed software for commercial use on a system that ran a
version of the Unix(TM) operating system licensed only for educational
use.  In compensation for this dastardly deed, they would owe ATT the
cost of a commerical Unix license.  This alleged offense would be
independent of whether the code they developed has any ATT code in it.
This would be a Pyrrhic victory indeed for ATT.  I am not predicting
this result, nor am I saying I would agree with it.  I'm just trying
to caution you that the issues he saw in the discussion were somewhat
different than those that we as hackers see.
From: rcjvdb@rw9.urc.tue.nl (Jan van den Bosch)
Newsgroups: comp.unix.bsd
Subject: Re: Problems in X
Keywords: X
Date: 30 Sep 92 08:22:54 GMT
Reply-To: rcjvdb@urc.tue.nl

tim@kimba.catt.citri.edu.au (Tim Liddelow) writes:

>I have X installed fine.  The only problems I am encountering seem to
>be keyboard related.  Sometimes, when I enter text in an xterm or even
>under xdm, I will get uppercase characters and am unable to get back to lower
>case.  
I've had the same problems, allthough I used the starx script from the
"X FAQ" from Amacio Hasty, posted 5 aug.
The script from the FAQ: (Why is the X server not accepting characters
from the keyboard? )
* If you start X from your console, X is probably competing with
* your shell for characters from the keyboard. I usually start X from
* a script :
   xdm -config <where you installed X11>/lib/X11/xdm/xdm-config
   stty raw
   sleep 99999999
< end of faq>
The reason for the behaviour: The shift key is of make/break type,
generating two scancode's for each event. If the break (release)
event is not caught by the X program, then it (pccons) stays in the 
shift-state!
The same can happen with the control key.
What happens to me was: sometimes I started 'startx' in the background, 
because  I used to start most x programs like that, and the strange
shift problem was there!
Remedy: DON'T START startx IN THE BACKGROUND! 
>Is this the default handling (like login) which senses you have
>only uppercase available ?  Also, sometimes when running some x apps, like
>the new tetris that was posted recently, the input is supposed to be in
>the x app window, but the text appears in the xterm, even though the window
>manager focus is definitely in the X application.  
Must be a programm writing to stderr or stdout, I think the wm-focus
only handles intput.
>Also, the tty driver also
>seems to get into cooked mode with control characters from time to time.  This
See above (same as shift-problem)
>is very unfortunate if you happen to press 'D' ... ;-)
Indeed
>Also, the output of ps returns -1.0 for certain percentages - is this the
>floating point emulation bug ?  (I have no co-processor).

>Tim.
Jan v.d.Bosch
rcjvdb@urc.tue.nl
Newsgroups: comp.unix.bsd
From: nbladt@autelca.ascom.ch (Norbert Bladt)
Subject: Re: device 0/0 0/1
Keywords: as0 sd0 boot swap root device
Organization: Ascom Autelca AG, Guemligen, Switzerland
Date: Mon, 5 Oct 1992 08:16:10 GMT

kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes:


>I'm running 386bsd on a ah1542b with as0a as root, as0b swap, as0h /usr.
>Yesterday I installed Julian Elischers (thank you, Julian), scsibeta2.1
>release because my DAT tape (DEC TLZ04) was never recognized by the as
>driver. With the above SCSI driver it is recognized.

>But I have a strange behaviour when booting. I always get 
>no swap space present (yet)   and  later: 
>savecore: device not configured as0b.

>I could not figure out where this string occurs in the kernel code. I did a 
It does not occur in the kernel. This message is from one of the programs
which are started during boot, e.g., in /etc/rc.
This program's name is (didn't you guess it from the error message):
	savecore
I had exactly this problem and solved it by looking at three things:
	1. If you had a line containing
		... root on as0 swap on as0
	   in your config file (e.g. SCSITEST), you should change that
	   to
		... root on sd0 swap on sd0
	2. Look at the "swap386bsd.c" file in your configuration directory
	   This should include something like "sd0".
	
	3. Do a "disklabel -r sd0".
	   If it doesn't show something like
		b: ....   swap ...
	   then this could be another cause of your problem. You have to fix it.
	   I won't recommend writing a new disklabel here, because after my
	   bad experience with disklabel I am very careful using it.
	   Do not misunderstand this statement. The actions "disklabel"
	   did to my harddisk were all caused by me !


>strings 386bsd and the only string 'as' was in wdswfdwtas (or something like )
>which I located in autoconf.c. The new driver is using sd0 instead of as0.
>I'm not using wd0 (wdc0) in my config file. Should I? Presently I don't 
>know whether my system is using swap space at all. Following the messages
>it does not but I did a lot of kernel builds etc. on the system without
>problems. I'd rather solve this problem than continue to live with it.
Yes. I guess that your system is using swap space. However the "savecore"
program couldn't find the device, that's it.

>Any help/comments etc. are much appreciated.
Hope it did.
I am sorry, I can't be more specific, but I have the system at home
and I am at work, now.

Norbert.
-- 
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt
-- 
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt
From: ghod@drycas.club.cc.cmu.edu
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] fixing ps: major/minor numbers for /dev/console wrong?
Date: 28 Sep 92 03:23:53 GMT
Organization: Carnegie Mellon Computer Club

In article <wutcd.717632941@hadrian>, wutcd@chemnitz.guug.de (Joerg Wunsch) 
writes:
> ghod@drycas.club.cc.cmu.edu writes:
> 
>>Greetings...
> greetings return:-)
> 
>> [some ps trouble...]
> 
>> [1) some names not found...]
>>Problem #1 is not, ps's fault: it's the kernel. The stock kernel in the 0.1
>>...
> Okay, it's quiet clear: the dist kernel had to fit onto a diskette:-)
> 

Actually, this was a true honest to goodness bug, not an attempt to whittle
the kernel down to fit onto the distrubution diskette. The kernel on dist.fs
is slightly larger than 400 Kbytes. The one I ftp'ed from
rachel.ibmpcug.co.uk was about 380 Kbytes, and included more drivers than the
stock kernel. Go figure. :)

Also, upon further investigation, ps's inability to print command line args
doesn't appear to be due to a bug in its code. The call used to get the 
arguments from the kernel is kvm_getargs(), which I'm assuming is related
to the kvm_getcmd() call in SunOS. kvm_getargs() seems to return only the
command name, not the command line args, so I guess the solution will indeed
lie in some kernel hacking. Unfortunately, I don't have the space to build
a new kernel (and with only a 16Mhz 386SX it would probably take days :)
so I guess I'll just have to wait for the next release or patch.

--Bill Paul
Assistant System Administrator
New Windsor Associates L.P.

	ghod@drycas.club.cc.cmu.edu  -or-  ghod@drycas.bitnet

	"A black hole is what happens when god divides by zero."
Newsgroups: comp.unix.bsd
Newsgroups: comp.unix.bsd
Subject: [386BSD] FIFO support: an update
From: scott@lopez.marquette.MI.US (Scott Reynolds,Insanity)
Date: Wed, 30 Sep 1992 09:33:41 EDT
Organization: Great White North/UPLink

I've narrowed it down a bit further.  In kern/fifo_vnops.c I added a
printf() to check what the number of readers and writers on the fifo was
(and the address of the fifo structure to make sure I'm looking at the same
one).  The result of this was that the first open (for reading) proceeds
normally:

	create the fifo structure
	tack it onto the vnode
	setting up the sockets
	zeroing out the count of readers and writers
===[ above this line executes only on creation of fifo ]===
	printf() -> "addr = xxxx, readers = 0, writers = 0"
	increment number of readers
	tsleep() waiting for writers to start up

The second open, for writing, goes like this:

	printf() -> "addr = xxxx, readers = 0, writers = 0" !!
	increment number of writers
	tsleep() waiting for readers to start up

The "addr = xxxx" varies between tests but always agrees on any given
trial.  The surprising part is that the number of readers and writers
is always 0!  Some experimenting proved that setting the number of readers
and writers to 1 in the structure init will give a "working" fifo, but the
problems associated with this hack in the real world are obvious.  [In case
you're wondering, the printf() always prints "readers = 1, writers = 1"
when I do this.]

How can this happen?  The way I understand it, kernal malloc() returns
memory for use by the kernal and not the user process, and memory obtained
in this way is semi-permanent in the sense that it stays around as long as
the kernal needs it and it doesn't have any relationship to the user
process that made the call.  This is supported by the evidence I've
accumulated, also (I put a printf() inside the fifo creation code at one
point).

I'm baffled.  Nothing in this code appears to be incredibly complex yet it
has defied my best efforts to track down the problem.

Suggestions?  Comments?  Please let me know, even if you think it's obvious
and I haven't mentioned it here.
--
Scott Reynolds			scott@lopez.marquette.MI.US
Great White North/UPLink	alternate:  A094@NMUMUS.BITNET
	"Insufficient facts always invite danger." -- Spock
Newsgroups: comp.unix.bsd
From: anything@max.u.washington.edu
Subject: [386BSD] looking for a good adduser script
Organization: 
Date: Fri, 2 Oct 1992 21:19:10 GMT

Does anyone have a good adduser script they would be willing to pass on?

Newsgroups: comp.unix.bsd
From: jewels@well.sf.ca.us (Julian Gordon)
Subject: Setsid system call
Keywords: session, system calls
Organization: Whole Earth 'Lectronic Link
Date: Thu, 1 Oct 1992 00:22:22 GMT

We are trying to port the bsd version of telnetd to a Dynix 3.0.1 OS,
and have found that it has no setsid call. We would like to if anyone
has encountered this same problem. 

As the man page states it:

DESCRIPTION
	 setsid  executes  command  after  altering   the   execution
	 environment  such  that  the  next  non-controlling terminal
	 opened will be assigned as command's controlling terminal.

We would like to know if anyone has attempted to fudge this system
call on a system that doesn't have this call. Or if there is any
source available to show us how it is implemented.

Thanks

*******************************************************************>
*            ~~ Jewels ~~ of ~~ Thought ~~                        ->
*   Breaking the electronic frontier, and forging into cyberspace. >
*   By increasing communication, are we also breaking it?         ->
*   "Television allows thousands to laugh at the same time at the  >
*    same joke, and still remain alone"                           ->
*                           Bertrand Russell.                     ->
*    Will computers do the same....                               ->
*                                                                 ->
* /\/\ Julian Gordon             /\/\     (jewels@well.sf.ca.us)   >
* /\/\ The WELL,                /\/\/\    (415) 332-4335 9-5 PDT  ->
* /\/\ 27 Gate Five Road,       \/\/\/                             >
* /\/\ Sausalito, CA 94965       \/\/                             ->
*******************************************************************>
From: lafollet@astro.ocis.temple.edu (Paul Lafollette)
Newsgroups: comp.unix.bsd
Subject: 386BSD/Xfree com ports questions
Date: 27 Sep 92 14:30:15 GMT
Organization: Temple University
X-Newsreader: Tin 1.1 PL5

Wow... I did x386install, twiddled a couple of lines in
Xconfig, typed xdm and got an X login!  I am impressed.
Now, however, I have a couple remaining problems:

1) I have a Genius mouse on com1.  Does one of the
standard protocols useable in Xconfig work for it?
(I mean the thing where I get to choose from {logitech, microsoft ...}
If not, what source file do I need to hack and does anyone know if
Genius will release to me their encoding scheme (I only have
documentation for microsoft's).  Or, better still, can someone
send me docs for this beast. 
Actually, somehow I had gotten the idea somewhere that it used
the same encoding scheme as microsoft, but it doesn't work
when i choose the Microsoft keyword.  Of course this could be
related to question 2 which is...

2) One of the changes I made in Xconfig was to change
"/dev/tty00" to "/dev/com1".  Was this reasonable?
More important, how do I get the baud rate set right on
com1?  Does it suffice to include the speed paramater in Xconfig?
Do i need to make changes to ttys or gettytab or other mysterious
Unix files?  do i need to make com1 off instead of on?
Sorry to ask "baby" questions but I am mostly a VMS expert, and
Unix management is still a bit of a mystery to me.  Without
apropos or lp working it is tough to rtfm (although Nemeth, Snyder
and Seebass has been a big help.)  

3) Related to number 2... i have an internal modem on com2.  I
would like to configure it so that when i am home i can use
it for dialout with tip or (God help me) slip.  On the
otherhand when I am at work, I would like to be able to use
this as a dial-in port.  Is this possible?  Is it possible
to do it so I don't have to remember to make a change before
I go running out the door late for class? :)

Thank all of you who post here.  The questions are often as
useful as the answers.

Paul LaFollette
CIS Dept.
Temple University
lafollet@astro.ocis.temple.edu
Newsgroups: comp.unix.bsd
From: julian@uhccvx.uhcc.hawaii.edu (Julian Cowley)
Subject: Re: BEWARE:  stupid placement of swap space...
Organization: University of Hawaii
Date: Mon, 5 Oct 1992 05:43:27 GMT

Tore Haraldsen:

>I think this handling of the swap partition is quite normal for BSD type
>systems. You NEVER put the swap partition first on the disk. The swap
>partition is used in a way analog to a raw device...

This may be somewhat off the original subject, but isn't the best
place for a swap partition in the middle of the disk?  If it's on the
end, then the head has to move twice as far to reach the partition, on
the average.

Julian Cowley
julian@uhccvx.uhcc.hawaii.edu
Newsgroups: comp.unix.bsd
From: chuck@coplex.com (Chuck Sites)
Subject: Re: Xfree & Paradise VGA Plus card
Organization: Copper Electronics, Inc.
Date: Thu, 1 Oct 1992 17:29:06 GMT
Keywords: (or:  Don't be stupid like me :-)

toreh@bootes.sds.no (Tore Haraldsen) writes:

>.. is it possible to run Xfree/X386 on a Paradise VGA Plus? Under DOS it
>supports up to 800x600. What would the Xconfig file look like?

It is possible, I know I'm using just that type of board right now.  
Getting it up and running was a feat though since the X386.0 doc file
has a small misprint.  The Chipset is not pvga. It's pvga1.   Anyway,
under the line in /usr/X386/lib/X11/Xconfig VGA256, add, `chipset "pvga1"`.
You will need a 512k board.  There seems to be a problem with 800x600 mode
that causes pixels to be misplaced in the center 1/3 of the screen. 640x480
works fine.  Anybody out there might have a fix for that?
  

>-- tore


Have Fun,
Chuck Sites
chuck@coplex.com 
Newsgroups: comp.unix.bsd
From: johnp@mundil.cs.mu.OZ.AU (John Steve PETROU)
Subject: free() - not working properly
Organization: Computer Science, University of Melbourne, Australia
Date: Wed, 30 Sep 1992 04:13:16 GMT



I was wondering if anyone else has had the same problems as me with
free().

I am running a 486 with 8MEG of memory and 16MEG of swap space. I am
currently using the kernel supplied with the lasest release of X386, but
have had the same problem with other kernels.

If a process mallocs and frees memory durings its normal execution, I find
that ps -axv reports that the VSZ is always growing. I first noticed it
while using xman. The more manual enteries I read the more I noticed disk
activity increasing. (I closed each page after reading it BTW). ps -axv
showed that the more I used xman the greater the VSZ. I found the same thing
with xgif, after increasing the size of an image the VSZ increased as
expected but wouldn't decrease when the image was reduced. I wrote the
following couple of lines to test the problem out of X386, and the same
problem could be seen. 

main()
{
	int i;
	char *p. c;

	while(1) {
		if((c = getrchar()) == 'q') exit(0);
		p = (char *)malloc(100000 + 10000 * i++);
		free(p);
	}
}

I checked VSZ after a few loops and it just kept growing. I have also 
noted that the more often these programs are run the worse the performance
due to excessive swapping.

Is this a problem ?
Thanks
John Petrou
From: jdevries@apple.com (Jeff DeVries)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Works at 8Mz; flaky at 33Mz; Any ideas?
Date: 30 Sep 92 22:30:51 GMT
Distribution: usa
Organization: Apple Computer Inc, Cupertino, CA

While running off the distribution floppy I discovered that I could
run reliably with the CPU clock at 8Mhz (its a 486), but at 33Mhz I
would get general flakiness (sometimes panics, but different types 
of errors in general).

Now that I have the full binaries installed, I can still run at 8Mhz,
but if I bump up to 33Mhz I hang pretty regularly during "Starting Network".

Any ideas about what is going on, and what I can do about it?
Any comments are welcome (it they're on this topic, that is B^)

Jeff De Vries
jdevries@apple.com
From: pejn@cc.uow.edu.au (Paul Nulsen)
Subject: Re: free() - not working properly
Organization: University Of Wollongong
Date: Wed, 30 Sep 92 07:43:01 GMT

johnp@mundil.cs.mu.OZ.AU (John Steve PETROU) writes:
>I was wondering if anyone else has had the same problems as me with
>free().

I am having problems that look as though they are caused by memory leaks
too. The first symptom I noticed is that there seems to be excessive
swapping under X windows. As the only user, with 3 xterms, xman (maybe one
page open) and xclock running the system quickly gets into a state where it
has to swap each time I move between xterms - even when I just hop back and
forth between two. Perhaps I do not understand memory management very well,
but this seems excessive to me.

My system is a 486 with 8 MByte memory and about 30 Mbyte of swap space.
When I try to format the jove manual, groff died with an out of memory
message. This happens even when I try to do it as the only user (without X
windows) immediately after a reboot. Again, I have not investigated this
very carefully, but I can't see anything obvious wrong with the manual
source. I suppose it could be a bug in groff too. Any ideas anyone?

Paul Nulsen
pejn@wampyr.cc.uow.edu.au
Newsgroups: comp.unix.bsd
From: plek@admiral.uucp (peter eriksson)
Subject: 3.5" boot disk?
Reply-To: plek@admiral.uucp (peter eriksson)
Organization: The Grid/Waffle BBS, 203-661-2873, -1279, -0450, -2967
Date: Wed, 30 Sep 1992 18:16:12 GMT

You cat format a 3.5" disc to 1.2 MB, i don't know the reason. But
you can fool MSDOS format to think that the 3.5" disk driver is a
5 1/4 disc driver. Then you can use FORMAT A: /f: 1.2 .
(this can be a problem on some disc).

HOW DO I DO ?
        You must go to the SETUP program and here change the 
        parameters for driver A to 1.2 MB.
     (don't forgott to rechange the SETUP).

ps: to do this you need 2 disk drivers, A - 1.44,  B - 1.2 MB.

--
plek%admiral.uucp@yale.edu (peter eriksson) <yale!admiral!plek>
The Admiral's Public UNIX - Greenwich, CT - System Administrator: Doug Fields
(HST/V32) (203)661-2873 -- (PEP/V32) -1279 -- (V32) -0450 -- (V29/MNP6) -2967
>FREE!< Unix shell accounts, Usenet access, and Internet-style mail available
Newsgroups: comp.unix.bsd