HDTenEightyP/NetNews huggingface dataset:
From: ken@sugra.uucp (Kenneth Ng)
Newsgroups: comp.unix.bsd
Subject: Re: Colorado Memory Systems tape drive
Keywords: CMJ, Jumbo, DJ-20
Date: 6 Sep 92 13:56:46 GMT
Organization: Private Computer, Totowa NJ

In article <1992Sep4.043955.19904@engr.uark.edu:, hbj@engr.uark.edu (Bernard Johnson,,,444-8266) writes:
: hasty@netcom.com (Amancio Hasty Jr) writes:
: >Also, you may add that they will not release any technical information
: >on their interface!
:QIC-40/80 is a standard and is documented.  You can call Quarter Inch Standards
: to obtain *free* documentation.  Probably what you are looking for is QIC-117
: which describes the command interface.

Got the number or an address of some kind I can give to information?  Calling
411 and saying "I'm looking for the number for Quarter Inch Standards, somewhere
in the United States, although it might be elsewhere."

-- 
Kenneth Ng
Please reply to ken@eies2.njit.edu for now.
Apple and AT&T lawsuits: Just say NO!
From: stripes@pix.com (Josh Osborne)
Newsgroups: comp.unix.bsd
Subject: Re: Shared Libs for X11?, was Re: 386bsd -- The New Newsgroup
Keywords: shared libraries X X11
Date: 11 Sep 92 21:46:18 GMT
Organization: Pix Technologies -- The company with no adult supervision

In article <7dnL02y821gh01@JUTS.ccc.amdahl.com> gab10@griffincd.amdahl.com (Gary A Browning) writes:
[...]
[...SVR3 uses fixed addresses, SVR4/SunOS uses PIC...]
>I tend to dislike the SysVr3 method since I got the impression that the source
>code had to be written differently (though I am not sure why).  I also noted
>that the GCC-2.2.2 compiler I just got compiled can produce PIC code which
>would be one of the major hurdles for the SysVr4 method.
>
>Any knowledgable person want to talk a little more about the pros and cons of
>these two (or any other) approach?

PIC code runs slower on some CPU's (ones that don't do PC indexed load/stores
as fast as dirrect load/stores, in fact I bet *some* code can't be PIC'ed
as fast as abs'ed on any CPU, but I won't be much).

Shared libs linked to an absolute address (a) are hard to update (you can't
change the entry points), and (b) all shared libs must be maped to diffrent
places, or they won't work together (i.e. libc can't overlap libX11, and if
libgdb overlaps libXt, then you can't link with both libXt and libgdb...).

I'm not sure why you would need to write absolute address'ed shared libs 
diffrently from PIC'ed ones, but I know both have some problems with
staticly allocated local variables (but this is implmention dependent).

I susspect that absolute addressed shared libs are easyer to implment.  Nither
should need support from the kernel, but it may be easyer/faster to do it
that way.  (I am assuming that we have a working mmap...).

>Anyone kept up with the Linux discussions of shared library implementations?
>Can you summarize?

Sorry, I don't know a thing about them.
-- 
           stripes@pix.com              "Security for Unix is like
      Josh_Osborne@Real_World,The          Multitasking for MS-DOS"
      "The dyslexic porgramer"                  - Kevin Lockwood
We all agree on the necessity of compromise.  We just can't agree on
when it's necessary to compromise.       - Larry Wall
From: allard@isi.edu (Dennis Allard)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd -- The New Newsgroup
Date: 10 Sep 92 23:21:27 GMT
Reply-To: allard@isi.edu (Dennis Allard)
Distribution: world
Organization: USC Information Sciences Institute

bdale@col.hp.com (Bdale Garbee) writes:
> wjolitz@soda.berkeley.edu (William F. Jolitz) writes:
> > 	comp.os.386bsd		(general questions and trivia)
> > 	comp.os.386bsd.kernel	(discussion on kernel content/structure)
> >     ...

> I'd be more interested in seeing a single comp.os.386bsd ...

Ditto.

> Good threaded user interfaces make keeping discussions together easy, ...

Indeed.

And (why not bring it up here), the future will see network server
based newsreaders where a newsreader will just import article headers
and only import an entire article when it is read.  There is more than
one way to skin the bandwidth cat.  (If anyone is working on this, or
interested in talking about it, please contact me)

