HDTenEightyP/NetNews huggingface dataset:
From: tomm@Ingres.COM (Tom Markson)
Newsgroups: comp.unix.bsd
Subject: Re: xlock won't recognize password
Date: 30 Sep 92 23:24:39 GMT
Article-I.D.: pony.1992Sep30.232439.2262
Organization: Ingres, Alameda CA 94501

tim@kimba.catt.citri.edu.au (Tim Liddelow) writes:
> Hi all.  I compiled up a X11R5 raw version of xlock from the X contrib
> directory at one of the X mirror sites here.  The problem is that it compiled
> up pretty well fine, but it won't recognize my password.  Now could this be
> anything to do with crypt() I added to the standard C library ?  Or can't
> it handle the shadow password entries (surely that would be built in to 
> the system calls.)

I made this work under BSDI.  The first thing is that xlock must be setuid
root or it won't be able to get the password information.  Second, I think
I had to change it so that it did a getpwuid instead of whatever it did.
THis is a side effect of making it setuid.  It would always want root's
password instead of the users.  Play around with it a bit.  One thing I
never got to work correctly was color under xlock.  No matter how hard I
fiddled, I could not get color to work - the locks were always in black
and white.  Did anyone get this to work?

Tom
Tom Markson					Unix Systems
email: tomm@ingres.com
From: lurch@ee.latrobe.edu.au (Geoffrey Liersch)
Newsgroups: comp.unix.bsd
Subject: vm86 system call
Date: 28 Sep 92 05:46:49 GMT
Organization: Department of Electronic Engineering, La Trobe University

Has anyone got any comments on where to start the implementation of the 
vm86 system call such as the system call number, parameters, header files to
be changed or any other hints/documentation that I should be aware of as I
am looking at implementing such a call?

Alternatively is there any one else out there that is working on such an 
implementation as it is needed before a dos emulator can become a reality!

Thanks in advance,

Lurch
From: alex@am.sublink.org (Alex Martelli)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD's non-standard C library
Date: 4 Oct 92 09:04:10 GMT
Article-I.D.: am.1992Oct04.090410.26720
Organization: Premiata Famiglia Martelli & Figli

wutcd@chemnitz.guug.de (Joerg Wunsch) writes:

:>Oops, Kendall is quiet right with his remarks. Of course, the existing
:>versions of tolower()/toupper() aren't right. The macros may be omitted,
:>(does ANSI really state there must be _macros_ for this???), but the
:>functions in /usr/src/lib/libc/gen/isctype.c do the same dirty job.
:>They should be patched to test for isupper()/islower() before applying
:>the diff value - but this value must be taken from the character class
:>definition (as the is*() functions already do).

:>If i have half an hour left, i'll post the diff's - all the other people
:>surely will make this themself.

I once benchmarked the is*() and to*() functions from ctype.h as macros
using table-lookup instead and got huge speedups... that was in some PC
C compiler long ago, but I believe a simple lookup will still be
superior to a comparison, if and addition, and you need only pay a
few hundred bytes (256 each for toupper(), tolower(), and is*() since
the latter can make do with 1 byte/char by using the bits as flags for
lowercase, uppercase, digit, etc, for example isalnum() will do the
lookup and & the flag byte with (ISLOWER|ISUPPER|ISDIGIT)).
-- 
Alex Martelli - alex@am.sublink.org - +39 (51) 250434 - Bologna, Italia
Newsgroups: comp.unix.bsd
Subject: SCDOWN
From: system@amc.uva.nl
Date: Fri, 25 Sep 1992 14:44:57 GMT
Organization: Central computer department

Dear networks,


I work on a ULTRIX 4.3 BSD DECSTATION 5000/125. There are two serial
ports. One of them i want to use as a terminal line to be able login
on a remote host.

I know, one can use the terminal directly, but i want to you use a serial
port of my machine. Instead of using many terminals, computers etc. i
want just open a window and use this port!!!!

Does anybody know how to do that??

Thanks in advance,


Frank Wetzels
e-mail: wetzels@amc.uva.nl
bitnet: wetzels@hasara51
From: David.Fox@Saigon.COM
Newsgroups: comp.unix.bsd
Subject: ecvt(), where's the source, Luke?
Date: 4 Oct 92 02:19:36 GMT
Organization: Station Zebra Corp, Sunnyvale CA Ph:408-739-1520

