HDTenEightyP/NetNews huggingface dataset:
From: raz@socs.uts.edu.au (The Inimitable Raz)
Subject: Re: [386bsd] cp something to /bin/cp and cp core dumps; bug or feature?
Organization: Computing Sciences, Uni of Technology, Sydney.
Date: 14 Dec 92 07:18:22 GMT

vixie@pa.dec.com (Paul A Vixie) writes:


>Paged "Virtual Memory", as BSD implements it, means that programs are
>brought into memory in itty bitty pieces called "pages", and various
>lies are told that make the program believe that its text and its data
>and its stack are all contiguous in memory even though most of it could
>be missing and what's there could be in random order in the real RAM.

[Excellent description of paged virtal memory deleted.]

As I understood it however, writing to an executable was supported by
virtue of unlinking it FIRST, thus leaving it floating in limbo till
the process(es) using the pages were terminated. Is this not the case?


--
Bye for now.
         - Raz           

raz@socs.uts.edu.au   (Roland Turner)   (OH) 61 2 319 5700
Newsgroups: comp.unix.bsd
From: randy@chinet.chi.il.us (Randy Suess)
Subject: Re: WD8003E ethernet card compatibility
Keywords: AKCL Common LISP Kyoto Austin 386BSD
Organization: Chinet - Public Access UNIX
Date: Thu, 17 Dec 1992 22:12:43 GMT

In article <1gorbsINN8ku@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:
>Has anyone managed to get 386BSD to work correctly with the WD8003E ethernet
>card?  I ultimately gave up on using this card for my development machine many
>months ago and bought an SMC/WD Elite16 Combo card instead which worked fine.
>
	I have never had a problem with the original WD8003e 8 bit
	cards.  You just need to remove the other ethernet drivers
	from the kernel if you want the wd8003 to be at interrupt 2/9.
	If you change it to something like 7 (disabling the useless
	lpt1 interrupt) it works fine with the other drivers still
	in the kernel.
	This is with various old wd8003es and 486/33s, 386/33s and
	386sx/25s.


-- 
	I am created Shiva the Destroyer; Death, the shatterer of worlds!
	Who is this dog meat who stands before me now?
	That's the biz, sweetheart.
Randy Suess					 randy@chinet.chi.il.us
From: agallagh@slate.mines.colorado.edu (GALLAGHER ANDREA J )
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] System ignores floppies.
Date: 12 Dec 92 00:28:07 GMT
Organization: Colorado School of Mines

ngorelic@speclab.cr.usgs.gov (I) writes:
> I can boot the dist.fs floppy fine.  It installs correctly,
> and I can even boot the hard drive thereafter.  What I cannot
> do however, is access either of the floppies.

Several people sent answers to this problem, immediatly after I figured
out how to solve it.  The is definitly a question/answer that should be
int the FAQ.