Dennis Allard
allard@isi.edu
From: kkwong@galaxy.gov.bc.ca
Newsgroups: comp.unix.bsd
Subject: Help: Gateway G/Ethertwist Card for 386BSD
Date: 14 Sep 92 11:47:23 -0700
Organization: BC Systems Corporation

Hi.
	I got tiny 386BSD (dist.fs and fixit.fs) installed on a Synergistic 
Computer,Inc's 486DX-33 with a Maxtor 200 Mb hard drive and 16 Meg RAM.
Now I like to ftp the full 386BSD distribution from my Sparc2.  
I have a Gateway G/Ethertwist 16 bit AT adaptor Ethernet card.  
Can I make this beast to work with 386BSD?  What is the procedure?  
It is using irq2 but 386BSD doesn't know it at startup.  I can't find
any Ethernet card driver (we0, ne0, ec0, or is0) in the stock /dev directory
either.  One more question:  what is npx0 at 0xf0 irq13?  
Is it the parallel card???  Thanks a zillion in advance.

Ken Wong		(email: kkwong@galaxy.gov.bc.ca)
Ministry of Environment, Lands & Parks, Victoria, BC, Canada
From: babraham@unpcs1.cs.unp.ac.za (Bobby Abraham)
Newsgroups: comp.unix.bsd
Subject: AKCL for BSD386 (wanted)
Date: Mon, 7 Sep 1992 07:47:36 GMT
Organization: Dept. Computer Science, UNP
Distribution: world
NNTP-Posting-Host: pc030.cc.unp.ac.za
Keywords: Common Lisp


Can anyone tell me how the work on a Common Lisp implementation for 386BSD
is going.  I am lost without it and even the SCO system I had could run 
AKCL (admittedly compiled under Esix).

Thank you
-------------------------------------------------------------------
Bobby Abraham
Dept. of Computer Science
University of Natal, Pietermaritzburg
email - babraham@unpcs1.cs.unp.ac.za
        abraham@unpsun1.cc.unp.ac.za
-------------------------------------------------------------------
From: gnb@duke.bby.com.au (Gregory N. Bond)
Newsgroups: comp.unix.bsd
Subject: Re: Shared Libs for X11?, was Re: 386bsd -- The New Newsgroup
Date: 14 Sep 92 23:29:49 GMT
	<veit.716026274@du9ds3> <18lkkkINN14d@agate.berkeley.edu>
	<veit.716107923@du9ds3> <7dnL02y821gh01@JUTS.ccc.amdahl.com>
	<veit.716291291@du9ds3>
Organization: Burdett, Buckeridge & Young, Melbourne, Australia

>>>>> On 12 Sep 92 09:48:11 GMT, veit@du9ds3.uni-duisburg.de (Holger Veit) said:

>> The program loader (kern_execve) resolves the lib references to the
>> shared area, and makes the program's shared data segment
>> copy-on-write so that it does not influence the memory of the
>> library server.

The kernel is probably the wrong place to put all this.  (kern_execve
is hairy enough; witness the number of patches).  Instead, do it like
SunOs does: include just enough stuff in the prolog to mmap() in a
dynamic linker (/usr/lib/ld.so) written in PIC (with no global data)
and jump to it.  Have it do all the fixups, then return.  Unmmap it
and call the main() routine.

This could be done completely independant of the kernel.

Greg.
--
Gregory Bond <gnb@bby.com.au> Burdett Buckeridge & Young Ltd Melbourne Australia
``USL has never sold long distance.  You're going after the wrong men in black 
  hats.  (Or, in the case of Plan 9, black space suits)'' - Tom Limoncelli
Newsgroups: comp.unix.bsd
From: richard@pegasus.com (Richard Foulk)
Subject: Re: AT&T Long Distance Boycott (was: BNR2SS, Mach, and The Lawsuit)
Organization: Pegasus,  Honolulu
Date: Mon, 7 Sep 92 15:34:53 GMT