Hi.  I'm compiling a program that needs the ecvt() function.  Anyone
have source to this one?
Xref: sparky comp.unix.bsd:6984 aus.archives:196
From: cagney@cs.adelaide.edu.au (Andrew Cagney - aka Noid)
Newsgroups: comp.unix.bsd,aus.archives
Subject: Xfree86 on ftp.cs.adelaide.edu.au:pub/Xfree86-1.1
Date: 6 Oct 92 09:16:00 GMT
Reply-To: cagney@cs.adelaide.edu.au (Andrew Cagney - aka Noid)
Distribution: aus
Organization: Comp Sci, Uni of Adelaide, Australia
NNTP-Posting-Host: winnie.cs.adelaide.edu.au


For a short while, the binaries for the new release for Xfree86 for 386bsd
will be available on:

	 ftp.cs.adelaide.edu.au

in the directory

	pub/Xfree86-1.1

					Andrew Cagney

PS: As of this posting, they are still being brought across :-)
PPS: AU computer science students: they are in ~ftp/pub/Xfree86-1.1
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: 386BSD and IDE drives
Organization: Weber State University  (Ogden, UT)
Date: Fri, 2 Oct 92 05:34:57 GMT

In article <1992Oct1.150420.9211@sceard.Sceard.COM> mrm@Sceard.COM (M.R.Murphy) writes:
>>People!  Please send this information to Mike for summary!
>
>Terry volunteers me to collect information about drives and controllers that
>work with 386bsd as punishment for my disagreement with his clearly bizarre
>contention that expensive SCSI systems are better than Yugos with blown head
>gaskets. I'll do it. If you send me a quick e-mail with the controller type
>and brand (noname ok), the drive size and model if known, in a few days I'll
>summarize. It might be nice to include CPU type, speed, and BIOS if known.

	Oops.  I thought when you said you "had mailed asking about this"
that you were the guy I remembered asking for the info to summary... boy,
is my face red!  I remebered that someone had asked, but I couldn't
remember who, and the article had expired.

	But since you have "volunteered"... 8-).


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: wutcd@chemnitz.guug.de (Joerg Wunsch)
Subject: Re: How to format UNIX floppies under 386BSD
Organization: tu-chemnitz
Date: Fri, 2 Oct 1992 19:48:05 GMT

levinson@vax.sonoma.edu writes:

>...
>-- 
>well, there is format /q in MSDOS which just overwrites the root directory.
>--
>Eric Levinson

I've got a pretty formatation prog for dos which allows to re-format
the first two cylinders only, written by a friend of mine. If there's
interest, i hope i could post it here (or elsewhere).

	J"org
--
J"org Wunsch, TCD GmbH Dresden, R"ahnitzgasse 18, D-O-8060 Dresden
                                                              \     ~.~. 
	joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de         \   ~  | ~ 
	voice: +49-351-5965 137                                 \    ===
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Motif for 386BSD
Keywords: Motif 386BSD
Organization: Weber State University  (Ogden, UT)
Date: Mon, 28 Sep 92 20:25:55 GMT

In article <7300@bigbird.hri.com.hri.com> erich@hri.com (Eric Hilfer) writes:
>I'm afraid I lost track of this thread, but I am still interested.
>Did someone say that they had built Motif on 386BSD?  I have just tried building
>Motif 1.2, and after a little fooling around it compiled without errors
>or missing symbols.  BUT, the mwm manager and most of the demos crash at random
>locations!  Those that run can only make Simple XmStrings, any compound string
>comes out garbled.  The Motif release notes say that internationalization
>must be present in the X11R5 build and in the C library.

The problem is with a GCC register optimization bug similar to that found
on Berkeley C compilers ala SunOS 4.1.2.

Recode the Xt routines that  have lvalues assigned to a function of
themselves where the variable in question is either a register or is
promoted to one.

Alternately, turn off optimization, add "x++; x--;" for every variable "x"
used this way in a function, declare it static, declare it volatile, or
declare it right before the function instead of in the scope of the
function.

Once the Xt library was fixed, I had no problems getting Motif 1.2 to
work.


					Terry Lambert
					terry_lambert@npd.novell.com
					terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: pk@cs.few.eur.nl (Paul Kranenburg)
Subject: Re: Marvellous Memory Munching Make
Keywords: where does it go? what does it do?
Reply-To: pk@cs.few.eur.nl
Organization: Erasmus University Rotterdam
Date: Mon, 28 Sep 1992 10:19:28 GMT

