LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2000-06-19 16:11:02 +00:00
parent c04182be4f
commit 188a096402
1 changed files with 350 additions and 164 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

514
LDP/howto/docbook/JavaStation-HOWTO.sgml
View File

@ -3,6 +3,12 @@
<!--
Here's the current source for the Linux on JavaStation HOWTO
Thanks for checking out the source.
Things to do:
1) All requests have been merged.
-->
<Article>
@ -24,12 +30,13 @@
<Ulink url="mailto://dubinski@mscs.mu.edu">dubinski@mscs.mu.edu</Ulink>
Is there any real valid way of adding an email address in the artheader
and still include both FirstName and SurName? And is there a MidName tag?
Email me and let me know.
-->
<Publisher>
<PublisherName>Linux Documentation Project</PublisherName>
</Publisher>
<PubDate>2000-Apr-25</PubDate>
<PubDate>2000-Jun-16</PubDate>
<Abstract>
@ -43,6 +50,7 @@ This is a HOWTO document describing how to enable the <Application><Acronym>GNU<
</ArtHeader>
<!-- Begin the document -->
@ -50,7 +58,7 @@ This is a HOWTO document describing how to enable the <Application><Acronym>GNU<
<Title>META Information</Title>
<Para>
This chapter lists the meta-information of this document. The
This section lists the meta-information of this document. The
hows, whys, location and changes to the structure of the document
are documented here. The main content begins in the next chapter.
</Para>
@ -88,7 +96,7 @@ techniques and files presented in this document.
</Para>
<Para>
In early 1999, Eric Brower <Email>ebrower@mscs.mu.edu</Email> wrote the
In early 1999, Eric Brower <Email>ebrower@usa.net</Email> wrote the
first informal HOWTO for the <ProductName>JavaStation</ProductName>. Parts
of this document are inspired by his work, and all unique information
presented there have since been merged into this document.
@ -208,14 +216,37 @@ The following people have contributed to this specific document:
(Proofreading and factual corrections of initial drafts)
</Para>
</ListItem>
<ListItem>
<Para>
Eric Brower <Email>ebrower@usa.net</Email>
(Proofreading and factual corrections of initial drafts)
</Para>
</ListItem>
<ListItem>
<Para>
Magdalena Wodzinska <Email>magdalena.wodzinska@marquette.edu</Email>
(Proofreading and document layout suggestions)
</Para>
</ListItem>
<ListItem>
<Para>
Richard Tomlinson <Email>Richard.Tomlinson@one2one.co.uk</Email>
(Document reader, Krups tester, feedback)
</Para>
</ListItem>
<ListItem>
<Para>
Michael R. Eckhoff <Email>foobar@null.net</Email>
(feedback on sample kernel)
</Para>
</ListItem>
</ItemizedList>
<Para>
If you contributed a tidbit of info and are not listed, please email
the document author to get yourself listed.
</Para>
</Sect2>
<Sect2 id="DocumentHistorySection">
@ -225,6 +256,30 @@ The following people have contributed to this specific document:
<RevHistory>
<Revision>
<RevNumber>1.05</RevNumber>
<Date>16 Jun 2000</Date>
<RevRemark>Requested Format Changes and Fixes</RevRemark>
</Revision>
<Revision>
<RevNumber>1.04</RevNumber>
<Date>13 Jun 2000</Date>
<RevRemark>Suggested Fixes and Added Requests</RevRemark>
</Revision>
<Revision>
<RevNumber>1.03</RevNumber>
<Date>04 May 2000</Date>
<RevRemark>Minor Fixes, Requests</RevRemark>
</Revision>
<Revision>
<RevNumber>1.02</RevNumber>
<Date>28 Apr 2000</Date>
<RevRemark>Small fixes.</RevRemark>
</Revision>
<Revision>
<RevNumber>1.01</RevNumber>
<Date>25 Apr 2000</Date>
@ -261,7 +316,7 @@ The following people have contributed to this specific document:
<Revision>
<RevNumber>0.7</RevNumber>
<Date>14 Apr 2000</Date>
<RevRemark>Linked on Pete Zaitcev's Website.
<RevRemark>Linked on Metabyte Website.
</RevRemark>
</Revision>
@ -547,7 +602,7 @@ of the Java <Acronym>NC</Acronym> design.
Hardware-wise, the <ProductName>JavaStation-1</ProductName> is a
Sun4M architecture machine. It is based on the <ProductName>SPARCStation-4
</ProductName> design, with some deletions and <Acronym>PC</Acronym>-like
modifications. It is powered by a <Hardware>100 Mhz MicroSPARC IIe
modifications. It is powered by a <Hardware>110 Mhz MicroSPARC IIe
CPU</Hardware> and has no <Hardware>SCSI</Hardware>, <Hardware>internal disks
</Hardware>, <Hardware>floppy</Hardware>, <Hardware>CD</Hardware> or
<Hardware>expansion slots</Hardware>. The <ProductName>Mr. Coffee
@ -611,8 +666,8 @@ anticipation for its <Quote>real</Quote> <ProductName>JavaStation
<Para>
See the <ProductName>JavaStation-1</ProductName> at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_front_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_front_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_front_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_front_view.jpg
</Ulink>
</Para>
@ -647,7 +702,7 @@ the characteristic <ProductName>JavaStation</ProductName> architecture.
<Para>
<ProductName>Krups</ProductName> is powered by a
<Hardware>110Mhz MicroSPARC IIep</Hardware> chip, (note the 'p').
<Hardware>100Mhz MicroSPARC IIep</Hardware> chip, (note the 'p').
Its mainboard had the internal addition of a <Hardware>PCI bus</Hardware>,
about a year before this standard bus made its well-publicized
appearance on the <ProductName>Sun Ultra</ProductName> workstation
@ -671,8 +726,8 @@ time between generations one and two of the <ProductName>JavaStation
</ProductName> line, so it was fitting for Sun to switch to
it in anticipation of their status low-cost commodity memory chips. The
<Hardware>DIMMs</Hardware> accepted by the <Quote>tower</Quote> are
<Hardware>168pin, 3.3V unbuffered DIMMs</Hardware>. With two sockets
capable of holding a <Hardware>32MB DIMM</Hardware> each, the
<Hardware>168pin, 3.3V unbuffered EDO DIMMs (not SDRAM)</Hardware>. With
two sockets capable of holding a <Hardware>32MB DIMM</Hardware> each, the
<ProductName>Krups</ProductName> has a maximum capacity of 64<Acronym>MB
</Acronym> <Acronym>RAM</Acronym>. As with the <ProductName>JavaStation-1
</ProductName>, the number <Quote>xx</Quote> in the Sun option number
@ -703,7 +758,7 @@ The <Quote>tower</Quote> came with the <Hardware>9-pin serial port
<Para>
Another addition in the <ProductName>JavaStation-NC</ProductName> is a
<Hardware>flash memory chip</Hardware>. This allows one to load the
<Hardware>flash memory SIMM</Hardware>. This allows one to load the
current revision of the <Acronym>OS</Acronym> onboard, increasing
boot-speed tremendously.
</Para>
@ -741,8 +796,8 @@ product line.
<Para>
See the <ProductName>JavaStation-NC</ProductName> at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_front_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_front_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_front_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_front_view.jpg
</Ulink>
</Para>
@ -793,9 +848,8 @@ Mr. Coffee</ProductName> and <ProductName>Krups</ProductName>.
<Para>
<ProductName>Espresso</ProductName> uses the same <Hardware>168-pin,
3.3V unbuffered DIMMs</Hardware> as <ProductName>Krups</ProductName>.
The maximum allowed is not known at the time of this document's writing.
<!--<Comment>(ed note: verify)</Comment>-->
3.3V unbuffered EDO DIMMs</Hardware> as <ProductName>Krups</ProductName>.
The maximum amount of memory for Espresso is reported to be 96MB.
As with the <ProductName>Mr. Coffee</ProductName> and <ProductName>Krups
</ProductName>, the number <Quote>xx</Quote> in the Sun option number
refers to the amount of memory shipped with the unit.
@ -840,17 +894,17 @@ mass-production.
</Para>
<Para>
Pete Zaitcev <Email>zaitcev@metabyte.com</Email> currently uses his
<ProductName>Espresso</ProductName> as both a server and router, with
the addition of an <Hardware>IDE disk</Hardware> and <Hardware>3C905 ethenet
card</Hardware>, demonstrating the expandability of this unit.
One <ProductName>Espresso</ProductName> user mentioned he now uses
his unit as both a server and router, with the addition of an
<Hardware>IDE disk</Hardware> and <Hardware>3C905 ethenet card</Hardware>,
demonstrating the expandability of this unit.
</Para>
<Para>
See the <ProductName>JavaStation-E</ProductName> at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_front_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_front_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_front_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_front_view.jpg
</Ulink>
</Para>
@ -868,8 +922,8 @@ rare find.
<Para>
This unit is supposed to be of similar board design to the Krups, but in
an ATX form factor, without flash memory, and with a regular SVGA video
chipset.
an ATX form factor, with soldered onboard flash memory, and with a
regular SVGA video chipset.
</Para>
<Para>
@ -889,8 +943,8 @@ submissions from the public are welcome.
<Para>
See the <ProductName>JavaEngine-1</ProductName> at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/je1_overhead_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/je1_overhead_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/je1_overhead_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/je1_overhead_view.jpg
</Ulink>
</Para>
@ -972,6 +1026,27 @@ It is included here though, for the sake of completeness.
</Sect3>
<Sect3 id="JavaStationProtoDescSection">
<Title>
The Early JavaStation Prototype?
</Title>
<Para>
After the original publishing of this HOWTO, word of one more
"JavaStation" model has surfaced. John of bodoman.com, a reseller
of JavaStation equipment, chimed in that he has a motherboard of a
pre-JavaStation machine. The board used a 68040 CPU. Apparently
the company that produced it was bought out by Sun and its
design became a basis for the JavaStation line.
</Para>
<Para>
As this is the first mention of this prototype machine, any further
info is appreciated.
</Para>
</Sect3>
</Sect2>
@ -982,9 +1057,8 @@ It is included here though, for the sake of completeness.
<Para>
It turns out that <Application>Linux</Application> makes the
<ProductName>JavaStations</ProductName> perform more than adequately
on the desktop. Thanks to the kernel work of Pete Zaitcev
<Email>zaitcev@metabyte.com</Email> with mods and documentation
contributed by others, the <ProductName>JavaStations</ProductName>
on the desktop. Thanks to the dedicated work of the Linux
developer community, the <ProductName>JavaStations</ProductName>
offer users the low-cost, zero-admin, versatile desktop
<Acronym>NC</Acronym>'s they were originally billed to be, but with
the added freedom granted by the <Application>Linux OS</Application>.
@ -1036,10 +1110,8 @@ should not be directly compared to today's workstation offerings.
<ListItem>
<Para>
A router and server, as Pete Zaitcev <Email>zaitcev@metabyte.com</Email>
demonstrates as possible with his <ProductName>Espresso</ProductName>
model <ProductName>JavaStation</ProductName> decked out with <Hardware>
IDE disk</Hardware> and <Hardware>ethernet card</Hardware>.
A small router and server, particularly with the <ProductName>Espresso
</ProductName> model decked out with added IDE disks and NIC.
</Para>
</ListItem>
</ItemizedList>
@ -1096,12 +1168,13 @@ computing device itself), there is no explanation why the two do not co-exist.
</Para>
<Para>
In talking to the users of the <ProductName>JavaStations</ProductName>, you
will find strong opinions as to why the <ProductName>JavaStations
</ProductName> are no more. The common thread in almost all opinions
collected is that the software provided by Sun was inadequete for
a production environment. Here are collected opinions from users of the
Sun-provided software, included with their permission:
In talking to the users of the <ProductName>JavaStations</ProductName>
in the pre-Linux era, you will find strong opinions as to why
the <ProductName>JavaStations</ProductName> are no more. The common
thread in almost all opinions collected is that the software provided
by Sun was inadequete for a production environment. Here are
collected opinions from users of the Sun-provided software, included
with their permission:
</Para>
<BlockQuote>
@ -1324,19 +1397,22 @@ handful from Sun as demo units are now trying to offload them any way
they can. Search around the auction sites like Ebay and Yahoo Auctions,
and you should be able to turn some up.
</Para>
<Para>
Lastly, a great resource for <ProductName>JavaStations</ProductName> is
<Quote>Bodoman's JavaStation site</Quote> at:
<ULink url="http://www.bodoman.com/javastation/javastation.html">
http://www.bodoman.com/javastation/javastation.html</ULink>
. Here you can find <ProductName>Mr. Coffee</ProductName> and
<ProductName>Krups</ProductName> models.
<ProductName>Krups</ProductName> models. As of June 15th 2000, Bodoman
was selling out of Krups models and was thinking about selling all
remaining Mr. Coffees to a different reseller. If you want a JavaStation
from BodoMan, contact him now!
</Para>
<Para>
The current going price as of May 2000 for a <ProductName>Mr. Coffee
</ProductName> model without memory or monitor is about $70-100US, while
The current going price as of June 2000 for a <ProductName>Mr. Coffee
</ProductName> model without memory or monitor is about $50-100US, while
the <ProductName>Krups</ProductName> goes for about $85-100US. Anything
more is typically due to memory pre-installed. Since the Taiwanese
earthquake of 1999, memory prices have fluctuated on a near daily basis,
@ -1345,9 +1421,8 @@ making it difficult to pin a price range down in this manner.
<Para>
You might also get lucky and stumble on someone who wants to get rid of
<ProductName>JavaStations</ProductName> cheap. Pete Zaitcev <Email>
zaitcev@metabyte.com</Email> purchased a <Hardware>32-MB Krups</Hardware>
for $75US in a pristine unopened box.
<ProductName>JavaStations</ProductName> cheap. One reader reported
finding a 32-MB Krups for $75 in a pristine unopened box.
</Para>
</Sect2>
@ -1515,9 +1590,8 @@ software environment to 3.11. <ProductName>Krups</ProductName> and
<Para>
It turns out the later 3.x series of <Acronym>PROMs</Acronym> is not
conducive to booting <Application>Linux</Application> upon.
Fortunately, kernel hacker Pete Zaitcev <Email>zaitcev@metabyte.com</Email>
wrote a complete <Acronym>PROM</Acronym> replacement called <Application>PROLL
</Application>.
Fortunately, a complete <Acronym>PROM</Acronym> replacement
called <Application>PROLL</Application> now exists to get by this limitation.
</Para>
<Para>
@ -1534,21 +1608,21 @@ PROLL</Application>. This can make troubleshooting new installs easier.
<Para>
The current, master version of <Application>PROLL</Application> is available
from Pete Zaitcev's website at:
from the Metabyte website at:
<ULink url="http://www.metabyte.com/~zaitcev/linux/">
http://www.metabyte.com/~zaitcev/linux</ULink>.
</Para>
<Para>
The current version at the time of this writing is <Quote>11</Quote>.
The current version at the time of this writing is <Quote>13</Quote>.
</Para>
<Para>
<Application>PROLL</Application> can also be found mirrored on <Quote>VGER
</Quote>, and also on this HOWTO's distribution site at:
<ULink url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/proll_11.tar.gz">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/proll_11.tar.gz</ULink>
(HOWTO website mirror)".
<ULink url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/proll_13.tar.bz2">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/proll_13.tar.bz2</ULink>
(HOWTO website mirror - version 13)
</Para>
</Sect2>
@ -1615,6 +1689,21 @@ configuration. When you have things stabilized, move to
</Sect2>
<Sect2 id="SupportSitesSection">
<Title>Support Sites to Check Out: Metabyte</Title>
<Para>
One website to keep on reference when you begin thinking about
putting Linux on your JavaStation is Pete Zaitcev's website at:
<ULink url="http://www.metabyte.com/~zaitcev/linux">
http://www.metabyte.com/~zaitcev/linux</ULink>, referenced
throughout this document as the <Quote>Metabyte server</Quote>.
Here you will find the latest version of PROLL and many low-level
details about dealing with the JavaStations.
</Para>
</Sect2>
</Sect1>
@ -1856,8 +1945,8 @@ If you can not do this, the patch below makes the edit for you.
<Para>
4MB to 16MB kernel patch file is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/ramdisk_patch">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/ramdisk_patch
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/ramdisk_patch">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/ramdisk_patch
</Ulink>
</Para>
@ -1915,8 +2004,8 @@ to get confused with when you have multiple boot kernel images down the road.
</Sect2>
<Sect2 id="KernelSamplesSection">
<Title><ProductName>JavaStation</ProductName>-Ready Kernel Images and
<Quote>.config</Quote> File Samples</Title>
<Title><ProductName>JavaStation</ProductName>-Ready Kernel Images,
System.map and <Quote>.config</Quote> File Samples</Title>
<Para>
Here are some sample <Quote>.config</Quote> and <ProductName>JavaStation
@ -1930,14 +2019,14 @@ Here are some sample <Quote>.config</Quote> and <ProductName>JavaStation
<Para>
<Ulink
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/kernel_config_2_3_99_pre3_mar_17" >
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/kernel_config_2_3_99_pre3_mar_17</ULink>
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/kernel_embedded_config_2_3_99pre3_mar_17" >
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/kernel_embedded_config_2_3_99pre3_mar_17</ULink>
</Para>
<Para>
This is a <Quote>.config</Quote> file donated by Robert Dubinski
<Email>dubinski@mscs.mu.edu</Email>. It was used at Marquette
University to build a boot image from the Mar. 17, 2000 CVS kernel
University to build an embedded boot image from the Mar. 17, 2000 CVS kernel
version. This includes support for both <ProductName>Mr. Coffee</ProductName>
and <ProductName>Krups</ProductName> in an <Quote>Embedded-Root</Quote>
filesystem configuration. These options should be valid for newer kernels
@ -1945,6 +2034,16 @@ as well; Perform a <UserInput>make oldconfig</UserInput> when using with
latter kernels.
</Para>
<Para>
<Ulink
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/kernel_nfsroot_config_2_3_99pre3_mar_17" >
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/kernel_nfsroot_config_2_3_99pre3_mar_17</ULink>
</Para>
<Para>
This is an nfs-root capable version of the above <Quote>.config</Quote> file.
</Para>
</Sect3>
<Sect3 id="KernelFileSamplesSection">
@ -1953,8 +2052,8 @@ Files</Title>
<Para>
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/vmlinux_2_3_99pre3_mar_17" >
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/vmlinux_2_3_99pre3_mar_17
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/vmlinux_embedded_2_3_99pre3_mar_17" >
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/vmlinux_embedded_2_3_99pre3_mar_17
</ULink>
</Para>
@ -1975,14 +2074,45 @@ This boot kernel image has already been converted to the required
<Acronym>AOUT</Acronym> executable format.
</Para>
</Sect3>
<Para>
<ULink
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/vmlinux_nfsroot_2_3_99pre3_mar_17" >
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/vmlinux_nfsroot_2_3_99pre3_mar_17
</ULink>
</Para>
<Para>
This is the nfs-root version of the above kernel.
</Para>
<Para>
<ULink
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/system.map_embedded_2_3_99pre3_mar_17" >
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/system.map_embedded_2_3_99pre3_mar_17
</ULink>
</Para>
<Para>
The System.map for the embedded kernel image.
</Para>
<Para>
<ULink
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/system.map_nfsroot_2_3_99pre3_mar_17" >
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/system.map_nfsroot_2_3_99pre3_mar_17
</ULink>
</Para>
<Para>
The System.map for the nfsroot kernel image.
</Para>
</Sect3>
</Sect2>
</Sect1>
<Sect1 id="BuildFileSystemChapter">
<Title>Build A <ProductName>JavaStation</ProductName>-Ready FileSystem</Title>
@ -2319,8 +2449,8 @@ Here are some sample filesystems for you to start with.
A filesystem image contributed by Varol Kapton <Email>varol@ulakbim.gov.tr
</Email> is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/jsroot_varol.tar.gz">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/jsroot_varol.tar.gz
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/jsroot_varol.tar.gz">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/jsroot_varol.tar.gz
</Ulink>
</Para>
@ -2460,7 +2590,9 @@ DHCPD Version 2.0 and above</Application>.
</Para>
<Para>
Pete Zaitcev sent a longer <ULink url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/petes_dhcpd.conf.txt">dhcpd.conf</Ulink> for demonstration purposes.
A longer
<ULink url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/petes_dhcpd.conf.txt">dhcpd.conf</Ulink> from the Metabyte server is mirrored here for
demonstration purposes.
</Para>
</Sect2>
@ -2584,6 +2716,27 @@ shoulder, hunting black cats and sacrificing chickens (KFC will suffice).
</Sect2>
<Sect2 id="BootVisualsSection">
<Title>What to See When Booting Linux</Title>
<Para>
When you boot things properly, your JavaStation will start up with
the normal white background screen with the PROM banner at the top,
and you will get the black "exclamation mark in triangle" logo,
signalling the system doesn't yet know who it is. When contact is
made with the DHCP server, the logo goes away and changes to the
Java coffee cup logo. After this, a black background window opens.
This is the PROLL window. It'll show status of the TFTP download in
progress, and give stats on the size of the file downloaded. Next,
the whole screen should go black, you should see a picture of Tux the
penguin in the upper left hand of the screen, and have the
normal Linux kernel messages printed before you. Any mistakes from
this point are due to the filesystem you are using, the filesystem
mounting, or missing kernel drivers which should have been compiled
in.
</Para>
</Sect2>
</Sect1>
@ -2602,11 +2755,38 @@ infrequently encountered problems in enabling <Application>Linux
</Title>
<Para>
This symptom likely means you forgot to run <UserInput>elftoaout</UserInput>
on your kernel image.
On systems that have the older OpenBoot version 2.3, and are not set
up to use PROLL, you will get this message when attempting to boot
up a kernel image that is not in AOUT format. Be sure to run
<UserInput>elftoaout</UserInput> on your kernel image.
</Para>
</Sect2>
<Sect2 id="NoMagicTSSection">
<Title>When booting, the message <Quote>no a.out magic</Quote> appears
and halts the boot. Why?
</Title>
<Para>
On systems that are set up to use PROLL, you will see this message
when attempting to boot up a kernel image that is not in AOUT format.
Be sure to run <UserInput>elftoaout</UserInput> on your kernel image.
</Para>
</Sect2>
<Sect2 id="FlashTSSection">
<Title>I tried booting a Krups but JavaOS comes up. I don't even have JavaOS!
</Title>
<Para>
This likely means you have a copy of JavaOS loaded on your flash SIMM.
Remove the SIMM and the problem should go away.
</Para>
</Sect2>
<Sect2 id="TenMBLimitTSSection">
<Title>Cannot Boot an <Quote>Embedded-Root</Quote> image &gt; 10 <Acronym>MB
</Acronym>on my <ProductName>JavaStation</ProductName>. Why?</Title>
@ -2624,9 +2804,8 @@ added to it.
</Para>
<Para>
Pete Zaitcev <Email>zaitcev@metabyte.com</Email>, author of <Application>
PROLL</Application> answers this can be fixed if needed by someone, as
the source to <Application>PROLL</Application> has been released under the
This limit can be fixed if needed by someone, as the source
to <Application>PROLL</Application> has been released under the
General Public License <Acronym>GPL</Acronym>.
</Para>
@ -2687,47 +2866,66 @@ to this problem.
<Sect2 id="XDMCPTSSection">
<Title>Performing Indirect <Acronym>XDMCP</Acronym> to a <Application>
Solaris</Application> Server Results in Session Login Failures. Why?
Solaris</Application> Server Results in Session Login Failures. Why?
</Title>
<Para>
Congratulations! You must have one of patch numbers 107180-12 through
107180-19 installed on a <Application>Solaris 7</Application>
server. You need to upgrade to 107180-20 or above to fix this problem.
Congratulations! You must have one of patch numbers 107180-12 through
107180-19 installed on a <Application>Solaris 7</Application>
server. You need to upgrade to 107180-20 or above to fix this problem.
</Para>
<BlockQuote>
<Attribution>Robert Dubinski, Computer Systems Technician at Marquette
<Attribution>Robert Dubinski, Computer Systems Technician at Marquette
University
<Email>tech@mscs.mu.edu</Email>
</Attribution>
<Para>
Here's a little rant:
</Para>
<Para>
I reported this problem to Sun in November 1999, at which time I was
told a fix was not scheduled to be made, since I was using an
<Quote>unsupported configuration.</Quote>. Never mind the client
was a piece of hardware made by Sun itself. Also never mind that
indirect <Acronym>XDMCP</Acronym> queries is a standard itself which
I reported this problem to Sun in November 1999, at which time I was
told a fix was not scheduled to be made, since I was using an
<Quote>unsupported configuration.</Quote>. Never mind the client
was a piece of hardware made by Sun itself. Also never mind that
indirect <Acronym>XDMCP</Acronym> queries is a standard itself which
was broken by Sun. A call back in late January 2000, and I learn that
the record of my previous call was non-existant, but a fix was now on
the record of my previous call was non-existant, but a fix was now on
its way. The fix finally was made available in April 2000, five months
after first reporting the problem. Considering revisions to this
patch during the broken <Acronym>XDMCP</Acronym> period dealt with
fixing system security issues, we were forced to run the older insecure
software for five months while waiting for a fix to a problem which
after first reporting the problem. Considering revisions to this
patch during the broken <Acronym>XDMCP</Acronym> period dealt with
fixing system security issues, we were forced to run the older insecure
software for five months while waiting for a fix to a problem which
should have been patched immediately.
</Para>
<Para>
The moral of the story: test your <ProductName>JavaStation</ProductName>
The moral of the story: test your <ProductName>JavaStation</ProductName>
configuration against an upgraded server that is not in production mode.
</Para>
</BlockQuote>
</Sect2>
<Sect2 id="SUSETftpTSSection">
<Title>TFTPd config doesn't work on SUSE. Why?</Title>
<Para>
This was reported by a user after this document was first released.
</Para>
<Para>
In SUSE 6.3, using the tftpd from the 'a' package of the netkit rpm,
you must be sure your tftpd line in /etc/inetd.conf has the -s flag.
Otherwise you need to specify a full path.
</Para>
<Para>
Also, it is not necessary to run tftpd as root, so the suggested username
and group for tftpd on SUSE 6.3 is 'nobody' and 'nogroup'
</Para>
</Sect2>
</Sect1>
<Sect1 id="MiscAnswersChapter">
@ -2753,15 +2951,14 @@ however.
<Para>
This document explains how to set up kernel-level <Acronym>RARP</Acronym>
for the remaining models. In kernel versions 2.3.x/2.4.x, kernel-level
<Acronym>RARP</Acronym> support is removed. Pete Zaitcev
<Email>zaitcev@metabyte.com</Email> has made a patch to <Application>
ANK userland RARP</Application> that allows it to compile on Linux/SPARC.
It is available from:
<ULink url="ftp://corp.metabyte.com/private/linux_roxy/tools/">
ftp://corp.metabyte.com/private/linux_roxy/tools/"</Ulink>. The command
to use then is <UserInput>rarpd-ank -e eth0</UserInput>. <Quote>-e</Quote>
makes it ignore /tftpboot checking, and <Quote>eth0</Quote> is needed if
you are behind a firewall.
<Acronym>RARP</Acronym> support is removed. The Metabyte server
holds a version of <Application> ANK userland RARP</Application> from
Andi Klein of SuSE that will work with Linux/SPARC. It is available
from: <ULink url="http://corp.metabyte.com/~zaitcev/linux/rarpd-ap1.tar.bz2">
http://corp.metabyte.com/~zaitcev/linux/rarpd-ap1.tar.bz2</Ulink>.
The command to use then is <UserInput>rarpd-ank -e eth0</UserInput>.
<Quote>-e</Quote> makes it ignore /tftpboot checking, and
<Quote>eth0</Quote> is needed if you are behind a firewall.
</Para>
</Sect2>
@ -2809,7 +3006,7 @@ Next, fill in your /var/dhcp/dhcptab file with entries similar to:
# First, some network info
#
Locale m :UTCoffst=21600:
studsys m :Include=Locale:Timeserv=192.168.128.100:DNSdmain=my.own.net:DNSserv=192.168.128.100:
www m :Include=Locale:Timeserv=192.168.128.100:DNSdmain=my.own.net:DNSserv=192.168.128.100:
192.168.128.0 m :Broadcst=192.168.128.255:Subnet=255.255.255.0:MTU=1500:BootSrvA=192.168.128.100:Router=192.168.128.101:NISdmain=my.own.net:NISservs=192.168.128.100:
#
# note: BootServA can point to a different TFTP server to get the kernel image
@ -2819,8 +3016,8 @@ studsys m :Include=Locale:Timeserv=192.168.128.100:DNSdmain=my.own.net:DNSserv
##
# Now we define the JavaStation TFTPboot parameters
#
SUNW.Linux m :Include=studsys:JOSchksm=0x155dbf97:Rootpath=/tftpboot:BootFile=proll.mrcoffee:BootSrvA=192.168.128.100:TFTPsrvN=lnxserv:
SUNW.Linux.Krups m :Include=studsys:Rootpath=/tftpboot:BootFile=proll.krups:BootSrvA=192.168.128.100:TFTPsrvN=lnxserv:
SUNW.Linux m :Include=www:JOSchksm=0x155dbf97:Rootpath=/tftpboot:BootFile=proll.mrcoffee:BootSrvA=192.168.128.100:TFTPsrvN=lnxserv:
SUNW.Linux.Krups m :Include=www:Rootpath=/tftpboot:BootFile=proll.krups:BootSrvA=192.168.128.100:TFTPsrvN=lnxserv:
#
#
# note: different classes are defined for the different PROLL images.
@ -2889,16 +3086,16 @@ JavaStations</ProductName>.
<Para>
Sample XFree Sun Frambuffer X Server File is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/XF86_FBDev">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/XF86_FBDev
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/XF86_FBDev">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/XF86_FBDev
</Ulink>
</Para>
<Para>
Sample XFree JavaStation-Ready XF86Config File is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/XF86Config">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/XF86Config
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/XF86Config">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/XF86Config
</Ulink>
</Para>
@ -2931,34 +3128,12 @@ w=2">http://www.progressive-comp.com/Lists/?l=linux-sparc&amp;r=1&amp;w=2"
</Sect2>
<Sect2 id="AlternateHelpSitesFAQSection">
<Title>Are There Alternate Help Sources Available?</Title>
<Sect2 id="FlashBootFAQSection">
<Title>Can One Boot a JavaStation from Onboard Flash Memory?</Title>
<Para>
There are a few known sources of <Application>Linux</Application>
on <ProductName>JavaStation</ProductName> help outside of this HOWTO
and the <Application>Linux/Sparc</Application> mailing list.
</Para>
<OrderedList>
<ListItem>
<Para>
Pete Zaitcev <Email>zaitcev@metabyte.com</Email> was the driving force
in programming the <Application>Linux kernel</Application> support for
the <ProductName>JavaStation</ProductName> line. He maintains a
website of low-level hardware details at
<ULink url="http://corp.metabyte.com/~zaitcev/linux">
http://corp.metabyte.com/~zaitcev/linux</ULink>.
Here you will find all kinds of little source patches, though none presented
are necessary for basic <ProductName>JavaStation</ProductName> support
as described in this document.
</Para>
</ListItem>
</OrderedList>
<Para>
Additional sources of information will be added as they appear.
It is possible to boot a JavaStation-NC from flash, but requires
too much arcane knowledge at the moment to be recommended.
</Para>
</Sect2>
@ -2998,6 +3173,17 @@ too?
</Sect2>
<Sect2 id="FlashUseUnanswered">
<Title>What can one use the Krups Flash memory for?</Title>
<Para>
Though it is not supported without some experimental patches from
Metabyte, the question arises as to what uses one might put the
flash to use for, aside from booting?
</Para>
</Sect2>
</Sect1>
@ -3066,120 +3252,120 @@ This section contains links to pictures of the JavaStation line.
<Para>
Front view of Mr. Coffee is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_front_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_front_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_front_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_front_view.jpg
</Ulink>
</Para>
<Para>
Top view of Mr. Coffee is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_top_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_top_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_top_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_top_view.jpg
</Ulink>
</Para>
<Para>
Inside view of Mr. Coffee is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_inside_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_inside_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_inside_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_inside_view.jpg
</Ulink>
</Para>
<Para>
Mr. Coffee white case variation #1 at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_white_case_1.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_white_case_1.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_white_case_1.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_white_case_1.jpg
</Ulink>
</Para>
<Para>
Mr. Coffee white case variation #2 at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_white_case_2.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_white_case_2.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_white_case_2.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/mr_coffee_white_case_2.jpg
</Ulink>
</Para>
<Para>
Front view of krups is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_front_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_front_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_front_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_front_view.jpg
</Ulink>
</Para>
<Para>
Side view of krups is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_side_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_side_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_side_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_side_view.jpg
</Ulink>
</Para>
<Para>
Top view of krups is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_top_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_top_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_top_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/krups_top_view.jpg
</Ulink>
</Para>
<Para>
Front view of Espresso is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_front_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_front_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_front_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_front_view.jpg
</Ulink>
</Para>
<Para>
Side view of Espresso is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_side_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_side_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_side_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_side_view.jpg
</Ulink>
</Para>
<Para>
Rear view of Espresso is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_rear_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_rear_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_rear_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_rear_view.jpg
</Ulink>
</Para>
<Para>
Inside view of Espresso is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_inside_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_inside_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_inside_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/espresso_inside_view.jpg
</Ulink>
</Para>
<Para>
See the <ProductName>JavaEngine-1</ProductName> at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/je1_overhead_view.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/je1_overhead_view.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/je1_overhead_view.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/je1_overhead_view.jpg
</Ulink>
</Para>
<Para>
View of the JavaStation mousepad is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/javastation_mousepad.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/javastation_mousepad.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/javastation_mousepad.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/javastation_mousepad.jpg
</Ulink>
</Para>
<Para>
View of a Lab of JavaStations running Linux is at:
<ULink
url="http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/lab_of_javastations.jpg">
http://studsys.mscs.mu.edu/~tech/Linux_on_JS/Files/lab_of_javastations.jpg
url="http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/lab_of_javastations.jpg">
http://www.mscs.mu.edu/~tech/Linux_on_JS/Files/lab_of_javastations.jpg
</Ulink>
</Para>