>>You're assuming that "posix compliant" means anything actually useful.
>>From what I've seen it's seriously incomplete for any real applications,
>>and so amounts to no more than a checkmark on a requirements sheet.
>
>I don't know about that.  gcc, gas, GNU make, the GNU binutils (and,
>perforce, the GNU BFD library) can all be built in a POSIX-only environment.
>(They can do this, partially, because they supply lots of what the need, but
>that's okay.)


If you're saying that POSIX specifies *everything* necessary to build
those GNU products, I think you are mistaken.

POSIX is too limited to be worthwhile.


-- 
Richard Foulk		richard@pegasus.com
Organization: Doctoral student, Statistics, Carnegie Mellon, Pittsburgh, PA
Newsgroups: comp.unix.bsd
Date: Thu, 10 Sep 1992 04:03:19 -0400 
From: Tao Jiang <tj2n+@andrew.cmu.edu>
Subject: [386BSD] cc1 fatal error


Hi, I tried to compile a program and got the cc1 fata error like:
cc -I.. -I../..  -O -c fogdeck.c
cc: Program cc1 got fatal signal 6.
*** Error code 1

I could not figure out what's wrong with it.

Any help will be greatly appreciated!

TJ
Newsgroups: comp.unix.bsd
From: michael@resonex.com (Michael Bryan)
Subject: Re: 386bsd -- The New Newsgroup
Organization: Resonex Inc., Sunnyvale CA
Date: Wed, 9 Sep 1992 10:04:05 GMT

In article <1992Sep9.143323.7559@terminator.cc.umich.edu> pauls@umich.edu writes:
>I'm not stuck on the names of any of these, so don't debate them with me.   
>This is what I would propose if I were to do it today:
>
>comp.os.386bsd                <-- misc discussion and coordination
>comp.os.386bsd.install        <-- slightly nicer term for newbie
>comp.os.386bsd.development    <-- patches, bugs, ports, new software

Again, if you're doing a heirarchy like this, you should have
"comp.os.386bsd.misc", and no upper level group.

I still think a single group is enough, though.

-- 
Michael Bryan  michael@resonex.com  "Milk and Cheese in '92!"  |     ,_,
"Lovers are like... dentures.  You don't want them in your     |    /oo \
mouth all night, but you sure as hell want them within arm's   |    <>__|
reach in the morning!"  --- Miss Elmira Gulch                  |    |  U|
Newsgroups: comp.unix.bsd
From: richard@pegasus.com (Richard Foulk)
Subject: Re: AT&T Long Distance Boycott (was: BNR2SS, Mach, and The Lawsuit)
Organization: Pegasus,  Honolulu
Date: Thu, 10 Sep 92 01:55:48 GMT

>>A good example of the problem that half a standard (POSIX) creates!  Take
>>a look at just about any of the larger products that have crossed over
>>from the DOS world.  They all use their own incompatible version of a
>>termcap-like library.
>
>A good example of what a closed mind creates.
>
>The termcap library I used was the Net/2 termcap library.  Since I was
>creating a library suite that could be used without any of the system's
>library or header files, I obviously couldn't use the system termcap library.
>
>Sad situation.
>

A sad situation that a better POSIX standard could have helped to avoid.

Termcap/terminfo is a standard that's available on, pretty much, all
Unixes.  So why leave it out of the POSIX standard?

This is just one example of the problems with POSIX, btw.


-- 
Richard Foulk		richard@pegasus.com
Newsgroups: comp.unix.bsd
From: tim@kimba.catt.citri.edu.au (Tim Liddelow)
Subject: Can't build kernel due to lack of ../../sys/param.h
Keywords: kernel
Organization: CATT Centre at CITRI, Melbourne, Australia
Date: Tue, 15 Sep 92 01:47:20 GMT

I have tried a 'make depend' when attempting to compile a new kernel;
I have found that I do not have /usr/src/sys.386bsd/sys directory at all.
This could be because I had to do a manual 'cpio' from the etc01.?? files,
however after grabbing a listing from cpio of the files, I can't find
the dir in the archive.  Could someone let me know whats going on ?  I
usually use 'tar', and this was the first time I have used cpio.  Did I leave
something out ?  

As a result of not having the directory, I get a 'can't find ../../sys/param.h'
error from make.

And replies by email appreciated.
Thanks in advance

Tim Liddelow


-- 
________________________________________________________________________________
  Tim Liddelow                                          for(;;) fork();
  Systems Programmer
  Centre of Advanced Technology in Telecommunications   My brain on a bad day.
  CITRI, Melbourne, Australia                           
  internet : tim@kimba.catt.citri.edu.au                
  Phone : +61 3 282 2455   Fax : +61 3 282 2444	        
________________________________________________________________________________
Newsgroups: comp.unix.bsd
From: bcrawfor@sol.UVic.CA (Bryan Crawford)
Subject: emacs for bsd386??
Organization: University of Victoria
Date: 14 Sep 92 17:02:20 GMT

an anuyone point me in the right direction for acquiring
emacs (preferably GNU) which has been ported to BSD386.

thanks in advance,

Pat Dowler
dowler@otter.phys.uvic.ca

-- 

bcrawfor@Sol.UVic.CA  -- member of the society for simple .signatures (SSS)
Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: Anyone ported GNU-make to 386BSD ?
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Sun, 6 Sep 1992 01:57:03 GMT

In article 19476@Informatik.TU-Muenchen.DE, gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart) writes:
>I need gmake to install the GNU-netfax package. It would be much work
>to rewrite the package to be compatible to usual make.
>After playing aroung with some defines I got gmake compiled but it 
>keeps core-dumping.