In <1992Sep25.174613.19954@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:

>In article <1992Sep25.020038.28923@citec.oz.au> sgccseh@citec.oz.au (Steve Hocking) writes:
>>
>>	I've noticed that make seems to eat memory like there's no tomorrow.
>>Often I have to stop & restart a make because gcc et al complains about
>>being out of memory. I know that if I reinstall with something other than
>>the default swap size, then the problem will be hidden, but it seems like
>>this is not the optimal solution. BTW the leak only seems to happen when
>>make actually kicks off another program.

>This is because of the malloc before the exec.  Change the "vfork" used to
>start the child process to a "fork" and the memory leak will go away.  This
>will make make somewhat slower, but since the malloc occures into the parents
>heap, this is the culprit.  The problem gets worse on larger environments
>set up by the user.

In the new VM system, the only difference between fork() and vfork() is in
scheduling: the parent waits until its child either exits or execs. Sharing
of address spaces on longer occurs.
From: ygoland@edison.seas.ucla.edu (The Jester)
Newsgroups: comp.unix.bsd
Subject: Greetings and Salutations oh BSD users!
Date: 29 Sep 92 02:34:49 GMT
Organization: PGP VER2 Key Available Upon Request

This post will serve two purposes,
	1.It will hopefully generate a response that will tell me
	what I want to know.

	2.It will help other newbies figure out what the hell is
	going on here.

	(OH and if theres a faq, can someone tell me where?)

My questions are as follows:
	I'm a dos/os/2 user (translation:My drive is very full), I
	love unix (i'm a hacker, can you tell? =) and would love to
	have it on my 486 (who cares if I have to buy another hard
	drive (my 210 is really really full), can anyone spare
	$300?) (I say 486 because I hope that will take care of any
	questions about 'is my computer able to run it')). So I
	would like to know:
		1.How much disk space does it take?
		2.How easy/difficult is it to install?
		3.How much 'other' resources does it need?
		4.Now that i have it? wWHAT THE HELL DO I DO W/IT?!?
		 (NOTE:The response "anything you damn well please"
		       is not to be considered a legit one =) 

These seem to be fairly reasonable questions, I look forward to the
responses.
				The Jester
-- 
For some reason unintelligible to me, Lord Acton's dictum that
"Power tends to corrupt and absolute power corrupts absolutely"
is rarely raised in connection with judges, who...possess power
..that comes [close] to being absolute"-Judge Bork
From: gab10@cd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: Greetings and Salutations oh BSD users!
Date: 2 Oct 92 07:02:29 GMT
Organization: Amdahl Corporation, Sunnyvale CA

In article <8200@lee.SEAS.UCLA.EDU>, ygoland@edison.seas.ucla.edu (The
Jester) writes:

> 	(OH and if theres a faq, can someone tell me where?)

An unofficial FAQ is on agate.berkeley.edu in
/pub/386BSD/386bsd-0.1/unofficial/terry/FAQ.09Aug92/FAQ.09Aug92.

To save bandwidth, please read it first and then come back with any
unanswered questions.

You might also want to read some of the back postings.  Warren Toomey claimed 
in the past to be maintaining a fifo archive based on the available disk
space on minnie.cd.adfa.oz.au:bsdnews and Frank Terhaar-Yonkers claims to
have a culled archive on sunvis.rtpnc.epa.gov:~/pub/386bsd/culled.news.
This should get you up to speed right quick.

-- 
Gary Browning        | Exhilaration is that feeling you get just after a
		     | great idea hits you, and just before you realize
                     | what is wrong with it.
Newsgroups: comp.unix.bsd
From: mcpapen@cip.informatik.uni-erlangen.de (Marc Papen)
Subject: [386BSD] Syquest 5110 and Controllers
Organization: CSD., University of Erlangen
Date: Tue, 29 Sep 1992 12:25:15 GMT
Keywords: 386BSD SCSI Syquest

Hi 

I have a couple of questions about the Syquest 5110 drive.

	1) Is anybody using this drive with 386BSD?

	2) What (supported) controllers do work with it?
	(Does the SQ-01 work or any other cheap card)

	3) Does anybody have any experiences with this drive in general?

Thanks in advance for all responses and thanks to all who have helped to put 
together this Operating system.

Please respond to the net or send me email.

	Marc

---
Marc Papen
email:	mcpapen@cip.informatik.uni-erlangen.de
     or marc@lft.uni-erlangen.de


