102 lines
3.2 KiB
HTML
102 lines
3.2 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
|||
|
<HTML>
|
|||
|
<HEAD>
|
|||
|
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
|||
|
<TITLE>Linux+Solaris HOWTO: Preparing Linux</TITLE>
|
|||
|
<LINK HREF="Linux+Solaris-4.html" REL=next>
|
|||
|
<LINK HREF="Linux+Solaris-2.html" REL=previous>
|
|||
|
<LINK HREF="Linux+Solaris.html#toc3" REL=contents>
|
|||
|
</HEAD>
|
|||
|
<BODY>
|
|||
|
<A HREF="Linux+Solaris-4.html">Next</A>
|
|||
|
<A HREF="Linux+Solaris-2.html">Previous</A>
|
|||
|
<A HREF="Linux+Solaris.html#toc3">Contents</A>
|
|||
|
<HR>
|
|||
|
<H2><A NAME="s3">3. Preparing Linux</A></H2>
|
|||
|
|
|||
|
<H2><A NAME="kernel"></A> <A NAME="ss3.1">3.1 Building a new kernel</A>
|
|||
|
</H2>
|
|||
|
|
|||
|
<P>Some people don<6F>t like building a custom kernel. For those of you:
|
|||
|
you <EM>must</EM> build your own kernel if you want to share data
|
|||
|
between Solaris and Linux on one hard disk. If, however, you do not
|
|||
|
want to share data, you are safe with your old kernel.
|
|||
|
<P>Here are your kernel options for ``Solaris compatibility'':
|
|||
|
<UL>
|
|||
|
<LI>Under <CODE>code maturity</CODE>:
|
|||
|
<DL>
|
|||
|
<DT><B><CODE>Prompt for development drivers</CODE></B><DD><P>Unfortunately UFS writing is still experimental.
|
|||
|
</DL>
|
|||
|
</LI>
|
|||
|
<LI>In <CODE>file systems</CODE>:
|
|||
|
<DL>
|
|||
|
<DT><B><CODE>UFS file system support</CODE></B><DD><P>UFS is
|
|||
|
the Solaris file system
|
|||
|
<DT><B><CODE>UFS file system
|
|||
|
write support</CODE></B><DD><P>The only way to pass data
|
|||
|
to Solaris
|
|||
|
<DT><B><CODE>partition types / Solaris
|
|||
|
(x86) partition table support</CODE></B><DD><P>Is needed
|
|||
|
for the slices within your Solaris partition to be
|
|||
|
found.
|
|||
|
</DL>
|
|||
|
</LI>
|
|||
|
</UL>
|
|||
|
|
|||
|
Additional info about kernel building can be found in the
|
|||
|
Kernel-HOWTO
|
|||
|
<H2><A NAME="ss3.2">3.2 Preparing your boot loader</A>
|
|||
|
</H2>
|
|||
|
|
|||
|
<P><EM>Before
|
|||
|
messing with your boot loader, please make sure that you have
|
|||
|
an emergency disk ready which enables you to boot your old
|
|||
|
system.</EM>
|
|||
|
<P>Unfortunately the Solaris install
|
|||
|
overwrites the master boot record (MBR) and overwrites your
|
|||
|
old boot manager.
|
|||
|
<P>Fortunately, the Solaris boot manager
|
|||
|
is able to chain-boot. For this to work you have to put your
|
|||
|
old boot loader (e.g. lilo) into the boot sector of one primary
|
|||
|
Linux partition.
|
|||
|
<P>For lilo this means: look at your
|
|||
|
/etc/lilo.conf. Look for the <CODE>boot=</CODE>
|
|||
|
line. If it is something like <CODE>boot=/dev/hda1</CODE>
|
|||
|
everything is fine. But if it<69>s something like
|
|||
|
<CODE>boot=/dev/hda</CODE> it points to the MBR. Please change
|
|||
|
it to point to a primary Linux partition
|
|||
|
(e.g. <CODE>boot=/dev/hda1</CODE>)
|
|||
|
<P>A way to check if your
|
|||
|
boot-loader is chain-loadable is installing lilo in to the
|
|||
|
MBR and trying to chain load your other boot-manager. I used
|
|||
|
the following file called lilo.conf.mbr for
|
|||
|
this:
|
|||
|
<HR>
|
|||
|
<PRE>
|
|||
|
#lilo.conf.mbr
|
|||
|
#Lilo in Master Boot Record doing nothing but chain-loading another lilo
|
|||
|
boot=/dev/hda
|
|||
|
root=/dev/hda5
|
|||
|
install=/boot/boot.b
|
|||
|
map=/boot/map
|
|||
|
vga=ask
|
|||
|
delay=50
|
|||
|
other=/dev/hda1
|
|||
|
label=lilochain
|
|||
|
</PRE>
|
|||
|
<HR>
|
|||
|
|
|||
|
You can then
|
|||
|
run <CODE>lilo -C lilo.conf.mbr</CODE> to install lilo into your
|
|||
|
MBR. And don<6F>t forget to run <CODE>lilo</CODE> to have lilo in
|
|||
|
the boot sector of your hard-drive.
|
|||
|
<P>If you reboot
|
|||
|
now, you should have a lilo-prompt. When you select <CODE>other</CODE> this
|
|||
|
chain loads the old lilo, which in turn loads Linux.
|
|||
|
<HR>
|
|||
|
<A HREF="Linux+Solaris-4.html">Next</A>
|
|||
|
<A HREF="Linux+Solaris-2.html">Previous</A>
|
|||
|
<A HREF="Linux+Solaris.html#toc3">Contents</A>
|
|||
|
</BODY>
|
|||
|
</HTML>
|