That's the easy problem: you need to make sure that the files that reference
glob() include <glob.h> and not "glob/glob.h".  The glob_t structure declared
in "glob/glob.h" is two words shorter than the one used by the BSD glob() so
glob() clobbers some local variables.

The one problem I haven't sorted out yet is the fact that GNU make calls
setgid() in an invalid context.  This causes problems if you invoke make
from emacs.

	Chris Flatters
	cflatter@nrao.edu
From: adam@micromuse.co.uk (Adam Kerrison)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD - Success & Failure !
Date: 7 Sep 92 08:21:22 GMT
Reply-To: adam@micromuse.co.uk
Organization: MicroMuse Ltd, London, UK

For those of you who are interested ...

I know have my ST1239A drive working with BSD - a great it is too !

The problem turned out to be the IDE controller. I had one of these
integrated IDE controllers, with 2 serial and 2 parallel ports on it
as well. I have now changed this for a really old IDE controller and
equally old serial/parallel board and the system is fine.

Great, now I have UNIX at home - now to compile X386, set up the printer,
write a device driver for my scanner, write the application to read the
scanner, and .......

Oh well, At least its a start.

Thanks again to all those people who took the time to reply ..

Adam

---
===========================================================================
Adam Kerrison                  | Phone : +44 71 352 7774
Technical Support              | Fax   : +44 71 351 7834
MicroMuse Ltd                  | E-mail: adam@micromuse.co.uk
London SW10 0RN                | 
===========================================================================
"When you kill a man, you're a murderer. Kill many, and you're a conqueror.
Kill them all, you're a god !" - Think about it
===========================================================================
From: hedrick@athos.rutgers.edu (Charles Hedrick)
Newsgroups: comp.unix.bsd
Subject: solution to booting problem
Date: 7 Sep 92 18:06:00 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

A few days ago I posted that I was unable to boot after minibsd
installed itself to disk.  It turns out that it wants the partition
to be on a cylinder boundary.  I was using the first partition.
It was offset by one sector, to provide root for the master boot
block.  This isn't enough.  I recreated it starting at the second
cylinder, and it worked fine.
Newsgroups: comp.unix.bsd
From: vixie@pa.dec.com (Paul A Vixie)
Subject: Re: 4.3bsd vs NET2: upgrading a VAX?
Organization: DEC Network Software Lab
Date: 11 Sep 92 14:09:43