Newsgroups: comp.unix.bsd
From: peter@ferranti.com (peter da silva)
Subject: Re: 386BSD and IDE drives
Organization: Xenix Support, FICC
Date: Mon, 28 Sep 1992 21:20:26 GMT

In article <Bv32LD.K9t@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes:
> 	Something is very wrong here.  My experience is that IDE drives
> 	are great for UNIX and IDEAL for 386bsd.  Main reason is that, like
> 	SCSI, they hide bad sectors from the OS.

This is the one problem with SCSI, and presumably IDE. Why? What happens
when you have a marginal disk? When you're running MFM or ESDI, you start
getting more and more disk errors, and you have time to back up and reformat.
When you're running SCSI, you suddenly (without warning) get a LOT of errors
when the bad sector table fills up. By then it's too late to do anything
about it.

I've been burned by this.

I used to think this sort of bad track mapping was cool, but I've come to the
conclusion that the operating system should manage bad sectors. It's the part
of the whole system that knows (1) what the bad sectors mean, and (2) how to
tell the user something's wrong.

Of course, it needs to do a good job of this, with options to automatically
map bad blocks into a bad block list and tools to clean up afterwards. This
is a lot harder than assuming a perfect medium. But it's 

>       Never a need to run bad144 or worry about bad sectors.

Oh, you should worry. Trust me.

>       Second, for a 1 or 2 drive system, IDE
> 	is a non-negligable amount less cost than SCSI.

Not unless you really compromise on the quality of the drives, or unless
you've got some sort of special deal. Street prices vary by $20-$50 for
the same drive in SCSI and IDE versions.
-- 
Peter da Silva                                               `-_-'
Ferranti Intl. Ctls. Corp.                                    'U` 
Sugar Land, TX  77487-5012
+1 713 274 5180                                   Har du kramat din varg idag?
Newsgroups: comp.unix.bsd
From: g89s9112@hippo.ru.ac.za (Dirk Sturzebecher)
Subject: printer an LPT1  HOW ???
Organization: Rhodes University, Grahamstown, South Africa
Distribution: global
Date: Tue, 29 Sep 1992 12:40:46 GMT

Hi all,
can someone tell me how to get my printer working under 386bsd ?

If that is a problem (I thing it could be, the printer is not an
interrupt driven device, bad thing for a multi tasking system) can
anyone direct me where I can find documentation how to get low level
drivers into bsd ? A good description how the COM drivers work could
do the trick. After all the parallel port has a interrupt (unused
normally), so maybe a bit of wire and some reconfig ......

Cheers, Dirk

-- 
-----------------------------------------------------------------------
Dirk Sturzebecher				g89s9112@alpha.ru.ac.za
Rhodes University Grahamstown			South Africa
Newsgroups: comp.unix.bsd
From: pauls@css.itd.umich.edu (Paul Southworth)
Subject: 386bsd as NFS client
Organization: University of Michigan ITD Consulting and Support Services
Date: Wed, 30 Sep 1992 18:55:46 GMT

I'm getting very frustrated trying to get a 386bsd machine to mount an
nfs volume.  If you have successfully done it, please send me mail.


Paul Southworth                    |     ftp redspread.css.itd.umich.edu
Consulting and Support Services    |        Anonymous Political Archives
Information Technology Division    |                     100% 386BSD 0.1
University of Michigan, Ann Arbor  |  Coming soon: mirror of ftp.eff.org

  <Representing myself.  Everything I say is for educational use only.>
Newsgroups: comp.unix.bsd
From: adrian@ibmpcug.co.uk (Superuser)
Subject: Archive Listing for rachel.ibmpcug.co.uk
Organization: The IBM PC User Group, UK.
Date: Wed, 7 Oct 1992 00:24:16 GMT

The following files are archived at rachel.ibmpcug.co.uk in
~ftp/src/local

archie-1.3.2.tar.Z      	Archie Client
gopher1.03.tar.Z        	Gopher Client
irc2.7.2g.tar.Z         	IRC Server
ircII2.2pre7.myc6.tar.Z 	IRC II Client (Myc Patches)
webster.tar.Z			Webster Dictionary Client
elm2.3.tar.Z            	ELM Mailer 2.3pl11
metamail.tar.Z          	Meta Mailer (untested by me)
emacs-4-386bsd.tar.Z    	Emacs 18.58
gcpio-2.0.tar.Z         	Gnu CPIO
mush.tar.Z			Mush Mailer

