Newsgroups: gnu.misc.discuss,comp.unix.sysv386,comp.unix.misc
Path: sparky!uunet!ferkel.ucsb.edu!ferkel!jim
From: j...@ferkel.ucsb.edu (Jim Lick)
Subject: BSD Networking Release 2 tape?
Message-ID: <jim.694482861@ferkel>
Organization: University of California, Santa Barbara
Date: Fri, 3 Jan 1992 23:54:21 GMT
Lines: 16
I have been hearing quite a lot of talk about this tape
which supposedly includes a lot more of the BSD system
than was previously available. Is this tape currently
available, or not yet released? Is the material freely
distributable? If so, is it available via ftp from
anywhere?
Thanks
Jim Lick
Work: University of California | Play: 6657 El Colegio #24
Santa Barbara | Isla Vista, CA 93117-4280
Dept. of Mechanical Engr. | (805) 968-0189 voice/msg
2311 Engr II Building | "Don't be naive,
(805) 893-4113 | Don't deny what you see"
j...@ferkel.ucsb.edu | -Erasure
Newsgroups: gnu.misc.discuss,comp.unix.sysv386,comp.unix.misc
Path: sparky!uunet!uunet!revell
From: rev...@uunet.uu.net (James R Revell Jr)
Subject: Re: BSD Networking Release 2 tape?
Message-ID: <1992Jan4.053228.16124@uunet.uu.net>
Reply-To: rev...@uunet.uu.net (James R Revell Jr)
Organization: UUNET Technologies Inc, Falls Church, VA
References: <jim.694482861@ferkel>
Date: Sat, 4 Jan 1992 05:32:28 GMT
In article <jim.694482861@ferkel> j...@ferkel.ucsb.edu (Jim Lick) writes:
} I have been hearing quite a lot of talk about this tape
[The BSD Networking Release II tape]
} Is the material freely distributable? If so, is it available via ftp
} from anywhere?
Yes. At long last it's available in ftp.uu.net:/packages/bsd-sources.
We had to hold up the ftp release due to export restrictions the US govt
placed on IP networking software due to the war in the gulf. All's well
now.
--
James Revell sr uunet postmaster <rev...@uunet.uu.net> /8^{~
Path: sparky!uunet!mcsun!news.funet.fi!polaris!polaris!mea
From: m...@polaris.utu.fi (Matti Aarnio)
Newsgroups: gnu.misc.discuss,comp.unix.sysv386,comp.unix.misc
Subject: Re: BSD Networking Release 2 tape?
Message-ID: <MEA.92Jan4182923@polaris.utu.fi>
Date: 4 Jan 92 17:29:23 GMT
References: <jim.694482861@ferkel> <1992Jan4.053228.16124@uunet.uu.net>
Sender: m...@polaris.utu.fi (Matti Aarnio)
Organization: University of Turku, Computing Centre
Lines: 36
In-Reply-To: revell@uunet.uu.net's message of 4 Jan 92 05:32:28 GMT
In article <1992Jan4.053228.16...@uunet.uu.net> rev...@uunet.uu.net (James R Revell Jr) writes:
> In article <jim.694482861@ferkel> j...@ferkel.ucsb.edu (Jim Lick) writes:
> } I have been hearing quite a lot of talk about this tape
>
> [The BSD Networking Release II tape]
>
> } Is the material freely distributable? If so, is it available via ftp
> } from anywhere?
>
> Yes. At long last it's available in ftp.uu.net:/packages/bsd-sources.
> We had to hold up the ftp release due to export restrictions the US govt
> placed on IP networking software due to the war in the gulf. All's well
> now.
And now also at the FTP.FUNET.FI:/pub/unix/4.3bsd-net2/ -tree.
(There are also the previous two sets, 4.3bsd-tahoe, and 4.3bsd-reno for
those wanting to see the historical progress :-)
FTP.FUNET.FI is recommended site for the scandinavian area, others are
propably (network vice) closer to FTP.UU.NET.
> James Revell sr uunet postmaster <rev...@uunet.uu.net> /8^{~
/Matti Aarnio <m...@utu.fi> <m...@nic.funet.fi> Postmaster
--
/Matti Aarnio <m...@utu.fi> <m...@nic.funet.fi>
Span/Hepnet: 21905::kontu::mea
FUNIC: Finnish Academic and Research Network Project
Network Information/Software Archival Service
OH1MQK - Radio Amateurs do it in Super High Frequency (24GHz)
--
/Matti Aarnio <m...@utu.fi> <m...@nic.funet.fi>
Span/Hepnet: 21905::kontu::mea
FUNIC: Finnish Academic and Research Network Project
Network Information/Software Archival Service
Path: sparky!uunet!elroy.jpl.nasa.gov!sdd.hp.com!wupost!darwin.sura.net!Sirius.dfn.de!fauern!ira.uka.de!unido!uni-koeln!rrz.Uni-Koeln.DE!clauberg
From: claub...@rrz.Uni-Koeln.DE (Axel Clauberg)
Newsgroups: dnet.archiv,de.admin.archiv
Subject: BSD Networking Software Release II Tape auf ftp.uni-koeln.de
Message-ID: <1992Jan7.112009.177702@rrz.uni-koeln.de>
Date: 7 Jan 92 11:20:09 GMT
Sender: a0...@rrz.Uni-Koeln.DE (Axel Clauberg)
Followup-To: de.admin.archiv
Organization: Regional Computing Center, University of Cologne
Lines: 36
Nachdem es nun wohl doch exportiert werden darf:
frisch von ftp.uu.net das BSD Networking Release II Tape auf ftp.Uni-Koeln.DE
[134.95.80.1] in /packages/bsd-sources
Das gesamte Paket ist fast 48 MB gross...
cd ~ftp/packages/bsd-sources
du -s *
0 Makefile
8 README.Z
956 bin
88 contrib
844 etc
3428 games
232 include
796 kerberosIV
7508 lib
436 libexec
840 sbin
4980 share
7104 sys
17744 usr.bin
2996 usr.sbin
Die Files sind -wie auf ftp.uu.net- ausgepackt und komprimiert abgelegt, es reicht also
ein get directory.tar (nicht directory.tar.Z !!!).
Gruesse, Axel
--
Axel Clauberg, Regional Computing Center, University of Cologne
Robert-Koch Str. 10
D- 5000 Koeln 41, Germany
Phone: +49 (221) 478-5589
Internet: claub...@rrz.Uni-Koeln.DE
Path: sparky!uunet!wupost!csus.edu!umn.edu!math.fu-berlin.de!fub!public!incom!smurf.sub.org!news
From: urli...@smurf.sub.org (Matthias Urlichs)
Newsgroups: de.admin.archiv
Subject: Re: BSD Networking Software Release II Tape auf ftp.uni-koeln.de
Date: 7 Jan 1992 18:36:25 +0100
Organization: University of Karlsruhe, FRG
Lines: 23
Message-ID: <kmjp8pINN51o@smurf.smurf.sub.org>
References: <1992Jan7.112009.177702@rrz.uni-koeln.de>
NNTP-Posting-Host: smurf.smurf.sub.org
In de.admin.archiv, article <1992Jan7.112009.177...@rrz.uni-koeln.de>,
claub...@rrz.Uni-Koeln.DE (Axel Clauberg) writes:
<
< Das gesamte Paket ist fast 48 MB gross...
<
< Die Files sind -wie auf ftp.uu.net- ausgepackt und komprimiert abgelegt, es reicht also
< ein get directory.tar (nicht directory.tar.Z !!!).
<
Schade -- es waere (genug Platz vorausgesetzt) sinnvoll, erst zu teeren und
dann zu federn, aeh zu komprimieren, da das gegenueber der umgekehrten
Reihenfolge doch einiges an Uebertragungskapazitaet spart.
Diejenigen, die auf ihrem eigenen System nicht genug Platz haben zum
Auspacken, koennen dann immer noch mit
get directory.tar.Z |uncompress|tar xf -
den FTP-Datenstrom direkt dem tar verfuettern. Fuer Einzeldateien ist diese
Methode natuerlich unguenstiger. ;-)
--
Matthias Urlichs -- urli...@smurf.sub.org -- urli...@smurf.ira.uka.de /(o\
Humboldtstrasse 7 -- 7500 Karlsruhe 1 -- Germany -- +49-721-9612521 \o)/
Path: sparky!uunet!sun-barr!cs.utexas.edu!qt.cs.utexas.edu!zaphod.mps.ohio-state.edu!think.com!mintaka.lcs.mit.edu!ai-lab!zurich.ai.mit.edu!ara
From: a...@zurich.ai.mit.edu (Allan Adler)
Newsgroups: comp.unix.msdos
Subject: Public domain unix for PC's ?
Message-ID: <ARA.92Jan7231737@schwyz.ai.mit.edu>
Date: 8 Jan 92 04:17:37 GMT
Sender: n...@ai.mit.edu
Distribution: comp
Organization: M.I.T. Artificial Intelligence Lab.
Lines: 6
Is there one ? If so, where can I get it ?
Allan Adler
a...@altdorf.ai.mit.edu
Newsgroups: comp.unix.sysv386
Path: sparky!uunet!paladin.american.edu!darwin.sura.net!jvnc.net!yale.edu!qt.cs.utexas.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!bronze!mosque.huji.ac.il!ury
From: u...@mosque.huji.ac.il (ury segal)
Subject: 386's UNIX kernel source
Message-ID: <1992Jan8.071839.14478@bronze.ucs.indiana.edu>
Sender: n...@bronze.ucs.indiana.edu (USENET News System)
Nntp-Posting-Host: mosque.huji.ac.il
Organization: Hebrew University of Jerusalem, Israel
Date: Wed, 8 Jan 92 07:18:39 GMT
Lines: 9
Does someone have (free) 386's UNIX kernel source ?
--
*******************************************************************************
* Ury Segal * Phone: Home: (02) 971187
* Distributed Computing Project * Lab: (02) 585762
* Dept. of Computer Science * E-mail:
* Hebrew University, Jerusalem, Israel * u...@cs.huji.ac.il
*******************************************************************************
Path: sparky!uunet!mcsun!uknet!icdoc!lmjm
From: l...@doc.ic.ac.uk (Lee M J McLoughlin)
Newsgroups: comp.unix.sysv386
Subject: Re: 386's UNIX kernel source
Message-ID: <LMJM.92Jan9173533@raquel.doc.ic.ac.uk>
Date: 9 Jan 92 17:35:33 GMT
References: <1992Jan8.071839.14478@bronze.ucs.indiana.edu>
Organization: Dept. of Computing, Imperial College, London. U.K.
Lines: 15
Nntp-Posting-Host: raquel.doc.ic.ac.uk
In-Reply-To: ury@mosque.huji.ac.il's message of 8 Jan 92 07:18:39 GMT
I can't say for sure but in the second Berkeley networking release
there appears to be enough source for unix and enough 386 specific
code to actually get a system up and running. Have a look in
src.doc.ic.ac.uk:unix/bsd-sources
ftp.uu.net:unix/bsd-sources
--
Lee McLoughlin. Phone: 071 589 5111 X 5085
Dept of Computing, Imperial College, Fax: 071 581 8024
180 Queens Gate, London, SW7 2BZ, UK. Email: L.McLough...@doc.ic.ac.uk
--
--
Lee McLoughlin. Phone: 071 589 5111 X 5085
Dept of Computing, Imperial College, Fax: 071 581 8024
180 Queens Gate, London, SW7 2BZ, UK. Email: L.McLough...@doc.ic.ac.uk
Newsgroups: comp.unix.msdos
Path: sparky!uunet!math.fu-berlin.de!unidui!du9ds3!veit
From: v...@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: Public domain unix for PC's ?
References: <ARA.92Jan7231737@schwyz.ai.mit.edu> <LMJM.92Jan9172952@raquel.doc.ic.ac.uk>
Date: 10 Jan 92 08:47:31 GMT
Distribution: comp
Reply-To: v...@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung
Sender: @unidui.uni-duisburg.de
Message-ID: <veit.695033251@du9ds3>
Lines: 34
In <LMJM.92Jan9172...@raquel.doc.ic.ac.uk> l...@doc.ic.ac.uk (Lee M J McLoughlin) writes:
>I can't say for sure but in the second Berkeley networking release
>there appears to be enough source for unix and enough 386 specific
>code to actually get a system up and running. Have a look in
> src.doc.ic.ac.uk:unix/bsd-sources
> ftp.uu.net:unix/bsd-sources
>--
>--
>Lee McLoughlin. Phone: 071 589 5111 X 5085
>Dept of Computing, Imperial College, Fax: 071 581 8024
>180 Queens Gate, London, SW7 2BZ, UK. Email: L.McLough...@doc.ic.ac.uk
Some utilities like 'adb', 'vi', 'at', 'cron', 'grep' (!) 'pr', 'tail'
and others are missing in the BSD Networking Release 2. This is not a
problem at all, since one can often choose among different PD versions
for that (e.g. borrowing from MINIX, or GNU-FSF).
One vital missing file of the BSD NWR-2 is /sbin/init. Except this
and some device drivers one might like (SCSI support) it seems to be quite
complete to build a UNIX kernel (provided you find an existing compatible
BSD-unix to prepare the first bootable root file system on disk. The
reading of the articles 'Porting UNIX to the 386' in DrDobbs' Journal
(01/91-12/91) is strongly recommended.
BTW, has anyone a suited *available* /sbin/init source to complete the
distribution?
Holger
--
| | / Holger Veit | INTERNET: v...@du9ds3.uni-duisburg.de
|__| / University of Duisburg | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
| | / Dept. of Electr. Eng. | X.400: /S=veit /O=du9ds3 /P=uni-duisburg
| |/ Inst. f. Dataprocessing | /A=dbp /C=de
Path: sparky!uunet!mcsun!uknet!edcastle!aiai!richard
From: rich...@aiai.ed.ac.uk (Richard Tobin)
Newsgroups: comp.unix.sysv386
Subject: Re: 386's UNIX kernel source
Message-ID: <5936@skye.ed.ac.uk>
Date: 10 Jan 92 15:19:45 GMT
References: <1992Jan8.071839.14478@bronze.ucs.indiana.edu> <LMJM.92Jan9173533@raquel.doc.ic.ac.uk>
Organization: AIAI, University of Edinburgh, Scotland
Lines: 31
In article <LMJM.92Jan9173...@raquel.doc.ic.ac.uk> l...@doc.ic.ac.uk (Lee M J McLoughlin) writes:
>I can't say for sure but in the second Berkeley networking release
>there appears to be enough source for unix and enough 386 specific
>code to actually get a system up and running.
The following from kern_exec.c suggests otherwise:
execve(p, uap, retval)
register struct proc *p;
register struct args {
char *fname;
char **argp;
char **envp;
} *uap;
int *retval;
{
/*
* Body deleted.
*/
return (ENOSYS);
}
There are other similar functions. Also, the standalone stuff needed
for bootstrapping is incomplete.
-- Richard
--
Richard Tobin,
AI Applications Institute, R.To...@ed.ac.uk
Edinburgh University.
Newsgroups: comp.unix.sysv386
Path: sparky!uunet!uunet!revell
From: rev...@uunet.uu.net (James R Revell Jr)
Subject: Re: 386's UNIX kernel source
Message-ID: <1992Jan11.022438.25193@uunet.uu.net>
Reply-To: rev...@uunet.uu.net (James R Revell Jr)
Organization: UUNET Technologies Inc, Falls Church, VA
References: <1992Jan8.071839.14478@bronze.ucs.indiana.edu> <LMJM.92Jan9173533@raquel.doc.ic.ac.uk>
Date: Sat, 11 Jan 1992 02:24:38 GMT
In article <LMJM.92Jan9173...@raquel.doc.ic.ac.uk> l...@doc.ic.ac.uk (Lee M J McLoughlin) writes:
} I can't say for sure but in the second Berkeley networking release
} there appears to be enough source for unix and enough 386 specific
} code to actually get a system up and running. Have a look in
...
} ftp.uu.net:unix/bsd-sources
Use ftp.uu.net:/packages/bsd-sources
[Note, since I revealed the second networking tape was available at
that location one week ago we've logged over 100,000 transfers of
files in bsd-sources. Many of those were transfers of
bsd-sources.tar{,.Z} too. This is approximately 60% of all files ftp
over that time. Thanks for helping me with the burn in test of the
new ftp server :-) ]
--
James Revell sr uunet postmaster <rev...@uunet.uu.net> /8^{~
Path: sparky!uunet!wupost!darwin.sura.net!Sirius.dfn.de!fauern!unido!mcsun!fuug!sics.se!seunet!kullmar!compuram!pgd
From: p...@compuram.bbt.se
Newsgroups: comp.unix.sysv386,comp.unix.internals
Subject: Re: 386's UNIX kernel source
Message-ID: <1992Jan11.082427.11910@compuram.bbt.se>
Date: 11 Jan 92 08:24:27 GMT
References: <5936@skye.ed.ac.uk>
Lines: 50
Richard Tobin (rich...@aiai.ed.ac.uk) writes:
: In article <LMJM.92Jan9173...@raquel.doc.ic.ac.uk> l...@doc.ic.ac.uk (Lee M J McLoughlin) writes:
: >I can't say for sure but in the second Berkeley networking release
: >there appears to be enough source for unix and enough 386 specific
: >code to actually get a system up and running.
:
: The following from kern_exec.c suggests otherwise:
:
......
: /*
: * Body deleted.
: */
: return (ENOSYS);
: }
:
: There are other similar functions. Also, the standalone stuff needed
: for bootstrapping is incomplete.
Routines which are thus missing from the kernel are:
acct(), sysacct(), execve() with friends, physio(),
minphys(), rminit(), rmalloc(), rmfree(), ptrace(),
procxmt(), profil(), cinit(), getc(), q_to_p(),
ndqb(), ndflush(), putc(), b_to_q(), nextc(),
unputc(), bufinit(), bread(), breada(), bwrite(),
bdwrite(), bawrite(), brelse(), incore(), getblk(),
geteblk(), allocbuf(), getnewbuf(), biowait(), biodone()
I have looked them up in the unix v7 sources, and they amount to
approximately 800 lines of code.
Some I cannot find there. They are:
minphys(), rminit(), rmalloc(), rmfree(), procxmt(), nextc(),
unputc(), bufinit(), allocbuf(), getnewbuf()
Do they really containt AT&T code, or were they just kicked out "by
mistake"?
In any case, unless there are more surprises, it should not be too
hard to rewrite these routines. Many are quite straightforward.
Most routines contain 10-20 lines of code. One only 2.
Some are ridiculusly simple. In fact, I wonder how they can be
rewritten to not be identical with the AT&T ones.
Now, I wonder, are these routines really identical to the Unix v7
routines, or are they modified by the BSD people?
That is, would it be possible to plug in the V7 routines, modify them,
and get it working, without having seen the actual bsd routines?
--
Per Lindqvist
Internet: p...@compuram.bbt.se Fidonet: Per Lindqvist @ 2:201/332
Path: sparky!uunet!sun-barr!cronkite.Central.Sun.COM!newstop!eastapps!vergil!gsteckel
From: gstec...@vergil.East.Sun.COM (Geoff Steckel - Sun BOS Hardware CONTRACTOR)
Newsgroups: comp.unix.sysv386,comp.unix.internals
Subject: Re: 386's UNIX kernel source
Summary: re-invent ATT's wheel
Message-ID: <10349@eastapps.East.Sun.COM>
Date: 11 Jan 92 19:49:35 GMT
References: <5936@skye.ed.ac.uk> <1992Jan11.082427.11910@compuram.bbt.se>
Sender: n...@East.Sun.COM
Reply-To: gstec...@east.sun.com (Geoff Steckel - Sun BOS Hardware CONTRACTOR)
Followup-To: comp.unix.sysv386
Organization: Omnivore Technology, Newton, Mass. (617)332-9252
Lines: 45
In article <1992Jan11.082427.11...@compuram.bbt.se> p...@compuram.bbt.se writes:
>Richard Tobin (rich...@aiai.ed.ac.uk) writes:
>:
>: The following from kern_exec.c suggests otherwise:
>:
>......
>: /*
>: * Body deleted.
>: */
>: return (ENOSYS);
>: }
>Routines which are thus missing from the kernel are:
>[deleted]
>
>I have looked them up in the unix v7 sources, and they amount to
>approximately 800 lines of code.
[...]
>In any case, unless there are more surprises, it should not be too
>hard to rewrite these routines. Many are quite straightforward.
>Most routines contain 10-20 lines of code. One only 2.
>Some are ridiculusly simple. In fact, I wonder how they can be
>rewritten to not be identical with the AT&T ones.
Well, it depends... things like getc() and putc() would be hard
to make much different!
>Now, I wonder, are these routines really identical to the Unix v7
>routines, or are they modified by the BSD people?
They've been changed for things like VM and hashed buffer chains.
But not lots.
I'd do it myself (aside from minor things like a multi-year backup
of other projects & a need to keep clients happy...) but it certainly
wouldn't be `clean-room' - I've seen far too much of the ATT sources.
Ok, net-folk: one routine a person? it shouldn't take >too< long
to assemble a set of working versions. According to a posting from
UUNET, over 100,000 copies of the BSD files went out in one week!
SOMEbody must have a little time!
The interfaces are `well-defined' (:-) (:-) (:-)
regards,
geoff steckel (g...@wjh12.harvard.EDU)
(...!husc6!wjh12!omnivore!gws)
Disclaimer: I am not affiliated with Sun Microsystems, despite the From: line.
This posting is entirely the author's responsibility.
Newsgroups: comp.unix.sysv386,comp.unix.internals
Path: sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!bronze!mosque.huji.ac.il!ury
From: u...@mosque.huji.ac.il (ury segal)
Subject: Re: 386's UNIX kernel source
Message-ID: <1992Jan12.110903.26878@bronze.ucs.indiana.edu>
Sender: n...@bronze.ucs.indiana.edu (USENET News System)
Nntp-Posting-Host: mosque.huji.ac.il
Organization: Hebrew University of Jerusalem, Israel
References: <5936@skye.ed.ac.uk> <1992Jan11.082427.11910@compuram.bbt.se>
Date: Sun, 12 Jan 92 11:09:03 GMT
Lines: 62
In article <1992Jan11.082427.11...@compuram.bbt.se>, p...@compuram.bbt.se writes:
|> Richard Tobin (rich...@aiai.ed.ac.uk) writes:
|> : In article <LMJM.92Jan9173...@raquel.doc.ic.ac.uk> l...@doc.ic.ac.uk (Lee M J McLoughlin) writes:
|> : >I can't say for sure but in the second Berkeley networking release
|> : >there appears to be enough source for unix and enough 386 specific
|> : >code to actually get a system up and running.
|> :
|> : The following from kern_exec.c suggests otherwise:
|> :
|> ......
|> : /*
|> : * Body deleted.
|> : */
|> : return (ENOSYS);
|> : }
|> :
|> : There are other similar functions. Also, the standalone stuff needed
|> : for bootstrapping is incomplete.
|>
|> Routines which are thus missing from the kernel are:
|> acct(), sysacct(), execve() with friends, physio(),
|> minphys(), rminit(), rmalloc(), rmfree(), ptrace(),
|> procxmt(), profil(), cinit(), getc(), q_to_p(),
|> ndqb(), ndflush(), putc(), b_to_q(), nextc(),
|> unputc(), bufinit(), bread(), breada(), bwrite(),
|> bdwrite(), bawrite(), brelse(), incore(), getblk(),
|> geteblk(), allocbuf(), getnewbuf(), biowait(), biodone()
|>
|> I have looked them up in the unix v7 sources, and they amount to
|> approximately 800 lines of code.
|> Some I cannot find there. They are:
|> minphys(), rminit(), rmalloc(), rmfree(), procxmt(), nextc(),
|> unputc(), bufinit(), allocbuf(), getnewbuf()
|> Do they really containt AT&T code, or were they just kicked out "by
|> mistake"?
|>
|> In any case, unless there are more surprises, it should not be too
|> hard to rewrite these routines. Many are quite straightforward.
|> Most routines contain 10-20 lines of code. One only 2.
|> Some are ridiculusly simple. In fact, I wonder how they can be
|> rewritten to not be identical with the AT&T ones.
|>
|> Now, I wonder, are these routines really identical to the Unix v7
|> routines, or are they modified by the BSD people?
|> That is, would it be possible to plug in the V7 routines, modify them,
|> and get it working, without having seen the actual bsd routines?
|>
Can someone work with me and add the code from reno or such, if legal ?
|> --
|> Per Lindqvist
|>
|> Internet: p...@compuram.bbt.se Fidonet: Per Lindqvist @ 2:201/332
--
*******************************************************************************
* Ury Segal * Phone: Home: (02) 971187
* Distributed Computing Project * Lab: (02) 585762
* Dept. of Computer Science * E-mail:
* Hebrew University, Jerusalem, Israel * u...@cs.huji.ac.il
*******************************************************************************
Newsgroups: comp.unix.sysv386,comp.unix.internals
Path: sparky!uunet!caen!sol.ctr.columbia.edu!bronze!mosque.huji.ac.il!ury
From: u...@mosque.huji.ac.il (ury segal)
Subject: Re: 386's UNIX kernel source
Message-ID: <1992Jan12.111831.27174@bronze.ucs.indiana.edu>
Sender: n...@bronze.ucs.indiana.edu (USENET News System)
Nntp-Posting-Host: mosque.huji.ac.il
Organization: Hebrew University of Jerusalem, Israel
References: <5936@skye.ed.ac.uk> <1992Jan11.082427.11910@compuram.bbt.se> <1992Jan12.010507@eklektix.com>
Date: Sun, 12 Jan 92 11:18:31 GMT
Lines: 34
In article <1992Jan12.010...@eklektix.com>, r...@raven.eklektix.com (Dick Dunn) writes:
|> p...@compuram.bbt.se writes about the missing code in the BSD net 2 release:
|> >Routines which are thus missing from the kernel are:
|> [several dozen]
|> >I have looked them up in the unix v7 sources, and they amount to
|> >approximately 800 lines of code.
|> >Some I cannot find there. They are:
|> [ten more]
|>
|> [comparison with V7 background]
|> >Now, I wonder, are these routines really identical to the Unix v7
|> >routines, or are they modified by the BSD people?
|> >That is, would it be possible to plug in the V7 routines, modify them,
|> >and get it working, without having seen the actual bsd routines?
|>
|> It would probably be possible to start with the V7 routines--IF you could
|> use them. But remember that V7 source is also under AT&T license; you
|> can't distribute it. (Nor can you get a V7 source license any more.)
|>
We can use reno code.
|> How would you go about using V7 code?
|> --
|> Dick Dunn r...@raven.eklektix.com -or- raven!rcd Boulder, Colorado
|> ...Simpler is better.
--
*******************************************************************************
* Ury Segal * Phone: Home: (02) 971187
* Distributed Computing Project * Lab: (02) 585762
* Dept. of Computer Science * E-mail:
* Hebrew University, Jerusalem, Israel * u...@cs.huji.ac.il
*******************************************************************************
Path: sparky!uunet!auspex-gw!guy
From: g...@Auspex.COM (Guy Harris)
Newsgroups: comp.unix.sysv386,comp.unix.internals
Subject: Re: 386's UNIX kernel source
Message-ID: <11649@auspex-gw.auspex.com>
Date: 12 Jan 92 21:43:17 GMT
References: <5936@skye.ed.ac.uk> <1992Jan11.082427.11910@compuram.bbt.se> <1992Jan12.110903.26878@bronze.ucs.indiana.edu>
Sender: n...@auspex-gw.auspex.com
Followup-To: comp.unix.sysv386
Organization: Auspex Systems, Santa Clara
Lines: 68
Nntp-Posting-Host: auspex.auspex.com
>|> Routines which are thus missing from the kernel are:
>|> acct(), sysacct(), execve() with friends, physio(),
>|> minphys(), rminit(), rmalloc(), rmfree(), ptrace(),
>|> procxmt(), profil(), cinit(), getc(), q_to_p(),
>|> ndqb(), ndflush(), putc(), b_to_q(), nextc(),
>|> unputc(), bufinit(), bread(), breada(), bwrite(),
>|> bdwrite(), bawrite(), brelse(), incore(), getblk(),
>|> geteblk(), allocbuf(), getnewbuf(), biowait(), biodone()
>Can someone work with me and add the code from reno or such, if legal ?
They probably could; too bad the Reno code in question *ISN'T* legal in
all cases. The Reno "vfs_bio.c" has what appears to be an "AT&T-free"
copyright notice, which would take care of:
bread(), breada(), bwrite(), bdwrite(), bawrite(), brelse(),
incore(), getblk(), geteblk(), getnewbuf(), biowait(),
biodone()
and the Reno "kern_exec.c" also has that notice, which takes care of:
execve() and company
and the reno "{hp300,tahoe}/ufs_machdep.c" also have that notice, which
gives Tahoe and HP 9000/3xx versions of:
allocbuf()
(although the VAX version doesn't have that notice) *IF*, in fact, they
really consider them AT&T-free.
However, the Reno "vm_swp.c" *doesn't* have that copyright notice, and
it contains:
physio(), minphys()
and the Reno "kern_acct.c" doesn't, either, and it contains:
acct(), sysacct()
and the Reno "subr_rmap.c" doesn't, and it contains:
rminit(), rmalloc(), rmfree()
and the Reno "sys_process.c" doesn't, and it contains:
ptrace(), procxmt()
and the Reno "kern_clock.c" doesn't, and it contains:
profil()
and the Reno "tty_subr.c" doesn't, and it contains:
getc(), q_to_b(), ndqb(), ndflush(), putc(), b_to_q(), nextc(),
unputc()
and the Reno "init_main.c" doesn't, and it contains:
cinit()
Also, the Reno "vaxstand/format.c" doesn't, and it contains:
bufinit()
unless the kernel in question has a "bufinit()" different from the one
in that particular *stand-alone* program, in which case Reno doesn't
appear to have such a routine in its kernel.
Path: sparky!uunet!mcsun!uknet!edcastle!aiai!richard
From: rich...@aiai.ed.ac.uk (Richard Tobin)
Newsgroups: comp.unix.sysv386,comp.unix.internals
Subject: Re: 386's UNIX kernel source
Message-ID: <5958@skye.ed.ac.uk>
Date: 13 Jan 92 14:18:10 GMT
References: <5936@skye.ed.ac.uk> <1992Jan11.082427.11910@compuram.bbt.se>
Organization: AIAI, University of Edinburgh, Scotland
Lines: 13
In article <1992Jan11.082427.11...@compuram.bbt.se> p...@compuram.bbt.se writes:
>In any case, unless there are more surprises, it should not be too
>hard to rewrite these routines.
Could someone from Berkeley tell us whether they are still working on
a complete detoxed version? Or has this aim been in some way
superseded by the BSDI release?
-- Richard
--
Richard Tobin,
AI Applications Institute, R.To...@ed.ac.uk
Edinburgh University.
Newsgroups: comp.unix.sysv386
Path: sparky!uunet!uunet!rick
From: r...@uunet.uu.net (Rick Adams)
Subject: Re: 386's UNIX kernel source
Message-ID: <1992Jan13.185201.15947@uunet.uu.net>
Summary: not att free
Sender: use...@uunet.uu.net (UseNet News)
Nntp-Posting-Host: rodan.uu.net
Organization: UUNET Communications Services
References: <5936@skye.ed.ac.uk> <1992Jan11.082427.11910@compuram.bbt.se> <11649@auspex-gw.auspex.com>
Date: Mon, 13 Jan 1992 18:52:01 GMT
In article <11...@auspex-gw.auspex.com>, g...@Auspex.COM (Guy Harris) writes:
> >Can someone work with me and add the code from reno or such, if legal ?
>
> They probably could; too bad the Reno code in question *ISN'T* legal in
> all cases. The Reno "vfs_bio.c" has what appears to be an "AT&T-free"
> copyright notice, which would take care of:
>
> bread(), breada(), bwrite(), bdwrite(), bawrite(), brelse(),
> incore(), getblk(), geteblk(), getnewbuf(), biowait(),
> biodone()
>
> and the Reno "kern_exec.c" also has that notice, which takes care of:
>
> execve() and company
>
vfs_bio.c and kern_exec.c were INCORRECTLY MARKED on the reno release.
They do contain ATT code.
Thats also why they aren't on the NET2 release. They've been remarked.
--rick
Newsgroups: comp.unix.sysv386,comp.unix.internals
Path: sparky!uunet!sequent!muncher.sequent.com!jjb
From: j...@sequent.com
Subject: Re: 386's UNIX kernel source
References: <5936@skye.ed.ac.uk> <1992Jan11.082427.11910@compuram.bbt.se>
Message-ID: <1992Jan12.030302.16335@sequent.com>
Sender: n...@sequent.com (News on Muncher)
Organization: Sequent Computer Systems, Inc.
Date: Sun, 12 Jan 92 03:03:02 GMT
Lines: 34
In article <1992Jan11.082427.11...@compuram.bbt.se> p...@compuram.bbt.se writes:
>
>Routines which are thus missing from the kernel are...
>[Deleted list]
>Do they really containt AT&T code, or were they just kicked out "by
>mistake"...would it be possible to plug in the V7 routines, modify them,
>and get it working, without having seen the actual bsd routines?
If you have access to the V7 code, you have an AT&T source license, right?
In that case you can get a full Berkeley distribution and do whatever you
want with it; most of the routines you mention are not machine dependent.
(There may be licensing "levels" or issues I don't understand here - no
doubt some net.person will straighten me out if so.)
If you don't have a source license, then what you are proposing to do is,
well, Bad - fleshing out the mostly-complete unencumbered BSD distribution
through unlicensed access to the missing pieces.
If you want to do it yourself, without access to the AT&T sources, that
is interesting. The companies that clone PC BIOS code go to great
lengths to prevent their work from being "tainted". Certainly, nobody
who ever read or worked on the published IBM BIOS code would be allowed
to work on the clone, for obvious legal reasons.
By analogy, it seems to me that anybody who's done Unix kernel work over
the past 10 or 15 years is not a good candidate to recreate these
functions "from scratch". That rules out many of the best candidate
people to solve the problem.
Perhaps somebody from BSDI would be willing to comment on their strategy
for dealing with a potential legal assault from AT&T? What did they do
to ensure that their work was legally viewed as "original"?
--
Jeff Berkowitz, Sequent Computer Systems j...@sequent.com uunet!sequent!jjb
Newsgroups: comp.unix.sysv386,comp.unix.internals
Path: sparky!uunet!uunet!kolstad
From: kols...@uunet.uu.net (Rob Kolstad)
Subject: Re: 386's UNIX kernel source
Message-ID: <1992Jan14.204706.5662@uunet.uu.net>
Followup-To: comp.unix.sysv386
Summary: BSDI endeavors to do everything quite legally.
Sender: use...@uunet.uu.net (UseNet News)
Nntp-Posting-Host: rlavax.uu.net
Organization: UUNET Communications Services
References: <5936@skye.ed.ac.uk> <1992Jan11.082427.11910@compuram.bbt.se> <1992Jan12.030302.16335@sequent.com>
Date: Tue, 14 Jan 1992 20:47:06 GMT
Last week, Jeff Berkowitz asked:
From: j...@sequent.com
Subject: Re: 386's UNIX kernel source
Message-ID: <1992Jan12.030302.16...@sequent.com>
Organization: Sequent Computer Systems, Inc.
Date: Sun, 12 Jan 92 03:03:02 GMT
Perhaps somebody from BSDI would be willing to comment on their
strategy for dealing with a potential legal assault from AT&T? What
did they do to ensure that their work was legally viewed as
"original"?
--
Jeff Berkowitz, Sequent Computer Systems j...@sequent.com uunet!sequent!jjb
BSDI has worked extensively with a computer law specialist to ensure that
all of our business dealings are strictly legal -- both within the letter
and the spirit of the law. It is inappropriate to discuss details of
these transactions in this public forum.
BSDI Program Manager,
Rob
--
====================================================================
/\ Rob Kolstad Berkeley Software Design, Inc.
/\/ \ kols...@bsdi.com 7759 Delmonico Drive
Path: sparky!uunet!spool.mu.edu!umn.edu!buddha.ncc.umn.edu!rodeen
From: rod...@buddha.ncc.umn.edu (Rick Odeen)
Newsgroups: comp.unix.bsd
Subject: Where to ftp the Networking-2 tape from?
Message-ID: <1992Feb27.165706.23317@news2.cis.umn.edu>
Date: 27 Feb 92 16:57:06 GMT
Article-I.D.: news2.1992Feb27.165706.23317
Sender: n...@news2.cis.umn.edu (Usenet News Administration)
Organization: Nutrition Coordinating Center, University of Minnesota
Lines: 14
Nntp-Posting-Host: buddha.ncc.umn.edu
Can someone point me to an ftp location for the bsd networking-2 tape
where I can grab the distribution on one chunk. I've seen the sources
on uunet and wuarchive but don't know how to easily ftp the entire
source tree.
Thanks!
-Rick Odeen
--
"MINIX costs $169, but the license allows | Rick Odeen
making two backup copies, so the effective | rod...@buddha.ncc.umn.edu
price can be under $60." | rutgers!umn-cs!buddha!rodeen
- a...@cs.vu.nl (Andy Tanenbaum) |
Newsgroups: comp.unix.bsd
Path: sparky!uunet!decwrl!pa.dec.com!vixie
From: vi...@pa.dec.com (Paul A Vixie)
Subject: Re: Where to ftp the Networking-2 tape from?
In-Reply-To: rodeen@buddha.ncc.umn.edu's message of 27 Feb 92 16:57:06 GMT
Message-ID: <VIXIE.92Feb27164318@cognition.pa.dec.com>
Sender: n...@PA.dec.com (News)
Organization: DEC Network Software Lab
References: <1992Feb27.165706.23317@news2.cis.umn.edu>
Date: 27 Feb 92 16:43:18
Lines: 26
>> I've seen the sources on uunet and wuarchive but don't know how to easily
>> ftp the entire source tree.
I think wuarchive's ftp server will send you a .tar.Z file if you try to
get "/whatever/mumble.tar.Z" and it has a "/whatever/mumble" directory.
Against what would pass for my better judgement if I had enough to compare,
I've made a /pub/bsd-sources-2.tar.Z file on gatekeeper.dec.com:~ftp and
you are all welcome to grab it from us if you want to do that. We normally
just have the unpacked files, which are more popular with most folks since
they like to pick and choose.
It's worth mentioning that if you are a large outfit, you should buy the
tape from CSRG. Every dollar they can sell helps them stay alive and keep
on producing this stuff. If you can afford their $850, then it is axiomatic
that the $850 is more important to them than it is to you. If you can't
afford it, then it's very likely that you will be doing the BSD community
a big favor down the line as you contribute enhancements and fixes to UCB --
so grab the bits via FTP either way, but please consider ordering the tape
if you've got a non-shallow pocket around somewhere.
Cheers,
--
Paul Vixie, DEC Network Systems Lab
Palo Alto, California, USA
<vi...@decwrl.dec.com> decwrl!vixie
<p...@vixie.sf.ca.us> vixie!paul
Newsgroups: comp.unix.bsd
Path: sparky!uunet!uunet!revell
From: rev...@uunet.uu.net (James R Revell Jr)
Subject: Re: Where to ftp the Networking-2 tape from?
Message-ID: <1992Feb28.012341.11647@uunet.uu.net>
Sender: use...@uunet.uu.net (UseNet News)
Nntp-Posting-Host: rodan.uu.net
Reply-To: rev...@uunet.uu.net (James R Revell Jr)
Organization: UUNET Technologies Inc, Falls Church, VA
References: <1992Feb27.165706.23317@news2.cis.umn.edu> <VIXIE.92Feb27164318@cognition.pa.dec.com>
Date: Fri, 28 Feb 1992 01:23:41 GMT
In article <VIXIE.92Feb27164...@cognition.pa.dec.com> vi...@pa.dec.com (Paul A Vixie) writes:
} >> I've seen the sources on uunet and wuarchive but don't know how to easily
} >> ftp the entire source tree.
}
} I think wuarchive's ftp server will send you a .tar.Z file if you try to
} get "/whatever/mumble.tar.Z" and it has a "/whatever/mumble" directory.
This can be done on ftp.uu.net also. The files are compressed already
though and the total size of bsd-sources even compressed is 39 MB. I
would encourage taring of the 13 sub dirs rather than the whole thing
at once. It's also a bit useless to try and recompress the tar's.
--
James Revell sr uunet postmaster <rev...@uunet.uu.net> /8^{~
Newsgroups: comp.unix.bsd
Path: sparky!uunet!news!mday
From: m...@icon.com (Matt Day)
Subject: vi in Net-2
Organization: Icon International, Inc., Orem, UT, USA
Date: Thu, 12 Mar 1992 19:04:12 GMT
Message-ID: <1992Mar12.190412.1646@icon.com>
Sender: n...@icon.com (Mr. News)
Nntp-Posting-Host: physh.icon.com
I can't find "vi" in Net-2. Where is it?
Newsgroups: comp.unix.bsd
Path: sparky!uunet!wupost!usc!rpi!news-server.csri.toronto.edu!utzoo!henry
From: he...@zoo.toronto.edu (Henry Spencer)
Subject: Re: vi in Net-2
Message-ID: <1992Mar12.213643.7405@zoo.toronto.edu>
Date: Thu, 12 Mar 1992 21:36:43 GMT
References: <1992Mar12.190412.1646@icon.com>
Organization: U of Toronto Zoology
Lines: 9
In article <1992Mar12.190412.1...@icon.com> m...@icon.com (Matt Day) writes:
>I can't find "vi" in Net-2. Where is it?
It's not. It is (distantly) derived from ed, which is licensed software,
and hence cannot be made freely available. (I assume this is being worked
on.)
--
GCC 2.0 is to C as SVR4 is to Unix. | Henry Spencer @ U of Toronto Zoology
-Dick Dunn | he...@zoo.toronto.edu utzoo!henry
Newsgroups: uunet.forum
Path: sparky!uunet!spooky!witr
From: w...@rwwa.COM (Robert Withrow)
Subject: Mirroring of various OS projects?
Message-ID: <1992Mar16.164239.18972@rwwa.COM>
Organization: R.W. Withrow Associates
Distribution: us
Date: Mon, 16 Mar 1992 16:42:39 GMT
Is UUNET mirroring the 386BSD code being discussed (ad nauseum) in the
comp.os.bsd group? If not, could you please?
Also, is UUNET mirroring the MACH code? A ls-lR I took late last week
shows you have version MK64 whereas MK71 or MK72 is current... If
not, could you please?
(By mirror I guess I mean semi-automagical updating of your stuff to
track their stuff...)
Finally, I see your BSD4.3 NET 2 stuff is exploded into the component
pieces. Do you have a (perhaps split) tar.Z form?
--
---
Robert Withrow, R.W. Withrow Associates, Swampscott MA 01907 USA
Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: w...@rwwa.COM
Newsgroups: uunet.forum
Path: sparky!uunet!uunet!revell
From: rev...@uunet.uu.net (James R Revell Jr)
Subject: Re: Mirroring of various OS projects?
Message-ID: <1992Mar16.223658.1839@uunet.uu.net>
Sender: use...@uunet.uu.net (UseNet News)
Nntp-Posting-Host: ghidra.uu.net
Reply-To: rev...@uunet.uu.net (James R Revell Jr)
Organization: UUNET Technologies Inc, Falls Church, VA
References: <1992Mar16.164239.18972@rwwa.COM>
Date: Mon, 16 Mar 1992 22:36:58 GMT
In article <1992Mar16.164239.18...@rwwa.COM> w...@rwwa.COM (Robert Withrow) writes:
} Is UUNET mirroring the 386BSD code being discussed (ad nauseum) in the
} comp.os.bsd group? If not, could you please?
Yes and no. I specifically did not mirror the 0.0old version of the
386BSD code which was announced late last week. If you saw the
announcement then you noticed the fact that a new version would be
available soon (in fact, it came out today) and they recommended that
people wait for it.
I have already configured mirroring of the 386BSD code within
uunet!~/pub/OS/386BSD (the 0.0new subdir actually)
I'm mirroring gatekeeper.dec.com since there is no hope whatsoever of
connecting to agate.berkeley.edu. gatekeeper doesn't yet have the
new version, but they should tonight sometime. I'll make sure we have
it by tommorow afternoon
} Also, is UUNET mirroring the MACH code? A ls-lR I took late last week
} shows you have version MK64 whereas MK71 or MK72 is current...
No, mk64 is still the most current available from the CMU mach archive.
There are some newer files than what we had though, including the
default.tar.Z and default.mk64.tar.Z (now available as split files).
I WAS mirroring the mach stuff, but had to stop right around the beginning
of the year because of problems obtaining listings from the CMU mach archive.
Bad listings were being returned and we were deleting files, which should
have remained, as a result.
Testing now, it appears that we can once again mirror the mach stuff. I
will leave that mirror active and watch for problems with it.
} Finally, I see your BSD4.3 NET 2 stuff is exploded into the component
} pieces. Do you have a (perhaps split) tar.Z form?
No. The bsd-sources directory is 39 MB already (all compressed). We can
*either* keep split tar.Z files *or* keep the components. Unless someone
would like to give us some more disk :-)
--
James Revell sr uunet postmaster <rev...@uunet.uu.net> /8^{~
Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!jvnc.net!netnews.upenn.edu!uofs!falcon.cs.uofs.edu!bill
From: b...@falcon.cs.uofs.edu (Bill Gunshannon)
Newsgroups: comp.unix.bsd
Subject: 386BSD
Message-ID: <10672@platypus.uofs.uofs.edu>
Date: 23 Mar 92 18:01:02 GMT
Sender: n...@uofs.uofs.edu
Reply-To: b...@platypus.uofs.edu
Organization: University of Scranton, Scranton, PA
Lines: 20
Nntp-Posting-Host: falcon.cs.uofs.edu
I have looked at what is on UUNET. Now I have a couple more questions.
Is there anywhere I can FTP a tar of the whole distribution?? The many
subdirectories make it somewhat of a pain trying to make sure you get it
all.
Is there anywhere I can FTP a tar of the NET/2 distribution??
Because my targets are not INTEL based machines at all, I could use all
the examples I can lay my hands on. Especially the VAX.
Thanks in advance for any help.
bill
--
Bill Gunshannon | If this statement wasn't here,
b...@platypus.uofs.edu | This space would be left intentionally blank
b...@tuatara.uofs.edu | #include <std.disclaimer.h>
Path: sparky!uunet!zaphod.mps.ohio-state.edu!mips!atha!aupair.cs.athabascau.ca!rwa
From: r...@cs.athabascau.ca (Ross Alexander)
Newsgroups: comp.unix.bsd
Subject: need uncorrupted /usr/src/sys.386bsd/sys/signalvar.h
Keywords: 386BSD /usr/src/sys.386bsd/sys/signalvar.h
Message-ID: <2191@aupair.cs.athabascau.ca>
Date: 28 Mar 92 00:35:39 GMT
Distribution: na
Organization: Athabasca University
Lines: 22
I dragged the 386BSD sources from gatekeeper.dec.com:/pub/micro/386bsd.03.17.92
over our incredibly saturated and tiny link to the world yesterday. Just about
everything seems to be dandy EXCEPT that my copy of
/usr/src/sys.386bsd/sys/signalvar.h is corrupted; there's a big chunk of \0's
sitting about 10 lines before EOF, and of course cc isn't having any of that
:-(. The problem seems to be in the data; extracting the file on my DS2100
gets the same clobbered result.
Where can I pick up single files via FTP (rather than multi-floppy-image
compressed tarsets)? I know about agate but I'm reluctant to go in there
from consideration of the relative triviality of my need.
BTW, great gushes of gratitude to William & Lynne and all the fine folks at
CSRG. This whole thing is the most unbelievably marvellous gift, that I simply
can't get over it.
regards,
Ross
--
Ross Alexander r...@cs.athabascau.ca (403) 675 6311 ve6...@ve6mgs.ampr.org
"DOS emulators are largely deficient in this area and don't properly
support many of the popular viruses." Richard Foulk, rich...@pegasus.com
Newsgroups: comp.unix.bsd
Path: sparky!uunet!zaphod.mps.ohio-state.edu!menudo.uh.edu!sugar!karl
From: k...@NeoSoft.com (Karl Lehenbauer)
Subject: Re: need uncorrupted /usr/src/sys.386bsd/sys/signalvar.h
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Sat, 04 Apr 1992 00:15:02 GMT
Message-ID: <1992Apr04.001502.2415@NeoSoft.com>
Keywords: 386BSD /usr/src/sys.386bsd/sys/signalvar.h
References: <2191@aupair.cs.athabascau.ca>
In article <2...@aupair.cs.athabascau.ca> r...@cs.athabascau.ca (Ross Alexander) writes:
>/usr/src/sys.386bsd/sys/signalvar.h is corrupted...
>Where can I pick up single files via FTP (rather than multi-floppy-image
>compressed tarsets)? I know about agate but I'm reluctant to go in there
>from consideration of the relative triviality of my need.
The Net-2 distribution is all unpacked and file-by-file accessible on
ftp.uu.net in packages/bsd-sources.
The specific file you're looking for is packages/bsd-sources/sys/sys/signalvar.h
--
-- Email i...@NeoSoft.com for info on getting Internet access.
"Trust me. I know what I'm doing." -- Sledge Hammer
Path: sparky!uunet!think.com!mips!swrinde!gatech!gatech!sbmsg1!bsts00!rlb
From: r...@bsts00.uucp (Ronald (Ron) L. Bolin 3945 snk=)
Newsgroups: comp.unix.bsd
Subject: Missing Includes in 386BSD
Message-ID: <195@bsts00.UUCP>
Date: 15 Apr 92 12:25:07 GMT
Sender: r...@bsts00.UUCP
Reply-To: gatech!sbmsg1!bsts00!rlb
Distribution: usa
Organization: BellSouth Services, Switching Technical Support (BSS-STS), Altanta, GA 30375
Lines: 12
Ther are several missing include files in the 386BSD floppy distb. Where
can I find them? One I am especially interested in is
/usr/src/sys.386bsd/i386/isa/wtreg.h
Can someone tell me what ftp site has the complete include file set for 386BSD
please.
Thank's
Ron
Newsgroups: misc.test
Path: sparky!uunet!think.com!spdcc!dirtydog.ima.isc.com!ispd-newsserver!jmoore
From: The Software Warehouse, (x3HELP), wareho...@ssd.kodak.com
Subject: Software Only changes on UUNET archive for week ending Mar_2_92
Message-ID: <1992Apr15.132736.6943@ssd.kodak.com>
X-Comment-01: This posting is generated automatically. Please
X-Comment-02: report any errors or problems to Jim Moore. He can
X-Comment-03: be reached at jmo...@pixel.kodak.com.
Originator: jmoore@fricka
Sender: n...@ssd.kodak.com
Organization: The Software Warehouse, Software Core Platform Center, Eastman Kodak Co.
Distribution: ek
Date: Wed, 15 Apr 92 13:27:36 GMT
Keyword: Weekly Software Only changes to UUNET archive Mar_2_92
Lines: 193
What follows is a list of the weekly updates to the UUNET archive
administerd by the Usenix organization. Their weekly changes list
has been reduced through a special perl script which separates out
filesystems which do not generally contain things of interest, or
filesystems whose security is non-existant (like tmp) or questionable.
Also an attempt has been made to separate the listing of files by
interest groups.
All that is available is the filenames. You have to know what you are
looking for. (Actually, these lists are most useful for checking
when new versions of something that you already have come out).
Anything on the list can be obtained as a request through The Software
Warehouse, if you don't have internet access.
If you do have internet access, feel free to pull it in yourself.
Please notify Jim Moore (jmo...@ssd.kodak.com) if you are seriously
considering putting up something obtained from UUNET (actually ftp.uu.net).
Jim coordinates freely redistributable / public domain software for
The Software Warehouse, and may be able to put you in touch with
someone else working on the same software. Jim may also be able
to tell you if there is something with similar functionality already
in The Software Warehouse. Lastly, if it is something that is good,
we will work with you to get it submitted to The Warehouse (It is
a lot easier than it used to be.)
As a matter of information. When you pull something in, please create
a "EK_SOURCES" file in the directory that records the name of the
package pulled in, who pulled it in, and when it was pulled in. If
you can, also include the date and size of the file on the archive.
The Software Warehouse always includes that information in the "WH_Notes"
files that they generate.
Also if configuration is required, and you must edit files to build
the application, please use the csh alias eddist (included immediately
following). Eddist takes a single filename argument, and moves the
one received in the distribution to the filename-dist, and then make
a copy of the distribution back to the original file name, for editing"
alias eddist 'set filename="\!*"; mv $filename ${filename}-dist ; cp ${filename}-dist $filename'
Thank you for your patronage.
The staff at The Software Warehouse (EIPC)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-rw-r--r-- 1 archive 289 Feb 26 05:56 ./packages/X/contrib/vex/x92.slides.tar.Z-split/README
-rw-r--r-- 1 archive 295 Feb 26 06:03 ./packages/X/contrib/winterp/winterp-1.13.tar.Z-split/README
-rw-r--r-- 1 archive 545 Feb 26 16:56 ./packages/X/contrib/hp_xlfd_enhancements/README.Z
-rw-r--r-- 1 archive 1542 Feb 24 17:14 ./packages/X/contrib/hp_xlfd_enhancements/announcement.Z
-rw-r--r-- 1 archive 41711 Feb 27 18:35 ./packages/X/contrib/hp_xlfd_enhancements/hp_xlfd_demo.tar.Z
-rw-r--r-- 1 archive 7462 Feb 24 17:04 ./packages/X/contrib/hp_xlfd_enhancements/hp_xlfd_enhancements.Z
-rw-r--r-- 1 archive 46183 Feb 26 16:55 ./packages/X/contrib/hp_xlfd_enhancements/hp_xlfd_patches.public.tar.Z
-rw-r--r-- 1 archive 43922 Feb 24 17:02 ./packages/X/contrib/hp_xlfd_enhancements/hp_xlfd_patches.tar.Z
-rw-r--r-- 1 archive 212 Feb 26 06:00 ./packages/X/contrib/periodic/periodic.Z-split/README
-rw-r--r-- 1 archive 976712 Feb 27 14:22 ./packages/X/contrib/ImageMagick.tar.Z
-rw-r--r-- 1 archive 247 Feb 24 16:17 ./packages/X/contrib/dec-pexlib.tar.Z-split/README
-rw-r--r-- 1 archive 408 Feb 26 06:51 ./packages/X/contrib/serpent/serpent_1.2_tar.Z-split/README
-rw-r--r-- 1 archive 245 Feb 24 16:35 ./packages/X/contrib/Wcl.1.06.tar.Z-split/README
-rw-r--r-- 1 archive 246 Feb 24 16:34 ./packages/X/contrib/xtank1.3a.tar.Z-split/README
-rw-r--r-- 1 archive 84009 Feb 24 08:45 ./packages/X/contrib/FAQ.Z
-rw-r--r-- 1 archive 240 Feb 24 17:27 ./packages/X/contrib/UIT.tar.Z-split/README
-rw-r--r-- 1 archive 365 Feb 24 17:31 ./packages/X/contrib/ada.xlib.6-0-0.tar.Z-split/README
-rw-r--r-- 1 archive 299008 Feb 25 11:40 ./packages/X/contrib/ModemX-1.02.tar.Z
-rw-r--r-- 1 archive 319 Feb 24 17:48 ./packages/X/contrib/THINGS.tar.Z-split/README
-rw-r--r-- 1 archive 260 Feb 26 01:11 ./packages/X/contrib/clue.tar.Z-split/README
-rw-r--r-- 1 archive 335 Feb 26 01:44 ./packages/X/contrib/mlx.tar.Z-split/README
-rw-r--r-- 1 archive 270 Feb 24 17:41 ./packages/X/contrib/xgrasp.glfiles.tar.Z-split/README
-rw-r--r-- 1 archive 274568 Feb 27 12:00 ./packages/X/contrib/young.c++.tar.Z
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part01
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part02
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part03
-rw-r--r-- 1 archive 277 Feb 26 02:20 ./packages/X/contrib/Xw.tar.Z-split/README
-rw-r--r-- 1 archive 99171 Feb 28 18:11 ./packages/X/contrib/xkeycaps.tar.Z
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part04
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part05
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part06
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part07
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part08
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part09
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part10
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part11
-rw-r--r-- 1 archive 495 Feb 27 23:55 ./packages/X/contrib/ModemX-1.02.tar.Z-split/README
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part12
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part13
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part14
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part15
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part16
-rw-r--r-- 1 archive 256000 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part17
-rw-r--r-- 1 archive 206643 Feb 26 09:13 ./packages/X/contrib/ModemX-1.02.tar.Z-split/part18
-rw-r--r-- 1 archive 96103 Feb 27 12:30 ./packages/X/contrib/contool-3.2a.tar.Z
-rw-r--r-- 1 archive 77045 Feb 24 08:11 ./packages/X/contrib/CTW-1.1.tar.Z
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part01
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part02
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part03
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part04
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part05
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part06
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part07
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part08
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part09
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part10
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part11
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part12
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part13
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part14
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part15
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part16
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part17
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part18
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part19
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part20
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part21
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part22
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part23
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part24
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part25
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part26
-rw-r--r-- 1 archive 736821 Feb 27 11:32 ./packages/X/contrib/pextk.tar.Z
-rw-r--r-- 1 archive 775 Feb 24 15:03 ./packages/X/contrib/wframe.tar.Z-split/README
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part27
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part28
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part29
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part30
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part31
-rw-r--r-- 1 archive 256000 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part32
-rw-r--r-- 1 archive 32768 Feb 24 02:23 ./packages/X/contrib/wframe.tar.Z-split/part33
-rw-r--r-- 1 archive 0 Feb 25 02:51 ./packages/.notar
dr-xr-xr-x 2 rick 512 Feb 28 11:15 ./packages/bsd-sources/bin/cp
-r--r--r-- 1 rick 89 Feb 28 11:14 ./packages/bsd-sources/bin/cp/Makefile
-r--r--r-- 1 rick 3206 Feb 28 11:14 ./packages/bsd-sources/bin/cp/cp.1.Z
-r--r--r-- 1 rick 7675 Feb 28 11:14 ./packages/bsd-sources/bin/cp/cp.c.Z
-r--r--r-- 1 rick 1569 Feb 28 11:14 ./packages/bsd-sources/bin/cp/extern.h.Z
-r--r--r-- 1 rick 2467 Feb 28 11:14 ./packages/bsd-sources/bin/cp/path.c.Z
-rw-r--r-- 1 archive 214689 Feb 25 11:26 ./packages/gnu/find-3.5.tar.Z
-rw-r--r-- 1 archive 27680 Feb 25 11:31 ./packages/gnu/find.diff-3.4-3.5.Z
-rw-r--r-- 1 archive 1107403 Feb 29 14:00 ./packages/gnu/gcc-vms-1.40.tar.Z
-rw-r--r-- 1 archive 850706 Feb 26 14:51 ./packages/gnu/glibc-1.00.tar.Z
-rw-r--r-- 1 archive 13833 Feb 28 01:15 ./packages/InterViews/contrib/iedit3.0.patch1.Z
-rw-r--r-- 1 archive 219 Feb 28 23:11 ./mail/mh/Index.Z
-rw-r--r-- 1 archive 45 Feb 28 23:11 ./mail/mh/contrib/Index.Z
-rw-r--r-- 1 archive 496 Feb 28 23:11 ./mail/mh/doc/Index.Z
-rw-r--r-- 1 archive 188 Feb 28 23:11 ./mail/mh/tar/Index.Z
-rw-r--r-- 1 archive 162 Feb 28 23:10 ./mail/mh/updates/Index.Z
-rw-r--r-- 1 archive 519354 Feb 24 20:03 ./graphics/vogle/vogle.tar.Z
-rw-r--r-- 1 archive 859 Feb 27 12:29 ./mail/listserv/WARNINGS.Z
-rw-r--r-- 1 archive 1675 Feb 29 14:15 ./mail/listserv/current_version.Z
-rw-r--r-- 1 archive 183056 Feb 29 17:35 ./mail/listserv/listserv5.41.sh.Z
-rw-r--r-- 1 archive 60143 Feb 27 16:52 ./mail/metamail/BodyFormats.ez.Z
-rw-r--r-- 1 archive 128293 Feb 27 16:51 ./mail/metamail/BodyFormats.ps.Z
-rw-r--r-- 1 archive 65397 Feb 27 16:51 ./mail/metamail/BodyFormats.txt.Z
-rw-r--r-- 1 archive 40706 Feb 27 16:51 ./mail/metamail/FEB.DIFFS.Z
-rw-r--r-- 1 archive 0 Feb 25 02:51 ./networking/.notar
-rw-r--r-- 1 revell 144739 Feb 24 23:53 ./published/nutshell/phigs/examples.tar.Z
-rw-r--r-- 1 revell 158885 Feb 27 16:40 ./published/unix-today/benchmarks/3292.bench.tar.Z
-rw-r--r-- 1 revell 2674 Feb 26 00:17 ./published/unix-world/ans2unix/1992/feb92.Z
-rw-r--r-- 1 revell 2651 Feb 26 00:16 ./published/unix-world/ans2unix/1992/jan92.Z
-rw-r--r-- 1 revell 513 Feb 26 00:17 ./published/unix-world/ans2unix/1992/mar92.Z
-rw-r--r-- 1 78 78577 Feb 26 13:29 ./usenet/comp.sources.misc/index
-rw-r--r-- 1 78 7784 Feb 26 13:34 ./usenet/comp.sources.misc/volume28/index
-rw-r--r-- 1 78 16631 Feb 26 13:23 ./usenet/comp.sources.misc/volume28/jgraph/patch07.5.Z
-rw-r--r-- 1 78 878 Feb 26 13:22 ./usenet/comp.sources.misc/volume28/mksheet.err.Z
-rw-r--r-- 1 78 14267 Feb 24 00:16 ./usenet/comp.sources.misc/volume28/mvalloc/part01.Z
-rw-r--r-- 1 78 10904 Feb 26 13:23 ./usenet/comp.sources.misc/volume28/rec/part01.Z
-rw-r--r-- 1 78 3455 Feb 26 13:22 ./usenet/comp.sources.misc/volume28/uureroute/part01.Z
-rw-r--r-- 1 78 16605 Feb 26 13:23 ./usenet/comp.sources.misc/volume28/gnufusers/part01.Z
-rw-r--r-- 1 78 29508 Feb 26 13:23 ./usenet/comp.sources.misc/volume28/perlref/part01.Z
-rw-r--r-- 1 78 25226 Feb 26 13:23 ./usenet/comp.sources.misc/volume28/perlref/part02.Z
-rw-r--r-- 1 78 23722 Feb 26 13:23 ./usenet/comp.sources.misc/volume28/perlref/part03.Z
-rw-rw-r-- 1 news 22079 Feb 24 13:34 ./usenet/comp.sources.x/new/FebMon,.0.Z
-rw-rw-r-- 1 32 91030 Feb 24 13:34 ./usenet/comp.sources.x/new/LOGFILE
-rwSr--r-- 1 sef 82126 Feb 28 19:12 ./usenet/comp.std.unix/archive
-rw-r--r-- 1 archive 18476 Mar 1 10:49 ./usenet/comp.sources.wanted/Anonymous_FTP_List_-_Sites.Z
-rw-r--r-- 1 archive 20499 Mar 1 10:49 ./usenet/comp.sources.wanted/Anonymous_FTP_List_-_Sites.part1.Z
-rw-r--r-- 1 archive 2671 Mar 1 10:49 ./usenet/comp.sources.wanted/Anonymous_FTP_List_-_Sites.part2.Z
-rw-r--r-- 1 archive 5818 Feb 27 14:28 ./inet/resource-guide/index-resource-guide.Z
-rw-r--r-- 1 archive 273 Feb 26 09:09 ./inet/rfc/fyi-by-author.Z
-rw-r--r-- 1 archive 625 Feb 26 09:09 ./inet/rfc/fyi-by-title.Z
-rw-r--r-- 1 archive 2704 Feb 26 09:06 ./inet/rfc/fyi-index.Z
-rw-r--r-- 1 archive 9528 Feb 28 15:47 ./inet/rfc/rfc-by-author.Z
-rw-r--r-- 1 archive 25838 Feb 28 15:47 ./inet/rfc/rfc-by-title.Z
-rw-r--r-- 1 archive 56214 Feb 28 15:47 ./inet/rfc/rfc-index.Z
-rw-r--r-- 1 archive 9576 Feb 26 12:05 ./inet/rfc/rfc1303.Z
-rw-r--r-- 1 archive 16910 Feb 28 15:47 ./inet/rfc/rfc1304.Z
-rw-r--r-- 1 archive 74777 Feb 24 19:13 ./inet/rfc/rfc1291.ps.Z
-rw-r--r-- 1 archive 12069 Feb 25 09:24 ./inet/rfc/rfc1302.Z
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - James H. Moore, The Software Warehouse, Eastman Kodak Co. 726-0322 -
- - jmo...@ssd.kodak.com, PROFS: DDTC12(JMOORE) VMS: DDTC12::JMOORE - -
- - May your Easter be filled with communion and fellowship with Jesus - -
Newsgroups: comp.unix.bsd
Path: sparky!uunet!elroy.jpl.nasa.gov!ames!agate!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!zaphod.mps.ohio-state.edu!menudo.uh.edu!sugar!karl
From: k...@NeoSoft.com (Karl Lehenbauer)
Subject: Re: Missing Includes in 386BSD
Organization: NeoSoft Communications Services -- (713) 684-5900
Distribution: usa
Date: Fri, 17 Apr 1992 02:22:57 GMT
Message-ID: <1992Apr17.022257.5150@NeoSoft.com>
References: <195@bsts00.UUCP>
Lines: 14
In article <1...@bsts00.UUCP> gatech!sbmsg1!bsts00!rlb writes:
>Ther are several missing include files in the 386BSD floppy distb. Where
>can I find them? One I am especially interested in is
>/usr/src/sys.386bsd/i386/isa/wtreg.h
>
>Can someone tell me what ftp site has the complete include file set for 386BSD
>please.
The Net-2 release is available, unpacked, from ftp.uu.net.
wtreg.h, for example, can be found there in /packages/bsd-sources/sys/i386/isa
--
-- Email i...@NeoSoft.com for info on getting Internet access.
"Trust me. I know what I'm doing." -- Sledge Hammer
Path: sparky!uunet!gatech!ncar!noao!arizona!jtillema
From: jtill...@cs.arizona.edu (John E. Tilleam)
Newsgroups: comp.unix.bsd
Subject: Is there A non 386BSD group?
Keywords: 4.3BSD
Message-ID: <17695@optima.cs.arizona.edu>
Date: 10 Jun 92 17:59:04 GMT
Sender: n...@cs.arizona.edu
Lines: 15
Is there a newsgroup that deals with BSD 4.x instead of 386BSD?
I thought this group was for bsd in general, but can't remember the
last time I saw a non 386 message. Maybe its time to either rename
this group or spawn a new 386bsd group (this may already have been
discussed, as I haven't read here for quite a while).
Anyway, on the chance someone knows...
1) An email address for questions on BSD 4.3
2) Where can one get missing include files for BSD 4.3?
(our dist tape seems to have been really messed up)
John
Path: sparky!uunet!darwin.sura.net!mips!atha!canada!lyndon
From: lyn...@ampr.ab.ca (Lyndon Nerenberg)
Newsgroups: comp.unix.bsd
Subject: Re: Is there A non 386BSD group?
Keywords: 4.3BSD
Message-ID: <68@ampr.ab.ca>
Date: 10 Jun 92 20:13:21 GMT
References: <17695@optima.cs.arizona.edu>
Organization: Alberta Packet Radio Network
Lines: 17
jtill...@cs.arizona.edu (John E. Tilleam) writes:
> I thought this group was for bsd in general, but can't remember the
> last time I saw a non 386 message.
I can't either. Keep posting and maybe that will change :-)
> 1) An email address for questions on BSD 4.3
Post them here. Lots of 4.3 literate people read this group.
> 2) Where can one get missing include files for BSD 4.3?
If it's part of the unencumbered software, look on ftp.uu.net in
packages/bsd-sources. That gets you the Networking 2 release which
is close enough to 4.3 for most purposes. gatekeeper.dec.com also
has BSD sources.
Path: sparky!uunet!uunet!not-for-mail
From: rev...@ghidra.UU.NET (James R Revell Jr)
Newsgroups: uunet.status
Subject: Archive down for system maintenance
Followup-To: uunet.forum
Date: 2 Jul 1992 22:35:24 -0400
Organization: UUNET Technologies Inc, Falls Church, VA
Lines: 15
Approved: rev...@uunet.uu.net
Message-ID: <130edcINNno@ghidra.UU.NET>
Reply-To: arch...@uunet.uu.net (James R Revell Jr)
NNTP-Posting-Host: ghidra.uu.net
A large section of UUNET's archive will be unavailable on Monday July 6
while we replace a bad disk. From approximately 3 PM until 10 PM on
that day everything within the top level "packages" directory (AKA:
uunet!~/packages) will be offline.
This includes 700 MB of the most popular software such as the BSD Net/2,
GNU, X11, TeX, and 386BSD sources, as well as our InterViews, NCSA_Telnet,
NeWS, athena, faces, isode, linux, mach, and neuroprose archives. Links
from other areas of our archive related to these subjecys will also be
affected.
Any attempts to transfer files from this portion of our archive during
that period will fail immediately.
--
James Revell Network Services Mgr <rev...@uunet.uu.net> /8^{~
Path: sparky!uunet!darwin.sura.net!wupost!sdd.hp.com!caen!umeecs!umn.edu!noc.msc.net!uc.msc.edu!shamash!!ldh
From: l...@svl.cdc.com (Lawrence D. Hare)
Newsgroups: comp.unix.programmer
Subject: Public Domain FTP Source based on BSD Sockets
Message-ID: <45821@shamash.cdc.com>
Date: 29 Jul 92 00:38:12 GMT
Sender: use...@shamash.cdc.com
Organization: Control Data Systems
Lines: 6
X-UserAgent: Nuntius v1.1.1d1
Does anyone know whether there exists public domain source code for FTP
based on the BSD Socket Interface? Likewise for Telnet?
--
Lawrence D. Hare Control Data - Silicon Valley Operations
Consultant Voice: (408) 496 4339 - C/N [234] 4339
l...@svl.cdc.com Mail: SVLa60 FAX: (408) 496-4106
Newsgroups: comp.unix.programmer
Path: sparky!uunet!elroy.jpl.nasa.gov!ufo!dnoble
From: dno...@jpl-devvax.jpl.nasa.gov (David Noble)
Subject: Re: Public Domain FTP Source based on BSD Sockets
Message-ID: <1992Jul29.171544.17859@jpl-devvax.jpl.nasa.gov>
Organization: Jet Propulsion Laboratory (NASA)
References: <45821@shamash.cdc.com>
Date: Wed, 29 Jul 1992 17:15:44 GMT
Lines: 23
In article <45...@shamash.cdc.com> l...@svl.cdc.com (Lawrence D. Hare) writes:
>Does anyone know whether there exists public domain source code for FTP
>based on the BSD Socket Interface? Likewise for Telnet?
There is a ton of stuff like this at ftp.uu.net [137.39.1.9] under the
/packages/bsd-sources directory. The two subdirectories you want are:
ftp.uu.net:/packages/bsd-sources/usr.bin/ftp
ftp.uu.net:/packages/bsd-sources/usr.bin/telnet
You might also want to look at the RFCs that document the FTP and Telnet
protocols. They are located in the directroy
ftp.uu.net:/inet/rfc
I think RFC #854 is the one that defines the simplest layer of Telnet, but
I don't know off the top of my head which RFC deals with FTP. I guess that's
why there's an index in the rfc directory :-) Happy hunting...
--
David Noble - RPI Computer & Systems Eng, class of '92 and 1/2
dno...@ufo.jpl.nasa.gov - JPL Section 367 System Integration & Testing
dno...@rdrc.rpi.edu - Virtual Environment Group, RDRC/RPI
Newsgroups: comp.bugs.4bsd
Path: sparky!uunet!uunet.ca!geac!alias!news
From: m...@alias.com (Mark Andrews)
Subject: Code Newer than Net/2
Message-ID: <1992Aug13.165751.10727@alias.com>
Sender: n...@alias.com (News Owner)
Organization: Alias Research Inc., Toronto ON Canada
Distribution: na
Date: Thu, 13 Aug 1992 16:57:51 GMT
Lines: 10
I just noticed that someone reported a typo from the Net/2 tset source code.
Alot of these typos have already been reported to CSRG, been fixed and the
code made available. I remember a new version of tset being made available
at ftp.uu.net in packages/bsd-sources/usr.bin/tset. There are a number of
utilities like this; the original code from the Net/2 tape has been replaced
by code found at uunet.
Hope this helps,
Mark