Your best bet is to just install 4.3bsd-reno.  I have (thanks to some other
guys involved in the 4.4bsd->VAX port) a 4.3-reno kernel with a mostly-4.4bsd
top half, and I have been using this to port the bottom half.  Neither kernel
is as stable as 4.3-reno was.  And at this point it's looking like it's not
going to be done by the time 4.4 ships.
--
Paul Vixie, DEC Network Systems Lab	
Palo Alto, California, USA         	"Don't be a rebel, or a conformist;
<vixie@pa.dec.com> decwrl!vixie		they're the same thing, anyway.  Find
<paul@vix.com>     vixie!paul		your own path, and stay on it."  -me
Newsgroups: comp.unix.bsd
From: elh@netcom.com (Ed Hudson)
Subject: Re: 386BSD PARTIAL PATCH KIT NOW AVAILABLE
Date: Tue, 15 Sep 92 22:47:27 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Distribution: usa


	seconding what asoper@azania.twuug.com has said,

	thanks very much Mr. Lambert for your efforts in putting
	this patch kit together.

		-elh
Newsgroups: comp.unix.bsd
From: rivers@ponds.uucp (Thomas David Rivers)
Subject: Some more on NMI problems (some meager advancement)
Date: Mon, 7 Sep 1992 01:43:51 GMT


Well, I thought I would relay my current status with the NMI
investigation.

  Right now, I'm thinking it has something to do with an IDE
 controller/disk drive, so I have been examining the wd.c driver
 trying to divine what it might be; without too much luck. (I 
 know very little about the IDE/WD disk controllers.)

  The common thread seems to be:
    1) It happens during some prolonged disk I/O
         (i.e. rebuilding the kernel over-and-over, or building X)
    2) It happens with IDE drives, other people have run my test
        (rebuilding the kernel) with a SCSI drive, 486-33 and 16meg
        without finding any NMIs.

 I have tried several switches on my controller; 

   1) Having the disk drive/controller assert IOCHRDY (by default it
      doesn't.)
   2) Changing the "precompensation" (which I don't believe is
      related to disk precompensation) from 125ns to 187ns.
   3) Changing the speed of the processor from 20mhz to 8mhz.

  None of these changes seems to affect the problem.

  Several people have suggested it could be a cache problem; but I'm
 running on a very old 20mhz 386, it doesn't have any caches.

  I'm still reluctant to believe it's actually a memory problem, since
 
   1) It doesn't occur with version 0.0
   2) It only occurs *once*, once I get one NMI, it never happens
        again.  You wouldn't think the memory could repair itself...
   3) It happens within 2 hours of running the kernel compiles, often
       within two minutes.  38+hours of memory tests (reading and
       writting double/single words randomly) found nothing.


 One last item; I did discover where the empty /var/log/messages line
 was produced, and why you only got the empty line on the console,
 without the NMI messages.

 In isa.c, the function to handle the Non-Maskable Interrupt (isa_nmi)
 calls log(), but the string contains an initial new-line.  Removing
 that new-line fixes those problem, at least.

 Again, suggestions are always welcome - I would especially appreciate
 it if someone with an IDE setup tries to compile the kernel over-and-over
 (i.e. in a shell "for"-loop) to see if the problem can be reproduced
 by more people.

 My next approach is to replace the wd.c driver with Tom Ivar Helbekkmo's
 new driver - to see if he has altered things enough to either cause
 the problem to go away, or make it's occurrence more reliable.  Unfortunately,
 I don't seem to be able to get to barsoom.nhh.no right now...
 (trans-atlantic links are difficult at best.)

   - Still trying!! -

  - Dave Rivers -
   (rivers@ponds.uucp)
From: esw@po.CWRU.Edu (Eric S. Wallace)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Ethernet problem
Date: 10 Sep 1992 05:59:25 GMT
Organization: Case Western Reserve University, Cleveland, Ohio (USA)
NNTP-Posting-Host: hela.ins.cwru.edu



   I'm trying to install 386 BSD via the internet, only Tiny BSD 386
won't recognize my ethernet card on bootup. The card is a Cabletron
configured to IRQ9, port 0x280. So I guess my basic questions are,

a) Does anyone know if this card will even work? (I have no idea if
   Cabletron is a "clone" of a supported card or not.)
b) What criteria does 386 BSD use to determine if a card is present?
   Failing meeting this criteria, is there anyway to "fool" BSD into
   putting the driver on anyway? The reason I ask this is because even
   booting on DOS, the packet driver complains about a possible IRQ
   conflict (a game port, now disabled) and babbles about an 8-bit bus,
   which it never did on any other IRQ. I don't know if any of these
   warnings might relate to BSD not recognizing the card.

Thanks in advance,