In addition, two kernels (kernel.NFS and kernel.NONFS) are in ~ftp.
These files are fully patched kernels to Alpha-3 Patchkit.

Being worked on at the moment :-

	Gcc 1.42	(We think we have this working, including
			 the compiling of the kernel. It will be put
			 up in the next few days if we are sure of it.)

	Beta-Patchkit Kernels.

	Kernels with Julians SCSI system.

Contributions:

	If anyone wishes to contribute to the archive, I accept complete
	packages, ready to be compiled (generally, all that is required
	is a make and a make install).

Adrian Hall

-- 
--------------------------------------------------------------------------
Adrian Hall					Connect Systems Manager
adrian@ibmpcug.co.uk				The IBM PC User Group
Tel: +44 81 863 1191				Harrow, London, UK
From: prd@wmsims.UUCP (Philip R. Docken)
Newsgroups: comp.unix.bsd
Subject: Ethernet Western Digital Troubles
Keywords: ethernet western digital wd8013
Date: 2 Oct 92 18:44:48 GMT
Organization: Williams & Company Consulting, Inc.

I'm have trouble getting tiny 386bsd to find the ethernet card.
The card is set to: IRO 2 mem 0xd0000 Port 280 ram size 16k.

Tiny 386bsd fails to see the card...

I must be missing smething.

Any assistance would be much appreciated.


==============================================================================
|| Philip R. Docken                      Williams & Company Consulting Inc. ||
|| Email: prd@wms.uucp                            814 Pierce Street         ||
||        uunet!wms!prd                         Sioux City, Iowa, USA       ||
|| Voice: 1-712-252-4041                         FAX  : 1-712-252-5974      ||
==============================================================================
From: wmbfmk@rw9.urc.tue.nl (Marc van Kempen)
Newsgroups: comp.unix.bsd
Subject: Clock.exe doesn't seem to work
Date: 2 Oct 92 08:55:07 GMT
Reply-To: wmbfmk@urc.tue.nl

If I use clock.exe to determine my videoclocks, 
this is what I get:
D
  25.2   28.3   19.8  23.7  25.2  28.3  19.8  23.7

I have however another program for the videocard, DMODE.EXE, 
which gives the following results:

  50.35  56.672  65.306  72.240 80.276  90.172  63.114  75.498

My videocard is an ET4000, with 15-bit RAMDAC.
I know my card can run 1024x768x256 at 70Hz, I can put it into
that mode using DMODE. I find both listings of clocks a bit 
suspicious however.

(I have not yet been able to test this because of a harddisk crash)

Has anyone any ideas?

Thanks in advance,
A

Marc.
wmbfmk@urc.tue.nl

Newsgroups: comp.unix.bsd
From: peter@ferranti.com (peter da silva)
Subject: Re: 386BSD's non-standard C library
Organization: Xenix Support, FICC
Date: Mon, 28 Sep 1992 21:38:51 GMT

In article <1992Sep24.031603.21009@minyos.xx.rmit.oz.au> rcskb@minyos.xx.rmit.oz.au (Kendall Bennett) writes:
> Hmph. I assumed that the standard C library for 386BSD (the one that
> comes with 0.1 bindist/srcdist) would be standard,

It is. It's a standard K&R library.

> so my ANSI C
> conforming programs would work no problems.

Ah. That's your problem. You're using a newer standard.

> Well, it seems that the
> library is far from standard and is taking a number of shortcuts.

Not shortcuts, exactly. The library *predates* the standard. For example,
the ANSI standard changed the behaviour of tolower for most compilers.

Portable code should be written in the expectation that there are still
a lot of old compilers out there. The portable version of your code is:

	if(isupper(c))
		c = tolower(c);

> I fixed the above problem, but the program core dumps with a bus error,

I dare say.

Anyone with pretentions of writing portable code should be forced to port
their code to (say) Xenix-286.

That'll separate the men from the boys.

> so I have no idea what is going on (and I hate using dbx :-( ).

Oh yeh, you'd REALLY hate adb.

> What can be done about this? There are a number of solutions.

Fix your code. Run lint over it until it lints clean.
-- 
Peter da Silva                                               `-_-'
Ferranti Intl. Ctls. Corp.                                    'U` 
Sugar Land, TX  77487-5012
+1 713 274 5180                                   Har du kramat din varg idag?