The answer is (don't laugh):  You cannot boot with a floppy in the drive,
                              even if the drive door is open.  Apparently
                              just having a floppy in there is enough to
                              cause timing problems, and the system just
                              ignores the floppies thereafter.

Simple fix, but completely crippling if you don't know the answer.

Noel (ngorelic@speclab.cr.usgs.gov)
From: wjin@cs.uh.edu (W. Woody Jin)
Newsgroups: comp.unix.bsd
Subject: Re: Dumb Question: Why 512 byte block?
Date: 18 Dec 1992 18:59:50 GMT
Organization: University of Houston
NNTP-Posting-Host: rodin.cs.uh.edu

In article <1992Dec18.030833.7395@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>In article <1992Dec18.005050.20594@decuac.dec.com>, darryl@vfofu1.dco.dec.com (Darryl Wagoner) writes:
>|> Why is everything in 1/2 k block instead the BSD standard of 1024 byte blocks?
>|> Yes, I know there is a '-k' switch, but it seems to me it should be
>|> the otherway around.
>
>Think of disk blocks as the curve-fitting algoritm they taught you when you
>first learned integral calculus:  the smaller your slices, the closer you
>come to approximating the area under the curve.
>
>If I have a set of 6 512 byte files, I will use up 3K of disk for them;
>similarly, if I had a blocking factor of 1K, I would use of 6K (since the
>smallest fragment usable by a file is now 1K.
>
>If I have 6 1.5K files, this translates to 9K of disk(512B) or 12K of disk(1K).
>Obviously, if I have 6 1.6K files, both blocking factors take up 512K.

I did not think that Fast Unix File System works this way.
If you have 6 1.5K files using 1K blocks,
   6 1k blocks will take each 1K from each file, and 
   3 1k blocks will take 0.5k from each file.
This was my understading from the famous FUFS paper.
   

>The offset into the disk is a _block_offset_; what this means is that you
>will start looking for data at the offet*blocking_size when given an address,
>and that reads/write into kernel cache are done (usually) in block_size
>increments.  A device accessed this way is a blocked device.
>
>When you store a lot of little files on the disk, small blocks are wasteful
>of disk space (for instance, 1024 empty files take 512K vs 1M of disk for
>the smaller blocking factor).

And choosing a disk block size is a performance issue rather than
disk space issue. One should tune disk block size and fragment size
to get the best performance.

I thought that 386BSD uses this Fast Unix File System.

-- 
____   ____  ____ ____________________________________ (___) _________________
|  |   |  |  |  |  W. Woody Jin (wjin@cs.uh.edu)       (o o)      Moo.... 
|  |   |  |__|  |  PhD Student. Research Asst.  o=======\ /  I'm  a Cow Lover.
|  |   |        |  Dept. of Computer Science   / |     ||O   My wife  was born
\  |---|  |--|  |  University of Houston      `  ||'---||    in Cow year. Mooo
 \____/|__|  |__| _______________________________^^    ^^_____________________


Newsgroups: comp.unix.bsd
From: fredriks@austin.ibm.com (Lars Fredriksen)
Subject: ATI Ultra Pro
Originator: @worf.cet.austin.ibm.com
Date: Fri, 18 Dec 1992 22:00:03 GMT
Organization: IBM Austin


Hi,
	Has anyone an ATI Ultra Pro working with XfreeX (the XBSD8514 server)?

Are you able to get the 24 bit color in 758x1024 mode and the 16 bit color
in the 1024x1024 mode? How much of a nuicance is it that you don't have access
to the Mach32 documentation. I know that you know can get a hold of the Mach8
docs, but I don't know how compatible they are.

	Can someone compare the Ultra Pro to some of the S3 boards that do
24 bit color? I'd like to get a board that I can get the docs for, but I am
also interested in performance. I will have a 17 inch 1024x1024 capable monitor
hooked up to the system so I would like to be able to take advantage of it (Nanao
560i).

	Thanks a lot,

		Lars Fredriksen


PS. as an aside, are there anyone out there that is running 386BSD on a 
MYLEX MAE-486-33? If so could you please contact me. I am having problems
with the new bootblocks, and I would like to find out what the problem is.
-- 

Newsgroups: comp.unix.bsd
From: rich@Rice.edu (& Murphey)
Subject: Re: [386bsd] ftpd bugfix
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
	<RICH.92Dec17231903@superego.Rice.edu>
Date: Fri, 18 Dec 1992 06:16:21 GMT


They fixed ftpd fies are /usr/home/rich/ftpd-0.2-bin.tar.Z and
/usr/home/rich/ftpd-0.2-src.tar.Z on ref.tfs.com (140.145.254.251).
Rich
From: edzard@wft.stack.urc.tue.nl (Jim Rump)
Newsgroups: comp.unix.bsd
Subject: BSD port on 68030 ???
Date: 16 Dec 92 02:45:54 GMT
Organization: Baseline Labs. Eindhoven Holland
NNTP-Posting-Host: shark.wft.stack.urc.tue.nl
X-Newsreader: TIN [version 1.1 PL6]


Hi,

I wonder if there are ports of bsd on 68030 based systems that are
available as *source*. My plan is to port bsd to the Atari-TT.
Well... at least if nobody did this before!


Please respond by mail.

-- Edzard.
From: sitongia@hao.ucar.edu (HAO Computer System Managment Group)
Newsgroups: comp.unix.bsd
Subject: [386bsd] what tape drives can be used?
Keywords: 386bsd tape scsi
Date: 15 Dec 92 22:32:14 GMT
Reply-To: sitongia@hao.ucar.edu
Distribution: usa
Organization: High Altitude Observatory/NCAR, Boulder CO

What brand of tape drives are people using on their 386bsd systems?  I've seen
the threads about not being able to use CMS tape drives.  What about SCSI tape
drives?  What brands of tape drives can be used?

Thanks for your time.

---
--Leonard E. Sitongia           HAO System Manager                 
sitongia@ncar.ucar.edu          voice: (303)497-1509   fax: (303)497-1589
High Altitude Observatory       P.O. Box 3000 Boulder CO  80307
From: vax@ccwf.cc.utexas.edu (Vax)
Newsgroups: comp.unix.bsd
Subject: [386bsd] lock file problems on com port
Keywords: com lock problem help serial rs232
Date: 20 Dec 92 17:42:16 GMT
Organization: The University of Texas at Austin, Austin TX

My machine, if it boots with a lock file in place (left over from a crash),
esp. those on com01, will not use the com port.  This behaviour is correct.
But when the lock file is removed, further attempts to open /dev/com01
hang the entire system.  This is a repeatable failure.
Hints?
-- 
Protect our endangered bandwidth - reply by email.  NO BIG SIGS!
VaX#n8 vax@ccwf.cc.utexas.edu - finger for more info if you even care.
Newsgroups: comp.unix.bsd
From: rooij@mozart.cft.philips.nl (G. van Rooij)
Subject: [386bsd] IDE native geometry, is there a summary?
Keywords: 386bsd, ide
Organization: Philips Communications & Processing Services, Eindhoven
Date: Thu, 17 Dec 1992 15:42:03 GMT

Some time ago, there was a discussion on the usage of ide
disks in native and translated modes. I wondered if someone
can post a summary of this. In particalur I want to know the
follwoing:
I ran the programm posted then that reports the geometry of
thje ide disk. This is done twice, one in normal operation and
once after resetting the controller. 
This program reported the same geometries in both modes. Does
this mean that I can only use them in translated modes?
FYI: the disk are a quantum lpt120 and a seagate st3144a.

-Guido
Newsgroups: comp.unix.bsd
From: darryl@vfofu1.dco.dec.com (Darryl Wagoner)
Subject: [386BSD] Hangs on NFS to wd file copy
Reply-To: darryl@sai.com
Organization: Digital Equipment Corp., Washington ULTRIX Resource Center
X-Newsreader: TIN [version 1.1 PL6]
Date: Mon, 14 Dec 1992 17:03:39 GMT

Configuration:

	486 33Mz with 16 meg ram (no name mother board)
	WD 2340 IDE drive with no name controller
	WD Elite-16 SMD ethernet at IRQ 2 IO 280 and share ram DC000

Symtoms:

	When copying from NFS filesystem to a local disk system will
	just hang.  

	If I do a tar -cf - foo | rsh 386bsd '(cd foodir;tar -xvf -)'

	everything works fine.  

	The system has three partitions a which is 26400 512 blocks,
	g which is 607180 block and swap of 33000 blocks.

	The hangs did seem to start happen after I repartitioned.

Any ideas?

-darryl
darryl@sai.com
	

Xref: sparky comp.unix.bsd:10315 comp.os.linux:20785
From: unger@thorin.swb.de (Juergen Unger)
Newsgroups: comp.unix.bsd,comp.os.linux
Subject: Re: 386BSD + LINIX + GNU + X11R5 on CDROM - let us know what you wan
Date: 15 Dec 92 22:19:59 GMT
Organization: home of the dwarves

wade@nb.rockwell.com (Wade Guthrie) writes:
> In article <1992Dec2.055049.24923@tfs.com>, julian@tfs.com (Julian Elischer) 
> > In article <ByM6vo.C8C@ux1.cso.uiuc.edu> Jeff-Randall@uiuc.edu (Jeff Randal
> > >>The CD will be will be mastered in ISO 9660 format (all filenames 8.3)
> Hoooray!!!!
> > >Perhaps using the rockridge extensions would be a better Idea than a 
> > >non-standard program hacked up just for this CD.. I believe that the
> > >Linux CD-ROM driver already handles them and it would be likely that
> > >the 386BSD driver would eventually support it as well... if it doesn't
> > >already... 
> The Linux cd-rom drivers may support this already, but if you don't already
> HAVE Linux up and running on your system, the point is moot.  I would not
> like to see the Rockridge extensions, 'cause then I wouldn't be able to 
> load Linux from the CD on a system that currently has only DOS.

I thought you can use the CD with the Rockridge extensions on
a system without the this extensions, because its an extension
to the ISO9660 format and not an replacement for it.
Or I'm wrong ?

-Juergen-

-- 
Juergen Unger
EMail : unger@thorin.swb.de + Privat: +49 6253 85140   / most  Computers /
Office: +49 6196 908 688    + FAX   : +49 6253 85110 / doing it binary /
Newsgroups: comp.unix.bsd
From: thomas@aeon.in-berlin.de (Thomas Wolfram)
Subject: Re: OS-BS & Codrv (was:Re: Want info on German Boot Manager thingy please)
Organization: Cities in Dust
Date: Wed, 16 Dec 1992 00:54:35 GMT

In <veit.724415647@du9ds3> veit@du9ds3.fb9dv.uni-duisburg.de (Holger Veit) writes:

>In <veit.724405437@du9ds3> veit@du9ds3.fb9dv.uni-duisburg.de (Holger Veit) writes:

>Some addendum to a possible problem between the partition switcher OS-BS
>mentioned above and my console driver CODRV:

>(excerpt from BUGLIST.151292, only bug added since BUGLIST.011292):

>-------
>BUG 14:	The old pccons worked. Codrv hangs after showing the Copyright
>	message. I use Thomas Wolfram's "os-bs" (osbs-132/134) 
>	partition switcher.

>FIX 14:	os-bs is broken in that way that the keyboard character to be
>	entered is not correctly removed from the keyboard queue. 
>	OS-BS does not use, for some unknown reasons, BIOS Interrupt 16h, 
>	but fiddles with the keyboard controller itself. This causes a 
>	release code to be left in the keyboard queue, when a selection 
>	key is pressed. This code irriates the codrv attach routine and 
>	causes 386bsd to hang. The problem (with a different effect) also
>	occurs with OS/2 2.0 with the first keyboard request.

I know myself some installations with OS/2 and os-bs working fine.

>	Fix: This should be fixed in OS-BS, but it is unknown whether the
>	author is still available.

I'm alive!!! (I don't read this group regulary.)
But I'll try to fix it soon and make a new version 1.35.

>	The next version of codrv will address this problem for 386bsd.
>	Workarounds:
>	1. Make 386bsd the default partition, and let it timeout.
>	   The effect in other (DOS-type) OS versions is not so extreme
>	   (mostly additional character at first keyboard access). The
>	   effect on Linux or other UNIX versions is unknown.

This is no problem for Linux, Interactive, OS/2, DOS. (I've reports.)

[...]

regards,
Thomas
-- 
Thomas Wolfram, thomas@aeon.in-berlin.de
EANTC, TU Berlin, wolf@prz.tu-berlin.de, +49 030 31421294
From: merlin@neuro.usc.edu (merlin)
Newsgroups: comp.unix.bsd
Subject: 386BSD INGRES ???
Date: 16 Dec 1992 19:16:54 -0800
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: neuro.usc.edu
Keywords: x

I read somewhere recently that INGRES was available on 386BSD.  Where is it
possible to acquire this package?  Does it seem pretty reliable?  Would the
sources possibly compile without problems under SCO UNIX 3.2r2.0 ODT 1.1 ??

Thanks, AJ

------------------------------------------------------------------------------
Alexander-James Annala
Principal Investigator
Neuroscience Image Analysis Network
HEDCO Neuroscience Building, Fifth Floor
University of Southern California
University Park
Los Angeles, CA 90089-2520
------------------------------------------------------------------------------
From: michaelm@pike.ee.mcgill.ca (Michael Moscovitch)
Newsgroups: comp.unix.bsd
Subject: need help with slip problem.
Date: 20 Dec 92 19:11:40 GMT
Organization: McGill University - VLSI Laboratory, Montreal, CANADA.

I'm having a problem with SLIP. After using it for a while, it ceases to work.
I used to have slip working such that it would run all night without problems,
however I reinstalled the system on a new disk. Does this problem sound
familiar to anyone? Is there an existing patch for this?

My configuration is:
386bsd 0.1 patched with patchkit upto 58. using cgd's multiport com driver.

The following is an example of what happens when slip nolonger works.

% ping pike
PING pike (132.206.62.1): 56 data bytes
ping: sendto: No buffer space available
ping: wrote pike 64 chars, ret=-1
ping: sendto: No buffer space available
ping: wrote pike 64 chars, ret=-1
ping: sendto: No buffer space available
ping: wrote pike 64 chars, ret=-1
ping: sendto: No buffer space available
ping: wrote pike 64 chars, ret=-1
^C
--- pike ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss

% netstat -i
Name  Mtu   Network     Address            Ipkts Ierrs    Opkts Oerrs  Coll
sl0   296   <Link>                           538     0      585    15     0
sl0   296   132.206.27  romulus.ee.mcgi      538     0      585    15     0
sl1*  296   <Link>                             0     0        0     0     0
lo0   1536  <Link>                           130     0      130     0     0
lo0   1536  loopback    localhost            130     0      130     0     0

% netstat -m
168 mbufs in use:
        31 mbufs allocated to data
        42 mbufs allocated to packet headers
        63 mbufs allocated to protocol control blocks
        30 mbufs allocated to socket names and addresses
        2 mbufs allocated to interface addresses
1/16 mapped pages in use
37 Kbytes allocated to network (59% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines


------

Michael Moscovitch
michaelm@pike.ee.mcgill.ca
From: andrew@werple.apana.org.au (Andrew Herbert)
Newsgroups: comp.unix.bsd
Subject: [386bsd] ICMP redirect handling panic - FIX
Date: 14 Dec 1992 13:30:41 +1100
Organization: werple public-access unix, Melbourne
NNTP-Posting-Host: werple.apana.org.au

Running a 386bsd machine attached to a router box (running the freely available
pcroute software) handling modem-based SLIP links can panic 386bsd if a link
fails while in use.  This is due to pcroute sending ICMP redirects to say that
the current route is no longer valid.

The fact that the ENETUNREACH branch (look in the source for rtredirect()),
the cause of the panic, is taken at all makes me somewhat dubious as to whether
pcroute is doing the right thing.  printf()s indicated that the redirects were
coming from the router's slip interface that had just died, rather than the
ethernet interface as is (reasonably) expected by 386bsd.  But in any case, it
certainly uncovered a 386bsd bug.

Few people are likely to have run into this particular problem, but for those
that have (and for people that don't like the thought of running broken
kernels :-) the fix follows...

enjoy,
Andrew Herbert

*** /sys/net/route.c.unhacked	Sat Dec 12 18:06:18 1992
--- /sys/net/route.c	Mon Dec 14 13:06:07 1992
***************
*** 31,36 ****
--- 31,40 ----
   * SUCH DAMAGE.
   *
   *	@(#)route.c	7.22 (Berkeley) 6/27/91
+  *
+  * PATCHES
+  * -------
+  * rtredirect() fix	12 Dec 92	andrew@werple.apana.org.au
   */
  #include "param.h"
  #include "systm.h"
***************
*** 150,156 ****
  	int flags;
  	struct rtentry **rtp;
  {
! 	register struct rtentry *rt;
  	int error = 0;
  	short *stat = 0;
  
--- 154,160 ----
  	int flags;
  	struct rtentry **rtp;
  {
! 	register struct rtentry *rt = 0;   /* andrew@werple - 12 Dec 92  XXX */
  	int error = 0;
  	short *stat = 0;
  
***************
*** 170,175 ****
--- 174,183 ----
  	if (!(flags & RTF_DONE) && rt && !equal(src, rt->rt_gateway))
  		error = EINVAL;
  	else if (ifa_ifwithaddr(gateway))
+ /*
+  * XXX - shouldn't this be testing whether (ifa_ifwithaddr(gateway) == 0) ???
+  * i.e. gateway can't be reached from any interface - andrew@werple, 12 Dec 92
+  */
  		error = EHOSTUNREACH;
  	if (error)
  		goto done;
From: mathias@stacken.kth.se (Mathias Bage)
Newsgroups: comp.unix.bsd
Subject: Re: INTERNATIONALIZATION: JAPAN, FAR EAST
Keywords: Han Kanji Katakana Hirugana ISO10646 Unicode Codepages
Date: 16 Dec 92 00:57:36 GMT
Organization: Royal Institute of Technology, NADA

In <1gksolINNmkg@frigate.doc.ic.ac.uk> kd@doc.ic.ac.uk (Kostis Dryllerakis) writes:
>In article <1992Dec14.185028.9757@fcom.cc.utah.edu>, you write:
>> I know a lot of the Japaneese 386BSD community can not email out of Japan,
>> so this is an open letter to them, and to Atsushi MURAI and other people
>> there who are active in this newsgroup.
>> 
>> What kind of internationalization would best enable you to use 386BSD?
>> 
>>       o       Kanji support?
>>       o       Kana (Katakan/Hirugana) support?
>> 
[stuff deleted]

>        Preliminary attemps have already been made (I personally work
>under X-windows with greek ISO-standard characters without many
>problems) but a coordinated effort for internationalisation is indeed
>necessary. Note that the rest of the operating systems are currently
>"externally touched" in order to support the greek language i.e.  bu
>hacking your way out.

  Has anyone in this newsgroup ever heard of the Unicode/ISO10646
(UCS) standard?  It exists today and has everything (almost), even
though the Japanese don't like the sort order of the Kanji
characters...  Look/ask in comp.internat.std for more info.  See also
RFC 1345.

-Mathias
-- 
         .        <= it's actually a ring over the a
Mathias Bage		mathias@stacken.kth.se
Organization: Stanford Linear Accelerator Center
Date: Monday, 14 Dec 1992 20:08:49 PST
From: <CALT@SLACVM.SLAC.STANFORD.EDU>
Newsgroups: comp.unix.bsd
Subject: Config SLIP

Hello -- I have 386bsd and XFree86 installed. They worked just fine.
I have a 9600-baud modem. I want to configure SLIP so that my PC
can join my local network here. I understand 386bsd supports SLIP.
Could someone advise me how to configure it? Thanks a lot!
Ching Shih
shih@cithex.caltech.edu
From: ferrick@acsu.buffalo.edu (Patrick K. Ferrick)
Newsgroups: comp.unix.bsd
Subject: Tape Handling routines?
Keywords: 386bsd tape scsi
Date: 20 Dec 92 18:23:44 GMT
Distribution: usa
Organization: UB


Just wondering:  has anyone worked on "mt" (a magnetic tape handling program
that I last saw running under SunOS) ??

Or is it proprietary to Sun?  I was having great fun using it with multiple-
tar tapes on a Sun, and I'd like to be able to use it unde 386bsd to get at 
my collection of source code!

thanks,
pat
Newsgroups: comp.unix.bsd
From: wolfy@im.ncu.edu.tw (Jann-Yea Sue)
Subject: Re: Diffs to BSDI BSD/386 Ported Software List
Reply-To: wolfy@im.ncu.edu.tw
Organization: Sun Microsystems, Inc.
Date: Fri, 18 Dec 1992 12:59:23 GMT

Hi! all guys of 386bsd
   There is a new mirror-site in Taiwan which domain name is im.mgt.ncu.edu.tw. Welcome to use it, Good luck all!
				Ice_Baby(wolfy@im.mgt.ncu.edu.tw)
From: "Andrew A. Chernov, Black Mage" <ache@astral.msk.su>
Newsgroups: comp.unix.bsd
Subject: [386bsd] Time change in CMOS
Date: Tue, 15 Dec 92 21:20:50 +0300
Distribution: world
Organization: Ha-oh-lahm Yetzirah
Reply-To: ache@astral.msk.su

Hi, folks.
Does anybody have code to make time change really written to CMOS?
Current settimeofday() function don't touch CMOS clock :-(
-- 
In-This-Life:  Andrew A. Chernov    |  "Hay mas dicha, mas contento
Internet:      ache@astral.msk.su   |  "Que adorar una hermosura
Organization:  The RELCOM Corp.,    |  "Brujuleada entre los lejos
               Moscow, Russia       |  "De lo imposible?!"  (Calderon)

Newsgroups: comp.unix.bsd
From: ricky@lindblat.cc.monash.edu.au (Mr RS Mcconachy)
Subject: Want info on German Boot Manager thingy please
Organization: Monash University, Melb., Australia.
Date: Mon, 14 Dec 1992 02:34:13 GMT

G'day people,

A few months back (not long after the release of 0.1 386BSD in fact)
a German getleman posted a note to this group about his boot manager
program.  It was a small C program that you compiled using Turbo C
and ran from DOS to create a boot record that presents a menu on
booting the machine asking which primary partition you would like to
boot from.  It had all sorts of nice features and worked great on a
friend's system, and I would like to use it on mine now.  Unfortunately
I no longer have the post (which gave and FTP site and filename) or the
program.  If anyone can help me track this program down I'd be very
appreciative.  Thaks in advance,

Richard McConachy - ricky@lindblat.cc.monash.edu.au