| 1 |
<HTML> |
| 2 |
<HEAD> |
| 3 |
<TITLE>Using SheepShaver</TITLE> |
| 4 |
</HEAD> |
| 5 |
<BODY BGCOLOR=#FFFFFF> |
| 6 |
|
| 7 |
<H1>Using SheepShaver</H1> |
| 8 |
|
| 9 |
<H2>Changing the display mode</H2> |
| 10 |
|
| 11 |
SheepShaver can display the MacOS user interface in an X11 window or full-screen |
| 12 |
(much faster). You select the display mode as usual under MacOS in the "Monitors" |
| 13 |
control panel (under System 7.x, click on "Options"). The "75Hz" modes are full-screen |
| 14 |
modes, the "60Hz" modes are window modes (this doesn't mean that the video refresh |
| 15 |
rate is 75 or 60Hz in the respective modes; the rate displayed has no meaning; it's |
| 16 |
simply there to distinguish full screen modes from window modes). |
| 17 |
|
| 18 |
<H2>Full-screen mode</H2> |
| 19 |
|
| 20 |
The full-screen mode uses the whole X11 screen for displaying the MacOS user interface. |
| 21 |
You can temporarily switch back to the X11 desktop by pressing Ctrl-Tab. The MacOS (and |
| 22 |
all MacOS applications) will now be suspended. You can resume SheepShaver by activating |
| 23 |
the "SheepShaver suspended" window and pressing the space key. Using full-screen mode |
| 24 |
requires a DGA capable X server. |
| 25 |
|
| 26 |
<H2>Networking</H2> |
| 27 |
|
| 28 |
There are three approaches to networking with SheepShaver: |
| 29 |
|
| 30 |
<OL> |
| 31 |
<LI>Direct access to an Ethernet card via the "sheep_net" driver. |
| 32 |
In this case, the "ethernet card description" must be the name |
| 33 |
of a real Ethernet card, e.g. "eth0". It also requires the "sheep_net" |
| 34 |
driver to be installed and accessible. This approach will allow you |
| 35 |
to run all networking protocols under MacOS (TCP/IP, AppleTalk, IPX |
| 36 |
etc.) but there is no connection between Linux networking and MacOS |
| 37 |
networking. MacOS will only be able to talk to other machines on |
| 38 |
the Ethernet, but not to other networks that your Linux box routes |
| 39 |
(e.g. a second Ethernet or a PPP connection to the Internet). |
| 40 |
|
| 41 |
<LI>Putting SheepShaver on a virtual Ethernet via the "ethertap" device. |
| 42 |
In this case, the "ethernet card description" must be the name |
| 43 |
of an ethertap interface, e.g. "tap0". It also requires that you |
| 44 |
configure your kernel to enable routing and the ethertap device: |
| 45 |
under "Networking options", enable "Kernel/User netlink socket" and |
| 46 |
"Netlink device emulation", under "Network device support", activate |
| 47 |
"Ethertap network tap". You also have to modify <CODE>devices/net/ethertap.c</CODE> |
| 48 |
a bit before compiling the new kernel: |
| 49 |
|
| 50 |
<UL> |
| 51 |
<LI>insert <CODE>#define CONFIG_ETHERTAP_MC 1</CODE> near the top (after the <CODE>#include</CODE> lines) |
| 52 |
<LI>comment out the line <CODE>dev->flags|=IFF_NOARP;</CODE> in <CODE>ethertap_probe()</CODE> |
| 53 |
</UL> |
| 54 |
|
| 55 |
<P> |
| 56 |
Next, see <CODE>/usr/src/linux/Documentation/networking/ethertap.txt</CODE> for |
| 57 |
information on how to set up <CODE>/dev/tap*</CODE> device nodes and activate the |
| 58 |
ethertap interface. Under MacOS, select an IP address that is on the |
| 59 |
virtual network and set the default gateway to the IP address of the |
| 60 |
ethertap interface. This approach will let you access all networks |
| 61 |
that your Linux box has access to (especially, if your Linux box has |
| 62 |
a dial-up Internet connection and is configured for IP masquerading, |
| 63 |
you can access the Internet from MacOS). The drawback is that you |
| 64 |
can only use network protocols that Linux can route, so you have to |
| 65 |
install and configure netatalk if you want to use AppleTalk. Here is |
| 66 |
an example <CODE>/etc/atalk/atalkd.conf</CODE> for a LAN: |
| 67 |
|
| 68 |
<PRE> |
| 69 |
eth0 -seed -phase 2 -net 1 -addr 1.47 -zone "Ethernet" |
| 70 |
tap0 -seed -phase 2 -net 2 -addr 2.47 -zone "Sheepnet" |
| 71 |
</PRE> |
| 72 |
|
| 73 |
(the "47" is an arbitrary node number). This will set up a zone |
| 74 |
"Ethernet" (net 1) for the Ethernet and a zone "Sheepnet" (net 2) |
| 75 |
for the internal network connection of the ethertap interface. |
| 76 |
MacOS should automatically recognize the nets and zones upon startup. |
| 77 |
If you are in an existing AppleTalk network, you should contact |
| 78 |
your network administrator about the nets and zones you can use |
| 79 |
(instead of the ones given in the example above). |
| 80 |
|
| 81 |
<LI>Networking protocols for serial connections (PPP and SLIP, for example) |
| 82 |
can be used provided that you have the appropriate MacOS system components |
| 83 |
installed (e.g. Open Transport/PPP). |
| 84 |
</OL> |
| 85 |
|
| 86 |
<H2>Using floppy disks</H2> |
| 87 |
|
| 88 |
Floppy disks are not automatically detected when they are inserted. They have to be |
| 89 |
mounted explicitly: after inserting a floppy disk, press Ctrl-F1. |
| 90 |
|
| 91 |
<H2>Accessing Linux files</H2> |
| 92 |
|
| 93 |
SheepShaver will display a "Linux" disk icon on the Mac desktop that allows you |
| 94 |
to access any Linux files which are in the directory specified as "Linux Root" |
| 95 |
in the "Volumes" pane of the SheepShaver settings. You can open and save files on the |
| 96 |
"Linux" disk from Mac applications, copy, move or rename files from the Finder etc. |
| 97 |
SheepShaver translates some file name extensions to MacOS types and vice versa, |
| 98 |
so e.g. *.jpg and *.pdf files will show the correct icons in the Finder. MacOS |
| 99 |
resources and Finder attributes are stored in hidden <CODE>.rsrc</CODE> and |
| 100 |
<CODE>.finf</CODE> directories. |
| 101 |
|
| 102 |
<H2>Copying text via the clipboard</H2> |
| 103 |
|
| 104 |
SheepShaver tries to keep the Linux and MacOS clipboards synchronized. That means, |
| 105 |
when you copy a piece of text under Linux, you can paste it into a MacOS application |
| 106 |
and vice versa. |
| 107 |
|
| 108 |
<HR> |
| 109 |
<ADDRESS> |
| 110 |
SheepShaver User's Guide |
| 111 |
</ADDRESS> |
| 112 |
</BODY> |
| 113 |
</HTML> |
