*BSD News Article 15314


Return to BSD News archive

Xref: sserve comp.os.386bsd.misc:250 comp.os.linux:36505
Newsgroups: comp.os.386bsd.misc,comp.os.linux
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!gatech!news.byu.edu!ns.novell.com!gateway.univel.com!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Linux/386bsd on a diskless workstation
Message-ID: <1993Apr28.204501.6685@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University  (Ogden, UT)
References: <C5sACr.Jp2@sleeper.apana.org.au> <1993Apr22.214040.27674@fcom.cc.utah.edu> <C62u58.3Du@sleeper.apana.org.au>
Date: Wed, 28 Apr 93 20:45:01 GMT
Lines: 56

In article <C62u58.3Du@sleeper.apana.org.au> raz@sleeper.apana.org.au (Roland Turner) writes:
>terry@cs.weber.edu (A Wizard of Earth C) writes:
>>location that doesn't interfere with the operation of the download.  This
>>is the first good argument I have heard for a DOS boot-loader for 386BSD
>>or Linux... but I would change the process as follows:
>
>>	LSL
>>	RPLODI
>>	NE2000
>>	IPXODI
>>	NETX
>>	F:
>>	COPYHIGH BOOT_IMAGE
>>	DETACHER
>>	EXECHIGH <options>
>
>Involves a little more work (all of the last three would ned to be written,
>yes?) but I like it. Complete immediate detachment is a little neater than
>having to reconfigure your server to accomodate Linux workstations, perhaps.
>
>A further thought - won't that REQUIRE that you utilise a RAM disk, given
>that the last command is AFTER DETACHER?

Correct, unless you were to modify the EXECHIGH to do the detach, or
possibly EXECHIGH /BEFORE=DETACHER <options> to get rid of any type
of dependence on the boot image source.  There would be no need for a
ram drive if the DETACHER returned to EXECHIGH instead of the batch
file before EXECHIGH did it's stuff.  The RAM disk requirement is the
DOS COMMAND.COM doing it's interpreter work on batch files as a disk
based interpreter instead of loading them in core.

>There most definitely is a 3 connection limit. Try the following:
[ ...about a 3 connection limit for Native 3.11 get nearest server
  requests, *NOT* attached but unlogged-in connections... ]
>I am confident that this 3 remote boot session limit exists.

I haven't been able to duplicate this locally on NetWare for UNIX; I'll
forward it to the Native NetWare support group in Provo; since some of the
machines in the superlab remote boot, I'd think this would be caught if it
weren't a configuration issue.  You may want to check out your configuration
options dealing with "get nearest server" requests rather than those
dealing with booting or connections... in any case, the remote boot
attach process is the same as that used by netx or equivalent, as can be
verified with a lanalyzer.


					Terry Lambert
					terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------