Eric Wallace
wallace@chezmoto.ai.mit.edu
esw@po.cwru.edu
From: fty@bizarre.rtpnc.epa.gov (Frank Terhaar-Yonkers)
Newsgroups: comp.unix.bsd
Subject: Re: more about 386BSD SLIP
Date: 8 Sep 92 20:10:31 GMT
Organization: United States Environmental Protection Agency

>In article,  schneck@Physik.TU-Muenchen.DE (Bernhard Schneck) writes:
>dmuntz@quip.eecs.umich.edu (Daniel A Muntz) writes:
>
>In article <Sep.7.14.41.53.1992.602@athos.rutgers.edu> hedrick@athos.rutgers.edu (Charles Hedrick) writes:
>>>Aside from the well-known silo overflow problem, I think there's
>>>another problem in the serial driver.  I just had output hang in SLIP.
>
>There may be a buglet in obcopy (or something like that) in the kernel
>code, which will kill TCP ACK packets (among others).  There was a fix
>in the PPP code for 386BSD which also repairs SLIP.
>
>\Bernhard.
>--
>Bernhard Schneck              | Email: Bernhard.Schneck@Physik.TU-Muenchen.DE
>GeNUA Gesellschaft fuer Netz- | TU Muenchen Physik | There is no problem so big
>und UNIX-Administration mbH   | 8046 Garching      | that it cannot be run away
>8000 Muenchen 83, Germany     | Germany            | from.   Illusions, R. Bach

Indeed there is!  I've been trying to get PPP up and running.  I finally got
the boxes talking and I'm seeing the same behaviour.  Where can I find
this fix?  It wasn't in the PPP code I picked up from cayman.com. 
(I don't think ...)

-- 
-------------------------------------------------
Frank Terhaar-Yonkers	fty@bizarre.rtpnc.epa.gov
Unisys/U.S. EPA		(919)541-2297
From: r_moore@vger.nsu.edu
Newsgroups: comp.unix.bsd
Subject: Re: Minimum system requirements for 386bsd ?
Date: 15 Sep 92 13:02:40 EDT

In article <2551.2ab5de20@vger.nsu.edu>, r_moore@vger.nsu.edu writes:
> I need to know what the minimum requirements are to run 386bsd are. More
> specifically will it run on this configuration:
> 386sx @16mhz
> 1 meg RAM
> 40 meg HD
> if it will not run on this system what additions will I need to make ?
>         Thanks, Richard
> 
 While I'm at it is there a bsd FAQ for information such as my above question ?
if so is there a site where I can FTP it from ?
          Thanks again, Richard
From: tmh@keks.first.gmd.de (Thomas Hoberg)
Newsgroups: comp.unix.bsd
Subject: Re: Shared Libraries for 386BSD
Date: 15 Sep 92 01:53:52 GMT
	<7dnL02y821gh01@JUTS.ccc.amdahl.com>
	<1992Sep11.154912.25093@fcom.cc.utah.edu>
Organization: GMD-FIRST, Berlin
In-reply-to: terry@cs.weber.edu's message of 11 Sep 92 15:49:12 GMT

Hmm, didn't SUN contribute their VM system and shared library source
code to BSD some months ago? Did that perhaps find it's way into 4.4?
Or was that only the VM system...?
Who knows more?
---
Thomas M. Hoberg   | Internet: tmh@first.gmd.de
1000 Berlin 41     |           tmh@cs.tu-berlin.de
Wielandstr. 4      |
Germany            | BITNET:   tmh@tub.bitnet 
+49-30-851-50-21   |

Newsgroups: comp.unix.bsd,comp.protocols.tcp-ip.ibmpc
From: dana@me.chalmers.se (Dan Andersson)
Newsgroups: comp.unix.bsd
Subject: Has anyone GCC-2.2.2 for 386bsd?
Date: 8 Sep 92 22:14:52 GMT


Has anyone got gcc-2.2.2 up and running yet?
I've been fighting with it for a couple of days now, but sees no end in 
the patching.

If you have it up and running? Pls mail a patch-list or where to be found
for FTP.

Respond with direct e-mail....   dana@theta.me.chalmers.se


Rgds


Dan Andersson
Newsgroups: comp.unix.bsd